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