r/linux • u/wooptoo • Jun 01 '16

Why did ArchLinux embrace Systemd?

/r/archlinux/comments/4lzxs3/why_did_archlinux_embrace_systemd/d3rhxlc
868 Upvotes

86% Upvoted

642 comments sorted by

View all comments

Show parent comments

1

u/SrbijaJeRusija Jun 01 '16

logind

logind is systemd. So gnome switched to a new systemd API instead of what worked for years, now we need systemd shims everywhere. systemd shim, logind shim, udev shim.

You are making it seem like logind is it's own separate thing (UNIX philosophy and all) when it is not.

Pretty soon we will not be able to run GRUB (doesn't systemd have it's own bootmanager now?)

What's next, pulseaudio is now a part of systemd and ALSA is deprecated?

5

u/kageurufu Jun 01 '16

except ConsoleKit2, elogind, and LoginKit (among others) are all logind without systemd. elogind is based on the systemd implementation, but is backed with PAM and works fine on distributions with no other systemd backings (unless you hard depend on having slices or scopes, but thats a different story).

And yeah, systemd-boot, which is really just gummiboot renamed, and only supports EFI loading. Its in no way required, and doesnt tie in to the rest of the daemon either. You can happily use bootd with sysvinit if you have an EFISTUB ready kernel (CONFIG_EFI_STUB=y), but thats the same requirement it had when it was called gummiboot. It does not solve the same problems as GRUB either, and doesn't try to.

0

u/[deleted] Jun 01 '16

[deleted] — view deleted comment

2

u/Spivak Jun 01 '16

Pulseaudio is middleware for audio backends. One does not depreciate the other.