Date: Sun, 9 May 1999 14:42:12 -0700 (PDT) From: wpaul@FreeBSD.ORG (Bill Paul) To: phk@critter.freebsd.dk (Poul-Henning Kamp) Cc: cvs-committers@freebsd.org, cvs-all@freebsd.org, jb@cimlogic.com.au Subject: Re: cvs commit: src/sys/conf options src/sys/i386/i386 autoconf.c src/sys/i386/conf GENERIC LINT Makefile.i386 files.i386 Message-ID: <19990509214212.2A41015168@hub.freebsd.org> In-Reply-To: <21969.926281972@critter.freebsd.dk> from Poul-Henning Kamp at "May 9, 1999 10:32:52 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> In message <199905092039.GAA15011@cimlogic.com.au>, John Birrell writes: > >Poul-Henning Kamp wrote: > >> Major lobotomy of config(8). The > >> > >> config kernel mumble mumble > >> > >> line has been obsoleted and removed and with it went all knowledge of > >> devices on the part of config. > > > >Does this change mean that it is no longer possible to choose the name > >of the "kernel"? I was using this "feature" for embedded kernels that > >get loaded into flash on boards. These embedded kernels aren't general, > >so I thought they deserved to have board-specific names. > > Uhm, sorry, didn't think anybody used that feature (considering how > many places "kernel" was already hardcoded). Well now you know. Please put it back (not all of it, just the ability to say "config foo" to specify the name of the kernel image). As for "kernel" being hardcoded, it should not be. Anything that needs to know the name of the currently running kernel image should be getting it from the kern.bootfile sysctl variable. Harcoding "kernel" is generally a bug. (savecore(8) is one example.) It's certainly a bug here. I name all my kernels "vmunix". Anyone who does something that breaks my ability to do that will have to face me and *my* axe. -Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990509214212.2A41015168>