From owner-freebsd-hackers  Wed Aug 30 01:07:47 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.FreeBSD.org (8.6.11/8.6.6) id BAA17713
          for hackers-outgoing; Wed, 30 Aug 1995 01:07:47 -0700
Received: from time.cdrom.com (time.cdrom.com [192.216.222.226])
          by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id BAA17702
          for <hackers@freefall.FreeBSD.org>; Wed, 30 Aug 1995 01:07:41 -0700
Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id BAA02326; Wed, 30 Aug 1995 01:06:53 -0700
To: "Kaleb S. KEITHLEY" <kaleb@x.org>
cc: hackers@freefall.FreeBSD.org
Subject: Re: pilot error on my part or feedback on the 2.1 snap 
In-reply-to: Your message of "Tue, 29 Aug 1995 21:38:40 EST."
             <199508300138.VAA04525@exalt.x.org> 
Date: Wed, 30 Aug 1995 01:06:53 -0700
Message-ID: <2324.809770013@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: hackers-owner@FreeBSD.org
Precedence: bulk

> I've tried quite a few different ways through the menus, but one thing
> that's confounded me more than once was, when trying to (W)rite the
> disklabel, to have it tell me that I have to label the disk in order
> to complete this operation. Now this seems confusing when I'm in
> disklabel, trying to disklabel the disk, to have it tell me I need to
> label the disk in order to label the disk. :-)

Hmmmmm.  I may have spazzed..  Let me take a look at this!

> But even more confounding is, when it finally seems willing to write 
> the label, to have the kernel panic with the message "biodone: buffer 
> not busy", sync the disk and reboot. So far this has happened several
> times and I have been otherwise unsuccessful in installing.

Woops!  That's no good!  I wonder what's going on HERE..

> Is this somehow a pilot error or should I fall back to 2.0.5?

Why not fall back for now?  I'll have another snapshot for you shortly
that goes FAR beyond the last 2.1 snap and I'd much rather be finding
the bugs in that one..  Not that I'm not interested in the other bugs,
but if we're going to try to work through what looks to be a fairly
evil set of problems, let's try to do it with more recent bits.

					Jordan