[[ please put your remarks *below* the quoted text, preserves context and makes replying soo much more fun ]]
On Wed, May 09, 2001 at 03:34:48AM +0800, [EMAIL PROTECTED] wrote: > Device Boot Start End Blocks Id System ..snipped normal looking output of fdisk > I mean debian *installing* program mistake my partiotion table. Yep, and what part of the install program suite? The part were you get to partition your hard disk? If so that would be "cfdisk". So it would be interesting to compare the output of *both* fdisk and cfdisk: # cfdisk -Pt /dev/hda # fdisk -l /dev/hda > freebsd has it's partition,/dev/hda3=wd0s2,it's a primary partiotion > absolutly. Yep your definitely right here, checked in on the web in FreeBSD excelent online docs. > I suspect debian's installing program mistake wd0s2a,wd0s2b...as > extended partion. I find this a bit worrying, if fdisk and cfdisk treat BSD partitions differently, who knows how the kernel will treat them! So, let's have a look:) Ah, I see a CONFIG_BSD_DISKLABEL flag in the config help, and setting this would indeed bring life into that special bsd-primary-partition. [[ had your running kernel that flag on when compiled? the default debian kernels seem to have it on. ]] Looking further into the source I think this bsd-primary-partition is delt with *after* all normal (linux/dos/windows) extended partitions are traversed, so bsd partitions will be numbered last. At least in the kernel. > CF> For better help, post your partition table, i.e. the output of: > > CF> # fdisk -l /dev/hda > CF> # cfdisk -Pt /dev/hda -- groetjes, carel
