Date: Sun, 21 Sep 2008 10:33:11 +0100 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: Odhiambo Washington <odhiambo@gmail.com> Cc: Grant Peel <gpeel@thenetnow.com>, freebsd-questions@freebsd.org Subject: Re: Upgrading Message-ID: <48D614D7.5070505@infracaninophile.co.uk> In-Reply-To: <991123400809202255h489af3b8x256cb41490875abf@mail.gmail.com> References: <2B72BBF1803C4CDBB9F84D0727CE1E42@GRANT> <991123400809202255h489af3b8x256cb41490875abf@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig92F6376D78732CC1A44B36CB
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Odhiambo Washington wrote:
> On Sun, Sep 21, 2008 at 2:29 AM, Grant Peel <gpeel@thenetnow.com> wrote=
:
>> Hi all,
>>
>> I am preparing to upgrade all servers from FBSD 6.2 to 6.3 in preperat=
ion
>> for 6.4, and some day 7.x
>>
>> One thing I have always found a little confusing is what tag to specif=
y in
>> the supfile.
>>
>> If a machine is running 6.2, and I want to upgrade to the latest produ=
ction
>> release, would I use:
>>
>> RELENG_6_3 ?
>=20
> RELENG_6
>=20
No. RELENG_6 will give you 6-STABLE. The OP was quite correct:
RELENG_6_3 will get 6.3-RELEASE-pX which is currently the latest
production release from the 6.x series. Eventually there will be
a RELENG_6_4 tag, but it hasn't been laid down quite yet. That
usually happens around when re@.. switches from 6.4-BETA to 6.4-RC
which will probably be fairly soon.
>> Also, What do you all think about jumping from 6.4 straight to 7.1 whe=
n its
>> released (cvsup method)?
If the OPs final aim is to track 7.1, then:
* upgrading 6.2 -> 6.3 -> 6.4 doesn't really get you anything
except a whole heap of wasted time -- unless you want practice
at running 'make buildworld' and so forth?
* Upgrading from 6.2 -> 7.0 directly works just fine. I expect
6.2 -> 7.1 would probably work too.
* It's the 6 -> 7 jump which is the big deal in terms of what you
have to do while upgrading. Rebuilding all of your installed ports
will take a significant amount of time, and you're going to have
to take the server out of action at least some of that time.
Alternatively, if the aim at the moment is to track 6.4, then upgrading
6.2 -> 6.4 in one step will get you there pretty simply. Just wait a
few weeks until 6.4 is out.
> Hmm.... In such cases, it will depend on what the server is running.
> I'd prefer a fresh install and migrate services by hand. However,
> upgrade from 6.4 -> 7.x should be doable.
Oh, it depends on how conservative you want to be. If you must always=20
absolutely definitely have a fast back-out path in case of things going=20
horribly wrong, then the thing to do is either install a new HDD and set =
up=20
the target version of the OS on that, or split up a RAID1 mirror, update =
one half of the mirror and then resynch in the appropriate direction once=
=20
your testing shows the update to have succeeded or not.
Of course, those are more expensive and time consuming procedures than
are usually justifiable. For general purpose use, the upgrade procedures =
described in /usr/src/UPDATING, the handbook, Colin Percival's=20
daemonology.org blog and RSE's web pages at freebsd.org will basically=20
work.
> Anyway, see this: http://people.freebsd.org/~rse/upgrade/
>=20
> It's some authoritative source for upgrades.
While RSE's account is factual and accurate and well worth the time
of anyone looking into doing an upgrade, I don't believe it's /the/
authoritative source. He says himself: your systems will be different.
As the perl folk say: TIMTOWTDI.
Cheers,
Matthew
--=20
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
Kent, CT11 9PW
--------------enig92F6376D78732CC1A44B36CB
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEAREIAAYFAkjWFN0ACgkQ8Mjk52CukIxmuACfRX9Mbgk1twqwzTWPNuRcAYJk
QT8An3BKCfA/7/r9WWcvURfS6esBXXs2
=hUab
-----END PGP SIGNATURE-----
--------------enig92F6376D78732CC1A44B36CB--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?48D614D7.5070505>