Uh... options is what the user would specify. If the user can't specify it it isn't really policy, but implementation. Either way, some filesystems do have ranges in mount options, too. Chuck Lever <chuck.lever@xxxxxxxxxx> wrote: > >On Jan 7, 2013, at 4:57 PM, H. Peter Anvin <hpa@xxxxxxxxx> wrote: > >> On 12/31/2012 01:53 AM, Chuck Lever wrote: >>> >>> However, NFS version and transport autonegotiation happens in user >space because it is a policy. >>> >> >> Is it? The policy input is the presence of a user override, which >can >> be specified as command-line options. > >Policy choices include whether to allow or prevent the use of >particular transports or NFS versions when negotiating. For example, >client administrators might want to allow the use of either NFSv3 or >v4, but ensure that NFSv2 is not used. > >Mount options traditionally don't specify a range of choices: it's >either "that one" or "any". -- Sent from my mobile phone. Please excuse brevity and lack of formatting. -- To unsubscribe from this list: send the line "unsubscribe autofs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
