doc-el commit 984:52b8c459e0a7 - Whitespace only: major fixes in...
freebsd-doc-el at lists.hellug.gr
freebsd-doc-el at lists.hellug.gr
Sun Nov 2 18:33:24 EET 2008
changeset: 984:52b8c459e0a7
user: Manolis Kiagias <sonicy at otenet.gr>
date: 2008-10-31 23:39 +0200
details: http://hg.hellug.gr/freebsd/doc-el/?cmd=changeset;node=52b8c459e0a7
description:
Whitespace only: major fixes in english cutting-edge chapter
diffstat:
1 file changed, 538 insertions(+), 518 deletions(-)
en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml | 1056 +++++++-------
diffs (truncated from 1704 to 300 lines):
diff -r 465a3cfa2e00 -r 52b8c459e0a7 en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml
--- a/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml Fri Oct 31 22:28:09 2008 +0200
+++ b/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml Fri Oct 31 23:39:43 2008 +0200
@@ -14,20 +14,24 @@
</author>
<!-- Mar 2000 -->
</authorgroup>
+
<authorgroup>
<author>
<firstname>Jordan</firstname>
<surname>Hubbard</surname>
<contrib>Original work by </contrib>
</author>
+
<author>
<firstname>Poul-Henning</firstname>
<surname>Kamp</surname>
</author>
+
<author>
<firstname>John</firstname>
<surname>Polstra</surname>
</author>
+
<author>
<firstname>Nik</firstname>
<surname>Clayton</surname>
@@ -52,28 +56,36 @@
<para>After reading this chapter, you will know:</para>
<itemizedlist>
- <listitem><para>The difference between the two development
- branches: &os.stable; and &os.current;.</para>
+ <listitem>
+ <para>The difference between the two development
+ branches: &os.stable; and &os.current;.</para>
</listitem>
- <listitem><para>How to keep your system up to date with
+
+ <listitem>
+ <para>How to keep your system up to date with
<application>CVSup</application>,
<application>CVS</application>, or
<application>CTM</application>.</para>
</listitem>
- <listitem><para>How to rebuild and reinstall the entire base
- system with <command>make buildworld</command> (etc).</para>
+
+ <listitem>
+ <para>How to rebuild and reinstall the entire base
+ system with <command>make buildworld</command> (etc).</para>
</listitem>
-
</itemizedlist>
<para>Before reading this chapter, you should:</para>
<itemizedlist>
- <listitem><para>Properly set up your network connection (<xref
- linkend="advanced-networking">).</para>
+ <listitem>
+ <para>Properly set up your network connection (<xref
+ linkend="advanced-networking">).</para>
</listitem>
- <listitem><para>Know how to install additional third-party
- software (<xref linkend="ports">).</para></listitem>
+
+ <listitem>
+ <para>Know how to install additional third-party
+ software (<xref linkend="ports">).</para>
+ </listitem>
</itemizedlist>
<note>
@@ -85,7 +97,7 @@
with &man.csup.1;, which is now part of the base system.</para>
</note>
</sect1>
-
+
<sect1 id="current-stable">
<title>&os.current; vs. &os.stable;</title>
<indexterm><primary>-CURRENT</primary></indexterm>
@@ -104,7 +116,7 @@
&os.current; users are expected to have a high degree of
technical skill, and should be capable of solving difficult
system problems on their own. If you are new to &os;, think
- twice before installing it. </para>
+ twice before installing it.</para>
<sect3>
<title>What Is &os.current;?</title>
@@ -193,22 +205,22 @@
<sect3>
<title>Using &os.current;</title>
-
+
<indexterm>
<primary>-CURRENT</primary>
<secondary>using</secondary>
</indexterm>
<orderedlist>
<listitem>
- <para>Join the &a.current.name; and the &a.svn-src-head.name; lists. This is not
- just a good idea, it is <emphasis>essential</emphasis>. If
- you are not on the <emphasis>&a.current.name;</emphasis> list,
- you will not see the comments that people are
- making about the current state of the system and thus will
- probably end up stumbling over a lot of problems that others
- have already found and solved. Even more importantly, you
- will miss out on important bulletins which may be critical
- to your system's continued health.</para>
+ <para>Join the &a.current.name; and the &a.svn-src-head.name;
+ lists. This is not just a good idea, it is
+ <emphasis>essential</emphasis>. If you are not on the
+ <emphasis>&a.current.name;</emphasis> list, you will not see
+ the comments that people are making about the current state of
+ the system and thus will probably end up stumbling over a lot
+ of problems that others have already found and solved. Even
+ more importantly, you will miss out on important bulletins
+ which may be critical to your system's continued health.</para>
<para>The &a.svn-src-head.name; list will allow you to see the
commit log entry for each change as it is made, along with
@@ -227,29 +239,32 @@
site</link>. You can do this in one of two ways:</para>
<orderedlist>
- <indexterm>
- <primary><command>cvsup</command></primary>
- </indexterm>
- <indexterm>
- <primary><command>cron</command></primary>
- </indexterm>
- <indexterm>
- <primary>-CURRENT</primary>
+ <indexterm>
+ <primary><command>cvsup</command></primary>
+ </indexterm>
+ <indexterm>
+ <primary><command>cron</command></primary>
+ </indexterm>
+ <indexterm>
+ <primary>-CURRENT</primary>
<secondary>Syncing with <application>CVSup</application></secondary>
</indexterm>
<listitem>
<para>Use the <link linkend="cvsup">cvsup</link> program
- with the <filename>supfile</filename> named <filename>standard-supfile</filename>
- available from <filename>/usr/share/examples/cvsup</filename>.
- This is the most recommended
- method, since it allows you to grab the entire
- collection once and then only what has changed from then
- on. Many people run <command>cvsup</command> from
- <command>cron</command> and keep their
- sources up-to-date automatically. You have to
- customize the sample <filename>supfile</filename> above, and configure
- <link linkend="cvsup">cvsup</link> for your environment.</para>
+ with the <filename>supfile</filename> named
+ <filename>standard-supfile</filename>
+ available from
+ <filename>/usr/share/examples/cvsup</filename>.
+ This is the most recommended method, since it allows you to
+ grab the entire collection once and then only what has
+ changed from then on. Many people run
+ <command>cvsup</command> from <command>cron</command> and
+ keep their sources up-to-date automatically. You have to
+ customize the sample <filename>supfile</filename> above,
+ and configure <link
+ linkend="cvsup">cvsup</link> for your environment.</para>
+
<note>
<para>The sample <filename>standard-supfile</filename> is
intended for tracking a specific security branch of
@@ -268,22 +283,22 @@
</note>
</listitem>
- <indexterm>
- <primary>-CURRENT</primary>
+ <indexterm>
+ <primary>-CURRENT</primary>
<secondary>Syncing with CTM</secondary>
</indexterm>
<listitem>
<para>Use the <application><link
linkend="ctm">CTM</link></application> facility. If you
have very bad connectivity (high price connections or
- only email access) <application>CTM</application> is an option.
- However, it is a lot of hassle and can give you broken files.
- This leads to it being rarely used, which again increases
- the chance of it not working for fairly long periods of
- time. We recommend using
+ only email access) <application>CTM</application> is an
+ option. However, it is a lot of hassle and can give you
+ broken files. This leads to it being rarely used, which
+ again increases the chance of it not working for fairly
+ long periods of time. We recommend using
<application><link linkend="cvsup">CVSup</link></application>
- for anybody with a 9600 bps modem or faster connection.
- </para>
+ for anybody with a 9600 bps modem or faster
+ connection.</para>
</listitem>
</orderedlist>
</listitem>
@@ -303,13 +318,14 @@
<para>Before compiling &os.current;, read the
<filename>Makefile</filename> in <filename>/usr/src</filename>
carefully. You should at least <link
- linkend="makeworld">install a new kernel and rebuild the world</link> the first time through
+ linkend="makeworld">install a new kernel and rebuild the
+ world</link> the first time through
as part of the upgrading process. Reading the &a.current;
- and <filename>/usr/src/UPDATING</filename> will keep you up-to-date on other bootstrapping procedures
- that sometimes become necessary as we move toward the next
- release.</para>
+ and <filename>/usr/src/UPDATING</filename> will keep you
+ up-to-date on other bootstrapping procedures that sometimes
+ become necessary as we move toward the next release.</para>
</listitem>
-
+
<listitem>
<para>Be active! If you are running &os.current;, we want
to know what you have to say about it, especially if you
@@ -320,7 +336,7 @@
</orderedlist>
</sect3>
</sect2>
-
+
<sect2 id="stable">
<title>Staying Stable with &os;</title>
@@ -332,8 +348,8 @@
are made. Changes go into this branch at a different pace, and
with the general assumption that they have first gone into
&os.current; for testing. This is <emphasis>still</emphasis>
- a development branch, however, and this means that at any given time,
- the sources for &os.stable; may or may not be suitable for any
+ a development branch, however, and this means that at any given
+ time, the sources for &os.stable; may or may not be suitable for any
particular purpose. It is simply another engineering development
track, not a resource for end-users.</para>
</sect3>
@@ -342,21 +358,21 @@
<title>Who Needs &os.stable;?</title>
<para>If you are interested in tracking or contributing to the
- FreeBSD development process, especially as it relates to the
+ FreeBSD development process, especially as it relates to the
next <quote>point</quote> release of FreeBSD, then you should
consider following &os.stable;.</para>
<para>While it is true that security fixes also go into the
&os.stable; branch, you do not <emphasis>need</emphasis> to
- track &os.stable; to do this. Every security advisory for
+ track &os.stable; to do this. Every security advisory for
FreeBSD explains how to fix the problem for the releases it
affects
<footnote><para>That is not quite true. We can not continue to
- support old releases of FreeBSD forever, although we do
- support them for many years. For a complete description
- of the current security policy for old releases of
- FreeBSD, please see <ulink
- url="&url.base;/security/">http://www.FreeBSD.org/security/</ulink>.</para>
+ support old releases of FreeBSD forever, although we do
+ support them for many years. For a complete description
+ of the current security policy for old releases of
+ FreeBSD, please see <ulink
+ url="&url.base;/security/">http://www.FreeBSD.org/security/</ulink>.</para>
</footnote>
, and tracking an entire development branch just
for security reasons is likely to bring in a lot of unwanted
@@ -382,28 +398,27 @@
<sect3>
<title>Using &os.stable;</title>
-
+
<indexterm>
<primary>-STABLE</primary>
<secondary>using</secondary>
</indexterm>
<orderedlist>
<listitem>
- <para>Join the &a.stable.name; list. This will keep you informed of
- build-dependencies that may appear in &os.stable;
- or any other issues requiring
- special attention. Developers will also make announcements
- in this mailing list when they are contemplating some
- controversial fix or update, giving the users a chance to
- respond if they have any issues to raise concerning the
- proposed change.</para>
+ <para>Join the &a.stable.name; list. This will keep you informed
+ of build-dependencies that may appear in &os.stable;
More information about the Freebsd-doc-el
mailing list