Comment by 5G_activated
2 days ago
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
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?
Nobody complains about a very wide variety of only vaguely related utilities being in the Gnu coreutils tree.
Nor the 20 or so odd reimplementations of various filesystem drivers and LUKS encryption in the grub2 tree.
But, who is counting?
1 reply →
so its a marketing problem, irregardless of whether it's in systemd's tree because the systemd maintainers want to maintain it in-tree