svn commit: r44814 - head/en_US.ISO8859-1/books/faq
Dru Lavigne
dru at FreeBSD.org
Mon May 12 14:18:12 UTC 2014
Author: dru
Date: Mon May 12 14:18:11 2014
New Revision: 44814
URL: http://svnweb.freebsd.org/changeset/doc/44814
Log:
White space fix only. Translators can ignore.
Sponsored by: iXsystems
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 Mon May 12 13:27:37 2014 (r44813)
+++ head/en_US.ISO8859-1/books/faq/book.xml Mon May 12 14:18:11 2014 (r44814)
@@ -21,8 +21,7 @@
]>
<book xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:lang="en">
<info><title>Frequently Asked Questions for &os;
- &rel3.relx;, &rel2.relx; and &rel.relx;</title>
-
+ &rel3.relx;, &rel2.relx; and &rel.relx;</title>
<author><orgname>The &os; Documentation Project</orgname></author>
@@ -70,16 +69,19 @@
<releaseinfo>$FreeBSD$</releaseinfo>
<abstract>
- <para>This is the FAQ for &os; versions &rel3.relx;, &rel2.relx; and
- &rel.relx;. Every effort has been made to make this FAQ as
- informative as possible; if you have any suggestions as to how
- it may be improved, please feel free to mail them to the
+ <para>This is the FAQ for &os; versions &rel3.relx;, &rel2.relx;
+ and &rel.relx;. Every effort has been made to make this FAQ
+ as informative as possible; if you have any suggestions as to
+ how it may be improved, please feel free to mail them to the
&a.doc;.</para>
- <para>The latest version of
- this document is always available from the <link xlink:href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/faq/index.html">&os; website</link>.
- It may also be downloaded as one large <link xlink:href="book.html">HTML</link> file with HTTP or as a variety
- of other formats from the <link xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/">&os; FTP
+ <para>The latest version of this document is always available
+ from the <link
+ xlink:href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/faq/index.html">&os;
+ website</link>. It may also be downloaded as one large
+ <link xlink:href="book.html">HTML</link> file with HTTP or as
+ a variety of other formats from the <link
+ xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/">&os; FTP
server</link>.</para>
</abstract>
</info>
@@ -95,24 +97,26 @@
<answer>
<para>&os; is a modern operating system for desktops,
- laptops, servers, and embedded systems with
- support for a large number of <link xlink:href="http://www.FreeBSD.org/platforms/">platforms</link>.</para>
-
- <para>It is 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.</para>
+ laptops, servers, and embedded systems with support for a
+ large number of <link
+ xlink:href="http://www.FreeBSD.org/platforms/">platforms</link>.</para>
+
+ <para>It is 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.</para>
<para>&os; is used by companies, Internet Service Providers,
- researchers, computer professionals, students and home users
- all over the world in their work, education and
+ researchers, computer professionals, students and home
+ users all over the world in their work, education and
recreation.</para>
<para>For more detailed information on &os;, please see the
- <link xlink:href="&url.books.handbook;/index.html">&os; Handbook</link>.</para>
+ <link xlink:href="&url.books.handbook;/index.html">&os;
+ Handbook</link>.</para>
</answer>
</qandaentry>
@@ -122,11 +126,9 @@
</question>
<answer>
- <para>The goal of the &os; Project is to provide a
- stable and fast general purpose
- operating system that may
- be used for any purpose
- without strings attached.</para>
+ <para>The goal of the &os; Project is to provide a stable
+ and fast general purpose operating system that may be used
+ for any purpose without strings attached.</para>
</answer>
</qandaentry>
@@ -136,9 +138,11 @@
</question>
<answer>
- <para>Yes. Those restrictions do not control how you use the
- code, merely how you treat the &os; Project itself. If you
- have serious license concerns, read the actual <link xlink:href="http://www.FreeBSD.org/copyright/freebsd-license.html">license</link>.
+ <para>Yes. Those restrictions do not control how you use
+ the code, merely how you treat the &os; Project itself.
+ If you have serious license concerns, read the actual
+ <link
+ xlink:href="http://www.FreeBSD.org/copyright/freebsd-license.html">license</link>.
For the simply curious, the license can be summarized like
this.</para>
@@ -157,29 +161,29 @@
</itemizedlist>
<para>Many of us have a significant investment in the
- project
- and would certainly not mind a little financial
+ project and would certainly not mind a little financial
compensation now and then, but we definitely do not insist
on it. We believe that our first and foremost
<quote>mission</quote> is to provide code to any and all
comers, and for whatever purpose, so that the code gets
- the
- widest possible use and provides the widest possible
- benefit. This, we believe, is one of the most
- fundamental
+ the widest possible use and provides the widest possible
+ benefit. This, we believe, is one of the most fundamental
goals of Free Software and one that we enthusiastically
support.</para>
- <para>Code in our source tree which falls under the
- <link xlink:href="http://www.FreeBSD.org/copyright/COPYING">GNU General Public License (GPL)</link>
- or <link xlink:href="http://www.FreeBSD.org/copyright/COPYING.LIB">GNU Library General Public License (LGPL)</link>
- comes with slightly more strings attached, though at least
- on the side of enforced access rather than the usual
- opposite. Due to the additional complexities that can
- evolve in the commercial use of GPL software, we do,
- however, endeavor to replace such software with submissions
- under the more relaxed <link xlink:href="http://www.FreeBSD.org/copyright/freebsd-license.html">&os; license</link>
- whenever possible.</para>
+ <para>Code in our source tree which falls under the <link
+ xlink:href="http://www.FreeBSD.org/copyright/COPYING">GNU
+ General Public License (GPL)</link> or <link
+ xlink:href="http://www.FreeBSD.org/copyright/COPYING.LIB">GNU
+ Library General Public License (LGPL)</link> comes with
+ slightly more strings attached, though at least on the
+ side of enforced access rather than the usual opposite.
+ Due to the additional complexities that can evolve in the
+ commercial use of GPL software, we do, however, endeavor
+ to replace such software with submissions under the more
+ relaxed <link
+ xlink:href="http://www.FreeBSD.org/copyright/freebsd-license.html">&os;
+ license</link> whenever possible.</para>
</answer>
</qandaentry>
@@ -193,36 +197,39 @@
that cut-and-dried.</para>
<para>Most people do not actually use an operating system.
- They use applications. The applications are what really use
- the operating system. &os; is designed to provide a robust
- and full-featured environment for applications. It supports
- a wide variety of web browsers, office suites, email
- readers, graphics programs, programming environments,
- network servers, and just about everything else you might
- want. Most of these applications can be managed through the
- <link xlink:href="http://www.FreeBSD.org/ports/">Ports Collection</link>.</para>
-
- <para>If you need to use an application that is only available
- on one operating system, you simply cannot replace that
- operating system. Chances are there is a very similar
- application on &os;, however. If you want a solid office or
- Internet server, a reliable workstation, or just the ability
- to do your job without interruptions, &os; will almost
- certainly do everything you need. Many computer users
- across the world, including both novices and experienced
- &unix; administrators, use &os; as their only desktop
- operating system.</para>
+ They use applications. The applications are what really
+ use the operating system. &os; is designed to provide a
+ robust and full-featured environment for applications. It
+ supports a wide variety of web browsers, office suites,
+ email readers, graphics programs, programming
+ environments, network servers, and just about everything
+ else you might want. Most of these applications can be
+ managed through the <link
+ xlink:href="http://www.FreeBSD.org/ports/">Ports
+ Collection</link>.</para>
+
+ <para>If you need to use an application that is only
+ available on one operating system, you simply cannot
+ replace that operating system. Chances are there is a
+ very similar application on &os;, however. If you want a
+ solid office or Internet server, a reliable workstation,
+ or just the ability to do your job without interruptions,
+ &os; will almost certainly do everything you need. Many
+ computer users across the world, including both novices
+ and experienced &unix; administrators, use &os; as their
+ only desktop operating system.</para>
<para>If you are migrating to &os; from some other &unix;
- environment, you already know most of what you need to. If
- your background is in graphic-driven operating systems such
- as &windows; and &macos;, you may be interested in using
- <link xlink:href="http://www.pcbsd.org/">PC-BSD</link>, a &os; based
- distribution, instead. If you have not used &unix; before
- expect to invest
- additional time learning the &unix; way of doing things.
- This FAQ and the <link xlink:href="&url.books.handbook;/index.html">&os; Handbook</link>
- are excellent places to start.</para>
+ environment, you already know most of what you need to.
+ If your background is in graphic-driven operating systems
+ such as &windows; and &macos;, you may be interested in
+ using <link
+ xlink:href="http://www.pcbsd.org/">PC-BSD</link>, a &os;
+ based distribution, instead. If you have not used &unix;
+ before expect to invest additional time learning the
+ &unix; way of doing things. This FAQ and the <link
+ xlink:href="&url.books.handbook;/index.html">&os;
+ Handbook</link> are excellent places to start.</para>
</answer>
</qandaentry>
@@ -241,54 +248,59 @@
<listitem>
<para>Full source for the operating system is freely
available, and the minimum possible restrictions have
- been placed upon its use, distribution and incorporation
- into other work (commercial or non-commercial).</para>
+ been placed upon its use, distribution and
+ incorporation into other work (commercial or
+ non-commercial).</para>
</listitem>
<listitem>
- <para>Anyone who has an improvement or bug fix is free to
- submit their code and have it added to the source tree
- (subject to one or two obvious provisions).</para>
+ <para>Anyone who has an improvement or bug fix is free
+ to submit their code and have it added to the source
+ tree (subject to one or two obvious
+ provisions).</para>
</listitem>
</itemizedlist>
<para>It is worth pointing out that the word
<quote>free</quote> is being used in two ways here, one
meaning <quote>at no cost</quote>, the other meaning
- <quote>you can do whatever you like</quote>. Apart from one
- or two things you <emphasis>cannot</emphasis> do with the
- &os; code, for example pretending you wrote it, you can
- really do whatever you like with it.</para>
+ <quote>you can do whatever you like</quote>. Apart from
+ one or two things you <emphasis>cannot</emphasis> do with
+ the &os; code, for example pretending you wrote it, you
+ can really do whatever you like with it.</para>
</answer>
</qandaentry>
<qandaentry>
<question xml:id="differences-to-other-bsds">
<para>What are the differences between &os; and NetBSD,
- OpenBSD, and other open source BSD operating systems?</para>
+ OpenBSD, and other open source BSD operating
+ systems?</para>
</question>
<answer>
- <para>James Howard wrote a good explanation of the history and
- differences between the various projects,
- called <link xlink:href="http://www.freebsdworld.gr/freebsd/bsd-family-tree.html">The BSD Family Tree</link>
- which goes a fair way to answering this question.
- Some of the information is out of date, but the history
- portion in particular remains accurate.</para>
+ <para>James Howard wrote a good explanation of the history
+ and differences between the various projects, called <link
+ xlink:href="http://www.freebsdworld.gr/freebsd/bsd-family-tree.html">The
+ BSD Family Tree</link> which goes a fair way to
+ answering this question. Some of the information is out
+ of date, but the history portion in particular remains
+ accurate.</para>
<para>Most of the BSDs share patches and code, even today.
All of the BSDs have common ancestry.</para>
- <para>The design goals of &os; are described in
- <xref linkend="FreeBSD-goals"/>, above. The design goals
- of the other most popular BSDs may be summarized as
+ <para>The design goals of &os; are described in <xref
+ linkend="FreeBSD-goals"/>, above. The design goals of
+ the other most popular BSDs may be summarized as
follows:</para>
<itemizedlist>
<listitem>
<para>OpenBSD aims for operating system security above
all else. The OpenBSD team wrote &man.ssh.1; and
- &man.pf.4;, which have both been ported to &os;.</para>
+ &man.pf.4;, which have both been ported to
+ &os;.</para>
</listitem>
<listitem>
@@ -297,9 +309,9 @@
</listitem>
<listitem>
- <para>DragonFly BSD is a fork of &os; 4.8 that has
- since developed many interesting features of its own,
- including the HAMMER file system and support for
+ <para>DragonFly BSD is a fork of &os; 4.8 that
+ has since developed many interesting features of its
+ own, including the HAMMER file system and support for
user-mode <quote>vkernels</quote>.</para>
</listitem>
</itemizedlist>
@@ -313,48 +325,51 @@
<answer>
<para>At any point in the development of &os;, there can be
- multiple parallel branches. &rel.relx; releases are
- made from the &rel.stable; branch, and &rel2.relx;
- releases are made from the &rel2.stable; branch.</para>
-
- <para>Up until the release of 9.0, the
- &rel2.relx; series was the one known as
- <emphasis>-STABLE</emphasis>. However, as of
- &rel.head.relx;, the
- &rel2.relx; branch will be designated for
- an <quote>extended support</quote> status and receive only
- fixes for major problems, such as security-related fixes.
+ multiple parallel branches. &rel.relx; releases are made
+ from the &rel.stable; branch, and &rel2.relx; releases are
+ made from the &rel2.stable; branch.</para>
+
+ <para>Up until the release of 9.0, the &rel2.relx; series
+ was the one known as <emphasis>-STABLE</emphasis>.
+ However, as of &rel.head.relx;, the &rel2.relx; branch
+ will be designated for an <quote>extended support</quote>
+ status and receive only fixes for major problems, such as
+ security-related fixes.
<!--There will be no more releases made from the
&rel2.stable; branch, and it is considered a
<quote>legacy</quote> branch and most current work will only
become a part of &rel.stable; and &rel2.stable;.--></para>
- <para>Version <link xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/i386/&rel.current;-RELEASE/">&rel.current;</link>
- is the latest release from the &rel.stable;
- branch; it was released in &rel.current.date;. Version
- <link xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel2.current;-RELEASE/">&rel2.current;</link>
- is the latest release from the &rel2.stable;
- branch; it was released in &rel2.current.date;.</para>
+ <para>Version <link
+ xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/i386/&rel.current;-RELEASE/">&rel.current;</link>
+ is the latest release from the &rel.stable; branch; it was
+ released in &rel.current.date;. Version <link
+ xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel2.current;-RELEASE/">&rel2.current;</link>
+ is the latest release from the &rel2.stable; branch; it
+ was released in &rel2.current.date;.</para>
<para>Briefly, <emphasis>-STABLE</emphasis> is aimed at the
ISP, corporate user, or any user who wants stability and a
- minimal number of changes compared to the new (and possibly
- unstable) features of the latest
+ minimal number of changes compared to the new (and
+ possibly unstable) features of the latest
<emphasis>-CURRENT</emphasis> snapshot. Releases can come
- from either branch, but <emphasis>-CURRENT</emphasis> should
- only be used if you are prepared for its increased
+ from either branch, but <emphasis>-CURRENT</emphasis>
+ should only be used if you are prepared for its increased
volatility (relative to <emphasis>-STABLE</emphasis>, that
is).</para>
- <para>Releases are made <link linkend="release-freq">every few months</link>. While
- many people stay more up-to-date with the &os; sources (see
- the questions on <link linkend="current">&os.current;</link> and <link linkend="stable">&os.stable;</link>) than that, doing so
+ <para>Releases are made <link linkend="release-freq">every
+ few months</link>. While many people stay more
+ up-to-date with the &os; sources (see the questions on
+ <link linkend="current">&os.current;</link> and <link
+ linkend="stable">&os.stable;</link>) than that, doing so
is more of a commitment, as the sources are a moving
target.</para>
<para>More information on &os; releases can be found on the
- <link xlink:href="http://www.FreeBSD.org/releng/index.html#release-build">Release Engineering page</link>
- and in &man.release.7;.</para>
+ <link
+ xlink:href="http://www.FreeBSD.org/releng/index.html#release-build">Release
+ Engineering page</link> and in &man.release.7;.</para>
</answer>
</qandaentry>
@@ -364,22 +379,26 @@
</question>
<answer>
- <para><link xlink:href="&url.books.handbook;/current-stable.html#current">&os.current;</link>
+ <para><link
+ xlink:href="&url.books.handbook;/current-stable.html#current">&os.current;</link>
is the development version of the operating system, which
will in due course become the new &os.stable; branch. As
- such, it is really only of interest to developers working on
- the system and die-hard hobbyists. See the <link xlink:href="&url.books.handbook;/current-stable.html#current">relevant section</link>
- in the <link xlink:href="&url.books.handbook;/index.html">Handbook</link> for
- details on running <emphasis>-CURRENT</emphasis>.</para>
+ such, it is really only of interest to developers working
+ on the system and die-hard hobbyists. See the <link
+ xlink:href="&url.books.handbook;/current-stable.html#current">relevant
+ section</link> in the <link
+ xlink:href="&url.books.handbook;/index.html">Handbook</link>
+ for details on running
+ <emphasis>-CURRENT</emphasis>.</para>
- <para>If you are not familiar with &os;
- you should not use
+ <para>If you are not familiar with &os; you should not use
&os.current;. This branch sometimes evolves quite quickly
- and due to mistake can be un-buildable at times.
- People that use &os.current; are expected to be able to
- analyze, debug, and report problems.</para>
+ and due to mistake can be un-buildable at times. People
+ that use &os.current; are expected to be able to analyze,
+ debug, and report problems.</para>
- <para>&os; <link xlink:href="&url.base;/snapshots/">snapshot</link>
+ <para>&os; <link
+ xlink:href="&url.base;/snapshots/">snapshot</link>
releases are made based on the current state of the
<emphasis>-CURRENT</emphasis> and
<emphasis>-STABLE</emphasis> branches. The goals behind
@@ -395,32 +414,34 @@
<para>To give people who would like to run
<emphasis>-CURRENT</emphasis> or
<emphasis>-STABLE</emphasis> but who do not have the
- time or bandwidth to follow it on a day-to-day basis an
- easy way of bootstrapping it onto their systems.</para>
+ time or bandwidth to follow it on a day-to-day basis
+ an easy way of bootstrapping it onto their
+ systems.</para>
</listitem>
<listitem>
- <para>To preserve a fixed reference point for the code in
- question, just in case we break something really badly
- later. (Although Subversion normally prevents anything
- horrible like this happening.)</para>
+ <para>To preserve a fixed reference point for the code
+ in question, just in case we break something really
+ badly later. (Although Subversion normally prevents
+ anything horrible like this happening.)</para>
</listitem>
<listitem>
- <para>To ensure that all new features and fixes in need of
- testing have the greatest possible number of potential
- testers.</para>
+ <para>To ensure that all new features and fixes in need
+ of testing have the greatest possible number of
+ potential testers.</para>
</listitem>
</itemizedlist>
<para>No claims are made that any
<emphasis>-CURRENT</emphasis> snapshot can be considered
<quote>production quality</quote> for any purpose. If you
- want to run a stable and fully tested system, you will have
- to stick to full releases, or use the
+ want to run a stable and fully tested system, you will
+ have to stick to full releases, or use the
<emphasis>-STABLE</emphasis> snapshots.</para>
- <para>Snapshot releases are directly available from <link xlink:href="&url.base;/snapshots/">snapshot</link>.</para>
+ <para>Snapshot releases are directly available from <link
+ xlink:href="&url.base;/snapshots/">snapshot</link>.</para>
<para>Official snapshots are generated on a regular
basis for all actively developed branches.</para>
@@ -434,30 +455,38 @@
</question>
<answer>
- <para>Back when &os; 2.0.5 was released, &os; development
- branched in two. One branch was named <link xlink:href="&url.books.handbook;/current-stable.html#stable">-STABLE</link>,
- one <link xlink:href="&url.books.handbook;/current-stable.html#current">-CURRENT</link>.
+ <para>Back when &os; 2.0.5 was released, &os;
+ development branched in two. One branch was named <link
+ xlink:href="&url.books.handbook;/current-stable.html#stable">-STABLE</link>,
+ one <link
+ xlink:href="&url.books.handbook;/current-stable.html#current">-CURRENT</link>.
<emphasis>&os;-STABLE</emphasis> is intended for Internet
- Service Providers and other commercial enterprises for whom
- sudden shifts or experimental features are quite
+ Service Providers and other commercial enterprises for
+ whom sudden shifts or experimental features are quite
undesirable. It receives only well-tested bug fixes and
other small incremental enhancements.
<emphasis>&os;-CURRENT</emphasis>, on the other hand, has
been one unbroken line since 2.0 was released, leading
- towards &rel.current;-RELEASE and beyond. For more detailed
- information on branches see <quote><link xlink:href="&url.articles.releng;/release-proc.html#rel-branch">&os; Release Engineering: Creating the Release Branch</link></quote>,
- the status of the branches and the upcoming release schedule
- can be found on the <link xlink:href="http://www.FreeBSD.org/releng">Release Engineering Information</link> page.</para>
+ towards &rel.current;-RELEASE and beyond. For more
+ detailed information on branches see <quote><link
+ xlink:href="&url.articles.releng;/release-proc.html#rel-branch">&os;
+ Release Engineering: Creating the Release
+ Branch</link></quote>, the status of the branches and
+ the upcoming release schedule can be found on the <link
+ xlink:href="http://www.FreeBSD.org/releng">Release
+ Engineering Information</link> page.</para>
<para>&rel.current;-STABLE is the actively developed
- <emphasis>-STABLE</emphasis> branch. The latest release on
- the &rel.current;-STABLE branch is &rel.current;-RELEASE,
- which was released in &rel.current.date;.</para>
+ <emphasis>-STABLE</emphasis> branch. The latest release
+ on the &rel.current;-STABLE branch is
+ &rel.current;-RELEASE, which was released in
+ &rel.current.date;.</para>
<para>The &rel.head; branch is the actively developed
<emphasis>-CURRENT</emphasis> branch toward the next
- generation of &os;. See <link linkend="current">What is &os;-CURRENT?</link> for more
- information on this branch.</para>
+ generation of &os;. See <link linkend="current">What is
+ &os;-CURRENT?</link> for more information on this
+ branch.</para>
</answer>
</qandaentry>
@@ -468,24 +497,26 @@
<answer>
<para>The &a.re; releases a new major version of &os; about
- every 18 months and a new minor version about every 8 months,
- on average. Release dates are announced well in advance, so
- that the people working on the system know when their
- projects need to be finished and tested. A testing period
- precedes each release, to ensure that the addition
- of new features does not compromise the stability of the
- release. Many users regard this caution as one of the best
- things about &os;, even though waiting for all the latest
- goodies to reach <emphasis>-STABLE</emphasis> can be a
- little frustrating.</para>
+ every 18 months and a new minor version about every 8
+ months, on average. Release dates are announced well in
+ advance, so that the people working on the system know
+ when their projects need to be finished and tested. A
+ testing period precedes each release, to ensure that the
+ addition of new features does not compromise the stability
+ of the release. Many users regard this caution as one of
+ the best things about &os;, even though waiting for all
+ the latest goodies to reach <emphasis>-STABLE</emphasis>
+ can be a little frustrating.</para>
<para>More information on the release engineering process
- (including a schedule of upcoming releases) can be found on
- the <link xlink:href="http://www.FreeBSD.org/releng/index.html">release engineering</link>
- pages on the &os; Web site.</para>
+ (including a schedule of upcoming releases) can be found
+ on the <link
+ xlink:href="http://www.FreeBSD.org/releng/index.html">release
+ engineering</link> pages on the &os; Web site.</para>
<para>For people who need or want a little more excitement,
- binary snapshots are made weekly as discussed above.</para>
+ binary snapshots are made weekly as discussed
+ above.</para>
</answer>
</qandaentry>
@@ -497,16 +528,18 @@
<answer>
<para>The key decisions concerning the &os; project, such as
the overall direction of the project and who is allowed to
- add code to the source tree, are made by a <link xlink:href="&url.base;/administration.html#t-core">core team</link> of
- 9 people. There is a much larger team of more than 350
- <link xlink:href="&url.articles.contributors;/article.html#staff-committers">committers</link>
+ add code to the source tree, are made by a <link
+ xlink:href="&url.base;/administration.html#t-core">core
+ team</link> of 9 people. There is a much larger team of
+ more than 350 <link
+ xlink:href="&url.articles.contributors;/article.html#staff-committers">committers</link>
who are authorized to make changes directly to the &os;
source tree.</para>
<para>However, most non-trivial changes are discussed in
- advance in the <link linkend="mailing">mailing lists</link>,
- and there are no restrictions on who may take part in the
- discussion.</para>
+ advance in the <link linkend="mailing">mailing
+ lists</link>, and there are no restrictions on who may
+ take part in the discussion.</para>
</answer>
</qandaentry>
@@ -517,29 +550,40 @@
<answer>
<para>Every significant release of &os; is available via
- anonymous FTP from the <link xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/"> &os; FTP site</link>:</para>
+ anonymous FTP from the <link
+ xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/"> &os;
+ FTP site</link>:</para>
<itemizedlist>
<listitem>
- <para>The latest &rel.stable; release, &rel.current;-RELEASE
- can be found in the <link xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/i386/&rel.current;-RELEASE/">&rel.current;-RELEASE directory</link>.</para>
+ <para>The latest &rel.stable; release,
+ &rel.current;-RELEASE can be found in the <link
+ xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/i386/&rel.current;-RELEASE/">&rel.current;-RELEASE
+ directory</link>.</para>
</listitem>
<listitem>
- <para><link xlink:href="&url.base;/snapshots/"> Snapshot</link>
- releases are made monthly for the <link linkend="current">-CURRENT</link> and <link linkend="stable">-STABLE</link> branch, these being of
- service purely to bleeding-edge testers and
+ <para><link
+ xlink:href="&url.base;/snapshots/">Snapshot</link>
+ releases are made monthly for the <link
+ linkend="current">-CURRENT</link> and <link
+ linkend="stable">-STABLE</link> branch, these being
+ of service purely to bleeding-edge testers and
developers.</para>
</listitem>
<listitem>
- <para>The latest &rel2.stable; release, &rel2.current;-RELEASE
- can be found in the <link xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel2.current;-RELEASE/">&rel2.current;-RELEASE directory</link>.</para>
+ <para>The latest &rel2.stable; release,
+ &rel2.current;-RELEASE can be found in the <link
+ xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel2.current;-RELEASE/">&rel2.current;-RELEASE
+ directory</link>.</para>
</listitem>
</itemizedlist>
<para>Information about obtaining &os; on CD, DVD, and other
- media can be found in <link xlink:href="&url.books.handbook;/mirrors.html">the Handbook</link>.</para>
+ media can be found in <link
+ xlink:href="&url.books.handbook;/mirrors.html">the
+ Handbook</link>.</para>
</answer>
</qandaentry>
@@ -549,18 +593,22 @@
</question>
<answer>
- <para>The Problem Report database of all user change requests
- may be queried by using our web-based PR <link xlink:href="http://www.FreeBSD.org/cgi/query-pr.cgi?query">query</link>
+ <para>The Problem Report database of all user change
+ requests may be queried by using our web-based PR <link
+ xlink:href="http://www.FreeBSD.org/cgi/query-pr.cgi?query">query</link>
interface.</para>
<para>The &man.send-pr.1; command can be used to submit
problem reports and change requests via electronic mail.
- Alternatively, the <link xlink:href="http://www.freebsd.org/send-pr.html">web-based problem report submission interface</link>
- can be used to submit problem reports through a web
- browser.</para>
-
- <para>Before submitting a problem report, please read <link xlink:href="&url.articles.problem-reports;/article.html">Writing &os; Problem Reports</link>,
- an article on how to write good problem reports.</para>
+ Alternatively, the <link
+ xlink:href="http://www.freebsd.org/send-pr.html">web-based
+ problem report submission interface</link> can be used
+ to submit problem reports through a web browser.</para>
+
+ <para>Before submitting a problem report, please read <link
+ xlink:href="&url.articles.problem-reports;/article.html">Writing
+ &os; Problem Reports</link>, an article on how to write
+ good problem reports.</para>
</answer>
</qandaentry>
</qandaset>
@@ -577,22 +625,28 @@
<answer>
<para>The project produces a wide range of documentation,
- available online from this link: <uri xlink:href="http://www.FreeBSD.org/docs.html">http://www.FreeBSD.org/docs.html</uri>. In addition, <link linkend="bibliography">the Bibliography</link> at the end of this
- FAQ, and <link xlink:href="&url.books.handbook;/bibliography.html">the one in the Handbook</link>
- reference other recommended books.</para>
+ available online from this link: <uri
+ xlink:href="http://www.FreeBSD.org/docs.html">http://www.FreeBSD.org/docs.html</uri>.
+ In addition, <link
+ linkend="bibliography">the Bibliography</link> at the
+ end of this FAQ, and <link
+ xlink:href="&url.books.handbook;/bibliography.html">the
+ one in the Handbook</link> reference other recommended
+ books.</para>
</answer>
</qandaentry>
<qandaentry>
<question xml:id="doc-formats">
- <para>Is the documentation available in other formats, such as
- plain text (ASCII), or &postscript;?</para>
+ <para>Is the documentation available in other formats, such
+ as plain text (ASCII), or &postscript;?</para>
</question>
<answer>
<para>Yes. The documentation is available in a number of
different formats and compression schemes on the &os; FTP
- site, in the <link xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/">/pub/FreeBSD/doc/</link>
+ site, in the <link
+ xlink:href="ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/">/pub/FreeBSD/doc/</link>
directory.</para>
<para>The documentation is categorized in a number of
@@ -600,8 +654,9 @@
<itemizedlist>
<listitem>
- <para>The document's name, such as <literal>faq</literal>,
- or <literal>handbook</literal>.</para>
+ <para>The document's name, such as
+ <literal>faq</literal>, or
+ <literal>handbook</literal>.</para>
</listitem>
<listitem>
@@ -685,7 +740,8 @@
<row>
<entry><literal>mn_MN.UTF-8</literal></entry>
- <entry>Mongolian (Mongolia, UTF-8 encoding)</entry>
+ <entry>Mongolian (Mongolia, UTF-8
+ encoding)</entry>
</row>
<row>
@@ -740,7 +796,8 @@
<row>
<entry><literal>zh_TW.Big5</literal></entry>
- <entry>Traditional Chinese (Taiwan, Big5 encoding)</entry>
+ <entry>Traditional Chinese (Taiwan, Big5
+ encoding)</entry>
</row>
</tbody>
</tgroup>
@@ -753,16 +810,17 @@
</listitem>
<listitem>
- <para>The document's format. We produce the documentation
- in a number of different output formats. Each format
- has its own advantages and disadvantages. Some formats
- are better suited for online reading, while others are
- meant to be aesthetically pleasing when printed on
- paper. Having the documentation available in any of
- these formats ensures that our readers will be able to
- read the parts they are interested in, either on their
- monitor, or on paper after printing the documents. The
- currently available formats are:</para>
+ <para>The document's format. We produce the
+ documentation in a number of different output formats.
+ Each format has its own advantages and disadvantages.
+ Some formats are better suited for online reading,
+ while others are meant to be aesthetically pleasing
+ when printed on paper. Having the documentation
+ available in any of these formats ensures that our
+ readers will be able to read the parts they are
+ interested in, either on their monitor, or on paper
+ after printing the documents. The currently available
+ formats are:</para>
<informaltable frame="none" pgwide="1">
<tgroup cols="2">
@@ -818,8 +876,10 @@
<note>
<para>Page numbers are not automatically updated when
- loading Rich Text Format into Word. Press <keycombo action="simul"><keycap>Ctrl</keycap><keycap>A</keycap></keycombo>,
- <keycombo action="simul"><keycap>Ctrl</keycap><keycap>End</keycap></keycombo>,
+ loading Rich Text Format into Word. Press <keycombo
+ action="simul"><keycap>Ctrl</keycap><keycap>A</keycap></keycombo>,
+ <keycombo
+ action="simul"><keycap>Ctrl</keycap><keycap>End</keycap></keycombo>,
<keycap>F9</keycap> after loading the document, to
update the page numbers.</para>
</note>
@@ -831,17 +891,17 @@
<orderedlist>
<listitem>
<para>Where the format is
- <literal>html-split</literal>, the files are bundled
- up using &man.tar.1;. The resulting
+ <literal>html-split</literal>, the files are
+ bundled up using &man.tar.1;. The resulting
<filename>.tar</filename> file is then compressed
using the compression schemes detailed in the next
point.</para>
</listitem>
<listitem>
- <para>All the other formats generate one file, called
- <filename>type.format</filename>
- (i.e., <filename>article.pdf</filename>,
+ <para>All the other formats generate one file,
+ called <filename>type.format</filename> (i.e.,
+ <filename>article.pdf</filename>,
<filename>book.html</filename>, and so on).</para>
<para>These files are then compressed using either
@@ -851,24 +911,25 @@
files.</para>
<para>So the &postscript; version of the Handbook,
- compressed using <literal>bzip2</literal> will be stored in a file
- called <filename>book.ps.bz2</filename> in the
+ compressed using <literal>bzip2</literal> will be
+ stored in a file called
+ <filename>book.ps.bz2</filename> in the
<filename>handbook/</filename> directory.</para>
</listitem>
</orderedlist>
</listitem>
</itemizedlist>
- <para>After choosing the format and compression mechanism that
- you want to download, you will have to download the compressed
- files yourself, uncompress them, and then copy the
- appropriate documents into place.</para>
+ <para>After choosing the format and compression mechanism
+ that you want to download, you will have to download the
+ compressed files yourself, uncompress them, and then copy
+ the appropriate documents into place.</para>
<para>For example, the split HTML version of the FAQ,
compressed using &man.bzip2.1;, can be found in
<filename>doc/en_US.ISO8859-1/books/faq/book.html-split.tar.bz2</filename>
- To download and uncompress that file you would have
- to do this:</para>
+ To download and uncompress that file you would have to do
+ this:</para>
<screen>&prompt.root; <userinput>fetch ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/en_US.ISO8859-1/books/faq/book.html-split.tar.bz2</userinput>
&prompt.root; <userinput>tar xvf book.html-split.tar.bz2</userinput></screen>
@@ -887,13 +948,16 @@
<qandaentry>
<question xml:id="mailing">
- <para>Where do I find info on the &os; mailing lists?
- What &os; news groups are available?</para>
+ <para>Where do I find info on the &os; mailing lists? What
+ &os; news groups are available?</para>
</question>
<answer>
- <para>You can find full information in the <link xlink:href="&url.books.handbook;/eresources.html#eresources-mail">Handbook entry on mailing-lists</link>
- and the <link xlink:href="&url.books.handbook;/eresources-news.html">Handbook entry on newsgroups</link>.</para>
+ <para>You can find full information in the <link
+ xlink:href="&url.books.handbook;/eresources.html#eresources-mail">Handbook
+ entry on mailing-lists</link> and the <link
+ xlink:href="&url.books.handbook;/eresources-news.html">Handbook
+ entry on newsgroups</link>.</para>
</answer>
</qandaentry>
@@ -909,70 +973,79 @@
<itemizedlist>
<listitem>
- <para>Channel <literal>#FreeBSDhelp</literal> on <link xlink:href="http://www.efnet.org/index.php">EFNet</link> is
- a channel dedicated to helping &os; users. They are
- much more sympathetic to questions than
+ <para>Channel <literal>#FreeBSDhelp</literal> on <link
+ xlink:href="http://www.efnet.org/index.php">EFNet</link>
+ is a channel dedicated to helping &os; users. They
+ are much more sympathetic to questions than
<literal>#FreeBSD</literal> is.</para>
</listitem>
<listitem>
- <para>Channel <literal>#FreeBSD</literal> on <link xlink:href="http://freenode.net/">Freenode</link> is a
- general help channel with many users at any time.
- The conversations have been known to run off-topic for a
- while, but priority is given to users with &os;
- questions. We are good about helping you understand the
- basics, referring to the Handbook whenever possible, and
- directing you where to learn more about the topic you
- need help with. We are a primarily English speaking
- channel, though we have users from all over the world.
- If you would like to speak in your native language, try
- to ask the question in English and then relocate to
- another channel
- <literal>##freebsd-lang</literal>
- as appropriate.</para>
+ <para>Channel <literal>#FreeBSD</literal> on <link
+ xlink:href="http://freenode.net/">Freenode</link> is
+ a general help channel with many users at any time.
+ The conversations have been known to run off-topic for
+ a while, but priority is given to users with &os;
+ questions. We are good about helping you understand
+ the basics, referring to the Handbook whenever
+ possible, and directing you where to learn more about
+ the topic you need help with. We are a primarily
+ English speaking channel, though we have users from
+ all over the world. If you would like to speak in
+ your native language, try to ask the question in
+ English and then relocate to another channel
+ <literal>##freebsd-lang</literal> as
+ appropriate.</para>
</listitem>
<listitem>
- <para>Channel <literal>#FreeBSD</literal> on <link xlink:href="http://www.dal.net/">DALNET</link> is available at
- <systemitem>irc.dal.net</systemitem> in the US and
- <systemitem>irc.eu.dal.net</systemitem> in Europe.</para>
+ <para>Channel <literal>#FreeBSD</literal> on <link
+ xlink:href="http://www.dal.net/">DALNET</link> is
+ available at <systemitem>irc.dal.net</systemitem> in
+ the US and <systemitem>irc.eu.dal.net</systemitem> in
+ Europe.</para>
</listitem>
<listitem>
- <para>Channel <literal>#FreeBSD</literal> on <link xlink:href="http://www.undernet.org/">UNDERNET</link> is
- available at <systemitem>us.undernet.org</systemitem> in the US
- and <systemitem>eu.undernet.org</systemitem> in Europe. Since
- it is a help channel, be prepared to read the documents
- you are referred to.</para>
+ <para>Channel <literal>#FreeBSD</literal> on <link
+ xlink:href="http://www.undernet.org/">UNDERNET</link>
+ is available at
+ <systemitem>us.undernet.org</systemitem> in the US and
+ <systemitem>eu.undernet.org</systemitem> in Europe.
+ Since it is a help channel, be prepared to read the
+ documents you are referred to.</para>
</listitem>
<listitem>
- <para>Channel <literal>#FreeBSD</literal> on
- <link xlink:href="http://www.rusnet.org.ru/">RUSNET</link>
- is a russian-language oriented channel dedicated
- to helping &os; users. This is also good place
- for non-technical discussions.</para>
+ <para>Channel <literal>#FreeBSD</literal> on <link
+ xlink:href="http://www.rusnet.org.ru/">RUSNET</link>
+ is a russian-language oriented channel dedicated to
+ helping &os; users. This is also good place for
+ non-technical discussions.</para>
</listitem>
<listitem>
- <para>Channel <literal>#bsdchat</literal> on <link xlink:href="http://freenode.net/">Freenode</link> is a
- Traditional-Chinese (UTF-8 encoding) language oriented
- channel dedicated to helping &os; users. This is also
- good place for non-technical discussions.</para>
+ <para>Channel <literal>#bsdchat</literal> on <link
+ xlink:href="http://freenode.net/">Freenode</link> is
+ a Traditional-Chinese (UTF-8 encoding) language
+ oriented channel dedicated to helping &os; users.
+ This is also good place for non-technical
+ discussions.</para>
</listitem>
</itemizedlist>
- <para>The &os; wiki has a <link xlink:href="http://wiki.freebsd.org/IrcChannels">good list</link>
- of IRC channels.</para>
+ <para>The &os; wiki has a <link
+ xlink:href="http://wiki.freebsd.org/IrcChannels">good
+ list</link> of IRC channels.</para>
<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>
+ 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>
@@ -981,7 +1054,8 @@
<para>Are there any web based forums to discuss &os;?</para>
</question>
<answer>
- <para>The official &os; forums are located at <link xlink:href="http://forums.FreeBSD.org/">http://forums.FreeBSD.org/</link>.</para>
+ <para>The official &os; forums are located at <link
+ xlink:href="http://forums.FreeBSD.org/">http://forums.FreeBSD.org/</link>.</para>
</answer>
</qandaentry>
@@ -992,14 +1066,21 @@
*** DIFF OUTPUT TRUNCATED AT 1000 LINES ***
More information about the svn-doc-all
mailing list