> >> /proc/config
> ...
> >I don't want 8K of my kernel wasted because I can't remember to save config
> >files.
>
> Perhaps this should be a config option? CONFIG_PROC_CONFIG?
I would add that this is far from 8K. For the following reason
-You store only what is being configured in the kernel
if it is not it is not.
-Many configuration option are visible in /proc already
-Stuff selected as module don't need to told. they are modules
anyway.
This would amount at few hundred byte to the most. I have done something
like this 2 years ago. I have added a minor modification to the current
config script and it was possible to extract "useful" configuration
information and build /proc/config dynamicly at kernel compile time. In
the config script, I was flagging the config option which were useful
(because their status could not be grabbed at run time from other mean).
--------------------------------------------------------
Jacques Gelinas (jacques@solucorp.qc.ca)
Linuxconf: The ultimate administration system for Linux.
see http://www.solucorp.qc.ca/linuxconf