Remix.run Logo
bryanlarsen 4 hours ago

systemd is not a monolith, and distros make different choices on what portions of systemd they which to ship and enable by default.

For example, not all distros ship and use systemd-resolved by default, to choose from your list.

bsimpson 3 hours ago | parent [-]

systemd-boot competes with grub

bryanlarsen 12 minutes ago | parent | next [-]

Even better example, I don't think systemd-boot is broadly adopted yet although there are certainly some distributions that use it.

5G_activated 3 hours ago | parent | prev [-]

and grub is a rotting pile while systemd-boot is a simple boot entry multiplexer that rides off the kernel's capability of being run as an EFI executable, it just happens to live in systemd's tree. not a good example

fragmede 3 hours ago | parent [-]

It's a pretty good example of why people think systemd is bloated and does too much. It's a simple boot entry multiplexer. Does it need to live in systemd's tree?

bryanlarsen an hour ago | parent | next [-]

Nobody complains about a very wide variety of only vaguely related utilities being in the Gnu coreutils tree.

Foxboron an hour ago | parent [-]

Nor the 20 or so odd reimplementations of various filesystem drivers and LUKS encryption in the grub2 tree.

But, who is counting?

5G_activated an hour ago | parent | prev [-]

so its a marketing problem, irregardless of whether it's in systemd's tree because the systemd maintainers want to maintain it in-tree