Date: Wed, 14 Mar 2001 18:08:14 +0100 From: =?iso-8859-1?Q?Michael_Lyngb=F8l?= <michael@lyngbol.dk> To: Mike Harding <mvh@ix.netcom.com> Cc: steffen@vorrix.com, freebsd-stable@freebsd.org Subject: Re: Major upgrade Message-ID: <20010314180814.Y81775@tigerdyr.lyngbol.dk> In-Reply-To: <20010314163609.49125113D43@netcom1.netcom.com>; from mvh@ix.netcom.com on Wed, Mar 14, 2001 at 08:36:09AM -0800 References: <000e01c0ac9d$abd50040$fd03a8c0@ws001> <20010314163609.49125113D43@netcom1.netcom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Mar 14, 2001 at 08:36:09AM -0800, Mike Harding wrote: > > Having done this before I would HIGHLY recommend doing a clean install > and restoring the 'good stuff' from backup. You can do the upgrades > in place, but it takes a while, and you have to do it in steps, and if > you misstep you may blow up the box, and so on. You should know how > to do clean installs and backups anyways. Since you have 2 machines, > assuming sufficient clear disk space on each, you can back one up onto > the other and so on. Some time ago, Ralf S. Engelschall posted a description about upgradeing a bunch of 3.5-STABLE boxes to 4.1.1-STABLE: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=699499+0+archive/2000/freebsd-stable/20000806.freebsd-stable /Michael > > - Mike H. > > From: "Steffen Vorrix" <steffen@vorrix.com> > Date: Wed, 14 Mar 2001 10:44:34 -0500 > Content-Type: multipart/alternative; > boundary="----=_NextPart_000_000B_01C0AC73.C2523D80" > X-Priority: 3 > X-MSMail-Priority: Normal > X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 > X-MDRemoteIP: 208.60.70.195 > X-Return-Path: steffen@vorrix.com > X-MDaemon-Deliver-To: freebsd-stable@freebsd.org > Sender: owner-freebsd-stable@FreeBSD.ORG > X-Loop: FreeBSD.ORG > Precedence: bulk > > This is a multi-part message in MIME format. > > ------=_NextPart_000_000B_01C0AC73.C2523D80 > Content-Type: text/plain; > charset="iso-8859-1" > Content-Transfer-Encoding: quoted-printable > > I have been tracking this list for about 3 or 4 weeks now, and I have = > learned alot more about FreeBSD then I thought I might. I have = > successfully upgrade my two home FreeBSD machines from 4.2 REL to the = > current stable version, and everything went just fine. However, I now = > need to upgrade 2 production machines for my employer, and these have to = > go as painlessly as possible. The problem is that these machines are = > 3.4 REL. I have looked through the mail over the past weeks, and I have = > found people mention that 3.4 to 4 can have some gotcha's associated = > with it, but I haven't seen anything specifically mentioned. Are there = > things that I need to watch out for? The reference that I am referring = > to was a thread regarding remotely updating servers. While this was = > frowned upon by almost everyone in the list, one person specifically = > mentioned that remote updating would be a problem from a 3.x to a 4.x. = > I don't plan to do any remote updating, but I want to be sure there = > aren't other things I need to watch out for. > > Thanks a bunch. > > Chris Schremser > > ------=_NextPart_000_000B_01C0AC73.C2523D80 > Content-Type: text/html; > charset="iso-8859-1" > Content-Transfer-Encoding: quoted-printable > > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> > <HTML><HEAD> > <META http-equiv=3DContent-Type content=3D"text/html; = > charset=3Diso-8859-1"> > <META content=3D"MSHTML 5.50.4611.1300" name=3DGENERATOR> > <STYLE></STYLE> > </HEAD> > <BODY bgColor=3D#ffffff> > <DIV><FONT face=3DArial size=3D2>I have been tracking this list for = > about 3 or 4=20 > weeks now, and I have learned alot more about FreeBSD then I thought I=20 > might. I have successfully upgrade my two home FreeBSD machines = > from 4.2=20 > REL to the current stable version, and everything went just fine. = > However,=20 > I now need to upgrade 2 production machines for my employer, and these = > have to=20 > go as painlessly as possible. The problem is that these machines = > are 3.4=20 > REL. I have looked through the mail over the past weeks, and I = > have found=20 > people mention that 3.4 to 4 can have some gotcha's associated with it, = > but I=20 > haven't seen anything specifically mentioned. Are there things = > that I need=20 > to watch out for? The reference that I am referring to was a = > thread=20 > regarding remotely updating servers. While this was frowned upon = > by almost=20 > everyone in the list, one person specifically mentioned that remote = > updating=20 > would be a problem from a 3.x to a 4.x. I don't plan to do any = > remote=20 > updating, but I want to be sure there aren't other things I need to = > watch out=20 > for.</FONT></DIV> > <DIV><FONT face=3DArial size=3D2></FONT> </DIV> > <DIV><FONT face=3DArial size=3D2>Thanks a bunch.</FONT></DIV> > <DIV><FONT face=3DArial size=3D2></FONT> </DIV> > <DIV><FONT face=3DArial size=3D2>Chris = > Schremser</FONT></DIV></BODY></HTML> > > ------=_NextPart_000_000B_01C0AC73.C2523D80-- > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010314180814.Y81775>