Heikki Pesonen schreef: >On 1/30/06, > > >>On 1/30/06, Heikki Pesonen <[EMAIL PROTECTED]> wrote: >> >> >>>Thank you for the clear and useful description of the process. A >>>newbie like me needed a bit more particular description how to do all >>>that. >>> >>> > >The answer LinuxManMikeC wrote is the second reasonable description >of the lilo/grub -mess I have seen. I have started my tour to >Linux-world about 2-3 moths ago and now I faced a problem having >installed Mandrake to my computer with WindowsXP and Suse 10.0. >Mandrake lost Suse but found Windows. Now I want Suse-installation >back. > >After some expedition tours I have Mandrakes lilo.conf and Suses >menu.list printed on two A4 papers on my hand. It seems, that what is >left is only "simple" edition using vi/vim. > >But should I use Suses grub or Mandrakes lilo as my Linux and Windows >loader. And this seems to be so difficult a question that I probably >take 1 € coin and cast it up - or what? > > Heikki,
About Grub or LILO: i would prefer to use the same system for simplicity. I chose for Grub because i also started out with SuSE, and because my first Mandrake install was hosed by a kernel update when i forgot to run this 'lilo' command grub doesn't need. Below i give you a simple solution, but it helps if you invest some time in reading - general: http://users.ameritech.net/gholmer/booting.html - to help you with your issue extensively: http://portal.suse.com/sdb/en/2002/09/fhassel_grub_overview.html - if you want to install other systems continuously 'without the hassle': http://www.whiteley.org/~bart/linux/multi-root-linux-install.html At least prepare a note where you have written down how your systems looks like. You need to know where your kernel and root-sector are situated (hda*, and for Grub (hdx,x). Watch out Grub starts counting from ) onwards, so (hd0,0) = hda1). Your printouts will show this, but if Mandriva created new partitions the SuSE can be changed. To redirect Mandriva to Grub you can reinstall the mandriva botloader via the mandriva Configuration Center (mcc) -> boot -> configure how the system boots - Select Grub - Next - Here you can add a new selection, where you type over what you need to install suse (from your printout). This wil change the menu.lst in the Mandriva's /boot - Save this to Mandriva's rootsector first (so you can use he chainloader as explained in the 'without the hassle' hyperlink. - Then do this again and save it to the MBR. => the system should work again. Now if you are like me and you like SuSE's bootsplash better you can also do the same thing from suse onwards. This works very well if yoou are hosed completely (next time?): The easiest solution to get suse (and other stuff) back in a graphical way is to use SuSE's nice rescue system. - Put the suse install disk in your system. - Choose install (not that we want to do this). - Select language - Accept licence - Choose for Button: Other (NOT New instal or Update!) Now either if you want to fire up SuSE: - Select: Boot installed system -> select SuSE and off you go..... If you cannot get things to work at all: - Select: Repair installed system -> Expert tools (the automatic one can help you further than you want to!) - Save system settings to floppy can be usefull - Install new bootloader (and pick the correct root sector for SuSE) If SuSE starts you can reinstall and remake the bootloader fron YaST onwards (not to explain here on a Mandriva site). The nicest difference is the osibility to read existing menu.lsts and to create a complete listing automatically (very often gives you more than is available though) HTH, Peter Vollebregt ____________________________________________________ Want to buy your Pack or Services from Mandriva? Go to http://store.mandriva.com Join the Club : http://www.mandrivaclub.com ____________________________________________________
