Jeff Layton wrote: > +/foo [2001:321:9:e54::/64](rw) 192.168.1.0/24(rw) > '''/pub/private (noaccess) > .fi > .PP > @@ -501,7 +502,8 @@ option in this entry also allows clients with NFS implementations that > don't use a reserved port for NFS. > The sixth line exports a directory read-write to the machine 'server' > as well as the `@trusted' netgroup, and read-only to netgroup `@external', > -all three mounts with the `sync' option enabled. > +all three mounts with the `sync' option enabled. The seventh line exports > +a directory to both an IPv6 and an IPv4 subnet. > ''' The last line denies all NFS clients > '''access to the private directory. > '''.SH CAVEATS Self NAK on this, as brackets don't seem to be required after all. I'll respin and resend once I get that straightened out. Are the brackets allowed, and if so, must the mask be inside the brackets or can it be outside? And should this be documented? This came up on another server implementation recently and I couldn't find any spec that describes the brackets. It would be nice to achieve some kind of standardization. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
