Somehow my system has gotten into a state where the choice of bootable kernel I make during bootup is being ignored. Whatever kernel I choose, I get the one labelled "Linux" in lilo.conf. I've tried running lilo several times, without any improvement. One clue is the pseudo-file /proc/cmdline, which reads: auto BOOT_IMAGE=Linux root=2102 2.4.18-W No matter what I do I can't get rid of that BOOT_IMAGE specification, which seems to be forcing lilo to select the image with the "Linux" label. Here's my lilo.conf file: ------ begin quoted file # LILO configuration file # Start LILO global Section # If you want to prevent console users to boot with init=/bin/bash, # restrict usage of boot params by setting a passwd and using the option # restricted. #password=bootpwd #restricted lba32 boot=/dev/hde # vga=normal install = /boot/boot.b message = /boot/message menu-title = "Suillus boot choices" menu-scheme=Wg:kw:Wg:Wg # read-only prompt timeout=50 root=/dev/hde2 # End LILO global Section # image = /boot/vmlinuz # root = /dev/hde2 label = Linux initrd = /boot/initrd # other = /dev/hde3 label = "Windows 98" # table = /dev/hde # other = /dev/hde1 label = DOS # table = /dev/hde # image = /boot/memtest.bin label = memtest86 # image = /boot/vmlinuz-2.4.17 # root = /dev/hde2 label = "Linux 2.4.17" initrd = /boot/initrd-2.4.17 image = /boot/vmlinuz-2.4.17A root = /dev/hde2 label = "Linux 2.4.17A" initrd = /boot/initrd-2.4.17A # image = /boot/vmlinuz-2.4.18-Win4Lin # root = /dev/hde2 label = "Linux 2.4.18-W" initrd = /boot/initrd-2.4.18-Win4Lin ------ end quoted file The file /boot/vmlinuz is linked to the kernel for 2.4.17A, which is /boot/vmlinuz-2.4.17A. The boot device is /dev/hde rather than /dev/hda because I'm using a Promise IDE controller. Ideas, anyone? Paul Abrahams
participants (1)
-
Paul W. Abrahams