Re: nfs4 filesystem mounted via the "bind" option reports wrong fstype

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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: nfs4 filesystem mounted via the "bind" option reports wrong fstype
    • From: "J. Bruce Fields" <[email protected]>

• References:
  • nfs4 filesystem mounted via the "bind" option reports wrong fstype
    • From: Gabriel Barazer <[email protected]>
  • Re: nfs4 filesystem mounted via the "bind" option reports wrong fstype
    • From: "J. Bruce Fields" <[email protected]>

• Prev by Date: Re: Who wants to maintain KR list for stable releases? (was Re: nmi_watchdog=2 regression in 2.6.21)
• Next by Date: Re: [patch] sched: fix broken smt/mc optimizations with CFS
• Previous by thread: Re: nfs4 filesystem mounted via the "bind" option reports wrong fstype
• Next by thread: Re: nfs4 filesystem mounted via the "bind" option reports wrong fstype
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]