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