><TD
>Utility to report process status</TD
></TR
><TR
><TD
><B
CLASS="COMMAND"
>pwd</B
></TD
><TD
>Utility to print name of current working directory</TD
></TR
><TR
><TD
><B
CLASS="COMMAND"
>rm</B
></TD
><TD
>Utility to remove files or directories</TD
></TR
><TR
><TD
><B
CLASS="COMMAND"
>rmdir</B
></TD
><TD
>Utility to remove empty directories</TD
></TR
><TR
><TD
><B
CLASS="COMMAND"
>sed</B
></TD
><TD
>The `sed' stream editor</TD
></TR
><TR
><TD
><B
CLASS="COMMAND"
>sh</B
></TD
><TD
>The Bourne command shell</TD
></TR
><TR
><TD
><B
CLASS="COMMAND"
>stty</B
></TD
><TD
>Utility to change and print terminal line settings</TD
></TR
><TR
><TD
><B
CLASS="COMMAND"
>su</B
></TD
><TD
>Utility to change user ID</TD
></TR
><TR
><TD
><B
CLASS="COMMAND"
>sync</B
></TD
><TD
>Utility to flush filesystem buffers</TD
></TR
><TR
><TD
><B
CLASS="COMMAND"
>true</B
></TD
><TD
>Utility to do nothing, successfully</TD
></TR
><TR
><TD
><B
CLASS="COMMAND"
>umount</B
></TD
><TD
>Utility to unmount file systems</TD
></TR
><TR
><TD
><B
CLASS="COMMAND"
>uname</B
></TD
><TD
>Utility to print system information</TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
><P
>If <B
CLASS="COMMAND"
>/bin/sh</B
> is not a true Bourne shell, it
must be a hard or symbolic link to the real shell command.</P
><P
>The <B
CLASS="COMMAND"
>[</B
> and <B
CLASS="COMMAND"
>test</B
>
commands must be placed together in either <TT
CLASS="FILENAME"
>/bin</TT
>
or <TT
CLASS="FILENAME"
>/usr/bin</TT
>.</P
><DIV
CLASS="TIP"
><P
></P
><TABLE
CLASS="TIP"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="tip.gif"
HSPACE="5"
ALT="Tip"></TD
><TH
ALIGN="LEFT"
VALIGN="CENTER"
><B
>Rationale</B
></TH
></TR
><TR
><TD
>&nbsp;</TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>For example bash behaves differently when called as
<B
CLASS="COMMAND"
>sh</B
> or <B
CLASS="COMMAND"
>bash</B
>. The use of a
symbolic link also allows users to easily see that
<B
CLASS="COMMAND"
>/bin/sh</B
> is not a true Bourne shell.</P
><P
>The requirement for the <B
CLASS="COMMAND"
>[</B
> and
<B
CLASS="COMMAND"
>test</B
> commands to be included as binaries (even if
implemented internally by the shell) is shared with the POSIX.2
standard.&#13;</P
></TD
></TR
></TABLE
></DIV
></DIV
><DIV
CLASS="SECTION"
><HR><H3
CLASS="SECTION"
><A
NAME="SPECIFICOPTIONS2"
>Specific Options</A
></H3
><P
>The following programs, or symbolic links to programs, must be
in <TT
CLASS="FILENAME"
>/bin</TT
> if the corresponding subsystem is
installed:</P
><DIV
CLASS="INFORMALTABLE"
><P
></P
><A
NAME="AEN431"
></A
><TABLE
BORDER="0"
FRAME="void"
CLASS="CALSTABLE"
><COL><COL><THEAD
><TR
><TH
>Command</TH
><TH
>Description</TH
></TR
></THEAD
><TBODY
><TR
><TD
><B
CLASS="COMMAND"
>csh</B
></TD
><TD
>The C shell (optional)</TD
></TR
><TR
><TD
><B
CLASS="COMMAND"
>ed</B
></TD
><TD
>The `ed' editor (optional)</TD
></TR
><TR
><TD
><B
CLASS="COMMAND"
>tar</B
></TD
><TD
>The tar archiving utility (optional)</TD
></TR
><TR
><TD
><B
CLASS="COMMAND"
>cpio</B
></TD
><TD
>The cpio archiving utility (optional)</TD
></TR
><TR
><TD
><B
CLASS="COMMAND"
>gzip</B
></TD
><TD
>The GNU compression utility (optional)</TD
></TR
><TR
><TD
><B
CLASS="COMMAND"
>gunzip</B
></TD
><TD
>The GNU uncompression utility (optional)</TD
></TR
><TR
><TD
><B
CLASS="COMMAND"
>zcat</B
></TD
><TD
>The GNU uncompression utility (optional)</TD
></TR
><TR
><TD
><B
CLASS="COMMAND"
>netstat</B
></TD
><TD
>The network statistics utility (optional)</TD
></TR
><TR
><TD
><B
CLASS="COMMAND"
>ping</B
></TD
><TD
>The ICMP network test utility (optional)</TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
><P
>If the <B
CLASS="COMMAND"
>gunzip</B
> and <B
CLASS="COMMAND"
>zcat</B
>
programs exist, they must be symbolic or hard links to
gzip. <B
CLASS="COMMAND"
>/bin/csh</B
> may be a symbolic link to
<B
CLASS="COMMAND"
>/bin/tcsh</B
> or
<B
CLASS="COMMAND"
>/usr/bin/tcsh</B
>.</P
><DIV
CLASS="TIP"
><P
></P
><TABLE
CLASS="TIP"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="tip.gif"
HSPACE="5"
ALT="Tip"></TD
><TH
ALIGN="LEFT"
VALIGN="CENTER"
><B
>Rationale</B
></TH
></TR
><TR
><TD
>&nbsp;</TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>The tar, gzip and cpio commands have been added to make restoration of a
system possible (provided that <TT
CLASS="FILENAME"
>/</TT
> is intact).</P
><P
>Conversely, if no restoration from the root partition is ever
expected, then these binaries might be omitted (e.g., a ROM chip root,
mounting <TT
CLASS="FILENAME"
>/usr</TT
> through NFS). If restoration of a
system is planned through the network, then <B
CLASS="COMMAND"
>ftp</B
>
or <B
CLASS="COMMAND"
>tftp</B
> (along with everything necessary to get
an ftp connection) must be available on the root partition.&#13;</P
></TD
></TR
></TABLE
></DIV
></DIV
></DIV
><DIV
CLASS="SECTION"
><HR><H2
CLASS="SECTION"
><A
NAME="BOOTSTATICFILESOFTHEBOOTLOADER"
>/boot : Static files of the boot loader</A
></H2
><DIV
CLASS="SECTION"
><H3
CLASS="SECTION"
><A
NAME="PURPOSE4"
>Purpose</A
></H3
><P
>This directory contains everything required for the boot process
except configuration files not needed at boot time and the map
installer. Thus /boot stores data that is used before the kernel
begins executing user-mode programs. This may include saved master
boot sectors and sector map files.

