Re: [PATCH 0/3] removing unwanted module configs

[Ingo Molnar]

* Steven Rostedt <rostedt@xxxxxxxxxxx> wrote:

> On Thu, 30 Apr 2009, Ingo Molnar wrote:
> > 
> > CONFIG_IKCONFIG=y would be a one-off thing, only to make the 
> > whole concept self-hosting. If i boot a localyesconfig kernel, 
> > how does the script figure out what is built in? It cannot, 
> > unless i provide it the precise .config - but often that wont be 
> > provided. The script should clone the environment it is running 
> > in really.
> 
> Does IKCONFIG get loaded in the running kernel if IKCONFIG_PROC is 
> not set, or does it just sit in the vmlinux file.
> 
> Since this option can also be used for helping embedded developers 
> (I used it for that) I would not want to bloat the kernel with 
> running a script that is suppose to minimize it. But if IKCONFIG 
> && !IKCONFIG_PROC does not add more data to the kernel, then I 
> would be happy to turn it on by default.

this is a basic usability issue. The main goal is to help regular 
Linux users.

> I see I can use scripts/extract-ikconfig to get the config from 
> the current image. Now which image should it try?

no, enable IKCONFIG_PROC and it will be under /proc/config.gz.

> /boot/vmlinuz-`uname -r`
> ./vmlinux
> 
> I could have it first try /proc/config.gz and if it does not find 
> it then try the /boot kernel, if it does not find it or does not 
> find a config file in it, it would then try ./vmlinux file. If it 
> does not find the file or the config then it would just use the 
> local .config.

yeah, that sounds like a good plan.

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/