Re: multi-booting without screwing up my current grub settings == A bit more ==
- From: AnnonymousFC4 <afc4@xxxxxxxxxxx>
- Date: Thu, 30 Mar 2006 12:03:54 -0800
Hi:
1) it is a good idea to save the MBR (master boot record), in a safe place,
and use dd for this (as root)
example:
dd if=/dev/hda of=/mbr.linux bs=512 count=1
2) Here (at the end of this msg)
is my /boot/grub/menu.lst file, for a multi boot system, with SUSE 10.0,
Windows XP, and FC5, you may want to read the *info grub* which is quite
good.
3) Whenever you install a new software (Linux) just do not install the boot
loader, (or install it a the beginning of the install partition).
If you have to reinstall windows, then reinstall windows... which will
rewrite the MBR (its own!), and after that use a CD bootable Linux (KNOPPIX
is great), to restaire the MBR you have previously saved.
4) Note that SUSE, Fedora, and Mandriva, will detect Windows, if installed,
and cretae the proper GRUB entry.
5) Use GRUB, LILO works in multi boot... but is harder to configure, and in
no way better!
NOW:
====== my /boot/grub/menu.lst file ====
# Modified by YaST2. Last modification on Wed Feb 15 22:56:02 PST 2006
color white/blue black/light-gray
default 0
timeout 8
gfxmenu (hd0,1)/message
###Don't change this comment - YaST2 identifier: Original name: linux###
title SUSE LINUX 10.0
root (hd0,1)
kernel /vmlinuz root=/dev/hda3 vga=0x317 selinux=0 resume=/dev/hda6
splash=silent showopts
initrd /initrd
###Don't change this comment - YaST2 identifier: Original name: windows###
title Windows
root (hd0,0)
chainloader +1
# 14 Nov, 2005
title Fedora Core 5 (2.6.15-1.1955)
root (hd0,1)
kernel /vmlinuz-2.6.15-1.1955_FC5 root=/dev/hda5 ro
initrd /initrd-2.6.15-1.1955_FC5.img
# 25 Oct, 2005
title Fedora Core 4 (2.6.13-1.1532_FC4.)
root (hd0,1)
kernel /vmlinuz-2.6.13-1.1532_FC4 root=/dev/hda5 ro
initrd /initrd-2.6.13-1.1532_FC4.img
title Fedora Core 4 (vmlinuz-2.6.12-1.1447_FC4)
root (hd0,1)
kernel /vmlinuz-2.6.12-1.1447_FC4 root=/dev/hda5 ro
initrd /initrd-2.6.12-1.1447_FC4.img
###Don't change this comment - YaST2 identifier: Original name: floppy###
title Floppy
root (fd0)
chainloader +1
###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- SUSE LINUX 10.0
root (hd0,1)
kernel /vmlinuz root=/dev/hda3 vga=normal showopts ide=nodma apm=off
acpi=off noresume selinux=0 nosmp noapic maxcpus=0 edd=off 3
initrd /initrd
Al wrote:
houghi wrote:
Jeff Harris wrote:Thx for the help
On Wed, 29 Mar 2006 23:10:51 +0000, Al wrote:
I'd like to add suse 10 on an empty partition. I run pro 9.3
currently.
How do i install 10 without it rewriting my current grub settings??
I don't think rewriting grub is a problem, but I hear you. Been there,
done that. To answer your question, tell the installation NOT to write
to the MBR.
Indeed that simple.
Reboot into 9.3 and edit /boot/grub/menu.lst to add 10.0 on the
partition you installed to. You better study up on grub so you know the
syntax before you do this however. Man grub.
To study is a bit of an overstatement. What I do is just look in
$SUSE10.0_DIR/boot/grub/menu.lst how it should look and add that to
/boot/grub/menu.lst.
If you have a floppy drive, use one floppy for 9.3 (For backup) and one
for 10.0 during installation. You most likely will have some floppies
laying around that you do not use.
Test the 9.3 one BEFORE you edit grub. It is always possible to use the
CD, but a floppy is much easier.
.
- References:
- Prev by Date: Re: Problems with files greater than 2 GB on Suse 10 Retail
- Next by Date: Re: KDE 3.5.2 == Which repository ??? ==
- Previous by thread: Re: multi-booting without screwing up my current grub settings
- Next by thread: Re: multi-booting without screwing up my current grub settings
- Index(es):
Relevant Pages
|
