partitioning bug during install: RH8/9 FC1
David Kewley
kewley at cns.caltech.edu
Mon Dec 22 07:12:42 UTC 2003
Trae McCombs wrote on Sunday 21 December 2003 20:51:
> On Sun, 2003-12-21 at 22:39, David Kewley wrote:
> > The Disk Druid partition ordering doesn't seem to be driven purely by
> > size on my home RHL9 box (keep in mind that I created the NTFS & FAT32
> > partitions before installing RHL9):
>
> Yeah, if there is something on the disk, or partitions already
> pre-existing, you are golden, as it won't touch data if there is
> something there. I'm talking about completely free space on an unused
> drive.
My point was actually aside from the three pre-existing Windows partitions.
Disk Druid put / in /dev/hda5, even though it's smaller than /local (hda6)
and /usr (hda7), but swap (which is smallest of all) got put in hda8. So
the ordering logic might have been "/boot-containing partition, then
largest to smallest" or something like that.
Device Boot Start End Blocks Id System
/dev/hda1 * 1 1275 10241406 7 HPFS/NTFS
/dev/hda2 1276 2295 8193150 7 HPFS/NTFS
/dev/hda3 2296 2550 2048287+ c Win95 FAT32 (LBA)
/dev/hda4 2551 9729 57665317+ f Win95 Ext'd (LBA)
/dev/hda5 2551 2677 1020096 83 Linux
/dev/hda6 2678 3952 10241406 83 Linux
/dev/hda7 3953 4717 6144831 83 Linux
/dev/hda8 4718 4782 522081 82 Linux swap
As for pre-allocating the Windows partition, without actually installing
Windows, there's no need to do something as involved as putting a minimal
RHL/FC installation on hda1. Just boot from the RHL/FC CD 1 as "linux
rescue", then use fdisk to create hda1 as partition type 7. :) Then reboot
with CD 1 as normal to install RHL/FC.
David
More information about the devel
mailing list