From owner-freebsd-qa Wed Mar 21 21:42:34 2001 Delivered-To: freebsd-qa@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id CF84B37B71B; Wed, 21 Mar 2001 21:42:32 -0800 (PST) (envelope-from jkh@osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.3/8.11.2) with ESMTP id f2M5gP013336; Wed, 21 Mar 2001 21:42:25 -0800 (PST) (envelope-from jkh@osd.bsdi.com) To: rwatson@FreeBSD.org Cc: jkh@FreeBSD.org, qa@FreeBSD.org Subject: Re: If sysinstall is used after boot to partition, ad0 and wd0 appear In-Reply-To: References: X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010321214225T.jkh@osd.bsdi.com> Date: Wed, 21 Mar 2001 21:42:25 -0800 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 21 Sender: owner-freebsd-qa@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I believe this is a function of libdisk(3), which cheerfully returns to sysinstall an array of disk devices which includes both wd0 and ad0. Perhaps wd0 should just be taken completely out of libdisk? - Jordan From: Robert Watson Subject: If sysinstall is used after boot to partition, ad0 and wd0 appear Date: Thu, 22 Mar 2001 00:07:50 -0500 (EST) > > If I run /stand/sysinstall after finishing the install and logging in as > root, both ad0 and wd0 appear in the devices menu if I choose Custom -> > Partition. This is potentially quite confusing, and given that our > recommended path for post-install disk management is /stand/sysinstall. > This appears to be the case because we continue to create all wd* devices > as well as ad* devices in /dev by default. > > Robert N M Watson FreeBSD Core Team, TrustedBSD Project > robert@fledge.watson.org NAI Labs, Safeport Network Services > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-qa" in the body of the message