Hi,

my boot menu contains three entries per kernel: the regular and rescue one
and a new entry '(sysvinit)'. My system only has sysvinit installed though,
so this is kinda misleading as it’s actually the same as the regular entry.

I think that on systems with only one init system installed those entries
should not be generated, to not confuse less versed users.

That's certainly not intended behaviour.  What do these commands report?

  readlink -f /sbin/init
  readlink -f /lib/sysvinit/init

Thanks,

Colin Watson dixit:

With more debugging:

tglase@tglase-nb:~ $ readlink -f /sbin/init
/sbin/init
tglase@tglase-nb:~ $ readlink -f /lib/sysvinit/init
/lib/sysvinit/init
tglase@tglase-nb:~ $ ll /sbin/init /lib/sysvinit/init
-rwxr-xr-x 1 root root 40648 May 21 13:34 /lib/sysvinit/init*
-rwxr-xr-x 1 root root 40648 May 21 13:34 /sbin/init*
tglase@tglase-nb:~ $ dpkg -S /sbin/init /lib/sysvinit/init
sysvinit-core: /sbin/init
sysvinit: /lib/sysvinit/init
tglase@tglase-nb:~ $ cd /var/cache/apt/archives
tglase@tglase-nb:/var/cache/apt/archives $ dpkg-deb -c sysvinit-core*.deb | fgrep /sbin/init
-rwxr-xr-x root/root     40648 2015-05-21 13:34 ./sbin/init
tglase@tglase-nb:/var/cache/apt/archives $ dpkg-deb -c sysvinit_*.deb | fgrep /lib/sysvinit/init
-rwxr-xr-x root/root     40648 2015-05-21 13:34 ./lib/sysvinit/init

On some *other* systems, I have a local diversion, so /sbin/init
should be treated with care (i386 systems with an amd64 kernel):

root@evolvis:~ # dpkg-divert --list | fgrep init
local diversion of /sbin/init to /sbin/init.real
root@evolvis:~ # ls -l /sbin/init*
-r-xr-xr-x 1 root root    55 Jul 22 10:47 /sbin/init
-rwxr-xr-x 1 root root 35216 Jul 18  2013 /sbin/init.real
root@evolvis:~ # cat /sbin/init
#!/bin/mksh-static
exec /usr/bin/linux32 /sbin/init.real "$@"

That’s not on this system, though (which is a pure amd64 laptop,
with a few i386 things installed).

bye,
//mirabilos