Re: Dual boot issues with bootpart
- From: Grant <bugsplatter@xxxxxxxxx>
- Date: Sat, 10 Jun 2006 02:27:08 +1000
On 9 Jun 2006 01:14:29 -0700, "R. P." <compnerd2032@xxxxxxxxxxxxxxx> wrote:
Then why does the Windows option with bootpart work but not the SuSE
Linux one?
I remember trying to use bootpart back when WinNT4sp6a was the go, it's
not the easiest way to manage dual-booting, and is very old. Lilo is
my preferred bootloader, as grub gets confused by some windows programs
on dual boot setups.
Bootpart is an out-dated tool that I've not used for many years, it has
no redeeming features when compared with lilo. The biggest problem is
that one must give bootpart a new bootsect file each time one updates
linux -- lilo is easier ;)
Lilo has no problems running a dual boot when you leave windoze owning
the MBR and change the active partition to another primary -> linux.
The linux bootloader then gives an option to boot windows. You setup
bootloader to default to whichever way you normally use the machine.
You give no technical information on your setup. Here's a multi-boot
Win98, FreeBSD, Slackware, Win2k laptop example:
root@tosh:~# fdisk -l
Disk /dev/hda: 40.0 GB, 40060403712 bytes
255 heads, 63 sectors/track, 4870 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hda1 1 128 1028128+ b W95 FAT32
/dev/hda2 129 640 4112640 a5 FreeBSD
/dev/hda3 * 641 1152 4112640 83 Linux
/dev/hda4 1153 4870 29864835 f W95 Ext'd (LBA)
/dev/hda5 1153 1184 257008+ 82 Linux swap
/dev/hda6 1185 1200 128488+ 83 Linux
/dev/hda7 1201 1712 4112608+ 7 HPFS/NTFS
/dev/hda8 1713 1968 2056288+ b W95 FAT32
/dev/hda9 1969 2608 5140768+ 83 Linux
/dev/hda10 2609 4870 18169483+ 83 Linux
root@tosh:~# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/hda3 4112508 2377920 1734588 58% /
deltree:/home/share 8224960 2311944 5913016 29% /home/share
root@tosh:~# cat /etc/lilo.conf
# /etc/lilo.conf for Slackware-10.2 on tosh - 2005-09-15 - Grant Coady
# MBR is owned by MSFT, we get control via active primary
boot = /dev/hda3
root = /dev/hda3
read-only
compact
prompt
timeout = 50
# vesa| 800x600 1024x768 1280x1024
# ---- -------- -------- ---------
# 256 | 0x303 0x305 0x307
# 32k | 0x313 0x316 0x319
# 64k | 0x314 0x317 0x31A
# 16M | 0x315 0x318 0x31B
vga = 0x313
append = "video=vesafb:mtrr,ywrap"
#default = 2.6.16.20a
#default = 2.4.33-pre3
#default = 2.4.32-hf32.6
#default = 2.4.31-hf32.6
image = /boot/bzImage-2.6.17-rc6-mm1a
optional
label = 17-rc6-mm1a
image = /boot/bzImage-2.6.17-rc6a
optional
label = 2.6.17-rc6a
image = /boot/bzImage-2.6.16.20a
optional
label = 2.6.16.20a
image = /boot/bzImage-2.4.33-pre3
optional
label = 2.4.33-pre3
image = /boot/bzImage-2.4.32-hf32.6
optional
label = 2.4.32-hf32.6
image = /boot/bzImage-2.4.31-hf32.6
optional
label = 2.4.31-hf32.6
image = /boot/bzImage-2.4.30-hf32.1
optional
label = 2.4.30-hf32.1
image = /boot/vmlinuz-ide-2.4.31
label = Slack-2.4.31
append = ""
other = /dev/hda2
label = FreeBSD
table = /dev/hda
other = /dev/hda1
label = Windows
table = /dev/hda
root@tosh:~#
Note that windows requires a primary for boot control, so if the above
didn't have win98, it would have WinNT in /dev/hda1 instead. The MBR
(windows owned) can only pass control to another primary, on older BIOS
boxen that would be a small /boot partition. These days you can put
larger primaries in, less partitions to worry about.
You can setup linux owning MBR, but that path seems to cause more grief
in the longer term, this method works for me for years, there are many
ways to run multi-boot, but the other available methods seem less
maintainable.
I suspect bootpart is useful only to those with a strong ms-dos
background, and it uses long outdated techniques when compared to
'modern' techniques in lilo. Grub seems fragile in multi-boot,
I've no idea if it's been fixed since I last used it.
Grant.
--
Memory fault -- brain fried
.
- References:
- Dual boot issues with bootpart
- From: R. P.
- Re: Dual boot issues with bootpart
- From: Robert Hull
- Re: Dual boot issues with bootpart
- From: R. P.
- Dual boot issues with bootpart
- Prev by Date: Re: sata_promise module
- Next by Date: Re: Kmail files
- Previous by thread: Re: Dual boot issues with bootpart
- Next by thread: Re: Dual boot issues with bootpart
- Index(es):
Relevant Pages
|
