From c1f3740d92c277cd2323dde26a8ed6c8c50f899a Mon Sep 17 00:00:00 2001 From: "Jesus R. Camou" Date: Sat, 3 Dec 2005 08:24:48 +0000 Subject: [PATCH] s/filesystem/file system/g Approved by: trhodes (mentor) --- .../handbook/network-servers/chapter.sgml | 62 +++++++++---------- 1 file changed, 31 insertions(+), 31 deletions(-) diff --git a/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml b/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml index 04660adb95..b9d302fda8 100644 --- a/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml @@ -37,7 +37,7 @@ - How to set up a network filesystem. + How to set up a network file system. @@ -566,7 +566,7 @@ server-program-arguments Network File System (NFS) NFS - Among the many different filesystems that FreeBSD supports + Among the many different file systems that FreeBSD supports is the Network File System, also known as NFS. NFS allows a system to share directories and @@ -712,11 +712,11 @@ mountd_flags="-r" nfs_client_enable="YES" The /etc/exports file specifies which - filesystems NFS should export (sometimes + file systems NFS should export (sometimes referred to as share). Each line in - /etc/exports specifies a filesystem to be - exported and which machines have access to that filesystem. - Along with what machines have access to that filesystem, + /etc/exports specifies a file system to be + exported and which machines have access to that file system. + Along with what machines have access to that file system, access options may also be specified. There are many such options that can be used in this file but only a few will be mentioned here. You can easily discover other options by @@ -731,15 +731,15 @@ mountd_flags="-r" 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, to export the /cdrom directory to three example machines that have the same domain name as the server (hence the lack of a domain name for each) or have entries in your /etc/hosts file. The - flag makes the exported filesystem + flag makes the exported file system read-only. With this flag, the remote system will not be able - to write any changes to the exported filesystem. + to write any changes to the exported file system. /cdrom -ro host1 host2 host3 @@ -757,27 +757,27 @@ mountd_flags="-r" /home -alldirs 10.0.0.2 10.0.0.3 10.0.0.4 The following line exports /a so that - two clients from different domains may access the filesystem. + two clients from different domains may access the file system. The flag allows the root user on the remote system to write - data on the exported filesystem as root. + data on the exported file system as root. If the -maproot=root flag is not specified, then even if a user has root access on the remote system, he will not be able to modify files on - the exported filesystem. + the exported file system. /a -maproot=root host.example.com box.example.org - In order for a client to access an exported filesystem, + In order for a client to access an exported file system, the client must have permission to do so. Make sure the client is listed in your /etc/exports file. In /etc/exports, each line represents - the export information for one filesystem to one host. A - remote host can only be specified once per filesystem, and may + the export information for one file system to one host. A + remote host can only be specified once per file system, and may only have one default entry. For example, assume that - /usr is a single filesystem. The + /usr is a single file system. The following /etc/exports would be invalid: @@ -785,20 +785,20 @@ mountd_flags="-r" /usr/src client /usr/ports client - One filesystem, /usr, has two lines + One file system, /usr, has two lines specifying exports to the same host, client. The correct format for this situation is: /usr/src /usr/ports client - The properties of one filesystem exported to a given host + The properties of one file system exported to a given host must all occur on one line. Lines without a client specified are treated as a single host. This limits how you can export - filesystems, but for most people this is not an issue. + file systems, but for most people this is not an issue. The following is an example of a valid export list, where /usr and /exports - are local filesystems: + are local file systems: # Export src and ports to client01 and client02, but only # client01 has root privileges on it @@ -836,7 +836,7 @@ mountd_flags="-r" system. In these examples the server's name will be server and the client's name will be client. 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 root on the client: @@ -851,8 +851,8 @@ mountd_flags="-r" /mnt on the client and see all the files that are on the server. - If you want to automatically mount a remote filesystem - each time the computer boots, add the filesystem to the + If you want to automatically mount a remote file system + each time the computer boots, add the file system to the /etc/fstab file. Here is an example: server:/home /mnt nfs rw 0 0 @@ -921,8 +921,8 @@ mountd_flags="-r" &man.amd.8; (the automatic mounter daemon) automatically mounts a - remote filesystem whenever a file or directory within that - filesystem is accessed. Filesystems that are inactive for a + remote file system whenever a file or directory within that + file system is accessed. Filesystems that are inactive for a period of time will also be automatically unmounted by amd. Using amd provides a simple alternative @@ -935,7 +935,7 @@ mountd_flags="-r" within one of these directories, amd looks up the corresponding remote mount and automatically mounts it. /net is used to mount an exported - filesystem from an IP address, while /host + file system from an IP address, while /host is used to mount an export from a remote hostname. An access to a file within @@ -1024,7 +1024,7 @@ Exports list on foobar: server, include the option on the mount from the client. If the FreeBSD system is the client, then mount - the NFS filesystem with the option . + the NFS file system with the option . These options may be specified using the fourth field of the fstab entry on the client for automatic mounts, or by using the parameter of the @@ -1042,9 +1042,9 @@ Exports list on foobar: freebox is the host (interface) name of a FreeBSD system with a lower-performance Ethernet adapter. Also, /sharedfs will be the exported NFS - filesystem (see &man.exports.5;), and + file system (see &man.exports.5;), and /project 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 or and may be desirable in your application. @@ -3101,7 +3101,7 @@ host mailhost { role="domainname">example.org. is more specific than org., as org. is more 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 /dev directory falls within the root, and so on. @@ -4736,7 +4736,7 @@ AddModule mod_php5.c The smb.conf file contains runtime configuration information for Samba, such as definitions of the - printers and filesystem shares that you would + printers and file system shares that you would like to share with &windows; clients. The Samba package includes a web based tool called swat which provides a