From owner-freebsd-current Sun Aug 9 13:48:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA22437 for freebsd-current-outgoing; Sun, 9 Aug 1998 13:48:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.camalott.com (mail.camalott.com [208.203.140.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA22428 for ; Sun, 9 Aug 1998 13:48:33 -0700 (PDT) (envelope-from joelh@gnu.org) Received: from detlev.UUCP (tex-118.camalott.com [208.229.74.118]) by mail.camalott.com (8.8.7/8.8.5) with ESMTP id PAA27315; Sun, 9 Aug 1998 15:49:06 -0500 Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id PAA03447; Sun, 9 Aug 1998 15:46:37 -0500 (CDT) (envelope-from joelh) Date: Sun, 9 Aug 1998 15:46:37 -0500 (CDT) Message-Id: <199808092046.PAA03447@detlev.UUCP> To: mike@smith.net.au CC: ben@rosengart.com, dacole@netcom.ca, current@FreeBSD.ORG In-reply-to: <199808061544.IAA03196@antipodes.cdrom.com> (message from Mike Smith on Thu, 06 Aug 1998 08:44:07 -0700) Subject: Re: New bootstrap config file(s) (Re: booting with verbosity by default? ) From: Joel Ray Holveck Reply-to: joelh@gnu.org References: <199808061544.IAA03196@antipodes.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>> I would like to force my systems to always boot with '-v'.. Is there >>>> any way to do this without operator intervention? >>> Take a look at what boot(8) has to say about /boot.config. >> It says that -v doesn't make the cut for boot.config. The fix is >> trivial, but I haven't yet rolled a pr. >> This suggestion hasn't been carefully considered or tested, but if you >> want to fix it yourself, then in /sys/i386/boot/biosboot/boot.c, move >> the bit about "loadflags &= (RB_DUAL | RB_SERIAL);" to right around >> "readfile("boot.config", ...);" about 40 lines up. (The key is that >> it should be before "getbootdev(boot_config, &loadflags);".) This >> will effectively allow any boot flags in. > It will become either "-v" in /boot.config or "set bootverbose" in > the new bootstrap config, which I haven't named. > And this is a handy topic to raise it under; the new bootstrap will > (optionally) need access to quite a few files, and we may not really > want these cluttering up the root directory. How do people feel about > a /boot directory these days? If you're reworking the bootstrap, is it worth me submitting a pr with this patch? (I'm implementing it locally anyway.) Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message