mike wrote:
Mikkel L. Ellertson wrote:
mike wrote:
I have 1 harddrive and 10.0mdk and 10.1mdk installed on it.
I use lilo as my boot manager and installed in mbr.
The lilo.conf on my 10.0 side is the one I use and have a entry like
so in my lilo.conf for 10.1 side...
image=/mnt/mdk101/boot/vmlinuz
label="mdk10.1"
root=/dev/hda1
initrd=/mnt/mdk101/boot/initrd.img
append="acpi=ht resume=/dev/hda5 splash=no"
vga=788
read-only
I have renamed my lilo.conf in the 10.1 side to something else, so
when I update the kernel on the 10.1 side it could not run lilo (and
write over the conf I have on the 10.0 side).
Which has worked on previous version's of mdk for me. But, not this
time. Now when I updated the kernel on the 10.1 side it would not do
it because (error 16 could not find boot loader), which is correct
because I renamed the conf file.
This way of doing has worked up to now for me but perhaps no longer.
Any suggestions or advise would be appreciated.
Thanks,
Mike
Why not, in the 10.1 lilo.conf, change "boot=/dev/hda" to
"boot=/dev/hda1". This way, lilo in 10.1 will write its boot loader, and
information to the boot record of the root partition, instead of the
MBR.
Mikkel, this sounds like what I'm looking for. But I am struggling
with it so far. I changed "boot=/dev/hda" to "boot=/dev/hda1" on my
10.1 lilo.conf and ran "lilo" but I recieve and error at the end
something like "Fatal, unable to find default image".
Do I need to install lilo into /dev/hda1 ?
For the 10.1 side that is.
If you want to keep your current setup, you can then copy the
changes from 10.1's lilo.conf to your mail lilo.conf. Or, if you don't
mind seeing 2 boot loaders when running 10.1, you could change the 10.1
entry to something like:
other=/dev/hda1
label=Mandrake-10.1
When you pick that entry, it will transfer control to the 10.1 boot
loader. If you wanted to, you could turn off the splash screen, and the
prompt, and give it a timeout of 10 seconds, before it boots. This is
enough time to hit a key, and interrupt the boot sequence if you need
to. Otherwise, a 10 second delay when booting 10.1 would not be too
noticeable.
Mikkel
Your first option sounds like the one I want go with. If possible.
Thanks,
Mike
If you post your lilo.conf for 10.1, I can tell you what is wrong. From
the error message, I suspect that the <lable> from your
"default=<lable>" statment does not match any "lable=<label>" statment.
So lilo dosent know what to do if it times out, or if you just hit
"Enter". If you run "lilo -v", it will give you more information about
what it is doing.
Mikkel
____________________________________________________
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
Join the Club : http://www.mandrakeclub.com
____________________________________________________
