From owner-freebsd-stable@FreeBSD.ORG Wed Feb 22 07:00:00 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 6027116A420 for ; Wed, 22 Feb 2006 07:00:00 +0000 (GMT) (envelope-from plosher-keyword-freebsd.a36e57@plosh.net) Received: from luftpost.plosh.net (luftpost.plosh.net [204.152.186.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 127A543D45 for ; Wed, 22 Feb 2006 07:00:00 +0000 (GMT) (envelope-from plosher-keyword-freebsd.a36e57@plosh.net) Received: by luftpost.plosh.net (Postfix, from userid 1001) id 823C132606; Tue, 21 Feb 2006 23:02:02 -0800 (PST) Received: from [10.0.0.3] (c-67-161-77-203.hsd1.ca.comcast.net [67.161.77.203]) by luftpost.plosh.net (tmda-ofmipd) with ESMTP; Tue, 21 Feb 2006 23:01:59 -0800 (PST) Message-ID: <43FC0BE2.8020605@plosh.net> Date: Tue, 21 Feb 2006 22:59:46 -0800 Organization: Plosh Networking User-Agent: Thunderbird 1.5 (Macintosh/20051201) MIME-Version: 1.0 To: freebsd-stable@freebsd.org X-Enigmail-Version: 0.94.0.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig11D05F2BC2E982BCEE57FFE2" From: Peter Losher X-Delivery-Agent: TMDA/1.0.3 (Seattle Slew) Subject: Forcing a da* numbering scheme. 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: Wed, 22 Feb 2006 07:00:00 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig11D05F2BC2E982BCEE57FFE2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi - What's the proper method these days for defining a static naming scheme for direct access devices (da*)? In this case, I have two systems (one 5.1 and one 6.0) connected to a read-only RAID appliance (via FibreChannel) while having two SCSI disks onboard for the OS and applications. With the 5.4 system, the onboard SCSI disks take up da{0,1} and the FibreChannel connected devices fall behind it. With the 6.0 system it's the reverse, with the onboard disks taking up the end of the line, which causes more than a little havoc w/ fstab when we add more read-only devices over FibreChannel and the boot partition keeps moving because of it... :( It used to be in the 4.x days you could define the da* in the kernel and tie it to it's SCSI ID, is that still the case now, or is there some boot-time variable in /boot/loader.conf that is now preferred? -Peter --=20 [ http://www.plosh.net/ ] - "Earth Halted: Please reboot to continue" --------------enig11D05F2BC2E982BCEE57FFE2 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (Darwin) iD8DBQFD/AvpuffIhmkXw7kRAu18AJ0b82N0jnI49a4+9m8Kt59Yi2fGxQCfb69l wlJgFUNyOztPwPE7xz6xNDw= =7jhj -----END PGP SIGNATURE----- --------------enig11D05F2BC2E982BCEE57FFE2--