INCLUDE_CONFIG_FILE in GENERIC

[Dag-Erling Smørgrav]

"M. Warner Losh" <imp at bsdimp.com> writes:
> [...]  I think this
> is the model that best fits most user's needs, since they EITHER take
> GENERIC and hack on it (in which case we preserve all that), OR they
> include GENERIC and opt in/out of things based on that default.

The latter is a far better option - I use the former and have been
bitten several times by new mandatory devices and options such as device
io, scheduler selection, etc.  However, the latter option is not very
practical.  Picking one of my machines at random, its kernel config has
65 device / option lines, while GENERIC has 219, and they only have 51
lines in common.  Instead of 65 device / option lines, I would need 168
nodevice / nooption lines plus 14 device / option lines, for a total of
182 lines.

> Heck, we could save the whole src/sys tree as a tarball in a separate
> non-loadable ELF section if people that that was useful.

Ouch.

OTOH, the sys tree is actually smaller than a full GENERIC build...

Is there any way we could limit this to those parts of the tree that
were actually used to build the kernel?

DES
-- 
Dag-Erling Smørgrav - des at des.no