Rewrap various lines in Chapter 1 that were 80 columns or darn close.

Whitespace-only commit, no content changes.
This commit is contained in:
Michael Lucas 2001-12-18 15:56:37 +00:00
parent 9cb5fb8789
commit 344941f6ba
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=11461

View file

@ -75,14 +75,16 @@
</question> </question>
<answer> <answer>
<para>Briefly, FreeBSD is a UN*X-like operating system for the <para>Briefly, FreeBSD is a UN*X-like operating system for
i386 and Alpha/AXP platforms based on U.C. Berkeley's the i386 and Alpha/AXP platforms based on U.C. Berkeley's
<quote>4.4BSD-Lite</quote> release, with some <quote>4.4BSD-Lite2</quote> enhancements. <quote>4.4BSD-Lite</quote> release, with some
It is also based indirectly on William Jolitz's port of U.C. <quote>4.4BSD-Lite2</quote> enhancements. It is also based
Berkeley's <quote>Net/2</quote> to the i386, known as <quote>386BSD</quote>, though very indirectly on William Jolitz's port of U.C. Berkeley's
little of the 386BSD code remains. A fuller description of <quote>Net/2</quote> to the i386, known as
what FreeBSD is and how it can work for you may be found on <quote>386BSD</quote>, though very little of the 386BSD
the <ulink URL="../../../../index.html">FreeBSD home code remains. A fuller description of what FreeBSD is and
how it can work for you may be found on the <ulink
URL="../../../../index.html">FreeBSD home
page</ulink>.</para> page</ulink>.</para>
<para>FreeBSD is used by companies, Internet Service Providers, <para>FreeBSD is used by companies, Internet Service Providers,
@ -277,14 +279,14 @@
<answer> <answer>
<para><ulink <para><ulink
URL="../handbook/cutting-edge.html#CURRENT">FreeBSD-CURRENT</ulink> URL="../handbook/cutting-edge.html#CURRENT">FreeBSD-CURRENT</ulink>
is the development version of the operating system, which will is the development version of the operating system, which
in due course become 5.0-RELEASE. As such, it is really only will in due course become 5.0-RELEASE. As such, it is
of interest to developers working on the system and die-hard really only of interest to developers working on the
hobbyists. See the <ulink system and die-hard hobbyists. See the <ulink
URL="../handbook/cutting-edge.html#CURRENT">relevant URL="../handbook/cutting-edge.html#CURRENT">relevant
section</ulink> in the <ulink section</ulink> in the <ulink
URL="../handbook/index.html">handbook</ulink> for details on URL="../handbook/index.html">handbook</ulink> for details
running -CURRENT.</para> on running -CURRENT.</para>
<para>If you are not familiar with the operating system or are <para>If you are not familiar with the operating system or are
not capable of identifying the difference between a real not capable of identifying the difference between a real
@ -359,16 +361,19 @@
<answer> <answer>
<para>Back when FreeBSD 2.0.5 was released, we decided to <para>Back when FreeBSD 2.0.5 was released, we decided to
branch FreeBSD development into two parts. One branch was branch FreeBSD development into two parts. One branch was
named <ulink URL="../handbook/current-stable.html#STABLE">-STABLE</ulink>, named <ulink
with the intention that only well-tested bug fixes and small URL="../handbook/current-stable.html#STABLE">-STABLE</ulink>,
incremental enhancements would be made to it (for Internet with the intention that only well-tested bug fixes and
Service Providers and other commercial enterprises for whom small incremental enhancements would be made to it (for
sudden shifts or experimental features are quite Internet Service Providers and other commercial
undesirable). The other branch was <ulink enterprises for whom sudden shifts or experimental
features are quite undesirable). The other branch was
<ulink
URL="../handbook/cutting-edge.html#CURRENT">-CURRENT</ulink>, URL="../handbook/cutting-edge.html#CURRENT">-CURRENT</ulink>,
which essentially has been one unbroken line leading towards which essentially has been one unbroken line leading
5.0-RELEASE (and beyond) since 2.0 was released. If a little towards 5.0-RELEASE (and beyond) since 2.0 was
ASCII art would help, this is how it looks:</para> released. If a little ASCII art would help, this is how it
looks:</para>
<programlisting> 2.0 <programlisting> 2.0
| |
@ -406,13 +411,15 @@
branches will be, for the most part, security-related bug branches will be, for the most part, security-related bug
fixes.</para> fixes.</para>
<para>4-STABLE is the actively developed -STABLE branch. The <para>4-STABLE is the actively developed -STABLE branch.
latest release on the 4-STABLE is &rel.current;-RELEASE, which was released The latest release on the 4-STABLE is
in &rel.current.date;.</para> &rel.current;-RELEASE, which was released in
&rel.current.date;.</para>
<para>The 5-CURRENT branch is slowly progressing toward 5.0-RELEASE <para>The 5-CURRENT branch is slowly progressing toward
and beyond. See <link linkend="current">What is 5.0-RELEASE and beyond. See <link linkend="current">What
FreeBSD-CURRENT?</link> for more information on this branch.</para> is FreeBSD-CURRENT?</link> for more information on this
branch.</para>
</answer> </answer>
</qandaentry> </qandaentry>
@ -448,14 +455,15 @@
</question> </question>
<answer> <answer>
<para>The key decisions concerning the FreeBSD project, such as <para>The key decisions concerning the FreeBSD project, such
the overall direction of the project and who is allowed to add as the overall direction of the project and who is allowed
code to the source tree, are made by a <ulink to add code to the source tree, are made by a <ulink
URL="../../articles/contributors/article.html#STAFF-CORE">core team</ulink> of URL="../../articles/contributors/article.html#STAFF-CORE">core
9 people. There is a much larger team of more than 200 <ulink team</ulink> of 9 people. There is a much larger team of
URL="../../articles/contributors/article.html#STAFF-COMMITTERS">committers</ulink> who more than 200 <ulink
are authorized to make changes directly to the FreeBSD source URL="../../articles/contributors/article.html#STAFF-COMMITTERS">committers</ulink>
tree.</para> who are authorized to make changes directly to the FreeBSD
source tree.</para>
<para>However, most non-trivial changes are discussed in advance <para>However, most non-trivial changes are discussed in advance
in the <link linkend="mailing">mailing lists</link>, and there in the <link linkend="mailing">mailing lists</link>, and there
@ -602,12 +610,13 @@
</listitem> </listitem>
</itemizedlist> </itemizedlist>
<para>Each of these channels are distinct and are not connected <para>Each of these channels are distinct and are not
to each other. Their chat styles also differ, so you may need connected to each other. Their chat styles also differ,
to try each to find one suited to your chat style. As with so you may need to try each to find one suited to your
<emphasis>all</emphasis> types of IRC traffic, if you are easily offended or cannot chat style. As with <emphasis>all</emphasis> types of IRC
deal with lots of young people (and more than a few older traffic, if you are easily offended or cannot deal with
ones) doing the verbal equivalent of jello wrestling, do not lots of young people (and more than a few older ones)
doing the verbal equivalent of jello wrestling, do not
even bother with it.</para> even bother with it.</para>
</answer> </answer>
</qandaentry> </qandaentry>
@ -643,10 +652,11 @@
</question> </question>
<answer> <answer>
<para>Yes. The documentation is available in a number of different <para>Yes. The documentation is available in a number of
formats and compression schemes on the FreeBSD FTP site, in the different formats and compression schemes on the FreeBSD
<ulink FTP site, in the <ulink
URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/">/pub/FreeBSD/doc/</ulink> directory.</para> URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/">/pub/FreeBSD/doc/</ulink>
directory.</para>
<para>The documentation is categorised in a number of different <para>The documentation is categorised in a number of different
ways. These include:</para> ways. These include:</para>