I switched today to slackware-current on one of my desktops to play with it and ran directly into a problem.
Since ages my lilo.conf has two entries for slackware. One for runlevel 3 and one for runlevel 4.
Code:
lba32
boot = /dev/sda1
compact
bitmap = /boot/slack.bmp
bmp-colors = 255,0,255,0,255,0
bmp-table = 60,6,1,16
bmp-timer = 65,27,0,255
append=" vt.default_utf8=1"
prompt
timeout = 50
vga = 794
image = /boot/vmlinuz
root = /dev/mapper/crypt-vg-root
initrd = /boot/initrd.gz
label = Slackware
append = "init 4"
read-only
image = /boot/vmlinuz
root = /dev/mapper/crypt-vg-root
initrd = /boot/initrd.gz
label = Slackware-r3
append = "init 3"
read-only
Since the upgrade this is no more possible because I get a kernel panic as soon as
udevadm trigger is called. The stack says something about an unknown boot option. Because that i removed the append lines from my lilo.conf and i was able to boot the system. The crash happens when udev is called from within the ramdisk and afterwards. I tried both.
My question is now. Is this a bug in udev or expected? I have this setup since at least 5 years and had never problems with that. What do I have to do to be able to select the runlevel at boot time?