[Pkg-sysvinit-devel] Bug#768060: sysvinit-core doesn't trigger a dracut initrd rebuild if installed after systemd

matteo nunziati eng.matteo.nunziati at gmail.com
Tue Nov 4 15:47:48 UTC 2014

Package: sysvinit-core
Severity: normal

Dear Maintainer,

I'm running a weekly updated jessie/sid.
systemd is the default init, dracut the default
initram generator.

last sunday I've tried to install sysvinit-core along with
systemd-shim to substitute the systemd init process and
login to gnome after a sysv init (makefile style).

the reboot still used systemd as init system.

after investigation I've rebuild the initrd with dracut,
$ dracut --omit="systemd"

the new initrd actually used sysv to init the system and
everything has gone fine.

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages sysvinit-core depends on:
ii  debconf [debconf-2.0]  1.5.53
ii  debianutils            4.4
ii  initscripts            2.88dsf-53.4
ii  libc6                  2.19-12
ii  libselinux1            2.3-2
ii  libsepol1              2.3-2
ii  sysv-rc                2.88dsf-53.4
ii  sysvinit-utils         2.88dsf-53.4

sysvinit-core recommends no packages.

sysvinit-core suggests no packages.

More information about the Pkg-sysvinit-devel mailing list