From owner-freebsd-current@FreeBSD.ORG Tue Dec 9 19:07:49 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A961516A4CE; Tue, 9 Dec 2003 19:07:49 -0800 (PST) Received: from pit.databus.com (p70-227.acedsl.com [66.114.70.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 67BE843D2E; Tue, 9 Dec 2003 19:07:48 -0800 (PST) (envelope-from barney@pit.databus.com) Received: from pit.databus.com (localhost [127.0.0.1]) by pit.databus.com (8.12.10/8.12.10) with ESMTP id hBA37lRL047607; Tue, 9 Dec 2003 22:07:47 -0500 (EST) (envelope-from barney@pit.databus.com) Received: (from barney@localhost) by pit.databus.com (8.12.10/8.12.10/Submit) id hBA37lln047606; Tue, 9 Dec 2003 22:07:47 -0500 (EST) (envelope-from barney) Date: Tue, 9 Dec 2003 22:07:47 -0500 From: Barney Wolff To: "David O'Brien" Message-ID: <20031210030747.GA47528@pit.databus.com> References: <20031206171511.GA23158@SDF.LONESTAR.ORG> <20031207131034.X7085@carver.gumbysoft.com> <20031207230044.GA6169@SDF.LONESTAR.ORG> <20031208180718.GA49355@xor.obsecurity.org> <20031209181920.GD19222@dragon.nuxi.com> <20031209191252.GA39883@pit.databus.com> <20031210025930.GA34162@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031210025930.GA34162@dragon.nuxi.com> User-Agent: Mutt/1.4.1i X-Scanned-By: MIMEDefang 2.38 cc: freebsd-current@freebsd.org Subject: Re: last cvs Makefile.inc1 errors X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2003 03:07:49 -0000 On Tue, Dec 09, 2003 at 06:59:30PM -0800, David O'Brien wrote: > > > > I can think of two reasons: First, the separate steps make it possible > > to do make reinstallkernel when one does not want to overwrite kernel.old. > > Your sequence is: > make buildworld > make buildkernel > make reinstallkernel > make installworld > > which is not what we suggest in UPDATING and not what I have above. > Please stick to the exact sequence above. Well of course I normally do make installkernel. But when, as not infrequently with -current, the new kernel doesn't work, it's just as well that I'm not in the habit of doing make kernel, so there's a chance I'll remember to do make reinstallkernel next time, and preserve my working kernel.old. (Yes, I often rename kernel.old to kernel.lkg to avoid the chance for error.) -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net.