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 20191023 p4 FreeBSD-EN-19:18.tzdata
21 Import tzdata 2019c. [EN-19:18.tzdata]
23 20190820 p3 FreeBSD-EN-19:16.bhyve
27 FreeBSD-SA-19:24.mqueuefs
29 Bhyve instruction emulation improvements (opcode 03H and F7H).
32 Fix ipfw(8) jail keyword prior to jail startup. [EN-19:17.ipfw]
34 Fix IPv6 remote denial of service. [SA-19:22.mbuf]
36 Fix kernel memory disclosure from /dev/midistat. [SA-19:23.midi]
38 Fix reference count overflow in mqueuefs. [SA-19:24.mqueuefs]
40 20190806 p2 FreeBSD-SA-19:18.bzip2
41 FreeBSD-SA-19:19.mldv2
42 FreeBSD-SA-19:20.bsnmp
43 FreeBSD-SA-19:21.bhyve
45 Fix multiple vulnerabilities in bzip2. [SA-19:18.bzip2]
47 Fix ICMPv6 / MLDv2 out-of-bounds memory access. [SA-19:19.mldv2]
49 Fix insufficient message length validation in bsnmp library.
52 Fix insufficient validation of guest-supplied data (e1000 device).
55 20190724 p1 FreeBSD-EN-19:13.mds
56 FreeBSD-SA-19:12.telnet
58 FreeBSD-SA-19:14.freebsd32
59 FreeBSD-SA-19:15.mqueuefs
60 FreeBSD-SA-19:16.bhyve
63 Fix panic from Intel CPU vulnerability mitigation. [EN-19:13.mds]
65 Fix multiple telnet client vulnerabilities. [SA-19:12.telnet]
67 Fix pts write-after-free. [SA-19:13.pts]
69 Fix kernel memory disclosure in freebsd32_ioctl. [SA-19:14.freebsd32]
71 Fix reference count overflow in mqueuefs. [SA-19:15.mqueuefs]
73 Fix byhve out-of-bounds read in XHCI device. [SA-19:16.bhyve]
75 Fix file descriptor reference count leak. [SA-19:17.fd]
80 20190702 FreeBSD-EN-19:12.tzdata
81 FreeBSD-SA-19:09.iconv
82 FreeBSD-SA-19:11.cd_ioctl
84 Import tzdata 2019b. [EN-19:12.tzdata]
86 Fix iconv buffer overflow. [SA-19:09.iconv]
88 Fix privilege escalation in cd(4) driver. [SA-19:11.cd_ioctl]
91 CARP now sets DSCP value CS7(Network Traffic) in the flowlabel field
92 of packets by default instead of only setting TOS_LOWDELAY in IPv4,
93 which was deprecated in 1998. Original behavior can be restored by
94 setting sysctl net.inet.carp.dscp=4.
97 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
98 8.0.0. Please see the 20141231 entry below for information about
99 prerequisites and upgrading, if you are not already using clang 3.5.0
103 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
104 compiled into your custom kernel, add 'device xz' statement to the
108 Co-existance for Forth and Lua interpreters in bootloaders has now been
109 merged to ease testing of lualoader. LOADER_DEFAULT_INTERP, documented
110 in build(7), may be used to control which interpreter flavor is used in
111 the default loader to be installed. For systems where Lua and Forth
112 coexist, this switch can also be made on a running system by creating a
113 link from /boot/loader{,.efi} to /boot/loader_${flavor}{,.efi} rather
114 than requiring a rebuild.
116 The default flavor in this branch will remain Forth. As indicated in
117 the 20190216 UPDATING entry, booting is a complex environment; it would
118 be prudent to assume that lualoader may not work for your setup and make
119 provisions for backup boot methods.
122 zfsloader's functionality has now been folded into loader.
123 zfsloader is no longer necesasary once you've updated your
124 boot blocks. For a transition period, we will install a
125 hardlink for zfsloader to loader to allow a smooth transition
126 until the boot blocks can be updated (hard link because old
127 zfs boot blocks don't understand symlinks).
130 Lualoader has been merged to facilitate testing on this branch. It's
131 purely opt-in for now by building WITH_LOADER_LUA and WITHOUT_FORTH in
132 /etc/src.conf, but co-existance will come shortly. Booting is a complex
133 environment and test coverage for Lua-enabled loaders has been thin, so
134 it would be prudent to assume it might not work and make provisions for
138 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
139 7.0.1. Please see the 20141231 entry below for information about
140 prerequisites and upgrading, if you are not already using clang 3.5.0
144 r342562 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
145 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
146 servers that have vfs.nfsd.nfs_privport set will only allow mounts
147 from clients using a reserved port#. Since both the FreeBSD and Linux
148 NFSv4 clients use reserved port#s by default, this should not affect
152 The '%I' format in the kern.corefile sysctl limits the number of
153 core files that a process can generate to the number stored in the
154 debug.ncores sysctl. The '%I' format is replaced by the single digit
155 index. Previously, if all indexes were taken the kernel would overwrite
156 only a core file with the highest index in a filename.
157 Currently the system will create a new core file if there is a free
158 index or if all slots are taken it will overwrite the oldest one.
161 WITH_OFED option now only enables the build for the OFED libraries
162 and some fundamental client utilities. OpenSM and rest of the
163 debugging tools are enabled by WITH_OFED_EXTRA build switch.
164 WITH_OFED is turned on by default on amd64.
167 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
168 6.0.1. Please see the 20141231 entry below for information about
169 prerequisites and upgrading, if you are not already using clang 3.5.0
173 The releng/11.2 branch has been created from stable/11@r334458.
176 The tz database (tzdb) has been updated to 2018e. This version more
177 correctly models time stamps in time zones with negative DST such as
178 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
179 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
180 time zone abbreviations and the tm_isdst flag.
183 The use of RSS hash from the network card aka flowid has been
184 disabled by default for lagg(4) as it's currently incompatible with
185 the lacp and loadbalance protocols.
187 This can be re-enabled by setting the following in loader.conf:
188 net.link.lagg.default_use_flowid="1"
191 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
192 6.0.0. Please see the 20141231 entry below for information about
193 prerequisites and upgrading, if you are not already using clang 3.5.0
197 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
198 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
199 to WITH/OUT_LOADER_GELI.
202 The geli password typed at boot is now hidden. To restore the previous
203 behavior, see geli(8) for configuration options.
205 The SW_WATCHDOG option is no longer necessary to enable the
206 hardclock-based software watchdog if no hardware watchdog is
207 configured. As before, SW_WATCHDOG will cause the software
208 watchdog to be enabled even if a hardware watchdog is configured.
211 lint(1) binaries and library are no longer built by default. To
212 enable building them, define WITH_LINT in src.conf. If you are using
213 a FreeBSD 12 or later system to build 11-stable, you may need to
214 install a lint(1) binary to use WITH_LINT.
217 When building multiple kernels using KERNCONF, non-existent KERNCONF
218 files will produce an error and buildkernel will fail. Previously
219 missing KERNCONF files silently failed giving no indication as to
220 why, only to subsequently discover during installkernel that the
221 desired kernel was never built in the first place.
224 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
225 Please see the 20141231 entry below for information about prerequisites
226 and upgrading, if you are not already using clang 3.5.0 or higher.
229 Since the switch to GPT disk labels, fsck for UFS/FFS has been
230 unable to automatically find alternate superblocks. As of r322806,
231 the information needed to find alternate superblocks has been
232 moved to the end of the area reserved for the boot block.
233 Filesystems created with a newfs of this vintage or later
234 will create the recovery information. If you have a filesystem
235 created prior to this change and wish to have a recovery block
236 created for your filesystem, you can do so by running fsck in
237 forground mode (i.e., do not use the -p or -y options). As it
238 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
239 to which you should answer yes.
242 The releng/11.1 branch has been created from stable/11@r320475.
245 arm64 builds now use the base system LLD 4.0.0 linker by default,
246 instead of requiring that the aarch64-binutils port or package be
247 installed. To continue using aarch64-binutils, set
248 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
251 The ctl.ko module no longer implements the iSCSI target frontend:
252 cfiscsi.ko does instead.
254 If building cfiscsi.ko as a kernel module, the module can be loaded
255 via one of the following methods:
256 - `cfiscsi_load="YES"` in loader.conf(5).
257 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
258 - ctladm(8)/ctld(8), when compiled with iSCSI support
259 (`WITH_ISCSI=yes` in src.conf(5))
261 Please see cfiscsi(4) for more details.
264 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
265 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
266 same source (previously, the dependency of mmcsd.ko on mmc.ko was
267 missing, but mmcsd.ko now will refuse to load if it is incompatible
271 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
272 use any explicitly assigned loopback address available in the jail
273 instead of using the first assigned address of the jail.
276 As of r316810 for ipfilter, keep frags is no longer assumed when
277 keep state is specified in a rule. r316810 aligns ipfilter with
278 documentation in man pages separating keep frags from keep state.
279 This allows keep state to specified without forcing keep frags
280 and allows keep frags to be specified independently of keep state.
281 To maintain previous behaviour, also specify keep frags with
282 keep state (as documented in ipf.conf.5).
285 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
286 Please see the 20141231 entry below for information about prerequisites
287 and upgrading, if you are not already using clang 3.5.0 or higher.
290 The code that provides support for ZFS .zfs/ directory functionality
291 has been reimplemented. It's not possible now to create a snapshot
292 by mkdir under .zfs/snapshot/. That should be the only user visible
296 Many changes in the IPsec code have been merged from the FreeBSD-CURRENT
297 branch. The IPSEC_FILTERTUNNEL kernel option is removed in favour of
298 corresponding sysctl. The IPSEC_NAT_T kernel option is also removed,
299 and now NAT-T is supported by default. Security associations now use
300 the single namespace for SPI allocation, so if you use several manually
301 configured security associations with the same SPI, this configuration
305 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
306 Please see the 20141231 entry below for information about prerequisites
307 and upgrading, if you are not already using clang 3.5.0 or higher.
310 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
311 Please see the 20141231 entry below for information about prerequisites
312 and upgrading, if you are not already using clang 3.5.0 or higher.
315 The layout of the pmap structure has changed for powerpc to put the pmap
316 statistics at the front for all CPU variations. libkvm(3) and all tools
317 that link against it need to be recompiled.
320 isl(4) and cyapa(4) drivers now require a new driver,
321 chromebook_platform(4), to work properly on Chromebook-class hardware.
322 On other types of hardware the drivers may need to be configured using
323 device hints. Please see the corresponding manual pages for details.
326 Relocatable object files with the extension of .So have been renamed
327 to use an extension of .pico instead. The purpose of this change is
328 to avoid a name clash with shared libraries on case-insensitive file
329 systems. On those file systems, foo.So is the same file as foo.so.
332 The releng/11.0 branch has been created from stable/11@r303970.
335 The stable/11 branch has been created from head@r302406.
338 The libc stub for the pipe(2) system call has been replaced with
339 a wrapper that calls the pipe2(2) system call and the pipe(2)
340 system call is now only implemented by the kernels that include
341 "options COMPAT_FREEBSD10" in their config file (this is the
342 default). Users should ensure that this option is enabled in
343 their kernel or upgrade userspace to r302092 before upgrading their
347 CAM will now strip leading spaces from SCSI disks' serial numbers.
348 This will effect users who create UFS filesystems on SCSI disks using
349 those disk's diskid device nodes. For example, if /etc/fstab
350 previously contained a line like
351 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
352 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
353 transforms like gmirror may also be affected. ZFS users should
357 The bitstring(3) API has been updated with new functionality and
358 improved performance. But it is binary-incompatible with the old API.
359 Objects built with the new headers may not be linked against objects
360 built with the old headers.
363 The brk and sbrk functions have been removed from libc on arm64.
364 Binutils from ports has been updated to not link to these
365 functions and should be updated to the latest version before
366 installing a new libc.
369 The armv6 port now defaults to hard float ABI. Limited support
370 for running both hardfloat and soft float on the same system
371 is available using the libraries installed with -DWITH_LIBSOFT.
372 This has only been tested as an upgrade path for installworld
373 and packages may fail or need manual intervention to run. New
374 packages will be needed.
376 To update an existing self-hosted armv6hf system, you must add
377 TARGET_ARCH=armv6 on the make command line for both the build
378 and the install steps.
381 Kernel modules compiled outside of a kernel build now default to
382 installing to /boot/modules instead of /boot/kernel. Many kernel
383 modules built this way (such as those in ports) already overrode
384 KMODDIR explicitly to install into /boot/modules. However,
385 manually building and installing a module from /sys/modules will
386 now install to /boot/modules instead of /boot/kernel.
389 The CAM I/O scheduler has been committed to the kernel. There should be
390 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
391 list of known rogues that claim support for this but actually corrupt
392 data is believed to be complete, be on the lookout for data
393 corruption. The known rogue list is believed to be complete:
395 o Crucial MX100, M550 drives with MU01 firmware.
396 o Micron M510 and M550 drives with MU01 firmware.
397 o Micron M500 prior to MU07 firmware
398 o Samsung 830, 840, and 850 all firmwares
399 o FCCT M500 all firmwares
401 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
402 with working NCQ TRIM. For Micron branded drives, see your sales rep for
403 updated firmware. Black listed drives will work correctly because these
404 drives work correctly so long as no NCQ TRIMs are sent to them. Given
405 this list is the same as found in Linux, it's believed there are no
406 other rogues in the market place. All other models from the above
409 To be safe, if you are at all concerned, you can quirk each of your
410 drives to prevent NCQ from being sent by setting:
411 kern.cam.ada.X.quirks="0x2"
412 in loader.conf. If the drive requires the 4k sector quirk, set the
416 The FAST_DEPEND build option has been removed and its functionality is
417 now the one true way. The old mkdep(1) style of 'make depend' has
418 been removed. See 20160311 for further details.
421 Resource range types have grown from unsigned long to uintmax_t. All
422 drivers, and anything using libdevinfo, need to be recompiled.
425 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
426 builds. It no longer runs mkdep(1) during 'make depend', and the
427 'make depend' stage can safely be skipped now as it is auto ran
428 when building 'make all' and will generate all SRCS and DPSRCS before
429 building anything else. Dependencies are gathered at compile time with
430 -MF flags kept in separate .depend files per object file. Users should
431 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
435 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
436 kernel modules. Therefore, if you load any kernel modules at boot time,
437 please install the boot loaders after you install the kernel, but before
441 make kernel KERNCONF=YOUR_KERNEL_HERE
442 make -C sys/boot install
443 <reboot in single user>
445 Then follow the usual steps, described in the General Notes section,
449 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
450 see the 20141231 entry below for information about prerequisites and
451 upgrading, if you are not already using clang 3.5.0 or higher.
454 The AIO subsystem is now a standard part of the kernel. The
455 VFS_AIO kernel option and aio.ko kernel module have been removed.
456 Due to stability concerns, asynchronous I/O requests are only
457 permitted on sockets and raw disks by default. To enable
458 asynchronous I/O requests on all file types, set the
459 vfs.aio.enable_unsafe sysctl to a non-zero value.
462 The ELF object manipulation tool objcopy is now provided by the
463 ELF Tool Chain project rather than by GNU binutils. It should be a
464 drop-in replacement, with the addition of arm64 support. The
465 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
466 to obtain the GNU version if necessary.
469 Building ZFS pools on top of zvols is prohibited by default. That
470 feature has never worked safely; it's always been prone to deadlocks.
471 Using a zvol as the backing store for a VM guest's virtual disk will
472 still work, even if the guest is using ZFS. Legacy behavior can be
473 restored by setting vfs.zfs.vol.recursive=1.
476 The NONE and HPN patches has been removed from OpenSSH. They are
477 still available in the security/openssh-portable port.
480 With the addition of ypldap(8), a new _ypldap user is now required
481 during installworld. "mergemaster -p" can be used to add the user
482 prior to installworld, as documented in the handbook.
485 The tftp loader (pxeboot) now uses the option root-path directive. As a
486 consequence it no longer looks for a pxeboot.4th file on the tftp
487 server. Instead it uses the regular /boot infrastructure as with the
491 The code to start recording plug and play data into the modules has
492 been committed. While the old tools will properly build a new kernel,
493 a number of warnings about "unknown metadata record 4" will be produced
494 for an older kldxref. To avoid such warnings, make sure to rebuild
495 the kernel toolchain (or world). Make sure that you have r292078 or
496 later when trying to build 292077 or later before rebuilding.
499 Debug data files are now built by default with 'make buildworld' and
500 installed with 'make installworld'. This facilitates debugging but
501 requires more disk space both during the build and for the installed
502 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
506 r291527 changed the internal interface between the nfsd.ko and
507 nfscommon.ko modules. As such, they must both be upgraded to-gether.
508 __FreeBSD_version has been bumped because of this.
511 Add support for unicode collation strings leads to a change of
512 order of files listed by ls(1) for example. To get back to the old
513 behaviour, set LC_COLLATE environment variable to "C".
515 Databases administrators will need to reindex their databases given
516 collation results will be different.
518 Due to a bug in install(1) it is recommended to remove the ancient
519 locales before running make installworld.
521 rm -rf /usr/share/locale/*
524 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
525 libcrypto.so.7 or libssl.so.7 must be recompiled.
528 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
529 Kernel modules isp_2400_multi and isp_2500_multi were removed and
530 should be replaced with isp_2400 and isp_2500 modules respectively.
533 The build previously allowed using 'make -n' to not recurse into
534 sub-directories while showing what commands would be executed, and
535 'make -n -n' to recursively show commands. Now 'make -n' will recurse
536 and 'make -N' will not.
539 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
540 and etcupdate will now use this file. A custom sendmail.cf is now
541 updated via this mechanism rather than via installworld. If you had
542 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
543 want to remove the exclusion or change it to "always install".
544 /etc/mail/sendmail.cf is now managed the same way regardless of
545 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
546 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
549 Compatibility shims for legacy ATA device names have been removed.
550 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
551 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
552 environment variables, /dev/ad* and /dev/ar* symbolic links.
555 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
556 Please see the 20141231 entry below for information about prerequisites
557 and upgrading, if you are not already using clang 3.5.0 or higher.
560 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
561 and renamed from .symbols to .debug. This reduces the size requirements
562 on the boot partition or file system and provides consistency with
563 userland debug files.
565 When using the supported kernel installation method the
566 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
567 as is done with /boot/kernel.
569 Developers wishing to maintain the historical behavior of installing
570 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
573 The wireless drivers had undergone changes that remove the 'parent
574 interface' from the ifconfig -l output. The rc.d network scripts
575 used to check presence of a parent interface in the list, so old
576 scripts would fail to start wireless networking. Thus, etcupdate(3)
577 or mergemaster(8) run is required after kernel update, to update your
578 rc.d scripts in /etc.
581 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
582 These configurations are now automatically interpreted as
583 'scrub fragment reassemble'.
586 Kernel-loadable modules for the random(4) device are back. To use
587 them, the kernel must have
590 options RANDOM_LOADABLE
592 kldload(8) can then be used to load random_fortuna.ko
593 or random_yarrow.ko. Please note that due to the indirect
594 function calls that the loadable modules need to provide,
595 the build-in variants will be slightly more efficient.
597 The random(4) kernel option RANDOM_DUMMY has been retired due to
598 unpopularity. It was not all that useful anyway.
601 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
602 Control over building the ELF Tool Chain tools is now provided by
603 the WITHOUT_TOOLCHAIN knob.
606 The polarity of Pulse Per Second (PPS) capture events with the
607 uart(4) driver has been corrected. Prior to this change the PPS
608 "assert" event corresponded to the trailing edge of a positive PPS
609 pulse and the "clear" event was the leading edge of the next pulse.
611 As the width of a PPS pulse in a typical GPS receiver is on the
612 order of 1 millisecond, most users will not notice any significant
613 difference with this change.
615 Anyone who has compensated for the historical polarity reversal by
616 configuring a negative offset equal to the pulse width will need to
617 remove that workaround.
620 The default group assigned to /dev/dri entries has been changed
621 from 'wheel' to 'video' with the id of '44'. If you want to have
622 access to the dri devices please add yourself to the video group
625 # pw groupmod video -m $USER
628 The menu.rc and loader.rc files will now be replaced during
629 upgrades. Please migrate local changes to menu.rc.local and
630 loader.rc.local instead.
633 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
634 strings and strip have been removed. The src.conf(5) knob
635 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
638 As ZFS requires more kernel stack pages than is the default on some
639 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
640 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
642 Please consider using 'options KSTACK_PAGES=X' where X is greater
643 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
646 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
647 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
648 default, i.e., they will not contain "::". For example, instead
649 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
650 to have a more specific match, such as different map entries for
651 IPv6:0:0 vs IPv6:0. This change requires that configuration
652 data (including maps, files, classes, custom ruleset, etc.) must
653 use the same format, so make certain such configuration data is
654 upgrading. As a very simple check search for patterns like
655 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
656 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
657 the cf option UseCompressedIPv6Addresses.
660 The default kernel entropy-processing algorithm is now
661 Fortuna, replacing Yarrow.
663 Assuming you have 'device random' in your kernel config
664 file, the configurations allow a kernel option to override
665 this default. You may choose *ONE* of:
667 options RANDOM_YARROW # Legacy /dev/random algorithm.
668 options RANDOM_DUMMY # Blocking-only driver.
670 If you have neither, you get Fortuna. For most people,
671 read no further, Fortuna will give a /dev/random that works
672 like it always used to, and the difference will be irrelevant.
674 If you remove 'device random', you get *NO* kernel-processed
675 entropy at all. This may be acceptable to folks building
676 embedded systems, but has complications. Carry on reading,
677 and it is assumed you know what you need.
679 *PLEASE* read random(4) and random(9) if you are in the
680 habit of tweaking kernel configs, and/or if you are a member
681 of the embedded community, wanting specific and not-usual
682 behaviour from your security subsystems.
684 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
685 random', you will NOT have a functioning /dev/random, and
686 many cryptographic features will not work, including SSH.
687 You may also find strange behaviour from the random(3) set
688 of library functions, in particular sranddev(3), srandomdev(3)
689 and arc4random(3). The reason for this is that the KERN_ARND
690 sysctl only returns entropy if it thinks it has some to
691 share, and with RANDOM_DUMMY or no 'device random' this
695 An additional fix for the issue described in the 20150614 sendmail
696 entry below has been been committed in revision 284717.
699 FreeBSD's old make (fmake) has been removed from the system. It is
700 available as the devel/fmake port or via pkg install fmake.
703 The fix for the issue described in the 20150614 sendmail entry
704 below has been been committed in revision 284436. The work
705 around described in that entry is no longer needed unless the
706 default setting is overridden by a confDH_PARAMETERS configuration
707 setting of '5' or pointing to a 512 bit DH parameter file.
710 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
711 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
712 and devel/kyua to version 0.20+ and adjust any calling code to work
713 with Kyuafile and kyua.
716 The import of openssl to address the FreeBSD-SA-15:10.openssl
717 security advisory includes a change which rejects handshakes
718 with DH parameters below 768 bits. sendmail releases prior
719 to 8.15.2 (not yet released), defaulted to a 512 bit
720 DH parameter setting for client connections. To work around
721 this interoperability, sendmail can be configured to use a
722 2048 bit DH parameter by:
724 1. Edit /etc/mail/`hostname`.mc
725 2. If a setting for confDH_PARAMETERS does not exist or
726 exists and is set to a string beginning with '5',
728 3. If a setting for confDH_PARAMETERS exists and is set to
729 a file path, create a new file with:
730 openssl dhparam -out /path/to/file 2048
731 4. Rebuild the .cf file:
732 cd /etc/mail/; make; make install
734 cd /etc/mail/; make restart
736 A sendmail patch is coming, at which time this file will be
740 Generation of legacy formatted entries have been disabled by default
741 in pwd_mkdb(8), as all base system consumers of the legacy formatted
742 entries were converted to use the new format by default when the new,
743 machine independent format have been added and supported since FreeBSD
746 Please see the pwd_mkdb(8) manual page for further details.
749 Clang and llvm have been upgraded to 3.6.1 release. Please see the
750 20141231 entry below for information about prerequisites and upgrading,
751 if you are not already using 3.5.0 or higher.
754 TI platform code switched to using vendor DTS files and this update
755 may break existing systems running on Beaglebone, Beaglebone Black,
758 - dtb files should be regenerated/reinstalled. Filenames are the
759 same but content is different now
760 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
761 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
762 addressing scheme is now pin 25 on /dev/gpioc3.
763 - Pandaboard: /etc/ttys should be updated, serial console device is
764 now /dev/ttyu2, not /dev/ttyu0
767 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
768 If you need the GNU extension from groff soelim(1), install groff
769 from package: pkg install groff, or via ports: textproc/groff.
772 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
773 defined in symlink(7); previously symlinks were silently ignored.
776 The const qualifier has been removed from iconv(3) to comply with
777 POSIX. The ports tree is aware of this from r384038 onwards.
780 Libraries specified by LIBADD in Makefiles must have a corresponding
781 DPADD_<lib> variable to ensure correct dependencies. This is now
782 enforced in src.libnames.mk.
785 From legacy ata(4) driver was removed support for SATA controllers
786 supported by more functional drivers ahci(4), siis(4) and mvs(4).
787 Kernel modules ataahci and ataadaptec were removed completely,
788 replaced by ahci and mvs modules respectively.
791 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
792 the 20141231 entry below for information about prerequisites and
793 upgrading, if you are not already using 3.5.0 or higher.
796 The 32-bit PowerPC kernel has been changed to a position-independent
797 executable. This can only be booted with a version of loader(8)
798 newer than January 31, 2015, so make sure to update both world and
799 kernel before rebooting.
802 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
803 but before r278950, the RNG was not seeded properly. Immediately
804 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
805 ssh keys or openssl keys) that were generated w/ a kernel from that
806 range. This does not affect programs that directly used /dev/random
807 or /dev/urandom. All userland uses of arc4random(3) are affected.
810 The autofs(4) ABI was changed in order to restore binary compatibility
811 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
815 The powerpc64 kernel has been changed to a position-independent
816 executable. This can only be booted with a new version of loader(8),
817 so make sure to update both world and kernel before rebooting.
820 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
821 only release, no new features have been added. Please see the 20141231
822 entry below for information about prerequisites and upgrading, if you
823 are not already using 3.5.0.
826 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
827 taken from the ELF Tool Chain project rather than GNU binutils. They
828 should be drop-in replacements, with the addition of arm64 support.
829 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
830 binutils tools, if necessary. See 20150805 for updated information.
833 The default Unbound configuration now enables remote control
834 using a local socket. Users who have already enabled the
835 local_unbound service should regenerate their configuration
836 by running "service local_unbound setup" as root.
839 The GNU texinfo and GNU info pages have been removed.
840 To be able to view GNU info pages please install texinfo from ports.
843 Clang, llvm and lldb have been upgraded to 3.5.0 release.
845 As of this release, a prerequisite for building clang, llvm and lldb is
846 a C++11 capable compiler and C++11 standard library. This means that to
847 be able to successfully build the cross-tools stage of buildworld, with
848 clang as the bootstrap compiler, your system compiler or cross compiler
849 should either be clang 3.3 or later, or gcc 4.8 or later, and your
850 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
853 On any standard FreeBSD 10.x or 11.x installation, where clang and
854 libc++ are on by default (that is, on x86 or arm), this should work out
857 On 9.x installations where clang is enabled by default, e.g. on x86 and
858 powerpc, libc++ will not be enabled by default, so libc++ should be
859 built (with clang) and installed first. If both clang and libc++ are
860 missing, build clang first, then use it to build libc++.
862 On 8.x and earlier installations, upgrade to 9.x first, and then follow
863 the instructions for 9.x above.
865 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
866 default, and do not build clang.
868 Many embedded systems are resource constrained, and will not be able to
869 build clang in a reasonable time, or in some cases at all. In those
870 cases, cross building bootable systems on amd64 is a workaround.
872 This new version of clang introduces a number of new warnings, of which
873 the following are most likely to appear:
877 This warns in two cases, for both C and C++:
878 * When the code is trying to take the absolute value of an unsigned
879 quantity, which is effectively a no-op, and almost never what was
880 intended. The code should be fixed, if at all possible. If you are
881 sure that the unsigned quantity can be safely cast to signed, without
882 loss of information or undefined behavior, you can add an explicit
883 cast, or disable the warning.
885 * When the code is trying to take an absolute value, but the called
886 abs() variant is for the wrong type, which can lead to truncation.
887 If you want to disable the warning instead of fixing the code, please
888 make sure that truncation will not occur, or it might lead to unwanted
891 -Wtautological-undefined-compare and
892 -Wundefined-bool-conversion
894 These warn when C++ code is trying to compare 'this' against NULL, while
895 'this' should never be NULL in well-defined C++ code. However, there is
896 some legacy (pre C++11) code out there, which actively abuses this
897 feature, which was less strictly defined in previous C++ versions.
899 Squid and openjdk do this, for example. The warning can be turned off
900 for C++98 and earlier, but compiling the code in C++11 mode might result
901 in unexpected behavior; for example, the parts of the program that are
902 unreachable could be optimized away.
905 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
906 kernel sources have been removed. The .h files remain, since some
907 utilities include them. This will need to be fixed later.
908 If "mount -t oldnfs ..." is attempted, it will fail.
909 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
910 the utilities will report errors.
913 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
914 directories to top level SUBDIR variable when their parent
915 directory is included in LOCAL_DIRS. Users with build systems with
916 such hierarchies and without SUBDIR entries in the parent
917 directory Makefiles should add them or add the directories to
921 faith(4) and faithd(8) have been removed from the base system. Faith
922 has been obsolete for a very long time.
925 vt(4), the new console driver, is enabled by default. It brings
926 support for Unicode and double-width characters, as well as
927 support for UEFI and integration with the KMS kernel video
930 You may need to update your console settings in /etc/rc.conf,
931 most probably the keymap. During boot, /etc/rc.d/syscons will
932 indicate what you need to do.
934 vt(4) still has issues and lacks some features compared to
935 syscons(4). See the wiki for up-to-date information:
936 https://wiki.freebsd.org/Newcons
938 If you want to keep using syscons(4), you can do so by adding
939 the following line to /boot/loader.conf:
943 pjdfstest has been integrated into kyua as an opt-in test suite.
944 Please see share/doc/pjdfstest/README for more details on how to
948 gperf has been removed from the base system for architectures
949 that use clang. Ports that require gperf will obtain it from the
953 pjdfstest has been moved from tools/regression/pjdfstest to
957 At svn r271982, The default linux compat kernel ABI has been adjusted
958 to 2.6.18 in support of the linux-c6 compat ports infrastructure
959 update. If you wish to continue using the linux-f10 compat ports,
960 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
961 encouraged to update their linux-compat packages to linux-c6 during
962 their next update cycle.
965 The ofwfb driver, used to provide a graphics console on PowerPC when
966 using vt(4), no longer allows mmap() of all physical memory. This
967 will prevent Xorg on PowerPC with some ATI graphics cards from
968 initializing properly unless x11-servers/xorg-server is updated to
972 The xdev targets have been converted to using TARGET and
973 TARGET_ARCH instead of XDEV and XDEV_ARCH.
976 The default unbound configuration has been modified to address
977 issues with reverse lookups on networks that use private
978 address ranges. If you use the local_unbound service, run
979 "service local_unbound setup" as root to regenerate your
980 configuration, then "service local_unbound reload" to load the
984 The GNU texinfo and GNU info pages are not built and installed
985 anymore, WITH_INFO knob has been added to allow to built and install
987 UPDATE: see 20150102 entry on texinfo's removal
990 The GNU readline library is now an INTERNALLIB - that is, it is
991 statically linked into consumers (GDB and variants) in the base
992 system, and the shared library is no longer installed. The
993 devel/readline port is available for third party software that
997 The Itanium architecture (ia64) has been removed from the list of
998 known architectures. This is the first step in the removal of the
1002 Commit r268115 has added NFSv4.1 server support, merged from
1003 projects/nfsv4.1-server. Since this includes changes to the
1004 internal interfaces between the NFS related modules, a full
1005 build of the kernel and modules will be necessary.
1006 __FreeBSD_version has been bumped.
1009 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1010 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1011 which differs from the behaviour controlled by this knob.)
1014 Maximal length of the serial number in CTL was increased from 16 to
1015 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1016 and ctld, need to be rebuilt to work with a new kernel.
1019 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1020 1 respectively to match the upstream numbers. They were out of
1021 sync because, when they were originally added to FreeBSD, the
1022 upstream versions were not respected. These libraries are private
1023 and not yet built by default, so renumbering them should be a
1024 non-issue. However, unclean source trees will yield broken test
1025 programs once the operator executes "make delete-old-libs" after a
1026 "make installworld".
1028 Additionally, the atf-sh binary was made private by moving it into
1029 /usr/libexec/. Already-built shell test programs will keep the
1030 path to the old binary so they will break after "make delete-old"
1033 If you are using WITH_TESTS=yes (not the default), wipe the object
1034 tree and rebuild from scratch to prevent spurious test failures.
1035 This is only needed once: the misnumbered libraries and misplaced
1036 binaries have been added to OptionalObsoleteFiles.inc so they will
1037 be removed during a clean upgrade.
1040 Clang and llvm have been upgraded to 3.4.1 release.
1043 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1044 be removed to avoid issues in the future (and has been added to
1048 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1049 past, it affected all builds that used the bsd.*.mk files. The old
1050 behavior was a bug, but people may have relied upon it. To get this
1051 behavior back, you can .include /etc/src.conf from /etc/make.conf
1052 (which is still global and isn't changed). This also changes the
1053 behavior of incremental builds inside the tree of individual
1054 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1055 Although this has survived make universe and some upgrade scenarios,
1056 other upgrade scenarios may have broken. At least one form of
1057 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1058 as well... In cases where MAKESYSPATH isn't working with this
1059 setting, you'll need to set it to the full path to your tree.
1061 One side effect of all this cleaning up is that bsd.compiler.mk
1062 is no longer implicitly included by bsd.own.mk. If you wish to
1063 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1067 The lindev device has been removed since /dev/full has been made a
1068 standard device. __FreeBSD_version has been bumped.
1071 The knob WITHOUT_VI was added to the base system, which controls
1072 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1073 in order to reorder files share/termcap and didn't build ex(1) as a
1074 build tool, so building/installing with WITH_VI is highly advised for
1075 build hosts for older releases.
1077 This issue has been fixed in stable/9 and stable/10 in r277022 and
1078 r276991, respectively.
1081 The YES_HESIOD knob has been removed. It has been obsolete for
1082 a decade. Please move to using WITH_HESIOD instead or your builds
1083 will silently lack HESIOD.
1086 The uart(4) driver has been changed with respect to its handling
1087 of the low-level console. Previously the uart(4) driver prevented
1088 any process from changing the baudrate or the CLOCAL and HUPCL
1089 control flags. By removing the restrictions, operators can make
1090 changes to the serial console port without having to reboot.
1091 However, when getty(8) is started on the serial device that is
1092 associated with the low-level console, a misconfigured terminal
1093 line in /etc/ttys will now have a real impact.
1094 Before upgrading the kernel, make sure that /etc/ttys has the
1095 serial console device configured as 3wire without baudrate to
1096 preserve the previous behaviour. E.g:
1097 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1100 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1101 to improve performance. To re-enable it, if needed, run rpcbind
1102 with command line option -W.
1105 Switched back to the GPL dtc compiler due to updates in the upstream
1106 dts files not being supported by the BSDL dtc compiler. You will need
1107 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1108 may result while building dtb files during a kernel build if you fail
1109 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1112 Clang and llvm have been upgraded to 3.4 release.
1115 The nve(4) driver has been removed. Please use the nfe(4) driver
1116 for NVIDIA nForce MCP Ethernet adapters instead.
1119 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1120 This could cause certain C++ applications using shared libraries built
1121 against the previous version of libc++ to crash. The incompatibility
1122 has now been fixed, but any C++ applications or shared libraries built
1123 between r261283 and r261801 should be recompiled.
1126 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1127 capability mode support. Please note that enabling the feature in
1128 kernel is still highly recommended.
1131 OpenSSH is now built with sandbox support, and will use sandbox as
1132 the default privilege separation method. This requires Capsicum
1133 capability mode support in kernel.
1136 The libelf and libdwarf libraries have been updated to newer
1137 versions from upstream. Shared library version numbers for
1138 these two libraries were bumped. Any ports or binaries
1139 requiring these two libraries should be recompiled.
1140 __FreeBSD_version is bumped to 1100006.
1143 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1144 instead of providing an explicit one, this would prevent such
1145 Makefile from providing its own Kyuafile in the future during
1146 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1147 intervention is needed to clean an objdir if you use NO_CLEAN:
1148 # find /usr/obj -name Kyuafile | xargs rm -f
1151 The behavior of gss_pseudo_random() for the krb5 mechanism
1152 has changed, for applications requesting a longer random string
1153 than produced by the underlying enctype's pseudo-random() function.
1154 In particular, the random string produced from a session key of
1155 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1156 be different at the 17th octet and later, after this change.
1157 The counter used in the PRF+ construction is now encoded as a
1158 big-endian integer in accordance with RFC 4402.
1159 __FreeBSD_version is bumped to 1100004.
1162 The WITHOUT_ATF build knob has been removed and its functionality
1163 has been subsumed into the more generic WITHOUT_TESTS. If you were
1164 using the former to disable the build of the ATF libraries, you
1165 should change your settings to use the latter.
1168 The default version of mtree is nmtree which is obtained from
1169 NetBSD. The output is generally the same, but may vary
1170 slightly. If you found you need identical output adding
1171 "-F freebsd9" to the command line should do the trick. For the
1172 time being, the old mtree is available as fmtree.
1175 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1176 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1177 1.1.4_8 and verify bsdyml not linked in, before running "make
1179 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1181 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1184 The stable/10 branch has been created in subversion from head
1188 The rc.d/jail script has been updated to support jail(8)
1189 configuration file. The "jail_<jname>_*" rc.conf(5) variables
1190 for per-jail configuration are automatically converted to
1191 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
1192 This is transparently backward compatible. See below about some
1193 incompatibilities and rc.conf(5) manual page for more details.
1195 These variables are now deprecated in favor of jail(8) configuration
1196 file. One can use "rc.d/jail config <jname>" command to generate
1197 a jail(8) configuration file in /var/run/jail.<jname>.conf without
1198 running the jail(8) utility. The default pathname of the
1199 configuration file is /etc/jail.conf and can be specified by
1200 using $jail_conf or $jail_<jname>_conf variables.
1202 Please note that jail_devfs_ruleset accepts an integer at
1203 this moment. Please consider to rewrite the ruleset name
1207 BIND has been removed from the base system. If all you need
1208 is a local resolver, simply enable and start the local_unbound
1209 service instead. Otherwise, several versions of BIND are
1210 available in the ports tree. The dns/bind99 port is one example.
1212 With this change, nslookup(1) and dig(1) are no longer in the base
1213 system. Users should instead use host(1) and drill(1) which are
1214 in the base system. Alternatively, nslookup and dig can
1215 be obtained by installing the dns/bind-tools port.
1218 With the addition of unbound(8), a new unbound user is now
1219 required during installworld. "mergemaster -p" can be used to
1220 add the user prior to installworld, as documented in the handbook.
1223 OpenSSH is now built with DNSSEC support, and will by default
1224 silently trust signed SSHFP records. This can be controlled with
1225 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1226 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1229 The GNU Compiler Collection and C++ standard library (libstdc++)
1230 are no longer built by default on platforms where clang is the system
1231 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1232 options in src.conf.
1235 The PROCDESC kernel option is now part of the GENERIC kernel
1236 configuration and is required for the rwhod(8) to work.
1237 If you are using custom kernel configuration, you should include
1241 The API and ABI related to the Capsicum framework was modified
1242 in backward incompatible way. The userland libraries and programs
1243 have to be recompiled to work with the new kernel. This includes the
1244 following libraries and programs, but the whole buildworld is
1245 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1246 kdump, procstat, rwho, rwhod, uniq.
1249 AES-NI intrinsic support has been added to gcc. The AES-NI module
1250 has been updated to use this support. A new gcc is required to build
1251 the aesni module on both i386 and amd64.
1254 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1255 Thus "device padlock_rng" and "device rdrand_rng" should be
1256 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1259 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1260 enables just the iconv* functionality and is now on by default.
1261 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1262 compatibility. Set WITHOUT_ICONV to build the old way.
1263 If you have been using WITH_ICONV before, you will very likely
1264 need to turn on WITH_LIBICONV_COMPAT.
1267 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1268 Illumos origin, including ZFS. If you have INVARIANTS in your
1269 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1271 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1272 locks if WITNESS option was set. Because that generated a lot of
1273 witness(9) reports and all of them were believed to be false
1274 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1275 can be used to achieve the previous behavior.
1278 Timer values in IPv6 data structures now use time_uptime instead
1279 of time_second. Although this is not a user-visible functional
1280 change, userland utilities which directly use them---ndp(8),
1281 rtadvd(8), and rtsold(8) in the base system---need to be updated
1282 to r253970 or later.
1285 find -delete can now delete the pathnames given as arguments,
1286 instead of only files found below them or if the pathname did
1287 not contain any slashes. Formerly, the following error message
1290 find: -delete: <path>: relative path potentially not safe
1292 Deleting the pathnames given as arguments can be prevented
1293 without error messages using -mindepth 1 or by changing
1294 directory and passing "." as argument to find. This works in the
1295 old as well as the new version of find.
1298 Behavior of devfs rules path matching has been changed.
1299 Pattern is now always matched against fully qualified devfs
1300 path and slash characters must be explicitly matched by
1301 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1302 subdirectories must be reviewed.
1305 The default ARM ABI has changed to the ARM EABI. The old ABI is
1306 incompatible with the ARM EABI and all programs and modules will
1307 need to be rebuilt to work with a new kernel.
1309 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1311 NOTE: Support for the old ABI will be removed in the future and
1312 users are advised to upgrade.
1315 pkg_install has been disconnected from the build if you really need it
1316 you should add WITH_PKGTOOLS in your src.conf(5).
1319 Most of network statistics structures were changed to be able
1320 keep 64-bits counters. Thus all tools, that work with networking
1321 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1324 Fix a bug that allowed a tracing process (e.g. gdb) to write
1325 to a memory-mapped file in the traced process's address space
1326 even if neither the traced process nor the tracing process had
1327 write access to that file.
1330 CVS has been removed from the base system. An exact copy
1331 of the code is available from the devel/cvs port.
1334 Some people report the following error after the switch to bmake:
1336 make: illegal option -- J
1337 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1339 *** [buildworld] Error code 2
1341 this likely due to an old instance of make in
1342 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1343 which src/Makefile will use that blindly, if it exists, so if
1344 you see the above error:
1346 rm -rf `make -V MAKEPATH`
1351 Use bmake by default.
1352 Whereas before one could choose to build with bmake via
1353 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1354 make. The goal is to remove these knobs for 10-RELEASE.
1356 It is worth noting that bmake (like gmake) treats the command
1357 line as the unit of failure, rather than statements within the
1358 command line. Thus '(cd some/where && dosomething)' is safer
1359 than 'cd some/where; dosomething'. The '()' allows consistent
1360 behavior in parallel build.
1363 Fix a bug that allows NFS clients to issue READDIR on files.
1366 The WITHOUT_IDEA option has been removed because
1367 the IDEA patent expired.
1370 The sysctl which controls TRIM support under ZFS has been renamed
1371 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1375 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1376 rather than creating it's own in the temporary directory in
1377 order allow access to bootstrapped versions of tools such as
1378 install and mtree. When upgrading from version of FreeBSD where
1379 the install command does not support -l, you will need to
1380 install a new mergemaster command if mergemaster -p is required.
1381 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1385 Legacy ATA stack, disabled and replaced by new CAM-based one since
1386 FreeBSD 9.0, completely removed from the sources. Kernel modules
1387 atadisk and atapi*, user-level tools atacontrol and burncd are
1388 removed. Kernel option `options ATA_CAM` is now permanently enabled
1392 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1393 and socketpair(2). Software, in particular Kerberos, may
1394 automatically detect and use these during building. The resulting
1395 binaries will not work on older kernels.
1398 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1399 information, see the respective 20130304 entry).
1402 Recent commits to callout(9) changed the size of struct callout,
1403 so the KBI is probably heavily disturbed. Also, some functions
1404 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1405 by macros. Every kernel module using it won't load, so rebuild
1408 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1409 but does not initialize by default (because of the new CTL_DISABLE
1410 option) to save memory. To re-enable it, remove the CTL_DISABLE
1411 option from the kernel config file or set kern.cam.ctl.disable=0
1412 in /boot/loader.conf.
1415 The ctl device has been disabled in GENERIC for i386 and amd64.
1416 This was done due to the extra memory being allocated at system
1417 initialisation time by the ctl driver which was only used if
1418 a CAM target device was created. This makes a FreeBSD system
1419 unusable on 128MB or less of RAM.
1422 A new compression method (lz4) has been merged to -HEAD. Please
1423 refer to zpool-features(7) for more information.
1425 Please refer to the "ZFS notes" section of this file for information
1426 on upgrading boot ZFS pools.
1429 A BSD-licensed patch(1) variant has been added and is installed
1430 as bsdpatch, being the GNU version the default patch.
1431 To inverse the logic and use the BSD-licensed one as default,
1432 while having the GNU version installed as gnupatch, rebuild
1433 and install world with the WITH_BSD_PATCH knob set.
1436 Due to the use of the new -l option to install(1) during build
1437 and install, you must take care not to directly set the INSTALL
1438 make variable in your /etc/make.conf, /etc/src.conf, or on the
1439 command line. If you wish to use the -C flag for all installs
1440 you may be able to add INSTALL+=-C to /etc/make.conf or
1444 The install(1) option -M has changed meaning and now takes an
1445 argument that is a file or path to append logs to. In the
1446 unlikely event that -M was the last option on the command line
1447 and the command line contained at least two files and a target
1448 directory the first file will have logs appended to it. The -M
1449 option served little practical purpose in the last decade so its
1450 use is expected to be extremely rare.
1453 After switching to Clang as the default compiler some users of ZFS
1454 on i386 systems started to experience stack overflow kernel panics.
1455 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1458 GEOM_LABEL now mangles label names read from file system metadata.
1459 Mangling affect labels containing spaces, non-printable characters,
1460 '%' or '"'. Device names in /etc/fstab and other places may need to
1464 By default, only the 10 most recent kernel dumps will be saved. To
1465 restore the previous behaviour (no limit on the number of kernel dumps
1466 stored in the dump directory) add the following line to /etc/rc.conf:
1471 With the addition of auditdistd(8), a new auditdistd user is now
1472 required during installworld. "mergemaster -p" can be used to
1473 add the user prior to installworld, as documented in the handbook.
1476 The sin6_scope_id member variable in struct sockaddr_in6 is now
1477 filled by the kernel before passing the structure to the userland via
1478 sysctl or routing socket. This means the KAME-specific embedded scope
1479 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1480 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1481 __FreeBSD_version is bumped to 1000025.
1484 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1485 This means that the world and kernel will be compiled with clang
1486 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1487 and /usr/bin/cpp. To disable this behavior and revert to building
1488 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1489 of current may need to bootstrap WITHOUT_CLANG first if the clang
1490 build fails (its compatibility window doesn't extend to the 9 stable
1494 The IPFIREWALL_FORWARD kernel option has been removed. Its
1495 functionality now turned on by default.
1498 The ZERO_COPY_SOCKET kernel option has been removed and
1499 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1500 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1501 mechanism which is not safe and may result in kernel crashes.
1502 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1503 driver supports disposeable external page sized mbuf storage.
1504 Proper replacements for both zero-copy mechanisms are under
1505 consideration and will eventually lead to complete removal
1506 of the two kernel options.
1509 The IPv4 network stack has been converted to network byte
1510 order. The following modules need to be recompiled together
1511 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1512 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1515 Support for non-MPSAFE filesystems was removed from VFS. The
1516 VFS_VERSION was bumped, all filesystem modules shall be
1520 All the non-MPSAFE filesystems have been disconnected from
1521 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1522 portalfs, smbfs, xfs.
1525 The interface cloning API and ABI has changed. The following
1526 modules need to be recompiled together with kernel:
1527 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1528 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1529 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1532 The sdhci driver was split in two parts: sdhci (generic SD Host
1533 Controller logic) and sdhci_pci (actual hardware driver).
1534 No kernel config modifications are required, but if you
1535 load sdhc as a module you must switch to sdhci_pci instead.
1538 Import the FUSE kernel and userland support into base system.
1541 The GNU sort(1) program has been removed since the BSD-licensed
1542 sort(1) has been the default for quite some time and no serious
1543 problems have been reported. The corresponding WITH_GNU_SORT
1547 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1548 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1552 The net80211(4) ABI has been changed to allow for improved driver
1553 PS-POLL and power-save support. All wireless drivers need to be
1554 recompiled to work with the new kernel.
1557 The random(4) support for the VIA hardware random number
1558 generator (`PADLOCK') is no longer enabled unconditionally.
1559 Add the padlock_rng device in the custom kernel config if
1560 needed. The GENERIC kernels on i386 and amd64 do include the
1561 device, so the change only affects the custom kernel
1565 The pf(4) packet filter ABI has been changed. pfctl(8) and
1566 snmp_pf module need to be recompiled to work with new kernel.
1569 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1570 to -HEAD. Pools that have empty_bpobj in active state can not be
1571 imported read-write with ZFS implementations that do not support
1572 this feature. For more information read the zpool-features(5)
1576 The sparc64 ZFS loader has been changed to no longer try to auto-
1577 detect ZFS providers based on diskN aliases but now requires these
1578 to be explicitly listed in the OFW boot-device environment variable.
1581 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1582 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1583 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1586 The following sysctls and tunables have been renamed for consistency
1587 with other variables:
1588 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1589 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1592 The sort utility has been replaced with BSD sort. For now, GNU sort
1593 is also available as "gnusort" or the default can be set back to
1594 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1595 installed as "bsdsort".
1598 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1599 Starting with this version the old system of ZFS pool versioning
1600 is superseded by "feature flags". This concept enables forward
1601 compatibility against certain future changes in functionality of ZFS
1602 pools. The first read-only compatible "feature flag" for ZFS pools
1603 is named "com.delphix:async_destroy". For more information
1604 read the new zpool-features(5) manual page.
1605 Please refer to the "ZFS notes" section of this file for information
1606 on upgrading boot ZFS pools.
1609 The malloc(3) implementation embedded in libc now uses sources imported
1610 as contrib/jemalloc. The most disruptive API change is to
1611 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1612 delete it prior to installworld, and optionally re-create it using the
1613 new format after rebooting. See malloc.conf(5) for details
1614 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1618 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1619 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1620 now spelled mips. This is to aid compatibility with third-party
1621 software that expects this naming scheme in uname(3). Little-endian
1622 settings are unchanged. If you are updating a big-endian mips64 machine
1623 from before this change, you may need to set MACHINE_ARCH=mips64 in
1624 your environment before the new build system will recognize your machine.
1627 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1631 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1632 nullfs(5) did not pass through all behaviours to the underlying layer,
1633 as a result if we bound to a socket on the lower layer we could connect
1634 only to the lower path; if we bound to the upper layer we could connect
1635 only to the upper path. The new behavior is one can connect to both the
1636 lower and the upper paths regardless what layer path one binds to.
1639 The getifaddrs upgrade path broken with 20111215 has been restored.
1640 If you have upgraded in between 20111215 and 20120209 you need to
1641 recompile libc again with your kernel. You still need to recompile
1642 world to be able to configure CARP but this restriction already
1643 comes from 20111215.
1646 The set_rcvar() function has been removed from /etc/rc.subr. All
1647 base and ports rc.d scripts have been updated, so if you have a
1648 port installed with a script in /usr/local/etc/rc.d you can either
1649 hand-edit the rcvar= line, or reinstall the port.
1651 An easy way to handle the mass-update of /etc/rc.d:
1652 rm /etc/rc.d/* && mergemaster -i
1655 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1656 on the current CPU and prevents other threads from running.
1657 This behavior can be reverted using the kern.stop_scheduler_on_panic
1659 The new behavior can be incompatible with kern.sync_on_panic.
1662 The carp(4) facility has been changed significantly. Configuration
1663 of the CARP protocol via ifconfig(8) has changed, as well as format
1664 of CARP events submitted to devd(8) has changed. See manual pages
1665 for more information. The arpbalance feature of carp(4) is currently
1666 not supported anymore.
1668 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1669 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1670 need to be recompiled.
1673 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1677 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1678 explicitely support non-MPSAFE filesystems.
1679 It is on by default for all supported platform at this present
1683 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1684 i386 and pc98 GENERIC kernel configuration files.
1687 sysinstall has been removed
1690 The stable/9 branch created in subversion. This corresponds to the
1691 RELENG_9 branch in CVS.
1697 Avoid using make -j when upgrading. While generally safe, there are
1698 sometimes problems using -j to upgrade. If your upgrade fails with
1699 -j, please try again without -j. From time to time in the past there
1700 have been problems using -j with buildworld and/or installworld. This
1701 is especially true when upgrading between "distant" versions (eg one
1702 that cross a major release boundary or several minor releases, or when
1703 several months have passed on the -current branch).
1705 Sometimes, obscure build problems are the result of environment
1706 poisoning. This can happen because the make utility reads its
1707 environment when searching for values for global variables. To run
1708 your build attempts in an "environmental clean room", prefix all make
1709 commands with 'env -i '. See the env(1) manual page for more details.
1711 When upgrading from one major version to another it is generally best
1712 to upgrade to the latest code in the currently installed branch first,
1713 then do an upgrade to the new branch. This is the best-tested upgrade
1714 path, and has the highest probability of being successful. Please try
1715 this approach before reporting problems with a major version upgrade.
1717 When upgrading a live system, having a root shell around before
1718 installing anything can help undo problems. Not having a root shell
1719 around can lead to problems if pam has changed too much from your
1720 starting point to allow continued authentication after the upgrade.
1722 This file should be read as a log of events. When a later event changes
1723 information of a prior event, the prior event should not be deleted.
1724 Instead, a pointer to the entry with the new information should be
1725 placed in the old entry. Readers of this file should also sanity check
1726 older entries before relying on them blindly. Authors of new entries
1727 should write them with this in mind.
1731 When upgrading the boot ZFS pool to a new version, always follow
1734 1.) recompile and reinstall the ZFS boot loader and boot block
1735 (this is part of "make buildworld" and "make installworld")
1737 2.) update the ZFS boot block on your boot drive
1739 The following example updates the ZFS boot block on the first
1740 partition (freebsd-boot) of a GPT partitioned drive ada0:
1741 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1743 Non-boot pools do not need these updates.
1747 If you are updating from a prior version of FreeBSD (even one just
1748 a few days old), you should follow this procedure. It is the most
1749 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1751 make kernel-toolchain
1752 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1753 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1755 To test a kernel once
1756 ---------------------
1757 If you just want to boot a kernel once (because you are not sure
1758 if it works, or if you want to boot a known bad kernel to provide
1759 debugging information) run
1760 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1761 nextboot -k testkernel
1763 To just build a kernel when you know that it won't mess you up
1764 --------------------------------------------------------------
1765 This assumes you are already running a CURRENT system. Replace
1766 ${arch} with the architecture of your machine (e.g. "i386",
1767 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1769 cd src/sys/${arch}/conf
1770 config KERNEL_NAME_HERE
1771 cd ../compile/KERNEL_NAME_HERE
1776 If this fails, go to the "To build a kernel" section.
1778 To rebuild everything and install it on the current system.
1779 -----------------------------------------------------------
1780 # Note: sometimes if you are running current you gotta do more than
1781 # is listed here if you are upgrading from a really old current.
1783 <make sure you have good level 0 dumps>
1785 make kernel KERNCONF=YOUR_KERNEL_HERE
1787 <reboot in single user> [3]
1794 To cross-install current onto a separate partition
1795 --------------------------------------------------
1796 # In this approach we use a separate partition to hold
1797 # current's root, 'usr', and 'var' directories. A partition
1798 # holding "/", "/usr" and "/var" should be about 2GB in
1801 <make sure you have good level 0 dumps>
1804 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1805 <maybe newfs current's root partition>
1806 <mount current's root partition on directory ${CURRENT_ROOT}>
1807 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1808 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1809 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1810 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1811 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1812 <reboot into current>
1813 <do a "native" rebuild/install as described in the previous section>
1814 <maybe install compatibility libraries from ports/misc/compat*>
1818 To upgrade in-place from stable to current
1819 ----------------------------------------------
1820 <make sure you have good level 0 dumps>
1822 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1824 <reboot in single user> [3]
1831 Make sure that you've read the UPDATING file to understand the
1832 tweaks to various things you need. At this point in the life
1833 cycle of current, things change often and you are on your own
1834 to cope. The defaults can also change, so please read ALL of
1835 the UPDATING entries.
1837 Also, if you are tracking -current, you must be subscribed to
1838 freebsd-current@freebsd.org. Make sure that before you update
1839 your sources that you have read and understood all the recent
1840 messages there. If in doubt, please track -stable which has
1841 much fewer pitfalls.
1843 [1] If you have third party modules, such as vmware, you
1844 should disable them at this point so they don't crash your
1847 [3] From the bootblocks, boot -s, and then do
1852 adjkerntz -i # if CMOS is wall time
1853 Also, when doing a major release upgrade, it is required that
1854 you boot into single user mode to do the installworld.
1856 [4] Note: This step is non-optional. Failure to do this step
1857 can result in a significant reduction in the functionality of the
1858 system. Attempting to do it by hand is not recommended and those
1859 that pursue this avenue should read this file carefully, as well
1860 as the archives of freebsd-current and freebsd-hackers mailing lists
1861 for potential gotchas. The -U option is also useful to consider.
1862 See mergemaster(8) for more information.
1864 [5] Usually this step is a noop. However, from time to time
1865 you may need to do this if you get unknown user in the following
1866 step. It never hurts to do it all the time. You may need to
1867 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1868 install) after the buildworld before this step if you last updated
1869 from current before 20130425 or from -stable before 20130430.
1871 [6] This only deletes old files and directories. Old libraries
1872 can be deleted by "make delete-old-libs", but you have to make
1873 sure that no program is using those libraries anymore.
1875 [8] The new kernel must be able to run existing binaries used by
1876 an installworld. When upgrading across major versions, the new
1877 kernel's configuration must include the correct COMPAT_FREEBSD<n>
1878 option for existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x
1879 binaries). Failure to do so may leave you with a system that is
1880 hard to boot to recover. A GENERIC kernel will include suitable
1881 compatibility options to run binaries from older branches.
1883 Make sure that you merge any new devices from GENERIC since the
1884 last time you updated your kernel config file.
1886 [9] When checking out sources, you must include the -P flag to have
1887 cvs prune empty directories.
1889 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1890 "?=" instead of the "=" assignment operator, so that buildworld can
1891 override the CPUTYPE if it needs to.
1893 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1894 not on the command line, or in /etc/make.conf. buildworld will
1895 warn if it is improperly defined.
1898 This file contains a list, in reverse chronological order, of major
1899 breakages in tracking -current. It is not guaranteed to be a complete
1900 list of such breakages, and only contains entries since September 23, 2011.
1901 If you need to see UPDATING entries from before that date, you will need
1902 to fetch an UPDATING file from an older FreeBSD release.
1904 Copyright information:
1906 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1908 Redistribution, publication, translation and use, with or without
1909 modification, in full or in part, in any form or format of this
1910 document are permitted without further permission from the author.
1912 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1913 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1914 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1915 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1916 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1917 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1918 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1919 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1920 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1921 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1922 POSSIBILITY OF SUCH DAMAGE.
1924 Contact Warner Losh if you have any questions about your use of