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
19 LinuxKPI pm.h changes require an update to the latest drm-kmod version
20 before re-compiling to avoid errors.
23 Bump __FreeBSD_verion to 1301501 after merging LinuxKPI and
24 net80211 changes in order to help out-of-tree consumers to deal
28 For 64-bit architectures the base system is now built with Position
29 Independent Executable (PIE) support enabled by default. It may be
30 disabled using the WITHOUT_PIE knob. A clean build is required.
33 The macros provided for the manipulation of CPU sets (e.g. CPU_AND)
34 have been modified to take 2 source arguments instead of only 1.
35 Externally maintained sources that use these macros will have to
36 be adapted. The FreeBSD version has been bumped to 1300524 to
40 Commit 18f5b477ee66 adds two arguments to VOP_ALLOCATE().
41 Normally changes to VOP calls are not MFC'd, but a
42 discussion on freebsd-current@ seemed to agree that
43 it was acceptable in this case, to fix the NFSv4.2 server.
44 Any out of source tree file system with a custom
45 VOP_ALLOCATE() call will need to be modified.
46 Bump __FreeBSD_version to 1300523 since the NFS modules need
47 to be rebuilt from sources.
50 Commit 6e8e261f0d4e changed the internal KAPI between the NFS
51 modules. As such, all the modules must be rebuilt from sources.
52 __FreeBSD_version has been bumped to 1300522.
55 Bump __FreeBSD_version to 1300521 after merging LinuxKPI and
56 net80211 changes in order to support building various wireless
57 drivers. This is to help other external consumers of LinuxKPI
58 and net80211 to deal accordingly.
61 Commit a599f9f7620b deleted the variable called nfs_maxcopyrange
62 from nfscommon.ko, since it no longer needs to be global. As such,
63 the other nfs modules must be rebuilt from up to date sources.
64 Bump __FreeBSD_version to 1300516 for this.
67 As of commit 622809b0868f OpenSSL no longer enables kernel TLS
68 by default. Users can enable kernel TLS via the "KTLS" SSL
69 option. This can be enabled globally by using a custom
70 OpenSSL config file via OPENSSL_CONF or via an
71 application-specific configuration option for applications
72 which permit setting SSL options via SSL_CONF_cmd(3).
75 Commits 9fb6e613373c and 9ec7dbf46b0a both changed the internal
76 KAPI between the NFS modules. Bump __FreeBSD_version to 1300514.
77 All NFS modules must be rebuilt from sources.
80 Commit b69019c14cd8 removes pf's DIOCGETSTATESNV ioctl.
81 As of be70c7a50d32 it is no longer used by userspace, but it does mean
82 users may not be able to enumerate pf states if they update the kernel
83 past c021ff986e2b without first updating userspace past be70c7a50d32.
86 Bump __FreeBSD_version to 1300512 after merging LinuxKPI, OFED,
87 net80211, and driver changes in order to support building
88 Intel wireless iwlwifi drivers. This is especially needed for
89 drm-kmod which needs updates after this.
92 The 20210707 awk update brought in a change in behavior. This has
93 been corrected as of d4d252c49976. Between these dates, if you
94 installed a new awk binary, you may not be able to build a new
95 kernel because the change in behavior affected the genoffset
96 script used to build the kernel. If you did update, the fix is
97 to update your sources past the above hash and do
100 % sudo -E make install
101 to enable building kernels again.
104 Commit 8a04edfdcbd2 changes the default minor version
105 used for NFSv4 mounts to the highest minor version supported
106 by the NFSv4 server. This default can be overridden by using
107 the "minorversion" mount option.
108 The consensus of a discussion on freebsd-current@ indicated
109 that this would be acceptable to do and would not be considered
113 awk has been updated to the latest one-true-awk version 20210215.
114 This contains a number of minor bug fixes.
117 Commit ca179c4d74f2/632e3f2f3a66 changed the package in which
118 the OpenSSL libraries and utilities are packaged.
119 It is recommended for pkgbase user to do:
120 pkg install -f FreeBSD-openssl
121 before pkg upgrade otherwise some dependencies might not be met
122 and pkg will stop working as libssl will not be present anymore
126 Commit 841006678745 changed the internal KAPI between the krpc
127 and nfsd modules. As such, they must both be rebuilt from
129 __FreeBSD_version is bumped to 1300510.
132 Commit 272f39942254 changed the internal KAPI between the
133 nscl.ko and nfscommon.ko modules, so they both need to be
134 rebuilt from sources.
137 Commit 5a45802b3c8c changed the internal KAPI between
138 the krpc and NFS. As such, the krpc, nfscommon and
139 nfscl modules must all be rebuilt from sources.
140 Without this patch, NFSv4.1/4.2 mounts should not
141 be done with the nfscbd(8) daemon running, to avoid
142 needing a working back channel for server->client RPCs.
145 Various LinuxKPI functionality was added which conflicts with DRM.
146 Please update your drm-kmod port to after the __FreeBSD_verison 1300139
150 The stable/13 branch has been created from main.
153 PC Card attachments for all devices have been removed. In the case of
154 wi and cmx, the entire drivers were removed because they were only
155 PC Card devices. FreeBSD_version 1300134 should be used for this
156 since it was bumped so recently.
159 Transport-independent parts of HID support have been split off the USB
160 code in to separate subsystem. Kernel configs which include one of
161 ums, ukbd, uhid, atp, wsp, wmt, uaudio, ugold or ucycom drivers should
162 be updated with adding of "device hid" line.
165 ncurses installation has been modified to only keep the widechar
166 enabled version. Incremental build is broken for that change, so it
167 requires a clean build.
170 The FreeBSD project has migrated from Subversion to Git. Temporary
171 instructions can be found at
172 https://github.com/bsdimp/freebsd-git-docs/blob/main/src-cvt.md
173 and other documents in that repo.
176 The services database has been updated to cover more of the basic
177 services expected in a modern system. The database is big enough
178 that it will cause issues in mergemaster in Releases previous to
179 12.2 and 11.3, or in very old current systems from before r358154.
182 Obsolete in-tree GDB 6.1.1 has been removed. GDB (including kgdb)
183 may be installed from ports or packages.
186 ping6 has been merged into ping. It can now be called as "ping -6".
187 See ping(8) for details.
190 Default value of net.add_addr_allfibs has been changed to 0.
191 If you have multi-fib configuration and rely on existence of all
192 interface routes in every fib, you need to set the above sysctl to 1.
194 The internal pre-processor in the calendar(1) program has been
195 extended to support more C pre-processor commands (e.g. #ifdef, #else,
196 and #undef) and to detect unbalanced conditional statements.
197 Error messages have been extended to include the filename and line
198 number if processing stops to help fixing malformed data files.
201 All the data files for the calendar(1) program, except calendar.freebsd,
202 have been moved to the deskutils/calendar-data port, much like the
203 jewish calendar entries were moved to deskutils/hebcal years ago. After
204 make delete-old-files, you need to install it to retain full
205 functionality. calendar(1) will issue a reminder for files it can't
209 LINT files are no longer generated. We now include the relevant NOTES
210 files. Note: This may cause conflicts with updating in some cases.
211 find sys -name LINT\* -delete
212 is suggested across this commit to remove the generated LINT files.
214 If you have tried to update with generated files there, the svn
215 command you want to un-auger the tree is
218 and then do the above find from the top level. Substitute 'amd64'
219 above with where the error message indicates a conflict.
222 OpenZFS support has been integrated. Do not upgrade root pools until
223 the loader is updated to support zstd. Furthermore, we caution against
224 'zpool upgrade' for the next few weeks. The change should be transparent
225 unless you want to use new features.
227 Not all "NO_CLEAN" build scenarios work across these changes. Many
228 scenarios have been tested and fixed, but rebuilding kernels without
229 rebuilding world may fail.
231 The ZFS cache file has moved from /boot to /etc to match the OpenZFS
232 upstream default. A fallback to /boot has been added for mountroot.
234 Pool auto import behavior at boot has been moved from the kernel module
235 to an explicit "zpool import -a" in one of the rc scripts enabled by
236 zfs_enable=YES. This means your non-root zpools won't auto import until
237 you upgrade your /etc/rc.d files.
240 The resume code now notifies devd with the 'kernel' system
241 rather than the old 'kern' subsystem to be consistent with
242 other use. The old notification will be created as well, but
243 will be removed prior to FreeBSD 14.0.
246 r362275 changed the internal API between the kernel RPC and the
247 NFS modules. As such, all the modules must be recompiled from
251 r364330 modified the internal API used between the NFS modules.
252 As such, all the NFS modules must be re-compiled from sources.
255 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
256 been upgraded to 11.0.0. Please see the 20141231 entry below for
257 information about prerequisites and upgrading, if you are not already
258 using clang 3.5.0 or higher.
261 r364092 modified the internal ABI used between the kernel NFS
262 modules. As such, all of these modules need to be rebuilt
263 from sources, so a version bump was done.
266 Makefile.inc has been updated to work around the issue documented in
267 20200729. It was a case where the optimization of using symbolic links
268 to point to binaries created a situation where we'd run new binaries
269 with old libraries starting midway through the installworld process.
272 r363679 has redefined some undefined behavior in regcomp(3); notably,
273 extraneous escapes of most ordinary characters will no longer be
274 accepted. An exp-run has identified all of the problems with this in
275 ports, but other non-ports software may need extra escapes removed to
276 continue to function.
278 Because of this change, installworld may encounter the following error
279 from rtld: Undefined symbol "regcomp@FBSD_1.6" -- It is imperative that
280 you do not halt installworld. Instead, let it run to completion (whether
281 successful or not) and run installworld once more.
284 A new implementation of bc and dc has been imported in r362681. This
285 implementation corrects non-conformant behavior of the previous bc
286 and adds GNU bc compatible options. It offers a number of extensions,
287 is much faster on large values, and has support for message catalogs
288 (a number of languages are already supported, contributions of further
289 languages welcome). The option WITHOUT_GH_BC can be used to build the
290 world with the previous versions of bc and dc.
293 r362639 changed the internal API used between the NFS kernel modules.
294 As such, they all need to be rebuilt from sources.
297 r362158 changed the arguments for VFS_CHECKEXP(). As such, any
298 out of tree file systems need to be modified and rebuilt.
299 Also, any file systems that are modules must be rebuilt.
302 read(2) of a directory fd is now rejected by default. root may
303 re-enable it for system root only on non-ZFS filesystems with the
304 security.bsd.allow_read_dir sysctl(8) MIB if
305 security.bsd.suser_enabled=1.
307 It may be advised to setup aliases for grep to default to `-d skip` if
308 commonly non-recursively grepping a list that includes directories and
309 the potential for the resulting stderr output is not tolerable. Example
310 aliases are now installed, commented out, in /root/.cshrc and
314 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
315 been upgraded to 10.0.1. Please see the 20141231 entry below for
316 information about prerequisites and upgrading, if you are not already
317 using clang 3.5.0 or higher.
320 Support for obsolete compilers has been removed from the build system.
321 Clang 6 and GCC 6.4 are the minimum supported versions.
324 closefrom(2) has been moved under COMPAT12, and replaced in libc with a
325 stub that calls close_range(2). If using a custom kernel configuration,
326 you may want to ensure that the COMPAT_FREEBSD12 option is included, as
327 a slightly older -CURRENT userland and older FreeBSD userlands may not
328 be functional without closefrom(2).
331 Upstream DTS from Linux 5.6 was merged and they now have the SID
332 and THS (Secure ID controller and THermal Sensor) node present.
333 The DTB overlays have now been removed from the tree for the H3/H5 and
334 A64 SoCs and the aw_sid and aw_thermal driver have been updated to
335 deal with upstream DTS. If you are using those overlays you need to
336 remove them from loader.conf and update the DTBs on the FAT partition.
339 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
340 been upgraded to 10.0.0. Please see the 20141231 entry below for
341 information about prerequisites and upgrading, if you are not already
342 using clang 3.5.0 or higher.
345 The amd(8) automount daemon has been removed from the source tree.
346 As of FreeBSD 10.1 autofs(5) is the preferred tool for automounting.
347 amd is still available in the sysutils/am-utils port.
350 Removed brooktree driver (bktr.4) from the tree.
353 The WITH_GPL_DTC option has been removed. The BSD-licenced device tree
354 compiler in usr.bin/dtc is used on all architectures which use dtc, and
355 the GPL dtc is available (if needed) from the sysutils/dtc port.
358 The WITHOUT_LLVM_LIBUNWIND option has been removed. LLVM's libunwind
359 is used by all supported CPU architectures.
362 GCC 4.2.1 has been removed from the tree. The WITH_GCC,
363 WITH_GCC_BOOTSTRAP, and WITH_GNUCXX options are no longer available.
364 Users who wish to build FreeBSD with GCC must use the external toolchain
368 ncurses has been updated to a newer version (6.2-20200215). Given the ABI
369 has changed, users will have to rebuild all the ports that are linked to
373 The size of struct vnet and the magic cookie have changed.
374 Users need to recompile libkvm and all modules using VIMAGE
375 together with their new kernel.
378 Defining the long deprecated NO_CTF, NO_DEBUG_FILES, NO_INSTALLLIB,
379 NO_MAN, NO_PROFILE, and NO_WARNS variables is now an error. Update
380 your Makefiles and scripts to define MK_<var>=no instead as required.
382 One exception to this is that program or library Makefiles should
383 define MAN to empty rather than setting MK_MAN=no.
386 Clang/LLVM is now the default compiler and LLD the default
390 make universe no longer uses GCC 4.2.1 on any architectures.
391 Architectures not supported by in-tree Clang/LLVM require an
392 external toolchain package.
395 GCC 4.2.1 is now not built by default, as part of the GCC 4.2.1
396 retirement plan. Specifically, the GCC, GCC_BOOTSTRAP, and GNUCXX
397 options default to off for all supported CPU architectures. As a
398 short-term transition aid they may be enabled via WITH_* options.
399 GCC 4.2.1 is expected to be removed from the tree on 2020-03-31.
402 Support for armv5 has been disconnected and is being removed. The
403 machine combination MACHINE=arm MACHINE_ARCH=arm is no longer valid.
404 You must now use a MACHINE_ARCH of armv6 or armv7. The default
405 MACHINE_ARCH for MACHINE=arm is now armv7.
408 Clang/LLVM is now the default compiler for all powerpc architectures.
409 LLD is now the default linker for powerpc64. The change for powerpc64
410 also includes a change to the ELFv2 ABI, incompatible with the existing
414 Kernel-loadable random(4) modules are no longer unloadable.
417 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
418 been upgraded to 9.0.1. Please see the 20141231 entry below for
419 information about prerequisites and upgrading, if you are not already
420 using clang 3.5.0 or higher.
423 r355677 has modified the internal interface used between the
424 NFS modules in the kernel. As such, they must all be upgraded
425 simultaneously. I will do a version bump for this.
428 The root certificates of the Mozilla CA Certificate Store have been
429 imported into the base system and can be managed with the certctl(8)
430 utility. If you have installed the security/ca_root_nss port or package
431 with the ETCSYMLINK option (the default), be advised that there may be
432 differences between those included in the port and those included in
433 base due to differences in nss branch used as well as general update
434 frequency. Note also that certctl(8) cannot manage certs in the
435 format used by the security/ca_root_nss port.
438 The amd(8) automount daemon has been disabled by default, and will be
439 removed in the future. As of FreeBSD 10.1 the autofs(5) is available
443 The nctgpio and wbwd drivers have been moved to the superio bus.
444 If you have one of these drivers in a kernel configuration, then
445 you should add device superio to it. If you use one of these drivers
446 as a module and you compile a custom set of modules, then you should
447 add superio to the set.
450 KPIs for network drivers to access interface addresses have changed.
451 Users need to recompile NIC driver modules together with kernel.
454 The net.link.tap.user_open sysctl no longer prevents user opening of
455 already created /dev/tapNN devices. Access is still controlled by
456 node permissions, just like tun devices. The net.link.tap.user_open
457 sysctl is now used only to allow users to perform devfs cloning of
458 tap devices, and the subsequent open may not succeed if the user is not
459 in the appropriate group. This sysctl may be deprecated/removed
460 completely in the future.
463 mips, powerpc, and sparc64 are no longer built as part of
464 universe / tinderbox unless MAKE_OBSOLETE_GCC is defined. If
465 not defined, mips, powerpc, and sparc64 builds will look for
466 the xtoolchain binaries and if installed use them for universe
467 builds. As llvm 9.0 becomes vetted for these architectures, they
468 will be removed from the list.
471 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
472 been upgraded to 9.0.0. Please see the 20141231 entry below for
473 information about prerequisites and upgrading, if you are not already
474 using clang 3.5.0 or higher.
477 The hpt27xx, hptmv, hptnr, and hptrr drivers have been removed from
478 GENERIC. They are available as modules and can be loaded by adding
479 to /boot/loader.conf hpt27xx_load="YES", hptmv_load="YES",
480 hptnr_load="YES", or hptrr_load="YES", respectively.
483 ntpd no longer by default locks its pages in memory, allowing them
484 to be paged out by the kernel. Use rlimit memlock to restore
485 historic BSD behaviour. For example, add "rlimit memlock 32"
486 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
489 Several of ping6's options have been renamed for better consistency
490 with ping. If you use any of -ARWXaghmrtwx, you must update your
491 scripts. See ping6(8) for details.
494 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
495 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
496 been removed from mount_fusefs(8). You can safely remove them from
497 your scripts, because they had no effect.
499 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
500 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
501 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
502 sysctls have been removed. If you felt the need to set any of them to
503 a non-default value, please tell asomers@FreeBSD.org why.
506 Default permissions on the /var/account/acct file (and copies of it
507 rotated by periodic daily scripts) are changed from 0644 to 0640
508 because the file contains sensitive information that should not be
509 world-readable. If the /var/account directory must be created by
510 rc.d/accounting, the mode used is now 0750. Admins who use the
511 accounting feature are encouraged to change the mode of an existing
512 /var/account directory to 0750 or 0700.
515 Entropy collection and the /dev/random device are no longer optional
516 components. The "device random" option has been removed.
517 Implementations of distilling algorithms can still be made loadable
518 with "options RANDOM_LOADABLE" (e.g., random_fortuna.ko).
521 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
522 been upgraded to 8.0.1. Please see the 20141231 entry below for
523 information about prerequisites and upgrading, if you are not already
524 using clang 3.5.0 or higher.
527 A fix was applied to i386 kernel modules to avoid panics with
528 dpcpu or vnet. Users need to recompile i386 kernel modules
529 having pcpu or vnet sections or they will refuse to load.
532 User-wired pages now have their own counter,
533 vm.stats.vm.v_user_wire_count. The vm.max_wired sysctl was renamed
534 to vm.max_user_wired and changed from an unsigned int to an unsigned
535 long. bhyve VMs wired with the -S are now subject to the user
536 wiring limit; the vm.max_user_wired sysctl may need to be tuned to
537 avoid running into the limit.
540 The IPSEC option has been removed from GENERIC. Users requiring
541 ipsec(4) must now load the ipsec(4) kernel module.
544 The tap(4) driver has been folded into tun(4), and the module has been
545 renamed to tuntap. You should update any kld_list="if_tap" or
546 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
547 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
548 module instead, and "device tap" or "device tun" entries in kernel
549 config files to select the tuntap device instead.
552 The following knobs have been added related to tradeoffs between
553 safe use of the random device and availability in the absence of
556 kern.random.initial_seeding.bypass_before_seeding: tunable; set
557 non-zero to bypass the random device prior to seeding, or zero to
558 block random requests until the random device is initially seeded.
559 For now, set to 1 (unsafe) by default to restore pre-r346250 boot
560 availability properties.
562 kern.random.initial_seeding.read_random_bypassed_before_seeding:
563 read-only diagnostic sysctl that is set when bypass is enabled and
564 read_random(9) is bypassed, to enable programmatic handling of this
565 initial condition, if desired.
567 kern.random.initial_seeding.arc4random_bypassed_before_seeding:
568 Similar to the above, but for arc4random(9) initial seeding.
570 kern.random.initial_seeding.disable_bypass_warnings: tunable; set
571 non-zero to disable warnings in dmesg when the same conditions are
572 met as for the diagnostic sysctls above. Defaults to zero, i.e.,
573 produce warnings in dmesg when the conditions are met.
576 The loadable random module KPI has changed; the random_infra_init()
577 routine now requires a 3rd function pointer for a bool (*)(void)
578 method that returns true if the random device is seeded (and
579 therefore unblocked).
582 r345895 reverts r320698. This implies that an nfsuserd(8) daemon
583 built from head sources between r320757 (July 6, 2017) and
584 r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
585 is added to the command line.
586 nfsuserd daemons built from head sources that are post-r338192 are
587 not affected and should continue to work.
590 The fuse(4) module has been renamed to fusefs(4) for consistency with
591 other filesystems. You should update any kld_load="fuse" entries in
592 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
593 "options FUSE" entries in kernel config files.
596 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
597 8.0.0. Please see the 20141231 entry below for information about
598 prerequisites and upgrading, if you are not already using clang 3.5.0
602 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
603 compiled into your custom kernel, add 'device xz' statement to the
607 drm and drm2 have been removed from the tree. Please see
608 https://wiki.freebsd.org/Graphics for the latest information on
609 migrating to the drm ports.
612 Iflib is no longer unconditionally compiled into the kernel. Drivers
613 using iflib and statically compiled into the kernel, now require
614 the 'device iflib' config option. For the same drivers loaded as
615 modules on kernels not having 'device iflib', the iflib.ko module
616 is loaded automatically.
619 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
620 options no longer exist since r343219 and r343427 respectively;
621 nothing uses them, so they should be just removed from custom
625 r342635 changes the way efibootmgr(8) works by requiring users to add
626 the -b (bootnum) parameter for commands where the bootnum was previously
627 specified with each option. For example 'efibootmgr -B 0001' is now
628 'efibootmgr -B -b 0001'.
631 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
632 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
633 servers that have vfs.nfsd.nfs_privport set will only allow mounts
634 from clients using a reserved port#. Since both the FreeBSD and Linux
635 NFSv4 clients use reserved port#s by default, this should not affect
639 The XLP config has been removed. We can't support 64-bit atomics in this
640 kernel because it is running in 32-bit mode. XLP users must transition
641 to running a 64-bit kernel (XLP64 or XLPN32).
643 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
644 the preferred emulator today and we don't need two different ones.
646 The old sibyte / swarm / Broadcom BCM1250 support has been
647 removed from the mips port.
650 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
651 7.0.1. Please see the 20141231 entry below for information about
652 prerequisites and upgrading, if you are not already using clang 3.5.0
656 Remove the timed and netdate programs from the base tree. Setting
657 the time with these daemons has been obsolete for over a decade.
660 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
661 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
662 it produces broken binaries when ifuncs are in use. Users needing
663 GNU ld should install the binutils port or package.
666 The BSD crtbegin and crtend code has been enabled by default. It has
667 had extensive testing on amd64, arm64, and i386. It can be disabled
668 by building a world with -DWITHOUT_BSD_CRTBEGIN.
671 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
672 has been converted to a port (misc/ctm) and will be removed from
673 FreeBSD-13. It is available as a package (ctm) for all supported
677 The default newsyslog.conf(5) file has been changed to only include
678 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
679 the filenames end in '.conf' and do not begin with a '.'.
681 You should check the configuration files in these two directories match
682 this naming convention. You can verify which configuration files are
683 being included using the command:
687 Ports for the DRM modules have been simplified. Now, amd64 users should
688 just install the drm-kmod port. All others should install
691 Graphics hardware that's newer than about 2010 usually works with
692 drm-kmod. For hardware older than 2013, however, some users will need
693 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
694 than 2008 usually only works in drm-legacy-kmod. The graphics team can
695 only commit to hardware made since 2013 due to the complexity of the
696 market and difficulty to test all the older cards effectively. If you
697 have hardware supported by drm-kmod, you are strongly encouraged to use
698 that as you will get better support.
700 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
701 elsewhere, the drm and drm2 modules will be eliminated from the src base
702 soon (with a limited exception for arm). Please update to the package
703 asap and report any issues to x11@freebsd.org.
705 Generally, anybody using the drm*-kmod packages should add
706 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
707 cross-threading surprises, especially with automatic driver
708 loading from X11 startup. These will become the defaults in 13-current
712 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
713 custom kernel and module loading configuration files must be updated
714 accordingly. Moreover, interfaces previous presented as ixlvN to the
715 system are now exposed as iavfN and network configuration files must
716 be adjusted as necessary.
719 OpenSSL has been updated to version 1.1.1. This update included
720 additional various API changes throughout the base system. It is
721 important to rebuild third-party software after upgrading. The value
722 of __FreeBSD_version has been bumped accordingly.
725 The legacy DRM modules and drivers have now been added to the loader's
726 module blacklist, in favor of loading them with kld_list in rc.conf(5).
727 The module blacklist may be overridden with the loader.conf(5)
728 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
732 The cam(4) based nda(4) driver will be used over nvd(4) by default on
733 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
734 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
735 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
739 Reproducible build mode is now on by default, in preparation for
740 FreeBSD 12.0. This eliminates build metadata such as the user,
741 host, and time from the kernel (and uname), unless the working tree
742 corresponds to a modified checkout from a version control system.
743 The previous behavior can be obtained by setting the /etc/src.conf
744 knob WITHOUT_REPRODUCIBLE_BUILD.
747 The Yarrow CSPRNG has been removed from the kernel as it has not been
748 supported by its designers since at least 2003. Fortuna has been the
749 default since FreeBSD-11.
752 devctl freeze/thaw have gone into the tree, the rc scripts have been
753 updated to use them and devmatch has been changed. You should update
754 kernel, userland and rc scripts all at the same time.
757 The default interpreter has been switched from 4th to Lua.
758 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
759 interpreter. If you have custom FORTH code you will need to set
760 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
761 src.conf for the build. This will create default hard links between
762 loader and loader_4th instead of loader and loader_lua, the new default.
763 If you are using UEFI it will create the proper hard link to loader.efi.
765 bhyve uses userboot.so. It remains 4th-only until some issues are solved
766 regarding coexisting with multiple versions of FreeBSD are resolved.
769 ls(1) now respects the COLORTERM environment variable used in other
770 systems and software to indicate that a colored terminal is both
771 supported and desired. If ls(1) is suddenly emitting colors, they may
772 be disabled again by either removing the unwanted COLORTERM from your
773 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
774 may not be observed in a future release.
777 The default pager for most commands has been changed to "less". To
778 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
782 The jedec_ts(4) driver has been removed. A superset of its functionality
783 is available in the jedec_dimm(4) driver, and the manpage for that
784 driver includes migration instructions. If you have "device jedec_ts"
785 in your kernel configuration file, it must be removed.
788 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
789 This should have no effect if the kernel is booted via BIOS/legacy boot.
790 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
791 has a buggy firmware that prevents a successful boot due to use of
795 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
796 support has been removed from the tree. These ports were
797 obsolete and/or known to be broken for many years.
800 loader.efi has been augmented to participate more fully in the
801 UEFI boot manager protocol. loader.efi will now look at the
802 BootXXXX environment variable to determine if a specific kernel
803 or root partition was specified. XXXX is derived from BootCurrent.
804 efibootmgr(8) manages these standard UEFI variables.
807 zfsloader's functionality has now been folded into loader.
808 zfsloader is no longer necessary once you've updated your
809 boot blocks. For a transition period, we will install a
810 hardlink for zfsloader to loader to allow a smooth transition
811 until the boot blocks can be updated (hard link because old
812 zfs boot blocks don't understand symlinks).
815 ARM64 now have efifb support, if you want to have serial console
816 on your arm64 board when an screen is connected and the bootloader
817 setup a frame buffer for us to use, just add :
821 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
822 an screen connected as the firmware will setup a frame buffer are that
823 u-boot will expose as an EFI frame buffer.
826 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
827 or take steps to update /etc/passwd before doing installworld on
828 existing systems. Do not skip the "mergemaster -Fp" step before
829 installworld, as described in the update procedures near the bottom
830 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
831 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
832 the ntp config file contain options that change file/dir locations.
833 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
834 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
835 taking steps to ensure that all required files/dirs are accessible
839 Big endian arm support has been removed.
842 The static environment setup in kernel configs is no longer mutually
843 exclusive with the loader(8) environment by default. In order to
844 restore the previous default behavior of disabling the loader(8)
845 environment if a static environment is present, you must specify
846 loader_env.disabled=1 in the static environment.
849 The ABI of syscalls used by management tools like sockstat and
850 netstat has been broken to allow 32-bit binaries to work on
851 64-bit kernels without modification. These programs will need
852 to match the kernel in order to function. External programs may
853 require minor modifications to accommodate a change of type in
854 structures from pointers to 64-bit virtual addresses.
857 On i386 and amd64 atomics are now inlined. Out of tree modules using
858 atomics will need to be rebuilt.
861 The '%I' format in the kern.corefile sysctl limits the number of
862 core files that a process can generate to the number stored in the
863 debug.ncores sysctl. The '%I' format is replaced by the single digit
864 index. Previously, if all indexes were taken the kernel would overwrite
865 only a core file with the highest index in a filename.
866 Currently the system will create a new core file if there is a free
867 index or if all slots are taken it will overwrite the oldest one.
870 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
871 6.0.1. Please see the 20141231 entry below for information about
872 prerequisites and upgrading, if you are not already using clang 3.5.0
876 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
877 needed to be changed to work with it. This change was made with r335763
878 and requires a mergemaster / etcupdate / etc to update the installed
882 r334930 changed the interface between the NFS modules, so they all
883 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
886 As of r334391 lld is the default amd64 system linker; it is installed
887 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
891 The kernel / userland interface for devinfo changed, so you'll
892 need a new kernel and userland as a pair for it to work (rebuilding
893 lib/libdevinfo is all that's required). devinfo and devmatch will
894 not work, but everything else will when there's a mismatch.
897 The on-disk format for hwpmc callchain records has changed to include
898 threadid corresponding to a given record. This changes the field offsets
899 and thus requires that libpmcstat be rebuilt before using a kernel
903 The vxge(4) driver has been removed. This driver was introduced into
904 HEAD one week before the Exar left the Ethernet market and is not
905 known to be used. If you have device vxge in your kernel config file
909 The amd64 kernel now requires a ld that supports ifunc to produce a
910 working kernel, either lld or a newer binutils. lld is built by default
911 on amd64, and the 'buildkernel' target uses it automatically. However,
912 it is not the default linker, so building the kernel the traditional
913 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
914 binutils port/package). lld will soon be default, and this requirement
917 NOTE: As of r334391 lld is the default system linker on amd64, and no
918 workaround is necessary.
921 The nxge(4) driver has been removed. This driver was for PCI-X 10g
922 cards made by s2io/Neterion. The company was acquired by Exar and
923 no longer sells or supports Ethernet products. If you have device
924 nxge in your kernel config file it must be removed.
927 The tz database (tzdb) has been updated to 2018e. This version more
928 correctly models time stamps in time zones with negative DST such as
929 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
930 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
931 time zone abbreviations and the tm_isdst flag.
934 The ixgb(4) driver has been removed. This driver was for an early and
935 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
936 quickly shifted to the long lived ixgbe family. If you have device
937 ixgb in your kernel config file it must be removed.
940 The lmc(4) driver has been removed. This was a WAN interface
941 card that was already reportedly rare in 2003, and had an ambiguous
942 license. If you have device lmc in your kernel config file it must
946 Support for Arcnet networks has been removed. If you have device
947 arcnet or device cm in your kernel config file they must be
951 Support for FDDI networks has been removed. If you have device
952 fddi or device fpa in your kernel config file they must be
956 In addition to supporting RFC 3164 formatted messages, the
957 syslogd(8) service is now capable of parsing RFC 5424 formatted
958 log messages. The main benefit of using RFC 5424 is that clients
959 may now send log messages with timestamps containing year numbers,
960 microseconds and time zone offsets.
962 Similarly, the syslog(3) C library function has been altered to
963 send RFC 5424 formatted messages to the local system logging
964 daemon. On systems using syslogd(8), this change should have no
965 negative impact, as long as syslogd(8) and the C library are
966 updated at the same time. On systems using a different system
967 logging daemon, it may be necessary to make configuration
968 adjustments, depending on the software used.
970 When using syslog-ng, add the 'syslog-protocol' flag to local
971 input sources to enable parsing of RFC 5424 formatted messages:
974 unix-dgram("/var/run/log" flags(syslog-protocol));
977 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
978 of the 'imuxsock' module to let messages be processed by the
979 regular RFC 3164/5424 parsing pipeline:
981 module(load="imuxsock" SysSock.UseSpecialParser="off")
983 Do note that these changes only affect communication between local
984 applications and syslogd(8). The format that syslogd(8) uses to
985 store messages on disk or forward messages to other systems
986 remains unchanged. syslogd(8) still uses RFC 3164 for these
987 purposes. Options to customize this behaviour will be added in the
988 future. Utilities that process log files stored in /var/log are
989 thus expected to continue to function as before.
991 __FreeBSD_version has been incremented to 1200061 to denote this
995 Support for token ring networks has been removed. If you
996 have "device token" in your kernel config you should remove
997 it. No device drivers supported token ring.
1000 makefs was modified to be able to tag ISO9660 El Torito boot catalog
1001 entries as EFI instead of overloading the i386 tag as done previously.
1002 The amd64 mkisoimages.sh script used to build amd64 ISO images for
1003 release was updated to use this. This may mean that makefs must be
1004 updated before "make cdrom" can be run in the release directory. This
1005 should be as simple as:
1007 $ cd $SRCDIR/usr.sbin/makefs
1008 $ make depend all install
1011 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
1012 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
1013 Co-existence for the transition period will come shortly. Booting is a
1014 complex environment and test coverage for Lua-enabled loaders has been
1015 thin, so it would be prudent to assume it might not work and make
1016 provisions for backup boot methods.
1019 devmatch functionality has been turned on in devd. It will automatically
1020 load drivers for unattached devices. This may cause unexpected drivers
1021 to be loaded. Please report any problems to current@ and
1025 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
1026 6.0.0. Please see the 20141231 entry below for information about
1027 prerequisites and upgrading, if you are not already using clang 3.5.0
1031 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
1032 This means it is used to link the kernel and userland libraries and
1033 executables, but is not yet installed as /usr/bin/ld by default.
1035 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
1036 WITHOUT_LLD_BOOTSTRAP=yes
1039 On i386, pmtimer has been removed. Its functionality has been folded
1040 into apm. It was a no-op on ACPI in current for a while now (but was
1041 still needed on i386 in FreeBSD 11 and earlier). Users may need to
1042 remove it from kernel config files.
1045 The use of RSS hash from the network card aka flowid has been
1046 disabled by default for lagg(4) as it's currently incompatible with
1047 the lacp and loadbalance protocols.
1049 This can be re-enabled by setting the following in loader.conf:
1050 net.link.lagg.default_use_flowid="1"
1053 The SW_WATCHDOG option is no longer necessary to enable the
1054 hardclock-based software watchdog if no hardware watchdog is
1055 configured. As before, SW_WATCHDOG will cause the software
1056 watchdog to be enabled even if a hardware watchdog is configured.
1059 r326887 fixes the issue described in the 20171214 UPDATING entry.
1060 r326888 flips the switch back to building GELI support always.
1063 r362593 broke ZFS + GELI support for reasons unknown. However,
1064 it also broke ZFS support generally, so GELI has been turned off
1065 by default as the lesser evil in r326857. If you boot off ZFS and/or
1066 GELI, it might not be a good time to update.
1069 PowerPC users must update loader(8) by rebuilding world before
1070 installing a new kernel, as the protocol connecting them has
1071 changed. Without the update, loader metadata will not be passed
1072 successfully to the kernel and users will have to enter their
1073 root partition at the kernel mountroot prompt to continue booting.
1074 Newer versions of loader can boot old kernels without issue.
1077 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
1078 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
1079 to WITH/OUT_LOADER_GELI.
1082 The naive and non-compliant support of posix_fallocate(2) in ZFS
1083 has been removed as of r325320. The system call now returns EINVAL
1084 when used on a ZFS file. Although the new behavior complies with the
1085 standard, some consumers are not prepared to cope with it.
1086 One known victim is lld prior to r325420.
1089 Building in a FreeBSD src checkout will automatically create object
1090 directories now rather than store files in the current directory if
1091 'make obj' was not ran. Calling 'make obj' is no longer necessary.
1092 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
1093 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
1097 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
1098 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
1099 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
1100 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
1101 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
1102 The UNIFIED_OBJDIR option is a transitional feature that will be
1103 removed for 12.0 release; please migrate to the new format for any
1104 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
1105 than hardcoding paths.
1108 The native-xtools target no longer installs the files by default to the
1109 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
1110 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
1113 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
1114 options are changing from controlling the build if defined / undefined
1115 to controlling the build with explicit 'yes' or 'no' values. They will
1116 shift to WITH/WITHOUT options to match other options in the system.
1119 libstand has turned into a private library for sys/boot use only.
1120 It is no longer supported as a public interface outside of sys/boot.
1123 The arm port has split armv6 into armv6 and armv7. armv7 is now
1124 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
1125 and are running a kernel from before r324363, you will need to add
1126 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
1129 When building multiple kernels using KERNCONF, non-existent KERNCONF
1130 files will produce an error and buildkernel will fail. Previously
1131 missing KERNCONF files silently failed giving no indication as to
1132 why, only to subsequently discover during installkernel that the
1133 desired kernel was never built in the first place.
1136 The default serial number format for CTL LUNs has changed. This will
1137 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
1138 or iSCSI clients care about their LUNs' serial numbers. Users who
1139 require serial number stability should hardcode serial numbers in
1143 For 32-bit arm compiled for hard-float support, soft-floating point
1144 binaries now always get their shared libraries from
1145 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
1146 /usr/libsoft also existed). Only users with a hard-float ld.so, but
1147 soft-float everything else should be affected.
1150 The geli password typed at boot is now hidden. To restore the previous
1151 behavior, see geli(8) for configuration options.
1154 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
1155 sysctl values. Minor nit, but requires a rebuild of both world/kernel
1159 "make check" behavior (made in ^/head@r295380) has been changed to
1160 execute from a limited sandbox, as opposed to executing from
1164 - The "beforecheck" and "aftercheck" targets are now specified.
1165 - ${CHECKDIR} (added in commit noted above) has been removed.
1166 - Legacy behavior can be enabled by setting
1167 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
1169 If the limited sandbox mode is enabled, "make check" will execute
1170 "make distribution", then install, execute the tests, and clean up the
1171 sandbox if successful.
1173 The "make distribution" and "make install" targets are typically run as
1174 root to set appropriate permissions and ownership at installation time.
1175 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
1176 environment if executing "make check" with limited sandbox mode using
1177 an unprivileged user.
1180 Since the switch to GPT disk labels, fsck for UFS/FFS has been
1181 unable to automatically find alternate superblocks. As of r322297,
1182 the information needed to find alternate superblocks has been
1183 moved to the end of the area reserved for the boot block.
1184 Filesystems created with a newfs of this vintage or later
1185 will create the recovery information. If you have a filesystem
1186 created prior to this change and wish to have a recovery block
1187 created for your filesystem, you can do so by running fsck in
1188 foreground mode (i.e., do not use the -p or -y options). As it
1189 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
1190 to which you should answer yes.
1193 As of r321665, an NFSv4 server configuration that services
1194 Kerberos mounts or clients that do not support the uid/gid in
1195 owner/owner_group string capability, must explicitly enable
1196 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
1197 machine's /etc/rc.conf file.
1200 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
1201 Please see the 20141231 entry below for information about prerequisites
1202 and upgrading, if you are not already using clang 3.5.0 or higher.
1205 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
1206 r-commands (rlogin, rsh, etc.) to be built with the base system.
1209 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
1210 a very major ABI incompatible change, so users of FreeBSD/powerpc must
1211 be careful when performing source upgrades. It is best to run
1212 'make installworld' from an alternate root system, either a live
1213 CD/memory stick, or a temporary root partition. Additionally, all ports
1214 must be recompiled. powerpc64 is largely unaffected, except in the case
1215 of 32-bit compatibility. All 32-bit binaries will be affected.
1218 Forward compatibility for the "ino64" project have been committed. This
1219 will allow most new binaries to run on older kernels in a limited
1220 fashion. This prevents many of the common foot-shooting actions in the
1221 upgrade as well as the limited ability to roll back the kernel across
1222 the ino64 upgrade. Complicated use cases may not work properly, though
1223 enough simpler ones work to allow recovery in most situations.
1226 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
1227 if you require the GPL compiler.
1230 The internal ABI used for communication between the NFS kernel modules
1231 was changed by r320085, so __FreeBSD_version was bumped to
1232 ensure all the NFS related modules are updated together.
1235 The ABI of struct event was changed by extending the data
1236 member to 64bit and adding ext fields. For upgrade, same
1237 precautions as for the entry 20170523 "ino64" must be
1241 The GNU roff toolchain has been removed from base. To render manpages
1242 which are not supported by mandoc(1), man(1) can fallback on GNU roff
1243 from ports (and recommends to install it).
1244 To render roff(7) documents, consider using GNU roff from ports or the
1245 heirloom doctools roff toolchain from ports via pkg install groff or
1246 via pkg install heirloom-doctools.
1249 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
1250 smaller runtime footprint builds. This is useful for embedded systems
1251 which only require one chipset support.
1253 If you load it as a module, make sure this is in /boot/loader.conf:
1257 This will load the HAL, all chip/RF backends and if_ath_pci.
1258 If you have if_ath_pci in /boot/loader.conf, ensure it is after
1259 if_ath or it will not load any HAL chipset support.
1261 If you want to selectively load things (eg on ye cheape ARM/MIPS
1262 platforms where RAM is at a premium) you should:
1265 * load the chip modules in question
1266 * load ath_rate, ath_dfs
1268 * load if_ath_pci and/or if_ath_ahb depending upon your particular
1269 bus bind type - this is where probe/attach is done.
1271 For further comments/feedback, poke adrian@ .
1274 The "ino64" 64-bit inode project has been committed, which extends
1275 a number of types to 64 bits. Upgrading in place requires care and
1276 adherence to the documented upgrade procedure.
1278 If using a custom kernel configuration ensure that the
1279 COMPAT_FREEBSD11 option is included (as during the upgrade the
1280 system will be running the ino64 kernel with the existing world).
1282 For the safest in-place upgrade begin by removing previous build
1283 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full
1284 procedure documented below under the heading "To rebuild everything and
1285 install it on the current system." Specifically, a reboot is required
1286 after installing the new kernel before installing world. While an
1287 installworld normally works by accident from multiuser after rebooting
1288 the proper kernel, there are many cases where this will fail across this
1289 upgrade and installworld from single user is required.
1292 The NATM framework including the en(4), fatm(4), hatm(4), and
1293 patm(4) devices has been removed. Consumers should plan a
1294 migration before the end-of-life date for FreeBSD 11.
1297 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
1298 diff has not been implemented, if those are needed a newer version of
1299 GNU diff is available via the diffutils package under the gdiff name.
1302 As of r316810 for ipfilter, keep frags is no longer assumed when
1303 keep state is specified in a rule. r316810 aligns ipfilter with
1304 documentation in man pages separating keep frags from keep state.
1305 This allows keep state to be specified without forcing keep frags
1306 and allows keep frags to be specified independently of keep state.
1307 To maintain previous behaviour, also specify keep frags with
1308 keep state (as documented in ipf.conf.5).
1311 arm64 builds now use the base system LLD 4.0.0 linker by default,
1312 instead of requiring that the aarch64-binutils port or package be
1313 installed. To continue using aarch64-binutils, set
1314 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
1317 The UDP optimization in entry 20160818 that added the sysctl
1318 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
1319 packets will no longer be treated as L3 broadcast packets.
1322 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
1323 use any explicitly assigned loopback address available in the jail
1324 instead of using the first assigned address of the jail.
1327 The ctl.ko module no longer implements the iSCSI target frontend:
1328 cfiscsi.ko does instead.
1330 If building cfiscsi.ko as a kernel module, the module can be loaded
1331 via one of the following methods:
1332 - `cfiscsi_load="YES"` in loader.conf(5).
1333 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
1334 - ctladm(8)/ctld(8), when compiled with iSCSI support
1335 (`WITH_ISCSI=yes` in src.conf(5))
1337 Please see cfiscsi(4) for more details.
1340 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
1341 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
1342 same source (previously, the dependency of mmcsd.ko on mmc.ko was
1343 missing, but mmcsd.ko now will refuse to load if it is incompatible
1347 The syntax of ipfw(8) named states was changed to avoid ambiguity.
1348 If you have used named states in the firewall rules, you need to modify
1349 them after installworld and before rebooting. Now named states must
1350 be prefixed with colon.
1353 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
1354 removed as the userland we provide cannot use them. The KMS version
1355 (sys/dev/drm2) supports the same hardware.
1358 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
1359 Please see the 20141231 entry below for information about prerequisites
1360 and upgrading, if you are not already using clang 3.5.0 or higher.
1363 The code that provides support for ZFS .zfs/ directory functionality
1364 has been reimplemented. It's not possible now to create a snapshot
1365 by mkdir under .zfs/snapshot/. That should be the only user visible
1369 EISA bus support has been removed. The WITH_EISA option is no longer
1373 MCA bus support has been removed.
1376 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
1377 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
1380 The EM_MULTIQUEUE kernel configuration option is deprecated now that
1381 the em(4) driver conforms to iflib specifications.
1384 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
1385 IFLIB. If you have a custom kernel configuration that excludes em(4)
1386 but you use igb(4), you need to re-add em(4) to your custom
1390 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
1391 Please see the 20141231 entry below for information about prerequisites
1392 and upgrading, if you are not already using clang 3.5.0 or higher.
1395 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
1396 Please see the 20141231 entry below for information about prerequisites
1397 and upgrading, if you are not already using clang 3.5.0 or higher.
1400 The layout of the pmap structure has changed for powerpc to put the pmap
1401 statistics at the front for all CPU variations. libkvm(3) and all tools
1402 that link against it need to be recompiled.
1405 isl(4) and cyapa(4) drivers now require a new driver,
1406 chromebook_platform(4), to work properly on Chromebook-class hardware.
1407 On other types of hardware the drivers may need to be configured using
1408 device hints. Please see the corresponding manual pages for details.
1411 The urtwn(4) driver was merged into rtwn(4) and now consists of
1412 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
1414 Also, firmware for RTL8188CE was renamed due to possible name
1415 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
1418 GNU rcs has been removed from base. It is available as packages:
1419 - rcs: Latest GPLv3 GNU rcs version.
1420 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
1424 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
1425 modules now requires that the kernel configuration contain the
1426 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
1429 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
1430 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
1433 Relocatable object files with the extension of .So have been renamed
1434 to use an extension of .pico instead. The purpose of this change is
1435 to avoid a name clash with shared libraries on case-insensitive file
1436 systems. On those file systems, foo.So is the same file as foo.so.
1439 GNU rcs has been turned off by default. It can (temporarily) be built
1440 again by adding WITH_RCS knob in src.conf.
1441 Otherwise, GNU rcs is available from packages:
1442 - rcs: Latest GPLv3 GNU rcs version.
1443 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
1446 The backup_uses_rcs functionality has been removed from rc.subr.
1449 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
1450 two separate components, QUEUE_MACRO_DEBUG_TRACE and
1451 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
1452 QUEUE_MACRO_DEBUG behavior.
1455 r304787 changed some ioctl interfaces between the iSCSI userspace
1456 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1457 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1461 The UDP receive code has been updated to only treat incoming UDP
1462 packets that were addressed to an L2 broadcast address as L3
1463 broadcast packets. It is not expected that this will affect any
1464 standards-conforming UDP application. The new behaviour can be
1465 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1469 Remove the openbsd_poll system call.
1470 __FreeBSD_version has been bumped because of this.
1473 The stable/11 branch has been created from head@r302406.
1476 The libc stub for the pipe(2) system call has been replaced with
1477 a wrapper that calls the pipe2(2) system call and the pipe(2)
1478 system call is now only implemented by the kernels that include
1479 "options COMPAT_FREEBSD10" in their config file (this is the
1480 default). Users should ensure that this option is enabled in
1481 their kernel or upgrade userspace to r302092 before upgrading their
1485 CAM will now strip leading spaces from SCSI disks' serial numbers.
1486 This will affect users who create UFS filesystems on SCSI disks using
1487 those disk's diskid device nodes. For example, if /etc/fstab
1488 previously contained a line like
1489 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
1490 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
1491 transforms like gmirror may also be affected. ZFS users should
1495 The bitstring(3) API has been updated with new functionality and
1496 improved performance. But it is binary-incompatible with the old API.
1497 Objects built with the new headers may not be linked against objects
1498 built with the old headers.
1501 The brk and sbrk functions have been removed from libc on arm64.
1502 Binutils from ports has been updated to not link to these
1503 functions and should be updated to the latest version before
1504 installing a new libc.
1507 The armv6 port now defaults to hard float ABI. Limited support
1508 for running both hardfloat and soft float on the same system
1509 is available using the libraries installed with -DWITH_LIBSOFT.
1510 This has only been tested as an upgrade path for installworld
1511 and packages may fail or need manual intervention to run. New
1512 packages will be needed.
1514 To update an existing self-hosted armv6hf system, you must add
1515 TARGET_ARCH=armv6 on the make command line for both the build
1516 and the install steps.
1519 Kernel modules compiled outside of a kernel build now default to
1520 installing to /boot/modules instead of /boot/kernel. Many kernel
1521 modules built this way (such as those in ports) already overrode
1522 KMODDIR explicitly to install into /boot/modules. However,
1523 manually building and installing a module from /sys/modules will
1524 now install to /boot/modules instead of /boot/kernel.
1527 The CAM I/O scheduler has been committed to the kernel. There should be
1528 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1529 list of known rogues that claim support for this but actually corrupt
1530 data is believed to be complete, be on the lookout for data
1531 corruption. The known rogue list is believed to be complete:
1533 o Crucial MX100, M550 drives with MU01 firmware.
1534 o Micron M510 and M550 drives with MU01 firmware.
1535 o Micron M500 prior to MU07 firmware
1536 o Samsung 830, 840, and 850 all firmwares
1537 o FCCT M500 all firmwares
1539 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1540 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1541 updated firmware. Black listed drives will work correctly because these
1542 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1543 this list is the same as found in Linux, it's believed there are no
1544 other rogues in the market place. All other models from the above
1547 To be safe, if you are at all concerned, you can quirk each of your
1548 drives to prevent NCQ from being sent by setting:
1549 kern.cam.ada.X.quirks="0x2"
1550 in loader.conf. If the drive requires the 4k sector quirk, set the
1551 quirks entry to 0x3.
1554 The FAST_DEPEND build option has been removed and its functionality is
1555 now the one true way. The old mkdep(1) style of 'make depend' has
1556 been removed. See 20160311 for further details.
1559 Resource range types have grown from unsigned long to uintmax_t. All
1560 drivers, and anything using libdevinfo, need to be recompiled.
1563 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1564 builds. It no longer runs mkdep(1) during 'make depend', and the
1565 'make depend' stage can safely be skipped now as it is auto ran
1566 when building 'make all' and will generate all SRCS and DPSRCS before
1567 building anything else. Dependencies are gathered at compile time with
1568 -MF flags kept in separate .depend files per object file. Users should
1569 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1570 stale .depend files.
1573 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1574 kernel modules. Therefore, if you load any kernel modules at boot time,
1575 please install the boot loaders after you install the kernel, but before
1579 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1580 make installkernel KERNCONF=YOUR_KERNEL_HERE
1581 make -C sys/boot install
1582 <reboot in single user>
1584 Then follow the usual steps, described in the General Notes section,
1588 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1589 see the 20141231 entry below for information about prerequisites and
1590 upgrading, if you are not already using clang 3.5.0 or higher.
1593 The AIO subsystem is now a standard part of the kernel. The
1594 VFS_AIO kernel option and aio.ko kernel module have been removed.
1595 Due to stability concerns, asynchronous I/O requests are only
1596 permitted on sockets and raw disks by default. To enable
1597 asynchronous I/O requests on all file types, set the
1598 vfs.aio.enable_unsafe sysctl to a non-zero value.
1601 The ELF object manipulation tool objcopy is now provided by the
1602 ELF Tool Chain project rather than by GNU binutils. It should be a
1603 drop-in replacement, with the addition of arm64 support. The
1604 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1605 to obtain the GNU version if necessary.
1608 Building ZFS pools on top of zvols is prohibited by default. That
1609 feature has never worked safely; it's always been prone to deadlocks.
1610 Using a zvol as the backing store for a VM guest's virtual disk will
1611 still work, even if the guest is using ZFS. Legacy behavior can be
1612 restored by setting vfs.zfs.vol.recursive=1.
1615 The NONE and HPN patches has been removed from OpenSSH. They are
1616 still available in the security/openssh-portable port.
1619 With the addition of ypldap(8), a new _ypldap user is now required
1620 during installworld. "mergemaster -p" can be used to add the user
1621 prior to installworld, as documented in the handbook.
1624 The tftp loader (pxeboot) now uses the option root-path directive. As a
1625 consequence it no longer looks for a pxeboot.4th file on the tftp
1626 server. Instead it uses the regular /boot infrastructure as with the
1630 The code to start recording plug and play data into the modules has
1631 been committed. While the old tools will properly build a new kernel,
1632 a number of warnings about "unknown metadata record 4" will be produced
1633 for an older kldxref. To avoid such warnings, make sure to rebuild
1634 the kernel toolchain (or world). Make sure that you have r292078 or
1635 later when trying to build 292077 or later before rebuilding.
1638 Debug data files are now built by default with 'make buildworld' and
1639 installed with 'make installworld'. This facilitates debugging but
1640 requires more disk space both during the build and for the installed
1641 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1645 r291527 changed the internal interface between the nfsd.ko and
1646 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1647 __FreeBSD_version has been bumped because of this.
1650 Add support for unicode collation strings leads to a change of
1651 order of files listed by ls(1) for example. To get back to the old
1652 behaviour, set LC_COLLATE environment variable to "C".
1654 Databases administrators will need to reindex their databases given
1655 collation results will be different.
1657 Due to a bug in install(1) it is recommended to remove the ancient
1658 locales before running make installworld.
1660 rm -rf /usr/share/locale/*
1663 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1664 libcrypto.so.7 or libssl.so.7 must be recompiled.
1667 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1668 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1669 should be replaced with isp_2400 and isp_2500 modules respectively.
1672 The build previously allowed using 'make -n' to not recurse into
1673 sub-directories while showing what commands would be executed, and
1674 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1675 and 'make -N' will not.
1678 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1679 and etcupdate will now use this file. A custom sendmail.cf is now
1680 updated via this mechanism rather than via installworld. If you had
1681 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1682 want to remove the exclusion or change it to "always install".
1683 /etc/mail/sendmail.cf is now managed the same way regardless of
1684 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1685 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1688 Compatibility shims for legacy ATA device names have been removed.
1689 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1690 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1691 environment variables, /dev/ad* and /dev/ar* symbolic links.
1694 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1695 Please see the 20141231 entry below for information about prerequisites
1696 and upgrading, if you are not already using clang 3.5.0 or higher.
1699 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1700 and renamed from .symbols to .debug. This reduces the size requirements
1701 on the boot partition or file system and provides consistency with
1702 userland debug files.
1704 When using the supported kernel installation method the
1705 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1706 as is done with /boot/kernel.
1708 Developers wishing to maintain the historical behavior of installing
1709 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1712 The wireless drivers had undergone changes that remove the 'parent
1713 interface' from the ifconfig -l output. The rc.d network scripts
1714 used to check presence of a parent interface in the list, so old
1715 scripts would fail to start wireless networking. Thus, etcupdate(3)
1716 or mergemaster(8) run is required after kernel update, to update your
1717 rc.d scripts in /etc.
1720 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1721 These configurations are now automatically interpreted as
1722 'scrub fragment reassemble'.
1725 Kernel-loadable modules for the random(4) device are back. To use
1726 them, the kernel must have
1729 options RANDOM_LOADABLE
1731 kldload(8) can then be used to load random_fortuna.ko
1732 or random_yarrow.ko. Please note that due to the indirect
1733 function calls that the loadable modules need to provide,
1734 the build-in variants will be slightly more efficient.
1736 The random(4) kernel option RANDOM_DUMMY has been retired due to
1737 unpopularity. It was not all that useful anyway.
1740 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1741 Control over building the ELF Tool Chain tools is now provided by
1742 the WITHOUT_TOOLCHAIN knob.
1745 The polarity of Pulse Per Second (PPS) capture events with the
1746 uart(4) driver has been corrected. Prior to this change the PPS
1747 "assert" event corresponded to the trailing edge of a positive PPS
1748 pulse and the "clear" event was the leading edge of the next pulse.
1750 As the width of a PPS pulse in a typical GPS receiver is on the
1751 order of 1 millisecond, most users will not notice any significant
1752 difference with this change.
1754 Anyone who has compensated for the historical polarity reversal by
1755 configuring a negative offset equal to the pulse width will need to
1756 remove that workaround.
1759 The default group assigned to /dev/dri entries has been changed
1760 from 'wheel' to 'video' with the id of '44'. If you want to have
1761 access to the dri devices please add yourself to the video group
1764 # pw groupmod video -m $USER
1767 The menu.rc and loader.rc files will now be replaced during
1768 upgrades. Please migrate local changes to menu.rc.local and
1769 loader.rc.local instead.
1772 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1773 strings and strip have been removed. The src.conf(5) knob
1774 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1777 As ZFS requires more kernel stack pages than is the default on some
1778 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1779 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1781 Please consider using 'options KSTACK_PAGES=X' where X is greater
1782 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1785 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1786 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1787 default, i.e., they will not contain "::". For example, instead
1788 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1789 to have a more specific match, such as different map entries for
1790 IPv6:0:0 vs IPv6:0. This change requires that configuration
1791 data (including maps, files, classes, custom ruleset, etc.) must
1792 use the same format, so make certain such configuration data is
1793 upgrading. As a very simple check search for patterns like
1794 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1795 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1796 the cf option UseCompressedIPv6Addresses.
1799 The default kernel entropy-processing algorithm is now
1800 Fortuna, replacing Yarrow.
1802 Assuming you have 'device random' in your kernel config
1803 file, the configurations allow a kernel option to override
1804 this default. You may choose *ONE* of:
1806 options RANDOM_YARROW # Legacy /dev/random algorithm.
1807 options RANDOM_DUMMY # Blocking-only driver.
1809 If you have neither, you get Fortuna. For most people,
1810 read no further, Fortuna will give a /dev/random that works
1811 like it always used to, and the difference will be irrelevant.
1813 If you remove 'device random', you get *NO* kernel-processed
1814 entropy at all. This may be acceptable to folks building
1815 embedded systems, but has complications. Carry on reading,
1816 and it is assumed you know what you need.
1818 *PLEASE* read random(4) and random(9) if you are in the
1819 habit of tweaking kernel configs, and/or if you are a member
1820 of the embedded community, wanting specific and not-usual
1821 behaviour from your security subsystems.
1823 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1824 random', you will NOT have a functioning /dev/random, and
1825 many cryptographic features will not work, including SSH.
1826 You may also find strange behaviour from the random(3) set
1827 of library functions, in particular sranddev(3), srandomdev(3)
1828 and arc4random(3). The reason for this is that the KERN_ARND
1829 sysctl only returns entropy if it thinks it has some to
1830 share, and with RANDOM_DUMMY or no 'device random' this
1834 An additional fix for the issue described in the 20150614 sendmail
1835 entry below has been committed in revision 284717.
1838 FreeBSD's old make (fmake) has been removed from the system. It is
1839 available as the devel/fmake port or via pkg install fmake.
1842 The fix for the issue described in the 20150614 sendmail entry
1843 below has been committed in revision 284436. The work
1844 around described in that entry is no longer needed unless the
1845 default setting is overridden by a confDH_PARAMETERS configuration
1846 setting of '5' or pointing to a 512 bit DH parameter file.
1849 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1850 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1851 and devel/kyua to version 0.20+ and adjust any calling code to work
1852 with Kyuafile and kyua.
1855 The import of openssl to address the FreeBSD-SA-15:10.openssl
1856 security advisory includes a change which rejects handshakes
1857 with DH parameters below 768 bits. sendmail releases prior
1858 to 8.15.2 (not yet released), defaulted to a 512 bit
1859 DH parameter setting for client connections. To work around
1860 this interoperability, sendmail can be configured to use a
1861 2048 bit DH parameter by:
1863 1. Edit /etc/mail/`hostname`.mc
1864 2. If a setting for confDH_PARAMETERS does not exist or
1865 exists and is set to a string beginning with '5',
1866 replace it with '2'.
1867 3. If a setting for confDH_PARAMETERS exists and is set to
1868 a file path, create a new file with:
1869 openssl dhparam -out /path/to/file 2048
1870 4. Rebuild the .cf file:
1871 cd /etc/mail/; make; make install
1872 5. Restart sendmail:
1873 cd /etc/mail/; make restart
1875 A sendmail patch is coming, at which time this file will be
1879 Generation of legacy formatted entries have been disabled by default
1880 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1881 entries were converted to use the new format by default when the new,
1882 machine independent format have been added and supported since FreeBSD
1885 Please see the pwd_mkdb(8) manual page for further details.
1888 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1889 20141231 entry below for information about prerequisites and upgrading,
1890 if you are not already using 3.5.0 or higher.
1893 TI platform code switched to using vendor DTS files and this update
1894 may break existing systems running on Beaglebone, Beaglebone Black,
1897 - dtb files should be regenerated/reinstalled. Filenames are the
1898 same but content is different now
1899 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1900 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1901 addressing scheme is now pin 25 on /dev/gpioc3.
1902 - Pandaboard: /etc/ttys should be updated, serial console device is
1903 now /dev/ttyu2, not /dev/ttyu0
1906 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1907 If you need the GNU extension from groff soelim(1), install groff
1908 from package: pkg install groff, or via ports: textproc/groff.
1911 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1912 defined in symlink(7); previously symlinks were silently ignored.
1915 The const qualifier has been removed from iconv(3) to comply with
1916 POSIX. The ports tree is aware of this from r384038 onwards.
1919 Libraries specified by LIBADD in Makefiles must have a corresponding
1920 DPADD_<lib> variable to ensure correct dependencies. This is now
1921 enforced in src.libnames.mk.
1924 From legacy ata(4) driver was removed support for SATA controllers
1925 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1926 Kernel modules ataahci and ataadaptec were removed completely,
1927 replaced by ahci and mvs modules respectively.
1930 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1931 the 20141231 entry below for information about prerequisites and
1932 upgrading, if you are not already using 3.5.0 or higher.
1935 The 32-bit PowerPC kernel has been changed to a position-independent
1936 executable. This can only be booted with a version of loader(8)
1937 newer than January 31, 2015, so make sure to update both world and
1938 kernel before rebooting.
1941 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1942 but before r278950, the RNG was not seeded properly. Immediately
1943 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1944 ssh keys or openssl keys) that were generated w/ a kernel from that
1945 range. This does not affect programs that directly used /dev/random
1946 or /dev/urandom. All userland uses of arc4random(3) are affected.
1949 The autofs(4) ABI was changed in order to restore binary compatibility
1950 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1951 with the new kernel.
1954 The powerpc64 kernel has been changed to a position-independent
1955 executable. This can only be booted with a new version of loader(8),
1956 so make sure to update both world and kernel before rebooting.
1959 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1960 only release, no new features have been added. Please see the 20141231
1961 entry below for information about prerequisites and upgrading, if you
1962 are not already using 3.5.0.
1965 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1966 taken from the ELF Tool Chain project rather than GNU binutils. They
1967 should be drop-in replacements, with the addition of arm64 support.
1968 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1969 binutils tools, if necessary. See 20150805 for updated information.
1972 The default Unbound configuration now enables remote control
1973 using a local socket. Users who have already enabled the
1974 local_unbound service should regenerate their configuration
1975 by running "service local_unbound setup" as root.
1978 The GNU texinfo and GNU info pages have been removed.
1979 To be able to view GNU info pages please install texinfo from ports.
1982 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1984 As of this release, a prerequisite for building clang, llvm and lldb is
1985 a C++11 capable compiler and C++11 standard library. This means that to
1986 be able to successfully build the cross-tools stage of buildworld, with
1987 clang as the bootstrap compiler, your system compiler or cross compiler
1988 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1989 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1992 On any standard FreeBSD 10.x or 11.x installation, where clang and
1993 libc++ are on by default (that is, on x86 or arm), this should work out
1996 On 9.x installations where clang is enabled by default, e.g. on x86 and
1997 powerpc, libc++ will not be enabled by default, so libc++ should be
1998 built (with clang) and installed first. If both clang and libc++ are
1999 missing, build clang first, then use it to build libc++.
2001 On 8.x and earlier installations, upgrade to 9.x first, and then follow
2002 the instructions for 9.x above.
2004 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
2005 default, and do not build clang.
2007 Many embedded systems are resource constrained, and will not be able to
2008 build clang in a reasonable time, or in some cases at all. In those
2009 cases, cross building bootable systems on amd64 is a workaround.
2011 This new version of clang introduces a number of new warnings, of which
2012 the following are most likely to appear:
2016 This warns in two cases, for both C and C++:
2017 * When the code is trying to take the absolute value of an unsigned
2018 quantity, which is effectively a no-op, and almost never what was
2019 intended. The code should be fixed, if at all possible. If you are
2020 sure that the unsigned quantity can be safely cast to signed, without
2021 loss of information or undefined behavior, you can add an explicit
2022 cast, or disable the warning.
2024 * When the code is trying to take an absolute value, but the called
2025 abs() variant is for the wrong type, which can lead to truncation.
2026 If you want to disable the warning instead of fixing the code, please
2027 make sure that truncation will not occur, or it might lead to unwanted
2030 -Wtautological-undefined-compare and
2031 -Wundefined-bool-conversion
2033 These warn when C++ code is trying to compare 'this' against NULL, while
2034 'this' should never be NULL in well-defined C++ code. However, there is
2035 some legacy (pre C++11) code out there, which actively abuses this
2036 feature, which was less strictly defined in previous C++ versions.
2038 Squid and openjdk do this, for example. The warning can be turned off
2039 for C++98 and earlier, but compiling the code in C++11 mode might result
2040 in unexpected behavior; for example, the parts of the program that are
2041 unreachable could be optimized away.
2044 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
2045 kernel sources have been removed. The .h files remain, since some
2046 utilities include them. This will need to be fixed later.
2047 If "mount -t oldnfs ..." is attempted, it will fail.
2048 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
2049 the utilities will report errors.
2052 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
2053 directories to top level SUBDIR variable when their parent
2054 directory is included in LOCAL_DIRS. Users with build systems with
2055 such hierarchies and without SUBDIR entries in the parent
2056 directory Makefiles should add them or add the directories to
2060 faith(4) and faithd(8) have been removed from the base system. Faith
2061 has been obsolete for a very long time.
2064 vt(4), the new console driver, is enabled by default. It brings
2065 support for Unicode and double-width characters, as well as
2066 support for UEFI and integration with the KMS kernel video
2069 You may need to update your console settings in /etc/rc.conf,
2070 most probably the keymap. During boot, /etc/rc.d/syscons will
2071 indicate what you need to do.
2073 vt(4) still has issues and lacks some features compared to
2074 syscons(4). See the wiki for up-to-date information:
2075 https://wiki.freebsd.org/Newcons
2077 If you want to keep using syscons(4), you can do so by adding
2078 the following line to /boot/loader.conf:
2082 pjdfstest has been integrated into kyua as an opt-in test suite.
2083 Please see share/doc/pjdfstest/README for more details on how to
2087 gperf has been removed from the base system for architectures
2088 that use clang. Ports that require gperf will obtain it from the
2092 pjdfstest has been moved from tools/regression/pjdfstest to
2096 At svn r271982, The default linux compat kernel ABI has been adjusted
2097 to 2.6.18 in support of the linux-c6 compat ports infrastructure
2098 update. If you wish to continue using the linux-f10 compat ports,
2099 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
2100 encouraged to update their linux-compat packages to linux-c6 during
2101 their next update cycle.
2104 The ofwfb driver, used to provide a graphics console on PowerPC when
2105 using vt(4), no longer allows mmap() of all physical memory. This
2106 will prevent Xorg on PowerPC with some ATI graphics cards from
2107 initializing properly unless x11-servers/xorg-server is updated to
2111 The xdev targets have been converted to using TARGET and
2112 TARGET_ARCH instead of XDEV and XDEV_ARCH.
2115 The default unbound configuration has been modified to address
2116 issues with reverse lookups on networks that use private
2117 address ranges. If you use the local_unbound service, run
2118 "service local_unbound setup" as root to regenerate your
2119 configuration, then "service local_unbound reload" to load the
2123 The GNU texinfo and GNU info pages are not built and installed
2124 anymore, WITH_INFO knob has been added to allow to built and install
2126 UPDATE: see 20150102 entry on texinfo's removal
2129 The GNU readline library is now an INTERNALLIB - that is, it is
2130 statically linked into consumers (GDB and variants) in the base
2131 system, and the shared library is no longer installed. The
2132 devel/readline port is available for third party software that
2136 The Itanium architecture (ia64) has been removed from the list of
2137 known architectures. This is the first step in the removal of the
2141 Commit r268115 has added NFSv4.1 server support, merged from
2142 projects/nfsv4.1-server. Since this includes changes to the
2143 internal interfaces between the NFS related modules, a full
2144 build of the kernel and modules will be necessary.
2145 __FreeBSD_version has been bumped.
2148 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
2149 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
2150 which differs from the behaviour controlled by this knob.)
2153 Maximal length of the serial number in CTL was increased from 16 to
2154 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
2155 and ctld, need to be rebuilt to work with a new kernel.
2158 The libatf-c and libatf-c++ major versions were downgraded to 0 and
2159 1 respectively to match the upstream numbers. They were out of
2160 sync because, when they were originally added to FreeBSD, the
2161 upstream versions were not respected. These libraries are private
2162 and not yet built by default, so renumbering them should be a
2163 non-issue. However, unclean source trees will yield broken test
2164 programs once the operator executes "make delete-old-libs" after a
2165 "make installworld".
2167 Additionally, the atf-sh binary was made private by moving it into
2168 /usr/libexec/. Already-built shell test programs will keep the
2169 path to the old binary so they will break after "make delete-old"
2172 If you are using WITH_TESTS=yes (not the default), wipe the object
2173 tree and rebuild from scratch to prevent spurious test failures.
2174 This is only needed once: the misnumbered libraries and misplaced
2175 binaries have been added to OptionalObsoleteFiles.inc so they will
2176 be removed during a clean upgrade.
2179 Clang and llvm have been upgraded to 3.4.1 release.
2182 We bogusly installed src.opts.mk in /usr/share/mk. This file should
2183 be removed to avoid issues in the future (and has been added to
2187 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
2188 past, it affected all builds that used the bsd.*.mk files. The old
2189 behavior was a bug, but people may have relied upon it. To get this
2190 behavior back, you can .include /etc/src.conf from /etc/make.conf
2191 (which is still global and isn't changed). This also changes the
2192 behavior of incremental builds inside the tree of individual
2193 directories. Set MAKESYSPATH to ".../share/mk" to do that.
2194 Although this has survived make universe and some upgrade scenarios,
2195 other upgrade scenarios may have broken. At least one form of
2196 temporary breakage was fixed with MAKESYSPATH settings for buildworld
2197 as well... In cases where MAKESYSPATH isn't working with this
2198 setting, you'll need to set it to the full path to your tree.
2200 One side effect of all this cleaning up is that bsd.compiler.mk
2201 is no longer implicitly included by bsd.own.mk. If you wish to
2202 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
2206 The lindev device has been removed since /dev/full has been made a
2207 standard device. __FreeBSD_version has been bumped.
2210 The knob WITHOUT_VI was added to the base system, which controls
2211 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
2212 in order to reorder files share/termcap and didn't build ex(1) as a
2213 build tool, so building/installing with WITH_VI is highly advised for
2214 build hosts for older releases.
2216 This issue has been fixed in stable/9 and stable/10 in r277022 and
2217 r276991, respectively.
2220 The YES_HESIOD knob has been removed. It has been obsolete for
2221 a decade. Please move to using WITH_HESIOD instead or your builds
2222 will silently lack HESIOD.
2225 The uart(4) driver has been changed with respect to its handling
2226 of the low-level console. Previously the uart(4) driver prevented
2227 any process from changing the baudrate or the CLOCAL and HUPCL
2228 control flags. By removing the restrictions, operators can make
2229 changes to the serial console port without having to reboot.
2230 However, when getty(8) is started on the serial device that is
2231 associated with the low-level console, a misconfigured terminal
2232 line in /etc/ttys will now have a real impact.
2233 Before upgrading the kernel, make sure that /etc/ttys has the
2234 serial console device configured as 3wire without baudrate to
2235 preserve the previous behaviour. E.g:
2236 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
2239 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
2240 to improve performance. To re-enable it, if needed, run rpcbind
2241 with command line option -W.
2244 Switched back to the GPL dtc compiler due to updates in the upstream
2245 dts files not being supported by the BSDL dtc compiler. You will need
2246 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
2247 may result while building dtb files during a kernel build if you fail
2248 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
2251 Clang and llvm have been upgraded to 3.4 release.
2254 The nve(4) driver has been removed. Please use the nfe(4) driver
2255 for NVIDIA nForce MCP Ethernet adapters instead.
2258 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
2259 This could cause certain C++ applications using shared libraries built
2260 against the previous version of libc++ to crash. The incompatibility
2261 has now been fixed, but any C++ applications or shared libraries built
2262 between r261283 and r261801 should be recompiled.
2265 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
2266 capability mode support. Please note that enabling the feature in
2267 kernel is still highly recommended.
2270 OpenSSH is now built with sandbox support, and will use sandbox as
2271 the default privilege separation method. This requires Capsicum
2272 capability mode support in kernel.
2275 The libelf and libdwarf libraries have been updated to newer
2276 versions from upstream. Shared library version numbers for
2277 these two libraries were bumped. Any ports or binaries
2278 requiring these two libraries should be recompiled.
2279 __FreeBSD_version is bumped to 1100006.
2282 If a Makefile in a tests/ directory was auto-generating a Kyuafile
2283 instead of providing an explicit one, this would prevent such
2284 Makefile from providing its own Kyuafile in the future during
2285 NO_CLEAN builds. This has been fixed in the Makefiles but manual
2286 intervention is needed to clean an objdir if you use NO_CLEAN:
2287 # find /usr/obj -name Kyuafile | xargs rm -f
2290 The behavior of gss_pseudo_random() for the krb5 mechanism
2291 has changed, for applications requesting a longer random string
2292 than produced by the underlying enctype's pseudo-random() function.
2293 In particular, the random string produced from a session key of
2294 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
2295 be different at the 17th octet and later, after this change.
2296 The counter used in the PRF+ construction is now encoded as a
2297 big-endian integer in accordance with RFC 4402.
2298 __FreeBSD_version is bumped to 1100004.
2301 The WITHOUT_ATF build knob has been removed and its functionality
2302 has been subsumed into the more generic WITHOUT_TESTS. If you were
2303 using the former to disable the build of the ATF libraries, you
2304 should change your settings to use the latter.
2307 The default version of mtree is nmtree which is obtained from
2308 NetBSD. The output is generally the same, but may vary
2309 slightly. If you found you need identical output adding
2310 "-F freebsd9" to the command line should do the trick. For the
2311 time being, the old mtree is available as fmtree.
2314 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
2315 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
2316 1.1.4_8 and verify bsdyml not linked in, before running "make
2318 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
2320 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
2323 The stable/10 branch has been created in subversion from head
2330 Sometimes, obscure build problems are the result of environment
2331 poisoning. This can happen because the make utility reads its
2332 environment when searching for values for global variables. To run
2333 your build attempts in an "environmental clean room", prefix all make
2334 commands with 'env -i '. See the env(1) manual page for more details.
2335 Occasionally a build failure will occur with "make -j" due to a race
2336 condition. If this happens try building again without -j, and please
2337 report a bug if it happens consistently.
2339 When upgrading from one major version to another it is generally best to
2340 upgrade to the latest code in the currently installed branch first, then
2341 do an upgrade to the new branch. This is the best-tested upgrade path,
2342 and has the highest probability of being successful. Please try this
2343 approach if you encounter problems with a major version upgrade. Since
2344 the stable 4.x branch point, one has generally been able to upgrade from
2345 anywhere in the most recent stable branch to head / current (or even the
2346 last couple of stable branches). See the top of this file when there's
2349 The update process will emit an error on an attempt to perform a build
2350 or install from a FreeBSD version below the earliest supported version.
2351 When updating from an older version the update should be performed one
2352 major release at a time, including running `make delete-old` at each
2355 When upgrading a live system, having a root shell around before
2356 installing anything can help undo problems. Not having a root shell
2357 around can lead to problems if pam has changed too much from your
2358 starting point to allow continued authentication after the upgrade.
2360 This file should be read as a log of events. When a later event changes
2361 information of a prior event, the prior event should not be deleted.
2362 Instead, a pointer to the entry with the new information should be
2363 placed in the old entry. Readers of this file should also sanity check
2364 older entries before relying on them blindly. Authors of new entries
2365 should write them with this in mind.
2369 When upgrading the boot ZFS pool to a new version, always follow
2372 1.) recompile and reinstall the ZFS boot loader and boot block
2373 (this is part of "make buildworld" and "make installworld")
2375 2.) update the ZFS boot block on your boot drive
2377 The following example updates the ZFS boot block on the
2378 freebsd-boot partition of a GPT partitioned drive ada0:
2379 "gpart bootcode -p /boot/gptzfsboot -i $N ada0"
2380 The value $N will typically be 1 (if booting from BIOS) or 2 (if
2383 Non-boot pools do not need these updates.
2387 If you are updating from a prior version of FreeBSD (even one just
2388 a few days old), you should follow this procedure. It is the most
2389 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2391 make kernel-toolchain
2392 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2393 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2395 To test a kernel once
2396 ---------------------
2397 If you just want to boot a kernel once (because you are not sure
2398 if it works, or if you want to boot a known bad kernel to provide
2399 debugging information) run
2400 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2401 nextboot -k testkernel
2403 To rebuild everything and install it on the current system.
2404 -----------------------------------------------------------
2405 # Note: sometimes if you are running current you gotta do more than
2406 # is listed here if you are upgrading from a really old current.
2408 <make sure you have good level 0 dumps>
2410 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2411 make installkernel KERNCONF=YOUR_KERNEL_HERE
2413 <reboot in single user> [3]
2420 To cross-install current onto a separate partition
2421 --------------------------------------------------
2422 # In this approach we use a separate partition to hold
2423 # current's root, 'usr', and 'var' directories. A partition
2424 # holding "/", "/usr" and "/var" should be about 2GB in
2427 <make sure you have good level 0 dumps>
2430 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2431 <maybe newfs current's root partition>
2432 <mount current's root partition on directory ${CURRENT_ROOT}>
2433 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
2434 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2435 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2436 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2437 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2438 <reboot into current>
2439 <do a "native" rebuild/install as described in the previous section>
2440 <maybe install compatibility libraries from ports/misc/compat*>
2444 To upgrade in-place from stable to current
2445 ----------------------------------------------
2446 <make sure you have good level 0 dumps>
2448 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
2449 make installkernel KERNCONF=YOUR_KERNEL_HERE
2451 <reboot in single user> [3]
2458 Make sure that you've read the UPDATING file to understand the
2459 tweaks to various things you need. At this point in the life
2460 cycle of current, things change often and you are on your own
2461 to cope. The defaults can also change, so please read ALL of
2462 the UPDATING entries.
2464 Also, if you are tracking -current, you must be subscribed to
2465 freebsd-current@freebsd.org. Make sure that before you update
2466 your sources that you have read and understood all the recent
2467 messages there. If in doubt, please track -stable which has
2468 much fewer pitfalls.
2470 [1] If you have third party modules, such as vmware, you should disable
2471 them at this point so they don't crash your system on
2472 reboot. Alternatively, you should rebuild all the modules you have in
2473 your system and install them as well. If you are running -current, you
2474 should seriously consider placing all sources to all the modules for
2475 your system (or symlinks to them) in /usr/local/sys/modules so this
2476 happens automatically. If all your modules come from ports, then adding
2477 the port origin directories to PORTS_MODULES instead is also automatic
2479 PORTS_MODULES+=x11/nvidia-driver
2481 [3] From the bootblocks, boot -s, and then do
2485 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed
2486 cd src # full path to source
2487 adjkerntz -i # if CMOS is wall time
2488 Also, when doing a major release upgrade, it is required that you boot
2489 into single user mode to do the installworld.
2491 [4] Note: This step is non-optional. Failure to do this step
2492 can result in a significant reduction in the functionality of the
2493 system. Attempting to do it by hand is not recommended and those
2494 that pursue this avenue should read this file carefully, as well
2495 as the archives of freebsd-current and freebsd-hackers mailing lists
2496 for potential gotchas. The -U option is also useful to consider.
2497 See mergemaster(8) for more information.
2499 [5] Usually this step is a no-op. However, from time to time
2500 you may need to do this if you get unknown user in the following
2501 step. It never hurts to do it all the time. You may need to
2502 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2503 install) after the buildworld before this step if you last updated
2504 from current before 20130425 or from -stable before 20130430.
2506 [6] This only deletes old files and directories. Old libraries
2507 can be deleted by "make delete-old-libs", but you have to make
2508 sure that no program is using those libraries anymore.
2510 [8] The new kernel must be able to run existing binaries used by an
2511 installworld. When upgrading across major versions, the new kernel's
2512 configuration must include the correct COMPAT_FREEBSD<n> option for
2513 existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure
2514 to do so may leave you with a system that is hard to boot to recover. A
2515 GENERIC kernel will include suitable compatibility options to run
2516 binaries from older branches. Note that the ability to run binaries
2517 from unsupported branches is not guaranteed.
2519 Make sure that you merge any new devices from GENERIC since the
2520 last time you updated your kernel config file. Options also
2521 change over time, so you may need to adjust your custom kernels
2524 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2525 "?=" instead of the "=" assignment operator, so that buildworld can
2526 override the CPUTYPE if it needs to.
2528 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2529 not on the command line, or in /etc/make.conf. buildworld will
2530 warn if it is improperly defined.
2533 This file contains a list, in reverse chronological order, of major
2534 breakages in tracking -current. It is not guaranteed to be a complete
2535 list of such breakages, and only contains entries since September 23, 2011.
2536 If you need to see UPDATING entries from before that date, you will need
2537 to fetch an UPDATING file from an older FreeBSD release.
2539 Copyright information:
2541 Copyright 1998-2009 M. Warner Losh <imp@FreeBSD.org>
2543 Redistribution, publication, translation and use, with or without
2544 modification, in full or in part, in any form or format of this
2545 document are permitted without further permission from the author.
2547 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2548 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2549 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2550 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2551 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2552 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2553 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2554 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2555 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2556 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2557 POSSIBILITY OF SUCH DAMAGE.
2559 Contact Warner Losh if you have any questions about your use of