Hi,
boot the CD and be sure to know on which device /dev/sd? you've installed Slackware. Now chroot into your Slackware installation:
Code:
mkdir /mnt/slack
mount /dev/sda? /mnt/slack
mount -t proc none /mnt/slack/proc
mount --rbind /sys /mnt/slack/sys
mount --rbind /dev /mnt/slack/dev
The ? stands for a, b, or what else is correct on your system.
now you're within your Slackware-installation and can edit lilo.conf as if Slackware were running
I would recommend to add the huge-kernel as a failsafe option to lilo.conf, here as an example (a part of) my lilo.conf
Code:
# Linux bootable partition config begins
image = /boot/vmlinuz
initrd = /boot/initrd.gz
append = "resume=/dev/sda9"
root = /dev/sda5
label = Slack64-current
read-only
###
image = /boot/vmlinuz-huge-3.5.4
root = /dev/sda5
label = failsafe
read-only
# Linux bootable partition config ends
I'm using also the generic kernel (as the default) but when my initrd would not work, I can chose for the failsafe option.
Afterwards run lilo and simply type "exit" to leave the chroot-environment. Then you can reboot the system.
Markus
BTW: Slackware uses elvis as default editor, use vi instead of vim when you've booted the install-CD