1 Updating Information for FreeBSD stable/13 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 updating system packages
16 Bump __FreeBSD_version to 1300521 after merging LinuxKPI and
17 net80211 changes in order to support building various wireless
18 drivers. This is to help other external consumers of LinuxKPI
19 and net80211 to deal accordingly.
22 Commit a599f9f7620b deleted the variable called nfs_maxcopyrange
23 from nfscommon.ko, since it no longer needs to be global. As such,
24 the other nfs modules must be rebuilt from up to date sources.
25 Bump __FreeBSD_version to 1300516 for this.
28 As of commit 622809b0868f OpenSSL no longer enables kernel TLS
29 by default. Users can enable kernel TLS via the "KTLS" SSL
30 option. This can be enabled globally by using a custom
31 OpenSSL config file via OPENSSL_CONF or via an
32 application-specific configuration option for applications
33 which permit setting SSL options via SSL_CONF_cmd(3).
36 Commits 9fb6e613373c and 9ec7dbf46b0a both changed the internal
37 KAPI between the NFS modules. Bump __FreeBSD_version to 1300514.
38 All NFS modules must be rebuilt from sources.
41 Commit b69019c14cd8 removes pf's DIOCGETSTATESNV ioctl.
42 As of be70c7a50d32 it is no longer used by userspace, but it does mean
43 users may not be able to enumerate pf states if they update the kernel
44 past c021ff986e2b without first updating userspace past be70c7a50d32.
47 Bump __FreeBSD_version to 1300512 after merging LinuxKPI, OFED,
48 net80211, and driver changes in order to support building
49 Intel wireless iwlwifi drivers. This is especially needed for
50 drm-kmod which needs updates after this.
53 The 20210707 awk update brought in a change in behavior. This has
54 been corrected as of d4d252c49976. Between these dates, if you
55 installed a new awk binary, you may not be able to build a new
56 kernel because the change in behavior affected the genoffset
57 script used to build the kernel. If you did update, the fix is
58 to update your sources past the above hash and do
61 % sudo -E make install
62 to enable building kernels again.
65 Commit 8a04edfdcbd2 changes the default minor version
66 used for NFSv4 mounts to the highest minor version supported
67 by the NFSv4 server. This default can be overridden by using
68 the "minorversion" mount option.
69 The consensus of a discussion on freebsd-current@ indicated
70 that this would be acceptable to do and would not be considered
74 awk has been updated to the latest one-true-awk version 20210215.
75 This contains a number of minor bug fixes.
78 Commit ca179c4d74f2/632e3f2f3a66 changed the package in which
79 the OpenSSL libraries and utilities are packaged.
80 It is recommended for pkgbase user to do:
81 pkg install -f FreeBSD-openssl
82 before pkg upgrade otherwise some dependencies might not be met
83 and pkg will stop working as libssl will not be present anymore
87 Commit 841006678745 changed the internal KAPI between the krpc
88 and nfsd modules. As such, they must both be rebuilt from
90 __FreeBSD_version is bumped to 1300510.
93 Commit 272f39942254 changed the internal KAPI between the
94 nscl.ko and nfscommon.ko modules, so they both need to be
98 Commit 5a45802b3c8c changed the internal KAPI between
99 the krpc and NFS. As such, the krpc, nfscommon and
100 nfscl modules must all be rebuilt from sources.
101 Without this patch, NFSv4.1/4.2 mounts should not
102 be done with the nfscbd(8) daemon running, to avoid
103 needing a working back channel for server->client RPCs.
106 Various LinuxKPI functionality was added which conflicts with DRM.
107 Please update your drm-kmod port to after the __FreeBSD_verison 1300139
111 The stable/13 branch has been created from main.
114 PC Card attachments for all devices have been removed. In the case of
115 wi and cmx, the entire drivers were removed because they were only
116 PC Card devices. FreeBSD_version 1300134 should be used for this
117 since it was bumped so recently.
120 Transport-independent parts of HID support have been split off the USB
121 code in to separate subsystem. Kernel configs which include one of
122 ums, ukbd, uhid, atp, wsp, wmt, uaudio, ugold or ucycom drivers should
123 be updated with adding of "device hid" line.
126 ncurses installation has been modified to only keep the widechar
127 enabled version. Incremental build is broken for that change, so it
128 requires a clean build.
131 The FreeBSD project has migrated from Subversion to Git. Temporary
132 instructions can be found at
133 https://github.com/bsdimp/freebsd-git-docs/blob/main/src-cvt.md
134 and other documents in that repo.
137 The services database has been updated to cover more of the basic
138 services expected in a modern system. The database is big enough
139 that it will cause issues in mergemaster in Releases previous to
140 12.2 and 11.3, or in very old current systems from before r358154.
143 Obsolete in-tree GDB 6.1.1 has been removed. GDB (including kgdb)
144 may be installed from ports or packages.
147 ping6 has been merged into ping. It can now be called as "ping -6".
148 See ping(8) for details.
151 Default value of net.add_addr_allfibs has been changed to 0.
152 If you have multi-fib configuration and rely on existence of all
153 interface routes in every fib, you need to set the above sysctl to 1.
155 The internal pre-processor in the calendar(1) program has been
156 extended to support more C pre-processor commands (e.g. #ifdef, #else,
157 and #undef) and to detect unbalanced conditional statements.
158 Error messages have been extended to include the filename and line
159 number if processing stops to help fixing malformed data files.
162 All the data files for the calendar(1) program, except calendar.freebsd,
163 have been moved to the deskutils/calendar-data port, much like the
164 jewish calendar entries were moved to deskutils/hebcal years ago. After
165 make delete-old-files, you need to install it to retain full
166 functionality. calendar(1) will issue a reminder for files it can't
170 LINT files are no longer generated. We now include the relevant NOTES
171 files. Note: This may cause conflicts with updating in some cases.
172 find sys -name LINT\* -delete
173 is suggested across this commit to remove the generated LINT files.
175 If you have tried to update with generated files there, the svn
176 command you want to un-auger the tree is
179 and then do the above find from the top level. Substitute 'amd64'
180 above with where the error message indicates a conflict.
183 OpenZFS support has been integrated. Do not upgrade root pools until
184 the loader is updated to support zstd. Furthermore, we caution against
185 'zpool upgrade' for the next few weeks. The change should be transparent
186 unless you want to use new features.
188 Not all "NO_CLEAN" build scenarios work across these changes. Many
189 scenarios have been tested and fixed, but rebuilding kernels without
190 rebuilding world may fail.
192 The ZFS cache file has moved from /boot to /etc to match the OpenZFS
193 upstream default. A fallback to /boot has been added for mountroot.
195 Pool auto import behavior at boot has been moved from the kernel module
196 to an explicit "zpool import -a" in one of the rc scripts enabled by
197 zfs_enable=YES. This means your non-root zpools won't auto import until
198 you upgrade your /etc/rc.d files.
201 The resume code now notifies devd with the 'kernel' system
202 rather than the old 'kern' subsystem to be consistent with
203 other use. The old notification will be created as well, but
204 will be removed prior to FreeBSD 14.0.
207 r362275 changed the internal API between the kernel RPC and the
208 NFS modules. As such, all the modules must be recompiled from
212 r364330 modified the internal API used between the NFS modules.
213 As such, all the NFS modules must be re-compiled from sources.
216 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
217 been upgraded to 11.0.0. Please see the 20141231 entry below for
218 information about prerequisites and upgrading, if you are not already
219 using clang 3.5.0 or higher.
222 r364092 modified the internal ABI used between the kernel NFS
223 modules. As such, all of these modules need to be rebuilt
224 from sources, so a version bump was done.
227 Makefile.inc has been updated to work around the issue documented in
228 20200729. It was a case where the optimization of using symbolic links
229 to point to binaries created a situation where we'd run new binaries
230 with old libraries starting midway through the installworld process.
233 r363679 has redefined some undefined behavior in regcomp(3); notably,
234 extraneous escapes of most ordinary characters will no longer be
235 accepted. An exp-run has identified all of the problems with this in
236 ports, but other non-ports software may need extra escapes removed to
237 continue to function.
239 Because of this change, installworld may encounter the following error
240 from rtld: Undefined symbol "regcomp@FBSD_1.6" -- It is imperative that
241 you do not halt installworld. Instead, let it run to completion (whether
242 successful or not) and run installworld once more.
245 A new implementation of bc and dc has been imported in r362681. This
246 implementation corrects non-conformant behavior of the previous bc
247 and adds GNU bc compatible options. It offers a number of extensions,
248 is much faster on large values, and has support for message catalogs
249 (a number of languages are already supported, contributions of further
250 languages welcome). The option WITHOUT_GH_BC can be used to build the
251 world with the previous versions of bc and dc.
254 r362639 changed the internal API used between the NFS kernel modules.
255 As such, they all need to be rebuilt from sources.
258 r362158 changed the arguments for VFS_CHECKEXP(). As such, any
259 out of tree file systems need to be modified and rebuilt.
260 Also, any file systems that are modules must be rebuilt.
263 read(2) of a directory fd is now rejected by default. root may
264 re-enable it for system root only on non-ZFS filesystems with the
265 security.bsd.allow_read_dir sysctl(8) MIB if
266 security.bsd.suser_enabled=1.
268 It may be advised to setup aliases for grep to default to `-d skip` if
269 commonly non-recursively grepping a list that includes directories and
270 the potential for the resulting stderr output is not tolerable. Example
271 aliases are now installed, commented out, in /root/.cshrc and
275 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
276 been upgraded to 10.0.1. Please see the 20141231 entry below for
277 information about prerequisites and upgrading, if you are not already
278 using clang 3.5.0 or higher.
281 Support for obsolete compilers has been removed from the build system.
282 Clang 6 and GCC 6.4 are the minimum supported versions.
285 closefrom(2) has been moved under COMPAT12, and replaced in libc with a
286 stub that calls close_range(2). If using a custom kernel configuration,
287 you may want to ensure that the COMPAT_FREEBSD12 option is included, as
288 a slightly older -CURRENT userland and older FreeBSD userlands may not
289 be functional without closefrom(2).
292 Upstream DTS from Linux 5.6 was merged and they now have the SID
293 and THS (Secure ID controller and THermal Sensor) node present.
294 The DTB overlays have now been removed from the tree for the H3/H5 and
295 A64 SoCs and the aw_sid and aw_thermal driver have been updated to
296 deal with upstream DTS. If you are using those overlays you need to
297 remove them from loader.conf and update the DTBs on the FAT partition.
300 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
301 been upgraded to 10.0.0. Please see the 20141231 entry below for
302 information about prerequisites and upgrading, if you are not already
303 using clang 3.5.0 or higher.
306 The amd(8) automount daemon has been removed from the source tree.
307 As of FreeBSD 10.1 autofs(5) is the preferred tool for automounting.
308 amd is still available in the sysutils/am-utils port.
311 Removed brooktree driver (bktr.4) from the tree.
314 The WITH_GPL_DTC option has been removed. The BSD-licenced device tree
315 compiler in usr.bin/dtc is used on all architectures which use dtc, and
316 the GPL dtc is available (if needed) from the sysutils/dtc port.
319 The WITHOUT_LLVM_LIBUNWIND option has been removed. LLVM's libunwind
320 is used by all supported CPU architectures.
323 GCC 4.2.1 has been removed from the tree. The WITH_GCC,
324 WITH_GCC_BOOTSTRAP, and WITH_GNUCXX options are no longer available.
325 Users who wish to build FreeBSD with GCC must use the external toolchain
329 ncurses has been updated to a newer version (6.2-20200215). Given the ABI
330 has changed, users will have to rebuild all the ports that are linked to
334 The size of struct vnet and the magic cookie have changed.
335 Users need to recompile libkvm and all modules using VIMAGE
336 together with their new kernel.
339 Defining the long deprecated NO_CTF, NO_DEBUG_FILES, NO_INSTALLLIB,
340 NO_MAN, NO_PROFILE, and NO_WARNS variables is now an error. Update
341 your Makefiles and scripts to define MK_<var>=no instead as required.
343 One exception to this is that program or library Makefiles should
344 define MAN to empty rather than setting MK_MAN=no.
347 Clang/LLVM is now the default compiler and LLD the default
351 make universe no longer uses GCC 4.2.1 on any architectures.
352 Architectures not supported by in-tree Clang/LLVM require an
353 external toolchain package.
356 GCC 4.2.1 is now not built by default, as part of the GCC 4.2.1
357 retirement plan. Specifically, the GCC, GCC_BOOTSTRAP, and GNUCXX
358 options default to off for all supported CPU architectures. As a
359 short-term transition aid they may be enabled via WITH_* options.
360 GCC 4.2.1 is expected to be removed from the tree on 2020-03-31.
363 Support for armv5 has been disconnected and is being removed. The
364 machine combination MACHINE=arm MACHINE_ARCH=arm is no longer valid.
365 You must now use a MACHINE_ARCH of armv6 or armv7. The default
366 MACHINE_ARCH for MACHINE=arm is now armv7.
369 Clang/LLVM is now the default compiler for all powerpc architectures.
370 LLD is now the default linker for powerpc64. The change for powerpc64
371 also includes a change to the ELFv2 ABI, incompatible with the existing
375 Kernel-loadable random(4) modules are no longer unloadable.
378 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
379 been upgraded to 9.0.1. Please see the 20141231 entry below for
380 information about prerequisites and upgrading, if you are not already
381 using clang 3.5.0 or higher.
384 r355677 has modified the internal interface used between the
385 NFS modules in the kernel. As such, they must all be upgraded
386 simultaneously. I will do a version bump for this.
389 The root certificates of the Mozilla CA Certificate Store have been
390 imported into the base system and can be managed with the certctl(8)
391 utility. If you have installed the security/ca_root_nss port or package
392 with the ETCSYMLINK option (the default), be advised that there may be
393 differences between those included in the port and those included in
394 base due to differences in nss branch used as well as general update
395 frequency. Note also that certctl(8) cannot manage certs in the
396 format used by the security/ca_root_nss port.
399 The amd(8) automount daemon has been disabled by default, and will be
400 removed in the future. As of FreeBSD 10.1 the autofs(5) is available
404 The nctgpio and wbwd drivers have been moved to the superio bus.
405 If you have one of these drivers in a kernel configuration, then
406 you should add device superio to it. If you use one of these drivers
407 as a module and you compile a custom set of modules, then you should
408 add superio to the set.
411 KPIs for network drivers to access interface addresses have changed.
412 Users need to recompile NIC driver modules together with kernel.
415 The net.link.tap.user_open sysctl no longer prevents user opening of
416 already created /dev/tapNN devices. Access is still controlled by
417 node permissions, just like tun devices. The net.link.tap.user_open
418 sysctl is now used only to allow users to perform devfs cloning of
419 tap devices, and the subsequent open may not succeed if the user is not
420 in the appropriate group. This sysctl may be deprecated/removed
421 completely in the future.
424 mips, powerpc, and sparc64 are no longer built as part of
425 universe / tinderbox unless MAKE_OBSOLETE_GCC is defined. If
426 not defined, mips, powerpc, and sparc64 builds will look for
427 the xtoolchain binaries and if installed use them for universe
428 builds. As llvm 9.0 becomes vetted for these architectures, they
429 will be removed from the list.
432 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
433 been upgraded to 9.0.0. Please see the 20141231 entry below for
434 information about prerequisites and upgrading, if you are not already
435 using clang 3.5.0 or higher.
438 The hpt27xx, hptmv, hptnr, and hptrr drivers have been removed from
439 GENERIC. They are available as modules and can be loaded by adding
440 to /boot/loader.conf hpt27xx_load="YES", hptmv_load="YES",
441 hptnr_load="YES", or hptrr_load="YES", respectively.
444 ntpd no longer by default locks its pages in memory, allowing them
445 to be paged out by the kernel. Use rlimit memlock to restore
446 historic BSD behaviour. For example, add "rlimit memlock 32"
447 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
450 Several of ping6's options have been renamed for better consistency
451 with ping. If you use any of -ARWXaghmrtwx, you must update your
452 scripts. See ping6(8) for details.
455 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
456 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
457 been removed from mount_fusefs(8). You can safely remove them from
458 your scripts, because they had no effect.
460 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
461 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
462 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
463 sysctls have been removed. If you felt the need to set any of them to
464 a non-default value, please tell asomers@FreeBSD.org why.
467 Default permissions on the /var/account/acct file (and copies of it
468 rotated by periodic daily scripts) are changed from 0644 to 0640
469 because the file contains sensitive information that should not be
470 world-readable. If the /var/account directory must be created by
471 rc.d/accounting, the mode used is now 0750. Admins who use the
472 accounting feature are encouraged to change the mode of an existing
473 /var/account directory to 0750 or 0700.
476 Entropy collection and the /dev/random device are no longer optional
477 components. The "device random" option has been removed.
478 Implementations of distilling algorithms can still be made loadable
479 with "options RANDOM_LOADABLE" (e.g., random_fortuna.ko).
482 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
483 been upgraded to 8.0.1. Please see the 20141231 entry below for
484 information about prerequisites and upgrading, if you are not already
485 using clang 3.5.0 or higher.
488 A fix was applied to i386 kernel modules to avoid panics with
489 dpcpu or vnet. Users need to recompile i386 kernel modules
490 having pcpu or vnet sections or they will refuse to load.
493 User-wired pages now have their own counter,
494 vm.stats.vm.v_user_wire_count. The vm.max_wired sysctl was renamed
495 to vm.max_user_wired and changed from an unsigned int to an unsigned
496 long. bhyve VMs wired with the -S are now subject to the user
497 wiring limit; the vm.max_user_wired sysctl may need to be tuned to
498 avoid running into the limit.
501 The IPSEC option has been removed from GENERIC. Users requiring
502 ipsec(4) must now load the ipsec(4) kernel module.
505 The tap(4) driver has been folded into tun(4), and the module has been
506 renamed to tuntap. You should update any kld_list="if_tap" or
507 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
508 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
509 module instead, and "device tap" or "device tun" entries in kernel
510 config files to select the tuntap device instead.
513 The following knobs have been added related to tradeoffs between
514 safe use of the random device and availability in the absence of
517 kern.random.initial_seeding.bypass_before_seeding: tunable; set
518 non-zero to bypass the random device prior to seeding, or zero to
519 block random requests until the random device is initially seeded.
520 For now, set to 1 (unsafe) by default to restore pre-r346250 boot
521 availability properties.
523 kern.random.initial_seeding.read_random_bypassed_before_seeding:
524 read-only diagnostic sysctl that is set when bypass is enabled and
525 read_random(9) is bypassed, to enable programmatic handling of this
526 initial condition, if desired.
528 kern.random.initial_seeding.arc4random_bypassed_before_seeding:
529 Similar to the above, but for for arc4random(9) initial seeding.
531 kern.random.initial_seeding.disable_bypass_warnings: tunable; set
532 non-zero to disable warnings in dmesg when the same conditions are
533 met as for the diagnostic sysctls above. Defaults to zero, i.e.,
534 produce warnings in dmesg when the conditions are met.
537 The loadable random module KPI has changed; the random_infra_init()
538 routine now requires a 3rd function pointer for a bool (*)(void)
539 method that returns true if the random device is seeded (and
540 therefore unblocked).
543 r345895 reverts r320698. This implies that an nfsuserd(8) daemon
544 built from head sources between r320757 (July 6, 2017) and
545 r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
546 is added to the command line.
547 nfsuserd daemons built from head sources that are post-r338192 are
548 not affected and should continue to work.
551 The fuse(4) module has been renamed to fusefs(4) for consistency with
552 other filesystems. You should update any kld_load="fuse" entries in
553 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
554 "options FUSE" entries in kernel config files.
557 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
558 8.0.0. Please see the 20141231 entry below for information about
559 prerequisites and upgrading, if you are not already using clang 3.5.0
563 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
564 compiled into your custom kernel, add 'device xz' statement to the
568 drm and drm2 have been removed from the tree. Please see
569 https://wiki.freebsd.org/Graphics for the latest information on
570 migrating to the drm ports.
573 Iflib is no longer unconditionally compiled into the kernel. Drivers
574 using iflib and statically compiled into the kernel, now require
575 the 'device iflib' config option. For the same drivers loaded as
576 modules on kernels not having 'device iflib', the iflib.ko module
577 is loaded automatically.
580 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
581 options no longer exist since r343219 and r343427 respectively;
582 nothing uses them, so they should be just removed from custom
586 r342635 changes the way efibootmgr(8) works by requiring users to add
587 the -b (bootnum) parameter for commands where the bootnum was previously
588 specified with each option. For example 'efibootmgr -B 0001' is now
589 'efibootmgr -B -b 0001'.
592 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
593 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
594 servers that have vfs.nfsd.nfs_privport set will only allow mounts
595 from clients using a reserved port#. Since both the FreeBSD and Linux
596 NFSv4 clients use reserved port#s by default, this should not affect
600 The XLP config has been removed. We can't support 64-bit atomics in this
601 kernel because it is running in 32-bit mode. XLP users must transition
602 to running a 64-bit kernel (XLP64 or XLPN32).
604 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
605 the preferred emulator today and we don't need two different ones.
607 The old sibyte / swarm / Broadcom BCM1250 support has been
608 removed from the mips port.
611 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
612 7.0.1. Please see the 20141231 entry below for information about
613 prerequisites and upgrading, if you are not already using clang 3.5.0
617 Remove the timed and netdate programs from the base tree. Setting
618 the time with these daemons has been obsolete for over a decade.
621 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
622 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
623 it produces broken binaries when ifuncs are in use. Users needing
624 GNU ld should install the binutils port or package.
627 The BSD crtbegin and crtend code has been enabled by default. It has
628 had extensive testing on amd64, arm64, and i386. It can be disabled
629 by building a world with -DWITHOUT_BSD_CRTBEGIN.
632 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
633 has been converted to a port (misc/ctm) and will be removed from
634 FreeBSD-13. It is available as a package (ctm) for all supported
638 The default newsyslog.conf(5) file has been changed to only include
639 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
640 the filenames end in '.conf' and do not begin with a '.'.
642 You should check the configuration files in these two directories match
643 this naming convention. You can verify which configuration files are
644 being included using the command:
648 Ports for the DRM modules have been simplified. Now, amd64 users should
649 just install the drm-kmod port. All others should install
652 Graphics hardware that's newer than about 2010 usually works with
653 drm-kmod. For hardware older than 2013, however, some users will need
654 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
655 than 2008 usually only works in drm-legacy-kmod. The graphics team can
656 only commit to hardware made since 2013 due to the complexity of the
657 market and difficulty to test all the older cards effectively. If you
658 have hardware supported by drm-kmod, you are strongly encouraged to use
659 that as you will get better support.
661 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
662 elsewhere, the drm and drm2 modules will be eliminated from the src base
663 soon (with a limited exception for arm). Please update to the package
664 asap and report any issues to x11@freebsd.org.
666 Generally, anybody using the drm*-kmod packages should add
667 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
668 cross-threading surprises, especially with automatic driver
669 loading from X11 startup. These will become the defaults in 13-current
673 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
674 custom kernel and module loading configuration files must be updated
675 accordingly. Moreover, interfaces previous presented as ixlvN to the
676 system are now exposed as iavfN and network configuration files must
677 be adjusted as necessary.
680 OpenSSL has been updated to version 1.1.1. This update included
681 additional various API changes throughout the base system. It is
682 important to rebuild third-party software after upgrading. The value
683 of __FreeBSD_version has been bumped accordingly.
686 The legacy DRM modules and drivers have now been added to the loader's
687 module blacklist, in favor of loading them with kld_list in rc.conf(5).
688 The module blacklist may be overridden with the loader.conf(5)
689 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
693 The cam(4) based nda(4) driver will be used over nvd(4) by default on
694 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
695 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
696 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
700 Reproducible build mode is now on by default, in preparation for
701 FreeBSD 12.0. This eliminates build metadata such as the user,
702 host, and time from the kernel (and uname), unless the working tree
703 corresponds to a modified checkout from a version control system.
704 The previous behavior can be obtained by setting the /etc/src.conf
705 knob WITHOUT_REPRODUCIBLE_BUILD.
708 The Yarrow CSPRNG has been removed from the kernel as it has not been
709 supported by its designers since at least 2003. Fortuna has been the
710 default since FreeBSD-11.
713 devctl freeze/thaw have gone into the tree, the rc scripts have been
714 updated to use them and devmatch has been changed. You should update
715 kernel, userland and rc scripts all at the same time.
718 The default interpreter has been switched from 4th to Lua.
719 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
720 interpreter. If you have custom FORTH code you will need to set
721 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
722 src.conf for the build. This will create default hard links between
723 loader and loader_4th instead of loader and loader_lua, the new default.
724 If you are using UEFI it will create the proper hard link to loader.efi.
726 bhyve uses userboot.so. It remains 4th-only until some issues are solved
727 regarding coexisting with multiple versions of FreeBSD are resolved.
730 ls(1) now respects the COLORTERM environment variable used in other
731 systems and software to indicate that a colored terminal is both
732 supported and desired. If ls(1) is suddenly emitting colors, they may
733 be disabled again by either removing the unwanted COLORTERM from your
734 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
735 may not be observed in a future release.
738 The default pager for most commands has been changed to "less". To
739 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
743 The jedec_ts(4) driver has been removed. A superset of its functionality
744 is available in the jedec_dimm(4) driver, and the manpage for that
745 driver includes migration instructions. If you have "device jedec_ts"
746 in your kernel configuration file, it must be removed.
749 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
750 This should have no effect if the kernel is booted via BIOS/legacy boot.
751 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
752 has a buggy firmware that prevents a successful boot due to use of
756 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
757 support has been removed from the tree. These ports were
758 obsolete and/or known to be broken for many years.
761 loader.efi has been augmented to participate more fully in the
762 UEFI boot manager protocol. loader.efi will now look at the
763 BootXXXX environment variable to determine if a specific kernel
764 or root partition was specified. XXXX is derived from BootCurrent.
765 efibootmgr(8) manages these standard UEFI variables.
768 zfsloader's functionality has now been folded into loader.
769 zfsloader is no longer necessary once you've updated your
770 boot blocks. For a transition period, we will install a
771 hardlink for zfsloader to loader to allow a smooth transition
772 until the boot blocks can be updated (hard link because old
773 zfs boot blocks don't understand symlinks).
776 ARM64 now have efifb support, if you want to have serial console
777 on your arm64 board when an screen is connected and the bootloader
778 setup a frame buffer for us to use, just add :
782 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
783 an screen connected as the firmware will setup a frame buffer are that
784 u-boot will expose as an EFI frame buffer.
787 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
788 or take steps to update /etc/passwd before doing installworld on
789 existing systems. Do not skip the "mergemaster -Fp" step before
790 installworld, as described in the update procedures near the bottom
791 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
792 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
793 the ntp config file contain options that change file/dir locations.
794 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
795 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
796 taking steps to ensure that all required files/dirs are accessible
800 Big endian arm support has been removed.
803 The static environment setup in kernel configs is no longer mutually
804 exclusive with the loader(8) environment by default. In order to
805 restore the previous default behavior of disabling the loader(8)
806 environment if a static environment is present, you must specify
807 loader_env.disabled=1 in the static environment.
810 The ABI of syscalls used by management tools like sockstat and
811 netstat has been broken to allow 32-bit binaries to work on
812 64-bit kernels without modification. These programs will need
813 to match the kernel in order to function. External programs may
814 require minor modifications to accommodate a change of type in
815 structures from pointers to 64-bit virtual addresses.
818 On i386 and amd64 atomics are now inlined. Out of tree modules using
819 atomics will need to be rebuilt.
822 The '%I' format in the kern.corefile sysctl limits the number of
823 core files that a process can generate to the number stored in the
824 debug.ncores sysctl. The '%I' format is replaced by the single digit
825 index. Previously, if all indexes were taken the kernel would overwrite
826 only a core file with the highest index in a filename.
827 Currently the system will create a new core file if there is a free
828 index or if all slots are taken it will overwrite the oldest one.
831 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
832 6.0.1. Please see the 20141231 entry below for information about
833 prerequisites and upgrading, if you are not already using clang 3.5.0
837 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
838 needed to be changed to work with it. This change was made with r335763
839 and requires a mergemaster / etcupdate / etc to update the installed
843 r334930 changed the interface between the NFS modules, so they all
844 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
847 As of r334391 lld is the default amd64 system linker; it is installed
848 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
852 The kernel / userland interface for devinfo changed, so you'll
853 need a new kernel and userland as a pair for it to work (rebuilding
854 lib/libdevinfo is all that's required). devinfo and devmatch will
855 not work, but everything else will when there's a mismatch.
858 The on-disk format for hwpmc callchain records has changed to include
859 threadid corresponding to a given record. This changes the field offsets
860 and thus requires that libpmcstat be rebuilt before using a kernel
864 The vxge(4) driver has been removed. This driver was introduced into
865 HEAD one week before the Exar left the Ethernet market and is not
866 known to be used. If you have device vxge in your kernel config file
870 The amd64 kernel now requires a ld that supports ifunc to produce a
871 working kernel, either lld or a newer binutils. lld is built by default
872 on amd64, and the 'buildkernel' target uses it automatically. However,
873 it is not the default linker, so building the kernel the traditional
874 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
875 binutils port/package). lld will soon be default, and this requirement
878 NOTE: As of r334391 lld is the default system linker on amd64, and no
879 workaround is necessary.
882 The nxge(4) driver has been removed. This driver was for PCI-X 10g
883 cards made by s2io/Neterion. The company was acquired by Exar and
884 no longer sells or supports Ethernet products. If you have device
885 nxge in your kernel config file it must be removed.
888 The tz database (tzdb) has been updated to 2018e. This version more
889 correctly models time stamps in time zones with negative DST such as
890 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
891 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
892 time zone abbreviations and the tm_isdst flag.
895 The ixgb(4) driver has been removed. This driver was for an early and
896 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
897 quickly shifted to the long lived ixgbe family. If you have device
898 ixgb in your kernel config file it must be removed.
901 The lmc(4) driver has been removed. This was a WAN interface
902 card that was already reportedly rare in 2003, and had an ambiguous
903 license. If you have device lmc in your kernel config file it must
907 Support for Arcnet networks has been removed. If you have device
908 arcnet or device cm in your kernel config file they must be
912 Support for FDDI networks has been removed. If you have device
913 fddi or device fpa in your kernel config file they must be
917 In addition to supporting RFC 3164 formatted messages, the
918 syslogd(8) service is now capable of parsing RFC 5424 formatted
919 log messages. The main benefit of using RFC 5424 is that clients
920 may now send log messages with timestamps containing year numbers,
921 microseconds and time zone offsets.
923 Similarly, the syslog(3) C library function has been altered to
924 send RFC 5424 formatted messages to the local system logging
925 daemon. On systems using syslogd(8), this change should have no
926 negative impact, as long as syslogd(8) and the C library are
927 updated at the same time. On systems using a different system
928 logging daemon, it may be necessary to make configuration
929 adjustments, depending on the software used.
931 When using syslog-ng, add the 'syslog-protocol' flag to local
932 input sources to enable parsing of RFC 5424 formatted messages:
935 unix-dgram("/var/run/log" flags(syslog-protocol));
938 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
939 of the 'imuxsock' module to let messages be processed by the
940 regular RFC 3164/5424 parsing pipeline:
942 module(load="imuxsock" SysSock.UseSpecialParser="off")
944 Do note that these changes only affect communication between local
945 applications and syslogd(8). The format that syslogd(8) uses to
946 store messages on disk or forward messages to other systems
947 remains unchanged. syslogd(8) still uses RFC 3164 for these
948 purposes. Options to customize this behaviour will be added in the
949 future. Utilities that process log files stored in /var/log are
950 thus expected to continue to function as before.
952 __FreeBSD_version has been incremented to 1200061 to denote this
956 Support for token ring networks has been removed. If you
957 have "device token" in your kernel config you should remove
958 it. No device drivers supported token ring.
961 makefs was modified to be able to tag ISO9660 El Torito boot catalog
962 entries as EFI instead of overloading the i386 tag as done previously.
963 The amd64 mkisoimages.sh script used to build amd64 ISO images for
964 release was updated to use this. This may mean that makefs must be
965 updated before "make cdrom" can be run in the release directory. This
966 should be as simple as:
968 $ cd $SRCDIR/usr.sbin/makefs
969 $ make depend all install
972 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
973 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
974 Co-existence for the transition period will come shortly. Booting is a
975 complex environment and test coverage for Lua-enabled loaders has been
976 thin, so it would be prudent to assume it might not work and make
977 provisions for backup boot methods.
980 devmatch functionality has been turned on in devd. It will automatically
981 load drivers for unattached devices. This may cause unexpected drivers
982 to be loaded. Please report any problems to current@ and
986 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
987 6.0.0. Please see the 20141231 entry below for information about
988 prerequisites and upgrading, if you are not already using clang 3.5.0
992 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
993 This means it is used to link the kernel and userland libraries and
994 executables, but is not yet installed as /usr/bin/ld by default.
996 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
997 WITHOUT_LLD_BOOTSTRAP=yes
1000 On i386, pmtimer has been removed. Its functionality has been folded
1001 into apm. It was a no-op on ACPI in current for a while now (but was
1002 still needed on i386 in FreeBSD 11 and earlier). Users may need to
1003 remove it from kernel config files.
1006 The use of RSS hash from the network card aka flowid has been
1007 disabled by default for lagg(4) as it's currently incompatible with
1008 the lacp and loadbalance protocols.
1010 This can be re-enabled by setting the following in loader.conf:
1011 net.link.lagg.default_use_flowid="1"
1014 The SW_WATCHDOG option is no longer necessary to enable the
1015 hardclock-based software watchdog if no hardware watchdog is
1016 configured. As before, SW_WATCHDOG will cause the software
1017 watchdog to be enabled even if a hardware watchdog is configured.
1020 r326887 fixes the issue described in the 20171214 UPDATING entry.
1021 r326888 flips the switch back to building GELI support always.
1024 r362593 broke ZFS + GELI support for reasons unknown. However,
1025 it also broke ZFS support generally, so GELI has been turned off
1026 by default as the lesser evil in r326857. If you boot off ZFS and/or
1027 GELI, it might not be a good time to update.
1030 PowerPC users must update loader(8) by rebuilding world before
1031 installing a new kernel, as the protocol connecting them has
1032 changed. Without the update, loader metadata will not be passed
1033 successfully to the kernel and users will have to enter their
1034 root partition at the kernel mountroot prompt to continue booting.
1035 Newer versions of loader can boot old kernels without issue.
1038 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
1039 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
1040 to WITH/OUT_LOADER_GELI.
1043 The naive and non-compliant support of posix_fallocate(2) in ZFS
1044 has been removed as of r325320. The system call now returns EINVAL
1045 when used on a ZFS file. Although the new behavior complies with the
1046 standard, some consumers are not prepared to cope with it.
1047 One known victim is lld prior to r325420.
1050 Building in a FreeBSD src checkout will automatically create object
1051 directories now rather than store files in the current directory if
1052 'make obj' was not ran. Calling 'make obj' is no longer necessary.
1053 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
1054 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
1058 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
1059 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
1060 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
1061 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
1062 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
1063 The UNIFIED_OBJDIR option is a transitional feature that will be
1064 removed for 12.0 release; please migrate to the new format for any
1065 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
1066 than hardcoding paths.
1069 The native-xtools target no longer installs the files by default to the
1070 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
1071 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
1074 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
1075 options are changing from controlling the build if defined / undefined
1076 to controlling the build with explicit 'yes' or 'no' values. They will
1077 shift to WITH/WITHOUT options to match other options in the system.
1080 libstand has turned into a private library for sys/boot use only.
1081 It is no longer supported as a public interface outside of sys/boot.
1084 The arm port has split armv6 into armv6 and armv7. armv7 is now
1085 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
1086 and are running a kernel from before r324363, you will need to add
1087 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
1090 When building multiple kernels using KERNCONF, non-existent KERNCONF
1091 files will produce an error and buildkernel will fail. Previously
1092 missing KERNCONF files silently failed giving no indication as to
1093 why, only to subsequently discover during installkernel that the
1094 desired kernel was never built in the first place.
1097 The default serial number format for CTL LUNs has changed. This will
1098 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
1099 or iSCSI clients care about their LUNs' serial numbers. Users who
1100 require serial number stability should hardcode serial numbers in
1104 For 32-bit arm compiled for hard-float support, soft-floating point
1105 binaries now always get their shared libraries from
1106 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
1107 /usr/libsoft also existed). Only users with a hard-float ld.so, but
1108 soft-float everything else should be affected.
1111 The geli password typed at boot is now hidden. To restore the previous
1112 behavior, see geli(8) for configuration options.
1115 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
1116 sysctl values. Minor nit, but requires a rebuild of both world/kernel
1120 "make check" behavior (made in ^/head@r295380) has been changed to
1121 execute from a limited sandbox, as opposed to executing from
1125 - The "beforecheck" and "aftercheck" targets are now specified.
1126 - ${CHECKDIR} (added in commit noted above) has been removed.
1127 - Legacy behavior can be enabled by setting
1128 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
1130 If the limited sandbox mode is enabled, "make check" will execute
1131 "make distribution", then install, execute the tests, and clean up the
1132 sandbox if successful.
1134 The "make distribution" and "make install" targets are typically run as
1135 root to set appropriate permissions and ownership at installation time.
1136 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
1137 environment if executing "make check" with limited sandbox mode using
1138 an unprivileged user.
1141 Since the switch to GPT disk labels, fsck for UFS/FFS has been
1142 unable to automatically find alternate superblocks. As of r322297,
1143 the information needed to find alternate superblocks has been
1144 moved to the end of the area reserved for the boot block.
1145 Filesystems created with a newfs of this vintage or later
1146 will create the recovery information. If you have a filesystem
1147 created prior to this change and wish to have a recovery block
1148 created for your filesystem, you can do so by running fsck in
1149 foreground mode (i.e., do not use the -p or -y options). As it
1150 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
1151 to which you should answer yes.
1154 As of r321665, an NFSv4 server configuration that services
1155 Kerberos mounts or clients that do not support the uid/gid in
1156 owner/owner_group string capability, must explicitly enable
1157 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
1158 machine's /etc/rc.conf file.
1161 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
1162 Please see the 20141231 entry below for information about prerequisites
1163 and upgrading, if you are not already using clang 3.5.0 or higher.
1166 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
1167 r-commands (rlogin, rsh, etc.) to be built with the base system.
1170 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
1171 a very major ABI incompatible change, so users of FreeBSD/powerpc must
1172 be careful when performing source upgrades. It is best to run
1173 'make installworld' from an alternate root system, either a live
1174 CD/memory stick, or a temporary root partition. Additionally, all ports
1175 must be recompiled. powerpc64 is largely unaffected, except in the case
1176 of 32-bit compatibility. All 32-bit binaries will be affected.
1179 Forward compatibility for the "ino64" project have been committed. This
1180 will allow most new binaries to run on older kernels in a limited
1181 fashion. This prevents many of the common foot-shooting actions in the
1182 upgrade as well as the limited ability to roll back the kernel across
1183 the ino64 upgrade. Complicated use cases may not work properly, though
1184 enough simpler ones work to allow recovery in most situations.
1187 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
1188 if you require the GPL compiler.
1191 The internal ABI used for communication between the NFS kernel modules
1192 was changed by r320085, so __FreeBSD_version was bumped to
1193 ensure all the NFS related modules are updated together.
1196 The ABI of struct event was changed by extending the data
1197 member to 64bit and adding ext fields. For upgrade, same
1198 precautions as for the entry 20170523 "ino64" must be
1202 The GNU roff toolchain has been removed from base. To render manpages
1203 which are not supported by mandoc(1), man(1) can fallback on GNU roff
1204 from ports (and recommends to install it).
1205 To render roff(7) documents, consider using GNU roff from ports or the
1206 heirloom doctools roff toolchain from ports via pkg install groff or
1207 via pkg install heirloom-doctools.
1210 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
1211 smaller runtime footprint builds. This is useful for embedded systems
1212 which only require one chipset support.
1214 If you load it as a module, make sure this is in /boot/loader.conf:
1218 This will load the HAL, all chip/RF backends and if_ath_pci.
1219 If you have if_ath_pci in /boot/loader.conf, ensure it is after
1220 if_ath or it will not load any HAL chipset support.
1222 If you want to selectively load things (eg on ye cheape ARM/MIPS
1223 platforms where RAM is at a premium) you should:
1226 * load the chip modules in question
1227 * load ath_rate, ath_dfs
1229 * load if_ath_pci and/or if_ath_ahb depending upon your particular
1230 bus bind type - this is where probe/attach is done.
1232 For further comments/feedback, poke adrian@ .
1235 The "ino64" 64-bit inode project has been committed, which extends
1236 a number of types to 64 bits. Upgrading in place requires care and
1237 adherence to the documented upgrade procedure.
1239 If using a custom kernel configuration ensure that the
1240 COMPAT_FREEBSD11 option is included (as during the upgrade the
1241 system will be running the ino64 kernel with the existing world).
1243 For the safest in-place upgrade begin by removing previous build
1244 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full
1245 procedure documented below under the heading "To rebuild everything and
1246 install it on the current system." Specifically, a reboot is required
1247 after installing the new kernel before installing world. While an
1248 installworld normally works by accident from multiuser after rebooting
1249 the proper kernel, there are many cases where this will fail across this
1250 upgrade and installworld from single user is required.
1253 The NATM framework including the en(4), fatm(4), hatm(4), and
1254 patm(4) devices has been removed. Consumers should plan a
1255 migration before the end-of-life date for FreeBSD 11.
1258 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
1259 diff has not been implemented, if those are needed a newer version of
1260 GNU diff is available via the diffutils package under the gdiff name.
1263 As of r316810 for ipfilter, keep frags is no longer assumed when
1264 keep state is specified in a rule. r316810 aligns ipfilter with
1265 documentation in man pages separating keep frags from keep state.
1266 This allows keep state to be specified without forcing keep frags
1267 and allows keep frags to be specified independently of keep state.
1268 To maintain previous behaviour, also specify keep frags with
1269 keep state (as documented in ipf.conf.5).
1272 arm64 builds now use the base system LLD 4.0.0 linker by default,
1273 instead of requiring that the aarch64-binutils port or package be
1274 installed. To continue using aarch64-binutils, set
1275 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
1278 The UDP optimization in entry 20160818 that added the sysctl
1279 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
1280 packets will no longer be treated as L3 broadcast packets.
1283 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
1284 use any explicitly assigned loopback address available in the jail
1285 instead of using the first assigned address of the jail.
1288 The ctl.ko module no longer implements the iSCSI target frontend:
1289 cfiscsi.ko does instead.
1291 If building cfiscsi.ko as a kernel module, the module can be loaded
1292 via one of the following methods:
1293 - `cfiscsi_load="YES"` in loader.conf(5).
1294 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
1295 - ctladm(8)/ctld(8), when compiled with iSCSI support
1296 (`WITH_ISCSI=yes` in src.conf(5))
1298 Please see cfiscsi(4) for more details.
1301 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
1302 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
1303 same source (previously, the dependency of mmcsd.ko on mmc.ko was
1304 missing, but mmcsd.ko now will refuse to load if it is incompatible
1308 The syntax of ipfw(8) named states was changed to avoid ambiguity.
1309 If you have used named states in the firewall rules, you need to modify
1310 them after installworld and before rebooting. Now named states must
1311 be prefixed with colon.
1314 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
1315 removed as the userland we provide cannot use them. The KMS version
1316 (sys/dev/drm2) supports the same hardware.
1319 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
1320 Please see the 20141231 entry below for information about prerequisites
1321 and upgrading, if you are not already using clang 3.5.0 or higher.
1324 The code that provides support for ZFS .zfs/ directory functionality
1325 has been reimplemented. It's not possible now to create a snapshot
1326 by mkdir under .zfs/snapshot/. That should be the only user visible
1330 EISA bus support has been removed. The WITH_EISA option is no longer
1334 MCA bus support has been removed.
1337 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
1338 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
1341 The EM_MULTIQUEUE kernel configuration option is deprecated now that
1342 the em(4) driver conforms to iflib specifications.
1345 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
1346 IFLIB. If you have a custom kernel configuration that excludes em(4)
1347 but you use igb(4), you need to re-add em(4) to your custom
1351 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
1352 Please see the 20141231 entry below for information about prerequisites
1353 and upgrading, if you are not already using clang 3.5.0 or higher.
1356 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
1357 Please see the 20141231 entry below for information about prerequisites
1358 and upgrading, if you are not already using clang 3.5.0 or higher.
1361 The layout of the pmap structure has changed for powerpc to put the pmap
1362 statistics at the front for all CPU variations. libkvm(3) and all tools
1363 that link against it need to be recompiled.
1366 isl(4) and cyapa(4) drivers now require a new driver,
1367 chromebook_platform(4), to work properly on Chromebook-class hardware.
1368 On other types of hardware the drivers may need to be configured using
1369 device hints. Please see the corresponding manual pages for details.
1372 The urtwn(4) driver was merged into rtwn(4) and now consists of
1373 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
1375 Also, firmware for RTL8188CE was renamed due to possible name
1376 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
1379 GNU rcs has been removed from base. It is available as packages:
1380 - rcs: Latest GPLv3 GNU rcs version.
1381 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
1385 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
1386 modules now requires that the kernel configuration contain the
1387 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
1390 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
1391 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
1394 Relocatable object files with the extension of .So have been renamed
1395 to use an extension of .pico instead. The purpose of this change is
1396 to avoid a name clash with shared libraries on case-insensitive file
1397 systems. On those file systems, foo.So is the same file as foo.so.
1400 GNU rcs has been turned off by default. It can (temporarily) be built
1401 again by adding WITH_RCS knob in src.conf.
1402 Otherwise, GNU rcs is available from packages:
1403 - rcs: Latest GPLv3 GNU rcs version.
1404 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
1407 The backup_uses_rcs functionality has been removed from rc.subr.
1410 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
1411 two separate components, QUEUE_MACRO_DEBUG_TRACE and
1412 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
1413 QUEUE_MACRO_DEBUG behavior.
1416 r304787 changed some ioctl interfaces between the iSCSI userspace
1417 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1418 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1422 The UDP receive code has been updated to only treat incoming UDP
1423 packets that were addressed to an L2 broadcast address as L3
1424 broadcast packets. It is not expected that this will affect any
1425 standards-conforming UDP application. The new behaviour can be
1426 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1430 Remove the openbsd_poll system call.
1431 __FreeBSD_version has been bumped because of this.
1434 The stable/11 branch has been created from head@r302406.
1437 The libc stub for the pipe(2) system call has been replaced with
1438 a wrapper that calls the pipe2(2) system call and the pipe(2)
1439 system call is now only implemented by the kernels that include
1440 "options COMPAT_FREEBSD10" in their config file (this is the
1441 default). Users should ensure that this option is enabled in
1442 their kernel or upgrade userspace to r302092 before upgrading their
1446 CAM will now strip leading spaces from SCSI disks' serial numbers.
1447 This will affect users who create UFS filesystems on SCSI disks using
1448 those disk's diskid device nodes. For example, if /etc/fstab
1449 previously contained a line like
1450 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
1451 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
1452 transforms like gmirror may also be affected. ZFS users should
1456 The bitstring(3) API has been updated with new functionality and
1457 improved performance. But it is binary-incompatible with the old API.
1458 Objects built with the new headers may not be linked against objects
1459 built with the old headers.
1462 The brk and sbrk functions have been removed from libc on arm64.
1463 Binutils from ports has been updated to not link to these
1464 functions and should be updated to the latest version before
1465 installing a new libc.
1468 The armv6 port now defaults to hard float ABI. Limited support
1469 for running both hardfloat and soft float on the same system
1470 is available using the libraries installed with -DWITH_LIBSOFT.
1471 This has only been tested as an upgrade path for installworld
1472 and packages may fail or need manual intervention to run. New
1473 packages will be needed.
1475 To update an existing self-hosted armv6hf system, you must add
1476 TARGET_ARCH=armv6 on the make command line for both the build
1477 and the install steps.
1480 Kernel modules compiled outside of a kernel build now default to
1481 installing to /boot/modules instead of /boot/kernel. Many kernel
1482 modules built this way (such as those in ports) already overrode
1483 KMODDIR explicitly to install into /boot/modules. However,
1484 manually building and installing a module from /sys/modules will
1485 now install to /boot/modules instead of /boot/kernel.
1488 The CAM I/O scheduler has been committed to the kernel. There should be
1489 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1490 list of known rogues that claim support for this but actually corrupt
1491 data is believed to be complete, be on the lookout for data
1492 corruption. The known rogue list is believed to be complete:
1494 o Crucial MX100, M550 drives with MU01 firmware.
1495 o Micron M510 and M550 drives with MU01 firmware.
1496 o Micron M500 prior to MU07 firmware
1497 o Samsung 830, 840, and 850 all firmwares
1498 o FCCT M500 all firmwares
1500 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1501 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1502 updated firmware. Black listed drives will work correctly because these
1503 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1504 this list is the same as found in Linux, it's believed there are no
1505 other rogues in the market place. All other models from the above
1508 To be safe, if you are at all concerned, you can quirk each of your
1509 drives to prevent NCQ from being sent by setting:
1510 kern.cam.ada.X.quirks="0x2"
1511 in loader.conf. If the drive requires the 4k sector quirk, set the
1512 quirks entry to 0x3.
1515 The FAST_DEPEND build option has been removed and its functionality is
1516 now the one true way. The old mkdep(1) style of 'make depend' has
1517 been removed. See 20160311 for further details.
1520 Resource range types have grown from unsigned long to uintmax_t. All
1521 drivers, and anything using libdevinfo, need to be recompiled.
1524 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1525 builds. It no longer runs mkdep(1) during 'make depend', and the
1526 'make depend' stage can safely be skipped now as it is auto ran
1527 when building 'make all' and will generate all SRCS and DPSRCS before
1528 building anything else. Dependencies are gathered at compile time with
1529 -MF flags kept in separate .depend files per object file. Users should
1530 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1531 stale .depend files.
1534 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1535 kernel modules. Therefore, if you load any kernel modules at boot time,
1536 please install the boot loaders after you install the kernel, but before
1540 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1541 make installkernel KERNCONF=YOUR_KERNEL_HERE
1542 make -C sys/boot install
1543 <reboot in single user>
1545 Then follow the usual steps, described in the General Notes section,
1549 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1550 see the 20141231 entry below for information about prerequisites and
1551 upgrading, if you are not already using clang 3.5.0 or higher.
1554 The AIO subsystem is now a standard part of the kernel. The
1555 VFS_AIO kernel option and aio.ko kernel module have been removed.
1556 Due to stability concerns, asynchronous I/O requests are only
1557 permitted on sockets and raw disks by default. To enable
1558 asynchronous I/O requests on all file types, set the
1559 vfs.aio.enable_unsafe sysctl to a non-zero value.
1562 The ELF object manipulation tool objcopy is now provided by the
1563 ELF Tool Chain project rather than by GNU binutils. It should be a
1564 drop-in replacement, with the addition of arm64 support. The
1565 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1566 to obtain the GNU version if necessary.
1569 Building ZFS pools on top of zvols is prohibited by default. That
1570 feature has never worked safely; it's always been prone to deadlocks.
1571 Using a zvol as the backing store for a VM guest's virtual disk will
1572 still work, even if the guest is using ZFS. Legacy behavior can be
1573 restored by setting vfs.zfs.vol.recursive=1.
1576 The NONE and HPN patches has been removed from OpenSSH. They are
1577 still available in the security/openssh-portable port.
1580 With the addition of ypldap(8), a new _ypldap user is now required
1581 during installworld. "mergemaster -p" can be used to add the user
1582 prior to installworld, as documented in the handbook.
1585 The tftp loader (pxeboot) now uses the option root-path directive. As a
1586 consequence it no longer looks for a pxeboot.4th file on the tftp
1587 server. Instead it uses the regular /boot infrastructure as with the
1591 The code to start recording plug and play data into the modules has
1592 been committed. While the old tools will properly build a new kernel,
1593 a number of warnings about "unknown metadata record 4" will be produced
1594 for an older kldxref. To avoid such warnings, make sure to rebuild
1595 the kernel toolchain (or world). Make sure that you have r292078 or
1596 later when trying to build 292077 or later before rebuilding.
1599 Debug data files are now built by default with 'make buildworld' and
1600 installed with 'make installworld'. This facilitates debugging but
1601 requires more disk space both during the build and for the installed
1602 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1606 r291527 changed the internal interface between the nfsd.ko and
1607 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1608 __FreeBSD_version has been bumped because of this.
1611 Add support for unicode collation strings leads to a change of
1612 order of files listed by ls(1) for example. To get back to the old
1613 behaviour, set LC_COLLATE environment variable to "C".
1615 Databases administrators will need to reindex their databases given
1616 collation results will be different.
1618 Due to a bug in install(1) it is recommended to remove the ancient
1619 locales before running make installworld.
1621 rm -rf /usr/share/locale/*
1624 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1625 libcrypto.so.7 or libssl.so.7 must be recompiled.
1628 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1629 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1630 should be replaced with isp_2400 and isp_2500 modules respectively.
1633 The build previously allowed using 'make -n' to not recurse into
1634 sub-directories while showing what commands would be executed, and
1635 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1636 and 'make -N' will not.
1639 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1640 and etcupdate will now use this file. A custom sendmail.cf is now
1641 updated via this mechanism rather than via installworld. If you had
1642 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1643 want to remove the exclusion or change it to "always install".
1644 /etc/mail/sendmail.cf is now managed the same way regardless of
1645 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1646 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1649 Compatibility shims for legacy ATA device names have been removed.
1650 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1651 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1652 environment variables, /dev/ad* and /dev/ar* symbolic links.
1655 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1656 Please see the 20141231 entry below for information about prerequisites
1657 and upgrading, if you are not already using clang 3.5.0 or higher.
1660 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1661 and renamed from .symbols to .debug. This reduces the size requirements
1662 on the boot partition or file system and provides consistency with
1663 userland debug files.
1665 When using the supported kernel installation method the
1666 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1667 as is done with /boot/kernel.
1669 Developers wishing to maintain the historical behavior of installing
1670 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1673 The wireless drivers had undergone changes that remove the 'parent
1674 interface' from the ifconfig -l output. The rc.d network scripts
1675 used to check presence of a parent interface in the list, so old
1676 scripts would fail to start wireless networking. Thus, etcupdate(3)
1677 or mergemaster(8) run is required after kernel update, to update your
1678 rc.d scripts in /etc.
1681 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1682 These configurations are now automatically interpreted as
1683 'scrub fragment reassemble'.
1686 Kernel-loadable modules for the random(4) device are back. To use
1687 them, the kernel must have
1690 options RANDOM_LOADABLE
1692 kldload(8) can then be used to load random_fortuna.ko
1693 or random_yarrow.ko. Please note that due to the indirect
1694 function calls that the loadable modules need to provide,
1695 the build-in variants will be slightly more efficient.
1697 The random(4) kernel option RANDOM_DUMMY has been retired due to
1698 unpopularity. It was not all that useful anyway.
1701 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1702 Control over building the ELF Tool Chain tools is now provided by
1703 the WITHOUT_TOOLCHAIN knob.
1706 The polarity of Pulse Per Second (PPS) capture events with the
1707 uart(4) driver has been corrected. Prior to this change the PPS
1708 "assert" event corresponded to the trailing edge of a positive PPS
1709 pulse and the "clear" event was the leading edge of the next pulse.
1711 As the width of a PPS pulse in a typical GPS receiver is on the
1712 order of 1 millisecond, most users will not notice any significant
1713 difference with this change.
1715 Anyone who has compensated for the historical polarity reversal by
1716 configuring a negative offset equal to the pulse width will need to
1717 remove that workaround.
1720 The default group assigned to /dev/dri entries has been changed
1721 from 'wheel' to 'video' with the id of '44'. If you want to have
1722 access to the dri devices please add yourself to the video group
1725 # pw groupmod video -m $USER
1728 The menu.rc and loader.rc files will now be replaced during
1729 upgrades. Please migrate local changes to menu.rc.local and
1730 loader.rc.local instead.
1733 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1734 strings and strip have been removed. The src.conf(5) knob
1735 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1738 As ZFS requires more kernel stack pages than is the default on some
1739 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1740 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1742 Please consider using 'options KSTACK_PAGES=X' where X is greater
1743 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1746 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1747 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1748 default, i.e., they will not contain "::". For example, instead
1749 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1750 to have a more specific match, such as different map entries for
1751 IPv6:0:0 vs IPv6:0. This change requires that configuration
1752 data (including maps, files, classes, custom ruleset, etc.) must
1753 use the same format, so make certain such configuration data is
1754 upgrading. As a very simple check search for patterns like
1755 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1756 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1757 the cf option UseCompressedIPv6Addresses.
1760 The default kernel entropy-processing algorithm is now
1761 Fortuna, replacing Yarrow.
1763 Assuming you have 'device random' in your kernel config
1764 file, the configurations allow a kernel option to override
1765 this default. You may choose *ONE* of:
1767 options RANDOM_YARROW # Legacy /dev/random algorithm.
1768 options RANDOM_DUMMY # Blocking-only driver.
1770 If you have neither, you get Fortuna. For most people,
1771 read no further, Fortuna will give a /dev/random that works
1772 like it always used to, and the difference will be irrelevant.
1774 If you remove 'device random', you get *NO* kernel-processed
1775 entropy at all. This may be acceptable to folks building
1776 embedded systems, but has complications. Carry on reading,
1777 and it is assumed you know what you need.
1779 *PLEASE* read random(4) and random(9) if you are in the
1780 habit of tweaking kernel configs, and/or if you are a member
1781 of the embedded community, wanting specific and not-usual
1782 behaviour from your security subsystems.
1784 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1785 random', you will NOT have a functioning /dev/random, and
1786 many cryptographic features will not work, including SSH.
1787 You may also find strange behaviour from the random(3) set
1788 of library functions, in particular sranddev(3), srandomdev(3)
1789 and arc4random(3). The reason for this is that the KERN_ARND
1790 sysctl only returns entropy if it thinks it has some to
1791 share, and with RANDOM_DUMMY or no 'device random' this
1795 An additional fix for the issue described in the 20150614 sendmail
1796 entry below has been committed in revision 284717.
1799 FreeBSD's old make (fmake) has been removed from the system. It is
1800 available as the devel/fmake port or via pkg install fmake.
1803 The fix for the issue described in the 20150614 sendmail entry
1804 below has been committed in revision 284436. The work
1805 around described in that entry is no longer needed unless the
1806 default setting is overridden by a confDH_PARAMETERS configuration
1807 setting of '5' or pointing to a 512 bit DH parameter file.
1810 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1811 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1812 and devel/kyua to version 0.20+ and adjust any calling code to work
1813 with Kyuafile and kyua.
1816 The import of openssl to address the FreeBSD-SA-15:10.openssl
1817 security advisory includes a change which rejects handshakes
1818 with DH parameters below 768 bits. sendmail releases prior
1819 to 8.15.2 (not yet released), defaulted to a 512 bit
1820 DH parameter setting for client connections. To work around
1821 this interoperability, sendmail can be configured to use a
1822 2048 bit DH parameter by:
1824 1. Edit /etc/mail/`hostname`.mc
1825 2. If a setting for confDH_PARAMETERS does not exist or
1826 exists and is set to a string beginning with '5',
1827 replace it with '2'.
1828 3. If a setting for confDH_PARAMETERS exists and is set to
1829 a file path, create a new file with:
1830 openssl dhparam -out /path/to/file 2048
1831 4. Rebuild the .cf file:
1832 cd /etc/mail/; make; make install
1833 5. Restart sendmail:
1834 cd /etc/mail/; make restart
1836 A sendmail patch is coming, at which time this file will be
1840 Generation of legacy formatted entries have been disabled by default
1841 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1842 entries were converted to use the new format by default when the new,
1843 machine independent format have been added and supported since FreeBSD
1846 Please see the pwd_mkdb(8) manual page for further details.
1849 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1850 20141231 entry below for information about prerequisites and upgrading,
1851 if you are not already using 3.5.0 or higher.
1854 TI platform code switched to using vendor DTS files and this update
1855 may break existing systems running on Beaglebone, Beaglebone Black,
1858 - dtb files should be regenerated/reinstalled. Filenames are the
1859 same but content is different now
1860 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1861 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1862 addressing scheme is now pin 25 on /dev/gpioc3.
1863 - Pandaboard: /etc/ttys should be updated, serial console device is
1864 now /dev/ttyu2, not /dev/ttyu0
1867 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1868 If you need the GNU extension from groff soelim(1), install groff
1869 from package: pkg install groff, or via ports: textproc/groff.
1872 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1873 defined in symlink(7); previously symlinks were silently ignored.
1876 The const qualifier has been removed from iconv(3) to comply with
1877 POSIX. The ports tree is aware of this from r384038 onwards.
1880 Libraries specified by LIBADD in Makefiles must have a corresponding
1881 DPADD_<lib> variable to ensure correct dependencies. This is now
1882 enforced in src.libnames.mk.
1885 From legacy ata(4) driver was removed support for SATA controllers
1886 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1887 Kernel modules ataahci and ataadaptec were removed completely,
1888 replaced by ahci and mvs modules respectively.
1891 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1892 the 20141231 entry below for information about prerequisites and
1893 upgrading, if you are not already using 3.5.0 or higher.
1896 The 32-bit PowerPC kernel has been changed to a position-independent
1897 executable. This can only be booted with a version of loader(8)
1898 newer than January 31, 2015, so make sure to update both world and
1899 kernel before rebooting.
1902 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1903 but before r278950, the RNG was not seeded properly. Immediately
1904 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1905 ssh keys or openssl keys) that were generated w/ a kernel from that
1906 range. This does not affect programs that directly used /dev/random
1907 or /dev/urandom. All userland uses of arc4random(3) are affected.
1910 The autofs(4) ABI was changed in order to restore binary compatibility
1911 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1912 with the new kernel.
1915 The powerpc64 kernel has been changed to a position-independent
1916 executable. This can only be booted with a new version of loader(8),
1917 so make sure to update both world and kernel before rebooting.
1920 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1921 only release, no new features have been added. Please see the 20141231
1922 entry below for information about prerequisites and upgrading, if you
1923 are not already using 3.5.0.
1926 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1927 taken from the ELF Tool Chain project rather than GNU binutils. They
1928 should be drop-in replacements, with the addition of arm64 support.
1929 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1930 binutils tools, if necessary. See 20150805 for updated information.
1933 The default Unbound configuration now enables remote control
1934 using a local socket. Users who have already enabled the
1935 local_unbound service should regenerate their configuration
1936 by running "service local_unbound setup" as root.
1939 The GNU texinfo and GNU info pages have been removed.
1940 To be able to view GNU info pages please install texinfo from ports.
1943 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1945 As of this release, a prerequisite for building clang, llvm and lldb is
1946 a C++11 capable compiler and C++11 standard library. This means that to
1947 be able to successfully build the cross-tools stage of buildworld, with
1948 clang as the bootstrap compiler, your system compiler or cross compiler
1949 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1950 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1953 On any standard FreeBSD 10.x or 11.x installation, where clang and
1954 libc++ are on by default (that is, on x86 or arm), this should work out
1957 On 9.x installations where clang is enabled by default, e.g. on x86 and
1958 powerpc, libc++ will not be enabled by default, so libc++ should be
1959 built (with clang) and installed first. If both clang and libc++ are
1960 missing, build clang first, then use it to build libc++.
1962 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1963 the instructions for 9.x above.
1965 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1966 default, and do not build clang.
1968 Many embedded systems are resource constrained, and will not be able to
1969 build clang in a reasonable time, or in some cases at all. In those
1970 cases, cross building bootable systems on amd64 is a workaround.
1972 This new version of clang introduces a number of new warnings, of which
1973 the following are most likely to appear:
1977 This warns in two cases, for both C and C++:
1978 * When the code is trying to take the absolute value of an unsigned
1979 quantity, which is effectively a no-op, and almost never what was
1980 intended. The code should be fixed, if at all possible. If you are
1981 sure that the unsigned quantity can be safely cast to signed, without
1982 loss of information or undefined behavior, you can add an explicit
1983 cast, or disable the warning.
1985 * When the code is trying to take an absolute value, but the called
1986 abs() variant is for the wrong type, which can lead to truncation.
1987 If you want to disable the warning instead of fixing the code, please
1988 make sure that truncation will not occur, or it might lead to unwanted
1991 -Wtautological-undefined-compare and
1992 -Wundefined-bool-conversion
1994 These warn when C++ code is trying to compare 'this' against NULL, while
1995 'this' should never be NULL in well-defined C++ code. However, there is
1996 some legacy (pre C++11) code out there, which actively abuses this
1997 feature, which was less strictly defined in previous C++ versions.
1999 Squid and openjdk do this, for example. The warning can be turned off
2000 for C++98 and earlier, but compiling the code in C++11 mode might result
2001 in unexpected behavior; for example, the parts of the program that are
2002 unreachable could be optimized away.
2005 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
2006 kernel sources have been removed. The .h files remain, since some
2007 utilities include them. This will need to be fixed later.
2008 If "mount -t oldnfs ..." is attempted, it will fail.
2009 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
2010 the utilities will report errors.
2013 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
2014 directories to top level SUBDIR variable when their parent
2015 directory is included in LOCAL_DIRS. Users with build systems with
2016 such hierarchies and without SUBDIR entries in the parent
2017 directory Makefiles should add them or add the directories to
2021 faith(4) and faithd(8) have been removed from the base system. Faith
2022 has been obsolete for a very long time.
2025 vt(4), the new console driver, is enabled by default. It brings
2026 support for Unicode and double-width characters, as well as
2027 support for UEFI and integration with the KMS kernel video
2030 You may need to update your console settings in /etc/rc.conf,
2031 most probably the keymap. During boot, /etc/rc.d/syscons will
2032 indicate what you need to do.
2034 vt(4) still has issues and lacks some features compared to
2035 syscons(4). See the wiki for up-to-date information:
2036 https://wiki.freebsd.org/Newcons
2038 If you want to keep using syscons(4), you can do so by adding
2039 the following line to /boot/loader.conf:
2043 pjdfstest has been integrated into kyua as an opt-in test suite.
2044 Please see share/doc/pjdfstest/README for more details on how to
2048 gperf has been removed from the base system for architectures
2049 that use clang. Ports that require gperf will obtain it from the
2053 pjdfstest has been moved from tools/regression/pjdfstest to
2057 At svn r271982, The default linux compat kernel ABI has been adjusted
2058 to 2.6.18 in support of the linux-c6 compat ports infrastructure
2059 update. If you wish to continue using the linux-f10 compat ports,
2060 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
2061 encouraged to update their linux-compat packages to linux-c6 during
2062 their next update cycle.
2065 The ofwfb driver, used to provide a graphics console on PowerPC when
2066 using vt(4), no longer allows mmap() of all physical memory. This
2067 will prevent Xorg on PowerPC with some ATI graphics cards from
2068 initializing properly unless x11-servers/xorg-server is updated to
2072 The xdev targets have been converted to using TARGET and
2073 TARGET_ARCH instead of XDEV and XDEV_ARCH.
2076 The default unbound configuration has been modified to address
2077 issues with reverse lookups on networks that use private
2078 address ranges. If you use the local_unbound service, run
2079 "service local_unbound setup" as root to regenerate your
2080 configuration, then "service local_unbound reload" to load the
2084 The GNU texinfo and GNU info pages are not built and installed
2085 anymore, WITH_INFO knob has been added to allow to built and install
2087 UPDATE: see 20150102 entry on texinfo's removal
2090 The GNU readline library is now an INTERNALLIB - that is, it is
2091 statically linked into consumers (GDB and variants) in the base
2092 system, and the shared library is no longer installed. The
2093 devel/readline port is available for third party software that
2097 The Itanium architecture (ia64) has been removed from the list of
2098 known architectures. This is the first step in the removal of the
2102 Commit r268115 has added NFSv4.1 server support, merged from
2103 projects/nfsv4.1-server. Since this includes changes to the
2104 internal interfaces between the NFS related modules, a full
2105 build of the kernel and modules will be necessary.
2106 __FreeBSD_version has been bumped.
2109 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
2110 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
2111 which differs from the behaviour controlled by this knob.)
2114 Maximal length of the serial number in CTL was increased from 16 to
2115 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
2116 and ctld, need to be rebuilt to work with a new kernel.
2119 The libatf-c and libatf-c++ major versions were downgraded to 0 and
2120 1 respectively to match the upstream numbers. They were out of
2121 sync because, when they were originally added to FreeBSD, the
2122 upstream versions were not respected. These libraries are private
2123 and not yet built by default, so renumbering them should be a
2124 non-issue. However, unclean source trees will yield broken test
2125 programs once the operator executes "make delete-old-libs" after a
2126 "make installworld".
2128 Additionally, the atf-sh binary was made private by moving it into
2129 /usr/libexec/. Already-built shell test programs will keep the
2130 path to the old binary so they will break after "make delete-old"
2133 If you are using WITH_TESTS=yes (not the default), wipe the object
2134 tree and rebuild from scratch to prevent spurious test failures.
2135 This is only needed once: the misnumbered libraries and misplaced
2136 binaries have been added to OptionalObsoleteFiles.inc so they will
2137 be removed during a clean upgrade.
2140 Clang and llvm have been upgraded to 3.4.1 release.
2143 We bogusly installed src.opts.mk in /usr/share/mk. This file should
2144 be removed to avoid issues in the future (and has been added to
2148 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
2149 past, it affected all builds that used the bsd.*.mk files. The old
2150 behavior was a bug, but people may have relied upon it. To get this
2151 behavior back, you can .include /etc/src.conf from /etc/make.conf
2152 (which is still global and isn't changed). This also changes the
2153 behavior of incremental builds inside the tree of individual
2154 directories. Set MAKESYSPATH to ".../share/mk" to do that.
2155 Although this has survived make universe and some upgrade scenarios,
2156 other upgrade scenarios may have broken. At least one form of
2157 temporary breakage was fixed with MAKESYSPATH settings for buildworld
2158 as well... In cases where MAKESYSPATH isn't working with this
2159 setting, you'll need to set it to the full path to your tree.
2161 One side effect of all this cleaning up is that bsd.compiler.mk
2162 is no longer implicitly included by bsd.own.mk. If you wish to
2163 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
2167 The lindev device has been removed since /dev/full has been made a
2168 standard device. __FreeBSD_version has been bumped.
2171 The knob WITHOUT_VI was added to the base system, which controls
2172 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
2173 in order to reorder files share/termcap and didn't build ex(1) as a
2174 build tool, so building/installing with WITH_VI is highly advised for
2175 build hosts for older releases.
2177 This issue has been fixed in stable/9 and stable/10 in r277022 and
2178 r276991, respectively.
2181 The YES_HESIOD knob has been removed. It has been obsolete for
2182 a decade. Please move to using WITH_HESIOD instead or your builds
2183 will silently lack HESIOD.
2186 The uart(4) driver has been changed with respect to its handling
2187 of the low-level console. Previously the uart(4) driver prevented
2188 any process from changing the baudrate or the CLOCAL and HUPCL
2189 control flags. By removing the restrictions, operators can make
2190 changes to the serial console port without having to reboot.
2191 However, when getty(8) is started on the serial device that is
2192 associated with the low-level console, a misconfigured terminal
2193 line in /etc/ttys will now have a real impact.
2194 Before upgrading the kernel, make sure that /etc/ttys has the
2195 serial console device configured as 3wire without baudrate to
2196 preserve the previous behaviour. E.g:
2197 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
2200 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
2201 to improve performance. To re-enable it, if needed, run rpcbind
2202 with command line option -W.
2205 Switched back to the GPL dtc compiler due to updates in the upstream
2206 dts files not being supported by the BSDL dtc compiler. You will need
2207 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
2208 may result while building dtb files during a kernel build if you fail
2209 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
2212 Clang and llvm have been upgraded to 3.4 release.
2215 The nve(4) driver has been removed. Please use the nfe(4) driver
2216 for NVIDIA nForce MCP Ethernet adapters instead.
2219 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
2220 This could cause certain C++ applications using shared libraries built
2221 against the previous version of libc++ to crash. The incompatibility
2222 has now been fixed, but any C++ applications or shared libraries built
2223 between r261283 and r261801 should be recompiled.
2226 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
2227 capability mode support. Please note that enabling the feature in
2228 kernel is still highly recommended.
2231 OpenSSH is now built with sandbox support, and will use sandbox as
2232 the default privilege separation method. This requires Capsicum
2233 capability mode support in kernel.
2236 The libelf and libdwarf libraries have been updated to newer
2237 versions from upstream. Shared library version numbers for
2238 these two libraries were bumped. Any ports or binaries
2239 requiring these two libraries should be recompiled.
2240 __FreeBSD_version is bumped to 1100006.
2243 If a Makefile in a tests/ directory was auto-generating a Kyuafile
2244 instead of providing an explicit one, this would prevent such
2245 Makefile from providing its own Kyuafile in the future during
2246 NO_CLEAN builds. This has been fixed in the Makefiles but manual
2247 intervention is needed to clean an objdir if you use NO_CLEAN:
2248 # find /usr/obj -name Kyuafile | xargs rm -f
2251 The behavior of gss_pseudo_random() for the krb5 mechanism
2252 has changed, for applications requesting a longer random string
2253 than produced by the underlying enctype's pseudo-random() function.
2254 In particular, the random string produced from a session key of
2255 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
2256 be different at the 17th octet and later, after this change.
2257 The counter used in the PRF+ construction is now encoded as a
2258 big-endian integer in accordance with RFC 4402.
2259 __FreeBSD_version is bumped to 1100004.
2262 The WITHOUT_ATF build knob has been removed and its functionality
2263 has been subsumed into the more generic WITHOUT_TESTS. If you were
2264 using the former to disable the build of the ATF libraries, you
2265 should change your settings to use the latter.
2268 The default version of mtree is nmtree which is obtained from
2269 NetBSD. The output is generally the same, but may vary
2270 slightly. If you found you need identical output adding
2271 "-F freebsd9" to the command line should do the trick. For the
2272 time being, the old mtree is available as fmtree.
2275 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
2276 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
2277 1.1.4_8 and verify bsdyml not linked in, before running "make
2279 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
2281 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
2284 The stable/10 branch has been created in subversion from head
2291 Sometimes, obscure build problems are the result of environment
2292 poisoning. This can happen because the make utility reads its
2293 environment when searching for values for global variables. To run
2294 your build attempts in an "environmental clean room", prefix all make
2295 commands with 'env -i '. See the env(1) manual page for more details.
2296 Occasionally a build failure will occur with "make -j" due to a race
2297 condition. If this happens try building again without -j, and please
2298 report a bug if it happens consistently.
2300 When upgrading from one major version to another it is generally best to
2301 upgrade to the latest code in the currently installed branch first, then
2302 do an upgrade to the new branch. This is the best-tested upgrade path,
2303 and has the highest probability of being successful. Please try this
2304 approach if you encounter problems with a major version upgrade. Since
2305 the stable 4.x branch point, one has generally been able to upgrade from
2306 anywhere in the most recent stable branch to head / current (or even the
2307 last couple of stable branches). See the top of this file when there's
2310 The update process will emit an error on an attempt to perform a build
2311 or install from a FreeBSD version below the earliest supported version.
2312 When updating from an older version the update should be performed one
2313 major release at a time, including running `make delete-old` at each
2316 When upgrading a live system, having a root shell around before
2317 installing anything can help undo problems. Not having a root shell
2318 around can lead to problems if pam has changed too much from your
2319 starting point to allow continued authentication after the upgrade.
2321 This file should be read as a log of events. When a later event changes
2322 information of a prior event, the prior event should not be deleted.
2323 Instead, a pointer to the entry with the new information should be
2324 placed in the old entry. Readers of this file should also sanity check
2325 older entries before relying on them blindly. Authors of new entries
2326 should write them with this in mind.
2330 When upgrading the boot ZFS pool to a new version, always follow
2333 1.) recompile and reinstall the ZFS boot loader and boot block
2334 (this is part of "make buildworld" and "make installworld")
2336 2.) update the ZFS boot block on your boot drive
2338 The following example updates the ZFS boot block on the
2339 freebsd-boot partition of a GPT partitioned drive ada0:
2340 "gpart bootcode -p /boot/gptzfsboot -i $N ada0"
2341 The value $N will typically be 1 (if booting from BIOS) or 2 (if
2344 Non-boot pools do not need these updates.
2348 If you are updating from a prior version of FreeBSD (even one just
2349 a few days old), you should follow this procedure. It is the most
2350 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2352 make kernel-toolchain
2353 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2354 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2356 To test a kernel once
2357 ---------------------
2358 If you just want to boot a kernel once (because you are not sure
2359 if it works, or if you want to boot a known bad kernel to provide
2360 debugging information) run
2361 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2362 nextboot -k testkernel
2364 To rebuild everything and install it on the current system.
2365 -----------------------------------------------------------
2366 # Note: sometimes if you are running current you gotta do more than
2367 # is listed here if you are upgrading from a really old current.
2369 <make sure you have good level 0 dumps>
2371 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2372 make installkernel KERNCONF=YOUR_KERNEL_HERE
2374 <reboot in single user> [3]
2381 To cross-install current onto a separate partition
2382 --------------------------------------------------
2383 # In this approach we use a separate partition to hold
2384 # current's root, 'usr', and 'var' directories. A partition
2385 # holding "/", "/usr" and "/var" should be about 2GB in
2388 <make sure you have good level 0 dumps>
2391 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2392 <maybe newfs current's root partition>
2393 <mount current's root partition on directory ${CURRENT_ROOT}>
2394 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
2395 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2396 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2397 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2398 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2399 <reboot into current>
2400 <do a "native" rebuild/install as described in the previous section>
2401 <maybe install compatibility libraries from ports/misc/compat*>
2405 To upgrade in-place from stable to current
2406 ----------------------------------------------
2407 <make sure you have good level 0 dumps>
2409 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
2410 make installkernel KERNCONF=YOUR_KERNEL_HERE
2412 <reboot in single user> [3]
2419 Make sure that you've read the UPDATING file to understand the
2420 tweaks to various things you need. At this point in the life
2421 cycle of current, things change often and you are on your own
2422 to cope. The defaults can also change, so please read ALL of
2423 the UPDATING entries.
2425 Also, if you are tracking -current, you must be subscribed to
2426 freebsd-current@freebsd.org. Make sure that before you update
2427 your sources that you have read and understood all the recent
2428 messages there. If in doubt, please track -stable which has
2429 much fewer pitfalls.
2431 [1] If you have third party modules, such as vmware, you should disable
2432 them at this point so they don't crash your system on
2433 reboot. Alternatively, you should rebuild all the modules you have in
2434 your system and install them as well. If you are running -current, you
2435 should seriously consider placing all sources to all the modules for
2436 your system (or symlinks to them) in /usr/local/sys/modules so this
2437 happens automatically. If all your modules come from ports, then adding
2438 the port origin directories to PORTS_MODULES instead is also automatic
2440 PORTS_MODULES+=x11/nvidia-driver
2442 [3] From the bootblocks, boot -s, and then do
2446 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed
2447 cd src # full path to source
2448 adjkerntz -i # if CMOS is wall time
2449 Also, when doing a major release upgrade, it is required that you boot
2450 into single user mode to do the installworld.
2452 [4] Note: This step is non-optional. Failure to do this step
2453 can result in a significant reduction in the functionality of the
2454 system. Attempting to do it by hand is not recommended and those
2455 that pursue this avenue should read this file carefully, as well
2456 as the archives of freebsd-current and freebsd-hackers mailing lists
2457 for potential gotchas. The -U option is also useful to consider.
2458 See mergemaster(8) for more information.
2460 [5] Usually this step is a no-op. However, from time to time
2461 you may need to do this if you get unknown user in the following
2462 step. It never hurts to do it all the time. You may need to
2463 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2464 install) after the buildworld before this step if you last updated
2465 from current before 20130425 or from -stable before 20130430.
2467 [6] This only deletes old files and directories. Old libraries
2468 can be deleted by "make delete-old-libs", but you have to make
2469 sure that no program is using those libraries anymore.
2471 [8] The new kernel must be able to run existing binaries used by an
2472 installworld. When upgrading across major versions, the new kernel's
2473 configuration must include the correct COMPAT_FREEBSD<n> option for
2474 existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure
2475 to do so may leave you with a system that is hard to boot to recover. A
2476 GENERIC kernel will include suitable compatibility options to run
2477 binaries from older branches. Note that the ability to run binaries
2478 from unsupported branches is not guaranteed.
2480 Make sure that you merge any new devices from GENERIC since the
2481 last time you updated your kernel config file. Options also
2482 change over time, so you may need to adjust your custom kernels
2485 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2486 "?=" instead of the "=" assignment operator, so that buildworld can
2487 override the CPUTYPE if it needs to.
2489 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2490 not on the command line, or in /etc/make.conf. buildworld will
2491 warn if it is improperly defined.
2494 This file contains a list, in reverse chronological order, of major
2495 breakages in tracking -current. It is not guaranteed to be a complete
2496 list of such breakages, and only contains entries since September 23, 2011.
2497 If you need to see UPDATING entries from before that date, you will need
2498 to fetch an UPDATING file from an older FreeBSD release.
2500 Copyright information:
2502 Copyright 1998-2009 M. Warner Losh <imp@FreeBSD.org>
2504 Redistribution, publication, translation and use, with or without
2505 modification, in full or in part, in any form or format of this
2506 document are permitted without further permission from the author.
2508 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2509 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2510 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2511 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2512 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2513 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2514 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2515 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2516 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2517 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2518 POSSIBILITY OF SUCH DAMAGE.
2520 Contact Warner Losh if you have any questions about your use of