1 Updating Information for FreeBSD stable/13 users.
3 This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>.
4 See end of file for further details. For commonly done items, please see the
5 COMMON ITEMS: section later in the file. These instructions assume that you
6 basically know what you are doing. If not, then please consult the FreeBSD
9 https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
11 Items affecting the ports and packages system can be found in
12 /usr/ports/UPDATING. Please read that file before updating system packages
16 13.1-RELEASE-p3 FreeBSD-EN-22:21.zfs
17 FreeBSD-EN-22:22.tzdata
22 FreeBSD-EN-22:27.loader
24 ZFS B-Tree use-after-free [EN-22:21.zfs]
26 Timezone database information update [EN-22:22.tzdata]
28 Memory pages become unreclaimable [EN-22:23.vm]
30 ZFS snapshot directories not accessible over NFS [EN-22:24.zfs]
32 Possible data corruption with TCP SACK retransmissions [EN-22:25.tcp]
34 CAM ioctl(2) compatibility breakage [EN-22:26.cam]
36 UEFI loader failing to boot older amd64 kernels [EN-22:27.loader]
39 13.1-RELEASE-p2 FreeBSD-SA-22:13.zlib
40 FreeBSD-EN-22:20.tzdata
42 zlib heap buffer overflow [SA-22:13.zlib]
44 Timezone database information update [EN-22:20.tzdata]
47 13.1-RELEASE-p1 FreeBSD-SA-22:09.elf
49 FreeBSD-SA-22:12.lib9p
50 FreeBSD-EN-22:16.kqueue
52 FreeBSD-EN-22:19.pam_exec
54 Out of bounds read in elf_not_prpsinfo() [SA-22:09.elf]
56 Memory disclosure by stale virtual memory mapping [SA-22:11.vm]
58 Missing bounds check in 9p message handling [SA-22:12.lib9p]
60 kevent(2) timers fire too often [EN-22:16.kqueue]
62 Kernel memory corruption during SCSI error recovery [EN-22:17.cam]
64 NULL pointer dereference in pam_exec(8) [EN-22:19.pam_exec]
70 For 64-bit architectures the base system is now built with Position
71 Independent Executable (PIE) support enabled by default. It may be
72 disabled using the WITHOUT_PIE knob. A clean build is required.
75 The macros provided for the manipulation of CPU sets (e.g. CPU_AND)
76 have been modified to take 2 source arguments instead of only 1.
77 Externally maintained sources that use these macros will have to
78 be adapted. The FreeBSD version has been bumped to 1300524 to
82 Commit 18f5b477ee66 adds two arguments to VOP_ALLOCATE().
83 Normally changes to VOP calls are not MFC'd, but a
84 discussion on freebsd-current@ seemed to agree that
85 it was acceptable in this case, to fix the NFSv4.2 server.
86 Any out of source tree file system with a custom
87 VOP_ALLOCATE() call will need to be modified.
88 Bump __FreeBSD_version to 1300523 since the NFS modules need
89 to be rebuilt from sources.
92 Commit 6e8e261f0d4e changed the internal KAPI between the NFS
93 modules. As such, all the modules must be rebuilt from sources.
94 __FreeBSD_version has been bumped to 1300522.
97 Bump __FreeBSD_version to 1300521 after merging LinuxKPI and
98 net80211 changes in order to support building various wireless
99 drivers. This is to help other external consumers of LinuxKPI
100 and net80211 to deal accordingly.
103 Commit a599f9f7620b deleted the variable called nfs_maxcopyrange
104 from nfscommon.ko, since it no longer needs to be global. As such,
105 the other nfs modules must be rebuilt from up to date sources.
106 Bump __FreeBSD_version to 1300516 for this.
109 As of commit 622809b0868f OpenSSL no longer enables kernel TLS
110 by default. Users can enable kernel TLS via the "KTLS" SSL
111 option. This can be enabled globally by using a custom
112 OpenSSL config file via OPENSSL_CONF or via an
113 application-specific configuration option for applications
114 which permit setting SSL options via SSL_CONF_cmd(3).
117 Commits 9fb6e613373c and 9ec7dbf46b0a both changed the internal
118 KAPI between the NFS modules. Bump __FreeBSD_version to 1300514.
119 All NFS modules must be rebuilt from sources.
122 Commit b69019c14cd8 removes pf's DIOCGETSTATESNV ioctl.
123 As of be70c7a50d32 it is no longer used by userspace, but it does mean
124 users may not be able to enumerate pf states if they update the kernel
125 past c021ff986e2b without first updating userspace past be70c7a50d32.
128 Bump __FreeBSD_version to 1300512 after merging LinuxKPI, OFED,
129 net80211, and driver changes in order to support building
130 Intel wireless iwlwifi drivers. This is especially needed for
131 drm-kmod which needs updates after this.
134 The 20210707 awk update brought in a change in behavior. This has
135 been corrected as of d4d252c49976. Between these dates, if you
136 installed a new awk binary, you may not be able to build a new
137 kernel because the change in behavior affected the genoffset
138 script used to build the kernel. If you did update, the fix is
139 to update your sources past the above hash and do
142 % sudo -E make install
143 to enable building kernels again.
146 Commit 8a04edfdcbd2 changes the default minor version
147 used for NFSv4 mounts to the highest minor version supported
148 by the NFSv4 server. This default can be overridden by using
149 the "minorversion" mount option.
150 The consensus of a discussion on freebsd-current@ indicated
151 that this would be acceptable to do and would not be considered
155 awk has been updated to the latest one-true-awk version 20210215.
156 This contains a number of minor bug fixes.
159 Commit ca179c4d74f2/632e3f2f3a66 changed the package in which
160 the OpenSSL libraries and utilities are packaged.
161 It is recommended for pkgbase user to do:
162 pkg install -f FreeBSD-openssl
163 before pkg upgrade otherwise some dependencies might not be met
164 and pkg will stop working as libssl will not be present anymore
168 Commit 841006678745 changed the internal KAPI between the krpc
169 and nfsd modules. As such, they must both be rebuilt from
171 __FreeBSD_version is bumped to 1300510.
174 Commit 272f39942254 changed the internal KAPI between the
175 nscl.ko and nfscommon.ko modules, so they both need to be
176 rebuilt from sources.
179 Commit 5a45802b3c8c changed the internal KAPI between
180 the krpc and NFS. As such, the krpc, nfscommon and
181 nfscl modules must all be rebuilt from sources.
182 Without this patch, NFSv4.1/4.2 mounts should not
183 be done with the nfscbd(8) daemon running, to avoid
184 needing a working back channel for server->client RPCs.
187 Various LinuxKPI functionality was added which conflicts with DRM.
188 Please update your drm-kmod port to after the __FreeBSD_verison 1300139
192 The stable/13 branch has been created from main.
195 PC Card attachments for all devices have been removed. In the case of
196 wi and cmx, the entire drivers were removed because they were only
197 PC Card devices. FreeBSD_version 1300134 should be used for this
198 since it was bumped so recently.
201 Transport-independent parts of HID support have been split off the USB
202 code in to separate subsystem. Kernel configs which include one of
203 ums, ukbd, uhid, atp, wsp, wmt, uaudio, ugold or ucycom drivers should
204 be updated with adding of "device hid" line.
207 ncurses installation has been modified to only keep the widechar
208 enabled version. Incremental build is broken for that change, so it
209 requires a clean build.
212 The FreeBSD project has migrated from Subversion to Git. Temporary
213 instructions can be found at
214 https://github.com/bsdimp/freebsd-git-docs/blob/main/src-cvt.md
215 and other documents in that repo.
218 The services database has been updated to cover more of the basic
219 services expected in a modern system. The database is big enough
220 that it will cause issues in mergemaster in Releases previous to
221 12.2 and 11.3, or in very old current systems from before r358154.
224 Obsolete in-tree GDB 6.1.1 has been removed. GDB (including kgdb)
225 may be installed from ports or packages.
228 ping6 has been merged into ping. It can now be called as "ping -6".
229 See ping(8) for details.
232 Default value of net.add_addr_allfibs has been changed to 0.
233 If you have multi-fib configuration and rely on existence of all
234 interface routes in every fib, you need to set the above sysctl to 1.
236 The internal pre-processor in the calendar(1) program has been
237 extended to support more C pre-processor commands (e.g. #ifdef, #else,
238 and #undef) and to detect unbalanced conditional statements.
239 Error messages have been extended to include the filename and line
240 number if processing stops to help fixing malformed data files.
243 All the data files for the calendar(1) program, except calendar.freebsd,
244 have been moved to the deskutils/calendar-data port, much like the
245 jewish calendar entries were moved to deskutils/hebcal years ago. After
246 make delete-old-files, you need to install it to retain full
247 functionality. calendar(1) will issue a reminder for files it can't
251 LINT files are no longer generated. We now include the relevant NOTES
252 files. Note: This may cause conflicts with updating in some cases.
253 find sys -name LINT\* -delete
254 is suggested across this commit to remove the generated LINT files.
256 If you have tried to update with generated files there, the svn
257 command you want to un-auger the tree is
260 and then do the above find from the top level. Substitute 'amd64'
261 above with where the error message indicates a conflict.
264 OpenZFS support has been integrated. Do not upgrade root pools until
265 the loader is updated to support zstd. Furthermore, we caution against
266 'zpool upgrade' for the next few weeks. The change should be transparent
267 unless you want to use new features.
269 Not all "NO_CLEAN" build scenarios work across these changes. Many
270 scenarios have been tested and fixed, but rebuilding kernels without
271 rebuilding world may fail.
273 The ZFS cache file has moved from /boot to /etc to match the OpenZFS
274 upstream default. A fallback to /boot has been added for mountroot.
276 Pool auto import behavior at boot has been moved from the kernel module
277 to an explicit "zpool import -a" in one of the rc scripts enabled by
278 zfs_enable=YES. This means your non-root zpools won't auto import until
279 you upgrade your /etc/rc.d files.
282 The resume code now notifies devd with the 'kernel' system
283 rather than the old 'kern' subsystem to be consistent with
284 other use. The old notification will be created as well, but
285 will be removed prior to FreeBSD 14.0.
288 r362275 changed the internal API between the kernel RPC and the
289 NFS modules. As such, all the modules must be recompiled from
293 r364330 modified the internal API used between the NFS modules.
294 As such, all the NFS modules must be re-compiled from sources.
297 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
298 been upgraded to 11.0.0. Please see the 20141231 entry below for
299 information about prerequisites and upgrading, if you are not already
300 using clang 3.5.0 or higher.
303 r364092 modified the internal ABI used between the kernel NFS
304 modules. As such, all of these modules need to be rebuilt
305 from sources, so a version bump was done.
308 Makefile.inc has been updated to work around the issue documented in
309 20200729. It was a case where the optimization of using symbolic links
310 to point to binaries created a situation where we'd run new binaries
311 with old libraries starting midway through the installworld process.
314 r363679 has redefined some undefined behavior in regcomp(3); notably,
315 extraneous escapes of most ordinary characters will no longer be
316 accepted. An exp-run has identified all of the problems with this in
317 ports, but other non-ports software may need extra escapes removed to
318 continue to function.
320 Because of this change, installworld may encounter the following error
321 from rtld: Undefined symbol "regcomp@FBSD_1.6" -- It is imperative that
322 you do not halt installworld. Instead, let it run to completion (whether
323 successful or not) and run installworld once more.
326 A new implementation of bc and dc has been imported in r362681. This
327 implementation corrects non-conformant behavior of the previous bc
328 and adds GNU bc compatible options. It offers a number of extensions,
329 is much faster on large values, and has support for message catalogs
330 (a number of languages are already supported, contributions of further
331 languages welcome). The option WITHOUT_GH_BC can be used to build the
332 world with the previous versions of bc and dc.
335 r362639 changed the internal API used between the NFS kernel modules.
336 As such, they all need to be rebuilt from sources.
339 r362158 changed the arguments for VFS_CHECKEXP(). As such, any
340 out of tree file systems need to be modified and rebuilt.
341 Also, any file systems that are modules must be rebuilt.
344 read(2) of a directory fd is now rejected by default. root may
345 re-enable it for system root only on non-ZFS filesystems with the
346 security.bsd.allow_read_dir sysctl(8) MIB if
347 security.bsd.suser_enabled=1.
349 It may be advised to setup aliases for grep to default to `-d skip` if
350 commonly non-recursively grepping a list that includes directories and
351 the potential for the resulting stderr output is not tolerable. Example
352 aliases are now installed, commented out, in /root/.cshrc and
356 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
357 been upgraded to 10.0.1. Please see the 20141231 entry below for
358 information about prerequisites and upgrading, if you are not already
359 using clang 3.5.0 or higher.
362 Support for obsolete compilers has been removed from the build system.
363 Clang 6 and GCC 6.4 are the minimum supported versions.
366 closefrom(2) has been moved under COMPAT12, and replaced in libc with a
367 stub that calls close_range(2). If using a custom kernel configuration,
368 you may want to ensure that the COMPAT_FREEBSD12 option is included, as
369 a slightly older -CURRENT userland and older FreeBSD userlands may not
370 be functional without closefrom(2).
373 Upstream DTS from Linux 5.6 was merged and they now have the SID
374 and THS (Secure ID controller and THermal Sensor) node present.
375 The DTB overlays have now been removed from the tree for the H3/H5 and
376 A64 SoCs and the aw_sid and aw_thermal driver have been updated to
377 deal with upstream DTS. If you are using those overlays you need to
378 remove them from loader.conf and update the DTBs on the FAT partition.
381 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
382 been upgraded to 10.0.0. Please see the 20141231 entry below for
383 information about prerequisites and upgrading, if you are not already
384 using clang 3.5.0 or higher.
387 The amd(8) automount daemon has been removed from the source tree.
388 As of FreeBSD 10.1 autofs(5) is the preferred tool for automounting.
389 amd is still available in the sysutils/am-utils port.
392 Removed brooktree driver (bktr.4) from the tree.
395 The WITH_GPL_DTC option has been removed. The BSD-licenced device tree
396 compiler in usr.bin/dtc is used on all architectures which use dtc, and
397 the GPL dtc is available (if needed) from the sysutils/dtc port.
400 The WITHOUT_LLVM_LIBUNWIND option has been removed. LLVM's libunwind
401 is used by all supported CPU architectures.
404 GCC 4.2.1 has been removed from the tree. The WITH_GCC,
405 WITH_GCC_BOOTSTRAP, and WITH_GNUCXX options are no longer available.
406 Users who wish to build FreeBSD with GCC must use the external toolchain
410 ncurses has been updated to a newer version (6.2-20200215). Given the ABI
411 has changed, users will have to rebuild all the ports that are linked to
415 The size of struct vnet and the magic cookie have changed.
416 Users need to recompile libkvm and all modules using VIMAGE
417 together with their new kernel.
420 Defining the long deprecated NO_CTF, NO_DEBUG_FILES, NO_INSTALLLIB,
421 NO_MAN, NO_PROFILE, and NO_WARNS variables is now an error. Update
422 your Makefiles and scripts to define MK_<var>=no instead as required.
424 One exception to this is that program or library Makefiles should
425 define MAN to empty rather than setting MK_MAN=no.
428 Clang/LLVM is now the default compiler and LLD the default
432 make universe no longer uses GCC 4.2.1 on any architectures.
433 Architectures not supported by in-tree Clang/LLVM require an
434 external toolchain package.
437 GCC 4.2.1 is now not built by default, as part of the GCC 4.2.1
438 retirement plan. Specifically, the GCC, GCC_BOOTSTRAP, and GNUCXX
439 options default to off for all supported CPU architectures. As a
440 short-term transition aid they may be enabled via WITH_* options.
441 GCC 4.2.1 is expected to be removed from the tree on 2020-03-31.
444 Support for armv5 has been disconnected and is being removed. The
445 machine combination MACHINE=arm MACHINE_ARCH=arm is no longer valid.
446 You must now use a MACHINE_ARCH of armv6 or armv7. The default
447 MACHINE_ARCH for MACHINE=arm is now armv7.
450 Clang/LLVM is now the default compiler for all powerpc architectures.
451 LLD is now the default linker for powerpc64. The change for powerpc64
452 also includes a change to the ELFv2 ABI, incompatible with the existing
456 Kernel-loadable random(4) modules are no longer unloadable.
459 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
460 been upgraded to 9.0.1. Please see the 20141231 entry below for
461 information about prerequisites and upgrading, if you are not already
462 using clang 3.5.0 or higher.
465 r355677 has modified the internal interface used between the
466 NFS modules in the kernel. As such, they must all be upgraded
467 simultaneously. I will do a version bump for this.
470 The root certificates of the Mozilla CA Certificate Store have been
471 imported into the base system and can be managed with the certctl(8)
472 utility. If you have installed the security/ca_root_nss port or package
473 with the ETCSYMLINK option (the default), be advised that there may be
474 differences between those included in the port and those included in
475 base due to differences in nss branch used as well as general update
476 frequency. Note also that certctl(8) cannot manage certs in the
477 format used by the security/ca_root_nss port.
480 The amd(8) automount daemon has been disabled by default, and will be
481 removed in the future. As of FreeBSD 10.1 the autofs(5) is available
485 The nctgpio and wbwd drivers have been moved to the superio bus.
486 If you have one of these drivers in a kernel configuration, then
487 you should add device superio to it. If you use one of these drivers
488 as a module and you compile a custom set of modules, then you should
489 add superio to the set.
492 KPIs for network drivers to access interface addresses have changed.
493 Users need to recompile NIC driver modules together with kernel.
496 The net.link.tap.user_open sysctl no longer prevents user opening of
497 already created /dev/tapNN devices. Access is still controlled by
498 node permissions, just like tun devices. The net.link.tap.user_open
499 sysctl is now used only to allow users to perform devfs cloning of
500 tap devices, and the subsequent open may not succeed if the user is not
501 in the appropriate group. This sysctl may be deprecated/removed
502 completely in the future.
505 mips, powerpc, and sparc64 are no longer built as part of
506 universe / tinderbox unless MAKE_OBSOLETE_GCC is defined. If
507 not defined, mips, powerpc, and sparc64 builds will look for
508 the xtoolchain binaries and if installed use them for universe
509 builds. As llvm 9.0 becomes vetted for these architectures, they
510 will be removed from the list.
513 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
514 been upgraded to 9.0.0. Please see the 20141231 entry below for
515 information about prerequisites and upgrading, if you are not already
516 using clang 3.5.0 or higher.
519 The hpt27xx, hptmv, hptnr, and hptrr drivers have been removed from
520 GENERIC. They are available as modules and can be loaded by adding
521 to /boot/loader.conf hpt27xx_load="YES", hptmv_load="YES",
522 hptnr_load="YES", or hptrr_load="YES", respectively.
525 ntpd no longer by default locks its pages in memory, allowing them
526 to be paged out by the kernel. Use rlimit memlock to restore
527 historic BSD behaviour. For example, add "rlimit memlock 32"
528 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
531 Several of ping6's options have been renamed for better consistency
532 with ping. If you use any of -ARWXaghmrtwx, you must update your
533 scripts. See ping6(8) for details.
536 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
537 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
538 been removed from mount_fusefs(8). You can safely remove them from
539 your scripts, because they had no effect.
541 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
542 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
543 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
544 sysctls have been removed. If you felt the need to set any of them to
545 a non-default value, please tell asomers@FreeBSD.org why.
548 Default permissions on the /var/account/acct file (and copies of it
549 rotated by periodic daily scripts) are changed from 0644 to 0640
550 because the file contains sensitive information that should not be
551 world-readable. If the /var/account directory must be created by
552 rc.d/accounting, the mode used is now 0750. Admins who use the
553 accounting feature are encouraged to change the mode of an existing
554 /var/account directory to 0750 or 0700.
557 Entropy collection and the /dev/random device are no longer optional
558 components. The "device random" option has been removed.
559 Implementations of distilling algorithms can still be made loadable
560 with "options RANDOM_LOADABLE" (e.g., random_fortuna.ko).
563 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
564 been upgraded to 8.0.1. Please see the 20141231 entry below for
565 information about prerequisites and upgrading, if you are not already
566 using clang 3.5.0 or higher.
569 A fix was applied to i386 kernel modules to avoid panics with
570 dpcpu or vnet. Users need to recompile i386 kernel modules
571 having pcpu or vnet sections or they will refuse to load.
574 User-wired pages now have their own counter,
575 vm.stats.vm.v_user_wire_count. The vm.max_wired sysctl was renamed
576 to vm.max_user_wired and changed from an unsigned int to an unsigned
577 long. bhyve VMs wired with the -S are now subject to the user
578 wiring limit; the vm.max_user_wired sysctl may need to be tuned to
579 avoid running into the limit.
582 The IPSEC option has been removed from GENERIC. Users requiring
583 ipsec(4) must now load the ipsec(4) kernel module.
586 The tap(4) driver has been folded into tun(4), and the module has been
587 renamed to tuntap. You should update any kld_list="if_tap" or
588 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
589 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
590 module instead, and "device tap" or "device tun" entries in kernel
591 config files to select the tuntap device instead.
594 The following knobs have been added related to tradeoffs between
595 safe use of the random device and availability in the absence of
598 kern.random.initial_seeding.bypass_before_seeding: tunable; set
599 non-zero to bypass the random device prior to seeding, or zero to
600 block random requests until the random device is initially seeded.
601 For now, set to 1 (unsafe) by default to restore pre-r346250 boot
602 availability properties.
604 kern.random.initial_seeding.read_random_bypassed_before_seeding:
605 read-only diagnostic sysctl that is set when bypass is enabled and
606 read_random(9) is bypassed, to enable programmatic handling of this
607 initial condition, if desired.
609 kern.random.initial_seeding.arc4random_bypassed_before_seeding:
610 Similar to the above, but for for arc4random(9) initial seeding.
612 kern.random.initial_seeding.disable_bypass_warnings: tunable; set
613 non-zero to disable warnings in dmesg when the same conditions are
614 met as for the diagnostic sysctls above. Defaults to zero, i.e.,
615 produce warnings in dmesg when the conditions are met.
618 The loadable random module KPI has changed; the random_infra_init()
619 routine now requires a 3rd function pointer for a bool (*)(void)
620 method that returns true if the random device is seeded (and
621 therefore unblocked).
624 r345895 reverts r320698. This implies that an nfsuserd(8) daemon
625 built from head sources between r320757 (July 6, 2017) and
626 r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
627 is added to the command line.
628 nfsuserd daemons built from head sources that are post-r338192 are
629 not affected and should continue to work.
632 The fuse(4) module has been renamed to fusefs(4) for consistency with
633 other filesystems. You should update any kld_load="fuse" entries in
634 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
635 "options FUSE" entries in kernel config files.
638 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
639 8.0.0. Please see the 20141231 entry below for information about
640 prerequisites and upgrading, if you are not already using clang 3.5.0
644 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
645 compiled into your custom kernel, add 'device xz' statement to the
649 drm and drm2 have been removed from the tree. Please see
650 https://wiki.freebsd.org/Graphics for the latest information on
651 migrating to the drm ports.
654 Iflib is no longer unconditionally compiled into the kernel. Drivers
655 using iflib and statically compiled into the kernel, now require
656 the 'device iflib' config option. For the same drivers loaded as
657 modules on kernels not having 'device iflib', the iflib.ko module
658 is loaded automatically.
661 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
662 options no longer exist since r343219 and r343427 respectively;
663 nothing uses them, so they should be just removed from custom
667 r342635 changes the way efibootmgr(8) works by requiring users to add
668 the -b (bootnum) parameter for commands where the bootnum was previously
669 specified with each option. For example 'efibootmgr -B 0001' is now
670 'efibootmgr -B -b 0001'.
673 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
674 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
675 servers that have vfs.nfsd.nfs_privport set will only allow mounts
676 from clients using a reserved port#. Since both the FreeBSD and Linux
677 NFSv4 clients use reserved port#s by default, this should not affect
681 The XLP config has been removed. We can't support 64-bit atomics in this
682 kernel because it is running in 32-bit mode. XLP users must transition
683 to running a 64-bit kernel (XLP64 or XLPN32).
685 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
686 the preferred emulator today and we don't need two different ones.
688 The old sibyte / swarm / Broadcom BCM1250 support has been
689 removed from the mips port.
692 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
693 7.0.1. Please see the 20141231 entry below for information about
694 prerequisites and upgrading, if you are not already using clang 3.5.0
698 Remove the timed and netdate programs from the base tree. Setting
699 the time with these daemons has been obsolete for over a decade.
702 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
703 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
704 it produces broken binaries when ifuncs are in use. Users needing
705 GNU ld should install the binutils port or package.
708 The BSD crtbegin and crtend code has been enabled by default. It has
709 had extensive testing on amd64, arm64, and i386. It can be disabled
710 by building a world with -DWITHOUT_BSD_CRTBEGIN.
713 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
714 has been converted to a port (misc/ctm) and will be removed from
715 FreeBSD-13. It is available as a package (ctm) for all supported
719 The default newsyslog.conf(5) file has been changed to only include
720 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
721 the filenames end in '.conf' and do not begin with a '.'.
723 You should check the configuration files in these two directories match
724 this naming convention. You can verify which configuration files are
725 being included using the command:
729 Ports for the DRM modules have been simplified. Now, amd64 users should
730 just install the drm-kmod port. All others should install
733 Graphics hardware that's newer than about 2010 usually works with
734 drm-kmod. For hardware older than 2013, however, some users will need
735 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
736 than 2008 usually only works in drm-legacy-kmod. The graphics team can
737 only commit to hardware made since 2013 due to the complexity of the
738 market and difficulty to test all the older cards effectively. If you
739 have hardware supported by drm-kmod, you are strongly encouraged to use
740 that as you will get better support.
742 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
743 elsewhere, the drm and drm2 modules will be eliminated from the src base
744 soon (with a limited exception for arm). Please update to the package
745 asap and report any issues to x11@freebsd.org.
747 Generally, anybody using the drm*-kmod packages should add
748 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
749 cross-threading surprises, especially with automatic driver
750 loading from X11 startup. These will become the defaults in 13-current
754 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
755 custom kernel and module loading configuration files must be updated
756 accordingly. Moreover, interfaces previous presented as ixlvN to the
757 system are now exposed as iavfN and network configuration files must
758 be adjusted as necessary.
761 OpenSSL has been updated to version 1.1.1. This update included
762 additional various API changes throughout the base system. It is
763 important to rebuild third-party software after upgrading. The value
764 of __FreeBSD_version has been bumped accordingly.
767 The legacy DRM modules and drivers have now been added to the loader's
768 module blacklist, in favor of loading them with kld_list in rc.conf(5).
769 The module blacklist may be overridden with the loader.conf(5)
770 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
774 The cam(4) based nda(4) driver will be used over nvd(4) by default on
775 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
776 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
777 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
781 Reproducible build mode is now on by default, in preparation for
782 FreeBSD 12.0. This eliminates build metadata such as the user,
783 host, and time from the kernel (and uname), unless the working tree
784 corresponds to a modified checkout from a version control system.
785 The previous behavior can be obtained by setting the /etc/src.conf
786 knob WITHOUT_REPRODUCIBLE_BUILD.
789 The Yarrow CSPRNG has been removed from the kernel as it has not been
790 supported by its designers since at least 2003. Fortuna has been the
791 default since FreeBSD-11.
794 devctl freeze/thaw have gone into the tree, the rc scripts have been
795 updated to use them and devmatch has been changed. You should update
796 kernel, userland and rc scripts all at the same time.
799 The default interpreter has been switched from 4th to Lua.
800 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
801 interpreter. If you have custom FORTH code you will need to set
802 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
803 src.conf for the build. This will create default hard links between
804 loader and loader_4th instead of loader and loader_lua, the new default.
805 If you are using UEFI it will create the proper hard link to loader.efi.
807 bhyve uses userboot.so. It remains 4th-only until some issues are solved
808 regarding coexisting with multiple versions of FreeBSD are resolved.
811 ls(1) now respects the COLORTERM environment variable used in other
812 systems and software to indicate that a colored terminal is both
813 supported and desired. If ls(1) is suddenly emitting colors, they may
814 be disabled again by either removing the unwanted COLORTERM from your
815 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
816 may not be observed in a future release.
819 The default pager for most commands has been changed to "less". To
820 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
824 The jedec_ts(4) driver has been removed. A superset of its functionality
825 is available in the jedec_dimm(4) driver, and the manpage for that
826 driver includes migration instructions. If you have "device jedec_ts"
827 in your kernel configuration file, it must be removed.
830 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
831 This should have no effect if the kernel is booted via BIOS/legacy boot.
832 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
833 has a buggy firmware that prevents a successful boot due to use of
837 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
838 support has been removed from the tree. These ports were
839 obsolete and/or known to be broken for many years.
842 loader.efi has been augmented to participate more fully in the
843 UEFI boot manager protocol. loader.efi will now look at the
844 BootXXXX environment variable to determine if a specific kernel
845 or root partition was specified. XXXX is derived from BootCurrent.
846 efibootmgr(8) manages these standard UEFI variables.
849 zfsloader's functionality has now been folded into loader.
850 zfsloader is no longer necessary once you've updated your
851 boot blocks. For a transition period, we will install a
852 hardlink for zfsloader to loader to allow a smooth transition
853 until the boot blocks can be updated (hard link because old
854 zfs boot blocks don't understand symlinks).
857 ARM64 now have efifb support, if you want to have serial console
858 on your arm64 board when an screen is connected and the bootloader
859 setup a frame buffer for us to use, just add :
863 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
864 an screen connected as the firmware will setup a frame buffer are that
865 u-boot will expose as an EFI frame buffer.
868 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
869 or take steps to update /etc/passwd before doing installworld on
870 existing systems. Do not skip the "mergemaster -Fp" step before
871 installworld, as described in the update procedures near the bottom
872 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
873 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
874 the ntp config file contain options that change file/dir locations.
875 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
876 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
877 taking steps to ensure that all required files/dirs are accessible
881 Big endian arm support has been removed.
884 The static environment setup in kernel configs is no longer mutually
885 exclusive with the loader(8) environment by default. In order to
886 restore the previous default behavior of disabling the loader(8)
887 environment if a static environment is present, you must specify
888 loader_env.disabled=1 in the static environment.
891 The ABI of syscalls used by management tools like sockstat and
892 netstat has been broken to allow 32-bit binaries to work on
893 64-bit kernels without modification. These programs will need
894 to match the kernel in order to function. External programs may
895 require minor modifications to accommodate a change of type in
896 structures from pointers to 64-bit virtual addresses.
899 On i386 and amd64 atomics are now inlined. Out of tree modules using
900 atomics will need to be rebuilt.
903 The '%I' format in the kern.corefile sysctl limits the number of
904 core files that a process can generate to the number stored in the
905 debug.ncores sysctl. The '%I' format is replaced by the single digit
906 index. Previously, if all indexes were taken the kernel would overwrite
907 only a core file with the highest index in a filename.
908 Currently the system will create a new core file if there is a free
909 index or if all slots are taken it will overwrite the oldest one.
912 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
913 6.0.1. Please see the 20141231 entry below for information about
914 prerequisites and upgrading, if you are not already using clang 3.5.0
918 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
919 needed to be changed to work with it. This change was made with r335763
920 and requires a mergemaster / etcupdate / etc to update the installed
924 r334930 changed the interface between the NFS modules, so they all
925 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
928 As of r334391 lld is the default amd64 system linker; it is installed
929 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
933 The kernel / userland interface for devinfo changed, so you'll
934 need a new kernel and userland as a pair for it to work (rebuilding
935 lib/libdevinfo is all that's required). devinfo and devmatch will
936 not work, but everything else will when there's a mismatch.
939 The on-disk format for hwpmc callchain records has changed to include
940 threadid corresponding to a given record. This changes the field offsets
941 and thus requires that libpmcstat be rebuilt before using a kernel
945 The vxge(4) driver has been removed. This driver was introduced into
946 HEAD one week before the Exar left the Ethernet market and is not
947 known to be used. If you have device vxge in your kernel config file
951 The amd64 kernel now requires a ld that supports ifunc to produce a
952 working kernel, either lld or a newer binutils. lld is built by default
953 on amd64, and the 'buildkernel' target uses it automatically. However,
954 it is not the default linker, so building the kernel the traditional
955 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
956 binutils port/package). lld will soon be default, and this requirement
959 NOTE: As of r334391 lld is the default system linker on amd64, and no
960 workaround is necessary.
963 The nxge(4) driver has been removed. This driver was for PCI-X 10g
964 cards made by s2io/Neterion. The company was acquired by Exar and
965 no longer sells or supports Ethernet products. If you have device
966 nxge in your kernel config file it must be removed.
969 The tz database (tzdb) has been updated to 2018e. This version more
970 correctly models time stamps in time zones with negative DST such as
971 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
972 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
973 time zone abbreviations and the tm_isdst flag.
976 The ixgb(4) driver has been removed. This driver was for an early and
977 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
978 quickly shifted to the long lived ixgbe family. If you have device
979 ixgb in your kernel config file it must be removed.
982 The lmc(4) driver has been removed. This was a WAN interface
983 card that was already reportedly rare in 2003, and had an ambiguous
984 license. If you have device lmc in your kernel config file it must
988 Support for Arcnet networks has been removed. If you have device
989 arcnet or device cm in your kernel config file they must be
993 Support for FDDI networks has been removed. If you have device
994 fddi or device fpa in your kernel config file they must be
998 In addition to supporting RFC 3164 formatted messages, the
999 syslogd(8) service is now capable of parsing RFC 5424 formatted
1000 log messages. The main benefit of using RFC 5424 is that clients
1001 may now send log messages with timestamps containing year numbers,
1002 microseconds and time zone offsets.
1004 Similarly, the syslog(3) C library function has been altered to
1005 send RFC 5424 formatted messages to the local system logging
1006 daemon. On systems using syslogd(8), this change should have no
1007 negative impact, as long as syslogd(8) and the C library are
1008 updated at the same time. On systems using a different system
1009 logging daemon, it may be necessary to make configuration
1010 adjustments, depending on the software used.
1012 When using syslog-ng, add the 'syslog-protocol' flag to local
1013 input sources to enable parsing of RFC 5424 formatted messages:
1016 unix-dgram("/var/run/log" flags(syslog-protocol));
1019 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
1020 of the 'imuxsock' module to let messages be processed by the
1021 regular RFC 3164/5424 parsing pipeline:
1023 module(load="imuxsock" SysSock.UseSpecialParser="off")
1025 Do note that these changes only affect communication between local
1026 applications and syslogd(8). The format that syslogd(8) uses to
1027 store messages on disk or forward messages to other systems
1028 remains unchanged. syslogd(8) still uses RFC 3164 for these
1029 purposes. Options to customize this behaviour will be added in the
1030 future. Utilities that process log files stored in /var/log are
1031 thus expected to continue to function as before.
1033 __FreeBSD_version has been incremented to 1200061 to denote this
1037 Support for token ring networks has been removed. If you
1038 have "device token" in your kernel config you should remove
1039 it. No device drivers supported token ring.
1042 makefs was modified to be able to tag ISO9660 El Torito boot catalog
1043 entries as EFI instead of overloading the i386 tag as done previously.
1044 The amd64 mkisoimages.sh script used to build amd64 ISO images for
1045 release was updated to use this. This may mean that makefs must be
1046 updated before "make cdrom" can be run in the release directory. This
1047 should be as simple as:
1049 $ cd $SRCDIR/usr.sbin/makefs
1050 $ make depend all install
1053 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
1054 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
1055 Co-existence for the transition period will come shortly. Booting is a
1056 complex environment and test coverage for Lua-enabled loaders has been
1057 thin, so it would be prudent to assume it might not work and make
1058 provisions for backup boot methods.
1061 devmatch functionality has been turned on in devd. It will automatically
1062 load drivers for unattached devices. This may cause unexpected drivers
1063 to be loaded. Please report any problems to current@ and
1067 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
1068 6.0.0. Please see the 20141231 entry below for information about
1069 prerequisites and upgrading, if you are not already using clang 3.5.0
1073 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
1074 This means it is used to link the kernel and userland libraries and
1075 executables, but is not yet installed as /usr/bin/ld by default.
1077 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
1078 WITHOUT_LLD_BOOTSTRAP=yes
1081 On i386, pmtimer has been removed. Its functionality has been folded
1082 into apm. It was a no-op on ACPI in current for a while now (but was
1083 still needed on i386 in FreeBSD 11 and earlier). Users may need to
1084 remove it from kernel config files.
1087 The use of RSS hash from the network card aka flowid has been
1088 disabled by default for lagg(4) as it's currently incompatible with
1089 the lacp and loadbalance protocols.
1091 This can be re-enabled by setting the following in loader.conf:
1092 net.link.lagg.default_use_flowid="1"
1095 The SW_WATCHDOG option is no longer necessary to enable the
1096 hardclock-based software watchdog if no hardware watchdog is
1097 configured. As before, SW_WATCHDOG will cause the software
1098 watchdog to be enabled even if a hardware watchdog is configured.
1101 r326887 fixes the issue described in the 20171214 UPDATING entry.
1102 r326888 flips the switch back to building GELI support always.
1105 r362593 broke ZFS + GELI support for reasons unknown. However,
1106 it also broke ZFS support generally, so GELI has been turned off
1107 by default as the lesser evil in r326857. If you boot off ZFS and/or
1108 GELI, it might not be a good time to update.
1111 PowerPC users must update loader(8) by rebuilding world before
1112 installing a new kernel, as the protocol connecting them has
1113 changed. Without the update, loader metadata will not be passed
1114 successfully to the kernel and users will have to enter their
1115 root partition at the kernel mountroot prompt to continue booting.
1116 Newer versions of loader can boot old kernels without issue.
1119 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
1120 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
1121 to WITH/OUT_LOADER_GELI.
1124 The naive and non-compliant support of posix_fallocate(2) in ZFS
1125 has been removed as of r325320. The system call now returns EINVAL
1126 when used on a ZFS file. Although the new behavior complies with the
1127 standard, some consumers are not prepared to cope with it.
1128 One known victim is lld prior to r325420.
1131 Building in a FreeBSD src checkout will automatically create object
1132 directories now rather than store files in the current directory if
1133 'make obj' was not ran. Calling 'make obj' is no longer necessary.
1134 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
1135 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
1139 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
1140 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
1141 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
1142 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
1143 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
1144 The UNIFIED_OBJDIR option is a transitional feature that will be
1145 removed for 12.0 release; please migrate to the new format for any
1146 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
1147 than hardcoding paths.
1150 The native-xtools target no longer installs the files by default to the
1151 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
1152 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
1155 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
1156 options are changing from controlling the build if defined / undefined
1157 to controlling the build with explicit 'yes' or 'no' values. They will
1158 shift to WITH/WITHOUT options to match other options in the system.
1161 libstand has turned into a private library for sys/boot use only.
1162 It is no longer supported as a public interface outside of sys/boot.
1165 The arm port has split armv6 into armv6 and armv7. armv7 is now
1166 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
1167 and are running a kernel from before r324363, you will need to add
1168 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
1171 When building multiple kernels using KERNCONF, non-existent KERNCONF
1172 files will produce an error and buildkernel will fail. Previously
1173 missing KERNCONF files silently failed giving no indication as to
1174 why, only to subsequently discover during installkernel that the
1175 desired kernel was never built in the first place.
1178 The default serial number format for CTL LUNs has changed. This will
1179 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
1180 or iSCSI clients care about their LUNs' serial numbers. Users who
1181 require serial number stability should hardcode serial numbers in
1185 For 32-bit arm compiled for hard-float support, soft-floating point
1186 binaries now always get their shared libraries from
1187 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
1188 /usr/libsoft also existed). Only users with a hard-float ld.so, but
1189 soft-float everything else should be affected.
1192 The geli password typed at boot is now hidden. To restore the previous
1193 behavior, see geli(8) for configuration options.
1196 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
1197 sysctl values. Minor nit, but requires a rebuild of both world/kernel
1201 "make check" behavior (made in ^/head@r295380) has been changed to
1202 execute from a limited sandbox, as opposed to executing from
1206 - The "beforecheck" and "aftercheck" targets are now specified.
1207 - ${CHECKDIR} (added in commit noted above) has been removed.
1208 - Legacy behavior can be enabled by setting
1209 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
1211 If the limited sandbox mode is enabled, "make check" will execute
1212 "make distribution", then install, execute the tests, and clean up the
1213 sandbox if successful.
1215 The "make distribution" and "make install" targets are typically run as
1216 root to set appropriate permissions and ownership at installation time.
1217 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
1218 environment if executing "make check" with limited sandbox mode using
1219 an unprivileged user.
1222 Since the switch to GPT disk labels, fsck for UFS/FFS has been
1223 unable to automatically find alternate superblocks. As of r322297,
1224 the information needed to find alternate superblocks has been
1225 moved to the end of the area reserved for the boot block.
1226 Filesystems created with a newfs of this vintage or later
1227 will create the recovery information. If you have a filesystem
1228 created prior to this change and wish to have a recovery block
1229 created for your filesystem, you can do so by running fsck in
1230 foreground mode (i.e., do not use the -p or -y options). As it
1231 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
1232 to which you should answer yes.
1235 As of r321665, an NFSv4 server configuration that services
1236 Kerberos mounts or clients that do not support the uid/gid in
1237 owner/owner_group string capability, must explicitly enable
1238 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
1239 machine's /etc/rc.conf file.
1242 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
1243 Please see the 20141231 entry below for information about prerequisites
1244 and upgrading, if you are not already using clang 3.5.0 or higher.
1247 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
1248 r-commands (rlogin, rsh, etc.) to be built with the base system.
1251 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
1252 a very major ABI incompatible change, so users of FreeBSD/powerpc must
1253 be careful when performing source upgrades. It is best to run
1254 'make installworld' from an alternate root system, either a live
1255 CD/memory stick, or a temporary root partition. Additionally, all ports
1256 must be recompiled. powerpc64 is largely unaffected, except in the case
1257 of 32-bit compatibility. All 32-bit binaries will be affected.
1260 Forward compatibility for the "ino64" project have been committed. This
1261 will allow most new binaries to run on older kernels in a limited
1262 fashion. This prevents many of the common foot-shooting actions in the
1263 upgrade as well as the limited ability to roll back the kernel across
1264 the ino64 upgrade. Complicated use cases may not work properly, though
1265 enough simpler ones work to allow recovery in most situations.
1268 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
1269 if you require the GPL compiler.
1272 The internal ABI used for communication between the NFS kernel modules
1273 was changed by r320085, so __FreeBSD_version was bumped to
1274 ensure all the NFS related modules are updated together.
1277 The ABI of struct event was changed by extending the data
1278 member to 64bit and adding ext fields. For upgrade, same
1279 precautions as for the entry 20170523 "ino64" must be
1283 The GNU roff toolchain has been removed from base. To render manpages
1284 which are not supported by mandoc(1), man(1) can fallback on GNU roff
1285 from ports (and recommends to install it).
1286 To render roff(7) documents, consider using GNU roff from ports or the
1287 heirloom doctools roff toolchain from ports via pkg install groff or
1288 via pkg install heirloom-doctools.
1291 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
1292 smaller runtime footprint builds. This is useful for embedded systems
1293 which only require one chipset support.
1295 If you load it as a module, make sure this is in /boot/loader.conf:
1299 This will load the HAL, all chip/RF backends and if_ath_pci.
1300 If you have if_ath_pci in /boot/loader.conf, ensure it is after
1301 if_ath or it will not load any HAL chipset support.
1303 If you want to selectively load things (eg on ye cheape ARM/MIPS
1304 platforms where RAM is at a premium) you should:
1307 * load the chip modules in question
1308 * load ath_rate, ath_dfs
1310 * load if_ath_pci and/or if_ath_ahb depending upon your particular
1311 bus bind type - this is where probe/attach is done.
1313 For further comments/feedback, poke adrian@ .
1316 The "ino64" 64-bit inode project has been committed, which extends
1317 a number of types to 64 bits. Upgrading in place requires care and
1318 adherence to the documented upgrade procedure.
1320 If using a custom kernel configuration ensure that the
1321 COMPAT_FREEBSD11 option is included (as during the upgrade the
1322 system will be running the ino64 kernel with the existing world).
1324 For the safest in-place upgrade begin by removing previous build
1325 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full
1326 procedure documented below under the heading "To rebuild everything and
1327 install it on the current system." Specifically, a reboot is required
1328 after installing the new kernel before installing world. While an
1329 installworld normally works by accident from multiuser after rebooting
1330 the proper kernel, there are many cases where this will fail across this
1331 upgrade and installworld from single user is required.
1334 The NATM framework including the en(4), fatm(4), hatm(4), and
1335 patm(4) devices has been removed. Consumers should plan a
1336 migration before the end-of-life date for FreeBSD 11.
1339 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
1340 diff has not been implemented, if those are needed a newer version of
1341 GNU diff is available via the diffutils package under the gdiff name.
1344 As of r316810 for ipfilter, keep frags is no longer assumed when
1345 keep state is specified in a rule. r316810 aligns ipfilter with
1346 documentation in man pages separating keep frags from keep state.
1347 This allows keep state to be specified without forcing keep frags
1348 and allows keep frags to be specified independently of keep state.
1349 To maintain previous behaviour, also specify keep frags with
1350 keep state (as documented in ipf.conf.5).
1353 arm64 builds now use the base system LLD 4.0.0 linker by default,
1354 instead of requiring that the aarch64-binutils port or package be
1355 installed. To continue using aarch64-binutils, set
1356 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
1359 The UDP optimization in entry 20160818 that added the sysctl
1360 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
1361 packets will no longer be treated as L3 broadcast packets.
1364 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
1365 use any explicitly assigned loopback address available in the jail
1366 instead of using the first assigned address of the jail.
1369 The ctl.ko module no longer implements the iSCSI target frontend:
1370 cfiscsi.ko does instead.
1372 If building cfiscsi.ko as a kernel module, the module can be loaded
1373 via one of the following methods:
1374 - `cfiscsi_load="YES"` in loader.conf(5).
1375 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
1376 - ctladm(8)/ctld(8), when compiled with iSCSI support
1377 (`WITH_ISCSI=yes` in src.conf(5))
1379 Please see cfiscsi(4) for more details.
1382 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
1383 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
1384 same source (previously, the dependency of mmcsd.ko on mmc.ko was
1385 missing, but mmcsd.ko now will refuse to load if it is incompatible
1389 The syntax of ipfw(8) named states was changed to avoid ambiguity.
1390 If you have used named states in the firewall rules, you need to modify
1391 them after installworld and before rebooting. Now named states must
1392 be prefixed with colon.
1395 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
1396 removed as the userland we provide cannot use them. The KMS version
1397 (sys/dev/drm2) supports the same hardware.
1400 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
1401 Please see the 20141231 entry below for information about prerequisites
1402 and upgrading, if you are not already using clang 3.5.0 or higher.
1405 The code that provides support for ZFS .zfs/ directory functionality
1406 has been reimplemented. It's not possible now to create a snapshot
1407 by mkdir under .zfs/snapshot/. That should be the only user visible
1411 EISA bus support has been removed. The WITH_EISA option is no longer
1415 MCA bus support has been removed.
1418 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
1419 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
1422 The EM_MULTIQUEUE kernel configuration option is deprecated now that
1423 the em(4) driver conforms to iflib specifications.
1426 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
1427 IFLIB. If you have a custom kernel configuration that excludes em(4)
1428 but you use igb(4), you need to re-add em(4) to your custom
1432 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
1433 Please see the 20141231 entry below for information about prerequisites
1434 and upgrading, if you are not already using clang 3.5.0 or higher.
1437 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
1438 Please see the 20141231 entry below for information about prerequisites
1439 and upgrading, if you are not already using clang 3.5.0 or higher.
1442 The layout of the pmap structure has changed for powerpc to put the pmap
1443 statistics at the front for all CPU variations. libkvm(3) and all tools
1444 that link against it need to be recompiled.
1447 isl(4) and cyapa(4) drivers now require a new driver,
1448 chromebook_platform(4), to work properly on Chromebook-class hardware.
1449 On other types of hardware the drivers may need to be configured using
1450 device hints. Please see the corresponding manual pages for details.
1453 The urtwn(4) driver was merged into rtwn(4) and now consists of
1454 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
1456 Also, firmware for RTL8188CE was renamed due to possible name
1457 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
1460 GNU rcs has been removed from base. It is available as packages:
1461 - rcs: Latest GPLv3 GNU rcs version.
1462 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
1466 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
1467 modules now requires that the kernel configuration contain the
1468 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
1471 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
1472 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
1475 Relocatable object files with the extension of .So have been renamed
1476 to use an extension of .pico instead. The purpose of this change is
1477 to avoid a name clash with shared libraries on case-insensitive file
1478 systems. On those file systems, foo.So is the same file as foo.so.
1481 GNU rcs has been turned off by default. It can (temporarily) be built
1482 again by adding WITH_RCS knob in src.conf.
1483 Otherwise, GNU rcs is available from packages:
1484 - rcs: Latest GPLv3 GNU rcs version.
1485 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
1488 The backup_uses_rcs functionality has been removed from rc.subr.
1491 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
1492 two separate components, QUEUE_MACRO_DEBUG_TRACE and
1493 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
1494 QUEUE_MACRO_DEBUG behavior.
1497 r304787 changed some ioctl interfaces between the iSCSI userspace
1498 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1499 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1503 The UDP receive code has been updated to only treat incoming UDP
1504 packets that were addressed to an L2 broadcast address as L3
1505 broadcast packets. It is not expected that this will affect any
1506 standards-conforming UDP application. The new behaviour can be
1507 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1511 Remove the openbsd_poll system call.
1512 __FreeBSD_version has been bumped because of this.
1515 The stable/11 branch has been created from head@r302406.
1518 The libc stub for the pipe(2) system call has been replaced with
1519 a wrapper that calls the pipe2(2) system call and the pipe(2)
1520 system call is now only implemented by the kernels that include
1521 "options COMPAT_FREEBSD10" in their config file (this is the
1522 default). Users should ensure that this option is enabled in
1523 their kernel or upgrade userspace to r302092 before upgrading their
1527 CAM will now strip leading spaces from SCSI disks' serial numbers.
1528 This will affect users who create UFS filesystems on SCSI disks using
1529 those disk's diskid device nodes. For example, if /etc/fstab
1530 previously contained a line like
1531 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
1532 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
1533 transforms like gmirror may also be affected. ZFS users should
1537 The bitstring(3) API has been updated with new functionality and
1538 improved performance. But it is binary-incompatible with the old API.
1539 Objects built with the new headers may not be linked against objects
1540 built with the old headers.
1543 The brk and sbrk functions have been removed from libc on arm64.
1544 Binutils from ports has been updated to not link to these
1545 functions and should be updated to the latest version before
1546 installing a new libc.
1549 The armv6 port now defaults to hard float ABI. Limited support
1550 for running both hardfloat and soft float on the same system
1551 is available using the libraries installed with -DWITH_LIBSOFT.
1552 This has only been tested as an upgrade path for installworld
1553 and packages may fail or need manual intervention to run. New
1554 packages will be needed.
1556 To update an existing self-hosted armv6hf system, you must add
1557 TARGET_ARCH=armv6 on the make command line for both the build
1558 and the install steps.
1561 Kernel modules compiled outside of a kernel build now default to
1562 installing to /boot/modules instead of /boot/kernel. Many kernel
1563 modules built this way (such as those in ports) already overrode
1564 KMODDIR explicitly to install into /boot/modules. However,
1565 manually building and installing a module from /sys/modules will
1566 now install to /boot/modules instead of /boot/kernel.
1569 The CAM I/O scheduler has been committed to the kernel. There should be
1570 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1571 list of known rogues that claim support for this but actually corrupt
1572 data is believed to be complete, be on the lookout for data
1573 corruption. The known rogue list is believed to be complete:
1575 o Crucial MX100, M550 drives with MU01 firmware.
1576 o Micron M510 and M550 drives with MU01 firmware.
1577 o Micron M500 prior to MU07 firmware
1578 o Samsung 830, 840, and 850 all firmwares
1579 o FCCT M500 all firmwares
1581 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1582 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1583 updated firmware. Black listed drives will work correctly because these
1584 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1585 this list is the same as found in Linux, it's believed there are no
1586 other rogues in the market place. All other models from the above
1589 To be safe, if you are at all concerned, you can quirk each of your
1590 drives to prevent NCQ from being sent by setting:
1591 kern.cam.ada.X.quirks="0x2"
1592 in loader.conf. If the drive requires the 4k sector quirk, set the
1593 quirks entry to 0x3.
1596 The FAST_DEPEND build option has been removed and its functionality is
1597 now the one true way. The old mkdep(1) style of 'make depend' has
1598 been removed. See 20160311 for further details.
1601 Resource range types have grown from unsigned long to uintmax_t. All
1602 drivers, and anything using libdevinfo, need to be recompiled.
1605 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1606 builds. It no longer runs mkdep(1) during 'make depend', and the
1607 'make depend' stage can safely be skipped now as it is auto ran
1608 when building 'make all' and will generate all SRCS and DPSRCS before
1609 building anything else. Dependencies are gathered at compile time with
1610 -MF flags kept in separate .depend files per object file. Users should
1611 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1612 stale .depend files.
1615 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1616 kernel modules. Therefore, if you load any kernel modules at boot time,
1617 please install the boot loaders after you install the kernel, but before
1621 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1622 make installkernel KERNCONF=YOUR_KERNEL_HERE
1623 make -C sys/boot install
1624 <reboot in single user>
1626 Then follow the usual steps, described in the General Notes section,
1630 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1631 see the 20141231 entry below for information about prerequisites and
1632 upgrading, if you are not already using clang 3.5.0 or higher.
1635 The AIO subsystem is now a standard part of the kernel. The
1636 VFS_AIO kernel option and aio.ko kernel module have been removed.
1637 Due to stability concerns, asynchronous I/O requests are only
1638 permitted on sockets and raw disks by default. To enable
1639 asynchronous I/O requests on all file types, set the
1640 vfs.aio.enable_unsafe sysctl to a non-zero value.
1643 The ELF object manipulation tool objcopy is now provided by the
1644 ELF Tool Chain project rather than by GNU binutils. It should be a
1645 drop-in replacement, with the addition of arm64 support. The
1646 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1647 to obtain the GNU version if necessary.
1650 Building ZFS pools on top of zvols is prohibited by default. That
1651 feature has never worked safely; it's always been prone to deadlocks.
1652 Using a zvol as the backing store for a VM guest's virtual disk will
1653 still work, even if the guest is using ZFS. Legacy behavior can be
1654 restored by setting vfs.zfs.vol.recursive=1.
1657 The NONE and HPN patches has been removed from OpenSSH. They are
1658 still available in the security/openssh-portable port.
1661 With the addition of ypldap(8), a new _ypldap user is now required
1662 during installworld. "mergemaster -p" can be used to add the user
1663 prior to installworld, as documented in the handbook.
1666 The tftp loader (pxeboot) now uses the option root-path directive. As a
1667 consequence it no longer looks for a pxeboot.4th file on the tftp
1668 server. Instead it uses the regular /boot infrastructure as with the
1672 The code to start recording plug and play data into the modules has
1673 been committed. While the old tools will properly build a new kernel,
1674 a number of warnings about "unknown metadata record 4" will be produced
1675 for an older kldxref. To avoid such warnings, make sure to rebuild
1676 the kernel toolchain (or world). Make sure that you have r292078 or
1677 later when trying to build 292077 or later before rebuilding.
1680 Debug data files are now built by default with 'make buildworld' and
1681 installed with 'make installworld'. This facilitates debugging but
1682 requires more disk space both during the build and for the installed
1683 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1687 r291527 changed the internal interface between the nfsd.ko and
1688 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1689 __FreeBSD_version has been bumped because of this.
1692 Add support for unicode collation strings leads to a change of
1693 order of files listed by ls(1) for example. To get back to the old
1694 behaviour, set LC_COLLATE environment variable to "C".
1696 Databases administrators will need to reindex their databases given
1697 collation results will be different.
1699 Due to a bug in install(1) it is recommended to remove the ancient
1700 locales before running make installworld.
1702 rm -rf /usr/share/locale/*
1705 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1706 libcrypto.so.7 or libssl.so.7 must be recompiled.
1709 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1710 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1711 should be replaced with isp_2400 and isp_2500 modules respectively.
1714 The build previously allowed using 'make -n' to not recurse into
1715 sub-directories while showing what commands would be executed, and
1716 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1717 and 'make -N' will not.
1720 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1721 and etcupdate will now use this file. A custom sendmail.cf is now
1722 updated via this mechanism rather than via installworld. If you had
1723 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1724 want to remove the exclusion or change it to "always install".
1725 /etc/mail/sendmail.cf is now managed the same way regardless of
1726 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1727 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1730 Compatibility shims for legacy ATA device names have been removed.
1731 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1732 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1733 environment variables, /dev/ad* and /dev/ar* symbolic links.
1736 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1737 Please see the 20141231 entry below for information about prerequisites
1738 and upgrading, if you are not already using clang 3.5.0 or higher.
1741 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1742 and renamed from .symbols to .debug. This reduces the size requirements
1743 on the boot partition or file system and provides consistency with
1744 userland debug files.
1746 When using the supported kernel installation method the
1747 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1748 as is done with /boot/kernel.
1750 Developers wishing to maintain the historical behavior of installing
1751 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1754 The wireless drivers had undergone changes that remove the 'parent
1755 interface' from the ifconfig -l output. The rc.d network scripts
1756 used to check presence of a parent interface in the list, so old
1757 scripts would fail to start wireless networking. Thus, etcupdate(3)
1758 or mergemaster(8) run is required after kernel update, to update your
1759 rc.d scripts in /etc.
1762 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1763 These configurations are now automatically interpreted as
1764 'scrub fragment reassemble'.
1767 Kernel-loadable modules for the random(4) device are back. To use
1768 them, the kernel must have
1771 options RANDOM_LOADABLE
1773 kldload(8) can then be used to load random_fortuna.ko
1774 or random_yarrow.ko. Please note that due to the indirect
1775 function calls that the loadable modules need to provide,
1776 the build-in variants will be slightly more efficient.
1778 The random(4) kernel option RANDOM_DUMMY has been retired due to
1779 unpopularity. It was not all that useful anyway.
1782 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1783 Control over building the ELF Tool Chain tools is now provided by
1784 the WITHOUT_TOOLCHAIN knob.
1787 The polarity of Pulse Per Second (PPS) capture events with the
1788 uart(4) driver has been corrected. Prior to this change the PPS
1789 "assert" event corresponded to the trailing edge of a positive PPS
1790 pulse and the "clear" event was the leading edge of the next pulse.
1792 As the width of a PPS pulse in a typical GPS receiver is on the
1793 order of 1 millisecond, most users will not notice any significant
1794 difference with this change.
1796 Anyone who has compensated for the historical polarity reversal by
1797 configuring a negative offset equal to the pulse width will need to
1798 remove that workaround.
1801 The default group assigned to /dev/dri entries has been changed
1802 from 'wheel' to 'video' with the id of '44'. If you want to have
1803 access to the dri devices please add yourself to the video group
1806 # pw groupmod video -m $USER
1809 The menu.rc and loader.rc files will now be replaced during
1810 upgrades. Please migrate local changes to menu.rc.local and
1811 loader.rc.local instead.
1814 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1815 strings and strip have been removed. The src.conf(5) knob
1816 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1819 As ZFS requires more kernel stack pages than is the default on some
1820 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1821 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1823 Please consider using 'options KSTACK_PAGES=X' where X is greater
1824 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1827 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1828 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1829 default, i.e., they will not contain "::". For example, instead
1830 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1831 to have a more specific match, such as different map entries for
1832 IPv6:0:0 vs IPv6:0. This change requires that configuration
1833 data (including maps, files, classes, custom ruleset, etc.) must
1834 use the same format, so make certain such configuration data is
1835 upgrading. As a very simple check search for patterns like
1836 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1837 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1838 the cf option UseCompressedIPv6Addresses.
1841 The default kernel entropy-processing algorithm is now
1842 Fortuna, replacing Yarrow.
1844 Assuming you have 'device random' in your kernel config
1845 file, the configurations allow a kernel option to override
1846 this default. You may choose *ONE* of:
1848 options RANDOM_YARROW # Legacy /dev/random algorithm.
1849 options RANDOM_DUMMY # Blocking-only driver.
1851 If you have neither, you get Fortuna. For most people,
1852 read no further, Fortuna will give a /dev/random that works
1853 like it always used to, and the difference will be irrelevant.
1855 If you remove 'device random', you get *NO* kernel-processed
1856 entropy at all. This may be acceptable to folks building
1857 embedded systems, but has complications. Carry on reading,
1858 and it is assumed you know what you need.
1860 *PLEASE* read random(4) and random(9) if you are in the
1861 habit of tweaking kernel configs, and/or if you are a member
1862 of the embedded community, wanting specific and not-usual
1863 behaviour from your security subsystems.
1865 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1866 random', you will NOT have a functioning /dev/random, and
1867 many cryptographic features will not work, including SSH.
1868 You may also find strange behaviour from the random(3) set
1869 of library functions, in particular sranddev(3), srandomdev(3)
1870 and arc4random(3). The reason for this is that the KERN_ARND
1871 sysctl only returns entropy if it thinks it has some to
1872 share, and with RANDOM_DUMMY or no 'device random' this
1876 An additional fix for the issue described in the 20150614 sendmail
1877 entry below has been committed in revision 284717.
1880 FreeBSD's old make (fmake) has been removed from the system. It is
1881 available as the devel/fmake port or via pkg install fmake.
1884 The fix for the issue described in the 20150614 sendmail entry
1885 below has been committed in revision 284436. The work
1886 around described in that entry is no longer needed unless the
1887 default setting is overridden by a confDH_PARAMETERS configuration
1888 setting of '5' or pointing to a 512 bit DH parameter file.
1891 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1892 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1893 and devel/kyua to version 0.20+ and adjust any calling code to work
1894 with Kyuafile and kyua.
1897 The import of openssl to address the FreeBSD-SA-15:10.openssl
1898 security advisory includes a change which rejects handshakes
1899 with DH parameters below 768 bits. sendmail releases prior
1900 to 8.15.2 (not yet released), defaulted to a 512 bit
1901 DH parameter setting for client connections. To work around
1902 this interoperability, sendmail can be configured to use a
1903 2048 bit DH parameter by:
1905 1. Edit /etc/mail/`hostname`.mc
1906 2. If a setting for confDH_PARAMETERS does not exist or
1907 exists and is set to a string beginning with '5',
1908 replace it with '2'.
1909 3. If a setting for confDH_PARAMETERS exists and is set to
1910 a file path, create a new file with:
1911 openssl dhparam -out /path/to/file 2048
1912 4. Rebuild the .cf file:
1913 cd /etc/mail/; make; make install
1914 5. Restart sendmail:
1915 cd /etc/mail/; make restart
1917 A sendmail patch is coming, at which time this file will be
1921 Generation of legacy formatted entries have been disabled by default
1922 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1923 entries were converted to use the new format by default when the new,
1924 machine independent format have been added and supported since FreeBSD
1927 Please see the pwd_mkdb(8) manual page for further details.
1930 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1931 20141231 entry below for information about prerequisites and upgrading,
1932 if you are not already using 3.5.0 or higher.
1935 TI platform code switched to using vendor DTS files and this update
1936 may break existing systems running on Beaglebone, Beaglebone Black,
1939 - dtb files should be regenerated/reinstalled. Filenames are the
1940 same but content is different now
1941 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1942 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1943 addressing scheme is now pin 25 on /dev/gpioc3.
1944 - Pandaboard: /etc/ttys should be updated, serial console device is
1945 now /dev/ttyu2, not /dev/ttyu0
1948 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1949 If you need the GNU extension from groff soelim(1), install groff
1950 from package: pkg install groff, or via ports: textproc/groff.
1953 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1954 defined in symlink(7); previously symlinks were silently ignored.
1957 The const qualifier has been removed from iconv(3) to comply with
1958 POSIX. The ports tree is aware of this from r384038 onwards.
1961 Libraries specified by LIBADD in Makefiles must have a corresponding
1962 DPADD_<lib> variable to ensure correct dependencies. This is now
1963 enforced in src.libnames.mk.
1966 From legacy ata(4) driver was removed support for SATA controllers
1967 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1968 Kernel modules ataahci and ataadaptec were removed completely,
1969 replaced by ahci and mvs modules respectively.
1972 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1973 the 20141231 entry below for information about prerequisites and
1974 upgrading, if you are not already using 3.5.0 or higher.
1977 The 32-bit PowerPC kernel has been changed to a position-independent
1978 executable. This can only be booted with a version of loader(8)
1979 newer than January 31, 2015, so make sure to update both world and
1980 kernel before rebooting.
1983 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1984 but before r278950, the RNG was not seeded properly. Immediately
1985 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1986 ssh keys or openssl keys) that were generated w/ a kernel from that
1987 range. This does not affect programs that directly used /dev/random
1988 or /dev/urandom. All userland uses of arc4random(3) are affected.
1991 The autofs(4) ABI was changed in order to restore binary compatibility
1992 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1993 with the new kernel.
1996 The powerpc64 kernel has been changed to a position-independent
1997 executable. This can only be booted with a new version of loader(8),
1998 so make sure to update both world and kernel before rebooting.
2001 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
2002 only release, no new features have been added. Please see the 20141231
2003 entry below for information about prerequisites and upgrading, if you
2004 are not already using 3.5.0.
2007 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
2008 taken from the ELF Tool Chain project rather than GNU binutils. They
2009 should be drop-in replacements, with the addition of arm64 support.
2010 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
2011 binutils tools, if necessary. See 20150805 for updated information.
2014 The default Unbound configuration now enables remote control
2015 using a local socket. Users who have already enabled the
2016 local_unbound service should regenerate their configuration
2017 by running "service local_unbound setup" as root.
2020 The GNU texinfo and GNU info pages have been removed.
2021 To be able to view GNU info pages please install texinfo from ports.
2024 Clang, llvm and lldb have been upgraded to 3.5.0 release.
2026 As of this release, a prerequisite for building clang, llvm and lldb is
2027 a C++11 capable compiler and C++11 standard library. This means that to
2028 be able to successfully build the cross-tools stage of buildworld, with
2029 clang as the bootstrap compiler, your system compiler or cross compiler
2030 should either be clang 3.3 or later, or gcc 4.8 or later, and your
2031 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
2034 On any standard FreeBSD 10.x or 11.x installation, where clang and
2035 libc++ are on by default (that is, on x86 or arm), this should work out
2038 On 9.x installations where clang is enabled by default, e.g. on x86 and
2039 powerpc, libc++ will not be enabled by default, so libc++ should be
2040 built (with clang) and installed first. If both clang and libc++ are
2041 missing, build clang first, then use it to build libc++.
2043 On 8.x and earlier installations, upgrade to 9.x first, and then follow
2044 the instructions for 9.x above.
2046 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
2047 default, and do not build clang.
2049 Many embedded systems are resource constrained, and will not be able to
2050 build clang in a reasonable time, or in some cases at all. In those
2051 cases, cross building bootable systems on amd64 is a workaround.
2053 This new version of clang introduces a number of new warnings, of which
2054 the following are most likely to appear:
2058 This warns in two cases, for both C and C++:
2059 * When the code is trying to take the absolute value of an unsigned
2060 quantity, which is effectively a no-op, and almost never what was
2061 intended. The code should be fixed, if at all possible. If you are
2062 sure that the unsigned quantity can be safely cast to signed, without
2063 loss of information or undefined behavior, you can add an explicit
2064 cast, or disable the warning.
2066 * When the code is trying to take an absolute value, but the called
2067 abs() variant is for the wrong type, which can lead to truncation.
2068 If you want to disable the warning instead of fixing the code, please
2069 make sure that truncation will not occur, or it might lead to unwanted
2072 -Wtautological-undefined-compare and
2073 -Wundefined-bool-conversion
2075 These warn when C++ code is trying to compare 'this' against NULL, while
2076 'this' should never be NULL in well-defined C++ code. However, there is
2077 some legacy (pre C++11) code out there, which actively abuses this
2078 feature, which was less strictly defined in previous C++ versions.
2080 Squid and openjdk do this, for example. The warning can be turned off
2081 for C++98 and earlier, but compiling the code in C++11 mode might result
2082 in unexpected behavior; for example, the parts of the program that are
2083 unreachable could be optimized away.
2086 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
2087 kernel sources have been removed. The .h files remain, since some
2088 utilities include them. This will need to be fixed later.
2089 If "mount -t oldnfs ..." is attempted, it will fail.
2090 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
2091 the utilities will report errors.
2094 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
2095 directories to top level SUBDIR variable when their parent
2096 directory is included in LOCAL_DIRS. Users with build systems with
2097 such hierarchies and without SUBDIR entries in the parent
2098 directory Makefiles should add them or add the directories to
2102 faith(4) and faithd(8) have been removed from the base system. Faith
2103 has been obsolete for a very long time.
2106 vt(4), the new console driver, is enabled by default. It brings
2107 support for Unicode and double-width characters, as well as
2108 support for UEFI and integration with the KMS kernel video
2111 You may need to update your console settings in /etc/rc.conf,
2112 most probably the keymap. During boot, /etc/rc.d/syscons will
2113 indicate what you need to do.
2115 vt(4) still has issues and lacks some features compared to
2116 syscons(4). See the wiki for up-to-date information:
2117 https://wiki.freebsd.org/Newcons
2119 If you want to keep using syscons(4), you can do so by adding
2120 the following line to /boot/loader.conf:
2124 pjdfstest has been integrated into kyua as an opt-in test suite.
2125 Please see share/doc/pjdfstest/README for more details on how to
2129 gperf has been removed from the base system for architectures
2130 that use clang. Ports that require gperf will obtain it from the
2134 pjdfstest has been moved from tools/regression/pjdfstest to
2138 At svn r271982, The default linux compat kernel ABI has been adjusted
2139 to 2.6.18 in support of the linux-c6 compat ports infrastructure
2140 update. If you wish to continue using the linux-f10 compat ports,
2141 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
2142 encouraged to update their linux-compat packages to linux-c6 during
2143 their next update cycle.
2146 The ofwfb driver, used to provide a graphics console on PowerPC when
2147 using vt(4), no longer allows mmap() of all physical memory. This
2148 will prevent Xorg on PowerPC with some ATI graphics cards from
2149 initializing properly unless x11-servers/xorg-server is updated to
2153 The xdev targets have been converted to using TARGET and
2154 TARGET_ARCH instead of XDEV and XDEV_ARCH.
2157 The default unbound configuration has been modified to address
2158 issues with reverse lookups on networks that use private
2159 address ranges. If you use the local_unbound service, run
2160 "service local_unbound setup" as root to regenerate your
2161 configuration, then "service local_unbound reload" to load the
2165 The GNU texinfo and GNU info pages are not built and installed
2166 anymore, WITH_INFO knob has been added to allow to built and install
2168 UPDATE: see 20150102 entry on texinfo's removal
2171 The GNU readline library is now an INTERNALLIB - that is, it is
2172 statically linked into consumers (GDB and variants) in the base
2173 system, and the shared library is no longer installed. The
2174 devel/readline port is available for third party software that
2178 The Itanium architecture (ia64) has been removed from the list of
2179 known architectures. This is the first step in the removal of the
2183 Commit r268115 has added NFSv4.1 server support, merged from
2184 projects/nfsv4.1-server. Since this includes changes to the
2185 internal interfaces between the NFS related modules, a full
2186 build of the kernel and modules will be necessary.
2187 __FreeBSD_version has been bumped.
2190 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
2191 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
2192 which differs from the behaviour controlled by this knob.)
2195 Maximal length of the serial number in CTL was increased from 16 to
2196 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
2197 and ctld, need to be rebuilt to work with a new kernel.
2200 The libatf-c and libatf-c++ major versions were downgraded to 0 and
2201 1 respectively to match the upstream numbers. They were out of
2202 sync because, when they were originally added to FreeBSD, the
2203 upstream versions were not respected. These libraries are private
2204 and not yet built by default, so renumbering them should be a
2205 non-issue. However, unclean source trees will yield broken test
2206 programs once the operator executes "make delete-old-libs" after a
2207 "make installworld".
2209 Additionally, the atf-sh binary was made private by moving it into
2210 /usr/libexec/. Already-built shell test programs will keep the
2211 path to the old binary so they will break after "make delete-old"
2214 If you are using WITH_TESTS=yes (not the default), wipe the object
2215 tree and rebuild from scratch to prevent spurious test failures.
2216 This is only needed once: the misnumbered libraries and misplaced
2217 binaries have been added to OptionalObsoleteFiles.inc so they will
2218 be removed during a clean upgrade.
2221 Clang and llvm have been upgraded to 3.4.1 release.
2224 We bogusly installed src.opts.mk in /usr/share/mk. This file should
2225 be removed to avoid issues in the future (and has been added to
2229 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
2230 past, it affected all builds that used the bsd.*.mk files. The old
2231 behavior was a bug, but people may have relied upon it. To get this
2232 behavior back, you can .include /etc/src.conf from /etc/make.conf
2233 (which is still global and isn't changed). This also changes the
2234 behavior of incremental builds inside the tree of individual
2235 directories. Set MAKESYSPATH to ".../share/mk" to do that.
2236 Although this has survived make universe and some upgrade scenarios,
2237 other upgrade scenarios may have broken. At least one form of
2238 temporary breakage was fixed with MAKESYSPATH settings for buildworld
2239 as well... In cases where MAKESYSPATH isn't working with this
2240 setting, you'll need to set it to the full path to your tree.
2242 One side effect of all this cleaning up is that bsd.compiler.mk
2243 is no longer implicitly included by bsd.own.mk. If you wish to
2244 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
2248 The lindev device has been removed since /dev/full has been made a
2249 standard device. __FreeBSD_version has been bumped.
2252 The knob WITHOUT_VI was added to the base system, which controls
2253 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
2254 in order to reorder files share/termcap and didn't build ex(1) as a
2255 build tool, so building/installing with WITH_VI is highly advised for
2256 build hosts for older releases.
2258 This issue has been fixed in stable/9 and stable/10 in r277022 and
2259 r276991, respectively.
2262 The YES_HESIOD knob has been removed. It has been obsolete for
2263 a decade. Please move to using WITH_HESIOD instead or your builds
2264 will silently lack HESIOD.
2267 The uart(4) driver has been changed with respect to its handling
2268 of the low-level console. Previously the uart(4) driver prevented
2269 any process from changing the baudrate or the CLOCAL and HUPCL
2270 control flags. By removing the restrictions, operators can make
2271 changes to the serial console port without having to reboot.
2272 However, when getty(8) is started on the serial device that is
2273 associated with the low-level console, a misconfigured terminal
2274 line in /etc/ttys will now have a real impact.
2275 Before upgrading the kernel, make sure that /etc/ttys has the
2276 serial console device configured as 3wire without baudrate to
2277 preserve the previous behaviour. E.g:
2278 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
2281 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
2282 to improve performance. To re-enable it, if needed, run rpcbind
2283 with command line option -W.
2286 Switched back to the GPL dtc compiler due to updates in the upstream
2287 dts files not being supported by the BSDL dtc compiler. You will need
2288 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
2289 may result while building dtb files during a kernel build if you fail
2290 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
2293 Clang and llvm have been upgraded to 3.4 release.
2296 The nve(4) driver has been removed. Please use the nfe(4) driver
2297 for NVIDIA nForce MCP Ethernet adapters instead.
2300 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
2301 This could cause certain C++ applications using shared libraries built
2302 against the previous version of libc++ to crash. The incompatibility
2303 has now been fixed, but any C++ applications or shared libraries built
2304 between r261283 and r261801 should be recompiled.
2307 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
2308 capability mode support. Please note that enabling the feature in
2309 kernel is still highly recommended.
2312 OpenSSH is now built with sandbox support, and will use sandbox as
2313 the default privilege separation method. This requires Capsicum
2314 capability mode support in kernel.
2317 The libelf and libdwarf libraries have been updated to newer
2318 versions from upstream. Shared library version numbers for
2319 these two libraries were bumped. Any ports or binaries
2320 requiring these two libraries should be recompiled.
2321 __FreeBSD_version is bumped to 1100006.
2324 If a Makefile in a tests/ directory was auto-generating a Kyuafile
2325 instead of providing an explicit one, this would prevent such
2326 Makefile from providing its own Kyuafile in the future during
2327 NO_CLEAN builds. This has been fixed in the Makefiles but manual
2328 intervention is needed to clean an objdir if you use NO_CLEAN:
2329 # find /usr/obj -name Kyuafile | xargs rm -f
2332 The behavior of gss_pseudo_random() for the krb5 mechanism
2333 has changed, for applications requesting a longer random string
2334 than produced by the underlying enctype's pseudo-random() function.
2335 In particular, the random string produced from a session key of
2336 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
2337 be different at the 17th octet and later, after this change.
2338 The counter used in the PRF+ construction is now encoded as a
2339 big-endian integer in accordance with RFC 4402.
2340 __FreeBSD_version is bumped to 1100004.
2343 The WITHOUT_ATF build knob has been removed and its functionality
2344 has been subsumed into the more generic WITHOUT_TESTS. If you were
2345 using the former to disable the build of the ATF libraries, you
2346 should change your settings to use the latter.
2349 The default version of mtree is nmtree which is obtained from
2350 NetBSD. The output is generally the same, but may vary
2351 slightly. If you found you need identical output adding
2352 "-F freebsd9" to the command line should do the trick. For the
2353 time being, the old mtree is available as fmtree.
2356 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
2357 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
2358 1.1.4_8 and verify bsdyml not linked in, before running "make
2360 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
2362 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
2365 The stable/10 branch has been created in subversion from head
2372 Sometimes, obscure build problems are the result of environment
2373 poisoning. This can happen because the make utility reads its
2374 environment when searching for values for global variables. To run
2375 your build attempts in an "environmental clean room", prefix all make
2376 commands with 'env -i '. See the env(1) manual page for more details.
2377 Occasionally a build failure will occur with "make -j" due to a race
2378 condition. If this happens try building again without -j, and please
2379 report a bug if it happens consistently.
2381 When upgrading from one major version to another it is generally best to
2382 upgrade to the latest code in the currently installed branch first, then
2383 do an upgrade to the new branch. This is the best-tested upgrade path,
2384 and has the highest probability of being successful. Please try this
2385 approach if you encounter problems with a major version upgrade. Since
2386 the stable 4.x branch point, one has generally been able to upgrade from
2387 anywhere in the most recent stable branch to head / current (or even the
2388 last couple of stable branches). See the top of this file when there's
2391 The update process will emit an error on an attempt to perform a build
2392 or install from a FreeBSD version below the earliest supported version.
2393 When updating from an older version the update should be performed one
2394 major release at a time, including running `make delete-old` at each
2397 When upgrading a live system, having a root shell around before
2398 installing anything can help undo problems. Not having a root shell
2399 around can lead to problems if pam has changed too much from your
2400 starting point to allow continued authentication after the upgrade.
2402 This file should be read as a log of events. When a later event changes
2403 information of a prior event, the prior event should not be deleted.
2404 Instead, a pointer to the entry with the new information should be
2405 placed in the old entry. Readers of this file should also sanity check
2406 older entries before relying on them blindly. Authors of new entries
2407 should write them with this in mind.
2411 When upgrading the boot ZFS pool to a new version, always follow
2414 1.) recompile and reinstall the ZFS boot loader and boot block
2415 (this is part of "make buildworld" and "make installworld")
2417 2.) update the ZFS boot block on your boot drive
2419 The following example updates the ZFS boot block on the
2420 freebsd-boot partition of a GPT partitioned drive ada0:
2421 "gpart bootcode -p /boot/gptzfsboot -i $N ada0"
2422 The value $N will typically be 1 (if booting from BIOS) or 2 (if
2425 Non-boot pools do not need these updates.
2429 If you are updating from a prior version of FreeBSD (even one just
2430 a few days old), you should follow this procedure. It is the most
2431 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2433 make kernel-toolchain
2434 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2435 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2437 To test a kernel once
2438 ---------------------
2439 If you just want to boot a kernel once (because you are not sure
2440 if it works, or if you want to boot a known bad kernel to provide
2441 debugging information) run
2442 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2443 nextboot -k testkernel
2445 To rebuild everything and install it on the current system.
2446 -----------------------------------------------------------
2447 # Note: sometimes if you are running current you gotta do more than
2448 # is listed here if you are upgrading from a really old current.
2450 <make sure you have good level 0 dumps>
2452 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2453 make installkernel KERNCONF=YOUR_KERNEL_HERE
2455 <reboot in single user> [3]
2462 To cross-install current onto a separate partition
2463 --------------------------------------------------
2464 # In this approach we use a separate partition to hold
2465 # current's root, 'usr', and 'var' directories. A partition
2466 # holding "/", "/usr" and "/var" should be about 2GB in
2469 <make sure you have good level 0 dumps>
2472 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2473 <maybe newfs current's root partition>
2474 <mount current's root partition on directory ${CURRENT_ROOT}>
2475 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
2476 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2477 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2478 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2479 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2480 <reboot into current>
2481 <do a "native" rebuild/install as described in the previous section>
2482 <maybe install compatibility libraries from ports/misc/compat*>
2486 To upgrade in-place from stable to current
2487 ----------------------------------------------
2488 <make sure you have good level 0 dumps>
2490 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
2491 make installkernel KERNCONF=YOUR_KERNEL_HERE
2493 <reboot in single user> [3]
2500 Make sure that you've read the UPDATING file to understand the
2501 tweaks to various things you need. At this point in the life
2502 cycle of current, things change often and you are on your own
2503 to cope. The defaults can also change, so please read ALL of
2504 the UPDATING entries.
2506 Also, if you are tracking -current, you must be subscribed to
2507 freebsd-current@freebsd.org. Make sure that before you update
2508 your sources that you have read and understood all the recent
2509 messages there. If in doubt, please track -stable which has
2510 much fewer pitfalls.
2512 [1] If you have third party modules, such as vmware, you should disable
2513 them at this point so they don't crash your system on
2514 reboot. Alternatively, you should rebuild all the modules you have in
2515 your system and install them as well. If you are running -current, you
2516 should seriously consider placing all sources to all the modules for
2517 your system (or symlinks to them) in /usr/local/sys/modules so this
2518 happens automatically. If all your modules come from ports, then adding
2519 the port origin directories to PORTS_MODULES instead is also automatic
2521 PORTS_MODULES+=x11/nvidia-driver
2523 [3] From the bootblocks, boot -s, and then do
2527 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed
2528 cd src # full path to source
2529 adjkerntz -i # if CMOS is wall time
2530 Also, when doing a major release upgrade, it is required that you boot
2531 into single user mode to do the installworld.
2533 [4] Note: This step is non-optional. Failure to do this step
2534 can result in a significant reduction in the functionality of the
2535 system. Attempting to do it by hand is not recommended and those
2536 that pursue this avenue should read this file carefully, as well
2537 as the archives of freebsd-current and freebsd-hackers mailing lists
2538 for potential gotchas. The -U option is also useful to consider.
2539 See mergemaster(8) for more information.
2541 [5] Usually this step is a no-op. However, from time to time
2542 you may need to do this if you get unknown user in the following
2543 step. It never hurts to do it all the time. You may need to
2544 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2545 install) after the buildworld before this step if you last updated
2546 from current before 20130425 or from -stable before 20130430.
2548 [6] This only deletes old files and directories. Old libraries
2549 can be deleted by "make delete-old-libs", but you have to make
2550 sure that no program is using those libraries anymore.
2552 [8] The new kernel must be able to run existing binaries used by an
2553 installworld. When upgrading across major versions, the new kernel's
2554 configuration must include the correct COMPAT_FREEBSD<n> option for
2555 existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure
2556 to do so may leave you with a system that is hard to boot to recover. A
2557 GENERIC kernel will include suitable compatibility options to run
2558 binaries from older branches. Note that the ability to run binaries
2559 from unsupported branches is not guaranteed.
2561 Make sure that you merge any new devices from GENERIC since the
2562 last time you updated your kernel config file. Options also
2563 change over time, so you may need to adjust your custom kernels
2566 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2567 "?=" instead of the "=" assignment operator, so that buildworld can
2568 override the CPUTYPE if it needs to.
2570 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2571 not on the command line, or in /etc/make.conf. buildworld will
2572 warn if it is improperly defined.
2575 This file contains a list, in reverse chronological order, of major
2576 breakages in tracking -current. It is not guaranteed to be a complete
2577 list of such breakages, and only contains entries since September 23, 2011.
2578 If you need to see UPDATING entries from before that date, you will need
2579 to fetch an UPDATING file from an older FreeBSD release.
2581 Copyright information:
2583 Copyright 1998-2009 M. Warner Losh <imp@FreeBSD.org>
2585 Redistribution, publication, translation and use, with or without
2586 modification, in full or in part, in any form or format of this
2587 document are permitted without further permission from the author.
2589 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2590 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2591 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2592 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2593 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2594 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2595 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2596 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2597 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2598 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2599 POSSIBILITY OF SUCH DAMAGE.
2601 Contact Warner Losh if you have any questions about your use of