

How ironic!
Now post the output:
ls -ld /run/systemd/io.*
Collecting downvotes since before forums even had thank you’s.


How ironic!
Now post the output:
ls -ld /run/systemd/io.*


First one on the list.
% readelf -d /usr/bin/bootctl | rg -r '$1' '.*NEEDED.*\[(.*)\]'
libsystemd-shared-262-1.so
libgcc_s.so.1
libc.so.6


Share the content of the file 90-systemd.preset from your system.


Let’s play a game. Pick a “separate utility” from the list above, and let’s see if you know what you’re talking about, or just waffling.


Your “separate utilities developed under systemd umbrella” claim was simply false.
Your attempted retort was even more funny, since many coreutils implementations can actually literally be built into a single binary with many symlinks, with dispatch done based on arg0. It’s even the preferred packaging option.
There are a lot of interdependencies within those source trees. Nothing is self-contained. So the “itz just monorepo bro” is also false.
they also overreaching and that’s THE point?
You literally just listed multiple projects 🤭, where their collective surface is also nowhere close the the systemd forced hegemony. Maybe they should all unite and join the “umbrella”.


No, they aren’t. These are the binaries from THE systemd package , built from systemd releases, from THE systemd repo.
A single source tree looking like an “umbrella”, and an overreaching one at that, is THE point.


I’m the type of person who wants more systemd in my computer
Hear hear. A couple hundred more should do the trick.
bootctl
busctl
coredumpctl
homectl
hostnamectl
importctl
installkernel -> kernel-install
journalctl
kernel-install
localectl
loginctl
machinectl
mount.ddi -> systemd-dissect
mount.mstack -> systemd-mstack
mount.storage -> storagectl
networkctl
oomctl
portablectl
resolvectl
run0 -> systemd-run
storagectl
systemctl
systemd-ac-power
systemd-analyze
systemd-ask-password
systemd-cat
systemd-cgls
systemd-cgtop
systemd-confext -> systemd-sysext
systemd-creds
systemd-cryptenroll
systemd-cryptsetup
systemd-delta
systemd-detect-virt
systemd-dissect
systemd-escape
systemd-firstboot
systemd-home-fallback-shell -> homectl
systemd-hwdb
systemd-id128
systemd-inhibit
systemd-machine-id-setup
systemd-mount
systemd-mstack
systemd-mute-console
systemd-notify
systemd-nspawn
systemd-path
systemd-pty-forward
systemd-repart
systemd-resolve -> resolvectl
systemd-run
systemd-socket-activate
systemd-stdio-bridge
systemd-sysext
systemd-sysinstall
systemd-sysusers
systemd-tmpfiles
systemd-tty-ask-password-agent
systemd-umount -> systemd-mount
systemd-vmspawn
systemd-vpick
timedatectl
udevadm
updatectl
userdbctl
varlinkctl


A PR fixing the issue has already been submitted (which surfaced another issue, but it doesn’t concern stable).
People likening this to the issue behind cve-rs (which is blocked on a major rework) are clueless, which happens to be par for the course regarding anything Rust. So no surprises there.


But I don’t understand why everyone else has an outdated version number.
Who are you talking about? If it’s AUR uploaders, the version you see is the version in the last uploaded PKGBUILD. AUR itself doesn’t build anything. And PKGBUILD uploaders don’t need to keep uploading to bump the version because it auto-updates when a user builds it. They only need to upload to fix builds if they get broken, or update meta info, …etc.
git (vcs in general) packages always update unless you pass --holdver with makepkg.
And just to be clear, that relates to git sources not the package name. The -git naming is just a convention that has no bearing on functionality.
Maybe its just a placeholder
Mostly yes. You can just put “0” or “1” initially. Build once, and it will be populated anyway.


The +nightly syntax is a rustup proxy feature, so a distro-packaged cargo won’t even parse it. Nightly is a different compiler every day.
export RUSTC_BOOTSTRAP=1 and you wouldn’t need rustup or nightly. It will work with your stable distro package.
clap = “4” and anyhow = “1” are ranges, and there’s no Cargo.lock.
you can do clap = "=4.x.x", ditto for all deps, direct and indirect.
Nightly is a different compiler every day.
Nothing about that script is fixed except its text.
Is nix finished free-standing software?
I think the other user meant that ls output is not supposed to be treated as parsable, because the tool doesn’t offer any guarantees in that regards.
Shells have built-in support for globbing files anyway. xargs is also not needed. If someone is allergic to using a shell for loop, find always had -exec with ; instead + which wouldn’t trip on too many arguments.


Vibe-coded trash + outdated models.
Wouldn’t have expected anything better from a trash website.


They didn’t use that technique. Some vibers do ask Codex to review Claude and vice versa. But since this is Anthropic-owned, they did use “parallel agents”, but they were all Claude.


You could have searched for some benchmarks yourself, instead of thinking you’re winning an argument in such a stupid manner.
Note that Jarred himself (bun creator) wouldn’t push against this either. Instead, he will sell you the aggregate performance talking point (as another user did), which is why I made my deliberately facetious comment about webshittery.


can execute TypeScript directly.
Did the word “directly” get the same fate the word “literally” got? As in, it completely lost its real meaning?
Bundling a compiler/transpiler and directing inotify at a source directory (for glorious hot-reloading) doesn’t a language “runtime” make. Otherwise, I can create “runtimes” for any language in three lines of code right now.
unless you’re saying that Bun is slower.
Are you saying JavaScriptCore is faster than V8? Or is the majority of time in webshittery operations not spent on actually running code, and that’s how bun “wins” ?


I’m going to call cargo a Rust runtime from now on, considering cargo-script exists.


First of all. Strictly speaking, there is no such a thing as a TS runtime. TS compiles to JS.
Second of all, bun binds against JavaScriptCore, which is the JS engine used in Safari. Node binds against V8, which is the engine used by Blink (Chromium et al). Both are implemented in C++. And the latter is considered the fastest engine.
Ironically, both engines are mentioned by name in the very bun blog post being discussed, which points to a problem that is almost bigger than mere tech literacy from the pseudo-intellectual OP.


You can interface with a C++ JS engine without
unsafe(which is equivalent to just using C btw), if you just really put a real effort into it.
😇
I do love me some internet gantry commentary. Especially when it’s super confident and acting knowledgable, with multiple layers of genius on display.


You clearly don’t even know what unsafe in rust means. And it’s not something you can avoid when FFI is involved, slopping involved or otherwise.
Good.
So the tool YOU chose is NOT:
libsystemd-shared.sodep without requiring looking further) ✅This and the sibling sub-thread where I mentioned presets show with actual facts how the systemd forced hegemony actually works, where it’s not just a simple case of “they just have some stand-alone cli tools under their umbrella bro”.
The project itself wouldn’t try to (clumsily) dispute this either, since it’s at the core of what they consider a selling point; interface unification and deeper integration with the system.