75 lines
4.9 KiB
HTML
75 lines
4.9 KiB
HTML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<!DOCTYPE html
|
|
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
|
<html lang="en-us" xml:lang="en-us">
|
|
<head>
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
|
<meta name="security" content="public" />
|
|
<meta name="Robots" content="index,follow" />
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
|
<meta name="DC.Type" content="reference" />
|
|
<meta name="DC.Title" content="Network File System (NFS)" />
|
|
<meta name="abstract" content="The Network File System (NFS) provides the user with access to data and objects that are stored on a remote NFS server." />
|
|
<meta name="description" content="The Network File System (NFS) provides the user with access to data and objects that are stored on a remote NFS server." />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxfsknow.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxnfschar.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxnfsvar.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxnfslink.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxnfsifscom.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxnfsapi.htm" />
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1999, 2006" />
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1999, 2006" />
|
|
<meta name="DC.Format" content="XHTML" />
|
|
<meta name="DC.Identifier" content="rzaaxnfs" />
|
|
<meta name="DC.Language" content="en-us" />
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
|
<!-- US Government Users Restricted Rights -->
|
|
<!-- Use, duplication or disclosure restricted by -->
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
|
<title>Network File System (NFS)</title>
|
|
</head>
|
|
<body id="rzaaxnfs"><a name="rzaaxnfs"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Network File System (NFS)</h1>
|
|
<div><p><span>The Network File System (NFS) provides
|
|
the user with access to data and objects that are stored on a remote NFS server.</span></p>
|
|
<div class="section"><p>An NFS server can export a Network File System that NFS clients
|
|
will then mount dynamically.</p>
|
|
<p> In addition, any file system mounted locally
|
|
through the Network File System will have the features, characteristics, limitations,
|
|
and dependencies of the directory or file system it was mounted from on the
|
|
remote server. Operations on mounted file systems are not performed locally.
|
|
Requests flow through the connection to the server and must obey the requirements
|
|
and restrictions of the type of file system on the server.</p>
|
|
</div>
|
|
<div class="section"><h4 class="sectiontitle">Use NFS file systems through the integrated file system interface</h4><p>The
|
|
NFS is accessible through the integrated file system interface. Be aware of
|
|
these considerations and limitations.</p>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<ul class="ullinks">
|
|
<li class="ulchildlink"><strong><a href="rzaaxnfschar.htm">Characteristics of the Network File System</a></strong><br />
|
|
<span>The characteristics of any file system
|
|
mounted through NFS are dependent on the type of file system
|
|
that was mounted from the server.</span></li>
|
|
<li class="ulchildlink"><strong><a href="rzaaxnfsvar.htm">Variations of servers and clients in the Network File System</a></strong><br />
|
|
There are three major possibilities for client/server connections that can affect how the Network File System (NFS) will function and what its characteristics will be.</li>
|
|
<li class="ulchildlink"><strong><a href="rzaaxnfslink.htm">Links in the Network File System</a></strong><br />
|
|
Generally, multiple hard links to the same object are allowed in the Network File System.</li>
|
|
<li class="ulchildlink"><strong><a href="rzaaxnfsifscom.htm">Integrated file system commands in the Network File System</a></strong><br />
|
|
<span>Many integrated file system commands are
|
|
valid in the Network File System (NFS).</span></li>
|
|
<li class="ulchildlink"><strong><a href="rzaaxnfsapi.htm">Integrated file system APIs in the Network File System</a></strong><br />
|
|
<span>Many integrated file system APIs are valid
|
|
in the Network File System (NFS).</span></li>
|
|
</ul>
|
|
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaaxfsknow.htm" title="A file system provides you the support to access specific segments of storage that are organized as logical units. These logical units on your server are files, directories, libraries, and objects.">Work with file systems</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |