Date: Wed, 17 Mar 2010 18:03:55 +0100 From: "Bas v.d. Wiel" <bas@kompasmedia.nl> To: Mikolaj Rydzewski <miki@ceti.pl> Cc: freebsd-questions@freebsd.org Subject: Re: Which version of FreeBSD is it? Message-ID: <57443e3f6cec390a13ed02c4d1d9afa4@asterix.area536.com> In-Reply-To: <4BA0F706.1010209@ceti.pl> References: <3f1c29e71003170656u1b932fd2v37f5062440653e3b@mail.gmail.com> <0b9982274818d454f23bc89ac74d30f5@asterix.area536.com> <3f1c29e71003170745u55a4fad2rd8c6f39d02fa968f@mail.gmail.com> <4BA0F706.1010209@ceti.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 17 Mar 2010 16:36:38 +0100, Mikolaj Rydzewski <miki@ceti.pl> wrote: > Антон Клесс wrote: >> That is what I suspected for. >> >> What is the most safe way to upgrade it, remembering that this is >> production >> server and I have to keep it working properly? >> >> 6.2-RC1 -> 6.2 RELEASE -> 7.2 RELEASE -> 8.0 RELEASE, or somehow in this >> style? >> > If it works, do not fix it! I beg to differ: having a release candidate running in production should never happen so this situation has been sort of broken from the start. Luckily FreeBSD is a rock solid OS! > > Actually, I'm facing exactly the same problem now: I want to upgrade > 6.2-RELEASE to something (8.0?) newer. > > Since I don't have spare machine for tests, I'm playing now with > VirtualBox (hosted on Linux). I'd like to test upgrade using > cvsup/buildworld. After I will success on virtualbox I'll perform the > same path on real machine. Making an image backup of the machine's disk before you start should give you a decent rollback scenario in case things go badly. Bas
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?57443e3f6cec390a13ed02c4d1d9afa4>