Subj : Re: systemd
To   : Gerrit Kuehn
From : Tony Langdon
Date : Wed Dec 09 2020 19:43:00

-=> On 12-08-20 13:16, Gerrit Kuehn wrote to Dennis Katsonis <=-

 GK> Hello Dennis!

 GK> 08 Dec 20 21:54, Dennis Katsonis wrote to Gerrit Kuehn:


 DK> Systemd isn't that bad.  It's much better than Lennart's pulseaudio,
 DK> now THAT sucks.

 GK> Tell me about it. OSS always worked fine for me. So did JACK.

OSS worked, but limited in some ways.  ALSA generally works well for my needs. 
JACK looks good, but I've never actually used it, even though it's been around
for donkeys years.

 GK> As I said, this wholly depends on your use case. If you're running a
 GK> notebook, I totally see the benefit. However, I have mainly servers and
 GK> a few workstations to maintain. These are not booted for days, weeks or
 GK> even months, and they hardly ever change their network settings. If
 GK> they boot, hardware detection alone might take minutes, so I absolutely
 GK> don't care about saving a few seconds afterwards during boot.
 GK> On the other hand, from day one I had a hard time making systemd *not*
 GK> causing race conditions and actually wait for things that are required
 GK> during boot on these machines, especially network connections and
 GK> remote mounts.

I don't have a need for everything to try starting all at once, and on spinning
metal, that can sometimes take longer (*cough* Windows *cough).  The thing I do
like about SystemV is that the login prompt comes up after everything has
started.

But as I said in the last message, I haven't had any issues with systemd.


.... Speed doesn't kill. Stopping very fast kills.
=== MultiMail/Win v0.51
--- SBBSecho 3.10-Linux
 * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)

.