os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

s/filesystem/file system/g

Browse source 
Approved by:	trhodes (mentor)
This commit is contained in:
Jesus R. Camou 2005-12-03 08:24:48 +00:00
parent e8c851fbad
commit c1f3740d92
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=26508
1 changed files with 31 additions and 31 deletions
Download patch file Download diff file Expand all files Collapse all files

62
en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml
View file

@ -37,7 +37,7 @@
</listitem> </listitem>
<listitem> <listitem>
<para>How to set up a network filesystem.</para> <para>How to set up a network file system.</para>
</listitem> </listitem>
<listitem> <listitem>
@ -566,7 +566,7 @@ server-program-arguments</programlisting>
<title>Network File System (NFS)</title> <title>Network File System (NFS)</title>
<indexterm><primary>NFS</primary></indexterm> <indexterm><primary>NFS</primary></indexterm>
<para>Among the many different filesystems that FreeBSD supports <para>Among the many different file systems that FreeBSD supports
is the Network File System, also known as <acronym role="Network is the Network File System, also known as <acronym role="Network
File System">NFS</acronym>. <acronym role="Network File File System">NFS</acronym>. <acronym role="Network File
System">NFS</acronym> allows a system to share directories and System">NFS</acronym> allows a system to share directories and
@ -712,11 +712,11 @@ mountd_flags="-r"</programlisting>
<programlisting>nfs_client_enable="YES"</programlisting> <programlisting>nfs_client_enable="YES"</programlisting>
<para>The <filename>/etc/exports</filename> file specifies which <para>The <filename>/etc/exports</filename> file specifies which
filesystems <acronym>NFS</acronym> should export (sometimes file systems <acronym>NFS</acronym> should export (sometimes
referred to as <quote>share</quote>). Each line in referred to as <quote>share</quote>). Each line in
<filename>/etc/exports</filename> specifies a filesystem to be <filename>/etc/exports</filename> specifies a file system to be
exported and which machines have access to that filesystem. exported and which machines have access to that file system.
Along with what machines have access to that filesystem, Along with what machines have access to that file system,
access options may also be specified. There are many such access options may also be specified. There are many such
options that can be used in this file but only a few will be options that can be used in this file but only a few will be
mentioned here. You can easily discover other options by mentioned here. You can easily discover other options by
@ -731,15 +731,15 @@ mountd_flags="-r"</programlisting>
</indexterm> </indexterm>
<para>The following examples give an idea of how to export <para>The following examples give an idea of how to export
filesystems, although the settings may be different depending file systems, although the settings may be different depending
on your environment and network configuration. For instance, on your environment and network configuration. For instance,
to export the <filename>/cdrom</filename> directory to three to export the <filename>/cdrom</filename> directory to three
example machines that have the same domain name as the server example machines that have the same domain name as the server
(hence the lack of a domain name for each) or have entries in (hence the lack of a domain name for each) or have entries in
your <filename>/etc/hosts</filename> file. The your <filename>/etc/hosts</filename> file. The
<option>-ro</option> flag makes the exported filesystem <option>-ro</option> flag makes the exported file system
read-only. With this flag, the remote system will not be able read-only. With this flag, the remote system will not be able
to write any changes to the exported filesystem.</para> to write any changes to the exported file system.</para>
<programlisting>/cdrom -ro host1 host2 host3</programlisting> <programlisting>/cdrom -ro host1 host2 host3</programlisting>
@ -757,27 +757,27 @@ mountd_flags="-r"</programlisting>
<programlisting>/home -alldirs 10.0.0.2 10.0.0.3 10.0.0.4</programlisting> <programlisting>/home -alldirs 10.0.0.2 10.0.0.3 10.0.0.4</programlisting>
<para>The following line exports <filename>/a</filename> so that <para>The following line exports <filename>/a</filename> so that
two clients from different domains may access the filesystem. two clients from different domains may access the file system.
The <option>-maproot=root</option> flag allows the The <option>-maproot=root</option> flag allows the
<username>root</username> user on the remote system to write <username>root</username> user on the remote system to write
data on the exported filesystem as <username>root</username>. data on the exported file system as <username>root</username>.
If the <literal>-maproot=root</literal> flag is not specified, If the <literal>-maproot=root</literal> flag is not specified,
then even if a user has <username>root</username> access on then even if a user has <username>root</username> access on
the remote system, he will not be able to modify files on the remote system, he will not be able to modify files on
the exported filesystem.</para> the exported file system.</para>
<programlisting>/a -maproot=root host.example.com box.example.org</programlisting> <programlisting>/a -maproot=root host.example.com box.example.org</programlisting>
<para>In order for a client to access an exported filesystem, <para>In order for a client to access an exported file system,
the client must have permission to do so. Make sure the the client must have permission to do so. Make sure the
client is listed in your <filename>/etc/exports</filename> client is listed in your <filename>/etc/exports</filename>
file.</para> file.</para>
<para>In <filename>/etc/exports</filename>, each line represents <para>In <filename>/etc/exports</filename>, each line represents
the export information for one filesystem to one host. A the export information for one file system to one host. A
remote host can only be specified once per filesystem, and may remote host can only be specified once per file system, and may
only have one default entry. For example, assume that only have one default entry. For example, assume that
<filename>/usr</filename> is a single filesystem. The <filename>/usr</filename> is a single file system. The
following <filename>/etc/exports</filename> would be following <filename>/etc/exports</filename> would be
invalid:</para> invalid:</para>
@ -785,20 +785,20 @@ mountd_flags="-r"</programlisting>
/usr/src client /usr/src client
/usr/ports client</programlisting> /usr/ports client</programlisting>
<para>One filesystem, <filename>/usr</filename>, has two lines <para>One file system, <filename>/usr</filename>, has two lines
specifying exports to the same host, <hostid>client</hostid>. specifying exports to the same host, <hostid>client</hostid>.
The correct format for this situation is:</para> The correct format for this situation is:</para>
<programlisting>/usr/src /usr/ports client</programlisting> <programlisting>/usr/src /usr/ports client</programlisting>
<para>The properties of one filesystem exported to a given host <para>The properties of one file system exported to a given host
must all occur on one line. Lines without a client specified must all occur on one line. Lines without a client specified
are treated as a single host. This limits how you can export are treated as a single host. This limits how you can export
filesystems, but for most people this is not an issue.</para> file systems, but for most people this is not an issue.</para>
<para>The following is an example of a valid export list, where <para>The following is an example of a valid export list, where
<filename>/usr</filename> and <filename>/exports</filename> <filename>/usr</filename> and <filename>/exports</filename>
are local filesystems:</para> are local file systems:</para>
<programlisting># Export src and ports to client01 and client02, but only <programlisting># Export src and ports to client01 and client02, but only
# client01 has root privileges on it # client01 has root privileges on it
@ -836,7 +836,7 @@ mountd_flags="-r"</programlisting>
system. In these examples the system. In these examples the
server's name will be <hostid>server</hostid> and the client's server's name will be <hostid>server</hostid> and the client's
name will be <hostid>client</hostid>. If you only want to name will be <hostid>client</hostid>. If you only want to
temporarily mount a remote filesystem or would rather test the temporarily mount a remote file system or would rather test the
configuration, just execute a command like this as <username>root</username> on the configuration, just execute a command like this as <username>root</username> on the
client:</para> client:</para>
<indexterm> <indexterm>
@ -851,8 +851,8 @@ mountd_flags="-r"</programlisting>
<filename>/mnt</filename> on the client and see all the files <filename>/mnt</filename> on the client and see all the files
that are on the server.</para> that are on the server.</para>
<para>If you want to automatically mount a remote filesystem <para>If you want to automatically mount a remote file system
each time the computer boots, add the filesystem to the each time the computer boots, add the file system to the
<filename>/etc/fstab</filename> file. Here is an example:</para> <filename>/etc/fstab</filename> file. Here is an example:</para>
<programlisting>server:/home /mnt nfs rw 0 0</programlisting> <programlisting>server:/home /mnt nfs rw 0 0</programlisting>
@ -921,8 +921,8 @@ mountd_flags="-r"</programlisting>
<para>&man.amd.8; (the automatic mounter daemon) <para>&man.amd.8; (the automatic mounter daemon)
automatically mounts a automatically mounts a
remote filesystem whenever a file or directory within that remote file system whenever a file or directory within that
filesystem is accessed. Filesystems that are inactive for a file system is accessed. Filesystems that are inactive for a
period of time will also be automatically unmounted by period of time will also be automatically unmounted by
<application>amd</application>. Using <application>amd</application>. Using
<application>amd</application> provides a simple alternative <application>amd</application> provides a simple alternative
@ -935,7 +935,7 @@ mountd_flags="-r"</programlisting>
within one of these directories, <application>amd</application> within one of these directories, <application>amd</application>
looks up the corresponding remote mount and automatically mounts looks up the corresponding remote mount and automatically mounts
it. <filename>/net</filename> is used to mount an exported it. <filename>/net</filename> is used to mount an exported
filesystem from an IP address, while <filename>/host</filename> file system from an IP address, while <filename>/host</filename>
is used to mount an export from a remote hostname.</para> is used to mount an export from a remote hostname.</para>
<para>An access to a file within <para>An access to a file within
@ -1024,7 +1024,7 @@ Exports list on foobar:
<emphasis>server</emphasis>, include the option <emphasis>server</emphasis>, include the option
<option>-w=1024</option> on the mount from the client. If the <option>-w=1024</option> on the mount from the client. If the
FreeBSD system is the <emphasis>client</emphasis>, then mount FreeBSD system is the <emphasis>client</emphasis>, then mount
the NFS filesystem with the option <option>-r=1024</option>. the NFS file system with the option <option>-r=1024</option>.
These options may be specified using the fourth field of the These options may be specified using the fourth field of the
<filename>fstab</filename> entry on the client for automatic <filename>fstab</filename> entry on the client for automatic
mounts, or by using the <option>-o</option> parameter of the mounts, or by using the <option>-o</option> parameter of the
@ -1042,9 +1042,9 @@ Exports list on foobar:
<hostid>freebox</hostid> is the host (interface) name of a FreeBSD <hostid>freebox</hostid> is the host (interface) name of a FreeBSD
system with a lower-performance Ethernet adapter. Also, system with a lower-performance Ethernet adapter. Also,
<filename>/sharedfs</filename> will be the exported NFS <filename>/sharedfs</filename> will be the exported NFS
filesystem (see &man.exports.5;), and file system (see &man.exports.5;), and
<filename>/project</filename> will be the mount point on the <filename>/project</filename> will be the mount point on the
client for the exported filesystem. In all cases, note that client for the exported file system. In all cases, note that
additional options, such as <option>hard</option> or additional options, such as <option>hard</option> or
<option>soft</option> and <option>bg</option> may be desirable in <option>soft</option> and <option>bg</option> may be desirable in
your application.</para> your application.</para>
@ -3101,7 +3101,7 @@ host mailhost {
role="domainname">example.org.</hostid> is more specific than role="domainname">example.org.</hostid> is more specific than
<hostid>org.</hostid>, as <hostid>org.</hostid> is more <hostid>org.</hostid>, as <hostid>org.</hostid> is more
specific than the root zone. The layout of each part of a specific than the root zone. The layout of each part of a
hostname is much like a filesystem: the hostname is much like a file system: the
<filename>/dev</filename> directory falls within the root, and <filename>/dev</filename> directory falls within the root, and
so on.</para> so on.</para>
@ -4736,7 +4736,7 @@ AddModule mod_php5.c
<para>The <filename>smb.conf</filename> file contains runtime <para>The <filename>smb.conf</filename> file contains runtime
configuration information for configuration information for
<application>Samba</application>, such as definitions of the <application>Samba</application>, such as definitions of the
printers and <quote>filesystem shares</quote> that you would printers and <quote>file system shares</quote> that you would
like to share with &windows; clients. The like to share with &windows; clients. The
<application>Samba</application> package includes a web based <application>Samba</application> package includes a web based
tool called <application>swat</application> which provides a tool called <application>swat</application> which provides a