From owner-freebsd-stable@FreeBSD.ORG Fri Jan 12 15:26:40 2007 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5DC1B16A407 for ; Fri, 12 Jan 2007 15:26:40 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.freebsd.org (Postfix) with ESMTP id 0B35A13C448 for ; Fri, 12 Jan 2007 15:26:39 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7]) (authenticated bits=0) by server.baldwin.cx (8.13.6/8.13.6) with ESMTP id l0CFQXnZ006781; Fri, 12 Jan 2007 10:26:37 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-stable@freebsd.org Date: Fri, 12 Jan 2007 10:25:15 -0500 User-Agent: KMail/1.9.4 References: <09710CBA-0006-4502-B5F7-6048B290D3B8@svcolo.com> In-Reply-To: <09710CBA-0006-4502-B5F7-6048B290D3B8@svcolo.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200701121025.15555.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [192.168.0.1]); Fri, 12 Jan 2007 10:26:38 -0500 (EST) X-Virus-Scanned: ClamAV 0.88.3/2437/Thu Jan 11 18:59:09 2007 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: Jo Rhett Subject: Re: any real documentation of the boot2 prompt? 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: Fri, 12 Jan 2007 15:26:40 -0000 On Thursday 11 January 2007 23:55, Jo Rhett wrote: > On Jan 11, 2007, at 8:50 PM, Jo Rhett wrote: > > So I've been searching for hours now, and it appears that short of > > reading the C code, there's no documentation of the boot2 menu prompt. > > I'd like to add to this that the handbook is riddled full of > undocumented terms, like BIOS Drive #. How do you determine this for > a SCSI drive? A BIOS driver number is the number you pass to the BIOS to access a drive. Typically drive 0x0 is a floppy drive and hard drives start at 0x80. Usually the SCSI BIOS will list the BIOS driver number during the POST messages and it will look like 80, 81, etc. There is no standard way as it is at the BIOS' discretion. > And what is the difference between the drive number and the unit > number anyway? Completely unrelated. Drive number is assigned by the SCSI BIOS, unit number is assigned by the kernel driver. To answer your question: you need to first make sure your SCSI BIOS is registering your second disk with the BIOS. Assuming it's mapped as drive 81, you can then use '1:da(1,a)'. If it shows up as drive 82, then use 2:da(1,a)', etc. -- John Baldwin