Re: config procfs patch

Keith Owens (kaos@ocs.com.au)
Sun, 25 May 1997 14:06:52 +1000

On 24 May 1997 11:10:45 -0700,
o.r.c@p.e.l.l.p.o.r.t.l.a.n.d.o.r.u.s (david parsons) wrote:
>In article <linux.kernel.udlk9kpvlyg.fsf@tux.mit.edu>,
>Aaron M. Ucko <amu@mit.edu> wrote:
>>Unless I'm mistaken, the reason is that it would be redundant;
>>you should already have the .config.
>
> One place I can see this breaking badly is where you do kernel builds
> on one machine and then install these kernels on other machines (I
> do this) or where you have a collection of different kernels that
> you boot on one machine with differing capacities (I do this, too.)

Assuming you still maintain a separate System.map for each kernel, this
one line addition to Makefile will append the current config to the
map. No kernel changes required. Extract the config by "grep CONFIG_
System.map". Is this method was standard, a simple change to syslogd
could extract it automatically. If you don't have a separate
System.map for each kernel, my commiserations.

--- linux-2.1.40/Makefile Sat May 24 23:42:32 1997
+++ linux/Makefile Sat May 24 23:43:38 1997
@@ -182,6 +182,7 @@
$(LIBS) \
-o vmlinux
$(NM) vmlinux | grep -v '\(compiled\)\|\(\.o$$\)\|\( [aU] \)\|\(\.\.ng$$\)\|\(LASH[RL]DI\)' | sort > System.map
+ sed -ne "/^CONFIG_/s/^/`sed -ne '/ _end$$/s/ .*//p' System.map` ? /p" .config >> System.map

symlinks:
rm -f include/asm