Messages in this thread | | | Date | Wed, 09 Apr 2003 13:02:20 -0700 | From | "Martin J. Bligh" <> | Subject | Re: CONFIG_INPUT problems |
| |
>> 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 > > 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?
I think in general, that's the right behaviour (else you'd override your previous settings every time). It's just that in this case, it creates a serious user problem that we really need to fix. Personally, I'd be happy to just force it to on all the time, but I suspect that'd get me lynched ;-)
>> 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 ;-) > > I know, this has been requested a few times, I hope to have something > soon. (It's more a time problem.)
OK, thanks.
M.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |