From owner-freebsd-qa Wed Mar 21 21:51:51 2001 Delivered-To: freebsd-qa@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 600ED37B71B; Wed, 21 Mar 2001 21:51:49 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.1/8.11.1) with SMTP id f2M5phh04723; Thu, 22 Mar 2001 00:51:43 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Thu, 22 Mar 2001 00:51:43 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Jordan Hubbard Cc: jkh@FreeBSD.org, qa@FreeBSD.org Subject: Re: If sysinstall is used after boot to partition, ad0 and wd0 appear In-Reply-To: <20010321214225T.jkh@osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-qa@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Perhaps it should be taken out of MAKEDEV all? :-) Has to be preserved in case the kernel is rebuilt with wd instead of ad, but if ad is the default driver, there's no reason to create wd nodes also. We need wd in libdisk since wd can still be a valid drive name in 4.x. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services On Wed, 21 Mar 2001, Jordan Hubbard wrote: > 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