3420141231:
35 Clang, llvm and lldb have been upgraded to 3.5.0 release.
36
37 As of this release, a prerequisite for building clang, llvm and lldb is
38 a C++11 capable compiler and C++11 standard library. This means that to
39 be able to successfully build the cross-tools stage of buildworld, with
40 clang as the bootstrap compiler, your system compiler or cross compiler
41 should either be clang 3.3 or later, or gcc 4.8 or later, and your
42 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
43 later.
44
45 On any standard FreeBSD 10.x or 11.x installation, where clang and
46 libc++ are on by default (that is, on x86 or arm), this should work out
47 of the box.
48
49 On 9.x installations where clang is enabled by default, e.g. on x86 and
50 powerpc, libc++ will not be enabled by default, so libc++ should be
51 built (with clang) and installed first. If both clang and libc++ are
52 missing, build clang first, then use it to build libc++.
53
54 On 8.x and earlier installations, upgrade to 9.x first, and then follow
55 the instructions for 9.x above.
56
57 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
58 default, and do not build clang.
59
60 Many embedded systems are resource constrained, and will not be able to
61 build clang in a reasonable time, or in some cases at all. In those
62 cases, cross building bootable systems on amd64 is a workaround.
63
64 This new version of clang introduces a number of new warnings, of which
65 the following are most likely to appear:
66
67 -Wabsolute-value
68
69 This warns in two cases, for both C and C++:
70 * When the code is trying to take the absolute value of an unsigned
71 quantity, which is effectively a no-op, and almost never what was
72 intended. The code should be fixed, if at all possible. If you are
73 sure that the unsigned quantity can be safely cast to signed, without
74 loss of information or undefined behavior, you can add an explicit
75 cast, or disable the warning.
76
77 * When the code is trying to take an absolute value, but the called
78 abs() variant is for the wrong type, which can lead to truncation.
79 If you want to disable the warning instead of fixing the code, please
80 make sure that truncation will not occur, or it might lead to unwanted
81 side-effects.
82
83 -Wtautological-undefined-compare and
84 -Wundefined-bool-conversion
85
86 These warn when C++ code is trying to compare 'this' against NULL, while
87 'this' should never be NULL in well-defined C++ code. However, there is
88 some legacy (pre C++11) code out there, which actively abuses this
89 feature, which was less strictly defined in previous C++ versions.
90
91 Squid and openjdk do this, for example. The warning can be turned off
92 for C++98 and earlier, but compiling the code in C++11 mode might result
93 in unexpected behavior; for example, the parts of the program that are
94 unreachable could be optimized away.
95
9620141222:
97 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
98 kernel sources have been removed. The .h files remain, since some
99 utilities include them. This will need to be fixed later.
100 If "mount -t oldnfs ..." is attempted, it will fail.
101 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
102 the utilities will report errors.
103
10420141121:
105 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
106 directories to top level SUBDIR variable when their parent
107 directory is included in LOCAL_DIRS. Users with build systems with
108 such hierarchies and without SUBDIR entries in the parent
109 directory Makefiles should add them or add the directories to
110 LOCAL_DIRS.
111
11220141109:
113 faith(4) and faithd(8) has been removed from base system. It
114 has been obsolete for a very long time.
115
11620141104:
117 vt(4), the new console driver, is enabled by default. It brings
118 support for Unicode and double-width characters, as well as
119 support for UEFI and integration with the KMS kernel video
120 drivers.
121
122 You may need to update your console settings in /etc/rc.conf,
123 most probably the keymap. During boot, /etc/rc.d/syscons will
124 indicate what you need to do.
125
126 vt(4) still has issues and lacks some features compared to
127 syscons(4). See the wiki for up-to-date information:
128 https://wiki.freebsd.org/Newcons
129
130 If you want to keep using syscons(4), you can do so by adding
131 the following line to /boot/loader.conf:
132 kern.vty=sc
133
13420141102:
135 pjdfstest has been integrated into kyua as an opt-in test suite.
136 Please see share/doc/pjdfstest/README for a more details on how to
137 execute it.
138
13920141009:
140 gperf has been removed from the base system for architectures
141 that use clang. Ports that require gperf will obtain it from the
142 devel/gperf port.
143
14420140923:
145 pjdfstest has been moved from tools/regression/pjdfstest to
146 contrib/pjdfstest .
147
14820140922:
149 At svn r271982, The default linux compat kernel ABI has been adjusted
150 to 2.6.18 in support of the linux-c6 compat ports infrastructure
151 update. If you wish to continue using the linux-f10 compat ports,
152 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
153 encouraged to update their linux-compat packages to linux-c6 during
154 their next update cycle.
155
15620140729:
157 The ofwfb driver, used to provide a graphics console on PowerPC when
158 using vt(4), no longer allows mmap() of all of physical memory. This
159 will prevent Xorg on PowerPC with some ATI graphics cards from
160 initializing properly unless x11-servers/xorg-server is updated to
161 1.12.4_8 or newer.
162
16320140723:
164 The xdev targets have been converted to using TARGET and
165 TARGET_ARCH instead of XDEV and XDEV_ARCH.
166
16720140719:
168 The default unbound configuration has been modified to address
169 issues with reverse lookups on networks that use private
170 address ranges. If you use the local_unbound service, run
171 "service local_unbound setup" as root to regenerate your
172 configuration, then "service local_unbound reload" to load the
173 new configuration.
174
17520140709:
176 The GNU texinfo and GNU info pages are not built and installed
177 anymore, WITH_INFO knob has been added to allow to built and install
178 them again.
| 3820141231:
39 Clang, llvm and lldb have been upgraded to 3.5.0 release.
40
41 As of this release, a prerequisite for building clang, llvm and lldb is
42 a C++11 capable compiler and C++11 standard library. This means that to
43 be able to successfully build the cross-tools stage of buildworld, with
44 clang as the bootstrap compiler, your system compiler or cross compiler
45 should either be clang 3.3 or later, or gcc 4.8 or later, and your
46 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
47 later.
48
49 On any standard FreeBSD 10.x or 11.x installation, where clang and
50 libc++ are on by default (that is, on x86 or arm), this should work out
51 of the box.
52
53 On 9.x installations where clang is enabled by default, e.g. on x86 and
54 powerpc, libc++ will not be enabled by default, so libc++ should be
55 built (with clang) and installed first. If both clang and libc++ are
56 missing, build clang first, then use it to build libc++.
57
58 On 8.x and earlier installations, upgrade to 9.x first, and then follow
59 the instructions for 9.x above.
60
61 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
62 default, and do not build clang.
63
64 Many embedded systems are resource constrained, and will not be able to
65 build clang in a reasonable time, or in some cases at all. In those
66 cases, cross building bootable systems on amd64 is a workaround.
67
68 This new version of clang introduces a number of new warnings, of which
69 the following are most likely to appear:
70
71 -Wabsolute-value
72
73 This warns in two cases, for both C and C++:
74 * When the code is trying to take the absolute value of an unsigned
75 quantity, which is effectively a no-op, and almost never what was
76 intended. The code should be fixed, if at all possible. If you are
77 sure that the unsigned quantity can be safely cast to signed, without
78 loss of information or undefined behavior, you can add an explicit
79 cast, or disable the warning.
80
81 * When the code is trying to take an absolute value, but the called
82 abs() variant is for the wrong type, which can lead to truncation.
83 If you want to disable the warning instead of fixing the code, please
84 make sure that truncation will not occur, or it might lead to unwanted
85 side-effects.
86
87 -Wtautological-undefined-compare and
88 -Wundefined-bool-conversion
89
90 These warn when C++ code is trying to compare 'this' against NULL, while
91 'this' should never be NULL in well-defined C++ code. However, there is
92 some legacy (pre C++11) code out there, which actively abuses this
93 feature, which was less strictly defined in previous C++ versions.
94
95 Squid and openjdk do this, for example. The warning can be turned off
96 for C++98 and earlier, but compiling the code in C++11 mode might result
97 in unexpected behavior; for example, the parts of the program that are
98 unreachable could be optimized away.
99
10020141222:
101 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
102 kernel sources have been removed. The .h files remain, since some
103 utilities include them. This will need to be fixed later.
104 If "mount -t oldnfs ..." is attempted, it will fail.
105 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
106 the utilities will report errors.
107
10820141121:
109 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
110 directories to top level SUBDIR variable when their parent
111 directory is included in LOCAL_DIRS. Users with build systems with
112 such hierarchies and without SUBDIR entries in the parent
113 directory Makefiles should add them or add the directories to
114 LOCAL_DIRS.
115
11620141109:
117 faith(4) and faithd(8) has been removed from base system. It
118 has been obsolete for a very long time.
119
12020141104:
121 vt(4), the new console driver, is enabled by default. It brings
122 support for Unicode and double-width characters, as well as
123 support for UEFI and integration with the KMS kernel video
124 drivers.
125
126 You may need to update your console settings in /etc/rc.conf,
127 most probably the keymap. During boot, /etc/rc.d/syscons will
128 indicate what you need to do.
129
130 vt(4) still has issues and lacks some features compared to
131 syscons(4). See the wiki for up-to-date information:
132 https://wiki.freebsd.org/Newcons
133
134 If you want to keep using syscons(4), you can do so by adding
135 the following line to /boot/loader.conf:
136 kern.vty=sc
137
13820141102:
139 pjdfstest has been integrated into kyua as an opt-in test suite.
140 Please see share/doc/pjdfstest/README for a more details on how to
141 execute it.
142
14320141009:
144 gperf has been removed from the base system for architectures
145 that use clang. Ports that require gperf will obtain it from the
146 devel/gperf port.
147
14820140923:
149 pjdfstest has been moved from tools/regression/pjdfstest to
150 contrib/pjdfstest .
151
15220140922:
153 At svn r271982, The default linux compat kernel ABI has been adjusted
154 to 2.6.18 in support of the linux-c6 compat ports infrastructure
155 update. If you wish to continue using the linux-f10 compat ports,
156 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
157 encouraged to update their linux-compat packages to linux-c6 during
158 their next update cycle.
159
16020140729:
161 The ofwfb driver, used to provide a graphics console on PowerPC when
162 using vt(4), no longer allows mmap() of all of physical memory. This
163 will prevent Xorg on PowerPC with some ATI graphics cards from
164 initializing properly unless x11-servers/xorg-server is updated to
165 1.12.4_8 or newer.
166
16720140723:
168 The xdev targets have been converted to using TARGET and
169 TARGET_ARCH instead of XDEV and XDEV_ARCH.
170
17120140719:
172 The default unbound configuration has been modified to address
173 issues with reverse lookups on networks that use private
174 address ranges. If you use the local_unbound service, run
175 "service local_unbound setup" as root to regenerate your
176 configuration, then "service local_unbound reload" to load the
177 new configuration.
178
17920140709:
180 The GNU texinfo and GNU info pages are not built and installed
181 anymore, WITH_INFO knob has been added to allow to built and install
182 them again.
|
179
18020140708:
181 The GNU readline library is now an INTERNALLIB - that is, it is
182 statically linked into consumers (GDB and variants) in the base
183 system, and the shared library is no longer installed. The
184 devel/readline port is available for third party software that
185 requires readline.
186
18720140702:
188 The Itanium architecture (ia64) has been removed from the list of
189 known architectures. This is the first step in the removal of the
190 architecture.
191
19220140701:
193 Commit r268115 has added NFSv4.1 server support, merged from
194 projects/nfsv4.1-server. Since this includes changes to the
195 internal interfaces between the NFS related modules, a full
196 build of the kernel and modules will be necessary.
197 __FreeBSD_version has been bumped.
198
19920140629:
200 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
201 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
202 which differs from the behaviour controlled by this knob.)
203
20420140619:
205 Maximal length of the serial number in CTL was increased from 16 to
206 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
207 and ctld, need to be rebuilt to work with a new kernel.
208
20920140606:
210 The libatf-c and libatf-c++ major versions were downgraded to 0 and
211 1 respectively to match the upstream numbers. They were out of
212 sync because, when they were originally added to FreeBSD, the
213 upstream versions were not respected. These libraries are private
214 and not yet built by default, so renumbering them should be a
215 non-issue. However, unclean source trees will yield broken test
216 programs once the operator executes "make delete-old-libs" after a
217 "make installworld".
218
219 Additionally, the atf-sh binary was made private by moving it into
220 /usr/libexec/. Already-built shell test programs will keep the
221 path to the old binary so they will break after "make delete-old"
222 is run.
223
224 If you are using WITH_TESTS=yes (not the default), wipe the object
225 tree and rebuild from scratch to prevent spurious test failures.
226 This is only needed once: the misnumbered libraries and misplaced
227 binaries have been added to OptionalObsoleteFiles.inc so they will
228 be removed during a clean upgrade.
229
23020140512:
231 Clang and llvm have been upgraded to 3.4.1 release.
232
23320140508:
234 We bogusly installed src.opts.mk in /usr/share/mk. This file should
235 be removed to avoid issues in the future (and has been added to
236 ObsoleteFiles.inc).
237
23820140505:
239 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
240 past, it affected all builds that used the bsd.*.mk files. The old
241 behavior was a bug, but people may have relied upon it. To get this
242 behavior back, you can .include /etc/src.conf from /etc/make.conf
243 (which is still global and isn't changed). This also changes the
244 behavior of incremental builds inside the tree of individual
245 directories. Set MAKESYSPATH to ".../share/mk" to do that.
246 Although this has survived make universe and some upgrade scenarios,
247 other upgrade scenarios may have broken. At least one form of
248 temporary breakage was fixed with MAKESYSPATH settings for buildworld
249 as well... In cases where MAKESYSPATH isn't working with this
250 setting, you'll need to set it to the full path to your tree.
251
252 One side effect of all this cleaning up is that bsd.compiler.mk
253 is no longer implicitly included by bsd.own.mk. If you wish to
254 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
255 as well.
256
25720140430:
258 The lindev device has been removed since /dev/full has been made a
259 standard device. __FreeBSD_version has been bumped.
260
26120140418:
262 The YES_HESIOD knob has been removed. It has been obsolete for
263 a decade. Please move to using WITH_HESIOD instead or your builds
264 will silently lack HESIOD.
265
26620140405:
267 The uart(4) driver has been changed with respect to its handling
268 of the low-level console. Previously the uart(4) driver prevented
269 any process from changing the baudrate or the CLOCAL and HUPCL
270 control flags. By removing the restrictions, operators can make
271 changes to the serial console port without having to reboot.
272 However, when getty(8) is started on the serial device that is
273 associated with the low-level console, a misconfigured terminal
274 line in /etc/ttys will now have a real impact.
275 Before upgrading the kernel, make sure that /etc/ttys has the
276 serial console device configured as 3wire without baudrate to
277 preserve the previous behaviour. E.g:
278 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
279
28020140306:
281 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
282 to improve performance. To re-enable it, if needed, run rpcbind
283 with command line option -W.
284
28520140226:
286 Switched back to the GPL dtc compiler due to updates in the upstream
287 dts files not being supported by the BSDL dtc compiler. You will need
288 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
289 may result while building dtb files during a kernel build if you fail
290 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
291
29220140216:
293 Clang and llvm have been upgraded to 3.4 release.
294
29520140216:
296 The nve(4) driver has been removed. Please use the nfe(4) driver
297 for NVIDIA nForce MCP Ethernet adapters instead.
298
29920140212:
300 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
301 This could cause certain C++ applications using shared libraries built
302 against the previous version of libc++ to crash. The incompatibility
303 has now been fixed, but any C++ applications or shared libraries built
304 between r261283 and r261801 should be recompiled.
305
30620140204:
307 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
308 capability mode support. Please note that enabling the feature in
309 kernel is still highly recommended.
310
31120140131:
312 OpenSSH is now built with sandbox support, and will use sandbox as
313 the default privilege separation method. This requires Capsicum
314 capability mode support in kernel.
315
31620140128:
317 The libelf and libdwarf libraries have been updated to newer
318 versions from upstream. Shared library version numbers for
319 these two libraries were bumped. Any ports or binaries
320 requiring these two libraries should be recompiled.
321 __FreeBSD_version is bumped to 1100006.
322
32320140110:
324 If a Makefile in a tests/ directory was auto-generating a Kyuafile
325 instead of providing an explicit one, this would prevent such
326 Makefile from providing its own Kyuafile in the future during
327 NO_CLEAN builds. This has been fixed in the Makefiles but manual
328 intervention is needed to clean an objdir if you use NO_CLEAN:
329 # find /usr/obj -name Kyuafile | xargs rm -f
330
33120131213:
332 The behavior of gss_pseudo_random() for the krb5 mechanism
333 has changed, for applications requesting a longer random string
334 than produced by the underlying enctype's pseudo-random() function.
335 In particular, the random string produced from a session key of
336 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
337 be different at the 17th octet and later, after this change.
338 The counter used in the PRF+ construction is now encoded as a
339 big-endian integer in accordance with RFC 4402.
340 __FreeBSD_version is bumped to 1100004.
341
34220131108:
343 The WITHOUT_ATF build knob has been removed and its functionality
344 has been subsumed into the more generic WITHOUT_TESTS. If you were
345 using the former to disable the build of the ATF libraries, you
346 should change your settings to use the latter.
347
34820131025:
349 The default version of mtree is nmtree which is obtained from
350 NetBSD. The output is generally the same, but may vary
351 slightly. If you found you need identical output adding
352 "-F freebsd9" to the command line should do the trick. For the
353 time being, the old mtree is available as fmtree.
354
35520131014:
356 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
357 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
358 1.1.4_8 and verify bsdyml not linked in, before running "make
359 delete-old-libs":
360 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
361 or
362 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
363
36420131010:
365 The rc.d/jail script has been updated to support jail(8)
366 configuration file. The "jail_<jname>_*" rc.conf(5) variables
367 for per-jail configuration are automatically converted to
368 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
369 This is transparently backward compatible. See below about some
370 incompatibilities and rc.conf(5) manual page for more details.
371
372 These variables are now deprecated in favor of jail(8) configuration
373 file. One can use "rc.d/jail config <jname>" command to generate
374 a jail(8) configuration file in /var/run/jail.<jname>.conf without
375 running the jail(8) utility. The default pathname of the
376 configuration file is /etc/jail.conf and can be specified by
377 using $jail_conf or $jail_<jname>_conf variables.
378
379 Please note that jail_devfs_ruleset accepts an integer at
380 this moment. Please consider to rewrite the ruleset name
381 with an integer.
382
38320130930:
384 BIND has been removed from the base system. If all you need
385 is a local resolver, simply enable and start the local_unbound
386 service instead. Otherwise, several versions of BIND are
387 available in the ports tree. The dns/bind99 port is one example.
388
389 With this change, nslookup(1) and dig(1) are no longer in the base
390 system. Users should instead use host(1) and drill(1) which are
391 in the base system. Alternatively, nslookup and dig can
392 be obtained by installing the dns/bind-tools port.
393
39420130916:
395 With the addition of unbound(8), a new unbound user is now
396 required during installworld. "mergemaster -p" can be used to
397 add the user prior to installworld, as documented in the handbook.
398
39920130911:
400 OpenSSH is now built with DNSSEC support, and will by default
401 silently trust signed SSHFP records. This can be controlled with
402 the VerifyHostKeyDNS client configuration setting. DNSSEC support
403 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
404
40520130906:
406 The GNU Compiler Collection and C++ standard library (libstdc++)
407 are no longer built by default on platforms where clang is the system
408 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
409 options in src.conf.
410
41120130905:
412 The PROCDESC kernel option is now part of the GENERIC kernel
413 configuration and is required for the rwhod(8) to work.
414 If you are using custom kernel configuration, you should include
415 'options PROCDESC'.
416
41720130905:
418 The API and ABI related to the Capsicum framework was modified
419 in backward incompatible way. The userland libraries and programs
420 have to be recompiled to work with the new kernel. This includes the
421 following libraries and programs, but the whole buildworld is
422 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
423 kdump, procstat, rwho, rwhod, uniq.
424
42520130903:
426 AES-NI intrinsic support has been added to gcc. The AES-NI module
427 has been updated to use this support. A new gcc is required to build
428 the aesni module on both i386 and amd64.
429
43020130821:
431 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
432 Thus "device padlock_rng" and "device rdrand_rng" should be
433 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
434
43520130813:
436 WITH_ICONV has been split into two feature sets. WITH_ICONV now
437 enables just the iconv* functionality and is now on by default.
438 WITH_LIBICONV_COMPAT enables the libiconv api and link time
439 compatability. Set WITHOUT_ICONV to build the old way.
440 If you have been using WITH_ICONV before, you will very likely
441 need to turn on WITH_LIBICONV_COMPAT.
442
44320130806:
444 INVARIANTS option now enables DEBUG for code with OpenSolaris and
445 Illumos origin, including ZFS. If you have INVARIANTS in your
446 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
447 explicitly.
448 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
449 locks if WITNESS option was set. Because that generated a lot of
450 witness(9) reports and all of them were believed to be false
451 positives, this is no longer done. New option OPENSOLARIS_WITNESS
452 can be used to achieve the previous behavior.
453
45420130806:
455 Timer values in IPv6 data structures now use time_uptime instead
456 of time_second. Although this is not a user-visible functional
457 change, userland utilities which directly use them---ndp(8),
458 rtadvd(8), and rtsold(8) in the base system---need to be updated
459 to r253970 or later.
460
46120130802:
462 find -delete can now delete the pathnames given as arguments,
463 instead of only files found below them or if the pathname did
464 not contain any slashes. Formerly, the following error message
465 would result:
466
467 find: -delete: <path>: relative path potentially not safe
468
469 Deleting the pathnames given as arguments can be prevented
470 without error messages using -mindepth 1 or by changing
471 directory and passing "." as argument to find. This works in the
472 old as well as the new version of find.
473
47420130726:
475 Behavior of devfs rules path matching has been changed.
476 Pattern is now always matched against fully qualified devfs
477 path and slash characters must be explicitly matched by
478 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
479 subdirectories must be reviewed.
480
48120130716:
482 The default ARM ABI has changed to the ARM EABI. The old ABI is
483 incompatible with the ARM EABI and all programs and modules will
484 need to be rebuilt to work with a new kernel.
485
486 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
487
488 NOTE: Support for the old ABI will be removed in the future and
489 users are advised to upgrade.
490
49120130709:
492 pkg_install has been disconnected from the build if you really need it
493 you should add WITH_PKGTOOLS in your src.conf(5).
494
49520130709:
496 Most of network statistics structures were changed to be able
497 keep 64-bits counters. Thus all tools, that work with networking
498 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
499
50020130629:
501 Fix targets that run multiple make's to use && rather than ;
502 so that subsequent steps depend on success of previous.
503
504 NOTE: if building 'universe' with -j* on stable/8 or stable/9
505 it would be better to start the build using bmake, to avoid
506 overloading the machine.
507
50820130618:
509 Fix a bug that allowed a tracing process (e.g. gdb) to write
510 to a memory-mapped file in the traced process's address space
511 even if neither the traced process nor the tracing process had
512 write access to that file.
513
51420130615:
515 CVS has been removed from the base system. An exact copy
516 of the code is available from the devel/cvs port.
517
51820130613:
519 Some people report the following error after the switch to bmake:
520
521 make: illegal option -- J
522 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
523 ...
524 *** [buildworld] Error code 2
525
526 this likely due to an old instance of make in
527 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
528 which src/Makefile will use that blindly, if it exists, so if
529 you see the above error:
530
531 rm -rf `make -V MAKEPATH`
532
533 should resolve it.
534
53520130516:
536 Use bmake by default.
537 Whereas before one could choose to build with bmake via
538 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
539 make. The goal is to remove these knobs for 10-RELEASE.
540
541 It is worth noting that bmake (like gmake) treats the command
542 line as the unit of failure, rather than statements within the
543 command line. Thus '(cd some/where && dosomething)' is safer
544 than 'cd some/where; dosomething'. The '()' allows consistent
545 behavior in parallel build.
546
54720130429:
548 Fix a bug that allows NFS clients to issue READDIR on files.
549
55020130426:
551 The WITHOUT_IDEA option has been removed because
552 the IDEA patent expired.
553
55420130426:
555 The sysctl which controls TRIM support under ZFS has been renamed
556 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
557 enabled by default.
558
55920130425:
560 The mergemaster command now uses the default MAKEOBJDIRPREFIX
561 rather than creating it's own in the temporary directory in
562 order allow access to bootstrapped versions of tools such as
563 install and mtree. When upgrading from version of FreeBSD where
564 the install command does not support -l, you will need to
565 install a new mergemaster command if mergemaster -p is required.
566 This can be accomplished with the command (cd src/usr.sbin/mergemaster
567 && make install).
568
56920130404:
570 Legacy ATA stack, disabled and replaced by new CAM-based one since
571 FreeBSD 9.0, completely removed from the sources. Kernel modules
572 atadisk and atapi*, user-level tools atacontrol and burncd are
573 removed. Kernel option `options ATA_CAM` is now permanently enabled
574 and removed.
575
57620130319:
577 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
578 and socketpair(2). Software, in particular Kerberos, may
579 automatically detect and use these during building. The resulting
580 binaries will not work on older kernels.
581
58220130308:
583 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
584 information, see the respective 20130304 entry).
585
58620130304:
587 Recent commits to callout(9) changed the size of struct callout,
588 so the KBI is probably heavily disturbed. Also, some functions
589 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
590 by macros. Every kernel module using it won't load, so rebuild
591 is requested.
592
593 The ctl device has been re-enabled in GENERIC for i386 and amd64,
594 but does not initialize by default (because of the new CTL_DISABLE
595 option) to save memory. To re-enable it, remove the CTL_DISABLE
596 option from the kernel config file or set kern.cam.ctl.disable=0
597 in /boot/loader.conf.
598
59920130301:
600 The ctl device has been disabled in GENERIC for i386 and amd64.
601 This was done due to the extra memory being allocated at system
602 initialisation time by the ctl driver which was only used if
603 a CAM target device was created. This makes a FreeBSD system
604 unusable on 128MB or less of RAM.
605
60620130208:
607 A new compression method (lz4) has been merged to -HEAD. Please
608 refer to zpool-features(7) for more information.
609
610 Please refer to the "ZFS notes" section of this file for information
611 on upgrading boot ZFS pools.
612
61320130129:
614 A BSD-licensed patch(1) variant has been added and is installed
615 as bsdpatch, being the GNU version the default patch.
616 To inverse the logic and use the BSD-licensed one as default,
617 while having the GNU version installed as gnupatch, rebuild
618 and install world with the WITH_BSD_PATCH knob set.
619
62020130121:
621 Due to the use of the new -l option to install(1) during build
622 and install, you must take care not to directly set the INSTALL
623 make variable in your /etc/make.conf, /etc/src.conf, or on the
624 command line. If you wish to use the -C flag for all installs
625 you may be able to add INSTALL+=-C to /etc/make.conf or
626 /etc/src.conf.
627
62820130118:
629 The install(1) option -M has changed meaning and now takes an
630 argument that is a file or path to append logs to. In the
631 unlikely event that -M was the last option on the command line
632 and the command line contained at least two files and a target
633 directory the first file will have logs appended to it. The -M
634 option served little practical purpose in the last decade so its
635 use is expected to be extremely rare.
636
63720121223:
638 After switching to Clang as the default compiler some users of ZFS
639 on i386 systems started to experience stack overflow kernel panics.
640 Please consider using 'options KSTACK_PAGES=4' in such configurations.
641
64220121222:
643 GEOM_LABEL now mangles label names read from file system metadata.
644 Mangling affect labels containing spaces, non-printable characters,
645 '%' or '"'. Device names in /etc/fstab and other places may need to
646 be updated.
647
64820121217:
649 By default, only the 10 most recent kernel dumps will be saved. To
650 restore the previous behaviour (no limit on the number of kernel dumps
651 stored in the dump directory) add the following line to /etc/rc.conf:
652
653 savecore_flags=""
654
65520121201:
656 With the addition of auditdistd(8), a new auditdistd user is now
657 required during installworld. "mergemaster -p" can be used to
658 add the user prior to installworld, as documented in the handbook.
659
66020121117:
661 The sin6_scope_id member variable in struct sockaddr_in6 is now
662 filled by the kernel before passing the structure to the userland via
663 sysctl or routing socket. This means the KAME-specific embedded scope
664 id in sin6_addr.s6_addr[2] is always cleared in userland application.
665 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
666 __FreeBSD_version is bumped to 1000025.
667
66820121105:
669 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
670 This means that the world and kernel will be compiled with clang
671 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
672 and /usr/bin/cpp. To disable this behavior and revert to building
673 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
674 of current may need to bootstrap WITHOUT_CLANG first if the clang
675 build fails (its compatibility window doesn't extend to the 9 stable
676 branch point).
677
67820121102:
679 The IPFIREWALL_FORWARD kernel option has been removed. Its
680 functionality now turned on by default.
681
68220121023:
683 The ZERO_COPY_SOCKET kernel option has been removed and
684 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
685 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
686 mechanism which is not safe and may result in kernel crashes.
687 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
688 driver supports disposeable external page sized mbuf storage.
689 Proper replacements for both zero-copy mechanisms are under
690 consideration and will eventually lead to complete removal
691 of the two kernel options.
692
69320121023:
694 The IPv4 network stack has been converted to network byte
695 order. The following modules need to be recompiled together
696 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
697 pf(4), ipfw(4), ng_ipfw(4), stf(4).
698
69920121022:
700 Support for non-MPSAFE filesystems was removed from VFS. The
701 VFS_VERSION was bumped, all filesystem modules shall be
702 recompiled.
703
70420121018:
705 All the non-MPSAFE filesystems have been disconnected from
706 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
707 portalfs, smbfs, xfs.
708
70920121016:
710 The interface cloning API and ABI has changed. The following
711 modules need to be recompiled together with kernel:
712 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
713 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
714 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
715
71620121015:
717 The sdhci driver was split in two parts: sdhci (generic SD Host
718 Controller logic) and sdhci_pci (actual hardware driver).
719 No kernel config modifications are required, but if you
720 load sdhc as a module you must switch to sdhci_pci instead.
721
72220121014:
723 Import the FUSE kernel and userland support into base system.
724
72520121013:
726 The GNU sort(1) program has been removed since the BSD-licensed
727 sort(1) has been the default for quite some time and no serious
728 problems have been reported. The corresponding WITH_GNU_SORT
729 knob has also gone.
730
73120121006:
732 The pfil(9) API/ABI for AF_INET family has been changed. Packet
733 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
734 with new kernel.
735
73620121001:
737 The net80211(4) ABI has been changed to allow for improved driver
738 PS-POLL and power-save support. All wireless drivers need to be
739 recompiled to work with the new kernel.
740
74120120913:
742 The random(4) support for the VIA hardware random number
743 generator (`PADLOCK') is no longer enabled unconditionally.
744 Add the padlock_rng device in the custom kernel config if
745 needed. The GENERIC kernels on i386 and amd64 do include the
746 device, so the change only affects the custom kernel
747 configurations.
748
74920120908:
750 The pf(4) packet filter ABI has been changed. pfctl(8) and
751 snmp_pf module need to be recompiled to work with new kernel.
752
75320120828:
754 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
755 to -HEAD. Pools that have empty_bpobj in active state can not be
756 imported read-write with ZFS implementations that do not support
757 this feature. For more information read the zpool-features(5)
758 manual page.
759
76020120727:
761 The sparc64 ZFS loader has been changed to no longer try to auto-
762 detect ZFS providers based on diskN aliases but now requires these
763 to be explicitly listed in the OFW boot-device environment variable.
764
76520120712:
766 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
767 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
768 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
769
77020120712:
771 The following sysctls and tunables have been renamed for consistency
772 with other variables:
773 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
774 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
775
77620120628:
777 The sort utility has been replaced with BSD sort. For now, GNU sort
778 is also available as "gnusort" or the default can be set back to
779 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
780 installed as "bsdsort".
781
78220120611:
783 A new version of ZFS (pool version 5000) has been merged to -HEAD.
784 Starting with this version the old system of ZFS pool versioning
785 is superseded by "feature flags". This concept enables forward
786 compatibility against certain future changes in functionality of ZFS
787 pools. The first read-only compatible "feature flag" for ZFS pools
788 is named "com.delphix:async_destroy". For more information
789 read the new zpool-features(5) manual page.
790 Please refer to the "ZFS notes" section of this file for information
791 on upgrading boot ZFS pools.
792
79320120417:
794 The malloc(3) implementation embedded in libc now uses sources imported
795 as contrib/jemalloc. The most disruptive API change is to
796 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
797 delete it prior to installworld, and optionally re-create it using the
798 new format after rebooting. See malloc.conf(5) for details
799 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
800 NAMESPACE section).
801
80220120328:
803 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
804 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
805 now spelled mips. This is to aid compatibility with third-party
806 software that expects this naming scheme in uname(3). Little-endian
807 settings are unchanged. If you are updating a big-endian mips64 machine
808 from before this change, you may need to set MACHINE_ARCH=mips64 in
809 your environment before the new build system will recognize your machine.
810
81120120306:
812 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
813 platforms.
814
81520120229:
816 Now unix domain sockets behave "as expected" on nullfs(5). Previously
817 nullfs(5) did not pass through all behaviours to the underlying layer,
818 as a result if we bound to a socket on the lower layer we could connect
819 only to the lower path; if we bound to the upper layer we could connect
820 only to the upper path. The new behavior is one can connect to both the
821 lower and the upper paths regardless what layer path one binds to.
822
82320120211:
824 The getifaddrs upgrade path broken with 20111215 has been restored.
825 If you have upgraded in between 20111215 and 20120209 you need to
826 recompile libc again with your kernel. You still need to recompile
827 world to be able to configure CARP but this restriction already
828 comes from 20111215.
829
83020120114:
831 The set_rcvar() function has been removed from /etc/rc.subr. All
832 base and ports rc.d scripts have been updated, so if you have a
833 port installed with a script in /usr/local/etc/rc.d you can either
834 hand-edit the rcvar= line, or reinstall the port.
835
836 An easy way to handle the mass-update of /etc/rc.d:
837 rm /etc/rc.d/* && mergemaster -i
838
83920120109:
840 panic(9) now stops other CPUs in the SMP systems, disables interrupts
841 on the current CPU and prevents other threads from running.
842 This behavior can be reverted using the kern.stop_scheduler_on_panic
843 tunable/sysctl.
844 The new behavior can be incompatible with kern.sync_on_panic.
845
84620111215:
847 The carp(4) facility has been changed significantly. Configuration
848 of the CARP protocol via ifconfig(8) has changed, as well as format
849 of CARP events submitted to devd(8) has changed. See manual pages
850 for more information. The arpbalance feature of carp(4) is currently
851 not supported anymore.
852
853 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
854 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
855 need to be recompiled.
856
85720111122:
858 The acpi_wmi(4) status device /dev/wmistat has been renamed to
859 /dev/wmistat0.
860
86120111108:
862 The option VFS_ALLOW_NONMPSAFE option has been added in order to
863 explicitely support non-MPSAFE filesystems.
864 It is on by default for all supported platform at this present
865 time.
866
86720111101:
868 The broken amd(4) driver has been replaced with esp(4) in the amd64,
869 i386 and pc98 GENERIC kernel configuration files.
870
87120110930:
872 sysinstall has been removed
873
87420110923:
875 The stable/9 branch created in subversion. This corresponds to the
876 RELENG_9 branch in CVS.
877
878COMMON ITEMS:
879
880 General Notes
881 -------------
882 Avoid using make -j when upgrading. While generally safe, there are
883 sometimes problems using -j to upgrade. If your upgrade fails with
884 -j, please try again without -j. From time to time in the past there
885 have been problems using -j with buildworld and/or installworld. This
886 is especially true when upgrading between "distant" versions (eg one
887 that cross a major release boundary or several minor releases, or when
888 several months have passed on the -current branch).
889
890 Sometimes, obscure build problems are the result of environment
891 poisoning. This can happen because the make utility reads its
892 environment when searching for values for global variables. To run
893 your build attempts in an "environmental clean room", prefix all make
894 commands with 'env -i '. See the env(1) manual page for more details.
895
896 When upgrading from one major version to another it is generally best
897 to upgrade to the latest code in the currently installed branch first,
898 then do an upgrade to the new branch. This is the best-tested upgrade
899 path, and has the highest probability of being successful. Please try
900 this approach before reporting problems with a major version upgrade.
901
902 When upgrading a live system, having a root shell around before
903 installing anything can help undo problems. Not having a root shell
904 around can lead to problems if pam has changed too much from your
905 starting point to allow continued authentication after the upgrade.
906
907 ZFS notes
908 ---------
909 When upgrading the boot ZFS pool to a new version, always follow
910 these two steps:
911
912 1.) recompile and reinstall the ZFS boot loader and boot block
913 (this is part of "make buildworld" and "make installworld")
914
915 2.) update the ZFS boot block on your boot drive
916
917 The following example updates the ZFS boot block on the first
918 partition (freebsd-boot) of a GPT partitioned drive ada0:
919 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
920
921 Non-boot pools do not need these updates.
922
923 To build a kernel
924 -----------------
925 If you are updating from a prior version of FreeBSD (even one just
926 a few days old), you should follow this procedure. It is the most
927 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
928
929 make kernel-toolchain
930 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
931 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
932
933 To test a kernel once
934 ---------------------
935 If you just want to boot a kernel once (because you are not sure
936 if it works, or if you want to boot a known bad kernel to provide
937 debugging information) run
938 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
939 nextboot -k testkernel
940
941 To just build a kernel when you know that it won't mess you up
942 --------------------------------------------------------------
943 This assumes you are already running a CURRENT system. Replace
944 ${arch} with the architecture of your machine (e.g. "i386",
945 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
946
947 cd src/sys/${arch}/conf
948 config KERNEL_NAME_HERE
949 cd ../compile/KERNEL_NAME_HERE
950 make depend
951 make
952 make install
953
954 If this fails, go to the "To build a kernel" section.
955
956 To rebuild everything and install it on the current system.
957 -----------------------------------------------------------
958 # Note: sometimes if you are running current you gotta do more than
959 # is listed here if you are upgrading from a really old current.
960
961 <make sure you have good level 0 dumps>
962 make buildworld
963 make kernel KERNCONF=YOUR_KERNEL_HERE
964 [1]
965 <reboot in single user> [3]
966 mergemaster -Fp [5]
967 make installworld
968 mergemaster -Fi [4]
969 make delete-old [6]
970 <reboot>
971
972 To cross-install current onto a separate partition
973 --------------------------------------------------
974 # In this approach we use a separate partition to hold
975 # current's root, 'usr', and 'var' directories. A partition
976 # holding "/", "/usr" and "/var" should be about 2GB in
977 # size.
978
979 <make sure you have good level 0 dumps>
980 <boot into -stable>
981 make buildworld
982 make buildkernel KERNCONF=YOUR_KERNEL_HERE
983 <maybe newfs current's root partition>
984 <mount current's root partition on directory ${CURRENT_ROOT}>
985 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
986 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
987 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
988 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
989 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
990 <reboot into current>
991 <do a "native" rebuild/install as described in the previous section>
992 <maybe install compatibility libraries from ports/misc/compat*>
993 <reboot>
994
995
996 To upgrade in-place from stable to current
997 ----------------------------------------------
998 <make sure you have good level 0 dumps>
999 make buildworld [9]
1000 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1001 [1]
1002 <reboot in single user> [3]
1003 mergemaster -Fp [5]
1004 make installworld
1005 mergemaster -Fi [4]
1006 make delete-old [6]
1007 <reboot>
1008
1009 Make sure that you've read the UPDATING file to understand the
1010 tweaks to various things you need. At this point in the life
1011 cycle of current, things change often and you are on your own
1012 to cope. The defaults can also change, so please read ALL of
1013 the UPDATING entries.
1014
1015 Also, if you are tracking -current, you must be subscribed to
1016 freebsd-current@freebsd.org. Make sure that before you update
1017 your sources that you have read and understood all the recent
1018 messages there. If in doubt, please track -stable which has
1019 much fewer pitfalls.
1020
1021 [1] If you have third party modules, such as vmware, you
1022 should disable them at this point so they don't crash your
1023 system on reboot.
1024
1025 [3] From the bootblocks, boot -s, and then do
1026 fsck -p
1027 mount -u /
1028 mount -a
1029 cd src
1030 adjkerntz -i # if CMOS is wall time
1031 Also, when doing a major release upgrade, it is required that
1032 you boot into single user mode to do the installworld.
1033
1034 [4] Note: This step is non-optional. Failure to do this step
1035 can result in a significant reduction in the functionality of the
1036 system. Attempting to do it by hand is not recommended and those
1037 that pursue this avenue should read this file carefully, as well
1038 as the archives of freebsd-current and freebsd-hackers mailing lists
1039 for potential gotchas. The -U option is also useful to consider.
1040 See mergemaster(8) for more information.
1041
1042 [5] Usually this step is a noop. However, from time to time
1043 you may need to do this if you get unknown user in the following
1044 step. It never hurts to do it all the time. You may need to
1045 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1046 install) after the buildworld before this step if you last updated
1047 from current before 20130425 or from -stable before 20130430.
1048
1049 [6] This only deletes old files and directories. Old libraries
1050 can be deleted by "make delete-old-libs", but you have to make
1051 sure that no program is using those libraries anymore.
1052
1053 [8] In order to have a kernel that can run the 4.x binaries needed to
1054 do an installworld, you must include the COMPAT_FREEBSD4 option in
1055 your kernel. Failure to do so may leave you with a system that is
1056 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1057 required to run the 5.x binaries on more recent kernels. And so on
1058 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1059
1060 Make sure that you merge any new devices from GENERIC since the
1061 last time you updated your kernel config file.
1062
1063 [9] When checking out sources, you must include the -P flag to have
1064 cvs prune empty directories.
1065
1066 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1067 "?=" instead of the "=" assignment operator, so that buildworld can
1068 override the CPUTYPE if it needs to.
1069
1070 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1071 not on the command line, or in /etc/make.conf. buildworld will
1072 warn if it is improperly defined.
1073FORMAT:
1074
1075This file contains a list, in reverse chronological order, of major
1076breakages in tracking -current. It is not guaranteed to be a complete
1077list of such breakages, and only contains entries since October 10, 2007.
1078If you need to see UPDATING entries from before that date, you will need
1079to fetch an UPDATING file from an older FreeBSD release.
1080
1081Copyright information:
1082
1083Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1084
1085Redistribution, publication, translation and use, with or without
1086modification, in full or in part, in any form or format of this
1087document are permitted without further permission from the author.
1088
1089THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1090IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1091WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1092DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1093INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1094(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1095SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1096HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1097STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1098IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1099POSSIBILITY OF SUCH DAMAGE.
1100
1101Contact Warner Losh if you have any questions about your use of
1102this document.
1103
| 184
18520140708:
186 The GNU readline library is now an INTERNALLIB - that is, it is
187 statically linked into consumers (GDB and variants) in the base
188 system, and the shared library is no longer installed. The
189 devel/readline port is available for third party software that
190 requires readline.
191
19220140702:
193 The Itanium architecture (ia64) has been removed from the list of
194 known architectures. This is the first step in the removal of the
195 architecture.
196
19720140701:
198 Commit r268115 has added NFSv4.1 server support, merged from
199 projects/nfsv4.1-server. Since this includes changes to the
200 internal interfaces between the NFS related modules, a full
201 build of the kernel and modules will be necessary.
202 __FreeBSD_version has been bumped.
203
20420140629:
205 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
206 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
207 which differs from the behaviour controlled by this knob.)
208
20920140619:
210 Maximal length of the serial number in CTL was increased from 16 to
211 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
212 and ctld, need to be rebuilt to work with a new kernel.
213
21420140606:
215 The libatf-c and libatf-c++ major versions were downgraded to 0 and
216 1 respectively to match the upstream numbers. They were out of
217 sync because, when they were originally added to FreeBSD, the
218 upstream versions were not respected. These libraries are private
219 and not yet built by default, so renumbering them should be a
220 non-issue. However, unclean source trees will yield broken test
221 programs once the operator executes "make delete-old-libs" after a
222 "make installworld".
223
224 Additionally, the atf-sh binary was made private by moving it into
225 /usr/libexec/. Already-built shell test programs will keep the
226 path to the old binary so they will break after "make delete-old"
227 is run.
228
229 If you are using WITH_TESTS=yes (not the default), wipe the object
230 tree and rebuild from scratch to prevent spurious test failures.
231 This is only needed once: the misnumbered libraries and misplaced
232 binaries have been added to OptionalObsoleteFiles.inc so they will
233 be removed during a clean upgrade.
234
23520140512:
236 Clang and llvm have been upgraded to 3.4.1 release.
237
23820140508:
239 We bogusly installed src.opts.mk in /usr/share/mk. This file should
240 be removed to avoid issues in the future (and has been added to
241 ObsoleteFiles.inc).
242
24320140505:
244 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
245 past, it affected all builds that used the bsd.*.mk files. The old
246 behavior was a bug, but people may have relied upon it. To get this
247 behavior back, you can .include /etc/src.conf from /etc/make.conf
248 (which is still global and isn't changed). This also changes the
249 behavior of incremental builds inside the tree of individual
250 directories. Set MAKESYSPATH to ".../share/mk" to do that.
251 Although this has survived make universe and some upgrade scenarios,
252 other upgrade scenarios may have broken. At least one form of
253 temporary breakage was fixed with MAKESYSPATH settings for buildworld
254 as well... In cases where MAKESYSPATH isn't working with this
255 setting, you'll need to set it to the full path to your tree.
256
257 One side effect of all this cleaning up is that bsd.compiler.mk
258 is no longer implicitly included by bsd.own.mk. If you wish to
259 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
260 as well.
261
26220140430:
263 The lindev device has been removed since /dev/full has been made a
264 standard device. __FreeBSD_version has been bumped.
265
26620140418:
267 The YES_HESIOD knob has been removed. It has been obsolete for
268 a decade. Please move to using WITH_HESIOD instead or your builds
269 will silently lack HESIOD.
270
27120140405:
272 The uart(4) driver has been changed with respect to its handling
273 of the low-level console. Previously the uart(4) driver prevented
274 any process from changing the baudrate or the CLOCAL and HUPCL
275 control flags. By removing the restrictions, operators can make
276 changes to the serial console port without having to reboot.
277 However, when getty(8) is started on the serial device that is
278 associated with the low-level console, a misconfigured terminal
279 line in /etc/ttys will now have a real impact.
280 Before upgrading the kernel, make sure that /etc/ttys has the
281 serial console device configured as 3wire without baudrate to
282 preserve the previous behaviour. E.g:
283 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
284
28520140306:
286 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
287 to improve performance. To re-enable it, if needed, run rpcbind
288 with command line option -W.
289
29020140226:
291 Switched back to the GPL dtc compiler due to updates in the upstream
292 dts files not being supported by the BSDL dtc compiler. You will need
293 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
294 may result while building dtb files during a kernel build if you fail
295 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
296
29720140216:
298 Clang and llvm have been upgraded to 3.4 release.
299
30020140216:
301 The nve(4) driver has been removed. Please use the nfe(4) driver
302 for NVIDIA nForce MCP Ethernet adapters instead.
303
30420140212:
305 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
306 This could cause certain C++ applications using shared libraries built
307 against the previous version of libc++ to crash. The incompatibility
308 has now been fixed, but any C++ applications or shared libraries built
309 between r261283 and r261801 should be recompiled.
310
31120140204:
312 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
313 capability mode support. Please note that enabling the feature in
314 kernel is still highly recommended.
315
31620140131:
317 OpenSSH is now built with sandbox support, and will use sandbox as
318 the default privilege separation method. This requires Capsicum
319 capability mode support in kernel.
320
32120140128:
322 The libelf and libdwarf libraries have been updated to newer
323 versions from upstream. Shared library version numbers for
324 these two libraries were bumped. Any ports or binaries
325 requiring these two libraries should be recompiled.
326 __FreeBSD_version is bumped to 1100006.
327
32820140110:
329 If a Makefile in a tests/ directory was auto-generating a Kyuafile
330 instead of providing an explicit one, this would prevent such
331 Makefile from providing its own Kyuafile in the future during
332 NO_CLEAN builds. This has been fixed in the Makefiles but manual
333 intervention is needed to clean an objdir if you use NO_CLEAN:
334 # find /usr/obj -name Kyuafile | xargs rm -f
335
33620131213:
337 The behavior of gss_pseudo_random() for the krb5 mechanism
338 has changed, for applications requesting a longer random string
339 than produced by the underlying enctype's pseudo-random() function.
340 In particular, the random string produced from a session key of
341 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
342 be different at the 17th octet and later, after this change.
343 The counter used in the PRF+ construction is now encoded as a
344 big-endian integer in accordance with RFC 4402.
345 __FreeBSD_version is bumped to 1100004.
346
34720131108:
348 The WITHOUT_ATF build knob has been removed and its functionality
349 has been subsumed into the more generic WITHOUT_TESTS. If you were
350 using the former to disable the build of the ATF libraries, you
351 should change your settings to use the latter.
352
35320131025:
354 The default version of mtree is nmtree which is obtained from
355 NetBSD. The output is generally the same, but may vary
356 slightly. If you found you need identical output adding
357 "-F freebsd9" to the command line should do the trick. For the
358 time being, the old mtree is available as fmtree.
359
36020131014:
361 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
362 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
363 1.1.4_8 and verify bsdyml not linked in, before running "make
364 delete-old-libs":
365 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
366 or
367 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
368
36920131010:
370 The rc.d/jail script has been updated to support jail(8)
371 configuration file. The "jail_<jname>_*" rc.conf(5) variables
372 for per-jail configuration are automatically converted to
373 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
374 This is transparently backward compatible. See below about some
375 incompatibilities and rc.conf(5) manual page for more details.
376
377 These variables are now deprecated in favor of jail(8) configuration
378 file. One can use "rc.d/jail config <jname>" command to generate
379 a jail(8) configuration file in /var/run/jail.<jname>.conf without
380 running the jail(8) utility. The default pathname of the
381 configuration file is /etc/jail.conf and can be specified by
382 using $jail_conf or $jail_<jname>_conf variables.
383
384 Please note that jail_devfs_ruleset accepts an integer at
385 this moment. Please consider to rewrite the ruleset name
386 with an integer.
387
38820130930:
389 BIND has been removed from the base system. If all you need
390 is a local resolver, simply enable and start the local_unbound
391 service instead. Otherwise, several versions of BIND are
392 available in the ports tree. The dns/bind99 port is one example.
393
394 With this change, nslookup(1) and dig(1) are no longer in the base
395 system. Users should instead use host(1) and drill(1) which are
396 in the base system. Alternatively, nslookup and dig can
397 be obtained by installing the dns/bind-tools port.
398
39920130916:
400 With the addition of unbound(8), a new unbound user is now
401 required during installworld. "mergemaster -p" can be used to
402 add the user prior to installworld, as documented in the handbook.
403
40420130911:
405 OpenSSH is now built with DNSSEC support, and will by default
406 silently trust signed SSHFP records. This can be controlled with
407 the VerifyHostKeyDNS client configuration setting. DNSSEC support
408 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
409
41020130906:
411 The GNU Compiler Collection and C++ standard library (libstdc++)
412 are no longer built by default on platforms where clang is the system
413 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
414 options in src.conf.
415
41620130905:
417 The PROCDESC kernel option is now part of the GENERIC kernel
418 configuration and is required for the rwhod(8) to work.
419 If you are using custom kernel configuration, you should include
420 'options PROCDESC'.
421
42220130905:
423 The API and ABI related to the Capsicum framework was modified
424 in backward incompatible way. The userland libraries and programs
425 have to be recompiled to work with the new kernel. This includes the
426 following libraries and programs, but the whole buildworld is
427 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
428 kdump, procstat, rwho, rwhod, uniq.
429
43020130903:
431 AES-NI intrinsic support has been added to gcc. The AES-NI module
432 has been updated to use this support. A new gcc is required to build
433 the aesni module on both i386 and amd64.
434
43520130821:
436 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
437 Thus "device padlock_rng" and "device rdrand_rng" should be
438 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
439
44020130813:
441 WITH_ICONV has been split into two feature sets. WITH_ICONV now
442 enables just the iconv* functionality and is now on by default.
443 WITH_LIBICONV_COMPAT enables the libiconv api and link time
444 compatability. Set WITHOUT_ICONV to build the old way.
445 If you have been using WITH_ICONV before, you will very likely
446 need to turn on WITH_LIBICONV_COMPAT.
447
44820130806:
449 INVARIANTS option now enables DEBUG for code with OpenSolaris and
450 Illumos origin, including ZFS. If you have INVARIANTS in your
451 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
452 explicitly.
453 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
454 locks if WITNESS option was set. Because that generated a lot of
455 witness(9) reports and all of them were believed to be false
456 positives, this is no longer done. New option OPENSOLARIS_WITNESS
457 can be used to achieve the previous behavior.
458
45920130806:
460 Timer values in IPv6 data structures now use time_uptime instead
461 of time_second. Although this is not a user-visible functional
462 change, userland utilities which directly use them---ndp(8),
463 rtadvd(8), and rtsold(8) in the base system---need to be updated
464 to r253970 or later.
465
46620130802:
467 find -delete can now delete the pathnames given as arguments,
468 instead of only files found below them or if the pathname did
469 not contain any slashes. Formerly, the following error message
470 would result:
471
472 find: -delete: <path>: relative path potentially not safe
473
474 Deleting the pathnames given as arguments can be prevented
475 without error messages using -mindepth 1 or by changing
476 directory and passing "." as argument to find. This works in the
477 old as well as the new version of find.
478
47920130726:
480 Behavior of devfs rules path matching has been changed.
481 Pattern is now always matched against fully qualified devfs
482 path and slash characters must be explicitly matched by
483 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
484 subdirectories must be reviewed.
485
48620130716:
487 The default ARM ABI has changed to the ARM EABI. The old ABI is
488 incompatible with the ARM EABI and all programs and modules will
489 need to be rebuilt to work with a new kernel.
490
491 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
492
493 NOTE: Support for the old ABI will be removed in the future and
494 users are advised to upgrade.
495
49620130709:
497 pkg_install has been disconnected from the build if you really need it
498 you should add WITH_PKGTOOLS in your src.conf(5).
499
50020130709:
501 Most of network statistics structures were changed to be able
502 keep 64-bits counters. Thus all tools, that work with networking
503 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
504
50520130629:
506 Fix targets that run multiple make's to use && rather than ;
507 so that subsequent steps depend on success of previous.
508
509 NOTE: if building 'universe' with -j* on stable/8 or stable/9
510 it would be better to start the build using bmake, to avoid
511 overloading the machine.
512
51320130618:
514 Fix a bug that allowed a tracing process (e.g. gdb) to write
515 to a memory-mapped file in the traced process's address space
516 even if neither the traced process nor the tracing process had
517 write access to that file.
518
51920130615:
520 CVS has been removed from the base system. An exact copy
521 of the code is available from the devel/cvs port.
522
52320130613:
524 Some people report the following error after the switch to bmake:
525
526 make: illegal option -- J
527 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
528 ...
529 *** [buildworld] Error code 2
530
531 this likely due to an old instance of make in
532 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
533 which src/Makefile will use that blindly, if it exists, so if
534 you see the above error:
535
536 rm -rf `make -V MAKEPATH`
537
538 should resolve it.
539
54020130516:
541 Use bmake by default.
542 Whereas before one could choose to build with bmake via
543 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
544 make. The goal is to remove these knobs for 10-RELEASE.
545
546 It is worth noting that bmake (like gmake) treats the command
547 line as the unit of failure, rather than statements within the
548 command line. Thus '(cd some/where && dosomething)' is safer
549 than 'cd some/where; dosomething'. The '()' allows consistent
550 behavior in parallel build.
551
55220130429:
553 Fix a bug that allows NFS clients to issue READDIR on files.
554
55520130426:
556 The WITHOUT_IDEA option has been removed because
557 the IDEA patent expired.
558
55920130426:
560 The sysctl which controls TRIM support under ZFS has been renamed
561 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
562 enabled by default.
563
56420130425:
565 The mergemaster command now uses the default MAKEOBJDIRPREFIX
566 rather than creating it's own in the temporary directory in
567 order allow access to bootstrapped versions of tools such as
568 install and mtree. When upgrading from version of FreeBSD where
569 the install command does not support -l, you will need to
570 install a new mergemaster command if mergemaster -p is required.
571 This can be accomplished with the command (cd src/usr.sbin/mergemaster
572 && make install).
573
57420130404:
575 Legacy ATA stack, disabled and replaced by new CAM-based one since
576 FreeBSD 9.0, completely removed from the sources. Kernel modules
577 atadisk and atapi*, user-level tools atacontrol and burncd are
578 removed. Kernel option `options ATA_CAM` is now permanently enabled
579 and removed.
580
58120130319:
582 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
583 and socketpair(2). Software, in particular Kerberos, may
584 automatically detect and use these during building. The resulting
585 binaries will not work on older kernels.
586
58720130308:
588 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
589 information, see the respective 20130304 entry).
590
59120130304:
592 Recent commits to callout(9) changed the size of struct callout,
593 so the KBI is probably heavily disturbed. Also, some functions
594 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
595 by macros. Every kernel module using it won't load, so rebuild
596 is requested.
597
598 The ctl device has been re-enabled in GENERIC for i386 and amd64,
599 but does not initialize by default (because of the new CTL_DISABLE
600 option) to save memory. To re-enable it, remove the CTL_DISABLE
601 option from the kernel config file or set kern.cam.ctl.disable=0
602 in /boot/loader.conf.
603
60420130301:
605 The ctl device has been disabled in GENERIC for i386 and amd64.
606 This was done due to the extra memory being allocated at system
607 initialisation time by the ctl driver which was only used if
608 a CAM target device was created. This makes a FreeBSD system
609 unusable on 128MB or less of RAM.
610
61120130208:
612 A new compression method (lz4) has been merged to -HEAD. Please
613 refer to zpool-features(7) for more information.
614
615 Please refer to the "ZFS notes" section of this file for information
616 on upgrading boot ZFS pools.
617
61820130129:
619 A BSD-licensed patch(1) variant has been added and is installed
620 as bsdpatch, being the GNU version the default patch.
621 To inverse the logic and use the BSD-licensed one as default,
622 while having the GNU version installed as gnupatch, rebuild
623 and install world with the WITH_BSD_PATCH knob set.
624
62520130121:
626 Due to the use of the new -l option to install(1) during build
627 and install, you must take care not to directly set the INSTALL
628 make variable in your /etc/make.conf, /etc/src.conf, or on the
629 command line. If you wish to use the -C flag for all installs
630 you may be able to add INSTALL+=-C to /etc/make.conf or
631 /etc/src.conf.
632
63320130118:
634 The install(1) option -M has changed meaning and now takes an
635 argument that is a file or path to append logs to. In the
636 unlikely event that -M was the last option on the command line
637 and the command line contained at least two files and a target
638 directory the first file will have logs appended to it. The -M
639 option served little practical purpose in the last decade so its
640 use is expected to be extremely rare.
641
64220121223:
643 After switching to Clang as the default compiler some users of ZFS
644 on i386 systems started to experience stack overflow kernel panics.
645 Please consider using 'options KSTACK_PAGES=4' in such configurations.
646
64720121222:
648 GEOM_LABEL now mangles label names read from file system metadata.
649 Mangling affect labels containing spaces, non-printable characters,
650 '%' or '"'. Device names in /etc/fstab and other places may need to
651 be updated.
652
65320121217:
654 By default, only the 10 most recent kernel dumps will be saved. To
655 restore the previous behaviour (no limit on the number of kernel dumps
656 stored in the dump directory) add the following line to /etc/rc.conf:
657
658 savecore_flags=""
659
66020121201:
661 With the addition of auditdistd(8), a new auditdistd user is now
662 required during installworld. "mergemaster -p" can be used to
663 add the user prior to installworld, as documented in the handbook.
664
66520121117:
666 The sin6_scope_id member variable in struct sockaddr_in6 is now
667 filled by the kernel before passing the structure to the userland via
668 sysctl or routing socket. This means the KAME-specific embedded scope
669 id in sin6_addr.s6_addr[2] is always cleared in userland application.
670 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
671 __FreeBSD_version is bumped to 1000025.
672
67320121105:
674 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
675 This means that the world and kernel will be compiled with clang
676 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
677 and /usr/bin/cpp. To disable this behavior and revert to building
678 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
679 of current may need to bootstrap WITHOUT_CLANG first if the clang
680 build fails (its compatibility window doesn't extend to the 9 stable
681 branch point).
682
68320121102:
684 The IPFIREWALL_FORWARD kernel option has been removed. Its
685 functionality now turned on by default.
686
68720121023:
688 The ZERO_COPY_SOCKET kernel option has been removed and
689 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
690 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
691 mechanism which is not safe and may result in kernel crashes.
692 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
693 driver supports disposeable external page sized mbuf storage.
694 Proper replacements for both zero-copy mechanisms are under
695 consideration and will eventually lead to complete removal
696 of the two kernel options.
697
69820121023:
699 The IPv4 network stack has been converted to network byte
700 order. The following modules need to be recompiled together
701 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
702 pf(4), ipfw(4), ng_ipfw(4), stf(4).
703
70420121022:
705 Support for non-MPSAFE filesystems was removed from VFS. The
706 VFS_VERSION was bumped, all filesystem modules shall be
707 recompiled.
708
70920121018:
710 All the non-MPSAFE filesystems have been disconnected from
711 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
712 portalfs, smbfs, xfs.
713
71420121016:
715 The interface cloning API and ABI has changed. The following
716 modules need to be recompiled together with kernel:
717 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
718 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
719 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
720
72120121015:
722 The sdhci driver was split in two parts: sdhci (generic SD Host
723 Controller logic) and sdhci_pci (actual hardware driver).
724 No kernel config modifications are required, but if you
725 load sdhc as a module you must switch to sdhci_pci instead.
726
72720121014:
728 Import the FUSE kernel and userland support into base system.
729
73020121013:
731 The GNU sort(1) program has been removed since the BSD-licensed
732 sort(1) has been the default for quite some time and no serious
733 problems have been reported. The corresponding WITH_GNU_SORT
734 knob has also gone.
735
73620121006:
737 The pfil(9) API/ABI for AF_INET family has been changed. Packet
738 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
739 with new kernel.
740
74120121001:
742 The net80211(4) ABI has been changed to allow for improved driver
743 PS-POLL and power-save support. All wireless drivers need to be
744 recompiled to work with the new kernel.
745
74620120913:
747 The random(4) support for the VIA hardware random number
748 generator (`PADLOCK') is no longer enabled unconditionally.
749 Add the padlock_rng device in the custom kernel config if
750 needed. The GENERIC kernels on i386 and amd64 do include the
751 device, so the change only affects the custom kernel
752 configurations.
753
75420120908:
755 The pf(4) packet filter ABI has been changed. pfctl(8) and
756 snmp_pf module need to be recompiled to work with new kernel.
757
75820120828:
759 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
760 to -HEAD. Pools that have empty_bpobj in active state can not be
761 imported read-write with ZFS implementations that do not support
762 this feature. For more information read the zpool-features(5)
763 manual page.
764
76520120727:
766 The sparc64 ZFS loader has been changed to no longer try to auto-
767 detect ZFS providers based on diskN aliases but now requires these
768 to be explicitly listed in the OFW boot-device environment variable.
769
77020120712:
771 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
772 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
773 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
774
77520120712:
776 The following sysctls and tunables have been renamed for consistency
777 with other variables:
778 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
779 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
780
78120120628:
782 The sort utility has been replaced with BSD sort. For now, GNU sort
783 is also available as "gnusort" or the default can be set back to
784 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
785 installed as "bsdsort".
786
78720120611:
788 A new version of ZFS (pool version 5000) has been merged to -HEAD.
789 Starting with this version the old system of ZFS pool versioning
790 is superseded by "feature flags". This concept enables forward
791 compatibility against certain future changes in functionality of ZFS
792 pools. The first read-only compatible "feature flag" for ZFS pools
793 is named "com.delphix:async_destroy". For more information
794 read the new zpool-features(5) manual page.
795 Please refer to the "ZFS notes" section of this file for information
796 on upgrading boot ZFS pools.
797
79820120417:
799 The malloc(3) implementation embedded in libc now uses sources imported
800 as contrib/jemalloc. The most disruptive API change is to
801 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
802 delete it prior to installworld, and optionally re-create it using the
803 new format after rebooting. See malloc.conf(5) for details
804 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
805 NAMESPACE section).
806
80720120328:
808 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
809 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
810 now spelled mips. This is to aid compatibility with third-party
811 software that expects this naming scheme in uname(3). Little-endian
812 settings are unchanged. If you are updating a big-endian mips64 machine
813 from before this change, you may need to set MACHINE_ARCH=mips64 in
814 your environment before the new build system will recognize your machine.
815
81620120306:
817 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
818 platforms.
819
82020120229:
821 Now unix domain sockets behave "as expected" on nullfs(5). Previously
822 nullfs(5) did not pass through all behaviours to the underlying layer,
823 as a result if we bound to a socket on the lower layer we could connect
824 only to the lower path; if we bound to the upper layer we could connect
825 only to the upper path. The new behavior is one can connect to both the
826 lower and the upper paths regardless what layer path one binds to.
827
82820120211:
829 The getifaddrs upgrade path broken with 20111215 has been restored.
830 If you have upgraded in between 20111215 and 20120209 you need to
831 recompile libc again with your kernel. You still need to recompile
832 world to be able to configure CARP but this restriction already
833 comes from 20111215.
834
83520120114:
836 The set_rcvar() function has been removed from /etc/rc.subr. All
837 base and ports rc.d scripts have been updated, so if you have a
838 port installed with a script in /usr/local/etc/rc.d you can either
839 hand-edit the rcvar= line, or reinstall the port.
840
841 An easy way to handle the mass-update of /etc/rc.d:
842 rm /etc/rc.d/* && mergemaster -i
843
84420120109:
845 panic(9) now stops other CPUs in the SMP systems, disables interrupts
846 on the current CPU and prevents other threads from running.
847 This behavior can be reverted using the kern.stop_scheduler_on_panic
848 tunable/sysctl.
849 The new behavior can be incompatible with kern.sync_on_panic.
850
85120111215:
852 The carp(4) facility has been changed significantly. Configuration
853 of the CARP protocol via ifconfig(8) has changed, as well as format
854 of CARP events submitted to devd(8) has changed. See manual pages
855 for more information. The arpbalance feature of carp(4) is currently
856 not supported anymore.
857
858 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
859 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
860 need to be recompiled.
861
86220111122:
863 The acpi_wmi(4) status device /dev/wmistat has been renamed to
864 /dev/wmistat0.
865
86620111108:
867 The option VFS_ALLOW_NONMPSAFE option has been added in order to
868 explicitely support non-MPSAFE filesystems.
869 It is on by default for all supported platform at this present
870 time.
871
87220111101:
873 The broken amd(4) driver has been replaced with esp(4) in the amd64,
874 i386 and pc98 GENERIC kernel configuration files.
875
87620110930:
877 sysinstall has been removed
878
87920110923:
880 The stable/9 branch created in subversion. This corresponds to the
881 RELENG_9 branch in CVS.
882
883COMMON ITEMS:
884
885 General Notes
886 -------------
887 Avoid using make -j when upgrading. While generally safe, there are
888 sometimes problems using -j to upgrade. If your upgrade fails with
889 -j, please try again without -j. From time to time in the past there
890 have been problems using -j with buildworld and/or installworld. This
891 is especially true when upgrading between "distant" versions (eg one
892 that cross a major release boundary or several minor releases, or when
893 several months have passed on the -current branch).
894
895 Sometimes, obscure build problems are the result of environment
896 poisoning. This can happen because the make utility reads its
897 environment when searching for values for global variables. To run
898 your build attempts in an "environmental clean room", prefix all make
899 commands with 'env -i '. See the env(1) manual page for more details.
900
901 When upgrading from one major version to another it is generally best
902 to upgrade to the latest code in the currently installed branch first,
903 then do an upgrade to the new branch. This is the best-tested upgrade
904 path, and has the highest probability of being successful. Please try
905 this approach before reporting problems with a major version upgrade.
906
907 When upgrading a live system, having a root shell around before
908 installing anything can help undo problems. Not having a root shell
909 around can lead to problems if pam has changed too much from your
910 starting point to allow continued authentication after the upgrade.
911
912 ZFS notes
913 ---------
914 When upgrading the boot ZFS pool to a new version, always follow
915 these two steps:
916
917 1.) recompile and reinstall the ZFS boot loader and boot block
918 (this is part of "make buildworld" and "make installworld")
919
920 2.) update the ZFS boot block on your boot drive
921
922 The following example updates the ZFS boot block on the first
923 partition (freebsd-boot) of a GPT partitioned drive ada0:
924 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
925
926 Non-boot pools do not need these updates.
927
928 To build a kernel
929 -----------------
930 If you are updating from a prior version of FreeBSD (even one just
931 a few days old), you should follow this procedure. It is the most
932 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
933
934 make kernel-toolchain
935 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
936 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
937
938 To test a kernel once
939 ---------------------
940 If you just want to boot a kernel once (because you are not sure
941 if it works, or if you want to boot a known bad kernel to provide
942 debugging information) run
943 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
944 nextboot -k testkernel
945
946 To just build a kernel when you know that it won't mess you up
947 --------------------------------------------------------------
948 This assumes you are already running a CURRENT system. Replace
949 ${arch} with the architecture of your machine (e.g. "i386",
950 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
951
952 cd src/sys/${arch}/conf
953 config KERNEL_NAME_HERE
954 cd ../compile/KERNEL_NAME_HERE
955 make depend
956 make
957 make install
958
959 If this fails, go to the "To build a kernel" section.
960
961 To rebuild everything and install it on the current system.
962 -----------------------------------------------------------
963 # Note: sometimes if you are running current you gotta do more than
964 # is listed here if you are upgrading from a really old current.
965
966 <make sure you have good level 0 dumps>
967 make buildworld
968 make kernel KERNCONF=YOUR_KERNEL_HERE
969 [1]
970 <reboot in single user> [3]
971 mergemaster -Fp [5]
972 make installworld
973 mergemaster -Fi [4]
974 make delete-old [6]
975 <reboot>
976
977 To cross-install current onto a separate partition
978 --------------------------------------------------
979 # In this approach we use a separate partition to hold
980 # current's root, 'usr', and 'var' directories. A partition
981 # holding "/", "/usr" and "/var" should be about 2GB in
982 # size.
983
984 <make sure you have good level 0 dumps>
985 <boot into -stable>
986 make buildworld
987 make buildkernel KERNCONF=YOUR_KERNEL_HERE
988 <maybe newfs current's root partition>
989 <mount current's root partition on directory ${CURRENT_ROOT}>
990 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
991 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
992 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
993 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
994 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
995 <reboot into current>
996 <do a "native" rebuild/install as described in the previous section>
997 <maybe install compatibility libraries from ports/misc/compat*>
998 <reboot>
999
1000
1001 To upgrade in-place from stable to current
1002 ----------------------------------------------
1003 <make sure you have good level 0 dumps>
1004 make buildworld [9]
1005 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1006 [1]
1007 <reboot in single user> [3]
1008 mergemaster -Fp [5]
1009 make installworld
1010 mergemaster -Fi [4]
1011 make delete-old [6]
1012 <reboot>
1013
1014 Make sure that you've read the UPDATING file to understand the
1015 tweaks to various things you need. At this point in the life
1016 cycle of current, things change often and you are on your own
1017 to cope. The defaults can also change, so please read ALL of
1018 the UPDATING entries.
1019
1020 Also, if you are tracking -current, you must be subscribed to
1021 freebsd-current@freebsd.org. Make sure that before you update
1022 your sources that you have read and understood all the recent
1023 messages there. If in doubt, please track -stable which has
1024 much fewer pitfalls.
1025
1026 [1] If you have third party modules, such as vmware, you
1027 should disable them at this point so they don't crash your
1028 system on reboot.
1029
1030 [3] From the bootblocks, boot -s, and then do
1031 fsck -p
1032 mount -u /
1033 mount -a
1034 cd src
1035 adjkerntz -i # if CMOS is wall time
1036 Also, when doing a major release upgrade, it is required that
1037 you boot into single user mode to do the installworld.
1038
1039 [4] Note: This step is non-optional. Failure to do this step
1040 can result in a significant reduction in the functionality of the
1041 system. Attempting to do it by hand is not recommended and those
1042 that pursue this avenue should read this file carefully, as well
1043 as the archives of freebsd-current and freebsd-hackers mailing lists
1044 for potential gotchas. The -U option is also useful to consider.
1045 See mergemaster(8) for more information.
1046
1047 [5] Usually this step is a noop. However, from time to time
1048 you may need to do this if you get unknown user in the following
1049 step. It never hurts to do it all the time. You may need to
1050 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1051 install) after the buildworld before this step if you last updated
1052 from current before 20130425 or from -stable before 20130430.
1053
1054 [6] This only deletes old files and directories. Old libraries
1055 can be deleted by "make delete-old-libs", but you have to make
1056 sure that no program is using those libraries anymore.
1057
1058 [8] In order to have a kernel that can run the 4.x binaries needed to
1059 do an installworld, you must include the COMPAT_FREEBSD4 option in
1060 your kernel. Failure to do so may leave you with a system that is
1061 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1062 required to run the 5.x binaries on more recent kernels. And so on
1063 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1064
1065 Make sure that you merge any new devices from GENERIC since the
1066 last time you updated your kernel config file.
1067
1068 [9] When checking out sources, you must include the -P flag to have
1069 cvs prune empty directories.
1070
1071 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1072 "?=" instead of the "=" assignment operator, so that buildworld can
1073 override the CPUTYPE if it needs to.
1074
1075 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1076 not on the command line, or in /etc/make.conf. buildworld will
1077 warn if it is improperly defined.
1078FORMAT:
1079
1080This file contains a list, in reverse chronological order, of major
1081breakages in tracking -current. It is not guaranteed to be a complete
1082list of such breakages, and only contains entries since October 10, 2007.
1083If you need to see UPDATING entries from before that date, you will need
1084to fetch an UPDATING file from an older FreeBSD release.
1085
1086Copyright information:
1087
1088Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1089
1090Redistribution, publication, translation and use, with or without
1091modification, in full or in part, in any form or format of this
1092document are permitted without further permission from the author.
1093
1094THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1095IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1096WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1097DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1098INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1099(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1100SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1101HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1102STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1103IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1104POSSIBILITY OF SUCH DAMAGE.
1105
1106Contact Warner Losh if you have any questions about your use of
1107this document.
1108
|