Trying to config lilo....

[Nu-Bee]

I just placed Mandrake 9.1b3 on another partition and am loading it...now how do I get lilo set up to let me choose between 9.0 and 9.1b3 ?

...that is hda11 for 9.1b3, and hda6 for 9.0...

It is hda6 that I am trying to get into lilo. I have 2 kernels there so don't be confused by this.

Here is my lilo:


boot=/dev/hda
map=/boot/map
vga=791
default="Linux"
keytable=/boot/us.klt
prompt
nowarn
timeout=100
message=/boot/message
menu-scheme=wb:bw:wb:bw
ignore-table

image=/boot/vmlinuz
label="Linux"
root=/dev/hda11
initrd=/boot/initrd.img
append="quiet devfs=mount hdd=ide-scsi"
vga=788
read-only

image=/boot/vmlinuz-2.4.19-24mdkcustom
label=2419-24custom
root=/dev/hda6
initrd=/boot/initrd-2.4.19-24mdkcustom.img
append="quiet devfs=mount hdd=ide-scsi"
vga=788
read-only

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

image=/boot/vmlinuz
label=linux
root=/dev/hda6
initrd=/boot/initrd.img
append="quiet devfs=mount hdd=ide-scsi"
vga=788
read-only

image=/boot/vmlinuz
label="old-linux"
root=/dev/hda6
initrd=/boot/initrd.img
append="quiet devfs=mount hdd=ide-scsi"
vga=788
read-only

image=/boot/vmlinuz
label="linux-nonfb"
root=/dev/hda11
initrd=/boot/initrd.img
append="devfs=mount hdd=ide-scsi"
read-only

image=/boot/vmlinuz
label="failsafe"
root=/dev/hda11
initrd=/boot/initrd.img
append="failsafe devfs=nomount hdd=ide-scsi"
read-only

other=/dev/fd0
label="floppy"
unsafe


But, when I try to run lilo, this is what I get:

[root@localhost joseph]# lilo
Added Linux * Fatal: open /boot/vmlinuz-2.4.19-24mdkcustom: No such file or directory

Here is df:

[root@localhost joseph]# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/hda11 7060276 1517064 5184564 23% /
/dev/hda1 6132832 4028548 2104284 66% /mnt/win_c
/dev/hda5 15358104 5506156 9851948 36% /mnt/win_d
/dev/hda10 3062380 42072 3020308 2% /mnt/win_e

Here is my current fstab, and I am not exactly sure how to mount the other / and /home partitions.

I mean...what titles to give them.

I can mount them...but with odd titles.

I am afraid to try to mount 2x "/", and 2x "/home".


/dev/hda11 / ext3 defaults 1 1 none /dev/pts devpts mode=0620 0 0
/dev/hdc /mnt/cdrom auto user,iocharset=iso8859-1,codepage=850,noauto,ro,umask=0,exec 0 0
/dev/scd0 /mnt/cdrom2 auto user,iocharset=iso8859-1,codepage=850,noauto,ro,umask=0,exec 0 0
/dev/fd0 /mnt/floppy auto user,iocharset=iso8859-1,sync,codepage=850,noauto,umask=0,exec 0 0 /dev/hda1 /mnt/win_c vfat iocharset=iso8859-1,codepage=850,umask=0 0 0
/dev/hda5 /mnt/win_d ntfs iocharset=iso8859-1,ro,umask=0 0 0
/dev/hda10 /mnt/win_e vfat iocharset=iso8859-1,codepage=850,umask=0 0 0 none /proc proc defaults 0 0
/dev/hda7 swap swap defaults 0 0

I have a /usr also but I can figger that out later.

Right now I am most concerned with getting lilo set up...and being able to edit files on the original /etc...

BTW, the old / is hda6

The old /home is hda9

My old /usr is had8


TIA,

UPDATE:


I have been able to return the system to the 9.0 lilo, and boot the 9.1b3 off a floppy. I would however still like to have them both on the lilo menu.

[VSELP_EFRC]

I have a similar problem, but I'll get to that in a minute.

Isinitrd-2.4.19-24mdkcustom.img
in hda6 /boot ?

Have you tried removing this entry and booting the old linux on hda6 ?
Aren't these two entries refering to the same image:
image=/boot/vmlinuz
label=linux
root=/dev/hda6
initrd=/boot/initrd.img
append="quiet devfs=mount hdd=ide-scsi"
vga=788
read-only

image=/boot/vmlinuz
label="old-linux"
root=/dev/hda6
initrd=/boot/initrd.img
append="quiet devfs=mount hdd=ide-scsi"
vga=788
read-only



I know this sounds simple, but I sometimes overlook the easy fixes. Just a suggestion. Let me know if this helps.

I am trying to use LILO to manage booting Mandrake 9.0, WinXP, Win2K on hda and Slackware 8.0 on hdb. So far, I can only boot Slack with a floppy boot disk. Not even as close as you are with 2 Mandrakes. I welcome any suggestions.

[Nu-Bee]

Originally posted by VSELP_EFRC
I have a similar problem, but I'll get to that in a minute.

Is initrd-2.4.19-24mdkcustom.img
in hda6 /boot ?

Yes


Originally posted by VSELP_EFRC

Have you tried removing this entry and booting the old linux on hda6 ?

They both worked in my old lilo. They are two diff. kernels.

2.4.19-16 (old)
and
2.4.19-24 (new)


Originally posted by VSELP_EFRC

Aren't these two entries refering to the same image:
image=/boot/vmlinuz
label=linux
root=/dev/hda6
initrd=/boot/initrd.img
append="quiet devfs=mount hdd=ide-scsi"
vga=788
read-only

image=/boot/vmlinuz
label="old-linux"
root=/dev/hda6
initrd=/boot/initrd.img
append="quiet devfs=mount hdd=ide-scsi"
vga=788
read-only

As I said...


Originally posted by VSELP_EFRC

I know this sounds simple, but I sometimes overlook the easy fixes. Just a suggestion. Let me know if this helps.

I am trying to use LILO to manage booting Mandrake 9.0, WinXP, Win2K on hda and Slackware 8.0 on hdb. So far, I can only boot Slack with a floppy boot disk. Not even as close as you are with 2 Mandrakes. I welcome any suggestions.

I am sure that in time I'll find the answer. If I clould just run lilo I'm sure that would do it.

I agree, it's probably something real simple...

[mdwatts]

If you installed the 9.1b3 bootloader into it's own root (hda11) partition (as you should if you are already using a bootloader from another installation), then you only need to add

other=/dev/hda11
label=Mandrake 9.1b3
table=/dev/hda

to /etc/lilo.conf.

[Modorf]

Originally posted by mdwatts
If you installed the 9.1b3 bootloader into it's own root (hda11) partition (as you should if you are already using a bootloader from another installation), then you only need to add

other=/dev/hda11
label=Mandrake 9.1b3
table=/dev/hda

to /etc/lilo.conf.

That is for the lilo.conf on the hda6 installation.

Then for the lilo.conf on the hda11 install
change the line :: boot=/dev/hda11
and remove all the options for the hda6 install

This will create two levels of menus, but I'm sure will work.
If you want your default distro on the first level of menus (switched) a) swap the info b) make sure you have a boot floppy to start the installations. There is always a chance the mbr will get screwed up and nothing will boot.

Nathan.