From owner-freebsd-current Sun Sep 13 13:57:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA00712 for freebsd-current-outgoing; Sun, 13 Sep 1998 13:57:19 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA00688 for ; Sun, 13 Sep 1998 13:57:12 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id GAA23488; Mon, 14 Sep 1998 06:59:57 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199809132059.GAA23488@cimlogic.com.au> Subject: Re: Upgrading 2.2.2 to 3.0 In-Reply-To: <199809131759.KAA06494@word.smith.net.au> from Mike Smith at "Sep 13, 98 10:59:34 am" To: mike@smith.net.au (Mike Smith) Date: Mon, 14 Sep 1998 06:59:57 +1000 (EST) Cc: dag-erli@ifi.uio.no, viren@rstcorp.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > I think you misunderstood me; I'm interested in reports of succesfully > > upgrading from 2.2.2-RELEASE to -current. I am already familiar with > > the issue of upgrading -stable to -current. > > Upgrading from anything other than the most recent release is never > supported. In this case that means you can't start from anything > earlier than 2.2.7 and expect it to work. I've tested upgrading from 2.2.5. I won't try before that because the ethernet board on my scratch box is not supported prior to that. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message