summaryrefslogtreecommitdiffstats
path: root/scripts/gcc-version.sh
diff options
context:
space:
mode:
authorChuck Lever <chuck.lever@oracle.com>2008-06-23 18:36:45 +0200
committerTrond Myklebust <Trond.Myklebust@netapp.com>2008-07-09 18:09:27 +0200
commitd1aa08257312f1439c1ab7c8a18e3856f9530f46 (patch)
tree04ac6b07e5fda3ea93a706fb4074e92b7a95aee3 /scripts/gcc-version.sh
parentNFS: Use common device name parsing logic for NFSv4 and NFSv2/v3 (diff)
downloadlinux-d1aa08257312f1439c1ab7c8a18e3856f9530f46.tar.xz
linux-d1aa08257312f1439c1ab7c8a18e3856f9530f46.zip
NFS: Support raw IPv6 address hostnames during NFS mount operation
Traditionally the mount command has looked for a ":" to separate the server's hostname from the export path in the mounted on device name, like this: mount server:/export /mounted/on/dir The server's hostname is "server" and the export path is "/export". You can also substitute a specific IPv4 network address for the server hostname, like this: mount 192.168.0.55:/export /mounted/on/dir Raw IPv6 addresses present a problem, however, because they look something like this: fe80::200:5aff:fe00:30b Note the use of colons. To get around the presence of colons, copy the Solaris convention used for mounting IPv6 servers by address: wrap a raw IPv6 address with square brackets. Signed-off-by: Chuck Lever <chuck.lever@oracle.com> Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
Diffstat (limited to 'scripts/gcc-version.sh')
0 files changed, 0 insertions, 0 deletions