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/updating-src.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 20191023 p15 FreeBSD-EN-19:18.tzdata
21 Import tzdata 2019c. [EN-19:18.tzdata]
23 20190820 p14 FreeBSD-SA-19:22.mbuf
25 FreeBSD-SA-19:24.mqueuefs
27 Fix IPv6 remote denial of service. [SA-19:22.mbuf]
29 Fix kernel memory disclosure from /dev/midistat. [SA-19:23.midi]
31 Fix reference count overflow in mqueuefs. [SA-19:24.mqueuefs]
33 20190806 p13 FreeBSD-EN-19:15.libunwind
34 FreeBSD-SA-19:18.bzip2
35 FreeBSD-SA-19:19.mldv2
36 FreeBSD-SA-19:20.bsnmp
37 FreeBSD-SA-19:21.bhyve
39 Fix incorrect exception handling. [EN-19:15.libunwind]
41 Fix multiple vulnerabilities in bzip2. [SA-19:18.bzip2]
43 Fix ICMPv6 / MLDv2 out-of-bounds memory access. [SA-19:19.mldv2]
45 Fix insufficient message length validation in bsnmp library.
48 Fix insufficient validation of guest-supplied data (e1000 device).
51 20190724 p12 FreeBSD-EN-19:13.mds
52 FreeBSD-SA-19:12.telnet
54 FreeBSD-SA-19:14.freebsd32
55 FreeBSD-SA-19:15.mqueuefs
56 FreeBSD-SA-19:16.bhyve
59 Fix panic from Intel CPU vulnerability mitigation. [EN-19:13.mds]
61 Fix multiple telnet client vulnerabilities. [SA-19:12.telnet]
63 Fix pts write-after-free. [SA-19:13.pts]
65 Fix kernel memory disclosure in freebsd32_ioctl. [SA-19:14.freebsd32]
67 Fix reference count overflow in mqueuefs. [SA-19:15.mqueuefs]
69 Fix byhve out-of-bounds read in XHCI device. [SA-19:16.bhyve]
71 Fix file descriptor reference count leak. [SA-19:17.fd]
73 20190702 p11 FreeBSD-EN-19:12.tzdata
74 FreeBSD-SA-19:09.iconv
76 FreeBSD-SA-19:11.cd_ioctl
78 Import tzdata 2019b. [EN-19:12.tzdata]
80 Fix iconv buffer overflow. [SA-19:09.iconv]
82 Fix kernel stack disclosure in UFS/FFS. [SA-19:10.ufs]
84 Fix privilege escalation in cd(4) driver. [SA-19:11.cd_ioctl]
86 20190514 p10 FreeBSD-EN-19:08.tzdata
87 FreeBSD-EN-19:09.xinstall
94 Import tzdata 2019a. [EN-19:08.tzdata]
96 Fix install with partially matching relative paths. [EN-19:09.xinstall]
98 Fix multiple vulnerabilities in hostapd/wpa_supplicant. [SA-19:03.wpa]
100 Fix authenticated denial of service in ntpd. [SA-19:04.ntp]
102 Fix IPv6 fragment reassembly in pf. [SA-19:05.pf]
104 Fix ICMP/ICMP6 packet filter bypass in pf. [SA-19:06.pf]
106 Add mitigations for Microarchitectural Data Sampling. [SA-19:07.mds]
109 20190205 p9 FreeBSD-SA-19:01.syscall
111 amd64: clear callee-preserved registers on syscall exit
114 20190109 p8 FreeBSD-EN-19:03.sqlite
115 FreeBSD-EN-19:04.tzdata
116 FreeBSD-EN-19:05.kqueue
118 Update sqlite3-3.20.0 --> sqlite3-3.26.0 (3260000) [EN-19:03.sqlite]
120 Import tzdata 2018h, 2018i [EN-19:04.tzdata]
122 Avoid unsynchronized updates to kn_status. [EN-19:05.kqueue]
125 20181219 p7 FreeBSD-SA-18:15.bootpd
126 FreeBSD-EN-18:16.ptrace
130 bootpd: validate hardware type [SA-18:15.bootpd]
132 Only clear a pending thread event if one is pending. [EN-18:16.ptrace]
134 Update the free page count when blacklisting pages. [EN-18:17.vm]
136 Resolve a hang in ZFS during vnode reclamation [EN-18:18.zfs]
139 20181204 p6 FreeBSD-SA-18:14.bhyve
141 Fix insufficient bounds checking in bhyve(8) device model.
144 20181127 p5 FreeBSD-SA-18:13.nfs
145 FreeBSD-EN-18:13.icmp
146 FreeBSD-EN-18:14.tzdata
147 FreeBSD-EN-18:15.loader
149 Fix multiple vulnerabilities in NFS server code. [SA-18:13.nfs]
151 Fix ICMP buffer underwrite. [EN-18:13.icmp]
153 Timezone database information update. [EN-18:14.tzdata]
155 Fix deferred kernel loading breaks loader password. [EN-18:15.loader]
157 20180927 p4 FreeBSD-EN-18:09.ip
158 FreeBSD-EN-18:10.syscall
159 FreeBSD-EN-18:11.listen
162 Fix regression in IPv6 fragment reassembly. [EN-18:09.ip]
164 Fix NULL pointer dereference in freebsd4_getfsstat. [EN-18:10.syscall]
166 Fix DoS in listen syscall over IPv6 socket. [EN-18:11.listen]
168 Fix small kernel memory disclosures. [EN-18:12.mem]
170 20180912 p3 FreeBSD-SA-18:12.elf
171 FreeBSD-EN-18:08.lazyfpu
173 Fix improper elf header parsing. [SA-18:12.elf]
175 Fix regression in Lazy FPU remediation. [EN-18:08.lazyfpu]
177 20180814 p2 FreeBSD-SA-18:08.tcp [revised]
178 FreeBSD-SA-18:09.l1tf
180 FreeBSD-SA-18:11.hostapd
182 Revise manual pages. [SA-18:08.tcp]
184 Fix L1 Terminal Fault (L1TF) kernel information disclosure.
187 Fix resource exhaustion in IP fragment reassembly. [SA-18:10.ip]
189 Fix unauthenticated EAPOL-Key decryption vulnerability.
192 20180806 p1 FreeBSD-SA-18:08.tcp
194 Fix resource exhaustion in TCP reassembly.
200 The tz database (tzdb) has been updated to 2018e. This version more
201 correctly models time stamps in time zones with negative DST such as
202 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
203 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
204 time zone abbreviations and the tm_isdst flag.
207 The use of RSS hash from the network card aka flowid has been
208 disabled by default for lagg(4) as it's currently incompatible with
209 the lacp and loadbalance protocols.
211 This can be re-enabled by setting the following in loader.conf:
212 net.link.lagg.default_use_flowid="1"
215 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
216 6.0.0. Please see the 20141231 entry below for information about
217 prerequisites and upgrading, if you are not already using clang 3.5.0
221 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
222 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
223 to WITH/OUT_LOADER_GELI.
226 The geli password typed at boot is now hidden. To restore the previous
227 behavior, see geli(8) for configuration options.
229 The SW_WATCHDOG option is no longer necessary to enable the
230 hardclock-based software watchdog if no hardware watchdog is
231 configured. As before, SW_WATCHDOG will cause the software
232 watchdog to be enabled even if a hardware watchdog is configured.
235 lint(1) binaries and library are no longer built by default. To
236 enable building them, define WITH_LINT in src.conf. If you are using
237 a FreeBSD 12 or later system to build 11-stable, you may need to
238 install a lint(1) binary to use WITH_LINT.
241 When building multiple kernels using KERNCONF, non-existent KERNCONF
242 files will produce an error and buildkernel will fail. Previously
243 missing KERNCONF files silently failed giving no indication as to
244 why, only to subsequently discover during installkernel that the
245 desired kernel was never built in the first place.
248 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
249 Please see the 20141231 entry below for information about prerequisites
250 and upgrading, if you are not already using clang 3.5.0 or higher.
253 Since the switch to GPT disk labels, fsck for UFS/FFS has been
254 unable to automatically find alternate superblocks. As of r322806,
255 the information needed to find alternate superblocks has been
256 moved to the end of the area reserved for the boot block.
257 Filesystems created with a newfs of this vintage or later
258 will create the recovery information. If you have a filesystem
259 created prior to this change and wish to have a recovery block
260 created for your filesystem, you can do so by running fsck in
261 forground mode (i.e., do not use the -p or -y options). As it
262 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
263 to which you should answer yes.
266 arm64 builds now use the base system LLD 4.0.0 linker by default,
267 instead of requiring that the aarch64-binutils port or package be
268 installed. To continue using aarch64-binutils, set
269 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
272 The ctl.ko module no longer implements the iSCSI target frontend:
273 cfiscsi.ko does instead.
275 If building cfiscsi.ko as a kernel module, the module can be loaded
276 via one of the following methods:
277 - `cfiscsi_load="YES"` in loader.conf(5).
278 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
279 - ctladm(8)/ctld(8), when compiled with iSCSI support
280 (`WITH_ISCSI=yes` in src.conf(5))
282 Please see cfiscsi(4) for more details.
285 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
286 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
287 same source (previously, the dependency of mmcsd.ko on mmc.ko was
288 missing, but mmcsd.ko now will refuse to load if it is incompatible
292 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
293 use any explicitly assigned loopback address available in the jail
294 instead of using the first assigned address of the jail.
297 As of r316810 for ipfilter, keep frags is no longer assumed when
298 keep state is specified in a rule. r316810 aligns ipfilter with
299 documentation in man pages separating keep frags from keep state.
300 This allows keep state to specified without forcing keep frags
301 and allows keep frags to be specified independently of keep state.
302 To maintain previous behaviour, also specify keep frags with
303 keep state (as documented in ipf.conf.5).
306 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.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 The code that provides support for ZFS .zfs/ directory functionality
312 has been reimplemented. It's not possible now to create a snapshot
313 by mkdir under .zfs/snapshot/. That should be the only user visible
317 Many changes in the IPsec code have been merged from the FreeBSD-CURRENT
318 branch. The IPSEC_FILTERTUNNEL kernel option is removed in favour of
319 corresponding sysctl. The IPSEC_NAT_T kernel option is also removed,
320 and now NAT-T is supported by default. Security associations now use
321 the single namespace for SPI allocation, so if you use several manually
322 configured security associations with the same SPI, this configuration
326 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
327 Please see the 20141231 entry below for information about prerequisites
328 and upgrading, if you are not already using clang 3.5.0 or higher.
331 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
332 Please see the 20141231 entry below for information about prerequisites
333 and upgrading, if you are not already using clang 3.5.0 or higher.
336 The layout of the pmap structure has changed for powerpc to put the pmap
337 statistics at the front for all CPU variations. libkvm(3) and all tools
338 that link against it need to be recompiled.
341 isl(4) and cyapa(4) drivers now require a new driver,
342 chromebook_platform(4), to work properly on Chromebook-class hardware.
343 On other types of hardware the drivers may need to be configured using
344 device hints. Please see the corresponding manual pages for details.
347 Relocatable object files with the extension of .So have been renamed
348 to use an extension of .pico instead. The purpose of this change is
349 to avoid a name clash with shared libraries on case-insensitive file
350 systems. On those file systems, foo.So is the same file as foo.so.
353 The libc stub for the pipe(2) system call has been replaced with
354 a wrapper that calls the pipe2(2) system call and the pipe(2)
355 system call is now only implemented by the kernels that include
356 "options COMPAT_FREEBSD10" in their config file (this is the
357 default). Users should ensure that this option is enabled in
358 their kernel or upgrade userspace to r302092 before upgrading their
362 CAM will now strip leading spaces from SCSI disks' serial numbers.
363 This will effect users who create UFS filesystems on SCSI disks using
364 those disk's diskid device nodes. For example, if /etc/fstab
365 previously contained a line like
366 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
367 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
368 transforms like gmirror may also be affected. ZFS users should
372 The bitstring(3) API has been updated with new functionality and
373 improved performance. But it is binary-incompatible with the old API.
374 Objects built with the new headers may not be linked against objects
375 built with the old headers.
378 The brk and sbrk functions have been removed from libc on arm64.
379 Binutils from ports has been updated to not link to these
380 functions and should be updated to the latest version before
381 installing a new libc.
384 The armv6 port now defaults to hard float ABI. Limited support
385 for running both hardfloat and soft float on the same system
386 is available using the libraries installed with -DWITH_LIBSOFT.
387 This has only been tested as an upgrade path for installworld
388 and packages may fail or need manual intervention to run. New
389 packages will be needed.
391 To update an existing self-hosted armv6hf system, you must add
392 TARGET_ARCH=armv6 on the make command line for both the build
393 and the install steps.
396 Kernel modules compiled outside of a kernel build now default to
397 installing to /boot/modules instead of /boot/kernel. Many kernel
398 modules built this way (such as those in ports) already overrode
399 KMODDIR explicitly to install into /boot/modules. However,
400 manually building and installing a module from /sys/modules will
401 now install to /boot/modules instead of /boot/kernel.
404 The CAM I/O scheduler has been committed to the kernel. There should be
405 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
406 list of known rogues that claim support for this but actually corrupt
407 data is believed to be complete, be on the lookout for data
408 corruption. The known rogue list is believed to be complete:
410 o Crucial MX100, M550 drives with MU01 firmware.
411 o Micron M510 and M550 drives with MU01 firmware.
412 o Micron M500 prior to MU07 firmware
413 o Samsung 830, 840, and 850 all firmwares
414 o FCCT M500 all firmwares
416 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
417 with working NCQ TRIM. For Micron branded drives, see your sales rep for
418 updated firmware. Black listed drives will work correctly because these
419 drives work correctly so long as no NCQ TRIMs are sent to them. Given
420 this list is the same as found in Linux, it's believed there are no
421 other rogues in the market place. All other models from the above
424 To be safe, if you are at all concerned, you can quirk each of your
425 drives to prevent NCQ from being sent by setting:
426 kern.cam.ada.X.quirks="0x2"
427 in loader.conf. If the drive requires the 4k sector quirk, set the
431 The FAST_DEPEND build option has been removed and its functionality is
432 now the one true way. The old mkdep(1) style of 'make depend' has
433 been removed. See 20160311 for further details.
436 Resource range types have grown from unsigned long to uintmax_t. All
437 drivers, and anything using libdevinfo, need to be recompiled.
440 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
441 builds. It no longer runs mkdep(1) during 'make depend', and the
442 'make depend' stage can safely be skipped now as it is auto ran
443 when building 'make all' and will generate all SRCS and DPSRCS before
444 building anything else. Dependencies are gathered at compile time with
445 -MF flags kept in separate .depend files per object file. Users should
446 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
450 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
451 kernel modules. Therefore, if you load any kernel modules at boot time,
452 please install the boot loaders after you install the kernel, but before
456 make kernel KERNCONF=YOUR_KERNEL_HERE
457 make -C sys/boot install
458 <reboot in single user>
460 Then follow the usual steps, described in the General Notes section,
464 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
465 see the 20141231 entry below for information about prerequisites and
466 upgrading, if you are not already using clang 3.5.0 or higher.
469 The AIO subsystem is now a standard part of the kernel. The
470 VFS_AIO kernel option and aio.ko kernel module have been removed.
471 Due to stability concerns, asynchronous I/O requests are only
472 permitted on sockets and raw disks by default. To enable
473 asynchronous I/O requests on all file types, set the
474 vfs.aio.enable_unsafe sysctl to a non-zero value.
477 The ELF object manipulation tool objcopy is now provided by the
478 ELF Tool Chain project rather than by GNU binutils. It should be a
479 drop-in replacement, with the addition of arm64 support. The
480 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
481 to obtain the GNU version if necessary.
484 Building ZFS pools on top of zvols is prohibited by default. That
485 feature has never worked safely; it's always been prone to deadlocks.
486 Using a zvol as the backing store for a VM guest's virtual disk will
487 still work, even if the guest is using ZFS. Legacy behavior can be
488 restored by setting vfs.zfs.vol.recursive=1.
491 The NONE and HPN patches has been removed from OpenSSH. They are
492 still available in the security/openssh-portable port.
495 With the addition of ypldap(8), a new _ypldap user is now required
496 during installworld. "mergemaster -p" can be used to add the user
497 prior to installworld, as documented in the handbook.
500 The tftp loader (pxeboot) now uses the option root-path directive. As a
501 consequence it no longer looks for a pxeboot.4th file on the tftp
502 server. Instead it uses the regular /boot infrastructure as with the
506 The code to start recording plug and play data into the modules has
507 been committed. While the old tools will properly build a new kernel,
508 a number of warnings about "unknown metadata record 4" will be produced
509 for an older kldxref. To avoid such warnings, make sure to rebuild
510 the kernel toolchain (or world). Make sure that you have r292078 or
511 later when trying to build 292077 or later before rebuilding.
514 Debug data files are now built by default with 'make buildworld' and
515 installed with 'make installworld'. This facilitates debugging but
516 requires more disk space both during the build and for the installed
517 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
521 r291527 changed the internal interface between the nfsd.ko and
522 nfscommon.ko modules. As such, they must both be upgraded to-gether.
523 __FreeBSD_version has been bumped because of this.
526 Add support for unicode collation strings leads to a change of
527 order of files listed by ls(1) for example. To get back to the old
528 behaviour, set LC_COLLATE environment variable to "C".
530 Databases administrators will need to reindex their databases given
531 collation results will be different.
533 Due to a bug in install(1) it is recommended to remove the ancient
534 locales before running make installworld.
536 rm -rf /usr/share/locale/*
539 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
540 libcrypto.so.7 or libssl.so.7 must be recompiled.
543 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
544 Kernel modules isp_2400_multi and isp_2500_multi were removed and
545 should be replaced with isp_2400 and isp_2500 modules respectively.
548 The build previously allowed using 'make -n' to not recurse into
549 sub-directories while showing what commands would be executed, and
550 'make -n -n' to recursively show commands. Now 'make -n' will recurse
551 and 'make -N' will not.
554 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
555 and etcupdate will now use this file. A custom sendmail.cf is now
556 updated via this mechanism rather than via installworld. If you had
557 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
558 want to remove the exclusion or change it to "always install".
559 /etc/mail/sendmail.cf is now managed the same way regardless of
560 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
561 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
564 Compatibility shims for legacy ATA device names have been removed.
565 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
566 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
567 environment variables, /dev/ad* and /dev/ar* symbolic links.
570 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
571 Please see the 20141231 entry below for information about prerequisites
572 and upgrading, if you are not already using clang 3.5.0 or higher.
575 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
576 and renamed from .symbols to .debug. This reduces the size requirements
577 on the boot partition or file system and provides consistency with
578 userland debug files.
580 When using the supported kernel installation method the
581 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
582 as is done with /boot/kernel.
584 Developers wishing to maintain the historical behavior of installing
585 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
588 The wireless drivers had undergone changes that remove the 'parent
589 interface' from the ifconfig -l output. The rc.d network scripts
590 used to check presence of a parent interface in the list, so old
591 scripts would fail to start wireless networking. Thus, etcupdate(3)
592 or mergemaster(8) run is required after kernel update, to update your
593 rc.d scripts in /etc.
596 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
597 These configurations are now automatically interpreted as
598 'scrub fragment reassemble'.
601 Kernel-loadable modules for the random(4) device are back. To use
602 them, the kernel must have
605 options RANDOM_LOADABLE
607 kldload(8) can then be used to load random_fortuna.ko
608 or random_yarrow.ko. Please note that due to the indirect
609 function calls that the loadable modules need to provide,
610 the build-in variants will be slightly more efficient.
612 The random(4) kernel option RANDOM_DUMMY has been retired due to
613 unpopularity. It was not all that useful anyway.
616 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
617 Control over building the ELF Tool Chain tools is now provided by
618 the WITHOUT_TOOLCHAIN knob.
621 The polarity of Pulse Per Second (PPS) capture events with the
622 uart(4) driver has been corrected. Prior to this change the PPS
623 "assert" event corresponded to the trailing edge of a positive PPS
624 pulse and the "clear" event was the leading edge of the next pulse.
626 As the width of a PPS pulse in a typical GPS receiver is on the
627 order of 1 millisecond, most users will not notice any significant
628 difference with this change.
630 Anyone who has compensated for the historical polarity reversal by
631 configuring a negative offset equal to the pulse width will need to
632 remove that workaround.
635 The default group assigned to /dev/dri entries has been changed
636 from 'wheel' to 'video' with the id of '44'. If you want to have
637 access to the dri devices please add yourself to the video group
640 # pw groupmod video -m $USER
643 The menu.rc and loader.rc files will now be replaced during
644 upgrades. Please migrate local changes to menu.rc.local and
645 loader.rc.local instead.
648 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
649 strings and strip have been removed. The src.conf(5) knob
650 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
653 As ZFS requires more kernel stack pages than is the default on some
654 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
655 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
657 Please consider using 'options KSTACK_PAGES=X' where X is greater
658 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
661 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
662 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
663 default, i.e., they will not contain "::". For example, instead
664 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
665 to have a more specific match, such as different map entries for
666 IPv6:0:0 vs IPv6:0. This change requires that configuration
667 data (including maps, files, classes, custom ruleset, etc.) must
668 use the same format, so make certain such configuration data is
669 upgrading. As a very simple check search for patterns like
670 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
671 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
672 the cf option UseCompressedIPv6Addresses.
675 The default kernel entropy-processing algorithm is now
676 Fortuna, replacing Yarrow.
678 Assuming you have 'device random' in your kernel config
679 file, the configurations allow a kernel option to override
680 this default. You may choose *ONE* of:
682 options RANDOM_YARROW # Legacy /dev/random algorithm.
683 options RANDOM_DUMMY # Blocking-only driver.
685 If you have neither, you get Fortuna. For most people,
686 read no further, Fortuna will give a /dev/random that works
687 like it always used to, and the difference will be irrelevant.
689 If you remove 'device random', you get *NO* kernel-processed
690 entropy at all. This may be acceptable to folks building
691 embedded systems, but has complications. Carry on reading,
692 and it is assumed you know what you need.
694 *PLEASE* read random(4) and random(9) if you are in the
695 habit of tweaking kernel configs, and/or if you are a member
696 of the embedded community, wanting specific and not-usual
697 behaviour from your security subsystems.
699 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
700 random', you will NOT have a functioning /dev/random, and
701 many cryptographic features will not work, including SSH.
702 You may also find strange behaviour from the random(3) set
703 of library functions, in particular sranddev(3), srandomdev(3)
704 and arc4random(3). The reason for this is that the KERN_ARND
705 sysctl only returns entropy if it thinks it has some to
706 share, and with RANDOM_DUMMY or no 'device random' this
710 An additional fix for the issue described in the 20150614 sendmail
711 entry below has been been committed in revision 284717.
714 FreeBSD's old make (fmake) has been removed from the system. It is
715 available as the devel/fmake port or via pkg install fmake.
718 The fix for the issue described in the 20150614 sendmail entry
719 below has been been committed in revision 284436. The work
720 around described in that entry is no longer needed unless the
721 default setting is overridden by a confDH_PARAMETERS configuration
722 setting of '5' or pointing to a 512 bit DH parameter file.
725 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
726 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
727 and devel/kyua to version 0.20+ and adjust any calling code to work
728 with Kyuafile and kyua.
731 The import of openssl to address the FreeBSD-SA-15:10.openssl
732 security advisory includes a change which rejects handshakes
733 with DH parameters below 768 bits. sendmail releases prior
734 to 8.15.2 (not yet released), defaulted to a 512 bit
735 DH parameter setting for client connections. To work around
736 this interoperability, sendmail can be configured to use a
737 2048 bit DH parameter by:
739 1. Edit /etc/mail/`hostname`.mc
740 2. If a setting for confDH_PARAMETERS does not exist or
741 exists and is set to a string beginning with '5',
743 3. If a setting for confDH_PARAMETERS exists and is set to
744 a file path, create a new file with:
745 openssl dhparam -out /path/to/file 2048
746 4. Rebuild the .cf file:
747 cd /etc/mail/; make; make install
749 cd /etc/mail/; make restart
751 A sendmail patch is coming, at which time this file will be
755 Generation of legacy formatted entries have been disabled by default
756 in pwd_mkdb(8), as all base system consumers of the legacy formatted
757 entries were converted to use the new format by default when the new,
758 machine independent format have been added and supported since FreeBSD
761 Please see the pwd_mkdb(8) manual page for further details.
764 Clang and llvm have been upgraded to 3.6.1 release. Please see the
765 20141231 entry below for information about prerequisites and upgrading,
766 if you are not already using 3.5.0 or higher.
769 TI platform code switched to using vendor DTS files and this update
770 may break existing systems running on Beaglebone, Beaglebone Black,
773 - dtb files should be regenerated/reinstalled. Filenames are the
774 same but content is different now
775 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
776 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
777 addressing scheme is now pin 25 on /dev/gpioc3.
778 - Pandaboard: /etc/ttys should be updated, serial console device is
779 now /dev/ttyu2, not /dev/ttyu0
782 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
783 If you need the GNU extension from groff soelim(1), install groff
784 from package: pkg install groff, or via ports: textproc/groff.
787 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
788 defined in symlink(7); previously symlinks were silently ignored.
791 The const qualifier has been removed from iconv(3) to comply with
792 POSIX. The ports tree is aware of this from r384038 onwards.
795 Libraries specified by LIBADD in Makefiles must have a corresponding
796 DPADD_<lib> variable to ensure correct dependencies. This is now
797 enforced in src.libnames.mk.
800 From legacy ata(4) driver was removed support for SATA controllers
801 supported by more functional drivers ahci(4), siis(4) and mvs(4).
802 Kernel modules ataahci and ataadaptec were removed completely,
803 replaced by ahci and mvs modules respectively.
806 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
807 the 20141231 entry below for information about prerequisites and
808 upgrading, if you are not already using 3.5.0 or higher.
811 The 32-bit PowerPC kernel has been changed to a position-independent
812 executable. This can only be booted with a version of loader(8)
813 newer than January 31, 2015, so make sure to update both world and
814 kernel before rebooting.
817 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
818 but before r278950, the RNG was not seeded properly. Immediately
819 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
820 ssh keys or openssl keys) that were generated w/ a kernel from that
821 range. This does not affect programs that directly used /dev/random
822 or /dev/urandom. All userland uses of arc4random(3) are affected.
825 The autofs(4) ABI was changed in order to restore binary compatibility
826 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
830 The powerpc64 kernel has been changed to a position-independent
831 executable. This can only be booted with a new version of loader(8),
832 so make sure to update both world and kernel before rebooting.
835 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
836 only release, no new features have been added. Please see the 20141231
837 entry below for information about prerequisites and upgrading, if you
838 are not already using 3.5.0.
841 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
842 taken from the ELF Tool Chain project rather than GNU binutils. They
843 should be drop-in replacements, with the addition of arm64 support.
844 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
845 binutils tools, if necessary. See 20150805 for updated information.
848 The default Unbound configuration now enables remote control
849 using a local socket. Users who have already enabled the
850 local_unbound service should regenerate their configuration
851 by running "service local_unbound setup" as root.
854 The GNU texinfo and GNU info pages have been removed.
855 To be able to view GNU info pages please install texinfo from ports.
858 Clang, llvm and lldb have been upgraded to 3.5.0 release.
860 As of this release, a prerequisite for building clang, llvm and lldb is
861 a C++11 capable compiler and C++11 standard library. This means that to
862 be able to successfully build the cross-tools stage of buildworld, with
863 clang as the bootstrap compiler, your system compiler or cross compiler
864 should either be clang 3.3 or later, or gcc 4.8 or later, and your
865 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
868 On any standard FreeBSD 10.x or 11.x installation, where clang and
869 libc++ are on by default (that is, on x86 or arm), this should work out
872 On 9.x installations where clang is enabled by default, e.g. on x86 and
873 powerpc, libc++ will not be enabled by default, so libc++ should be
874 built (with clang) and installed first. If both clang and libc++ are
875 missing, build clang first, then use it to build libc++.
877 On 8.x and earlier installations, upgrade to 9.x first, and then follow
878 the instructions for 9.x above.
880 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
881 default, and do not build clang.
883 Many embedded systems are resource constrained, and will not be able to
884 build clang in a reasonable time, or in some cases at all. In those
885 cases, cross building bootable systems on amd64 is a workaround.
887 This new version of clang introduces a number of new warnings, of which
888 the following are most likely to appear:
892 This warns in two cases, for both C and C++:
893 * When the code is trying to take the absolute value of an unsigned
894 quantity, which is effectively a no-op, and almost never what was
895 intended. The code should be fixed, if at all possible. If you are
896 sure that the unsigned quantity can be safely cast to signed, without
897 loss of information or undefined behavior, you can add an explicit
898 cast, or disable the warning.
900 * When the code is trying to take an absolute value, but the called
901 abs() variant is for the wrong type, which can lead to truncation.
902 If you want to disable the warning instead of fixing the code, please
903 make sure that truncation will not occur, or it might lead to unwanted
906 -Wtautological-undefined-compare and
907 -Wundefined-bool-conversion
909 These warn when C++ code is trying to compare 'this' against NULL, while
910 'this' should never be NULL in well-defined C++ code. However, there is
911 some legacy (pre C++11) code out there, which actively abuses this
912 feature, which was less strictly defined in previous C++ versions.
914 Squid and openjdk do this, for example. The warning can be turned off
915 for C++98 and earlier, but compiling the code in C++11 mode might result
916 in unexpected behavior; for example, the parts of the program that are
917 unreachable could be optimized away.
920 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
921 kernel sources have been removed. The .h files remain, since some
922 utilities include them. This will need to be fixed later.
923 If "mount -t oldnfs ..." is attempted, it will fail.
924 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
925 the utilities will report errors.
928 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
929 directories to top level SUBDIR variable when their parent
930 directory is included in LOCAL_DIRS. Users with build systems with
931 such hierarchies and without SUBDIR entries in the parent
932 directory Makefiles should add them or add the directories to
936 faith(4) and faithd(8) have been removed from the base system. Faith
937 has been obsolete for a very long time.
940 vt(4), the new console driver, is enabled by default. It brings
941 support for Unicode and double-width characters, as well as
942 support for UEFI and integration with the KMS kernel video
945 You may need to update your console settings in /etc/rc.conf,
946 most probably the keymap. During boot, /etc/rc.d/syscons will
947 indicate what you need to do.
949 vt(4) still has issues and lacks some features compared to
950 syscons(4). See the wiki for up-to-date information:
951 https://wiki.freebsd.org/Newcons
953 If you want to keep using syscons(4), you can do so by adding
954 the following line to /boot/loader.conf:
958 pjdfstest has been integrated into kyua as an opt-in test suite.
959 Please see share/doc/pjdfstest/README for more details on how to
963 gperf has been removed from the base system for architectures
964 that use clang. Ports that require gperf will obtain it from the
968 pjdfstest has been moved from tools/regression/pjdfstest to
972 At svn r271982, The default linux compat kernel ABI has been adjusted
973 to 2.6.18 in support of the linux-c6 compat ports infrastructure
974 update. If you wish to continue using the linux-f10 compat ports,
975 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
976 encouraged to update their linux-compat packages to linux-c6 during
977 their next update cycle.
980 The ofwfb driver, used to provide a graphics console on PowerPC when
981 using vt(4), no longer allows mmap() of all physical memory. This
982 will prevent Xorg on PowerPC with some ATI graphics cards from
983 initializing properly unless x11-servers/xorg-server is updated to
987 The xdev targets have been converted to using TARGET and
988 TARGET_ARCH instead of XDEV and XDEV_ARCH.
991 The default unbound configuration has been modified to address
992 issues with reverse lookups on networks that use private
993 address ranges. If you use the local_unbound service, run
994 "service local_unbound setup" as root to regenerate your
995 configuration, then "service local_unbound reload" to load the
999 The GNU texinfo and GNU info pages are not built and installed
1000 anymore, WITH_INFO knob has been added to allow to built and install
1002 UPDATE: see 20150102 entry on texinfo's removal
1005 The GNU readline library is now an INTERNALLIB - that is, it is
1006 statically linked into consumers (GDB and variants) in the base
1007 system, and the shared library is no longer installed. The
1008 devel/readline port is available for third party software that
1012 The Itanium architecture (ia64) has been removed from the list of
1013 known architectures. This is the first step in the removal of the
1017 Commit r268115 has added NFSv4.1 server support, merged from
1018 projects/nfsv4.1-server. Since this includes changes to the
1019 internal interfaces between the NFS related modules, a full
1020 build of the kernel and modules will be necessary.
1021 __FreeBSD_version has been bumped.
1024 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1025 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1026 which differs from the behaviour controlled by this knob.)
1029 Maximal length of the serial number in CTL was increased from 16 to
1030 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1031 and ctld, need to be rebuilt to work with a new kernel.
1034 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1035 1 respectively to match the upstream numbers. They were out of
1036 sync because, when they were originally added to FreeBSD, the
1037 upstream versions were not respected. These libraries are private
1038 and not yet built by default, so renumbering them should be a
1039 non-issue. However, unclean source trees will yield broken test
1040 programs once the operator executes "make delete-old-libs" after a
1041 "make installworld".
1043 Additionally, the atf-sh binary was made private by moving it into
1044 /usr/libexec/. Already-built shell test programs will keep the
1045 path to the old binary so they will break after "make delete-old"
1048 If you are using WITH_TESTS=yes (not the default), wipe the object
1049 tree and rebuild from scratch to prevent spurious test failures.
1050 This is only needed once: the misnumbered libraries and misplaced
1051 binaries have been added to OptionalObsoleteFiles.inc so they will
1052 be removed during a clean upgrade.
1055 Clang and llvm have been upgraded to 3.4.1 release.
1058 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1059 be removed to avoid issues in the future (and has been added to
1063 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1064 past, it affected all builds that used the bsd.*.mk files. The old
1065 behavior was a bug, but people may have relied upon it. To get this
1066 behavior back, you can .include /etc/src.conf from /etc/make.conf
1067 (which is still global and isn't changed). This also changes the
1068 behavior of incremental builds inside the tree of individual
1069 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1070 Although this has survived make universe and some upgrade scenarios,
1071 other upgrade scenarios may have broken. At least one form of
1072 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1073 as well... In cases where MAKESYSPATH isn't working with this
1074 setting, you'll need to set it to the full path to your tree.
1076 One side effect of all this cleaning up is that bsd.compiler.mk
1077 is no longer implicitly included by bsd.own.mk. If you wish to
1078 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1082 The lindev device has been removed since /dev/full has been made a
1083 standard device. __FreeBSD_version has been bumped.
1086 The knob WITHOUT_VI was added to the base system, which controls
1087 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1088 in order to reorder files share/termcap and didn't build ex(1) as a
1089 build tool, so building/installing with WITH_VI is highly advised for
1090 build hosts for older releases.
1092 This issue has been fixed in stable/9 and stable/10 in r277022 and
1093 r276991, respectively.
1096 The YES_HESIOD knob has been removed. It has been obsolete for
1097 a decade. Please move to using WITH_HESIOD instead or your builds
1098 will silently lack HESIOD.
1101 The uart(4) driver has been changed with respect to its handling
1102 of the low-level console. Previously the uart(4) driver prevented
1103 any process from changing the baudrate or the CLOCAL and HUPCL
1104 control flags. By removing the restrictions, operators can make
1105 changes to the serial console port without having to reboot.
1106 However, when getty(8) is started on the serial device that is
1107 associated with the low-level console, a misconfigured terminal
1108 line in /etc/ttys will now have a real impact.
1109 Before upgrading the kernel, make sure that /etc/ttys has the
1110 serial console device configured as 3wire without baudrate to
1111 preserve the previous behaviour. E.g:
1112 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1115 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1116 to improve performance. To re-enable it, if needed, run rpcbind
1117 with command line option -W.
1120 Switched back to the GPL dtc compiler due to updates in the upstream
1121 dts files not being supported by the BSDL dtc compiler. You will need
1122 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1123 may result while building dtb files during a kernel build if you fail
1124 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1127 Clang and llvm have been upgraded to 3.4 release.
1130 The nve(4) driver has been removed. Please use the nfe(4) driver
1131 for NVIDIA nForce MCP Ethernet adapters instead.
1134 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1135 This could cause certain C++ applications using shared libraries built
1136 against the previous version of libc++ to crash. The incompatibility
1137 has now been fixed, but any C++ applications or shared libraries built
1138 between r261283 and r261801 should be recompiled.
1141 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1142 capability mode support. Please note that enabling the feature in
1143 kernel is still highly recommended.
1146 OpenSSH is now built with sandbox support, and will use sandbox as
1147 the default privilege separation method. This requires Capsicum
1148 capability mode support in kernel.
1151 The libelf and libdwarf libraries have been updated to newer
1152 versions from upstream. Shared library version numbers for
1153 these two libraries were bumped. Any ports or binaries
1154 requiring these two libraries should be recompiled.
1155 __FreeBSD_version is bumped to 1100006.
1158 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1159 instead of providing an explicit one, this would prevent such
1160 Makefile from providing its own Kyuafile in the future during
1161 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1162 intervention is needed to clean an objdir if you use NO_CLEAN:
1163 # find /usr/obj -name Kyuafile | xargs rm -f
1166 The behavior of gss_pseudo_random() for the krb5 mechanism
1167 has changed, for applications requesting a longer random string
1168 than produced by the underlying enctype's pseudo-random() function.
1169 In particular, the random string produced from a session key of
1170 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1171 be different at the 17th octet and later, after this change.
1172 The counter used in the PRF+ construction is now encoded as a
1173 big-endian integer in accordance with RFC 4402.
1174 __FreeBSD_version is bumped to 1100004.
1177 The WITHOUT_ATF build knob has been removed and its functionality
1178 has been subsumed into the more generic WITHOUT_TESTS. If you were
1179 using the former to disable the build of the ATF libraries, you
1180 should change your settings to use the latter.
1183 The default version of mtree is nmtree which is obtained from
1184 NetBSD. The output is generally the same, but may vary
1185 slightly. If you found you need identical output adding
1186 "-F freebsd9" to the command line should do the trick. For the
1187 time being, the old mtree is available as fmtree.
1190 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1191 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1192 1.1.4_8 and verify bsdyml not linked in, before running "make
1194 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1196 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1199 The stable/10 branch has been created in subversion from head
1203 The rc.d/jail script has been updated to support jail(8)
1204 configuration file. The "jail_<jname>_*" rc.conf(5) variables
1205 for per-jail configuration are automatically converted to
1206 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
1207 This is transparently backward compatible. See below about some
1208 incompatibilities and rc.conf(5) manual page for more details.
1210 These variables are now deprecated in favor of jail(8) configuration
1211 file. One can use "rc.d/jail config <jname>" command to generate
1212 a jail(8) configuration file in /var/run/jail.<jname>.conf without
1213 running the jail(8) utility. The default pathname of the
1214 configuration file is /etc/jail.conf and can be specified by
1215 using $jail_conf or $jail_<jname>_conf variables.
1217 Please note that jail_devfs_ruleset accepts an integer at
1218 this moment. Please consider to rewrite the ruleset name
1222 BIND has been removed from the base system. If all you need
1223 is a local resolver, simply enable and start the local_unbound
1224 service instead. Otherwise, several versions of BIND are
1225 available in the ports tree. The dns/bind99 port is one example.
1227 With this change, nslookup(1) and dig(1) are no longer in the base
1228 system. Users should instead use host(1) and drill(1) which are
1229 in the base system. Alternatively, nslookup and dig can
1230 be obtained by installing the dns/bind-tools port.
1233 With the addition of unbound(8), a new unbound user is now
1234 required during installworld. "mergemaster -p" can be used to
1235 add the user prior to installworld, as documented in the handbook.
1238 OpenSSH is now built with DNSSEC support, and will by default
1239 silently trust signed SSHFP records. This can be controlled with
1240 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1241 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1244 The GNU Compiler Collection and C++ standard library (libstdc++)
1245 are no longer built by default on platforms where clang is the system
1246 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1247 options in src.conf.
1250 The PROCDESC kernel option is now part of the GENERIC kernel
1251 configuration and is required for the rwhod(8) to work.
1252 If you are using custom kernel configuration, you should include
1256 The API and ABI related to the Capsicum framework was modified
1257 in backward incompatible way. The userland libraries and programs
1258 have to be recompiled to work with the new kernel. This includes the
1259 following libraries and programs, but the whole buildworld is
1260 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1261 kdump, procstat, rwho, rwhod, uniq.
1264 AES-NI intrinsic support has been added to gcc. The AES-NI module
1265 has been updated to use this support. A new gcc is required to build
1266 the aesni module on both i386 and amd64.
1269 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1270 Thus "device padlock_rng" and "device rdrand_rng" should be
1271 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1274 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1275 enables just the iconv* functionality and is now on by default.
1276 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1277 compatibility. Set WITHOUT_ICONV to build the old way.
1278 If you have been using WITH_ICONV before, you will very likely
1279 need to turn on WITH_LIBICONV_COMPAT.
1282 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1283 Illumos origin, including ZFS. If you have INVARIANTS in your
1284 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1286 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1287 locks if WITNESS option was set. Because that generated a lot of
1288 witness(9) reports and all of them were believed to be false
1289 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1290 can be used to achieve the previous behavior.
1293 Timer values in IPv6 data structures now use time_uptime instead
1294 of time_second. Although this is not a user-visible functional
1295 change, userland utilities which directly use them---ndp(8),
1296 rtadvd(8), and rtsold(8) in the base system---need to be updated
1297 to r253970 or later.
1300 find -delete can now delete the pathnames given as arguments,
1301 instead of only files found below them or if the pathname did
1302 not contain any slashes. Formerly, the following error message
1305 find: -delete: <path>: relative path potentially not safe
1307 Deleting the pathnames given as arguments can be prevented
1308 without error messages using -mindepth 1 or by changing
1309 directory and passing "." as argument to find. This works in the
1310 old as well as the new version of find.
1313 Behavior of devfs rules path matching has been changed.
1314 Pattern is now always matched against fully qualified devfs
1315 path and slash characters must be explicitly matched by
1316 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1317 subdirectories must be reviewed.
1320 The default ARM ABI has changed to the ARM EABI. The old ABI is
1321 incompatible with the ARM EABI and all programs and modules will
1322 need to be rebuilt to work with a new kernel.
1324 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1326 NOTE: Support for the old ABI will be removed in the future and
1327 users are advised to upgrade.
1330 pkg_install has been disconnected from the build if you really need it
1331 you should add WITH_PKGTOOLS in your src.conf(5).
1334 Most of network statistics structures were changed to be able
1335 keep 64-bits counters. Thus all tools, that work with networking
1336 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1339 Fix a bug that allowed a tracing process (e.g. gdb) to write
1340 to a memory-mapped file in the traced process's address space
1341 even if neither the traced process nor the tracing process had
1342 write access to that file.
1345 CVS has been removed from the base system. An exact copy
1346 of the code is available from the devel/cvs port.
1349 Some people report the following error after the switch to bmake:
1351 make: illegal option -- J
1352 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1354 *** [buildworld] Error code 2
1356 this likely due to an old instance of make in
1357 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1358 which src/Makefile will use that blindly, if it exists, so if
1359 you see the above error:
1361 rm -rf `make -V MAKEPATH`
1366 Use bmake by default.
1367 Whereas before one could choose to build with bmake via
1368 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1369 make. The goal is to remove these knobs for 10-RELEASE.
1371 It is worth noting that bmake (like gmake) treats the command
1372 line as the unit of failure, rather than statements within the
1373 command line. Thus '(cd some/where && dosomething)' is safer
1374 than 'cd some/where; dosomething'. The '()' allows consistent
1375 behavior in parallel build.
1378 Fix a bug that allows NFS clients to issue READDIR on files.
1381 The WITHOUT_IDEA option has been removed because
1382 the IDEA patent expired.
1385 The sysctl which controls TRIM support under ZFS has been renamed
1386 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1390 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1391 rather than creating it's own in the temporary directory in
1392 order allow access to bootstrapped versions of tools such as
1393 install and mtree. When upgrading from version of FreeBSD where
1394 the install command does not support -l, you will need to
1395 install a new mergemaster command if mergemaster -p is required.
1396 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1400 Legacy ATA stack, disabled and replaced by new CAM-based one since
1401 FreeBSD 9.0, completely removed from the sources. Kernel modules
1402 atadisk and atapi*, user-level tools atacontrol and burncd are
1403 removed. Kernel option `options ATA_CAM` is now permanently enabled
1407 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1408 and socketpair(2). Software, in particular Kerberos, may
1409 automatically detect and use these during building. The resulting
1410 binaries will not work on older kernels.
1413 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1414 information, see the respective 20130304 entry).
1417 Recent commits to callout(9) changed the size of struct callout,
1418 so the KBI is probably heavily disturbed. Also, some functions
1419 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1420 by macros. Every kernel module using it won't load, so rebuild
1423 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1424 but does not initialize by default (because of the new CTL_DISABLE
1425 option) to save memory. To re-enable it, remove the CTL_DISABLE
1426 option from the kernel config file or set kern.cam.ctl.disable=0
1427 in /boot/loader.conf.
1430 The ctl device has been disabled in GENERIC for i386 and amd64.
1431 This was done due to the extra memory being allocated at system
1432 initialisation time by the ctl driver which was only used if
1433 a CAM target device was created. This makes a FreeBSD system
1434 unusable on 128MB or less of RAM.
1437 A new compression method (lz4) has been merged to -HEAD. Please
1438 refer to zpool-features(7) for more information.
1440 Please refer to the "ZFS notes" section of this file for information
1441 on upgrading boot ZFS pools.
1444 A BSD-licensed patch(1) variant has been added and is installed
1445 as bsdpatch, being the GNU version the default patch.
1446 To inverse the logic and use the BSD-licensed one as default,
1447 while having the GNU version installed as gnupatch, rebuild
1448 and install world with the WITH_BSD_PATCH knob set.
1451 Due to the use of the new -l option to install(1) during build
1452 and install, you must take care not to directly set the INSTALL
1453 make variable in your /etc/make.conf, /etc/src.conf, or on the
1454 command line. If you wish to use the -C flag for all installs
1455 you may be able to add INSTALL+=-C to /etc/make.conf or
1459 The install(1) option -M has changed meaning and now takes an
1460 argument that is a file or path to append logs to. In the
1461 unlikely event that -M was the last option on the command line
1462 and the command line contained at least two files and a target
1463 directory the first file will have logs appended to it. The -M
1464 option served little practical purpose in the last decade so its
1465 use is expected to be extremely rare.
1468 After switching to Clang as the default compiler some users of ZFS
1469 on i386 systems started to experience stack overflow kernel panics.
1470 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1473 GEOM_LABEL now mangles label names read from file system metadata.
1474 Mangling affect labels containing spaces, non-printable characters,
1475 '%' or '"'. Device names in /etc/fstab and other places may need to
1479 By default, only the 10 most recent kernel dumps will be saved. To
1480 restore the previous behaviour (no limit on the number of kernel dumps
1481 stored in the dump directory) add the following line to /etc/rc.conf:
1486 With the addition of auditdistd(8), a new auditdistd user is now
1487 required during installworld. "mergemaster -p" can be used to
1488 add the user prior to installworld, as documented in the handbook.
1491 The sin6_scope_id member variable in struct sockaddr_in6 is now
1492 filled by the kernel before passing the structure to the userland via
1493 sysctl or routing socket. This means the KAME-specific embedded scope
1494 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1495 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1496 __FreeBSD_version is bumped to 1000025.
1499 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1500 This means that the world and kernel will be compiled with clang
1501 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1502 and /usr/bin/cpp. To disable this behavior and revert to building
1503 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1504 of current may need to bootstrap WITHOUT_CLANG first if the clang
1505 build fails (its compatibility window doesn't extend to the 9 stable
1509 The IPFIREWALL_FORWARD kernel option has been removed. Its
1510 functionality now turned on by default.
1513 The ZERO_COPY_SOCKET kernel option has been removed and
1514 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1515 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1516 mechanism which is not safe and may result in kernel crashes.
1517 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1518 driver supports disposeable external page sized mbuf storage.
1519 Proper replacements for both zero-copy mechanisms are under
1520 consideration and will eventually lead to complete removal
1521 of the two kernel options.
1524 The IPv4 network stack has been converted to network byte
1525 order. The following modules need to be recompiled together
1526 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1527 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1530 Support for non-MPSAFE filesystems was removed from VFS. The
1531 VFS_VERSION was bumped, all filesystem modules shall be
1535 All the non-MPSAFE filesystems have been disconnected from
1536 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1537 portalfs, smbfs, xfs.
1540 The interface cloning API and ABI has changed. The following
1541 modules need to be recompiled together with kernel:
1542 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1543 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1544 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1547 The sdhci driver was split in two parts: sdhci (generic SD Host
1548 Controller logic) and sdhci_pci (actual hardware driver).
1549 No kernel config modifications are required, but if you
1550 load sdhc as a module you must switch to sdhci_pci instead.
1553 Import the FUSE kernel and userland support into base system.
1556 The GNU sort(1) program has been removed since the BSD-licensed
1557 sort(1) has been the default for quite some time and no serious
1558 problems have been reported. The corresponding WITH_GNU_SORT
1562 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1563 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1567 The net80211(4) ABI has been changed to allow for improved driver
1568 PS-POLL and power-save support. All wireless drivers need to be
1569 recompiled to work with the new kernel.
1572 The random(4) support for the VIA hardware random number
1573 generator (`PADLOCK') is no longer enabled unconditionally.
1574 Add the padlock_rng device in the custom kernel config if
1575 needed. The GENERIC kernels on i386 and amd64 do include the
1576 device, so the change only affects the custom kernel
1580 The pf(4) packet filter ABI has been changed. pfctl(8) and
1581 snmp_pf module need to be recompiled to work with new kernel.
1584 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1585 to -HEAD. Pools that have empty_bpobj in active state can not be
1586 imported read-write with ZFS implementations that do not support
1587 this feature. For more information read the zpool-features(5)
1591 The sparc64 ZFS loader has been changed to no longer try to auto-
1592 detect ZFS providers based on diskN aliases but now requires these
1593 to be explicitly listed in the OFW boot-device environment variable.
1596 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1597 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1598 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1601 The following sysctls and tunables have been renamed for consistency
1602 with other variables:
1603 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1604 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1607 The sort utility has been replaced with BSD sort. For now, GNU sort
1608 is also available as "gnusort" or the default can be set back to
1609 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1610 installed as "bsdsort".
1613 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1614 Starting with this version the old system of ZFS pool versioning
1615 is superseded by "feature flags". This concept enables forward
1616 compatibility against certain future changes in functionality of ZFS
1617 pools. The first read-only compatible "feature flag" for ZFS pools
1618 is named "com.delphix:async_destroy". For more information
1619 read the new zpool-features(5) manual page.
1620 Please refer to the "ZFS notes" section of this file for information
1621 on upgrading boot ZFS pools.
1624 The malloc(3) implementation embedded in libc now uses sources imported
1625 as contrib/jemalloc. The most disruptive API change is to
1626 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1627 delete it prior to installworld, and optionally re-create it using the
1628 new format after rebooting. See malloc.conf(5) for details
1629 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1633 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1634 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1635 now spelled mips. This is to aid compatibility with third-party
1636 software that expects this naming scheme in uname(3). Little-endian
1637 settings are unchanged. If you are updating a big-endian mips64 machine
1638 from before this change, you may need to set MACHINE_ARCH=mips64 in
1639 your environment before the new build system will recognize your machine.
1642 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1646 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1647 nullfs(5) did not pass through all behaviours to the underlying layer,
1648 as a result if we bound to a socket on the lower layer we could connect
1649 only to the lower path; if we bound to the upper layer we could connect
1650 only to the upper path. The new behavior is one can connect to both the
1651 lower and the upper paths regardless what layer path one binds to.
1654 The getifaddrs upgrade path broken with 20111215 has been restored.
1655 If you have upgraded in between 20111215 and 20120209 you need to
1656 recompile libc again with your kernel. You still need to recompile
1657 world to be able to configure CARP but this restriction already
1658 comes from 20111215.
1661 The set_rcvar() function has been removed from /etc/rc.subr. All
1662 base and ports rc.d scripts have been updated, so if you have a
1663 port installed with a script in /usr/local/etc/rc.d you can either
1664 hand-edit the rcvar= line, or reinstall the port.
1666 An easy way to handle the mass-update of /etc/rc.d:
1667 rm /etc/rc.d/* && mergemaster -i
1670 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1671 on the current CPU and prevents other threads from running.
1672 This behavior can be reverted using the kern.stop_scheduler_on_panic
1674 The new behavior can be incompatible with kern.sync_on_panic.
1677 The carp(4) facility has been changed significantly. Configuration
1678 of the CARP protocol via ifconfig(8) has changed, as well as format
1679 of CARP events submitted to devd(8) has changed. See manual pages
1680 for more information. The arpbalance feature of carp(4) is currently
1681 not supported anymore.
1683 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1684 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1685 need to be recompiled.
1688 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1692 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1693 explicitely support non-MPSAFE filesystems.
1694 It is on by default for all supported platform at this present
1698 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1699 i386 and pc98 GENERIC kernel configuration files.
1702 sysinstall has been removed
1705 The stable/9 branch created in subversion. This corresponds to the
1706 RELENG_9 branch in CVS.
1712 Avoid using make -j when upgrading. While generally safe, there are
1713 sometimes problems using -j to upgrade. If your upgrade fails with
1714 -j, please try again without -j. From time to time in the past there
1715 have been problems using -j with buildworld and/or installworld. This
1716 is especially true when upgrading between "distant" versions (eg one
1717 that cross a major release boundary or several minor releases, or when
1718 several months have passed on the -current branch).
1720 Sometimes, obscure build problems are the result of environment
1721 poisoning. This can happen because the make utility reads its
1722 environment when searching for values for global variables. To run
1723 your build attempts in an "environmental clean room", prefix all make
1724 commands with 'env -i '. See the env(1) manual page for more details.
1726 When upgrading from one major version to another it is generally best
1727 to upgrade to the latest code in the currently installed branch first,
1728 then do an upgrade to the new branch. This is the best-tested upgrade
1729 path, and has the highest probability of being successful. Please try
1730 this approach before reporting problems with a major version upgrade.
1732 When upgrading a live system, having a root shell around before
1733 installing anything can help undo problems. Not having a root shell
1734 around can lead to problems if pam has changed too much from your
1735 starting point to allow continued authentication after the upgrade.
1737 This file should be read as a log of events. When a later event changes
1738 information of a prior event, the prior event should not be deleted.
1739 Instead, a pointer to the entry with the new information should be
1740 placed in the old entry. Readers of this file should also sanity check
1741 older entries before relying on them blindly. Authors of new entries
1742 should write them with this in mind.
1746 When upgrading the boot ZFS pool to a new version, always follow
1749 1.) recompile and reinstall the ZFS boot loader and boot block
1750 (this is part of "make buildworld" and "make installworld")
1752 2.) update the ZFS boot block on your boot drive
1754 The following example updates the ZFS boot block on the first
1755 partition (freebsd-boot) of a GPT partitioned drive ada0:
1756 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1758 Non-boot pools do not need these updates.
1762 If you are updating from a prior version of FreeBSD (even one just
1763 a few days old), you should follow this procedure. It is the most
1764 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1766 make kernel-toolchain
1767 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1768 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1770 To test a kernel once
1771 ---------------------
1772 If you just want to boot a kernel once (because you are not sure
1773 if it works, or if you want to boot a known bad kernel to provide
1774 debugging information) run
1775 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1776 nextboot -k testkernel
1778 To just build a kernel when you know that it won't mess you up
1779 --------------------------------------------------------------
1780 This assumes you are already running a CURRENT system. Replace
1781 ${arch} with the architecture of your machine (e.g. "i386",
1782 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1784 cd src/sys/${arch}/conf
1785 config KERNEL_NAME_HERE
1786 cd ../compile/KERNEL_NAME_HERE
1791 If this fails, go to the "To build a kernel" section.
1793 To rebuild everything and install it on the current system.
1794 -----------------------------------------------------------
1795 # Note: sometimes if you are running current you gotta do more than
1796 # is listed here if you are upgrading from a really old current.
1798 <make sure you have good level 0 dumps>
1800 make kernel KERNCONF=YOUR_KERNEL_HERE
1802 <reboot in single user> [3]
1809 To cross-install current onto a separate partition
1810 --------------------------------------------------
1811 # In this approach we use a separate partition to hold
1812 # current's root, 'usr', and 'var' directories. A partition
1813 # holding "/", "/usr" and "/var" should be about 2GB in
1816 <make sure you have good level 0 dumps>
1819 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1820 <maybe newfs current's root partition>
1821 <mount current's root partition on directory ${CURRENT_ROOT}>
1822 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1823 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1824 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1825 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1826 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1827 <reboot into current>
1828 <do a "native" rebuild/install as described in the previous section>
1829 <maybe install compatibility libraries from ports/misc/compat*>
1833 To upgrade in-place from stable to current
1834 ----------------------------------------------
1835 <make sure you have good level 0 dumps>
1837 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1839 <reboot in single user> [3]
1846 Make sure that you've read the UPDATING file to understand the
1847 tweaks to various things you need. At this point in the life
1848 cycle of current, things change often and you are on your own
1849 to cope. The defaults can also change, so please read ALL of
1850 the UPDATING entries.
1852 Also, if you are tracking -current, you must be subscribed to
1853 freebsd-current@freebsd.org. Make sure that before you update
1854 your sources that you have read and understood all the recent
1855 messages there. If in doubt, please track -stable which has
1856 much fewer pitfalls.
1858 [1] If you have third party modules, such as vmware, you
1859 should disable them at this point so they don't crash your
1862 [3] From the bootblocks, boot -s, and then do
1867 adjkerntz -i # if CMOS is wall time
1868 Also, when doing a major release upgrade, it is required that
1869 you boot into single user mode to do the installworld.
1871 [4] Note: This step is non-optional. Failure to do this step
1872 can result in a significant reduction in the functionality of the
1873 system. Attempting to do it by hand is not recommended and those
1874 that pursue this avenue should read this file carefully, as well
1875 as the archives of freebsd-current and freebsd-hackers mailing lists
1876 for potential gotchas. The -U option is also useful to consider.
1877 See mergemaster(8) for more information.
1879 [5] Usually this step is a noop. However, from time to time
1880 you may need to do this if you get unknown user in the following
1881 step. It never hurts to do it all the time. You may need to
1882 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1883 install) after the buildworld before this step if you last updated
1884 from current before 20130425 or from -stable before 20130430.
1886 [6] This only deletes old files and directories. Old libraries
1887 can be deleted by "make delete-old-libs", but you have to make
1888 sure that no program is using those libraries anymore.
1890 [8] In order to have a kernel that can run the 4.x binaries needed to
1891 do an installworld, you must include the COMPAT_FREEBSD4 option in
1892 your kernel. Failure to do so may leave you with a system that is
1893 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1894 required to run the 5.x binaries on more recent kernels. And so on
1895 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1897 Make sure that you merge any new devices from GENERIC since the
1898 last time you updated your kernel config file.
1900 [9] When checking out sources, you must include the -P flag to have
1901 cvs prune empty directories.
1903 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1904 "?=" instead of the "=" assignment operator, so that buildworld can
1905 override the CPUTYPE if it needs to.
1907 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1908 not on the command line, or in /etc/make.conf. buildworld will
1909 warn if it is improperly defined.
1912 This file contains a list, in reverse chronological order, of major
1913 breakages in tracking -current. It is not guaranteed to be a complete
1914 list of such breakages, and only contains entries since September 23, 2011.
1915 If you need to see UPDATING entries from before that date, you will need
1916 to fetch an UPDATING file from an older FreeBSD release.
1918 Copyright information:
1920 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1922 Redistribution, publication, translation and use, with or without
1923 modification, in full or in part, in any form or format of this
1924 document are permitted without further permission from the author.
1926 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1927 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1928 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1929 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1930 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1931 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1932 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1933 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1934 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1935 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1936 POSSIBILITY OF SUCH DAMAGE.
1938 Contact Warner Losh if you have any questions about your use of