1
2
3		 NFS information
4
5
6
7NFS support is provided by the Sun WebNFS API, finally i was able to get it running in combination
8with my linux box at home.
9
10NFS URLs are a little bit tricky, depending on the type of the NFS version you want to use you have
11to use some custom extensions of the url parser.
12
13This is what the devolopers of the WebNFS API write in their javadoc:
14
15"This is just a dumb URL parser class.
16I wrote it because I got fed up with the JDK URL class calling NFS URL's "invalid" simply because the Handler wasn't installed.
17This URL parser also handles undocumented testing options inserted in the URL in the port field.
18The following sequence of option letters may appear before or after the port number, or alone if the port number is not given.
19vn - NFS version, e.g. "v3" u - Force UDP - normally TCP is preferred t - Force TDP - don't fall back to UDP m - Force Mount protocol.
20Normally public filehandle is preferred Option ordering is not important. Example: nfs://server:123v2um/path Use port 123 with NFS
21v2 over UDP and Mount protocol nfs://server:m/path Use default port, prefer V3/TCP but use Mount protocol."
22
23
24------------ COMPATIBILITY ---------------
25
26
27Server type: NFS2
28Test system: linux universal nfsd 2.2beta47
29
30TESTED: nfs://server:v2m/tmp       - nfs2, tcp with udp fallback, use mount
31SHOULD: nfs://server:v2tm/tmp    - nfs2, force tcp, use mount
32SHOULD: nfs://server:v2um/tmp   - nfs2, force udp, use mount
33
34
35
36Server type: NFS3
37Test system: none
38
39UNKNOWN: nfs://server:v3m/tmp     - nfs3, tcp with udp fallback, use mount
40UNKNOWN: nfs://server:v3tm/tmp    - nfs3, force tcp, use mount
41UNKNOWN: nfs://server:v3um/tmp   - nfs3, force udp, use mount
42
43
44
45Server type: WebNFS
46Test system: none
47
48UNKNOWN: nfs://server:v3/tmp     - may support webnfs
49UNKNOWN: nfs://server/tmp          - may support webnfs
50
51
52
53
54