[Followups set to comp.os.linux.misc]

Hi,

I previously had Windows 2000 (/dev/hda, 20GB WD200BB) and Slackware 9.1
(/dev/hdb, 13.5GB IBM-DJNA-371350) running together on my machine. LILO
was installed with the following configuration:

-- BEGIN lilo.conf --

boot=/dev/hda
map=/boot/map
install=/boot/boot.b
prompt
timeout = 300
default=Linux

vga = normal

image = /boot/vmlinuz
root = /dev/hdb3
label = Linux
read-only

image = /boot/vmlinuz.old
root = /dev/hdb3
label = Linux_old
read-only

other = /dev/hda1
label = Windows
table = /dev/hda

-- END lilo.conf --

This worked fine, and I knew that wasn't proper, so I upgraded to an 80GB
WD800JB drive. I needed to boot Windows before I had done anything to the
new drive (other than plug it in), and I figured that since LILO had been
installed to the first drive, which was still in the machine, it would at
least get me to the OS selection screen so I could boot Windows. Instead,
I got "L 01 01 01 01 01 01 ...". When I put the old IBM drive back in, it
booted fine, and after I had finished installing Arch 0.6 and LILO on the
new drive, it also booted fine.

So I was wondering what is stored on /dev/hdb when the boot device is
specified as /dev/hda. I'm assuming it has to do with my /boot partition,
but why could it not even list the available kernels to boot? Comments
and pointers to further reading are appreciated.

Thanks,

Brandan L.
--
bclennox \at eos \dot ncsu \dot edu