From owner-freebsd-questions Thu Aug 19 17: 0:21 1999 Delivered-To: freebsd-questions@freebsd.org Received: from dt010nb9.san.rr.com (dt010nb9.san.rr.com [204.210.12.185]) by hub.freebsd.org (Postfix) with ESMTP id EE60C14E1F for ; Thu, 19 Aug 1999 17:00:17 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from localhost (doug@localhost) by dt010nb9.san.rr.com (8.9.3/8.8.8) with ESMTP id QAA60216; Thu, 19 Aug 1999 16:59:57 -0700 (PDT) (envelope-from Doug@gorean.org) Date: Thu, 19 Aug 1999 16:59:57 -0700 (PDT) From: Doug X-Sender: doug@dt010nb9.san.rr.com To: Ben Smithurst Cc: Doug , mcwong@ascend.com, questions@freebsd.org Subject: Re: Safe upgrade from 2.2.5 --> 3.2 ? In-Reply-To: <19990819213621.A12658@lithium.scientia.demon.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 19 Aug 1999, Ben Smithurst wrote: > Doug wrote: > > > Specifically, you should not try to upgrade from 2.2.5 straight to > > 3.2-Stable since I've seen people run into trouble with a system older > > than 2.2.6. > > Ah, sorry. I thought the differences between 2.2.5 and 2.2.6 wouldn't be > much compared to the differences between 2.2.6 and 3.2. Evidently they are > too much :-) *Nod* Post 2.2.5 was when they started getting really serious about making the 2.2.x => 3.x upgrade work, AND had a stable enough API for the upgrade to make such efforts doable. In general, the safest bet is to just upgrade to 2.2.8 first. Doug -- On account of being a democracy and run by the people, we are the only nation in the world that has to keep a government four years, no matter what it does. -- Will Rogers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message