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.2-RELEASE-p5 EN-23:13.freebsd-update
21 freebsd-update does not handle deep boot environments [EN-23:13.freebsd-update]
23 Incorrect regular expression escape handling [EN-23:14.regcomp]
25 libc stdio buffer overflow [SA-23:15.stdio]
27 Incorrect libcap_net limitation list manipulation [SA-23:16.cap_net]
30 13.2-RELEASE-p4 FreeBSD-EN-23:12.freebsd-update
31 FreeBSD-SA-23:12.msdosfs
32 FreeBSD-SA-23:13.capsicum
33 FreeBSD-SA-23:14.smccc
35 freebsd-update to 14.0 fails [EN-23:12.freebsd-update]
37 Fix msdosfs data disclosure [SA-23:12.msdosfs]
39 copy_file_range insufficient capability rights check [SA-23:13.capsicum]
41 arm64 boot CPUs may lack speculative execution protections [SA-23:14.smccc]
44 13.2-RELEASE-p3 FreeBSD-EN-23:09.freebsd-update
46 FreeBSD-EN-23:11.caroot
50 freebsd-update incorrectly merges files on upgrade [EN-23:09.freebsd-update]
52 PCI-e hot-plug is broken with certain devices [EN-23:10.pci-update]
54 Root certificate bundle update [EN-23:11.caroot]
56 pf incorrectly handles multiple IPv6 fragment headers [SA-23:10.pf]
58 Wi-Fi encryption bypass [SA-23:11.wifi]
61 13.2-RELEASE-p2 FreeBSD-EN-23:08.vnet
63 FreeBSD-SA-23:07.bhyve
65 FreeBSD-SA-23:09.pam_krb5
67 VNET and DCPU modules panic on arm64 due to linker relaxation [EN-23:08.vnet]
69 Remote denial of service in IPv6 fragment reassembly [SA-23:06.ipv6]
71 bhyve privileged guest escape via fwctl [SA-23:07.bhyve]
73 Potential remote code execution via ssh-agent forwarding [SA-23:08.ssh]
75 Network authentication attack via pam_krb5 [SA-23:09.pam_krb5]
78 13.2-RELEASE-p1 FreeBSD-EN-23:06.loader
80 FreeBSD-SA-23:04.pam_krb5
82 x86 kernel console configuration [EN-23:06.loader]
84 Fix mpr(4) failure to initialize devices [EN-23:07.mpr]
86 Fix network authentication attack via pam_krb5 [SA-23:04.pam_krb5]
92 LinuxKPI pm.h changes require an update to the latest drm-kmod version
93 before re-compiling to avoid errors.
96 Bump __FreeBSD_verion to 1301501 after merging LinuxKPI and
97 net80211 changes in order to help out-of-tree consumers to deal
101 For 64-bit architectures the base system is now built with Position
102 Independent Executable (PIE) support enabled by default. It may be
103 disabled using the WITHOUT_PIE knob. A clean build is required.
106 The macros provided for the manipulation of CPU sets (e.g. CPU_AND)
107 have been modified to take 2 source arguments instead of only 1.
108 Externally maintained sources that use these macros will have to
109 be adapted. The FreeBSD version has been bumped to 1300524 to
113 Commit 18f5b477ee66 adds two arguments to VOP_ALLOCATE().
114 Normally changes to VOP calls are not MFC'd, but a
115 discussion on freebsd-current@ seemed to agree that
116 it was acceptable in this case, to fix the NFSv4.2 server.
117 Any out of source tree file system with a custom
118 VOP_ALLOCATE() call will need to be modified.
119 Bump __FreeBSD_version to 1300523 since the NFS modules need
120 to be rebuilt from sources.
123 Commit 6e8e261f0d4e changed the internal KAPI between the NFS
124 modules. As such, all the modules must be rebuilt from sources.
125 __FreeBSD_version has been bumped to 1300522.
128 Bump __FreeBSD_version to 1300521 after merging LinuxKPI and
129 net80211 changes in order to support building various wireless
130 drivers. This is to help other external consumers of LinuxKPI
131 and net80211 to deal accordingly.
134 Commit a599f9f7620b deleted the variable called nfs_maxcopyrange
135 from nfscommon.ko, since it no longer needs to be global. As such,
136 the other nfs modules must be rebuilt from up to date sources.
137 Bump __FreeBSD_version to 1300516 for this.
140 As of commit 622809b0868f OpenSSL no longer enables kernel TLS
141 by default. Users can enable kernel TLS via the "KTLS" SSL
142 option. This can be enabled globally by using a custom
143 OpenSSL config file via OPENSSL_CONF or via an
144 application-specific configuration option for applications
145 which permit setting SSL options via SSL_CONF_cmd(3).
148 Commits 9fb6e613373c and 9ec7dbf46b0a both changed the internal
149 KAPI between the NFS modules. Bump __FreeBSD_version to 1300514.
150 All NFS modules must be rebuilt from sources.
153 Commit b69019c14cd8 removes pf's DIOCGETSTATESNV ioctl.
154 As of be70c7a50d32 it is no longer used by userspace, but it does mean
155 users may not be able to enumerate pf states if they update the kernel
156 past c021ff986e2b without first updating userspace past be70c7a50d32.
159 Bump __FreeBSD_version to 1300512 after merging LinuxKPI, OFED,
160 net80211, and driver changes in order to support building
161 Intel wireless iwlwifi drivers. This is especially needed for
162 drm-kmod which needs updates after this.
165 The 20210707 awk update brought in a change in behavior. This has
166 been corrected as of d4d252c49976. Between these dates, if you
167 installed a new awk binary, you may not be able to build a new
168 kernel because the change in behavior affected the genoffset
169 script used to build the kernel. If you did update, the fix is
170 to update your sources past the above hash and do
173 % sudo -E make install
174 to enable building kernels again.
177 Commit 8a04edfdcbd2 changes the default minor version
178 used for NFSv4 mounts to the highest minor version supported
179 by the NFSv4 server. This default can be overridden by using
180 the "minorversion" mount option.
181 The consensus of a discussion on freebsd-current@ indicated
182 that this would be acceptable to do and would not be considered
186 awk has been updated to the latest one-true-awk version 20210215.
187 This contains a number of minor bug fixes.
190 Commit ca179c4d74f2/632e3f2f3a66 changed the package in which
191 the OpenSSL libraries and utilities are packaged.
192 It is recommended for pkgbase user to do:
193 pkg install -f FreeBSD-openssl
194 before pkg upgrade otherwise some dependencies might not be met
195 and pkg will stop working as libssl will not be present anymore
199 Commit 841006678745 changed the internal KAPI between the krpc
200 and nfsd modules. As such, they must both be rebuilt from
202 __FreeBSD_version is bumped to 1300510.
205 Commit 272f39942254 changed the internal KAPI between the
206 nscl.ko and nfscommon.ko modules, so they both need to be
207 rebuilt from sources.
210 Commit 5a45802b3c8c changed the internal KAPI between
211 the krpc and NFS. As such, the krpc, nfscommon and
212 nfscl modules must all be rebuilt from sources.
213 Without this patch, NFSv4.1/4.2 mounts should not
214 be done with the nfscbd(8) daemon running, to avoid
215 needing a working back channel for server->client RPCs.
218 Various LinuxKPI functionality was added which conflicts with DRM.
219 Please update your drm-kmod port to after the __FreeBSD_verison 1300139
223 The stable/13 branch has been created from main.
226 PC Card attachments for all devices have been removed. In the case of
227 wi and cmx, the entire drivers were removed because they were only
228 PC Card devices. FreeBSD_version 1300134 should be used for this
229 since it was bumped so recently.
232 Transport-independent parts of HID support have been split off the USB
233 code in to separate subsystem. Kernel configs which include one of
234 ums, ukbd, uhid, atp, wsp, wmt, uaudio, ugold or ucycom drivers should
235 be updated with adding of "device hid" line.
238 ncurses installation has been modified to only keep the widechar
239 enabled version. Incremental build is broken for that change, so it
240 requires a clean build.
243 The FreeBSD project has migrated from Subversion to Git. Temporary
244 instructions can be found at
245 https://github.com/bsdimp/freebsd-git-docs/blob/main/src-cvt.md
246 and other documents in that repo.
249 The services database has been updated to cover more of the basic
250 services expected in a modern system. The database is big enough
251 that it will cause issues in mergemaster in Releases previous to
252 12.2 and 11.3, or in very old current systems from before r358154.
255 Obsolete in-tree GDB 6.1.1 has been removed. GDB (including kgdb)
256 may be installed from ports or packages.
259 ping6 has been merged into ping. It can now be called as "ping -6".
260 See ping(8) for details.
263 Default value of net.add_addr_allfibs has been changed to 0.
264 If you have multi-fib configuration and rely on existence of all
265 interface routes in every fib, you need to set the above sysctl to 1.
267 The internal pre-processor in the calendar(1) program has been
268 extended to support more C pre-processor commands (e.g. #ifdef, #else,
269 and #undef) and to detect unbalanced conditional statements.
270 Error messages have been extended to include the filename and line
271 number if processing stops to help fixing malformed data files.
274 All the data files for the calendar(1) program, except calendar.freebsd,
275 have been moved to the deskutils/calendar-data port, much like the
276 jewish calendar entries were moved to deskutils/hebcal years ago. After
277 make delete-old-files, you need to install it to retain full
278 functionality. calendar(1) will issue a reminder for files it can't
282 LINT files are no longer generated. We now include the relevant NOTES
283 files. Note: This may cause conflicts with updating in some cases.
284 find sys -name LINT\* -delete
285 is suggested across this commit to remove the generated LINT files.
287 If you have tried to update with generated files there, the svn
288 command you want to un-auger the tree is
291 and then do the above find from the top level. Substitute 'amd64'
292 above with where the error message indicates a conflict.
295 OpenZFS support has been integrated. Do not upgrade root pools until
296 the loader is updated to support zstd. Furthermore, we caution against
297 'zpool upgrade' for the next few weeks. The change should be transparent
298 unless you want to use new features.
300 Not all "NO_CLEAN" build scenarios work across these changes. Many
301 scenarios have been tested and fixed, but rebuilding kernels without
302 rebuilding world may fail.
304 The ZFS cache file has moved from /boot to /etc to match the OpenZFS
305 upstream default. A fallback to /boot has been added for mountroot.
307 Pool auto import behavior at boot has been moved from the kernel module
308 to an explicit "zpool import -a" in one of the rc scripts enabled by
309 zfs_enable=YES. This means your non-root zpools won't auto import until
310 you upgrade your /etc/rc.d files.
313 The resume code now notifies devd with the 'kernel' system
314 rather than the old 'kern' subsystem to be consistent with
315 other use. The old notification will be created as well, but
316 will be removed prior to FreeBSD 14.0.
319 r362275 changed the internal API between the kernel RPC and the
320 NFS modules. As such, all the modules must be recompiled from
324 r364330 modified the internal API used between the NFS modules.
325 As such, all the NFS modules must be re-compiled from sources.
328 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
329 been upgraded to 11.0.0. Please see the 20141231 entry below for
330 information about prerequisites and upgrading, if you are not already
331 using clang 3.5.0 or higher.
334 r364092 modified the internal ABI used between the kernel NFS
335 modules. As such, all of these modules need to be rebuilt
336 from sources, so a version bump was done.
339 Makefile.inc has been updated to work around the issue documented in
340 20200729. It was a case where the optimization of using symbolic links
341 to point to binaries created a situation where we'd run new binaries
342 with old libraries starting midway through the installworld process.
345 r363679 has redefined some undefined behavior in regcomp(3); notably,
346 extraneous escapes of most ordinary characters will no longer be
347 accepted. An exp-run has identified all of the problems with this in
348 ports, but other non-ports software may need extra escapes removed to
349 continue to function.
351 Because of this change, installworld may encounter the following error
352 from rtld: Undefined symbol "regcomp@FBSD_1.6" -- It is imperative that
353 you do not halt installworld. Instead, let it run to completion (whether
354 successful or not) and run installworld once more.
357 A new implementation of bc and dc has been imported in r362681. This
358 implementation corrects non-conformant behavior of the previous bc
359 and adds GNU bc compatible options. It offers a number of extensions,
360 is much faster on large values, and has support for message catalogs
361 (a number of languages are already supported, contributions of further
362 languages welcome). The option WITHOUT_GH_BC can be used to build the
363 world with the previous versions of bc and dc.
366 r362639 changed the internal API used between the NFS kernel modules.
367 As such, they all need to be rebuilt from sources.
370 r362158 changed the arguments for VFS_CHECKEXP(). As such, any
371 out of tree file systems need to be modified and rebuilt.
372 Also, any file systems that are modules must be rebuilt.
375 read(2) of a directory fd is now rejected by default. root may
376 re-enable it for system root only on non-ZFS filesystems with the
377 security.bsd.allow_read_dir sysctl(8) MIB if
378 security.bsd.suser_enabled=1.
380 It may be advised to setup aliases for grep to default to `-d skip` if
381 commonly non-recursively grepping a list that includes directories and
382 the potential for the resulting stderr output is not tolerable. Example
383 aliases are now installed, commented out, in /root/.cshrc and
387 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
388 been upgraded to 10.0.1. Please see the 20141231 entry below for
389 information about prerequisites and upgrading, if you are not already
390 using clang 3.5.0 or higher.
393 Support for obsolete compilers has been removed from the build system.
394 Clang 6 and GCC 6.4 are the minimum supported versions.
397 closefrom(2) has been moved under COMPAT12, and replaced in libc with a
398 stub that calls close_range(2). If using a custom kernel configuration,
399 you may want to ensure that the COMPAT_FREEBSD12 option is included, as
400 a slightly older -CURRENT userland and older FreeBSD userlands may not
401 be functional without closefrom(2).
404 Upstream DTS from Linux 5.6 was merged and they now have the SID
405 and THS (Secure ID controller and THermal Sensor) node present.
406 The DTB overlays have now been removed from the tree for the H3/H5 and
407 A64 SoCs and the aw_sid and aw_thermal driver have been updated to
408 deal with upstream DTS. If you are using those overlays you need to
409 remove them from loader.conf and update the DTBs on the FAT partition.
412 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
413 been upgraded to 10.0.0. Please see the 20141231 entry below for
414 information about prerequisites and upgrading, if you are not already
415 using clang 3.5.0 or higher.
418 The amd(8) automount daemon has been removed from the source tree.
419 As of FreeBSD 10.1 autofs(5) is the preferred tool for automounting.
420 amd is still available in the sysutils/am-utils port.
423 Removed brooktree driver (bktr.4) from the tree.
426 The WITH_GPL_DTC option has been removed. The BSD-licenced device tree
427 compiler in usr.bin/dtc is used on all architectures which use dtc, and
428 the GPL dtc is available (if needed) from the sysutils/dtc port.
431 The WITHOUT_LLVM_LIBUNWIND option has been removed. LLVM's libunwind
432 is used by all supported CPU architectures.
435 GCC 4.2.1 has been removed from the tree. The WITH_GCC,
436 WITH_GCC_BOOTSTRAP, and WITH_GNUCXX options are no longer available.
437 Users who wish to build FreeBSD with GCC must use the external toolchain
441 ncurses has been updated to a newer version (6.2-20200215). Given the ABI
442 has changed, users will have to rebuild all the ports that are linked to
446 The size of struct vnet and the magic cookie have changed.
447 Users need to recompile libkvm and all modules using VIMAGE
448 together with their new kernel.
451 Defining the long deprecated NO_CTF, NO_DEBUG_FILES, NO_INSTALLLIB,
452 NO_MAN, NO_PROFILE, and NO_WARNS variables is now an error. Update
453 your Makefiles and scripts to define MK_<var>=no instead as required.
455 One exception to this is that program or library Makefiles should
456 define MAN to empty rather than setting MK_MAN=no.
459 Clang/LLVM is now the default compiler and LLD the default
463 make universe no longer uses GCC 4.2.1 on any architectures.
464 Architectures not supported by in-tree Clang/LLVM require an
465 external toolchain package.
468 GCC 4.2.1 is now not built by default, as part of the GCC 4.2.1
469 retirement plan. Specifically, the GCC, GCC_BOOTSTRAP, and GNUCXX
470 options default to off for all supported CPU architectures. As a
471 short-term transition aid they may be enabled via WITH_* options.
472 GCC 4.2.1 is expected to be removed from the tree on 2020-03-31.
475 Support for armv5 has been disconnected and is being removed. The
476 machine combination MACHINE=arm MACHINE_ARCH=arm is no longer valid.
477 You must now use a MACHINE_ARCH of armv6 or armv7. The default
478 MACHINE_ARCH for MACHINE=arm is now armv7.
481 Clang/LLVM is now the default compiler for all powerpc architectures.
482 LLD is now the default linker for powerpc64. The change for powerpc64
483 also includes a change to the ELFv2 ABI, incompatible with the existing
487 Kernel-loadable random(4) modules are no longer unloadable.
490 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
491 been upgraded to 9.0.1. Please see the 20141231 entry below for
492 information about prerequisites and upgrading, if you are not already
493 using clang 3.5.0 or higher.
496 r355677 has modified the internal interface used between the
497 NFS modules in the kernel. As such, they must all be upgraded
498 simultaneously. I will do a version bump for this.
501 The root certificates of the Mozilla CA Certificate Store have been
502 imported into the base system and can be managed with the certctl(8)
503 utility. If you have installed the security/ca_root_nss port or package
504 with the ETCSYMLINK option (the default), be advised that there may be
505 differences between those included in the port and those included in
506 base due to differences in nss branch used as well as general update
507 frequency. Note also that certctl(8) cannot manage certs in the
508 format used by the security/ca_root_nss port.
511 The amd(8) automount daemon has been disabled by default, and will be
512 removed in the future. As of FreeBSD 10.1 the autofs(5) is available
516 The nctgpio and wbwd drivers have been moved to the superio bus.
517 If you have one of these drivers in a kernel configuration, then
518 you should add device superio to it. If you use one of these drivers
519 as a module and you compile a custom set of modules, then you should
520 add superio to the set.
523 KPIs for network drivers to access interface addresses have changed.
524 Users need to recompile NIC driver modules together with kernel.
527 The net.link.tap.user_open sysctl no longer prevents user opening of
528 already created /dev/tapNN devices. Access is still controlled by
529 node permissions, just like tun devices. The net.link.tap.user_open
530 sysctl is now used only to allow users to perform devfs cloning of
531 tap devices, and the subsequent open may not succeed if the user is not
532 in the appropriate group. This sysctl may be deprecated/removed
533 completely in the future.
536 mips, powerpc, and sparc64 are no longer built as part of
537 universe / tinderbox unless MAKE_OBSOLETE_GCC is defined. If
538 not defined, mips, powerpc, and sparc64 builds will look for
539 the xtoolchain binaries and if installed use them for universe
540 builds. As llvm 9.0 becomes vetted for these architectures, they
541 will be removed from the list.
544 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
545 been upgraded to 9.0.0. Please see the 20141231 entry below for
546 information about prerequisites and upgrading, if you are not already
547 using clang 3.5.0 or higher.
550 The hpt27xx, hptmv, hptnr, and hptrr drivers have been removed from
551 GENERIC. They are available as modules and can be loaded by adding
552 to /boot/loader.conf hpt27xx_load="YES", hptmv_load="YES",
553 hptnr_load="YES", or hptrr_load="YES", respectively.
556 ntpd no longer by default locks its pages in memory, allowing them
557 to be paged out by the kernel. Use rlimit memlock to restore
558 historic BSD behaviour. For example, add "rlimit memlock 32"
559 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
562 Several of ping6's options have been renamed for better consistency
563 with ping. If you use any of -ARWXaghmrtwx, you must update your
564 scripts. See ping6(8) for details.
567 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
568 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
569 been removed from mount_fusefs(8). You can safely remove them from
570 your scripts, because they had no effect.
572 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
573 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
574 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
575 sysctls have been removed. If you felt the need to set any of them to
576 a non-default value, please tell asomers@FreeBSD.org why.
579 Default permissions on the /var/account/acct file (and copies of it
580 rotated by periodic daily scripts) are changed from 0644 to 0640
581 because the file contains sensitive information that should not be
582 world-readable. If the /var/account directory must be created by
583 rc.d/accounting, the mode used is now 0750. Admins who use the
584 accounting feature are encouraged to change the mode of an existing
585 /var/account directory to 0750 or 0700.
588 Entropy collection and the /dev/random device are no longer optional
589 components. The "device random" option has been removed.
590 Implementations of distilling algorithms can still be made loadable
591 with "options RANDOM_LOADABLE" (e.g., random_fortuna.ko).
594 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
595 been upgraded to 8.0.1. Please see the 20141231 entry below for
596 information about prerequisites and upgrading, if you are not already
597 using clang 3.5.0 or higher.
600 A fix was applied to i386 kernel modules to avoid panics with
601 dpcpu or vnet. Users need to recompile i386 kernel modules
602 having pcpu or vnet sections or they will refuse to load.
605 User-wired pages now have their own counter,
606 vm.stats.vm.v_user_wire_count. The vm.max_wired sysctl was renamed
607 to vm.max_user_wired and changed from an unsigned int to an unsigned
608 long. bhyve VMs wired with the -S are now subject to the user
609 wiring limit; the vm.max_user_wired sysctl may need to be tuned to
610 avoid running into the limit.
613 The IPSEC option has been removed from GENERIC. Users requiring
614 ipsec(4) must now load the ipsec(4) kernel module.
617 The tap(4) driver has been folded into tun(4), and the module has been
618 renamed to tuntap. You should update any kld_list="if_tap" or
619 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
620 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
621 module instead, and "device tap" or "device tun" entries in kernel
622 config files to select the tuntap device instead.
625 The following knobs have been added related to tradeoffs between
626 safe use of the random device and availability in the absence of
629 kern.random.initial_seeding.bypass_before_seeding: tunable; set
630 non-zero to bypass the random device prior to seeding, or zero to
631 block random requests until the random device is initially seeded.
632 For now, set to 1 (unsafe) by default to restore pre-r346250 boot
633 availability properties.
635 kern.random.initial_seeding.read_random_bypassed_before_seeding:
636 read-only diagnostic sysctl that is set when bypass is enabled and
637 read_random(9) is bypassed, to enable programmatic handling of this
638 initial condition, if desired.
640 kern.random.initial_seeding.arc4random_bypassed_before_seeding:
641 Similar to the above, but for arc4random(9) initial seeding.
643 kern.random.initial_seeding.disable_bypass_warnings: tunable; set
644 non-zero to disable warnings in dmesg when the same conditions are
645 met as for the diagnostic sysctls above. Defaults to zero, i.e.,
646 produce warnings in dmesg when the conditions are met.
649 The loadable random module KPI has changed; the random_infra_init()
650 routine now requires a 3rd function pointer for a bool (*)(void)
651 method that returns true if the random device is seeded (and
652 therefore unblocked).
655 r345895 reverts r320698. This implies that an nfsuserd(8) daemon
656 built from head sources between r320757 (July 6, 2017) and
657 r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
658 is added to the command line.
659 nfsuserd daemons built from head sources that are post-r338192 are
660 not affected and should continue to work.
663 The fuse(4) module has been renamed to fusefs(4) for consistency with
664 other filesystems. You should update any kld_load="fuse" entries in
665 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
666 "options FUSE" entries in kernel config files.
669 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
670 8.0.0. Please see the 20141231 entry below for information about
671 prerequisites and upgrading, if you are not already using clang 3.5.0
675 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
676 compiled into your custom kernel, add 'device xz' statement to the
680 drm and drm2 have been removed from the tree. Please see
681 https://wiki.freebsd.org/Graphics for the latest information on
682 migrating to the drm ports.
685 Iflib is no longer unconditionally compiled into the kernel. Drivers
686 using iflib and statically compiled into the kernel, now require
687 the 'device iflib' config option. For the same drivers loaded as
688 modules on kernels not having 'device iflib', the iflib.ko module
689 is loaded automatically.
692 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
693 options no longer exist since r343219 and r343427 respectively;
694 nothing uses them, so they should be just removed from custom
698 r342635 changes the way efibootmgr(8) works by requiring users to add
699 the -b (bootnum) parameter for commands where the bootnum was previously
700 specified with each option. For example 'efibootmgr -B 0001' is now
701 'efibootmgr -B -b 0001'.
704 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
705 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
706 servers that have vfs.nfsd.nfs_privport set will only allow mounts
707 from clients using a reserved port#. Since both the FreeBSD and Linux
708 NFSv4 clients use reserved port#s by default, this should not affect
712 The XLP config has been removed. We can't support 64-bit atomics in this
713 kernel because it is running in 32-bit mode. XLP users must transition
714 to running a 64-bit kernel (XLP64 or XLPN32).
716 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
717 the preferred emulator today and we don't need two different ones.
719 The old sibyte / swarm / Broadcom BCM1250 support has been
720 removed from the mips port.
723 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
724 7.0.1. Please see the 20141231 entry below for information about
725 prerequisites and upgrading, if you are not already using clang 3.5.0
729 Remove the timed and netdate programs from the base tree. Setting
730 the time with these daemons has been obsolete for over a decade.
733 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
734 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
735 it produces broken binaries when ifuncs are in use. Users needing
736 GNU ld should install the binutils port or package.
739 The BSD crtbegin and crtend code has been enabled by default. It has
740 had extensive testing on amd64, arm64, and i386. It can be disabled
741 by building a world with -DWITHOUT_BSD_CRTBEGIN.
744 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
745 has been converted to a port (misc/ctm) and will be removed from
746 FreeBSD-13. It is available as a package (ctm) for all supported
750 The default newsyslog.conf(5) file has been changed to only include
751 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
752 the filenames end in '.conf' and do not begin with a '.'.
754 You should check the configuration files in these two directories match
755 this naming convention. You can verify which configuration files are
756 being included using the command:
760 Ports for the DRM modules have been simplified. Now, amd64 users should
761 just install the drm-kmod port. All others should install
764 Graphics hardware that's newer than about 2010 usually works with
765 drm-kmod. For hardware older than 2013, however, some users will need
766 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
767 than 2008 usually only works in drm-legacy-kmod. The graphics team can
768 only commit to hardware made since 2013 due to the complexity of the
769 market and difficulty to test all the older cards effectively. If you
770 have hardware supported by drm-kmod, you are strongly encouraged to use
771 that as you will get better support.
773 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
774 elsewhere, the drm and drm2 modules will be eliminated from the src base
775 soon (with a limited exception for arm). Please update to the package
776 asap and report any issues to x11@freebsd.org.
778 Generally, anybody using the drm*-kmod packages should add
779 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
780 cross-threading surprises, especially with automatic driver
781 loading from X11 startup. These will become the defaults in 13-current
785 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
786 custom kernel and module loading configuration files must be updated
787 accordingly. Moreover, interfaces previous presented as ixlvN to the
788 system are now exposed as iavfN and network configuration files must
789 be adjusted as necessary.
792 OpenSSL has been updated to version 1.1.1. This update included
793 additional various API changes throughout the base system. It is
794 important to rebuild third-party software after upgrading. The value
795 of __FreeBSD_version has been bumped accordingly.
798 The legacy DRM modules and drivers have now been added to the loader's
799 module blacklist, in favor of loading them with kld_list in rc.conf(5).
800 The module blacklist may be overridden with the loader.conf(5)
801 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
805 The cam(4) based nda(4) driver will be used over nvd(4) by default on
806 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
807 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
808 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
812 Reproducible build mode is now on by default, in preparation for
813 FreeBSD 12.0. This eliminates build metadata such as the user,
814 host, and time from the kernel (and uname), unless the working tree
815 corresponds to a modified checkout from a version control system.
816 The previous behavior can be obtained by setting the /etc/src.conf
817 knob WITHOUT_REPRODUCIBLE_BUILD.
820 The Yarrow CSPRNG has been removed from the kernel as it has not been
821 supported by its designers since at least 2003. Fortuna has been the
822 default since FreeBSD-11.
825 devctl freeze/thaw have gone into the tree, the rc scripts have been
826 updated to use them and devmatch has been changed. You should update
827 kernel, userland and rc scripts all at the same time.
830 The default interpreter has been switched from 4th to Lua.
831 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
832 interpreter. If you have custom FORTH code you will need to set
833 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
834 src.conf for the build. This will create default hard links between
835 loader and loader_4th instead of loader and loader_lua, the new default.
836 If you are using UEFI it will create the proper hard link to loader.efi.
838 bhyve uses userboot.so. It remains 4th-only until some issues are solved
839 regarding coexisting with multiple versions of FreeBSD are resolved.
842 ls(1) now respects the COLORTERM environment variable used in other
843 systems and software to indicate that a colored terminal is both
844 supported and desired. If ls(1) is suddenly emitting colors, they may
845 be disabled again by either removing the unwanted COLORTERM from your
846 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
847 may not be observed in a future release.
850 The default pager for most commands has been changed to "less". To
851 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
855 The jedec_ts(4) driver has been removed. A superset of its functionality
856 is available in the jedec_dimm(4) driver, and the manpage for that
857 driver includes migration instructions. If you have "device jedec_ts"
858 in your kernel configuration file, it must be removed.
861 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
862 This should have no effect if the kernel is booted via BIOS/legacy boot.
863 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
864 has a buggy firmware that prevents a successful boot due to use of
868 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
869 support has been removed from the tree. These ports were
870 obsolete and/or known to be broken for many years.
873 loader.efi has been augmented to participate more fully in the
874 UEFI boot manager protocol. loader.efi will now look at the
875 BootXXXX environment variable to determine if a specific kernel
876 or root partition was specified. XXXX is derived from BootCurrent.
877 efibootmgr(8) manages these standard UEFI variables.
880 zfsloader's functionality has now been folded into loader.
881 zfsloader is no longer necessary once you've updated your
882 boot blocks. For a transition period, we will install a
883 hardlink for zfsloader to loader to allow a smooth transition
884 until the boot blocks can be updated (hard link because old
885 zfs boot blocks don't understand symlinks).
888 ARM64 now have efifb support, if you want to have serial console
889 on your arm64 board when an screen is connected and the bootloader
890 setup a frame buffer for us to use, just add :
894 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
895 an screen connected as the firmware will setup a frame buffer are that
896 u-boot will expose as an EFI frame buffer.
899 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
900 or take steps to update /etc/passwd before doing installworld on
901 existing systems. Do not skip the "mergemaster -Fp" step before
902 installworld, as described in the update procedures near the bottom
903 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
904 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
905 the ntp config file contain options that change file/dir locations.
906 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
907 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
908 taking steps to ensure that all required files/dirs are accessible
912 Big endian arm support has been removed.
915 The static environment setup in kernel configs is no longer mutually
916 exclusive with the loader(8) environment by default. In order to
917 restore the previous default behavior of disabling the loader(8)
918 environment if a static environment is present, you must specify
919 loader_env.disabled=1 in the static environment.
922 The ABI of syscalls used by management tools like sockstat and
923 netstat has been broken to allow 32-bit binaries to work on
924 64-bit kernels without modification. These programs will need
925 to match the kernel in order to function. External programs may
926 require minor modifications to accommodate a change of type in
927 structures from pointers to 64-bit virtual addresses.
930 On i386 and amd64 atomics are now inlined. Out of tree modules using
931 atomics will need to be rebuilt.
934 The '%I' format in the kern.corefile sysctl limits the number of
935 core files that a process can generate to the number stored in the
936 debug.ncores sysctl. The '%I' format is replaced by the single digit
937 index. Previously, if all indexes were taken the kernel would overwrite
938 only a core file with the highest index in a filename.
939 Currently the system will create a new core file if there is a free
940 index or if all slots are taken it will overwrite the oldest one.
943 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
944 6.0.1. Please see the 20141231 entry below for information about
945 prerequisites and upgrading, if you are not already using clang 3.5.0
949 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
950 needed to be changed to work with it. This change was made with r335763
951 and requires a mergemaster / etcupdate / etc to update the installed
955 r334930 changed the interface between the NFS modules, so they all
956 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
959 As of r334391 lld is the default amd64 system linker; it is installed
960 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
964 The kernel / userland interface for devinfo changed, so you'll
965 need a new kernel and userland as a pair for it to work (rebuilding
966 lib/libdevinfo is all that's required). devinfo and devmatch will
967 not work, but everything else will when there's a mismatch.
970 The on-disk format for hwpmc callchain records has changed to include
971 threadid corresponding to a given record. This changes the field offsets
972 and thus requires that libpmcstat be rebuilt before using a kernel
976 The vxge(4) driver has been removed. This driver was introduced into
977 HEAD one week before the Exar left the Ethernet market and is not
978 known to be used. If you have device vxge in your kernel config file
982 The amd64 kernel now requires a ld that supports ifunc to produce a
983 working kernel, either lld or a newer binutils. lld is built by default
984 on amd64, and the 'buildkernel' target uses it automatically. However,
985 it is not the default linker, so building the kernel the traditional
986 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
987 binutils port/package). lld will soon be default, and this requirement
990 NOTE: As of r334391 lld is the default system linker on amd64, and no
991 workaround is necessary.
994 The nxge(4) driver has been removed. This driver was for PCI-X 10g
995 cards made by s2io/Neterion. The company was acquired by Exar and
996 no longer sells or supports Ethernet products. If you have device
997 nxge in your kernel config file it must be removed.
1000 The tz database (tzdb) has been updated to 2018e. This version more
1001 correctly models time stamps in time zones with negative DST such as
1002 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
1003 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
1004 time zone abbreviations and the tm_isdst flag.
1007 The ixgb(4) driver has been removed. This driver was for an early and
1008 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
1009 quickly shifted to the long lived ixgbe family. If you have device
1010 ixgb in your kernel config file it must be removed.
1013 The lmc(4) driver has been removed. This was a WAN interface
1014 card that was already reportedly rare in 2003, and had an ambiguous
1015 license. If you have device lmc in your kernel config file it must
1019 Support for Arcnet networks has been removed. If you have device
1020 arcnet or device cm in your kernel config file they must be
1024 Support for FDDI networks has been removed. If you have device
1025 fddi or device fpa in your kernel config file they must be
1029 In addition to supporting RFC 3164 formatted messages, the
1030 syslogd(8) service is now capable of parsing RFC 5424 formatted
1031 log messages. The main benefit of using RFC 5424 is that clients
1032 may now send log messages with timestamps containing year numbers,
1033 microseconds and time zone offsets.
1035 Similarly, the syslog(3) C library function has been altered to
1036 send RFC 5424 formatted messages to the local system logging
1037 daemon. On systems using syslogd(8), this change should have no
1038 negative impact, as long as syslogd(8) and the C library are
1039 updated at the same time. On systems using a different system
1040 logging daemon, it may be necessary to make configuration
1041 adjustments, depending on the software used.
1043 When using syslog-ng, add the 'syslog-protocol' flag to local
1044 input sources to enable parsing of RFC 5424 formatted messages:
1047 unix-dgram("/var/run/log" flags(syslog-protocol));
1050 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
1051 of the 'imuxsock' module to let messages be processed by the
1052 regular RFC 3164/5424 parsing pipeline:
1054 module(load="imuxsock" SysSock.UseSpecialParser="off")
1056 Do note that these changes only affect communication between local
1057 applications and syslogd(8). The format that syslogd(8) uses to
1058 store messages on disk or forward messages to other systems
1059 remains unchanged. syslogd(8) still uses RFC 3164 for these
1060 purposes. Options to customize this behaviour will be added in the
1061 future. Utilities that process log files stored in /var/log are
1062 thus expected to continue to function as before.
1064 __FreeBSD_version has been incremented to 1200061 to denote this
1068 Support for token ring networks has been removed. If you
1069 have "device token" in your kernel config you should remove
1070 it. No device drivers supported token ring.
1073 makefs was modified to be able to tag ISO9660 El Torito boot catalog
1074 entries as EFI instead of overloading the i386 tag as done previously.
1075 The amd64 mkisoimages.sh script used to build amd64 ISO images for
1076 release was updated to use this. This may mean that makefs must be
1077 updated before "make cdrom" can be run in the release directory. This
1078 should be as simple as:
1080 $ cd $SRCDIR/usr.sbin/makefs
1081 $ make depend all install
1084 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
1085 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
1086 Co-existence for the transition period will come shortly. Booting is a
1087 complex environment and test coverage for Lua-enabled loaders has been
1088 thin, so it would be prudent to assume it might not work and make
1089 provisions for backup boot methods.
1092 devmatch functionality has been turned on in devd. It will automatically
1093 load drivers for unattached devices. This may cause unexpected drivers
1094 to be loaded. Please report any problems to current@ and
1098 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
1099 6.0.0. Please see the 20141231 entry below for information about
1100 prerequisites and upgrading, if you are not already using clang 3.5.0
1104 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
1105 This means it is used to link the kernel and userland libraries and
1106 executables, but is not yet installed as /usr/bin/ld by default.
1108 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
1109 WITHOUT_LLD_BOOTSTRAP=yes
1112 On i386, pmtimer has been removed. Its functionality has been folded
1113 into apm. It was a no-op on ACPI in current for a while now (but was
1114 still needed on i386 in FreeBSD 11 and earlier). Users may need to
1115 remove it from kernel config files.
1118 The use of RSS hash from the network card aka flowid has been
1119 disabled by default for lagg(4) as it's currently incompatible with
1120 the lacp and loadbalance protocols.
1122 This can be re-enabled by setting the following in loader.conf:
1123 net.link.lagg.default_use_flowid="1"
1126 The SW_WATCHDOG option is no longer necessary to enable the
1127 hardclock-based software watchdog if no hardware watchdog is
1128 configured. As before, SW_WATCHDOG will cause the software
1129 watchdog to be enabled even if a hardware watchdog is configured.
1132 r326887 fixes the issue described in the 20171214 UPDATING entry.
1133 r326888 flips the switch back to building GELI support always.
1136 r362593 broke ZFS + GELI support for reasons unknown. However,
1137 it also broke ZFS support generally, so GELI has been turned off
1138 by default as the lesser evil in r326857. If you boot off ZFS and/or
1139 GELI, it might not be a good time to update.
1142 PowerPC users must update loader(8) by rebuilding world before
1143 installing a new kernel, as the protocol connecting them has
1144 changed. Without the update, loader metadata will not be passed
1145 successfully to the kernel and users will have to enter their
1146 root partition at the kernel mountroot prompt to continue booting.
1147 Newer versions of loader can boot old kernels without issue.
1150 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
1151 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
1152 to WITH/OUT_LOADER_GELI.
1155 The naive and non-compliant support of posix_fallocate(2) in ZFS
1156 has been removed as of r325320. The system call now returns EINVAL
1157 when used on a ZFS file. Although the new behavior complies with the
1158 standard, some consumers are not prepared to cope with it.
1159 One known victim is lld prior to r325420.
1162 Building in a FreeBSD src checkout will automatically create object
1163 directories now rather than store files in the current directory if
1164 'make obj' was not ran. Calling 'make obj' is no longer necessary.
1165 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
1166 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
1170 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
1171 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
1172 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
1173 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
1174 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
1175 The UNIFIED_OBJDIR option is a transitional feature that will be
1176 removed for 12.0 release; please migrate to the new format for any
1177 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
1178 than hardcoding paths.
1181 The native-xtools target no longer installs the files by default to the
1182 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
1183 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
1186 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
1187 options are changing from controlling the build if defined / undefined
1188 to controlling the build with explicit 'yes' or 'no' values. They will
1189 shift to WITH/WITHOUT options to match other options in the system.
1192 libstand has turned into a private library for sys/boot use only.
1193 It is no longer supported as a public interface outside of sys/boot.
1196 The arm port has split armv6 into armv6 and armv7. armv7 is now
1197 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
1198 and are running a kernel from before r324363, you will need to add
1199 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
1202 When building multiple kernels using KERNCONF, non-existent KERNCONF
1203 files will produce an error and buildkernel will fail. Previously
1204 missing KERNCONF files silently failed giving no indication as to
1205 why, only to subsequently discover during installkernel that the
1206 desired kernel was never built in the first place.
1209 The default serial number format for CTL LUNs has changed. This will
1210 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
1211 or iSCSI clients care about their LUNs' serial numbers. Users who
1212 require serial number stability should hardcode serial numbers in
1216 For 32-bit arm compiled for hard-float support, soft-floating point
1217 binaries now always get their shared libraries from
1218 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
1219 /usr/libsoft also existed). Only users with a hard-float ld.so, but
1220 soft-float everything else should be affected.
1223 The geli password typed at boot is now hidden. To restore the previous
1224 behavior, see geli(8) for configuration options.
1227 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
1228 sysctl values. Minor nit, but requires a rebuild of both world/kernel
1232 "make check" behavior (made in ^/head@r295380) has been changed to
1233 execute from a limited sandbox, as opposed to executing from
1237 - The "beforecheck" and "aftercheck" targets are now specified.
1238 - ${CHECKDIR} (added in commit noted above) has been removed.
1239 - Legacy behavior can be enabled by setting
1240 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
1242 If the limited sandbox mode is enabled, "make check" will execute
1243 "make distribution", then install, execute the tests, and clean up the
1244 sandbox if successful.
1246 The "make distribution" and "make install" targets are typically run as
1247 root to set appropriate permissions and ownership at installation time.
1248 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
1249 environment if executing "make check" with limited sandbox mode using
1250 an unprivileged user.
1253 Since the switch to GPT disk labels, fsck for UFS/FFS has been
1254 unable to automatically find alternate superblocks. As of r322297,
1255 the information needed to find alternate superblocks has been
1256 moved to the end of the area reserved for the boot block.
1257 Filesystems created with a newfs of this vintage or later
1258 will create the recovery information. If you have a filesystem
1259 created prior to this change and wish to have a recovery block
1260 created for your filesystem, you can do so by running fsck in
1261 foreground mode (i.e., do not use the -p or -y options). As it
1262 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
1263 to which you should answer yes.
1266 As of r321665, an NFSv4 server configuration that services
1267 Kerberos mounts or clients that do not support the uid/gid in
1268 owner/owner_group string capability, must explicitly enable
1269 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
1270 machine's /etc/rc.conf file.
1273 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
1274 Please see the 20141231 entry below for information about prerequisites
1275 and upgrading, if you are not already using clang 3.5.0 or higher.
1278 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
1279 r-commands (rlogin, rsh, etc.) to be built with the base system.
1282 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
1283 a very major ABI incompatible change, so users of FreeBSD/powerpc must
1284 be careful when performing source upgrades. It is best to run
1285 'make installworld' from an alternate root system, either a live
1286 CD/memory stick, or a temporary root partition. Additionally, all ports
1287 must be recompiled. powerpc64 is largely unaffected, except in the case
1288 of 32-bit compatibility. All 32-bit binaries will be affected.
1291 Forward compatibility for the "ino64" project have been committed. This
1292 will allow most new binaries to run on older kernels in a limited
1293 fashion. This prevents many of the common foot-shooting actions in the
1294 upgrade as well as the limited ability to roll back the kernel across
1295 the ino64 upgrade. Complicated use cases may not work properly, though
1296 enough simpler ones work to allow recovery in most situations.
1299 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
1300 if you require the GPL compiler.
1303 The internal ABI used for communication between the NFS kernel modules
1304 was changed by r320085, so __FreeBSD_version was bumped to
1305 ensure all the NFS related modules are updated together.
1308 The ABI of struct event was changed by extending the data
1309 member to 64bit and adding ext fields. For upgrade, same
1310 precautions as for the entry 20170523 "ino64" must be
1314 The GNU roff toolchain has been removed from base. To render manpages
1315 which are not supported by mandoc(1), man(1) can fallback on GNU roff
1316 from ports (and recommends to install it).
1317 To render roff(7) documents, consider using GNU roff from ports or the
1318 heirloom doctools roff toolchain from ports via pkg install groff or
1319 via pkg install heirloom-doctools.
1322 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
1323 smaller runtime footprint builds. This is useful for embedded systems
1324 which only require one chipset support.
1326 If you load it as a module, make sure this is in /boot/loader.conf:
1330 This will load the HAL, all chip/RF backends and if_ath_pci.
1331 If you have if_ath_pci in /boot/loader.conf, ensure it is after
1332 if_ath or it will not load any HAL chipset support.
1334 If you want to selectively load things (eg on ye cheape ARM/MIPS
1335 platforms where RAM is at a premium) you should:
1338 * load the chip modules in question
1339 * load ath_rate, ath_dfs
1341 * load if_ath_pci and/or if_ath_ahb depending upon your particular
1342 bus bind type - this is where probe/attach is done.
1344 For further comments/feedback, poke adrian@ .
1347 The "ino64" 64-bit inode project has been committed, which extends
1348 a number of types to 64 bits. Upgrading in place requires care and
1349 adherence to the documented upgrade procedure.
1351 If using a custom kernel configuration ensure that the
1352 COMPAT_FREEBSD11 option is included (as during the upgrade the
1353 system will be running the ino64 kernel with the existing world).
1355 For the safest in-place upgrade begin by removing previous build
1356 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full
1357 procedure documented below under the heading "To rebuild everything and
1358 install it on the current system." Specifically, a reboot is required
1359 after installing the new kernel before installing world. While an
1360 installworld normally works by accident from multiuser after rebooting
1361 the proper kernel, there are many cases where this will fail across this
1362 upgrade and installworld from single user is required.
1365 The NATM framework including the en(4), fatm(4), hatm(4), and
1366 patm(4) devices has been removed. Consumers should plan a
1367 migration before the end-of-life date for FreeBSD 11.
1370 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
1371 diff has not been implemented, if those are needed a newer version of
1372 GNU diff is available via the diffutils package under the gdiff name.
1375 As of r316810 for ipfilter, keep frags is no longer assumed when
1376 keep state is specified in a rule. r316810 aligns ipfilter with
1377 documentation in man pages separating keep frags from keep state.
1378 This allows keep state to be specified without forcing keep frags
1379 and allows keep frags to be specified independently of keep state.
1380 To maintain previous behaviour, also specify keep frags with
1381 keep state (as documented in ipf.conf.5).
1384 arm64 builds now use the base system LLD 4.0.0 linker by default,
1385 instead of requiring that the aarch64-binutils port or package be
1386 installed. To continue using aarch64-binutils, set
1387 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
1390 The UDP optimization in entry 20160818 that added the sysctl
1391 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
1392 packets will no longer be treated as L3 broadcast packets.
1395 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
1396 use any explicitly assigned loopback address available in the jail
1397 instead of using the first assigned address of the jail.
1400 The ctl.ko module no longer implements the iSCSI target frontend:
1401 cfiscsi.ko does instead.
1403 If building cfiscsi.ko as a kernel module, the module can be loaded
1404 via one of the following methods:
1405 - `cfiscsi_load="YES"` in loader.conf(5).
1406 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
1407 - ctladm(8)/ctld(8), when compiled with iSCSI support
1408 (`WITH_ISCSI=yes` in src.conf(5))
1410 Please see cfiscsi(4) for more details.
1413 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
1414 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
1415 same source (previously, the dependency of mmcsd.ko on mmc.ko was
1416 missing, but mmcsd.ko now will refuse to load if it is incompatible
1420 The syntax of ipfw(8) named states was changed to avoid ambiguity.
1421 If you have used named states in the firewall rules, you need to modify
1422 them after installworld and before rebooting. Now named states must
1423 be prefixed with colon.
1426 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
1427 removed as the userland we provide cannot use them. The KMS version
1428 (sys/dev/drm2) supports the same hardware.
1431 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
1432 Please see the 20141231 entry below for information about prerequisites
1433 and upgrading, if you are not already using clang 3.5.0 or higher.
1436 The code that provides support for ZFS .zfs/ directory functionality
1437 has been reimplemented. It's not possible now to create a snapshot
1438 by mkdir under .zfs/snapshot/. That should be the only user visible
1442 EISA bus support has been removed. The WITH_EISA option is no longer
1446 MCA bus support has been removed.
1449 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
1450 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
1453 The EM_MULTIQUEUE kernel configuration option is deprecated now that
1454 the em(4) driver conforms to iflib specifications.
1457 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
1458 IFLIB. If you have a custom kernel configuration that excludes em(4)
1459 but you use igb(4), you need to re-add em(4) to your custom
1463 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
1464 Please see the 20141231 entry below for information about prerequisites
1465 and upgrading, if you are not already using clang 3.5.0 or higher.
1468 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
1469 Please see the 20141231 entry below for information about prerequisites
1470 and upgrading, if you are not already using clang 3.5.0 or higher.
1473 The layout of the pmap structure has changed for powerpc to put the pmap
1474 statistics at the front for all CPU variations. libkvm(3) and all tools
1475 that link against it need to be recompiled.
1478 isl(4) and cyapa(4) drivers now require a new driver,
1479 chromebook_platform(4), to work properly on Chromebook-class hardware.
1480 On other types of hardware the drivers may need to be configured using
1481 device hints. Please see the corresponding manual pages for details.
1484 The urtwn(4) driver was merged into rtwn(4) and now consists of
1485 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
1487 Also, firmware for RTL8188CE was renamed due to possible name
1488 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
1491 GNU rcs has been removed from base. It is available as packages:
1492 - rcs: Latest GPLv3 GNU rcs version.
1493 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
1497 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
1498 modules now requires that the kernel configuration contain the
1499 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
1502 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
1503 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
1506 Relocatable object files with the extension of .So have been renamed
1507 to use an extension of .pico instead. The purpose of this change is
1508 to avoid a name clash with shared libraries on case-insensitive file
1509 systems. On those file systems, foo.So is the same file as foo.so.
1512 GNU rcs has been turned off by default. It can (temporarily) be built
1513 again by adding WITH_RCS knob in src.conf.
1514 Otherwise, GNU rcs is available from packages:
1515 - rcs: Latest GPLv3 GNU rcs version.
1516 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
1519 The backup_uses_rcs functionality has been removed from rc.subr.
1522 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
1523 two separate components, QUEUE_MACRO_DEBUG_TRACE and
1524 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
1525 QUEUE_MACRO_DEBUG behavior.
1528 r304787 changed some ioctl interfaces between the iSCSI userspace
1529 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1530 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1534 The UDP receive code has been updated to only treat incoming UDP
1535 packets that were addressed to an L2 broadcast address as L3
1536 broadcast packets. It is not expected that this will affect any
1537 standards-conforming UDP application. The new behaviour can be
1538 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1542 Remove the openbsd_poll system call.
1543 __FreeBSD_version has been bumped because of this.
1546 The stable/11 branch has been created from head@r302406.
1549 The libc stub for the pipe(2) system call has been replaced with
1550 a wrapper that calls the pipe2(2) system call and the pipe(2)
1551 system call is now only implemented by the kernels that include
1552 "options COMPAT_FREEBSD10" in their config file (this is the
1553 default). Users should ensure that this option is enabled in
1554 their kernel or upgrade userspace to r302092 before upgrading their
1558 CAM will now strip leading spaces from SCSI disks' serial numbers.
1559 This will affect users who create UFS filesystems on SCSI disks using
1560 those disk's diskid device nodes. For example, if /etc/fstab
1561 previously contained a line like
1562 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
1563 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
1564 transforms like gmirror may also be affected. ZFS users should
1568 The bitstring(3) API has been updated with new functionality and
1569 improved performance. But it is binary-incompatible with the old API.
1570 Objects built with the new headers may not be linked against objects
1571 built with the old headers.
1574 The brk and sbrk functions have been removed from libc on arm64.
1575 Binutils from ports has been updated to not link to these
1576 functions and should be updated to the latest version before
1577 installing a new libc.
1580 The armv6 port now defaults to hard float ABI. Limited support
1581 for running both hardfloat and soft float on the same system
1582 is available using the libraries installed with -DWITH_LIBSOFT.
1583 This has only been tested as an upgrade path for installworld
1584 and packages may fail or need manual intervention to run. New
1585 packages will be needed.
1587 To update an existing self-hosted armv6hf system, you must add
1588 TARGET_ARCH=armv6 on the make command line for both the build
1589 and the install steps.
1592 Kernel modules compiled outside of a kernel build now default to
1593 installing to /boot/modules instead of /boot/kernel. Many kernel
1594 modules built this way (such as those in ports) already overrode
1595 KMODDIR explicitly to install into /boot/modules. However,
1596 manually building and installing a module from /sys/modules will
1597 now install to /boot/modules instead of /boot/kernel.
1600 The CAM I/O scheduler has been committed to the kernel. There should be
1601 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1602 list of known rogues that claim support for this but actually corrupt
1603 data is believed to be complete, be on the lookout for data
1604 corruption. The known rogue list is believed to be complete:
1606 o Crucial MX100, M550 drives with MU01 firmware.
1607 o Micron M510 and M550 drives with MU01 firmware.
1608 o Micron M500 prior to MU07 firmware
1609 o Samsung 830, 840, and 850 all firmwares
1610 o FCCT M500 all firmwares
1612 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1613 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1614 updated firmware. Black listed drives will work correctly because these
1615 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1616 this list is the same as found in Linux, it's believed there are no
1617 other rogues in the market place. All other models from the above
1620 To be safe, if you are at all concerned, you can quirk each of your
1621 drives to prevent NCQ from being sent by setting:
1622 kern.cam.ada.X.quirks="0x2"
1623 in loader.conf. If the drive requires the 4k sector quirk, set the
1624 quirks entry to 0x3.
1627 The FAST_DEPEND build option has been removed and its functionality is
1628 now the one true way. The old mkdep(1) style of 'make depend' has
1629 been removed. See 20160311 for further details.
1632 Resource range types have grown from unsigned long to uintmax_t. All
1633 drivers, and anything using libdevinfo, need to be recompiled.
1636 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1637 builds. It no longer runs mkdep(1) during 'make depend', and the
1638 'make depend' stage can safely be skipped now as it is auto ran
1639 when building 'make all' and will generate all SRCS and DPSRCS before
1640 building anything else. Dependencies are gathered at compile time with
1641 -MF flags kept in separate .depend files per object file. Users should
1642 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1643 stale .depend files.
1646 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1647 kernel modules. Therefore, if you load any kernel modules at boot time,
1648 please install the boot loaders after you install the kernel, but before
1652 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1653 make installkernel KERNCONF=YOUR_KERNEL_HERE
1654 make -C sys/boot install
1655 <reboot in single user>
1657 Then follow the usual steps, described in the General Notes section,
1661 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1662 see the 20141231 entry below for information about prerequisites and
1663 upgrading, if you are not already using clang 3.5.0 or higher.
1666 The AIO subsystem is now a standard part of the kernel. The
1667 VFS_AIO kernel option and aio.ko kernel module have been removed.
1668 Due to stability concerns, asynchronous I/O requests are only
1669 permitted on sockets and raw disks by default. To enable
1670 asynchronous I/O requests on all file types, set the
1671 vfs.aio.enable_unsafe sysctl to a non-zero value.
1674 The ELF object manipulation tool objcopy is now provided by the
1675 ELF Tool Chain project rather than by GNU binutils. It should be a
1676 drop-in replacement, with the addition of arm64 support. The
1677 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1678 to obtain the GNU version if necessary.
1681 Building ZFS pools on top of zvols is prohibited by default. That
1682 feature has never worked safely; it's always been prone to deadlocks.
1683 Using a zvol as the backing store for a VM guest's virtual disk will
1684 still work, even if the guest is using ZFS. Legacy behavior can be
1685 restored by setting vfs.zfs.vol.recursive=1.
1688 The NONE and HPN patches has been removed from OpenSSH. They are
1689 still available in the security/openssh-portable port.
1692 With the addition of ypldap(8), a new _ypldap user is now required
1693 during installworld. "mergemaster -p" can be used to add the user
1694 prior to installworld, as documented in the handbook.
1697 The tftp loader (pxeboot) now uses the option root-path directive. As a
1698 consequence it no longer looks for a pxeboot.4th file on the tftp
1699 server. Instead it uses the regular /boot infrastructure as with the
1703 The code to start recording plug and play data into the modules has
1704 been committed. While the old tools will properly build a new kernel,
1705 a number of warnings about "unknown metadata record 4" will be produced
1706 for an older kldxref. To avoid such warnings, make sure to rebuild
1707 the kernel toolchain (or world). Make sure that you have r292078 or
1708 later when trying to build 292077 or later before rebuilding.
1711 Debug data files are now built by default with 'make buildworld' and
1712 installed with 'make installworld'. This facilitates debugging but
1713 requires more disk space both during the build and for the installed
1714 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1718 r291527 changed the internal interface between the nfsd.ko and
1719 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1720 __FreeBSD_version has been bumped because of this.
1723 Add support for unicode collation strings leads to a change of
1724 order of files listed by ls(1) for example. To get back to the old
1725 behaviour, set LC_COLLATE environment variable to "C".
1727 Databases administrators will need to reindex their databases given
1728 collation results will be different.
1730 Due to a bug in install(1) it is recommended to remove the ancient
1731 locales before running make installworld.
1733 rm -rf /usr/share/locale/*
1736 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1737 libcrypto.so.7 or libssl.so.7 must be recompiled.
1740 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1741 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1742 should be replaced with isp_2400 and isp_2500 modules respectively.
1745 The build previously allowed using 'make -n' to not recurse into
1746 sub-directories while showing what commands would be executed, and
1747 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1748 and 'make -N' will not.
1751 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1752 and etcupdate will now use this file. A custom sendmail.cf is now
1753 updated via this mechanism rather than via installworld. If you had
1754 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1755 want to remove the exclusion or change it to "always install".
1756 /etc/mail/sendmail.cf is now managed the same way regardless of
1757 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1758 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1761 Compatibility shims for legacy ATA device names have been removed.
1762 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1763 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1764 environment variables, /dev/ad* and /dev/ar* symbolic links.
1767 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1768 Please see the 20141231 entry below for information about prerequisites
1769 and upgrading, if you are not already using clang 3.5.0 or higher.
1772 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1773 and renamed from .symbols to .debug. This reduces the size requirements
1774 on the boot partition or file system and provides consistency with
1775 userland debug files.
1777 When using the supported kernel installation method the
1778 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1779 as is done with /boot/kernel.
1781 Developers wishing to maintain the historical behavior of installing
1782 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1785 The wireless drivers had undergone changes that remove the 'parent
1786 interface' from the ifconfig -l output. The rc.d network scripts
1787 used to check presence of a parent interface in the list, so old
1788 scripts would fail to start wireless networking. Thus, etcupdate(3)
1789 or mergemaster(8) run is required after kernel update, to update your
1790 rc.d scripts in /etc.
1793 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1794 These configurations are now automatically interpreted as
1795 'scrub fragment reassemble'.
1798 Kernel-loadable modules for the random(4) device are back. To use
1799 them, the kernel must have
1802 options RANDOM_LOADABLE
1804 kldload(8) can then be used to load random_fortuna.ko
1805 or random_yarrow.ko. Please note that due to the indirect
1806 function calls that the loadable modules need to provide,
1807 the build-in variants will be slightly more efficient.
1809 The random(4) kernel option RANDOM_DUMMY has been retired due to
1810 unpopularity. It was not all that useful anyway.
1813 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1814 Control over building the ELF Tool Chain tools is now provided by
1815 the WITHOUT_TOOLCHAIN knob.
1818 The polarity of Pulse Per Second (PPS) capture events with the
1819 uart(4) driver has been corrected. Prior to this change the PPS
1820 "assert" event corresponded to the trailing edge of a positive PPS
1821 pulse and the "clear" event was the leading edge of the next pulse.
1823 As the width of a PPS pulse in a typical GPS receiver is on the
1824 order of 1 millisecond, most users will not notice any significant
1825 difference with this change.
1827 Anyone who has compensated for the historical polarity reversal by
1828 configuring a negative offset equal to the pulse width will need to
1829 remove that workaround.
1832 The default group assigned to /dev/dri entries has been changed
1833 from 'wheel' to 'video' with the id of '44'. If you want to have
1834 access to the dri devices please add yourself to the video group
1837 # pw groupmod video -m $USER
1840 The menu.rc and loader.rc files will now be replaced during
1841 upgrades. Please migrate local changes to menu.rc.local and
1842 loader.rc.local instead.
1845 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1846 strings and strip have been removed. The src.conf(5) knob
1847 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1850 As ZFS requires more kernel stack pages than is the default on some
1851 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1852 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1854 Please consider using 'options KSTACK_PAGES=X' where X is greater
1855 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1858 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1859 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1860 default, i.e., they will not contain "::". For example, instead
1861 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1862 to have a more specific match, such as different map entries for
1863 IPv6:0:0 vs IPv6:0. This change requires that configuration
1864 data (including maps, files, classes, custom ruleset, etc.) must
1865 use the same format, so make certain such configuration data is
1866 upgrading. As a very simple check search for patterns like
1867 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1868 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1869 the cf option UseCompressedIPv6Addresses.
1872 The default kernel entropy-processing algorithm is now
1873 Fortuna, replacing Yarrow.
1875 Assuming you have 'device random' in your kernel config
1876 file, the configurations allow a kernel option to override
1877 this default. You may choose *ONE* of:
1879 options RANDOM_YARROW # Legacy /dev/random algorithm.
1880 options RANDOM_DUMMY # Blocking-only driver.
1882 If you have neither, you get Fortuna. For most people,
1883 read no further, Fortuna will give a /dev/random that works
1884 like it always used to, and the difference will be irrelevant.
1886 If you remove 'device random', you get *NO* kernel-processed
1887 entropy at all. This may be acceptable to folks building
1888 embedded systems, but has complications. Carry on reading,
1889 and it is assumed you know what you need.
1891 *PLEASE* read random(4) and random(9) if you are in the
1892 habit of tweaking kernel configs, and/or if you are a member
1893 of the embedded community, wanting specific and not-usual
1894 behaviour from your security subsystems.
1896 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1897 random', you will NOT have a functioning /dev/random, and
1898 many cryptographic features will not work, including SSH.
1899 You may also find strange behaviour from the random(3) set
1900 of library functions, in particular sranddev(3), srandomdev(3)
1901 and arc4random(3). The reason for this is that the KERN_ARND
1902 sysctl only returns entropy if it thinks it has some to
1903 share, and with RANDOM_DUMMY or no 'device random' this
1907 An additional fix for the issue described in the 20150614 sendmail
1908 entry below has been committed in revision 284717.
1911 FreeBSD's old make (fmake) has been removed from the system. It is
1912 available as the devel/fmake port or via pkg install fmake.
1915 The fix for the issue described in the 20150614 sendmail entry
1916 below has been committed in revision 284436. The work
1917 around described in that entry is no longer needed unless the
1918 default setting is overridden by a confDH_PARAMETERS configuration
1919 setting of '5' or pointing to a 512 bit DH parameter file.
1922 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1923 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1924 and devel/kyua to version 0.20+ and adjust any calling code to work
1925 with Kyuafile and kyua.
1928 The import of openssl to address the FreeBSD-SA-15:10.openssl
1929 security advisory includes a change which rejects handshakes
1930 with DH parameters below 768 bits. sendmail releases prior
1931 to 8.15.2 (not yet released), defaulted to a 512 bit
1932 DH parameter setting for client connections. To work around
1933 this interoperability, sendmail can be configured to use a
1934 2048 bit DH parameter by:
1936 1. Edit /etc/mail/`hostname`.mc
1937 2. If a setting for confDH_PARAMETERS does not exist or
1938 exists and is set to a string beginning with '5',
1939 replace it with '2'.
1940 3. If a setting for confDH_PARAMETERS exists and is set to
1941 a file path, create a new file with:
1942 openssl dhparam -out /path/to/file 2048
1943 4. Rebuild the .cf file:
1944 cd /etc/mail/; make; make install
1945 5. Restart sendmail:
1946 cd /etc/mail/; make restart
1948 A sendmail patch is coming, at which time this file will be
1952 Generation of legacy formatted entries have been disabled by default
1953 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1954 entries were converted to use the new format by default when the new,
1955 machine independent format have been added and supported since FreeBSD
1958 Please see the pwd_mkdb(8) manual page for further details.
1961 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1962 20141231 entry below for information about prerequisites and upgrading,
1963 if you are not already using 3.5.0 or higher.
1966 TI platform code switched to using vendor DTS files and this update
1967 may break existing systems running on Beaglebone, Beaglebone Black,
1970 - dtb files should be regenerated/reinstalled. Filenames are the
1971 same but content is different now
1972 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1973 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1974 addressing scheme is now pin 25 on /dev/gpioc3.
1975 - Pandaboard: /etc/ttys should be updated, serial console device is
1976 now /dev/ttyu2, not /dev/ttyu0
1979 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1980 If you need the GNU extension from groff soelim(1), install groff
1981 from package: pkg install groff, or via ports: textproc/groff.
1984 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1985 defined in symlink(7); previously symlinks were silently ignored.
1988 The const qualifier has been removed from iconv(3) to comply with
1989 POSIX. The ports tree is aware of this from r384038 onwards.
1992 Libraries specified by LIBADD in Makefiles must have a corresponding
1993 DPADD_<lib> variable to ensure correct dependencies. This is now
1994 enforced in src.libnames.mk.
1997 From legacy ata(4) driver was removed support for SATA controllers
1998 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1999 Kernel modules ataahci and ataadaptec were removed completely,
2000 replaced by ahci and mvs modules respectively.
2003 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
2004 the 20141231 entry below for information about prerequisites and
2005 upgrading, if you are not already using 3.5.0 or higher.
2008 The 32-bit PowerPC kernel has been changed to a position-independent
2009 executable. This can only be booted with a version of loader(8)
2010 newer than January 31, 2015, so make sure to update both world and
2011 kernel before rebooting.
2014 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
2015 but before r278950, the RNG was not seeded properly. Immediately
2016 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
2017 ssh keys or openssl keys) that were generated w/ a kernel from that
2018 range. This does not affect programs that directly used /dev/random
2019 or /dev/urandom. All userland uses of arc4random(3) are affected.
2022 The autofs(4) ABI was changed in order to restore binary compatibility
2023 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
2024 with the new kernel.
2027 The powerpc64 kernel has been changed to a position-independent
2028 executable. This can only be booted with a new version of loader(8),
2029 so make sure to update both world and kernel before rebooting.
2032 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
2033 only release, no new features have been added. Please see the 20141231
2034 entry below for information about prerequisites and upgrading, if you
2035 are not already using 3.5.0.
2038 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
2039 taken from the ELF Tool Chain project rather than GNU binutils. They
2040 should be drop-in replacements, with the addition of arm64 support.
2041 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
2042 binutils tools, if necessary. See 20150805 for updated information.
2045 The default Unbound configuration now enables remote control
2046 using a local socket. Users who have already enabled the
2047 local_unbound service should regenerate their configuration
2048 by running "service local_unbound setup" as root.
2051 The GNU texinfo and GNU info pages have been removed.
2052 To be able to view GNU info pages please install texinfo from ports.
2055 Clang, llvm and lldb have been upgraded to 3.5.0 release.
2057 As of this release, a prerequisite for building clang, llvm and lldb is
2058 a C++11 capable compiler and C++11 standard library. This means that to
2059 be able to successfully build the cross-tools stage of buildworld, with
2060 clang as the bootstrap compiler, your system compiler or cross compiler
2061 should either be clang 3.3 or later, or gcc 4.8 or later, and your
2062 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
2065 On any standard FreeBSD 10.x or 11.x installation, where clang and
2066 libc++ are on by default (that is, on x86 or arm), this should work out
2069 On 9.x installations where clang is enabled by default, e.g. on x86 and
2070 powerpc, libc++ will not be enabled by default, so libc++ should be
2071 built (with clang) and installed first. If both clang and libc++ are
2072 missing, build clang first, then use it to build libc++.
2074 On 8.x and earlier installations, upgrade to 9.x first, and then follow
2075 the instructions for 9.x above.
2077 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
2078 default, and do not build clang.
2080 Many embedded systems are resource constrained, and will not be able to
2081 build clang in a reasonable time, or in some cases at all. In those
2082 cases, cross building bootable systems on amd64 is a workaround.
2084 This new version of clang introduces a number of new warnings, of which
2085 the following are most likely to appear:
2089 This warns in two cases, for both C and C++:
2090 * When the code is trying to take the absolute value of an unsigned
2091 quantity, which is effectively a no-op, and almost never what was
2092 intended. The code should be fixed, if at all possible. If you are
2093 sure that the unsigned quantity can be safely cast to signed, without
2094 loss of information or undefined behavior, you can add an explicit
2095 cast, or disable the warning.
2097 * When the code is trying to take an absolute value, but the called
2098 abs() variant is for the wrong type, which can lead to truncation.
2099 If you want to disable the warning instead of fixing the code, please
2100 make sure that truncation will not occur, or it might lead to unwanted
2103 -Wtautological-undefined-compare and
2104 -Wundefined-bool-conversion
2106 These warn when C++ code is trying to compare 'this' against NULL, while
2107 'this' should never be NULL in well-defined C++ code. However, there is
2108 some legacy (pre C++11) code out there, which actively abuses this
2109 feature, which was less strictly defined in previous C++ versions.
2111 Squid and openjdk do this, for example. The warning can be turned off
2112 for C++98 and earlier, but compiling the code in C++11 mode might result
2113 in unexpected behavior; for example, the parts of the program that are
2114 unreachable could be optimized away.
2117 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
2118 kernel sources have been removed. The .h files remain, since some
2119 utilities include them. This will need to be fixed later.
2120 If "mount -t oldnfs ..." is attempted, it will fail.
2121 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
2122 the utilities will report errors.
2125 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
2126 directories to top level SUBDIR variable when their parent
2127 directory is included in LOCAL_DIRS. Users with build systems with
2128 such hierarchies and without SUBDIR entries in the parent
2129 directory Makefiles should add them or add the directories to
2133 faith(4) and faithd(8) have been removed from the base system. Faith
2134 has been obsolete for a very long time.
2137 vt(4), the new console driver, is enabled by default. It brings
2138 support for Unicode and double-width characters, as well as
2139 support for UEFI and integration with the KMS kernel video
2142 You may need to update your console settings in /etc/rc.conf,
2143 most probably the keymap. During boot, /etc/rc.d/syscons will
2144 indicate what you need to do.
2146 vt(4) still has issues and lacks some features compared to
2147 syscons(4). See the wiki for up-to-date information:
2148 https://wiki.freebsd.org/Newcons
2150 If you want to keep using syscons(4), you can do so by adding
2151 the following line to /boot/loader.conf:
2155 pjdfstest has been integrated into kyua as an opt-in test suite.
2156 Please see share/doc/pjdfstest/README for more details on how to
2160 gperf has been removed from the base system for architectures
2161 that use clang. Ports that require gperf will obtain it from the
2165 pjdfstest has been moved from tools/regression/pjdfstest to
2169 At svn r271982, The default linux compat kernel ABI has been adjusted
2170 to 2.6.18 in support of the linux-c6 compat ports infrastructure
2171 update. If you wish to continue using the linux-f10 compat ports,
2172 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
2173 encouraged to update their linux-compat packages to linux-c6 during
2174 their next update cycle.
2177 The ofwfb driver, used to provide a graphics console on PowerPC when
2178 using vt(4), no longer allows mmap() of all physical memory. This
2179 will prevent Xorg on PowerPC with some ATI graphics cards from
2180 initializing properly unless x11-servers/xorg-server is updated to
2184 The xdev targets have been converted to using TARGET and
2185 TARGET_ARCH instead of XDEV and XDEV_ARCH.
2188 The default unbound configuration has been modified to address
2189 issues with reverse lookups on networks that use private
2190 address ranges. If you use the local_unbound service, run
2191 "service local_unbound setup" as root to regenerate your
2192 configuration, then "service local_unbound reload" to load the
2196 The GNU texinfo and GNU info pages are not built and installed
2197 anymore, WITH_INFO knob has been added to allow to built and install
2199 UPDATE: see 20150102 entry on texinfo's removal
2202 The GNU readline library is now an INTERNALLIB - that is, it is
2203 statically linked into consumers (GDB and variants) in the base
2204 system, and the shared library is no longer installed. The
2205 devel/readline port is available for third party software that
2209 The Itanium architecture (ia64) has been removed from the list of
2210 known architectures. This is the first step in the removal of the
2214 Commit r268115 has added NFSv4.1 server support, merged from
2215 projects/nfsv4.1-server. Since this includes changes to the
2216 internal interfaces between the NFS related modules, a full
2217 build of the kernel and modules will be necessary.
2218 __FreeBSD_version has been bumped.
2221 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
2222 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
2223 which differs from the behaviour controlled by this knob.)
2226 Maximal length of the serial number in CTL was increased from 16 to
2227 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
2228 and ctld, need to be rebuilt to work with a new kernel.
2231 The libatf-c and libatf-c++ major versions were downgraded to 0 and
2232 1 respectively to match the upstream numbers. They were out of
2233 sync because, when they were originally added to FreeBSD, the
2234 upstream versions were not respected. These libraries are private
2235 and not yet built by default, so renumbering them should be a
2236 non-issue. However, unclean source trees will yield broken test
2237 programs once the operator executes "make delete-old-libs" after a
2238 "make installworld".
2240 Additionally, the atf-sh binary was made private by moving it into
2241 /usr/libexec/. Already-built shell test programs will keep the
2242 path to the old binary so they will break after "make delete-old"
2245 If you are using WITH_TESTS=yes (not the default), wipe the object
2246 tree and rebuild from scratch to prevent spurious test failures.
2247 This is only needed once: the misnumbered libraries and misplaced
2248 binaries have been added to OptionalObsoleteFiles.inc so they will
2249 be removed during a clean upgrade.
2252 Clang and llvm have been upgraded to 3.4.1 release.
2255 We bogusly installed src.opts.mk in /usr/share/mk. This file should
2256 be removed to avoid issues in the future (and has been added to
2260 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
2261 past, it affected all builds that used the bsd.*.mk files. The old
2262 behavior was a bug, but people may have relied upon it. To get this
2263 behavior back, you can .include /etc/src.conf from /etc/make.conf
2264 (which is still global and isn't changed). This also changes the
2265 behavior of incremental builds inside the tree of individual
2266 directories. Set MAKESYSPATH to ".../share/mk" to do that.
2267 Although this has survived make universe and some upgrade scenarios,
2268 other upgrade scenarios may have broken. At least one form of
2269 temporary breakage was fixed with MAKESYSPATH settings for buildworld
2270 as well... In cases where MAKESYSPATH isn't working with this
2271 setting, you'll need to set it to the full path to your tree.
2273 One side effect of all this cleaning up is that bsd.compiler.mk
2274 is no longer implicitly included by bsd.own.mk. If you wish to
2275 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
2279 The lindev device has been removed since /dev/full has been made a
2280 standard device. __FreeBSD_version has been bumped.
2283 The knob WITHOUT_VI was added to the base system, which controls
2284 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
2285 in order to reorder files share/termcap and didn't build ex(1) as a
2286 build tool, so building/installing with WITH_VI is highly advised for
2287 build hosts for older releases.
2289 This issue has been fixed in stable/9 and stable/10 in r277022 and
2290 r276991, respectively.
2293 The YES_HESIOD knob has been removed. It has been obsolete for
2294 a decade. Please move to using WITH_HESIOD instead or your builds
2295 will silently lack HESIOD.
2298 The uart(4) driver has been changed with respect to its handling
2299 of the low-level console. Previously the uart(4) driver prevented
2300 any process from changing the baudrate or the CLOCAL and HUPCL
2301 control flags. By removing the restrictions, operators can make
2302 changes to the serial console port without having to reboot.
2303 However, when getty(8) is started on the serial device that is
2304 associated with the low-level console, a misconfigured terminal
2305 line in /etc/ttys will now have a real impact.
2306 Before upgrading the kernel, make sure that /etc/ttys has the
2307 serial console device configured as 3wire without baudrate to
2308 preserve the previous behaviour. E.g:
2309 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
2312 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
2313 to improve performance. To re-enable it, if needed, run rpcbind
2314 with command line option -W.
2317 Switched back to the GPL dtc compiler due to updates in the upstream
2318 dts files not being supported by the BSDL dtc compiler. You will need
2319 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
2320 may result while building dtb files during a kernel build if you fail
2321 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
2324 Clang and llvm have been upgraded to 3.4 release.
2327 The nve(4) driver has been removed. Please use the nfe(4) driver
2328 for NVIDIA nForce MCP Ethernet adapters instead.
2331 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
2332 This could cause certain C++ applications using shared libraries built
2333 against the previous version of libc++ to crash. The incompatibility
2334 has now been fixed, but any C++ applications or shared libraries built
2335 between r261283 and r261801 should be recompiled.
2338 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
2339 capability mode support. Please note that enabling the feature in
2340 kernel is still highly recommended.
2343 OpenSSH is now built with sandbox support, and will use sandbox as
2344 the default privilege separation method. This requires Capsicum
2345 capability mode support in kernel.
2348 The libelf and libdwarf libraries have been updated to newer
2349 versions from upstream. Shared library version numbers for
2350 these two libraries were bumped. Any ports or binaries
2351 requiring these two libraries should be recompiled.
2352 __FreeBSD_version is bumped to 1100006.
2355 If a Makefile in a tests/ directory was auto-generating a Kyuafile
2356 instead of providing an explicit one, this would prevent such
2357 Makefile from providing its own Kyuafile in the future during
2358 NO_CLEAN builds. This has been fixed in the Makefiles but manual
2359 intervention is needed to clean an objdir if you use NO_CLEAN:
2360 # find /usr/obj -name Kyuafile | xargs rm -f
2363 The behavior of gss_pseudo_random() for the krb5 mechanism
2364 has changed, for applications requesting a longer random string
2365 than produced by the underlying enctype's pseudo-random() function.
2366 In particular, the random string produced from a session key of
2367 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
2368 be different at the 17th octet and later, after this change.
2369 The counter used in the PRF+ construction is now encoded as a
2370 big-endian integer in accordance with RFC 4402.
2371 __FreeBSD_version is bumped to 1100004.
2374 The WITHOUT_ATF build knob has been removed and its functionality
2375 has been subsumed into the more generic WITHOUT_TESTS. If you were
2376 using the former to disable the build of the ATF libraries, you
2377 should change your settings to use the latter.
2380 The default version of mtree is nmtree which is obtained from
2381 NetBSD. The output is generally the same, but may vary
2382 slightly. If you found you need identical output adding
2383 "-F freebsd9" to the command line should do the trick. For the
2384 time being, the old mtree is available as fmtree.
2387 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
2388 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
2389 1.1.4_8 and verify bsdyml not linked in, before running "make
2391 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
2393 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
2396 The stable/10 branch has been created in subversion from head
2403 Sometimes, obscure build problems are the result of environment
2404 poisoning. This can happen because the make utility reads its
2405 environment when searching for values for global variables. To run
2406 your build attempts in an "environmental clean room", prefix all make
2407 commands with 'env -i '. See the env(1) manual page for more details.
2408 Occasionally a build failure will occur with "make -j" due to a race
2409 condition. If this happens try building again without -j, and please
2410 report a bug if it happens consistently.
2412 When upgrading from one major version to another it is generally best to
2413 upgrade to the latest code in the currently installed branch first, then
2414 do an upgrade to the new branch. This is the best-tested upgrade path,
2415 and has the highest probability of being successful. Please try this
2416 approach if you encounter problems with a major version upgrade. Since
2417 the stable 4.x branch point, one has generally been able to upgrade from
2418 anywhere in the most recent stable branch to head / current (or even the
2419 last couple of stable branches). See the top of this file when there's
2422 The update process will emit an error on an attempt to perform a build
2423 or install from a FreeBSD version below the earliest supported version.
2424 When updating from an older version the update should be performed one
2425 major release at a time, including running `make delete-old` at each
2428 When upgrading a live system, having a root shell around before
2429 installing anything can help undo problems. Not having a root shell
2430 around can lead to problems if pam has changed too much from your
2431 starting point to allow continued authentication after the upgrade.
2433 This file should be read as a log of events. When a later event changes
2434 information of a prior event, the prior event should not be deleted.
2435 Instead, a pointer to the entry with the new information should be
2436 placed in the old entry. Readers of this file should also sanity check
2437 older entries before relying on them blindly. Authors of new entries
2438 should write them with this in mind.
2442 When upgrading the boot ZFS pool to a new version, always follow
2445 1.) recompile and reinstall the ZFS boot loader and boot block
2446 (this is part of "make buildworld" and "make installworld")
2448 2.) update the ZFS boot block on your boot drive
2450 The following example updates the ZFS boot block on the
2451 freebsd-boot partition of a GPT partitioned drive ada0:
2452 "gpart bootcode -p /boot/gptzfsboot -i $N ada0"
2453 The value $N will typically be 1 (if booting from BIOS) or 2 (if
2456 Non-boot pools do not need these updates.
2460 If you are updating from a prior version of FreeBSD (even one just
2461 a few days old), you should follow this procedure. It is the most
2462 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2464 make kernel-toolchain
2465 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2466 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2468 To test a kernel once
2469 ---------------------
2470 If you just want to boot a kernel once (because you are not sure
2471 if it works, or if you want to boot a known bad kernel to provide
2472 debugging information) run
2473 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2474 nextboot -k testkernel
2476 To rebuild everything and install it on the current system.
2477 -----------------------------------------------------------
2478 # Note: sometimes if you are running current you gotta do more than
2479 # is listed here if you are upgrading from a really old current.
2481 <make sure you have good level 0 dumps>
2483 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2484 make installkernel KERNCONF=YOUR_KERNEL_HERE
2486 <reboot in single user> [3]
2493 To cross-install current onto a separate partition
2494 --------------------------------------------------
2495 # In this approach we use a separate partition to hold
2496 # current's root, 'usr', and 'var' directories. A partition
2497 # holding "/", "/usr" and "/var" should be about 2GB in
2500 <make sure you have good level 0 dumps>
2503 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2504 <maybe newfs current's root partition>
2505 <mount current's root partition on directory ${CURRENT_ROOT}>
2506 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
2507 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2508 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2509 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2510 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2511 <reboot into current>
2512 <do a "native" rebuild/install as described in the previous section>
2513 <maybe install compatibility libraries from ports/misc/compat*>
2517 To upgrade in-place from stable to current
2518 ----------------------------------------------
2519 <make sure you have good level 0 dumps>
2521 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
2522 make installkernel KERNCONF=YOUR_KERNEL_HERE
2524 <reboot in single user> [3]
2531 Make sure that you've read the UPDATING file to understand the
2532 tweaks to various things you need. At this point in the life
2533 cycle of current, things change often and you are on your own
2534 to cope. The defaults can also change, so please read ALL of
2535 the UPDATING entries.
2537 Also, if you are tracking -current, you must be subscribed to
2538 freebsd-current@freebsd.org. Make sure that before you update
2539 your sources that you have read and understood all the recent
2540 messages there. If in doubt, please track -stable which has
2541 much fewer pitfalls.
2543 [1] If you have third party modules, such as vmware, you should disable
2544 them at this point so they don't crash your system on
2545 reboot. Alternatively, you should rebuild all the modules you have in
2546 your system and install them as well. If you are running -current, you
2547 should seriously consider placing all sources to all the modules for
2548 your system (or symlinks to them) in /usr/local/sys/modules so this
2549 happens automatically. If all your modules come from ports, then adding
2550 the port origin directories to PORTS_MODULES instead is also automatic
2552 PORTS_MODULES+=x11/nvidia-driver
2554 [3] From the bootblocks, boot -s, and then do
2558 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed
2559 cd src # full path to source
2560 adjkerntz -i # if CMOS is wall time
2561 Also, when doing a major release upgrade, it is required that you boot
2562 into single user mode to do the installworld.
2564 [4] Note: This step is non-optional. Failure to do this step
2565 can result in a significant reduction in the functionality of the
2566 system. Attempting to do it by hand is not recommended and those
2567 that pursue this avenue should read this file carefully, as well
2568 as the archives of freebsd-current and freebsd-hackers mailing lists
2569 for potential gotchas. The -U option is also useful to consider.
2570 See mergemaster(8) for more information.
2572 [5] Usually this step is a no-op. However, from time to time
2573 you may need to do this if you get unknown user in the following
2574 step. It never hurts to do it all the time. You may need to
2575 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2576 install) after the buildworld before this step if you last updated
2577 from current before 20130425 or from -stable before 20130430.
2579 [6] This only deletes old files and directories. Old libraries
2580 can be deleted by "make delete-old-libs", but you have to make
2581 sure that no program is using those libraries anymore.
2583 [8] The new kernel must be able to run existing binaries used by an
2584 installworld. When upgrading across major versions, the new kernel's
2585 configuration must include the correct COMPAT_FREEBSD<n> option for
2586 existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure
2587 to do so may leave you with a system that is hard to boot to recover. A
2588 GENERIC kernel will include suitable compatibility options to run
2589 binaries from older branches. Note that the ability to run binaries
2590 from unsupported branches is not guaranteed.
2592 Make sure that you merge any new devices from GENERIC since the
2593 last time you updated your kernel config file. Options also
2594 change over time, so you may need to adjust your custom kernels
2597 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2598 "?=" instead of the "=" assignment operator, so that buildworld can
2599 override the CPUTYPE if it needs to.
2601 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2602 not on the command line, or in /etc/make.conf. buildworld will
2603 warn if it is improperly defined.
2606 This file contains a list, in reverse chronological order, of major
2607 breakages in tracking -current. It is not guaranteed to be a complete
2608 list of such breakages, and only contains entries since September 23, 2011.
2609 If you need to see UPDATING entries from before that date, you will need
2610 to fetch an UPDATING file from an older FreeBSD release.
2612 Copyright information:
2614 Copyright 1998-2009 M. Warner Losh <imp@FreeBSD.org>
2616 Redistribution, publication, translation and use, with or without
2617 modification, in full or in part, in any form or format of this
2618 document are permitted without further permission from the author.
2620 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2621 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2622 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2623 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2624 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2625 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2626 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2627 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2628 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2629 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2630 POSSIBILITY OF SUCH DAMAGE.
2632 Contact Warner Losh if you have any questions about your use of