Incoming 20-page comments section:
Announcement
Collapse
No announcement yet.
systemd Rolling Out "run0" As sudo Alternative
Collapse
X
-
Originally posted by Kjell View PostYou can't opt-out of most features unless you compile it yourself
- Likes 24
Comment
-
Originally posted by nvaert1986 View PostThere's nothing or nobody forcing you to use a specific feature
Majority of non obscure distros come with hard dependency on systemd
The package itself is usually compiled with all modules even if you personally don't use them
If you try packages from Arch Linux's repository in Artix Linux (fork with alternative init), you'll notice how deeply rooted systemd has become. Lots of packages are requiring various components like systemd-run / libsystemd
Code:# Modules included out of the box with minimal "base" pacstrap in Arch Linux systemd-ac-power systemd-analyze systemd-ask-password systemd-cat systemd-cgls systemd-cgtop systemd-confext systemd-creds systemd-cryptenroll systemd-cryptsetup systemd-delta systemd-detect-virt systemd-dissect systemd-escape systemd-firstboot systemd-hwdb systemd-id128 systemd-inhibit systemd-journald systemd-libs systemd-logind systemd-machine-id-setup systemd-machined systemd-mount systemd-notify systemd-nspawn systemd-path systemd-repart systemd-resolve systemd-run systemd-socket-activate systemd-stdio-bridge systemd-sysext systemd-sysusers systemd-tmpfiles systemd-tty-ask-password-agent systemd-udevd systemd-umount systemd-userwork systemd-vmspawn systemd-userdbd (soon) systemd-importctl (soon) systemd-ssh-generator (soon) systemd-vpick (user dependent) systemd-boot (user dependent) systemd-homed
Last edited by Kjell; 03 June 2024, 11:46 AM.
- Likes 7
Comment
-
The basic problem with packaging more and more into systemd is not that it happens, but that it happens in a way that is not interoperable.
No-one would care if you could take a distro, and switch out systemd package tot sysV and be done. But since systemd is written in such a way that it is not possible, it becomes a problem.
Same has happened previously with DE:s. You are supposed to just be able to install a DE package and run another DE on your setup. But in practice it's very problematic, and people just suggest to install a spin of the OS with the desired DE.
These are issues of people not caring to be interoperable, since their project is all that matters.
- Likes 12
Comment
-
Originally posted by Noitatsidem View Post
can you explain a bit more about this bad moderation?
- Likes 6
Comment
-
Originally posted by Kjell View Postsystemd is vendor lock-in at this point
You can't opt-out of most features unless you compile it yourself
Packages are gradually starting to depend on functionality of systemd
We no longer have the freedom of choice as they're pushing more and more features into a single point of failure.. XZ vulnerability depended on functionality of systemd (edit: for those missing the bigger point, such problems are a biproduct of feature creep. Also, let's not discuss how buggy core components like systemd-networkd & systemd-resolved are and how many attack vectors systemd introduces with the amount of modules they provide).
How far will this go?
systemd/GNU/Linux
- Likes 7
Comment
-
Originally posted by Kjell View Post
Wrong
Majority of non obscure distros come with hard dependency on systemd
The package itself is usually compiled with all modules even if you personally don't use them
If you try packages from Arch Linux's repository in Artix Linux (fork with alternative init), you'll notice how deeply rooted systemd is. E.g. packages requiring various components like systemd-run
Code:systemd-ac-power systemd-analyze systemd-ask-password systemd-cat systemd-cgls systemd-cgtop systemd-confext systemd-creds systemd-cryptenroll systemd-cryptsetup systemd-delta systemd-detect-virt systemd-dissect systemd-escape systemd-firstboot systemd-hwdb systemd-id128 systemd-inhibit systemd-machine-id-setup systemd-mount systemd-notify systemd-nspawn systemd-path systemd-repart systemd-resolve systemd-run systemd-socket-activate systemd-stdio-bridge systemd-sysext systemd-sysusers systemd-tmpfiles systemd-tty-ask-password-agent systemd-umount systemd-vmspawn (soon) systemd-importctl (soon) systemd-ssh-generator (soon) systemd-vpick (distro dependent) systemd-boot (distro dependent) systemd-homed
- Likes 19
Comment
-
Originally posted by back2未來 View Post[ basic criticism is, that systemd is binaries, while some predecessors are scripts utilizing more basic system tools, that are under strong review(?) ]
- Likes 12
Comment
-
Originally posted by holunder View PostBTW, please come to the Fediverse/Mastodon, Phoronix!
And I don’t mean Mastodon•social because many instances are already blocking them for bad moderation.
- Likes 3
Comment
Comment