public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben DJ <bendj095124367913213465@gmail.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: are multiple FSIDs supported?
Date: Fri, 23 Oct 2009 12:09:25 -0700	[thread overview]
Message-ID: <babafd2f0910231209w3c9ea401pc2e38b352e5f416f@mail.gmail.com> (raw)
In-Reply-To: <20091023190053.GB32155@fieldses.org>

Hi Bruce,

On Fri, Oct 23, 2009 at 12:00 PM, J. Bruce Fields <bfields@fieldses.org=
> wrote:
>> My goal would be to export, for example
>>
>> =A0/nfs1 & it's subdirs ONLY to LAN box1
>> =A0/nfs2 & it's subdirs ONLY to LAN box2
>> =A0etc
>
> Multiple export namespaces aren't currently supported.
>
> I'd like to some day, though I'd prefer to vary the namespace based o=
n
> server ip address instead of by client ip address.
>
> But for now I'd think just something like:
>
> =A0 =A0 =A0 =A0/nfs =A0 =A0*(ro,fsid=3D0,...)
> =A0 =A0 =A0 =A0/nfs/1 =A0box1(rw,nohide,crossmnt)
> =A0 =A0 =A0 =A0/nfs/2 =A0box2(rw,nohide,crossmnt)
>
> should server your purposes. =A0box1 will still be able to see that a
> directory named /nfs/2 exists,

There are a few situations where I'm going to have to figure out a way
around this.  I.e., where I don't want boxes to even "be able to see"
other boxes' dirs.

> but it shouldn't be able to descend into
> it. =A0(And vice-versa for box2 and /nfs/1.)

Thanks for the suggestion and explanation.  I'd seen the crossmnt
option, but didn't understand how it was really different than nohide.

BenDJ

      reply	other threads:[~2009-10-23 19:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-23 18:32 are multiple FSIDs supported? Ben DJ
     [not found] ` <babafd2f0910231132n464da0crc2a5cc0427af9a40-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-10-23 19:00   ` J. Bruce Fields
2009-10-23 19:09     ` Ben DJ [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:
  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=babafd2f0910231209w3c9ea401pc2e38b352e5f416f@mail.gmail.com \
    --to=bendj095124367913213465@gmail.com \
    --cc=bfields@fieldses.org \
    --cc=linux-nfs@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