diff options
| author | dougb <dougb@FreeBSD.org> | 2005-12-07 20:49:42 +0000 |
|---|---|---|
| committer | dougb <dougb@FreeBSD.org> | 2005-12-07 20:49:42 +0000 |
| commit | d12a77cb38481285a7a2411f5b64a31c10b9d89b (patch) | |
| tree | e700d022b4655c0b4d4abf3f06dc896ca9579c13 /UPDATING | |
| parent | c77096e7fcd9cc25799c7b6cbd802c37c9686dee (diff) | |
| download | FreeBSD-src-d12a77cb38481285a7a2411f5b64a31c10b9d89b.zip FreeBSD-src-d12a77cb38481285a7a2411f5b64a31c10b9d89b.tar.gz | |
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
Diffstat (limited to 'UPDATING')
| -rw-r--r-- | UPDATING | 7 |
1 files changed, 7 insertions, 0 deletions
@@ -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 |
