summaryrefslogtreecommitdiffstats
path: root/UPDATING
diff options
context:
space:
mode:
authorimp <imp@FreeBSD.org>2000-09-04 03:18:01 +0000
committerimp <imp@FreeBSD.org>2000-09-04 03:18:01 +0000
commit231ad713c4a4fa6928077b582101bda3738ef881 (patch)
treef139b594fe20a0d4ab564fb6945530a7150aa4f9 /UPDATING
parentbbd4badbd6d7b92261cdcf9cd93d0ee89b56a54c (diff)
downloadFreeBSD-src-231ad713c4a4fa6928077b582101bda3738ef881.zip
FreeBSD-src-231ad713c4a4fa6928077b582101bda3738ef881.tar.gz
Add note about avoiding -j when following the upgrade path. It isn't
strictly verboten, just a recommendation to avoid problems. Add note about LINT being built from NOTES.
Diffstat (limited to 'UPDATING')
-rw-r--r--UPDATING11
1 files changed, 10 insertions, 1 deletions
diff --git a/UPDATING b/UPDATING
index a24cbe5..00b96e8 100644
--- a/UPDATING
+++ b/UPDATING
@@ -167,7 +167,7 @@ ITEMS:'
the config file update procedure.
http://people.freebsd.org/~imp/config-upd.html
NOTE: LINT is gone. It has been replaced with NOTES. NOTES
- isn't buildable.
+ isn't buildable. However, you can generate a LINT file.
20000620:
Binutils 2.10 have hit the tree, or will shortly. As soon
@@ -271,6 +271,15 @@ ITEMS:'
COMMON ITEMS:
+ General Notes
+ -------------
+ Avoid using make -j when upgrading. From time to time in the
+ past there have been problems using -j with buildworld and/or
+ installworld. This is especially true when upgrading between
+ "distant" versions (eg one that cross a major release boundary
+ or several minor releases, or when several months have passed
+ on the -current branch).
+
To build a kernel
-----------------
If you are updating from a prior version of FreeBSD (even one just
OpenPOWER on IntegriCloud