From owner-freebsd-current Wed Dec 30 01:24:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA23482 for freebsd-current-outgoing; Wed, 30 Dec 1998 01:24:43 -0800 (PST) (envelope-from owner-freebsd-current@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 BAA23477 for ; Wed, 30 Dec 1998 01:24:41 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by nlsystems.com (8.9.1/8.8.5) with SMTP id JAA27763; Wed, 30 Dec 1998 09:24:29 GMT Date: Wed, 30 Dec 1998 09:24:28 +0000 (GMT) From: Doug Rabson To: Brian Behlendorf cc: "Jordan K. Hubbard" , FreeBSD current users Subject: Re: How do I build an a.out kld? In-Reply-To: <4.1.19981229140706.048df410@hyperreal.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 29 Dec 1998, Brian Behlendorf wrote: > At 12:46 PM 12/29/98 -0800, Jordan K. Hubbard wrote: > >> I just upgraded to an ELF kernel, updated the boot blocks, and everything > >> boots up great, except the new boot loader appears to be looking for a > >> /boot/boot.conf (fails, then waits for 8 seconds, then boots /kernel). I > >> noticed I have a zero-length /boot.config file - should I move that to > >> /boot/boot.conf? > > > >Yeah, /boot.config is basically obsolete though it can still be used > >for its old purpose, I in fact still use it to set my rootdev since I > >haven't grok'd how to do that yet with the new scheme. > > > >/boot/boot.conf is supposed to contain any boot commands you'd like to > >have run (boot.conf is actually a bad name, now that I think about it, > >since it implies configuration variables rather than actions - boot.rc > >would have been better, oh well!). > > So would a blank file tell it to boot the default immediately, or should I > put "boot /kernel" in there? It's not that I really NEED those 8 seconds, > it just seems like it'd be cleaner to boot directly. If /boot/boot.conf doesn't exist, it defaults to running the autoboot command (which waits as you have seen). You can put autoboot in your config file with a different timeout. If you use 'boot', there is no possibility of selecting a different kernel for disaster recovery. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message