svn commit: r47085 - head/en_US.ISO8859-1/books/handbook/basics
Dru Lavigne
dru at FreeBSD.org
Sun Jul 26 08:29:39 UTC 2015
Author: dru
Date: Sun Jul 26 08:29:38 2015
New Revision: 47085
URL: https://svnweb.freebsd.org/changeset/doc/47085
Log:
Fix redundancy. While here, correct usage of unix and tighten wording.
Sponsored by: Essen Devsummit Hackathon
Modified:
head/en_US.ISO8859-1/books/handbook/basics/chapter.xml
Modified: head/en_US.ISO8859-1/books/handbook/basics/chapter.xml
==============================================================================
--- head/en_US.ISO8859-1/books/handbook/basics/chapter.xml Sun Jul 26 08:13:26 2015 (r47084)
+++ head/en_US.ISO8859-1/books/handbook/basics/chapter.xml Sun Jul 26 08:29:38 2015 (r47085)
@@ -3178,14 +3178,14 @@ Swap: 2048M Total, 2048M Free
<para>Shell redirection is the action of sending the output or
the input of a command into another command or into a file.
To capture the output of the &man.ls.1; command, for example,
- into a file, simply redirect the output:</para>
+ into a file, redirect the output:</para>
<screen>&prompt.user; <userinput>ls > directory_listing.txt</userinput></screen>
- <para>The <filename>directory_listing.txt</filename> file will
- now contain the directory contents. Some commands allow you
- to read input in a similar one, such as &man.sort.1;. To sort
- this listing, redirect the input:</para>
+ <para>The directory contents will now be listed in
+ <filename>directory_listing.txt</filename>. Some commands can
+ be used to read input, such as &man.sort.1;. To sort this
+ listing, redirect the input:</para>
<screen>&prompt.user; <userinput>sort < directory_listing.txt</userinput></screen>
@@ -3196,26 +3196,24 @@ Swap: 2048M Total, 2048M Free
<screen>&prompt.user; <userinput>sort < directory_listing.txt > sorted.txt</userinput></screen>
<para>In all of the previous examples, the commands are
- performing redirection using file descriptors. Every unix
- system has file descriptors; however, here we will focus on
- three, so named as Standard Input, Standard Output, and
- Standard Error. Each one has a purpose, where input could be
- a keyboard or a mouse, something that provides input. Output
- could be a screen or paper in a printer for example. And
- error would be anything that is used for diagnostic or error
- messages. All three are considered <acronym>I/O</acronym>
- based file descriptors and sometimes considered
- streams.</para>
-
- <para>Through the use of these descriptors, short named stdin,
- stdout, and stderr, the shell allows output and input to be
- passed around through various commands and redirected to or
- from a file. Another method of redirection is the pipe
- operator.</para>
+ performing redirection using file descriptors. Every &unix;
+ system has file descriptors, which include standard input
+ (stdin), standard output (stdout), and standard error
+ (stderr). Each one has a purpose, where input could be a
+ keyboard or a mouse, something that provides input. Output
+ could be a screen or paper in a printer. And error would be
+ anything that is used for diagnostic or error messages. All
+ three are considered <acronym>I/O</acronym> based file
+ descriptors and sometimes considered streams.</para>
+
+ <para>Through the use of these descriptors, the shell allows
+ output and input to be passed around through various commands
+ and redirected to or from a file. Another method of
+ redirection is the pipe operator.</para>
<para>The &unix; pipe operator, <quote>|</quote> allows the
- output of one command to be directly passed, or directed to
- another program. Basically a pipe will allow the standard
+ output of one command to be directly passed or directed to
+ another program. Basically, a pipe allows the standard
output of a command to be passed as standard input to another
command, for example:</para>
More information about the svn-doc-head
mailing list