Bug#751589: [Pkg-sysvinit-devel] Bug#751589: sysvinit-core: /sbin/init missing after switching from systemd to sysvinit

[Michael Gold]

On Sat, Jun 14, 2014 at 16:47:45 +0200, Petter Reinholdtsen wrote:
> [Michael Gold]
> > /sbin was available in the emergency shell and contained some files,
> > but 'init' wasn't there.  'dpkg -L sysvinit-core' ended at the line
> > '/sbin' (i.e., it was missing /sbin/shutdown, /sbin/init, etc.).  I
> > eventually figured out to run 'dpkg -i' on that .deb; this restored
> > /sbin/init, and then I was able to boot the system normally.
> 
> This is quite strange.  My version 2.88dsf-53.2 of sysvinit-core in
> unstable contain these files:
...
> root at freedomboxtest:~# dpkg -L sysvinit-core|grep sbin
> /sbin
> /sbin/init
> /sbin/halt
> /sbin/runlevel
> /sbin/shutdown
> /sbin/poweroff
> /sbin/reboot
> /sbin/telinit
> root at freedomboxtest:~# 
> 
> Is the amd64 build broken?  Or did dpkg mess up something?  I switched
> from systemd to sysvinit earlier today in a test machine using
> unstable, so that should work fine too.

The build is fine--those files are there in 2.88dsf-53 and 2.88dsf-53.2,
and "dpkg -L sysvinit-core" shows them now.  And after all, /sbin/init
appeared after running "dpkg -i" on the same file apt tried to install.

But I'm certain they were missing and the output ended at "/sbin" when I
ran the command in the emergency shell.  It seemed strange that the
/sbin directory would be included without any files in it.  I was also
surprised to see the manual, init.8.gz, without the associated binary.

-- Michael
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20140614/b28eae9a/attachment.sig>