<A
NAME="AEN493"
HREF="#FTN.AEN493"
><SPAN
CLASS="footnote"
>[2]</SPAN
></A
>&#13;</P
></DIV
><DIV
CLASS="SECTION"
><HR><H3
CLASS="SECTION"
><A
NAME="SPECIFICOPTIONS3"
>Specific Options</A
></H3
><P
>The operating system kernel must be located in either
<TT
CLASS="FILENAME"
>/</TT
> or <TT
CLASS="FILENAME"
>/boot</TT
>.

<A
NAME="AEN507"
HREF="#FTN.AEN507"
><SPAN
CLASS="footnote"
>[3]</SPAN
></A
></P
></DIV
></DIV
><DIV
CLASS="SECTION"
><HR><H2
CLASS="SECTION"
><A
NAME="DEVDEVICEFILES"
>/dev : Device files</A
></H2
><DIV
CLASS="SECTION"
><H3
CLASS="SECTION"
><A
NAME="PURPOSE5"
>Purpose</A
></H3
><P
>The <TT
CLASS="FILENAME"
>/dev</TT
> directory is the location of
special or device files.</P
></DIV
><DIV
CLASS="SECTION"
><HR><H3
CLASS="SECTION"
><A
NAME="SPECIFICOPTIONS4"
>Specific Options</A
></H3
><P
>If it is possible that devices in <TT

Prev | Next
Pg.: 1 2 3 4 5 6 7 8 9 10 11 ... 30


Back to home | File page

Subscribe | Register | Login | N