From owner-freebsd-stable Tue Apr 4 21:22:19 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 41BA637BCA3; Tue, 4 Apr 2000 21:22:16 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id VAA85753; Tue, 4 Apr 2000 21:22:16 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Tue, 4 Apr 2000 21:22:15 -0700 (PDT) From: Kris Kennaway To: Michael DeMutis Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Upgrade Path from 2.2.2 In-Reply-To: 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 Tue, 4 Apr 2000, Michael DeMutis wrote: > This may seem like a silly question but I have a 2.2.2 FreeBSD Server that > we're using as a mail server. > > What is the proper upgrade path to move this up to a 3.4 STABLE machine, > and once I move to 3.x do I need to remove anything that would be > redundant? A binary installation of a 3.4 snapshot would by far be the easiest way to go. You can do a source upgrade but it's a long and difficult road: 2.2.2 -> 2.2.8-STABLE 2.2.8-STABLE -> 3.2-RELEASE (make aout-to-elf or something, check /usr/src/Makefile*) 3.2-RELEASE -> 3.4-STABLE. The reason you have to dgo to 3.2-REL and cant go directly to 3.4-STABLE is because of reported breakage if you try and go directly. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message