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