Re: safest way to upgrade a production server

On 9/8/08, John Almberg <jalmberg@xxxxxxxxxxx> wrote:

uname -a
FreeBSD ***servername*** 6.3-PRERELEASE FreeBSD 6.3-PRERELEASE #1:
Mon Dec 3 09:46:53 EST 2007 root@***servername***:/usr/obj/usr/
src/sys/INET_ON amd64

oooh, that is a bit old I think.

I chose this server as an example, because it's the oldest one. I
didn't install the OS on this server, the vendor did. Not sure why
they chose a prerelease version... perhaps 6.3 was almost ready to go
and they wanted to put us on the 6.3 branch? I don't know.


I had the same problem, except I was the vendor. Set up a system with
6.3-PRERELEASE for testing, then forgot it wasn't -RELEASE and put it
in production.

Anyway, I guess what I should do is patch this to the latest 6.3
version?


My strategy was to do a source-base upgrade to 6.3-RELEASE, and then
use freebsd-update to apply critical patches. Freebsd-update only
works on -RELEASE versions with generic kernels, but I find it much
faster and easier than trying to do upgrades from source. You also
need to keep track of ports that need updating: use portaudit for
that.

Or should I go to the latest 6.x version? I am pretty sure I don't
want to experiment with a 7.x upgrade.

I believe 6.3 is the latest 6.x version. For now the thing to do is
get to an up-to-date 6.3 system. Then take your time figuring out the
best strategy for the transition to 7.x.

- Bob
_______________________________________________
freebsd-questions@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: freebsd-update painfully slow - slower than source code build of world and kernel
    ... Judging from the speed of http://www.daemonology.net/, the freebsd-update server must be absolutely hammered. ... "freebsd-update upgrade -r 7.1-RELEASE" started to work properly but hase not done its work. ... We need some mirrors, or such a great tool is not really usable at all. ...
    (freebsd-stable)
  • Re: NT to W2K3 Migration
    ... You cannot just promote a member server to AD. ... upgrade your PDC to windows 2000 or 2003, whichever flavor of AD you want to ... Upgrading from Windows NT Server 4.0 ... ensure that you have designed a DNS ...
    (microsoft.public.windows.server.active_directory)
  • Re: Native 2003 mode and NT4 workstations?
    ... Migrating from Windows NT Server 4.0 to Windows Server 2003 ... How to Upgrade from Windows NT Server 4.0 ... ensure that you have designed a DNS ...
    (microsoft.public.windows.server.active_directory)
  • Re: NT to W2K3 Migration
    ... How to Upgrade from Windows NT Server 4.0 ... Best Practice Active Directory Design for Managing Windows Networks ...
    (microsoft.public.windows.server.active_directory)
  • Re: Migrating NT4 to Windows 2003
    ... Migrating from Windows NT Server 4.0 to Windows Server 2003 ... How to Upgrade from Windows NT Server 4.0 ... Best Practice Active Directory Design for Managing Windows Networks ... ensure that you have designed a DNS ...
    (microsoft.public.windows.server.active_directory)