From owner-freebsd-stable Tue Jan 18 1:31:15 2000 Delivered-To: freebsd-stable@freebsd.org Received: from sapphire.looksharp.net (mcdouga9.user.msu.edu [35.10.148.141]) by hub.freebsd.org (Postfix) with ESMTP id 25B691526E for ; Tue, 18 Jan 2000 01:31:08 -0800 (PST) (envelope-from bsdx@looksharp.net) Received: from localhost (bsdx@localhost) by sapphire.looksharp.net (8.9.3/8.9.3) with ESMTP id EAA94973; Tue, 18 Jan 2000 04:30:54 -0500 (EST) (envelope-from bsdx@looksharp.net) X-Authentication-Warning: sapphire.looksharp.net: bsdx owned process doing -bs Date: Tue, 18 Jan 2000 04:30:54 -0500 (EST) From: Adam To: "Dan O'Connor" Cc: Troy Settle , freebsd-stable@FreeBSD.ORG Subject: Re: 1/16/2000 make world success In-Reply-To: <01e101bf6174$7d584260$0200000a@danco.home> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 17 Jan 2000, Dan O'Connor wrote: > >With the recent threads about crap failing... > > > >I cvsup'ed the evening of 1/16/2000, and built the world and installed it, > >and didn't have a single problem. > > > >Actually, I can't remember the last time I had a failure that an immediate > >cvsup didn't fix. And even that has been at least a couple years. > > > Troubleshooting rules-of-thumb: > > 1. If you have a problem in Windows, reboot... > > 2. If 'make world', kernel rebuilds, or ports break in FreeBSD, wait a > couple of hours and re-cvsup... > > These two steps solve 99% of all computing problems in the known universe. > :-) > > --Dan I thought it was this: Having trouble in Windows? ReBoot. Having trouble in Unix? BeRoot. (paraphrased from Gldm) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message