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.
20 Iflib is no longer unconditionally compiled into the kernel. Drivers
21 using iflib and statically compiled into the kernel, now require
22 the 'device iflib' config option. For the same drivers loaded as
23 modules on kernels not having 'device iflib', the iflib.ko module
24 is loaded automatically.
27 r342561 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
28 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
29 servers that have vfs.nfsd.nfs_privport set will only allow mounts
30 from clients using a reserved port#. Since both the FreeBSD and Linux
31 NFSv4 clients use reserved port#s by default, this should not affect
35 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
36 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
37 it produces broken binaries when ifuncs are in use. Users needing
38 GNU ld should install the binutils port or package.
41 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
42 has been converted to a port (misc/ctm) and will be removed from
43 FreeBSD-13. A depreciation warning will be printed to stderr by
44 the ctm command, but the functionality will remain in base for all
48 The stable/12 branch has been created in subversion from head
52 Ports for the DRM modules have been simplified. Now, amd64 users should
53 just install the drm-kmod port. All others should install
56 Graphics hardware that's newer than about 2010 usually works with
57 drm-kmod. For hardware older than 2013, however, some users will need
58 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
59 than 2008 usually only works in drm-legacy-kmod. The graphics team can
60 only commit to hardware made since 2013 due to the complexity of the
61 market and difficulty to test all the older cards effectively. If you
62 have hardware supported by drm-kmod, you are strongly encouraged to use
63 that as you will get better support.
65 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
66 elsewhere, the drm and drm2 modules will be eliminated from the src base
67 soon (with a limited exception for arm). Please update to the package asap
68 and report any issues to x11@freebsd.org.
70 Generally, anybody using the drm*-kmod packages should add
71 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
72 cross-threading surprises, especially with automatic driver
73 loading from X11 startup. These will become the defaults in 13-current
77 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
78 custom kernel and module loading configuration files must be updated
79 accordingly. Moreover, interfaces previous presented as ixlvN to the
80 system are now exposed as iavfN and network configuration files must
81 be adjusted as necessary.
84 OpenSSL has been updated to version 1.1.1. This update included
85 additional various API changes througout the base system. It is
86 important to rebuild third-party software after upgrading. The value
87 of __FreeBSD_version has been bumped accordingly.
90 The legacy DRM modules and drivers have now been added to the loader's
91 module blacklist, in favor of loading them with kld_list in rc.conf(5).
92 The module blacklist may be overridden with the loader.conf(5)
93 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
97 The cam(4) based nda(4) driver will be used over nvd(4) by default on
98 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
99 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
100 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
104 Reproducible build mode is now on by default, in preparation for
105 FreeBSD 12.0. This eliminates build metadata such as the user,
106 host, and time from the kernel (and uname), unless the working tree
107 corresponds to a modified checkout from a version control system.
108 The previous behavior can be obtained by setting the /etc/src.conf
109 knob WITHOUT_REPRODUCIBLE_BUILD.
112 The Yarrow CSPRNG has been removed from the kernel as it has not been
113 supported by its designers since at least 2003. Fortuna has been the
114 default since FreeBSD-11.
117 devctl freeze/thaw have gone into the tree, the rc scripts have been
118 updated to use them and devmatch has been changed. You should update
119 kernel, userland and rc scripts all at the same time.
122 The default interpreter has been switched from 4th to Lua.
123 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
124 interpreter. If you have custom FORTH code you will need to set
125 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
126 src.conf for the build. This will create default hard links between
127 loader and loader_4th instead of loader and loader_lua, the new default.
128 If you are using UEFI it will create the proper hard link to loader.efi.
130 bhyve uses userboot.so. It remains 4th-only until some issues are solved
131 regarding coexisting with multiple versions of FreeBSD are resolved.
134 ls(1) now respects the COLORTERM environment variable used in other
135 systems and software to indicate that a colored terminal is both
136 supported and desired. If ls(1) is suddenly emitting colors, they may
137 be disabled again by either removing the unwanted COLORTERM from your
138 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
139 may not be observed in a future release.
142 The default pager for most commands has been changed to "less". To
143 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
147 The jedec_ts(4) driver has been removed. A superset of its functionality
148 is available in the jedec_dimm(4) driver, and the manpage for that
149 driver includes migration instructions. If you have "device jedec_ts"
150 in your kernel configuration file, it must be removed.
153 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
154 This should have no effect if the kernel is booted via BIOS/legacy boot.
155 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
156 has a buggy firmware that prevents a successful boot due to use of
160 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
161 support has been removed from the tree. These ports were
162 obsolete and/or known to be broken for many years.
165 loader.efi has been augmented to participate more fully in the
166 UEFI boot manager protocol. loader.efi will now look at the
167 BootXXXX environment variable to determine if a specific kernel
168 or root partition was specified. XXXX is derived from BootCurrent.
169 efibootmgr(8) manages these standard UEFI variables.
172 zfsloader's functionality has now been folded into loader.
173 zfsloader is no longer necessary once you've updated your
174 boot blocks. For a transition period, we will install a
175 hardlink for zfsloader to loader to allow a smooth transition
176 until the boot blocks can be updated (hard link because old
177 zfs boot blocks don't understand symlinks).
180 ARM64 now have efifb support, if you want to have serial console
181 on your arm64 board when an screen is connected and the bootloader
182 setup a frambuffer for us to use, just add :
186 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
187 an screen connected as the firmware will setup a framebuffer are that
188 u-boot will expose as an EFI framebuffer.
191 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
192 or take steps to update /etc/passwd before doing installworld on
193 existing systems. Do not skip the "mergemaster -Fp" step before
194 installworld, as described in the update procedures near the bottom
195 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
196 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
197 the ntp config file contain options that change file/dir locations.
198 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
199 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
200 taking steps to ensure that all required files/dirs are accessible
204 Big endian arm support has been removed.
207 The static environment setup in kernel configs is no longer mutually
208 exclusive with the loader(8) environment by default. In order to
209 restore the previous default behavior of disabling the loader(8)
210 environment if a static environment is present, you must specify
211 loader_env.disabled=1 in the static environment.
214 The ABI of syscalls used by management tools like sockstat and
215 netstat has been broken to allow 32-bit binaries to work on
216 64-bit kernels without modification. These programs will need
217 to match the kernel in order to function. External programs may
218 require minor modifications to accommodate a change of type in
219 structures from pointers to 64-bit virtual addresses.
222 On i386 and amd64 atomics are now inlined. Out of tree modules using
223 atomics will need to be rebuilt.
226 The '%I' format in the kern.corefile sysctl limits the number of
227 core files that a process can generate to the number stored in the
228 debug.ncores sysctl. The '%I' format is replaced by the single digit
229 index. Previously, if all indexes were taken the kernel would overwrite
230 only a core file with the highest index in a filename.
231 Currently the system will create a new core file if there is a free
232 index or if all slots are taken it will overwrite the oldest one.
235 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
236 6.0.1. Please see the 20141231 entry below for information about
237 prerequisites and upgrading, if you are not already using clang 3.5.0
241 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
242 needed to be changed to work with it. This change was made with r335763
243 and requires a mergemaster / etcupdate / etc to update the installed file.
246 r334930 changed the interface between the NFS modules, so they all
247 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
250 As of r334391 lld is the default amd64 system linker; it is installed
251 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
255 The kernel / userland interface for devinfo changed, so you'll
256 need a new kernel and userland as a pair for it to work (rebuilding
257 lib/libdevinfo is all that's required). devinfo and devmatch will
258 not work, but everything else will when there's a mismatch.
261 The on-disk format for hwpmc callchain records has changed to include
262 threadid corresponding to a given record. This changes the field offsets
263 and thus requires that libpmcstat be rebuilt before using a kernel
267 The vxge(4) driver has been removed. This driver was introduced into
268 HEAD one week before the Exar left the Ethernet market and is not
269 known to be used. If you have device vxge in your kernel config file
273 The amd64 kernel now requires a ld that supports ifunc to produce a
274 working kernel, either lld or a newer binutils. lld is built by default
275 on amd64, and the 'buildkernel' target uses it automatically. However,
276 it is not the default linker, so building the kernel the traditional
277 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
278 binutils port/package). lld will soon be default, and this requirement
281 NOTE: As of r334391 lld is the default system linker on amd64, and no
282 workaround is necessary.
285 The nxge(4) driver has been removed. This driver was for PCI-X 10g
286 cards made by s2io/Neterion. The company was aquired by Exar and
287 no longer sells or supports Ethernet products. If you have device
288 nxge in your kernel config file it must be removed.
291 The tz database (tzdb) has been updated to 2018e. This version more
292 correctly models time stamps in time zones with negative DST such as
293 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
294 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
295 time zone abbreviations and the tm_isdst flag.
298 The ixgb(4) driver has been removed. This driver was for an early and
299 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
300 quickly shifted to the long lived ixgbe family. If you have device
301 ixgb in your kernel config file it must be removed.
304 The lmc(4) driver has been removed. This was a WAN interface
305 card that was already reportedly rare in 2003, and had an ambiguous
306 license. If you have device lmc in your kernel config file it must
310 Support for Arcnet networks has been removed. If you have device
311 arcnet or device cm in your kernel config file they must be
315 Support for FDDI networks has been removed. If you have device
316 fddi or device fpa in your kernel config file they must be
320 In addition to supporting RFC 3164 formatted messages, the
321 syslogd(8) service is now capable of parsing RFC 5424 formatted
322 log messages. The main benefit of using RFC 5424 is that clients
323 may now send log messages with timestamps containing year numbers,
324 microseconds and time zone offsets.
326 Similarly, the syslog(3) C library function has been altered to
327 send RFC 5424 formatted messages to the local system logging
328 daemon. On systems using syslogd(8), this change should have no
329 negative impact, as long as syslogd(8) and the C library are
330 updated at the same time. On systems using a different system
331 logging daemon, it may be necessary to make configuration
332 adjustments, depending on the software used.
334 When using syslog-ng, add the 'syslog-protocol' flag to local
335 input sources to enable parsing of RFC 5424 formatted messages:
338 unix-dgram("/var/run/log" flags(syslog-protocol));
341 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
342 of the 'imuxsock' module to let messages be processed by the
343 regular RFC 3164/5424 parsing pipeline:
345 module(load="imuxsock" SysSock.UseSpecialParser="off")
347 Do note that these changes only affect communication between local
348 applications and syslogd(8). The format that syslogd(8) uses to
349 store messages on disk or forward messages to other systems
350 remains unchanged. syslogd(8) still uses RFC 3164 for these
351 purposes. Options to customize this behaviour will be added in the
352 future. Utilities that process log files stored in /var/log are
353 thus expected to continue to function as before.
355 __FreeBSD_version has been incremented to 1200061 to denote this
359 Support for token ring networks has been removed. If you
360 have "device token" in your kernel config you should remove
361 it. No device drivers supported token ring.
364 makefs was modified to be able to tag ISO9660 El Torito boot catalog
365 entries as EFI instead of overloading the i386 tag as done previously.
366 The amd64 mkisoimages.sh script used to build amd64 ISO images for
367 release was updated to use this. This may mean that makefs must be
368 updated before "make cdrom" can be run in the release directory. This
369 should be as simple as:
371 $ cd $SRCDIR/usr.sbin/makefs
372 $ make depend all install
375 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
376 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
377 Co-existance for the transition period will come shortly. Booting is a
378 complex environment and test coverage for Lua-enabled loaders has been
379 thin, so it would be prudent to assume it might not work and make
380 provisions for backup boot methods.
383 devmatch functionality has been turned on in devd. It will automatically
384 load drivers for unattached devices. This may cause unexpected drivers to
385 be loaded. Please report any problems to current@ and imp@freebsd.org.
388 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
389 6.0.0. Please see the 20141231 entry below for information about
390 prerequisites and upgrading, if you are not already using clang 3.5.0
394 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
395 This means it is used to link the kernel and userland libraries and
396 executables, but is not yet installed as /usr/bin/ld by default.
398 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
399 WITHOUT_LLD_BOOTSTRAP=yes
402 On i386, pmtimer has been removed. Its functionality has been folded
403 into apm. It was a no-op on ACPI in current for a while now (but was still
404 needed on i386 in FreeBSD 11 and earlier). Users may need to remove it
405 from kernel config files.
408 The use of RSS hash from the network card aka flowid has been
409 disabled by default for lagg(4) as it's currently incompatible with
410 the lacp and loadbalance protocols.
412 This can be re-enabled by setting the following in loader.conf:
413 net.link.lagg.default_use_flowid="1"
416 The SW_WATCHDOG option is no longer necessary to enable the
417 hardclock-based software watchdog if no hardware watchdog is
418 configured. As before, SW_WATCHDOG will cause the software
419 watchdog to be enabled even if a hardware watchdog is configured.
422 r326887 fixes the issue described in the 20171214 UPDATING entry.
423 r326888 flips the switch back to building GELI support always.
426 r362593 broke ZFS + GELI support for reasons unknown. However,
427 it also broke ZFS support generally, so GELI has been turned off
428 by default as the lesser evil in r326857. If you boot off ZFS and/or
429 GELI, it might not be a good time to update.
432 PowerPC users must update loader(8) by rebuilding world before
433 installing a new kernel, as the protocol connecting them has
434 changed. Without the update, loader metadata will not be passed
435 successfully to the kernel and users will have to enter their
436 root partition at the kernel mountroot prompt to continue booting.
437 Newer versions of loader can boot old kernels without issue.
440 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
441 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
442 to WITH/OUT_LOADER_GELI.
445 The naive and non-compliant support of posix_fallocate(2) in ZFS
446 has been removed as of r325320. The system call now returns EINVAL
447 when used on a ZFS file. Although the new behavior complies with the
448 standard, some consumers are not prepared to cope with it.
449 One known victim is lld prior to r325420.
452 Building in a FreeBSD src checkout will automatically create object
453 directories now rather than store files in the current directory if
454 'make obj' was not ran. Calling 'make obj' is no longer necessary.
455 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
456 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
460 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
461 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
462 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
463 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
464 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
465 The UNIFIED_OBJDIR option is a transitional feature that will be
466 removed for 12.0 release; please migrate to the new format for any
467 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
468 than hardcoding paths.
471 The native-xtools target no longer installs the files by default to the
472 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
473 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
476 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
477 options are changing from controlling the build if defined / undefined
478 to controlling the build with explicit 'yes' or 'no' values. They will
479 shift to WITH/WITHOUT options to match other options in the system.
482 libstand has turned into a private library for sys/boot use only.
483 It is no longer supported as a public interface outside of sys/boot.
486 The arm port has split armv6 into armv6 and armv7. armv7 is now
487 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
488 and are running a kernel from before r324363, you will need to add
489 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
492 When building multiple kernels using KERNCONF, non-existent KERNCONF
493 files will produce an error and buildkernel will fail. Previously
494 missing KERNCONF files silently failed giving no indication as to
495 why, only to subsequently discover during installkernel that the
496 desired kernel was never built in the first place.
499 The default serial number format for CTL LUNs has changed. This will
500 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
501 or iSCSI clients care about their LUNs' serial numbers. Users who
502 require serial number stability should hardcode serial numbers in
506 For 32-bit arm compiled for hard-float support, soft-floating point
507 binaries now always get their shared libraries from
508 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
509 /usr/libsoft also existed). Only users with a hard-float ld.so, but
510 soft-float everything else should be affected.
513 The geli password typed at boot is now hidden. To restore the previous
514 behavior, see geli(8) for configuration options.
517 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
518 sysctl values. Minor nit, but requires a rebuild of both world/kernel
522 "make check" behavior (made in ^/head@r295380) has been changed to
523 execute from a limited sandbox, as opposed to executing from
527 - The "beforecheck" and "aftercheck" targets are now specified.
528 - ${CHECKDIR} (added in commit noted above) has been removed.
529 - Legacy behavior can be enabled by setting
530 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
532 If the limited sandbox mode is enabled, "make check" will execute
533 "make distribution", then install, execute the tests, and clean up the
534 sandbox if successful.
536 The "make distribution" and "make install" targets are typically run as
537 root to set appropriate permissions and ownership at installation time.
538 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
539 environment if executing "make check" with limited sandbox mode using
540 an unprivileged user.
543 Since the switch to GPT disk labels, fsck for UFS/FFS has been
544 unable to automatically find alternate superblocks. As of r322297,
545 the information needed to find alternate superblocks has been
546 moved to the end of the area reserved for the boot block.
547 Filesystems created with a newfs of this vintage or later
548 will create the recovery information. If you have a filesystem
549 created prior to this change and wish to have a recovery block
550 created for your filesystem, you can do so by running fsck in
551 foreground mode (i.e., do not use the -p or -y options). As it
552 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
553 to which you should answer yes.
556 As of r321665, an NFSv4 server configuration that services
557 Kerberos mounts or clients that do not support the uid/gid in
558 owner/owner_group string capability, must explicitly enable
559 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
560 machine's /etc/rc.conf file.
563 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
564 Please see the 20141231 entry below for information about prerequisites
565 and upgrading, if you are not already using clang 3.5.0 or higher.
568 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
569 r-commands (rlogin, rsh, etc.) to be built with the base system.
572 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
573 a very major ABI incompatible change, so users of FreeBSD/powerpc must
574 be careful when performing source upgrades. It is best to run
575 'make installworld' from an alternate root system, either a live
576 CD/memory stick, or a temporary root partition. Additionally, all ports
577 must be recompiled. powerpc64 is largely unaffected, except in the case
578 of 32-bit compatibility. All 32-bit binaries will be affected.
581 Forward compatibility for the "ino64" project have been committed. This
582 will allow most new binaries to run on older kernels in a limited
583 fashion. This prevents many of the common foot-shooting actions in the
584 upgrade as well as the limited ability to roll back the kernel across
585 the ino64 upgrade. Complicated use cases may not work properly, though
586 enough simpler ones work to allow recovery in most situations.
589 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
590 if you require the GPL compiler.
593 The internal ABI used for communication between the NFS kernel modules
594 was changed by r320085, so __FreeBSD_version was bumped to
595 ensure all the NFS related modules are updated together.
598 The ABI of struct event was changed by extending the data
599 member to 64bit and adding ext fields. For upgrade, same
600 precautions as for the entry 20170523 "ino64" must be
604 The GNU roff toolchain has been removed from base. To render manpages
605 which are not supported by mandoc(1), man(1) can fallback on GNU roff
606 from ports (and recommends to install it).
607 To render roff(7) documents, consider using GNU roff from ports or the
608 heirloom doctools roff toolchain from ports via pkg install groff or
609 via pkg install heirloom-doctools.
612 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
613 smaller runtime footprint builds. This is useful for embedded systems
614 which only require one chipset support.
616 If you load it as a module, make sure this is in /boot/loader.conf:
620 This will load the HAL, all chip/RF backends and if_ath_pci.
621 If you have if_ath_pci in /boot/loader.conf, ensure it is after
622 if_ath or it will not load any HAL chipset support.
624 If you want to selectively load things (eg on ye cheape ARM/MIPS
625 platforms where RAM is at a premium) you should:
628 * load the chip modules in question
629 * load ath_rate, ath_dfs
631 * load if_ath_pci and/or if_ath_ahb depending upon your particular
632 bus bind type - this is where probe/attach is done.
634 For further comments/feedback, poke adrian@ .
637 The "ino64" 64-bit inode project has been committed, which extends
638 a number of types to 64 bits. Upgrading in place requires care and
639 adherence to the documented upgrade procedure.
641 If using a custom kernel configuration ensure that the
642 COMPAT_FREEBSD11 option is included (as during the upgrade the
643 system will be running the ino64 kernel with the existing world).
645 For the safest in-place upgrade begin by removing previous build
646 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
647 full procedure documented below under the heading "To rebuild
648 everything and install it on the current system." Specifically,
649 a reboot is required after installing the new kernel before
653 The NATM framework including the en(4), fatm(4), hatm(4), and
654 patm(4) devices has been removed. Consumers should plan a
655 migration before the end-of-life date for FreeBSD 11.
658 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
659 diff has not been implemented, if those are needed a newer version of
660 GNU diff is available via the diffutils package under the gdiff name.
663 As of r316810 for ipfilter, keep frags is no longer assumed when
664 keep state is specified in a rule. r316810 aligns ipfilter with
665 documentation in man pages separating keep frags from keep state.
666 This allows keep state to be specified without forcing keep frags
667 and allows keep frags to be specified independently of keep state.
668 To maintain previous behaviour, also specify keep frags with
669 keep state (as documented in ipf.conf.5).
672 arm64 builds now use the base system LLD 4.0.0 linker by default,
673 instead of requiring that the aarch64-binutils port or package be
674 installed. To continue using aarch64-binutils, set
675 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
678 The UDP optimization in entry 20160818 that added the sysctl
679 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
680 packets will no longer be treated as L3 broadcast packets.
683 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
684 use any explicitly assigned loopback address available in the jail
685 instead of using the first assigned address of the jail.
688 The ctl.ko module no longer implements the iSCSI target frontend:
689 cfiscsi.ko does instead.
691 If building cfiscsi.ko as a kernel module, the module can be loaded
692 via one of the following methods:
693 - `cfiscsi_load="YES"` in loader.conf(5).
694 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
695 - ctladm(8)/ctld(8), when compiled with iSCSI support
696 (`WITH_ISCSI=yes` in src.conf(5))
698 Please see cfiscsi(4) for more details.
701 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
702 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
703 same source (previously, the dependency of mmcsd.ko on mmc.ko was
704 missing, but mmcsd.ko now will refuse to load if it is incompatible
708 The syntax of ipfw(8) named states was changed to avoid ambiguity.
709 If you have used named states in the firewall rules, you need to modify
710 them after installworld and before rebooting. Now named states must
711 be prefixed with colon.
714 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
715 removed as the userland we provide cannot use them. The KMS version
716 (sys/dev/drm2) supports the same hardware.
719 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
720 Please see the 20141231 entry below for information about prerequisites
721 and upgrading, if you are not already using clang 3.5.0 or higher.
724 The code that provides support for ZFS .zfs/ directory functionality
725 has been reimplemented. It's not possible now to create a snapshot
726 by mkdir under .zfs/snapshot/. That should be the only user visible
730 EISA bus support has been removed. The WITH_EISA option is no longer
734 MCA bus support has been removed.
737 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
738 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
741 The EM_MULTIQUEUE kernel configuration option is deprecated now that
742 the em(4) driver conforms to iflib specifications.
745 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
746 IFLIB. If you have a custom kernel configuration that excludes em(4)
747 but you use igb(4), you need to re-add em(4) to your custom configuration.
750 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
751 Please see the 20141231 entry below for information about prerequisites
752 and upgrading, if you are not already using clang 3.5.0 or higher.
755 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
756 Please see the 20141231 entry below for information about prerequisites
757 and upgrading, if you are not already using clang 3.5.0 or higher.
760 The layout of the pmap structure has changed for powerpc to put the pmap
761 statistics at the front for all CPU variations. libkvm(3) and all tools
762 that link against it need to be recompiled.
765 isl(4) and cyapa(4) drivers now require a new driver,
766 chromebook_platform(4), to work properly on Chromebook-class hardware.
767 On other types of hardware the drivers may need to be configured using
768 device hints. Please see the corresponding manual pages for details.
771 The urtwn(4) driver was merged into rtwn(4) and now consists of
772 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
774 Also, firmware for RTL8188CE was renamed due to possible name
775 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
778 GNU rcs has been removed from base. It is available as packages:
779 - rcs: Latest GPLv3 GNU rcs version.
780 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
784 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
785 modules now requires that the kernel configuration contain the
786 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
789 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
790 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
793 Relocatable object files with the extension of .So have been renamed
794 to use an extension of .pico instead. The purpose of this change is
795 to avoid a name clash with shared libraries on case-insensitive file
796 systems. On those file systems, foo.So is the same file as foo.so.
799 GNU rcs has been turned off by default. It can (temporarily) be built
800 again by adding WITH_RCS knob in src.conf.
801 Otherwise, GNU rcs is available from packages:
802 - rcs: Latest GPLv3 GNU rcs version.
803 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
806 The backup_uses_rcs functionality has been removed from rc.subr.
809 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
810 two separate components, QUEUE_MACRO_DEBUG_TRACE and
811 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
812 QUEUE_MACRO_DEBUG behavior.
815 r304787 changed some ioctl interfaces between the iSCSI userspace
816 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
817 rebuilt to work with new kernels. __FreeBSD_version has been bumped
821 The UDP receive code has been updated to only treat incoming UDP
822 packets that were addressed to an L2 broadcast address as L3
823 broadcast packets. It is not expected that this will affect any
824 standards-conforming UDP application. The new behaviour can be
825 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
829 Remove the openbsd_poll system call.
830 __FreeBSD_version has been bumped because of this.
833 The stable/11 branch has been created from head@r302406.
836 The libc stub for the pipe(2) system call has been replaced with
837 a wrapper that calls the pipe2(2) system call and the pipe(2)
838 system call is now only implemented by the kernels that include
839 "options COMPAT_FREEBSD10" in their config file (this is the
840 default). Users should ensure that this option is enabled in
841 their kernel or upgrade userspace to r302092 before upgrading their
845 CAM will now strip leading spaces from SCSI disks' serial numbers.
846 This will affect users who create UFS filesystems on SCSI disks using
847 those disk's diskid device nodes. For example, if /etc/fstab
848 previously contained a line like
849 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
850 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
851 transforms like gmirror may also be affected. ZFS users should
855 The bitstring(3) API has been updated with new functionality and
856 improved performance. But it is binary-incompatible with the old API.
857 Objects built with the new headers may not be linked against objects
858 built with the old headers.
861 The brk and sbrk functions have been removed from libc on arm64.
862 Binutils from ports has been updated to not link to these
863 functions and should be updated to the latest version before
864 installing a new libc.
867 The armv6 port now defaults to hard float ABI. Limited support
868 for running both hardfloat and soft float on the same system
869 is available using the libraries installed with -DWITH_LIBSOFT.
870 This has only been tested as an upgrade path for installworld
871 and packages may fail or need manual intervention to run. New
872 packages will be needed.
874 To update an existing self-hosted armv6hf system, you must add
875 TARGET_ARCH=armv6 on the make command line for both the build
876 and the install steps.
879 Kernel modules compiled outside of a kernel build now default to
880 installing to /boot/modules instead of /boot/kernel. Many kernel
881 modules built this way (such as those in ports) already overrode
882 KMODDIR explicitly to install into /boot/modules. However,
883 manually building and installing a module from /sys/modules will
884 now install to /boot/modules instead of /boot/kernel.
887 The CAM I/O scheduler has been committed to the kernel. There should be
888 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
889 list of known rogues that claim support for this but actually corrupt
890 data is believed to be complete, be on the lookout for data
891 corruption. The known rogue list is believed to be complete:
893 o Crucial MX100, M550 drives with MU01 firmware.
894 o Micron M510 and M550 drives with MU01 firmware.
895 o Micron M500 prior to MU07 firmware
896 o Samsung 830, 840, and 850 all firmwares
897 o FCCT M500 all firmwares
899 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
900 with working NCQ TRIM. For Micron branded drives, see your sales rep for
901 updated firmware. Black listed drives will work correctly because these
902 drives work correctly so long as no NCQ TRIMs are sent to them. Given
903 this list is the same as found in Linux, it's believed there are no
904 other rogues in the market place. All other models from the above
907 To be safe, if you are at all concerned, you can quirk each of your
908 drives to prevent NCQ from being sent by setting:
909 kern.cam.ada.X.quirks="0x2"
910 in loader.conf. If the drive requires the 4k sector quirk, set the
914 The FAST_DEPEND build option has been removed and its functionality is
915 now the one true way. The old mkdep(1) style of 'make depend' has
916 been removed. See 20160311 for further details.
919 Resource range types have grown from unsigned long to uintmax_t. All
920 drivers, and anything using libdevinfo, need to be recompiled.
923 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
924 builds. It no longer runs mkdep(1) during 'make depend', and the
925 'make depend' stage can safely be skipped now as it is auto ran
926 when building 'make all' and will generate all SRCS and DPSRCS before
927 building anything else. Dependencies are gathered at compile time with
928 -MF flags kept in separate .depend files per object file. Users should
929 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
933 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
934 kernel modules. Therefore, if you load any kernel modules at boot time,
935 please install the boot loaders after you install the kernel, but before
939 make buildkernel KERNCONF=YOUR_KERNEL_HERE
940 make installkernel KERNCONF=YOUR_KERNEL_HERE
941 make -C sys/boot install
942 <reboot in single user>
944 Then follow the usual steps, described in the General Notes section,
948 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
949 see the 20141231 entry below for information about prerequisites and
950 upgrading, if you are not already using clang 3.5.0 or higher.
953 The AIO subsystem is now a standard part of the kernel. The
954 VFS_AIO kernel option and aio.ko kernel module have been removed.
955 Due to stability concerns, asynchronous I/O requests are only
956 permitted on sockets and raw disks by default. To enable
957 asynchronous I/O requests on all file types, set the
958 vfs.aio.enable_unsafe sysctl to a non-zero value.
961 The ELF object manipulation tool objcopy is now provided by the
962 ELF Tool Chain project rather than by GNU binutils. It should be a
963 drop-in replacement, with the addition of arm64 support. The
964 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
965 to obtain the GNU version if necessary.
968 Building ZFS pools on top of zvols is prohibited by default. That
969 feature has never worked safely; it's always been prone to deadlocks.
970 Using a zvol as the backing store for a VM guest's virtual disk will
971 still work, even if the guest is using ZFS. Legacy behavior can be
972 restored by setting vfs.zfs.vol.recursive=1.
975 The NONE and HPN patches has been removed from OpenSSH. They are
976 still available in the security/openssh-portable port.
979 With the addition of ypldap(8), a new _ypldap user is now required
980 during installworld. "mergemaster -p" can be used to add the user
981 prior to installworld, as documented in the handbook.
984 The tftp loader (pxeboot) now uses the option root-path directive. As a
985 consequence it no longer looks for a pxeboot.4th file on the tftp
986 server. Instead it uses the regular /boot infrastructure as with the
990 The code to start recording plug and play data into the modules has
991 been committed. While the old tools will properly build a new kernel,
992 a number of warnings about "unknown metadata record 4" will be produced
993 for an older kldxref. To avoid such warnings, make sure to rebuild
994 the kernel toolchain (or world). Make sure that you have r292078 or
995 later when trying to build 292077 or later before rebuilding.
998 Debug data files are now built by default with 'make buildworld' and
999 installed with 'make installworld'. This facilitates debugging but
1000 requires more disk space both during the build and for the installed
1001 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1005 r291527 changed the internal interface between the nfsd.ko and
1006 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1007 __FreeBSD_version has been bumped because of this.
1010 Add support for unicode collation strings leads to a change of
1011 order of files listed by ls(1) for example. To get back to the old
1012 behaviour, set LC_COLLATE environment variable to "C".
1014 Databases administrators will need to reindex their databases given
1015 collation results will be different.
1017 Due to a bug in install(1) it is recommended to remove the ancient
1018 locales before running make installworld.
1020 rm -rf /usr/share/locale/*
1023 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1024 libcrypto.so.7 or libssl.so.7 must be recompiled.
1027 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1028 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1029 should be replaced with isp_2400 and isp_2500 modules respectively.
1032 The build previously allowed using 'make -n' to not recurse into
1033 sub-directories while showing what commands would be executed, and
1034 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1035 and 'make -N' will not.
1038 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1039 and etcupdate will now use this file. A custom sendmail.cf is now
1040 updated via this mechanism rather than via installworld. If you had
1041 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1042 want to remove the exclusion or change it to "always install".
1043 /etc/mail/sendmail.cf is now managed the same way regardless of
1044 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1045 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1048 Compatibility shims for legacy ATA device names have been removed.
1049 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1050 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1051 environment variables, /dev/ad* and /dev/ar* symbolic links.
1054 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1055 Please see the 20141231 entry below for information about prerequisites
1056 and upgrading, if you are not already using clang 3.5.0 or higher.
1059 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1060 and renamed from .symbols to .debug. This reduces the size requirements
1061 on the boot partition or file system and provides consistency with
1062 userland debug files.
1064 When using the supported kernel installation method the
1065 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1066 as is done with /boot/kernel.
1068 Developers wishing to maintain the historical behavior of installing
1069 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1072 The wireless drivers had undergone changes that remove the 'parent
1073 interface' from the ifconfig -l output. The rc.d network scripts
1074 used to check presence of a parent interface in the list, so old
1075 scripts would fail to start wireless networking. Thus, etcupdate(3)
1076 or mergemaster(8) run is required after kernel update, to update your
1077 rc.d scripts in /etc.
1080 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1081 These configurations are now automatically interpreted as
1082 'scrub fragment reassemble'.
1085 Kernel-loadable modules for the random(4) device are back. To use
1086 them, the kernel must have
1089 options RANDOM_LOADABLE
1091 kldload(8) can then be used to load random_fortuna.ko
1092 or random_yarrow.ko. Please note that due to the indirect
1093 function calls that the loadable modules need to provide,
1094 the build-in variants will be slightly more efficient.
1096 The random(4) kernel option RANDOM_DUMMY has been retired due to
1097 unpopularity. It was not all that useful anyway.
1100 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1101 Control over building the ELF Tool Chain tools is now provided by
1102 the WITHOUT_TOOLCHAIN knob.
1105 The polarity of Pulse Per Second (PPS) capture events with the
1106 uart(4) driver has been corrected. Prior to this change the PPS
1107 "assert" event corresponded to the trailing edge of a positive PPS
1108 pulse and the "clear" event was the leading edge of the next pulse.
1110 As the width of a PPS pulse in a typical GPS receiver is on the
1111 order of 1 millisecond, most users will not notice any significant
1112 difference with this change.
1114 Anyone who has compensated for the historical polarity reversal by
1115 configuring a negative offset equal to the pulse width will need to
1116 remove that workaround.
1119 The default group assigned to /dev/dri entries has been changed
1120 from 'wheel' to 'video' with the id of '44'. If you want to have
1121 access to the dri devices please add yourself to the video group
1124 # pw groupmod video -m $USER
1127 The menu.rc and loader.rc files will now be replaced during
1128 upgrades. Please migrate local changes to menu.rc.local and
1129 loader.rc.local instead.
1132 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1133 strings and strip have been removed. The src.conf(5) knob
1134 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1137 As ZFS requires more kernel stack pages than is the default on some
1138 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1139 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1141 Please consider using 'options KSTACK_PAGES=X' where X is greater
1142 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1145 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1146 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1147 default, i.e., they will not contain "::". For example, instead
1148 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1149 to have a more specific match, such as different map entries for
1150 IPv6:0:0 vs IPv6:0. This change requires that configuration
1151 data (including maps, files, classes, custom ruleset, etc.) must
1152 use the same format, so make certain such configuration data is
1153 upgrading. As a very simple check search for patterns like
1154 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1155 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1156 the cf option UseCompressedIPv6Addresses.
1159 The default kernel entropy-processing algorithm is now
1160 Fortuna, replacing Yarrow.
1162 Assuming you have 'device random' in your kernel config
1163 file, the configurations allow a kernel option to override
1164 this default. You may choose *ONE* of:
1166 options RANDOM_YARROW # Legacy /dev/random algorithm.
1167 options RANDOM_DUMMY # Blocking-only driver.
1169 If you have neither, you get Fortuna. For most people,
1170 read no further, Fortuna will give a /dev/random that works
1171 like it always used to, and the difference will be irrelevant.
1173 If you remove 'device random', you get *NO* kernel-processed
1174 entropy at all. This may be acceptable to folks building
1175 embedded systems, but has complications. Carry on reading,
1176 and it is assumed you know what you need.
1178 *PLEASE* read random(4) and random(9) if you are in the
1179 habit of tweaking kernel configs, and/or if you are a member
1180 of the embedded community, wanting specific and not-usual
1181 behaviour from your security subsystems.
1183 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1184 random', you will NOT have a functioning /dev/random, and
1185 many cryptographic features will not work, including SSH.
1186 You may also find strange behaviour from the random(3) set
1187 of library functions, in particular sranddev(3), srandomdev(3)
1188 and arc4random(3). The reason for this is that the KERN_ARND
1189 sysctl only returns entropy if it thinks it has some to
1190 share, and with RANDOM_DUMMY or no 'device random' this
1194 An additional fix for the issue described in the 20150614 sendmail
1195 entry below has been committed in revision 284717.
1198 FreeBSD's old make (fmake) has been removed from the system. It is
1199 available as the devel/fmake port or via pkg install fmake.
1202 The fix for the issue described in the 20150614 sendmail entry
1203 below has been committed in revision 284436. The work
1204 around described in that entry is no longer needed unless the
1205 default setting is overridden by a confDH_PARAMETERS configuration
1206 setting of '5' or pointing to a 512 bit DH parameter file.
1209 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1210 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1211 and devel/kyua to version 0.20+ and adjust any calling code to work
1212 with Kyuafile and kyua.
1215 The import of openssl to address the FreeBSD-SA-15:10.openssl
1216 security advisory includes a change which rejects handshakes
1217 with DH parameters below 768 bits. sendmail releases prior
1218 to 8.15.2 (not yet released), defaulted to a 512 bit
1219 DH parameter setting for client connections. To work around
1220 this interoperability, sendmail can be configured to use a
1221 2048 bit DH parameter by:
1223 1. Edit /etc/mail/`hostname`.mc
1224 2. If a setting for confDH_PARAMETERS does not exist or
1225 exists and is set to a string beginning with '5',
1226 replace it with '2'.
1227 3. If a setting for confDH_PARAMETERS exists and is set to
1228 a file path, create a new file with:
1229 openssl dhparam -out /path/to/file 2048
1230 4. Rebuild the .cf file:
1231 cd /etc/mail/; make; make install
1232 5. Restart sendmail:
1233 cd /etc/mail/; make restart
1235 A sendmail patch is coming, at which time this file will be
1239 Generation of legacy formatted entries have been disabled by default
1240 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1241 entries were converted to use the new format by default when the new,
1242 machine independent format have been added and supported since FreeBSD
1245 Please see the pwd_mkdb(8) manual page for further details.
1248 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1249 20141231 entry below for information about prerequisites and upgrading,
1250 if you are not already using 3.5.0 or higher.
1253 TI platform code switched to using vendor DTS files and this update
1254 may break existing systems running on Beaglebone, Beaglebone Black,
1257 - dtb files should be regenerated/reinstalled. Filenames are the
1258 same but content is different now
1259 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1260 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1261 addressing scheme is now pin 25 on /dev/gpioc3.
1262 - Pandaboard: /etc/ttys should be updated, serial console device is
1263 now /dev/ttyu2, not /dev/ttyu0
1266 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1267 If you need the GNU extension from groff soelim(1), install groff
1268 from package: pkg install groff, or via ports: textproc/groff.
1271 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1272 defined in symlink(7); previously symlinks were silently ignored.
1275 The const qualifier has been removed from iconv(3) to comply with
1276 POSIX. The ports tree is aware of this from r384038 onwards.
1279 Libraries specified by LIBADD in Makefiles must have a corresponding
1280 DPADD_<lib> variable to ensure correct dependencies. This is now
1281 enforced in src.libnames.mk.
1284 From legacy ata(4) driver was removed support for SATA controllers
1285 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1286 Kernel modules ataahci and ataadaptec were removed completely,
1287 replaced by ahci and mvs modules respectively.
1290 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1291 the 20141231 entry below for information about prerequisites and
1292 upgrading, if you are not already using 3.5.0 or higher.
1295 The 32-bit PowerPC kernel has been changed to a position-independent
1296 executable. This can only be booted with a version of loader(8)
1297 newer than January 31, 2015, so make sure to update both world and
1298 kernel before rebooting.
1301 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1302 but before r278950, the RNG was not seeded properly. Immediately
1303 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1304 ssh keys or openssl keys) that were generated w/ a kernel from that
1305 range. This does not affect programs that directly used /dev/random
1306 or /dev/urandom. All userland uses of arc4random(3) are affected.
1309 The autofs(4) ABI was changed in order to restore binary compatibility
1310 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1311 with the new kernel.
1314 The powerpc64 kernel has been changed to a position-independent
1315 executable. This can only be booted with a new version of loader(8),
1316 so make sure to update both world and kernel before rebooting.
1319 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1320 only release, no new features have been added. Please see the 20141231
1321 entry below for information about prerequisites and upgrading, if you
1322 are not already using 3.5.0.
1325 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1326 taken from the ELF Tool Chain project rather than GNU binutils. They
1327 should be drop-in replacements, with the addition of arm64 support.
1328 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1329 binutils tools, if necessary. See 20150805 for updated information.
1332 The default Unbound configuration now enables remote control
1333 using a local socket. Users who have already enabled the
1334 local_unbound service should regenerate their configuration
1335 by running "service local_unbound setup" as root.
1338 The GNU texinfo and GNU info pages have been removed.
1339 To be able to view GNU info pages please install texinfo from ports.
1342 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1344 As of this release, a prerequisite for building clang, llvm and lldb is
1345 a C++11 capable compiler and C++11 standard library. This means that to
1346 be able to successfully build the cross-tools stage of buildworld, with
1347 clang as the bootstrap compiler, your system compiler or cross compiler
1348 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1349 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1352 On any standard FreeBSD 10.x or 11.x installation, where clang and
1353 libc++ are on by default (that is, on x86 or arm), this should work out
1356 On 9.x installations where clang is enabled by default, e.g. on x86 and
1357 powerpc, libc++ will not be enabled by default, so libc++ should be
1358 built (with clang) and installed first. If both clang and libc++ are
1359 missing, build clang first, then use it to build libc++.
1361 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1362 the instructions for 9.x above.
1364 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1365 default, and do not build clang.
1367 Many embedded systems are resource constrained, and will not be able to
1368 build clang in a reasonable time, or in some cases at all. In those
1369 cases, cross building bootable systems on amd64 is a workaround.
1371 This new version of clang introduces a number of new warnings, of which
1372 the following are most likely to appear:
1376 This warns in two cases, for both C and C++:
1377 * When the code is trying to take the absolute value of an unsigned
1378 quantity, which is effectively a no-op, and almost never what was
1379 intended. The code should be fixed, if at all possible. If you are
1380 sure that the unsigned quantity can be safely cast to signed, without
1381 loss of information or undefined behavior, you can add an explicit
1382 cast, or disable the warning.
1384 * When the code is trying to take an absolute value, but the called
1385 abs() variant is for the wrong type, which can lead to truncation.
1386 If you want to disable the warning instead of fixing the code, please
1387 make sure that truncation will not occur, or it might lead to unwanted
1390 -Wtautological-undefined-compare and
1391 -Wundefined-bool-conversion
1393 These warn when C++ code is trying to compare 'this' against NULL, while
1394 'this' should never be NULL in well-defined C++ code. However, there is
1395 some legacy (pre C++11) code out there, which actively abuses this
1396 feature, which was less strictly defined in previous C++ versions.
1398 Squid and openjdk do this, for example. The warning can be turned off
1399 for C++98 and earlier, but compiling the code in C++11 mode might result
1400 in unexpected behavior; for example, the parts of the program that are
1401 unreachable could be optimized away.
1404 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1405 kernel sources have been removed. The .h files remain, since some
1406 utilities include them. This will need to be fixed later.
1407 If "mount -t oldnfs ..." is attempted, it will fail.
1408 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1409 the utilities will report errors.
1412 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1413 directories to top level SUBDIR variable when their parent
1414 directory is included in LOCAL_DIRS. Users with build systems with
1415 such hierarchies and without SUBDIR entries in the parent
1416 directory Makefiles should add them or add the directories to
1420 faith(4) and faithd(8) have been removed from the base system. Faith
1421 has been obsolete for a very long time.
1424 vt(4), the new console driver, is enabled by default. It brings
1425 support for Unicode and double-width characters, as well as
1426 support for UEFI and integration with the KMS kernel video
1429 You may need to update your console settings in /etc/rc.conf,
1430 most probably the keymap. During boot, /etc/rc.d/syscons will
1431 indicate what you need to do.
1433 vt(4) still has issues and lacks some features compared to
1434 syscons(4). See the wiki for up-to-date information:
1435 https://wiki.freebsd.org/Newcons
1437 If you want to keep using syscons(4), you can do so by adding
1438 the following line to /boot/loader.conf:
1442 pjdfstest has been integrated into kyua as an opt-in test suite.
1443 Please see share/doc/pjdfstest/README for more details on how to
1447 gperf has been removed from the base system for architectures
1448 that use clang. Ports that require gperf will obtain it from the
1452 pjdfstest has been moved from tools/regression/pjdfstest to
1456 At svn r271982, The default linux compat kernel ABI has been adjusted
1457 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1458 update. If you wish to continue using the linux-f10 compat ports,
1459 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1460 encouraged to update their linux-compat packages to linux-c6 during
1461 their next update cycle.
1464 The ofwfb driver, used to provide a graphics console on PowerPC when
1465 using vt(4), no longer allows mmap() of all physical memory. This
1466 will prevent Xorg on PowerPC with some ATI graphics cards from
1467 initializing properly unless x11-servers/xorg-server is updated to
1471 The xdev targets have been converted to using TARGET and
1472 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1475 The default unbound configuration has been modified to address
1476 issues with reverse lookups on networks that use private
1477 address ranges. If you use the local_unbound service, run
1478 "service local_unbound setup" as root to regenerate your
1479 configuration, then "service local_unbound reload" to load the
1483 The GNU texinfo and GNU info pages are not built and installed
1484 anymore, WITH_INFO knob has been added to allow to built and install
1486 UPDATE: see 20150102 entry on texinfo's removal
1489 The GNU readline library is now an INTERNALLIB - that is, it is
1490 statically linked into consumers (GDB and variants) in the base
1491 system, and the shared library is no longer installed. The
1492 devel/readline port is available for third party software that
1496 The Itanium architecture (ia64) has been removed from the list of
1497 known architectures. This is the first step in the removal of the
1501 Commit r268115 has added NFSv4.1 server support, merged from
1502 projects/nfsv4.1-server. Since this includes changes to the
1503 internal interfaces between the NFS related modules, a full
1504 build of the kernel and modules will be necessary.
1505 __FreeBSD_version has been bumped.
1508 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1509 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1510 which differs from the behaviour controlled by this knob.)
1513 Maximal length of the serial number in CTL was increased from 16 to
1514 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1515 and ctld, need to be rebuilt to work with a new kernel.
1518 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1519 1 respectively to match the upstream numbers. They were out of
1520 sync because, when they were originally added to FreeBSD, the
1521 upstream versions were not respected. These libraries are private
1522 and not yet built by default, so renumbering them should be a
1523 non-issue. However, unclean source trees will yield broken test
1524 programs once the operator executes "make delete-old-libs" after a
1525 "make installworld".
1527 Additionally, the atf-sh binary was made private by moving it into
1528 /usr/libexec/. Already-built shell test programs will keep the
1529 path to the old binary so they will break after "make delete-old"
1532 If you are using WITH_TESTS=yes (not the default), wipe the object
1533 tree and rebuild from scratch to prevent spurious test failures.
1534 This is only needed once: the misnumbered libraries and misplaced
1535 binaries have been added to OptionalObsoleteFiles.inc so they will
1536 be removed during a clean upgrade.
1539 Clang and llvm have been upgraded to 3.4.1 release.
1542 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1543 be removed to avoid issues in the future (and has been added to
1547 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1548 past, it affected all builds that used the bsd.*.mk files. The old
1549 behavior was a bug, but people may have relied upon it. To get this
1550 behavior back, you can .include /etc/src.conf from /etc/make.conf
1551 (which is still global and isn't changed). This also changes the
1552 behavior of incremental builds inside the tree of individual
1553 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1554 Although this has survived make universe and some upgrade scenarios,
1555 other upgrade scenarios may have broken. At least one form of
1556 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1557 as well... In cases where MAKESYSPATH isn't working with this
1558 setting, you'll need to set it to the full path to your tree.
1560 One side effect of all this cleaning up is that bsd.compiler.mk
1561 is no longer implicitly included by bsd.own.mk. If you wish to
1562 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1566 The lindev device has been removed since /dev/full has been made a
1567 standard device. __FreeBSD_version has been bumped.
1570 The knob WITHOUT_VI was added to the base system, which controls
1571 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1572 in order to reorder files share/termcap and didn't build ex(1) as a
1573 build tool, so building/installing with WITH_VI is highly advised for
1574 build hosts for older releases.
1576 This issue has been fixed in stable/9 and stable/10 in r277022 and
1577 r276991, respectively.
1580 The YES_HESIOD knob has been removed. It has been obsolete for
1581 a decade. Please move to using WITH_HESIOD instead or your builds
1582 will silently lack HESIOD.
1585 The uart(4) driver has been changed with respect to its handling
1586 of the low-level console. Previously the uart(4) driver prevented
1587 any process from changing the baudrate or the CLOCAL and HUPCL
1588 control flags. By removing the restrictions, operators can make
1589 changes to the serial console port without having to reboot.
1590 However, when getty(8) is started on the serial device that is
1591 associated with the low-level console, a misconfigured terminal
1592 line in /etc/ttys will now have a real impact.
1593 Before upgrading the kernel, make sure that /etc/ttys has the
1594 serial console device configured as 3wire without baudrate to
1595 preserve the previous behaviour. E.g:
1596 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1599 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1600 to improve performance. To re-enable it, if needed, run rpcbind
1601 with command line option -W.
1604 Switched back to the GPL dtc compiler due to updates in the upstream
1605 dts files not being supported by the BSDL dtc compiler. You will need
1606 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1607 may result while building dtb files during a kernel build if you fail
1608 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1611 Clang and llvm have been upgraded to 3.4 release.
1614 The nve(4) driver has been removed. Please use the nfe(4) driver
1615 for NVIDIA nForce MCP Ethernet adapters instead.
1618 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1619 This could cause certain C++ applications using shared libraries built
1620 against the previous version of libc++ to crash. The incompatibility
1621 has now been fixed, but any C++ applications or shared libraries built
1622 between r261283 and r261801 should be recompiled.
1625 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1626 capability mode support. Please note that enabling the feature in
1627 kernel is still highly recommended.
1630 OpenSSH is now built with sandbox support, and will use sandbox as
1631 the default privilege separation method. This requires Capsicum
1632 capability mode support in kernel.
1635 The libelf and libdwarf libraries have been updated to newer
1636 versions from upstream. Shared library version numbers for
1637 these two libraries were bumped. Any ports or binaries
1638 requiring these two libraries should be recompiled.
1639 __FreeBSD_version is bumped to 1100006.
1642 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1643 instead of providing an explicit one, this would prevent such
1644 Makefile from providing its own Kyuafile in the future during
1645 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1646 intervention is needed to clean an objdir if you use NO_CLEAN:
1647 # find /usr/obj -name Kyuafile | xargs rm -f
1650 The behavior of gss_pseudo_random() for the krb5 mechanism
1651 has changed, for applications requesting a longer random string
1652 than produced by the underlying enctype's pseudo-random() function.
1653 In particular, the random string produced from a session key of
1654 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1655 be different at the 17th octet and later, after this change.
1656 The counter used in the PRF+ construction is now encoded as a
1657 big-endian integer in accordance with RFC 4402.
1658 __FreeBSD_version is bumped to 1100004.
1661 The WITHOUT_ATF build knob has been removed and its functionality
1662 has been subsumed into the more generic WITHOUT_TESTS. If you were
1663 using the former to disable the build of the ATF libraries, you
1664 should change your settings to use the latter.
1667 The default version of mtree is nmtree which is obtained from
1668 NetBSD. The output is generally the same, but may vary
1669 slightly. If you found you need identical output adding
1670 "-F freebsd9" to the command line should do the trick. For the
1671 time being, the old mtree is available as fmtree.
1674 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1675 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1676 1.1.4_8 and verify bsdyml not linked in, before running "make
1678 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1680 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1683 The stable/10 branch has been created in subversion from head
1690 Avoid using make -j when upgrading. While generally safe, there are
1691 sometimes problems using -j to upgrade. If your upgrade fails with
1692 -j, please try again without -j. From time to time in the past there
1693 have been problems using -j with buildworld and/or installworld. This
1694 is especially true when upgrading between "distant" versions (eg one
1695 that cross a major release boundary or several minor releases, or when
1696 several months have passed on the -current branch).
1698 Sometimes, obscure build problems are the result of environment
1699 poisoning. This can happen because the make utility reads its
1700 environment when searching for values for global variables. To run
1701 your build attempts in an "environmental clean room", prefix all make
1702 commands with 'env -i '. See the env(1) manual page for more details.
1704 When upgrading from one major version to another it is generally best to
1705 upgrade to the latest code in the currently installed branch first, then
1706 do an upgrade to the new branch. This is the best-tested upgrade path,
1707 and has the highest probability of being successful. Please try this
1708 approach if you encounter problems with a major version upgrade. Since
1709 the stable 4.x branch point, one has generally been able to upgrade from
1710 anywhere in the most recent stable branch to head / current (or even the
1711 last couple of stable branches). See the top of this file when there's
1714 When upgrading a live system, having a root shell around before
1715 installing anything can help undo problems. Not having a root shell
1716 around can lead to problems if pam has changed too much from your
1717 starting point to allow continued authentication after the upgrade.
1719 This file should be read as a log of events. When a later event changes
1720 information of a prior event, the prior event should not be deleted.
1721 Instead, a pointer to the entry with the new information should be
1722 placed in the old entry. Readers of this file should also sanity check
1723 older entries before relying on them blindly. Authors of new entries
1724 should write them with this in mind.
1728 When upgrading the boot ZFS pool to a new version, always follow
1731 1.) recompile and reinstall the ZFS boot loader and boot block
1732 (this is part of "make buildworld" and "make installworld")
1734 2.) update the ZFS boot block on your boot drive
1736 The following example updates the ZFS boot block on the first
1737 partition (freebsd-boot) of a GPT partitioned drive ada0:
1738 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1740 Non-boot pools do not need these updates.
1744 If you are updating from a prior version of FreeBSD (even one just
1745 a few days old), you should follow this procedure. It is the most
1746 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1748 make kernel-toolchain
1749 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1750 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1752 To test a kernel once
1753 ---------------------
1754 If you just want to boot a kernel once (because you are not sure
1755 if it works, or if you want to boot a known bad kernel to provide
1756 debugging information) run
1757 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1758 nextboot -k testkernel
1760 To rebuild everything and install it on the current system.
1761 -----------------------------------------------------------
1762 # Note: sometimes if you are running current you gotta do more than
1763 # is listed here if you are upgrading from a really old current.
1765 <make sure you have good level 0 dumps>
1767 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1768 make installkernel KERNCONF=YOUR_KERNEL_HERE
1770 <reboot in single user> [3]
1777 To cross-install current onto a separate partition
1778 --------------------------------------------------
1779 # In this approach we use a separate partition to hold
1780 # current's root, 'usr', and 'var' directories. A partition
1781 # holding "/", "/usr" and "/var" should be about 2GB in
1784 <make sure you have good level 0 dumps>
1787 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1788 <maybe newfs current's root partition>
1789 <mount current's root partition on directory ${CURRENT_ROOT}>
1790 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1791 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1792 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1793 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1794 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1795 <reboot into current>
1796 <do a "native" rebuild/install as described in the previous section>
1797 <maybe install compatibility libraries from ports/misc/compat*>
1801 To upgrade in-place from stable to current
1802 ----------------------------------------------
1803 <make sure you have good level 0 dumps>
1805 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1806 make installkernel KERNCONF=YOUR_KERNEL_HERE
1808 <reboot in single user> [3]
1815 Make sure that you've read the UPDATING file to understand the
1816 tweaks to various things you need. At this point in the life
1817 cycle of current, things change often and you are on your own
1818 to cope. The defaults can also change, so please read ALL of
1819 the UPDATING entries.
1821 Also, if you are tracking -current, you must be subscribed to
1822 freebsd-current@freebsd.org. Make sure that before you update
1823 your sources that you have read and understood all the recent
1824 messages there. If in doubt, please track -stable which has
1825 much fewer pitfalls.
1827 [1] If you have third party modules, such as vmware, you
1828 should disable them at this point so they don't crash your
1831 [3] From the bootblocks, boot -s, and then do
1836 adjkerntz -i # if CMOS is wall time
1837 Also, when doing a major release upgrade, it is required that
1838 you boot into single user mode to do the installworld.
1840 [4] Note: This step is non-optional. Failure to do this step
1841 can result in a significant reduction in the functionality of the
1842 system. Attempting to do it by hand is not recommended and those
1843 that pursue this avenue should read this file carefully, as well
1844 as the archives of freebsd-current and freebsd-hackers mailing lists
1845 for potential gotchas. The -U option is also useful to consider.
1846 See mergemaster(8) for more information.
1848 [5] Usually this step is a no-op. However, from time to time
1849 you may need to do this if you get unknown user in the following
1850 step. It never hurts to do it all the time. You may need to
1851 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1852 install) after the buildworld before this step if you last updated
1853 from current before 20130425 or from -stable before 20130430.
1855 [6] This only deletes old files and directories. Old libraries
1856 can be deleted by "make delete-old-libs", but you have to make
1857 sure that no program is using those libraries anymore.
1859 [8] In order to have a kernel that can run the 4.x binaries needed to
1860 do an installworld, you must include the COMPAT_FREEBSD4 option in
1861 your kernel. Failure to do so may leave you with a system that is
1862 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1863 required to run the 5.x binaries on more recent kernels. And so on
1864 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1866 Make sure that you merge any new devices from GENERIC since the
1867 last time you updated your kernel config file.
1869 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1870 "?=" instead of the "=" assignment operator, so that buildworld can
1871 override the CPUTYPE if it needs to.
1873 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1874 not on the command line, or in /etc/make.conf. buildworld will
1875 warn if it is improperly defined.
1878 This file contains a list, in reverse chronological order, of major
1879 breakages in tracking -current. It is not guaranteed to be a complete
1880 list of such breakages, and only contains entries since September 23, 2011.
1881 If you need to see UPDATING entries from before that date, you will need
1882 to fetch an UPDATING file from an older FreeBSD release.
1884 Copyright information:
1886 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1888 Redistribution, publication, translation and use, with or without
1889 modification, in full or in part, in any form or format of this
1890 document are permitted without further permission from the author.
1892 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1893 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1894 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1895 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1896 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1897 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1898 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1899 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1900 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1901 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1902 POSSIBILITY OF SUCH DAMAGE.
1904 Contact Warner Losh if you have any questions about your use of