From owner-svn-doc-all@freebsd.org Sun Oct 29 01:00:01 2017 Return-Path: Delivered-To: svn-doc-all@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ECD5AE53087; Sun, 29 Oct 2017 01:00:01 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C289A30CE; Sun, 29 Oct 2017 01:00:01 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id v9T101gG059591; Sun, 29 Oct 2017 01:00:01 GMT (envelope-from eadler@FreeBSD.org) Received: (from eadler@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id v9T101NZ059590; Sun, 29 Oct 2017 01:00:01 GMT (envelope-from eadler@FreeBSD.org) Message-Id: <201710290100.v9T101NZ059590@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: eadler set sender to eadler@FreeBSD.org using -f From: Eitan Adler Date: Sun, 29 Oct 2017 01:00:01 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r51152 - head/en_US.ISO8859-1/books/developers-handbook/kernelbuild X-SVN-Group: doc-head X-SVN-Commit-Author: eadler X-SVN-Commit-Paths: head/en_US.ISO8859-1/books/developers-handbook/kernelbuild X-SVN-Commit-Revision: 51152 X-SVN-Commit-Repository: doc MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Oct 2017 01:00:02 -0000 Author: eadler Date: Sun Oct 29 01:00:00 2017 New Revision: 51152 URL: https://svnweb.freebsd.org/changeset/doc/51152 Log: Move up the correct way to compile the kernel This makes the correct way more prominent. Also removes references to FreeBSD 4.x Reviewed By: allanjude Modified: head/en_US.ISO8859-1/books/developers-handbook/kernelbuild/chapter.xml Modified: head/en_US.ISO8859-1/books/developers-handbook/kernelbuild/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/developers-handbook/kernelbuild/chapter.xml Sat Oct 28 07:20:22 2017 (r51151) +++ head/en_US.ISO8859-1/books/developers-handbook/kernelbuild/chapter.xml Sun Oct 29 01:00:00 2017 (r51152) @@ -11,16 +11,12 @@ build process. To debug the &os; kernel it is required to be able to build one. There are two known ways to do so: - - - The Traditional Way - + The supported procedure to build and install a kernel + is documented in the + Building and + Installing a Custom Kernel chapter of the &os; + Handbook. - - The New Way - - - It is supposed that the reader of this chapter is familiar with the information described in the Building and @@ -31,18 +27,14 @@ - Building a Kernel the <quote>Traditional</quote> Way + Building the Faster but Brittle Way - Up to version 4.X of &os; this was the recommended way to - build a new kernel. It can still be used on newer versions - (instead of the buildkernel target of the toplevel - /usr/src/ makefiles). - Building the kernel this way may be useful when working on the + Building the kernel this way may be useful when working on + the kernel code and it may actually be faster than the - New procedure when only a single option or two were - tweaked in the kernel configuration file. On the other hand, it - might lead to unexpected kernel build breakage when used by - beginners on newer versions of &os;. + documented procedure when only a single option or two were + tweaked in the kernel configuration file. On the other hand, + it might lead to unexpected kernel build breakage. @@ -75,12 +67,4 @@ - - Building a Kernel the <quote>New</quote> Way - - This procedure is well supported and recommended under the - latest &os; releases and is documented in the Building and - Installing a Custom Kernel chapter of the &os; - Handbook. -