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 20190205: p3 FreeBSD-SA-19:01.syscall
21 FreeBSD-EN-19:06.dtrace
24 amd64: clear callee-preserved registers on syscall exit
27 Avoid leaking fp references when truncating SCM_RIGHTS control messages.
30 dtrace: fix userspace access on boxes with SMAP [EN-19:06.dtrace]
32 Fix an LLE lookup race [EN-19:07.lle]
34 20190109: p2 FreeBSD-EN-19:01.cc_cubic
36 FreeBSD-EN-19:03.sqlite
37 FreeBSD-EN-19:04.tzdata
39 Revert CC Cubic: fix underflow for cubic_cwnd() [EN-19:01.cc_cubic]
41 Fix a TCP handling of received segments. [EN-19:02.tcp]
43 Update sqlite3-3.23.1 --> sqlite3-3.26.0 (3260000) [EN-19:03.sqlite]
45 Import tzdata 2018h, 2018i [EN-19:04.tzdata]
47 20181219: p1 FreeBSD-SA-18:15.bootpd
49 bootpd: validate hardware type [SA-18:15.bootpd]
55 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
56 has been converted to a port (misc/ctm) and will be removed from
57 FreeBSD-13. A depreciation warning will be printed to stderr by
58 the ctm command, but the functionality will remain in base for all
62 The stable/12 branch has been created in subversion from head
66 Ports for the DRM modules have been simplified. Now, amd64 users should
67 just install the drm-kmod port. All others should install
70 Graphics hardware that's newer than about 2010 usually works with
71 drm-kmod. For hardware older than 2013, however, some users will need
72 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
73 than 2008 usually only works in drm-legacy-kmod. The graphics team can
74 only commit to hardware made since 2013 due to the complexity of the
75 market and difficulty to test all the older cards effectively. If you
76 have hardware supported by drm-kmod, you are strongly encouraged to use
77 that as you will get better support.
79 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
80 elsewhere, the drm and drm2 modules will be eliminated from the src base
81 soon (with a limited exception for arm). Please update to the package asap
82 and report any issues to x11@freebsd.org.
84 Generally, anybody using the drm*-kmod packages should add
85 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
86 cross-threading surprises, especially with automatic driver
87 loading from X11 startup. These will become the defaults in 13-current
91 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
92 custom kernel and module loading configuration files must be updated
93 accordingly. Moreover, interfaces previous presented as ixlvN to the
94 system are now exposed as iavfN and network configuration files must
95 be adjusted as necessary.
98 OpenSSL has been updated to version 1.1.1. This update included
99 additional various API changes througout the base system. It is
100 important to rebuild third-party software after upgrading. The value
101 of __FreeBSD_version has been bumped accordingly.
104 The legacy DRM modules and drivers have now been added to the loader's
105 module blacklist, in favor of loading them with kld_list in rc.conf(5).
106 The module blacklist may be overridden with the loader.conf(5)
107 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
111 The cam(4) based nda(4) driver will be used over nvd(4) by default on
112 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
113 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
114 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
118 Reproducible build mode is now on by default, in preparation for
119 FreeBSD 12.0. This eliminates build metadata such as the user,
120 host, and time from the kernel (and uname), unless the working tree
121 corresponds to a modified checkout from a version control system.
122 The previous behavior can be obtained by setting the /etc/src.conf
123 knob WITHOUT_REPRODUCIBLE_BUILD.
126 The Yarrow CSPRNG has been removed from the kernel as it has not been
127 supported by its designers since at least 2003. Fortuna has been the
128 default since FreeBSD-11.
131 devctl freeze/thaw have gone into the tree, the rc scripts have been
132 updated to use them and devmatch has been changed. You should update
133 kernel, userland and rc scripts all at the same time.
136 The default interpreter has been switched from 4th to Lua.
137 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
138 interpreter. If you have custom FORTH code you will need to set
139 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
140 src.conf for the build. This will create default hard links between
141 loader and loader_4th instead of loader and loader_lua, the new default.
142 If you are using UEFI it will create the proper hard link to loader.efi.
144 bhyve uses userboot.so. It remains 4th-only until some issues are solved
145 regarding coexisting with multiple versions of FreeBSD are resolved.
148 ls(1) now respects the COLORTERM environment variable used in other
149 systems and software to indicate that a colored terminal is both
150 supported and desired. If ls(1) is suddenly emitting colors, they may
151 be disabled again by either removing the unwanted COLORTERM from your
152 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
153 may not be observed in a future release.
156 The default pager for most commands has been changed to "less". To
157 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
161 The jedec_ts(4) driver has been removed. A superset of its functionality
162 is available in the jedec_dimm(4) driver, and the manpage for that
163 driver includes migration instructions. If you have "device jedec_ts"
164 in your kernel configuration file, it must be removed.
167 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
168 This should have no effect if the kernel is booted via BIOS/legacy boot.
169 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
170 has a buggy firmware that prevents a successful boot due to use of
174 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
175 support has been removed from the tree. These ports were
176 obsolete and/or known to be broken for many years.
179 loader.efi has been augmented to participate more fully in the
180 UEFI boot manager protocol. loader.efi will now look at the
181 BootXXXX environment variable to determine if a specific kernel
182 or root partition was specified. XXXX is derived from BootCurrent.
183 efibootmgr(8) manages these standard UEFI variables.
186 zfsloader's functionality has now been folded into loader.
187 zfsloader is no longer necessary once you've updated your
188 boot blocks. For a transition period, we will install a
189 hardlink for zfsloader to loader to allow a smooth transition
190 until the boot blocks can be updated (hard link because old
191 zfs boot blocks don't understand symlinks).
194 ARM64 now have efifb support, if you want to have serial console
195 on your arm64 board when an screen is connected and the bootloader
196 setup a frambuffer for us to use, just add :
200 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
201 an screen connected as the firmware will setup a framebuffer are that
202 u-boot will expose as an EFI framebuffer.
205 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
206 or take steps to update /etc/passwd before doing installworld on
207 existing systems. Do not skip the "mergemaster -Fp" step before
208 installworld, as described in the update procedures near the bottom
209 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
210 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
211 the ntp config file contain options that change file/dir locations.
212 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
213 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
214 taking steps to ensure that all required files/dirs are accessible
218 Big endian arm support has been removed.
221 The static environment setup in kernel configs is no longer mutually
222 exclusive with the loader(8) environment by default. In order to
223 restore the previous default behavior of disabling the loader(8)
224 environment if a static environment is present, you must specify
225 loader_env.disabled=1 in the static environment.
228 The ABI of syscalls used by management tools like sockstat and
229 netstat has been broken to allow 32-bit binaries to work on
230 64-bit kernels without modification. These programs will need
231 to match the kernel in order to function. External programs may
232 require minor modifications to accommodate a change of type in
233 structures from pointers to 64-bit virtual addresses.
236 On i386 and amd64 atomics are now inlined. Out of tree modules using
237 atomics will need to be rebuilt.
240 The '%I' format in the kern.corefile sysctl limits the number of
241 core files that a process can generate to the number stored in the
242 debug.ncores sysctl. The '%I' format is replaced by the single digit
243 index. Previously, if all indexes were taken the kernel would overwrite
244 only a core file with the highest index in a filename.
245 Currently the system will create a new core file if there is a free
246 index or if all slots are taken it will overwrite the oldest one.
249 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
250 6.0.1. Please see the 20141231 entry below for information about
251 prerequisites and upgrading, if you are not already using clang 3.5.0
255 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
256 needed to be changed to work with it. This change was made with r335763
257 and requires a mergemaster / etcupdate / etc to update the installed file.
260 r334930 changed the interface between the NFS modules, so they all
261 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
264 As of r334391 lld is the default amd64 system linker; it is installed
265 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
269 The kernel / userland interface for devinfo changed, so you'll
270 need a new kernel and userland as a pair for it to work (rebuilding
271 lib/libdevinfo is all that's required). devinfo and devmatch will
272 not work, but everything else will when there's a mismatch.
275 The on-disk format for hwpmc callchain records has changed to include
276 threadid corresponding to a given record. This changes the field offsets
277 and thus requires that libpmcstat be rebuilt before using a kernel
281 The vxge(4) driver has been removed. This driver was introduced into
282 HEAD one week before the Exar left the Ethernet market and is not
283 known to be used. If you have device vxge in your kernel config file
287 The amd64 kernel now requires a ld that supports ifunc to produce a
288 working kernel, either lld or a newer binutils. lld is built by default
289 on amd64, and the 'buildkernel' target uses it automatically. However,
290 it is not the default linker, so building the kernel the traditional
291 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
292 binutils port/package). lld will soon be default, and this requirement
295 NOTE: As of r334391 lld is the default system linker on amd64, and no
296 workaround is necessary.
299 The nxge(4) driver has been removed. This driver was for PCI-X 10g
300 cards made by s2io/Neterion. The company was aquired by Exar and
301 no longer sells or supports Ethernet products. If you have device
302 nxge in your kernel config file it must be removed.
305 The tz database (tzdb) has been updated to 2018e. This version more
306 correctly models time stamps in time zones with negative DST such as
307 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
308 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
309 time zone abbreviations and the tm_isdst flag.
312 The ixgb(4) driver has been removed. This driver was for an early and
313 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
314 quickly shifted to the long lived ixgbe family. If you have device
315 ixgb in your kernel config file it must be removed.
318 The lmc(4) driver has been removed. This was a WAN interface
319 card that was already reportedly rare in 2003, and had an ambiguous
320 license. If you have device lmc in your kernel config file it must
324 Support for Arcnet networks has been removed. If you have device
325 arcnet or device cm in your kernel config file they must be
329 Support for FDDI networks has been removed. If you have device
330 fddi or device fpa in your kernel config file they must be
334 In addition to supporting RFC 3164 formatted messages, the
335 syslogd(8) service is now capable of parsing RFC 5424 formatted
336 log messages. The main benefit of using RFC 5424 is that clients
337 may now send log messages with timestamps containing year numbers,
338 microseconds and time zone offsets.
340 Similarly, the syslog(3) C library function has been altered to
341 send RFC 5424 formatted messages to the local system logging
342 daemon. On systems using syslogd(8), this change should have no
343 negative impact, as long as syslogd(8) and the C library are
344 updated at the same time. On systems using a different system
345 logging daemon, it may be necessary to make configuration
346 adjustments, depending on the software used.
348 When using syslog-ng, add the 'syslog-protocol' flag to local
349 input sources to enable parsing of RFC 5424 formatted messages:
352 unix-dgram("/var/run/log" flags(syslog-protocol));
355 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
356 of the 'imuxsock' module to let messages be processed by the
357 regular RFC 3164/5424 parsing pipeline:
359 module(load="imuxsock" SysSock.UseSpecialParser="off")
361 Do note that these changes only affect communication between local
362 applications and syslogd(8). The format that syslogd(8) uses to
363 store messages on disk or forward messages to other systems
364 remains unchanged. syslogd(8) still uses RFC 3164 for these
365 purposes. Options to customize this behaviour will be added in the
366 future. Utilities that process log files stored in /var/log are
367 thus expected to continue to function as before.
369 __FreeBSD_version has been incremented to 1200061 to denote this
373 Support for token ring networks has been removed. If you
374 have "device token" in your kernel config you should remove
375 it. No device drivers supported token ring.
378 makefs was modified to be able to tag ISO9660 El Torito boot catalog
379 entries as EFI instead of overloading the i386 tag as done previously.
380 The amd64 mkisoimages.sh script used to build amd64 ISO images for
381 release was updated to use this. This may mean that makefs must be
382 updated before "make cdrom" can be run in the release directory. This
383 should be as simple as:
385 $ cd $SRCDIR/usr.sbin/makefs
386 $ make depend all install
389 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
390 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
391 Co-existance for the transition period will come shortly. Booting is a
392 complex environment and test coverage for Lua-enabled loaders has been
393 thin, so it would be prudent to assume it might not work and make
394 provisions for backup boot methods.
397 devmatch functionality has been turned on in devd. It will automatically
398 load drivers for unattached devices. This may cause unexpected drivers to
399 be loaded. Please report any problems to current@ and imp@freebsd.org.
402 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
403 6.0.0. Please see the 20141231 entry below for information about
404 prerequisites and upgrading, if you are not already using clang 3.5.0
408 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
409 This means it is used to link the kernel and userland libraries and
410 executables, but is not yet installed as /usr/bin/ld by default.
412 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
413 WITHOUT_LLD_BOOTSTRAP=yes
416 On i386, pmtimer has been removed. Its functionality has been folded
417 into apm. It was a no-op on ACPI in current for a while now (but was still
418 needed on i386 in FreeBSD 11 and earlier). Users may need to remove it
419 from kernel config files.
422 The use of RSS hash from the network card aka flowid has been
423 disabled by default for lagg(4) as it's currently incompatible with
424 the lacp and loadbalance protocols.
426 This can be re-enabled by setting the following in loader.conf:
427 net.link.lagg.default_use_flowid="1"
430 The SW_WATCHDOG option is no longer necessary to enable the
431 hardclock-based software watchdog if no hardware watchdog is
432 configured. As before, SW_WATCHDOG will cause the software
433 watchdog to be enabled even if a hardware watchdog is configured.
436 r326887 fixes the issue described in the 20171214 UPDATING entry.
437 r326888 flips the switch back to building GELI support always.
440 r362593 broke ZFS + GELI support for reasons unknown. However,
441 it also broke ZFS support generally, so GELI has been turned off
442 by default as the lesser evil in r326857. If you boot off ZFS and/or
443 GELI, it might not be a good time to update.
446 PowerPC users must update loader(8) by rebuilding world before
447 installing a new kernel, as the protocol connecting them has
448 changed. Without the update, loader metadata will not be passed
449 successfully to the kernel and users will have to enter their
450 root partition at the kernel mountroot prompt to continue booting.
451 Newer versions of loader can boot old kernels without issue.
454 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
455 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
456 to WITH/OUT_LOADER_GELI.
459 The naive and non-compliant support of posix_fallocate(2) in ZFS
460 has been removed as of r325320. The system call now returns EINVAL
461 when used on a ZFS file. Although the new behavior complies with the
462 standard, some consumers are not prepared to cope with it.
463 One known victim is lld prior to r325420.
466 Building in a FreeBSD src checkout will automatically create object
467 directories now rather than store files in the current directory if
468 'make obj' was not ran. Calling 'make obj' is no longer necessary.
469 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
470 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
474 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
475 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
476 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
477 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
478 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
479 The UNIFIED_OBJDIR option is a transitional feature that will be
480 removed for 12.0 release; please migrate to the new format for any
481 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
482 than hardcoding paths.
485 The native-xtools target no longer installs the files by default to the
486 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
487 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
490 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
491 options are changing from controlling the build if defined / undefined
492 to controlling the build with explicit 'yes' or 'no' values. They will
493 shift to WITH/WITHOUT options to match other options in the system.
496 libstand has turned into a private library for sys/boot use only.
497 It is no longer supported as a public interface outside of sys/boot.
500 The arm port has split armv6 into armv6 and armv7. armv7 is now
501 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
502 and are running a kernel from before r324363, you will need to add
503 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
506 When building multiple kernels using KERNCONF, non-existent KERNCONF
507 files will produce an error and buildkernel will fail. Previously
508 missing KERNCONF files silently failed giving no indication as to
509 why, only to subsequently discover during installkernel that the
510 desired kernel was never built in the first place.
513 The default serial number format for CTL LUNs has changed. This will
514 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
515 or iSCSI clients care about their LUNs' serial numbers. Users who
516 require serial number stability should hardcode serial numbers in
520 For 32-bit arm compiled for hard-float support, soft-floating point
521 binaries now always get their shared libraries from
522 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
523 /usr/libsoft also existed). Only users with a hard-float ld.so, but
524 soft-float everything else should be affected.
527 The geli password typed at boot is now hidden. To restore the previous
528 behavior, see geli(8) for configuration options.
531 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
532 sysctl values. Minor nit, but requires a rebuild of both world/kernel
536 "make check" behavior (made in ^/head@r295380) has been changed to
537 execute from a limited sandbox, as opposed to executing from
541 - The "beforecheck" and "aftercheck" targets are now specified.
542 - ${CHECKDIR} (added in commit noted above) has been removed.
543 - Legacy behavior can be enabled by setting
544 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
546 If the limited sandbox mode is enabled, "make check" will execute
547 "make distribution", then install, execute the tests, and clean up the
548 sandbox if successful.
550 The "make distribution" and "make install" targets are typically run as
551 root to set appropriate permissions and ownership at installation time.
552 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
553 environment if executing "make check" with limited sandbox mode using
554 an unprivileged user.
557 Since the switch to GPT disk labels, fsck for UFS/FFS has been
558 unable to automatically find alternate superblocks. As of r322297,
559 the information needed to find alternate superblocks has been
560 moved to the end of the area reserved for the boot block.
561 Filesystems created with a newfs of this vintage or later
562 will create the recovery information. If you have a filesystem
563 created prior to this change and wish to have a recovery block
564 created for your filesystem, you can do so by running fsck in
565 foreground mode (i.e., do not use the -p or -y options). As it
566 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
567 to which you should answer yes.
570 As of r321665, an NFSv4 server configuration that services
571 Kerberos mounts or clients that do not support the uid/gid in
572 owner/owner_group string capability, must explicitly enable
573 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
574 machine's /etc/rc.conf file.
577 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
578 Please see the 20141231 entry below for information about prerequisites
579 and upgrading, if you are not already using clang 3.5.0 or higher.
582 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
583 r-commands (rlogin, rsh, etc.) to be built with the base system.
586 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
587 a very major ABI incompatible change, so users of FreeBSD/powerpc must
588 be careful when performing source upgrades. It is best to run
589 'make installworld' from an alternate root system, either a live
590 CD/memory stick, or a temporary root partition. Additionally, all ports
591 must be recompiled. powerpc64 is largely unaffected, except in the case
592 of 32-bit compatibility. All 32-bit binaries will be affected.
595 Forward compatibility for the "ino64" project have been committed. This
596 will allow most new binaries to run on older kernels in a limited
597 fashion. This prevents many of the common foot-shooting actions in the
598 upgrade as well as the limited ability to roll back the kernel across
599 the ino64 upgrade. Complicated use cases may not work properly, though
600 enough simpler ones work to allow recovery in most situations.
603 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
604 if you require the GPL compiler.
607 The internal ABI used for communication between the NFS kernel modules
608 was changed by r320085, so __FreeBSD_version was bumped to
609 ensure all the NFS related modules are updated together.
612 The ABI of struct event was changed by extending the data
613 member to 64bit and adding ext fields. For upgrade, same
614 precautions as for the entry 20170523 "ino64" must be
618 The GNU roff toolchain has been removed from base. To render manpages
619 which are not supported by mandoc(1), man(1) can fallback on GNU roff
620 from ports (and recommends to install it).
621 To render roff(7) documents, consider using GNU roff from ports or the
622 heirloom doctools roff toolchain from ports via pkg install groff or
623 via pkg install heirloom-doctools.
626 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
627 smaller runtime footprint builds. This is useful for embedded systems
628 which only require one chipset support.
630 If you load it as a module, make sure this is in /boot/loader.conf:
634 This will load the HAL, all chip/RF backends and if_ath_pci.
635 If you have if_ath_pci in /boot/loader.conf, ensure it is after
636 if_ath or it will not load any HAL chipset support.
638 If you want to selectively load things (eg on ye cheape ARM/MIPS
639 platforms where RAM is at a premium) you should:
642 * load the chip modules in question
643 * load ath_rate, ath_dfs
645 * load if_ath_pci and/or if_ath_ahb depending upon your particular
646 bus bind type - this is where probe/attach is done.
648 For further comments/feedback, poke adrian@ .
651 The "ino64" 64-bit inode project has been committed, which extends
652 a number of types to 64 bits. Upgrading in place requires care and
653 adherence to the documented upgrade procedure.
655 If using a custom kernel configuration ensure that the
656 COMPAT_FREEBSD11 option is included (as during the upgrade the
657 system will be running the ino64 kernel with the existing world).
659 For the safest in-place upgrade begin by removing previous build
660 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
661 full procedure documented below under the heading "To rebuild
662 everything and install it on the current system." Specifically,
663 a reboot is required after installing the new kernel before
667 The NATM framework including the en(4), fatm(4), hatm(4), and
668 patm(4) devices has been removed. Consumers should plan a
669 migration before the end-of-life date for FreeBSD 11.
672 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
673 diff has not been implemented, if those are needed a newer version of
674 GNU diff is available via the diffutils package under the gdiff name.
677 As of r316810 for ipfilter, keep frags is no longer assumed when
678 keep state is specified in a rule. r316810 aligns ipfilter with
679 documentation in man pages separating keep frags from keep state.
680 This allows keep state to be specified without forcing keep frags
681 and allows keep frags to be specified independently of keep state.
682 To maintain previous behaviour, also specify keep frags with
683 keep state (as documented in ipf.conf.5).
686 arm64 builds now use the base system LLD 4.0.0 linker by default,
687 instead of requiring that the aarch64-binutils port or package be
688 installed. To continue using aarch64-binutils, set
689 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
692 The UDP optimization in entry 20160818 that added the sysctl
693 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
694 packets will no longer be treated as L3 broadcast packets.
697 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
698 use any explicitly assigned loopback address available in the jail
699 instead of using the first assigned address of the jail.
702 The ctl.ko module no longer implements the iSCSI target frontend:
703 cfiscsi.ko does instead.
705 If building cfiscsi.ko as a kernel module, the module can be loaded
706 via one of the following methods:
707 - `cfiscsi_load="YES"` in loader.conf(5).
708 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
709 - ctladm(8)/ctld(8), when compiled with iSCSI support
710 (`WITH_ISCSI=yes` in src.conf(5))
712 Please see cfiscsi(4) for more details.
715 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
716 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
717 same source (previously, the dependency of mmcsd.ko on mmc.ko was
718 missing, but mmcsd.ko now will refuse to load if it is incompatible
722 The syntax of ipfw(8) named states was changed to avoid ambiguity.
723 If you have used named states in the firewall rules, you need to modify
724 them after installworld and before rebooting. Now named states must
725 be prefixed with colon.
728 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
729 removed as the userland we provide cannot use them. The KMS version
730 (sys/dev/drm2) supports the same hardware.
733 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
734 Please see the 20141231 entry below for information about prerequisites
735 and upgrading, if you are not already using clang 3.5.0 or higher.
738 The code that provides support for ZFS .zfs/ directory functionality
739 has been reimplemented. It's not possible now to create a snapshot
740 by mkdir under .zfs/snapshot/. That should be the only user visible
744 EISA bus support has been removed. The WITH_EISA option is no longer
748 MCA bus support has been removed.
751 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
752 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
755 The EM_MULTIQUEUE kernel configuration option is deprecated now that
756 the em(4) driver conforms to iflib specifications.
759 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
760 IFLIB. If you have a custom kernel configuration that excludes em(4)
761 but you use igb(4), you need to re-add em(4) to your custom configuration.
764 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
765 Please see the 20141231 entry below for information about prerequisites
766 and upgrading, if you are not already using clang 3.5.0 or higher.
769 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
770 Please see the 20141231 entry below for information about prerequisites
771 and upgrading, if you are not already using clang 3.5.0 or higher.
774 The layout of the pmap structure has changed for powerpc to put the pmap
775 statistics at the front for all CPU variations. libkvm(3) and all tools
776 that link against it need to be recompiled.
779 isl(4) and cyapa(4) drivers now require a new driver,
780 chromebook_platform(4), to work properly on Chromebook-class hardware.
781 On other types of hardware the drivers may need to be configured using
782 device hints. Please see the corresponding manual pages for details.
785 The urtwn(4) driver was merged into rtwn(4) and now consists of
786 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
788 Also, firmware for RTL8188CE was renamed due to possible name
789 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
792 GNU rcs has been removed from base. It is available as packages:
793 - rcs: Latest GPLv3 GNU rcs version.
794 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
798 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
799 modules now requires that the kernel configuration contain the
800 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
803 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
804 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
807 Relocatable object files with the extension of .So have been renamed
808 to use an extension of .pico instead. The purpose of this change is
809 to avoid a name clash with shared libraries on case-insensitive file
810 systems. On those file systems, foo.So is the same file as foo.so.
813 GNU rcs has been turned off by default. It can (temporarily) be built
814 again by adding WITH_RCS knob in src.conf.
815 Otherwise, GNU rcs is available from packages:
816 - rcs: Latest GPLv3 GNU rcs version.
817 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
820 The backup_uses_rcs functionality has been removed from rc.subr.
823 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
824 two separate components, QUEUE_MACRO_DEBUG_TRACE and
825 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
826 QUEUE_MACRO_DEBUG behavior.
829 r304787 changed some ioctl interfaces between the iSCSI userspace
830 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
831 rebuilt to work with new kernels. __FreeBSD_version has been bumped
835 The UDP receive code has been updated to only treat incoming UDP
836 packets that were addressed to an L2 broadcast address as L3
837 broadcast packets. It is not expected that this will affect any
838 standards-conforming UDP application. The new behaviour can be
839 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
843 Remove the openbsd_poll system call.
844 __FreeBSD_version has been bumped because of this.
847 The stable/11 branch has been created from head@r302406.
850 The libc stub for the pipe(2) system call has been replaced with
851 a wrapper that calls the pipe2(2) system call and the pipe(2)
852 system call is now only implemented by the kernels that include
853 "options COMPAT_FREEBSD10" in their config file (this is the
854 default). Users should ensure that this option is enabled in
855 their kernel or upgrade userspace to r302092 before upgrading their
859 CAM will now strip leading spaces from SCSI disks' serial numbers.
860 This will affect users who create UFS filesystems on SCSI disks using
861 those disk's diskid device nodes. For example, if /etc/fstab
862 previously contained a line like
863 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
864 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
865 transforms like gmirror may also be affected. ZFS users should
869 The bitstring(3) API has been updated with new functionality and
870 improved performance. But it is binary-incompatible with the old API.
871 Objects built with the new headers may not be linked against objects
872 built with the old headers.
875 The brk and sbrk functions have been removed from libc on arm64.
876 Binutils from ports has been updated to not link to these
877 functions and should be updated to the latest version before
878 installing a new libc.
881 The armv6 port now defaults to hard float ABI. Limited support
882 for running both hardfloat and soft float on the same system
883 is available using the libraries installed with -DWITH_LIBSOFT.
884 This has only been tested as an upgrade path for installworld
885 and packages may fail or need manual intervention to run. New
886 packages will be needed.
888 To update an existing self-hosted armv6hf system, you must add
889 TARGET_ARCH=armv6 on the make command line for both the build
890 and the install steps.
893 Kernel modules compiled outside of a kernel build now default to
894 installing to /boot/modules instead of /boot/kernel. Many kernel
895 modules built this way (such as those in ports) already overrode
896 KMODDIR explicitly to install into /boot/modules. However,
897 manually building and installing a module from /sys/modules will
898 now install to /boot/modules instead of /boot/kernel.
901 The CAM I/O scheduler has been committed to the kernel. There should be
902 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
903 list of known rogues that claim support for this but actually corrupt
904 data is believed to be complete, be on the lookout for data
905 corruption. The known rogue list is believed to be complete:
907 o Crucial MX100, M550 drives with MU01 firmware.
908 o Micron M510 and M550 drives with MU01 firmware.
909 o Micron M500 prior to MU07 firmware
910 o Samsung 830, 840, and 850 all firmwares
911 o FCCT M500 all firmwares
913 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
914 with working NCQ TRIM. For Micron branded drives, see your sales rep for
915 updated firmware. Black listed drives will work correctly because these
916 drives work correctly so long as no NCQ TRIMs are sent to them. Given
917 this list is the same as found in Linux, it's believed there are no
918 other rogues in the market place. All other models from the above
921 To be safe, if you are at all concerned, you can quirk each of your
922 drives to prevent NCQ from being sent by setting:
923 kern.cam.ada.X.quirks="0x2"
924 in loader.conf. If the drive requires the 4k sector quirk, set the
928 The FAST_DEPEND build option has been removed and its functionality is
929 now the one true way. The old mkdep(1) style of 'make depend' has
930 been removed. See 20160311 for further details.
933 Resource range types have grown from unsigned long to uintmax_t. All
934 drivers, and anything using libdevinfo, need to be recompiled.
937 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
938 builds. It no longer runs mkdep(1) during 'make depend', and the
939 'make depend' stage can safely be skipped now as it is auto ran
940 when building 'make all' and will generate all SRCS and DPSRCS before
941 building anything else. Dependencies are gathered at compile time with
942 -MF flags kept in separate .depend files per object file. Users should
943 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
947 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
948 kernel modules. Therefore, if you load any kernel modules at boot time,
949 please install the boot loaders after you install the kernel, but before
953 make buildkernel KERNCONF=YOUR_KERNEL_HERE
954 make installkernel KERNCONF=YOUR_KERNEL_HERE
955 make -C sys/boot install
956 <reboot in single user>
958 Then follow the usual steps, described in the General Notes section,
962 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
963 see the 20141231 entry below for information about prerequisites and
964 upgrading, if you are not already using clang 3.5.0 or higher.
967 The AIO subsystem is now a standard part of the kernel. The
968 VFS_AIO kernel option and aio.ko kernel module have been removed.
969 Due to stability concerns, asynchronous I/O requests are only
970 permitted on sockets and raw disks by default. To enable
971 asynchronous I/O requests on all file types, set the
972 vfs.aio.enable_unsafe sysctl to a non-zero value.
975 The ELF object manipulation tool objcopy is now provided by the
976 ELF Tool Chain project rather than by GNU binutils. It should be a
977 drop-in replacement, with the addition of arm64 support. The
978 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
979 to obtain the GNU version if necessary.
982 Building ZFS pools on top of zvols is prohibited by default. That
983 feature has never worked safely; it's always been prone to deadlocks.
984 Using a zvol as the backing store for a VM guest's virtual disk will
985 still work, even if the guest is using ZFS. Legacy behavior can be
986 restored by setting vfs.zfs.vol.recursive=1.
989 The NONE and HPN patches has been removed from OpenSSH. They are
990 still available in the security/openssh-portable port.
993 With the addition of ypldap(8), a new _ypldap user is now required
994 during installworld. "mergemaster -p" can be used to add the user
995 prior to installworld, as documented in the handbook.
998 The tftp loader (pxeboot) now uses the option root-path directive. As a
999 consequence it no longer looks for a pxeboot.4th file on the tftp
1000 server. Instead it uses the regular /boot infrastructure as with the
1004 The code to start recording plug and play data into the modules has
1005 been committed. While the old tools will properly build a new kernel,
1006 a number of warnings about "unknown metadata record 4" will be produced
1007 for an older kldxref. To avoid such warnings, make sure to rebuild
1008 the kernel toolchain (or world). Make sure that you have r292078 or
1009 later when trying to build 292077 or later before rebuilding.
1012 Debug data files are now built by default with 'make buildworld' and
1013 installed with 'make installworld'. This facilitates debugging but
1014 requires more disk space both during the build and for the installed
1015 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1019 r291527 changed the internal interface between the nfsd.ko and
1020 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1021 __FreeBSD_version has been bumped because of this.
1024 Add support for unicode collation strings leads to a change of
1025 order of files listed by ls(1) for example. To get back to the old
1026 behaviour, set LC_COLLATE environment variable to "C".
1028 Databases administrators will need to reindex their databases given
1029 collation results will be different.
1031 Due to a bug in install(1) it is recommended to remove the ancient
1032 locales before running make installworld.
1034 rm -rf /usr/share/locale/*
1037 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1038 libcrypto.so.7 or libssl.so.7 must be recompiled.
1041 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1042 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1043 should be replaced with isp_2400 and isp_2500 modules respectively.
1046 The build previously allowed using 'make -n' to not recurse into
1047 sub-directories while showing what commands would be executed, and
1048 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1049 and 'make -N' will not.
1052 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1053 and etcupdate will now use this file. A custom sendmail.cf is now
1054 updated via this mechanism rather than via installworld. If you had
1055 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1056 want to remove the exclusion or change it to "always install".
1057 /etc/mail/sendmail.cf is now managed the same way regardless of
1058 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1059 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1062 Compatibility shims for legacy ATA device names have been removed.
1063 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1064 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1065 environment variables, /dev/ad* and /dev/ar* symbolic links.
1068 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1069 Please see the 20141231 entry below for information about prerequisites
1070 and upgrading, if you are not already using clang 3.5.0 or higher.
1073 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1074 and renamed from .symbols to .debug. This reduces the size requirements
1075 on the boot partition or file system and provides consistency with
1076 userland debug files.
1078 When using the supported kernel installation method the
1079 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1080 as is done with /boot/kernel.
1082 Developers wishing to maintain the historical behavior of installing
1083 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1086 The wireless drivers had undergone changes that remove the 'parent
1087 interface' from the ifconfig -l output. The rc.d network scripts
1088 used to check presence of a parent interface in the list, so old
1089 scripts would fail to start wireless networking. Thus, etcupdate(3)
1090 or mergemaster(8) run is required after kernel update, to update your
1091 rc.d scripts in /etc.
1094 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1095 These configurations are now automatically interpreted as
1096 'scrub fragment reassemble'.
1099 Kernel-loadable modules for the random(4) device are back. To use
1100 them, the kernel must have
1103 options RANDOM_LOADABLE
1105 kldload(8) can then be used to load random_fortuna.ko
1106 or random_yarrow.ko. Please note that due to the indirect
1107 function calls that the loadable modules need to provide,
1108 the build-in variants will be slightly more efficient.
1110 The random(4) kernel option RANDOM_DUMMY has been retired due to
1111 unpopularity. It was not all that useful anyway.
1114 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1115 Control over building the ELF Tool Chain tools is now provided by
1116 the WITHOUT_TOOLCHAIN knob.
1119 The polarity of Pulse Per Second (PPS) capture events with the
1120 uart(4) driver has been corrected. Prior to this change the PPS
1121 "assert" event corresponded to the trailing edge of a positive PPS
1122 pulse and the "clear" event was the leading edge of the next pulse.
1124 As the width of a PPS pulse in a typical GPS receiver is on the
1125 order of 1 millisecond, most users will not notice any significant
1126 difference with this change.
1128 Anyone who has compensated for the historical polarity reversal by
1129 configuring a negative offset equal to the pulse width will need to
1130 remove that workaround.
1133 The default group assigned to /dev/dri entries has been changed
1134 from 'wheel' to 'video' with the id of '44'. If you want to have
1135 access to the dri devices please add yourself to the video group
1138 # pw groupmod video -m $USER
1141 The menu.rc and loader.rc files will now be replaced during
1142 upgrades. Please migrate local changes to menu.rc.local and
1143 loader.rc.local instead.
1146 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1147 strings and strip have been removed. The src.conf(5) knob
1148 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1151 As ZFS requires more kernel stack pages than is the default on some
1152 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1153 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1155 Please consider using 'options KSTACK_PAGES=X' where X is greater
1156 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1159 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1160 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1161 default, i.e., they will not contain "::". For example, instead
1162 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1163 to have a more specific match, such as different map entries for
1164 IPv6:0:0 vs IPv6:0. This change requires that configuration
1165 data (including maps, files, classes, custom ruleset, etc.) must
1166 use the same format, so make certain such configuration data is
1167 upgrading. As a very simple check search for patterns like
1168 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1169 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1170 the cf option UseCompressedIPv6Addresses.
1173 The default kernel entropy-processing algorithm is now
1174 Fortuna, replacing Yarrow.
1176 Assuming you have 'device random' in your kernel config
1177 file, the configurations allow a kernel option to override
1178 this default. You may choose *ONE* of:
1180 options RANDOM_YARROW # Legacy /dev/random algorithm.
1181 options RANDOM_DUMMY # Blocking-only driver.
1183 If you have neither, you get Fortuna. For most people,
1184 read no further, Fortuna will give a /dev/random that works
1185 like it always used to, and the difference will be irrelevant.
1187 If you remove 'device random', you get *NO* kernel-processed
1188 entropy at all. This may be acceptable to folks building
1189 embedded systems, but has complications. Carry on reading,
1190 and it is assumed you know what you need.
1192 *PLEASE* read random(4) and random(9) if you are in the
1193 habit of tweaking kernel configs, and/or if you are a member
1194 of the embedded community, wanting specific and not-usual
1195 behaviour from your security subsystems.
1197 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1198 random', you will NOT have a functioning /dev/random, and
1199 many cryptographic features will not work, including SSH.
1200 You may also find strange behaviour from the random(3) set
1201 of library functions, in particular sranddev(3), srandomdev(3)
1202 and arc4random(3). The reason for this is that the KERN_ARND
1203 sysctl only returns entropy if it thinks it has some to
1204 share, and with RANDOM_DUMMY or no 'device random' this
1208 An additional fix for the issue described in the 20150614 sendmail
1209 entry below has been committed in revision 284717.
1212 FreeBSD's old make (fmake) has been removed from the system. It is
1213 available as the devel/fmake port or via pkg install fmake.
1216 The fix for the issue described in the 20150614 sendmail entry
1217 below has been committed in revision 284436. The work
1218 around described in that entry is no longer needed unless the
1219 default setting is overridden by a confDH_PARAMETERS configuration
1220 setting of '5' or pointing to a 512 bit DH parameter file.
1223 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1224 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1225 and devel/kyua to version 0.20+ and adjust any calling code to work
1226 with Kyuafile and kyua.
1229 The import of openssl to address the FreeBSD-SA-15:10.openssl
1230 security advisory includes a change which rejects handshakes
1231 with DH parameters below 768 bits. sendmail releases prior
1232 to 8.15.2 (not yet released), defaulted to a 512 bit
1233 DH parameter setting for client connections. To work around
1234 this interoperability, sendmail can be configured to use a
1235 2048 bit DH parameter by:
1237 1. Edit /etc/mail/`hostname`.mc
1238 2. If a setting for confDH_PARAMETERS does not exist or
1239 exists and is set to a string beginning with '5',
1240 replace it with '2'.
1241 3. If a setting for confDH_PARAMETERS exists and is set to
1242 a file path, create a new file with:
1243 openssl dhparam -out /path/to/file 2048
1244 4. Rebuild the .cf file:
1245 cd /etc/mail/; make; make install
1246 5. Restart sendmail:
1247 cd /etc/mail/; make restart
1249 A sendmail patch is coming, at which time this file will be
1253 Generation of legacy formatted entries have been disabled by default
1254 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1255 entries were converted to use the new format by default when the new,
1256 machine independent format have been added and supported since FreeBSD
1259 Please see the pwd_mkdb(8) manual page for further details.
1262 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1263 20141231 entry below for information about prerequisites and upgrading,
1264 if you are not already using 3.5.0 or higher.
1267 TI platform code switched to using vendor DTS files and this update
1268 may break existing systems running on Beaglebone, Beaglebone Black,
1271 - dtb files should be regenerated/reinstalled. Filenames are the
1272 same but content is different now
1273 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1274 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1275 addressing scheme is now pin 25 on /dev/gpioc3.
1276 - Pandaboard: /etc/ttys should be updated, serial console device is
1277 now /dev/ttyu2, not /dev/ttyu0
1280 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1281 If you need the GNU extension from groff soelim(1), install groff
1282 from package: pkg install groff, or via ports: textproc/groff.
1285 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1286 defined in symlink(7); previously symlinks were silently ignored.
1289 The const qualifier has been removed from iconv(3) to comply with
1290 POSIX. The ports tree is aware of this from r384038 onwards.
1293 Libraries specified by LIBADD in Makefiles must have a corresponding
1294 DPADD_<lib> variable to ensure correct dependencies. This is now
1295 enforced in src.libnames.mk.
1298 From legacy ata(4) driver was removed support for SATA controllers
1299 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1300 Kernel modules ataahci and ataadaptec were removed completely,
1301 replaced by ahci and mvs modules respectively.
1304 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1305 the 20141231 entry below for information about prerequisites and
1306 upgrading, if you are not already using 3.5.0 or higher.
1309 The 32-bit PowerPC kernel has been changed to a position-independent
1310 executable. This can only be booted with a version of loader(8)
1311 newer than January 31, 2015, so make sure to update both world and
1312 kernel before rebooting.
1315 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1316 but before r278950, the RNG was not seeded properly. Immediately
1317 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1318 ssh keys or openssl keys) that were generated w/ a kernel from that
1319 range. This does not affect programs that directly used /dev/random
1320 or /dev/urandom. All userland uses of arc4random(3) are affected.
1323 The autofs(4) ABI was changed in order to restore binary compatibility
1324 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1325 with the new kernel.
1328 The powerpc64 kernel has been changed to a position-independent
1329 executable. This can only be booted with a new version of loader(8),
1330 so make sure to update both world and kernel before rebooting.
1333 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1334 only release, no new features have been added. Please see the 20141231
1335 entry below for information about prerequisites and upgrading, if you
1336 are not already using 3.5.0.
1339 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1340 taken from the ELF Tool Chain project rather than GNU binutils. They
1341 should be drop-in replacements, with the addition of arm64 support.
1342 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1343 binutils tools, if necessary. See 20150805 for updated information.
1346 The default Unbound configuration now enables remote control
1347 using a local socket. Users who have already enabled the
1348 local_unbound service should regenerate their configuration
1349 by running "service local_unbound setup" as root.
1352 The GNU texinfo and GNU info pages have been removed.
1353 To be able to view GNU info pages please install texinfo from ports.
1356 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1358 As of this release, a prerequisite for building clang, llvm and lldb is
1359 a C++11 capable compiler and C++11 standard library. This means that to
1360 be able to successfully build the cross-tools stage of buildworld, with
1361 clang as the bootstrap compiler, your system compiler or cross compiler
1362 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1363 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1366 On any standard FreeBSD 10.x or 11.x installation, where clang and
1367 libc++ are on by default (that is, on x86 or arm), this should work out
1370 On 9.x installations where clang is enabled by default, e.g. on x86 and
1371 powerpc, libc++ will not be enabled by default, so libc++ should be
1372 built (with clang) and installed first. If both clang and libc++ are
1373 missing, build clang first, then use it to build libc++.
1375 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1376 the instructions for 9.x above.
1378 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1379 default, and do not build clang.
1381 Many embedded systems are resource constrained, and will not be able to
1382 build clang in a reasonable time, or in some cases at all. In those
1383 cases, cross building bootable systems on amd64 is a workaround.
1385 This new version of clang introduces a number of new warnings, of which
1386 the following are most likely to appear:
1390 This warns in two cases, for both C and C++:
1391 * When the code is trying to take the absolute value of an unsigned
1392 quantity, which is effectively a no-op, and almost never what was
1393 intended. The code should be fixed, if at all possible. If you are
1394 sure that the unsigned quantity can be safely cast to signed, without
1395 loss of information or undefined behavior, you can add an explicit
1396 cast, or disable the warning.
1398 * When the code is trying to take an absolute value, but the called
1399 abs() variant is for the wrong type, which can lead to truncation.
1400 If you want to disable the warning instead of fixing the code, please
1401 make sure that truncation will not occur, or it might lead to unwanted
1404 -Wtautological-undefined-compare and
1405 -Wundefined-bool-conversion
1407 These warn when C++ code is trying to compare 'this' against NULL, while
1408 'this' should never be NULL in well-defined C++ code. However, there is
1409 some legacy (pre C++11) code out there, which actively abuses this
1410 feature, which was less strictly defined in previous C++ versions.
1412 Squid and openjdk do this, for example. The warning can be turned off
1413 for C++98 and earlier, but compiling the code in C++11 mode might result
1414 in unexpected behavior; for example, the parts of the program that are
1415 unreachable could be optimized away.
1418 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1419 kernel sources have been removed. The .h files remain, since some
1420 utilities include them. This will need to be fixed later.
1421 If "mount -t oldnfs ..." is attempted, it will fail.
1422 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1423 the utilities will report errors.
1426 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1427 directories to top level SUBDIR variable when their parent
1428 directory is included in LOCAL_DIRS. Users with build systems with
1429 such hierarchies and without SUBDIR entries in the parent
1430 directory Makefiles should add them or add the directories to
1434 faith(4) and faithd(8) have been removed from the base system. Faith
1435 has been obsolete for a very long time.
1438 vt(4), the new console driver, is enabled by default. It brings
1439 support for Unicode and double-width characters, as well as
1440 support for UEFI and integration with the KMS kernel video
1443 You may need to update your console settings in /etc/rc.conf,
1444 most probably the keymap. During boot, /etc/rc.d/syscons will
1445 indicate what you need to do.
1447 vt(4) still has issues and lacks some features compared to
1448 syscons(4). See the wiki for up-to-date information:
1449 https://wiki.freebsd.org/Newcons
1451 If you want to keep using syscons(4), you can do so by adding
1452 the following line to /boot/loader.conf:
1456 pjdfstest has been integrated into kyua as an opt-in test suite.
1457 Please see share/doc/pjdfstest/README for more details on how to
1461 gperf has been removed from the base system for architectures
1462 that use clang. Ports that require gperf will obtain it from the
1466 pjdfstest has been moved from tools/regression/pjdfstest to
1470 At svn r271982, The default linux compat kernel ABI has been adjusted
1471 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1472 update. If you wish to continue using the linux-f10 compat ports,
1473 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1474 encouraged to update their linux-compat packages to linux-c6 during
1475 their next update cycle.
1478 The ofwfb driver, used to provide a graphics console on PowerPC when
1479 using vt(4), no longer allows mmap() of all physical memory. This
1480 will prevent Xorg on PowerPC with some ATI graphics cards from
1481 initializing properly unless x11-servers/xorg-server is updated to
1485 The xdev targets have been converted to using TARGET and
1486 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1489 The default unbound configuration has been modified to address
1490 issues with reverse lookups on networks that use private
1491 address ranges. If you use the local_unbound service, run
1492 "service local_unbound setup" as root to regenerate your
1493 configuration, then "service local_unbound reload" to load the
1497 The GNU texinfo and GNU info pages are not built and installed
1498 anymore, WITH_INFO knob has been added to allow to built and install
1500 UPDATE: see 20150102 entry on texinfo's removal
1503 The GNU readline library is now an INTERNALLIB - that is, it is
1504 statically linked into consumers (GDB and variants) in the base
1505 system, and the shared library is no longer installed. The
1506 devel/readline port is available for third party software that
1510 The Itanium architecture (ia64) has been removed from the list of
1511 known architectures. This is the first step in the removal of the
1515 Commit r268115 has added NFSv4.1 server support, merged from
1516 projects/nfsv4.1-server. Since this includes changes to the
1517 internal interfaces between the NFS related modules, a full
1518 build of the kernel and modules will be necessary.
1519 __FreeBSD_version has been bumped.
1522 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1523 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1524 which differs from the behaviour controlled by this knob.)
1527 Maximal length of the serial number in CTL was increased from 16 to
1528 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1529 and ctld, need to be rebuilt to work with a new kernel.
1532 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1533 1 respectively to match the upstream numbers. They were out of
1534 sync because, when they were originally added to FreeBSD, the
1535 upstream versions were not respected. These libraries are private
1536 and not yet built by default, so renumbering them should be a
1537 non-issue. However, unclean source trees will yield broken test
1538 programs once the operator executes "make delete-old-libs" after a
1539 "make installworld".
1541 Additionally, the atf-sh binary was made private by moving it into
1542 /usr/libexec/. Already-built shell test programs will keep the
1543 path to the old binary so they will break after "make delete-old"
1546 If you are using WITH_TESTS=yes (not the default), wipe the object
1547 tree and rebuild from scratch to prevent spurious test failures.
1548 This is only needed once: the misnumbered libraries and misplaced
1549 binaries have been added to OptionalObsoleteFiles.inc so they will
1550 be removed during a clean upgrade.
1553 Clang and llvm have been upgraded to 3.4.1 release.
1556 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1557 be removed to avoid issues in the future (and has been added to
1561 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1562 past, it affected all builds that used the bsd.*.mk files. The old
1563 behavior was a bug, but people may have relied upon it. To get this
1564 behavior back, you can .include /etc/src.conf from /etc/make.conf
1565 (which is still global and isn't changed). This also changes the
1566 behavior of incremental builds inside the tree of individual
1567 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1568 Although this has survived make universe and some upgrade scenarios,
1569 other upgrade scenarios may have broken. At least one form of
1570 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1571 as well... In cases where MAKESYSPATH isn't working with this
1572 setting, you'll need to set it to the full path to your tree.
1574 One side effect of all this cleaning up is that bsd.compiler.mk
1575 is no longer implicitly included by bsd.own.mk. If you wish to
1576 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1580 The lindev device has been removed since /dev/full has been made a
1581 standard device. __FreeBSD_version has been bumped.
1584 The knob WITHOUT_VI was added to the base system, which controls
1585 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1586 in order to reorder files share/termcap and didn't build ex(1) as a
1587 build tool, so building/installing with WITH_VI is highly advised for
1588 build hosts for older releases.
1590 This issue has been fixed in stable/9 and stable/10 in r277022 and
1591 r276991, respectively.
1594 The YES_HESIOD knob has been removed. It has been obsolete for
1595 a decade. Please move to using WITH_HESIOD instead or your builds
1596 will silently lack HESIOD.
1599 The uart(4) driver has been changed with respect to its handling
1600 of the low-level console. Previously the uart(4) driver prevented
1601 any process from changing the baudrate or the CLOCAL and HUPCL
1602 control flags. By removing the restrictions, operators can make
1603 changes to the serial console port without having to reboot.
1604 However, when getty(8) is started on the serial device that is
1605 associated with the low-level console, a misconfigured terminal
1606 line in /etc/ttys will now have a real impact.
1607 Before upgrading the kernel, make sure that /etc/ttys has the
1608 serial console device configured as 3wire without baudrate to
1609 preserve the previous behaviour. E.g:
1610 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1613 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1614 to improve performance. To re-enable it, if needed, run rpcbind
1615 with command line option -W.
1618 Switched back to the GPL dtc compiler due to updates in the upstream
1619 dts files not being supported by the BSDL dtc compiler. You will need
1620 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1621 may result while building dtb files during a kernel build if you fail
1622 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1625 Clang and llvm have been upgraded to 3.4 release.
1628 The nve(4) driver has been removed. Please use the nfe(4) driver
1629 for NVIDIA nForce MCP Ethernet adapters instead.
1632 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1633 This could cause certain C++ applications using shared libraries built
1634 against the previous version of libc++ to crash. The incompatibility
1635 has now been fixed, but any C++ applications or shared libraries built
1636 between r261283 and r261801 should be recompiled.
1639 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1640 capability mode support. Please note that enabling the feature in
1641 kernel is still highly recommended.
1644 OpenSSH is now built with sandbox support, and will use sandbox as
1645 the default privilege separation method. This requires Capsicum
1646 capability mode support in kernel.
1649 The libelf and libdwarf libraries have been updated to newer
1650 versions from upstream. Shared library version numbers for
1651 these two libraries were bumped. Any ports or binaries
1652 requiring these two libraries should be recompiled.
1653 __FreeBSD_version is bumped to 1100006.
1656 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1657 instead of providing an explicit one, this would prevent such
1658 Makefile from providing its own Kyuafile in the future during
1659 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1660 intervention is needed to clean an objdir if you use NO_CLEAN:
1661 # find /usr/obj -name Kyuafile | xargs rm -f
1664 The behavior of gss_pseudo_random() for the krb5 mechanism
1665 has changed, for applications requesting a longer random string
1666 than produced by the underlying enctype's pseudo-random() function.
1667 In particular, the random string produced from a session key of
1668 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1669 be different at the 17th octet and later, after this change.
1670 The counter used in the PRF+ construction is now encoded as a
1671 big-endian integer in accordance with RFC 4402.
1672 __FreeBSD_version is bumped to 1100004.
1675 The WITHOUT_ATF build knob has been removed and its functionality
1676 has been subsumed into the more generic WITHOUT_TESTS. If you were
1677 using the former to disable the build of the ATF libraries, you
1678 should change your settings to use the latter.
1681 The default version of mtree is nmtree which is obtained from
1682 NetBSD. The output is generally the same, but may vary
1683 slightly. If you found you need identical output adding
1684 "-F freebsd9" to the command line should do the trick. For the
1685 time being, the old mtree is available as fmtree.
1688 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1689 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1690 1.1.4_8 and verify bsdyml not linked in, before running "make
1692 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1694 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1697 The stable/10 branch has been created in subversion from head
1704 Avoid using make -j when upgrading. While generally safe, there are
1705 sometimes problems using -j to upgrade. If your upgrade fails with
1706 -j, please try again without -j. From time to time in the past there
1707 have been problems using -j with buildworld and/or installworld. This
1708 is especially true when upgrading between "distant" versions (eg one
1709 that cross a major release boundary or several minor releases, or when
1710 several months have passed on the -current branch).
1712 Sometimes, obscure build problems are the result of environment
1713 poisoning. This can happen because the make utility reads its
1714 environment when searching for values for global variables. To run
1715 your build attempts in an "environmental clean room", prefix all make
1716 commands with 'env -i '. See the env(1) manual page for more details.
1718 When upgrading from one major version to another it is generally best to
1719 upgrade to the latest code in the currently installed branch first, then
1720 do an upgrade to the new branch. This is the best-tested upgrade path,
1721 and has the highest probability of being successful. Please try this
1722 approach if you encounter problems with a major version upgrade. Since
1723 the stable 4.x branch point, one has generally been able to upgrade from
1724 anywhere in the most recent stable branch to head / current (or even the
1725 last couple of stable branches). See the top of this file when there's
1728 When upgrading a live system, having a root shell around before
1729 installing anything can help undo problems. Not having a root shell
1730 around can lead to problems if pam has changed too much from your
1731 starting point to allow continued authentication after the upgrade.
1733 This file should be read as a log of events. When a later event changes
1734 information of a prior event, the prior event should not be deleted.
1735 Instead, a pointer to the entry with the new information should be
1736 placed in the old entry. Readers of this file should also sanity check
1737 older entries before relying on them blindly. Authors of new entries
1738 should write them with this in mind.
1742 When upgrading the boot ZFS pool to a new version, always follow
1745 1.) recompile and reinstall the ZFS boot loader and boot block
1746 (this is part of "make buildworld" and "make installworld")
1748 2.) update the ZFS boot block on your boot drive
1750 The following example updates the ZFS boot block on the first
1751 partition (freebsd-boot) of a GPT partitioned drive ada0:
1752 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1754 Non-boot pools do not need these updates.
1758 If you are updating from a prior version of FreeBSD (even one just
1759 a few days old), you should follow this procedure. It is the most
1760 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1762 make kernel-toolchain
1763 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1764 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1766 To test a kernel once
1767 ---------------------
1768 If you just want to boot a kernel once (because you are not sure
1769 if it works, or if you want to boot a known bad kernel to provide
1770 debugging information) run
1771 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1772 nextboot -k testkernel
1774 To rebuild everything and install it on the current system.
1775 -----------------------------------------------------------
1776 # Note: sometimes if you are running current you gotta do more than
1777 # is listed here if you are upgrading from a really old current.
1779 <make sure you have good level 0 dumps>
1781 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1782 make installkernel KERNCONF=YOUR_KERNEL_HERE
1784 <reboot in single user> [3]
1791 To cross-install current onto a separate partition
1792 --------------------------------------------------
1793 # In this approach we use a separate partition to hold
1794 # current's root, 'usr', and 'var' directories. A partition
1795 # holding "/", "/usr" and "/var" should be about 2GB in
1798 <make sure you have good level 0 dumps>
1801 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1802 <maybe newfs current's root partition>
1803 <mount current's root partition on directory ${CURRENT_ROOT}>
1804 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1805 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1806 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1807 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1808 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1809 <reboot into current>
1810 <do a "native" rebuild/install as described in the previous section>
1811 <maybe install compatibility libraries from ports/misc/compat*>
1815 To upgrade in-place from stable to current
1816 ----------------------------------------------
1817 <make sure you have good level 0 dumps>
1819 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1820 make installkernel KERNCONF=YOUR_KERNEL_HERE
1822 <reboot in single user> [3]
1829 Make sure that you've read the UPDATING file to understand the
1830 tweaks to various things you need. At this point in the life
1831 cycle of current, things change often and you are on your own
1832 to cope. The defaults can also change, so please read ALL of
1833 the UPDATING entries.
1835 Also, if you are tracking -current, you must be subscribed to
1836 freebsd-current@freebsd.org. Make sure that before you update
1837 your sources that you have read and understood all the recent
1838 messages there. If in doubt, please track -stable which has
1839 much fewer pitfalls.
1841 [1] If you have third party modules, such as vmware, you
1842 should disable them at this point so they don't crash your
1845 [3] From the bootblocks, boot -s, and then do
1850 adjkerntz -i # if CMOS is wall time
1851 Also, when doing a major release upgrade, it is required that
1852 you boot into single user mode to do the installworld.
1854 [4] Note: This step is non-optional. Failure to do this step
1855 can result in a significant reduction in the functionality of the
1856 system. Attempting to do it by hand is not recommended and those
1857 that pursue this avenue should read this file carefully, as well
1858 as the archives of freebsd-current and freebsd-hackers mailing lists
1859 for potential gotchas. The -U option is also useful to consider.
1860 See mergemaster(8) for more information.
1862 [5] Usually this step is a no-op. However, from time to time
1863 you may need to do this if you get unknown user in the following
1864 step. It never hurts to do it all the time. You may need to
1865 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1866 install) after the buildworld before this step if you last updated
1867 from current before 20130425 or from -stable before 20130430.
1869 [6] This only deletes old files and directories. Old libraries
1870 can be deleted by "make delete-old-libs", but you have to make
1871 sure that no program is using those libraries anymore.
1873 [8] In order to have a kernel that can run the 4.x binaries needed to
1874 do an installworld, you must include the COMPAT_FREEBSD4 option in
1875 your kernel. Failure to do so may leave you with a system that is
1876 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1877 required to run the 5.x binaries on more recent kernels. And so on
1878 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1880 Make sure that you merge any new devices from GENERIC since the
1881 last time you updated your kernel config file.
1883 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1884 "?=" instead of the "=" assignment operator, so that buildworld can
1885 override the CPUTYPE if it needs to.
1887 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1888 not on the command line, or in /etc/make.conf. buildworld will
1889 warn if it is improperly defined.
1892 This file contains a list, in reverse chronological order, of major
1893 breakages in tracking -current. It is not guaranteed to be a complete
1894 list of such breakages, and only contains entries since September 23, 2011.
1895 If you need to see UPDATING entries from before that date, you will need
1896 to fetch an UPDATING file from an older FreeBSD release.
1898 Copyright information:
1900 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1902 Redistribution, publication, translation and use, with or without
1903 modification, in full or in part, in any form or format of this
1904 document are permitted without further permission from the author.
1906 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1907 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1908 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1909 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1910 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1911 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1912 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1913 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1914 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1915 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1916 POSSIBILITY OF SUCH DAMAGE.
1918 Contact Warner Losh if you have any questions about your use of
projects / FreeBSD / FreeBSD.git / blob