105 lines
7.5 KiB
HTML
105 lines
7.5 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=""root" (/) file system" />
|
||
|
<meta name="abstract" content="The root (/) file system takes full advantage of the stream file support and hierarchical directory structure of the integrated file system. It has the characteristics of the DOS and OS/2 file systems." />
|
||
|
<meta name="description" content="The root (/) file system takes full advantage of the stream file support and hierarchical directory structure of the integrated file system. It has the characteristics of the DOS and OS/2 file systems." />
|
||
|
<meta name="DC.subject" content="file system, root (/), characteristics and limitations, root (/) file system, characteristics and limitations" />
|
||
|
<meta name="keywords" content="file system, root (/), characteristics and limitations, root (/) file system, characteristics and limitations" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzaaxfsknow.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzaaxrootcase.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzaaxrootpath.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzaaxrootlinks.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzaaxrootifscom.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzaaxrootapi.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzaaxrootjournal.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzaaxudptcp.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="rzaaxrootfs" />
|
||
|
<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>"root" (/) file system</title>
|
||
|
</head>
|
||
|
<body id="rzaaxrootfs"><a name="rzaaxrootfs"><!-- --></a>
|
||
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
<h1 class="topictitle1">"root" (/) file system</h1>
|
||
|
<div><p>The <span class="q">"root"</span> (/) file system takes full advantage of the stream
|
||
|
file support and hierarchical directory structure of the integrated file system.
|
||
|
It has the characteristics of the DOS and OS/2<sup>®</sup> file systems.</p>
|
||
|
<div class="section"><p>In addition, it:</p>
|
||
|
</div>
|
||
|
<div class="section"> <ul><li>Is optimized for stream file input and output.</li>
|
||
|
<li>Supports multiple hard links and symbolic links.</li>
|
||
|
<li>Supports local sockets.</li>
|
||
|
<li>Supports threadsafe APIs.</li>
|
||
|
<li>Supports *FIFO objects.</li>
|
||
|
<li>Supports the <samp class="codeph">/dev/null</samp> and <samp class="codeph">/dev/zero</samp> *CHRSF
|
||
|
objects as well as other *CHRSF objects.</li>
|
||
|
<li>Supports the journaling of object changes.</li>
|
||
|
<li>Supports the scanning of objects using the integrated file system scan-related
|
||
|
exit points.</li>
|
||
|
</ul>
|
||
|
</div>
|
||
|
<div class="section"><p>The <span class="q">"root"</span> (/) file system has support for the character
|
||
|
special files (*CHRSF) called <samp class="codeph">/dev/null</samp> and <samp class="codeph">/dev/zero</samp>.
|
||
|
Character special files are associated with a device or resource of a computer
|
||
|
system. They have path names that appear in directories and have the same
|
||
|
access protection as regular files. The <samp class="codeph">/dev/null</samp> or <samp class="codeph">/dev/zero</samp> character
|
||
|
special files are always empty, and any data written to <samp class="codeph">/dev/null</samp> or <samp class="codeph">/dev/zero</samp> is
|
||
|
discarded. The files <samp class="codeph">/dev/null</samp> and <samp class="codeph">/dev/zero</samp> have
|
||
|
an object type of *CHRSF and can be used like regular files, except that no
|
||
|
data is ever read in the<samp class="codeph">/dev/null</samp> file, and the <samp class="codeph">/dev/zero</samp> file
|
||
|
always returns successfully with the data cleared to zeros.</p>
|
||
|
</div>
|
||
|
<div class="section"><h4 class="sectiontitle">Use the "root" (/) file system</h4><p>The <span class="q">"root"</span> (/)
|
||
|
file system can be accessed through the integrated file system interface using
|
||
|
either the <span class="keyword">i5/OS™</span> file server
|
||
|
or the integrated file system commands, user displays, and APIs.</p>
|
||
|
</div>
|
||
|
</div>
|
||
|
<div>
|
||
|
<ul class="ullinks">
|
||
|
<li class="ulchildlink"><strong><a href="rzaaxrootcase.htm">Case-sensitivity in the "root" (/) file system</a></strong><br />
|
||
|
The file system preserves the same uppercase and lowercase form in which object names are entered, but no distinction is made between uppercase and lowercase when the server searches for names.</li>
|
||
|
<li class="ulchildlink"><strong><a href="rzaaxrootpath.htm">Path names in the "root" (/) file system</a></strong><br />
|
||
|
Path names have specific form in the <span class="q">"root"</span> (/) file system.</li>
|
||
|
<li class="ulchildlink"><strong><a href="rzaaxrootlinks.htm">Links in the "root" (/) file system</a></strong><br />
|
||
|
Multiple hard links to the same object are allowed in the <span class="q">"root"</span> (/)
|
||
|
file system. Symbolic links are fully supported. </li>
|
||
|
<li class="ulchildlink"><strong><a href="rzaaxrootifscom.htm">Use integrated file system commands in the "root" (/) file system</a></strong><br />
|
||
|
All of the commands listed in Access using CL commands topic and
|
||
|
the displays described in Access using menus and displays topic can operate
|
||
|
on the <span class="q">"root"</span> (/) file system. However, it might not be safe to use
|
||
|
these commands in a multithread-capable process.</li>
|
||
|
<li class="ulchildlink"><strong><a href="rzaaxrootapi.htm">Use integrated file system APIs in the "root" (/) file system</a></strong><br />
|
||
|
All of the APIs listed in Perform operations using APIs topic can
|
||
|
operate on the <span class="q">"root"</span> (/) file system.</li>
|
||
|
<li class="ulchildlink"><strong><a href="rzaaxrootjournal.htm">Journal object changes in the "root" (/) file system</a></strong><br />
|
||
|
Objects in the <span class="q">"root"</span> (/) file system can be journaled. This
|
||
|
function enables you to recover the changes to an object that have occurred
|
||
|
since the object was last saved. </li>
|
||
|
<li class="ulchildlink"><strong><a href="rzaaxudptcp.htm">UDP and TCP devices in the "root" (/) file system</a></strong><br />
|
||
|
The <span class="q">"root"</span> (/) file system under the directory of /dev/xti
|
||
|
will now hold two device drivers named udp and tcp.</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>
|