diff options
| author | Doug Barton <dougb@FreeBSD.org> | 2005-12-07 20:49:42 +0000 |
|---|---|---|
| committer | Doug Barton <dougb@FreeBSD.org> | 2005-12-07 20:49:42 +0000 |
| commit | 081ff8ace35088a81dfec8cffd4e7873981ca5e0 (patch) | |
| tree | e700d022b4655c0b4d4abf3f06dc896ca9579c13 /UPDATING | |
| parent | 620b3a0c1d97d4a36da559714511a3ad967ce8a7 (diff) | |
| download | src-test-081ff8ace35088a81dfec8cffd4e7873981ca5e0.tar.gz src-test-081ff8ace35088a81dfec8cffd4e7873981ca5e0.zip | |
Add a paragraph to the COMMON ITEMS section that describes why
upgrading to the latest code in one branch before trying a major
version upgrade is a good idea.
Fleshing out of my thoughts provided by: kris
Notes
Notes:
svn path=/head/; revision=153211
Diffstat (limited to 'UPDATING')
| -rw-r--r-- | UPDATING | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/UPDATING b/UPDATING index dbcf56a4a9ea6..d5a4438ef11c9 100644 --- a/UPDATING +++ b/UPDATING @@ -267,6 +267,13 @@ COMMON ITEMS: prefix all make commands with 'env -i '. See the env(1) manual page for more details. + When upgrading from one major version to another it is generally + best to upgrade to the latest code in the currently installed branch + first, then do an upgrade to the new branch. This is the best-tested + upgrade path, and has the highest probability of being successful. + Please try this approach before reporting problems with a major + version upgrade. + To build a kernel ----------------- If you are updating from a prior version of FreeBSD (even one just |