Subject: HEADS UP: new config + config embedded in kernel
To: None <firstname.lastname@example.org>
From: Andrew Brown <email@example.com>
Date: 12/17/2001 21:59:44
apologies to any affected (one person that i know of directly)...i
should have sent this earlier today, but my alter ego as "a person
with other things that need doing" interfered. :)
i've tweaked config to emit a config_file.h that contains the kernel
config file (and all files it includes directly) as a string,
sys/conf/files to handle two new kernel options controlling the
string's contents, and param.c to include "config_file.h"...
...all so that one can now embed the kernel config file in the kernel
itself. the presence of the string shouldn't affect the size of the
kernel in memory, only the size of the kernel binary itself.
what this means for you is that if you've updated your source tree,
you'll need to rebuild and reinstall config, otherwise param.c will go
looking for files that the old config wasn't generating.
on the upside, one no longer has to worry about losing a kernel
|-----< "CODE WARRIOR" >-----|
firstname.lastname@example.org * "ah! i see you have the internet
email@example.com (Andrew Brown) that goes *ping*!"
firstname.lastname@example.org * "information is power -- share the wealth."