1 Updating Information for FreeBSD current users.
3 This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>.
4 See end of file for further details. For commonly done items, please see the
5 COMMON ITEMS: section later in the file. These instructions assume that you
6 basically know what you are doing. If not, then please consult the FreeBSD
9 https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
11 Items affecting the ports and packages system can be found in
12 /usr/ports/UPDATING. Please read that file before running portupgrade.
14 NOTE: FreeBSD has switched from gcc to clang. If you have trouble bootstrapping
15 from older versions of FreeBSD, try WITHOUT_CLANG and WITH_GCC to bootstrap to
16 the tip of head, and then rebuild without this option. The bootstrap process
17 from older version of current across the gcc/clang cutover is a bit fragile.
19 NOTE TO PEOPLE WHO THINK THAT FreeBSD 13.x IS SLOW:
20 FreeBSD 13.x has many debugging features turned on, in both the kernel
21 and userland. These features attempt to detect incorrect use of
22 system primitives, and encourage loud failure through extra sanity
23 checking and fail stop semantics. They also substantially impact
24 system performance. If you want to do performance measurement,
25 benchmarking, and optimization, you'll want to turn them off. This
26 includes various WITNESS- related kernel options, INVARIANTS, malloc
27 debugging flags in userland, and various verbose features in the
28 kernel. Many developers choose to disable these features on build
29 machines to maximize performance. (To completely disable malloc
30 debugging, define MALLOC_PRODUCTION in /etc/make.conf, or to merely
31 disable the most expensive debugging functionality run
32 "ln -s 'abort:false,junk:false' /etc/malloc.conf".)
35 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
36 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
37 it produces broken binaries when ifuncs are in use. Users needing
38 GNU ld should install the binutils port or package.
41 The BSD crtbegin and crtend code has been enabled by default. It has
42 had extensive testing on amd64, arm64, and i386. It can be disabled
43 by building a world with -DWITHOUT_BSD_CRTBEGIN.
46 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
47 has been converted to a port (misc/ctm) and will be removed from
48 FreeBSD-13. It is available as a package (ctm) for all supported
52 The default newsyslog.conf(5) file has been changed to only include
53 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
54 the filenames end in '.conf' and do not begin with a '.'.
56 You should check the configuration files in these two directories match
57 this naming convention. You can verify which configuration files are
58 being included using the command:
62 Ports for the DRM modules have been simplified. Now, amd64 users should
63 just install the drm-kmod port. All others should install
66 Graphics hardware that's newer than about 2010 usually works with
67 drm-kmod. For hardware older than 2013, however, some users will need
68 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
69 than 2008 usually only works in drm-legacy-kmod. The graphics team can
70 only commit to hardware made since 2013 due to the complexity of the
71 market and difficulty to test all the older cards effectively. If you
72 have hardware supported by drm-kmod, you are strongly encouraged to use
73 that as you will get better support.
75 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
76 elsewhere, the drm and drm2 modules will be eliminated from the src base
77 soon (with a limited exception for arm). Please update to the package asap
78 and report any issues to x11@freebsd.org.
80 Generally, anybody using the drm*-kmod packages should add
81 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
82 cross-threading surprises, especially with automatic driver
83 loading from X11 startup. These will become the defaults in 13-current
87 OpenSSL has been updated to version 1.1.1. This update included
88 additional various API changes througout the base system. It is
89 important to rebuild third-party software after upgrading. The value
90 of __FreeBSD_version has been bumped accordingly.
93 The legacy DRM modules and drivers have now been added to the loader's
94 module blacklist, in favor of loading them with kld_list in rc.conf(5).
95 The module blacklist may be overridden with the loader.conf(5)
96 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
100 The cam(4) based nda(4) driver will be used over nvd(4) by default on
101 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
102 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
103 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
107 Reproducible build mode is now on by default, in preparation for
108 FreeBSD 12.0. This eliminates build metadata such as the user,
109 host, and time from the kernel (and uname), unless the working tree
110 corresponds to a modified checkout from a version control system.
111 The previous behavior can be obtained by setting the /etc/src.conf
112 knob WITHOUT_REPRODUCIBLE_BUILD.
115 The Yarrow CSPRNG has been removed from the kernel as it has not been
116 supported by its designers since at least 2003. Fortuna has been the
117 default since FreeBSD-11.
120 devctl freeze/thaw have gone into the tree, the rc scripts have been
121 updated to use them and devmatch has been changed. You should update
122 kernel, userland and rc scripts all at the same time.
125 The default interpreter has been switched from 4th to Lua.
126 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
127 interpreter. If you have custom FORTH code you will need to set
128 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
129 src.conf for the build. This will create default hard links between
130 loader and loader_4th instead of loader and loader_lua, the new default.
131 If you are using UEFI it will create the proper hard link to loader.efi.
133 bhyve uses userboot.so. It remains 4th-only until some issues are solved
134 regarding coexisting with multiple versions of FreeBSD are resolved.
137 ls(1) now respects the COLORTERM environment variable used in other
138 systems and software to indicate that a colored terminal is both
139 supported and desired. If ls(1) is suddenly emitting colors, they may
140 be disabled again by either removing the unwanted COLORTERM from your
141 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
142 may not be observed in a future release.
145 The default pager for most commands has been changed to "less". To
146 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
150 The jedec_ts(4) driver has been removed. A superset of its functionality
151 is available in the jedec_dimm(4) driver, and the manpage for that
152 driver includes migration instructions. If you have "device jedec_ts"
153 in your kernel configuration file, it must be removed.
156 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
157 This should have no effect if the kernel is booted via BIOS/legacy boot.
158 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
159 has a buggy firmware that prevents a successful boot due to use of
163 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
164 support has been removed from the tree. These ports were
165 obsolete and/or known to be broken for many years.
168 loader.efi has been augmented to participate more fully in the
169 UEFI boot manager protocol. loader.efi will now look at the
170 BootXXXX environment variable to determine if a specific kernel
171 or root partition was specified. XXXX is derived from BootCurrent.
172 efibootmgr(8) manages these standard UEFI variables.
175 zfsloader's functionality has now been folded into loader.
176 zfsloader is no longer necessary once you've updated your
177 boot blocks. For a transition period, we will install a
178 hardlink for zfsloader to loader to allow a smooth transition
179 until the boot blocks can be updated (hard link because old
180 zfs boot blocks don't understand symlinks).
183 ARM64 now have efifb support, if you want to have serial console
184 on your arm64 board when an screen is connected and the bootloader
185 setup a frambuffer for us to use, just add :
189 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
190 an screen connected as the firmware will setup a framebuffer are that
191 u-boot will expose as an EFI framebuffer.
194 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
195 or take steps to update /etc/passwd before doing installworld on
196 existing systems. Do not skip the "mergemaster -Fp" step before
197 installworld, as described in the update procedures near the bottom
198 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
199 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
200 the ntp config file contain options that change file/dir locations.
201 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
202 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
203 taking steps to ensure that all required files/dirs are accessible
207 Big endian arm support has been removed.
210 The static environment setup in kernel configs is no longer mutually
211 exclusive with the loader(8) environment by default. In order to
212 restore the previous default behavior of disabling the loader(8)
213 environment if a static environment is present, you must specify
214 loader_env.disabled=1 in the static environment.
217 The ABI of syscalls used by management tools like sockstat and
218 netstat has been broken to allow 32-bit binaries to work on
219 64-bit kernels without modification. These programs will need
220 to match the kernel in order to function. External programs may
221 require minor modifications to accommodate a change of type in
222 structures from pointers to 64-bit virtual addresses.
225 On i386 and amd64 atomics are now inlined. Out of tree modules using
226 atomics will need to be rebuilt.
229 The '%I' format in the kern.corefile sysctl limits the number of
230 core files that a process can generate to the number stored in the
231 debug.ncores sysctl. The '%I' format is replaced by the single digit
232 index. Previously, if all indexes were taken the kernel would overwrite
233 only a core file with the highest index in a filename.
234 Currently the system will create a new core file if there is a free
235 index or if all slots are taken it will overwrite the oldest one.
238 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
239 6.0.1. Please see the 20141231 entry below for information about
240 prerequisites and upgrading, if you are not already using clang 3.5.0
244 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
245 needed to be changed to work with it. This change was made with r335763
246 and requires a mergemaster / etcupdate / etc to update the installed file.
249 r334930 changed the interface between the NFS modules, so they all
250 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
253 As of r334391 lld is the default amd64 system linker; it is installed
254 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
258 The kernel / userland interface for devinfo changed, so you'll
259 need a new kernel and userland as a pair for it to work (rebuilding
260 lib/libdevinfo is all that's required). devinfo and devmatch will
261 not work, but everything else will when there's a mismatch.
264 The on-disk format for hwpmc callchain records has changed to include
265 threadid corresponding to a given record. This changes the field offsets
266 and thus requires that libpmcstat be rebuilt before using a kernel
270 The vxge(4) driver has been removed. This driver was introduced into
271 HEAD one week before the Exar left the Ethernet market and is not
272 known to be used. If you have device vxge in your kernel config file
276 The amd64 kernel now requires a ld that supports ifunc to produce a
277 working kernel, either lld or a newer binutils. lld is built by default
278 on amd64, and the 'buildkernel' target uses it automatically. However,
279 it is not the default linker, so building the kernel the traditional
280 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
281 binutils port/package). lld will soon be default, and this requirement
284 NOTE: As of r334391 lld is the default system linker on amd64, and no
285 workaround is necessary.
288 The nxge(4) driver has been removed. This driver was for PCI-X 10g
289 cards made by s2io/Neterion. The company was aquired by Exar and
290 no longer sells or supports Ethernet products. If you have device
291 nxge in your kernel config file it must be removed.
294 The tz database (tzdb) has been updated to 2018e. This version more
295 correctly models time stamps in time zones with negative DST such as
296 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
297 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
298 time zone abbreviations and the tm_isdst flag.
301 The ixgb(4) driver has been removed. This driver was for an early and
302 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
303 quickly shifted to the long lived ixgbe family. If you have device
304 ixgb in your kernel config file it must be removed.
307 The lmc(4) driver has been removed. This was a WAN interface
308 card that was already reportedly rare in 2003, and had an ambiguous
309 license. If you have device lmc in your kernel config file it must
313 Support for Arcnet networks has been removed. If you have device
314 arcnet or device cm in your kernel config file they must be
318 Support for FDDI networks has been removed. If you have device
319 fddi or device fpa in your kernel config file they must be
323 In addition to supporting RFC 3164 formatted messages, the
324 syslogd(8) service is now capable of parsing RFC 5424 formatted
325 log messages. The main benefit of using RFC 5424 is that clients
326 may now send log messages with timestamps containing year numbers,
327 microseconds and time zone offsets.
329 Similarly, the syslog(3) C library function has been altered to
330 send RFC 5424 formatted messages to the local system logging
331 daemon. On systems using syslogd(8), this change should have no
332 negative impact, as long as syslogd(8) and the C library are
333 updated at the same time. On systems using a different system
334 logging daemon, it may be necessary to make configuration
335 adjustments, depending on the software used.
337 When using syslog-ng, add the 'syslog-protocol' flag to local
338 input sources to enable parsing of RFC 5424 formatted messages:
341 unix-dgram("/var/run/log" flags(syslog-protocol));
344 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
345 of the 'imuxsock' module to let messages be processed by the
346 regular RFC 3164/5424 parsing pipeline:
348 module(load="imuxsock" SysSock.UseSpecialParser="off")
350 Do note that these changes only affect communication between local
351 applications and syslogd(8). The format that syslogd(8) uses to
352 store messages on disk or forward messages to other systems
353 remains unchanged. syslogd(8) still uses RFC 3164 for these
354 purposes. Options to customize this behaviour will be added in the
355 future. Utilities that process log files stored in /var/log are
356 thus expected to continue to function as before.
358 __FreeBSD_version has been incremented to 1200061 to denote this
362 Support for token ring networks has been removed. If you
363 have "device token" in your kernel config you should remove
364 it. No device drivers supported token ring.
367 makefs was modified to be able to tag ISO9660 El Torito boot catalog
368 entries as EFI instead of overloading the i386 tag as done previously.
369 The amd64 mkisoimages.sh script used to build amd64 ISO images for
370 release was updated to use this. This may mean that makefs must be
371 updated before "make cdrom" can be run in the release directory. This
372 should be as simple as:
374 $ cd $SRCDIR/usr.sbin/makefs
375 $ make depend all install
378 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
379 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
380 Co-existance for the transition period will come shortly. Booting is a
381 complex environment and test coverage for Lua-enabled loaders has been
382 thin, so it would be prudent to assume it might not work and make
383 provisions for backup boot methods.
386 devmatch functionality has been turned on in devd. It will automatically
387 load drivers for unattached devices. This may cause unexpected drivers to
388 be loaded. Please report any problems to current@ and imp@freebsd.org.
391 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
392 6.0.0. Please see the 20141231 entry below for information about
393 prerequisites and upgrading, if you are not already using clang 3.5.0
397 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
398 This means it is used to link the kernel and userland libraries and
399 executables, but is not yet installed as /usr/bin/ld by default.
401 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
402 WITHOUT_LLD_BOOTSTRAP=yes
405 On i386, pmtimer has been removed. Its functionality has been folded
406 into apm. It was a no-op on ACPI in current for a while now (but was still
407 needed on i386 in FreeBSD 11 and earlier). Users may need to remove it
408 from kernel config files.
411 The use of RSS hash from the network card aka flowid has been
412 disabled by default for lagg(4) as it's currently incompatible with
413 the lacp and loadbalance protocols.
415 This can be re-enabled by setting the following in loader.conf:
416 net.link.lagg.default_use_flowid="1"
419 The SW_WATCHDOG option is no longer necessary to enable the
420 hardclock-based software watchdog if no hardware watchdog is
421 configured. As before, SW_WATCHDOG will cause the software
422 watchdog to be enabled even if a hardware watchdog is configured.
425 r326887 fixes the issue described in the 20171214 UPDATING entry.
426 r326888 flips the switch back to building GELI support always.
429 r362593 broke ZFS + GELI support for reasons unknown. However,
430 it also broke ZFS support generally, so GELI has been turned off
431 by default as the lesser evil in r326857. If you boot off ZFS and/or
432 GELI, it might not be a good time to update.
435 PowerPC users must update loader(8) by rebuilding world before
436 installing a new kernel, as the protocol connecting them has
437 changed. Without the update, loader metadata will not be passed
438 successfully to the kernel and users will have to enter their
439 root partition at the kernel mountroot prompt to continue booting.
440 Newer versions of loader can boot old kernels without issue.
443 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
444 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
445 to WITH/OUT_LOADER_GELI.
448 The naive and non-compliant support of posix_fallocate(2) in ZFS
449 has been removed as of r325320. The system call now returns EINVAL
450 when used on a ZFS file. Although the new behavior complies with the
451 standard, some consumers are not prepared to cope with it.
452 One known victim is lld prior to r325420.
455 Building in a FreeBSD src checkout will automatically create object
456 directories now rather than store files in the current directory if
457 'make obj' was not ran. Calling 'make obj' is no longer necessary.
458 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
459 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
463 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
464 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
465 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
466 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
467 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
468 The UNIFIED_OBJDIR option is a transitional feature that will be
469 removed for 12.0 release; please migrate to the new format for any
470 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
471 than hardcoding paths.
474 The native-xtools target no longer installs the files by default to the
475 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
476 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
479 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
480 options are changing from controlling the build if defined / undefined
481 to controlling the build with explicit 'yes' or 'no' values. They will
482 shift to WITH/WITHOUT options to match other options in the system.
485 libstand has turned into a private library for sys/boot use only.
486 It is no longer supported as a public interface outside of sys/boot.
489 The arm port has split armv6 into armv6 and armv7. armv7 is now
490 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
491 and are running a kernel from before r324363, you will need to add
492 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
495 When building multiple kernels using KERNCONF, non-existent KERNCONF
496 files will produce an error and buildkernel will fail. Previously
497 missing KERNCONF files silently failed giving no indication as to
498 why, only to subsequently discover during installkernel that the
499 desired kernel was never built in the first place.
502 The default serial number format for CTL LUNs has changed. This will
503 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
504 or iSCSI clients care about their LUNs' serial numbers. Users who
505 require serial number stability should hardcode serial numbers in
509 For 32-bit arm compiled for hard-float support, soft-floating point
510 binaries now always get their shared libraries from
511 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
512 /usr/libsoft also existed). Only users with a hard-float ld.so, but
513 soft-float everything else should be affected.
516 The geli password typed at boot is now hidden. To restore the previous
517 behavior, see geli(8) for configuration options.
520 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
521 sysctl values. Minor nit, but requires a rebuild of both world/kernel
525 "make check" behavior (made in ^/head@r295380) has been changed to
526 execute from a limited sandbox, as opposed to executing from
530 - The "beforecheck" and "aftercheck" targets are now specified.
531 - ${CHECKDIR} (added in commit noted above) has been removed.
532 - Legacy behavior can be enabled by setting
533 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
535 If the limited sandbox mode is enabled, "make check" will execute
536 "make distribution", then install, execute the tests, and clean up the
537 sandbox if successful.
539 The "make distribution" and "make install" targets are typically run as
540 root to set appropriate permissions and ownership at installation time.
541 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
542 environment if executing "make check" with limited sandbox mode using
543 an unprivileged user.
546 Since the switch to GPT disk labels, fsck for UFS/FFS has been
547 unable to automatically find alternate superblocks. As of r322297,
548 the information needed to find alternate superblocks has been
549 moved to the end of the area reserved for the boot block.
550 Filesystems created with a newfs of this vintage or later
551 will create the recovery information. If you have a filesystem
552 created prior to this change and wish to have a recovery block
553 created for your filesystem, you can do so by running fsck in
554 foreground mode (i.e., do not use the -p or -y options). As it
555 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
556 to which you should answer yes.
559 As of r321665, an NFSv4 server configuration that services
560 Kerberos mounts or clients that do not support the uid/gid in
561 owner/owner_group string capability, must explicitly enable
562 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
563 machine's /etc/rc.conf file.
566 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
567 Please see the 20141231 entry below for information about prerequisites
568 and upgrading, if you are not already using clang 3.5.0 or higher.
571 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
572 r-commands (rlogin, rsh, etc.) to be built with the base system.
575 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
576 a very major ABI incompatible change, so users of FreeBSD/powerpc must
577 be careful when performing source upgrades. It is best to run
578 'make installworld' from an alternate root system, either a live
579 CD/memory stick, or a temporary root partition. Additionally, all ports
580 must be recompiled. powerpc64 is largely unaffected, except in the case
581 of 32-bit compatibility. All 32-bit binaries will be affected.
584 Forward compatibility for the "ino64" project have been committed. This
585 will allow most new binaries to run on older kernels in a limited
586 fashion. This prevents many of the common foot-shooting actions in the
587 upgrade as well as the limited ability to roll back the kernel across
588 the ino64 upgrade. Complicated use cases may not work properly, though
589 enough simpler ones work to allow recovery in most situations.
592 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
593 if you require the GPL compiler.
596 The internal ABI used for communication between the NFS kernel modules
597 was changed by r320085, so __FreeBSD_version was bumped to
598 ensure all the NFS related modules are updated together.
601 The ABI of struct event was changed by extending the data
602 member to 64bit and adding ext fields. For upgrade, same
603 precautions as for the entry 20170523 "ino64" must be
607 The GNU roff toolchain has been removed from base. To render manpages
608 which are not supported by mandoc(1), man(1) can fallback on GNU roff
609 from ports (and recommends to install it).
610 To render roff(7) documents, consider using GNU roff from ports or the
611 heirloom doctools roff toolchain from ports via pkg install groff or
612 via pkg install heirloom-doctools.
615 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
616 smaller runtime footprint builds. This is useful for embedded systems
617 which only require one chipset support.
619 If you load it as a module, make sure this is in /boot/loader.conf:
623 This will load the HAL, all chip/RF backends and if_ath_pci.
624 If you have if_ath_pci in /boot/loader.conf, ensure it is after
625 if_ath or it will not load any HAL chipset support.
627 If you want to selectively load things (eg on ye cheape ARM/MIPS
628 platforms where RAM is at a premium) you should:
631 * load the chip modules in question
632 * load ath_rate, ath_dfs
634 * load if_ath_pci and/or if_ath_ahb depending upon your particular
635 bus bind type - this is where probe/attach is done.
637 For further comments/feedback, poke adrian@ .
640 The "ino64" 64-bit inode project has been committed, which extends
641 a number of types to 64 bits. Upgrading in place requires care and
642 adherence to the documented upgrade procedure.
644 If using a custom kernel configuration ensure that the
645 COMPAT_FREEBSD11 option is included (as during the upgrade the
646 system will be running the ino64 kernel with the existing world).
648 For the safest in-place upgrade begin by removing previous build
649 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
650 full procedure documented below under the heading "To rebuild
651 everything and install it on the current system." Specifically,
652 a reboot is required after installing the new kernel before
656 The NATM framework including the en(4), fatm(4), hatm(4), and
657 patm(4) devices has been removed. Consumers should plan a
658 migration before the end-of-life date for FreeBSD 11.
661 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
662 diff has not been implemented, if those are needed a newer version of
663 GNU diff is available via the diffutils package under the gdiff name.
666 As of r316810 for ipfilter, keep frags is no longer assumed when
667 keep state is specified in a rule. r316810 aligns ipfilter with
668 documentation in man pages separating keep frags from keep state.
669 This allows keep state to be specified without forcing keep frags
670 and allows keep frags to be specified independently of keep state.
671 To maintain previous behaviour, also specify keep frags with
672 keep state (as documented in ipf.conf.5).
675 arm64 builds now use the base system LLD 4.0.0 linker by default,
676 instead of requiring that the aarch64-binutils port or package be
677 installed. To continue using aarch64-binutils, set
678 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
681 The UDP optimization in entry 20160818 that added the sysctl
682 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
683 packets will no longer be treated as L3 broadcast packets.
686 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
687 use any explicitly assigned loopback address available in the jail
688 instead of using the first assigned address of the jail.
691 The ctl.ko module no longer implements the iSCSI target frontend:
692 cfiscsi.ko does instead.
694 If building cfiscsi.ko as a kernel module, the module can be loaded
695 via one of the following methods:
696 - `cfiscsi_load="YES"` in loader.conf(5).
697 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
698 - ctladm(8)/ctld(8), when compiled with iSCSI support
699 (`WITH_ISCSI=yes` in src.conf(5))
701 Please see cfiscsi(4) for more details.
704 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
705 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
706 same source (previously, the dependency of mmcsd.ko on mmc.ko was
707 missing, but mmcsd.ko now will refuse to load if it is incompatible
711 The syntax of ipfw(8) named states was changed to avoid ambiguity.
712 If you have used named states in the firewall rules, you need to modify
713 them after installworld and before rebooting. Now named states must
714 be prefixed with colon.
717 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
718 removed as the userland we provide cannot use them. The KMS version
719 (sys/dev/drm2) supports the same hardware.
722 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
723 Please see the 20141231 entry below for information about prerequisites
724 and upgrading, if you are not already using clang 3.5.0 or higher.
727 The code that provides support for ZFS .zfs/ directory functionality
728 has been reimplemented. It's not possible now to create a snapshot
729 by mkdir under .zfs/snapshot/. That should be the only user visible
733 EISA bus support has been removed. The WITH_EISA option is no longer
737 MCA bus support has been removed.
740 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
741 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
744 The EM_MULTIQUEUE kernel configuration option is deprecated now that
745 the em(4) driver conforms to iflib specifications.
748 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
749 IFLIB. If you have a custom kernel configuration that excludes em(4)
750 but you use igb(4), you need to re-add em(4) to your custom configuration.
753 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
754 Please see the 20141231 entry below for information about prerequisites
755 and upgrading, if you are not already using clang 3.5.0 or higher.
758 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
759 Please see the 20141231 entry below for information about prerequisites
760 and upgrading, if you are not already using clang 3.5.0 or higher.
763 The layout of the pmap structure has changed for powerpc to put the pmap
764 statistics at the front for all CPU variations. libkvm(3) and all tools
765 that link against it need to be recompiled.
768 isl(4) and cyapa(4) drivers now require a new driver,
769 chromebook_platform(4), to work properly on Chromebook-class hardware.
770 On other types of hardware the drivers may need to be configured using
771 device hints. Please see the corresponding manual pages for details.
774 The urtwn(4) driver was merged into rtwn(4) and now consists of
775 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
777 Also, firmware for RTL8188CE was renamed due to possible name
778 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
781 GNU rcs has been removed from base. It is available as packages:
782 - rcs: Latest GPLv3 GNU rcs version.
783 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
787 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
788 modules now requires that the kernel configuration contain the
789 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
792 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
793 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
796 Relocatable object files with the extension of .So have been renamed
797 to use an extension of .pico instead. The purpose of this change is
798 to avoid a name clash with shared libraries on case-insensitive file
799 systems. On those file systems, foo.So is the same file as foo.so.
802 GNU rcs has been turned off by default. It can (temporarily) be built
803 again by adding WITH_RCS knob in src.conf.
804 Otherwise, GNU rcs is available from packages:
805 - rcs: Latest GPLv3 GNU rcs version.
806 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
809 The backup_uses_rcs functionality has been removed from rc.subr.
812 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
813 two separate components, QUEUE_MACRO_DEBUG_TRACE and
814 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
815 QUEUE_MACRO_DEBUG behavior.
818 r304787 changed some ioctl interfaces between the iSCSI userspace
819 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
820 rebuilt to work with new kernels. __FreeBSD_version has been bumped
824 The UDP receive code has been updated to only treat incoming UDP
825 packets that were addressed to an L2 broadcast address as L3
826 broadcast packets. It is not expected that this will affect any
827 standards-conforming UDP application. The new behaviour can be
828 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
832 Remove the openbsd_poll system call.
833 __FreeBSD_version has been bumped because of this.
836 The stable/11 branch has been created from head@r302406.
839 The libc stub for the pipe(2) system call has been replaced with
840 a wrapper that calls the pipe2(2) system call and the pipe(2)
841 system call is now only implemented by the kernels that include
842 "options COMPAT_FREEBSD10" in their config file (this is the
843 default). Users should ensure that this option is enabled in
844 their kernel or upgrade userspace to r302092 before upgrading their
848 CAM will now strip leading spaces from SCSI disks' serial numbers.
849 This will affect users who create UFS filesystems on SCSI disks using
850 those disk's diskid device nodes. For example, if /etc/fstab
851 previously contained a line like
852 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
853 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
854 transforms like gmirror may also be affected. ZFS users should
858 The bitstring(3) API has been updated with new functionality and
859 improved performance. But it is binary-incompatible with the old API.
860 Objects built with the new headers may not be linked against objects
861 built with the old headers.
864 The brk and sbrk functions have been removed from libc on arm64.
865 Binutils from ports has been updated to not link to these
866 functions and should be updated to the latest version before
867 installing a new libc.
870 The armv6 port now defaults to hard float ABI. Limited support
871 for running both hardfloat and soft float on the same system
872 is available using the libraries installed with -DWITH_LIBSOFT.
873 This has only been tested as an upgrade path for installworld
874 and packages may fail or need manual intervention to run. New
875 packages will be needed.
877 To update an existing self-hosted armv6hf system, you must add
878 TARGET_ARCH=armv6 on the make command line for both the build
879 and the install steps.
882 Kernel modules compiled outside of a kernel build now default to
883 installing to /boot/modules instead of /boot/kernel. Many kernel
884 modules built this way (such as those in ports) already overrode
885 KMODDIR explicitly to install into /boot/modules. However,
886 manually building and installing a module from /sys/modules will
887 now install to /boot/modules instead of /boot/kernel.
890 The CAM I/O scheduler has been committed to the kernel. There should be
891 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
892 list of known rogues that claim support for this but actually corrupt
893 data is believed to be complete, be on the lookout for data
894 corruption. The known rogue list is believed to be complete:
896 o Crucial MX100, M550 drives with MU01 firmware.
897 o Micron M510 and M550 drives with MU01 firmware.
898 o Micron M500 prior to MU07 firmware
899 o Samsung 830, 840, and 850 all firmwares
900 o FCCT M500 all firmwares
902 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
903 with working NCQ TRIM. For Micron branded drives, see your sales rep for
904 updated firmware. Black listed drives will work correctly because these
905 drives work correctly so long as no NCQ TRIMs are sent to them. Given
906 this list is the same as found in Linux, it's believed there are no
907 other rogues in the market place. All other models from the above
910 To be safe, if you are at all concerned, you can quirk each of your
911 drives to prevent NCQ from being sent by setting:
912 kern.cam.ada.X.quirks="0x2"
913 in loader.conf. If the drive requires the 4k sector quirk, set the
917 The FAST_DEPEND build option has been removed and its functionality is
918 now the one true way. The old mkdep(1) style of 'make depend' has
919 been removed. See 20160311 for further details.
922 Resource range types have grown from unsigned long to uintmax_t. All
923 drivers, and anything using libdevinfo, need to be recompiled.
926 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
927 builds. It no longer runs mkdep(1) during 'make depend', and the
928 'make depend' stage can safely be skipped now as it is auto ran
929 when building 'make all' and will generate all SRCS and DPSRCS before
930 building anything else. Dependencies are gathered at compile time with
931 -MF flags kept in separate .depend files per object file. Users should
932 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
936 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
937 kernel modules. Therefore, if you load any kernel modules at boot time,
938 please install the boot loaders after you install the kernel, but before
942 make buildkernel KERNCONF=YOUR_KERNEL_HERE
943 make installkernel KERNCONF=YOUR_KERNEL_HERE
944 make -C sys/boot install
945 <reboot in single user>
947 Then follow the usual steps, described in the General Notes section,
951 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
952 see the 20141231 entry below for information about prerequisites and
953 upgrading, if you are not already using clang 3.5.0 or higher.
956 The AIO subsystem is now a standard part of the kernel. The
957 VFS_AIO kernel option and aio.ko kernel module have been removed.
958 Due to stability concerns, asynchronous I/O requests are only
959 permitted on sockets and raw disks by default. To enable
960 asynchronous I/O requests on all file types, set the
961 vfs.aio.enable_unsafe sysctl to a non-zero value.
964 The ELF object manipulation tool objcopy is now provided by the
965 ELF Tool Chain project rather than by GNU binutils. It should be a
966 drop-in replacement, with the addition of arm64 support. The
967 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
968 to obtain the GNU version if necessary.
971 Building ZFS pools on top of zvols is prohibited by default. That
972 feature has never worked safely; it's always been prone to deadlocks.
973 Using a zvol as the backing store for a VM guest's virtual disk will
974 still work, even if the guest is using ZFS. Legacy behavior can be
975 restored by setting vfs.zfs.vol.recursive=1.
978 The NONE and HPN patches has been removed from OpenSSH. They are
979 still available in the security/openssh-portable port.
982 With the addition of ypldap(8), a new _ypldap user is now required
983 during installworld. "mergemaster -p" can be used to add the user
984 prior to installworld, as documented in the handbook.
987 The tftp loader (pxeboot) now uses the option root-path directive. As a
988 consequence it no longer looks for a pxeboot.4th file on the tftp
989 server. Instead it uses the regular /boot infrastructure as with the
993 The code to start recording plug and play data into the modules has
994 been committed. While the old tools will properly build a new kernel,
995 a number of warnings about "unknown metadata record 4" will be produced
996 for an older kldxref. To avoid such warnings, make sure to rebuild
997 the kernel toolchain (or world). Make sure that you have r292078 or
998 later when trying to build 292077 or later before rebuilding.
1001 Debug data files are now built by default with 'make buildworld' and
1002 installed with 'make installworld'. This facilitates debugging but
1003 requires more disk space both during the build and for the installed
1004 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1008 r291527 changed the internal interface between the nfsd.ko and
1009 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1010 __FreeBSD_version has been bumped because of this.
1013 Add support for unicode collation strings leads to a change of
1014 order of files listed by ls(1) for example. To get back to the old
1015 behaviour, set LC_COLLATE environment variable to "C".
1017 Databases administrators will need to reindex their databases given
1018 collation results will be different.
1020 Due to a bug in install(1) it is recommended to remove the ancient
1021 locales before running make installworld.
1023 rm -rf /usr/share/locale/*
1026 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1027 libcrypto.so.7 or libssl.so.7 must be recompiled.
1030 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1031 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1032 should be replaced with isp_2400 and isp_2500 modules respectively.
1035 The build previously allowed using 'make -n' to not recurse into
1036 sub-directories while showing what commands would be executed, and
1037 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1038 and 'make -N' will not.
1041 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1042 and etcupdate will now use this file. A custom sendmail.cf is now
1043 updated via this mechanism rather than via installworld. If you had
1044 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1045 want to remove the exclusion or change it to "always install".
1046 /etc/mail/sendmail.cf is now managed the same way regardless of
1047 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1048 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1051 Compatibility shims for legacy ATA device names have been removed.
1052 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1053 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1054 environment variables, /dev/ad* and /dev/ar* symbolic links.
1057 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1058 Please see the 20141231 entry below for information about prerequisites
1059 and upgrading, if you are not already using clang 3.5.0 or higher.
1062 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1063 and renamed from .symbols to .debug. This reduces the size requirements
1064 on the boot partition or file system and provides consistency with
1065 userland debug files.
1067 When using the supported kernel installation method the
1068 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1069 as is done with /boot/kernel.
1071 Developers wishing to maintain the historical behavior of installing
1072 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1075 The wireless drivers had undergone changes that remove the 'parent
1076 interface' from the ifconfig -l output. The rc.d network scripts
1077 used to check presence of a parent interface in the list, so old
1078 scripts would fail to start wireless networking. Thus, etcupdate(3)
1079 or mergemaster(8) run is required after kernel update, to update your
1080 rc.d scripts in /etc.
1083 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1084 These configurations are now automatically interpreted as
1085 'scrub fragment reassemble'.
1088 Kernel-loadable modules for the random(4) device are back. To use
1089 them, the kernel must have
1092 options RANDOM_LOADABLE
1094 kldload(8) can then be used to load random_fortuna.ko
1095 or random_yarrow.ko. Please note that due to the indirect
1096 function calls that the loadable modules need to provide,
1097 the build-in variants will be slightly more efficient.
1099 The random(4) kernel option RANDOM_DUMMY has been retired due to
1100 unpopularity. It was not all that useful anyway.
1103 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1104 Control over building the ELF Tool Chain tools is now provided by
1105 the WITHOUT_TOOLCHAIN knob.
1108 The polarity of Pulse Per Second (PPS) capture events with the
1109 uart(4) driver has been corrected. Prior to this change the PPS
1110 "assert" event corresponded to the trailing edge of a positive PPS
1111 pulse and the "clear" event was the leading edge of the next pulse.
1113 As the width of a PPS pulse in a typical GPS receiver is on the
1114 order of 1 millisecond, most users will not notice any significant
1115 difference with this change.
1117 Anyone who has compensated for the historical polarity reversal by
1118 configuring a negative offset equal to the pulse width will need to
1119 remove that workaround.
1122 The default group assigned to /dev/dri entries has been changed
1123 from 'wheel' to 'video' with the id of '44'. If you want to have
1124 access to the dri devices please add yourself to the video group
1127 # pw groupmod video -m $USER
1130 The menu.rc and loader.rc files will now be replaced during
1131 upgrades. Please migrate local changes to menu.rc.local and
1132 loader.rc.local instead.
1135 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1136 strings and strip have been removed. The src.conf(5) knob
1137 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1140 As ZFS requires more kernel stack pages than is the default on some
1141 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1142 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1144 Please consider using 'options KSTACK_PAGES=X' where X is greater
1145 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1148 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1149 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1150 default, i.e., they will not contain "::". For example, instead
1151 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1152 to have a more specific match, such as different map entries for
1153 IPv6:0:0 vs IPv6:0. This change requires that configuration
1154 data (including maps, files, classes, custom ruleset, etc.) must
1155 use the same format, so make certain such configuration data is
1156 upgrading. As a very simple check search for patterns like
1157 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1158 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1159 the cf option UseCompressedIPv6Addresses.
1162 The default kernel entropy-processing algorithm is now
1163 Fortuna, replacing Yarrow.
1165 Assuming you have 'device random' in your kernel config
1166 file, the configurations allow a kernel option to override
1167 this default. You may choose *ONE* of:
1169 options RANDOM_YARROW # Legacy /dev/random algorithm.
1170 options RANDOM_DUMMY # Blocking-only driver.
1172 If you have neither, you get Fortuna. For most people,
1173 read no further, Fortuna will give a /dev/random that works
1174 like it always used to, and the difference will be irrelevant.
1176 If you remove 'device random', you get *NO* kernel-processed
1177 entropy at all. This may be acceptable to folks building
1178 embedded systems, but has complications. Carry on reading,
1179 and it is assumed you know what you need.
1181 *PLEASE* read random(4) and random(9) if you are in the
1182 habit of tweaking kernel configs, and/or if you are a member
1183 of the embedded community, wanting specific and not-usual
1184 behaviour from your security subsystems.
1186 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1187 random', you will NOT have a functioning /dev/random, and
1188 many cryptographic features will not work, including SSH.
1189 You may also find strange behaviour from the random(3) set
1190 of library functions, in particular sranddev(3), srandomdev(3)
1191 and arc4random(3). The reason for this is that the KERN_ARND
1192 sysctl only returns entropy if it thinks it has some to
1193 share, and with RANDOM_DUMMY or no 'device random' this
1197 An additional fix for the issue described in the 20150614 sendmail
1198 entry below has been committed in revision 284717.
1201 FreeBSD's old make (fmake) has been removed from the system. It is
1202 available as the devel/fmake port or via pkg install fmake.
1205 The fix for the issue described in the 20150614 sendmail entry
1206 below has been committed in revision 284436. The work
1207 around described in that entry is no longer needed unless the
1208 default setting is overridden by a confDH_PARAMETERS configuration
1209 setting of '5' or pointing to a 512 bit DH parameter file.
1212 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1213 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1214 and devel/kyua to version 0.20+ and adjust any calling code to work
1215 with Kyuafile and kyua.
1218 The import of openssl to address the FreeBSD-SA-15:10.openssl
1219 security advisory includes a change which rejects handshakes
1220 with DH parameters below 768 bits. sendmail releases prior
1221 to 8.15.2 (not yet released), defaulted to a 512 bit
1222 DH parameter setting for client connections. To work around
1223 this interoperability, sendmail can be configured to use a
1224 2048 bit DH parameter by:
1226 1. Edit /etc/mail/`hostname`.mc
1227 2. If a setting for confDH_PARAMETERS does not exist or
1228 exists and is set to a string beginning with '5',
1229 replace it with '2'.
1230 3. If a setting for confDH_PARAMETERS exists and is set to
1231 a file path, create a new file with:
1232 openssl dhparam -out /path/to/file 2048
1233 4. Rebuild the .cf file:
1234 cd /etc/mail/; make; make install
1235 5. Restart sendmail:
1236 cd /etc/mail/; make restart
1238 A sendmail patch is coming, at which time this file will be
1242 Generation of legacy formatted entries have been disabled by default
1243 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1244 entries were converted to use the new format by default when the new,
1245 machine independent format have been added and supported since FreeBSD
1248 Please see the pwd_mkdb(8) manual page for further details.
1251 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1252 20141231 entry below for information about prerequisites and upgrading,
1253 if you are not already using 3.5.0 or higher.
1256 TI platform code switched to using vendor DTS files and this update
1257 may break existing systems running on Beaglebone, Beaglebone Black,
1260 - dtb files should be regenerated/reinstalled. Filenames are the
1261 same but content is different now
1262 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1263 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1264 addressing scheme is now pin 25 on /dev/gpioc3.
1265 - Pandaboard: /etc/ttys should be updated, serial console device is
1266 now /dev/ttyu2, not /dev/ttyu0
1269 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1270 If you need the GNU extension from groff soelim(1), install groff
1271 from package: pkg install groff, or via ports: textproc/groff.
1274 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1275 defined in symlink(7); previously symlinks were silently ignored.
1278 The const qualifier has been removed from iconv(3) to comply with
1279 POSIX. The ports tree is aware of this from r384038 onwards.
1282 Libraries specified by LIBADD in Makefiles must have a corresponding
1283 DPADD_<lib> variable to ensure correct dependencies. This is now
1284 enforced in src.libnames.mk.
1287 From legacy ata(4) driver was removed support for SATA controllers
1288 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1289 Kernel modules ataahci and ataadaptec were removed completely,
1290 replaced by ahci and mvs modules respectively.
1293 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1294 the 20141231 entry below for information about prerequisites and
1295 upgrading, if you are not already using 3.5.0 or higher.
1298 The 32-bit PowerPC kernel has been changed to a position-independent
1299 executable. This can only be booted with a version of loader(8)
1300 newer than January 31, 2015, so make sure to update both world and
1301 kernel before rebooting.
1304 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1305 but before r278950, the RNG was not seeded properly. Immediately
1306 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1307 ssh keys or openssl keys) that were generated w/ a kernel from that
1308 range. This does not affect programs that directly used /dev/random
1309 or /dev/urandom. All userland uses of arc4random(3) are affected.
1312 The autofs(4) ABI was changed in order to restore binary compatibility
1313 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1314 with the new kernel.
1317 The powerpc64 kernel has been changed to a position-independent
1318 executable. This can only be booted with a new version of loader(8),
1319 so make sure to update both world and kernel before rebooting.
1322 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1323 only release, no new features have been added. Please see the 20141231
1324 entry below for information about prerequisites and upgrading, if you
1325 are not already using 3.5.0.
1328 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1329 taken from the ELF Tool Chain project rather than GNU binutils. They
1330 should be drop-in replacements, with the addition of arm64 support.
1331 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1332 binutils tools, if necessary. See 20150805 for updated information.
1335 The default Unbound configuration now enables remote control
1336 using a local socket. Users who have already enabled the
1337 local_unbound service should regenerate their configuration
1338 by running "service local_unbound setup" as root.
1341 The GNU texinfo and GNU info pages have been removed.
1342 To be able to view GNU info pages please install texinfo from ports.
1345 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1347 As of this release, a prerequisite for building clang, llvm and lldb is
1348 a C++11 capable compiler and C++11 standard library. This means that to
1349 be able to successfully build the cross-tools stage of buildworld, with
1350 clang as the bootstrap compiler, your system compiler or cross compiler
1351 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1352 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1355 On any standard FreeBSD 10.x or 11.x installation, where clang and
1356 libc++ are on by default (that is, on x86 or arm), this should work out
1359 On 9.x installations where clang is enabled by default, e.g. on x86 and
1360 powerpc, libc++ will not be enabled by default, so libc++ should be
1361 built (with clang) and installed first. If both clang and libc++ are
1362 missing, build clang first, then use it to build libc++.
1364 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1365 the instructions for 9.x above.
1367 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1368 default, and do not build clang.
1370 Many embedded systems are resource constrained, and will not be able to
1371 build clang in a reasonable time, or in some cases at all. In those
1372 cases, cross building bootable systems on amd64 is a workaround.
1374 This new version of clang introduces a number of new warnings, of which
1375 the following are most likely to appear:
1379 This warns in two cases, for both C and C++:
1380 * When the code is trying to take the absolute value of an unsigned
1381 quantity, which is effectively a no-op, and almost never what was
1382 intended. The code should be fixed, if at all possible. If you are
1383 sure that the unsigned quantity can be safely cast to signed, without
1384 loss of information or undefined behavior, you can add an explicit
1385 cast, or disable the warning.
1387 * When the code is trying to take an absolute value, but the called
1388 abs() variant is for the wrong type, which can lead to truncation.
1389 If you want to disable the warning instead of fixing the code, please
1390 make sure that truncation will not occur, or it might lead to unwanted
1393 -Wtautological-undefined-compare and
1394 -Wundefined-bool-conversion
1396 These warn when C++ code is trying to compare 'this' against NULL, while
1397 'this' should never be NULL in well-defined C++ code. However, there is
1398 some legacy (pre C++11) code out there, which actively abuses this
1399 feature, which was less strictly defined in previous C++ versions.
1401 Squid and openjdk do this, for example. The warning can be turned off
1402 for C++98 and earlier, but compiling the code in C++11 mode might result
1403 in unexpected behavior; for example, the parts of the program that are
1404 unreachable could be optimized away.
1407 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1408 kernel sources have been removed. The .h files remain, since some
1409 utilities include them. This will need to be fixed later.
1410 If "mount -t oldnfs ..." is attempted, it will fail.
1411 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1412 the utilities will report errors.
1415 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1416 directories to top level SUBDIR variable when their parent
1417 directory is included in LOCAL_DIRS. Users with build systems with
1418 such hierarchies and without SUBDIR entries in the parent
1419 directory Makefiles should add them or add the directories to
1423 faith(4) and faithd(8) have been removed from the base system. Faith
1424 has been obsolete for a very long time.
1427 vt(4), the new console driver, is enabled by default. It brings
1428 support for Unicode and double-width characters, as well as
1429 support for UEFI and integration with the KMS kernel video
1432 You may need to update your console settings in /etc/rc.conf,
1433 most probably the keymap. During boot, /etc/rc.d/syscons will
1434 indicate what you need to do.
1436 vt(4) still has issues and lacks some features compared to
1437 syscons(4). See the wiki for up-to-date information:
1438 https://wiki.freebsd.org/Newcons
1440 If you want to keep using syscons(4), you can do so by adding
1441 the following line to /boot/loader.conf:
1445 pjdfstest has been integrated into kyua as an opt-in test suite.
1446 Please see share/doc/pjdfstest/README for more details on how to
1450 gperf has been removed from the base system for architectures
1451 that use clang. Ports that require gperf will obtain it from the
1455 pjdfstest has been moved from tools/regression/pjdfstest to
1459 At svn r271982, The default linux compat kernel ABI has been adjusted
1460 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1461 update. If you wish to continue using the linux-f10 compat ports,
1462 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1463 encouraged to update their linux-compat packages to linux-c6 during
1464 their next update cycle.
1467 The ofwfb driver, used to provide a graphics console on PowerPC when
1468 using vt(4), no longer allows mmap() of all physical memory. This
1469 will prevent Xorg on PowerPC with some ATI graphics cards from
1470 initializing properly unless x11-servers/xorg-server is updated to
1474 The xdev targets have been converted to using TARGET and
1475 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1478 The default unbound configuration has been modified to address
1479 issues with reverse lookups on networks that use private
1480 address ranges. If you use the local_unbound service, run
1481 "service local_unbound setup" as root to regenerate your
1482 configuration, then "service local_unbound reload" to load the
1486 The GNU texinfo and GNU info pages are not built and installed
1487 anymore, WITH_INFO knob has been added to allow to built and install
1489 UPDATE: see 20150102 entry on texinfo's removal
1492 The GNU readline library is now an INTERNALLIB - that is, it is
1493 statically linked into consumers (GDB and variants) in the base
1494 system, and the shared library is no longer installed. The
1495 devel/readline port is available for third party software that
1499 The Itanium architecture (ia64) has been removed from the list of
1500 known architectures. This is the first step in the removal of the
1504 Commit r268115 has added NFSv4.1 server support, merged from
1505 projects/nfsv4.1-server. Since this includes changes to the
1506 internal interfaces between the NFS related modules, a full
1507 build of the kernel and modules will be necessary.
1508 __FreeBSD_version has been bumped.
1511 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1512 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1513 which differs from the behaviour controlled by this knob.)
1516 Maximal length of the serial number in CTL was increased from 16 to
1517 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1518 and ctld, need to be rebuilt to work with a new kernel.
1521 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1522 1 respectively to match the upstream numbers. They were out of
1523 sync because, when they were originally added to FreeBSD, the
1524 upstream versions were not respected. These libraries are private
1525 and not yet built by default, so renumbering them should be a
1526 non-issue. However, unclean source trees will yield broken test
1527 programs once the operator executes "make delete-old-libs" after a
1528 "make installworld".
1530 Additionally, the atf-sh binary was made private by moving it into
1531 /usr/libexec/. Already-built shell test programs will keep the
1532 path to the old binary so they will break after "make delete-old"
1535 If you are using WITH_TESTS=yes (not the default), wipe the object
1536 tree and rebuild from scratch to prevent spurious test failures.
1537 This is only needed once: the misnumbered libraries and misplaced
1538 binaries have been added to OptionalObsoleteFiles.inc so they will
1539 be removed during a clean upgrade.
1542 Clang and llvm have been upgraded to 3.4.1 release.
1545 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1546 be removed to avoid issues in the future (and has been added to
1550 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1551 past, it affected all builds that used the bsd.*.mk files. The old
1552 behavior was a bug, but people may have relied upon it. To get this
1553 behavior back, you can .include /etc/src.conf from /etc/make.conf
1554 (which is still global and isn't changed). This also changes the
1555 behavior of incremental builds inside the tree of individual
1556 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1557 Although this has survived make universe and some upgrade scenarios,
1558 other upgrade scenarios may have broken. At least one form of
1559 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1560 as well... In cases where MAKESYSPATH isn't working with this
1561 setting, you'll need to set it to the full path to your tree.
1563 One side effect of all this cleaning up is that bsd.compiler.mk
1564 is no longer implicitly included by bsd.own.mk. If you wish to
1565 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1569 The lindev device has been removed since /dev/full has been made a
1570 standard device. __FreeBSD_version has been bumped.
1573 The knob WITHOUT_VI was added to the base system, which controls
1574 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1575 in order to reorder files share/termcap and didn't build ex(1) as a
1576 build tool, so building/installing with WITH_VI is highly advised for
1577 build hosts for older releases.
1579 This issue has been fixed in stable/9 and stable/10 in r277022 and
1580 r276991, respectively.
1583 The YES_HESIOD knob has been removed. It has been obsolete for
1584 a decade. Please move to using WITH_HESIOD instead or your builds
1585 will silently lack HESIOD.
1588 The uart(4) driver has been changed with respect to its handling
1589 of the low-level console. Previously the uart(4) driver prevented
1590 any process from changing the baudrate or the CLOCAL and HUPCL
1591 control flags. By removing the restrictions, operators can make
1592 changes to the serial console port without having to reboot.
1593 However, when getty(8) is started on the serial device that is
1594 associated with the low-level console, a misconfigured terminal
1595 line in /etc/ttys will now have a real impact.
1596 Before upgrading the kernel, make sure that /etc/ttys has the
1597 serial console device configured as 3wire without baudrate to
1598 preserve the previous behaviour. E.g:
1599 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1602 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1603 to improve performance. To re-enable it, if needed, run rpcbind
1604 with command line option -W.
1607 Switched back to the GPL dtc compiler due to updates in the upstream
1608 dts files not being supported by the BSDL dtc compiler. You will need
1609 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1610 may result while building dtb files during a kernel build if you fail
1611 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1614 Clang and llvm have been upgraded to 3.4 release.
1617 The nve(4) driver has been removed. Please use the nfe(4) driver
1618 for NVIDIA nForce MCP Ethernet adapters instead.
1621 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1622 This could cause certain C++ applications using shared libraries built
1623 against the previous version of libc++ to crash. The incompatibility
1624 has now been fixed, but any C++ applications or shared libraries built
1625 between r261283 and r261801 should be recompiled.
1628 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1629 capability mode support. Please note that enabling the feature in
1630 kernel is still highly recommended.
1633 OpenSSH is now built with sandbox support, and will use sandbox as
1634 the default privilege separation method. This requires Capsicum
1635 capability mode support in kernel.
1638 The libelf and libdwarf libraries have been updated to newer
1639 versions from upstream. Shared library version numbers for
1640 these two libraries were bumped. Any ports or binaries
1641 requiring these two libraries should be recompiled.
1642 __FreeBSD_version is bumped to 1100006.
1645 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1646 instead of providing an explicit one, this would prevent such
1647 Makefile from providing its own Kyuafile in the future during
1648 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1649 intervention is needed to clean an objdir if you use NO_CLEAN:
1650 # find /usr/obj -name Kyuafile | xargs rm -f
1653 The behavior of gss_pseudo_random() for the krb5 mechanism
1654 has changed, for applications requesting a longer random string
1655 than produced by the underlying enctype's pseudo-random() function.
1656 In particular, the random string produced from a session key of
1657 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1658 be different at the 17th octet and later, after this change.
1659 The counter used in the PRF+ construction is now encoded as a
1660 big-endian integer in accordance with RFC 4402.
1661 __FreeBSD_version is bumped to 1100004.
1664 The WITHOUT_ATF build knob has been removed and its functionality
1665 has been subsumed into the more generic WITHOUT_TESTS. If you were
1666 using the former to disable the build of the ATF libraries, you
1667 should change your settings to use the latter.
1670 The default version of mtree is nmtree which is obtained from
1671 NetBSD. The output is generally the same, but may vary
1672 slightly. If you found you need identical output adding
1673 "-F freebsd9" to the command line should do the trick. For the
1674 time being, the old mtree is available as fmtree.
1677 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1678 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1679 1.1.4_8 and verify bsdyml not linked in, before running "make
1681 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1683 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1686 The stable/10 branch has been created in subversion from head
1693 Avoid using make -j when upgrading. While generally safe, there are
1694 sometimes problems using -j to upgrade. If your upgrade fails with
1695 -j, please try again without -j. From time to time in the past there
1696 have been problems using -j with buildworld and/or installworld. This
1697 is especially true when upgrading between "distant" versions (eg one
1698 that cross a major release boundary or several minor releases, or when
1699 several months have passed on the -current branch).
1701 Sometimes, obscure build problems are the result of environment
1702 poisoning. This can happen because the make utility reads its
1703 environment when searching for values for global variables. To run
1704 your build attempts in an "environmental clean room", prefix all make
1705 commands with 'env -i '. See the env(1) manual page for more details.
1707 When upgrading from one major version to another it is generally best to
1708 upgrade to the latest code in the currently installed branch first, then
1709 do an upgrade to the new branch. This is the best-tested upgrade path,
1710 and has the highest probability of being successful. Please try this
1711 approach if you encounter problems with a major version upgrade. Since
1712 the stable 4.x branch point, one has generally been able to upgrade from
1713 anywhere in the most recent stable branch to head / current (or even the
1714 last couple of stable branches). See the top of this file when there's
1717 When upgrading a live system, having a root shell around before
1718 installing anything can help undo problems. Not having a root shell
1719 around can lead to problems if pam has changed too much from your
1720 starting point to allow continued authentication after the upgrade.
1722 This file should be read as a log of events. When a later event changes
1723 information of a prior event, the prior event should not be deleted.
1724 Instead, a pointer to the entry with the new information should be
1725 placed in the old entry. Readers of this file should also sanity check
1726 older entries before relying on them blindly. Authors of new entries
1727 should write them with this in mind.
1731 When upgrading the boot ZFS pool to a new version, always follow
1734 1.) recompile and reinstall the ZFS boot loader and boot block
1735 (this is part of "make buildworld" and "make installworld")
1737 2.) update the ZFS boot block on your boot drive
1739 The following example updates the ZFS boot block on the first
1740 partition (freebsd-boot) of a GPT partitioned drive ada0:
1741 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1743 Non-boot pools do not need these updates.
1747 If you are updating from a prior version of FreeBSD (even one just
1748 a few days old), you should follow this procedure. It is the most
1749 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1751 make kernel-toolchain
1752 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1753 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1755 To test a kernel once
1756 ---------------------
1757 If you just want to boot a kernel once (because you are not sure
1758 if it works, or if you want to boot a known bad kernel to provide
1759 debugging information) run
1760 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1761 nextboot -k testkernel
1763 To rebuild everything and install it on the current system.
1764 -----------------------------------------------------------
1765 # Note: sometimes if you are running current you gotta do more than
1766 # is listed here if you are upgrading from a really old current.
1768 <make sure you have good level 0 dumps>
1770 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1771 make installkernel KERNCONF=YOUR_KERNEL_HERE
1773 <reboot in single user> [3]
1780 To cross-install current onto a separate partition
1781 --------------------------------------------------
1782 # In this approach we use a separate partition to hold
1783 # current's root, 'usr', and 'var' directories. A partition
1784 # holding "/", "/usr" and "/var" should be about 2GB in
1787 <make sure you have good level 0 dumps>
1790 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1791 <maybe newfs current's root partition>
1792 <mount current's root partition on directory ${CURRENT_ROOT}>
1793 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1794 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1795 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1796 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1797 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1798 <reboot into current>
1799 <do a "native" rebuild/install as described in the previous section>
1800 <maybe install compatibility libraries from ports/misc/compat*>
1804 To upgrade in-place from stable to current
1805 ----------------------------------------------
1806 <make sure you have good level 0 dumps>
1808 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1809 make installkernel KERNCONF=YOUR_KERNEL_HERE
1811 <reboot in single user> [3]
1818 Make sure that you've read the UPDATING file to understand the
1819 tweaks to various things you need. At this point in the life
1820 cycle of current, things change often and you are on your own
1821 to cope. The defaults can also change, so please read ALL of
1822 the UPDATING entries.
1824 Also, if you are tracking -current, you must be subscribed to
1825 freebsd-current@freebsd.org. Make sure that before you update
1826 your sources that you have read and understood all the recent
1827 messages there. If in doubt, please track -stable which has
1828 much fewer pitfalls.
1830 [1] If you have third party modules, such as vmware, you
1831 should disable them at this point so they don't crash your
1834 [3] From the bootblocks, boot -s, and then do
1839 adjkerntz -i # if CMOS is wall time
1840 Also, when doing a major release upgrade, it is required that
1841 you boot into single user mode to do the installworld.
1843 [4] Note: This step is non-optional. Failure to do this step
1844 can result in a significant reduction in the functionality of the
1845 system. Attempting to do it by hand is not recommended and those
1846 that pursue this avenue should read this file carefully, as well
1847 as the archives of freebsd-current and freebsd-hackers mailing lists
1848 for potential gotchas. The -U option is also useful to consider.
1849 See mergemaster(8) for more information.
1851 [5] Usually this step is a no-op. However, from time to time
1852 you may need to do this if you get unknown user in the following
1853 step. It never hurts to do it all the time. You may need to
1854 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1855 install) after the buildworld before this step if you last updated
1856 from current before 20130425 or from -stable before 20130430.
1858 [6] This only deletes old files and directories. Old libraries
1859 can be deleted by "make delete-old-libs", but you have to make
1860 sure that no program is using those libraries anymore.
1862 [8] In order to have a kernel that can run the 4.x binaries needed to
1863 do an installworld, you must include the COMPAT_FREEBSD4 option in
1864 your kernel. Failure to do so may leave you with a system that is
1865 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1866 required to run the 5.x binaries on more recent kernels. And so on
1867 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1869 Make sure that you merge any new devices from GENERIC since the
1870 last time you updated your kernel config file.
1872 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1873 "?=" instead of the "=" assignment operator, so that buildworld can
1874 override the CPUTYPE if it needs to.
1876 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1877 not on the command line, or in /etc/make.conf. buildworld will
1878 warn if it is improperly defined.
1881 This file contains a list, in reverse chronological order, of major
1882 breakages in tracking -current. It is not guaranteed to be a complete
1883 list of such breakages, and only contains entries since September 23, 2011.
1884 If you need to see UPDATING entries from before that date, you will need
1885 to fetch an UPDATING file from an older FreeBSD release.
1887 Copyright information:
1889 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1891 Redistribution, publication, translation and use, with or without
1892 modification, in full or in part, in any form or format of this
1893 document are permitted without further permission from the author.
1895 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1896 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1897 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1898 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1899 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1900 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1901 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1902 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1903 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1904 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1905 POSSIBILITY OF SUCH DAMAGE.
1907 Contact Warner Losh if you have any questions about your use of