From owner-freebsd-alpha Fri Jan 11 5:31: 0 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.inka.de (quechua.inka.de [212.227.14.2]) by hub.freebsd.org (Postfix) with ESMTP id E22A837B41B for ; Fri, 11 Jan 2002 05:30:51 -0800 (PST) Received: from kemoauc.mips.inka.de (uucp@) by mail.inka.de with local-bsmtp id 16P1lf-0008H3-01; Fri, 11 Jan 2002 14:30:47 +0100 Received: (from mailnull@localhost) by kemoauc.mips.inka.de (8.11.6/8.11.6) id g0BDDlj00651 for freebsd-alpha@freebsd.org; Fri, 11 Jan 2002 14:13:47 +0100 (CET) (envelope-from mailnull) From: naddy@mips.inka.de (Christian Weisgerber) Subject: Re: -CURRENT boot1 broken? Date: Fri, 11 Jan 2002 13:13:46 +0000 (UTC) Message-ID: References: Originator: naddy@mips.inka.de (Christian Weisgerber) To: freebsd-alpha@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Christian Weisgerber wrote: > As a side effect of experimenting with various boot combinations, > I'm confused about where the different components are loaded from. While testing Ian's patch, I've tried again various combinations, and Mike is right: > 1. At the SRM prompt, booting from a particular drive will load the > bootstrap (boot1) from there. > 2. boot1 proceeds to load /boot/loader from the same drive. You > can specify a different file name, but there appears to be no > way to qualify this with a drive. > 3. loader pulls in the kernel from da0, even if booted from a > different drive. 3. loader pulls in the kernel from the same drive. (I must have been confused there.) > 4. The kernel mounts da0a as root device. 4. The kernel mounts / as specified in /etc/fstab on the boot drive. -- Christian "naddy" Weisgerber naddy@mips.inka.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message