Date: Fri, 7 Dec 2012 13:00:58 +0000 (UTC) From: Eitan Adler <eadler@FreeBSD.org> To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40297 - head/en_US.ISO8859-1/books/faq Message-ID: <201212071300.qB7D0w5V099147@svn.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: eadler Date: Fri Dec 7 13:00:58 2012 New Revision: 40297 URL: http://svnweb.freebsd.org/changeset/doc/40297 Log: Rewrap minimal-sh Translators may ignore PR: 174029 Submitted by: Derek Wood <ddwood@highdensity.org> Approved by: bcr (mentor) Modified: head/en_US.ISO8859-1/books/faq/book.xml Modified: head/en_US.ISO8859-1/books/faq/book.xml ============================================================================== --- head/en_US.ISO8859-1/books/faq/book.xml Fri Dec 7 13:00:56 2012 (r40296) +++ head/en_US.ISO8859-1/books/faq/book.xml Fri Dec 7 13:00:58 2012 (r40297) @@ -3980,33 +3980,34 @@ kern.timecounter.hardware: TSC -> i82 <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> <answer> - <para>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 (&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>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 (&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 + 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 <command>bash</command>, <command>scsh</command>, - &man.tcsh.1;, 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>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201212071300.qB7D0w5V099147>