70 lines
4.6 KiB
HTML
70 lines
4.6 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="Variations of servers and clients in the Network File System" />
|
||
|
|
<meta name="abstract" content="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." />
|
||
|
|
<meta name="description" content="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." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxnfs.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxopenfs.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="rzaaxnfsvar" />
|
||
|
|
<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>Variations of servers and clients in the Network File System</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaaxnfsvar"><a name="rzaaxnfsvar"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Variations of servers and clients in the Network File System</h1>
|
||
|
|
<div><p>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.</p>
|
||
|
|
<div class="section"> <p>The three possibilities are:</p>
|
||
|
|
<ol><li>The user mounts a file system from an iSeries™ server on a client.</li>
|
||
|
|
<li>The user mounts a file system from a UNIX<sup>®</sup> server on a client.</li>
|
||
|
|
<li>The user mounts a file system on a client from a
|
||
|
|
server that is neither an iSeries server nor a UNIX server.</li>
|
||
|
|
</ol>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>In the first scenario, the mounted file system will behave on
|
||
|
|
the client similarly to how it behaves on the <span class="keyword">iSeries server</span>.
|
||
|
|
However, both the characteristics of the Network File System and the file
|
||
|
|
system being served need to be taken into account. For example, if you mount
|
||
|
|
the QDLS file system from the server to the client, it will have the characteristics
|
||
|
|
and limitations of the QDLS file system. For example, in the QDLS file system,
|
||
|
|
path name components are limited to 8 characters plus a 3 character extension.
|
||
|
|
However, the mounted file system will also have NFS characteristics and limitations.
|
||
|
|
For example, you cannot use the CHGAUD command to change the auditing value
|
||
|
|
of an NFS object.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>In the second scenario, it is important to realize that any file
|
||
|
|
system mounted from a UNIX server will behave most similar to the iSeries server
|
||
|
|
QOpenSys file system. </p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>In the third scenario, you will need to review the documentation
|
||
|
|
for the file system associated with the server's operating system.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaaxnfs.htm" title="The Network File System (NFS) provides the user with access to data and objects that are stored on a remote NFS server.">Network File System (NFS)</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relref"><strong>Related reference</strong><br />
|
||
|
|
<div><a href="rzaaxopenfs.htm" title="The QOpenSys file system is compatible with open system standards based on UNIX, such as POSIX and X/Open Portability Guide (XPG). Like the "root" (/) file system, this file system takes advantage of the stream file and directory support that is provided by the integrated file system.">Open systems file system (QOpenSys)</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|