From owner-freebsd-hackers@FreeBSD.ORG Tue Feb 9 19:22:57 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1F2CA106568B for ; Tue, 9 Feb 2010 19:22:57 +0000 (UTC) (envelope-from psteele@maxiscale.com) Received: from server505.appriver.com (server505a.appriver.com [98.129.35.4]) by mx1.freebsd.org (Postfix) with ESMTP id D87898FC0A for ; Tue, 9 Feb 2010 19:22:56 +0000 (UTC) X-Policy: GLOBAL - maxiscale.com X-Primary: psteele@maxiscale.com X-Note: This Email was scanned by AppRiver SecureTide X-ALLOW: psteele@maxiscale.com ALLOWED X-Virus-Scan: V- X-Note: Spam Tests Failed: X-Country-Path: UNITED STATES->UNITED STATES->UNITED STATES X-Note-Sending-IP: 98.129.23.45 X-Note-Reverse-DNS: ht03.exg5.exghost.com X-Note-WHTLIST: psteele@maxiscale.com X-Note: User Rule Hits: X-Note: Global Rule Hits: G173 G174 G175 G176 G180 G181 G192 G279 X-Note: Encrypt Rule Hits: X-Note: Mail Class: ALLOWEDSENDER X-Note: Headers Injected Received: from [98.129.23.45] (HELO HT03.exg5.exghost.com) by server505.appriver.com (CommuniGate Pro SMTP 5.3.2) with ESMTPS id 26965310 for freebsd-hackers@freebsd.org; Tue, 09 Feb 2010 13:22:59 -0600 Received: from mbx03.exg5.exghost.com ([169.254.1.200]) by HT03.exg5.exghost.com ([10.242.228.75]) with mapi; Tue, 9 Feb 2010 13:22:55 -0600 From: Peter Steele To: "freebsd-hackers@freebsd.org" Date: Tue, 9 Feb 2010 13:22:53 -0600 Thread-Topic: How can I force boot from alternate drive with boot.config? Thread-Index: Acqo9ezeDVbqj27rRfGZ4C8AIsEEhwACsuJAAC6tTdA= Message-ID: <7B9397B189EB6E46A5EE7B4C8A4BB7CB3849F770@MBX03.exg5.exghost.com> References: <7B9397B189EB6E46A5EE7B4C8A4BB7CB383B2699@MBX03.exg5.exghost.com> <20100208175621.GA43054@zibbi.meraka.csir.co.za> <7B9397B189EB6E46A5EE7B4C8A4BB7CB383B2775@MBX03.exg5.exghost.com> <20100208193540.GA53234@zibbi.meraka.csir.co.za> <23F2E2B0457F4046AD8350DAFB86C41130D434E7@MBX03.exg5.exghost.com> In-Reply-To: <23F2E2B0457F4046AD8350DAFB86C41130D434E7@MBX03.exg5.exghost.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: RE: How can I force boot from alternate drive with boot.config? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Feb 2010 19:22:57 -0000 >>> So, more precisely, if I wanted to boot from drive 1, I'd use this? >>>=20 >>> 1:ad(1p3)/boot/loader >> >>Yes, unless there are more bugs hiding. :-) I fixed a few in August last = year. > >Well, I'll give it a try and let you know if I find new bugs... :-) I just tried this and it works as advertised--thanks. One question though: = Why does this string list the device number twice? The man page describes i= t as bios_drive:interface(unit,[slice,]part)filename where bios_drive is the "drive number as recognized by the BIOS. 0 for the= first drive, 1 for the second drive, etc.", and unit is the "unit number = of the drive on the interface being used. 0 for the first drive, 1 for the = second drive, etc." This sounds like it's describing the same thing, but not exactly, but I've = always used the same value in both fields and it's always worked. Is there = a case where these values might be different? In the test I just did I boot= ed from the fourth drive of a four drive system using 3:ad(3p4)/boot/loader I know my hardware and knew ad10 mapped to the fourth drive and would be re= ferenced as drive 3 in this context. But how would I determine this generic= ally? For example, given something like /dev/adN, how do I know what number= I'd use for this drive in boot.config?