Re: Building .config into the kernel

Chris Adams (cadams@ro.com)
15 Jan 1999 09:55:29 -0600


Once upon a time, Alan Cox <alan@lxorguk.ukuu.org.uk> said:
>> It's often a hard fight to find which server booted what kernel from
>> where and whether it still has it even for a _good_ admin. There isn't
>> room for more than one or two good admins per institute. The rest will
>
>I didn't believe that to be a real issue. At least until I just tried
>with the production boxes around here. Now just where did that 1.2.13lmp
>kernel tree go ..

What I would like to see is a generic way for stuff to be included in
the kernel image and loaded at boot time, but then saved out somewhere
and discarded from kernel memory. Or make some kernel memory swapable.
This could be used for adding configuration info easily.

It could also be used to keep the modules for a kernel with that kernel
image. The modules could be tacked on the end of the image after it is
compiled. Then that memory could be made swapable, or be readable
through a special interface. A user mode program could read the modules
and write them to the disk and then tell the kernel it can discard them.
With a boot-time command line option to the kernel to just toss those
sections, this wouldn't take extra memory.

The System.map file could also be appended in the same way.

I think a general method to add things to the kernel image and get them
back after booting that image would be useful for many different things.

-- 
Chris Adams - cadams@ro.com
System Administrator - Renaissance Internet Services
I don't speak for anybody but myself - that's enough trouble.

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