d/freebsd-dev
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

After deeper software archaeology, reports that 10.3R was affected

Browse Source 
turned out to be mistaken. Adjust the entry and fix a few typos.
This commit is contained in:
Warner Losh 2016-10-19 15:13:08 +00:00
parent 3652bc8e09
commit fca3dcdf4e
Notes: svn2git 2020-12-20 02:59:44 +00:00 
svn path=/head/; revision=307639
1 changed files with 10 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
UPDATING
View File

@ -29,21 +29,22 @@ NOTE TO PEOPLE WHO THINK THAT FreeBSD 12.x IS SLOW:
machines to maximize performance. (To completely disable malloc
debugging, define MALLOC_PRODUCTION in /etc/make.conf, or to merely
disable the most expensive debugging functionality run
"ln -s 'abort:false,junk:false' /etc/malloc.
"ln -s 'abort:false,junk:false' /etc/malloc.conf".)
****************************** SPECIAL WARNING: ******************************
Due to a bug in some versions of clang that's very hard to workaround in
the upgrade process, to upgrade to -current you must first upgrade
either stable/9 after r286035 or stable/10 after r286033 or current
after r286007 (including stable/11 and 11.0-RELEASE). These revisions
post-date 10.3-RELEASE and 9.3-RELEASE, so you'll need to take the
unusual step of upgrading to the tip of the stable branch before moving
to 11 or -current via a source upgrade. stable/11 and 11.0-RELEASE
post-date the fix so you can move from them to -current. This differs
from the historical situation where one coule upgrade from anywhere on
the last couple of stable branches, so be careful.
either stable/9 after r286035 or stable/10 after r286033 (including
10.3-RELEASE) or current after r286007 (including stable/11 and
11.0-RELEASE). These revisions post-date the 10.2 and 9.3 releases, so
you'll need to take the unusual step of upgrading to the tip of the
stable branch before moving to 11 or -current via a source upgrade.
stable/11 and 11.0-RELEASE post-date the fix so you can move from them
to -current. This differs from the historical situation where one could
upgrade from anywhere on the last couple of stable branches, so be
careful.
****************************** SPECIAL WARNING: ******************************