Date: Tue, 29 Dec 1998 14:10:05 -0800 From: Brian Behlendorf <brian@hyperreal.org> To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com> Cc: FreeBSD current users <FreeBSD-current@FreeBSD.ORG> Subject: Re: How do I build an a.out kld? Message-ID: <4.1.19981229140706.048df410@hyperreal.org> In-Reply-To: <8069.914964398@zippy.cdrom.com> References: <Your message of "Tue, 29 Dec 1998 12:20:03 PST." <4.1.19981229121528.03d98ed0@hyperreal.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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. Brian --=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-- History is made at night; brian@hyperreal.org character is what you are in the dark. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4.1.19981229140706.048df410>