From owner-freebsd-stable Thu Jul 27 1: 8: 8 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id 3630E37C082 for ; Thu, 27 Jul 2000 01:08:02 -0700 (PDT) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id BAA24395; Thu, 27 Jul 2000 01:07:59 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <200007270807.BAA24395@freeway.dcfinc.com> Subject: Re: Innacurate statements in handbook about buildkernel In-Reply-To: from Bob K at "Jul 27, 0 00:08:35 am" To: melange@yip.org (Bob K) Date: Thu, 27 Jul 2000 01:07:59 -0700 (MST) Cc: freebsd-stable@FreeBSD.ORG Reply-To: chad@DCFinc.com Organization: DCF, Inc. X-O/S: FreeBSD 2.2.8-STABLE X-Unexpected: The Spanish Inquisition X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I recall, Bob K wrote: > No, no. You're all forgetting that on a system where the source, > libraries, and building tools never change, it will always build > consistently. It only comes into play when upgrading, but is merely one > other thing to do differently while doing so. But I was discussing the case of the folks that want to build a custom kernel, and catch bug fixes to the kernel sources without committing the disk space and effort to tracking the -STABLE tree. Most of the time they will be ok. But in some cases, they will be forced to choose between trying to SUP and build the whole source tree, or forgo the kernel bug fixes. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message