On Wed, Jan 9, 2013 at 12:14 PM, Steve French <smfrench@xxxxxxxxx> wrote: >> >> > I don't care much either way. The reason behind removing it, IIRC, >> >> > was that it was an undocumented feature that lead to an ambiguous >> >> > parsing situation when you had NFS syntax with an IPv6 address as the >> >> > server portion of the string (ie >> >> > dead:beef::1:/shareNameWithColon:/prepath). It was easier to remove >> >> > the undocumented feature than to support it for this use case. >> >> > >> >> > How does NFS syntax make things easier for SMB3? >> >> >> >> UNC names may be unfamiliar for some NFS users. Smb3 has many >> >> performance advantages and other features that may eventually be of >> >> strong interest to some Linux NFS users >> >> Sorry to resurrect a dead thread, but how does the nfs-utils mount >> helper deal with parsing IPv6 addresses when using NFS syntax? Does >> it just search for ":/" and assume that's the beginning of the share >> name (which 99.99999% of the time it will be)? >> -- >> Peace and Blessings, >> -Scott. > > > > I thought that NFS required that the IPv6 address be enclosed in brackets? > I haven't tested this to see how mount.cifs would handle this (if it is > broken presumably we should fix it) > > https://fedoraproject.org/wiki/QA:Testcase_NFS_IPv6 mount.cifs doesn't have this syntax in the parser. Right now the way to do it is to use the "ip=" flag and just put in your IPv6 address. Is the bracket syntax a standard of sorts or at least a de facto standard across mount helpers? -- Peace and Blessings, -Scott. -- To unsubscribe from this list: send the line "unsubscribe linux-cifs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
