From owner-freebsd-current Tue Mar 28 23:53:03 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA11382 for current-outgoing; Tue, 28 Mar 1995 23:53:03 -0800 Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id XAA11376 for ; Tue, 28 Mar 1995 23:53:02 -0800 Received: from localhost (localhost [127.0.0.1]) by precipice.shockwave.com (8.6.11/8.6.9) with SMTP id XAA00497; Tue, 28 Mar 1995 23:51:42 -0800 Message-Id: <199503290751.XAA00497@precipice.shockwave.com> To: Bruce Evans cc: current@FreeBSD.org Subject: Re: kern/280: new slice manager totally confused about old slice disks In-reply-to: Your message of "Wed, 29 Mar 1995 17:33:20 +1000." <199503290733.RAA21500@godzilla.zeta.org.au> Date: Tue, 28 Mar 1995 23:51:41 -0800 From: Paul Traina Sender: current-owner@FreeBSD.org Precedence: bulk No, what you have done is absolutely right. Disklabel should not be able to read a bsd pseudolabel if there is no BSD label there. All concerns I have are gone. From: Bruce Evans Subject: Re: kern/280: new slice manager totally confused about old slice dis >>ks >>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