1 Updating Information for FreeBSD current users.
3 This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>.
4 See end of file for further details. For commonly done items, please see the
5 COMMON ITEMS: section later in the file. These instructions assume that you
6 basically know what you are doing. If not, then please consult the FreeBSD
9 http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
11 Items affecting the ports and packages system can be found in
12 /usr/ports/UPDATING. Please read that file before running portupgrade.
14 NOTE: FreeBSD has switched from gcc to clang. If you have trouble bootstrapping
15 from older versions of FreeBSD, try WITHOUT_CLANG and WITH_GCC to bootstrap to
16 the tip of head, and then rebuild without this option. The bootstrap process
17 from older version of current across the gcc/clang cutover is a bit fragile.
19 NOTE TO PEOPLE WHO THINK THAT FreeBSD 12.x IS SLOW:
20 FreeBSD 12.x has many debugging features turned on, in both the kernel
21 and userland. These features attempt to detect incorrect use of
22 system primitives, and encourage loud failure through extra sanity
23 checking and fail stop semantics. They also substantially impact
24 system performance. If you want to do performance measurement,
25 benchmarking, and optimization, you'll want to turn them off. This
26 includes various WITNESS- related kernel options, INVARIANTS, malloc
27 debugging flags in userland, and various verbose features in the
28 kernel. Many developers choose to disable these features on build
29 machines to maximize performance. (To completely disable malloc
30 debugging, define MALLOC_PRODUCTION in /etc/make.conf, or to merely
31 disable the most expensive debugging functionality run
32 "ln -s 'abort:false,junk:false' /etc/malloc.conf".)
35 GNU rcs has been removed rom base. It is available as packages:
36 - rcs: Latest GPLv3 GNU rcs version.
37 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
40 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
41 modules now requires that the kernel configuration contain the
42 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
45 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
46 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
49 Relocatable object files with the extension of .So have been renamed
50 to use an extension of .pico instead. The purpose of this change is
51 to avoid a name clash with shared libraries on case-insensitive file
52 systems. On those file systems, foo.So is the same file as foo.so.
55 GNU rcs has been turned off by default. It can (temporarily) be built
56 again by adding WITH_RCS knob in src.conf.
57 Otherwise, GNU rcs is available from packages:
58 - rcs: Latest GPLv3 GNU rcs version.
59 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
62 The backup_uses_rcs functionality has been removed from rc.subr.
65 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
66 two separate components, QUEUE_MACRO_DEBUG_TRACE and
67 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
68 QUEUE_MACRO_DEBUG behavior.
71 r304787 changed some ioctl interfaces between the iSCSI userspace
72 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
73 rebuilt to work with new kernels. __FreeBSD_version has been bumped
77 The UDP receive code has been updated to only treat incoming UDP
78 packets that were addressed to an L2 broadcast address as L3
79 broadcast packets. It is not expected that this will affect any
80 standards-conforming UDP application. The new behaviour can be
81 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
85 Remove the openbsd_poll system call.
86 __FreeBSD_version has been bumped because of this.
89 The libc stub for the pipe(2) system call has been replaced with
90 a wrapper that calls the pipe2(2) system call and the pipe(2)
91 system call is now only implemented by the kernels that include
92 "options COMPAT_FREEBSD10" in their config file (this is the
93 default). Users should ensure that this option is enabled in
94 their kernel or upgrade userspace to r302092 before upgrading their
98 CAM will now strip leading spaces from SCSI disks' serial numbers.
99 This will effect users who create UFS filesystems on SCSI disks using
100 those disk's diskid device nodes. For example, if /etc/fstab
101 previously contained a line like
102 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
103 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
104 transforms like gmirror may also be affected. ZFS users should
108 The bitstring(3) API has been updated with new functionality and
109 improved performance. But it is binary-incompatible with the old API.
110 Objects built with the new headers may not be linked against objects
111 built with the old headers.
114 The brk and sbrk functions have been removed from libc on arm64.
115 Binutils from ports has been updated to not link to these
116 functions and should be updated to the latest version before
117 installing a new libc.
120 The armv6 port now defaults to hard float ABI. Limited support
121 for running both hardfloat and soft float on the same system
122 is available using the libraries installed with -DWITH_LIBSOFT.
123 This has only been tested as an upgrade path for installworld
124 and packages may fail or need manual intervention to run. New
125 packages will be needed.
127 To update an existing self-hosted armv6hf system, you must add
128 TARGET_ARCH=armv6 on the make command line for both the build
129 and the install steps.
132 Kernel modules compiled outside of a kernel build now default to
133 installing to /boot/modules instead of /boot/kernel. Many kernel
134 modules built this way (such as those in ports) already overrode
135 KMODDIR explicitly to install into /boot/modules. However,
136 manually building and installing a module from /sys/modules will
137 now install to /boot/modules instead of /boot/kernel.
140 The CAM I/O scheduler has been committed to the kernel. There should be
141 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
142 list of known rogues that claim support for this but actually corrupt
143 data is believed to be complete, be on the lookout for data
144 corruption. The known rogue list is believed to be complete:
146 o Crucial MX100, M550 drives with MU01 firmware.
147 o Micron M510 and M550 drives with MU01 firmware.
148 o Micron M500 prior to MU07 firmware
149 o Samsung 830, 840, and 850 all firmwares
150 o FCCT M500 all firmwares
152 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
153 with working NCQ TRIM. For Micron branded drives, see your sales rep for
154 updated firmware. Black listed drives will work correctly because these
155 drives work correctly so long as no NCQ TRIMs are sent to them. Given
156 this list is the same as found in Linux, it's believed there are no
157 other rogues in the market place. All other models from the above
160 To be safe, if you are at all concerned, you can quirk each of your
161 drives to prevent NCQ from being sent by setting:
162 kern.cam.ada.X.quirks="0x2"
163 in loader.conf. If the drive requires the 4k sector quirk, set the
167 The FAST_DEPEND build option has been removed and its functionality is
168 now the one true way. The old mkdep(1) style of 'make depend' has
169 been removed. See 20160311 for further details.
172 Resource range types have grown from unsigned long to uintmax_t. All
173 drivers, and anything using libdevinfo, need to be recompiled.
176 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
177 builds. It no longer runs mkdep(1) during 'make depend', and the
178 'make depend' stage can safely be skipped now as it is auto ran
179 when building 'make all' and will generate all SRCS and DPSRCS before
180 building anything else. Dependencies are gathered at compile time with
181 -MF flags kept in separate .depend files per object file. Users should
182 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
186 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
187 kernel modules. Therefore, if you load any kernel modules at boot time,
188 please install the boot loaders after you install the kernel, but before
192 make kernel KERNCONF=YOUR_KERNEL_HERE
193 make -C sys/boot install
194 <reboot in single user>
196 Then follow the usual steps, described in the General Notes section,
200 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
201 see the 20141231 entry below for information about prerequisites and
202 upgrading, if you are not already using clang 3.5.0 or higher.
205 The AIO subsystem is now a standard part of the kernel. The
206 VFS_AIO kernel option and aio.ko kernel module have been removed.
207 Due to stability concerns, asynchronous I/O requests are only
208 permitted on sockets and raw disks by default. To enable
209 asynchronous I/O requests on all file types, set the
210 vfs.aio.enable_unsafe sysctl to a non-zero value.
213 The ELF object manipulation tool objcopy is now provided by the
214 ELF Tool Chain project rather than by GNU binutils. It should be a
215 drop-in replacement, with the addition of arm64 support. The
216 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
217 to obtain the GNU version if necessary.
220 Building ZFS pools on top of zvols is prohibited by default. That
221 feature has never worked safely; it's always been prone to deadlocks.
222 Using a zvol as the backing store for a VM guest's virtual disk will
223 still work, even if the guest is using ZFS. Legacy behavior can be
224 restored by setting vfs.zfs.vol.recursive=1.
227 The NONE and HPN patches has been removed from OpenSSH. They are
228 still available in the security/openssh-portable port.
231 With the addition of ypldap(8), a new _ypldap user is now required
232 during installworld. "mergemaster -p" can be used to add the user
233 prior to installworld, as documented in the handbook.
236 The tftp loader (pxeboot) now uses the option root-path directive. As a
237 consequence it no longer looks for a pxeboot.4th file on the tftp
238 server. Instead it uses the regular /boot infrastructure as with the
242 The code to start recording plug and play data into the modules has
243 been committed. While the old tools will properly build a new kernel,
244 a number of warnings about "unknown metadata record 4" will be produced
245 for an older kldxref. To avoid such warnings, make sure to rebuild
246 the kernel toolchain (or world). Make sure that you have r292078 or
247 later when trying to build 292077 or later before rebuilding.
250 Debug data files are now built by default with 'make buildworld' and
251 installed with 'make installworld'. This facilitates debugging but
252 requires more disk space both during the build and for the installed
253 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
257 r291527 changed the internal interface between the nfsd.ko and
258 nfscommon.ko modules. As such, they must both be upgraded to-gether.
259 __FreeBSD_version has been bumped because of this.
262 Add support for unicode collation strings leads to a change of
263 order of files listed by ls(1) for example. To get back to the old
264 behaviour, set LC_COLLATE environment variable to "C".
266 Databases administrators will need to reindex their databases given
267 collation results will be different.
269 Due to a bug in install(1) it is recommended to remove the ancient
270 locales before running make installworld.
272 rm -rf /usr/share/locale/*
275 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
276 libcrypto.so.7 or libssl.so.7 must be recompiled.
279 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
280 Kernel modules isp_2400_multi and isp_2500_multi were removed and
281 should be replaced with isp_2400 and isp_2500 modules respectively.
284 The build previously allowed using 'make -n' to not recurse into
285 sub-directories while showing what commands would be executed, and
286 'make -n -n' to recursively show commands. Now 'make -n' will recurse
287 and 'make -N' will not.
290 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
291 and etcupdate will now use this file. A custom sendmail.cf is now
292 updated via this mechanism rather than via installworld. If you had
293 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
294 want to remove the exclusion or change it to "always install".
295 /etc/mail/sendmail.cf is now managed the same way regardless of
296 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
297 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
300 Compatibility shims for legacy ATA device names have been removed.
301 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
302 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
303 environment variables, /dev/ad* and /dev/ar* symbolic links.
306 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
307 Please see the 20141231 entry below for information about prerequisites
308 and upgrading, if you are not already using clang 3.5.0 or higher.
311 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
312 and renamed from .symbols to .debug. This reduces the size requirements
313 on the boot partition or file system and provides consistency with
314 userland debug files.
316 When using the supported kernel installation method the
317 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
318 as is done with /boot/kernel.
320 Developers wishing to maintain the historical behavior of installing
321 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
324 The wireless drivers had undergone changes that remove the 'parent
325 interface' from the ifconfig -l output. The rc.d network scripts
326 used to check presence of a parent interface in the list, so old
327 scripts would fail to start wireless networking. Thus, etcupdate(3)
328 or mergemaster(8) run is required after kernel update, to update your
329 rc.d scripts in /etc.
332 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
333 These configurations are now automatically interpreted as
334 'scrub fragment reassemble'.
337 Kernel-loadable modules for the random(4) device are back. To use
338 them, the kernel must have
341 options RANDOM_LOADABLE
343 kldload(8) can then be used to load random_fortuna.ko
344 or random_yarrow.ko. Please note that due to the indirect
345 function calls that the loadable modules need to provide,
346 the build-in variants will be slightly more efficient.
348 The random(4) kernel option RANDOM_DUMMY has been retired due to
349 unpopularity. It was not all that useful anyway.
352 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
353 Control over building the ELF Tool Chain tools is now provided by
354 the WITHOUT_TOOLCHAIN knob.
357 The polarity of Pulse Per Second (PPS) capture events with the
358 uart(4) driver has been corrected. Prior to this change the PPS
359 "assert" event corresponded to the trailing edge of a positive PPS
360 pulse and the "clear" event was the leading edge of the next pulse.
362 As the width of a PPS pulse in a typical GPS receiver is on the
363 order of 1 millisecond, most users will not notice any significant
364 difference with this change.
366 Anyone who has compensated for the historical polarity reversal by
367 configuring a negative offset equal to the pulse width will need to
368 remove that workaround.
371 The default group assigned to /dev/dri entries has been changed
372 from 'wheel' to 'video' with the id of '44'. If you want to have
373 access to the dri devices please add yourself to the video group
376 # pw groupmod video -m $USER
379 The menu.rc and loader.rc files will now be replaced during
380 upgrades. Please migrate local changes to menu.rc.local and
381 loader.rc.local instead.
384 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
385 strings and strip have been removed. The src.conf(5) knob
386 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
389 As ZFS requires more kernel stack pages than is the default on some
390 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
391 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
393 Please consider using 'options KSTACK_PAGES=X' where X is greater
394 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
397 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
398 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
399 default, i.e., they will not contain "::". For example, instead
400 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
401 to have a more specific match, such as different map entries for
402 IPv6:0:0 vs IPv6:0. This change requires that configuration
403 data (including maps, files, classes, custom ruleset, etc.) must
404 use the same format, so make certain such configuration data is
405 upgrading. As a very simple check search for patterns like
406 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
407 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
408 the cf option UseCompressedIPv6Addresses.
411 The default kernel entropy-processing algorithm is now
412 Fortuna, replacing Yarrow.
414 Assuming you have 'device random' in your kernel config
415 file, the configurations allow a kernel option to override
416 this default. You may choose *ONE* of:
418 options RANDOM_YARROW # Legacy /dev/random algorithm.
419 options RANDOM_DUMMY # Blocking-only driver.
421 If you have neither, you get Fortuna. For most people,
422 read no further, Fortuna will give a /dev/random that works
423 like it always used to, and the difference will be irrelevant.
425 If you remove 'device random', you get *NO* kernel-processed
426 entropy at all. This may be acceptable to folks building
427 embedded systems, but has complications. Carry on reading,
428 and it is assumed you know what you need.
430 *PLEASE* read random(4) and random(9) if you are in the
431 habit of tweaking kernel configs, and/or if you are a member
432 of the embedded community, wanting specific and not-usual
433 behaviour from your security subsystems.
435 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
436 random', you will NOT have a functioning /dev/random, and
437 many cryptographic features will not work, including SSH.
438 You may also find strange behaviour from the random(3) set
439 of library functions, in particular sranddev(3), srandomdev(3)
440 and arc4random(3). The reason for this is that the KERN_ARND
441 sysctl only returns entropy if it thinks it has some to
442 share, and with RANDOM_DUMMY or no 'device random' this
446 An additional fix for the issue described in the 20150614 sendmail
447 entry below has been been committed in revision 284717.
450 FreeBSD's old make (fmake) has been removed from the system. It is
451 available as the devel/fmake port or via pkg install fmake.
454 The fix for the issue described in the 20150614 sendmail entry
455 below has been been committed in revision 284436. The work
456 around described in that entry is no longer needed unless the
457 default setting is overridden by a confDH_PARAMETERS configuration
458 setting of '5' or pointing to a 512 bit DH parameter file.
461 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
462 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
463 and devel/kyua to version 0.20+ and adjust any calling code to work
464 with Kyuafile and kyua.
467 The import of openssl to address the FreeBSD-SA-15:10.openssl
468 security advisory includes a change which rejects handshakes
469 with DH parameters below 768 bits. sendmail releases prior
470 to 8.15.2 (not yet released), defaulted to a 512 bit
471 DH parameter setting for client connections. To work around
472 this interoperability, sendmail can be configured to use a
473 2048 bit DH parameter by:
475 1. Edit /etc/mail/`hostname`.mc
476 2. If a setting for confDH_PARAMETERS does not exist or
477 exists and is set to a string beginning with '5',
479 3. If a setting for confDH_PARAMETERS exists and is set to
480 a file path, create a new file with:
481 openssl dhparam -out /path/to/file 2048
482 4. Rebuild the .cf file:
483 cd /etc/mail/; make; make install
485 cd /etc/mail/; make restart
487 A sendmail patch is coming, at which time this file will be
491 Generation of legacy formatted entries have been disabled by default
492 in pwd_mkdb(8), as all base system consumers of the legacy formatted
493 entries were converted to use the new format by default when the new,
494 machine independent format have been added and supported since FreeBSD
497 Please see the pwd_mkdb(8) manual page for further details.
500 Clang and llvm have been upgraded to 3.6.1 release. Please see the
501 20141231 entry below for information about prerequisites and upgrading,
502 if you are not already using 3.5.0 or higher.
505 TI platform code switched to using vendor DTS files and this update
506 may break existing systems running on Beaglebone, Beaglebone Black,
509 - dtb files should be regenerated/reinstalled. Filenames are the
510 same but content is different now
511 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
512 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
513 addressing scheme is now pin 25 on /dev/gpioc3.
514 - Pandaboard: /etc/ttys should be updated, serial console device is
515 now /dev/ttyu2, not /dev/ttyu0
518 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
519 If you need the GNU extension from groff soelim(1), install groff
520 from package: pkg install groff, or via ports: textproc/groff.
523 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
524 defined in symlink(7); previously symlinks were silently ignored.
527 The const qualifier has been removed from iconv(3) to comply with
528 POSIX. The ports tree is aware of this from r384038 onwards.
531 Libraries specified by LIBADD in Makefiles must have a corresponding
532 DPADD_<lib> variable to ensure correct dependencies. This is now
533 enforced in src.libnames.mk.
536 From legacy ata(4) driver was removed support for SATA controllers
537 supported by more functional drivers ahci(4), siis(4) and mvs(4).
538 Kernel modules ataahci and ataadaptec were removed completely,
539 replaced by ahci and mvs modules respectively.
542 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
543 the 20141231 entry below for information about prerequisites and
544 upgrading, if you are not already using 3.5.0 or higher.
547 The 32-bit PowerPC kernel has been changed to a position-independent
548 executable. This can only be booted with a version of loader(8)
549 newer than January 31, 2015, so make sure to update both world and
550 kernel before rebooting.
553 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
554 but before r278950, the RNG was not seeded properly. Immediately
555 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
556 ssh keys or openssl keys) that were generated w/ a kernel from that
557 range. This does not affect programs that directly used /dev/random
558 or /dev/urandom. All userland uses of arc4random(3) are affected.
561 The autofs(4) ABI was changed in order to restore binary compatibility
562 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
566 The powerpc64 kernel has been changed to a position-independent
567 executable. This can only be booted with a new version of loader(8),
568 so make sure to update both world and kernel before rebooting.
571 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
572 only release, no new features have been added. Please see the 20141231
573 entry below for information about prerequisites and upgrading, if you
574 are not already using 3.5.0.
577 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
578 taken from the ELF Tool Chain project rather than GNU binutils. They
579 should be drop-in replacements, with the addition of arm64 support.
580 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
581 binutils tools, if necessary. See 20150805 for updated information.
584 The default Unbound configuration now enables remote control
585 using a local socket. Users who have already enabled the
586 local_unbound service should regenerate their configuration
587 by running "service local_unbound setup" as root.
590 The GNU texinfo and GNU info pages have been removed.
591 To be able to view GNU info pages please install texinfo from ports.
594 Clang, llvm and lldb have been upgraded to 3.5.0 release.
596 As of this release, a prerequisite for building clang, llvm and lldb is
597 a C++11 capable compiler and C++11 standard library. This means that to
598 be able to successfully build the cross-tools stage of buildworld, with
599 clang as the bootstrap compiler, your system compiler or cross compiler
600 should either be clang 3.3 or later, or gcc 4.8 or later, and your
601 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
604 On any standard FreeBSD 10.x or 11.x installation, where clang and
605 libc++ are on by default (that is, on x86 or arm), this should work out
608 On 9.x installations where clang is enabled by default, e.g. on x86 and
609 powerpc, libc++ will not be enabled by default, so libc++ should be
610 built (with clang) and installed first. If both clang and libc++ are
611 missing, build clang first, then use it to build libc++.
613 On 8.x and earlier installations, upgrade to 9.x first, and then follow
614 the instructions for 9.x above.
616 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
617 default, and do not build clang.
619 Many embedded systems are resource constrained, and will not be able to
620 build clang in a reasonable time, or in some cases at all. In those
621 cases, cross building bootable systems on amd64 is a workaround.
623 This new version of clang introduces a number of new warnings, of which
624 the following are most likely to appear:
628 This warns in two cases, for both C and C++:
629 * When the code is trying to take the absolute value of an unsigned
630 quantity, which is effectively a no-op, and almost never what was
631 intended. The code should be fixed, if at all possible. If you are
632 sure that the unsigned quantity can be safely cast to signed, without
633 loss of information or undefined behavior, you can add an explicit
634 cast, or disable the warning.
636 * When the code is trying to take an absolute value, but the called
637 abs() variant is for the wrong type, which can lead to truncation.
638 If you want to disable the warning instead of fixing the code, please
639 make sure that truncation will not occur, or it might lead to unwanted
642 -Wtautological-undefined-compare and
643 -Wundefined-bool-conversion
645 These warn when C++ code is trying to compare 'this' against NULL, while
646 'this' should never be NULL in well-defined C++ code. However, there is
647 some legacy (pre C++11) code out there, which actively abuses this
648 feature, which was less strictly defined in previous C++ versions.
650 Squid and openjdk do this, for example. The warning can be turned off
651 for C++98 and earlier, but compiling the code in C++11 mode might result
652 in unexpected behavior; for example, the parts of the program that are
653 unreachable could be optimized away.
656 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
657 kernel sources have been removed. The .h files remain, since some
658 utilities include them. This will need to be fixed later.
659 If "mount -t oldnfs ..." is attempted, it will fail.
660 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
661 the utilities will report errors.
664 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
665 directories to top level SUBDIR variable when their parent
666 directory is included in LOCAL_DIRS. Users with build systems with
667 such hierarchies and without SUBDIR entries in the parent
668 directory Makefiles should add them or add the directories to
672 faith(4) and faithd(8) have been removed from the base system. Faith
673 has been obsolete for a very long time.
676 vt(4), the new console driver, is enabled by default. It brings
677 support for Unicode and double-width characters, as well as
678 support for UEFI and integration with the KMS kernel video
681 You may need to update your console settings in /etc/rc.conf,
682 most probably the keymap. During boot, /etc/rc.d/syscons will
683 indicate what you need to do.
685 vt(4) still has issues and lacks some features compared to
686 syscons(4). See the wiki for up-to-date information:
687 https://wiki.freebsd.org/Newcons
689 If you want to keep using syscons(4), you can do so by adding
690 the following line to /boot/loader.conf:
694 pjdfstest has been integrated into kyua as an opt-in test suite.
695 Please see share/doc/pjdfstest/README for more details on how to
699 gperf has been removed from the base system for architectures
700 that use clang. Ports that require gperf will obtain it from the
704 pjdfstest has been moved from tools/regression/pjdfstest to
708 At svn r271982, The default linux compat kernel ABI has been adjusted
709 to 2.6.18 in support of the linux-c6 compat ports infrastructure
710 update. If you wish to continue using the linux-f10 compat ports,
711 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
712 encouraged to update their linux-compat packages to linux-c6 during
713 their next update cycle.
716 The ofwfb driver, used to provide a graphics console on PowerPC when
717 using vt(4), no longer allows mmap() of all physical memory. This
718 will prevent Xorg on PowerPC with some ATI graphics cards from
719 initializing properly unless x11-servers/xorg-server is updated to
723 The xdev targets have been converted to using TARGET and
724 TARGET_ARCH instead of XDEV and XDEV_ARCH.
727 The default unbound configuration has been modified to address
728 issues with reverse lookups on networks that use private
729 address ranges. If you use the local_unbound service, run
730 "service local_unbound setup" as root to regenerate your
731 configuration, then "service local_unbound reload" to load the
735 The GNU texinfo and GNU info pages are not built and installed
736 anymore, WITH_INFO knob has been added to allow to built and install
738 UPDATE: see 20150102 entry on texinfo's removal
741 The GNU readline library is now an INTERNALLIB - that is, it is
742 statically linked into consumers (GDB and variants) in the base
743 system, and the shared library is no longer installed. The
744 devel/readline port is available for third party software that
748 The Itanium architecture (ia64) has been removed from the list of
749 known architectures. This is the first step in the removal of the
753 Commit r268115 has added NFSv4.1 server support, merged from
754 projects/nfsv4.1-server. Since this includes changes to the
755 internal interfaces between the NFS related modules, a full
756 build of the kernel and modules will be necessary.
757 __FreeBSD_version has been bumped.
760 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
761 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
762 which differs from the behaviour controlled by this knob.)
765 Maximal length of the serial number in CTL was increased from 16 to
766 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
767 and ctld, need to be rebuilt to work with a new kernel.
770 The libatf-c and libatf-c++ major versions were downgraded to 0 and
771 1 respectively to match the upstream numbers. They were out of
772 sync because, when they were originally added to FreeBSD, the
773 upstream versions were not respected. These libraries are private
774 and not yet built by default, so renumbering them should be a
775 non-issue. However, unclean source trees will yield broken test
776 programs once the operator executes "make delete-old-libs" after a
779 Additionally, the atf-sh binary was made private by moving it into
780 /usr/libexec/. Already-built shell test programs will keep the
781 path to the old binary so they will break after "make delete-old"
784 If you are using WITH_TESTS=yes (not the default), wipe the object
785 tree and rebuild from scratch to prevent spurious test failures.
786 This is only needed once: the misnumbered libraries and misplaced
787 binaries have been added to OptionalObsoleteFiles.inc so they will
788 be removed during a clean upgrade.
791 Clang and llvm have been upgraded to 3.4.1 release.
794 We bogusly installed src.opts.mk in /usr/share/mk. This file should
795 be removed to avoid issues in the future (and has been added to
799 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
800 past, it affected all builds that used the bsd.*.mk files. The old
801 behavior was a bug, but people may have relied upon it. To get this
802 behavior back, you can .include /etc/src.conf from /etc/make.conf
803 (which is still global and isn't changed). This also changes the
804 behavior of incremental builds inside the tree of individual
805 directories. Set MAKESYSPATH to ".../share/mk" to do that.
806 Although this has survived make universe and some upgrade scenarios,
807 other upgrade scenarios may have broken. At least one form of
808 temporary breakage was fixed with MAKESYSPATH settings for buildworld
809 as well... In cases where MAKESYSPATH isn't working with this
810 setting, you'll need to set it to the full path to your tree.
812 One side effect of all this cleaning up is that bsd.compiler.mk
813 is no longer implicitly included by bsd.own.mk. If you wish to
814 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
818 The lindev device has been removed since /dev/full has been made a
819 standard device. __FreeBSD_version has been bumped.
822 The knob WITHOUT_VI was added to the base system, which controls
823 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
824 in order to reorder files share/termcap and didn't build ex(1) as a
825 build tool, so building/installing with WITH_VI is highly advised for
826 build hosts for older releases.
828 This issue has been fixed in stable/9 and stable/10 in r277022 and
829 r276991, respectively.
832 The YES_HESIOD knob has been removed. It has been obsolete for
833 a decade. Please move to using WITH_HESIOD instead or your builds
834 will silently lack HESIOD.
837 The uart(4) driver has been changed with respect to its handling
838 of the low-level console. Previously the uart(4) driver prevented
839 any process from changing the baudrate or the CLOCAL and HUPCL
840 control flags. By removing the restrictions, operators can make
841 changes to the serial console port without having to reboot.
842 However, when getty(8) is started on the serial device that is
843 associated with the low-level console, a misconfigured terminal
844 line in /etc/ttys will now have a real impact.
845 Before upgrading the kernel, make sure that /etc/ttys has the
846 serial console device configured as 3wire without baudrate to
847 preserve the previous behaviour. E.g:
848 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
851 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
852 to improve performance. To re-enable it, if needed, run rpcbind
853 with command line option -W.
856 Switched back to the GPL dtc compiler due to updates in the upstream
857 dts files not being supported by the BSDL dtc compiler. You will need
858 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
859 may result while building dtb files during a kernel build if you fail
860 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
863 Clang and llvm have been upgraded to 3.4 release.
866 The nve(4) driver has been removed. Please use the nfe(4) driver
867 for NVIDIA nForce MCP Ethernet adapters instead.
870 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
871 This could cause certain C++ applications using shared libraries built
872 against the previous version of libc++ to crash. The incompatibility
873 has now been fixed, but any C++ applications or shared libraries built
874 between r261283 and r261801 should be recompiled.
877 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
878 capability mode support. Please note that enabling the feature in
879 kernel is still highly recommended.
882 OpenSSH is now built with sandbox support, and will use sandbox as
883 the default privilege separation method. This requires Capsicum
884 capability mode support in kernel.
887 The libelf and libdwarf libraries have been updated to newer
888 versions from upstream. Shared library version numbers for
889 these two libraries were bumped. Any ports or binaries
890 requiring these two libraries should be recompiled.
891 __FreeBSD_version is bumped to 1100006.
894 If a Makefile in a tests/ directory was auto-generating a Kyuafile
895 instead of providing an explicit one, this would prevent such
896 Makefile from providing its own Kyuafile in the future during
897 NO_CLEAN builds. This has been fixed in the Makefiles but manual
898 intervention is needed to clean an objdir if you use NO_CLEAN:
899 # find /usr/obj -name Kyuafile | xargs rm -f
902 The behavior of gss_pseudo_random() for the krb5 mechanism
903 has changed, for applications requesting a longer random string
904 than produced by the underlying enctype's pseudo-random() function.
905 In particular, the random string produced from a session key of
906 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
907 be different at the 17th octet and later, after this change.
908 The counter used in the PRF+ construction is now encoded as a
909 big-endian integer in accordance with RFC 4402.
910 __FreeBSD_version is bumped to 1100004.
913 The WITHOUT_ATF build knob has been removed and its functionality
914 has been subsumed into the more generic WITHOUT_TESTS. If you were
915 using the former to disable the build of the ATF libraries, you
916 should change your settings to use the latter.
919 The default version of mtree is nmtree which is obtained from
920 NetBSD. The output is generally the same, but may vary
921 slightly. If you found you need identical output adding
922 "-F freebsd9" to the command line should do the trick. For the
923 time being, the old mtree is available as fmtree.
926 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
927 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
928 1.1.4_8 and verify bsdyml not linked in, before running "make
930 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
932 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
935 The stable/10 branch has been created in subversion from head
939 The rc.d/jail script has been updated to support jail(8)
940 configuration file. The "jail_<jname>_*" rc.conf(5) variables
941 for per-jail configuration are automatically converted to
942 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
943 This is transparently backward compatible. See below about some
944 incompatibilities and rc.conf(5) manual page for more details.
946 These variables are now deprecated in favor of jail(8) configuration
947 file. One can use "rc.d/jail config <jname>" command to generate
948 a jail(8) configuration file in /var/run/jail.<jname>.conf without
949 running the jail(8) utility. The default pathname of the
950 configuration file is /etc/jail.conf and can be specified by
951 using $jail_conf or $jail_<jname>_conf variables.
953 Please note that jail_devfs_ruleset accepts an integer at
954 this moment. Please consider to rewrite the ruleset name
958 BIND has been removed from the base system. If all you need
959 is a local resolver, simply enable and start the local_unbound
960 service instead. Otherwise, several versions of BIND are
961 available in the ports tree. The dns/bind99 port is one example.
963 With this change, nslookup(1) and dig(1) are no longer in the base
964 system. Users should instead use host(1) and drill(1) which are
965 in the base system. Alternatively, nslookup and dig can
966 be obtained by installing the dns/bind-tools port.
969 With the addition of unbound(8), a new unbound user is now
970 required during installworld. "mergemaster -p" can be used to
971 add the user prior to installworld, as documented in the handbook.
974 OpenSSH is now built with DNSSEC support, and will by default
975 silently trust signed SSHFP records. This can be controlled with
976 the VerifyHostKeyDNS client configuration setting. DNSSEC support
977 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
980 The GNU Compiler Collection and C++ standard library (libstdc++)
981 are no longer built by default on platforms where clang is the system
982 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
986 The PROCDESC kernel option is now part of the GENERIC kernel
987 configuration and is required for the rwhod(8) to work.
988 If you are using custom kernel configuration, you should include
992 The API and ABI related to the Capsicum framework was modified
993 in backward incompatible way. The userland libraries and programs
994 have to be recompiled to work with the new kernel. This includes the
995 following libraries and programs, but the whole buildworld is
996 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
997 kdump, procstat, rwho, rwhod, uniq.
1000 AES-NI intrinsic support has been added to gcc. The AES-NI module
1001 has been updated to use this support. A new gcc is required to build
1002 the aesni module on both i386 and amd64.
1005 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1006 Thus "device padlock_rng" and "device rdrand_rng" should be
1007 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1010 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1011 enables just the iconv* functionality and is now on by default.
1012 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1013 compatibility. Set WITHOUT_ICONV to build the old way.
1014 If you have been using WITH_ICONV before, you will very likely
1015 need to turn on WITH_LIBICONV_COMPAT.
1018 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1019 Illumos origin, including ZFS. If you have INVARIANTS in your
1020 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1022 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1023 locks if WITNESS option was set. Because that generated a lot of
1024 witness(9) reports and all of them were believed to be false
1025 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1026 can be used to achieve the previous behavior.
1029 Timer values in IPv6 data structures now use time_uptime instead
1030 of time_second. Although this is not a user-visible functional
1031 change, userland utilities which directly use them---ndp(8),
1032 rtadvd(8), and rtsold(8) in the base system---need to be updated
1033 to r253970 or later.
1036 find -delete can now delete the pathnames given as arguments,
1037 instead of only files found below them or if the pathname did
1038 not contain any slashes. Formerly, the following error message
1041 find: -delete: <path>: relative path potentially not safe
1043 Deleting the pathnames given as arguments can be prevented
1044 without error messages using -mindepth 1 or by changing
1045 directory and passing "." as argument to find. This works in the
1046 old as well as the new version of find.
1049 Behavior of devfs rules path matching has been changed.
1050 Pattern is now always matched against fully qualified devfs
1051 path and slash characters must be explicitly matched by
1052 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1053 subdirectories must be reviewed.
1056 The default ARM ABI has changed to the ARM EABI. The old ABI is
1057 incompatible with the ARM EABI and all programs and modules will
1058 need to be rebuilt to work with a new kernel.
1060 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1062 NOTE: Support for the old ABI will be removed in the future and
1063 users are advised to upgrade.
1066 pkg_install has been disconnected from the build if you really need it
1067 you should add WITH_PKGTOOLS in your src.conf(5).
1070 Most of network statistics structures were changed to be able
1071 keep 64-bits counters. Thus all tools, that work with networking
1072 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1075 Fix a bug that allowed a tracing process (e.g. gdb) to write
1076 to a memory-mapped file in the traced process's address space
1077 even if neither the traced process nor the tracing process had
1078 write access to that file.
1081 CVS has been removed from the base system. An exact copy
1082 of the code is available from the devel/cvs port.
1085 Some people report the following error after the switch to bmake:
1087 make: illegal option -- J
1088 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1090 *** [buildworld] Error code 2
1092 this likely due to an old instance of make in
1093 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1094 which src/Makefile will use that blindly, if it exists, so if
1095 you see the above error:
1097 rm -rf `make -V MAKEPATH`
1102 Use bmake by default.
1103 Whereas before one could choose to build with bmake via
1104 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1105 make. The goal is to remove these knobs for 10-RELEASE.
1107 It is worth noting that bmake (like gmake) treats the command
1108 line as the unit of failure, rather than statements within the
1109 command line. Thus '(cd some/where && dosomething)' is safer
1110 than 'cd some/where; dosomething'. The '()' allows consistent
1111 behavior in parallel build.
1114 Fix a bug that allows NFS clients to issue READDIR on files.
1117 The WITHOUT_IDEA option has been removed because
1118 the IDEA patent expired.
1121 The sysctl which controls TRIM support under ZFS has been renamed
1122 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1126 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1127 rather than creating it's own in the temporary directory in
1128 order allow access to bootstrapped versions of tools such as
1129 install and mtree. When upgrading from version of FreeBSD where
1130 the install command does not support -l, you will need to
1131 install a new mergemaster command if mergemaster -p is required.
1132 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1136 Legacy ATA stack, disabled and replaced by new CAM-based one since
1137 FreeBSD 9.0, completely removed from the sources. Kernel modules
1138 atadisk and atapi*, user-level tools atacontrol and burncd are
1139 removed. Kernel option `options ATA_CAM` is now permanently enabled
1143 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1144 and socketpair(2). Software, in particular Kerberos, may
1145 automatically detect and use these during building. The resulting
1146 binaries will not work on older kernels.
1149 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1150 information, see the respective 20130304 entry).
1153 Recent commits to callout(9) changed the size of struct callout,
1154 so the KBI is probably heavily disturbed. Also, some functions
1155 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1156 by macros. Every kernel module using it won't load, so rebuild
1159 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1160 but does not initialize by default (because of the new CTL_DISABLE
1161 option) to save memory. To re-enable it, remove the CTL_DISABLE
1162 option from the kernel config file or set kern.cam.ctl.disable=0
1163 in /boot/loader.conf.
1166 The ctl device has been disabled in GENERIC for i386 and amd64.
1167 This was done due to the extra memory being allocated at system
1168 initialisation time by the ctl driver which was only used if
1169 a CAM target device was created. This makes a FreeBSD system
1170 unusable on 128MB or less of RAM.
1173 A new compression method (lz4) has been merged to -HEAD. Please
1174 refer to zpool-features(7) for more information.
1176 Please refer to the "ZFS notes" section of this file for information
1177 on upgrading boot ZFS pools.
1180 A BSD-licensed patch(1) variant has been added and is installed
1181 as bsdpatch, being the GNU version the default patch.
1182 To inverse the logic and use the BSD-licensed one as default,
1183 while having the GNU version installed as gnupatch, rebuild
1184 and install world with the WITH_BSD_PATCH knob set.
1187 Due to the use of the new -l option to install(1) during build
1188 and install, you must take care not to directly set the INSTALL
1189 make variable in your /etc/make.conf, /etc/src.conf, or on the
1190 command line. If you wish to use the -C flag for all installs
1191 you may be able to add INSTALL+=-C to /etc/make.conf or
1195 The install(1) option -M has changed meaning and now takes an
1196 argument that is a file or path to append logs to. In the
1197 unlikely event that -M was the last option on the command line
1198 and the command line contained at least two files and a target
1199 directory the first file will have logs appended to it. The -M
1200 option served little practical purpose in the last decade so its
1201 use is expected to be extremely rare.
1204 After switching to Clang as the default compiler some users of ZFS
1205 on i386 systems started to experience stack overflow kernel panics.
1206 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1209 GEOM_LABEL now mangles label names read from file system metadata.
1210 Mangling affect labels containing spaces, non-printable characters,
1211 '%' or '"'. Device names in /etc/fstab and other places may need to
1215 By default, only the 10 most recent kernel dumps will be saved. To
1216 restore the previous behaviour (no limit on the number of kernel dumps
1217 stored in the dump directory) add the following line to /etc/rc.conf:
1222 With the addition of auditdistd(8), a new auditdistd user is now
1223 required during installworld. "mergemaster -p" can be used to
1224 add the user prior to installworld, as documented in the handbook.
1227 The sin6_scope_id member variable in struct sockaddr_in6 is now
1228 filled by the kernel before passing the structure to the userland via
1229 sysctl or routing socket. This means the KAME-specific embedded scope
1230 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1231 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1232 __FreeBSD_version is bumped to 1000025.
1235 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1236 This means that the world and kernel will be compiled with clang
1237 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1238 and /usr/bin/cpp. To disable this behavior and revert to building
1239 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1240 of current may need to bootstrap WITHOUT_CLANG first if the clang
1241 build fails (its compatibility window doesn't extend to the 9 stable
1245 The IPFIREWALL_FORWARD kernel option has been removed. Its
1246 functionality now turned on by default.
1249 The ZERO_COPY_SOCKET kernel option has been removed and
1250 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1251 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1252 mechanism which is not safe and may result in kernel crashes.
1253 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1254 driver supports disposeable external page sized mbuf storage.
1255 Proper replacements for both zero-copy mechanisms are under
1256 consideration and will eventually lead to complete removal
1257 of the two kernel options.
1260 The IPv4 network stack has been converted to network byte
1261 order. The following modules need to be recompiled together
1262 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1263 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1266 Support for non-MPSAFE filesystems was removed from VFS. The
1267 VFS_VERSION was bumped, all filesystem modules shall be
1271 All the non-MPSAFE filesystems have been disconnected from
1272 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1273 portalfs, smbfs, xfs.
1276 The interface cloning API and ABI has changed. The following
1277 modules need to be recompiled together with kernel:
1278 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1279 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1280 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1283 The sdhci driver was split in two parts: sdhci (generic SD Host
1284 Controller logic) and sdhci_pci (actual hardware driver).
1285 No kernel config modifications are required, but if you
1286 load sdhc as a module you must switch to sdhci_pci instead.
1289 Import the FUSE kernel and userland support into base system.
1292 The GNU sort(1) program has been removed since the BSD-licensed
1293 sort(1) has been the default for quite some time and no serious
1294 problems have been reported. The corresponding WITH_GNU_SORT
1298 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1299 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1303 The net80211(4) ABI has been changed to allow for improved driver
1304 PS-POLL and power-save support. All wireless drivers need to be
1305 recompiled to work with the new kernel.
1308 The random(4) support for the VIA hardware random number
1309 generator (`PADLOCK') is no longer enabled unconditionally.
1310 Add the padlock_rng device in the custom kernel config if
1311 needed. The GENERIC kernels on i386 and amd64 do include the
1312 device, so the change only affects the custom kernel
1316 The pf(4) packet filter ABI has been changed. pfctl(8) and
1317 snmp_pf module need to be recompiled to work with new kernel.
1320 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1321 to -HEAD. Pools that have empty_bpobj in active state can not be
1322 imported read-write with ZFS implementations that do not support
1323 this feature. For more information read the zpool-features(5)
1327 The sparc64 ZFS loader has been changed to no longer try to auto-
1328 detect ZFS providers based on diskN aliases but now requires these
1329 to be explicitly listed in the OFW boot-device environment variable.
1332 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1333 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1334 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1337 The following sysctls and tunables have been renamed for consistency
1338 with other variables:
1339 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1340 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1343 The sort utility has been replaced with BSD sort. For now, GNU sort
1344 is also available as "gnusort" or the default can be set back to
1345 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1346 installed as "bsdsort".
1349 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1350 Starting with this version the old system of ZFS pool versioning
1351 is superseded by "feature flags". This concept enables forward
1352 compatibility against certain future changes in functionality of ZFS
1353 pools. The first read-only compatible "feature flag" for ZFS pools
1354 is named "com.delphix:async_destroy". For more information
1355 read the new zpool-features(5) manual page.
1356 Please refer to the "ZFS notes" section of this file for information
1357 on upgrading boot ZFS pools.
1360 The malloc(3) implementation embedded in libc now uses sources imported
1361 as contrib/jemalloc. The most disruptive API change is to
1362 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1363 delete it prior to installworld, and optionally re-create it using the
1364 new format after rebooting. See malloc.conf(5) for details
1365 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1369 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1370 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1371 now spelled mips. This is to aid compatibility with third-party
1372 software that expects this naming scheme in uname(3). Little-endian
1373 settings are unchanged. If you are updating a big-endian mips64 machine
1374 from before this change, you may need to set MACHINE_ARCH=mips64 in
1375 your environment before the new build system will recognize your machine.
1378 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1382 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1383 nullfs(5) did not pass through all behaviours to the underlying layer,
1384 as a result if we bound to a socket on the lower layer we could connect
1385 only to the lower path; if we bound to the upper layer we could connect
1386 only to the upper path. The new behavior is one can connect to both the
1387 lower and the upper paths regardless what layer path one binds to.
1390 The getifaddrs upgrade path broken with 20111215 has been restored.
1391 If you have upgraded in between 20111215 and 20120209 you need to
1392 recompile libc again with your kernel. You still need to recompile
1393 world to be able to configure CARP but this restriction already
1394 comes from 20111215.
1397 The set_rcvar() function has been removed from /etc/rc.subr. All
1398 base and ports rc.d scripts have been updated, so if you have a
1399 port installed with a script in /usr/local/etc/rc.d you can either
1400 hand-edit the rcvar= line, or reinstall the port.
1402 An easy way to handle the mass-update of /etc/rc.d:
1403 rm /etc/rc.d/* && mergemaster -i
1406 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1407 on the current CPU and prevents other threads from running.
1408 This behavior can be reverted using the kern.stop_scheduler_on_panic
1410 The new behavior can be incompatible with kern.sync_on_panic.
1413 The carp(4) facility has been changed significantly. Configuration
1414 of the CARP protocol via ifconfig(8) has changed, as well as format
1415 of CARP events submitted to devd(8) has changed. See manual pages
1416 for more information. The arpbalance feature of carp(4) is currently
1417 not supported anymore.
1419 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1420 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1421 need to be recompiled.
1424 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1428 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1429 explicitely support non-MPSAFE filesystems.
1430 It is on by default for all supported platform at this present
1434 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1435 i386 and pc98 GENERIC kernel configuration files.
1438 sysinstall has been removed
1441 The stable/9 branch created in subversion. This corresponds to the
1442 RELENG_9 branch in CVS.
1448 Avoid using make -j when upgrading. While generally safe, there are
1449 sometimes problems using -j to upgrade. If your upgrade fails with
1450 -j, please try again without -j. From time to time in the past there
1451 have been problems using -j with buildworld and/or installworld. This
1452 is especially true when upgrading between "distant" versions (eg one
1453 that cross a major release boundary or several minor releases, or when
1454 several months have passed on the -current branch).
1456 Sometimes, obscure build problems are the result of environment
1457 poisoning. This can happen because the make utility reads its
1458 environment when searching for values for global variables. To run
1459 your build attempts in an "environmental clean room", prefix all make
1460 commands with 'env -i '. See the env(1) manual page for more details.
1462 When upgrading from one major version to another it is generally best
1463 to upgrade to the latest code in the currently installed branch first,
1464 then do an upgrade to the new branch. This is the best-tested upgrade
1465 path, and has the highest probability of being successful. Please try
1466 this approach before reporting problems with a major version upgrade.
1468 When upgrading a live system, having a root shell around before
1469 installing anything can help undo problems. Not having a root shell
1470 around can lead to problems if pam has changed too much from your
1471 starting point to allow continued authentication after the upgrade.
1473 This file should be read as a log of events. When a later event changes
1474 information of a prior event, the prior event should not be deleted.
1475 Instead, a pointer to the entry with the new information should be
1476 placed in the old entry. Readers of this file should also sanity check
1477 older entries before relying on them blindly. Authors of new entries
1478 should write them with this in mind.
1482 When upgrading the boot ZFS pool to a new version, always follow
1485 1.) recompile and reinstall the ZFS boot loader and boot block
1486 (this is part of "make buildworld" and "make installworld")
1488 2.) update the ZFS boot block on your boot drive
1490 The following example updates the ZFS boot block on the first
1491 partition (freebsd-boot) of a GPT partitioned drive ada0:
1492 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1494 Non-boot pools do not need these updates.
1498 If you are updating from a prior version of FreeBSD (even one just
1499 a few days old), you should follow this procedure. It is the most
1500 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1502 make kernel-toolchain
1503 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1504 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1506 To test a kernel once
1507 ---------------------
1508 If you just want to boot a kernel once (because you are not sure
1509 if it works, or if you want to boot a known bad kernel to provide
1510 debugging information) run
1511 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1512 nextboot -k testkernel
1514 To just build a kernel when you know that it won't mess you up
1515 --------------------------------------------------------------
1516 This assumes you are already running a CURRENT system. Replace
1517 ${arch} with the architecture of your machine (e.g. "i386",
1518 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1520 cd src/sys/${arch}/conf
1521 config KERNEL_NAME_HERE
1522 cd ../compile/KERNEL_NAME_HERE
1527 If this fails, go to the "To build a kernel" section.
1529 To rebuild everything and install it on the current system.
1530 -----------------------------------------------------------
1531 # Note: sometimes if you are running current you gotta do more than
1532 # is listed here if you are upgrading from a really old current.
1534 <make sure you have good level 0 dumps>
1536 make kernel KERNCONF=YOUR_KERNEL_HERE
1538 <reboot in single user> [3]
1545 To cross-install current onto a separate partition
1546 --------------------------------------------------
1547 # In this approach we use a separate partition to hold
1548 # current's root, 'usr', and 'var' directories. A partition
1549 # holding "/", "/usr" and "/var" should be about 2GB in
1552 <make sure you have good level 0 dumps>
1555 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1556 <maybe newfs current's root partition>
1557 <mount current's root partition on directory ${CURRENT_ROOT}>
1558 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1559 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1560 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1561 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1562 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1563 <reboot into current>
1564 <do a "native" rebuild/install as described in the previous section>
1565 <maybe install compatibility libraries from ports/misc/compat*>
1569 To upgrade in-place from stable to current
1570 ----------------------------------------------
1571 <make sure you have good level 0 dumps>
1573 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1575 <reboot in single user> [3]
1582 Make sure that you've read the UPDATING file to understand the
1583 tweaks to various things you need. At this point in the life
1584 cycle of current, things change often and you are on your own
1585 to cope. The defaults can also change, so please read ALL of
1586 the UPDATING entries.
1588 Also, if you are tracking -current, you must be subscribed to
1589 freebsd-current@freebsd.org. Make sure that before you update
1590 your sources that you have read and understood all the recent
1591 messages there. If in doubt, please track -stable which has
1592 much fewer pitfalls.
1594 [1] If you have third party modules, such as vmware, you
1595 should disable them at this point so they don't crash your
1598 [3] From the bootblocks, boot -s, and then do
1603 adjkerntz -i # if CMOS is wall time
1604 Also, when doing a major release upgrade, it is required that
1605 you boot into single user mode to do the installworld.
1607 [4] Note: This step is non-optional. Failure to do this step
1608 can result in a significant reduction in the functionality of the
1609 system. Attempting to do it by hand is not recommended and those
1610 that pursue this avenue should read this file carefully, as well
1611 as the archives of freebsd-current and freebsd-hackers mailing lists
1612 for potential gotchas. The -U option is also useful to consider.
1613 See mergemaster(8) for more information.
1615 [5] Usually this step is a noop. However, from time to time
1616 you may need to do this if you get unknown user in the following
1617 step. It never hurts to do it all the time. You may need to
1618 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1619 install) after the buildworld before this step if you last updated
1620 from current before 20130425 or from -stable before 20130430.
1622 [6] This only deletes old files and directories. Old libraries
1623 can be deleted by "make delete-old-libs", but you have to make
1624 sure that no program is using those libraries anymore.
1626 [8] In order to have a kernel that can run the 4.x binaries needed to
1627 do an installworld, you must include the COMPAT_FREEBSD4 option in
1628 your kernel. Failure to do so may leave you with a system that is
1629 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1630 required to run the 5.x binaries on more recent kernels. And so on
1631 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1633 Make sure that you merge any new devices from GENERIC since the
1634 last time you updated your kernel config file.
1636 [9] When checking out sources, you must include the -P flag to have
1637 cvs prune empty directories.
1639 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1640 "?=" instead of the "=" assignment operator, so that buildworld can
1641 override the CPUTYPE if it needs to.
1643 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1644 not on the command line, or in /etc/make.conf. buildworld will
1645 warn if it is improperly defined.
1648 This file contains a list, in reverse chronological order, of major
1649 breakages in tracking -current. It is not guaranteed to be a complete
1650 list of such breakages, and only contains entries since September 23, 2011.
1651 If you need to see UPDATING entries from before that date, you will need
1652 to fetch an UPDATING file from an older FreeBSD release.
1654 Copyright information:
1656 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1658 Redistribution, publication, translation and use, with or without
1659 modification, in full or in part, in any form or format of this
1660 document are permitted without further permission from the author.
1662 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1663 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1664 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1665 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1666 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1667 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1668 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1669 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1670 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1671 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1672 POSSIBILITY OF SUCH DAMAGE.
1674 Contact Warner Losh if you have any questions about your use of