From owner-freebsd-questions Thu Aug 19 16:40:20 1999 Delivered-To: freebsd-questions@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id D528514BD8 for ; Thu, 19 Aug 1999 16:39:45 -0700 (PDT) (envelope-from ben@scientia.demon.co.uk) Received: from lithium.scientia.demon.co.uk ([192.168.0.3] ident=exim) by scientia.demon.co.uk with esmtp (Exim 3.024 #3) id 11HYv6-000DvG-00; Thu, 19 Aug 1999 21:36:20 +0100 Received: (from ben) by lithium.scientia.demon.co.uk (Exim 3.024 #3) id 11HYv7-0003dq-00; Thu, 19 Aug 1999 21:36:21 +0100 Date: Thu, 19 Aug 1999 21:36:21 +0100 From: Ben Smithurst To: Doug Cc: mcwong@ascend.com, questions@freebsd.org Subject: Re: Safe upgrade from 2.2.5 --> 3.2 ? Message-ID: <19990819213621.A12658@lithium.scientia.demon.co.uk> References: <882567D2.003DC09F.00@colton.ascend.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 :-) -- Ben Smithurst | PGP: 0x99392F7D ben@scientia.demon.co.uk | key available from keyservers and | ben+pgp@scientia.demon.co.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message