archive mirror
 help / color / mirror / Atom feed
From: DervishD <>
To: Linux-kernel <>
Subject: Re: Using proc in chroot environments
Date: Fri, 7 Nov 2003 10:35:02 +0100	[thread overview]
Message-ID: <20031107093502.GY275@DervishD> (raw)
In-Reply-To: <20031106160028.GA6392@fargo>

    Hi David :)

 * David <> dixit:
> >     I'm using a chroot environment on my main disk as a 'crash test
> > dummy', and I need to access the proc filesystem inside it. Since
> > hard links are not allowed for directories, the only solution I can
> > think of is to mount proc inside the chroot environment just after
> > chrooting. This works, I've tested, but I have two problems:
> Have you tried the --bind mount option? It's great to solve this kind
> of problem, accesing to a directory within a chrooted enviroment. I've
> used it successly with a ftp server ;).

    I haven't tried, but I'm afraid it won't solve my problem. First,
if I do a 'binded' mount of /proc, any change in the chrooted proc
will reflect in the original one, so I'm in trouble anyway. Second,
if I do 'mount' or 'cat /proc/mounts' the proc filesystem will be
shown twice anyway (correct me here if I'm wrong).

    By now I'm going to keep using two independent mounts until I
find a better approach... Thanks for your answer :)

    Raúl Núñez de Arenas Coronado

Linux Registered User 88736 &

      reply	other threads:[~2003-11-07 22:18 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] ` <>
2003-11-02 21:40   ` DervishD
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 [this message]

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:

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

  git send-email \
    --in-reply-to=20031107093502.GY275@DervishD \ \ \

* 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).