blob: c627b6d2629d43eed0540d2b813a69f96cc0c6a3 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
|
<article lang="&language;" id="nfs">
<title
>nfs</title>
<articleinfo>
<authorgroup>
<author
>&Lauri.Watts; &Lauri.Watts.mail;</author>
<othercredit role="translator"
><firstname
>Malcolm</firstname
><surname
>Hunter</surname
><affiliation
><address
><email
>malcolm.hunter@gmx.co.uk</email
></address
></affiliation
><contrib
>Conversion to British English</contrib
></othercredit
>
</authorgroup>
</articleinfo>
<para
>Sun's <acronym
>NFS</acronym
> protocol provides transparent remote access to shared file systems across networks. The <acronym
>NFS</acronym
> protocol is designed to be machine, operating system, network architecture, and transport protocol independent. This independence is achieved through the use of Remote Procedure Call (<acronym
>RPC</acronym
>) primitives built on top of an eXternal Data Representation (<acronym
>XDR</acronym
>). </para>
<para
>The supporting MOUNT protocol performs the operating system-specific functions that allow clients to attach remote folder trees to a point within the local file system. The mount process also allows the server to grant remote access privileges to a restricted set of clients via export control.</para>
<para
>The Lock Manager provides support for file locking when used in the <acronym
>NFS</acronym
> environment. The Network Lock Manager (<acronym
>NLM</acronym
>) protocol isolates the inherently stateful aspects of file locking into a separate protocol.</para>
<para
>Source: <ulink url="http://www.networksorcery.com/enp/protocol/nfs.htm"
> http://www.networksorcery.com/enp/protocol/nfs.htm</ulink
> </para>
<para
>See the manual: <ulink url="man:/nfs"
>nfs</ulink
>. </para>
</article>
|
