From: Al Viro <viro@ftp.linux.org.uk>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Gabriel Barazer <gabriel@oxeva.fr>,
nfsv4@linux-nfs.org, nfs@lists.sourceforge.net,
linux-kernel@vger.kernel.org, jkar8572@users.sourceforge.net
Subject: Re: nfs4 filesystem mounted via the "bind" option reports wrong fstype
Date: Mon, 27 Aug 2007 20:15:07 +0100 [thread overview]
Message-ID: <20070827191507.GI21089@ftp.linux.org.uk> (raw)
In-Reply-To: <20070827184059.GI3118@fieldses.org>
On Mon, Aug 27, 2007 at 02:40:59PM -0400, J. Bruce Fields wrote:
> There's no reason not to just mount server:/exports/data directly at
> /home/data; the bind mounts are just a workaround for the somewhat
> primitive exports facility on the server side.
Bullshit. Bindings are first-class operations on _client_, regardless
of fs types involved.
next prev parent reply other threads:[~2007-08-27 19:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-27 18:32 nfs4 filesystem mounted via the "bind" option reports wrong fstype Gabriel Barazer
2007-08-27 18:40 ` J. Bruce Fields
2007-08-27 19:15 ` Al Viro [this message]
2007-08-27 19:32 ` J. Bruce Fields
2007-08-27 20:08 ` Gabriel Barazer
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=20070827191507.GI21089@ftp.linux.org.uk \
--to=viro@ftp.linux.org.uk \
--cc=bfields@fieldses.org \
--cc=gabriel@oxeva.fr \
--cc=jkar8572@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
--cc=nfsv4@linux-nfs.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