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 https://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 20191112 p5 FreeBSD-SA-19:25.mcepsc
21 Fix Machine Check Exception on Page Size Change [SA-19:25.mcepsc]
23 20191023 p4 FreeBSD-EN-19:18.tzdata
25 Import tzdata 2019c. [EN-19:18.tzdata]
27 20190820 p3 FreeBSD-EN-19:16.bhyve
31 FreeBSD-SA-19:24.mqueuefs
33 Bhyve instruction emulation improvements (opcode 03H and F7H).
36 Fix ipfw(8) jail keyword prior to jail startup. [EN-19:17.ipfw]
38 Fix IPv6 remote denial of service. [SA-19:22.mbuf]
40 Fix kernel memory disclosure from /dev/midistat. [SA-19:23.midi]
42 Fix reference count overflow in mqueuefs. [SA-19:24.mqueuefs]
44 20190806 p2 FreeBSD-SA-19:18.bzip2
45 FreeBSD-SA-19:19.mldv2
46 FreeBSD-SA-19:20.bsnmp
47 FreeBSD-SA-19:21.bhyve
49 Fix multiple vulnerabilities in bzip2. [SA-19:18.bzip2]
51 Fix ICMPv6 / MLDv2 out-of-bounds memory access. [SA-19:19.mldv2]
53 Fix insufficient message length validation in bsnmp library.
56 Fix insufficient validation of guest-supplied data (e1000 device).
59 20190724 p1 FreeBSD-EN-19:13.mds
60 FreeBSD-SA-19:12.telnet
62 FreeBSD-SA-19:14.freebsd32
63 FreeBSD-SA-19:15.mqueuefs
64 FreeBSD-SA-19:16.bhyve
67 Fix panic from Intel CPU vulnerability mitigation. [EN-19:13.mds]
69 Fix multiple telnet client vulnerabilities. [SA-19:12.telnet]
71 Fix pts write-after-free. [SA-19:13.pts]
73 Fix kernel memory disclosure in freebsd32_ioctl. [SA-19:14.freebsd32]
75 Fix reference count overflow in mqueuefs. [SA-19:15.mqueuefs]
77 Fix byhve out-of-bounds read in XHCI device. [SA-19:16.bhyve]
79 Fix file descriptor reference count leak. [SA-19:17.fd]
84 20190702 FreeBSD-EN-19:12.tzdata
85 FreeBSD-SA-19:09.iconv
86 FreeBSD-SA-19:11.cd_ioctl
88 Import tzdata 2019b. [EN-19:12.tzdata]
90 Fix iconv buffer overflow. [SA-19:09.iconv]
92 Fix privilege escalation in cd(4) driver. [SA-19:11.cd_ioctl]
95 CARP now sets DSCP value CS7(Network Traffic) in the flowlabel field
96 of packets by default instead of only setting TOS_LOWDELAY in IPv4,
97 which was deprecated in 1998. Original behavior can be restored by
98 setting sysctl net.inet.carp.dscp=4.
101 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
102 8.0.0. Please see the 20141231 entry below for information about
103 prerequisites and upgrading, if you are not already using clang 3.5.0
107 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
108 compiled into your custom kernel, add 'device xz' statement to the
112 Co-existance for Forth and Lua interpreters in bootloaders has now been
113 merged to ease testing of lualoader. LOADER_DEFAULT_INTERP, documented
114 in build(7), may be used to control which interpreter flavor is used in
115 the default loader to be installed. For systems where Lua and Forth
116 coexist, this switch can also be made on a running system by creating a
117 link from /boot/loader{,.efi} to /boot/loader_${flavor}{,.efi} rather
118 than requiring a rebuild.
120 The default flavor in this branch will remain Forth. As indicated in
121 the 20190216 UPDATING entry, booting is a complex environment; it would
122 be prudent to assume that lualoader may not work for your setup and make
123 provisions for backup boot methods.
126 zfsloader's functionality has now been folded into loader.
127 zfsloader is no longer necesasary once you've updated your
128 boot blocks. For a transition period, we will install a
129 hardlink for zfsloader to loader to allow a smooth transition
130 until the boot blocks can be updated (hard link because old
131 zfs boot blocks don't understand symlinks).
134 Lualoader has been merged to facilitate testing on this branch. It's
135 purely opt-in for now by building WITH_LOADER_LUA and WITHOUT_FORTH in
136 /etc/src.conf, but co-existance will come shortly. Booting is a complex
137 environment and test coverage for Lua-enabled loaders has been thin, so
138 it would be prudent to assume it might not work and make provisions for
142 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
143 7.0.1. Please see the 20141231 entry below for information about
144 prerequisites and upgrading, if you are not already using clang 3.5.0
148 r342562 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
149 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
150 servers that have vfs.nfsd.nfs_privport set will only allow mounts
151 from clients using a reserved port#. Since both the FreeBSD and Linux
152 NFSv4 clients use reserved port#s by default, this should not affect
156 The '%I' format in the kern.corefile sysctl limits the number of
157 core files that a process can generate to the number stored in the
158 debug.ncores sysctl. The '%I' format is replaced by the single digit
159 index. Previously, if all indexes were taken the kernel would overwrite
160 only a core file with the highest index in a filename.
161 Currently the system will create a new core file if there is a free
162 index or if all slots are taken it will overwrite the oldest one.
165 WITH_OFED option now only enables the build for the OFED libraries
166 and some fundamental client utilities. OpenSM and rest of the
167 debugging tools are enabled by WITH_OFED_EXTRA build switch.
168 WITH_OFED is turned on by default on amd64.
171 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
172 6.0.1. Please see the 20141231 entry below for information about
173 prerequisites and upgrading, if you are not already using clang 3.5.0
177 The releng/11.2 branch has been created from stable/11@r334458.
180 The tz database (tzdb) has been updated to 2018e. This version more
181 correctly models time stamps in time zones with negative DST such as
182 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
183 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
184 time zone abbreviations and the tm_isdst flag.
187 The use of RSS hash from the network card aka flowid has been
188 disabled by default for lagg(4) as it's currently incompatible with
189 the lacp and loadbalance protocols.
191 This can be re-enabled by setting the following in loader.conf:
192 net.link.lagg.default_use_flowid="1"
195 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
196 6.0.0. Please see the 20141231 entry below for information about
197 prerequisites and upgrading, if you are not already using clang 3.5.0
201 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
202 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
203 to WITH/OUT_LOADER_GELI.
206 The geli password typed at boot is now hidden. To restore the previous
207 behavior, see geli(8) for configuration options.
209 The SW_WATCHDOG option is no longer necessary to enable the
210 hardclock-based software watchdog if no hardware watchdog is
211 configured. As before, SW_WATCHDOG will cause the software
212 watchdog to be enabled even if a hardware watchdog is configured.
215 lint(1) binaries and library are no longer built by default. To
216 enable building them, define WITH_LINT in src.conf. If you are using
217 a FreeBSD 12 or later system to build 11-stable, you may need to
218 install a lint(1) binary to use WITH_LINT.
221 When building multiple kernels using KERNCONF, non-existent KERNCONF
222 files will produce an error and buildkernel will fail. Previously
223 missing KERNCONF files silently failed giving no indication as to
224 why, only to subsequently discover during installkernel that the
225 desired kernel was never built in the first place.
228 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
229 Please see the 20141231 entry below for information about prerequisites
230 and upgrading, if you are not already using clang 3.5.0 or higher.
233 Since the switch to GPT disk labels, fsck for UFS/FFS has been
234 unable to automatically find alternate superblocks. As of r322806,
235 the information needed to find alternate superblocks has been
236 moved to the end of the area reserved for the boot block.
237 Filesystems created with a newfs of this vintage or later
238 will create the recovery information. If you have a filesystem
239 created prior to this change and wish to have a recovery block
240 created for your filesystem, you can do so by running fsck in
241 forground mode (i.e., do not use the -p or -y options). As it
242 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
243 to which you should answer yes.
246 The releng/11.1 branch has been created from stable/11@r320475.
249 arm64 builds now use the base system LLD 4.0.0 linker by default,
250 instead of requiring that the aarch64-binutils port or package be
251 installed. To continue using aarch64-binutils, set
252 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
255 The ctl.ko module no longer implements the iSCSI target frontend:
256 cfiscsi.ko does instead.
258 If building cfiscsi.ko as a kernel module, the module can be loaded
259 via one of the following methods:
260 - `cfiscsi_load="YES"` in loader.conf(5).
261 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
262 - ctladm(8)/ctld(8), when compiled with iSCSI support
263 (`WITH_ISCSI=yes` in src.conf(5))
265 Please see cfiscsi(4) for more details.
268 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
269 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
270 same source (previously, the dependency of mmcsd.ko on mmc.ko was
271 missing, but mmcsd.ko now will refuse to load if it is incompatible
275 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
276 use any explicitly assigned loopback address available in the jail
277 instead of using the first assigned address of the jail.
280 As of r316810 for ipfilter, keep frags is no longer assumed when
281 keep state is specified in a rule. r316810 aligns ipfilter with
282 documentation in man pages separating keep frags from keep state.
283 This allows keep state to specified without forcing keep frags
284 and allows keep frags to be specified independently of keep state.
285 To maintain previous behaviour, also specify keep frags with
286 keep state (as documented in ipf.conf.5).
289 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
290 Please see the 20141231 entry below for information about prerequisites
291 and upgrading, if you are not already using clang 3.5.0 or higher.
294 The code that provides support for ZFS .zfs/ directory functionality
295 has been reimplemented. It's not possible now to create a snapshot
296 by mkdir under .zfs/snapshot/. That should be the only user visible
300 Many changes in the IPsec code have been merged from the FreeBSD-CURRENT
301 branch. The IPSEC_FILTERTUNNEL kernel option is removed in favour of
302 corresponding sysctl. The IPSEC_NAT_T kernel option is also removed,
303 and now NAT-T is supported by default. Security associations now use
304 the single namespace for SPI allocation, so if you use several manually
305 configured security associations with the same SPI, this configuration
309 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
310 Please see the 20141231 entry below for information about prerequisites
311 and upgrading, if you are not already using clang 3.5.0 or higher.
314 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
315 Please see the 20141231 entry below for information about prerequisites
316 and upgrading, if you are not already using clang 3.5.0 or higher.
319 The layout of the pmap structure has changed for powerpc to put the pmap
320 statistics at the front for all CPU variations. libkvm(3) and all tools
321 that link against it need to be recompiled.
324 isl(4) and cyapa(4) drivers now require a new driver,
325 chromebook_platform(4), to work properly on Chromebook-class hardware.
326 On other types of hardware the drivers may need to be configured using
327 device hints. Please see the corresponding manual pages for details.
330 Relocatable object files with the extension of .So have been renamed
331 to use an extension of .pico instead. The purpose of this change is
332 to avoid a name clash with shared libraries on case-insensitive file
333 systems. On those file systems, foo.So is the same file as foo.so.
336 The releng/11.0 branch has been created from stable/11@r303970.
339 The stable/11 branch has been created from head@r302406.
342 The libc stub for the pipe(2) system call has been replaced with
343 a wrapper that calls the pipe2(2) system call and the pipe(2)
344 system call is now only implemented by the kernels that include
345 "options COMPAT_FREEBSD10" in their config file (this is the
346 default). Users should ensure that this option is enabled in
347 their kernel or upgrade userspace to r302092 before upgrading their
351 CAM will now strip leading spaces from SCSI disks' serial numbers.
352 This will effect users who create UFS filesystems on SCSI disks using
353 those disk's diskid device nodes. For example, if /etc/fstab
354 previously contained a line like
355 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
356 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
357 transforms like gmirror may also be affected. ZFS users should
361 The bitstring(3) API has been updated with new functionality and
362 improved performance. But it is binary-incompatible with the old API.
363 Objects built with the new headers may not be linked against objects
364 built with the old headers.
367 The brk and sbrk functions have been removed from libc on arm64.
368 Binutils from ports has been updated to not link to these
369 functions and should be updated to the latest version before
370 installing a new libc.
373 The armv6 port now defaults to hard float ABI. Limited support
374 for running both hardfloat and soft float on the same system
375 is available using the libraries installed with -DWITH_LIBSOFT.
376 This has only been tested as an upgrade path for installworld
377 and packages may fail or need manual intervention to run. New
378 packages will be needed.
380 To update an existing self-hosted armv6hf system, you must add
381 TARGET_ARCH=armv6 on the make command line for both the build
382 and the install steps.
385 Kernel modules compiled outside of a kernel build now default to
386 installing to /boot/modules instead of /boot/kernel. Many kernel
387 modules built this way (such as those in ports) already overrode
388 KMODDIR explicitly to install into /boot/modules. However,
389 manually building and installing a module from /sys/modules will
390 now install to /boot/modules instead of /boot/kernel.
393 The CAM I/O scheduler has been committed to the kernel. There should be
394 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
395 list of known rogues that claim support for this but actually corrupt
396 data is believed to be complete, be on the lookout for data
397 corruption. The known rogue list is believed to be complete:
399 o Crucial MX100, M550 drives with MU01 firmware.
400 o Micron M510 and M550 drives with MU01 firmware.
401 o Micron M500 prior to MU07 firmware
402 o Samsung 830, 840, and 850 all firmwares
403 o FCCT M500 all firmwares
405 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
406 with working NCQ TRIM. For Micron branded drives, see your sales rep for
407 updated firmware. Black listed drives will work correctly because these
408 drives work correctly so long as no NCQ TRIMs are sent to them. Given
409 this list is the same as found in Linux, it's believed there are no
410 other rogues in the market place. All other models from the above
413 To be safe, if you are at all concerned, you can quirk each of your
414 drives to prevent NCQ from being sent by setting:
415 kern.cam.ada.X.quirks="0x2"
416 in loader.conf. If the drive requires the 4k sector quirk, set the
420 The FAST_DEPEND build option has been removed and its functionality is
421 now the one true way. The old mkdep(1) style of 'make depend' has
422 been removed. See 20160311 for further details.
425 Resource range types have grown from unsigned long to uintmax_t. All
426 drivers, and anything using libdevinfo, need to be recompiled.
429 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
430 builds. It no longer runs mkdep(1) during 'make depend', and the
431 'make depend' stage can safely be skipped now as it is auto ran
432 when building 'make all' and will generate all SRCS and DPSRCS before
433 building anything else. Dependencies are gathered at compile time with
434 -MF flags kept in separate .depend files per object file. Users should
435 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
439 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
440 kernel modules. Therefore, if you load any kernel modules at boot time,
441 please install the boot loaders after you install the kernel, but before
445 make kernel KERNCONF=YOUR_KERNEL_HERE
446 make -C sys/boot install
447 <reboot in single user>
449 Then follow the usual steps, described in the General Notes section,
453 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
454 see the 20141231 entry below for information about prerequisites and
455 upgrading, if you are not already using clang 3.5.0 or higher.
458 The AIO subsystem is now a standard part of the kernel. The
459 VFS_AIO kernel option and aio.ko kernel module have been removed.
460 Due to stability concerns, asynchronous I/O requests are only
461 permitted on sockets and raw disks by default. To enable
462 asynchronous I/O requests on all file types, set the
463 vfs.aio.enable_unsafe sysctl to a non-zero value.
466 The ELF object manipulation tool objcopy is now provided by the
467 ELF Tool Chain project rather than by GNU binutils. It should be a
468 drop-in replacement, with the addition of arm64 support. The
469 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
470 to obtain the GNU version if necessary.
473 Building ZFS pools on top of zvols is prohibited by default. That
474 feature has never worked safely; it's always been prone to deadlocks.
475 Using a zvol as the backing store for a VM guest's virtual disk will
476 still work, even if the guest is using ZFS. Legacy behavior can be
477 restored by setting vfs.zfs.vol.recursive=1.
480 The NONE and HPN patches has been removed from OpenSSH. They are
481 still available in the security/openssh-portable port.
484 With the addition of ypldap(8), a new _ypldap user is now required
485 during installworld. "mergemaster -p" can be used to add the user
486 prior to installworld, as documented in the handbook.
489 The tftp loader (pxeboot) now uses the option root-path directive. As a
490 consequence it no longer looks for a pxeboot.4th file on the tftp
491 server. Instead it uses the regular /boot infrastructure as with the
495 The code to start recording plug and play data into the modules has
496 been committed. While the old tools will properly build a new kernel,
497 a number of warnings about "unknown metadata record 4" will be produced
498 for an older kldxref. To avoid such warnings, make sure to rebuild
499 the kernel toolchain (or world). Make sure that you have r292078 or
500 later when trying to build 292077 or later before rebuilding.
503 Debug data files are now built by default with 'make buildworld' and
504 installed with 'make installworld'. This facilitates debugging but
505 requires more disk space both during the build and for the installed
506 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
510 r291527 changed the internal interface between the nfsd.ko and
511 nfscommon.ko modules. As such, they must both be upgraded to-gether.
512 __FreeBSD_version has been bumped because of this.
515 Add support for unicode collation strings leads to a change of
516 order of files listed by ls(1) for example. To get back to the old
517 behaviour, set LC_COLLATE environment variable to "C".
519 Databases administrators will need to reindex their databases given
520 collation results will be different.
522 Due to a bug in install(1) it is recommended to remove the ancient
523 locales before running make installworld.
525 rm -rf /usr/share/locale/*
528 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
529 libcrypto.so.7 or libssl.so.7 must be recompiled.
532 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
533 Kernel modules isp_2400_multi and isp_2500_multi were removed and
534 should be replaced with isp_2400 and isp_2500 modules respectively.
537 The build previously allowed using 'make -n' to not recurse into
538 sub-directories while showing what commands would be executed, and
539 'make -n -n' to recursively show commands. Now 'make -n' will recurse
540 and 'make -N' will not.
543 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
544 and etcupdate will now use this file. A custom sendmail.cf is now
545 updated via this mechanism rather than via installworld. If you had
546 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
547 want to remove the exclusion or change it to "always install".
548 /etc/mail/sendmail.cf is now managed the same way regardless of
549 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
550 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
553 Compatibility shims for legacy ATA device names have been removed.
554 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
555 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
556 environment variables, /dev/ad* and /dev/ar* symbolic links.
559 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
560 Please see the 20141231 entry below for information about prerequisites
561 and upgrading, if you are not already using clang 3.5.0 or higher.
564 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
565 and renamed from .symbols to .debug. This reduces the size requirements
566 on the boot partition or file system and provides consistency with
567 userland debug files.
569 When using the supported kernel installation method the
570 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
571 as is done with /boot/kernel.
573 Developers wishing to maintain the historical behavior of installing
574 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
577 The wireless drivers had undergone changes that remove the 'parent
578 interface' from the ifconfig -l output. The rc.d network scripts
579 used to check presence of a parent interface in the list, so old
580 scripts would fail to start wireless networking. Thus, etcupdate(3)
581 or mergemaster(8) run is required after kernel update, to update your
582 rc.d scripts in /etc.
585 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
586 These configurations are now automatically interpreted as
587 'scrub fragment reassemble'.
590 Kernel-loadable modules for the random(4) device are back. To use
591 them, the kernel must have
594 options RANDOM_LOADABLE
596 kldload(8) can then be used to load random_fortuna.ko
597 or random_yarrow.ko. Please note that due to the indirect
598 function calls that the loadable modules need to provide,
599 the build-in variants will be slightly more efficient.
601 The random(4) kernel option RANDOM_DUMMY has been retired due to
602 unpopularity. It was not all that useful anyway.
605 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
606 Control over building the ELF Tool Chain tools is now provided by
607 the WITHOUT_TOOLCHAIN knob.
610 The polarity of Pulse Per Second (PPS) capture events with the
611 uart(4) driver has been corrected. Prior to this change the PPS
612 "assert" event corresponded to the trailing edge of a positive PPS
613 pulse and the "clear" event was the leading edge of the next pulse.
615 As the width of a PPS pulse in a typical GPS receiver is on the
616 order of 1 millisecond, most users will not notice any significant
617 difference with this change.
619 Anyone who has compensated for the historical polarity reversal by
620 configuring a negative offset equal to the pulse width will need to
621 remove that workaround.
624 The default group assigned to /dev/dri entries has been changed
625 from 'wheel' to 'video' with the id of '44'. If you want to have
626 access to the dri devices please add yourself to the video group
629 # pw groupmod video -m $USER
632 The menu.rc and loader.rc files will now be replaced during
633 upgrades. Please migrate local changes to menu.rc.local and
634 loader.rc.local instead.
637 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
638 strings and strip have been removed. The src.conf(5) knob
639 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
642 As ZFS requires more kernel stack pages than is the default on some
643 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
644 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
646 Please consider using 'options KSTACK_PAGES=X' where X is greater
647 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
650 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
651 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
652 default, i.e., they will not contain "::". For example, instead
653 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
654 to have a more specific match, such as different map entries for
655 IPv6:0:0 vs IPv6:0. This change requires that configuration
656 data (including maps, files, classes, custom ruleset, etc.) must
657 use the same format, so make certain such configuration data is
658 upgrading. As a very simple check search for patterns like
659 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
660 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
661 the cf option UseCompressedIPv6Addresses.
664 The default kernel entropy-processing algorithm is now
665 Fortuna, replacing Yarrow.
667 Assuming you have 'device random' in your kernel config
668 file, the configurations allow a kernel option to override
669 this default. You may choose *ONE* of:
671 options RANDOM_YARROW # Legacy /dev/random algorithm.
672 options RANDOM_DUMMY # Blocking-only driver.
674 If you have neither, you get Fortuna. For most people,
675 read no further, Fortuna will give a /dev/random that works
676 like it always used to, and the difference will be irrelevant.
678 If you remove 'device random', you get *NO* kernel-processed
679 entropy at all. This may be acceptable to folks building
680 embedded systems, but has complications. Carry on reading,
681 and it is assumed you know what you need.
683 *PLEASE* read random(4) and random(9) if you are in the
684 habit of tweaking kernel configs, and/or if you are a member
685 of the embedded community, wanting specific and not-usual
686 behaviour from your security subsystems.
688 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
689 random', you will NOT have a functioning /dev/random, and
690 many cryptographic features will not work, including SSH.
691 You may also find strange behaviour from the random(3) set
692 of library functions, in particular sranddev(3), srandomdev(3)
693 and arc4random(3). The reason for this is that the KERN_ARND
694 sysctl only returns entropy if it thinks it has some to
695 share, and with RANDOM_DUMMY or no 'device random' this
699 An additional fix for the issue described in the 20150614 sendmail
700 entry below has been been committed in revision 284717.
703 FreeBSD's old make (fmake) has been removed from the system. It is
704 available as the devel/fmake port or via pkg install fmake.
707 The fix for the issue described in the 20150614 sendmail entry
708 below has been been committed in revision 284436. The work
709 around described in that entry is no longer needed unless the
710 default setting is overridden by a confDH_PARAMETERS configuration
711 setting of '5' or pointing to a 512 bit DH parameter file.
714 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
715 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
716 and devel/kyua to version 0.20+ and adjust any calling code to work
717 with Kyuafile and kyua.
720 The import of openssl to address the FreeBSD-SA-15:10.openssl
721 security advisory includes a change which rejects handshakes
722 with DH parameters below 768 bits. sendmail releases prior
723 to 8.15.2 (not yet released), defaulted to a 512 bit
724 DH parameter setting for client connections. To work around
725 this interoperability, sendmail can be configured to use a
726 2048 bit DH parameter by:
728 1. Edit /etc/mail/`hostname`.mc
729 2. If a setting for confDH_PARAMETERS does not exist or
730 exists and is set to a string beginning with '5',
732 3. If a setting for confDH_PARAMETERS exists and is set to
733 a file path, create a new file with:
734 openssl dhparam -out /path/to/file 2048
735 4. Rebuild the .cf file:
736 cd /etc/mail/; make; make install
738 cd /etc/mail/; make restart
740 A sendmail patch is coming, at which time this file will be
744 Generation of legacy formatted entries have been disabled by default
745 in pwd_mkdb(8), as all base system consumers of the legacy formatted
746 entries were converted to use the new format by default when the new,
747 machine independent format have been added and supported since FreeBSD
750 Please see the pwd_mkdb(8) manual page for further details.
753 Clang and llvm have been upgraded to 3.6.1 release. Please see the
754 20141231 entry below for information about prerequisites and upgrading,
755 if you are not already using 3.5.0 or higher.
758 TI platform code switched to using vendor DTS files and this update
759 may break existing systems running on Beaglebone, Beaglebone Black,
762 - dtb files should be regenerated/reinstalled. Filenames are the
763 same but content is different now
764 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
765 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
766 addressing scheme is now pin 25 on /dev/gpioc3.
767 - Pandaboard: /etc/ttys should be updated, serial console device is
768 now /dev/ttyu2, not /dev/ttyu0
771 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
772 If you need the GNU extension from groff soelim(1), install groff
773 from package: pkg install groff, or via ports: textproc/groff.
776 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
777 defined in symlink(7); previously symlinks were silently ignored.
780 The const qualifier has been removed from iconv(3) to comply with
781 POSIX. The ports tree is aware of this from r384038 onwards.
784 Libraries specified by LIBADD in Makefiles must have a corresponding
785 DPADD_<lib> variable to ensure correct dependencies. This is now
786 enforced in src.libnames.mk.
789 From legacy ata(4) driver was removed support for SATA controllers
790 supported by more functional drivers ahci(4), siis(4) and mvs(4).
791 Kernel modules ataahci and ataadaptec were removed completely,
792 replaced by ahci and mvs modules respectively.
795 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
796 the 20141231 entry below for information about prerequisites and
797 upgrading, if you are not already using 3.5.0 or higher.
800 The 32-bit PowerPC kernel has been changed to a position-independent
801 executable. This can only be booted with a version of loader(8)
802 newer than January 31, 2015, so make sure to update both world and
803 kernel before rebooting.
806 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
807 but before r278950, the RNG was not seeded properly. Immediately
808 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
809 ssh keys or openssl keys) that were generated w/ a kernel from that
810 range. This does not affect programs that directly used /dev/random
811 or /dev/urandom. All userland uses of arc4random(3) are affected.
814 The autofs(4) ABI was changed in order to restore binary compatibility
815 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
819 The powerpc64 kernel has been changed to a position-independent
820 executable. This can only be booted with a new version of loader(8),
821 so make sure to update both world and kernel before rebooting.
824 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
825 only release, no new features have been added. Please see the 20141231
826 entry below for information about prerequisites and upgrading, if you
827 are not already using 3.5.0.
830 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
831 taken from the ELF Tool Chain project rather than GNU binutils. They
832 should be drop-in replacements, with the addition of arm64 support.
833 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
834 binutils tools, if necessary. See 20150805 for updated information.
837 The default Unbound configuration now enables remote control
838 using a local socket. Users who have already enabled the
839 local_unbound service should regenerate their configuration
840 by running "service local_unbound setup" as root.
843 The GNU texinfo and GNU info pages have been removed.
844 To be able to view GNU info pages please install texinfo from ports.
847 Clang, llvm and lldb have been upgraded to 3.5.0 release.
849 As of this release, a prerequisite for building clang, llvm and lldb is
850 a C++11 capable compiler and C++11 standard library. This means that to
851 be able to successfully build the cross-tools stage of buildworld, with
852 clang as the bootstrap compiler, your system compiler or cross compiler
853 should either be clang 3.3 or later, or gcc 4.8 or later, and your
854 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
857 On any standard FreeBSD 10.x or 11.x installation, where clang and
858 libc++ are on by default (that is, on x86 or arm), this should work out
861 On 9.x installations where clang is enabled by default, e.g. on x86 and
862 powerpc, libc++ will not be enabled by default, so libc++ should be
863 built (with clang) and installed first. If both clang and libc++ are
864 missing, build clang first, then use it to build libc++.
866 On 8.x and earlier installations, upgrade to 9.x first, and then follow
867 the instructions for 9.x above.
869 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
870 default, and do not build clang.
872 Many embedded systems are resource constrained, and will not be able to
873 build clang in a reasonable time, or in some cases at all. In those
874 cases, cross building bootable systems on amd64 is a workaround.
876 This new version of clang introduces a number of new warnings, of which
877 the following are most likely to appear:
881 This warns in two cases, for both C and C++:
882 * When the code is trying to take the absolute value of an unsigned
883 quantity, which is effectively a no-op, and almost never what was
884 intended. The code should be fixed, if at all possible. If you are
885 sure that the unsigned quantity can be safely cast to signed, without
886 loss of information or undefined behavior, you can add an explicit
887 cast, or disable the warning.
889 * When the code is trying to take an absolute value, but the called
890 abs() variant is for the wrong type, which can lead to truncation.
891 If you want to disable the warning instead of fixing the code, please
892 make sure that truncation will not occur, or it might lead to unwanted
895 -Wtautological-undefined-compare and
896 -Wundefined-bool-conversion
898 These warn when C++ code is trying to compare 'this' against NULL, while
899 'this' should never be NULL in well-defined C++ code. However, there is
900 some legacy (pre C++11) code out there, which actively abuses this
901 feature, which was less strictly defined in previous C++ versions.
903 Squid and openjdk do this, for example. The warning can be turned off
904 for C++98 and earlier, but compiling the code in C++11 mode might result
905 in unexpected behavior; for example, the parts of the program that are
906 unreachable could be optimized away.
909 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
910 kernel sources have been removed. The .h files remain, since some
911 utilities include them. This will need to be fixed later.
912 If "mount -t oldnfs ..." is attempted, it will fail.
913 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
914 the utilities will report errors.
917 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
918 directories to top level SUBDIR variable when their parent
919 directory is included in LOCAL_DIRS. Users with build systems with
920 such hierarchies and without SUBDIR entries in the parent
921 directory Makefiles should add them or add the directories to
925 faith(4) and faithd(8) have been removed from the base system. Faith
926 has been obsolete for a very long time.
929 vt(4), the new console driver, is enabled by default. It brings
930 support for Unicode and double-width characters, as well as
931 support for UEFI and integration with the KMS kernel video
934 You may need to update your console settings in /etc/rc.conf,
935 most probably the keymap. During boot, /etc/rc.d/syscons will
936 indicate what you need to do.
938 vt(4) still has issues and lacks some features compared to
939 syscons(4). See the wiki for up-to-date information:
940 https://wiki.freebsd.org/Newcons
942 If you want to keep using syscons(4), you can do so by adding
943 the following line to /boot/loader.conf:
947 pjdfstest has been integrated into kyua as an opt-in test suite.
948 Please see share/doc/pjdfstest/README for more details on how to
952 gperf has been removed from the base system for architectures
953 that use clang. Ports that require gperf will obtain it from the
957 pjdfstest has been moved from tools/regression/pjdfstest to
961 At svn r271982, The default linux compat kernel ABI has been adjusted
962 to 2.6.18 in support of the linux-c6 compat ports infrastructure
963 update. If you wish to continue using the linux-f10 compat ports,
964 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
965 encouraged to update their linux-compat packages to linux-c6 during
966 their next update cycle.
969 The ofwfb driver, used to provide a graphics console on PowerPC when
970 using vt(4), no longer allows mmap() of all physical memory. This
971 will prevent Xorg on PowerPC with some ATI graphics cards from
972 initializing properly unless x11-servers/xorg-server is updated to
976 The xdev targets have been converted to using TARGET and
977 TARGET_ARCH instead of XDEV and XDEV_ARCH.
980 The default unbound configuration has been modified to address
981 issues with reverse lookups on networks that use private
982 address ranges. If you use the local_unbound service, run
983 "service local_unbound setup" as root to regenerate your
984 configuration, then "service local_unbound reload" to load the
988 The GNU texinfo and GNU info pages are not built and installed
989 anymore, WITH_INFO knob has been added to allow to built and install
991 UPDATE: see 20150102 entry on texinfo's removal
994 The GNU readline library is now an INTERNALLIB - that is, it is
995 statically linked into consumers (GDB and variants) in the base
996 system, and the shared library is no longer installed. The
997 devel/readline port is available for third party software that
1001 The Itanium architecture (ia64) has been removed from the list of
1002 known architectures. This is the first step in the removal of the
1006 Commit r268115 has added NFSv4.1 server support, merged from
1007 projects/nfsv4.1-server. Since this includes changes to the
1008 internal interfaces between the NFS related modules, a full
1009 build of the kernel and modules will be necessary.
1010 __FreeBSD_version has been bumped.
1013 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1014 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1015 which differs from the behaviour controlled by this knob.)
1018 Maximal length of the serial number in CTL was increased from 16 to
1019 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1020 and ctld, need to be rebuilt to work with a new kernel.
1023 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1024 1 respectively to match the upstream numbers. They were out of
1025 sync because, when they were originally added to FreeBSD, the
1026 upstream versions were not respected. These libraries are private
1027 and not yet built by default, so renumbering them should be a
1028 non-issue. However, unclean source trees will yield broken test
1029 programs once the operator executes "make delete-old-libs" after a
1030 "make installworld".
1032 Additionally, the atf-sh binary was made private by moving it into
1033 /usr/libexec/. Already-built shell test programs will keep the
1034 path to the old binary so they will break after "make delete-old"
1037 If you are using WITH_TESTS=yes (not the default), wipe the object
1038 tree and rebuild from scratch to prevent spurious test failures.
1039 This is only needed once: the misnumbered libraries and misplaced
1040 binaries have been added to OptionalObsoleteFiles.inc so they will
1041 be removed during a clean upgrade.
1044 Clang and llvm have been upgraded to 3.4.1 release.
1047 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1048 be removed to avoid issues in the future (and has been added to
1052 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1053 past, it affected all builds that used the bsd.*.mk files. The old
1054 behavior was a bug, but people may have relied upon it. To get this
1055 behavior back, you can .include /etc/src.conf from /etc/make.conf
1056 (which is still global and isn't changed). This also changes the
1057 behavior of incremental builds inside the tree of individual
1058 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1059 Although this has survived make universe and some upgrade scenarios,
1060 other upgrade scenarios may have broken. At least one form of
1061 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1062 as well... In cases where MAKESYSPATH isn't working with this
1063 setting, you'll need to set it to the full path to your tree.
1065 One side effect of all this cleaning up is that bsd.compiler.mk
1066 is no longer implicitly included by bsd.own.mk. If you wish to
1067 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1071 The lindev device has been removed since /dev/full has been made a
1072 standard device. __FreeBSD_version has been bumped.
1075 The knob WITHOUT_VI was added to the base system, which controls
1076 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1077 in order to reorder files share/termcap and didn't build ex(1) as a
1078 build tool, so building/installing with WITH_VI is highly advised for
1079 build hosts for older releases.
1081 This issue has been fixed in stable/9 and stable/10 in r277022 and
1082 r276991, respectively.
1085 The YES_HESIOD knob has been removed. It has been obsolete for
1086 a decade. Please move to using WITH_HESIOD instead or your builds
1087 will silently lack HESIOD.
1090 The uart(4) driver has been changed with respect to its handling
1091 of the low-level console. Previously the uart(4) driver prevented
1092 any process from changing the baudrate or the CLOCAL and HUPCL
1093 control flags. By removing the restrictions, operators can make
1094 changes to the serial console port without having to reboot.
1095 However, when getty(8) is started on the serial device that is
1096 associated with the low-level console, a misconfigured terminal
1097 line in /etc/ttys will now have a real impact.
1098 Before upgrading the kernel, make sure that /etc/ttys has the
1099 serial console device configured as 3wire without baudrate to
1100 preserve the previous behaviour. E.g:
1101 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1104 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1105 to improve performance. To re-enable it, if needed, run rpcbind
1106 with command line option -W.
1109 Switched back to the GPL dtc compiler due to updates in the upstream
1110 dts files not being supported by the BSDL dtc compiler. You will need
1111 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1112 may result while building dtb files during a kernel build if you fail
1113 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1116 Clang and llvm have been upgraded to 3.4 release.
1119 The nve(4) driver has been removed. Please use the nfe(4) driver
1120 for NVIDIA nForce MCP Ethernet adapters instead.
1123 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1124 This could cause certain C++ applications using shared libraries built
1125 against the previous version of libc++ to crash. The incompatibility
1126 has now been fixed, but any C++ applications or shared libraries built
1127 between r261283 and r261801 should be recompiled.
1130 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1131 capability mode support. Please note that enabling the feature in
1132 kernel is still highly recommended.
1135 OpenSSH is now built with sandbox support, and will use sandbox as
1136 the default privilege separation method. This requires Capsicum
1137 capability mode support in kernel.
1140 The libelf and libdwarf libraries have been updated to newer
1141 versions from upstream. Shared library version numbers for
1142 these two libraries were bumped. Any ports or binaries
1143 requiring these two libraries should be recompiled.
1144 __FreeBSD_version is bumped to 1100006.
1147 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1148 instead of providing an explicit one, this would prevent such
1149 Makefile from providing its own Kyuafile in the future during
1150 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1151 intervention is needed to clean an objdir if you use NO_CLEAN:
1152 # find /usr/obj -name Kyuafile | xargs rm -f
1155 The behavior of gss_pseudo_random() for the krb5 mechanism
1156 has changed, for applications requesting a longer random string
1157 than produced by the underlying enctype's pseudo-random() function.
1158 In particular, the random string produced from a session key of
1159 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1160 be different at the 17th octet and later, after this change.
1161 The counter used in the PRF+ construction is now encoded as a
1162 big-endian integer in accordance with RFC 4402.
1163 __FreeBSD_version is bumped to 1100004.
1166 The WITHOUT_ATF build knob has been removed and its functionality
1167 has been subsumed into the more generic WITHOUT_TESTS. If you were
1168 using the former to disable the build of the ATF libraries, you
1169 should change your settings to use the latter.
1172 The default version of mtree is nmtree which is obtained from
1173 NetBSD. The output is generally the same, but may vary
1174 slightly. If you found you need identical output adding
1175 "-F freebsd9" to the command line should do the trick. For the
1176 time being, the old mtree is available as fmtree.
1179 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1180 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1181 1.1.4_8 and verify bsdyml not linked in, before running "make
1183 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1185 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1188 The stable/10 branch has been created in subversion from head
1192 The rc.d/jail script has been updated to support jail(8)
1193 configuration file. The "jail_<jname>_*" rc.conf(5) variables
1194 for per-jail configuration are automatically converted to
1195 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
1196 This is transparently backward compatible. See below about some
1197 incompatibilities and rc.conf(5) manual page for more details.
1199 These variables are now deprecated in favor of jail(8) configuration
1200 file. One can use "rc.d/jail config <jname>" command to generate
1201 a jail(8) configuration file in /var/run/jail.<jname>.conf without
1202 running the jail(8) utility. The default pathname of the
1203 configuration file is /etc/jail.conf and can be specified by
1204 using $jail_conf or $jail_<jname>_conf variables.
1206 Please note that jail_devfs_ruleset accepts an integer at
1207 this moment. Please consider to rewrite the ruleset name
1211 BIND has been removed from the base system. If all you need
1212 is a local resolver, simply enable and start the local_unbound
1213 service instead. Otherwise, several versions of BIND are
1214 available in the ports tree. The dns/bind99 port is one example.
1216 With this change, nslookup(1) and dig(1) are no longer in the base
1217 system. Users should instead use host(1) and drill(1) which are
1218 in the base system. Alternatively, nslookup and dig can
1219 be obtained by installing the dns/bind-tools port.
1222 With the addition of unbound(8), a new unbound 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 OpenSSH is now built with DNSSEC support, and will by default
1228 silently trust signed SSHFP records. This can be controlled with
1229 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1230 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1233 The GNU Compiler Collection and C++ standard library (libstdc++)
1234 are no longer built by default on platforms where clang is the system
1235 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1236 options in src.conf.
1239 The PROCDESC kernel option is now part of the GENERIC kernel
1240 configuration and is required for the rwhod(8) to work.
1241 If you are using custom kernel configuration, you should include
1245 The API and ABI related to the Capsicum framework was modified
1246 in backward incompatible way. The userland libraries and programs
1247 have to be recompiled to work with the new kernel. This includes the
1248 following libraries and programs, but the whole buildworld is
1249 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1250 kdump, procstat, rwho, rwhod, uniq.
1253 AES-NI intrinsic support has been added to gcc. The AES-NI module
1254 has been updated to use this support. A new gcc is required to build
1255 the aesni module on both i386 and amd64.
1258 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1259 Thus "device padlock_rng" and "device rdrand_rng" should be
1260 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1263 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1264 enables just the iconv* functionality and is now on by default.
1265 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1266 compatibility. Set WITHOUT_ICONV to build the old way.
1267 If you have been using WITH_ICONV before, you will very likely
1268 need to turn on WITH_LIBICONV_COMPAT.
1271 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1272 Illumos origin, including ZFS. If you have INVARIANTS in your
1273 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1275 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1276 locks if WITNESS option was set. Because that generated a lot of
1277 witness(9) reports and all of them were believed to be false
1278 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1279 can be used to achieve the previous behavior.
1282 Timer values in IPv6 data structures now use time_uptime instead
1283 of time_second. Although this is not a user-visible functional
1284 change, userland utilities which directly use them---ndp(8),
1285 rtadvd(8), and rtsold(8) in the base system---need to be updated
1286 to r253970 or later.
1289 find -delete can now delete the pathnames given as arguments,
1290 instead of only files found below them or if the pathname did
1291 not contain any slashes. Formerly, the following error message
1294 find: -delete: <path>: relative path potentially not safe
1296 Deleting the pathnames given as arguments can be prevented
1297 without error messages using -mindepth 1 or by changing
1298 directory and passing "." as argument to find. This works in the
1299 old as well as the new version of find.
1302 Behavior of devfs rules path matching has been changed.
1303 Pattern is now always matched against fully qualified devfs
1304 path and slash characters must be explicitly matched by
1305 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1306 subdirectories must be reviewed.
1309 The default ARM ABI has changed to the ARM EABI. The old ABI is
1310 incompatible with the ARM EABI and all programs and modules will
1311 need to be rebuilt to work with a new kernel.
1313 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1315 NOTE: Support for the old ABI will be removed in the future and
1316 users are advised to upgrade.
1319 pkg_install has been disconnected from the build if you really need it
1320 you should add WITH_PKGTOOLS in your src.conf(5).
1323 Most of network statistics structures were changed to be able
1324 keep 64-bits counters. Thus all tools, that work with networking
1325 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1328 Fix a bug that allowed a tracing process (e.g. gdb) to write
1329 to a memory-mapped file in the traced process's address space
1330 even if neither the traced process nor the tracing process had
1331 write access to that file.
1334 CVS has been removed from the base system. An exact copy
1335 of the code is available from the devel/cvs port.
1338 Some people report the following error after the switch to bmake:
1340 make: illegal option -- J
1341 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1343 *** [buildworld] Error code 2
1345 this likely due to an old instance of make in
1346 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1347 which src/Makefile will use that blindly, if it exists, so if
1348 you see the above error:
1350 rm -rf `make -V MAKEPATH`
1355 Use bmake by default.
1356 Whereas before one could choose to build with bmake via
1357 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1358 make. The goal is to remove these knobs for 10-RELEASE.
1360 It is worth noting that bmake (like gmake) treats the command
1361 line as the unit of failure, rather than statements within the
1362 command line. Thus '(cd some/where && dosomething)' is safer
1363 than 'cd some/where; dosomething'. The '()' allows consistent
1364 behavior in parallel build.
1367 Fix a bug that allows NFS clients to issue READDIR on files.
1370 The WITHOUT_IDEA option has been removed because
1371 the IDEA patent expired.
1374 The sysctl which controls TRIM support under ZFS has been renamed
1375 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1379 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1380 rather than creating it's own in the temporary directory in
1381 order allow access to bootstrapped versions of tools such as
1382 install and mtree. When upgrading from version of FreeBSD where
1383 the install command does not support -l, you will need to
1384 install a new mergemaster command if mergemaster -p is required.
1385 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1389 Legacy ATA stack, disabled and replaced by new CAM-based one since
1390 FreeBSD 9.0, completely removed from the sources. Kernel modules
1391 atadisk and atapi*, user-level tools atacontrol and burncd are
1392 removed. Kernel option `options ATA_CAM` is now permanently enabled
1396 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1397 and socketpair(2). Software, in particular Kerberos, may
1398 automatically detect and use these during building. The resulting
1399 binaries will not work on older kernels.
1402 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1403 information, see the respective 20130304 entry).
1406 Recent commits to callout(9) changed the size of struct callout,
1407 so the KBI is probably heavily disturbed. Also, some functions
1408 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1409 by macros. Every kernel module using it won't load, so rebuild
1412 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1413 but does not initialize by default (because of the new CTL_DISABLE
1414 option) to save memory. To re-enable it, remove the CTL_DISABLE
1415 option from the kernel config file or set kern.cam.ctl.disable=0
1416 in /boot/loader.conf.
1419 The ctl device has been disabled in GENERIC for i386 and amd64.
1420 This was done due to the extra memory being allocated at system
1421 initialisation time by the ctl driver which was only used if
1422 a CAM target device was created. This makes a FreeBSD system
1423 unusable on 128MB or less of RAM.
1426 A new compression method (lz4) has been merged to -HEAD. Please
1427 refer to zpool-features(7) for more information.
1429 Please refer to the "ZFS notes" section of this file for information
1430 on upgrading boot ZFS pools.
1433 A BSD-licensed patch(1) variant has been added and is installed
1434 as bsdpatch, being the GNU version the default patch.
1435 To inverse the logic and use the BSD-licensed one as default,
1436 while having the GNU version installed as gnupatch, rebuild
1437 and install world with the WITH_BSD_PATCH knob set.
1440 Due to the use of the new -l option to install(1) during build
1441 and install, you must take care not to directly set the INSTALL
1442 make variable in your /etc/make.conf, /etc/src.conf, or on the
1443 command line. If you wish to use the -C flag for all installs
1444 you may be able to add INSTALL+=-C to /etc/make.conf or
1448 The install(1) option -M has changed meaning and now takes an
1449 argument that is a file or path to append logs to. In the
1450 unlikely event that -M was the last option on the command line
1451 and the command line contained at least two files and a target
1452 directory the first file will have logs appended to it. The -M
1453 option served little practical purpose in the last decade so its
1454 use is expected to be extremely rare.
1457 After switching to Clang as the default compiler some users of ZFS
1458 on i386 systems started to experience stack overflow kernel panics.
1459 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1462 GEOM_LABEL now mangles label names read from file system metadata.
1463 Mangling affect labels containing spaces, non-printable characters,
1464 '%' or '"'. Device names in /etc/fstab and other places may need to
1468 By default, only the 10 most recent kernel dumps will be saved. To
1469 restore the previous behaviour (no limit on the number of kernel dumps
1470 stored in the dump directory) add the following line to /etc/rc.conf:
1475 With the addition of auditdistd(8), a new auditdistd user is now
1476 required during installworld. "mergemaster -p" can be used to
1477 add the user prior to installworld, as documented in the handbook.
1480 The sin6_scope_id member variable in struct sockaddr_in6 is now
1481 filled by the kernel before passing the structure to the userland via
1482 sysctl or routing socket. This means the KAME-specific embedded scope
1483 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1484 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1485 __FreeBSD_version is bumped to 1000025.
1488 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1489 This means that the world and kernel will be compiled with clang
1490 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1491 and /usr/bin/cpp. To disable this behavior and revert to building
1492 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1493 of current may need to bootstrap WITHOUT_CLANG first if the clang
1494 build fails (its compatibility window doesn't extend to the 9 stable
1498 The IPFIREWALL_FORWARD kernel option has been removed. Its
1499 functionality now turned on by default.
1502 The ZERO_COPY_SOCKET kernel option has been removed and
1503 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1504 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1505 mechanism which is not safe and may result in kernel crashes.
1506 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1507 driver supports disposeable external page sized mbuf storage.
1508 Proper replacements for both zero-copy mechanisms are under
1509 consideration and will eventually lead to complete removal
1510 of the two kernel options.
1513 The IPv4 network stack has been converted to network byte
1514 order. The following modules need to be recompiled together
1515 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1516 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1519 Support for non-MPSAFE filesystems was removed from VFS. The
1520 VFS_VERSION was bumped, all filesystem modules shall be
1524 All the non-MPSAFE filesystems have been disconnected from
1525 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1526 portalfs, smbfs, xfs.
1529 The interface cloning API and ABI has changed. The following
1530 modules need to be recompiled together with kernel:
1531 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1532 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1533 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1536 The sdhci driver was split in two parts: sdhci (generic SD Host
1537 Controller logic) and sdhci_pci (actual hardware driver).
1538 No kernel config modifications are required, but if you
1539 load sdhc as a module you must switch to sdhci_pci instead.
1542 Import the FUSE kernel and userland support into base system.
1545 The GNU sort(1) program has been removed since the BSD-licensed
1546 sort(1) has been the default for quite some time and no serious
1547 problems have been reported. The corresponding WITH_GNU_SORT
1551 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1552 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1556 The net80211(4) ABI has been changed to allow for improved driver
1557 PS-POLL and power-save support. All wireless drivers need to be
1558 recompiled to work with the new kernel.
1561 The random(4) support for the VIA hardware random number
1562 generator (`PADLOCK') is no longer enabled unconditionally.
1563 Add the padlock_rng device in the custom kernel config if
1564 needed. The GENERIC kernels on i386 and amd64 do include the
1565 device, so the change only affects the custom kernel
1569 The pf(4) packet filter ABI has been changed. pfctl(8) and
1570 snmp_pf module need to be recompiled to work with new kernel.
1573 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1574 to -HEAD. Pools that have empty_bpobj in active state can not be
1575 imported read-write with ZFS implementations that do not support
1576 this feature. For more information read the zpool-features(5)
1580 The sparc64 ZFS loader has been changed to no longer try to auto-
1581 detect ZFS providers based on diskN aliases but now requires these
1582 to be explicitly listed in the OFW boot-device environment variable.
1585 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1586 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1587 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1590 The following sysctls and tunables have been renamed for consistency
1591 with other variables:
1592 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1593 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1596 The sort utility has been replaced with BSD sort. For now, GNU sort
1597 is also available as "gnusort" or the default can be set back to
1598 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1599 installed as "bsdsort".
1602 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1603 Starting with this version the old system of ZFS pool versioning
1604 is superseded by "feature flags". This concept enables forward
1605 compatibility against certain future changes in functionality of ZFS
1606 pools. The first read-only compatible "feature flag" for ZFS pools
1607 is named "com.delphix:async_destroy". For more information
1608 read the new zpool-features(5) manual page.
1609 Please refer to the "ZFS notes" section of this file for information
1610 on upgrading boot ZFS pools.
1613 The malloc(3) implementation embedded in libc now uses sources imported
1614 as contrib/jemalloc. The most disruptive API change is to
1615 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1616 delete it prior to installworld, and optionally re-create it using the
1617 new format after rebooting. See malloc.conf(5) for details
1618 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1622 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1623 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1624 now spelled mips. This is to aid compatibility with third-party
1625 software that expects this naming scheme in uname(3). Little-endian
1626 settings are unchanged. If you are updating a big-endian mips64 machine
1627 from before this change, you may need to set MACHINE_ARCH=mips64 in
1628 your environment before the new build system will recognize your machine.
1631 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1635 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1636 nullfs(5) did not pass through all behaviours to the underlying layer,
1637 as a result if we bound to a socket on the lower layer we could connect
1638 only to the lower path; if we bound to the upper layer we could connect
1639 only to the upper path. The new behavior is one can connect to both the
1640 lower and the upper paths regardless what layer path one binds to.
1643 The getifaddrs upgrade path broken with 20111215 has been restored.
1644 If you have upgraded in between 20111215 and 20120209 you need to
1645 recompile libc again with your kernel. You still need to recompile
1646 world to be able to configure CARP but this restriction already
1647 comes from 20111215.
1650 The set_rcvar() function has been removed from /etc/rc.subr. All
1651 base and ports rc.d scripts have been updated, so if you have a
1652 port installed with a script in /usr/local/etc/rc.d you can either
1653 hand-edit the rcvar= line, or reinstall the port.
1655 An easy way to handle the mass-update of /etc/rc.d:
1656 rm /etc/rc.d/* && mergemaster -i
1659 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1660 on the current CPU and prevents other threads from running.
1661 This behavior can be reverted using the kern.stop_scheduler_on_panic
1663 The new behavior can be incompatible with kern.sync_on_panic.
1666 The carp(4) facility has been changed significantly. Configuration
1667 of the CARP protocol via ifconfig(8) has changed, as well as format
1668 of CARP events submitted to devd(8) has changed. See manual pages
1669 for more information. The arpbalance feature of carp(4) is currently
1670 not supported anymore.
1672 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1673 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1674 need to be recompiled.
1677 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1681 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1682 explicitely support non-MPSAFE filesystems.
1683 It is on by default for all supported platform at this present
1687 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1688 i386 and pc98 GENERIC kernel configuration files.
1691 sysinstall has been removed
1694 The stable/9 branch created in subversion. This corresponds to the
1695 RELENG_9 branch in CVS.
1701 Avoid using make -j when upgrading. While generally safe, there are
1702 sometimes problems using -j to upgrade. If your upgrade fails with
1703 -j, please try again without -j. From time to time in the past there
1704 have been problems using -j with buildworld and/or installworld. This
1705 is especially true when upgrading between "distant" versions (eg one
1706 that cross a major release boundary or several minor releases, or when
1707 several months have passed on the -current branch).
1709 Sometimes, obscure build problems are the result of environment
1710 poisoning. This can happen because the make utility reads its
1711 environment when searching for values for global variables. To run
1712 your build attempts in an "environmental clean room", prefix all make
1713 commands with 'env -i '. See the env(1) manual page for more details.
1715 When upgrading from one major version to another it is generally best
1716 to upgrade to the latest code in the currently installed branch first,
1717 then do an upgrade to the new branch. This is the best-tested upgrade
1718 path, and has the highest probability of being successful. Please try
1719 this approach before reporting problems with a major version upgrade.
1721 When upgrading a live system, having a root shell around before
1722 installing anything can help undo problems. Not having a root shell
1723 around can lead to problems if pam has changed too much from your
1724 starting point to allow continued authentication after the upgrade.
1726 This file should be read as a log of events. When a later event changes
1727 information of a prior event, the prior event should not be deleted.
1728 Instead, a pointer to the entry with the new information should be
1729 placed in the old entry. Readers of this file should also sanity check
1730 older entries before relying on them blindly. Authors of new entries
1731 should write them with this in mind.
1735 When upgrading the boot ZFS pool to a new version, always follow
1738 1.) recompile and reinstall the ZFS boot loader and boot block
1739 (this is part of "make buildworld" and "make installworld")
1741 2.) update the ZFS boot block on your boot drive
1743 The following example updates the ZFS boot block on the first
1744 partition (freebsd-boot) of a GPT partitioned drive ada0:
1745 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1747 Non-boot pools do not need these updates.
1751 If you are updating from a prior version of FreeBSD (even one just
1752 a few days old), you should follow this procedure. It is the most
1753 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1755 make kernel-toolchain
1756 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1757 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1759 To test a kernel once
1760 ---------------------
1761 If you just want to boot a kernel once (because you are not sure
1762 if it works, or if you want to boot a known bad kernel to provide
1763 debugging information) run
1764 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1765 nextboot -k testkernel
1767 To just build a kernel when you know that it won't mess you up
1768 --------------------------------------------------------------
1769 This assumes you are already running a CURRENT system. Replace
1770 ${arch} with the architecture of your machine (e.g. "i386",
1771 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1773 cd src/sys/${arch}/conf
1774 config KERNEL_NAME_HERE
1775 cd ../compile/KERNEL_NAME_HERE
1780 If this fails, go to the "To build a kernel" section.
1782 To rebuild everything and install it on the current system.
1783 -----------------------------------------------------------
1784 # Note: sometimes if you are running current you gotta do more than
1785 # is listed here if you are upgrading from a really old current.
1787 <make sure you have good level 0 dumps>
1789 make kernel KERNCONF=YOUR_KERNEL_HERE
1791 <reboot in single user> [3]
1798 To cross-install current onto a separate partition
1799 --------------------------------------------------
1800 # In this approach we use a separate partition to hold
1801 # current's root, 'usr', and 'var' directories. A partition
1802 # holding "/", "/usr" and "/var" should be about 2GB in
1805 <make sure you have good level 0 dumps>
1808 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1809 <maybe newfs current's root partition>
1810 <mount current's root partition on directory ${CURRENT_ROOT}>
1811 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1812 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1813 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1814 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1815 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1816 <reboot into current>
1817 <do a "native" rebuild/install as described in the previous section>
1818 <maybe install compatibility libraries from ports/misc/compat*>
1822 To upgrade in-place from stable to current
1823 ----------------------------------------------
1824 <make sure you have good level 0 dumps>
1826 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1828 <reboot in single user> [3]
1835 Make sure that you've read the UPDATING file to understand the
1836 tweaks to various things you need. At this point in the life
1837 cycle of current, things change often and you are on your own
1838 to cope. The defaults can also change, so please read ALL of
1839 the UPDATING entries.
1841 Also, if you are tracking -current, you must be subscribed to
1842 freebsd-current@freebsd.org. Make sure that before you update
1843 your sources that you have read and understood all the recent
1844 messages there. If in doubt, please track -stable which has
1845 much fewer pitfalls.
1847 [1] If you have third party modules, such as vmware, you
1848 should disable them at this point so they don't crash your
1851 [3] From the bootblocks, boot -s, and then do
1856 adjkerntz -i # if CMOS is wall time
1857 Also, when doing a major release upgrade, it is required that
1858 you boot into single user mode to do the installworld.
1860 [4] Note: This step is non-optional. Failure to do this step
1861 can result in a significant reduction in the functionality of the
1862 system. Attempting to do it by hand is not recommended and those
1863 that pursue this avenue should read this file carefully, as well
1864 as the archives of freebsd-current and freebsd-hackers mailing lists
1865 for potential gotchas. The -U option is also useful to consider.
1866 See mergemaster(8) for more information.
1868 [5] Usually this step is a noop. However, from time to time
1869 you may need to do this if you get unknown user in the following
1870 step. It never hurts to do it all the time. You may need to
1871 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1872 install) after the buildworld before this step if you last updated
1873 from current before 20130425 or from -stable before 20130430.
1875 [6] This only deletes old files and directories. Old libraries
1876 can be deleted by "make delete-old-libs", but you have to make
1877 sure that no program is using those libraries anymore.
1879 [8] The new kernel must be able to run existing binaries used by
1880 an installworld. When upgrading across major versions, the new
1881 kernel's configuration must include the correct COMPAT_FREEBSD<n>
1882 option for existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x
1883 binaries). Failure to do so may leave you with a system that is
1884 hard to boot to recover. A GENERIC kernel will include suitable
1885 compatibility options to run binaries from older branches.
1887 Make sure that you merge any new devices from GENERIC since the
1888 last time you updated your kernel config file.
1890 [9] When checking out sources, you must include the -P flag to have
1891 cvs prune empty directories.
1893 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1894 "?=" instead of the "=" assignment operator, so that buildworld can
1895 override the CPUTYPE if it needs to.
1897 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1898 not on the command line, or in /etc/make.conf. buildworld will
1899 warn if it is improperly defined.
1902 This file contains a list, in reverse chronological order, of major
1903 breakages in tracking -current. It is not guaranteed to be a complete
1904 list of such breakages, and only contains entries since September 23, 2011.
1905 If you need to see UPDATING entries from before that date, you will need
1906 to fetch an UPDATING file from an older FreeBSD release.
1908 Copyright information:
1910 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1912 Redistribution, publication, translation and use, with or without
1913 modification, in full or in part, in any form or format of this
1914 document are permitted without further permission from the author.
1916 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1917 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1918 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1919 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1920 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1921 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1922 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1923 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1924 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1925 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1926 POSSIBILITY OF SUCH DAMAGE.
1928 Contact Warner Losh if you have any questions about your use of