From owner-freebsd-stable Mon Jul 10 7:24:55 2000 Delivered-To: freebsd-stable@freebsd.org Received: from kci.kciLink.com (kci.kciLink.com [204.117.82.1]) by hub.freebsd.org (Postfix) with ESMTP id BE64C37B700; Mon, 10 Jul 2000 07:24:52 -0700 (PDT) (envelope-from khera@kciLink.com) Received: from onceler.kcilink.com (onceler.kciLink.com [204.117.82.2]) by kci.kciLink.com (Postfix) with ESMTP id 7F4D4E8D1; Mon, 10 Jul 2000 10:24:52 -0400 (EDT) Received: (from khera@localhost) by onceler.kcilink.com (8.9.3/8.9.3) id KAA15365; Mon, 10 Jul 2000 10:24:52 -0400 (EDT) (envelope-from khera@kci.kcilink.com) From: Vivek Khera MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14697.56500.375223.683195@onceler.kcilink.com> Date: Mon, 10 Jul 2000 10:24:52 -0400 (EDT) To: Jeff Wyman Cc: Kris Kennaway , stable@FreeBSD.ORG Subject: Re: HEADS UP! Always use the 'make buildkernel' target to make yer kernels In-Reply-To: References: <14697.55301.614418.390096@onceler.kcilink.com> X-Mailer: VM 6.72 under 21.1 (patch 9) "Canyonlands" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "JW" == Jeff Wyman writes: >> So you're saying that even after upgrading from 3.4 to 4.0 you should >> use make buildkernel? That seems counter to what has been discussed >> before, and is way non-BSD-ish. JW> The buildkernel process is used _during_ an upgrade. After the JW> new 4.0 kernel has been booted and appropriate changes have been made to JW> the system, kernels may be built successfully in the traditional way. Which is contrary to the "subject line says it all" opening sentence of the original message... thus the confusion. Thanks for the clarification. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-301-545-6996 GPG & MIME spoken here http://www.khera.org/~vivek/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message