public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: florin@iucha.net (Florin Iucha)
To: Andries Brouwer <aebr@win.tue.nl>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Private namespaces
Date: Sat, 19 Apr 2003 09:52:39 -0500	[thread overview]
Message-ID: <20030419145239.GL29143@iucha.net> (raw)
In-Reply-To: <20030416132324.GA18700@win.tue.nl>

[-- Attachment #1: Type: text/plain, Size: 804 bytes --]

On Wed, Apr 16, 2003 at 03:23:24PM +0200, Andries Brouwer wrote:
> On Mon, May 05, 2003 at 10:23:56AM -0300, Adrian Etchevarne wrote:
> 
> > 	I've been looking for instructions to use private namespaces in Linux,
> > without results. Can anyone tell where is the documentation about it?
> > (I'm not refering to chroot(), but to /proc/<pid>/mounts). Or the proper
> > files in the kernel sources?
> 
> A tiny demo program is given in
>   http://www.win.tue.nl/~aeb/linux/lk/lk-6.html#ss6.3.3
> 
> In the kernel source, grep for CLONE_NEWNS.

I have compiled the sample program on 2.5.67-pre6 and it fails with
   clone: Cannot allocate memory
when run as a regular user. Is there a workaround?

Thank you,
florin

-- 

"NT is to UNIX what a doughnut is to a particle accelerator."

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-04-19 14:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-05 13:23 Private namespaces Adrian Etchevarne
2003-04-16 13:23 ` Andries Brouwer
2003-04-19 14:52   ` Florin Iucha [this message]
2003-04-19 16:21     ` Andries Brouwer
2003-04-19 21:35       ` Andrew Morton
2003-04-16 13:40 ` Lee Causier
  -- strict thread matches above, loose matches on Subject: below --
2003-04-19 22:18 Andries.Brouwer
2003-04-19 22:22 ` Andrew Morton

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=20030419145239.GL29143@iucha.net \
    --to=florin@iucha.net \
    --cc=aebr@win.tue.nl \
    --cc=linux-kernel@vger.kernel.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