Attachment 129956 Details for Bug 174029 – file.diff

[patch] file.diff

file.diff (text/plain), 2.89 KB, created by Derek Wood on 2012-12-01 06:10:00 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Derek Wood

Created: 2012-12-01 06:10:00 UTC

Size: 2.89 KB

patch

obsolete

>Index: en_US.ISO8859-1/books/faq/book.xml
>===================================================================
>--- en_US.ISO8859-1/books/faq/book.xml	(revision 40165)
>+++ en_US.ISO8859-1/books/faq/book.xml	(working copy)
>@@ -3975,8 +3975,8 @@
> 
>       <qandaentry>
> 	<question id="minimal-sh">
>-	  <para>Why is <command>/bin/sh</command> so minimal?  Why does
>-	    &os; not use <command>bash</command> or another
>+	  <para>Why is <command>/bin/sh</command> so minimal?  Why
>+	    does &os; not use <command>bash</command> or another
> 	    shell?</para>
> 	</question>
> 
>@@ -3986,25 +3986,26 @@
> 
> 	  <para>The more complicated answer: many people need to write
> 	    shell scripts which will be portable across many systems.
>-	    That is why &posix; specifies the shell and utility commands
>-	    in great detail.  Most scripts are written in Bourne shell,
>-	    and because several important programming interfaces
>-	    (&man.make.1;, &man.system.3;, &man.popen.3;, and analogues
>-	    in higher-level scripting languages like Perl and Tcl) are
>-	    specified to use the Bourne shell to interpret commands.
>-	    Because the Bourne shell is so often and widely used, it is
>-	    important for it to be quick to start, be deterministic in
>-	    its behavior, and have a small memory footprint.</para>
>+	    That is why &posix; specifies the shell and utility
>+	    commands in great detail.  Most scripts are written in
>+	    Bourne shell (&man.sh.1;), and because several important
>+	    programming interfaces (&man.make.1;, &man.system.3;,
>+	    &man.popen.3;, and analogues in higher-level scripting
>+	    languages like Perl and Tcl) are specified to use the
>+	    Bourne shell to interpret commands.  Because the Bourne
>+	    shell is so often and widely used, it is important for it
>+	    to be quick to start, be deterministic in its behavior,
>+	    and have a small memory footprint.</para>
> 
> 	  <para>The existing implementation is our best effort at
> 	    meeting as many of these requirements simultaneously as we
>-	    can.  In order to keep <command>/bin/sh</command> small, we
>-	    have not provided many of the convenience features that
>-	    other shells have.  That is why the Ports Collection
>-	    includes more featureful shells like
>+	    can.  In order to keep <command>/bin/sh</command> small,
>+	    we have not provided many of the convenience features that
>+	    other shells have.  That is why &os; and the Ports
>+	    Collection include more featureful shells like
> 	    <command>bash</command>, <command>scsh</command>,
>-	    <command>tcsh</command>, and <command>zsh</command>.  (You
>-	    can compare for yourself the memory utilization of all these
>+	    &man.tcsh.1;, and <command>zsh</command>.  (You can
>+	    compare for yourself the memory utilization of all these
> 	    shells by looking at the <quote>VSZ</quote> and
> 	    <quote>RSS</quote> columns in a <command>ps
> 	    <option>-u</option></command> listing.)</para>

Actions: View | Diff

Attachments on bug 174029: 129956 | 129957 | 129958