Ok, I got my lilo.conf file. This is all installed on a USB Slimdrive. When I boot it all up I get a kernal error, and I think it's related to the warning it gives me when I run lilo -v. But first, the lilo.conf file
When I run lilo -v, this is the output:Code:lba32 boot=/dev/sdb root=/dev/sdb3 # bitmap=/boot/sarge.bmp # bmp-colors=1,,0,2,,0 # bmp-table=120p,173p,1,15,17 # bmp-timer=254p,432p,1,0,0 # install=bmp prompt timeout=50 # map=/boot/map vga=0x317 image=/boot/vmlinuz label="BT4" read-only initrd=/boot/splash.initrd append=quiet
Now I know the boot partition /dev/sdb1 is flagged as bootable when I go into fdisk /dev/sdb. The /dev/sdb2 partition is the swap, and the /dev/sdb3 is the root folder. This could only mean that my problem should be somewhere in the lilo.conf file, right? I'll post the fstab just in case:Code:Reading boot sector from /dev/sdb Warning: /dev/sdb is not on the first disk Using MENU secondary loader Calling map_insert_data Boot image: /boot/vmlinuz Mapping RAM disk /boot/splash.initrd Added BT4 * Writing boot sector. /boot/boot.0810 exists - no boot sector backup copy made. One warning was issued.
When I go to boot off the USB harddrive, it gives me this error on the backtrack bootup screen, after I selcet "BT4" from Lilo.Code:/dev/sdb3 / reiserfs defaults 0 0 # AutoUpdate /dev/sdb2 none swap sw 0 0 proc /proc proc defaults 0 0 # AutoUpdate sysfs /sys sysfs defaults 0 0 # AutoUpdate devpts /dev/pts devpts gid=5,mode=620 0 0 # AutoUpdate tmpfs /dev/shm tmpfs defaults 0 0 # AutoUpdate
"Kernal panic - not syncing: VFS:Unable to mount root fs on unknown-block(8,19)"



