archive mirror
 help / color / mirror / Atom feed
From: DervishD <>
To: Linux-kernel <>
Subject: Using proc in chroot environments
Date: Sun, 2 Nov 2003 21:49:34 +0100	[thread overview]
Message-ID: <20031102204934.GB54@DervishD> (raw)

    Hi all :)

    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:

    - Any change in the chroot proc happens too in the main one (like
using /proc/sys/kernel variables). Not a big deal, since I want the
chroot environment to mimic the main filesystem where the original
proc is mounted, but is annoying.

    - I must mount copies of devpts, usbfs, etc... under the 'second'
proc, too, and this is even more annoying.

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

    Thanks a lot in advance :))

    Raúl Núñez de Arenas Coronado

Linux Registered User 88736 &

             reply	other threads:[~2003-11-02 20:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-02 20:49 DervishD [this message]
     [not found] ` <>
2003-11-02 21:40   ` Using proc in chroot environments 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

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=20031102204934.GB54@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).