The original message was received at Mon, 14 Mar 1994 12:45:32 -0800
from baloo.UCSC.EDU [128.114.16.4]

   ----- The following addresses had delivery problems -----
<netbsd-current@sun-lamp.cs.berkeley.edu>  (unrecoverable error)

   ----- Transcript of session follows -----
... while talking to sun-lamp.cs.berkeley.edu.:
>>> RCPT To:<netbsd-current@sun-lamp.cs.berkeley.edu>
<<< 550 <netbsd-current@sun-lamp.cs.berkeley.edu>... User unknown
550 <netbsd-current@sun-lamp.cs.berkeley.edu>... User unknown

   ----- Original message follows -----
	id MAA18415; Mon, 14 Mar 1994 12:45:32 -0800
Message-Id: <199403142045.MAA00275@baloo.ucsc.edu>
From: buhrow@cats.ucsc.edu (Brian Buhrow)
Date: Mon, 14 Mar 1994 12:45:28 -0800
To: netbsd-current@sun-lamp.cs.berkeley.edu
Subject: DISKTAB

	I have come to love the disktab mechanism for labeling and partitioning
disks.  In an environment where we want to manage a large number of similar
disks, it is extremely nice to be able to write one label for all the disks
you want and then just put that label on the floppy you use for disk
labeling.  As more and more types of drives get into your library, you
compile an extremely valuable resource with your disktab file.  As long as
you have it, you can re-label any of your disks in an identical fashion to
the way it was labeled before and not worry about whether or not your
zorched your partitions.  In addition, you can see the geometry of any
drive in your library without having to scramble to the machine and do a
disklabel command.
	I don't know if anyone has plans on dropping the current labeling scheme, but 
I would encourage you to stick with the current labeling scheme.
-Brian


------------------------------------------------------------------------------