2
<!DOCTYPE article PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN"
4
<!ENTITY % addindex "IGNORE">
5
<!ENTITY % British-English "INCLUDE"
6
> <!-- change language only here -->
9
<article lang="&language;" id="nfs">
15
>&Lauri.Watts; &Lauri.Watts.mail;</author>
16
<othercredit role="translator"
24
>malcolm.hunter@gmx.co.uk</email
28
>Conversion to British English</contrib
36
> protocol provides transparent remote access to shared file systems across networks. The <acronym
38
> 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
40
>) primitives built on top of an eXternal Data Representation (<acronym
45
>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>
48
>The Lock Manager provides support for file locking when used in the <acronym
50
> environment. The Network Lock Manager (<acronym
52
>) protocol isolates the inherently stateful aspects of file locking into a separate protocol.</para>
55
>Source: <ulink url="http://www.networksorcery.com/enp/protocol/nfs.htm"
56
> http://www.networksorcery.com/enp/protocol/nfs.htm</ulink
60
>See the manual: <ulink url="man:/nfs"