I'm thinking about dual booting the same OS but updating the second to test.

I'm not sure of all the implications.

I have a /boot partition. That means I will be overwriting the first kernel init etc, with the same, cannot think that is likely to be any problem.

Lilo will still be in the MBR, but it will have the script from second install,
because there is no option available these days to skip lilo install.Developers please note.


Second install will use it's own /etc/lilo.conf file.
but this is likely to be the naff OS , especially if it goes wrong with the updates.


Not, to my mind, a satisfactory state of affairs.
I want to be booting everything from the first OS /etc/lilo.conf.
Question is how to do that.

F1-rescue - install new bootloader ,
but it's going to have two identicle OS's each with it's own /etc/lilo.conf
how will it know which to choose ?
In otherwords how do I tell it which OS /etc/lilo.conf script it's to use ?

each OS will have it's seperate partition, lets say for arguements sake,
M9.1 OS1 on /hda7
M9.1 OS2 on /hda6

can I pass some arguement in the F1 -rescue - install new boot loader , to tell it which partition to look for an /etc/lilo.conf ?

Does say, F1 - rescue /dev/hda7 make anything useful happen to where it reads /etc/lilo.conf ?

I bet there is a way round this

anyone ?

John


--
John Richard Smith
[EMAIL PROTECTED]




Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com

Reply via email to