From owner-freebsd-stable@FreeBSD.ORG Mon Jan 30 06:20:53 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 05D3716A420 for ; Mon, 30 Jan 2006 06:20:53 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 430FE43D4C for ; Mon, 30 Jan 2006 06:20:48 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (inchoate.gsoft.com.au [203.31.81.31]) (authenticated bits=0) by cain.gsoft.com.au (8.13.5/8.13.4) with ESMTP id k0U6KRng009979 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 30 Jan 2006 16:50:30 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-stable@freebsd.org Date: Mon, 30 Jan 2006 16:49:56 +1030 User-Agent: KMail/1.9.1 References: <20060129205612.G751@sauron.bolingbroke.com> In-Reply-To: <20060129205612.G751@sauron.bolingbroke.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart6397793.vQLJMmRt7y"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200601301650.16285.doconnor@gsoft.com.au> X-Spam-Score: -1.36 () ALL_TRUSTED X-Scanned-By: MIMEDefang 2.54 on 203.31.81.10 Cc: Subject: Re: Have the device names for hard discs been changed? (fwd) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jan 2006 06:20:53 -0000 --nextPart6397793.vQLJMmRt7y Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Monday 30 January 2006 15:27, Ken Bolingbroke wrote: > You start out with a disk, /dev/ad6, and you "dangerously dedicate" it, > then you _should_ have 's1' appended to /dev/ad6 to make /dev/ad6s1. But > for some reason, it's appending it to /dev/ad6c instead to make > /dev/ad6cs1, and then sysinstall tries to label the disk with /dev/ad6cs1= c, > etc, and fails. (Note the _two_ 'c' characters in that device name) > > My work around so far is after using fdisk in sysinstall to "dangerously > dedicate" my disk, I exit, then "rm /dev/ad6cs1", then go back to > sysinstall and label the disk, and then it will correctly use /dev/ad6s1. If you're using 5.x or 6.x which have devfs, it would point to a bug in geo= m=20 (or somewhere in the kernel anyway) as the device names are generated insid= e=20 the kernel. Personally I'd just stick to not using dangerously dedicated. =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart6397793.vQLJMmRt7y Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBD3bAg5ZPcIHs/zowRApbOAKCE4afpbxFY9RtgsKUQ5RLoSlNC3gCgqtFr FC4r79M5fRp9D/ekyJIlvhU= =0PiJ -----END PGP SIGNATURE----- --nextPart6397793.vQLJMmRt7y--