Systemd is an init system (the first process that manages/runs everything else). However it does far more than a traditional init system; arguably it’s tendrils are all over mainstream Linux now.
GLIBC is the GNU Project’s implementation of the C standard library. It is a wrapper around system calls of the kernel for application use.
To be fair, I don’t think systemd is classified as just an init system anymore. It’s a software suite that just “conveniently” happened to have an init system included.
I agree, some of us just want a simple init system that isn’t millions of lines of code and to be able to pick our own parts to use in a UNIXY fashion - If it ain’t broke why fix it…
For example on my alpine system I have acpid, crond, dhcpcd, openntpd, seatd, udev, wpa_supplicant as services that systemd would replace.
I’ve been using linux for ~2 years now and only know one of these (GUI installer), anyone smarter than me can explain what they are?
Systemd is an init system (the first process that manages/runs everything else). However it does far more than a traditional init system; arguably it’s tendrils are all over mainstream Linux now.
GLIBC is the GNU Project’s implementation of the C standard library. It is a wrapper around system calls of the kernel for application use.
To be fair, I don’t think systemd is classified as just an init system anymore. It’s a software suite that just “conveniently” happened to have an init system included.
I agree, some of us just want a simple init system that isn’t millions of lines of code and to be able to pick our own parts to use in a UNIXY fashion - If it ain’t broke why fix it…
For example on my alpine system I have acpid, crond, dhcpcd, openntpd, seatd, udev, wpa_supplicant as services that systemd would replace.