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 LinuxKPI pm.h changes require an update to the latest drm-kmod version
17 before re-compiling to avoid errors.
20 Bump __FreeBSD_verion to 1301501 after merging LinuxKPI and
21 net80211 changes in order to help out-of-tree consumers to deal
25 For 64-bit architectures the base system is now built with Position
26 Independent Executable (PIE) support enabled by default. It may be
27 disabled using the WITHOUT_PIE knob. A clean build is required.
30 The macros provided for the manipulation of CPU sets (e.g. CPU_AND)
31 have been modified to take 2 source arguments instead of only 1.
32 Externally maintained sources that use these macros will have to
33 be adapted. The FreeBSD version has been bumped to 1300524 to
37 Commit 18f5b477ee66 adds two arguments to VOP_ALLOCATE().
38 Normally changes to VOP calls are not MFC'd, but a
39 discussion on freebsd-current@ seemed to agree that
40 it was acceptable in this case, to fix the NFSv4.2 server.
41 Any out of source tree file system with a custom
42 VOP_ALLOCATE() call will need to be modified.
43 Bump __FreeBSD_version to 1300523 since the NFS modules need
44 to be rebuilt from sources.
47 Commit 6e8e261f0d4e changed the internal KAPI between the NFS
48 modules. As such, all the modules must be rebuilt from sources.
49 __FreeBSD_version has been bumped to 1300522.
52 Bump __FreeBSD_version to 1300521 after merging LinuxKPI and
53 net80211 changes in order to support building various wireless
54 drivers. This is to help other external consumers of LinuxKPI
55 and net80211 to deal accordingly.
58 Commit a599f9f7620b deleted the variable called nfs_maxcopyrange
59 from nfscommon.ko, since it no longer needs to be global. As such,
60 the other nfs modules must be rebuilt from up to date sources.
61 Bump __FreeBSD_version to 1300516 for this.
64 As of commit 622809b0868f OpenSSL no longer enables kernel TLS
65 by default. Users can enable kernel TLS via the "KTLS" SSL
66 option. This can be enabled globally by using a custom
67 OpenSSL config file via OPENSSL_CONF or via an
68 application-specific configuration option for applications
69 which permit setting SSL options via SSL_CONF_cmd(3).
72 Commits 9fb6e613373c and 9ec7dbf46b0a both changed the internal
73 KAPI between the NFS modules. Bump __FreeBSD_version to 1300514.
74 All NFS modules must be rebuilt from sources.
77 Commit b69019c14cd8 removes pf's DIOCGETSTATESNV ioctl.
78 As of be70c7a50d32 it is no longer used by userspace, but it does mean
79 users may not be able to enumerate pf states if they update the kernel
80 past c021ff986e2b without first updating userspace past be70c7a50d32.
83 Bump __FreeBSD_version to 1300512 after merging LinuxKPI, OFED,
84 net80211, and driver changes in order to support building
85 Intel wireless iwlwifi drivers. This is especially needed for
86 drm-kmod which needs updates after this.
89 The 20210707 awk update brought in a change in behavior. This has
90 been corrected as of d4d252c49976. Between these dates, if you
91 installed a new awk binary, you may not be able to build a new
92 kernel because the change in behavior affected the genoffset
93 script used to build the kernel. If you did update, the fix is
94 to update your sources past the above hash and do
97 % sudo -E make install
98 to enable building kernels again.
101 Commit 8a04edfdcbd2 changes the default minor version
102 used for NFSv4 mounts to the highest minor version supported
103 by the NFSv4 server. This default can be overridden by using
104 the "minorversion" mount option.
105 The consensus of a discussion on freebsd-current@ indicated
106 that this would be acceptable to do and would not be considered
110 awk has been updated to the latest one-true-awk version 20210215.
111 This contains a number of minor bug fixes.
114 Commit ca179c4d74f2/632e3f2f3a66 changed the package in which
115 the OpenSSL libraries and utilities are packaged.
116 It is recommended for pkgbase user to do:
117 pkg install -f FreeBSD-openssl
118 before pkg upgrade otherwise some dependencies might not be met
119 and pkg will stop working as libssl will not be present anymore
123 Commit 841006678745 changed the internal KAPI between the krpc
124 and nfsd modules. As such, they must both be rebuilt from
126 __FreeBSD_version is bumped to 1300510.
129 Commit 272f39942254 changed the internal KAPI between the
130 nscl.ko and nfscommon.ko modules, so they both need to be
131 rebuilt from sources.
134 Commit 5a45802b3c8c changed the internal KAPI between
135 the krpc and NFS. As such, the krpc, nfscommon and
136 nfscl modules must all be rebuilt from sources.
137 Without this patch, NFSv4.1/4.2 mounts should not
138 be done with the nfscbd(8) daemon running, to avoid
139 needing a working back channel for server->client RPCs.
142 Various LinuxKPI functionality was added which conflicts with DRM.
143 Please update your drm-kmod port to after the __FreeBSD_verison 1300139
147 The stable/13 branch has been created from main.
150 PC Card attachments for all devices have been removed. In the case of
151 wi and cmx, the entire drivers were removed because they were only
152 PC Card devices. FreeBSD_version 1300134 should be used for this
153 since it was bumped so recently.
156 Transport-independent parts of HID support have been split off the USB
157 code in to separate subsystem. Kernel configs which include one of
158 ums, ukbd, uhid, atp, wsp, wmt, uaudio, ugold or ucycom drivers should
159 be updated with adding of "device hid" line.
162 ncurses installation has been modified to only keep the widechar
163 enabled version. Incremental build is broken for that change, so it
164 requires a clean build.
167 The FreeBSD project has migrated from Subversion to Git. Temporary
168 instructions can be found at
169 https://github.com/bsdimp/freebsd-git-docs/blob/main/src-cvt.md
170 and other documents in that repo.
173 The services database has been updated to cover more of the basic
174 services expected in a modern system. The database is big enough
175 that it will cause issues in mergemaster in Releases previous to
176 12.2 and 11.3, or in very old current systems from before r358154.
179 Obsolete in-tree GDB 6.1.1 has been removed. GDB (including kgdb)
180 may be installed from ports or packages.
183 ping6 has been merged into ping. It can now be called as "ping -6".
184 See ping(8) for details.
187 Default value of net.add_addr_allfibs has been changed to 0.
188 If you have multi-fib configuration and rely on existence of all
189 interface routes in every fib, you need to set the above sysctl to 1.
191 The internal pre-processor in the calendar(1) program has been
192 extended to support more C pre-processor commands (e.g. #ifdef, #else,
193 and #undef) and to detect unbalanced conditional statements.
194 Error messages have been extended to include the filename and line
195 number if processing stops to help fixing malformed data files.
198 All the data files for the calendar(1) program, except calendar.freebsd,
199 have been moved to the deskutils/calendar-data port, much like the
200 jewish calendar entries were moved to deskutils/hebcal years ago. After
201 make delete-old-files, you need to install it to retain full
202 functionality. calendar(1) will issue a reminder for files it can't
206 LINT files are no longer generated. We now include the relevant NOTES
207 files. Note: This may cause conflicts with updating in some cases.
208 find sys -name LINT\* -delete
209 is suggested across this commit to remove the generated LINT files.
211 If you have tried to update with generated files there, the svn
212 command you want to un-auger the tree is
215 and then do the above find from the top level. Substitute 'amd64'
216 above with where the error message indicates a conflict.
219 OpenZFS support has been integrated. Do not upgrade root pools until
220 the loader is updated to support zstd. Furthermore, we caution against
221 'zpool upgrade' for the next few weeks. The change should be transparent
222 unless you want to use new features.
224 Not all "NO_CLEAN" build scenarios work across these changes. Many
225 scenarios have been tested and fixed, but rebuilding kernels without
226 rebuilding world may fail.
228 The ZFS cache file has moved from /boot to /etc to match the OpenZFS
229 upstream default. A fallback to /boot has been added for mountroot.
231 Pool auto import behavior at boot has been moved from the kernel module
232 to an explicit "zpool import -a" in one of the rc scripts enabled by
233 zfs_enable=YES. This means your non-root zpools won't auto import until
234 you upgrade your /etc/rc.d files.
237 The resume code now notifies devd with the 'kernel' system
238 rather than the old 'kern' subsystem to be consistent with
239 other use. The old notification will be created as well, but
240 will be removed prior to FreeBSD 14.0.
243 r362275 changed the internal API between the kernel RPC and the
244 NFS modules. As such, all the modules must be recompiled from
248 r364330 modified the internal API used between the NFS modules.
249 As such, all the NFS modules must be re-compiled from sources.
252 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
253 been upgraded to 11.0.0. Please see the 20141231 entry below for
254 information about prerequisites and upgrading, if you are not already
255 using clang 3.5.0 or higher.
258 r364092 modified the internal ABI used between the kernel NFS
259 modules. As such, all of these modules need to be rebuilt
260 from sources, so a version bump was done.
263 Makefile.inc has been updated to work around the issue documented in
264 20200729. It was a case where the optimization of using symbolic links
265 to point to binaries created a situation where we'd run new binaries
266 with old libraries starting midway through the installworld process.
269 r363679 has redefined some undefined behavior in regcomp(3); notably,
270 extraneous escapes of most ordinary characters will no longer be
271 accepted. An exp-run has identified all of the problems with this in
272 ports, but other non-ports software may need extra escapes removed to
273 continue to function.
275 Because of this change, installworld may encounter the following error
276 from rtld: Undefined symbol "regcomp@FBSD_1.6" -- It is imperative that
277 you do not halt installworld. Instead, let it run to completion (whether
278 successful or not) and run installworld once more.
281 A new implementation of bc and dc has been imported in r362681. This
282 implementation corrects non-conformant behavior of the previous bc
283 and adds GNU bc compatible options. It offers a number of extensions,
284 is much faster on large values, and has support for message catalogs
285 (a number of languages are already supported, contributions of further
286 languages welcome). The option WITHOUT_GH_BC can be used to build the
287 world with the previous versions of bc and dc.
290 r362639 changed the internal API used between the NFS kernel modules.
291 As such, they all need to be rebuilt from sources.
294 r362158 changed the arguments for VFS_CHECKEXP(). As such, any
295 out of tree file systems need to be modified and rebuilt.
296 Also, any file systems that are modules must be rebuilt.
299 read(2) of a directory fd is now rejected by default. root may
300 re-enable it for system root only on non-ZFS filesystems with the
301 security.bsd.allow_read_dir sysctl(8) MIB if
302 security.bsd.suser_enabled=1.
304 It may be advised to setup aliases for grep to default to `-d skip` if
305 commonly non-recursively grepping a list that includes directories and
306 the potential for the resulting stderr output is not tolerable. Example
307 aliases are now installed, commented out, in /root/.cshrc and
311 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
312 been upgraded to 10.0.1. Please see the 20141231 entry below for
313 information about prerequisites and upgrading, if you are not already
314 using clang 3.5.0 or higher.
317 Support for obsolete compilers has been removed from the build system.
318 Clang 6 and GCC 6.4 are the minimum supported versions.
321 closefrom(2) has been moved under COMPAT12, and replaced in libc with a
322 stub that calls close_range(2). If using a custom kernel configuration,
323 you may want to ensure that the COMPAT_FREEBSD12 option is included, as
324 a slightly older -CURRENT userland and older FreeBSD userlands may not
325 be functional without closefrom(2).
328 Upstream DTS from Linux 5.6 was merged and they now have the SID
329 and THS (Secure ID controller and THermal Sensor) node present.
330 The DTB overlays have now been removed from the tree for the H3/H5 and
331 A64 SoCs and the aw_sid and aw_thermal driver have been updated to
332 deal with upstream DTS. If you are using those overlays you need to
333 remove them from loader.conf and update the DTBs on the FAT partition.
336 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
337 been upgraded to 10.0.0. Please see the 20141231 entry below for
338 information about prerequisites and upgrading, if you are not already
339 using clang 3.5.0 or higher.
342 The amd(8) automount daemon has been removed from the source tree.
343 As of FreeBSD 10.1 autofs(5) is the preferred tool for automounting.
344 amd is still available in the sysutils/am-utils port.
347 Removed brooktree driver (bktr.4) from the tree.
350 The WITH_GPL_DTC option has been removed. The BSD-licenced device tree
351 compiler in usr.bin/dtc is used on all architectures which use dtc, and
352 the GPL dtc is available (if needed) from the sysutils/dtc port.
355 The WITHOUT_LLVM_LIBUNWIND option has been removed. LLVM's libunwind
356 is used by all supported CPU architectures.
359 GCC 4.2.1 has been removed from the tree. The WITH_GCC,
360 WITH_GCC_BOOTSTRAP, and WITH_GNUCXX options are no longer available.
361 Users who wish to build FreeBSD with GCC must use the external toolchain
365 ncurses has been updated to a newer version (6.2-20200215). Given the ABI
366 has changed, users will have to rebuild all the ports that are linked to
370 The size of struct vnet and the magic cookie have changed.
371 Users need to recompile libkvm and all modules using VIMAGE
372 together with their new kernel.
375 Defining the long deprecated NO_CTF, NO_DEBUG_FILES, NO_INSTALLLIB,
376 NO_MAN, NO_PROFILE, and NO_WARNS variables is now an error. Update
377 your Makefiles and scripts to define MK_<var>=no instead as required.
379 One exception to this is that program or library Makefiles should
380 define MAN to empty rather than setting MK_MAN=no.
383 Clang/LLVM is now the default compiler and LLD the default
387 make universe no longer uses GCC 4.2.1 on any architectures.
388 Architectures not supported by in-tree Clang/LLVM require an
389 external toolchain package.
392 GCC 4.2.1 is now not built by default, as part of the GCC 4.2.1
393 retirement plan. Specifically, the GCC, GCC_BOOTSTRAP, and GNUCXX
394 options default to off for all supported CPU architectures. As a
395 short-term transition aid they may be enabled via WITH_* options.
396 GCC 4.2.1 is expected to be removed from the tree on 2020-03-31.
399 Support for armv5 has been disconnected and is being removed. The
400 machine combination MACHINE=arm MACHINE_ARCH=arm is no longer valid.
401 You must now use a MACHINE_ARCH of armv6 or armv7. The default
402 MACHINE_ARCH for MACHINE=arm is now armv7.
405 Clang/LLVM is now the default compiler for all powerpc architectures.
406 LLD is now the default linker for powerpc64. The change for powerpc64
407 also includes a change to the ELFv2 ABI, incompatible with the existing
411 Kernel-loadable random(4) modules are no longer unloadable.
414 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
415 been upgraded to 9.0.1. Please see the 20141231 entry below for
416 information about prerequisites and upgrading, if you are not already
417 using clang 3.5.0 or higher.
420 r355677 has modified the internal interface used between the
421 NFS modules in the kernel. As such, they must all be upgraded
422 simultaneously. I will do a version bump for this.
425 The root certificates of the Mozilla CA Certificate Store have been
426 imported into the base system and can be managed with the certctl(8)
427 utility. If you have installed the security/ca_root_nss port or package
428 with the ETCSYMLINK option (the default), be advised that there may be
429 differences between those included in the port and those included in
430 base due to differences in nss branch used as well as general update
431 frequency. Note also that certctl(8) cannot manage certs in the
432 format used by the security/ca_root_nss port.
435 The amd(8) automount daemon has been disabled by default, and will be
436 removed in the future. As of FreeBSD 10.1 the autofs(5) is available
440 The nctgpio and wbwd drivers have been moved to the superio bus.
441 If you have one of these drivers in a kernel configuration, then
442 you should add device superio to it. If you use one of these drivers
443 as a module and you compile a custom set of modules, then you should
444 add superio to the set.
447 KPIs for network drivers to access interface addresses have changed.
448 Users need to recompile NIC driver modules together with kernel.
451 The net.link.tap.user_open sysctl no longer prevents user opening of
452 already created /dev/tapNN devices. Access is still controlled by
453 node permissions, just like tun devices. The net.link.tap.user_open
454 sysctl is now used only to allow users to perform devfs cloning of
455 tap devices, and the subsequent open may not succeed if the user is not
456 in the appropriate group. This sysctl may be deprecated/removed
457 completely in the future.
460 mips, powerpc, and sparc64 are no longer built as part of
461 universe / tinderbox unless MAKE_OBSOLETE_GCC is defined. If
462 not defined, mips, powerpc, and sparc64 builds will look for
463 the xtoolchain binaries and if installed use them for universe
464 builds. As llvm 9.0 becomes vetted for these architectures, they
465 will be removed from the list.
468 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
469 been upgraded to 9.0.0. Please see the 20141231 entry below for
470 information about prerequisites and upgrading, if you are not already
471 using clang 3.5.0 or higher.
474 The hpt27xx, hptmv, hptnr, and hptrr drivers have been removed from
475 GENERIC. They are available as modules and can be loaded by adding
476 to /boot/loader.conf hpt27xx_load="YES", hptmv_load="YES",
477 hptnr_load="YES", or hptrr_load="YES", respectively.
480 ntpd no longer by default locks its pages in memory, allowing them
481 to be paged out by the kernel. Use rlimit memlock to restore
482 historic BSD behaviour. For example, add "rlimit memlock 32"
483 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
486 Several of ping6's options have been renamed for better consistency
487 with ping. If you use any of -ARWXaghmrtwx, you must update your
488 scripts. See ping6(8) for details.
491 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
492 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
493 been removed from mount_fusefs(8). You can safely remove them from
494 your scripts, because they had no effect.
496 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
497 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
498 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
499 sysctls have been removed. If you felt the need to set any of them to
500 a non-default value, please tell asomers@FreeBSD.org why.
503 Default permissions on the /var/account/acct file (and copies of it
504 rotated by periodic daily scripts) are changed from 0644 to 0640
505 because the file contains sensitive information that should not be
506 world-readable. If the /var/account directory must be created by
507 rc.d/accounting, the mode used is now 0750. Admins who use the
508 accounting feature are encouraged to change the mode of an existing
509 /var/account directory to 0750 or 0700.
512 Entropy collection and the /dev/random device are no longer optional
513 components. The "device random" option has been removed.
514 Implementations of distilling algorithms can still be made loadable
515 with "options RANDOM_LOADABLE" (e.g., random_fortuna.ko).
518 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
519 been upgraded to 8.0.1. Please see the 20141231 entry below for
520 information about prerequisites and upgrading, if you are not already
521 using clang 3.5.0 or higher.
524 A fix was applied to i386 kernel modules to avoid panics with
525 dpcpu or vnet. Users need to recompile i386 kernel modules
526 having pcpu or vnet sections or they will refuse to load.
529 User-wired pages now have their own counter,
530 vm.stats.vm.v_user_wire_count. The vm.max_wired sysctl was renamed
531 to vm.max_user_wired and changed from an unsigned int to an unsigned
532 long. bhyve VMs wired with the -S are now subject to the user
533 wiring limit; the vm.max_user_wired sysctl may need to be tuned to
534 avoid running into the limit.
537 The IPSEC option has been removed from GENERIC. Users requiring
538 ipsec(4) must now load the ipsec(4) kernel module.
541 The tap(4) driver has been folded into tun(4), and the module has been
542 renamed to tuntap. You should update any kld_list="if_tap" or
543 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
544 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
545 module instead, and "device tap" or "device tun" entries in kernel
546 config files to select the tuntap device instead.
549 The following knobs have been added related to tradeoffs between
550 safe use of the random device and availability in the absence of
553 kern.random.initial_seeding.bypass_before_seeding: tunable; set
554 non-zero to bypass the random device prior to seeding, or zero to
555 block random requests until the random device is initially seeded.
556 For now, set to 1 (unsafe) by default to restore pre-r346250 boot
557 availability properties.
559 kern.random.initial_seeding.read_random_bypassed_before_seeding:
560 read-only diagnostic sysctl that is set when bypass is enabled and
561 read_random(9) is bypassed, to enable programmatic handling of this
562 initial condition, if desired.
564 kern.random.initial_seeding.arc4random_bypassed_before_seeding:
565 Similar to the above, but for arc4random(9) initial seeding.
567 kern.random.initial_seeding.disable_bypass_warnings: tunable; set
568 non-zero to disable warnings in dmesg when the same conditions are
569 met as for the diagnostic sysctls above. Defaults to zero, i.e.,
570 produce warnings in dmesg when the conditions are met.
573 The loadable random module KPI has changed; the random_infra_init()
574 routine now requires a 3rd function pointer for a bool (*)(void)
575 method that returns true if the random device is seeded (and
576 therefore unblocked).
579 r345895 reverts r320698. This implies that an nfsuserd(8) daemon
580 built from head sources between r320757 (July 6, 2017) and
581 r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
582 is added to the command line.
583 nfsuserd daemons built from head sources that are post-r338192 are
584 not affected and should continue to work.
587 The fuse(4) module has been renamed to fusefs(4) for consistency with
588 other filesystems. You should update any kld_load="fuse" entries in
589 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
590 "options FUSE" entries in kernel config files.
593 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
594 8.0.0. Please see the 20141231 entry below for information about
595 prerequisites and upgrading, if you are not already using clang 3.5.0
599 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
600 compiled into your custom kernel, add 'device xz' statement to the
604 drm and drm2 have been removed from the tree. Please see
605 https://wiki.freebsd.org/Graphics for the latest information on
606 migrating to the drm ports.
609 Iflib is no longer unconditionally compiled into the kernel. Drivers
610 using iflib and statically compiled into the kernel, now require
611 the 'device iflib' config option. For the same drivers loaded as
612 modules on kernels not having 'device iflib', the iflib.ko module
613 is loaded automatically.
616 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
617 options no longer exist since r343219 and r343427 respectively;
618 nothing uses them, so they should be just removed from custom
622 r342635 changes the way efibootmgr(8) works by requiring users to add
623 the -b (bootnum) parameter for commands where the bootnum was previously
624 specified with each option. For example 'efibootmgr -B 0001' is now
625 'efibootmgr -B -b 0001'.
628 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
629 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
630 servers that have vfs.nfsd.nfs_privport set will only allow mounts
631 from clients using a reserved port#. Since both the FreeBSD and Linux
632 NFSv4 clients use reserved port#s by default, this should not affect
636 The XLP config has been removed. We can't support 64-bit atomics in this
637 kernel because it is running in 32-bit mode. XLP users must transition
638 to running a 64-bit kernel (XLP64 or XLPN32).
640 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
641 the preferred emulator today and we don't need two different ones.
643 The old sibyte / swarm / Broadcom BCM1250 support has been
644 removed from the mips port.
647 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
648 7.0.1. Please see the 20141231 entry below for information about
649 prerequisites and upgrading, if you are not already using clang 3.5.0
653 Remove the timed and netdate programs from the base tree. Setting
654 the time with these daemons has been obsolete for over a decade.
657 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
658 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
659 it produces broken binaries when ifuncs are in use. Users needing
660 GNU ld should install the binutils port or package.
663 The BSD crtbegin and crtend code has been enabled by default. It has
664 had extensive testing on amd64, arm64, and i386. It can be disabled
665 by building a world with -DWITHOUT_BSD_CRTBEGIN.
668 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
669 has been converted to a port (misc/ctm) and will be removed from
670 FreeBSD-13. It is available as a package (ctm) for all supported
674 The default newsyslog.conf(5) file has been changed to only include
675 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
676 the filenames end in '.conf' and do not begin with a '.'.
678 You should check the configuration files in these two directories match
679 this naming convention. You can verify which configuration files are
680 being included using the command:
684 Ports for the DRM modules have been simplified. Now, amd64 users should
685 just install the drm-kmod port. All others should install
688 Graphics hardware that's newer than about 2010 usually works with
689 drm-kmod. For hardware older than 2013, however, some users will need
690 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
691 than 2008 usually only works in drm-legacy-kmod. The graphics team can
692 only commit to hardware made since 2013 due to the complexity of the
693 market and difficulty to test all the older cards effectively. If you
694 have hardware supported by drm-kmod, you are strongly encouraged to use
695 that as you will get better support.
697 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
698 elsewhere, the drm and drm2 modules will be eliminated from the src base
699 soon (with a limited exception for arm). Please update to the package
700 asap and report any issues to x11@freebsd.org.
702 Generally, anybody using the drm*-kmod packages should add
703 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
704 cross-threading surprises, especially with automatic driver
705 loading from X11 startup. These will become the defaults in 13-current
709 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
710 custom kernel and module loading configuration files must be updated
711 accordingly. Moreover, interfaces previous presented as ixlvN to the
712 system are now exposed as iavfN and network configuration files must
713 be adjusted as necessary.
716 OpenSSL has been updated to version 1.1.1. This update included
717 additional various API changes throughout the base system. It is
718 important to rebuild third-party software after upgrading. The value
719 of __FreeBSD_version has been bumped accordingly.
722 The legacy DRM modules and drivers have now been added to the loader's
723 module blacklist, in favor of loading them with kld_list in rc.conf(5).
724 The module blacklist may be overridden with the loader.conf(5)
725 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
729 The cam(4) based nda(4) driver will be used over nvd(4) by default on
730 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
731 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
732 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
736 Reproducible build mode is now on by default, in preparation for
737 FreeBSD 12.0. This eliminates build metadata such as the user,
738 host, and time from the kernel (and uname), unless the working tree
739 corresponds to a modified checkout from a version control system.
740 The previous behavior can be obtained by setting the /etc/src.conf
741 knob WITHOUT_REPRODUCIBLE_BUILD.
744 The Yarrow CSPRNG has been removed from the kernel as it has not been
745 supported by its designers since at least 2003. Fortuna has been the
746 default since FreeBSD-11.
749 devctl freeze/thaw have gone into the tree, the rc scripts have been
750 updated to use them and devmatch has been changed. You should update
751 kernel, userland and rc scripts all at the same time.
754 The default interpreter has been switched from 4th to Lua.
755 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
756 interpreter. If you have custom FORTH code you will need to set
757 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
758 src.conf for the build. This will create default hard links between
759 loader and loader_4th instead of loader and loader_lua, the new default.
760 If you are using UEFI it will create the proper hard link to loader.efi.
762 bhyve uses userboot.so. It remains 4th-only until some issues are solved
763 regarding coexisting with multiple versions of FreeBSD are resolved.
766 ls(1) now respects the COLORTERM environment variable used in other
767 systems and software to indicate that a colored terminal is both
768 supported and desired. If ls(1) is suddenly emitting colors, they may
769 be disabled again by either removing the unwanted COLORTERM from your
770 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
771 may not be observed in a future release.
774 The default pager for most commands has been changed to "less". To
775 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
779 The jedec_ts(4) driver has been removed. A superset of its functionality
780 is available in the jedec_dimm(4) driver, and the manpage for that
781 driver includes migration instructions. If you have "device jedec_ts"
782 in your kernel configuration file, it must be removed.
785 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
786 This should have no effect if the kernel is booted via BIOS/legacy boot.
787 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
788 has a buggy firmware that prevents a successful boot due to use of
792 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
793 support has been removed from the tree. These ports were
794 obsolete and/or known to be broken for many years.
797 loader.efi has been augmented to participate more fully in the
798 UEFI boot manager protocol. loader.efi will now look at the
799 BootXXXX environment variable to determine if a specific kernel
800 or root partition was specified. XXXX is derived from BootCurrent.
801 efibootmgr(8) manages these standard UEFI variables.
804 zfsloader's functionality has now been folded into loader.
805 zfsloader is no longer necessary once you've updated your
806 boot blocks. For a transition period, we will install a
807 hardlink for zfsloader to loader to allow a smooth transition
808 until the boot blocks can be updated (hard link because old
809 zfs boot blocks don't understand symlinks).
812 ARM64 now have efifb support, if you want to have serial console
813 on your arm64 board when an screen is connected and the bootloader
814 setup a frame buffer for us to use, just add :
818 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
819 an screen connected as the firmware will setup a frame buffer are that
820 u-boot will expose as an EFI frame buffer.
823 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
824 or take steps to update /etc/passwd before doing installworld on
825 existing systems. Do not skip the "mergemaster -Fp" step before
826 installworld, as described in the update procedures near the bottom
827 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
828 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
829 the ntp config file contain options that change file/dir locations.
830 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
831 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
832 taking steps to ensure that all required files/dirs are accessible
836 Big endian arm support has been removed.
839 The static environment setup in kernel configs is no longer mutually
840 exclusive with the loader(8) environment by default. In order to
841 restore the previous default behavior of disabling the loader(8)
842 environment if a static environment is present, you must specify
843 loader_env.disabled=1 in the static environment.
846 The ABI of syscalls used by management tools like sockstat and
847 netstat has been broken to allow 32-bit binaries to work on
848 64-bit kernels without modification. These programs will need
849 to match the kernel in order to function. External programs may
850 require minor modifications to accommodate a change of type in
851 structures from pointers to 64-bit virtual addresses.
854 On i386 and amd64 atomics are now inlined. Out of tree modules using
855 atomics will need to be rebuilt.
858 The '%I' format in the kern.corefile sysctl limits the number of
859 core files that a process can generate to the number stored in the
860 debug.ncores sysctl. The '%I' format is replaced by the single digit
861 index. Previously, if all indexes were taken the kernel would overwrite
862 only a core file with the highest index in a filename.
863 Currently the system will create a new core file if there is a free
864 index or if all slots are taken it will overwrite the oldest one.
867 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
868 6.0.1. Please see the 20141231 entry below for information about
869 prerequisites and upgrading, if you are not already using clang 3.5.0
873 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
874 needed to be changed to work with it. This change was made with r335763
875 and requires a mergemaster / etcupdate / etc to update the installed
879 r334930 changed the interface between the NFS modules, so they all
880 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
883 As of r334391 lld is the default amd64 system linker; it is installed
884 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
888 The kernel / userland interface for devinfo changed, so you'll
889 need a new kernel and userland as a pair for it to work (rebuilding
890 lib/libdevinfo is all that's required). devinfo and devmatch will
891 not work, but everything else will when there's a mismatch.
894 The on-disk format for hwpmc callchain records has changed to include
895 threadid corresponding to a given record. This changes the field offsets
896 and thus requires that libpmcstat be rebuilt before using a kernel
900 The vxge(4) driver has been removed. This driver was introduced into
901 HEAD one week before the Exar left the Ethernet market and is not
902 known to be used. If you have device vxge in your kernel config file
906 The amd64 kernel now requires a ld that supports ifunc to produce a
907 working kernel, either lld or a newer binutils. lld is built by default
908 on amd64, and the 'buildkernel' target uses it automatically. However,
909 it is not the default linker, so building the kernel the traditional
910 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
911 binutils port/package). lld will soon be default, and this requirement
914 NOTE: As of r334391 lld is the default system linker on amd64, and no
915 workaround is necessary.
918 The nxge(4) driver has been removed. This driver was for PCI-X 10g
919 cards made by s2io/Neterion. The company was acquired by Exar and
920 no longer sells or supports Ethernet products. If you have device
921 nxge in your kernel config file it must be removed.
924 The tz database (tzdb) has been updated to 2018e. This version more
925 correctly models time stamps in time zones with negative DST such as
926 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
927 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
928 time zone abbreviations and the tm_isdst flag.
931 The ixgb(4) driver has been removed. This driver was for an early and
932 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
933 quickly shifted to the long lived ixgbe family. If you have device
934 ixgb in your kernel config file it must be removed.
937 The lmc(4) driver has been removed. This was a WAN interface
938 card that was already reportedly rare in 2003, and had an ambiguous
939 license. If you have device lmc in your kernel config file it must
943 Support for Arcnet networks has been removed. If you have device
944 arcnet or device cm in your kernel config file they must be
948 Support for FDDI networks has been removed. If you have device
949 fddi or device fpa in your kernel config file they must be
953 In addition to supporting RFC 3164 formatted messages, the
954 syslogd(8) service is now capable of parsing RFC 5424 formatted
955 log messages. The main benefit of using RFC 5424 is that clients
956 may now send log messages with timestamps containing year numbers,
957 microseconds and time zone offsets.
959 Similarly, the syslog(3) C library function has been altered to
960 send RFC 5424 formatted messages to the local system logging
961 daemon. On systems using syslogd(8), this change should have no
962 negative impact, as long as syslogd(8) and the C library are
963 updated at the same time. On systems using a different system
964 logging daemon, it may be necessary to make configuration
965 adjustments, depending on the software used.
967 When using syslog-ng, add the 'syslog-protocol' flag to local
968 input sources to enable parsing of RFC 5424 formatted messages:
971 unix-dgram("/var/run/log" flags(syslog-protocol));
974 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
975 of the 'imuxsock' module to let messages be processed by the
976 regular RFC 3164/5424 parsing pipeline:
978 module(load="imuxsock" SysSock.UseSpecialParser="off")
980 Do note that these changes only affect communication between local
981 applications and syslogd(8). The format that syslogd(8) uses to
982 store messages on disk or forward messages to other systems
983 remains unchanged. syslogd(8) still uses RFC 3164 for these
984 purposes. Options to customize this behaviour will be added in the
985 future. Utilities that process log files stored in /var/log are
986 thus expected to continue to function as before.
988 __FreeBSD_version has been incremented to 1200061 to denote this
992 Support for token ring networks has been removed. If you
993 have "device token" in your kernel config you should remove
994 it. No device drivers supported token ring.
997 makefs was modified to be able to tag ISO9660 El Torito boot catalog
998 entries as EFI instead of overloading the i386 tag as done previously.
999 The amd64 mkisoimages.sh script used to build amd64 ISO images for
1000 release was updated to use this. This may mean that makefs must be
1001 updated before "make cdrom" can be run in the release directory. This
1002 should be as simple as:
1004 $ cd $SRCDIR/usr.sbin/makefs
1005 $ make depend all install
1008 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
1009 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
1010 Co-existence for the transition period will come shortly. Booting is a
1011 complex environment and test coverage for Lua-enabled loaders has been
1012 thin, so it would be prudent to assume it might not work and make
1013 provisions for backup boot methods.
1016 devmatch functionality has been turned on in devd. It will automatically
1017 load drivers for unattached devices. This may cause unexpected drivers
1018 to be loaded. Please report any problems to current@ and
1022 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
1023 6.0.0. Please see the 20141231 entry below for information about
1024 prerequisites and upgrading, if you are not already using clang 3.5.0
1028 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
1029 This means it is used to link the kernel and userland libraries and
1030 executables, but is not yet installed as /usr/bin/ld by default.
1032 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
1033 WITHOUT_LLD_BOOTSTRAP=yes
1036 On i386, pmtimer has been removed. Its functionality has been folded
1037 into apm. It was a no-op on ACPI in current for a while now (but was
1038 still needed on i386 in FreeBSD 11 and earlier). Users may need to
1039 remove it from kernel config files.
1042 The use of RSS hash from the network card aka flowid has been
1043 disabled by default for lagg(4) as it's currently incompatible with
1044 the lacp and loadbalance protocols.
1046 This can be re-enabled by setting the following in loader.conf:
1047 net.link.lagg.default_use_flowid="1"
1050 The SW_WATCHDOG option is no longer necessary to enable the
1051 hardclock-based software watchdog if no hardware watchdog is
1052 configured. As before, SW_WATCHDOG will cause the software
1053 watchdog to be enabled even if a hardware watchdog is configured.
1056 r326887 fixes the issue described in the 20171214 UPDATING entry.
1057 r326888 flips the switch back to building GELI support always.
1060 r362593 broke ZFS + GELI support for reasons unknown. However,
1061 it also broke ZFS support generally, so GELI has been turned off
1062 by default as the lesser evil in r326857. If you boot off ZFS and/or
1063 GELI, it might not be a good time to update.
1066 PowerPC users must update loader(8) by rebuilding world before
1067 installing a new kernel, as the protocol connecting them has
1068 changed. Without the update, loader metadata will not be passed
1069 successfully to the kernel and users will have to enter their
1070 root partition at the kernel mountroot prompt to continue booting.
1071 Newer versions of loader can boot old kernels without issue.
1074 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
1075 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
1076 to WITH/OUT_LOADER_GELI.
1079 The naive and non-compliant support of posix_fallocate(2) in ZFS
1080 has been removed as of r325320. The system call now returns EINVAL
1081 when used on a ZFS file. Although the new behavior complies with the
1082 standard, some consumers are not prepared to cope with it.
1083 One known victim is lld prior to r325420.
1086 Building in a FreeBSD src checkout will automatically create object
1087 directories now rather than store files in the current directory if
1088 'make obj' was not ran. Calling 'make obj' is no longer necessary.
1089 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
1090 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
1094 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
1095 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
1096 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
1097 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
1098 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
1099 The UNIFIED_OBJDIR option is a transitional feature that will be
1100 removed for 12.0 release; please migrate to the new format for any
1101 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
1102 than hardcoding paths.
1105 The native-xtools target no longer installs the files by default to the
1106 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
1107 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
1110 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
1111 options are changing from controlling the build if defined / undefined
1112 to controlling the build with explicit 'yes' or 'no' values. They will
1113 shift to WITH/WITHOUT options to match other options in the system.
1116 libstand has turned into a private library for sys/boot use only.
1117 It is no longer supported as a public interface outside of sys/boot.
1120 The arm port has split armv6 into armv6 and armv7. armv7 is now
1121 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
1122 and are running a kernel from before r324363, you will need to add
1123 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
1126 When building multiple kernels using KERNCONF, non-existent KERNCONF
1127 files will produce an error and buildkernel will fail. Previously
1128 missing KERNCONF files silently failed giving no indication as to
1129 why, only to subsequently discover during installkernel that the
1130 desired kernel was never built in the first place.
1133 The default serial number format for CTL LUNs has changed. This will
1134 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
1135 or iSCSI clients care about their LUNs' serial numbers. Users who
1136 require serial number stability should hardcode serial numbers in
1140 For 32-bit arm compiled for hard-float support, soft-floating point
1141 binaries now always get their shared libraries from
1142 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
1143 /usr/libsoft also existed). Only users with a hard-float ld.so, but
1144 soft-float everything else should be affected.
1147 The geli password typed at boot is now hidden. To restore the previous
1148 behavior, see geli(8) for configuration options.
1151 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
1152 sysctl values. Minor nit, but requires a rebuild of both world/kernel
1156 "make check" behavior (made in ^/head@r295380) has been changed to
1157 execute from a limited sandbox, as opposed to executing from
1161 - The "beforecheck" and "aftercheck" targets are now specified.
1162 - ${CHECKDIR} (added in commit noted above) has been removed.
1163 - Legacy behavior can be enabled by setting
1164 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
1166 If the limited sandbox mode is enabled, "make check" will execute
1167 "make distribution", then install, execute the tests, and clean up the
1168 sandbox if successful.
1170 The "make distribution" and "make install" targets are typically run as
1171 root to set appropriate permissions and ownership at installation time.
1172 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
1173 environment if executing "make check" with limited sandbox mode using
1174 an unprivileged user.
1177 Since the switch to GPT disk labels, fsck for UFS/FFS has been
1178 unable to automatically find alternate superblocks. As of r322297,
1179 the information needed to find alternate superblocks has been
1180 moved to the end of the area reserved for the boot block.
1181 Filesystems created with a newfs of this vintage or later
1182 will create the recovery information. If you have a filesystem
1183 created prior to this change and wish to have a recovery block
1184 created for your filesystem, you can do so by running fsck in
1185 foreground mode (i.e., do not use the -p or -y options). As it
1186 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
1187 to which you should answer yes.
1190 As of r321665, an NFSv4 server configuration that services
1191 Kerberos mounts or clients that do not support the uid/gid in
1192 owner/owner_group string capability, must explicitly enable
1193 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
1194 machine's /etc/rc.conf file.
1197 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
1198 Please see the 20141231 entry below for information about prerequisites
1199 and upgrading, if you are not already using clang 3.5.0 or higher.
1202 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
1203 r-commands (rlogin, rsh, etc.) to be built with the base system.
1206 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
1207 a very major ABI incompatible change, so users of FreeBSD/powerpc must
1208 be careful when performing source upgrades. It is best to run
1209 'make installworld' from an alternate root system, either a live
1210 CD/memory stick, or a temporary root partition. Additionally, all ports
1211 must be recompiled. powerpc64 is largely unaffected, except in the case
1212 of 32-bit compatibility. All 32-bit binaries will be affected.
1215 Forward compatibility for the "ino64" project have been committed. This
1216 will allow most new binaries to run on older kernels in a limited
1217 fashion. This prevents many of the common foot-shooting actions in the
1218 upgrade as well as the limited ability to roll back the kernel across
1219 the ino64 upgrade. Complicated use cases may not work properly, though
1220 enough simpler ones work to allow recovery in most situations.
1223 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
1224 if you require the GPL compiler.
1227 The internal ABI used for communication between the NFS kernel modules
1228 was changed by r320085, so __FreeBSD_version was bumped to
1229 ensure all the NFS related modules are updated together.
1232 The ABI of struct event was changed by extending the data
1233 member to 64bit and adding ext fields. For upgrade, same
1234 precautions as for the entry 20170523 "ino64" must be
1238 The GNU roff toolchain has been removed from base. To render manpages
1239 which are not supported by mandoc(1), man(1) can fallback on GNU roff
1240 from ports (and recommends to install it).
1241 To render roff(7) documents, consider using GNU roff from ports or the
1242 heirloom doctools roff toolchain from ports via pkg install groff or
1243 via pkg install heirloom-doctools.
1246 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
1247 smaller runtime footprint builds. This is useful for embedded systems
1248 which only require one chipset support.
1250 If you load it as a module, make sure this is in /boot/loader.conf:
1254 This will load the HAL, all chip/RF backends and if_ath_pci.
1255 If you have if_ath_pci in /boot/loader.conf, ensure it is after
1256 if_ath or it will not load any HAL chipset support.
1258 If you want to selectively load things (eg on ye cheape ARM/MIPS
1259 platforms where RAM is at a premium) you should:
1262 * load the chip modules in question
1263 * load ath_rate, ath_dfs
1265 * load if_ath_pci and/or if_ath_ahb depending upon your particular
1266 bus bind type - this is where probe/attach is done.
1268 For further comments/feedback, poke adrian@ .
1271 The "ino64" 64-bit inode project has been committed, which extends
1272 a number of types to 64 bits. Upgrading in place requires care and
1273 adherence to the documented upgrade procedure.
1275 If using a custom kernel configuration ensure that the
1276 COMPAT_FREEBSD11 option is included (as during the upgrade the
1277 system will be running the ino64 kernel with the existing world).
1279 For the safest in-place upgrade begin by removing previous build
1280 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full
1281 procedure documented below under the heading "To rebuild everything and
1282 install it on the current system." Specifically, a reboot is required
1283 after installing the new kernel before installing world. While an
1284 installworld normally works by accident from multiuser after rebooting
1285 the proper kernel, there are many cases where this will fail across this
1286 upgrade and installworld from single user is required.
1289 The NATM framework including the en(4), fatm(4), hatm(4), and
1290 patm(4) devices has been removed. Consumers should plan a
1291 migration before the end-of-life date for FreeBSD 11.
1294 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
1295 diff has not been implemented, if those are needed a newer version of
1296 GNU diff is available via the diffutils package under the gdiff name.
1299 As of r316810 for ipfilter, keep frags is no longer assumed when
1300 keep state is specified in a rule. r316810 aligns ipfilter with
1301 documentation in man pages separating keep frags from keep state.
1302 This allows keep state to be specified without forcing keep frags
1303 and allows keep frags to be specified independently of keep state.
1304 To maintain previous behaviour, also specify keep frags with
1305 keep state (as documented in ipf.conf.5).
1308 arm64 builds now use the base system LLD 4.0.0 linker by default,
1309 instead of requiring that the aarch64-binutils port or package be
1310 installed. To continue using aarch64-binutils, set
1311 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
1314 The UDP optimization in entry 20160818 that added the sysctl
1315 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
1316 packets will no longer be treated as L3 broadcast packets.
1319 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
1320 use any explicitly assigned loopback address available in the jail
1321 instead of using the first assigned address of the jail.
1324 The ctl.ko module no longer implements the iSCSI target frontend:
1325 cfiscsi.ko does instead.
1327 If building cfiscsi.ko as a kernel module, the module can be loaded
1328 via one of the following methods:
1329 - `cfiscsi_load="YES"` in loader.conf(5).
1330 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
1331 - ctladm(8)/ctld(8), when compiled with iSCSI support
1332 (`WITH_ISCSI=yes` in src.conf(5))
1334 Please see cfiscsi(4) for more details.
1337 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
1338 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
1339 same source (previously, the dependency of mmcsd.ko on mmc.ko was
1340 missing, but mmcsd.ko now will refuse to load if it is incompatible
1344 The syntax of ipfw(8) named states was changed to avoid ambiguity.
1345 If you have used named states in the firewall rules, you need to modify
1346 them after installworld and before rebooting. Now named states must
1347 be prefixed with colon.
1350 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
1351 removed as the userland we provide cannot use them. The KMS version
1352 (sys/dev/drm2) supports the same hardware.
1355 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
1356 Please see the 20141231 entry below for information about prerequisites
1357 and upgrading, if you are not already using clang 3.5.0 or higher.
1360 The code that provides support for ZFS .zfs/ directory functionality
1361 has been reimplemented. It's not possible now to create a snapshot
1362 by mkdir under .zfs/snapshot/. That should be the only user visible
1366 EISA bus support has been removed. The WITH_EISA option is no longer
1370 MCA bus support has been removed.
1373 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
1374 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
1377 The EM_MULTIQUEUE kernel configuration option is deprecated now that
1378 the em(4) driver conforms to iflib specifications.
1381 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
1382 IFLIB. If you have a custom kernel configuration that excludes em(4)
1383 but you use igb(4), you need to re-add em(4) to your custom
1387 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
1388 Please see the 20141231 entry below for information about prerequisites
1389 and upgrading, if you are not already using clang 3.5.0 or higher.
1392 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
1393 Please see the 20141231 entry below for information about prerequisites
1394 and upgrading, if you are not already using clang 3.5.0 or higher.
1397 The layout of the pmap structure has changed for powerpc to put the pmap
1398 statistics at the front for all CPU variations. libkvm(3) and all tools
1399 that link against it need to be recompiled.
1402 isl(4) and cyapa(4) drivers now require a new driver,
1403 chromebook_platform(4), to work properly on Chromebook-class hardware.
1404 On other types of hardware the drivers may need to be configured using
1405 device hints. Please see the corresponding manual pages for details.
1408 The urtwn(4) driver was merged into rtwn(4) and now consists of
1409 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
1411 Also, firmware for RTL8188CE was renamed due to possible name
1412 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
1415 GNU rcs has been removed from base. It is available as packages:
1416 - rcs: Latest GPLv3 GNU rcs version.
1417 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
1421 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
1422 modules now requires that the kernel configuration contain the
1423 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
1426 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
1427 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
1430 Relocatable object files with the extension of .So have been renamed
1431 to use an extension of .pico instead. The purpose of this change is
1432 to avoid a name clash with shared libraries on case-insensitive file
1433 systems. On those file systems, foo.So is the same file as foo.so.
1436 GNU rcs has been turned off by default. It can (temporarily) be built
1437 again by adding WITH_RCS knob in src.conf.
1438 Otherwise, GNU rcs is available from packages:
1439 - rcs: Latest GPLv3 GNU rcs version.
1440 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
1443 The backup_uses_rcs functionality has been removed from rc.subr.
1446 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
1447 two separate components, QUEUE_MACRO_DEBUG_TRACE and
1448 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
1449 QUEUE_MACRO_DEBUG behavior.
1452 r304787 changed some ioctl interfaces between the iSCSI userspace
1453 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1454 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1458 The UDP receive code has been updated to only treat incoming UDP
1459 packets that were addressed to an L2 broadcast address as L3
1460 broadcast packets. It is not expected that this will affect any
1461 standards-conforming UDP application. The new behaviour can be
1462 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1466 Remove the openbsd_poll system call.
1467 __FreeBSD_version has been bumped because of this.
1470 The stable/11 branch has been created from head@r302406.
1473 The libc stub for the pipe(2) system call has been replaced with
1474 a wrapper that calls the pipe2(2) system call and the pipe(2)
1475 system call is now only implemented by the kernels that include
1476 "options COMPAT_FREEBSD10" in their config file (this is the
1477 default). Users should ensure that this option is enabled in
1478 their kernel or upgrade userspace to r302092 before upgrading their
1482 CAM will now strip leading spaces from SCSI disks' serial numbers.
1483 This will affect users who create UFS filesystems on SCSI disks using
1484 those disk's diskid device nodes. For example, if /etc/fstab
1485 previously contained a line like
1486 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
1487 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
1488 transforms like gmirror may also be affected. ZFS users should
1492 The bitstring(3) API has been updated with new functionality and
1493 improved performance. But it is binary-incompatible with the old API.
1494 Objects built with the new headers may not be linked against objects
1495 built with the old headers.
1498 The brk and sbrk functions have been removed from libc on arm64.
1499 Binutils from ports has been updated to not link to these
1500 functions and should be updated to the latest version before
1501 installing a new libc.
1504 The armv6 port now defaults to hard float ABI. Limited support
1505 for running both hardfloat and soft float on the same system
1506 is available using the libraries installed with -DWITH_LIBSOFT.
1507 This has only been tested as an upgrade path for installworld
1508 and packages may fail or need manual intervention to run. New
1509 packages will be needed.
1511 To update an existing self-hosted armv6hf system, you must add
1512 TARGET_ARCH=armv6 on the make command line for both the build
1513 and the install steps.
1516 Kernel modules compiled outside of a kernel build now default to
1517 installing to /boot/modules instead of /boot/kernel. Many kernel
1518 modules built this way (such as those in ports) already overrode
1519 KMODDIR explicitly to install into /boot/modules. However,
1520 manually building and installing a module from /sys/modules will
1521 now install to /boot/modules instead of /boot/kernel.
1524 The CAM I/O scheduler has been committed to the kernel. There should be
1525 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1526 list of known rogues that claim support for this but actually corrupt
1527 data is believed to be complete, be on the lookout for data
1528 corruption. The known rogue list is believed to be complete:
1530 o Crucial MX100, M550 drives with MU01 firmware.
1531 o Micron M510 and M550 drives with MU01 firmware.
1532 o Micron M500 prior to MU07 firmware
1533 o Samsung 830, 840, and 850 all firmwares
1534 o FCCT M500 all firmwares
1536 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1537 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1538 updated firmware. Black listed drives will work correctly because these
1539 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1540 this list is the same as found in Linux, it's believed there are no
1541 other rogues in the market place. All other models from the above
1544 To be safe, if you are at all concerned, you can quirk each of your
1545 drives to prevent NCQ from being sent by setting:
1546 kern.cam.ada.X.quirks="0x2"
1547 in loader.conf. If the drive requires the 4k sector quirk, set the
1548 quirks entry to 0x3.
1551 The FAST_DEPEND build option has been removed and its functionality is
1552 now the one true way. The old mkdep(1) style of 'make depend' has
1553 been removed. See 20160311 for further details.
1556 Resource range types have grown from unsigned long to uintmax_t. All
1557 drivers, and anything using libdevinfo, need to be recompiled.
1560 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1561 builds. It no longer runs mkdep(1) during 'make depend', and the
1562 'make depend' stage can safely be skipped now as it is auto ran
1563 when building 'make all' and will generate all SRCS and DPSRCS before
1564 building anything else. Dependencies are gathered at compile time with
1565 -MF flags kept in separate .depend files per object file. Users should
1566 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1567 stale .depend files.
1570 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1571 kernel modules. Therefore, if you load any kernel modules at boot time,
1572 please install the boot loaders after you install the kernel, but before
1576 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1577 make installkernel KERNCONF=YOUR_KERNEL_HERE
1578 make -C sys/boot install
1579 <reboot in single user>
1581 Then follow the usual steps, described in the General Notes section,
1585 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1586 see the 20141231 entry below for information about prerequisites and
1587 upgrading, if you are not already using clang 3.5.0 or higher.
1590 The AIO subsystem is now a standard part of the kernel. The
1591 VFS_AIO kernel option and aio.ko kernel module have been removed.
1592 Due to stability concerns, asynchronous I/O requests are only
1593 permitted on sockets and raw disks by default. To enable
1594 asynchronous I/O requests on all file types, set the
1595 vfs.aio.enable_unsafe sysctl to a non-zero value.
1598 The ELF object manipulation tool objcopy is now provided by the
1599 ELF Tool Chain project rather than by GNU binutils. It should be a
1600 drop-in replacement, with the addition of arm64 support. The
1601 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1602 to obtain the GNU version if necessary.
1605 Building ZFS pools on top of zvols is prohibited by default. That
1606 feature has never worked safely; it's always been prone to deadlocks.
1607 Using a zvol as the backing store for a VM guest's virtual disk will
1608 still work, even if the guest is using ZFS. Legacy behavior can be
1609 restored by setting vfs.zfs.vol.recursive=1.
1612 The NONE and HPN patches has been removed from OpenSSH. They are
1613 still available in the security/openssh-portable port.
1616 With the addition of ypldap(8), a new _ypldap user is now required
1617 during installworld. "mergemaster -p" can be used to add the user
1618 prior to installworld, as documented in the handbook.
1621 The tftp loader (pxeboot) now uses the option root-path directive. As a
1622 consequence it no longer looks for a pxeboot.4th file on the tftp
1623 server. Instead it uses the regular /boot infrastructure as with the
1627 The code to start recording plug and play data into the modules has
1628 been committed. While the old tools will properly build a new kernel,
1629 a number of warnings about "unknown metadata record 4" will be produced
1630 for an older kldxref. To avoid such warnings, make sure to rebuild
1631 the kernel toolchain (or world). Make sure that you have r292078 or
1632 later when trying to build 292077 or later before rebuilding.
1635 Debug data files are now built by default with 'make buildworld' and
1636 installed with 'make installworld'. This facilitates debugging but
1637 requires more disk space both during the build and for the installed
1638 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1642 r291527 changed the internal interface between the nfsd.ko and
1643 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1644 __FreeBSD_version has been bumped because of this.
1647 Add support for unicode collation strings leads to a change of
1648 order of files listed by ls(1) for example. To get back to the old
1649 behaviour, set LC_COLLATE environment variable to "C".
1651 Databases administrators will need to reindex their databases given
1652 collation results will be different.
1654 Due to a bug in install(1) it is recommended to remove the ancient
1655 locales before running make installworld.
1657 rm -rf /usr/share/locale/*
1660 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1661 libcrypto.so.7 or libssl.so.7 must be recompiled.
1664 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1665 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1666 should be replaced with isp_2400 and isp_2500 modules respectively.
1669 The build previously allowed using 'make -n' to not recurse into
1670 sub-directories while showing what commands would be executed, and
1671 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1672 and 'make -N' will not.
1675 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1676 and etcupdate will now use this file. A custom sendmail.cf is now
1677 updated via this mechanism rather than via installworld. If you had
1678 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1679 want to remove the exclusion or change it to "always install".
1680 /etc/mail/sendmail.cf is now managed the same way regardless of
1681 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1682 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1685 Compatibility shims for legacy ATA device names have been removed.
1686 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1687 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1688 environment variables, /dev/ad* and /dev/ar* symbolic links.
1691 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1692 Please see the 20141231 entry below for information about prerequisites
1693 and upgrading, if you are not already using clang 3.5.0 or higher.
1696 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1697 and renamed from .symbols to .debug. This reduces the size requirements
1698 on the boot partition or file system and provides consistency with
1699 userland debug files.
1701 When using the supported kernel installation method the
1702 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1703 as is done with /boot/kernel.
1705 Developers wishing to maintain the historical behavior of installing
1706 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1709 The wireless drivers had undergone changes that remove the 'parent
1710 interface' from the ifconfig -l output. The rc.d network scripts
1711 used to check presence of a parent interface in the list, so old
1712 scripts would fail to start wireless networking. Thus, etcupdate(3)
1713 or mergemaster(8) run is required after kernel update, to update your
1714 rc.d scripts in /etc.
1717 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1718 These configurations are now automatically interpreted as
1719 'scrub fragment reassemble'.
1722 Kernel-loadable modules for the random(4) device are back. To use
1723 them, the kernel must have
1726 options RANDOM_LOADABLE
1728 kldload(8) can then be used to load random_fortuna.ko
1729 or random_yarrow.ko. Please note that due to the indirect
1730 function calls that the loadable modules need to provide,
1731 the build-in variants will be slightly more efficient.
1733 The random(4) kernel option RANDOM_DUMMY has been retired due to
1734 unpopularity. It was not all that useful anyway.
1737 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1738 Control over building the ELF Tool Chain tools is now provided by
1739 the WITHOUT_TOOLCHAIN knob.
1742 The polarity of Pulse Per Second (PPS) capture events with the
1743 uart(4) driver has been corrected. Prior to this change the PPS
1744 "assert" event corresponded to the trailing edge of a positive PPS
1745 pulse and the "clear" event was the leading edge of the next pulse.
1747 As the width of a PPS pulse in a typical GPS receiver is on the
1748 order of 1 millisecond, most users will not notice any significant
1749 difference with this change.
1751 Anyone who has compensated for the historical polarity reversal by
1752 configuring a negative offset equal to the pulse width will need to
1753 remove that workaround.
1756 The default group assigned to /dev/dri entries has been changed
1757 from 'wheel' to 'video' with the id of '44'. If you want to have
1758 access to the dri devices please add yourself to the video group
1761 # pw groupmod video -m $USER
1764 The menu.rc and loader.rc files will now be replaced during
1765 upgrades. Please migrate local changes to menu.rc.local and
1766 loader.rc.local instead.
1769 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1770 strings and strip have been removed. The src.conf(5) knob
1771 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1774 As ZFS requires more kernel stack pages than is the default on some
1775 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1776 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1778 Please consider using 'options KSTACK_PAGES=X' where X is greater
1779 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1782 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1783 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1784 default, i.e., they will not contain "::". For example, instead
1785 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1786 to have a more specific match, such as different map entries for
1787 IPv6:0:0 vs IPv6:0. This change requires that configuration
1788 data (including maps, files, classes, custom ruleset, etc.) must
1789 use the same format, so make certain such configuration data is
1790 upgrading. As a very simple check search for patterns like
1791 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1792 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1793 the cf option UseCompressedIPv6Addresses.
1796 The default kernel entropy-processing algorithm is now
1797 Fortuna, replacing Yarrow.
1799 Assuming you have 'device random' in your kernel config
1800 file, the configurations allow a kernel option to override
1801 this default. You may choose *ONE* of:
1803 options RANDOM_YARROW # Legacy /dev/random algorithm.
1804 options RANDOM_DUMMY # Blocking-only driver.
1806 If you have neither, you get Fortuna. For most people,
1807 read no further, Fortuna will give a /dev/random that works
1808 like it always used to, and the difference will be irrelevant.
1810 If you remove 'device random', you get *NO* kernel-processed
1811 entropy at all. This may be acceptable to folks building
1812 embedded systems, but has complications. Carry on reading,
1813 and it is assumed you know what you need.
1815 *PLEASE* read random(4) and random(9) if you are in the
1816 habit of tweaking kernel configs, and/or if you are a member
1817 of the embedded community, wanting specific and not-usual
1818 behaviour from your security subsystems.
1820 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1821 random', you will NOT have a functioning /dev/random, and
1822 many cryptographic features will not work, including SSH.
1823 You may also find strange behaviour from the random(3) set
1824 of library functions, in particular sranddev(3), srandomdev(3)
1825 and arc4random(3). The reason for this is that the KERN_ARND
1826 sysctl only returns entropy if it thinks it has some to
1827 share, and with RANDOM_DUMMY or no 'device random' this
1831 An additional fix for the issue described in the 20150614 sendmail
1832 entry below has been committed in revision 284717.
1835 FreeBSD's old make (fmake) has been removed from the system. It is
1836 available as the devel/fmake port or via pkg install fmake.
1839 The fix for the issue described in the 20150614 sendmail entry
1840 below has been committed in revision 284436. The work
1841 around described in that entry is no longer needed unless the
1842 default setting is overridden by a confDH_PARAMETERS configuration
1843 setting of '5' or pointing to a 512 bit DH parameter file.
1846 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1847 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1848 and devel/kyua to version 0.20+ and adjust any calling code to work
1849 with Kyuafile and kyua.
1852 The import of openssl to address the FreeBSD-SA-15:10.openssl
1853 security advisory includes a change which rejects handshakes
1854 with DH parameters below 768 bits. sendmail releases prior
1855 to 8.15.2 (not yet released), defaulted to a 512 bit
1856 DH parameter setting for client connections. To work around
1857 this interoperability, sendmail can be configured to use a
1858 2048 bit DH parameter by:
1860 1. Edit /etc/mail/`hostname`.mc
1861 2. If a setting for confDH_PARAMETERS does not exist or
1862 exists and is set to a string beginning with '5',
1863 replace it with '2'.
1864 3. If a setting for confDH_PARAMETERS exists and is set to
1865 a file path, create a new file with:
1866 openssl dhparam -out /path/to/file 2048
1867 4. Rebuild the .cf file:
1868 cd /etc/mail/; make; make install
1869 5. Restart sendmail:
1870 cd /etc/mail/; make restart
1872 A sendmail patch is coming, at which time this file will be
1876 Generation of legacy formatted entries have been disabled by default
1877 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1878 entries were converted to use the new format by default when the new,
1879 machine independent format have been added and supported since FreeBSD
1882 Please see the pwd_mkdb(8) manual page for further details.
1885 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1886 20141231 entry below for information about prerequisites and upgrading,
1887 if you are not already using 3.5.0 or higher.
1890 TI platform code switched to using vendor DTS files and this update
1891 may break existing systems running on Beaglebone, Beaglebone Black,
1894 - dtb files should be regenerated/reinstalled. Filenames are the
1895 same but content is different now
1896 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1897 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1898 addressing scheme is now pin 25 on /dev/gpioc3.
1899 - Pandaboard: /etc/ttys should be updated, serial console device is
1900 now /dev/ttyu2, not /dev/ttyu0
1903 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1904 If you need the GNU extension from groff soelim(1), install groff
1905 from package: pkg install groff, or via ports: textproc/groff.
1908 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1909 defined in symlink(7); previously symlinks were silently ignored.
1912 The const qualifier has been removed from iconv(3) to comply with
1913 POSIX. The ports tree is aware of this from r384038 onwards.
1916 Libraries specified by LIBADD in Makefiles must have a corresponding
1917 DPADD_<lib> variable to ensure correct dependencies. This is now
1918 enforced in src.libnames.mk.
1921 From legacy ata(4) driver was removed support for SATA controllers
1922 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1923 Kernel modules ataahci and ataadaptec were removed completely,
1924 replaced by ahci and mvs modules respectively.
1927 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1928 the 20141231 entry below for information about prerequisites and
1929 upgrading, if you are not already using 3.5.0 or higher.
1932 The 32-bit PowerPC kernel has been changed to a position-independent
1933 executable. This can only be booted with a version of loader(8)
1934 newer than January 31, 2015, so make sure to update both world and
1935 kernel before rebooting.
1938 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1939 but before r278950, the RNG was not seeded properly. Immediately
1940 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1941 ssh keys or openssl keys) that were generated w/ a kernel from that
1942 range. This does not affect programs that directly used /dev/random
1943 or /dev/urandom. All userland uses of arc4random(3) are affected.
1946 The autofs(4) ABI was changed in order to restore binary compatibility
1947 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1948 with the new kernel.
1951 The powerpc64 kernel has been changed to a position-independent
1952 executable. This can only be booted with a new version of loader(8),
1953 so make sure to update both world and kernel before rebooting.
1956 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1957 only release, no new features have been added. Please see the 20141231
1958 entry below for information about prerequisites and upgrading, if you
1959 are not already using 3.5.0.
1962 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1963 taken from the ELF Tool Chain project rather than GNU binutils. They
1964 should be drop-in replacements, with the addition of arm64 support.
1965 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1966 binutils tools, if necessary. See 20150805 for updated information.
1969 The default Unbound configuration now enables remote control
1970 using a local socket. Users who have already enabled the
1971 local_unbound service should regenerate their configuration
1972 by running "service local_unbound setup" as root.
1975 The GNU texinfo and GNU info pages have been removed.
1976 To be able to view GNU info pages please install texinfo from ports.
1979 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1981 As of this release, a prerequisite for building clang, llvm and lldb is
1982 a C++11 capable compiler and C++11 standard library. This means that to
1983 be able to successfully build the cross-tools stage of buildworld, with
1984 clang as the bootstrap compiler, your system compiler or cross compiler
1985 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1986 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1989 On any standard FreeBSD 10.x or 11.x installation, where clang and
1990 libc++ are on by default (that is, on x86 or arm), this should work out
1993 On 9.x installations where clang is enabled by default, e.g. on x86 and
1994 powerpc, libc++ will not be enabled by default, so libc++ should be
1995 built (with clang) and installed first. If both clang and libc++ are
1996 missing, build clang first, then use it to build libc++.
1998 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1999 the instructions for 9.x above.
2001 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
2002 default, and do not build clang.
2004 Many embedded systems are resource constrained, and will not be able to
2005 build clang in a reasonable time, or in some cases at all. In those
2006 cases, cross building bootable systems on amd64 is a workaround.
2008 This new version of clang introduces a number of new warnings, of which
2009 the following are most likely to appear:
2013 This warns in two cases, for both C and C++:
2014 * When the code is trying to take the absolute value of an unsigned
2015 quantity, which is effectively a no-op, and almost never what was
2016 intended. The code should be fixed, if at all possible. If you are
2017 sure that the unsigned quantity can be safely cast to signed, without
2018 loss of information or undefined behavior, you can add an explicit
2019 cast, or disable the warning.
2021 * When the code is trying to take an absolute value, but the called
2022 abs() variant is for the wrong type, which can lead to truncation.
2023 If you want to disable the warning instead of fixing the code, please
2024 make sure that truncation will not occur, or it might lead to unwanted
2027 -Wtautological-undefined-compare and
2028 -Wundefined-bool-conversion
2030 These warn when C++ code is trying to compare 'this' against NULL, while
2031 'this' should never be NULL in well-defined C++ code. However, there is
2032 some legacy (pre C++11) code out there, which actively abuses this
2033 feature, which was less strictly defined in previous C++ versions.
2035 Squid and openjdk do this, for example. The warning can be turned off
2036 for C++98 and earlier, but compiling the code in C++11 mode might result
2037 in unexpected behavior; for example, the parts of the program that are
2038 unreachable could be optimized away.
2041 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
2042 kernel sources have been removed. The .h files remain, since some
2043 utilities include them. This will need to be fixed later.
2044 If "mount -t oldnfs ..." is attempted, it will fail.
2045 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
2046 the utilities will report errors.
2049 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
2050 directories to top level SUBDIR variable when their parent
2051 directory is included in LOCAL_DIRS. Users with build systems with
2052 such hierarchies and without SUBDIR entries in the parent
2053 directory Makefiles should add them or add the directories to
2057 faith(4) and faithd(8) have been removed from the base system. Faith
2058 has been obsolete for a very long time.
2061 vt(4), the new console driver, is enabled by default. It brings
2062 support for Unicode and double-width characters, as well as
2063 support for UEFI and integration with the KMS kernel video
2066 You may need to update your console settings in /etc/rc.conf,
2067 most probably the keymap. During boot, /etc/rc.d/syscons will
2068 indicate what you need to do.
2070 vt(4) still has issues and lacks some features compared to
2071 syscons(4). See the wiki for up-to-date information:
2072 https://wiki.freebsd.org/Newcons
2074 If you want to keep using syscons(4), you can do so by adding
2075 the following line to /boot/loader.conf:
2079 pjdfstest has been integrated into kyua as an opt-in test suite.
2080 Please see share/doc/pjdfstest/README for more details on how to
2084 gperf has been removed from the base system for architectures
2085 that use clang. Ports that require gperf will obtain it from the
2089 pjdfstest has been moved from tools/regression/pjdfstest to
2093 At svn r271982, The default linux compat kernel ABI has been adjusted
2094 to 2.6.18 in support of the linux-c6 compat ports infrastructure
2095 update. If you wish to continue using the linux-f10 compat ports,
2096 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
2097 encouraged to update their linux-compat packages to linux-c6 during
2098 their next update cycle.
2101 The ofwfb driver, used to provide a graphics console on PowerPC when
2102 using vt(4), no longer allows mmap() of all physical memory. This
2103 will prevent Xorg on PowerPC with some ATI graphics cards from
2104 initializing properly unless x11-servers/xorg-server is updated to
2108 The xdev targets have been converted to using TARGET and
2109 TARGET_ARCH instead of XDEV and XDEV_ARCH.
2112 The default unbound configuration has been modified to address
2113 issues with reverse lookups on networks that use private
2114 address ranges. If you use the local_unbound service, run
2115 "service local_unbound setup" as root to regenerate your
2116 configuration, then "service local_unbound reload" to load the
2120 The GNU texinfo and GNU info pages are not built and installed
2121 anymore, WITH_INFO knob has been added to allow to built and install
2123 UPDATE: see 20150102 entry on texinfo's removal
2126 The GNU readline library is now an INTERNALLIB - that is, it is
2127 statically linked into consumers (GDB and variants) in the base
2128 system, and the shared library is no longer installed. The
2129 devel/readline port is available for third party software that
2133 The Itanium architecture (ia64) has been removed from the list of
2134 known architectures. This is the first step in the removal of the
2138 Commit r268115 has added NFSv4.1 server support, merged from
2139 projects/nfsv4.1-server. Since this includes changes to the
2140 internal interfaces between the NFS related modules, a full
2141 build of the kernel and modules will be necessary.
2142 __FreeBSD_version has been bumped.
2145 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
2146 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
2147 which differs from the behaviour controlled by this knob.)
2150 Maximal length of the serial number in CTL was increased from 16 to
2151 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
2152 and ctld, need to be rebuilt to work with a new kernel.
2155 The libatf-c and libatf-c++ major versions were downgraded to 0 and
2156 1 respectively to match the upstream numbers. They were out of
2157 sync because, when they were originally added to FreeBSD, the
2158 upstream versions were not respected. These libraries are private
2159 and not yet built by default, so renumbering them should be a
2160 non-issue. However, unclean source trees will yield broken test
2161 programs once the operator executes "make delete-old-libs" after a
2162 "make installworld".
2164 Additionally, the atf-sh binary was made private by moving it into
2165 /usr/libexec/. Already-built shell test programs will keep the
2166 path to the old binary so they will break after "make delete-old"
2169 If you are using WITH_TESTS=yes (not the default), wipe the object
2170 tree and rebuild from scratch to prevent spurious test failures.
2171 This is only needed once: the misnumbered libraries and misplaced
2172 binaries have been added to OptionalObsoleteFiles.inc so they will
2173 be removed during a clean upgrade.
2176 Clang and llvm have been upgraded to 3.4.1 release.
2179 We bogusly installed src.opts.mk in /usr/share/mk. This file should
2180 be removed to avoid issues in the future (and has been added to
2184 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
2185 past, it affected all builds that used the bsd.*.mk files. The old
2186 behavior was a bug, but people may have relied upon it. To get this
2187 behavior back, you can .include /etc/src.conf from /etc/make.conf
2188 (which is still global and isn't changed). This also changes the
2189 behavior of incremental builds inside the tree of individual
2190 directories. Set MAKESYSPATH to ".../share/mk" to do that.
2191 Although this has survived make universe and some upgrade scenarios,
2192 other upgrade scenarios may have broken. At least one form of
2193 temporary breakage was fixed with MAKESYSPATH settings for buildworld
2194 as well... In cases where MAKESYSPATH isn't working with this
2195 setting, you'll need to set it to the full path to your tree.
2197 One side effect of all this cleaning up is that bsd.compiler.mk
2198 is no longer implicitly included by bsd.own.mk. If you wish to
2199 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
2203 The lindev device has been removed since /dev/full has been made a
2204 standard device. __FreeBSD_version has been bumped.
2207 The knob WITHOUT_VI was added to the base system, which controls
2208 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
2209 in order to reorder files share/termcap and didn't build ex(1) as a
2210 build tool, so building/installing with WITH_VI is highly advised for
2211 build hosts for older releases.
2213 This issue has been fixed in stable/9 and stable/10 in r277022 and
2214 r276991, respectively.
2217 The YES_HESIOD knob has been removed. It has been obsolete for
2218 a decade. Please move to using WITH_HESIOD instead or your builds
2219 will silently lack HESIOD.
2222 The uart(4) driver has been changed with respect to its handling
2223 of the low-level console. Previously the uart(4) driver prevented
2224 any process from changing the baudrate or the CLOCAL and HUPCL
2225 control flags. By removing the restrictions, operators can make
2226 changes to the serial console port without having to reboot.
2227 However, when getty(8) is started on the serial device that is
2228 associated with the low-level console, a misconfigured terminal
2229 line in /etc/ttys will now have a real impact.
2230 Before upgrading the kernel, make sure that /etc/ttys has the
2231 serial console device configured as 3wire without baudrate to
2232 preserve the previous behaviour. E.g:
2233 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
2236 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
2237 to improve performance. To re-enable it, if needed, run rpcbind
2238 with command line option -W.
2241 Switched back to the GPL dtc compiler due to updates in the upstream
2242 dts files not being supported by the BSDL dtc compiler. You will need
2243 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
2244 may result while building dtb files during a kernel build if you fail
2245 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
2248 Clang and llvm have been upgraded to 3.4 release.
2251 The nve(4) driver has been removed. Please use the nfe(4) driver
2252 for NVIDIA nForce MCP Ethernet adapters instead.
2255 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
2256 This could cause certain C++ applications using shared libraries built
2257 against the previous version of libc++ to crash. The incompatibility
2258 has now been fixed, but any C++ applications or shared libraries built
2259 between r261283 and r261801 should be recompiled.
2262 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
2263 capability mode support. Please note that enabling the feature in
2264 kernel is still highly recommended.
2267 OpenSSH is now built with sandbox support, and will use sandbox as
2268 the default privilege separation method. This requires Capsicum
2269 capability mode support in kernel.
2272 The libelf and libdwarf libraries have been updated to newer
2273 versions from upstream. Shared library version numbers for
2274 these two libraries were bumped. Any ports or binaries
2275 requiring these two libraries should be recompiled.
2276 __FreeBSD_version is bumped to 1100006.
2279 If a Makefile in a tests/ directory was auto-generating a Kyuafile
2280 instead of providing an explicit one, this would prevent such
2281 Makefile from providing its own Kyuafile in the future during
2282 NO_CLEAN builds. This has been fixed in the Makefiles but manual
2283 intervention is needed to clean an objdir if you use NO_CLEAN:
2284 # find /usr/obj -name Kyuafile | xargs rm -f
2287 The behavior of gss_pseudo_random() for the krb5 mechanism
2288 has changed, for applications requesting a longer random string
2289 than produced by the underlying enctype's pseudo-random() function.
2290 In particular, the random string produced from a session key of
2291 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
2292 be different at the 17th octet and later, after this change.
2293 The counter used in the PRF+ construction is now encoded as a
2294 big-endian integer in accordance with RFC 4402.
2295 __FreeBSD_version is bumped to 1100004.
2298 The WITHOUT_ATF build knob has been removed and its functionality
2299 has been subsumed into the more generic WITHOUT_TESTS. If you were
2300 using the former to disable the build of the ATF libraries, you
2301 should change your settings to use the latter.
2304 The default version of mtree is nmtree which is obtained from
2305 NetBSD. The output is generally the same, but may vary
2306 slightly. If you found you need identical output adding
2307 "-F freebsd9" to the command line should do the trick. For the
2308 time being, the old mtree is available as fmtree.
2311 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
2312 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
2313 1.1.4_8 and verify bsdyml not linked in, before running "make
2315 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
2317 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
2320 The stable/10 branch has been created in subversion from head
2327 Sometimes, obscure build problems are the result of environment
2328 poisoning. This can happen because the make utility reads its
2329 environment when searching for values for global variables. To run
2330 your build attempts in an "environmental clean room", prefix all make
2331 commands with 'env -i '. See the env(1) manual page for more details.
2332 Occasionally a build failure will occur with "make -j" due to a race
2333 condition. If this happens try building again without -j, and please
2334 report a bug if it happens consistently.
2336 When upgrading from one major version to another it is generally best to
2337 upgrade to the latest code in the currently installed branch first, then
2338 do an upgrade to the new branch. This is the best-tested upgrade path,
2339 and has the highest probability of being successful. Please try this
2340 approach if you encounter problems with a major version upgrade. Since
2341 the stable 4.x branch point, one has generally been able to upgrade from
2342 anywhere in the most recent stable branch to head / current (or even the
2343 last couple of stable branches). See the top of this file when there's
2346 The update process will emit an error on an attempt to perform a build
2347 or install from a FreeBSD version below the earliest supported version.
2348 When updating from an older version the update should be performed one
2349 major release at a time, including running `make delete-old` at each
2352 When upgrading a live system, having a root shell around before
2353 installing anything can help undo problems. Not having a root shell
2354 around can lead to problems if pam has changed too much from your
2355 starting point to allow continued authentication after the upgrade.
2357 This file should be read as a log of events. When a later event changes
2358 information of a prior event, the prior event should not be deleted.
2359 Instead, a pointer to the entry with the new information should be
2360 placed in the old entry. Readers of this file should also sanity check
2361 older entries before relying on them blindly. Authors of new entries
2362 should write them with this in mind.
2366 When upgrading the boot ZFS pool to a new version, always follow
2369 1.) recompile and reinstall the ZFS boot loader and boot block
2370 (this is part of "make buildworld" and "make installworld")
2372 2.) update the ZFS boot block on your boot drive
2374 The following example updates the ZFS boot block on the
2375 freebsd-boot partition of a GPT partitioned drive ada0:
2376 "gpart bootcode -p /boot/gptzfsboot -i $N ada0"
2377 The value $N will typically be 1 (if booting from BIOS) or 2 (if
2380 Non-boot pools do not need these updates.
2384 If you are updating from a prior version of FreeBSD (even one just
2385 a few days old), you should follow this procedure. It is the most
2386 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2388 make kernel-toolchain
2389 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2390 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2392 To test a kernel once
2393 ---------------------
2394 If you just want to boot a kernel once (because you are not sure
2395 if it works, or if you want to boot a known bad kernel to provide
2396 debugging information) run
2397 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2398 nextboot -k testkernel
2400 To rebuild everything and install it on the current system.
2401 -----------------------------------------------------------
2402 # Note: sometimes if you are running current you gotta do more than
2403 # is listed here if you are upgrading from a really old current.
2405 <make sure you have good level 0 dumps>
2407 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2408 make installkernel KERNCONF=YOUR_KERNEL_HERE
2410 <reboot in single user> [3]
2417 To cross-install current onto a separate partition
2418 --------------------------------------------------
2419 # In this approach we use a separate partition to hold
2420 # current's root, 'usr', and 'var' directories. A partition
2421 # holding "/", "/usr" and "/var" should be about 2GB in
2424 <make sure you have good level 0 dumps>
2427 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2428 <maybe newfs current's root partition>
2429 <mount current's root partition on directory ${CURRENT_ROOT}>
2430 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
2431 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2432 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2433 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2434 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2435 <reboot into current>
2436 <do a "native" rebuild/install as described in the previous section>
2437 <maybe install compatibility libraries from ports/misc/compat*>
2441 To upgrade in-place from stable to current
2442 ----------------------------------------------
2443 <make sure you have good level 0 dumps>
2445 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
2446 make installkernel KERNCONF=YOUR_KERNEL_HERE
2448 <reboot in single user> [3]
2455 Make sure that you've read the UPDATING file to understand the
2456 tweaks to various things you need. At this point in the life
2457 cycle of current, things change often and you are on your own
2458 to cope. The defaults can also change, so please read ALL of
2459 the UPDATING entries.
2461 Also, if you are tracking -current, you must be subscribed to
2462 freebsd-current@freebsd.org. Make sure that before you update
2463 your sources that you have read and understood all the recent
2464 messages there. If in doubt, please track -stable which has
2465 much fewer pitfalls.
2467 [1] If you have third party modules, such as vmware, you should disable
2468 them at this point so they don't crash your system on
2469 reboot. Alternatively, you should rebuild all the modules you have in
2470 your system and install them as well. If you are running -current, you
2471 should seriously consider placing all sources to all the modules for
2472 your system (or symlinks to them) in /usr/local/sys/modules so this
2473 happens automatically. If all your modules come from ports, then adding
2474 the port origin directories to PORTS_MODULES instead is also automatic
2476 PORTS_MODULES+=x11/nvidia-driver
2478 [3] From the bootblocks, boot -s, and then do
2482 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed
2483 cd src # full path to source
2484 adjkerntz -i # if CMOS is wall time
2485 Also, when doing a major release upgrade, it is required that you boot
2486 into single user mode to do the installworld.
2488 [4] Note: This step is non-optional. Failure to do this step
2489 can result in a significant reduction in the functionality of the
2490 system. Attempting to do it by hand is not recommended and those
2491 that pursue this avenue should read this file carefully, as well
2492 as the archives of freebsd-current and freebsd-hackers mailing lists
2493 for potential gotchas. The -U option is also useful to consider.
2494 See mergemaster(8) for more information.
2496 [5] Usually this step is a no-op. However, from time to time
2497 you may need to do this if you get unknown user in the following
2498 step. It never hurts to do it all the time. You may need to
2499 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2500 install) after the buildworld before this step if you last updated
2501 from current before 20130425 or from -stable before 20130430.
2503 [6] This only deletes old files and directories. Old libraries
2504 can be deleted by "make delete-old-libs", but you have to make
2505 sure that no program is using those libraries anymore.
2507 [8] The new kernel must be able to run existing binaries used by an
2508 installworld. When upgrading across major versions, the new kernel's
2509 configuration must include the correct COMPAT_FREEBSD<n> option for
2510 existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure
2511 to do so may leave you with a system that is hard to boot to recover. A
2512 GENERIC kernel will include suitable compatibility options to run
2513 binaries from older branches. Note that the ability to run binaries
2514 from unsupported branches is not guaranteed.
2516 Make sure that you merge any new devices from GENERIC since the
2517 last time you updated your kernel config file. Options also
2518 change over time, so you may need to adjust your custom kernels
2521 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2522 "?=" instead of the "=" assignment operator, so that buildworld can
2523 override the CPUTYPE if it needs to.
2525 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2526 not on the command line, or in /etc/make.conf. buildworld will
2527 warn if it is improperly defined.
2530 This file contains a list, in reverse chronological order, of major
2531 breakages in tracking -current. It is not guaranteed to be a complete
2532 list of such breakages, and only contains entries since September 23, 2011.
2533 If you need to see UPDATING entries from before that date, you will need
2534 to fetch an UPDATING file from an older FreeBSD release.
2536 Copyright information:
2538 Copyright 1998-2009 M. Warner Losh <imp@FreeBSD.org>
2540 Redistribution, publication, translation and use, with or without
2541 modification, in full or in part, in any form or format of this
2542 document are permitted without further permission from the author.
2544 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2545 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2546 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2547 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2548 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2549 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2550 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2551 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2552 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2553 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2554 POSSIBILITY OF SUCH DAMAGE.
2556 Contact Warner Losh if you have any questions about your use of