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-p7 SA-23:17.pf
19 TCP spoofing vulnerability in pf(4) [SA-23:17.pf]
21 Fix clang sanitizer failure with ASLR enabled [EN-23:15.sanitizer]
24 13.2-RELEASE-p6 EN-23:16.openzfs
26 OpenZFS data corruption [EN-23:16.openzfs]
29 13.2-RELEASE-p5 EN-23:13.freebsd-update
34 freebsd-update does not handle deep boot environments [EN-23:13.freebsd-update]
36 Incorrect regular expression escape handling [EN-23:14.regcomp]
38 libc stdio buffer overflow [SA-23:15.stdio]
40 Incorrect libcap_net limitation list manipulation [SA-23:16.cap_net]
43 13.2-RELEASE-p4 FreeBSD-EN-23:12.freebsd-update
44 FreeBSD-SA-23:12.msdosfs
45 FreeBSD-SA-23:13.capsicum
46 FreeBSD-SA-23:14.smccc
48 freebsd-update to 14.0 fails [EN-23:12.freebsd-update]
50 Fix msdosfs data disclosure [SA-23:12.msdosfs]
52 copy_file_range insufficient capability rights check [SA-23:13.capsicum]
54 arm64 boot CPUs may lack speculative execution protections [SA-23:14.smccc]
57 13.2-RELEASE-p3 FreeBSD-EN-23:09.freebsd-update
59 FreeBSD-EN-23:11.caroot
63 freebsd-update incorrectly merges files on upgrade [EN-23:09.freebsd-update]
65 PCI-e hot-plug is broken with certain devices [EN-23:10.pci-update]
67 Root certificate bundle update [EN-23:11.caroot]
69 pf incorrectly handles multiple IPv6 fragment headers [SA-23:10.pf]
71 Wi-Fi encryption bypass [SA-23:11.wifi]
74 13.2-RELEASE-p2 FreeBSD-EN-23:08.vnet
76 FreeBSD-SA-23:07.bhyve
78 FreeBSD-SA-23:09.pam_krb5
80 VNET and DCPU modules panic on arm64 due to linker relaxation [EN-23:08.vnet]
82 Remote denial of service in IPv6 fragment reassembly [SA-23:06.ipv6]
84 bhyve privileged guest escape via fwctl [SA-23:07.bhyve]
86 Potential remote code execution via ssh-agent forwarding [SA-23:08.ssh]
88 Network authentication attack via pam_krb5 [SA-23:09.pam_krb5]
91 13.2-RELEASE-p1 FreeBSD-EN-23:06.loader
93 FreeBSD-SA-23:04.pam_krb5
95 x86 kernel console configuration [EN-23:06.loader]
97 Fix mpr(4) failure to initialize devices [EN-23:07.mpr]
99 Fix network authentication attack via pam_krb5 [SA-23:04.pam_krb5]
105 LinuxKPI pm.h changes require an update to the latest drm-kmod version
106 before re-compiling to avoid errors.
109 Bump __FreeBSD_verion to 1301501 after merging LinuxKPI and
110 net80211 changes in order to help out-of-tree consumers to deal
114 For 64-bit architectures the base system is now built with Position
115 Independent Executable (PIE) support enabled by default. It may be
116 disabled using the WITHOUT_PIE knob. A clean build is required.
119 The macros provided for the manipulation of CPU sets (e.g. CPU_AND)
120 have been modified to take 2 source arguments instead of only 1.
121 Externally maintained sources that use these macros will have to
122 be adapted. The FreeBSD version has been bumped to 1300524 to
126 Commit 18f5b477ee66 adds two arguments to VOP_ALLOCATE().
127 Normally changes to VOP calls are not MFC'd, but a
128 discussion on freebsd-current@ seemed to agree that
129 it was acceptable in this case, to fix the NFSv4.2 server.
130 Any out of source tree file system with a custom
131 VOP_ALLOCATE() call will need to be modified.
132 Bump __FreeBSD_version to 1300523 since the NFS modules need
133 to be rebuilt from sources.
136 Commit 6e8e261f0d4e changed the internal KAPI between the NFS
137 modules. As such, all the modules must be rebuilt from sources.
138 __FreeBSD_version has been bumped to 1300522.
141 Bump __FreeBSD_version to 1300521 after merging LinuxKPI and
142 net80211 changes in order to support building various wireless
143 drivers. This is to help other external consumers of LinuxKPI
144 and net80211 to deal accordingly.
147 Commit a599f9f7620b deleted the variable called nfs_maxcopyrange
148 from nfscommon.ko, since it no longer needs to be global. As such,
149 the other nfs modules must be rebuilt from up to date sources.
150 Bump __FreeBSD_version to 1300516 for this.
153 As of commit 622809b0868f OpenSSL no longer enables kernel TLS
154 by default. Users can enable kernel TLS via the "KTLS" SSL
155 option. This can be enabled globally by using a custom
156 OpenSSL config file via OPENSSL_CONF or via an
157 application-specific configuration option for applications
158 which permit setting SSL options via SSL_CONF_cmd(3).
161 Commits 9fb6e613373c and 9ec7dbf46b0a both changed the internal
162 KAPI between the NFS modules. Bump __FreeBSD_version to 1300514.
163 All NFS modules must be rebuilt from sources.
166 Commit b69019c14cd8 removes pf's DIOCGETSTATESNV ioctl.
167 As of be70c7a50d32 it is no longer used by userspace, but it does mean
168 users may not be able to enumerate pf states if they update the kernel
169 past c021ff986e2b without first updating userspace past be70c7a50d32.
172 Bump __FreeBSD_version to 1300512 after merging LinuxKPI, OFED,
173 net80211, and driver changes in order to support building
174 Intel wireless iwlwifi drivers. This is especially needed for
175 drm-kmod which needs updates after this.
178 The 20210707 awk update brought in a change in behavior. This has
179 been corrected as of d4d252c49976. Between these dates, if you
180 installed a new awk binary, you may not be able to build a new
181 kernel because the change in behavior affected the genoffset
182 script used to build the kernel. If you did update, the fix is
183 to update your sources past the above hash and do
186 % sudo -E make install
187 to enable building kernels again.
190 Commit 8a04edfdcbd2 changes the default minor version
191 used for NFSv4 mounts to the highest minor version supported
192 by the NFSv4 server. This default can be overridden by using
193 the "minorversion" mount option.
194 The consensus of a discussion on freebsd-current@ indicated
195 that this would be acceptable to do and would not be considered
199 awk has been updated to the latest one-true-awk version 20210215.
200 This contains a number of minor bug fixes.
203 Commit ca179c4d74f2/632e3f2f3a66 changed the package in which
204 the OpenSSL libraries and utilities are packaged.
205 It is recommended for pkgbase user to do:
206 pkg install -f FreeBSD-openssl
207 before pkg upgrade otherwise some dependencies might not be met
208 and pkg will stop working as libssl will not be present anymore
212 Commit 841006678745 changed the internal KAPI between the krpc
213 and nfsd modules. As such, they must both be rebuilt from
215 __FreeBSD_version is bumped to 1300510.
218 Commit 272f39942254 changed the internal KAPI between the
219 nscl.ko and nfscommon.ko modules, so they both need to be
220 rebuilt from sources.
223 Commit 5a45802b3c8c changed the internal KAPI between
224 the krpc and NFS. As such, the krpc, nfscommon and
225 nfscl modules must all be rebuilt from sources.
226 Without this patch, NFSv4.1/4.2 mounts should not
227 be done with the nfscbd(8) daemon running, to avoid
228 needing a working back channel for server->client RPCs.
231 Various LinuxKPI functionality was added which conflicts with DRM.
232 Please update your drm-kmod port to after the __FreeBSD_verison 1300139
236 The stable/13 branch has been created from main.
239 PC Card attachments for all devices have been removed. In the case of
240 wi and cmx, the entire drivers were removed because they were only
241 PC Card devices. FreeBSD_version 1300134 should be used for this
242 since it was bumped so recently.
245 Transport-independent parts of HID support have been split off the USB
246 code in to separate subsystem. Kernel configs which include one of
247 ums, ukbd, uhid, atp, wsp, wmt, uaudio, ugold or ucycom drivers should
248 be updated with adding of "device hid" line.
251 ncurses installation has been modified to only keep the widechar
252 enabled version. Incremental build is broken for that change, so it
253 requires a clean build.
256 The FreeBSD project has migrated from Subversion to Git. Temporary
257 instructions can be found at
258 https://github.com/bsdimp/freebsd-git-docs/blob/main/src-cvt.md
259 and other documents in that repo.
262 The services database has been updated to cover more of the basic
263 services expected in a modern system. The database is big enough
264 that it will cause issues in mergemaster in Releases previous to
265 12.2 and 11.3, or in very old current systems from before r358154.
268 Obsolete in-tree GDB 6.1.1 has been removed. GDB (including kgdb)
269 may be installed from ports or packages.
272 ping6 has been merged into ping. It can now be called as "ping -6".
273 See ping(8) for details.
276 Default value of net.add_addr_allfibs has been changed to 0.
277 If you have multi-fib configuration and rely on existence of all
278 interface routes in every fib, you need to set the above sysctl to 1.
280 The internal pre-processor in the calendar(1) program has been
281 extended to support more C pre-processor commands (e.g. #ifdef, #else,
282 and #undef) and to detect unbalanced conditional statements.
283 Error messages have been extended to include the filename and line
284 number if processing stops to help fixing malformed data files.
287 All the data files for the calendar(1) program, except calendar.freebsd,
288 have been moved to the deskutils/calendar-data port, much like the
289 jewish calendar entries were moved to deskutils/hebcal years ago. After
290 make delete-old-files, you need to install it to retain full
291 functionality. calendar(1) will issue a reminder for files it can't
295 LINT files are no longer generated. We now include the relevant NOTES
296 files. Note: This may cause conflicts with updating in some cases.
297 find sys -name LINT\* -delete
298 is suggested across this commit to remove the generated LINT files.
300 If you have tried to update with generated files there, the svn
301 command you want to un-auger the tree is
304 and then do the above find from the top level. Substitute 'amd64'
305 above with where the error message indicates a conflict.
308 OpenZFS support has been integrated. Do not upgrade root pools until
309 the loader is updated to support zstd. Furthermore, we caution against
310 'zpool upgrade' for the next few weeks. The change should be transparent
311 unless you want to use new features.
313 Not all "NO_CLEAN" build scenarios work across these changes. Many
314 scenarios have been tested and fixed, but rebuilding kernels without
315 rebuilding world may fail.
317 The ZFS cache file has moved from /boot to /etc to match the OpenZFS
318 upstream default. A fallback to /boot has been added for mountroot.
320 Pool auto import behavior at boot has been moved from the kernel module
321 to an explicit "zpool import -a" in one of the rc scripts enabled by
322 zfs_enable=YES. This means your non-root zpools won't auto import until
323 you upgrade your /etc/rc.d files.
326 The resume code now notifies devd with the 'kernel' system
327 rather than the old 'kern' subsystem to be consistent with
328 other use. The old notification will be created as well, but
329 will be removed prior to FreeBSD 14.0.
332 r362275 changed the internal API between the kernel RPC and the
333 NFS modules. As such, all the modules must be recompiled from
337 r364330 modified the internal API used between the NFS modules.
338 As such, all the NFS modules must be re-compiled from sources.
341 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
342 been upgraded to 11.0.0. Please see the 20141231 entry below for
343 information about prerequisites and upgrading, if you are not already
344 using clang 3.5.0 or higher.
347 r364092 modified the internal ABI used between the kernel NFS
348 modules. As such, all of these modules need to be rebuilt
349 from sources, so a version bump was done.
352 Makefile.inc has been updated to work around the issue documented in
353 20200729. It was a case where the optimization of using symbolic links
354 to point to binaries created a situation where we'd run new binaries
355 with old libraries starting midway through the installworld process.
358 r363679 has redefined some undefined behavior in regcomp(3); notably,
359 extraneous escapes of most ordinary characters will no longer be
360 accepted. An exp-run has identified all of the problems with this in
361 ports, but other non-ports software may need extra escapes removed to
362 continue to function.
364 Because of this change, installworld may encounter the following error
365 from rtld: Undefined symbol "regcomp@FBSD_1.6" -- It is imperative that
366 you do not halt installworld. Instead, let it run to completion (whether
367 successful or not) and run installworld once more.
370 A new implementation of bc and dc has been imported in r362681. This
371 implementation corrects non-conformant behavior of the previous bc
372 and adds GNU bc compatible options. It offers a number of extensions,
373 is much faster on large values, and has support for message catalogs
374 (a number of languages are already supported, contributions of further
375 languages welcome). The option WITHOUT_GH_BC can be used to build the
376 world with the previous versions of bc and dc.
379 r362639 changed the internal API used between the NFS kernel modules.
380 As such, they all need to be rebuilt from sources.
383 r362158 changed the arguments for VFS_CHECKEXP(). As such, any
384 out of tree file systems need to be modified and rebuilt.
385 Also, any file systems that are modules must be rebuilt.
388 read(2) of a directory fd is now rejected by default. root may
389 re-enable it for system root only on non-ZFS filesystems with the
390 security.bsd.allow_read_dir sysctl(8) MIB if
391 security.bsd.suser_enabled=1.
393 It may be advised to setup aliases for grep to default to `-d skip` if
394 commonly non-recursively grepping a list that includes directories and
395 the potential for the resulting stderr output is not tolerable. Example
396 aliases are now installed, commented out, in /root/.cshrc and
400 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
401 been upgraded to 10.0.1. Please see the 20141231 entry below for
402 information about prerequisites and upgrading, if you are not already
403 using clang 3.5.0 or higher.
406 Support for obsolete compilers has been removed from the build system.
407 Clang 6 and GCC 6.4 are the minimum supported versions.
410 closefrom(2) has been moved under COMPAT12, and replaced in libc with a
411 stub that calls close_range(2). If using a custom kernel configuration,
412 you may want to ensure that the COMPAT_FREEBSD12 option is included, as
413 a slightly older -CURRENT userland and older FreeBSD userlands may not
414 be functional without closefrom(2).
417 Upstream DTS from Linux 5.6 was merged and they now have the SID
418 and THS (Secure ID controller and THermal Sensor) node present.
419 The DTB overlays have now been removed from the tree for the H3/H5 and
420 A64 SoCs and the aw_sid and aw_thermal driver have been updated to
421 deal with upstream DTS. If you are using those overlays you need to
422 remove them from loader.conf and update the DTBs on the FAT partition.
425 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
426 been upgraded to 10.0.0. Please see the 20141231 entry below for
427 information about prerequisites and upgrading, if you are not already
428 using clang 3.5.0 or higher.
431 The amd(8) automount daemon has been removed from the source tree.
432 As of FreeBSD 10.1 autofs(5) is the preferred tool for automounting.
433 amd is still available in the sysutils/am-utils port.
436 Removed brooktree driver (bktr.4) from the tree.
439 The WITH_GPL_DTC option has been removed. The BSD-licenced device tree
440 compiler in usr.bin/dtc is used on all architectures which use dtc, and
441 the GPL dtc is available (if needed) from the sysutils/dtc port.
444 The WITHOUT_LLVM_LIBUNWIND option has been removed. LLVM's libunwind
445 is used by all supported CPU architectures.
448 GCC 4.2.1 has been removed from the tree. The WITH_GCC,
449 WITH_GCC_BOOTSTRAP, and WITH_GNUCXX options are no longer available.
450 Users who wish to build FreeBSD with GCC must use the external toolchain
454 ncurses has been updated to a newer version (6.2-20200215). Given the ABI
455 has changed, users will have to rebuild all the ports that are linked to
459 The size of struct vnet and the magic cookie have changed.
460 Users need to recompile libkvm and all modules using VIMAGE
461 together with their new kernel.
464 Defining the long deprecated NO_CTF, NO_DEBUG_FILES, NO_INSTALLLIB,
465 NO_MAN, NO_PROFILE, and NO_WARNS variables is now an error. Update
466 your Makefiles and scripts to define MK_<var>=no instead as required.
468 One exception to this is that program or library Makefiles should
469 define MAN to empty rather than setting MK_MAN=no.
472 Clang/LLVM is now the default compiler and LLD the default
476 make universe no longer uses GCC 4.2.1 on any architectures.
477 Architectures not supported by in-tree Clang/LLVM require an
478 external toolchain package.
481 GCC 4.2.1 is now not built by default, as part of the GCC 4.2.1
482 retirement plan. Specifically, the GCC, GCC_BOOTSTRAP, and GNUCXX
483 options default to off for all supported CPU architectures. As a
484 short-term transition aid they may be enabled via WITH_* options.
485 GCC 4.2.1 is expected to be removed from the tree on 2020-03-31.
488 Support for armv5 has been disconnected and is being removed. The
489 machine combination MACHINE=arm MACHINE_ARCH=arm is no longer valid.
490 You must now use a MACHINE_ARCH of armv6 or armv7. The default
491 MACHINE_ARCH for MACHINE=arm is now armv7.
494 Clang/LLVM is now the default compiler for all powerpc architectures.
495 LLD is now the default linker for powerpc64. The change for powerpc64
496 also includes a change to the ELFv2 ABI, incompatible with the existing
500 Kernel-loadable random(4) modules are no longer unloadable.
503 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
504 been upgraded to 9.0.1. Please see the 20141231 entry below for
505 information about prerequisites and upgrading, if you are not already
506 using clang 3.5.0 or higher.
509 r355677 has modified the internal interface used between the
510 NFS modules in the kernel. As such, they must all be upgraded
511 simultaneously. I will do a version bump for this.
514 The root certificates of the Mozilla CA Certificate Store have been
515 imported into the base system and can be managed with the certctl(8)
516 utility. If you have installed the security/ca_root_nss port or package
517 with the ETCSYMLINK option (the default), be advised that there may be
518 differences between those included in the port and those included in
519 base due to differences in nss branch used as well as general update
520 frequency. Note also that certctl(8) cannot manage certs in the
521 format used by the security/ca_root_nss port.
524 The amd(8) automount daemon has been disabled by default, and will be
525 removed in the future. As of FreeBSD 10.1 the autofs(5) is available
529 The nctgpio and wbwd drivers have been moved to the superio bus.
530 If you have one of these drivers in a kernel configuration, then
531 you should add device superio to it. If you use one of these drivers
532 as a module and you compile a custom set of modules, then you should
533 add superio to the set.
536 KPIs for network drivers to access interface addresses have changed.
537 Users need to recompile NIC driver modules together with kernel.
540 The net.link.tap.user_open sysctl no longer prevents user opening of
541 already created /dev/tapNN devices. Access is still controlled by
542 node permissions, just like tun devices. The net.link.tap.user_open
543 sysctl is now used only to allow users to perform devfs cloning of
544 tap devices, and the subsequent open may not succeed if the user is not
545 in the appropriate group. This sysctl may be deprecated/removed
546 completely in the future.
549 mips, powerpc, and sparc64 are no longer built as part of
550 universe / tinderbox unless MAKE_OBSOLETE_GCC is defined. If
551 not defined, mips, powerpc, and sparc64 builds will look for
552 the xtoolchain binaries and if installed use them for universe
553 builds. As llvm 9.0 becomes vetted for these architectures, they
554 will be removed from the list.
557 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
558 been upgraded to 9.0.0. Please see the 20141231 entry below for
559 information about prerequisites and upgrading, if you are not already
560 using clang 3.5.0 or higher.
563 The hpt27xx, hptmv, hptnr, and hptrr drivers have been removed from
564 GENERIC. They are available as modules and can be loaded by adding
565 to /boot/loader.conf hpt27xx_load="YES", hptmv_load="YES",
566 hptnr_load="YES", or hptrr_load="YES", respectively.
569 ntpd no longer by default locks its pages in memory, allowing them
570 to be paged out by the kernel. Use rlimit memlock to restore
571 historic BSD behaviour. For example, add "rlimit memlock 32"
572 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
575 Several of ping6's options have been renamed for better consistency
576 with ping. If you use any of -ARWXaghmrtwx, you must update your
577 scripts. See ping6(8) for details.
580 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
581 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
582 been removed from mount_fusefs(8). You can safely remove them from
583 your scripts, because they had no effect.
585 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
586 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
587 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
588 sysctls have been removed. If you felt the need to set any of them to
589 a non-default value, please tell asomers@FreeBSD.org why.
592 Default permissions on the /var/account/acct file (and copies of it
593 rotated by periodic daily scripts) are changed from 0644 to 0640
594 because the file contains sensitive information that should not be
595 world-readable. If the /var/account directory must be created by
596 rc.d/accounting, the mode used is now 0750. Admins who use the
597 accounting feature are encouraged to change the mode of an existing
598 /var/account directory to 0750 or 0700.
601 Entropy collection and the /dev/random device are no longer optional
602 components. The "device random" option has been removed.
603 Implementations of distilling algorithms can still be made loadable
604 with "options RANDOM_LOADABLE" (e.g., random_fortuna.ko).
607 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
608 been upgraded to 8.0.1. Please see the 20141231 entry below for
609 information about prerequisites and upgrading, if you are not already
610 using clang 3.5.0 or higher.
613 A fix was applied to i386 kernel modules to avoid panics with
614 dpcpu or vnet. Users need to recompile i386 kernel modules
615 having pcpu or vnet sections or they will refuse to load.
618 User-wired pages now have their own counter,
619 vm.stats.vm.v_user_wire_count. The vm.max_wired sysctl was renamed
620 to vm.max_user_wired and changed from an unsigned int to an unsigned
621 long. bhyve VMs wired with the -S are now subject to the user
622 wiring limit; the vm.max_user_wired sysctl may need to be tuned to
623 avoid running into the limit.
626 The IPSEC option has been removed from GENERIC. Users requiring
627 ipsec(4) must now load the ipsec(4) kernel module.
630 The tap(4) driver has been folded into tun(4), and the module has been
631 renamed to tuntap. You should update any kld_list="if_tap" or
632 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
633 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
634 module instead, and "device tap" or "device tun" entries in kernel
635 config files to select the tuntap device instead.
638 The following knobs have been added related to tradeoffs between
639 safe use of the random device and availability in the absence of
642 kern.random.initial_seeding.bypass_before_seeding: tunable; set
643 non-zero to bypass the random device prior to seeding, or zero to
644 block random requests until the random device is initially seeded.
645 For now, set to 1 (unsafe) by default to restore pre-r346250 boot
646 availability properties.
648 kern.random.initial_seeding.read_random_bypassed_before_seeding:
649 read-only diagnostic sysctl that is set when bypass is enabled and
650 read_random(9) is bypassed, to enable programmatic handling of this
651 initial condition, if desired.
653 kern.random.initial_seeding.arc4random_bypassed_before_seeding:
654 Similar to the above, but for arc4random(9) initial seeding.
656 kern.random.initial_seeding.disable_bypass_warnings: tunable; set
657 non-zero to disable warnings in dmesg when the same conditions are
658 met as for the diagnostic sysctls above. Defaults to zero, i.e.,
659 produce warnings in dmesg when the conditions are met.
662 The loadable random module KPI has changed; the random_infra_init()
663 routine now requires a 3rd function pointer for a bool (*)(void)
664 method that returns true if the random device is seeded (and
665 therefore unblocked).
668 r345895 reverts r320698. This implies that an nfsuserd(8) daemon
669 built from head sources between r320757 (July 6, 2017) and
670 r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
671 is added to the command line.
672 nfsuserd daemons built from head sources that are post-r338192 are
673 not affected and should continue to work.
676 The fuse(4) module has been renamed to fusefs(4) for consistency with
677 other filesystems. You should update any kld_load="fuse" entries in
678 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
679 "options FUSE" entries in kernel config files.
682 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
683 8.0.0. Please see the 20141231 entry below for information about
684 prerequisites and upgrading, if you are not already using clang 3.5.0
688 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
689 compiled into your custom kernel, add 'device xz' statement to the
693 drm and drm2 have been removed from the tree. Please see
694 https://wiki.freebsd.org/Graphics for the latest information on
695 migrating to the drm ports.
698 Iflib is no longer unconditionally compiled into the kernel. Drivers
699 using iflib and statically compiled into the kernel, now require
700 the 'device iflib' config option. For the same drivers loaded as
701 modules on kernels not having 'device iflib', the iflib.ko module
702 is loaded automatically.
705 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
706 options no longer exist since r343219 and r343427 respectively;
707 nothing uses them, so they should be just removed from custom
711 r342635 changes the way efibootmgr(8) works by requiring users to add
712 the -b (bootnum) parameter for commands where the bootnum was previously
713 specified with each option. For example 'efibootmgr -B 0001' is now
714 'efibootmgr -B -b 0001'.
717 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
718 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
719 servers that have vfs.nfsd.nfs_privport set will only allow mounts
720 from clients using a reserved port#. Since both the FreeBSD and Linux
721 NFSv4 clients use reserved port#s by default, this should not affect
725 The XLP config has been removed. We can't support 64-bit atomics in this
726 kernel because it is running in 32-bit mode. XLP users must transition
727 to running a 64-bit kernel (XLP64 or XLPN32).
729 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
730 the preferred emulator today and we don't need two different ones.
732 The old sibyte / swarm / Broadcom BCM1250 support has been
733 removed from the mips port.
736 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
737 7.0.1. Please see the 20141231 entry below for information about
738 prerequisites and upgrading, if you are not already using clang 3.5.0
742 Remove the timed and netdate programs from the base tree. Setting
743 the time with these daemons has been obsolete for over a decade.
746 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
747 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
748 it produces broken binaries when ifuncs are in use. Users needing
749 GNU ld should install the binutils port or package.
752 The BSD crtbegin and crtend code has been enabled by default. It has
753 had extensive testing on amd64, arm64, and i386. It can be disabled
754 by building a world with -DWITHOUT_BSD_CRTBEGIN.
757 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
758 has been converted to a port (misc/ctm) and will be removed from
759 FreeBSD-13. It is available as a package (ctm) for all supported
763 The default newsyslog.conf(5) file has been changed to only include
764 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
765 the filenames end in '.conf' and do not begin with a '.'.
767 You should check the configuration files in these two directories match
768 this naming convention. You can verify which configuration files are
769 being included using the command:
773 Ports for the DRM modules have been simplified. Now, amd64 users should
774 just install the drm-kmod port. All others should install
777 Graphics hardware that's newer than about 2010 usually works with
778 drm-kmod. For hardware older than 2013, however, some users will need
779 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
780 than 2008 usually only works in drm-legacy-kmod. The graphics team can
781 only commit to hardware made since 2013 due to the complexity of the
782 market and difficulty to test all the older cards effectively. If you
783 have hardware supported by drm-kmod, you are strongly encouraged to use
784 that as you will get better support.
786 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
787 elsewhere, the drm and drm2 modules will be eliminated from the src base
788 soon (with a limited exception for arm). Please update to the package
789 asap and report any issues to x11@freebsd.org.
791 Generally, anybody using the drm*-kmod packages should add
792 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
793 cross-threading surprises, especially with automatic driver
794 loading from X11 startup. These will become the defaults in 13-current
798 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
799 custom kernel and module loading configuration files must be updated
800 accordingly. Moreover, interfaces previous presented as ixlvN to the
801 system are now exposed as iavfN and network configuration files must
802 be adjusted as necessary.
805 OpenSSL has been updated to version 1.1.1. This update included
806 additional various API changes throughout the base system. It is
807 important to rebuild third-party software after upgrading. The value
808 of __FreeBSD_version has been bumped accordingly.
811 The legacy DRM modules and drivers have now been added to the loader's
812 module blacklist, in favor of loading them with kld_list in rc.conf(5).
813 The module blacklist may be overridden with the loader.conf(5)
814 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
818 The cam(4) based nda(4) driver will be used over nvd(4) by default on
819 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
820 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
821 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
825 Reproducible build mode is now on by default, in preparation for
826 FreeBSD 12.0. This eliminates build metadata such as the user,
827 host, and time from the kernel (and uname), unless the working tree
828 corresponds to a modified checkout from a version control system.
829 The previous behavior can be obtained by setting the /etc/src.conf
830 knob WITHOUT_REPRODUCIBLE_BUILD.
833 The Yarrow CSPRNG has been removed from the kernel as it has not been
834 supported by its designers since at least 2003. Fortuna has been the
835 default since FreeBSD-11.
838 devctl freeze/thaw have gone into the tree, the rc scripts have been
839 updated to use them and devmatch has been changed. You should update
840 kernel, userland and rc scripts all at the same time.
843 The default interpreter has been switched from 4th to Lua.
844 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
845 interpreter. If you have custom FORTH code you will need to set
846 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
847 src.conf for the build. This will create default hard links between
848 loader and loader_4th instead of loader and loader_lua, the new default.
849 If you are using UEFI it will create the proper hard link to loader.efi.
851 bhyve uses userboot.so. It remains 4th-only until some issues are solved
852 regarding coexisting with multiple versions of FreeBSD are resolved.
855 ls(1) now respects the COLORTERM environment variable used in other
856 systems and software to indicate that a colored terminal is both
857 supported and desired. If ls(1) is suddenly emitting colors, they may
858 be disabled again by either removing the unwanted COLORTERM from your
859 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
860 may not be observed in a future release.
863 The default pager for most commands has been changed to "less". To
864 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
868 The jedec_ts(4) driver has been removed. A superset of its functionality
869 is available in the jedec_dimm(4) driver, and the manpage for that
870 driver includes migration instructions. If you have "device jedec_ts"
871 in your kernel configuration file, it must be removed.
874 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
875 This should have no effect if the kernel is booted via BIOS/legacy boot.
876 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
877 has a buggy firmware that prevents a successful boot due to use of
881 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
882 support has been removed from the tree. These ports were
883 obsolete and/or known to be broken for many years.
886 loader.efi has been augmented to participate more fully in the
887 UEFI boot manager protocol. loader.efi will now look at the
888 BootXXXX environment variable to determine if a specific kernel
889 or root partition was specified. XXXX is derived from BootCurrent.
890 efibootmgr(8) manages these standard UEFI variables.
893 zfsloader's functionality has now been folded into loader.
894 zfsloader is no longer necessary once you've updated your
895 boot blocks. For a transition period, we will install a
896 hardlink for zfsloader to loader to allow a smooth transition
897 until the boot blocks can be updated (hard link because old
898 zfs boot blocks don't understand symlinks).
901 ARM64 now have efifb support, if you want to have serial console
902 on your arm64 board when an screen is connected and the bootloader
903 setup a frame buffer for us to use, just add :
907 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
908 an screen connected as the firmware will setup a frame buffer are that
909 u-boot will expose as an EFI frame buffer.
912 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
913 or take steps to update /etc/passwd before doing installworld on
914 existing systems. Do not skip the "mergemaster -Fp" step before
915 installworld, as described in the update procedures near the bottom
916 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
917 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
918 the ntp config file contain options that change file/dir locations.
919 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
920 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
921 taking steps to ensure that all required files/dirs are accessible
925 Big endian arm support has been removed.
928 The static environment setup in kernel configs is no longer mutually
929 exclusive with the loader(8) environment by default. In order to
930 restore the previous default behavior of disabling the loader(8)
931 environment if a static environment is present, you must specify
932 loader_env.disabled=1 in the static environment.
935 The ABI of syscalls used by management tools like sockstat and
936 netstat has been broken to allow 32-bit binaries to work on
937 64-bit kernels without modification. These programs will need
938 to match the kernel in order to function. External programs may
939 require minor modifications to accommodate a change of type in
940 structures from pointers to 64-bit virtual addresses.
943 On i386 and amd64 atomics are now inlined. Out of tree modules using
944 atomics will need to be rebuilt.
947 The '%I' format in the kern.corefile sysctl limits the number of
948 core files that a process can generate to the number stored in the
949 debug.ncores sysctl. The '%I' format is replaced by the single digit
950 index. Previously, if all indexes were taken the kernel would overwrite
951 only a core file with the highest index in a filename.
952 Currently the system will create a new core file if there is a free
953 index or if all slots are taken it will overwrite the oldest one.
956 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
957 6.0.1. Please see the 20141231 entry below for information about
958 prerequisites and upgrading, if you are not already using clang 3.5.0
962 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
963 needed to be changed to work with it. This change was made with r335763
964 and requires a mergemaster / etcupdate / etc to update the installed
968 r334930 changed the interface between the NFS modules, so they all
969 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
972 As of r334391 lld is the default amd64 system linker; it is installed
973 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
977 The kernel / userland interface for devinfo changed, so you'll
978 need a new kernel and userland as a pair for it to work (rebuilding
979 lib/libdevinfo is all that's required). devinfo and devmatch will
980 not work, but everything else will when there's a mismatch.
983 The on-disk format for hwpmc callchain records has changed to include
984 threadid corresponding to a given record. This changes the field offsets
985 and thus requires that libpmcstat be rebuilt before using a kernel
989 The vxge(4) driver has been removed. This driver was introduced into
990 HEAD one week before the Exar left the Ethernet market and is not
991 known to be used. If you have device vxge in your kernel config file
995 The amd64 kernel now requires a ld that supports ifunc to produce a
996 working kernel, either lld or a newer binutils. lld is built by default
997 on amd64, and the 'buildkernel' target uses it automatically. However,
998 it is not the default linker, so building the kernel the traditional
999 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
1000 binutils port/package). lld will soon be default, and this requirement
1003 NOTE: As of r334391 lld is the default system linker on amd64, and no
1004 workaround is necessary.
1007 The nxge(4) driver has been removed. This driver was for PCI-X 10g
1008 cards made by s2io/Neterion. The company was acquired by Exar and
1009 no longer sells or supports Ethernet products. If you have device
1010 nxge in your kernel config file it must be removed.
1013 The tz database (tzdb) has been updated to 2018e. This version more
1014 correctly models time stamps in time zones with negative DST such as
1015 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
1016 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
1017 time zone abbreviations and the tm_isdst flag.
1020 The ixgb(4) driver has been removed. This driver was for an early and
1021 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
1022 quickly shifted to the long lived ixgbe family. If you have device
1023 ixgb in your kernel config file it must be removed.
1026 The lmc(4) driver has been removed. This was a WAN interface
1027 card that was already reportedly rare in 2003, and had an ambiguous
1028 license. If you have device lmc in your kernel config file it must
1032 Support for Arcnet networks has been removed. If you have device
1033 arcnet or device cm in your kernel config file they must be
1037 Support for FDDI networks has been removed. If you have device
1038 fddi or device fpa in your kernel config file they must be
1042 In addition to supporting RFC 3164 formatted messages, the
1043 syslogd(8) service is now capable of parsing RFC 5424 formatted
1044 log messages. The main benefit of using RFC 5424 is that clients
1045 may now send log messages with timestamps containing year numbers,
1046 microseconds and time zone offsets.
1048 Similarly, the syslog(3) C library function has been altered to
1049 send RFC 5424 formatted messages to the local system logging
1050 daemon. On systems using syslogd(8), this change should have no
1051 negative impact, as long as syslogd(8) and the C library are
1052 updated at the same time. On systems using a different system
1053 logging daemon, it may be necessary to make configuration
1054 adjustments, depending on the software used.
1056 When using syslog-ng, add the 'syslog-protocol' flag to local
1057 input sources to enable parsing of RFC 5424 formatted messages:
1060 unix-dgram("/var/run/log" flags(syslog-protocol));
1063 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
1064 of the 'imuxsock' module to let messages be processed by the
1065 regular RFC 3164/5424 parsing pipeline:
1067 module(load="imuxsock" SysSock.UseSpecialParser="off")
1069 Do note that these changes only affect communication between local
1070 applications and syslogd(8). The format that syslogd(8) uses to
1071 store messages on disk or forward messages to other systems
1072 remains unchanged. syslogd(8) still uses RFC 3164 for these
1073 purposes. Options to customize this behaviour will be added in the
1074 future. Utilities that process log files stored in /var/log are
1075 thus expected to continue to function as before.
1077 __FreeBSD_version has been incremented to 1200061 to denote this
1081 Support for token ring networks has been removed. If you
1082 have "device token" in your kernel config you should remove
1083 it. No device drivers supported token ring.
1086 makefs was modified to be able to tag ISO9660 El Torito boot catalog
1087 entries as EFI instead of overloading the i386 tag as done previously.
1088 The amd64 mkisoimages.sh script used to build amd64 ISO images for
1089 release was updated to use this. This may mean that makefs must be
1090 updated before "make cdrom" can be run in the release directory. This
1091 should be as simple as:
1093 $ cd $SRCDIR/usr.sbin/makefs
1094 $ make depend all install
1097 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
1098 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
1099 Co-existence for the transition period will come shortly. Booting is a
1100 complex environment and test coverage for Lua-enabled loaders has been
1101 thin, so it would be prudent to assume it might not work and make
1102 provisions for backup boot methods.
1105 devmatch functionality has been turned on in devd. It will automatically
1106 load drivers for unattached devices. This may cause unexpected drivers
1107 to be loaded. Please report any problems to current@ and
1111 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
1112 6.0.0. Please see the 20141231 entry below for information about
1113 prerequisites and upgrading, if you are not already using clang 3.5.0
1117 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
1118 This means it is used to link the kernel and userland libraries and
1119 executables, but is not yet installed as /usr/bin/ld by default.
1121 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
1122 WITHOUT_LLD_BOOTSTRAP=yes
1125 On i386, pmtimer has been removed. Its functionality has been folded
1126 into apm. It was a no-op on ACPI in current for a while now (but was
1127 still needed on i386 in FreeBSD 11 and earlier). Users may need to
1128 remove it from kernel config files.
1131 The use of RSS hash from the network card aka flowid has been
1132 disabled by default for lagg(4) as it's currently incompatible with
1133 the lacp and loadbalance protocols.
1135 This can be re-enabled by setting the following in loader.conf:
1136 net.link.lagg.default_use_flowid="1"
1139 The SW_WATCHDOG option is no longer necessary to enable the
1140 hardclock-based software watchdog if no hardware watchdog is
1141 configured. As before, SW_WATCHDOG will cause the software
1142 watchdog to be enabled even if a hardware watchdog is configured.
1145 r326887 fixes the issue described in the 20171214 UPDATING entry.
1146 r326888 flips the switch back to building GELI support always.
1149 r362593 broke ZFS + GELI support for reasons unknown. However,
1150 it also broke ZFS support generally, so GELI has been turned off
1151 by default as the lesser evil in r326857. If you boot off ZFS and/or
1152 GELI, it might not be a good time to update.
1155 PowerPC users must update loader(8) by rebuilding world before
1156 installing a new kernel, as the protocol connecting them has
1157 changed. Without the update, loader metadata will not be passed
1158 successfully to the kernel and users will have to enter their
1159 root partition at the kernel mountroot prompt to continue booting.
1160 Newer versions of loader can boot old kernels without issue.
1163 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
1164 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
1165 to WITH/OUT_LOADER_GELI.
1168 The naive and non-compliant support of posix_fallocate(2) in ZFS
1169 has been removed as of r325320. The system call now returns EINVAL
1170 when used on a ZFS file. Although the new behavior complies with the
1171 standard, some consumers are not prepared to cope with it.
1172 One known victim is lld prior to r325420.
1175 Building in a FreeBSD src checkout will automatically create object
1176 directories now rather than store files in the current directory if
1177 'make obj' was not ran. Calling 'make obj' is no longer necessary.
1178 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
1179 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
1183 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
1184 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
1185 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
1186 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
1187 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
1188 The UNIFIED_OBJDIR option is a transitional feature that will be
1189 removed for 12.0 release; please migrate to the new format for any
1190 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
1191 than hardcoding paths.
1194 The native-xtools target no longer installs the files by default to the
1195 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
1196 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
1199 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
1200 options are changing from controlling the build if defined / undefined
1201 to controlling the build with explicit 'yes' or 'no' values. They will
1202 shift to WITH/WITHOUT options to match other options in the system.
1205 libstand has turned into a private library for sys/boot use only.
1206 It is no longer supported as a public interface outside of sys/boot.
1209 The arm port has split armv6 into armv6 and armv7. armv7 is now
1210 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
1211 and are running a kernel from before r324363, you will need to add
1212 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
1215 When building multiple kernels using KERNCONF, non-existent KERNCONF
1216 files will produce an error and buildkernel will fail. Previously
1217 missing KERNCONF files silently failed giving no indication as to
1218 why, only to subsequently discover during installkernel that the
1219 desired kernel was never built in the first place.
1222 The default serial number format for CTL LUNs has changed. This will
1223 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
1224 or iSCSI clients care about their LUNs' serial numbers. Users who
1225 require serial number stability should hardcode serial numbers in
1229 For 32-bit arm compiled for hard-float support, soft-floating point
1230 binaries now always get their shared libraries from
1231 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
1232 /usr/libsoft also existed). Only users with a hard-float ld.so, but
1233 soft-float everything else should be affected.
1236 The geli password typed at boot is now hidden. To restore the previous
1237 behavior, see geli(8) for configuration options.
1240 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
1241 sysctl values. Minor nit, but requires a rebuild of both world/kernel
1245 "make check" behavior (made in ^/head@r295380) has been changed to
1246 execute from a limited sandbox, as opposed to executing from
1250 - The "beforecheck" and "aftercheck" targets are now specified.
1251 - ${CHECKDIR} (added in commit noted above) has been removed.
1252 - Legacy behavior can be enabled by setting
1253 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
1255 If the limited sandbox mode is enabled, "make check" will execute
1256 "make distribution", then install, execute the tests, and clean up the
1257 sandbox if successful.
1259 The "make distribution" and "make install" targets are typically run as
1260 root to set appropriate permissions and ownership at installation time.
1261 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
1262 environment if executing "make check" with limited sandbox mode using
1263 an unprivileged user.
1266 Since the switch to GPT disk labels, fsck for UFS/FFS has been
1267 unable to automatically find alternate superblocks. As of r322297,
1268 the information needed to find alternate superblocks has been
1269 moved to the end of the area reserved for the boot block.
1270 Filesystems created with a newfs of this vintage or later
1271 will create the recovery information. If you have a filesystem
1272 created prior to this change and wish to have a recovery block
1273 created for your filesystem, you can do so by running fsck in
1274 foreground mode (i.e., do not use the -p or -y options). As it
1275 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
1276 to which you should answer yes.
1279 As of r321665, an NFSv4 server configuration that services
1280 Kerberos mounts or clients that do not support the uid/gid in
1281 owner/owner_group string capability, must explicitly enable
1282 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
1283 machine's /etc/rc.conf file.
1286 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
1287 Please see the 20141231 entry below for information about prerequisites
1288 and upgrading, if you are not already using clang 3.5.0 or higher.
1291 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
1292 r-commands (rlogin, rsh, etc.) to be built with the base system.
1295 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
1296 a very major ABI incompatible change, so users of FreeBSD/powerpc must
1297 be careful when performing source upgrades. It is best to run
1298 'make installworld' from an alternate root system, either a live
1299 CD/memory stick, or a temporary root partition. Additionally, all ports
1300 must be recompiled. powerpc64 is largely unaffected, except in the case
1301 of 32-bit compatibility. All 32-bit binaries will be affected.
1304 Forward compatibility for the "ino64" project have been committed. This
1305 will allow most new binaries to run on older kernels in a limited
1306 fashion. This prevents many of the common foot-shooting actions in the
1307 upgrade as well as the limited ability to roll back the kernel across
1308 the ino64 upgrade. Complicated use cases may not work properly, though
1309 enough simpler ones work to allow recovery in most situations.
1312 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
1313 if you require the GPL compiler.
1316 The internal ABI used for communication between the NFS kernel modules
1317 was changed by r320085, so __FreeBSD_version was bumped to
1318 ensure all the NFS related modules are updated together.
1321 The ABI of struct event was changed by extending the data
1322 member to 64bit and adding ext fields. For upgrade, same
1323 precautions as for the entry 20170523 "ino64" must be
1327 The GNU roff toolchain has been removed from base. To render manpages
1328 which are not supported by mandoc(1), man(1) can fallback on GNU roff
1329 from ports (and recommends to install it).
1330 To render roff(7) documents, consider using GNU roff from ports or the
1331 heirloom doctools roff toolchain from ports via pkg install groff or
1332 via pkg install heirloom-doctools.
1335 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
1336 smaller runtime footprint builds. This is useful for embedded systems
1337 which only require one chipset support.
1339 If you load it as a module, make sure this is in /boot/loader.conf:
1343 This will load the HAL, all chip/RF backends and if_ath_pci.
1344 If you have if_ath_pci in /boot/loader.conf, ensure it is after
1345 if_ath or it will not load any HAL chipset support.
1347 If you want to selectively load things (eg on ye cheape ARM/MIPS
1348 platforms where RAM is at a premium) you should:
1351 * load the chip modules in question
1352 * load ath_rate, ath_dfs
1354 * load if_ath_pci and/or if_ath_ahb depending upon your particular
1355 bus bind type - this is where probe/attach is done.
1357 For further comments/feedback, poke adrian@ .
1360 The "ino64" 64-bit inode project has been committed, which extends
1361 a number of types to 64 bits. Upgrading in place requires care and
1362 adherence to the documented upgrade procedure.
1364 If using a custom kernel configuration ensure that the
1365 COMPAT_FREEBSD11 option is included (as during the upgrade the
1366 system will be running the ino64 kernel with the existing world).
1368 For the safest in-place upgrade begin by removing previous build
1369 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full
1370 procedure documented below under the heading "To rebuild everything and
1371 install it on the current system." Specifically, a reboot is required
1372 after installing the new kernel before installing world. While an
1373 installworld normally works by accident from multiuser after rebooting
1374 the proper kernel, there are many cases where this will fail across this
1375 upgrade and installworld from single user is required.
1378 The NATM framework including the en(4), fatm(4), hatm(4), and
1379 patm(4) devices has been removed. Consumers should plan a
1380 migration before the end-of-life date for FreeBSD 11.
1383 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
1384 diff has not been implemented, if those are needed a newer version of
1385 GNU diff is available via the diffutils package under the gdiff name.
1388 As of r316810 for ipfilter, keep frags is no longer assumed when
1389 keep state is specified in a rule. r316810 aligns ipfilter with
1390 documentation in man pages separating keep frags from keep state.
1391 This allows keep state to be specified without forcing keep frags
1392 and allows keep frags to be specified independently of keep state.
1393 To maintain previous behaviour, also specify keep frags with
1394 keep state (as documented in ipf.conf.5).
1397 arm64 builds now use the base system LLD 4.0.0 linker by default,
1398 instead of requiring that the aarch64-binutils port or package be
1399 installed. To continue using aarch64-binutils, set
1400 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
1403 The UDP optimization in entry 20160818 that added the sysctl
1404 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
1405 packets will no longer be treated as L3 broadcast packets.
1408 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
1409 use any explicitly assigned loopback address available in the jail
1410 instead of using the first assigned address of the jail.
1413 The ctl.ko module no longer implements the iSCSI target frontend:
1414 cfiscsi.ko does instead.
1416 If building cfiscsi.ko as a kernel module, the module can be loaded
1417 via one of the following methods:
1418 - `cfiscsi_load="YES"` in loader.conf(5).
1419 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
1420 - ctladm(8)/ctld(8), when compiled with iSCSI support
1421 (`WITH_ISCSI=yes` in src.conf(5))
1423 Please see cfiscsi(4) for more details.
1426 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
1427 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
1428 same source (previously, the dependency of mmcsd.ko on mmc.ko was
1429 missing, but mmcsd.ko now will refuse to load if it is incompatible
1433 The syntax of ipfw(8) named states was changed to avoid ambiguity.
1434 If you have used named states in the firewall rules, you need to modify
1435 them after installworld and before rebooting. Now named states must
1436 be prefixed with colon.
1439 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
1440 removed as the userland we provide cannot use them. The KMS version
1441 (sys/dev/drm2) supports the same hardware.
1444 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
1445 Please see the 20141231 entry below for information about prerequisites
1446 and upgrading, if you are not already using clang 3.5.0 or higher.
1449 The code that provides support for ZFS .zfs/ directory functionality
1450 has been reimplemented. It's not possible now to create a snapshot
1451 by mkdir under .zfs/snapshot/. That should be the only user visible
1455 EISA bus support has been removed. The WITH_EISA option is no longer
1459 MCA bus support has been removed.
1462 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
1463 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
1466 The EM_MULTIQUEUE kernel configuration option is deprecated now that
1467 the em(4) driver conforms to iflib specifications.
1470 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
1471 IFLIB. If you have a custom kernel configuration that excludes em(4)
1472 but you use igb(4), you need to re-add em(4) to your custom
1476 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
1477 Please see the 20141231 entry below for information about prerequisites
1478 and upgrading, if you are not already using clang 3.5.0 or higher.
1481 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
1482 Please see the 20141231 entry below for information about prerequisites
1483 and upgrading, if you are not already using clang 3.5.0 or higher.
1486 The layout of the pmap structure has changed for powerpc to put the pmap
1487 statistics at the front for all CPU variations. libkvm(3) and all tools
1488 that link against it need to be recompiled.
1491 isl(4) and cyapa(4) drivers now require a new driver,
1492 chromebook_platform(4), to work properly on Chromebook-class hardware.
1493 On other types of hardware the drivers may need to be configured using
1494 device hints. Please see the corresponding manual pages for details.
1497 The urtwn(4) driver was merged into rtwn(4) and now consists of
1498 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
1500 Also, firmware for RTL8188CE was renamed due to possible name
1501 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
1504 GNU rcs has been removed from base. It is available as packages:
1505 - rcs: Latest GPLv3 GNU rcs version.
1506 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
1510 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
1511 modules now requires that the kernel configuration contain the
1512 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
1515 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
1516 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
1519 Relocatable object files with the extension of .So have been renamed
1520 to use an extension of .pico instead. The purpose of this change is
1521 to avoid a name clash with shared libraries on case-insensitive file
1522 systems. On those file systems, foo.So is the same file as foo.so.
1525 GNU rcs has been turned off by default. It can (temporarily) be built
1526 again by adding WITH_RCS knob in src.conf.
1527 Otherwise, GNU rcs is available from packages:
1528 - rcs: Latest GPLv3 GNU rcs version.
1529 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
1532 The backup_uses_rcs functionality has been removed from rc.subr.
1535 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
1536 two separate components, QUEUE_MACRO_DEBUG_TRACE and
1537 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
1538 QUEUE_MACRO_DEBUG behavior.
1541 r304787 changed some ioctl interfaces between the iSCSI userspace
1542 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1543 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1547 The UDP receive code has been updated to only treat incoming UDP
1548 packets that were addressed to an L2 broadcast address as L3
1549 broadcast packets. It is not expected that this will affect any
1550 standards-conforming UDP application. The new behaviour can be
1551 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1555 Remove the openbsd_poll system call.
1556 __FreeBSD_version has been bumped because of this.
1559 The stable/11 branch has been created from head@r302406.
1562 The libc stub for the pipe(2) system call has been replaced with
1563 a wrapper that calls the pipe2(2) system call and the pipe(2)
1564 system call is now only implemented by the kernels that include
1565 "options COMPAT_FREEBSD10" in their config file (this is the
1566 default). Users should ensure that this option is enabled in
1567 their kernel or upgrade userspace to r302092 before upgrading their
1571 CAM will now strip leading spaces from SCSI disks' serial numbers.
1572 This will affect users who create UFS filesystems on SCSI disks using
1573 those disk's diskid device nodes. For example, if /etc/fstab
1574 previously contained a line like
1575 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
1576 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
1577 transforms like gmirror may also be affected. ZFS users should
1581 The bitstring(3) API has been updated with new functionality and
1582 improved performance. But it is binary-incompatible with the old API.
1583 Objects built with the new headers may not be linked against objects
1584 built with the old headers.
1587 The brk and sbrk functions have been removed from libc on arm64.
1588 Binutils from ports has been updated to not link to these
1589 functions and should be updated to the latest version before
1590 installing a new libc.
1593 The armv6 port now defaults to hard float ABI. Limited support
1594 for running both hardfloat and soft float on the same system
1595 is available using the libraries installed with -DWITH_LIBSOFT.
1596 This has only been tested as an upgrade path for installworld
1597 and packages may fail or need manual intervention to run. New
1598 packages will be needed.
1600 To update an existing self-hosted armv6hf system, you must add
1601 TARGET_ARCH=armv6 on the make command line for both the build
1602 and the install steps.
1605 Kernel modules compiled outside of a kernel build now default to
1606 installing to /boot/modules instead of /boot/kernel. Many kernel
1607 modules built this way (such as those in ports) already overrode
1608 KMODDIR explicitly to install into /boot/modules. However,
1609 manually building and installing a module from /sys/modules will
1610 now install to /boot/modules instead of /boot/kernel.
1613 The CAM I/O scheduler has been committed to the kernel. There should be
1614 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1615 list of known rogues that claim support for this but actually corrupt
1616 data is believed to be complete, be on the lookout for data
1617 corruption. The known rogue list is believed to be complete:
1619 o Crucial MX100, M550 drives with MU01 firmware.
1620 o Micron M510 and M550 drives with MU01 firmware.
1621 o Micron M500 prior to MU07 firmware
1622 o Samsung 830, 840, and 850 all firmwares
1623 o FCCT M500 all firmwares
1625 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1626 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1627 updated firmware. Black listed drives will work correctly because these
1628 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1629 this list is the same as found in Linux, it's believed there are no
1630 other rogues in the market place. All other models from the above
1633 To be safe, if you are at all concerned, you can quirk each of your
1634 drives to prevent NCQ from being sent by setting:
1635 kern.cam.ada.X.quirks="0x2"
1636 in loader.conf. If the drive requires the 4k sector quirk, set the
1637 quirks entry to 0x3.
1640 The FAST_DEPEND build option has been removed and its functionality is
1641 now the one true way. The old mkdep(1) style of 'make depend' has
1642 been removed. See 20160311 for further details.
1645 Resource range types have grown from unsigned long to uintmax_t. All
1646 drivers, and anything using libdevinfo, need to be recompiled.
1649 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1650 builds. It no longer runs mkdep(1) during 'make depend', and the
1651 'make depend' stage can safely be skipped now as it is auto ran
1652 when building 'make all' and will generate all SRCS and DPSRCS before
1653 building anything else. Dependencies are gathered at compile time with
1654 -MF flags kept in separate .depend files per object file. Users should
1655 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1656 stale .depend files.
1659 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1660 kernel modules. Therefore, if you load any kernel modules at boot time,
1661 please install the boot loaders after you install the kernel, but before
1665 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1666 make installkernel KERNCONF=YOUR_KERNEL_HERE
1667 make -C sys/boot install
1668 <reboot in single user>
1670 Then follow the usual steps, described in the General Notes section,
1674 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1675 see the 20141231 entry below for information about prerequisites and
1676 upgrading, if you are not already using clang 3.5.0 or higher.
1679 The AIO subsystem is now a standard part of the kernel. The
1680 VFS_AIO kernel option and aio.ko kernel module have been removed.
1681 Due to stability concerns, asynchronous I/O requests are only
1682 permitted on sockets and raw disks by default. To enable
1683 asynchronous I/O requests on all file types, set the
1684 vfs.aio.enable_unsafe sysctl to a non-zero value.
1687 The ELF object manipulation tool objcopy is now provided by the
1688 ELF Tool Chain project rather than by GNU binutils. It should be a
1689 drop-in replacement, with the addition of arm64 support. The
1690 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1691 to obtain the GNU version if necessary.
1694 Building ZFS pools on top of zvols is prohibited by default. That
1695 feature has never worked safely; it's always been prone to deadlocks.
1696 Using a zvol as the backing store for a VM guest's virtual disk will
1697 still work, even if the guest is using ZFS. Legacy behavior can be
1698 restored by setting vfs.zfs.vol.recursive=1.
1701 The NONE and HPN patches has been removed from OpenSSH. They are
1702 still available in the security/openssh-portable port.
1705 With the addition of ypldap(8), a new _ypldap user is now required
1706 during installworld. "mergemaster -p" can be used to add the user
1707 prior to installworld, as documented in the handbook.
1710 The tftp loader (pxeboot) now uses the option root-path directive. As a
1711 consequence it no longer looks for a pxeboot.4th file on the tftp
1712 server. Instead it uses the regular /boot infrastructure as with the
1716 The code to start recording plug and play data into the modules has
1717 been committed. While the old tools will properly build a new kernel,
1718 a number of warnings about "unknown metadata record 4" will be produced
1719 for an older kldxref. To avoid such warnings, make sure to rebuild
1720 the kernel toolchain (or world). Make sure that you have r292078 or
1721 later when trying to build 292077 or later before rebuilding.
1724 Debug data files are now built by default with 'make buildworld' and
1725 installed with 'make installworld'. This facilitates debugging but
1726 requires more disk space both during the build and for the installed
1727 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1731 r291527 changed the internal interface between the nfsd.ko and
1732 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1733 __FreeBSD_version has been bumped because of this.
1736 Add support for unicode collation strings leads to a change of
1737 order of files listed by ls(1) for example. To get back to the old
1738 behaviour, set LC_COLLATE environment variable to "C".
1740 Databases administrators will need to reindex their databases given
1741 collation results will be different.
1743 Due to a bug in install(1) it is recommended to remove the ancient
1744 locales before running make installworld.
1746 rm -rf /usr/share/locale/*
1749 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1750 libcrypto.so.7 or libssl.so.7 must be recompiled.
1753 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1754 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1755 should be replaced with isp_2400 and isp_2500 modules respectively.
1758 The build previously allowed using 'make -n' to not recurse into
1759 sub-directories while showing what commands would be executed, and
1760 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1761 and 'make -N' will not.
1764 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1765 and etcupdate will now use this file. A custom sendmail.cf is now
1766 updated via this mechanism rather than via installworld. If you had
1767 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1768 want to remove the exclusion or change it to "always install".
1769 /etc/mail/sendmail.cf is now managed the same way regardless of
1770 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1771 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1774 Compatibility shims for legacy ATA device names have been removed.
1775 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1776 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1777 environment variables, /dev/ad* and /dev/ar* symbolic links.
1780 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1781 Please see the 20141231 entry below for information about prerequisites
1782 and upgrading, if you are not already using clang 3.5.0 or higher.
1785 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1786 and renamed from .symbols to .debug. This reduces the size requirements
1787 on the boot partition or file system and provides consistency with
1788 userland debug files.
1790 When using the supported kernel installation method the
1791 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1792 as is done with /boot/kernel.
1794 Developers wishing to maintain the historical behavior of installing
1795 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1798 The wireless drivers had undergone changes that remove the 'parent
1799 interface' from the ifconfig -l output. The rc.d network scripts
1800 used to check presence of a parent interface in the list, so old
1801 scripts would fail to start wireless networking. Thus, etcupdate(3)
1802 or mergemaster(8) run is required after kernel update, to update your
1803 rc.d scripts in /etc.
1806 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1807 These configurations are now automatically interpreted as
1808 'scrub fragment reassemble'.
1811 Kernel-loadable modules for the random(4) device are back. To use
1812 them, the kernel must have
1815 options RANDOM_LOADABLE
1817 kldload(8) can then be used to load random_fortuna.ko
1818 or random_yarrow.ko. Please note that due to the indirect
1819 function calls that the loadable modules need to provide,
1820 the build-in variants will be slightly more efficient.
1822 The random(4) kernel option RANDOM_DUMMY has been retired due to
1823 unpopularity. It was not all that useful anyway.
1826 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1827 Control over building the ELF Tool Chain tools is now provided by
1828 the WITHOUT_TOOLCHAIN knob.
1831 The polarity of Pulse Per Second (PPS) capture events with the
1832 uart(4) driver has been corrected. Prior to this change the PPS
1833 "assert" event corresponded to the trailing edge of a positive PPS
1834 pulse and the "clear" event was the leading edge of the next pulse.
1836 As the width of a PPS pulse in a typical GPS receiver is on the
1837 order of 1 millisecond, most users will not notice any significant
1838 difference with this change.
1840 Anyone who has compensated for the historical polarity reversal by
1841 configuring a negative offset equal to the pulse width will need to
1842 remove that workaround.
1845 The default group assigned to /dev/dri entries has been changed
1846 from 'wheel' to 'video' with the id of '44'. If you want to have
1847 access to the dri devices please add yourself to the video group
1850 # pw groupmod video -m $USER
1853 The menu.rc and loader.rc files will now be replaced during
1854 upgrades. Please migrate local changes to menu.rc.local and
1855 loader.rc.local instead.
1858 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1859 strings and strip have been removed. The src.conf(5) knob
1860 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1863 As ZFS requires more kernel stack pages than is the default on some
1864 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1865 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1867 Please consider using 'options KSTACK_PAGES=X' where X is greater
1868 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1871 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1872 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1873 default, i.e., they will not contain "::". For example, instead
1874 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1875 to have a more specific match, such as different map entries for
1876 IPv6:0:0 vs IPv6:0. This change requires that configuration
1877 data (including maps, files, classes, custom ruleset, etc.) must
1878 use the same format, so make certain such configuration data is
1879 upgrading. As a very simple check search for patterns like
1880 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1881 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1882 the cf option UseCompressedIPv6Addresses.
1885 The default kernel entropy-processing algorithm is now
1886 Fortuna, replacing Yarrow.
1888 Assuming you have 'device random' in your kernel config
1889 file, the configurations allow a kernel option to override
1890 this default. You may choose *ONE* of:
1892 options RANDOM_YARROW # Legacy /dev/random algorithm.
1893 options RANDOM_DUMMY # Blocking-only driver.
1895 If you have neither, you get Fortuna. For most people,
1896 read no further, Fortuna will give a /dev/random that works
1897 like it always used to, and the difference will be irrelevant.
1899 If you remove 'device random', you get *NO* kernel-processed
1900 entropy at all. This may be acceptable to folks building
1901 embedded systems, but has complications. Carry on reading,
1902 and it is assumed you know what you need.
1904 *PLEASE* read random(4) and random(9) if you are in the
1905 habit of tweaking kernel configs, and/or if you are a member
1906 of the embedded community, wanting specific and not-usual
1907 behaviour from your security subsystems.
1909 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1910 random', you will NOT have a functioning /dev/random, and
1911 many cryptographic features will not work, including SSH.
1912 You may also find strange behaviour from the random(3) set
1913 of library functions, in particular sranddev(3), srandomdev(3)
1914 and arc4random(3). The reason for this is that the KERN_ARND
1915 sysctl only returns entropy if it thinks it has some to
1916 share, and with RANDOM_DUMMY or no 'device random' this
1920 An additional fix for the issue described in the 20150614 sendmail
1921 entry below has been committed in revision 284717.
1924 FreeBSD's old make (fmake) has been removed from the system. It is
1925 available as the devel/fmake port or via pkg install fmake.
1928 The fix for the issue described in the 20150614 sendmail entry
1929 below has been committed in revision 284436. The work
1930 around described in that entry is no longer needed unless the
1931 default setting is overridden by a confDH_PARAMETERS configuration
1932 setting of '5' or pointing to a 512 bit DH parameter file.
1935 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1936 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1937 and devel/kyua to version 0.20+ and adjust any calling code to work
1938 with Kyuafile and kyua.
1941 The import of openssl to address the FreeBSD-SA-15:10.openssl
1942 security advisory includes a change which rejects handshakes
1943 with DH parameters below 768 bits. sendmail releases prior
1944 to 8.15.2 (not yet released), defaulted to a 512 bit
1945 DH parameter setting for client connections. To work around
1946 this interoperability, sendmail can be configured to use a
1947 2048 bit DH parameter by:
1949 1. Edit /etc/mail/`hostname`.mc
1950 2. If a setting for confDH_PARAMETERS does not exist or
1951 exists and is set to a string beginning with '5',
1952 replace it with '2'.
1953 3. If a setting for confDH_PARAMETERS exists and is set to
1954 a file path, create a new file with:
1955 openssl dhparam -out /path/to/file 2048
1956 4. Rebuild the .cf file:
1957 cd /etc/mail/; make; make install
1958 5. Restart sendmail:
1959 cd /etc/mail/; make restart
1961 A sendmail patch is coming, at which time this file will be
1965 Generation of legacy formatted entries have been disabled by default
1966 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1967 entries were converted to use the new format by default when the new,
1968 machine independent format have been added and supported since FreeBSD
1971 Please see the pwd_mkdb(8) manual page for further details.
1974 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1975 20141231 entry below for information about prerequisites and upgrading,
1976 if you are not already using 3.5.0 or higher.
1979 TI platform code switched to using vendor DTS files and this update
1980 may break existing systems running on Beaglebone, Beaglebone Black,
1983 - dtb files should be regenerated/reinstalled. Filenames are the
1984 same but content is different now
1985 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1986 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1987 addressing scheme is now pin 25 on /dev/gpioc3.
1988 - Pandaboard: /etc/ttys should be updated, serial console device is
1989 now /dev/ttyu2, not /dev/ttyu0
1992 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1993 If you need the GNU extension from groff soelim(1), install groff
1994 from package: pkg install groff, or via ports: textproc/groff.
1997 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1998 defined in symlink(7); previously symlinks were silently ignored.
2001 The const qualifier has been removed from iconv(3) to comply with
2002 POSIX. The ports tree is aware of this from r384038 onwards.
2005 Libraries specified by LIBADD in Makefiles must have a corresponding
2006 DPADD_<lib> variable to ensure correct dependencies. This is now
2007 enforced in src.libnames.mk.
2010 From legacy ata(4) driver was removed support for SATA controllers
2011 supported by more functional drivers ahci(4), siis(4) and mvs(4).
2012 Kernel modules ataahci and ataadaptec were removed completely,
2013 replaced by ahci and mvs modules respectively.
2016 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
2017 the 20141231 entry below for information about prerequisites and
2018 upgrading, if you are not already using 3.5.0 or higher.
2021 The 32-bit PowerPC kernel has been changed to a position-independent
2022 executable. This can only be booted with a version of loader(8)
2023 newer than January 31, 2015, so make sure to update both world and
2024 kernel before rebooting.
2027 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
2028 but before r278950, the RNG was not seeded properly. Immediately
2029 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
2030 ssh keys or openssl keys) that were generated w/ a kernel from that
2031 range. This does not affect programs that directly used /dev/random
2032 or /dev/urandom. All userland uses of arc4random(3) are affected.
2035 The autofs(4) ABI was changed in order to restore binary compatibility
2036 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
2037 with the new kernel.
2040 The powerpc64 kernel has been changed to a position-independent
2041 executable. This can only be booted with a new version of loader(8),
2042 so make sure to update both world and kernel before rebooting.
2045 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
2046 only release, no new features have been added. Please see the 20141231
2047 entry below for information about prerequisites and upgrading, if you
2048 are not already using 3.5.0.
2051 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
2052 taken from the ELF Tool Chain project rather than GNU binutils. They
2053 should be drop-in replacements, with the addition of arm64 support.
2054 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
2055 binutils tools, if necessary. See 20150805 for updated information.
2058 The default Unbound configuration now enables remote control
2059 using a local socket. Users who have already enabled the
2060 local_unbound service should regenerate their configuration
2061 by running "service local_unbound setup" as root.
2064 The GNU texinfo and GNU info pages have been removed.
2065 To be able to view GNU info pages please install texinfo from ports.
2068 Clang, llvm and lldb have been upgraded to 3.5.0 release.
2070 As of this release, a prerequisite for building clang, llvm and lldb is
2071 a C++11 capable compiler and C++11 standard library. This means that to
2072 be able to successfully build the cross-tools stage of buildworld, with
2073 clang as the bootstrap compiler, your system compiler or cross compiler
2074 should either be clang 3.3 or later, or gcc 4.8 or later, and your
2075 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
2078 On any standard FreeBSD 10.x or 11.x installation, where clang and
2079 libc++ are on by default (that is, on x86 or arm), this should work out
2082 On 9.x installations where clang is enabled by default, e.g. on x86 and
2083 powerpc, libc++ will not be enabled by default, so libc++ should be
2084 built (with clang) and installed first. If both clang and libc++ are
2085 missing, build clang first, then use it to build libc++.
2087 On 8.x and earlier installations, upgrade to 9.x first, and then follow
2088 the instructions for 9.x above.
2090 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
2091 default, and do not build clang.
2093 Many embedded systems are resource constrained, and will not be able to
2094 build clang in a reasonable time, or in some cases at all. In those
2095 cases, cross building bootable systems on amd64 is a workaround.
2097 This new version of clang introduces a number of new warnings, of which
2098 the following are most likely to appear:
2102 This warns in two cases, for both C and C++:
2103 * When the code is trying to take the absolute value of an unsigned
2104 quantity, which is effectively a no-op, and almost never what was
2105 intended. The code should be fixed, if at all possible. If you are
2106 sure that the unsigned quantity can be safely cast to signed, without
2107 loss of information or undefined behavior, you can add an explicit
2108 cast, or disable the warning.
2110 * When the code is trying to take an absolute value, but the called
2111 abs() variant is for the wrong type, which can lead to truncation.
2112 If you want to disable the warning instead of fixing the code, please
2113 make sure that truncation will not occur, or it might lead to unwanted
2116 -Wtautological-undefined-compare and
2117 -Wundefined-bool-conversion
2119 These warn when C++ code is trying to compare 'this' against NULL, while
2120 'this' should never be NULL in well-defined C++ code. However, there is
2121 some legacy (pre C++11) code out there, which actively abuses this
2122 feature, which was less strictly defined in previous C++ versions.
2124 Squid and openjdk do this, for example. The warning can be turned off
2125 for C++98 and earlier, but compiling the code in C++11 mode might result
2126 in unexpected behavior; for example, the parts of the program that are
2127 unreachable could be optimized away.
2130 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
2131 kernel sources have been removed. The .h files remain, since some
2132 utilities include them. This will need to be fixed later.
2133 If "mount -t oldnfs ..." is attempted, it will fail.
2134 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
2135 the utilities will report errors.
2138 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
2139 directories to top level SUBDIR variable when their parent
2140 directory is included in LOCAL_DIRS. Users with build systems with
2141 such hierarchies and without SUBDIR entries in the parent
2142 directory Makefiles should add them or add the directories to
2146 faith(4) and faithd(8) have been removed from the base system. Faith
2147 has been obsolete for a very long time.
2150 vt(4), the new console driver, is enabled by default. It brings
2151 support for Unicode and double-width characters, as well as
2152 support for UEFI and integration with the KMS kernel video
2155 You may need to update your console settings in /etc/rc.conf,
2156 most probably the keymap. During boot, /etc/rc.d/syscons will
2157 indicate what you need to do.
2159 vt(4) still has issues and lacks some features compared to
2160 syscons(4). See the wiki for up-to-date information:
2161 https://wiki.freebsd.org/Newcons
2163 If you want to keep using syscons(4), you can do so by adding
2164 the following line to /boot/loader.conf:
2168 pjdfstest has been integrated into kyua as an opt-in test suite.
2169 Please see share/doc/pjdfstest/README for more details on how to
2173 gperf has been removed from the base system for architectures
2174 that use clang. Ports that require gperf will obtain it from the
2178 pjdfstest has been moved from tools/regression/pjdfstest to
2182 At svn r271982, The default linux compat kernel ABI has been adjusted
2183 to 2.6.18 in support of the linux-c6 compat ports infrastructure
2184 update. If you wish to continue using the linux-f10 compat ports,
2185 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
2186 encouraged to update their linux-compat packages to linux-c6 during
2187 their next update cycle.
2190 The ofwfb driver, used to provide a graphics console on PowerPC when
2191 using vt(4), no longer allows mmap() of all physical memory. This
2192 will prevent Xorg on PowerPC with some ATI graphics cards from
2193 initializing properly unless x11-servers/xorg-server is updated to
2197 The xdev targets have been converted to using TARGET and
2198 TARGET_ARCH instead of XDEV and XDEV_ARCH.
2201 The default unbound configuration has been modified to address
2202 issues with reverse lookups on networks that use private
2203 address ranges. If you use the local_unbound service, run
2204 "service local_unbound setup" as root to regenerate your
2205 configuration, then "service local_unbound reload" to load the
2209 The GNU texinfo and GNU info pages are not built and installed
2210 anymore, WITH_INFO knob has been added to allow to built and install
2212 UPDATE: see 20150102 entry on texinfo's removal
2215 The GNU readline library is now an INTERNALLIB - that is, it is
2216 statically linked into consumers (GDB and variants) in the base
2217 system, and the shared library is no longer installed. The
2218 devel/readline port is available for third party software that
2222 The Itanium architecture (ia64) has been removed from the list of
2223 known architectures. This is the first step in the removal of the
2227 Commit r268115 has added NFSv4.1 server support, merged from
2228 projects/nfsv4.1-server. Since this includes changes to the
2229 internal interfaces between the NFS related modules, a full
2230 build of the kernel and modules will be necessary.
2231 __FreeBSD_version has been bumped.
2234 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
2235 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
2236 which differs from the behaviour controlled by this knob.)
2239 Maximal length of the serial number in CTL was increased from 16 to
2240 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
2241 and ctld, need to be rebuilt to work with a new kernel.
2244 The libatf-c and libatf-c++ major versions were downgraded to 0 and
2245 1 respectively to match the upstream numbers. They were out of
2246 sync because, when they were originally added to FreeBSD, the
2247 upstream versions were not respected. These libraries are private
2248 and not yet built by default, so renumbering them should be a
2249 non-issue. However, unclean source trees will yield broken test
2250 programs once the operator executes "make delete-old-libs" after a
2251 "make installworld".
2253 Additionally, the atf-sh binary was made private by moving it into
2254 /usr/libexec/. Already-built shell test programs will keep the
2255 path to the old binary so they will break after "make delete-old"
2258 If you are using WITH_TESTS=yes (not the default), wipe the object
2259 tree and rebuild from scratch to prevent spurious test failures.
2260 This is only needed once: the misnumbered libraries and misplaced
2261 binaries have been added to OptionalObsoleteFiles.inc so they will
2262 be removed during a clean upgrade.
2265 Clang and llvm have been upgraded to 3.4.1 release.
2268 We bogusly installed src.opts.mk in /usr/share/mk. This file should
2269 be removed to avoid issues in the future (and has been added to
2273 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
2274 past, it affected all builds that used the bsd.*.mk files. The old
2275 behavior was a bug, but people may have relied upon it. To get this
2276 behavior back, you can .include /etc/src.conf from /etc/make.conf
2277 (which is still global and isn't changed). This also changes the
2278 behavior of incremental builds inside the tree of individual
2279 directories. Set MAKESYSPATH to ".../share/mk" to do that.
2280 Although this has survived make universe and some upgrade scenarios,
2281 other upgrade scenarios may have broken. At least one form of
2282 temporary breakage was fixed with MAKESYSPATH settings for buildworld
2283 as well... In cases where MAKESYSPATH isn't working with this
2284 setting, you'll need to set it to the full path to your tree.
2286 One side effect of all this cleaning up is that bsd.compiler.mk
2287 is no longer implicitly included by bsd.own.mk. If you wish to
2288 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
2292 The lindev device has been removed since /dev/full has been made a
2293 standard device. __FreeBSD_version has been bumped.
2296 The knob WITHOUT_VI was added to the base system, which controls
2297 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
2298 in order to reorder files share/termcap and didn't build ex(1) as a
2299 build tool, so building/installing with WITH_VI is highly advised for
2300 build hosts for older releases.
2302 This issue has been fixed in stable/9 and stable/10 in r277022 and
2303 r276991, respectively.
2306 The YES_HESIOD knob has been removed. It has been obsolete for
2307 a decade. Please move to using WITH_HESIOD instead or your builds
2308 will silently lack HESIOD.
2311 The uart(4) driver has been changed with respect to its handling
2312 of the low-level console. Previously the uart(4) driver prevented
2313 any process from changing the baudrate or the CLOCAL and HUPCL
2314 control flags. By removing the restrictions, operators can make
2315 changes to the serial console port without having to reboot.
2316 However, when getty(8) is started on the serial device that is
2317 associated with the low-level console, a misconfigured terminal
2318 line in /etc/ttys will now have a real impact.
2319 Before upgrading the kernel, make sure that /etc/ttys has the
2320 serial console device configured as 3wire without baudrate to
2321 preserve the previous behaviour. E.g:
2322 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
2325 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
2326 to improve performance. To re-enable it, if needed, run rpcbind
2327 with command line option -W.
2330 Switched back to the GPL dtc compiler due to updates in the upstream
2331 dts files not being supported by the BSDL dtc compiler. You will need
2332 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
2333 may result while building dtb files during a kernel build if you fail
2334 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
2337 Clang and llvm have been upgraded to 3.4 release.
2340 The nve(4) driver has been removed. Please use the nfe(4) driver
2341 for NVIDIA nForce MCP Ethernet adapters instead.
2344 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
2345 This could cause certain C++ applications using shared libraries built
2346 against the previous version of libc++ to crash. The incompatibility
2347 has now been fixed, but any C++ applications or shared libraries built
2348 between r261283 and r261801 should be recompiled.
2351 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
2352 capability mode support. Please note that enabling the feature in
2353 kernel is still highly recommended.
2356 OpenSSH is now built with sandbox support, and will use sandbox as
2357 the default privilege separation method. This requires Capsicum
2358 capability mode support in kernel.
2361 The libelf and libdwarf libraries have been updated to newer
2362 versions from upstream. Shared library version numbers for
2363 these two libraries were bumped. Any ports or binaries
2364 requiring these two libraries should be recompiled.
2365 __FreeBSD_version is bumped to 1100006.
2368 If a Makefile in a tests/ directory was auto-generating a Kyuafile
2369 instead of providing an explicit one, this would prevent such
2370 Makefile from providing its own Kyuafile in the future during
2371 NO_CLEAN builds. This has been fixed in the Makefiles but manual
2372 intervention is needed to clean an objdir if you use NO_CLEAN:
2373 # find /usr/obj -name Kyuafile | xargs rm -f
2376 The behavior of gss_pseudo_random() for the krb5 mechanism
2377 has changed, for applications requesting a longer random string
2378 than produced by the underlying enctype's pseudo-random() function.
2379 In particular, the random string produced from a session key of
2380 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
2381 be different at the 17th octet and later, after this change.
2382 The counter used in the PRF+ construction is now encoded as a
2383 big-endian integer in accordance with RFC 4402.
2384 __FreeBSD_version is bumped to 1100004.
2387 The WITHOUT_ATF build knob has been removed and its functionality
2388 has been subsumed into the more generic WITHOUT_TESTS. If you were
2389 using the former to disable the build of the ATF libraries, you
2390 should change your settings to use the latter.
2393 The default version of mtree is nmtree which is obtained from
2394 NetBSD. The output is generally the same, but may vary
2395 slightly. If you found you need identical output adding
2396 "-F freebsd9" to the command line should do the trick. For the
2397 time being, the old mtree is available as fmtree.
2400 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
2401 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
2402 1.1.4_8 and verify bsdyml not linked in, before running "make
2404 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
2406 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
2409 The stable/10 branch has been created in subversion from head
2416 Sometimes, obscure build problems are the result of environment
2417 poisoning. This can happen because the make utility reads its
2418 environment when searching for values for global variables. To run
2419 your build attempts in an "environmental clean room", prefix all make
2420 commands with 'env -i '. See the env(1) manual page for more details.
2421 Occasionally a build failure will occur with "make -j" due to a race
2422 condition. If this happens try building again without -j, and please
2423 report a bug if it happens consistently.
2425 When upgrading from one major version to another it is generally best to
2426 upgrade to the latest code in the currently installed branch first, then
2427 do an upgrade to the new branch. This is the best-tested upgrade path,
2428 and has the highest probability of being successful. Please try this
2429 approach if you encounter problems with a major version upgrade. Since
2430 the stable 4.x branch point, one has generally been able to upgrade from
2431 anywhere in the most recent stable branch to head / current (or even the
2432 last couple of stable branches). See the top of this file when there's
2435 The update process will emit an error on an attempt to perform a build
2436 or install from a FreeBSD version below the earliest supported version.
2437 When updating from an older version the update should be performed one
2438 major release at a time, including running `make delete-old` at each
2441 When upgrading a live system, having a root shell around before
2442 installing anything can help undo problems. Not having a root shell
2443 around can lead to problems if pam has changed too much from your
2444 starting point to allow continued authentication after the upgrade.
2446 This file should be read as a log of events. When a later event changes
2447 information of a prior event, the prior event should not be deleted.
2448 Instead, a pointer to the entry with the new information should be
2449 placed in the old entry. Readers of this file should also sanity check
2450 older entries before relying on them blindly. Authors of new entries
2451 should write them with this in mind.
2455 When upgrading the boot ZFS pool to a new version, always follow
2458 1.) recompile and reinstall the ZFS boot loader and boot block
2459 (this is part of "make buildworld" and "make installworld")
2461 2.) update the ZFS boot block on your boot drive
2463 The following example updates the ZFS boot block on the
2464 freebsd-boot partition of a GPT partitioned drive ada0:
2465 "gpart bootcode -p /boot/gptzfsboot -i $N ada0"
2466 The value $N will typically be 1 (if booting from BIOS) or 2 (if
2469 Non-boot pools do not need these updates.
2473 If you are updating from a prior version of FreeBSD (even one just
2474 a few days old), you should follow this procedure. It is the most
2475 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2477 make kernel-toolchain
2478 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2479 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2481 To test a kernel once
2482 ---------------------
2483 If you just want to boot a kernel once (because you are not sure
2484 if it works, or if you want to boot a known bad kernel to provide
2485 debugging information) run
2486 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2487 nextboot -k testkernel
2489 To rebuild everything and install it on the current system.
2490 -----------------------------------------------------------
2491 # Note: sometimes if you are running current you gotta do more than
2492 # is listed here if you are upgrading from a really old current.
2494 <make sure you have good level 0 dumps>
2496 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2497 make installkernel KERNCONF=YOUR_KERNEL_HERE
2499 <reboot in single user> [3]
2506 To cross-install current onto a separate partition
2507 --------------------------------------------------
2508 # In this approach we use a separate partition to hold
2509 # current's root, 'usr', and 'var' directories. A partition
2510 # holding "/", "/usr" and "/var" should be about 2GB in
2513 <make sure you have good level 0 dumps>
2516 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2517 <maybe newfs current's root partition>
2518 <mount current's root partition on directory ${CURRENT_ROOT}>
2519 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
2520 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2521 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2522 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2523 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2524 <reboot into current>
2525 <do a "native" rebuild/install as described in the previous section>
2526 <maybe install compatibility libraries from ports/misc/compat*>
2530 To upgrade in-place from stable to current
2531 ----------------------------------------------
2532 <make sure you have good level 0 dumps>
2534 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
2535 make installkernel KERNCONF=YOUR_KERNEL_HERE
2537 <reboot in single user> [3]
2544 Make sure that you've read the UPDATING file to understand the
2545 tweaks to various things you need. At this point in the life
2546 cycle of current, things change often and you are on your own
2547 to cope. The defaults can also change, so please read ALL of
2548 the UPDATING entries.
2550 Also, if you are tracking -current, you must be subscribed to
2551 freebsd-current@freebsd.org. Make sure that before you update
2552 your sources that you have read and understood all the recent
2553 messages there. If in doubt, please track -stable which has
2554 much fewer pitfalls.
2556 [1] If you have third party modules, such as vmware, you should disable
2557 them at this point so they don't crash your system on
2558 reboot. Alternatively, you should rebuild all the modules you have in
2559 your system and install them as well. If you are running -current, you
2560 should seriously consider placing all sources to all the modules for
2561 your system (or symlinks to them) in /usr/local/sys/modules so this
2562 happens automatically. If all your modules come from ports, then adding
2563 the port origin directories to PORTS_MODULES instead is also automatic
2565 PORTS_MODULES+=x11/nvidia-driver
2567 [3] From the bootblocks, boot -s, and then do
2571 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed
2572 cd src # full path to source
2573 adjkerntz -i # if CMOS is wall time
2574 Also, when doing a major release upgrade, it is required that you boot
2575 into single user mode to do the installworld.
2577 [4] Note: This step is non-optional. Failure to do this step
2578 can result in a significant reduction in the functionality of the
2579 system. Attempting to do it by hand is not recommended and those
2580 that pursue this avenue should read this file carefully, as well
2581 as the archives of freebsd-current and freebsd-hackers mailing lists
2582 for potential gotchas. The -U option is also useful to consider.
2583 See mergemaster(8) for more information.
2585 [5] Usually this step is a no-op. However, from time to time
2586 you may need to do this if you get unknown user in the following
2587 step. It never hurts to do it all the time. You may need to
2588 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2589 install) after the buildworld before this step if you last updated
2590 from current before 20130425 or from -stable before 20130430.
2592 [6] This only deletes old files and directories. Old libraries
2593 can be deleted by "make delete-old-libs", but you have to make
2594 sure that no program is using those libraries anymore.
2596 [8] The new kernel must be able to run existing binaries used by an
2597 installworld. When upgrading across major versions, the new kernel's
2598 configuration must include the correct COMPAT_FREEBSD<n> option for
2599 existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure
2600 to do so may leave you with a system that is hard to boot to recover. A
2601 GENERIC kernel will include suitable compatibility options to run
2602 binaries from older branches. Note that the ability to run binaries
2603 from unsupported branches is not guaranteed.
2605 Make sure that you merge any new devices from GENERIC since the
2606 last time you updated your kernel config file. Options also
2607 change over time, so you may need to adjust your custom kernels
2610 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2611 "?=" instead of the "=" assignment operator, so that buildworld can
2612 override the CPUTYPE if it needs to.
2614 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2615 not on the command line, or in /etc/make.conf. buildworld will
2616 warn if it is improperly defined.
2619 This file contains a list, in reverse chronological order, of major
2620 breakages in tracking -current. It is not guaranteed to be a complete
2621 list of such breakages, and only contains entries since September 23, 2011.
2622 If you need to see UPDATING entries from before that date, you will need
2623 to fetch an UPDATING file from an older FreeBSD release.
2625 Copyright information:
2627 Copyright 1998-2009 M. Warner Losh <imp@FreeBSD.org>
2629 Redistribution, publication, translation and use, with or without
2630 modification, in full or in part, in any form or format of this
2631 document are permitted without further permission from the author.
2633 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2634 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2635 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2636 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2637 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2638 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2639 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2640 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2641 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2642 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2643 POSSIBILITY OF SUCH DAMAGE.
2645 Contact Warner Losh if you have any questions about your use of
projects / FreeBSD / FreeBSD.git / blob