RFC: add an ADVANCED_USER option

[Adrian Bunk <bunk@stusta.de>]

On Tue, Feb 07, 2006 at 10:38:05AM +0100, Bernd Petrovitsch wrote:
> On Tue, 2006-02-07 at 01:41 +0100, Herbert Poetzl wrote:
> > On Mon, Feb 06, 2006 at 03:56:34PM +0100, Jan Engelhardt wrote:
> [...]
> > > 
> > > So, just as I did in the sample patch, the manual split shall depend on 
> > > EMBEDDED. Those who run fat databases with big malloc/mmap assumptions 
> > > don't probably belong to the group using CONFIG_EMBEDDED.
> > 
> > *sigh* well, the embeded folks are unlikely to have 1-3GB
> 
> ACK.
> But don't be confused by the naming: CONFIG_EMBEDDED nowadays means
> "options for people who know really what they do". It came originally
> from the embedded world but applies now also to others. 
> No one has come up with a better option name up to now ...
>...

It's slightly different:

EMBEDDED is limited to options allowing additional space savings for 
machines with strong space limits.

If you have enough RAM that VMSPLIT matters, you shouldn't enable 
EMBEDDED.

What we could do is to add an additional ADVANCED_USER option that hides 
options like VMSPLIT or the NAPI options for net drivers.

This would result in the following (the text for ADVANCED_USER isn't 
good, but you get the idea):

config ADVANCED_USER
	bool "ask questions that require a deeper knowledge of the kernel"

config EXPERIMENTAL
	bool "Prompt for development and/or incomplete code/drivers"
	depends on ADVANCED_USER

menuconfig EMBEDDED
        bool "Configure standard kernel features (for small systems)"
        depends on ADVANCED_USER

> 	Bernd

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

-
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/