linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: DervishD <raul@pleyades.net>
To: Ville Herva <vherva@niksula.hut.fi>
Cc: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Using proc in chroot environments
Date: Sun, 2 Nov 2003 22:40:51 +0100	[thread overview]
Message-ID: <20031102214051.GC54@DervishD> (raw)
In-Reply-To: <20031102210320.GP4868@niksula.cs.hut.fi>

    Hi Ville :)

 * Ville Herva <vherva@niksula.hut.fi> dixit:
> >     - I must mount copies of devpts, usbfs, etc... under the 'second'
> > proc, too, and this is even more annoying.
> Mount them under /.../chroot/proc ? Hm.

    That's what I'm doing right now (well I mount them under the /dev
directory of the chroot environment ;)
  
> >     The perfect solution for me is to hardlink the proc directory of
> > the chrooted environment to the proc directory on the true root dir,
> > but since this is not possible, whan can I do instead of remounting a
> > second copy of proc (which, by the way, makes /proc/mounts a little
> > bit weird...)?
> mount --bind is closest to hardlink you can get and it works. But I don't
> know if that is that much different from mounting proc second time.

    For other filesystems I don't know, for proc is more or less the
same, except maybe that --bind maybe doesn't show proc mounted twice
:???

    Thanks :))

    Raúl Núñez de Arenas Coronado

-- 
Linux Registered User 88736
http://www.pleyades.net & http://raul.pleyades.net/

  parent reply	other threads:[~2003-11-02 21:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-02 20:49 Using proc in chroot environments DervishD
     [not found] ` <20031102210320.GP4868@niksula.cs.hut.fi>
2003-11-02 21:40   ` DervishD [this message]
2003-11-03  3:10 ` Mark Mielke
2003-11-03  9:49   ` DervishD
2003-11-06 16:00 ` David Gómez
2003-11-07  9:35   ` DervishD

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=20031102214051.GC54@DervishD \
    --to=raul@pleyades.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vherva@niksula.hut.fi \
    /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;
as well as URLs for NNTP newsgroup(s).