Date: Wed, 21 Mar 2001 21:42:25 -0800 From: Jordan Hubbard <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 Message-ID: <20010321214225T.jkh@osd.bsdi.com> In-Reply-To: <Pine.NEB.3.96L.1010322000533.3259C-100000@fledge.watson.org> References: <Pine.NEB.3.96L.1010322000533.3259C-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <rwatson@FreeBSD.org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010321214225T.jkh>