From owner-svn-doc-projects@FreeBSD.ORG Thu May 9 20:56:49 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 535711BC; Thu, 9 May 2013 20:56:49 +0000 (UTC) (envelope-from dru@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 43D9015D; Thu, 9 May 2013 20:56:49 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r49KunSo036667; Thu, 9 May 2013 20:56:49 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r49KuncN036666; Thu, 9 May 2013 20:56:49 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201305092056.r49KuncN036666@svn.freebsd.org> From: Dru Lavigne Date: Thu, 9 May 2013 20:56:49 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41584 - projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/basics X-SVN-Group: doc-projects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 May 2013 20:56:49 -0000 Author: dru Date: Thu May 9 20:56:48 2013 New Revision: 41584 URL: http://svnweb.freebsd.org/changeset/doc/41584 Log: White space fix only. Translators can ignore. Approved by: bcr (mentor) Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/basics/chapter.xml Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/basics/chapter.xml ============================================================================== --- projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/basics/chapter.xml Thu May 9 20:54:51 2013 (r41583) +++ projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/basics/chapter.xml Thu May 9 20:56:48 2013 (r41584) @@ -87,8 +87,8 @@ &os; can be used in various ways. One of them is typing commands to a text terminal. A lot of the flexibility and power - of a &unix; operating system is readily available - when using &os; this way. This section describes what + of a &unix; operating system is readily available when using + &os; this way. This section describes what terminals and consoles are, and how to use them in &os;. @@ -146,14 +146,14 @@ login: Type the username that was configured during system installation, as described in , and - press Enter. Then enter the password - associated with the username and press Enter. - The password is not echoed for security + linkend="bsdinstall-addusers"/>, and press + Enter. Then enter the password associated + with the username and press Enter. The + password is not echoed for security reasons. - Once the correct password is input, the message of - the day (MOTD) will be displayed followed + Once the correct password is input, the message of the + day (MOTD) will be displayed followed by a command prompt (a #, $, or % character). You are now logged into the &os; console and ready to try the @@ -229,10 +229,10 @@ ttyv8 "/usr/X11R6/bin/xdm -nodaemon" Single User Mode Console A detailed description of single user mode - can be found in . - There is only one console when &os; is in single user mode as - no other virtual consoles are available in this mode. The - settings for single user mode are found in this section of + can be found in . There is + only one console when &os; is in single user mode as no other + virtual consoles are available in this mode. The settings + for single user mode are found in this section of /etc/ttys: # name getty type status comments @@ -250,12 +250,11 @@ console none without prompting for a password. Be careful when changing this setting to - insecure. If - the root password is forgotten, booting - into - single user mode is still possible, but may be difficult for - someone who is not comfortable with the &os; booting - process. + insecure. If the + root password is forgotten, booting + into single user mode is still possible, but may be + difficult for someone who is not comfortable with the &os; + booting process. @@ -419,10 +418,10 @@ total 530 write, and execute permissions. The executable bit for a directory has a slightly different meaning than that of files. When a directory is marked executable, it means it is possible - to change into that directory using - &man.cd.1;. This also means that it is - possible to access the files within that directory, subject to - the permissions on the files themselves. + to change into that directory using &man.cd.1;. This also + means that it is possible to access the files within that + directory, subject to the permissions on the files + themselves. In order to perform a directory listing, the read permission must be set on the directory. In order to delete a file that @@ -583,10 +582,9 @@ total 530 In addition to file permissions, &os; supports the use of file flags. These flags add an additional - level of security and control over files, but not - directories. With file flags, even - root can be prevented from removing or - altering files. + level of security and control over files, but not directories. + With file flags, even root can be + prevented from removing or altering files. File flags are modified using &man.chflags.1;. For example, to enable the system undeletable flag on the file @@ -675,8 +673,8 @@ total 530 To view this in real time, open two terminals. On - one, type passwd as a normal - user. While it waits for a new password, check the process + one, type passwd as a normal user. + While it waits for a new password, check the process table and look at the user information for &man.passwd.1;: @@ -692,9 +690,9 @@ Old Password: trhodes 5232 0.0 0.2 3420 1608 0 R+ 2:10AM 0:00.00 grep passwd root 5211 0.0 0.2 3620 1724 2 I+ 2:09AM 0:00.01 passwd - Although &man.passwd.1; is run - as a normal user, it is using the effective - UID of root. + Although &man.passwd.1; is run as a normal user, it is + using the effective UID of + root. The setgid permission performs the same function as the setuid permission; @@ -704,8 +702,7 @@ root 5211 0.0 0.2 3620 1724 2 user who started the process. To set the setgid permission on a - file, provide &man.chmod.1; with a leading two - (2): + file, provide &man.chmod.1; with a leading two (2): &prompt.root; chmod 2755 sgidexample.sh @@ -960,26 +957,26 @@ root 5211 0.0 0.2 3620 1724 2 /usr/local/ Local executables and libraries. Also used as - the default destination for the &os; ports - framework. Within - /usr/local, the + the default destination for the &os; ports framework. + Within /usr/local, the general layout sketched out by &man.hier.7; for /usr should be used. Exceptions are the man directory, which is - directly under - /usr/local - rather than under - /usr/local/share, - and the ports documentation is in - share/doc/port. + directly under /usr/local + rather than under /usr/local/share, + and the ports documentation is in share/doc/port. /usr/obj/ Architecture-specific target tree produced by - building the - /usr/src + building the /usr/src tree. @@ -1044,8 +1041,8 @@ root 5211 0.0 0.2 3620 1724 2 /var/tmp/ Temporary files which are usually preserved - across a system reboot, unless - /var is a + across a system reboot, unless /var is a memory-based file system. @@ -1071,42 +1068,40 @@ root 5211 0.0 0.2 3620 1724 2 Files are stored in directories. A directory may contain no files, or it may contain many hundreds of files. A directory - can also contain other directories, allowing a - hierarchy of directories within one another in order to organize + can also contain other directories, allowing a hierarchy of + directories within one another in order to organize data. Files and directories are referenced by giving the file or directory name, followed by a forward slash, /, followed by any other directory names that - are necessary. For example, if the directory - foo contains a directory + are necessary. For example, if the directory foo contains a directory bar which contains the file readme.txt, the full name, or path, to the file is foo/bar/readme.txt. Note that this is - different from &windows; which uses - \ to separate file and directory - names. &os; does not use drive letters, or other drive names in - the path. For example, one would not type - c:/foo/bar/readme.txt on &os;. + different from &windows; which uses \ to + separate file and directory names. &os; does not use drive + letters, or other drive names in the path. For example, one + would not type c:/foo/bar/readme.txt on + &os;. Directories and files are stored in a file system. Each file system contains exactly one directory at the very top level, called the root directory for that - file system. This root directory can contain other - directories. One file system is designated the - root file system or /. - Every other file system is mounted under - the root file system. No matter how many disks are on the - &os; system, every directory appears to be part of the same - disk. - - Consider three file systems, called - A, B, and - C. Each file system has one root directory, - which contains two other directories, called - A1, A2 (and likewise - B1, B2 and + file system. This root directory can contain other directories. + One file system is designated the root file + system or /. Every other file + system is mounted under the root file + system. No matter how many disks are on the &os; system, every + directory appears to be part of the same disk. + + Consider three file systems, called A, + B, and C. Each file + system has one root directory, which contains two other + directories, called A1, A2 + (and likewise B1, B2 and C1, C2). Call A the root file system. If @@ -1130,11 +1125,11 @@ root 5211 0.0 0.2 3620 1724 2 A file system must be mounted on to a directory in another - file system. When mounting file system - B on to the directory A1, - the root directory of B replaces - A1, and the directories in - B appear accordingly: + file system. When mounting file system B + on to the directory A1, the root directory + of B replaces A1, and + the directories in B appear + accordingly: @@ -1156,10 +1151,9 @@ root 5211 0.0 0.2 3620 1724 2 Any files that are in the B1 or B2 directories can be reached with the path - /A1/B1 or - /A1/B2 as - necessary. Any files that were in - /A1 have + /A1/B1 or /A1/B2 as necessary. Any files + that were in /A1 have been temporarily hidden. They will reappear if B is unmounted from A. @@ -1187,9 +1181,8 @@ root 5211 0.0 0.2 3620 1724 2 and the paths would be - /A2/B1 and - /A2/B2 - respectively. + /A2/B1 and /A2/B2 respectively. File systems can be mounted on top of one another. Continuing the last example, the C file @@ -1264,9 +1257,9 @@ root 5211 0.0 0.2 3620 1724 2 mount options. For example, the root file system can be mounted read-only, making it impossible for users to inadvertently delete or edit a critical file. - Separating user-writable file systems, such as - /home, from other - file systems allows them to be mounted + Separating user-writable file systems, such as /home, from other file + systems allows them to be mounted nosuid. This option prevents the suid/guid bits on executables stored on the file system from taking effect, @@ -1283,10 +1276,9 @@ root 5211 0.0 0.2 3620 1724 2 - &os;'s file systems are robust if - power is lost. However, a power loss at a critical point - could - still damage the structure of the file system. By splitting + &os;'s file systems are robust if power is lost. + However, a power loss at a critical point could still + damage the structure of the file system. By splitting data over multiple file systems it is more likely that the system will still come up, making it easier to restore from backup as necessary. @@ -1379,10 +1371,10 @@ root 5211 0.0 0.2 3620 1724 2 Each partition-that-contains-a-file-system is stored in what - &os; calls a slice. Slice is - &os;'s term for what the common call partitions, and again, - this is because of &os;'s &unix; background. Slices are - numbered, starting at 1, through to 4. + &os; calls a slice. Slice is &os;'s + term for what the common call partitions, and again, this is + because of &os;'s &unix; background. Slices are numbered, + starting at 1, through to 4. slices partitions @@ -1403,17 +1395,18 @@ root 5211 0.0 0.2 3620 1724 2 partitions, which are represented as letters from a to h. This letter is appended to the device name, so - da0a is the a partition on - the first da drive, which is dangerously - dedicated. ad1s3e is - the fifth partition in the third slice of the second IDE disk - drive. + da0a is the + a partition on the first + da drive, which is dangerously + dedicated. ad1s3e + is the fifth partition in the third slice of the second IDE + disk drive. Finally, each disk on the system is identified. A disk name starts with a code that indicates the type of disk, and then a number, indicating which disk it is. Unlike slices, disk - numbering starts at 0. Common codes are - listed in . + numbering starts at 0. Common codes are listed in . When referring to a partition, include the disk name, s, the slice number, and then the partition @@ -1567,12 +1560,11 @@ root 5211 0.0 0.2 3620 1724 2 The file system is best visualized as a tree, rooted, as it were, at /. - /dev, - /usr, and the - other directories in the root directory are branches, which may - have their own branches, such as - /usr/local, and so - on. + /dev, /usr, and the other directories + in the root directory are branches, which may have their own + branches, such as /usr/local, and so on. root file system There are various reasons to house some of these @@ -1582,15 +1574,13 @@ root 5211 0.0 0.2 3620 1724 2 spool/, and various types of temporary files, and as such, may get filled up. Filling up the root file system is not a good idea, so splitting /var from - / is often - favorable. + class="directory">/var from / is often favorable. Another common reason to contain certain directory trees on other file systems is if they are to be housed on separate physical disks, or are separate virtual disks, such as Network - File System mounts, described in - , + File System mounts, described in , or CDROM drives. @@ -1641,8 +1631,8 @@ root 5211 0.0 0.2 3620 1724 2 options - Either for read-write - file systems, or for read-only file + Either for read-write file + systems, or for read-only file systems, followed by any other options that may be needed. A common option is for file systems not normally mounted during the boot @@ -1845,28 +1835,27 @@ root 5211 0.0 0.2 3620 1724 2 processes that are run by &os;. Each process is uniquely identified by a number called a - process ID - (PID). Similar to files, each process - has one owner and group, and the owner and group permissions are - used to determine which files and devices the process can open. - Most processes also have a parent process that started them. - For example, the shell is a process, and any command started in - the shell is a process which has the shell as its parent - process. The exception is a special process called - &man.init.8; which is always the first process to start at boot - time and which always has a PID of 1. + process ID (PID). + Similar to files, each process has one owner and group, and + the owner and group permissions are used to determine which + files and devices the process can open. Most processes also + have a parent process that started them. For example, the + shell is a process, and any command started in the shell is a + process which has the shell as its parent process. The + exception is a special process called &man.init.8; which is + always the first process to start at boot time and which always + has a PID of 1. To see the processes on the system, use &man.ps.1; and &man.top.1;. To display a static list of the currently running processes, their PIDs, how much memory they - are using, and the - command they were started with, use &man.ps.1;. To - display all the running processes and update the display every - few seconds in order to interactively see what the computer - is doing, use &man.top.1;. + are using, and the command they were started with, use + &man.ps.1;. To display all the running processes and update + the display every few seconds in order to interactively see + what the computer is doing, use &man.top.1;. - By default, &man.ps.1; only shows the commands - that are running and owned by the user. For example: + By default, &man.ps.1; only shows the commands that are + running and owned by the user. For example: &prompt.user; ps PID TT STAT TIME COMMAND @@ -1888,16 +1877,15 @@ root 5211 0.0 0.2 3620 1724 2 The output from &man.ps.1; is organized into a number of columns. The PID column displays the process ID. PIDs are assigned starting at 1, go up - to 99999, then wrap - around back to the beginning. However, a PID - is not reassigned - if it is already in use. The TT column shows - the tty the program is running on and STAT - shows the program's state. TIME is the - amount of time the program has been running on the CPU. This is - usually not the elapsed time since the program was started, as - most programs spend a lot of time waiting for things to happen - before they need to spend time on the CPU. Finally, + to 99999, then wrap around back to the beginning. However, a + PID is not reassigned if it is already in + use. The TT column shows the tty the program + is running on and STAT shows the program's + state. TIME is the amount of time the + program has been running on the CPU. This is usually not the + elapsed time since the program was started, as most programs + spend a lot of time waiting for things to happen before they + need to spend time on the CPU. Finally, COMMAND is the command that was used to start the program. @@ -1933,26 +1921,24 @@ Swap: 256M Total, 38M Used, 217M Free, 1 The output is split into two sections. The header (the first five lines) shows the PID of the last - process to run, the - system load averages (which are a measure of how busy the system - is), the system uptime (time since the last reboot) and the - current time. The other figures in the header relate to how - many processes are running (47 in this case), how much memory - and swap space has been used, and how much time the system is - spending in different CPU states. + process to run, the system load averages (which are a measure + of how busy the system is), the system uptime (time since the + last reboot) and the current time. The other figures in the + header relate to how many processes are running (47 in this + case), how much memory and swap space has been used, and how + much time the system is spending in different CPU states. Below the header is a series of columns containing similar information to the output from &man.ps.1;, such as the - PID, - username, amount of CPU time, and the command that started the - process. By default, &man.top.1; also displays the amount of - memory space taken by the process. This is split into two - columns: one for total size and one for resident size. Total - size is how much memory the application has needed and the - resident size is how much it is actually using at the moment. - In this example, mutt has - required almost 8 MB of RAM, but is currently only using - 5 MB. + PID, username, amount of CPU time, and the + command that started the process. By default, &man.top.1; also + displays the amount of memory space taken by the process. + This is split into two columns: one for total size and one for + resident size. Total size is how much memory the application + has needed and the resident size is how much it is actually + using at the moment. In this example, + mutt has required almost 8 MB + of RAM, but is currently only using 5 MB. &man.top.1; automatically updates the display every two seconds. A different interval can be specified with @@ -1980,13 +1966,12 @@ Swap: 256M Total, 38M Used, 217M Free, 1 There is a convention to name programs that normally run as daemons with a trailing d. BIND is the Berkeley Internet Name - Domain, but the actual program that executes is - &man.named.8;. The Apache - web server program is httpd and the - line printer spooling daemon is &man.lpd.8;. This is - only a naming convention. For example, the main mail daemon for - the Sendmail application is - &man.sendmail.8;, and not + Domain, but the actual program that executes is &man.named.8;. + The Apache web server program is + httpd and the line printer spooling daemon + is &man.lpd.8;. This is only a naming convention. For example, + the main mail daemon for the Sendmail + application is &man.sendmail.8;, and not maild. One way to communicate with a daemon, or any running @@ -2050,16 +2035,14 @@ Swap: 256M Total, 38M Used, 217M Free, 1 This example shows how to send a signal to &man.inetd.8;. The &man.inetd.8; configuration file is - /etc/inetd.conf, and - &man.inetd.8; will re-read this configuration file - when it is sent a SIGHUP. + /etc/inetd.conf, and &man.inetd.8; will + re-read this configuration file when it is sent a + SIGHUP. Find the PID of the process to send - the signal - to using &man.pgrep.1;. In this example, the - PID for - &man.inetd.8; is 198: + the signal to using &man.pgrep.1;. In this example, the + PID for &man.inetd.8; is 198: &prompt.user; pgrep -l inetd 198 inetd -wW @@ -2080,10 +2063,9 @@ Swap: 256M Total, 38M Used, 217M Free, 1 process not owned by that user, the message kill: PID: Operation not permitted will be displayed. Mistyping - the PID will either - send the signal to the wrong process, which could have - negative results, or will send the signal to a - PID that is + the PID will either send the signal to + the wrong process, which could have negative results, or + will send the signal to a PID that is not currently in use, resulting in the error kill: PID: No such process. @@ -2111,9 +2093,8 @@ Swap: 256M Total, 38M Used, 217M Free, 1 Killing a random process on the system can be a bad idea. In particular, &man.init.8;, PID 1, is - special. Running - /bin/kill -s KILL 1 is a quick, and - unrecommended, way to shutdown the system. + special. Running /bin/kill -s KILL 1 is + a quick, and unrecommended, way to shutdown the system. Always double check the arguments to &man.kill.1; before pressing Return. @@ -2131,11 +2112,10 @@ Swap: 256M Total, 38M Used, 217M Free, 1 them. Many shells provide built in functions to help with everyday tasks such as file management, file globbing, command line editing, command macros, and environment variables. &os; - comes with several shells, including the - Bourne shell (&man.sh.1;) and the extended C shell - (&man.tcsh.1;). - Other shells are available from the &os; Ports Collection, such - as zsh and bash. + comes with several shells, including the Bourne shell + (&man.sh.1;) and the extended C shell (&man.tcsh.1;). Other + shells are available from the &os; Ports Collection, such as + zsh and bash. The shell that is used is really a matter of taste. A C programmer might feel more comfortable with a C-like shell such @@ -2275,13 +2255,12 @@ Swap: 256M Total, 38M Used, 217M Free, 1 Shells treat special characters, known as meta-characters, as special representations of data. The most common - meta-character is *, which - represents any number of characters in a filename. - Meta-characters can be used to perform filename globbing. For - example, echo * is equivalent to - &man.ls.1; because the shell takes all the files that - match * and &man.echo.1; lists - them on the command line. + meta-character is *, which represents any + number of characters in a filename. Meta-characters can be + used to perform filename globbing. For example, echo + * is equivalent to &man.ls.1; because the shell + takes all the files that match * and + &man.echo.1; lists them on the command line. To prevent the shell from interpreting a special character, escape it from the shell by starting it with a backslash @@ -2297,9 +2276,8 @@ Swap: 256M Total, 38M Used, 217M Free, 1 to use chsh. Running this command will open the editor that is configured in the EDITOR environment variable, which by default - is set to &man.vi.1;. Change - the Shell: line to the full path of the - new shell. + is set to &man.vi.1;. Change the Shell: line + to the full path of the new shell. Alternately, use chsh -s which will set the specified shell without opening an editor. For example, @@ -2310,10 +2288,9 @@ Swap: 256M Total, 38M Used, 217M Free, 1 The new shell must be present in /etc/shells. If the shell was - installed from the &os; Ports - Collection as described in , it - should be automatically added to - this file. If it is missing, add it using this + installed from the &os; Ports Collection as described in + , it should be automatically added + to this file. If it is missing, add it using this command, replacing the path with the path of the shell: @@ -2343,9 +2320,9 @@ Swap: 256M Total, 38M Used, 217M Free, 1 &man.ee.1; - A simple editor to learn is &man.ee.1;, - which stands for easy editor. To start this editor, type - ee filename where + A simple editor to learn is &man.ee.1;, which stands for + easy editor. To start this editor, type ee + filename where filename is the name of the file to be edited. Once inside the editor, all of the commands for manipulating the editor's functions are listed at the top of the @@ -2353,10 +2330,9 @@ Swap: 256M Total, 38M Used, 217M Free, 1 Ctrl, so ^e expands to Ctrle. - To leave &man.ee.1;, press - Esc, then choose the leave - editor option from the main menu. The editor will - prompt to save any changes if the file has been + To leave &man.ee.1;, press Esc, then choose + the leave editor option from the main menu. + The editor will prompt to save any changes if the file has been modified. @@ -2375,9 +2351,8 @@ Swap: 256M Total, 38M Used, 217M Free, 1 &os; also comes with more powerful text editors, such as - &man.vi.1;, as part of the base system. - Other editors, like editors/emacs and + &man.vi.1;, as part of the base system. Other editors, like + editors/emacs and editors/vim, are part of the &os; Ports Collection. These editors offer more functionality at the expense of being a more complicated to learn. Learning a @@ -2407,8 +2382,8 @@ Swap: 256M Total, 38M Used, 217M Free, 1 keyboard. Most devices in a &os; must be accessed through special - files called device nodes, which are located in - /dev. + files called device nodes, which are located in /dev. Creating Device Nodes @@ -2482,8 +2457,8 @@ Swap: 256M Total, 38M Used, 217M Free, 1 the &man.a.out.5; format, a technology tried and proven through many generations of BSD releases, until the beginning of the 3.X branch. Though it was possible to build and run native - ELF binaries and kernels on a &os; - system for some time before that, &os; initially resisted the + ELF binaries and kernels on a &os; system + for some time before that, &os; initially resisted the push to switch to ELF as the default format. Why? When Linux made its painful transition to ELF, it was due to their inflexible @@ -2543,9 +2518,8 @@ Swap: 256M Total, 38M Used, 217M Free, 1 programs rewrote them and added simpler support for building cross compilers and plugging in different formats. Those who wanted to build cross compilers targeting &os; were out of luck - since the older sources that &os; had for - &man.as.1; and &man.ld.1; - were not up to the task. The new GNU tools chain + since the older sources that &os; had for &man.as.1; and + &man.ld.1; were not up to the task. The new GNU tools chain (binutils) supports cross compiling, ELF, shared libraries, and C++ extensions. In addition, many vendors release @@ -2583,8 +2557,8 @@ Swap: 256M Total, 38M Used, 217M Free, 1 &prompt.user; man command where command is the name of - the command to learn about. For example, to learn - more about &man.ls.1;, type: + the command to learn about. For example, to learn more about + &man.ls.1;, type: &prompt.user; man ls @@ -2632,18 +2606,16 @@ Swap: 256M Total, 38M Used, 217M Free, 1 In some cases, the same topic may appear in more than one section of the online manual. For example, there is a &man.chmod.1; user command and a - chmod() system call. To tell - &man.man.1; which section to display, specify the - section number: + chmod() system call. To tell &man.man.1; + which section to display, specify the section number: &prompt.user; man 1 chmod This will display the manual page for the user command - &man.chmod.1;. References to a particular section - of the online manual are traditionally placed in parenthesis - in written documentation, so &man.chmod.1; refers to the - user command and &man.chmod.2; refers - to the system call. + &man.chmod.1;. References to a particular section of the + online manual are traditionally placed in parenthesis in + written documentation, so &man.chmod.1; refers to the user + command and &man.chmod.2; refers to the system call. If the command name is unknown, use man -k to search for keywords in the command @@ -2655,8 +2627,8 @@ Swap: 256M Total, 38M Used, 217M Free, 1 keyword mail in their descriptions. This is equivalent to using &man.apropos.1;. - To determine what the commands in - /usr/bin do, + To determine what the commands in /usr/bin do, type: &prompt.user; cd /usr/bin