On Thu, 2014-05-08 at 18:42 -0700, Russ Allbery wrote: > Svante Signell <svante.sign...@gmail.com> writes: > > > I'm trying to install as little as possible of systemd stuff, and guess > > what happens: When booting one of the laptops boot starts with: > > systyemd-fsck <disks> > > > Is systemd taking over everything?? How to reduce the number of > > systemd-* features. > > It's a small wrapper around fsck that handles status reporting in a way > that works well with the journal and with systemd boot-time status > reporting and takes care of some dbus coordination and whatnot. I believe > It's basically the equivalent of all the shell logic in checkroot.sh and > checkfs.sh. In other words, well within the mandate for anything that > handles early boot, replacing shell scripts that were previously provided > by initscripts. > > The actual fsck work is still done by the separate fsck binary, just like > it always has been.
Well, I've not been asked if I wanted to switch to systemd based boot when upgrading. I think this is a bug in init system choice and should be reported. How to go back to sysvinit? Installed packages: ii libpam-systemd:amd64 204-10 ii libsystemd-daemon0:amd64 204-10 ii libsystemd-id128-0:amd64 204-10 ii libsystemd-journal0:amd64 204-10 ii libsystemd-login0:amd64 204-10 ii systemd 204-10 ii systemd-sysv 204-10 ii sysvinit 2.88dsf-53 ii initscripts 2.88dsf-53 ii sysv-rc 2.88dsf-53 Which ones can I safely remove when going back to sysvinit? -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1399631705.2096.16.camel@PackardBell-PC