On Fri, Dec 6, 2024 at 10:55 PM Roland Mainz <roland.mainz@xxxxxxxxxxx> wrote: > > Hi! > > ---- > > Below (also attached as > "0001-mount.nfs4-Add-support-for-nfs-URLs_v2.patch" and available at > https://nrubsig.kpaste.net/e8c5cb) is version 2 of the patch which > adds support for nfs://-URLs in mount.nfs4, as alternative to the > traditional hostname:/path+-o port=<tcp-port> notation. > > * Main advantages are: > - Single-line notation with the familiar URL syntax, which includes > hostname, path *AND* TCP port number (last one is a common generator > of *PAIN* with ISPs) in ONE string > - Support for non-ASCII mount points, e.g. paths with CJKV (Chinese, > Japanese, ...) characters, which is typically a big problem if you try > to transfer such mount point information across email/chat/clipboard > etc., which tends to mangle such characters to death (e.g. > transliteration, adding of ZWSP or just '?'). - Server mkdir '/nfsroot11/アーカイブ' - Convert path at https://www.urlencoder.org/ '/nfsroot11/アーカイブ' ----> '/nfsroot11/%E3%82%A2%E3%83%BC%E3%82%AB%E3%82%A4%E3%83%96' - Client mount.nfs -o rw 'nfs://133.1.138.101//nfsroot11//%E3%82%A2%E3%83%BC%E3%82%AB%E3%82%A4%E3%83%96' /mnt Works - (◕‿◕) - 素晴らしい @Roland Mainz Thank you!! > - URL parameters are supported, providing support for future extensions > * Notes: > - Similar support for nfs://-URLs exists in other NFSv4.* > implementations, including Illumos, Windows ms-nfs41-client, > sahlberg/libnfs, ... > - This is NOT about WebNFS, this is only to use an URL representation > to make the life of admins a LOT easier > - Only absolute paths are supported > - This feature will not be provided for NFSv3 NFSv3 does not do Unicode, so this is not going to work anyway -- Internationalization&localization dev / 大阪大学 Takeshi Nishimura <takeshi.nishimura.linux@xxxxxxxxx>
