CONFIG_INPUT problems

[Martin J. Bligh]

So we seem to have a problem with the way the config stuff deals
with CONFIG_INPUT, and I'd like some advice on the best way to
fix it.

The problem:

CONFIG_INPUT was commonly set to "n" in 2.4 kernels (and hence the
configs that upgrading people pick up). Even though it defaults to
"y" under the 2.5 subsystem, the old config overrides it, which I
guess is correct for most things, but it didn't govern keyboard
and (by cascade) CONFIG_VT_CONSOLE under 2.4 (I think).

The result:

Lots of people just get a really screwed up 2.5 kernel that does
nothing useful for them.

What to do ...

I thought about inverting the logic, and creating CONFIG_HEADLESS
which is !CONFIG_INPUT basically ... but changing all the stuff
depending on CONFIG_INPUT is rather invasive. So I was thinking of
something like

CONFIG_HEADLESS
	bool "headless console support
	default "n"

if HEADLESS = y
	define_bool CONFIG_INPUT = n
else
	define_bool CONFIG_INPUT = y
endif

or something vaguely along those lines ... except there doesn't
seem to be a way I can see to force a config option on from the
new config system? So that's actually a more general question, I guess ;-)

However, if someone has a better idea on how to not shoot the poor 
users over CONFIG_INPUT / CONFIG_VT_CONSOLE, I'd be very interested ...

M.