From owner-freebsd-alpha Fri Sep 25 15:10:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA22783 for freebsd-alpha-outgoing; Fri, 25 Sep 1998 15:10:58 -0700 (PDT) (envelope-from owner-freebsd-alpha@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA22700 for ; Fri, 25 Sep 1998 15:10:34 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id XAA11136; Fri, 25 Sep 1998 23:10:05 +0100 (BST) Date: Fri, 25 Sep 1998 23:10:05 +0100 (BST) From: Doug Rabson To: Matt Hamilton cc: freebsd-alpha@FreeBSD.ORG Subject: Re: installing bootblocks... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 25 Sep 1998, Matt Hamilton wrote: > Dear All, > Forgive my ignorance, as I haven't even tried -current on my Alpha yet > (UDB -still not supported right?), but where do bootblocks fit into the > Alpha boot process? I thought you just typed: boot blah/kernel into SRM > and it would boot the kernel? I guess I must be wrong, so where do the > bootblocks fit in? Does the boot command in SRM call the secondary boot > code in the bootblocks and then that calls the kernel? > > confused in NY I fixed the axppci33 support a few days ago (which should include UDB). I'll probably put up some more kernels tomorrow for testing. The boot blocks are necessary because SRM only knows how to load a single contiguous region of the disk. To load a kernel from a real filesystem, you need to get SRM to load a bootstrap which contains a UFS reader to read the kernel. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message