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 20190820 p3 FreeBSD-EN-19:16.bhyve
23 FreeBSD-SA-19:24.mqueuefs
25 Bhyve instruction emulation improvements (opcode 03H and F7H).
28 Fix ipfw(8) jail keyword prior to jail startup. [EN-19:17.ipfw]
30 Fix IPv6 remote denial of service. [SA-19:22.mbuf]
32 Fix kernel memory disclosure from /dev/midistat. [SA-19:23.midi]
34 Fix reference count overflow in mqueuefs. [SA-19:24.mqueuefs]
36 20190806 p2 FreeBSD-SA-19:18.bzip2
37 FreeBSD-SA-19:19.mldv2
38 FreeBSD-SA-19:20.bsnmp
39 FreeBSD-SA-19:21.bhyve
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 p1 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]
76 20190702 FreeBSD-EN-19:12.tzdata
77 FreeBSD-SA-19:09.iconv
78 FreeBSD-SA-19:11.cd_ioctl
80 Import tzdata 2019b. [EN-19:12.tzdata]
82 Fix iconv buffer overflow. [SA-19:09.iconv]
84 Fix privilege escalation in cd(4) driver. [SA-19:11.cd_ioctl]
87 CARP now sets DSCP value CS7(Network Traffic) in the flowlabel field
88 of packets by default instead of only setting TOS_LOWDELAY in IPv4,
89 which was deprecated in 1998. Original behavior can be restored by
90 setting sysctl net.inet.carp.dscp=4.
93 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
94 8.0.0. Please see the 20141231 entry below for information about
95 prerequisites and upgrading, if you are not already using clang 3.5.0
99 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
100 compiled into your custom kernel, add 'device xz' statement to the
104 Co-existance for Forth and Lua interpreters in bootloaders has now been
105 merged to ease testing of lualoader. LOADER_DEFAULT_INTERP, documented
106 in build(7), may be used to control which interpreter flavor is used in
107 the default loader to be installed. For systems where Lua and Forth
108 coexist, this switch can also be made on a running system by creating a
109 link from /boot/loader{,.efi} to /boot/loader_${flavor}{,.efi} rather
110 than requiring a rebuild.
112 The default flavor in this branch will remain Forth. As indicated in
113 the 20190216 UPDATING entry, booting is a complex environment; it would
114 be prudent to assume that lualoader may not work for your setup and make
115 provisions for backup boot methods.
118 zfsloader's functionality has now been folded into loader.
119 zfsloader is no longer necesasary once you've updated your
120 boot blocks. For a transition period, we will install a
121 hardlink for zfsloader to loader to allow a smooth transition
122 until the boot blocks can be updated (hard link because old
123 zfs boot blocks don't understand symlinks).
126 Lualoader has been merged to facilitate testing on this branch. It's
127 purely opt-in for now by building WITH_LOADER_LUA and WITHOUT_FORTH in
128 /etc/src.conf, but co-existance will come shortly. Booting is a complex
129 environment and test coverage for Lua-enabled loaders has been thin, so
130 it would be prudent to assume it might not work and make provisions for
134 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
135 7.0.1. Please see the 20141231 entry below for information about
136 prerequisites and upgrading, if you are not already using clang 3.5.0
140 r342562 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
141 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
142 servers that have vfs.nfsd.nfs_privport set will only allow mounts
143 from clients using a reserved port#. Since both the FreeBSD and Linux
144 NFSv4 clients use reserved port#s by default, this should not affect
148 The '%I' format in the kern.corefile sysctl limits the number of
149 core files that a process can generate to the number stored in the
150 debug.ncores sysctl. The '%I' format is replaced by the single digit
151 index. Previously, if all indexes were taken the kernel would overwrite
152 only a core file with the highest index in a filename.
153 Currently the system will create a new core file if there is a free
154 index or if all slots are taken it will overwrite the oldest one.
157 WITH_OFED option now only enables the build for the OFED libraries
158 and some fundamental client utilities. OpenSM and rest of the
159 debugging tools are enabled by WITH_OFED_EXTRA build switch.
160 WITH_OFED is turned on by default on amd64.
163 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
164 6.0.1. Please see the 20141231 entry below for information about
165 prerequisites and upgrading, if you are not already using clang 3.5.0
169 The releng/11.2 branch has been created from stable/11@r334458.
172 The tz database (tzdb) has been updated to 2018e. This version more
173 correctly models time stamps in time zones with negative DST such as
174 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
175 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
176 time zone abbreviations and the tm_isdst flag.
179 The use of RSS hash from the network card aka flowid has been
180 disabled by default for lagg(4) as it's currently incompatible with
181 the lacp and loadbalance protocols.
183 This can be re-enabled by setting the following in loader.conf:
184 net.link.lagg.default_use_flowid="1"
187 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
188 6.0.0. Please see the 20141231 entry below for information about
189 prerequisites and upgrading, if you are not already using clang 3.5.0
193 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
194 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
195 to WITH/OUT_LOADER_GELI.
198 The geli password typed at boot is now hidden. To restore the previous
199 behavior, see geli(8) for configuration options.
201 The SW_WATCHDOG option is no longer necessary to enable the
202 hardclock-based software watchdog if no hardware watchdog is
203 configured. As before, SW_WATCHDOG will cause the software
204 watchdog to be enabled even if a hardware watchdog is configured.
207 lint(1) binaries and library are no longer built by default. To
208 enable building them, define WITH_LINT in src.conf. If you are using
209 a FreeBSD 12 or later system to build 11-stable, you may need to
210 install a lint(1) binary to use WITH_LINT.
213 When building multiple kernels using KERNCONF, non-existent KERNCONF
214 files will produce an error and buildkernel will fail. Previously
215 missing KERNCONF files silently failed giving no indication as to
216 why, only to subsequently discover during installkernel that the
217 desired kernel was never built in the first place.
220 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
221 Please see the 20141231 entry below for information about prerequisites
222 and upgrading, if you are not already using clang 3.5.0 or higher.
225 Since the switch to GPT disk labels, fsck for UFS/FFS has been
226 unable to automatically find alternate superblocks. As of r322806,
227 the information needed to find alternate superblocks has been
228 moved to the end of the area reserved for the boot block.
229 Filesystems created with a newfs of this vintage or later
230 will create the recovery information. If you have a filesystem
231 created prior to this change and wish to have a recovery block
232 created for your filesystem, you can do so by running fsck in
233 forground mode (i.e., do not use the -p or -y options). As it
234 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
235 to which you should answer yes.
238 The releng/11.1 branch has been created from stable/11@r320475.
241 arm64 builds now use the base system LLD 4.0.0 linker by default,
242 instead of requiring that the aarch64-binutils port or package be
243 installed. To continue using aarch64-binutils, set
244 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
247 The ctl.ko module no longer implements the iSCSI target frontend:
248 cfiscsi.ko does instead.
250 If building cfiscsi.ko as a kernel module, the module can be loaded
251 via one of the following methods:
252 - `cfiscsi_load="YES"` in loader.conf(5).
253 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
254 - ctladm(8)/ctld(8), when compiled with iSCSI support
255 (`WITH_ISCSI=yes` in src.conf(5))
257 Please see cfiscsi(4) for more details.
260 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
261 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
262 same source (previously, the dependency of mmcsd.ko on mmc.ko was
263 missing, but mmcsd.ko now will refuse to load if it is incompatible
267 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
268 use any explicitly assigned loopback address available in the jail
269 instead of using the first assigned address of the jail.
272 As of r316810 for ipfilter, keep frags is no longer assumed when
273 keep state is specified in a rule. r316810 aligns ipfilter with
274 documentation in man pages separating keep frags from keep state.
275 This allows keep state to specified without forcing keep frags
276 and allows keep frags to be specified independently of keep state.
277 To maintain previous behaviour, also specify keep frags with
278 keep state (as documented in ipf.conf.5).
281 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
282 Please see the 20141231 entry below for information about prerequisites
283 and upgrading, if you are not already using clang 3.5.0 or higher.
286 The code that provides support for ZFS .zfs/ directory functionality
287 has been reimplemented. It's not possible now to create a snapshot
288 by mkdir under .zfs/snapshot/. That should be the only user visible
292 Many changes in the IPsec code have been merged from the FreeBSD-CURRENT
293 branch. The IPSEC_FILTERTUNNEL kernel option is removed in favour of
294 corresponding sysctl. The IPSEC_NAT_T kernel option is also removed,
295 and now NAT-T is supported by default. Security associations now use
296 the single namespace for SPI allocation, so if you use several manually
297 configured security associations with the same SPI, this configuration
301 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
302 Please see the 20141231 entry below for information about prerequisites
303 and upgrading, if you are not already using clang 3.5.0 or higher.
306 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.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 layout of the pmap structure has changed for powerpc to put the pmap
312 statistics at the front for all CPU variations. libkvm(3) and all tools
313 that link against it need to be recompiled.
316 isl(4) and cyapa(4) drivers now require a new driver,
317 chromebook_platform(4), to work properly on Chromebook-class hardware.
318 On other types of hardware the drivers may need to be configured using
319 device hints. Please see the corresponding manual pages for details.
322 Relocatable object files with the extension of .So have been renamed
323 to use an extension of .pico instead. The purpose of this change is
324 to avoid a name clash with shared libraries on case-insensitive file
325 systems. On those file systems, foo.So is the same file as foo.so.
328 The releng/11.0 branch has been created from stable/11@r303970.
331 The stable/11 branch has been created from head@r302406.
334 The libc stub for the pipe(2) system call has been replaced with
335 a wrapper that calls the pipe2(2) system call and the pipe(2)
336 system call is now only implemented by the kernels that include
337 "options COMPAT_FREEBSD10" in their config file (this is the
338 default). Users should ensure that this option is enabled in
339 their kernel or upgrade userspace to r302092 before upgrading their
343 CAM will now strip leading spaces from SCSI disks' serial numbers.
344 This will effect users who create UFS filesystems on SCSI disks using
345 those disk's diskid device nodes. For example, if /etc/fstab
346 previously contained a line like
347 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
348 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
349 transforms like gmirror may also be affected. ZFS users should
353 The bitstring(3) API has been updated with new functionality and
354 improved performance. But it is binary-incompatible with the old API.
355 Objects built with the new headers may not be linked against objects
356 built with the old headers.
359 The brk and sbrk functions have been removed from libc on arm64.
360 Binutils from ports has been updated to not link to these
361 functions and should be updated to the latest version before
362 installing a new libc.
365 The armv6 port now defaults to hard float ABI. Limited support
366 for running both hardfloat and soft float on the same system
367 is available using the libraries installed with -DWITH_LIBSOFT.
368 This has only been tested as an upgrade path for installworld
369 and packages may fail or need manual intervention to run. New
370 packages will be needed.
372 To update an existing self-hosted armv6hf system, you must add
373 TARGET_ARCH=armv6 on the make command line for both the build
374 and the install steps.
377 Kernel modules compiled outside of a kernel build now default to
378 installing to /boot/modules instead of /boot/kernel. Many kernel
379 modules built this way (such as those in ports) already overrode
380 KMODDIR explicitly to install into /boot/modules. However,
381 manually building and installing a module from /sys/modules will
382 now install to /boot/modules instead of /boot/kernel.
385 The CAM I/O scheduler has been committed to the kernel. There should be
386 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
387 list of known rogues that claim support for this but actually corrupt
388 data is believed to be complete, be on the lookout for data
389 corruption. The known rogue list is believed to be complete:
391 o Crucial MX100, M550 drives with MU01 firmware.
392 o Micron M510 and M550 drives with MU01 firmware.
393 o Micron M500 prior to MU07 firmware
394 o Samsung 830, 840, and 850 all firmwares
395 o FCCT M500 all firmwares
397 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
398 with working NCQ TRIM. For Micron branded drives, see your sales rep for
399 updated firmware. Black listed drives will work correctly because these
400 drives work correctly so long as no NCQ TRIMs are sent to them. Given
401 this list is the same as found in Linux, it's believed there are no
402 other rogues in the market place. All other models from the above
405 To be safe, if you are at all concerned, you can quirk each of your
406 drives to prevent NCQ from being sent by setting:
407 kern.cam.ada.X.quirks="0x2"
408 in loader.conf. If the drive requires the 4k sector quirk, set the
412 The FAST_DEPEND build option has been removed and its functionality is
413 now the one true way. The old mkdep(1) style of 'make depend' has
414 been removed. See 20160311 for further details.
417 Resource range types have grown from unsigned long to uintmax_t. All
418 drivers, and anything using libdevinfo, need to be recompiled.
421 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
422 builds. It no longer runs mkdep(1) during 'make depend', and the
423 'make depend' stage can safely be skipped now as it is auto ran
424 when building 'make all' and will generate all SRCS and DPSRCS before
425 building anything else. Dependencies are gathered at compile time with
426 -MF flags kept in separate .depend files per object file. Users should
427 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
431 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
432 kernel modules. Therefore, if you load any kernel modules at boot time,
433 please install the boot loaders after you install the kernel, but before
437 make kernel KERNCONF=YOUR_KERNEL_HERE
438 make -C sys/boot install
439 <reboot in single user>
441 Then follow the usual steps, described in the General Notes section,
445 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
446 see the 20141231 entry below for information about prerequisites and
447 upgrading, if you are not already using clang 3.5.0 or higher.
450 The AIO subsystem is now a standard part of the kernel. The
451 VFS_AIO kernel option and aio.ko kernel module have been removed.
452 Due to stability concerns, asynchronous I/O requests are only
453 permitted on sockets and raw disks by default. To enable
454 asynchronous I/O requests on all file types, set the
455 vfs.aio.enable_unsafe sysctl to a non-zero value.
458 The ELF object manipulation tool objcopy is now provided by the
459 ELF Tool Chain project rather than by GNU binutils. It should be a
460 drop-in replacement, with the addition of arm64 support. The
461 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
462 to obtain the GNU version if necessary.
465 Building ZFS pools on top of zvols is prohibited by default. That
466 feature has never worked safely; it's always been prone to deadlocks.
467 Using a zvol as the backing store for a VM guest's virtual disk will
468 still work, even if the guest is using ZFS. Legacy behavior can be
469 restored by setting vfs.zfs.vol.recursive=1.
472 The NONE and HPN patches has been removed from OpenSSH. They are
473 still available in the security/openssh-portable port.
476 With the addition of ypldap(8), a new _ypldap user is now required
477 during installworld. "mergemaster -p" can be used to add the user
478 prior to installworld, as documented in the handbook.
481 The tftp loader (pxeboot) now uses the option root-path directive. As a
482 consequence it no longer looks for a pxeboot.4th file on the tftp
483 server. Instead it uses the regular /boot infrastructure as with the
487 The code to start recording plug and play data into the modules has
488 been committed. While the old tools will properly build a new kernel,
489 a number of warnings about "unknown metadata record 4" will be produced
490 for an older kldxref. To avoid such warnings, make sure to rebuild
491 the kernel toolchain (or world). Make sure that you have r292078 or
492 later when trying to build 292077 or later before rebuilding.
495 Debug data files are now built by default with 'make buildworld' and
496 installed with 'make installworld'. This facilitates debugging but
497 requires more disk space both during the build and for the installed
498 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
502 r291527 changed the internal interface between the nfsd.ko and
503 nfscommon.ko modules. As such, they must both be upgraded to-gether.
504 __FreeBSD_version has been bumped because of this.
507 Add support for unicode collation strings leads to a change of
508 order of files listed by ls(1) for example. To get back to the old
509 behaviour, set LC_COLLATE environment variable to "C".
511 Databases administrators will need to reindex their databases given
512 collation results will be different.
514 Due to a bug in install(1) it is recommended to remove the ancient
515 locales before running make installworld.
517 rm -rf /usr/share/locale/*
520 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
521 libcrypto.so.7 or libssl.so.7 must be recompiled.
524 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
525 Kernel modules isp_2400_multi and isp_2500_multi were removed and
526 should be replaced with isp_2400 and isp_2500 modules respectively.
529 The build previously allowed using 'make -n' to not recurse into
530 sub-directories while showing what commands would be executed, and
531 'make -n -n' to recursively show commands. Now 'make -n' will recurse
532 and 'make -N' will not.
535 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
536 and etcupdate will now use this file. A custom sendmail.cf is now
537 updated via this mechanism rather than via installworld. If you had
538 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
539 want to remove the exclusion or change it to "always install".
540 /etc/mail/sendmail.cf is now managed the same way regardless of
541 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
542 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
545 Compatibility shims for legacy ATA device names have been removed.
546 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
547 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
548 environment variables, /dev/ad* and /dev/ar* symbolic links.
551 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
552 Please see the 20141231 entry below for information about prerequisites
553 and upgrading, if you are not already using clang 3.5.0 or higher.
556 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
557 and renamed from .symbols to .debug. This reduces the size requirements
558 on the boot partition or file system and provides consistency with
559 userland debug files.
561 When using the supported kernel installation method the
562 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
563 as is done with /boot/kernel.
565 Developers wishing to maintain the historical behavior of installing
566 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
569 The wireless drivers had undergone changes that remove the 'parent
570 interface' from the ifconfig -l output. The rc.d network scripts
571 used to check presence of a parent interface in the list, so old
572 scripts would fail to start wireless networking. Thus, etcupdate(3)
573 or mergemaster(8) run is required after kernel update, to update your
574 rc.d scripts in /etc.
577 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
578 These configurations are now automatically interpreted as
579 'scrub fragment reassemble'.
582 Kernel-loadable modules for the random(4) device are back. To use
583 them, the kernel must have
586 options RANDOM_LOADABLE
588 kldload(8) can then be used to load random_fortuna.ko
589 or random_yarrow.ko. Please note that due to the indirect
590 function calls that the loadable modules need to provide,
591 the build-in variants will be slightly more efficient.
593 The random(4) kernel option RANDOM_DUMMY has been retired due to
594 unpopularity. It was not all that useful anyway.
597 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
598 Control over building the ELF Tool Chain tools is now provided by
599 the WITHOUT_TOOLCHAIN knob.
602 The polarity of Pulse Per Second (PPS) capture events with the
603 uart(4) driver has been corrected. Prior to this change the PPS
604 "assert" event corresponded to the trailing edge of a positive PPS
605 pulse and the "clear" event was the leading edge of the next pulse.
607 As the width of a PPS pulse in a typical GPS receiver is on the
608 order of 1 millisecond, most users will not notice any significant
609 difference with this change.
611 Anyone who has compensated for the historical polarity reversal by
612 configuring a negative offset equal to the pulse width will need to
613 remove that workaround.
616 The default group assigned to /dev/dri entries has been changed
617 from 'wheel' to 'video' with the id of '44'. If you want to have
618 access to the dri devices please add yourself to the video group
621 # pw groupmod video -m $USER
624 The menu.rc and loader.rc files will now be replaced during
625 upgrades. Please migrate local changes to menu.rc.local and
626 loader.rc.local instead.
629 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
630 strings and strip have been removed. The src.conf(5) knob
631 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
634 As ZFS requires more kernel stack pages than is the default on some
635 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
636 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
638 Please consider using 'options KSTACK_PAGES=X' where X is greater
639 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
642 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
643 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
644 default, i.e., they will not contain "::". For example, instead
645 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
646 to have a more specific match, such as different map entries for
647 IPv6:0:0 vs IPv6:0. This change requires that configuration
648 data (including maps, files, classes, custom ruleset, etc.) must
649 use the same format, so make certain such configuration data is
650 upgrading. As a very simple check search for patterns like
651 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
652 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
653 the cf option UseCompressedIPv6Addresses.
656 The default kernel entropy-processing algorithm is now
657 Fortuna, replacing Yarrow.
659 Assuming you have 'device random' in your kernel config
660 file, the configurations allow a kernel option to override
661 this default. You may choose *ONE* of:
663 options RANDOM_YARROW # Legacy /dev/random algorithm.
664 options RANDOM_DUMMY # Blocking-only driver.
666 If you have neither, you get Fortuna. For most people,
667 read no further, Fortuna will give a /dev/random that works
668 like it always used to, and the difference will be irrelevant.
670 If you remove 'device random', you get *NO* kernel-processed
671 entropy at all. This may be acceptable to folks building
672 embedded systems, but has complications. Carry on reading,
673 and it is assumed you know what you need.
675 *PLEASE* read random(4) and random(9) if you are in the
676 habit of tweaking kernel configs, and/or if you are a member
677 of the embedded community, wanting specific and not-usual
678 behaviour from your security subsystems.
680 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
681 random', you will NOT have a functioning /dev/random, and
682 many cryptographic features will not work, including SSH.
683 You may also find strange behaviour from the random(3) set
684 of library functions, in particular sranddev(3), srandomdev(3)
685 and arc4random(3). The reason for this is that the KERN_ARND
686 sysctl only returns entropy if it thinks it has some to
687 share, and with RANDOM_DUMMY or no 'device random' this
691 An additional fix for the issue described in the 20150614 sendmail
692 entry below has been been committed in revision 284717.
695 FreeBSD's old make (fmake) has been removed from the system. It is
696 available as the devel/fmake port or via pkg install fmake.
699 The fix for the issue described in the 20150614 sendmail entry
700 below has been been committed in revision 284436. The work
701 around described in that entry is no longer needed unless the
702 default setting is overridden by a confDH_PARAMETERS configuration
703 setting of '5' or pointing to a 512 bit DH parameter file.
706 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
707 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
708 and devel/kyua to version 0.20+ and adjust any calling code to work
709 with Kyuafile and kyua.
712 The import of openssl to address the FreeBSD-SA-15:10.openssl
713 security advisory includes a change which rejects handshakes
714 with DH parameters below 768 bits. sendmail releases prior
715 to 8.15.2 (not yet released), defaulted to a 512 bit
716 DH parameter setting for client connections. To work around
717 this interoperability, sendmail can be configured to use a
718 2048 bit DH parameter by:
720 1. Edit /etc/mail/`hostname`.mc
721 2. If a setting for confDH_PARAMETERS does not exist or
722 exists and is set to a string beginning with '5',
724 3. If a setting for confDH_PARAMETERS exists and is set to
725 a file path, create a new file with:
726 openssl dhparam -out /path/to/file 2048
727 4. Rebuild the .cf file:
728 cd /etc/mail/; make; make install
730 cd /etc/mail/; make restart
732 A sendmail patch is coming, at which time this file will be
736 Generation of legacy formatted entries have been disabled by default
737 in pwd_mkdb(8), as all base system consumers of the legacy formatted
738 entries were converted to use the new format by default when the new,
739 machine independent format have been added and supported since FreeBSD
742 Please see the pwd_mkdb(8) manual page for further details.
745 Clang and llvm have been upgraded to 3.6.1 release. Please see the
746 20141231 entry below for information about prerequisites and upgrading,
747 if you are not already using 3.5.0 or higher.
750 TI platform code switched to using vendor DTS files and this update
751 may break existing systems running on Beaglebone, Beaglebone Black,
754 - dtb files should be regenerated/reinstalled. Filenames are the
755 same but content is different now
756 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
757 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
758 addressing scheme is now pin 25 on /dev/gpioc3.
759 - Pandaboard: /etc/ttys should be updated, serial console device is
760 now /dev/ttyu2, not /dev/ttyu0
763 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
764 If you need the GNU extension from groff soelim(1), install groff
765 from package: pkg install groff, or via ports: textproc/groff.
768 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
769 defined in symlink(7); previously symlinks were silently ignored.
772 The const qualifier has been removed from iconv(3) to comply with
773 POSIX. The ports tree is aware of this from r384038 onwards.
776 Libraries specified by LIBADD in Makefiles must have a corresponding
777 DPADD_<lib> variable to ensure correct dependencies. This is now
778 enforced in src.libnames.mk.
781 From legacy ata(4) driver was removed support for SATA controllers
782 supported by more functional drivers ahci(4), siis(4) and mvs(4).
783 Kernel modules ataahci and ataadaptec were removed completely,
784 replaced by ahci and mvs modules respectively.
787 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
788 the 20141231 entry below for information about prerequisites and
789 upgrading, if you are not already using 3.5.0 or higher.
792 The 32-bit PowerPC kernel has been changed to a position-independent
793 executable. This can only be booted with a version of loader(8)
794 newer than January 31, 2015, so make sure to update both world and
795 kernel before rebooting.
798 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
799 but before r278950, the RNG was not seeded properly. Immediately
800 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
801 ssh keys or openssl keys) that were generated w/ a kernel from that
802 range. This does not affect programs that directly used /dev/random
803 or /dev/urandom. All userland uses of arc4random(3) are affected.
806 The autofs(4) ABI was changed in order to restore binary compatibility
807 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
811 The powerpc64 kernel has been changed to a position-independent
812 executable. This can only be booted with a new version of loader(8),
813 so make sure to update both world and kernel before rebooting.
816 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
817 only release, no new features have been added. Please see the 20141231
818 entry below for information about prerequisites and upgrading, if you
819 are not already using 3.5.0.
822 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
823 taken from the ELF Tool Chain project rather than GNU binutils. They
824 should be drop-in replacements, with the addition of arm64 support.
825 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
826 binutils tools, if necessary. See 20150805 for updated information.
829 The default Unbound configuration now enables remote control
830 using a local socket. Users who have already enabled the
831 local_unbound service should regenerate their configuration
832 by running "service local_unbound setup" as root.
835 The GNU texinfo and GNU info pages have been removed.
836 To be able to view GNU info pages please install texinfo from ports.
839 Clang, llvm and lldb have been upgraded to 3.5.0 release.
841 As of this release, a prerequisite for building clang, llvm and lldb is
842 a C++11 capable compiler and C++11 standard library. This means that to
843 be able to successfully build the cross-tools stage of buildworld, with
844 clang as the bootstrap compiler, your system compiler or cross compiler
845 should either be clang 3.3 or later, or gcc 4.8 or later, and your
846 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
849 On any standard FreeBSD 10.x or 11.x installation, where clang and
850 libc++ are on by default (that is, on x86 or arm), this should work out
853 On 9.x installations where clang is enabled by default, e.g. on x86 and
854 powerpc, libc++ will not be enabled by default, so libc++ should be
855 built (with clang) and installed first. If both clang and libc++ are
856 missing, build clang first, then use it to build libc++.
858 On 8.x and earlier installations, upgrade to 9.x first, and then follow
859 the instructions for 9.x above.
861 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
862 default, and do not build clang.
864 Many embedded systems are resource constrained, and will not be able to
865 build clang in a reasonable time, or in some cases at all. In those
866 cases, cross building bootable systems on amd64 is a workaround.
868 This new version of clang introduces a number of new warnings, of which
869 the following are most likely to appear:
873 This warns in two cases, for both C and C++:
874 * When the code is trying to take the absolute value of an unsigned
875 quantity, which is effectively a no-op, and almost never what was
876 intended. The code should be fixed, if at all possible. If you are
877 sure that the unsigned quantity can be safely cast to signed, without
878 loss of information or undefined behavior, you can add an explicit
879 cast, or disable the warning.
881 * When the code is trying to take an absolute value, but the called
882 abs() variant is for the wrong type, which can lead to truncation.
883 If you want to disable the warning instead of fixing the code, please
884 make sure that truncation will not occur, or it might lead to unwanted
887 -Wtautological-undefined-compare and
888 -Wundefined-bool-conversion
890 These warn when C++ code is trying to compare 'this' against NULL, while
891 'this' should never be NULL in well-defined C++ code. However, there is
892 some legacy (pre C++11) code out there, which actively abuses this
893 feature, which was less strictly defined in previous C++ versions.
895 Squid and openjdk do this, for example. The warning can be turned off
896 for C++98 and earlier, but compiling the code in C++11 mode might result
897 in unexpected behavior; for example, the parts of the program that are
898 unreachable could be optimized away.
901 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
902 kernel sources have been removed. The .h files remain, since some
903 utilities include them. This will need to be fixed later.
904 If "mount -t oldnfs ..." is attempted, it will fail.
905 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
906 the utilities will report errors.
909 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
910 directories to top level SUBDIR variable when their parent
911 directory is included in LOCAL_DIRS. Users with build systems with
912 such hierarchies and without SUBDIR entries in the parent
913 directory Makefiles should add them or add the directories to
917 faith(4) and faithd(8) have been removed from the base system. Faith
918 has been obsolete for a very long time.
921 vt(4), the new console driver, is enabled by default. It brings
922 support for Unicode and double-width characters, as well as
923 support for UEFI and integration with the KMS kernel video
926 You may need to update your console settings in /etc/rc.conf,
927 most probably the keymap. During boot, /etc/rc.d/syscons will
928 indicate what you need to do.
930 vt(4) still has issues and lacks some features compared to
931 syscons(4). See the wiki for up-to-date information:
932 https://wiki.freebsd.org/Newcons
934 If you want to keep using syscons(4), you can do so by adding
935 the following line to /boot/loader.conf:
939 pjdfstest has been integrated into kyua as an opt-in test suite.
940 Please see share/doc/pjdfstest/README for more details on how to
944 gperf has been removed from the base system for architectures
945 that use clang. Ports that require gperf will obtain it from the
949 pjdfstest has been moved from tools/regression/pjdfstest to
953 At svn r271982, The default linux compat kernel ABI has been adjusted
954 to 2.6.18 in support of the linux-c6 compat ports infrastructure
955 update. If you wish to continue using the linux-f10 compat ports,
956 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
957 encouraged to update their linux-compat packages to linux-c6 during
958 their next update cycle.
961 The ofwfb driver, used to provide a graphics console on PowerPC when
962 using vt(4), no longer allows mmap() of all physical memory. This
963 will prevent Xorg on PowerPC with some ATI graphics cards from
964 initializing properly unless x11-servers/xorg-server is updated to
968 The xdev targets have been converted to using TARGET and
969 TARGET_ARCH instead of XDEV and XDEV_ARCH.
972 The default unbound configuration has been modified to address
973 issues with reverse lookups on networks that use private
974 address ranges. If you use the local_unbound service, run
975 "service local_unbound setup" as root to regenerate your
976 configuration, then "service local_unbound reload" to load the
980 The GNU texinfo and GNU info pages are not built and installed
981 anymore, WITH_INFO knob has been added to allow to built and install
983 UPDATE: see 20150102 entry on texinfo's removal
986 The GNU readline library is now an INTERNALLIB - that is, it is
987 statically linked into consumers (GDB and variants) in the base
988 system, and the shared library is no longer installed. The
989 devel/readline port is available for third party software that
993 The Itanium architecture (ia64) has been removed from the list of
994 known architectures. This is the first step in the removal of the
998 Commit r268115 has added NFSv4.1 server support, merged from
999 projects/nfsv4.1-server. Since this includes changes to the
1000 internal interfaces between the NFS related modules, a full
1001 build of the kernel and modules will be necessary.
1002 __FreeBSD_version has been bumped.
1005 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1006 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1007 which differs from the behaviour controlled by this knob.)
1010 Maximal length of the serial number in CTL was increased from 16 to
1011 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1012 and ctld, need to be rebuilt to work with a new kernel.
1015 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1016 1 respectively to match the upstream numbers. They were out of
1017 sync because, when they were originally added to FreeBSD, the
1018 upstream versions were not respected. These libraries are private
1019 and not yet built by default, so renumbering them should be a
1020 non-issue. However, unclean source trees will yield broken test
1021 programs once the operator executes "make delete-old-libs" after a
1022 "make installworld".
1024 Additionally, the atf-sh binary was made private by moving it into
1025 /usr/libexec/. Already-built shell test programs will keep the
1026 path to the old binary so they will break after "make delete-old"
1029 If you are using WITH_TESTS=yes (not the default), wipe the object
1030 tree and rebuild from scratch to prevent spurious test failures.
1031 This is only needed once: the misnumbered libraries and misplaced
1032 binaries have been added to OptionalObsoleteFiles.inc so they will
1033 be removed during a clean upgrade.
1036 Clang and llvm have been upgraded to 3.4.1 release.
1039 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1040 be removed to avoid issues in the future (and has been added to
1044 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1045 past, it affected all builds that used the bsd.*.mk files. The old
1046 behavior was a bug, but people may have relied upon it. To get this
1047 behavior back, you can .include /etc/src.conf from /etc/make.conf
1048 (which is still global and isn't changed). This also changes the
1049 behavior of incremental builds inside the tree of individual
1050 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1051 Although this has survived make universe and some upgrade scenarios,
1052 other upgrade scenarios may have broken. At least one form of
1053 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1054 as well... In cases where MAKESYSPATH isn't working with this
1055 setting, you'll need to set it to the full path to your tree.
1057 One side effect of all this cleaning up is that bsd.compiler.mk
1058 is no longer implicitly included by bsd.own.mk. If you wish to
1059 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1063 The lindev device has been removed since /dev/full has been made a
1064 standard device. __FreeBSD_version has been bumped.
1067 The knob WITHOUT_VI was added to the base system, which controls
1068 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1069 in order to reorder files share/termcap and didn't build ex(1) as a
1070 build tool, so building/installing with WITH_VI is highly advised for
1071 build hosts for older releases.
1073 This issue has been fixed in stable/9 and stable/10 in r277022 and
1074 r276991, respectively.
1077 The YES_HESIOD knob has been removed. It has been obsolete for
1078 a decade. Please move to using WITH_HESIOD instead or your builds
1079 will silently lack HESIOD.
1082 The uart(4) driver has been changed with respect to its handling
1083 of the low-level console. Previously the uart(4) driver prevented
1084 any process from changing the baudrate or the CLOCAL and HUPCL
1085 control flags. By removing the restrictions, operators can make
1086 changes to the serial console port without having to reboot.
1087 However, when getty(8) is started on the serial device that is
1088 associated with the low-level console, a misconfigured terminal
1089 line in /etc/ttys will now have a real impact.
1090 Before upgrading the kernel, make sure that /etc/ttys has the
1091 serial console device configured as 3wire without baudrate to
1092 preserve the previous behaviour. E.g:
1093 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1096 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1097 to improve performance. To re-enable it, if needed, run rpcbind
1098 with command line option -W.
1101 Switched back to the GPL dtc compiler due to updates in the upstream
1102 dts files not being supported by the BSDL dtc compiler. You will need
1103 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1104 may result while building dtb files during a kernel build if you fail
1105 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1108 Clang and llvm have been upgraded to 3.4 release.
1111 The nve(4) driver has been removed. Please use the nfe(4) driver
1112 for NVIDIA nForce MCP Ethernet adapters instead.
1115 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1116 This could cause certain C++ applications using shared libraries built
1117 against the previous version of libc++ to crash. The incompatibility
1118 has now been fixed, but any C++ applications or shared libraries built
1119 between r261283 and r261801 should be recompiled.
1122 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1123 capability mode support. Please note that enabling the feature in
1124 kernel is still highly recommended.
1127 OpenSSH is now built with sandbox support, and will use sandbox as
1128 the default privilege separation method. This requires Capsicum
1129 capability mode support in kernel.
1132 The libelf and libdwarf libraries have been updated to newer
1133 versions from upstream. Shared library version numbers for
1134 these two libraries were bumped. Any ports or binaries
1135 requiring these two libraries should be recompiled.
1136 __FreeBSD_version is bumped to 1100006.
1139 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1140 instead of providing an explicit one, this would prevent such
1141 Makefile from providing its own Kyuafile in the future during
1142 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1143 intervention is needed to clean an objdir if you use NO_CLEAN:
1144 # find /usr/obj -name Kyuafile | xargs rm -f
1147 The behavior of gss_pseudo_random() for the krb5 mechanism
1148 has changed, for applications requesting a longer random string
1149 than produced by the underlying enctype's pseudo-random() function.
1150 In particular, the random string produced from a session key of
1151 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1152 be different at the 17th octet and later, after this change.
1153 The counter used in the PRF+ construction is now encoded as a
1154 big-endian integer in accordance with RFC 4402.
1155 __FreeBSD_version is bumped to 1100004.
1158 The WITHOUT_ATF build knob has been removed and its functionality
1159 has been subsumed into the more generic WITHOUT_TESTS. If you were
1160 using the former to disable the build of the ATF libraries, you
1161 should change your settings to use the latter.
1164 The default version of mtree is nmtree which is obtained from
1165 NetBSD. The output is generally the same, but may vary
1166 slightly. If you found you need identical output adding
1167 "-F freebsd9" to the command line should do the trick. For the
1168 time being, the old mtree is available as fmtree.
1171 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1172 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1173 1.1.4_8 and verify bsdyml not linked in, before running "make
1175 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1177 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1180 The stable/10 branch has been created in subversion from head
1184 The rc.d/jail script has been updated to support jail(8)
1185 configuration file. The "jail_<jname>_*" rc.conf(5) variables
1186 for per-jail configuration are automatically converted to
1187 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
1188 This is transparently backward compatible. See below about some
1189 incompatibilities and rc.conf(5) manual page for more details.
1191 These variables are now deprecated in favor of jail(8) configuration
1192 file. One can use "rc.d/jail config <jname>" command to generate
1193 a jail(8) configuration file in /var/run/jail.<jname>.conf without
1194 running the jail(8) utility. The default pathname of the
1195 configuration file is /etc/jail.conf and can be specified by
1196 using $jail_conf or $jail_<jname>_conf variables.
1198 Please note that jail_devfs_ruleset accepts an integer at
1199 this moment. Please consider to rewrite the ruleset name
1203 BIND has been removed from the base system. If all you need
1204 is a local resolver, simply enable and start the local_unbound
1205 service instead. Otherwise, several versions of BIND are
1206 available in the ports tree. The dns/bind99 port is one example.
1208 With this change, nslookup(1) and dig(1) are no longer in the base
1209 system. Users should instead use host(1) and drill(1) which are
1210 in the base system. Alternatively, nslookup and dig can
1211 be obtained by installing the dns/bind-tools port.
1214 With the addition of unbound(8), a new unbound user is now
1215 required during installworld. "mergemaster -p" can be used to
1216 add the user prior to installworld, as documented in the handbook.
1219 OpenSSH is now built with DNSSEC support, and will by default
1220 silently trust signed SSHFP records. This can be controlled with
1221 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1222 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1225 The GNU Compiler Collection and C++ standard library (libstdc++)
1226 are no longer built by default on platforms where clang is the system
1227 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1228 options in src.conf.
1231 The PROCDESC kernel option is now part of the GENERIC kernel
1232 configuration and is required for the rwhod(8) to work.
1233 If you are using custom kernel configuration, you should include
1237 The API and ABI related to the Capsicum framework was modified
1238 in backward incompatible way. The userland libraries and programs
1239 have to be recompiled to work with the new kernel. This includes the
1240 following libraries and programs, but the whole buildworld is
1241 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1242 kdump, procstat, rwho, rwhod, uniq.
1245 AES-NI intrinsic support has been added to gcc. The AES-NI module
1246 has been updated to use this support. A new gcc is required to build
1247 the aesni module on both i386 and amd64.
1250 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1251 Thus "device padlock_rng" and "device rdrand_rng" should be
1252 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1255 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1256 enables just the iconv* functionality and is now on by default.
1257 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1258 compatibility. Set WITHOUT_ICONV to build the old way.
1259 If you have been using WITH_ICONV before, you will very likely
1260 need to turn on WITH_LIBICONV_COMPAT.
1263 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1264 Illumos origin, including ZFS. If you have INVARIANTS in your
1265 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1267 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1268 locks if WITNESS option was set. Because that generated a lot of
1269 witness(9) reports and all of them were believed to be false
1270 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1271 can be used to achieve the previous behavior.
1274 Timer values in IPv6 data structures now use time_uptime instead
1275 of time_second. Although this is not a user-visible functional
1276 change, userland utilities which directly use them---ndp(8),
1277 rtadvd(8), and rtsold(8) in the base system---need to be updated
1278 to r253970 or later.
1281 find -delete can now delete the pathnames given as arguments,
1282 instead of only files found below them or if the pathname did
1283 not contain any slashes. Formerly, the following error message
1286 find: -delete: <path>: relative path potentially not safe
1288 Deleting the pathnames given as arguments can be prevented
1289 without error messages using -mindepth 1 or by changing
1290 directory and passing "." as argument to find. This works in the
1291 old as well as the new version of find.
1294 Behavior of devfs rules path matching has been changed.
1295 Pattern is now always matched against fully qualified devfs
1296 path and slash characters must be explicitly matched by
1297 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1298 subdirectories must be reviewed.
1301 The default ARM ABI has changed to the ARM EABI. The old ABI is
1302 incompatible with the ARM EABI and all programs and modules will
1303 need to be rebuilt to work with a new kernel.
1305 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1307 NOTE: Support for the old ABI will be removed in the future and
1308 users are advised to upgrade.
1311 pkg_install has been disconnected from the build if you really need it
1312 you should add WITH_PKGTOOLS in your src.conf(5).
1315 Most of network statistics structures were changed to be able
1316 keep 64-bits counters. Thus all tools, that work with networking
1317 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1320 Fix a bug that allowed a tracing process (e.g. gdb) to write
1321 to a memory-mapped file in the traced process's address space
1322 even if neither the traced process nor the tracing process had
1323 write access to that file.
1326 CVS has been removed from the base system. An exact copy
1327 of the code is available from the devel/cvs port.
1330 Some people report the following error after the switch to bmake:
1332 make: illegal option -- J
1333 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1335 *** [buildworld] Error code 2
1337 this likely due to an old instance of make in
1338 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1339 which src/Makefile will use that blindly, if it exists, so if
1340 you see the above error:
1342 rm -rf `make -V MAKEPATH`
1347 Use bmake by default.
1348 Whereas before one could choose to build with bmake via
1349 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1350 make. The goal is to remove these knobs for 10-RELEASE.
1352 It is worth noting that bmake (like gmake) treats the command
1353 line as the unit of failure, rather than statements within the
1354 command line. Thus '(cd some/where && dosomething)' is safer
1355 than 'cd some/where; dosomething'. The '()' allows consistent
1356 behavior in parallel build.
1359 Fix a bug that allows NFS clients to issue READDIR on files.
1362 The WITHOUT_IDEA option has been removed because
1363 the IDEA patent expired.
1366 The sysctl which controls TRIM support under ZFS has been renamed
1367 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1371 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1372 rather than creating it's own in the temporary directory in
1373 order allow access to bootstrapped versions of tools such as
1374 install and mtree. When upgrading from version of FreeBSD where
1375 the install command does not support -l, you will need to
1376 install a new mergemaster command if mergemaster -p is required.
1377 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1381 Legacy ATA stack, disabled and replaced by new CAM-based one since
1382 FreeBSD 9.0, completely removed from the sources. Kernel modules
1383 atadisk and atapi*, user-level tools atacontrol and burncd are
1384 removed. Kernel option `options ATA_CAM` is now permanently enabled
1388 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1389 and socketpair(2). Software, in particular Kerberos, may
1390 automatically detect and use these during building. The resulting
1391 binaries will not work on older kernels.
1394 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1395 information, see the respective 20130304 entry).
1398 Recent commits to callout(9) changed the size of struct callout,
1399 so the KBI is probably heavily disturbed. Also, some functions
1400 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1401 by macros. Every kernel module using it won't load, so rebuild
1404 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1405 but does not initialize by default (because of the new CTL_DISABLE
1406 option) to save memory. To re-enable it, remove the CTL_DISABLE
1407 option from the kernel config file or set kern.cam.ctl.disable=0
1408 in /boot/loader.conf.
1411 The ctl device has been disabled in GENERIC for i386 and amd64.
1412 This was done due to the extra memory being allocated at system
1413 initialisation time by the ctl driver which was only used if
1414 a CAM target device was created. This makes a FreeBSD system
1415 unusable on 128MB or less of RAM.
1418 A new compression method (lz4) has been merged to -HEAD. Please
1419 refer to zpool-features(7) for more information.
1421 Please refer to the "ZFS notes" section of this file for information
1422 on upgrading boot ZFS pools.
1425 A BSD-licensed patch(1) variant has been added and is installed
1426 as bsdpatch, being the GNU version the default patch.
1427 To inverse the logic and use the BSD-licensed one as default,
1428 while having the GNU version installed as gnupatch, rebuild
1429 and install world with the WITH_BSD_PATCH knob set.
1432 Due to the use of the new -l option to install(1) during build
1433 and install, you must take care not to directly set the INSTALL
1434 make variable in your /etc/make.conf, /etc/src.conf, or on the
1435 command line. If you wish to use the -C flag for all installs
1436 you may be able to add INSTALL+=-C to /etc/make.conf or
1440 The install(1) option -M has changed meaning and now takes an
1441 argument that is a file or path to append logs to. In the
1442 unlikely event that -M was the last option on the command line
1443 and the command line contained at least two files and a target
1444 directory the first file will have logs appended to it. The -M
1445 option served little practical purpose in the last decade so its
1446 use is expected to be extremely rare.
1449 After switching to Clang as the default compiler some users of ZFS
1450 on i386 systems started to experience stack overflow kernel panics.
1451 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1454 GEOM_LABEL now mangles label names read from file system metadata.
1455 Mangling affect labels containing spaces, non-printable characters,
1456 '%' or '"'. Device names in /etc/fstab and other places may need to
1460 By default, only the 10 most recent kernel dumps will be saved. To
1461 restore the previous behaviour (no limit on the number of kernel dumps
1462 stored in the dump directory) add the following line to /etc/rc.conf:
1467 With the addition of auditdistd(8), a new auditdistd user is now
1468 required during installworld. "mergemaster -p" can be used to
1469 add the user prior to installworld, as documented in the handbook.
1472 The sin6_scope_id member variable in struct sockaddr_in6 is now
1473 filled by the kernel before passing the structure to the userland via
1474 sysctl or routing socket. This means the KAME-specific embedded scope
1475 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1476 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1477 __FreeBSD_version is bumped to 1000025.
1480 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1481 This means that the world and kernel will be compiled with clang
1482 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1483 and /usr/bin/cpp. To disable this behavior and revert to building
1484 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1485 of current may need to bootstrap WITHOUT_CLANG first if the clang
1486 build fails (its compatibility window doesn't extend to the 9 stable
1490 The IPFIREWALL_FORWARD kernel option has been removed. Its
1491 functionality now turned on by default.
1494 The ZERO_COPY_SOCKET kernel option has been removed and
1495 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1496 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1497 mechanism which is not safe and may result in kernel crashes.
1498 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1499 driver supports disposeable external page sized mbuf storage.
1500 Proper replacements for both zero-copy mechanisms are under
1501 consideration and will eventually lead to complete removal
1502 of the two kernel options.
1505 The IPv4 network stack has been converted to network byte
1506 order. The following modules need to be recompiled together
1507 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1508 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1511 Support for non-MPSAFE filesystems was removed from VFS. The
1512 VFS_VERSION was bumped, all filesystem modules shall be
1516 All the non-MPSAFE filesystems have been disconnected from
1517 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1518 portalfs, smbfs, xfs.
1521 The interface cloning API and ABI has changed. The following
1522 modules need to be recompiled together with kernel:
1523 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1524 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1525 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1528 The sdhci driver was split in two parts: sdhci (generic SD Host
1529 Controller logic) and sdhci_pci (actual hardware driver).
1530 No kernel config modifications are required, but if you
1531 load sdhc as a module you must switch to sdhci_pci instead.
1534 Import the FUSE kernel and userland support into base system.
1537 The GNU sort(1) program has been removed since the BSD-licensed
1538 sort(1) has been the default for quite some time and no serious
1539 problems have been reported. The corresponding WITH_GNU_SORT
1543 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1544 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1548 The net80211(4) ABI has been changed to allow for improved driver
1549 PS-POLL and power-save support. All wireless drivers need to be
1550 recompiled to work with the new kernel.
1553 The random(4) support for the VIA hardware random number
1554 generator (`PADLOCK') is no longer enabled unconditionally.
1555 Add the padlock_rng device in the custom kernel config if
1556 needed. The GENERIC kernels on i386 and amd64 do include the
1557 device, so the change only affects the custom kernel
1561 The pf(4) packet filter ABI has been changed. pfctl(8) and
1562 snmp_pf module need to be recompiled to work with new kernel.
1565 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1566 to -HEAD. Pools that have empty_bpobj in active state can not be
1567 imported read-write with ZFS implementations that do not support
1568 this feature. For more information read the zpool-features(5)
1572 The sparc64 ZFS loader has been changed to no longer try to auto-
1573 detect ZFS providers based on diskN aliases but now requires these
1574 to be explicitly listed in the OFW boot-device environment variable.
1577 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1578 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1579 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1582 The following sysctls and tunables have been renamed for consistency
1583 with other variables:
1584 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1585 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1588 The sort utility has been replaced with BSD sort. For now, GNU sort
1589 is also available as "gnusort" or the default can be set back to
1590 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1591 installed as "bsdsort".
1594 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1595 Starting with this version the old system of ZFS pool versioning
1596 is superseded by "feature flags". This concept enables forward
1597 compatibility against certain future changes in functionality of ZFS
1598 pools. The first read-only compatible "feature flag" for ZFS pools
1599 is named "com.delphix:async_destroy". For more information
1600 read the new zpool-features(5) manual page.
1601 Please refer to the "ZFS notes" section of this file for information
1602 on upgrading boot ZFS pools.
1605 The malloc(3) implementation embedded in libc now uses sources imported
1606 as contrib/jemalloc. The most disruptive API change is to
1607 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1608 delete it prior to installworld, and optionally re-create it using the
1609 new format after rebooting. See malloc.conf(5) for details
1610 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1614 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1615 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1616 now spelled mips. This is to aid compatibility with third-party
1617 software that expects this naming scheme in uname(3). Little-endian
1618 settings are unchanged. If you are updating a big-endian mips64 machine
1619 from before this change, you may need to set MACHINE_ARCH=mips64 in
1620 your environment before the new build system will recognize your machine.
1623 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1627 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1628 nullfs(5) did not pass through all behaviours to the underlying layer,
1629 as a result if we bound to a socket on the lower layer we could connect
1630 only to the lower path; if we bound to the upper layer we could connect
1631 only to the upper path. The new behavior is one can connect to both the
1632 lower and the upper paths regardless what layer path one binds to.
1635 The getifaddrs upgrade path broken with 20111215 has been restored.
1636 If you have upgraded in between 20111215 and 20120209 you need to
1637 recompile libc again with your kernel. You still need to recompile
1638 world to be able to configure CARP but this restriction already
1639 comes from 20111215.
1642 The set_rcvar() function has been removed from /etc/rc.subr. All
1643 base and ports rc.d scripts have been updated, so if you have a
1644 port installed with a script in /usr/local/etc/rc.d you can either
1645 hand-edit the rcvar= line, or reinstall the port.
1647 An easy way to handle the mass-update of /etc/rc.d:
1648 rm /etc/rc.d/* && mergemaster -i
1651 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1652 on the current CPU and prevents other threads from running.
1653 This behavior can be reverted using the kern.stop_scheduler_on_panic
1655 The new behavior can be incompatible with kern.sync_on_panic.
1658 The carp(4) facility has been changed significantly. Configuration
1659 of the CARP protocol via ifconfig(8) has changed, as well as format
1660 of CARP events submitted to devd(8) has changed. See manual pages
1661 for more information. The arpbalance feature of carp(4) is currently
1662 not supported anymore.
1664 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1665 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1666 need to be recompiled.
1669 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1673 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1674 explicitely support non-MPSAFE filesystems.
1675 It is on by default for all supported platform at this present
1679 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1680 i386 and pc98 GENERIC kernel configuration files.
1683 sysinstall has been removed
1686 The stable/9 branch created in subversion. This corresponds to the
1687 RELENG_9 branch in CVS.
1693 Avoid using make -j when upgrading. While generally safe, there are
1694 sometimes problems using -j to upgrade. If your upgrade fails with
1695 -j, please try again without -j. From time to time in the past there
1696 have been problems using -j with buildworld and/or installworld. This
1697 is especially true when upgrading between "distant" versions (eg one
1698 that cross a major release boundary or several minor releases, or when
1699 several months have passed on the -current branch).
1701 Sometimes, obscure build problems are the result of environment
1702 poisoning. This can happen because the make utility reads its
1703 environment when searching for values for global variables. To run
1704 your build attempts in an "environmental clean room", prefix all make
1705 commands with 'env -i '. See the env(1) manual page for more details.
1707 When upgrading from one major version to another it is generally best
1708 to upgrade to the latest code in the currently installed branch first,
1709 then do an upgrade to the new branch. This is the best-tested upgrade
1710 path, and has the highest probability of being successful. Please try
1711 this approach before reporting problems with a major version upgrade.
1713 When upgrading a live system, having a root shell around before
1714 installing anything can help undo problems. Not having a root shell
1715 around can lead to problems if pam has changed too much from your
1716 starting point to allow continued authentication after the upgrade.
1718 This file should be read as a log of events. When a later event changes
1719 information of a prior event, the prior event should not be deleted.
1720 Instead, a pointer to the entry with the new information should be
1721 placed in the old entry. Readers of this file should also sanity check
1722 older entries before relying on them blindly. Authors of new entries
1723 should write them with this in mind.
1727 When upgrading the boot ZFS pool to a new version, always follow
1730 1.) recompile and reinstall the ZFS boot loader and boot block
1731 (this is part of "make buildworld" and "make installworld")
1733 2.) update the ZFS boot block on your boot drive
1735 The following example updates the ZFS boot block on the first
1736 partition (freebsd-boot) of a GPT partitioned drive ada0:
1737 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1739 Non-boot pools do not need these updates.
1743 If you are updating from a prior version of FreeBSD (even one just
1744 a few days old), you should follow this procedure. It is the most
1745 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1747 make kernel-toolchain
1748 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1749 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1751 To test a kernel once
1752 ---------------------
1753 If you just want to boot a kernel once (because you are not sure
1754 if it works, or if you want to boot a known bad kernel to provide
1755 debugging information) run
1756 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1757 nextboot -k testkernel
1759 To just build a kernel when you know that it won't mess you up
1760 --------------------------------------------------------------
1761 This assumes you are already running a CURRENT system. Replace
1762 ${arch} with the architecture of your machine (e.g. "i386",
1763 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1765 cd src/sys/${arch}/conf
1766 config KERNEL_NAME_HERE
1767 cd ../compile/KERNEL_NAME_HERE
1772 If this fails, go to the "To build a kernel" section.
1774 To rebuild everything and install it on the current system.
1775 -----------------------------------------------------------
1776 # Note: sometimes if you are running current you gotta do more than
1777 # is listed here if you are upgrading from a really old current.
1779 <make sure you have good level 0 dumps>
1781 make kernel KERNCONF=YOUR_KERNEL_HERE
1783 <reboot in single user> [3]
1790 To cross-install current onto a separate partition
1791 --------------------------------------------------
1792 # In this approach we use a separate partition to hold
1793 # current's root, 'usr', and 'var' directories. A partition
1794 # holding "/", "/usr" and "/var" should be about 2GB in
1797 <make sure you have good level 0 dumps>
1800 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1801 <maybe newfs current's root partition>
1802 <mount current's root partition on directory ${CURRENT_ROOT}>
1803 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1804 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1805 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1806 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1807 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1808 <reboot into current>
1809 <do a "native" rebuild/install as described in the previous section>
1810 <maybe install compatibility libraries from ports/misc/compat*>
1814 To upgrade in-place from stable to current
1815 ----------------------------------------------
1816 <make sure you have good level 0 dumps>
1818 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1820 <reboot in single user> [3]
1827 Make sure that you've read the UPDATING file to understand the
1828 tweaks to various things you need. At this point in the life
1829 cycle of current, things change often and you are on your own
1830 to cope. The defaults can also change, so please read ALL of
1831 the UPDATING entries.
1833 Also, if you are tracking -current, you must be subscribed to
1834 freebsd-current@freebsd.org. Make sure that before you update
1835 your sources that you have read and understood all the recent
1836 messages there. If in doubt, please track -stable which has
1837 much fewer pitfalls.
1839 [1] If you have third party modules, such as vmware, you
1840 should disable them at this point so they don't crash your
1843 [3] From the bootblocks, boot -s, and then do
1848 adjkerntz -i # if CMOS is wall time
1849 Also, when doing a major release upgrade, it is required that
1850 you boot into single user mode to do the installworld.
1852 [4] Note: This step is non-optional. Failure to do this step
1853 can result in a significant reduction in the functionality of the
1854 system. Attempting to do it by hand is not recommended and those
1855 that pursue this avenue should read this file carefully, as well
1856 as the archives of freebsd-current and freebsd-hackers mailing lists
1857 for potential gotchas. The -U option is also useful to consider.
1858 See mergemaster(8) for more information.
1860 [5] Usually this step is a noop. However, from time to time
1861 you may need to do this if you get unknown user in the following
1862 step. It never hurts to do it all the time. You may need to
1863 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1864 install) after the buildworld before this step if you last updated
1865 from current before 20130425 or from -stable before 20130430.
1867 [6] This only deletes old files and directories. Old libraries
1868 can be deleted by "make delete-old-libs", but you have to make
1869 sure that no program is using those libraries anymore.
1871 [8] The new kernel must be able to run existing binaries used by
1872 an installworld. When upgrading across major versions, the new
1873 kernel's configuration must include the correct COMPAT_FREEBSD<n>
1874 option for existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x
1875 binaries). Failure to do so may leave you with a system that is
1876 hard to boot to recover. A GENERIC kernel will include suitable
1877 compatibility options to run binaries from older branches.
1879 Make sure that you merge any new devices from GENERIC since the
1880 last time you updated your kernel config file.
1882 [9] When checking out sources, you must include the -P flag to have
1883 cvs prune empty directories.
1885 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1886 "?=" instead of the "=" assignment operator, so that buildworld can
1887 override the CPUTYPE if it needs to.
1889 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1890 not on the command line, or in /etc/make.conf. buildworld will
1891 warn if it is improperly defined.
1894 This file contains a list, in reverse chronological order, of major
1895 breakages in tracking -current. It is not guaranteed to be a complete
1896 list of such breakages, and only contains entries since September 23, 2011.
1897 If you need to see UPDATING entries from before that date, you will need
1898 to fetch an UPDATING file from an older FreeBSD release.
1900 Copyright information:
1902 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1904 Redistribution, publication, translation and use, with or without
1905 modification, in full or in part, in any form or format of this
1906 document are permitted without further permission from the author.
1908 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1909 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1910 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1911 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1912 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1913 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1914 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1915 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1916 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1917 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1918 POSSIBILITY OF SUCH DAMAGE.
1920 Contact Warner Losh if you have any questions about your use of