Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 10 May 1999 06:22:12 +0800
From:      Peter Wemm <peter@netplex.com.au>
To:        wpaul@FreeBSD.ORG (Bill Paul)
Cc:        phk@critter.freebsd.dk (Poul-Henning Kamp), 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:  <19990509222214.B069E1F73@spinner.netplex.com.au>
In-Reply-To: Your message of "Sun, 09 May 1999 14:42:12 MST." <19990509214212.2A41015168@hub.freebsd.org> 

next in thread | previous in thread | raw e-mail | index | archive | help
Bill Paul wrote:
> > 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).

Umm, would this do?

makeoptions KERNEL=foo

> 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.

That part isn't, it's passed in from the bootblocks and the loader.

> 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.

peter@overcee[6:17am]~src/sys/compile/OVERCEE-111> make
[..]
linking vmunix
   text    data     bss     dec     hex filename
1517673  144151  209936 1871760  1c8f90 vmunix
peter@overcee[6:20am]~src/sys/compile/OVERCEE-118> make -n install
if [ ! -f vmunix ] ; then  echo "You must first build a kernel first." ;  exit 1 ;  fi
PATH=${PATH}:/sbin:/usr/sbin;  if [ `sysctl -n kern.bootfile` = /vmunix ] ; then  sysctl -w kern.bootfile=/vmunix.old ;  if [ -f /var/db/kvm_kernel.db ] ; then  mv -f /var/db/kvm_kernel.db /var/db/kvm_kernel.old.db ;  fi  fi
install -c -m 555 -o root -g wheel -fschg  vmunix /vmunix

This is with:
peter@overcee[6:20am]~src/sys/compile/OVERCEE-119> grep vmunix ../../i386/conf/OVERCEE 
makeoptions     KERNEL=vmunix

That should be as near to a replacement for 'config vmunix' as you can get.

There are a couple of places where the old name "kernel" is still hard coded
into the Makefiles, but they are much easier to fix now.

> -Bill

Cheers,
-Peter


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?19990509222214.B069E1F73>