From owner-svn-doc-head@FreeBSD.ORG Tue Feb 4 23:35:46 2014 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id F32A1848; Tue, 4 Feb 2014 23:35:45 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D6D751A58; Tue, 4 Feb 2014 23:35:45 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s14NZj6o016991; Tue, 4 Feb 2014 23:35:45 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s14NZj9j016990; Tue, 4 Feb 2014 23:35:45 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201402042335.s14NZj9j016990@svn.freebsd.org> From: Dru Lavigne Date: Tue, 4 Feb 2014 23:35:45 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43781 - head/en_US.ISO8859-1/books/handbook/cutting-edge X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Feb 2014 23:35:46 -0000 Author: dru Date: Tue Feb 4 23:35:45 2014 New Revision: 43781 URL: http://svnweb.freebsd.org/changeset/doc/43781 Log: Editorial pass through second 1/2 of this section. Sponsored by: iXsystems Modified: head/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.xml Tue Feb 4 22:40:49 2014 (r43780) +++ head/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.xml Tue Feb 4 23:35:45 2014 (r43781) @@ -1150,7 +1150,7 @@ before running "/usr/sbin/freebsd-update &os.current; is the bleeding edge of &os; development and &os.current; users are expected to have a high degree of technical skill. Less technical users who wish - to track a development brach should + to track a development branch should track &os.stable; instead. &os.current; is the very latest source code for &os; and @@ -1210,8 +1210,8 @@ before running "/usr/sbin/freebsd-update &a.svn-src-head.name; lists. This is essential in order to see the comments that people are making about the current state - of the system and to receive important bulletins which - may be critical to the system's continued health. + of the system and to receive important bulletins about + the current state of &os.current;. The &a.svn-src-head.name; list records the commit log entry for each change as it is made, along with any @@ -1220,7 +1220,7 @@ before running "/usr/sbin/freebsd-update To join these lists, go to &a.mailman.lists.link;, click on the list to subscribe to, and follow the instructions. In order to track changes to the whole - source tree, subscribe to the &a.svn-src-all.name; + source tree, not just the changes to &os.current;, subscribe to the &a.svn-src-all.name; list. @@ -1256,10 +1256,9 @@ before running "/usr/sbin/freebsd-update -CURRENT compiling , read - /usr/src/Makefile very carefully. - Install a new kernel and - rebuild the world the first time through as part - of the upgrading process. Read the &a.current; and + /usr/src/Makefile very carefully and follow the instructions in + Rebuilding + "world". Read the &a.current; and /usr/src/UPDATING to stay up-to-date on other bootstrapping procedures that sometimes become necessary on the road to the next @@ -1280,49 +1279,34 @@ before running "/usr/sbin/freebsd-update &os.stable; is the development branch from which major releases 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 - still 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. + slower pace and with the general assumption that they + have first been tested in &os.current;. This is + still a development branch and, + at any given time, the sources for + &os.stable; may or may not be suitable for general use. + It is simply another engineering development + track, not a resource for end-users. Users who do not have the resources to perform + testing should instead run the most + recent release of &os;. Those interested in tracking or contributing to the - FreeBSD development process, especially as it relates to the - next point release of FreeBSD, should + &os; development process, especially as it relates to the + next release of &os;, should consider following &os.stable;. - While security fixes go into the &os.stable; branch, one - does not need to track &os.stable; to - receive security fixes. Every security advisory for &os; - explains how to fix the problem for the releases it - affects which are not yet EOL. - - - For a complete description of the current security - policy for old releases of FreeBSD, refer to http://www.FreeBSD.org/security/.. - While the &os.stable; branch should compile and run at - all times, this cannot be guaranteed. While code is - developed in &os.current; before including it in - &os.stable;, more people run &os.stable; than &os.current;, - so it is inevitable that bugs and corner cases will + all times, this cannot be guaranteed. Since + more people run &os.stable; than &os.current;, + it is inevitable that bugs and corner cases will sometimes be found in &os.stable; that were not apparent in - &os.current;. - - For these reasons, one should not - blindly track &os.stable;. It is particularly important not + &os.current;. For this reason, one should not + blindly track &os.stable;. It is particularly important not to update any production servers to &os.stable; without - first thoroughly testing the code in a development/testing + thoroughly testing the code in a development or testing environment. - Except for those users who have the resources to perform - testing, it is recommended that users instead run the most - recent release of FreeBSD, and use the binary update - mechanism to move from release to release. - + To track &os.stable;: + -STABLE using @@ -1330,7 +1314,7 @@ before running "/usr/sbin/freebsd-update Join the &a.stable.name; list in order to stay - informed of build-dependencies that may appear in + 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 @@ -1354,66 +1338,35 @@ before running "/usr/sbin/freebsd-update - To install a new system running monthly snapshots - built from &os.stable;, refer to To install a new &os.stable; system, install the most recent &os.stable; release from the + &os; mirror sites or use a monthly snapshot + built from &os.stable;. Refer to Snapshots - for more information. Alternatively, it is possible to - install the most recent &os.stable; release from the - mirror sites and follow - the instructions below to upgrade the system to the most - up-to-date &os.stable; source code. - - Several methods are available to upgrade from a &os; - mirror site on a system - already running a previous release of &os;: + for more information about snapshots. - - - Use svn + To compile or upgrade to an existing &os; + system to &os.stable;, use svn Subversion - to check out the desired development or - release branch. This is the recommended method, - providing access to &os; development as it occurs. - Branch names include head for the - current development head, and branches identified in + to check out the source for the desired + branch. + Branch names, such as stable/9, are identified in the release - engineering page, such as - stable/9 - - -STABLE - syncing with - Subversion - - or releng/9.2. URL prefixes for - Subversion checkout of - the base system are shown in Subversion mirror - sites. Because of the size of the - repository, it is recommended that only desired - subtrees be checked out. - - - - Consider using CTM + engineering page. CTM can be used -STABLE syncing with CTM - if you do not have a fast connection to - the Internet. - - + if a reliable Internet connection is not available. - Before compiling &os.stable; + Before compiling or upgrading to &os.stable; -STABLE compiling , read - /usr/src/Makefile carefully. - Install a new kernel and - rebuild the world the first time through as part - of the upgrading process. Read &a.stable; and + /usr/src/Makefile carefully and follow the instructions in + Rebuilding + "world". Read &a.stable; and /usr/src/UPDATING to keep up-to-date on other bootstrapping procedures that sometimes become necessary on the road to the next