On Sun, 2018-10-14 at 18:19 +0200, to...@tuxteam.de wrote: > On Sun, Oct 14, 2018 at 04:57:49PM +0100, Tixy wrote: > > On Sun, 2018-10-14 at 10:23 -0400, Dan Ritter wrote: > > > Throughout Jessie and Stretch, I have been running Debian without > > > systemd as the init system. If systemd became installed by > > > accident, > > > I > > > promptly removed it in favor of sysvinit. > > > > > > I have done so on six desktops, two laptops, and a large number > > > (I > > > will > > > not specify, but in the hundreds) of servers. > > > > > > I have encountered no problems that can be attributed to my > > > choice of > > > init system. > > > > I take it you don't have encrypted disks then, because with them > > Stretch will hang on shutdown if you aren't using systemd as the > > init > > process [...] > > This is fixable. I've encrypted disks (unencrypted boot plus one LUKS > partition containing an LVM whithin which the other partitions live).
That's my setup too. > All under sysvinit. > > If there's interest, I can recap what I had to do to fix it (it > seemed > obvious to me at the time, but memory is treacherous). Thanks for the offer, personally I'm sticking with systemd for now. BTW, I just noticed, the Debian bug I mentioned [1] has had recent activity and was marked as fixed a month ago, so I guess Buster will be fixed. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794721 -- Tixy
