Jack Owens <jack@cox.net> ha scritto:

>image=/boot/vmlinuz-2.4.20-8
> label=2.4.20-8
> append="root=LABEL=/12"
> read-only
> initrd=/boot/initrd-2.4.20-8.img
>
>image=/boot/vmlinuz-2.4.20-8
> label=linux
> initrd=/boot/initrd-2.4.20-8.img
> read-only
> append="root=LABEL=/12"
The above 2 sections use the same kernel with same options, what's the
purpose?

>OUTPUT from lilo execution:
>[root@ip68-5-146-253 root]# lilo
>Warning: BIOS drive 0x82 may not be accessible

>NOTE: new hardisk only has 2 primary partitions

You didn't say:
- from where you are executing lilo (it's the lilo on a floppy?; is it
in hdc from where you booted?). What the exact command line?
- where is the lilo.conf you showed (you have restored it onto hda?)
- what's on hda now? You say 2 partitions, is it hda1 for swap and hda2
for root fs? Is it hda1 for /boot and hda2 for rootfs (no swap?)
- you booted from hdc and mounted hda under some dir?

1)
If you booted from hdc and want to make hda bootable by running lilo (so
that next boot the system will boot from hda), then you need to add to
lilo.conf (that I suppose is into hda)

disk = /dev/hda
bios = 0x80

this is because if you boot from hdc lilo is confused and does not now
that hda will be the 1st hd on next boot. This should eliminate the
message about 0x82 not accessible.

2)
then you need to comment out all the "other = " part (the dos label)
since you didn't restore a dos/win partition on hda.

3)
If you want to boot from hda a linux install that is into hda you ave
another problem; have you recreated the disk labels (/12) on hda? If not
you'd better modifying lilo.conf:
comment out:
append="root=LABEL=/12"
add:
root = /dev/hdaX where X is the right number for the root fs


So, it all depends on what's exactly your config now.

--
giulioo@pobox.com