Date: Tue, 9 Dec 2003 22:07:47 -0500 From: Barney Wolff <barney@databus.com> To: "David O'Brien" <obrien@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: last cvs Makefile.inc1 errors Message-ID: <20031210030747.GA47528@pit.databus.com> In-Reply-To: <20031210025930.GA34162@dragon.nuxi.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>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031210030747.GA47528>