Subject: Re: overlap, was Re: Work-in-progress "wedges" implementation
To: Jason Thorpe <thorpej@shagadelic.org>
From: Jonathan Stone <jonathan@dsg.stanford.edu>
List: tech-kern
Date: 09/24/2004 18:16:16
In message <1BB7FFB8-0E8A-11D9-8D83-000A957650EC@shagadelic.org>,
Jason Thorpe writes:

[...]
>The problem I am getting at is... take a look at a BSD disklabel on a 
>PC, where that disk also has an MBR, possibly shared with another OS 
>(e.g. Windows):
>
>#        size    offset     fstype [fsize bsize cpg/sgs]
>  a: 294250496  16386300     4.2BSD   4096 32768    64  # (Cyl.   1020 - 
>  19336*)
>  b:   2098948 310636796       swap                     # (Cyl.  19336*- 
>  19466*)
>  c: 296349444  16386300     unused      0     0        # (Cyl.   1020 - 
>  19466*)
>  d: 312735744         0     unused      0     0        # (Cyl.      0 - 
>  19466*)
>  e:  16386237        63       NTFS                     # (Cyl.      0*- 
>   1019)

Which reminds me: In this example, the BSD-disklabel partition with
type 'NTFS' is an ugly, error-prone kludge.  I hope wedges will let us
do away with such kludges altogether.  We should, instead, create a
separate wedge covering the distinct MBR-partition describing that
NTFS filesystem...