From owner-freebsd-hackers  Sat Apr 19 22:42:02 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id WAA05949
          for hackers-outgoing; Sat, 19 Apr 1997 22:42:02 -0700 (PDT)
Received: from rover.village.org (rover.village.org [204.144.255.49])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id WAA05944
          for <hackers@freebsd.org>; Sat, 19 Apr 1997 22:41:58 -0700 (PDT)
Received: from rover.village.org [127.0.0.1] 
	by rover.village.org with esmtp (Exim 1.60 #1)
	id 0wIpNr-0007gZ-00; Sat, 19 Apr 1997 23:41:55 -0600
To: hackers@freebsd.org
Subject: disklabel -- owner?
Date: Sat, 19 Apr 1997 23:41:54 -0600
From: Warner Losh <imp@village.org>
Message-Id: <E0wIpNr-0007gZ-00@rover.village.org>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


Is there an owner for disklabel?

I ask this because I have, over the years, grown to really really
really loath having to deal with this program.  With all of its
oddities, and you gotta set this right or that right, or or or or or.

So, I'd like to fix at least some of them.  Is there someone that I
should coordinate with?

Heck, I'd be happy to try to rewrite the whole fdisk/disklabel junk
into a nice, easy to use script.  sysinstall is OK, but it isn't as
nice as I'd like.  Is there a need for this, or are people generally
happy with the tools we have?

Yours in frustration,

Warner

P.S. I wasted several hours wondering why my new machine wouldn't boot
off of its new disk.  Turns out thats because the "TYPE" field in the
label wasn't SCSI, so it installed IDE boot blocks and paniced when it
tried to mount root.  disklabel should know better.  And don't even
get me started on fdisk...