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