Here are your real choices for upgrade: The handbook says it, every HOWTO in the world says it, so we're gonna say it too. Most folks get kinda nervous when it comes time for an upgrade and postpone the fateful day as long as possible.
This is a big mistake since the Free BSD team have done a great job in making it relatively simple and painless.
This step involves building all the various tools/utilities required to run Free BSD.
They are built and saved in the defined directores and are NOT INSTALLED (remember if it says build at the front it does NOT install).
This is a survival guide to keeping Free BSD up-to-date ('ish).
This note covers the automated tools (freebsd-update and portsnap) and manual methods for updating Free BSD.
We will be using non-standard paths so need we to do more work.
As with all things Free BSD there are about 100,000 million ways of doing things which can leave folk confused when they read three different HOWTOs all describing different ways to accomplish the same goal. The author of the HOWTO has always done it that way.Some level of risk is involved, offset against being udated for the lastest security fixes, and significantly lower risk than using -CURRENT.Resides in the /stable branch under the major version number, for example, svn.freebsd.org/base/stable/8 will provide the latest major version 8 sources (see here).While the Free BSD Handbook is generally a terrific resource - always check it first - but it can either make assumptions about background knowlege or it keeps things as simple as possible to minimize errors. We check the security advisories, nod sagely when we read 'em, and using the new automated tools (portsnap and freebsd-update) we keep our systems updated.As we all know Free BSD, like Perl, provides at least 8,000 ways to do the same thing. And occasionally even upgrade the ports we have installed. A major version upgrade only when it gets to a minimum of x.1.
In general, the automated tools should be the preferred method.