Date: Tue, 16 Mar 1999 05:45:07 -0500 From: "Donald J . Maddox" <dmaddox@conterra.com> To: Mark Ovens <marko@uk.radan.com> Cc: Chris Landauer <cal@rush.aero.org>, questions@FreeBSD.ORG Subject: Re: 2.2.8 boot still wants sysinstall - answered Message-ID: <19990316054507.A585@dmaddox.conterra.com> In-Reply-To: <36EE0BA1.1906680E@uk.radan.com>; from Mark Ovens on Tue, Mar 16, 1999 at 07:43:29AM %2B0000 References: <199903160211.SAA02628@chuck.aero.org> <36EE0BA1.1906680E@uk.radan.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Mar 16, 1999 at 07:43:29AM +0000, Mark Ovens wrote: > Chris Landauer wrote: > > > > I recently asked why the sysinstall menu came up when i booted 2.2.8, > > and i now see in my kernel configuration file that i enabled > > USERCONFIG_BOOT > > > > which i presume causes exactly that behavior > > No. USERCONFIG_BOOT causes the kernel to read /kernel.config at boot > time, and execute any commands in there as if you had done ``boot -c'' > and typed them manually. It even echoes them to the screen the way you > would type them in. You could check if there is anything in > /kernel.config (I don't know if there is a boot option to start > sysinstall). No, actually, USERCONFIG_BOOT just causes the kernel config editor to be entered at boot time, and sources the /kernel.config... If your /kernel.config doesn't end with 'quit' or 'q', or if you don't actually have a /kernel.config, you would simply find yourself in the config editor at boot, much like the original poster describes. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990316054507.A585>