Lilo edit
Forum: HD Install
Topic: Lilo edit
started by: lostcity
Posted by lostcity on Oct. 13 2004,00:42
Installed DSL 0.7.3 to hda2 with RH8 on hda1. I have set RH to boot with lilo. When I edit /ect/lilo.conf and run /sbin/lilo I get an error message which says it cannot recognize the boot signature for hda2 (dsl). Any ideas how I can modify /etc/lilo.conf to indentify the boot signature.Thanks
Posted by ssgt2002 on Oct. 15 2004,07:57
I don't a whole lot about linux yet but i think one of the easiest ways might be how I did it. Every time I loaded a new distro on my PC (six at once as it were) I used the new distro boot loader and just modified it with the other distros stuff.
Posted by tjm4fun on Oct. 17 2004,23:01
Create a mount point for dsl on redhat. ex /mnt/dslthen for lilo use something like:
boot = mnt/ds/boot
in the stanzas, any ref to dsl in the boot stanzas must be prefixed with the mount point. then run lilo, it will now be able to find the correct blocks to build the loader for that distro.
you can make it a temp mount point til you run lilo and it builds itself, after that it's not needed til the next lilo build. I put fstab entries in my other distros, so I can read the others, and if I make any changes, don;t have to remember to remount 2or 3 other distro's temporarily to run lilo.
Posted by lostcity on Oct. 18 2004,00:32
Thanks. Let see if I can get this to work.
Posted by somerville32@hotmail.com on Oct. 18 2004,01:06
Remind me to add a FAQ about this tomorrow. I am going to bed now 
Posted by Ian on Oct. 29 2004,03:17
| Quote (somerville32@hotmail.com @ Oct. 17 2004,21:06) |
| Remind me to add a FAQ about this tomorrow. I am going to bed now |
Reminder: Generate a FAQ that explains how to multiboot with DSL. (My DSL HD install trashed my Fedora GRUB boot loader. I would like to be able to boot both OS's. Since LILO is the current boot loader, what is the syntax to add the Fedora (hda1=/boot, hda2=/, hda3=swap) OS to lilo.conf ? )
Posted by AwPhuch on Oct. 29 2004,04:39
< http://www.rt.com/man/lilo.5.html >| Quote |
| It might look as follows: boot = /dev/hda delay = 40 compact vga = normal root = /dev/hda1 read-only image = /zImage-2.5.99 label = try image = /zImage-1.0.9 label = 1.0.9 image = /tamu/vmlinuz label = tamu root = /dev/hdb2 vga = ask other = /dev/hda3 label = dos table = /dev/hda |
My Fedora Core 1 looks like this
| Quote |
| [root@localhost etc]# cat lilo.conf.anaconda prompt timeout=50 default=linux boot=/dev/hda map=/boot/map install=/boot/boot.b linear image=/boot/vmlinuz-2.4.22-1.2115.nptl label=linux initrd=/boot/initrd-2.4.22-1.2115.nptl.img read-only append="rhgb root=LABEL=/" |
remember to type "lilo" after making any changes to make them permanent
Brian
AwPhuch
Posted by reid_geo on Oct. 31 2004,01:11
| Quote (AwPhuch @ Oct. 29 2004,00:39) | ||||
< http://www.rt.com/man/lilo.5.html >
My Fedora Core 1 looks like this
remember to type "lilo" after making any changes to make them permanent Brian AwPhuch |
So what finally worked was to use some of the lilo.conf.anaconda entries from the Fedora2 installation, AND add a line to fstab that mounts the Fedora boot partition. Lilo.conf entries needed to be modified to account for the location of the Fedora boot images (/mnt/fedora/vmlinuz-2.6.8....)
Thanks to all for the suggestions. I would still would rather use GRUB...
Posted by AwPhuch on Oct. 31 2004,04:16
| Quote (reid_geo @ Oct. 30 2004,21:11) |
| So what finally worked was to use some of the lilo.conf.anaconda entries from the Fedora2 installation, AND add a line to fstab that mounts the Fedora boot partition. Lilo.conf entries needed to be modified to account for the location of the Fedora boot images (/mnt/fedora/vmlinuz-2.6.8....) Thanks to all for the suggestions. I would still would rather use GRUB... |
I agree...I wonder if you could install grub and get it to work?
So what did your lilo.conf finally look like?
Brian
AwPhuch
Posted by reid_geo on Oct. 31 2004,06:25
| Quote (AwPhuch @ Oct. 31 2004,00:16) | ||
I agree...I wonder if you could install grub and get it to work? So what did your lilo.conf finally look like? Brian AwPhuch |
Here is the whole mess - first /etc/fstab, then the relevant parts of lilo.conf.
My method was to mount the Fedora2 Core partition via the command line as well as /etc/fstab, and then use those partitions in lilo.conf to define a new OS/kernel section.
I was then able to successfully run lilo to update the boot loader conffiguration.
/dev/hda
/dev/hda1 Fedora /boot
/dev/hda2 Fedora /
/dev/hda3 swap
/dev/hda4 DSL 0.83
# /etc/fstab: filesystem table.
#
# filesystem mountpoint type options dump pass
/dev/hda4 / ext2 defaults,errors=remount-ro 0 1
proc /proc proc defaults 0 0
/dev/fd0 /floppy vfat defaults,user,noauto,showexec,umask=022 0 0
/dev/cdrom /cdrom iso9660 defaults,ro,user,noexec,noauto 0 0
# partitions found by dsl
#/dev/hda1 /mnt/hda1 ext3 noauto,users,exec 0 0
#/dev/hda2 /mnt/hda2 ext3 noauto,users,exec 0 0
#/dev/hda4 /mnt/hda4 ext2 noauto,users,exec 0 0
/dev/hda1 /mnt/fedora ext2 defaults,errors=remount-ro 0 1
# Added by KNOPPIX
/dev/hda2 /mnt/hda2 ext3 noauto,users,exec 0 0
# Added by KNOPPIX
/dev/hda3 none swap defaults 0 0
**********************************************************
#lilo.conf
default=Linux
image=/boot/linux24
label=Linux
read-only
# restricted
# alias=1
image=/vmlinuz.old
label=LinuxOLD
read-only
optional
# restricted
# alias=2
image=/mnt/fedora/vmlinuz-2.6.8-1.521
root=/dev/hda1
label=Fedora2
initrd=/mnt/fedora/initrd-2.6.8-1.521.img
read-only
append="rhgb root=LABEL=/"