71
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 16 Feb 2026
71 points (100.0% liked)
Linux
12450 readers
144 users here now
A community for everything relating to the GNU/Linux operating system (except the memes!)
Also, check out:
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
founded 2 years ago
MODERATORS
Compromising/crashing pid1 (which becomes increasing likely when the program is massive) takes down the entire system. pid1 should only be the initial init (which should be as small as possible, basically a stub) and start the service manager as a separate pid. This allows the system to gracefully recover by restarting other processes without fully locking-up/crashing. It is a bad practice.
@Neptr @epik_kiwi This is the truth. I'm a #guix\#shepherd user myself, and even then I'm starting to think (because feature creep happens to the best of us) that a minimal cut-down version running as PID1, and then runs up a more sophisticated version after itself, would be on the whole a better set-up. It should also be possible to run alternative OS managers side-by-side.
Admittedly, Shepherd is really good and I'm reluctant to make systems more complicated, but it's the choice that matters.