From: "J. Bruce Fields" <bfields@fieldses.org>
To: Jason Keltz <jas@cse.yorku.ca>
Cc: James Pearson <james-p@moving-picture.com>, nfs@lists.sourceforge.net
Subject: Re: fsid question
Date: Tue, 27 Mar 2007 11:05:47 -0400 [thread overview]
Message-ID: <20070327150547.GA7161@fieldses.org> (raw)
In-Reply-To: <460930DE.50507@cse.yorku.ca>
On Tue, Mar 27, 2007 at 10:57:34AM -0400, Jason Keltz wrote:
> That makes sense, but what is still not clear to me is why I can't have
> the system show me the existing fsid that it is using in the absence of
> a user-specified fsid.
There *is* no "existing fsid". The fsid that you provide in the "fsid="
export option is totally different from what's used by default to
generate filehandles for that filesystem.
--b.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-03-27 15:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-26 20:29 fsid question Jason Keltz
2007-03-26 21:00 ` Wendy Cheng
2007-03-27 12:50 ` Jason Keltz
2007-03-27 12:56 ` James Pearson
2007-03-27 13:29 ` Jason Keltz
2007-03-27 14:27 ` James Pearson
2007-03-27 14:57 ` Jason Keltz
2007-03-27 15:05 ` J. Bruce Fields [this message]
2007-03-27 14:52 ` Wendy Cheng
2007-03-27 15:23 ` J. Bruce Fields
2007-03-27 15:32 ` Trond Myklebust
2007-03-27 15:31 ` Roger Heflin
2007-03-29 13:54 ` Chris Osicki
2007-03-29 14:23 ` Wendy Cheng
[not found] <mailman.7028.1175219061.5558.nfs@lists.sourceforge.net>
2007-03-30 6:38 ` Klaus Steinberger
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=20070327150547.GA7161@fieldses.org \
--to=bfields@fieldses.org \
--cc=james-p@moving-picture.com \
--cc=jas@cse.yorku.ca \
--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.