Insert CD1 , run to splash screen, choose F1, run to prompt, type expert, then enter, gives you expert install in graphical mode(or whaterver)Hi John, I installed mdk9.1 three times. Option auto / expert never came up.
Option to config or skip bootloader will came up after 3rd disk.How ?
ONLY on 2nd and 3rd install.How ?
As one would expect !It seems that on first time around you have no choice?
The next config option for bootloader will come up on the bottom of theWhich window ?
screen
where you can config a lot of stuff.I know it,
Select this option and on the screen that appear select ADVANCE
to be ableChoices ?
to select option for bootdisk.
After bootdisk is made you have option to config lilo -
here you have to make some choices.
Well yes, but it would be better not to install lilo at all on second attempt.If you are not succesful here and you have a bootdisk you can modify the lilo.conf after reboot.
sure,Here you have to look closely to configuration manner see below for this installation.. Refer to my previous postings
I always do.Please after first install and reboot mark this install somewhere so that you will know which is which. They look the same and is very confusing.
Well all this goes in your final active /etc/lilo.conf to either boot one, and mount the other as the case may be. I just want the active /etc/lilo.conf to be the first M9.1 install and remain so.Also mark the second install. Should you mount the non-live OS you must use full path to move around in it.
Youcann ot stop this then ?It is not really importend which partition is installed first and that the lilo is written to MBR the next will overwrite it.
yes and no, depends if your happy with booting off the lilo.conf of the second M9.1 install.What is importent is the way your lilo.conf will be written in the end - by mdk or yourself.
Suggest - cd /etc su.
Now there is some ways to use lilo.
Like - to see how now -- lilo -q
To see if your changes is legal without changing -- lilo -t
If you need more info lilo -t -v.
Be sure to backup your file before changes.
I enjoyed this testing - this is how I found out when to make bootdisk
before rebooting install and it also made me more confident.
Enjoy
Johan
OK, now this,
This looks really wierd to me, I'm not sure if I understand it.####Look closely to this image and initrd***** image=/mnt/linuxhde-7/boot/vmlinuz label="linuxhde7" root=/dev/hde7 initrd=/mnt/linuxhde-7/boot/initrd-2.4.21-0.13mdk.img read-only
image=/mnt/linuxhde-7/boot/vmlinuz
says, go look for the kernel to boot in /mnt/linuxhde-7 which must be some strange way of saying hde7 , boot directory, select kernel vmlinuz.
and again,
initrd=/mnt/linuxhde-7/boot/initrd-2.4.21-0.13mdk.img
use initrd in hde7 's /boot directory.
Now would this also work for me when I have a /boot partition.(hda5 if my memory serves me correctly)?
Which means all kernel and initrd files are in /dev/hda5 (or whaterver) So I have the simpler task of writing all /etc/lilo.conf entries to use kernel and init.rd files in the same /dev/hda5(or whatever). I still think my way is easier, keep to the one /boot partition, where all these files go for all the linux OS's, and what is more the installer puts them there automatically.
John
--
John Richard Smith
[EMAIL PROTECTED]
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
