All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vincent ROQUETA <vincent.roqueta@ext.bull.net>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: nfs@lists.sourceforge.net
Subject: Re: NFSv4 & /etc/exportfs
Date: Mon, 26 Jan 2004 17:13:50 +0100	[thread overview]
Message-ID: <200401261713.50547.vincent.roqueta@ext.bull.net> (raw)
In-Reply-To: <20040126152747.GA14181@fieldses.org>

Le Lundi 26 Janvier 2004 16:27, J. Bruce Fields a =E9crit :
> On Mon, Jan 26, 2004 at 03:44:07PM +0100, Vincent ROQUETA wrote:
> > I tried to mount a directory using the old nfs conf. format (as indicat=
ed
> > in the man) and using the new one, as described here :
> > http://www.citi.umich.edu/projects/nfsv4/june_2002_rel/exports.html
>
> That's very out of date; the format described there was for a much older
> version of the code and will probably never be used.  See
> http://www.citi.umich.edu/projects/nfsv4/linux/ for instructions on
> exporting to nfsv4.  The idea is to use the fsid=3D0 option to mark one
> export as the nfsv4 "pseudofilesystem root" (the filesystem clients will
> get if they mount yourserver:/) and then attach other exports underneath
> it using mount --bind.
>
> --Bruce Fields

Great! It works fine ;)=20
Thx


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

      reply	other threads:[~2004-01-26 16:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-26 14:44 NFSv4 & /etc/exportfs Vincent ROQUETA
2004-01-26 15:04 ` Vincent ROQUETA
2004-01-26 15:27 ` J. Bruce Fields
2004-01-26 16:13   ` Vincent ROQUETA [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=200401261713.50547.vincent.roqueta@ext.bull.net \
    --to=vincent.roqueta@ext.bull.net \
    --cc=bfields@fieldses.org \
    --cc=nfs@lists.sourceforge.net \
    /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.