Re: CONFIG_INPUT problems

[Martin J. Bligh]

>> > config INPUT
>> > 	default y if !HEADLESS
>> 
>> I don't see how that'll work ... we already have it defaulting to y,
>> but there's a previous setting that's 'n' from the 2.4 config file
>> they're upgrading from ... and that overrides the default, right?
> 
> A default without a visible prompt works like derived variable.
> If there is prompt, the .config value and the default value is used as 
> default input for the prompt.

Aha! that's perfect - thanks.

M.