Re: recent nfs change causes autofs regression

Linus Torvalds <[email protected]> wrote:

> In other words, let's assume that the user has /some/nfs/mount mounted 
> over NFS, and wants to re-mount it (or even just a subset of it) somewhere 
> else, the sane thing to do is not to mount it again, but to just do

What about a superset?  What about two intersecting sets?  Bind mounts aren't
quite it for this problem, and in any case your suggestion of:


-
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/

---

• References:
  • Re: recent nfs change causes autofs regression
    • From: Linus Torvalds <[email protected]>
  • recent nfs change causes autofs regression
    • From: "Hua Zhong" <[email protected]>
  • Re: recent nfs change causes autofs regression
    • From: Trond Myklebust <[email protected]>
  • Re: recent nfs change causes autofs regression
    • From: Linus Torvalds <[email protected]>
  • Re: recent nfs change causes autofs regression
    • From: Trond Myklebust <[email protected]>

• Prev by Date: Re: recent nfs change causes autofs regression
• Next by Date: [PATCH] Fix a potential NULL pointer dereference in uli526x_interrupt() in drivers/net/tulip/uli526x.c
• Previous by thread: Re: recent nfs change causes autofs regression
• Next by thread: Re: recent nfs change causes autofs regression
• 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]