From owner-freebsd-hackers  Tue Oct 29 03:26:41 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id DAA18719
          for hackers-outgoing; Tue, 29 Oct 1996 03:26:41 -0800 (PST)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA18709
          for <hackers@freebsd.org>; Tue, 29 Oct 1996 03:26:37 -0800 (PST)
Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.6/8.6.9) with ESMTP id DAA05168; Tue, 29 Oct 1996 03:26:34 -0800 (PST)
To: Warner Losh <imp@village.org>
cc: hackers@freebsd.org
Subject: Re: Weird install problems. 
In-reply-to: Your message of "Mon, 28 Oct 1996 20:32:56 MST."
             <E0vI4vA-0003gH-00@rover.village.org> 
Date: Tue, 29 Oct 1996 03:26:34 -0800
Message-ID: <5166.846588394@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> I've seen cases where relabeling disks cause the slice information to
> go away.  In one case this was done via the install program
> completely, and in the other I think it was done with disklabel.

It is an unfortunate side-effect of MAKEDEV to wipe the slice entries
out when making the other disk entries, and sysinstall doesn't know to
remake the device-specific slice entries again in this case, I
suppose.  I can see how it might happen, just not immediately where.
I'll go poking around.

					Jordan