Messages in this thread | | | Date | Tue, 3 Dec 2002 14:20:30 -0500 (EST) | From | Bill Davidsen <> | Subject | Re: [PATCH 2.5] Extract configuration from kernel |
| |
On Tue, 3 Dec 2002, Khalid Aziz wrote:
> bill davidsen wrote: > > > > | 2. Include configuration in kernel image file but not in the running > > | kernel. This adds to the kernel image file size but not the footprint of > > | running kernel. Configuration can be extracted from kernel image file > > | using scripts/extract-ikconfig. This script is in principle the same as > > | what Randy had written originally. I have made it little more robust and > > | structured it to accomodate more than just x86 architecture. > > > > I would suggest that making (2) available as a module would be useful, > > assuming that at some point 2.5 will have working module capability > > again. With a bit of tweaking you could make the kernel loader pull it > > in if a process accessed the file, I guess. > > It is trivial to make (2) available as a module but it has been debated > that having configuration information available as module does not make > the job of keeping a reliable source of kernel configuration any easier > than just keeping a copy of config file in, say, /lib/modules directory. > If you can ensure you always have the right module file available for > the running kernel, you can also ensure you always have the right config > file available for the kernel.
All true, I just find having the config in the same location for all kernels (in say /proc/config) is more convenient than having to resolve the kernel name from another file or do /lib/modules/$(uname -r)/config from a script. The kernel knows who it is, all others have to ask. It's just one less step a program would have to take, not a major problem.
-- bill davidsen <davidsen@tmr.com> CTO, TMR Associates, Inc Doing interesting things with little computers since 1979.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |