From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pavel Emelyanov Subject: Re: netns compilation Date: Wed, 14 Nov 2007 18:09:59 +0300 Message-ID: <473B0FC7.6040900@openvz.org> References: <473B0DF7.2050509@fr.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <473B0DF7.2050509-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: Daniel Lezcano Cc: Linux Containers , "Denis V. Lunev" , "Eric W. Biederman" List-Id: containers.vger.kernel.org Daniel Lezcano wrote: > Actually the CONFIG_NET_NS is depending on CONFIG_NET and !CONFIG_SYSFS > > In order to disable CONFIG_SYSFS, I must specify CONFIG_EMBEDDED to have > the choice to unset the sysfs. > > Why don't we make CONFIG_NET_NS depends on CONFIG_NET and > CONFIG_SYSFS_DEPRECATED ? > AFAIK the SYSFS_DEPRECATED hides the sysfs functionality (files) that is not recommended to use, but doesn't disable the sysfs filesystem as is. On the other hand the NET_NS doesn't require any deprecated sysfs files, it just can't work at all with the SYSFS turned on. That's why the things look like this. Thanks, Pavel