You are not logged in.
Hello,
I just installed Devuan Jessie.
I found a systemd-folder in /lib/ and also in /etc/
What is the purpose of these folders in a non-systemd distro?
In Grub I found two 3.16 kernels. One has a (SysV) behind the kernel name. What is the difference?
Does the other use systemd?
Thanks in advance.
Offline
Many packages ship with start-up files for systemd, but work without systemd. For a longer answer see :-
https://dev1galaxy.org/viewtopic.php?id=1925
Geoff
Offline
Thank you for your quick reply! That answers my first question about the systemd files and folders.
What about the two different kernels?
In Grub:
- Devuan GNU/Linux, with Linux 3.16.0-5-amd64
- Devuan GNU/Linux, with Linux 3.16.0-5-amd64 (sysvinit)
What is the difference?
Offline
It's not two different kernels, it's two different entries in the boot menu. Look at the menuentry for each in /boot/grub/grub.cfg to see if there's a difference in the linux lines.
I've only seen that on debian, where you had a choice to boot with sysvinit or systemd. How did you install devuan?
Offline
Thanks fsmithred,
I Installed the Devuan net-install, without X.
Here the menuentry for each in my /boot/grub/grub.cfg:
}
submenu 'Advanced options for Devuan GNU/Linux' $menuentry_id_option 'gnulinux-advanced-c562ab2a-f161-4647-b133-075f03f08ca4' {
menuentry 'Devuan GNU/Linux, with Linux 3.16.0-5-amd64' --class devuan --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.16.0-5-amd64-advanced-c562ab2a-f161-4647-b133-075f03f08ca4' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 bfd5444c-4928-4ba9-9b71-6e9ae93a34df
else
search --no-floppy --fs-uuid --set=root bfd5444c-4928-4ba9-9b71-6e9ae93a34df
fi
echo 'Loading Linux 3.16.0-5-amd64 ...'
linux /vmlinuz-3.16.0-5-amd64 root=/dev/mapper/debinox--vg-root ro quiet
echo 'Loading initial ramdisk ...'
initrd /initrd.img-3.16.0-5-amd64
}
menuentry 'Devuan GNU/Linux, with Linux 3.16.0-5-amd64 (sysvinit)' --class devuan --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.16.0-5-amd64-init-sysvinit-c562ab2a-f161-4647-b133-075f03f08ca4' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 bfd5444c-4928-4ba9-9b71-6e9ae93a34df
else
search --no-floppy --fs-uuid --set=root bfd5444c-4928-4ba9-9b71-6e9ae93a34df
fi
echo 'Loading Linux 3.16.0-5-amd64 ...'
linux /vmlinuz-3.16.0-5-amd64 root=/dev/mapper/debinox--vg-root ro quiet init=/lib/sysvinit/init
echo 'Loading initial ramdisk ...'
initrd /initrd.img-3.16.0-5-amd64
Thanks for the explanation. There is no real problem here, but I am just curious and want to know what is happening "under the hood'.
Offline
The sysvinit entry in the boot menu has 'init=/lib/sysvinit/init'. That gets used in debian when systemd is installed along with sysvinit, and in that case, /sbin/init is a symbolic link pointing to systemd. In devuan, /sbin/init should be the real init (a real file, not a symlink.) Does /lib/sysvinit/init even exist on your setup?
Offline
Does /lib/sysvinit/init even exist on your setup?
Yes it exists.
Edit:
Just because of curiosity I checked an other devuan computer (desktop) here. Strange thing is that there the /lib/sysvinit/ does NOT exist.
The only difference with my laptop is that I replaced the kernel for libre-kernel 4.16 and installed openbox as the windowmanager.
So on my laptop (devuan core, no X) it does exist, not on my desktop (devuan core + librekernel + Xserver + openbox) ....
Last edited by Ducas (2018-04-04 19:01:48)
Offline