Ian Kent <[email protected]> wrote: > But what about mounting with different protocol, tcp vs udp for example. I was referring specifically to the R/O / R/W variants of the same mount. Any flag variation that varies the way the NFS client talks to the NFS server must either result in a new superblock or be ignored. David - 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: recent nfs change causes autofs regression
- From: Trond Myklebust <[email protected]>
- Re: recent nfs change causes autofs regression
- References:
- Re: recent nfs change causes autofs regression
- From: Ian Kent <[email protected]>
- Re: recent nfs change causes autofs regression
- From: Bill Davidsen <[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]>
- Re: recent nfs change causes autofs regression
- From: David Howells <[email protected]>
- Re: recent nfs change causes autofs regression
- Prev by Date: request for information about the "ath5k" licensing
- Next by Date: Re: hda_intel : Patch + Regression in 2.6.18 -> 2.6.22
- Previous by thread: Re: recent nfs change causes autofs regression
- Next by thread: Re: recent nfs change causes autofs regression
- Index(es):
 |