[Devel] Re: Playing with namespaces and bloat-o-meeter

[Eric W. Biederman]

Pavel Emelyanov <xemul at openvz.org> writes:

>>  
>> +config NAMESPACES
>> +	bool "The namespaces support"
>> +	help
>> +	  Provides the way to make tasks work with different objects using
>> +	  the same id
>> +
>> +config NS_UTS
>> +	bool "Uname namespace"
>> +	depends on NAMESPACES
>> +	help
>> +	  The utsname namespace
>> +
>> +config NS_IPC
>> +	bool "IPC namespace"
>> +	depends on NAMESPACES && SYSVIPC
>> +	help
>> +	  The SYSVIPC ids namespaces
>> +
>> +config NS_PIDS
>> +	bool "PID namespace"
>> +	depends on NAMESPACES
>> +	help
>> +	  Tasks see only the pids living in the same namespace and in the
>> +	  child namespaces
>> +
>> +config NS_UID
>> +	bool "UID namespace"
>> +	depends on NAMESPACES && EXPERIMENTAL
>> +	help
>> +	  Support user namespaces.  This allows containers, i.e.
>> +	  vservers, to use user namespaces to provide different
>> +	  user info for different servers.  If unsure, say N.
>> +
>>  config BLK_DEV_INITRD
>>  	bool "Initial RAM filesystem and RAM disk (initramfs/initrd) support"
>>  	depends on BROKEN || !FRV

The reason we removed these options earlier was a maintenance issue
and the fact we could not actually compile out the namespaces.

If we don't cause maintenance complications I think the general
idea is fine.  But please.  This all should show up under
CONFIG_EMBEDDED since the only purpose is to save space.

While things are experimental there is an additional purpose of
not exposing people to broken or partially working code, so it
does make sense to have an option there.

Eric

_______________________________________________
Containers mailing list
Containers at lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/containers