mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Pavel Emelyanov <xemul@openvz.org>
Cc: Andrew Morton <akpm@osdl.org>, Cedric Le Goater <clg@fr.ibm.com>,
	Serge Hallyn <serue@us.ibm.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	devel@openvz.org
Subject: Re: [PATCH 1/5] The config option itself
Date: Mon, 1 Oct 2007 09:37:15 -0700	[thread overview]
Message-ID: <20071001093715.c4f10fe0.randy.dunlap@oracle.com> (raw)
In-Reply-To: <47011347.70906@openvz.org>

On Mon, 01 Oct 2007 19:33:27 +0400 Pavel Emelyanov wrote:

> diff --git a/init/Kconfig b/init/Kconfig
> index 6bb603a..67b1e41 100644
> --- a/init/Kconfig
> +++ b/init/Kconfig
> @@ -390,6 +381,23 @@ config RELAY
>  
>  	  If unsure, say N.
>  
> +config NAMESPACES
> +	bool "Namespaces support" if EMBEDDED
> +	default !EMBEDDED
> +	help
> +	  Provides the way to make tasks work with different objects using
> +	  the same id. For example same IPC id may refer to different objects
> +	  or same user id or pid may refer to different tasks when used in
> +	  different namespaces.
> +
> +config NAMESPACES_EXPERIMENTAL
> +	bool "Add experimantal namespaces support"

                  experimental

> +	depends on NAMESPACES && EXPERIMENTAL
> +	default n
> +	help
> +	  Also include the support for the namespaces that are not fnished

                                                                   finished

> +	  or well developed yet
> +
>  config BLK_DEV_INITRD
>  	bool "Initial RAM filesystem and RAM disk (initramfs/initrd) support"
>  	depends on BROKEN || !FRV


---
~Randy

  parent reply	other threads:[~2007-10-01 16:41 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-01 15:31 [PATCH 0/5] A config option to compile out some namespaces code (v2) Pavel Emelyanov
2007-10-01 15:33 ` [PATCH 1/5] The config option itself Pavel Emelyanov
2007-10-01 15:53   ` Serge E. Hallyn
2007-10-01 16:37   ` Randy Dunlap [this message]
2007-10-01 15:34 ` [PATCH 2/5] Move the UST namespace under the option Pavel Emelyanov
2007-10-01 15:38 ` [PATCH 3/5] Move the IPC " Pavel Emelyanov
2007-10-01 16:01   ` Cedric Le Goater
2007-10-01 15:40 ` [PATCH 4/5] Move the user " Pavel Emelyanov
2007-10-01 15:41 ` [PATCH 5/5] Move the PID " Pavel Emelyanov
  -- strict thread matches above, loose matches on Subject: below --
2007-10-31 10:58 [PATCH 0/5] A config option to compile out some namespaces code (v3) Pavel Emelyanov
2007-10-31 11:05 ` [PATCH 1/5] The config option itself Pavel Emelyanov
2007-10-31 16:19   ` Randy Dunlap
2007-10-31 17:34     ` Pavel Emelyanov
2007-10-31 22:29   ` Andrew Morton
2007-09-26 15:39 [PATCH 0/5] A config option to compile out some namespaces code Pavel Emelyanov
2007-09-26 15:43 ` [PATCH 1/5] The config option itself Pavel Emelyanov
2007-09-26 16:30   ` Randy Dunlap
2007-09-26 16:34   ` Serge E. Hallyn
2007-09-26 17:06     ` Serge E. Hallyn
2007-09-27  2:30       ` sukadev
2007-09-27  8:22         ` Pavel Emelyanov
2007-10-01 14:27           ` Serge E. Hallyn
2007-10-01 14:28             ` Pavel Emelyanov
2007-09-27 12:28   ` Cedric Le Goater

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20071001093715.c4f10fe0.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=akpm@osdl.org \
    --cc=clg@fr.ibm.com \
    --cc=devel@openvz.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=serue@us.ibm.com \
    --cc=xemul@openvz.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome