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