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