SuSE have several RPMs in their packages: one, linclude with just the
includes, linux with the actual kernel sources (without includes, they have
a dependency for that) and finally lx_suse with their hacked kernel version
complete with includes. Anyways, I think, there are a lot of people who just
follow some Kernel compilation FAQ to get their own kernel compiled with
different settings, yet they do know nothing about patches. This is where
a sort of patch registration comes in handy. It need not necessarily be in
the version itself, but a /proc/kernelconfig would also be fine. PLUS: if we
NUMBER each configuration option, not re-assigning numbers as options
disappears, we can handle all options with 2 bit each:
yes/module/no/illegal-state. The tool that decompresses the .config
information could then be either in user-space (binutils/modutils?) or a
module.
We can of course have the configuration linked in in plain text (stripping
everything that's commented out and stripping CONFIG_ prefixes), I don't
actually care since it does not matter if my bzImage is 891 or 896 k :) For
people with embedded systems, this .config-stored-in-kernel-thingy should be
optional to allow for tiny kernels.
--
Matthias Andree
--- How to obtain PGP public key
<mandree@dosis.uni-dortmund.de> <<< /finger/ this
<m_andree@line.org> <<< mail, subject "SEND PGP-PUBLIC-KEY"
-
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/