From owner-freebsd-current Mon Nov 1 15:16:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from venus.GAIANET.NET (venus.GAIANET.NET [207.211.200.51]) by hub.freebsd.org (Postfix) with ESMTP id 231FC153AB; Mon, 1 Nov 1999 15:15:57 -0800 (PST) (envelope-from vince@venus.GAIANET.NET) Received: from localhost (vince@localhost) by venus.GAIANET.NET (8.9.3/8.9.3) with ESMTP id PAA15877; Mon, 1 Nov 1999 15:15:29 -0800 (PST) (envelope-from vince@venus.GAIANET.NET) Date: Mon, 1 Nov 1999 15:15:29 -0800 (PST) From: Vincent Poy To: Chris Costello Cc: "David O'Brien" , FreeBSD-current@FreeBSD.ORG Subject: Re: -current build fails In-Reply-To: <19991101170957.I602@holly.calldei.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 1 Nov 1999, Chris Costello wrote: > On Mon, Nov 01, 1999, Vincent Poy wrote: > > > That's the perfect example of how and where not to use > > > -CURRENT. > > > > And your argument could be not to use -STABLE or -RELEASE since > > both would have the same problems. Like I said before, it's not which > > Quite the reverse. You _should_ anticipate an unbootable > system at each upgrade of -CURRENT. We're not trying to make > another -STABLE here. That is a known factor but I'm just saying booting with a newer kernel than the bins adds up another issue altogether. Cheers, Vince - vince@MCESTATE.COM - vince@GAIANET.NET ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message