On Wed, Oct 17, 2018 at 04:20:36PM -0400, Steve Litt wrote: > I'm not reproducing your results of functional Linux difficulties. I've > heard udev will now deliberately sabotage systems not using systemd as > PID1, but don't we have vdev and eudev? I'm personally running the > runit init system, and so far it works perfectly with every daemon > except the very, very few that provide no way to run the program in the > foreground. Your assertion gets traction on Gnome, and to a lesser > extent KDE and xfce. But there are so many good WM/DEs (Window > Manager/Desktop Environment) that foregoing those three WM/DEs is no > problem at all. > > About reimplementing the systemd functions: Most of them are either > marketing buzz or attempts to make systemd irreplaceable. How often do > you use "socket activation?" What's wrong with xinetd if you still want > to use that ancient paradigm left over from when you had to count every > byte and process? > > Multiseating? When's the last time you had serial cables to monitors? > We have much more efficient Gigabit Eternet. > > Cgroups? There are other ways to do Cgroups without systemd, and a lot > of systemd's buzz for using cgroups is available in runit, which has > the finish script to clean up, and the finish script for process A can > stop process b, c and d if that's desired. There's almost nothing > *needed* that systemd can do that runit can't do, except lock your OS > in a "no replaceable parts shield. > > Fast boot? Unless the system is a television or a container that's > constantly going up and down, who cares? Besides, s6 offers parallel > startup, so it can produce pretty darn fast boots. > > The systemd standard for daemons reporting their "upness"? Runit and s6 > enable you to make the test of your choice to determine another > daemon's functionality, without relying on what's returned from the > other daemon (which may be wrong). > > > > > Sometimes the only way out is through. > > > > And sometimes you're already in the right place, and the best move is > nothing. Systemd is nowhere near a done deal. Right now, on the > Debian-User mailing list, Debianers are discussing various ways to keep > using Debian with sysvinit, and some are even considering additional > init systems beyond the false choice of systemd vs sysvinit.
+1 -- Fernando M. Maresca - - - - - - - - - - - - - Cel: 221 15 545 8196 Tel: 221 450 5378 _______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
