3 ms·
> I for one am very glad that systemd modernized things a bit and helped remove some of this stuff from the equation. I, for one, I'm glad there are still opti
by TacticalCoder 5y ago
> I for one am very glad that systemd modernized things a bit and helped remove some of this stuff from the equation.
I, for one, I'm glad there are still options and that even Debian let the door open to, one day, switching to something else than systemd.
I'm running Devuan (Chimaera) now and it's fine (for my needs).
It's not all rosy: there's something to be said about the insane kitchen sink that systemd is. Having the PID1 so gigantic, with its tentacles everywhere in the system, ain't something the Linux community should be proud of. I'm very happy that, so far, Linus is resisting and nothing in the kernel is (yet?) tied to systemd.
Linux is about choices too. The day there ain't no choice anymore, I'm switching to a BSD.
I'm running Linus' Linux. Not IBM/Red Hat/Poettering's Linux.
- dale_glass 5y agoPID 1 isn't particularly gigantic under systemd. Most actual work is delegated to other binaries. Eg, journald isn't PID 1. Personally, I take the opposite stance. I have very little ideology besides things being open source. To me a machine is a tool to do a job, and if systemd does the job better, then that's the right tool, regardless of any violation of principles that it might involve. There's definitely good ideas in the Unix model, but if the model ceases to be useful, it's time to throw the bad parts out. I also have no issues whatsoever with running Red Hat's Linux (I use Fedora). It does the job, it provides the tools I like, that's what matters.
- trasz 5y agoIt doesn’t matter if PID 1 isn’t gigantic if it depends on stuff that is.
- dale_glass 5y agoThere are legitimate concerns for PID 1 being small and stable, since if that doesn't work you have big issues. The rest doesn't really matter. They're separate processes and many are task specific and not used if you don't need that particular bit of functionality.