Date: Thu, 27 Apr 2000 15:29:53 -0700 (PDT) From: Annelise Anderson <andrsn@andrsn.stanford.edu> To: Otter <otter@otter.cc> Cc: marcus@redcentre.com, freebsd-questions@FreeBSD.ORG Subject: Re: Upgrading FreeBSD 2.2.7 to 4.0 Message-ID: <Pine.BSF.4.10.10004271525130.50716-100000@andrsn.stanford.edu> In-Reply-To: <3908AF63.862AAAF5@otter.cc>
next in thread | previous in thread | raw e-mail | index | archive | help
If you're going for a new install anyway, might as well experiment first. How about rsyncing the whole thing from another machine, if you've got one running something you like? You can rsync from one to another (you'd have to install rsync on both) using ssh if you like. Then you fix up the /etc files; you install from the 4.x machine a generic kernel or one build on the 4.x machine and moved to the 2.2.x. especially if you use rsync with the --delete option (be sure to back up the home directories first) this might just work. Annelise On Thu, 27 Apr 2000, Otter wrote: > marcus@redcentre.com wrote: > > > > Hi, > > > > I'm just after a bit of advice regarding upgrading a production > > server from 2.2.7 to 4.0 (?). Is there a safe way to do this or > > would it be wiser to configure a new server and transfer the accounts > > across? > > > > Marcus > > > > Remembering the upgrade process from 2.x to 3.x and 3.x to 4.0, I'd > recommend doing a new install. Consider too that 2.x to 3.x required > an a.out->elf conversion. Since you have production machines, you > might want to do a trial run on an unused box just to make sure the > upgrade/change goes smoothly before you make it go live. (IMHO) > -Otter > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.10004271525130.50716-100000>