All of lore.kernel.org
 help / color / mirror / Atom feed
From: chris barry <Christopher.Barry@qlogic.com>
Cc: autofs@linux.kernel.org
Subject: Re: bind mounting into a generated multi-level directory	structure
Date: Thu, 14 Feb 2008 17:32:52 -0500	[thread overview]
Message-ID: <1203028372.8007.54.camel@localhost> (raw)
In-Reply-To: <47AF07BF.2040405@bononline.nl>

On Sun, 2008-02-10 at 15:18 +0100, Stef Bon wrote:
> Chris Stromsoe wrote:
> > I have a set of directories that are created and removed programmatically, 
> > and are hashed three levels deep (/top/hash/hash/name).  The depth is 
> > constant, the hashes and names are not.  There are around 35k at any time. 
> > I would like to bind mount a common directory into each top-level 
> > (/top/hash/hash/name/data) on demand.
> >
> > Can I use autofs to do that without having to explicitly list all of the 
> > directory paths in auto.master?
> >   
> Why not use symlinks to this shared common directory, and mount that one?
> 
> Stef Bon

His goal is to create a chroot'd environment, and the symlink cannot
function there. man chroot to help you understand why.

-C

  reply	other threads:[~2008-02-14 22:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-10  8:29 bind mounting into a generated multi-level directory structure Chris Stromsoe
2008-02-10 14:18 ` Stef Bon
2008-02-14 22:32   ` chris barry [this message]
2008-02-15  9:52     ` Stef Bon
2008-02-15 21:44       ` Chris Stromsoe
2008-02-16  9:47         ` Stef Bon
2008-02-17  7:51           ` Chris Stromsoe
2008-02-18 15:37         ` OT: was " chris barry
2008-02-11  8:13 ` Ian Kent
2008-02-11  9:53   ` Chris Stromsoe
2008-02-11 10:34     ` Ian Kent
2008-02-12 22:35       ` Chris Stromsoe
2008-02-11 13:50 ` Stef Bon

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=1203028372.8007.54.camel@localhost \
    --to=christopher.barry@qlogic.com \
    --cc=autofs@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.