From owner-svn-doc-head@FreeBSD.ORG Wed Feb 5 23:11:37 2014 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 17C4574C; Wed, 5 Feb 2014 23:11:37 +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 E8B3015EE; Wed, 5 Feb 2014 23:11:36 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s15NBauq096563; Wed, 5 Feb 2014 23:11:36 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s15NBaiI096561; Wed, 5 Feb 2014 23:11:36 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201402052311.s15NBaiI096561@svn.freebsd.org> From: Dru Lavigne Date: Wed, 5 Feb 2014 23:11:36 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r43794 - 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: Wed, 05 Feb 2014 23:11:37 -0000 Author: dru Date: Wed Feb 5 23:11:36 2014 New Revision: 43794 URL: http://svnweb.freebsd.org/changeset/doc/43794 Log: Initial shuffle in this section, much more to come in order to improve its flow. Place pre-build tasks at beginning and format as a procedure. 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 Wed Feb 5 20:59:58 2014 (r43793) +++ head/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.xml Wed Feb 5 23:11:36 2014 (r43794) @@ -1437,46 +1437,53 @@ before running "/usr/sbin/freebsd-update Once the local source tree is synchronized against a particular version of &os; such as &os.stable; or &os.current;, - the source tree can be used to rebuild the system. - - - Make a Backup - - It cannot be stressed enough how important it is to make a + the source tree can be used to rebuild the system. This process + is known as rebuilding world. + + Before rebuilding world, be sure to + perform the following tasks: + + + Perform These Tasks Before Building World + + + Backup all important data to another system or removable + media, verify the integrity of the backup, and have a bootable + installation media at hand. It cannot be + stressed enough how important it is to make a backup of the system before rebuilding - the system. While rebuilding the world is an easy task, there + the system. While rebuilding world is an easy task, there will inevitably be times when mistakes in the source tree - render the system unbootable. - - Create and verify a backup and have a bootable - installation media at hand. You will probably never have - to use it, but it is better to be safe than sorry! - - - - Subscribe to the Right Mailing List + render the system unbootable. You will probably never have + to use the backup, but it is better to be safe than sorry! + + mailing list - The &os.stable; and &os.current; branches are, by their - nature, in development. People that - contribute to &os; are human, and mistakes occasionally - happen. - - Sometimes these mistakes can be quite harmless, just - causing the system to print a new diagnostic warning. Or the - change may be catastrophic, and render the system unbootable - or destroy file systems. - - When problems occur, a heads up is - posted to the appropriate mailing list, explaining the nature - of the problem and which systems it affects. An all - clear announcement is posted when the problem has - been solved. - - Users who track &os.stable; or &os.current; and do - not read &a.stable; or &a.current; respectively, are asking - for trouble. - + Review the recent &a.stable.name; or &a.current.name; entries, depending + upon the branch being tracked. Be aware of any known + problems and which systems are affected. If a known issue + affects the version of synchronized code, wait for an all + clear announcement to be posted stating that the problem has + been solved. Resynchronize the sources to ensure that the + local version of source has the needed fix. + + + + Read + /usr/src/UPDATING for any pre-buildworld + steps necessary for that version of the source. This file contains + important information about potential problems and may specify + the order to run certain commands. Many upgrades require + specific additional steps such as renaming or deleting + specific files prior to installworld. These will be listed + at the end of this file where the currently recommended upgrade sequence + is explicitly spelled out. If + UPDATING contradicts any steps in + this chapter, the instructions in UPDATING take + precedence and should be followed. + + Do Not Use <command>make world</command> @@ -1492,10 +1499,8 @@ before running "/usr/sbin/freebsd-update The Canonical Way to Update Your System - Before updating the system, read - /usr/src/UPDATING for any pre-buildworld - steps necessary for that version of the sources. Then, use - the procedure outlined here. + Once the above tasks have been performed, use + the procedure outlined here to update the system. These upgrade steps assume an upgrade from an older &os; version, consisting of an old compiler, old kernel, @@ -1685,13 +1690,6 @@ before running "/usr/sbin/freebsd-update When upgrading across major releases, people who do not follow this procedure should expect some problems. - It is also worth noting that many upgrades may require - specific additional steps such as renaming or deleting - specific files prior to installworld. Read - /usr/src/UPDATING carefully, especially - at the end, where the currently recommended upgrade sequence - is explicitly spelled out. - This procedure has evolved over time as the developers have found it impossible to completely prevent certain kinds of mismatch problems. Hopefully, the current procedure will @@ -1749,25 +1747,6 @@ before running "/usr/sbin/freebsd-update - Read <filename>/usr/src/UPDATING</filename> - - Before updating, read - /usr/src/UPDATING. This file contains - important information about potential problems and may specify - the order to run certain commands. If - UPDATING contradicts the procedure in - this section, UPDATING takes - precedence. - - - Reading UPDATING is not an - acceptable substitute for subscribing to the correct mailing - list. The two requirements are complementary, not - exclusive. - - - - Check <filename>/etc/make.conf</filename> @@ -1917,12 +1896,9 @@ before running "/usr/sbin/freebsd-update &prompt.root; rm -rf * - + Recompile the Base System - - Saving the Output - It is a good idea to save the output from running &man.make.1; to a file. If something goes wrong, a copy of the error message can be posted to one of the &os; mailing @@ -1948,10 +1924,6 @@ Script done, … /var/tmp or in root's home directory. - - - - Compile the Base System While in /usr/src type: @@ -2068,10 +2040,6 @@ Script done, … On a multi-CPU machine using an SMP configured kernel, try values between 6 and 10 and see how they speed things up. - - - - Timings rebuilding world @@ -2083,7 +2051,6 @@ Script done, … &os.stable; tree, with no tricks or shortcuts used during the process. A &os.current; tree will take somewhat longer. -