From owner-freebsd-current  Tue Mar 28 23:40:28 1995
Return-Path: current-owner
Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA11175 for current-outgoing; Tue, 28 Mar 1995 23:40:28 -0800
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id XAA11158 for <current@freebsd.org>; Tue, 28 Mar 1995 23:39:46 -0800
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id RAA21500; Wed, 29 Mar 1995 17:33:20 +1000
Date: Wed, 29 Mar 1995 17:33:20 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199503290733.RAA21500@godzilla.zeta.org.au>
To: pst@shockwave.com
Subject: Re: kern/280: new slice manager totally confused about old slice disks
Cc: current@FreeBSD.org
Sender: current-owner@FreeBSD.org
Precedence: bulk

>>Synopsis:       the new slice code is bitching about my old slices

>1) It looks like the implicit label stuff for unlabeled disks is
>   non-functional?  I cannot ask disklable to read the pseudo-label off
>   of sd1

So we need the pseudo-label on all BSD slices?  Perhaps a read-only one
on non-BSD slices?  This would make it possible to determine the type
and size of all slices using standard ioctls and utilities (fdisk is
nonstandard and doesn't support extended partitions).

There are some semantic problems with modifiying pseudo-labels.  All
the slices and labels are currently reread on first-opens to pick up
any changes to the DOSpartition table (changes to labels are handled
better).  Modifications are thus going to be lost immediately (instead
of at the next boot) unless you keep another device on the drive open.

Bruce