Bruce Evans wrote:
> On Thu, 20 Jul 2000, John Baldwin wrote:
> > No, that's wrong, too.  A normal disk has a proper slice table (slices start
> > on cylinder boundaries and do not contain the MBR, thus leaving the first
>      track
> > cylinder unused).  A truly dedicated disk (disklabel auto <foo>) uses a
>   track
> > ...
> > at all to the drive's geometry.  As with truly dedicated mode, the MBR is
> > actually contained in boot1, but in dangerously dedicated mode we use the
> > slice table hard-coded into the boot code.  This slice table has 1 slice
> > which is 50000 blocks long, or 25000k.  The rest of the disk is marked as
> > unused even though it is, in fact, used.  The fact that it works at all is
> > due to brokenness on our part (we don't check that partitions in a disklabel
> > fit in the parent slice) and also results in several hacks in various portions
> > of the code where we have to check for such bogusness and work around it.
> No, that's wrong too :-) .  We a lot of checking that partitions in a
> disklabel fit in the parent slice.  We clip partitions that don't fit in
> various ways for backwards compatibility.
> Bruce

Erm, maybe we clip partitions which aren't dangerously dedicated, but
I've created test dangerously dedicated disks, and we certainly do not
bother to actually change any of the slice information when we do so.
disklabel(8) does for truly dedicated, but libdisk doesn't for dangerously


John Baldwin <[EMAIL PROTECTED]> --
PGP Key:
"Power Users Use the Power to Serve!"  -

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to