1 Updating Information for FreeBSD stable/13 users.
3 This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>.
4 See end of file for further details. For commonly done items, please see the
5 COMMON ITEMS: section later in the file. These instructions assume that you
6 basically know what you are doing. If not, then please consult the FreeBSD
9 https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
11 Items affecting the ports and packages system can be found in
12 /usr/ports/UPDATING. Please read that file before updating system packages
16 13.2-RELEASE-p11 SA-24:03.unbound
20 Fix multiple vulnerabilities in unbound [SA-24:03.unbound]
22 Fix tty kernel panic [EN-24:05.tty]
24 Fix insufficient barriers in WireGuard if_wg(4) [EN-24:06.wireguard]
27 13.2-RELEASE-p10 SA-24:01.bhyveload
33 Fix bhyveload host file access [SA-24:01.bhyveload]
35 Fix jail information leak [SA-24:02.tty]
37 Timezone database information update [EN-24:01.tzdata]
39 Fix login class resource limits and CPU mask bypass [EN-24:02.libutil]
41 Fix kqueue_close page fault on exit using rfork [EN-24:03.kqueue]
44 13.2-RELEASE-p9 SA-23:19.openssh
46 Prefix Truncation Attack in the SSH protocol [SA-23:19.openssh]
49 13.2-RELEASE-p8 SA-23:18.nfsclient
51 NFS client data corruption and kernel memory disclosure [SA-23:18.nfsclient]
54 13.2-RELEASE-p7 SA-23:17.pf
57 TCP spoofing vulnerability in pf(4) [SA-23:17.pf]
59 Fix clang sanitizer failure with ASLR enabled [EN-23:15.sanitizer]
62 13.2-RELEASE-p6 EN-23:16.openzfs
64 OpenZFS data corruption [EN-23:16.openzfs]
67 13.2-RELEASE-p5 EN-23:13.freebsd-update
72 freebsd-update does not handle deep boot environments [EN-23:13.freebsd-update]
74 Incorrect regular expression escape handling [EN-23:14.regcomp]
76 libc stdio buffer overflow [SA-23:15.stdio]
78 Incorrect libcap_net limitation list manipulation [SA-23:16.cap_net]
81 13.2-RELEASE-p4 FreeBSD-EN-23:12.freebsd-update
82 FreeBSD-SA-23:12.msdosfs
83 FreeBSD-SA-23:13.capsicum
84 FreeBSD-SA-23:14.smccc
86 freebsd-update to 14.0 fails [EN-23:12.freebsd-update]
88 Fix msdosfs data disclosure [SA-23:12.msdosfs]
90 copy_file_range insufficient capability rights check [SA-23:13.capsicum]
92 arm64 boot CPUs may lack speculative execution protections [SA-23:14.smccc]
95 13.2-RELEASE-p3 FreeBSD-EN-23:09.freebsd-update
97 FreeBSD-EN-23:11.caroot
101 freebsd-update incorrectly merges files on upgrade [EN-23:09.freebsd-update]
103 PCI-e hot-plug is broken with certain devices [EN-23:10.pci-update]
105 Root certificate bundle update [EN-23:11.caroot]
107 pf incorrectly handles multiple IPv6 fragment headers [SA-23:10.pf]
109 Wi-Fi encryption bypass [SA-23:11.wifi]
112 13.2-RELEASE-p2 FreeBSD-EN-23:08.vnet
113 FreeBSD-SA-23:06.ipv6
114 FreeBSD-SA-23:07.bhyve
116 FreeBSD-SA-23:09.pam_krb5
118 VNET and DCPU modules panic on arm64 due to linker relaxation [EN-23:08.vnet]
120 Remote denial of service in IPv6 fragment reassembly [SA-23:06.ipv6]
122 bhyve privileged guest escape via fwctl [SA-23:07.bhyve]
124 Potential remote code execution via ssh-agent forwarding [SA-23:08.ssh]
126 Network authentication attack via pam_krb5 [SA-23:09.pam_krb5]
129 13.2-RELEASE-p1 FreeBSD-EN-23:06.loader
131 FreeBSD-SA-23:04.pam_krb5
133 x86 kernel console configuration [EN-23:06.loader]
135 Fix mpr(4) failure to initialize devices [EN-23:07.mpr]
137 Fix network authentication attack via pam_krb5 [SA-23:04.pam_krb5]
143 LinuxKPI pm.h changes require an update to the latest drm-kmod version
144 before re-compiling to avoid errors.
147 Bump __FreeBSD_verion to 1301501 after merging LinuxKPI and
148 net80211 changes in order to help out-of-tree consumers to deal
152 For 64-bit architectures the base system is now built with Position
153 Independent Executable (PIE) support enabled by default. It may be
154 disabled using the WITHOUT_PIE knob. A clean build is required.
157 The macros provided for the manipulation of CPU sets (e.g. CPU_AND)
158 have been modified to take 2 source arguments instead of only 1.
159 Externally maintained sources that use these macros will have to
160 be adapted. The FreeBSD version has been bumped to 1300524 to
164 Commit 18f5b477ee66 adds two arguments to VOP_ALLOCATE().
165 Normally changes to VOP calls are not MFC'd, but a
166 discussion on freebsd-current@ seemed to agree that
167 it was acceptable in this case, to fix the NFSv4.2 server.
168 Any out of source tree file system with a custom
169 VOP_ALLOCATE() call will need to be modified.
170 Bump __FreeBSD_version to 1300523 since the NFS modules need
171 to be rebuilt from sources.
174 Commit 6e8e261f0d4e changed the internal KAPI between the NFS
175 modules. As such, all the modules must be rebuilt from sources.
176 __FreeBSD_version has been bumped to 1300522.
179 Bump __FreeBSD_version to 1300521 after merging LinuxKPI and
180 net80211 changes in order to support building various wireless
181 drivers. This is to help other external consumers of LinuxKPI
182 and net80211 to deal accordingly.
185 Commit a599f9f7620b deleted the variable called nfs_maxcopyrange
186 from nfscommon.ko, since it no longer needs to be global. As such,
187 the other nfs modules must be rebuilt from up to date sources.
188 Bump __FreeBSD_version to 1300516 for this.
191 As of commit 622809b0868f OpenSSL no longer enables kernel TLS
192 by default. Users can enable kernel TLS via the "KTLS" SSL
193 option. This can be enabled globally by using a custom
194 OpenSSL config file via OPENSSL_CONF or via an
195 application-specific configuration option for applications
196 which permit setting SSL options via SSL_CONF_cmd(3).
199 Commits 9fb6e613373c and 9ec7dbf46b0a both changed the internal
200 KAPI between the NFS modules. Bump __FreeBSD_version to 1300514.
201 All NFS modules must be rebuilt from sources.
204 Commit b69019c14cd8 removes pf's DIOCGETSTATESNV ioctl.
205 As of be70c7a50d32 it is no longer used by userspace, but it does mean
206 users may not be able to enumerate pf states if they update the kernel
207 past c021ff986e2b without first updating userspace past be70c7a50d32.
210 Bump __FreeBSD_version to 1300512 after merging LinuxKPI, OFED,
211 net80211, and driver changes in order to support building
212 Intel wireless iwlwifi drivers. This is especially needed for
213 drm-kmod which needs updates after this.
216 The 20210707 awk update brought in a change in behavior. This has
217 been corrected as of d4d252c49976. Between these dates, if you
218 installed a new awk binary, you may not be able to build a new
219 kernel because the change in behavior affected the genoffset
220 script used to build the kernel. If you did update, the fix is
221 to update your sources past the above hash and do
224 % sudo -E make install
225 to enable building kernels again.
228 Commit 8a04edfdcbd2 changes the default minor version
229 used for NFSv4 mounts to the highest minor version supported
230 by the NFSv4 server. This default can be overridden by using
231 the "minorversion" mount option.
232 The consensus of a discussion on freebsd-current@ indicated
233 that this would be acceptable to do and would not be considered
237 awk has been updated to the latest one-true-awk version 20210215.
238 This contains a number of minor bug fixes.
241 Commit ca179c4d74f2/632e3f2f3a66 changed the package in which
242 the OpenSSL libraries and utilities are packaged.
243 It is recommended for pkgbase user to do:
244 pkg install -f FreeBSD-openssl
245 before pkg upgrade otherwise some dependencies might not be met
246 and pkg will stop working as libssl will not be present anymore
250 Commit 841006678745 changed the internal KAPI between the krpc
251 and nfsd modules. As such, they must both be rebuilt from
253 __FreeBSD_version is bumped to 1300510.
256 Commit 272f39942254 changed the internal KAPI between the
257 nscl.ko and nfscommon.ko modules, so they both need to be
258 rebuilt from sources.
261 Commit 5a45802b3c8c changed the internal KAPI between
262 the krpc and NFS. As such, the krpc, nfscommon and
263 nfscl modules must all be rebuilt from sources.
264 Without this patch, NFSv4.1/4.2 mounts should not
265 be done with the nfscbd(8) daemon running, to avoid
266 needing a working back channel for server->client RPCs.
269 Various LinuxKPI functionality was added which conflicts with DRM.
270 Please update your drm-kmod port to after the __FreeBSD_verison 1300139
274 The stable/13 branch has been created from main.
277 PC Card attachments for all devices have been removed. In the case of
278 wi and cmx, the entire drivers were removed because they were only
279 PC Card devices. FreeBSD_version 1300134 should be used for this
280 since it was bumped so recently.
283 Transport-independent parts of HID support have been split off the USB
284 code in to separate subsystem. Kernel configs which include one of
285 ums, ukbd, uhid, atp, wsp, wmt, uaudio, ugold or ucycom drivers should
286 be updated with adding of "device hid" line.
289 ncurses installation has been modified to only keep the widechar
290 enabled version. Incremental build is broken for that change, so it
291 requires a clean build.
294 The FreeBSD project has migrated from Subversion to Git. Temporary
295 instructions can be found at
296 https://github.com/bsdimp/freebsd-git-docs/blob/main/src-cvt.md
297 and other documents in that repo.
300 The services database has been updated to cover more of the basic
301 services expected in a modern system. The database is big enough
302 that it will cause issues in mergemaster in Releases previous to
303 12.2 and 11.3, or in very old current systems from before r358154.
306 Obsolete in-tree GDB 6.1.1 has been removed. GDB (including kgdb)
307 may be installed from ports or packages.
310 ping6 has been merged into ping. It can now be called as "ping -6".
311 See ping(8) for details.
314 Default value of net.add_addr_allfibs has been changed to 0.
315 If you have multi-fib configuration and rely on existence of all
316 interface routes in every fib, you need to set the above sysctl to 1.
318 The internal pre-processor in the calendar(1) program has been
319 extended to support more C pre-processor commands (e.g. #ifdef, #else,
320 and #undef) and to detect unbalanced conditional statements.
321 Error messages have been extended to include the filename and line
322 number if processing stops to help fixing malformed data files.
325 All the data files for the calendar(1) program, except calendar.freebsd,
326 have been moved to the deskutils/calendar-data port, much like the
327 jewish calendar entries were moved to deskutils/hebcal years ago. After
328 make delete-old-files, you need to install it to retain full
329 functionality. calendar(1) will issue a reminder for files it can't
333 LINT files are no longer generated. We now include the relevant NOTES
334 files. Note: This may cause conflicts with updating in some cases.
335 find sys -name LINT\* -delete
336 is suggested across this commit to remove the generated LINT files.
338 If you have tried to update with generated files there, the svn
339 command you want to un-auger the tree is
342 and then do the above find from the top level. Substitute 'amd64'
343 above with where the error message indicates a conflict.
346 OpenZFS support has been integrated. Do not upgrade root pools until
347 the loader is updated to support zstd. Furthermore, we caution against
348 'zpool upgrade' for the next few weeks. The change should be transparent
349 unless you want to use new features.
351 Not all "NO_CLEAN" build scenarios work across these changes. Many
352 scenarios have been tested and fixed, but rebuilding kernels without
353 rebuilding world may fail.
355 The ZFS cache file has moved from /boot to /etc to match the OpenZFS
356 upstream default. A fallback to /boot has been added for mountroot.
358 Pool auto import behavior at boot has been moved from the kernel module
359 to an explicit "zpool import -a" in one of the rc scripts enabled by
360 zfs_enable=YES. This means your non-root zpools won't auto import until
361 you upgrade your /etc/rc.d files.
364 The resume code now notifies devd with the 'kernel' system
365 rather than the old 'kern' subsystem to be consistent with
366 other use. The old notification will be created as well, but
367 will be removed prior to FreeBSD 14.0.
370 r362275 changed the internal API between the kernel RPC and the
371 NFS modules. As such, all the modules must be recompiled from
375 r364330 modified the internal API used between the NFS modules.
376 As such, all the NFS modules must be re-compiled from sources.
379 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
380 been upgraded to 11.0.0. Please see the 20141231 entry below for
381 information about prerequisites and upgrading, if you are not already
382 using clang 3.5.0 or higher.
385 r364092 modified the internal ABI used between the kernel NFS
386 modules. As such, all of these modules need to be rebuilt
387 from sources, so a version bump was done.
390 Makefile.inc has been updated to work around the issue documented in
391 20200729. It was a case where the optimization of using symbolic links
392 to point to binaries created a situation where we'd run new binaries
393 with old libraries starting midway through the installworld process.
396 r363679 has redefined some undefined behavior in regcomp(3); notably,
397 extraneous escapes of most ordinary characters will no longer be
398 accepted. An exp-run has identified all of the problems with this in
399 ports, but other non-ports software may need extra escapes removed to
400 continue to function.
402 Because of this change, installworld may encounter the following error
403 from rtld: Undefined symbol "regcomp@FBSD_1.6" -- It is imperative that
404 you do not halt installworld. Instead, let it run to completion (whether
405 successful or not) and run installworld once more.
408 A new implementation of bc and dc has been imported in r362681. This
409 implementation corrects non-conformant behavior of the previous bc
410 and adds GNU bc compatible options. It offers a number of extensions,
411 is much faster on large values, and has support for message catalogs
412 (a number of languages are already supported, contributions of further
413 languages welcome). The option WITHOUT_GH_BC can be used to build the
414 world with the previous versions of bc and dc.
417 r362639 changed the internal API used between the NFS kernel modules.
418 As such, they all need to be rebuilt from sources.
421 r362158 changed the arguments for VFS_CHECKEXP(). As such, any
422 out of tree file systems need to be modified and rebuilt.
423 Also, any file systems that are modules must be rebuilt.
426 read(2) of a directory fd is now rejected by default. root may
427 re-enable it for system root only on non-ZFS filesystems with the
428 security.bsd.allow_read_dir sysctl(8) MIB if
429 security.bsd.suser_enabled=1.
431 It may be advised to setup aliases for grep to default to `-d skip` if
432 commonly non-recursively grepping a list that includes directories and
433 the potential for the resulting stderr output is not tolerable. Example
434 aliases are now installed, commented out, in /root/.cshrc and
438 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
439 been upgraded to 10.0.1. Please see the 20141231 entry below for
440 information about prerequisites and upgrading, if you are not already
441 using clang 3.5.0 or higher.
444 Support for obsolete compilers has been removed from the build system.
445 Clang 6 and GCC 6.4 are the minimum supported versions.
448 closefrom(2) has been moved under COMPAT12, and replaced in libc with a
449 stub that calls close_range(2). If using a custom kernel configuration,
450 you may want to ensure that the COMPAT_FREEBSD12 option is included, as
451 a slightly older -CURRENT userland and older FreeBSD userlands may not
452 be functional without closefrom(2).
455 Upstream DTS from Linux 5.6 was merged and they now have the SID
456 and THS (Secure ID controller and THermal Sensor) node present.
457 The DTB overlays have now been removed from the tree for the H3/H5 and
458 A64 SoCs and the aw_sid and aw_thermal driver have been updated to
459 deal with upstream DTS. If you are using those overlays you need to
460 remove them from loader.conf and update the DTBs on the FAT partition.
463 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
464 been upgraded to 10.0.0. Please see the 20141231 entry below for
465 information about prerequisites and upgrading, if you are not already
466 using clang 3.5.0 or higher.
469 The amd(8) automount daemon has been removed from the source tree.
470 As of FreeBSD 10.1 autofs(5) is the preferred tool for automounting.
471 amd is still available in the sysutils/am-utils port.
474 Removed brooktree driver (bktr.4) from the tree.
477 The WITH_GPL_DTC option has been removed. The BSD-licenced device tree
478 compiler in usr.bin/dtc is used on all architectures which use dtc, and
479 the GPL dtc is available (if needed) from the sysutils/dtc port.
482 The WITHOUT_LLVM_LIBUNWIND option has been removed. LLVM's libunwind
483 is used by all supported CPU architectures.
486 GCC 4.2.1 has been removed from the tree. The WITH_GCC,
487 WITH_GCC_BOOTSTRAP, and WITH_GNUCXX options are no longer available.
488 Users who wish to build FreeBSD with GCC must use the external toolchain
492 ncurses has been updated to a newer version (6.2-20200215). Given the ABI
493 has changed, users will have to rebuild all the ports that are linked to
497 The size of struct vnet and the magic cookie have changed.
498 Users need to recompile libkvm and all modules using VIMAGE
499 together with their new kernel.
502 Defining the long deprecated NO_CTF, NO_DEBUG_FILES, NO_INSTALLLIB,
503 NO_MAN, NO_PROFILE, and NO_WARNS variables is now an error. Update
504 your Makefiles and scripts to define MK_<var>=no instead as required.
506 One exception to this is that program or library Makefiles should
507 define MAN to empty rather than setting MK_MAN=no.
510 Clang/LLVM is now the default compiler and LLD the default
514 make universe no longer uses GCC 4.2.1 on any architectures.
515 Architectures not supported by in-tree Clang/LLVM require an
516 external toolchain package.
519 GCC 4.2.1 is now not built by default, as part of the GCC 4.2.1
520 retirement plan. Specifically, the GCC, GCC_BOOTSTRAP, and GNUCXX
521 options default to off for all supported CPU architectures. As a
522 short-term transition aid they may be enabled via WITH_* options.
523 GCC 4.2.1 is expected to be removed from the tree on 2020-03-31.
526 Support for armv5 has been disconnected and is being removed. The
527 machine combination MACHINE=arm MACHINE_ARCH=arm is no longer valid.
528 You must now use a MACHINE_ARCH of armv6 or armv7. The default
529 MACHINE_ARCH for MACHINE=arm is now armv7.
532 Clang/LLVM is now the default compiler for all powerpc architectures.
533 LLD is now the default linker for powerpc64. The change for powerpc64
534 also includes a change to the ELFv2 ABI, incompatible with the existing
538 Kernel-loadable random(4) modules are no longer unloadable.
541 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
542 been upgraded to 9.0.1. Please see the 20141231 entry below for
543 information about prerequisites and upgrading, if you are not already
544 using clang 3.5.0 or higher.
547 r355677 has modified the internal interface used between the
548 NFS modules in the kernel. As such, they must all be upgraded
549 simultaneously. I will do a version bump for this.
552 The root certificates of the Mozilla CA Certificate Store have been
553 imported into the base system and can be managed with the certctl(8)
554 utility. If you have installed the security/ca_root_nss port or package
555 with the ETCSYMLINK option (the default), be advised that there may be
556 differences between those included in the port and those included in
557 base due to differences in nss branch used as well as general update
558 frequency. Note also that certctl(8) cannot manage certs in the
559 format used by the security/ca_root_nss port.
562 The amd(8) automount daemon has been disabled by default, and will be
563 removed in the future. As of FreeBSD 10.1 the autofs(5) is available
567 The nctgpio and wbwd drivers have been moved to the superio bus.
568 If you have one of these drivers in a kernel configuration, then
569 you should add device superio to it. If you use one of these drivers
570 as a module and you compile a custom set of modules, then you should
571 add superio to the set.
574 KPIs for network drivers to access interface addresses have changed.
575 Users need to recompile NIC driver modules together with kernel.
578 The net.link.tap.user_open sysctl no longer prevents user opening of
579 already created /dev/tapNN devices. Access is still controlled by
580 node permissions, just like tun devices. The net.link.tap.user_open
581 sysctl is now used only to allow users to perform devfs cloning of
582 tap devices, and the subsequent open may not succeed if the user is not
583 in the appropriate group. This sysctl may be deprecated/removed
584 completely in the future.
587 mips, powerpc, and sparc64 are no longer built as part of
588 universe / tinderbox unless MAKE_OBSOLETE_GCC is defined. If
589 not defined, mips, powerpc, and sparc64 builds will look for
590 the xtoolchain binaries and if installed use them for universe
591 builds. As llvm 9.0 becomes vetted for these architectures, they
592 will be removed from the list.
595 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
596 been upgraded to 9.0.0. Please see the 20141231 entry below for
597 information about prerequisites and upgrading, if you are not already
598 using clang 3.5.0 or higher.
601 The hpt27xx, hptmv, hptnr, and hptrr drivers have been removed from
602 GENERIC. They are available as modules and can be loaded by adding
603 to /boot/loader.conf hpt27xx_load="YES", hptmv_load="YES",
604 hptnr_load="YES", or hptrr_load="YES", respectively.
607 ntpd no longer by default locks its pages in memory, allowing them
608 to be paged out by the kernel. Use rlimit memlock to restore
609 historic BSD behaviour. For example, add "rlimit memlock 32"
610 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
613 Several of ping6's options have been renamed for better consistency
614 with ping. If you use any of -ARWXaghmrtwx, you must update your
615 scripts. See ping6(8) for details.
618 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
619 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
620 been removed from mount_fusefs(8). You can safely remove them from
621 your scripts, because they had no effect.
623 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
624 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
625 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
626 sysctls have been removed. If you felt the need to set any of them to
627 a non-default value, please tell asomers@FreeBSD.org why.
630 Default permissions on the /var/account/acct file (and copies of it
631 rotated by periodic daily scripts) are changed from 0644 to 0640
632 because the file contains sensitive information that should not be
633 world-readable. If the /var/account directory must be created by
634 rc.d/accounting, the mode used is now 0750. Admins who use the
635 accounting feature are encouraged to change the mode of an existing
636 /var/account directory to 0750 or 0700.
639 Entropy collection and the /dev/random device are no longer optional
640 components. The "device random" option has been removed.
641 Implementations of distilling algorithms can still be made loadable
642 with "options RANDOM_LOADABLE" (e.g., random_fortuna.ko).
645 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
646 been upgraded to 8.0.1. Please see the 20141231 entry below for
647 information about prerequisites and upgrading, if you are not already
648 using clang 3.5.0 or higher.
651 A fix was applied to i386 kernel modules to avoid panics with
652 dpcpu or vnet. Users need to recompile i386 kernel modules
653 having pcpu or vnet sections or they will refuse to load.
656 User-wired pages now have their own counter,
657 vm.stats.vm.v_user_wire_count. The vm.max_wired sysctl was renamed
658 to vm.max_user_wired and changed from an unsigned int to an unsigned
659 long. bhyve VMs wired with the -S are now subject to the user
660 wiring limit; the vm.max_user_wired sysctl may need to be tuned to
661 avoid running into the limit.
664 The IPSEC option has been removed from GENERIC. Users requiring
665 ipsec(4) must now load the ipsec(4) kernel module.
668 The tap(4) driver has been folded into tun(4), and the module has been
669 renamed to tuntap. You should update any kld_list="if_tap" or
670 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
671 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
672 module instead, and "device tap" or "device tun" entries in kernel
673 config files to select the tuntap device instead.
676 The following knobs have been added related to tradeoffs between
677 safe use of the random device and availability in the absence of
680 kern.random.initial_seeding.bypass_before_seeding: tunable; set
681 non-zero to bypass the random device prior to seeding, or zero to
682 block random requests until the random device is initially seeded.
683 For now, set to 1 (unsafe) by default to restore pre-r346250 boot
684 availability properties.
686 kern.random.initial_seeding.read_random_bypassed_before_seeding:
687 read-only diagnostic sysctl that is set when bypass is enabled and
688 read_random(9) is bypassed, to enable programmatic handling of this
689 initial condition, if desired.
691 kern.random.initial_seeding.arc4random_bypassed_before_seeding:
692 Similar to the above, but for arc4random(9) initial seeding.
694 kern.random.initial_seeding.disable_bypass_warnings: tunable; set
695 non-zero to disable warnings in dmesg when the same conditions are
696 met as for the diagnostic sysctls above. Defaults to zero, i.e.,
697 produce warnings in dmesg when the conditions are met.
700 The loadable random module KPI has changed; the random_infra_init()
701 routine now requires a 3rd function pointer for a bool (*)(void)
702 method that returns true if the random device is seeded (and
703 therefore unblocked).
706 r345895 reverts r320698. This implies that an nfsuserd(8) daemon
707 built from head sources between r320757 (July 6, 2017) and
708 r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
709 is added to the command line.
710 nfsuserd daemons built from head sources that are post-r338192 are
711 not affected and should continue to work.
714 The fuse(4) module has been renamed to fusefs(4) for consistency with
715 other filesystems. You should update any kld_load="fuse" entries in
716 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
717 "options FUSE" entries in kernel config files.
720 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
721 8.0.0. Please see the 20141231 entry below for information about
722 prerequisites and upgrading, if you are not already using clang 3.5.0
726 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
727 compiled into your custom kernel, add 'device xz' statement to the
731 drm and drm2 have been removed from the tree. Please see
732 https://wiki.freebsd.org/Graphics for the latest information on
733 migrating to the drm ports.
736 Iflib is no longer unconditionally compiled into the kernel. Drivers
737 using iflib and statically compiled into the kernel, now require
738 the 'device iflib' config option. For the same drivers loaded as
739 modules on kernels not having 'device iflib', the iflib.ko module
740 is loaded automatically.
743 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
744 options no longer exist since r343219 and r343427 respectively;
745 nothing uses them, so they should be just removed from custom
749 r342635 changes the way efibootmgr(8) works by requiring users to add
750 the -b (bootnum) parameter for commands where the bootnum was previously
751 specified with each option. For example 'efibootmgr -B 0001' is now
752 'efibootmgr -B -b 0001'.
755 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
756 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
757 servers that have vfs.nfsd.nfs_privport set will only allow mounts
758 from clients using a reserved port#. Since both the FreeBSD and Linux
759 NFSv4 clients use reserved port#s by default, this should not affect
763 The XLP config has been removed. We can't support 64-bit atomics in this
764 kernel because it is running in 32-bit mode. XLP users must transition
765 to running a 64-bit kernel (XLP64 or XLPN32).
767 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
768 the preferred emulator today and we don't need two different ones.
770 The old sibyte / swarm / Broadcom BCM1250 support has been
771 removed from the mips port.
774 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
775 7.0.1. Please see the 20141231 entry below for information about
776 prerequisites and upgrading, if you are not already using clang 3.5.0
780 Remove the timed and netdate programs from the base tree. Setting
781 the time with these daemons has been obsolete for over a decade.
784 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
785 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
786 it produces broken binaries when ifuncs are in use. Users needing
787 GNU ld should install the binutils port or package.
790 The BSD crtbegin and crtend code has been enabled by default. It has
791 had extensive testing on amd64, arm64, and i386. It can be disabled
792 by building a world with -DWITHOUT_BSD_CRTBEGIN.
795 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
796 has been converted to a port (misc/ctm) and will be removed from
797 FreeBSD-13. It is available as a package (ctm) for all supported
801 The default newsyslog.conf(5) file has been changed to only include
802 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
803 the filenames end in '.conf' and do not begin with a '.'.
805 You should check the configuration files in these two directories match
806 this naming convention. You can verify which configuration files are
807 being included using the command:
811 Ports for the DRM modules have been simplified. Now, amd64 users should
812 just install the drm-kmod port. All others should install
815 Graphics hardware that's newer than about 2010 usually works with
816 drm-kmod. For hardware older than 2013, however, some users will need
817 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
818 than 2008 usually only works in drm-legacy-kmod. The graphics team can
819 only commit to hardware made since 2013 due to the complexity of the
820 market and difficulty to test all the older cards effectively. If you
821 have hardware supported by drm-kmod, you are strongly encouraged to use
822 that as you will get better support.
824 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
825 elsewhere, the drm and drm2 modules will be eliminated from the src base
826 soon (with a limited exception for arm). Please update to the package
827 asap and report any issues to x11@freebsd.org.
829 Generally, anybody using the drm*-kmod packages should add
830 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
831 cross-threading surprises, especially with automatic driver
832 loading from X11 startup. These will become the defaults in 13-current
836 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
837 custom kernel and module loading configuration files must be updated
838 accordingly. Moreover, interfaces previous presented as ixlvN to the
839 system are now exposed as iavfN and network configuration files must
840 be adjusted as necessary.
843 OpenSSL has been updated to version 1.1.1. This update included
844 additional various API changes throughout the base system. It is
845 important to rebuild third-party software after upgrading. The value
846 of __FreeBSD_version has been bumped accordingly.
849 The legacy DRM modules and drivers have now been added to the loader's
850 module blacklist, in favor of loading them with kld_list in rc.conf(5).
851 The module blacklist may be overridden with the loader.conf(5)
852 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
856 The cam(4) based nda(4) driver will be used over nvd(4) by default on
857 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
858 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
859 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
863 Reproducible build mode is now on by default, in preparation for
864 FreeBSD 12.0. This eliminates build metadata such as the user,
865 host, and time from the kernel (and uname), unless the working tree
866 corresponds to a modified checkout from a version control system.
867 The previous behavior can be obtained by setting the /etc/src.conf
868 knob WITHOUT_REPRODUCIBLE_BUILD.
871 The Yarrow CSPRNG has been removed from the kernel as it has not been
872 supported by its designers since at least 2003. Fortuna has been the
873 default since FreeBSD-11.
876 devctl freeze/thaw have gone into the tree, the rc scripts have been
877 updated to use them and devmatch has been changed. You should update
878 kernel, userland and rc scripts all at the same time.
881 The default interpreter has been switched from 4th to Lua.
882 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
883 interpreter. If you have custom FORTH code you will need to set
884 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
885 src.conf for the build. This will create default hard links between
886 loader and loader_4th instead of loader and loader_lua, the new default.
887 If you are using UEFI it will create the proper hard link to loader.efi.
889 bhyve uses userboot.so. It remains 4th-only until some issues are solved
890 regarding coexisting with multiple versions of FreeBSD are resolved.
893 ls(1) now respects the COLORTERM environment variable used in other
894 systems and software to indicate that a colored terminal is both
895 supported and desired. If ls(1) is suddenly emitting colors, they may
896 be disabled again by either removing the unwanted COLORTERM from your
897 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
898 may not be observed in a future release.
901 The default pager for most commands has been changed to "less". To
902 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
906 The jedec_ts(4) driver has been removed. A superset of its functionality
907 is available in the jedec_dimm(4) driver, and the manpage for that
908 driver includes migration instructions. If you have "device jedec_ts"
909 in your kernel configuration file, it must be removed.
912 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
913 This should have no effect if the kernel is booted via BIOS/legacy boot.
914 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
915 has a buggy firmware that prevents a successful boot due to use of
919 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
920 support has been removed from the tree. These ports were
921 obsolete and/or known to be broken for many years.
924 loader.efi has been augmented to participate more fully in the
925 UEFI boot manager protocol. loader.efi will now look at the
926 BootXXXX environment variable to determine if a specific kernel
927 or root partition was specified. XXXX is derived from BootCurrent.
928 efibootmgr(8) manages these standard UEFI variables.
931 zfsloader's functionality has now been folded into loader.
932 zfsloader is no longer necessary once you've updated your
933 boot blocks. For a transition period, we will install a
934 hardlink for zfsloader to loader to allow a smooth transition
935 until the boot blocks can be updated (hard link because old
936 zfs boot blocks don't understand symlinks).
939 ARM64 now have efifb support, if you want to have serial console
940 on your arm64 board when an screen is connected and the bootloader
941 setup a frame buffer for us to use, just add :
945 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
946 an screen connected as the firmware will setup a frame buffer are that
947 u-boot will expose as an EFI frame buffer.
950 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
951 or take steps to update /etc/passwd before doing installworld on
952 existing systems. Do not skip the "mergemaster -Fp" step before
953 installworld, as described in the update procedures near the bottom
954 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
955 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
956 the ntp config file contain options that change file/dir locations.
957 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
958 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
959 taking steps to ensure that all required files/dirs are accessible
963 Big endian arm support has been removed.
966 The static environment setup in kernel configs is no longer mutually
967 exclusive with the loader(8) environment by default. In order to
968 restore the previous default behavior of disabling the loader(8)
969 environment if a static environment is present, you must specify
970 loader_env.disabled=1 in the static environment.
973 The ABI of syscalls used by management tools like sockstat and
974 netstat has been broken to allow 32-bit binaries to work on
975 64-bit kernels without modification. These programs will need
976 to match the kernel in order to function. External programs may
977 require minor modifications to accommodate a change of type in
978 structures from pointers to 64-bit virtual addresses.
981 On i386 and amd64 atomics are now inlined. Out of tree modules using
982 atomics will need to be rebuilt.
985 The '%I' format in the kern.corefile sysctl limits the number of
986 core files that a process can generate to the number stored in the
987 debug.ncores sysctl. The '%I' format is replaced by the single digit
988 index. Previously, if all indexes were taken the kernel would overwrite
989 only a core file with the highest index in a filename.
990 Currently the system will create a new core file if there is a free
991 index or if all slots are taken it will overwrite the oldest one.
994 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
995 6.0.1. Please see the 20141231 entry below for information about
996 prerequisites and upgrading, if you are not already using clang 3.5.0
1000 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
1001 needed to be changed to work with it. This change was made with r335763
1002 and requires a mergemaster / etcupdate / etc to update the installed
1006 r334930 changed the interface between the NFS modules, so they all
1007 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
1010 As of r334391 lld is the default amd64 system linker; it is installed
1011 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
1015 The kernel / userland interface for devinfo changed, so you'll
1016 need a new kernel and userland as a pair for it to work (rebuilding
1017 lib/libdevinfo is all that's required). devinfo and devmatch will
1018 not work, but everything else will when there's a mismatch.
1021 The on-disk format for hwpmc callchain records has changed to include
1022 threadid corresponding to a given record. This changes the field offsets
1023 and thus requires that libpmcstat be rebuilt before using a kernel
1027 The vxge(4) driver has been removed. This driver was introduced into
1028 HEAD one week before the Exar left the Ethernet market and is not
1029 known to be used. If you have device vxge in your kernel config file
1033 The amd64 kernel now requires a ld that supports ifunc to produce a
1034 working kernel, either lld or a newer binutils. lld is built by default
1035 on amd64, and the 'buildkernel' target uses it automatically. However,
1036 it is not the default linker, so building the kernel the traditional
1037 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
1038 binutils port/package). lld will soon be default, and this requirement
1041 NOTE: As of r334391 lld is the default system linker on amd64, and no
1042 workaround is necessary.
1045 The nxge(4) driver has been removed. This driver was for PCI-X 10g
1046 cards made by s2io/Neterion. The company was acquired by Exar and
1047 no longer sells or supports Ethernet products. If you have device
1048 nxge in your kernel config file it must be removed.
1051 The tz database (tzdb) has been updated to 2018e. This version more
1052 correctly models time stamps in time zones with negative DST such as
1053 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
1054 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
1055 time zone abbreviations and the tm_isdst flag.
1058 The ixgb(4) driver has been removed. This driver was for an early and
1059 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
1060 quickly shifted to the long lived ixgbe family. If you have device
1061 ixgb in your kernel config file it must be removed.
1064 The lmc(4) driver has been removed. This was a WAN interface
1065 card that was already reportedly rare in 2003, and had an ambiguous
1066 license. If you have device lmc in your kernel config file it must
1070 Support for Arcnet networks has been removed. If you have device
1071 arcnet or device cm in your kernel config file they must be
1075 Support for FDDI networks has been removed. If you have device
1076 fddi or device fpa in your kernel config file they must be
1080 In addition to supporting RFC 3164 formatted messages, the
1081 syslogd(8) service is now capable of parsing RFC 5424 formatted
1082 log messages. The main benefit of using RFC 5424 is that clients
1083 may now send log messages with timestamps containing year numbers,
1084 microseconds and time zone offsets.
1086 Similarly, the syslog(3) C library function has been altered to
1087 send RFC 5424 formatted messages to the local system logging
1088 daemon. On systems using syslogd(8), this change should have no
1089 negative impact, as long as syslogd(8) and the C library are
1090 updated at the same time. On systems using a different system
1091 logging daemon, it may be necessary to make configuration
1092 adjustments, depending on the software used.
1094 When using syslog-ng, add the 'syslog-protocol' flag to local
1095 input sources to enable parsing of RFC 5424 formatted messages:
1098 unix-dgram("/var/run/log" flags(syslog-protocol));
1101 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
1102 of the 'imuxsock' module to let messages be processed by the
1103 regular RFC 3164/5424 parsing pipeline:
1105 module(load="imuxsock" SysSock.UseSpecialParser="off")
1107 Do note that these changes only affect communication between local
1108 applications and syslogd(8). The format that syslogd(8) uses to
1109 store messages on disk or forward messages to other systems
1110 remains unchanged. syslogd(8) still uses RFC 3164 for these
1111 purposes. Options to customize this behaviour will be added in the
1112 future. Utilities that process log files stored in /var/log are
1113 thus expected to continue to function as before.
1115 __FreeBSD_version has been incremented to 1200061 to denote this
1119 Support for token ring networks has been removed. If you
1120 have "device token" in your kernel config you should remove
1121 it. No device drivers supported token ring.
1124 makefs was modified to be able to tag ISO9660 El Torito boot catalog
1125 entries as EFI instead of overloading the i386 tag as done previously.
1126 The amd64 mkisoimages.sh script used to build amd64 ISO images for
1127 release was updated to use this. This may mean that makefs must be
1128 updated before "make cdrom" can be run in the release directory. This
1129 should be as simple as:
1131 $ cd $SRCDIR/usr.sbin/makefs
1132 $ make depend all install
1135 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
1136 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
1137 Co-existence for the transition period will come shortly. Booting is a
1138 complex environment and test coverage for Lua-enabled loaders has been
1139 thin, so it would be prudent to assume it might not work and make
1140 provisions for backup boot methods.
1143 devmatch functionality has been turned on in devd. It will automatically
1144 load drivers for unattached devices. This may cause unexpected drivers
1145 to be loaded. Please report any problems to current@ and
1149 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
1150 6.0.0. Please see the 20141231 entry below for information about
1151 prerequisites and upgrading, if you are not already using clang 3.5.0
1155 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
1156 This means it is used to link the kernel and userland libraries and
1157 executables, but is not yet installed as /usr/bin/ld by default.
1159 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
1160 WITHOUT_LLD_BOOTSTRAP=yes
1163 On i386, pmtimer has been removed. Its functionality has been folded
1164 into apm. It was a no-op on ACPI in current for a while now (but was
1165 still needed on i386 in FreeBSD 11 and earlier). Users may need to
1166 remove it from kernel config files.
1169 The use of RSS hash from the network card aka flowid has been
1170 disabled by default for lagg(4) as it's currently incompatible with
1171 the lacp and loadbalance protocols.
1173 This can be re-enabled by setting the following in loader.conf:
1174 net.link.lagg.default_use_flowid="1"
1177 The SW_WATCHDOG option is no longer necessary to enable the
1178 hardclock-based software watchdog if no hardware watchdog is
1179 configured. As before, SW_WATCHDOG will cause the software
1180 watchdog to be enabled even if a hardware watchdog is configured.
1183 r326887 fixes the issue described in the 20171214 UPDATING entry.
1184 r326888 flips the switch back to building GELI support always.
1187 r362593 broke ZFS + GELI support for reasons unknown. However,
1188 it also broke ZFS support generally, so GELI has been turned off
1189 by default as the lesser evil in r326857. If you boot off ZFS and/or
1190 GELI, it might not be a good time to update.
1193 PowerPC users must update loader(8) by rebuilding world before
1194 installing a new kernel, as the protocol connecting them has
1195 changed. Without the update, loader metadata will not be passed
1196 successfully to the kernel and users will have to enter their
1197 root partition at the kernel mountroot prompt to continue booting.
1198 Newer versions of loader can boot old kernels without issue.
1201 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
1202 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
1203 to WITH/OUT_LOADER_GELI.
1206 The naive and non-compliant support of posix_fallocate(2) in ZFS
1207 has been removed as of r325320. The system call now returns EINVAL
1208 when used on a ZFS file. Although the new behavior complies with the
1209 standard, some consumers are not prepared to cope with it.
1210 One known victim is lld prior to r325420.
1213 Building in a FreeBSD src checkout will automatically create object
1214 directories now rather than store files in the current directory if
1215 'make obj' was not ran. Calling 'make obj' is no longer necessary.
1216 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
1217 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
1221 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
1222 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
1223 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
1224 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
1225 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
1226 The UNIFIED_OBJDIR option is a transitional feature that will be
1227 removed for 12.0 release; please migrate to the new format for any
1228 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
1229 than hardcoding paths.
1232 The native-xtools target no longer installs the files by default to the
1233 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
1234 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
1237 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
1238 options are changing from controlling the build if defined / undefined
1239 to controlling the build with explicit 'yes' or 'no' values. They will
1240 shift to WITH/WITHOUT options to match other options in the system.
1243 libstand has turned into a private library for sys/boot use only.
1244 It is no longer supported as a public interface outside of sys/boot.
1247 The arm port has split armv6 into armv6 and armv7. armv7 is now
1248 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
1249 and are running a kernel from before r324363, you will need to add
1250 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
1253 When building multiple kernels using KERNCONF, non-existent KERNCONF
1254 files will produce an error and buildkernel will fail. Previously
1255 missing KERNCONF files silently failed giving no indication as to
1256 why, only to subsequently discover during installkernel that the
1257 desired kernel was never built in the first place.
1260 The default serial number format for CTL LUNs has changed. This will
1261 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
1262 or iSCSI clients care about their LUNs' serial numbers. Users who
1263 require serial number stability should hardcode serial numbers in
1267 For 32-bit arm compiled for hard-float support, soft-floating point
1268 binaries now always get their shared libraries from
1269 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
1270 /usr/libsoft also existed). Only users with a hard-float ld.so, but
1271 soft-float everything else should be affected.
1274 The geli password typed at boot is now hidden. To restore the previous
1275 behavior, see geli(8) for configuration options.
1278 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
1279 sysctl values. Minor nit, but requires a rebuild of both world/kernel
1283 "make check" behavior (made in ^/head@r295380) has been changed to
1284 execute from a limited sandbox, as opposed to executing from
1288 - The "beforecheck" and "aftercheck" targets are now specified.
1289 - ${CHECKDIR} (added in commit noted above) has been removed.
1290 - Legacy behavior can be enabled by setting
1291 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
1293 If the limited sandbox mode is enabled, "make check" will execute
1294 "make distribution", then install, execute the tests, and clean up the
1295 sandbox if successful.
1297 The "make distribution" and "make install" targets are typically run as
1298 root to set appropriate permissions and ownership at installation time.
1299 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
1300 environment if executing "make check" with limited sandbox mode using
1301 an unprivileged user.
1304 Since the switch to GPT disk labels, fsck for UFS/FFS has been
1305 unable to automatically find alternate superblocks. As of r322297,
1306 the information needed to find alternate superblocks has been
1307 moved to the end of the area reserved for the boot block.
1308 Filesystems created with a newfs of this vintage or later
1309 will create the recovery information. If you have a filesystem
1310 created prior to this change and wish to have a recovery block
1311 created for your filesystem, you can do so by running fsck in
1312 foreground mode (i.e., do not use the -p or -y options). As it
1313 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
1314 to which you should answer yes.
1317 As of r321665, an NFSv4 server configuration that services
1318 Kerberos mounts or clients that do not support the uid/gid in
1319 owner/owner_group string capability, must explicitly enable
1320 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
1321 machine's /etc/rc.conf file.
1324 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
1325 Please see the 20141231 entry below for information about prerequisites
1326 and upgrading, if you are not already using clang 3.5.0 or higher.
1329 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
1330 r-commands (rlogin, rsh, etc.) to be built with the base system.
1333 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
1334 a very major ABI incompatible change, so users of FreeBSD/powerpc must
1335 be careful when performing source upgrades. It is best to run
1336 'make installworld' from an alternate root system, either a live
1337 CD/memory stick, or a temporary root partition. Additionally, all ports
1338 must be recompiled. powerpc64 is largely unaffected, except in the case
1339 of 32-bit compatibility. All 32-bit binaries will be affected.
1342 Forward compatibility for the "ino64" project have been committed. This
1343 will allow most new binaries to run on older kernels in a limited
1344 fashion. This prevents many of the common foot-shooting actions in the
1345 upgrade as well as the limited ability to roll back the kernel across
1346 the ino64 upgrade. Complicated use cases may not work properly, though
1347 enough simpler ones work to allow recovery in most situations.
1350 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
1351 if you require the GPL compiler.
1354 The internal ABI used for communication between the NFS kernel modules
1355 was changed by r320085, so __FreeBSD_version was bumped to
1356 ensure all the NFS related modules are updated together.
1359 The ABI of struct event was changed by extending the data
1360 member to 64bit and adding ext fields. For upgrade, same
1361 precautions as for the entry 20170523 "ino64" must be
1365 The GNU roff toolchain has been removed from base. To render manpages
1366 which are not supported by mandoc(1), man(1) can fallback on GNU roff
1367 from ports (and recommends to install it).
1368 To render roff(7) documents, consider using GNU roff from ports or the
1369 heirloom doctools roff toolchain from ports via pkg install groff or
1370 via pkg install heirloom-doctools.
1373 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
1374 smaller runtime footprint builds. This is useful for embedded systems
1375 which only require one chipset support.
1377 If you load it as a module, make sure this is in /boot/loader.conf:
1381 This will load the HAL, all chip/RF backends and if_ath_pci.
1382 If you have if_ath_pci in /boot/loader.conf, ensure it is after
1383 if_ath or it will not load any HAL chipset support.
1385 If you want to selectively load things (eg on ye cheape ARM/MIPS
1386 platforms where RAM is at a premium) you should:
1389 * load the chip modules in question
1390 * load ath_rate, ath_dfs
1392 * load if_ath_pci and/or if_ath_ahb depending upon your particular
1393 bus bind type - this is where probe/attach is done.
1395 For further comments/feedback, poke adrian@ .
1398 The "ino64" 64-bit inode project has been committed, which extends
1399 a number of types to 64 bits. Upgrading in place requires care and
1400 adherence to the documented upgrade procedure.
1402 If using a custom kernel configuration ensure that the
1403 COMPAT_FREEBSD11 option is included (as during the upgrade the
1404 system will be running the ino64 kernel with the existing world).
1406 For the safest in-place upgrade begin by removing previous build
1407 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full
1408 procedure documented below under the heading "To rebuild everything and
1409 install it on the current system." Specifically, a reboot is required
1410 after installing the new kernel before installing world. While an
1411 installworld normally works by accident from multiuser after rebooting
1412 the proper kernel, there are many cases where this will fail across this
1413 upgrade and installworld from single user is required.
1416 The NATM framework including the en(4), fatm(4), hatm(4), and
1417 patm(4) devices has been removed. Consumers should plan a
1418 migration before the end-of-life date for FreeBSD 11.
1421 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
1422 diff has not been implemented, if those are needed a newer version of
1423 GNU diff is available via the diffutils package under the gdiff name.
1426 As of r316810 for ipfilter, keep frags is no longer assumed when
1427 keep state is specified in a rule. r316810 aligns ipfilter with
1428 documentation in man pages separating keep frags from keep state.
1429 This allows keep state to be specified without forcing keep frags
1430 and allows keep frags to be specified independently of keep state.
1431 To maintain previous behaviour, also specify keep frags with
1432 keep state (as documented in ipf.conf.5).
1435 arm64 builds now use the base system LLD 4.0.0 linker by default,
1436 instead of requiring that the aarch64-binutils port or package be
1437 installed. To continue using aarch64-binutils, set
1438 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
1441 The UDP optimization in entry 20160818 that added the sysctl
1442 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
1443 packets will no longer be treated as L3 broadcast packets.
1446 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
1447 use any explicitly assigned loopback address available in the jail
1448 instead of using the first assigned address of the jail.
1451 The ctl.ko module no longer implements the iSCSI target frontend:
1452 cfiscsi.ko does instead.
1454 If building cfiscsi.ko as a kernel module, the module can be loaded
1455 via one of the following methods:
1456 - `cfiscsi_load="YES"` in loader.conf(5).
1457 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
1458 - ctladm(8)/ctld(8), when compiled with iSCSI support
1459 (`WITH_ISCSI=yes` in src.conf(5))
1461 Please see cfiscsi(4) for more details.
1464 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
1465 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
1466 same source (previously, the dependency of mmcsd.ko on mmc.ko was
1467 missing, but mmcsd.ko now will refuse to load if it is incompatible
1471 The syntax of ipfw(8) named states was changed to avoid ambiguity.
1472 If you have used named states in the firewall rules, you need to modify
1473 them after installworld and before rebooting. Now named states must
1474 be prefixed with colon.
1477 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
1478 removed as the userland we provide cannot use them. The KMS version
1479 (sys/dev/drm2) supports the same hardware.
1482 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
1483 Please see the 20141231 entry below for information about prerequisites
1484 and upgrading, if you are not already using clang 3.5.0 or higher.
1487 The code that provides support for ZFS .zfs/ directory functionality
1488 has been reimplemented. It's not possible now to create a snapshot
1489 by mkdir under .zfs/snapshot/. That should be the only user visible
1493 EISA bus support has been removed. The WITH_EISA option is no longer
1497 MCA bus support has been removed.
1500 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
1501 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
1504 The EM_MULTIQUEUE kernel configuration option is deprecated now that
1505 the em(4) driver conforms to iflib specifications.
1508 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
1509 IFLIB. If you have a custom kernel configuration that excludes em(4)
1510 but you use igb(4), you need to re-add em(4) to your custom
1514 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
1515 Please see the 20141231 entry below for information about prerequisites
1516 and upgrading, if you are not already using clang 3.5.0 or higher.
1519 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
1520 Please see the 20141231 entry below for information about prerequisites
1521 and upgrading, if you are not already using clang 3.5.0 or higher.
1524 The layout of the pmap structure has changed for powerpc to put the pmap
1525 statistics at the front for all CPU variations. libkvm(3) and all tools
1526 that link against it need to be recompiled.
1529 isl(4) and cyapa(4) drivers now require a new driver,
1530 chromebook_platform(4), to work properly on Chromebook-class hardware.
1531 On other types of hardware the drivers may need to be configured using
1532 device hints. Please see the corresponding manual pages for details.
1535 The urtwn(4) driver was merged into rtwn(4) and now consists of
1536 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
1538 Also, firmware for RTL8188CE was renamed due to possible name
1539 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
1542 GNU rcs has been removed from base. It is available as packages:
1543 - rcs: Latest GPLv3 GNU rcs version.
1544 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
1548 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
1549 modules now requires that the kernel configuration contain the
1550 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
1553 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
1554 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
1557 Relocatable object files with the extension of .So have been renamed
1558 to use an extension of .pico instead. The purpose of this change is
1559 to avoid a name clash with shared libraries on case-insensitive file
1560 systems. On those file systems, foo.So is the same file as foo.so.
1563 GNU rcs has been turned off by default. It can (temporarily) be built
1564 again by adding WITH_RCS knob in src.conf.
1565 Otherwise, GNU rcs is available from packages:
1566 - rcs: Latest GPLv3 GNU rcs version.
1567 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
1570 The backup_uses_rcs functionality has been removed from rc.subr.
1573 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
1574 two separate components, QUEUE_MACRO_DEBUG_TRACE and
1575 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
1576 QUEUE_MACRO_DEBUG behavior.
1579 r304787 changed some ioctl interfaces between the iSCSI userspace
1580 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1581 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1585 The UDP receive code has been updated to only treat incoming UDP
1586 packets that were addressed to an L2 broadcast address as L3
1587 broadcast packets. It is not expected that this will affect any
1588 standards-conforming UDP application. The new behaviour can be
1589 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1593 Remove the openbsd_poll system call.
1594 __FreeBSD_version has been bumped because of this.
1597 The stable/11 branch has been created from head@r302406.
1600 The libc stub for the pipe(2) system call has been replaced with
1601 a wrapper that calls the pipe2(2) system call and the pipe(2)
1602 system call is now only implemented by the kernels that include
1603 "options COMPAT_FREEBSD10" in their config file (this is the
1604 default). Users should ensure that this option is enabled in
1605 their kernel or upgrade userspace to r302092 before upgrading their
1609 CAM will now strip leading spaces from SCSI disks' serial numbers.
1610 This will affect users who create UFS filesystems on SCSI disks using
1611 those disk's diskid device nodes. For example, if /etc/fstab
1612 previously contained a line like
1613 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
1614 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
1615 transforms like gmirror may also be affected. ZFS users should
1619 The bitstring(3) API has been updated with new functionality and
1620 improved performance. But it is binary-incompatible with the old API.
1621 Objects built with the new headers may not be linked against objects
1622 built with the old headers.
1625 The brk and sbrk functions have been removed from libc on arm64.
1626 Binutils from ports has been updated to not link to these
1627 functions and should be updated to the latest version before
1628 installing a new libc.
1631 The armv6 port now defaults to hard float ABI. Limited support
1632 for running both hardfloat and soft float on the same system
1633 is available using the libraries installed with -DWITH_LIBSOFT.
1634 This has only been tested as an upgrade path for installworld
1635 and packages may fail or need manual intervention to run. New
1636 packages will be needed.
1638 To update an existing self-hosted armv6hf system, you must add
1639 TARGET_ARCH=armv6 on the make command line for both the build
1640 and the install steps.
1643 Kernel modules compiled outside of a kernel build now default to
1644 installing to /boot/modules instead of /boot/kernel. Many kernel
1645 modules built this way (such as those in ports) already overrode
1646 KMODDIR explicitly to install into /boot/modules. However,
1647 manually building and installing a module from /sys/modules will
1648 now install to /boot/modules instead of /boot/kernel.
1651 The CAM I/O scheduler has been committed to the kernel. There should be
1652 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1653 list of known rogues that claim support for this but actually corrupt
1654 data is believed to be complete, be on the lookout for data
1655 corruption. The known rogue list is believed to be complete:
1657 o Crucial MX100, M550 drives with MU01 firmware.
1658 o Micron M510 and M550 drives with MU01 firmware.
1659 o Micron M500 prior to MU07 firmware
1660 o Samsung 830, 840, and 850 all firmwares
1661 o FCCT M500 all firmwares
1663 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1664 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1665 updated firmware. Black listed drives will work correctly because these
1666 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1667 this list is the same as found in Linux, it's believed there are no
1668 other rogues in the market place. All other models from the above
1671 To be safe, if you are at all concerned, you can quirk each of your
1672 drives to prevent NCQ from being sent by setting:
1673 kern.cam.ada.X.quirks="0x2"
1674 in loader.conf. If the drive requires the 4k sector quirk, set the
1675 quirks entry to 0x3.
1678 The FAST_DEPEND build option has been removed and its functionality is
1679 now the one true way. The old mkdep(1) style of 'make depend' has
1680 been removed. See 20160311 for further details.
1683 Resource range types have grown from unsigned long to uintmax_t. All
1684 drivers, and anything using libdevinfo, need to be recompiled.
1687 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1688 builds. It no longer runs mkdep(1) during 'make depend', and the
1689 'make depend' stage can safely be skipped now as it is auto ran
1690 when building 'make all' and will generate all SRCS and DPSRCS before
1691 building anything else. Dependencies are gathered at compile time with
1692 -MF flags kept in separate .depend files per object file. Users should
1693 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1694 stale .depend files.
1697 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1698 kernel modules. Therefore, if you load any kernel modules at boot time,
1699 please install the boot loaders after you install the kernel, but before
1703 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1704 make installkernel KERNCONF=YOUR_KERNEL_HERE
1705 make -C sys/boot install
1706 <reboot in single user>
1708 Then follow the usual steps, described in the General Notes section,
1712 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1713 see the 20141231 entry below for information about prerequisites and
1714 upgrading, if you are not already using clang 3.5.0 or higher.
1717 The AIO subsystem is now a standard part of the kernel. The
1718 VFS_AIO kernel option and aio.ko kernel module have been removed.
1719 Due to stability concerns, asynchronous I/O requests are only
1720 permitted on sockets and raw disks by default. To enable
1721 asynchronous I/O requests on all file types, set the
1722 vfs.aio.enable_unsafe sysctl to a non-zero value.
1725 The ELF object manipulation tool objcopy is now provided by the
1726 ELF Tool Chain project rather than by GNU binutils. It should be a
1727 drop-in replacement, with the addition of arm64 support. The
1728 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1729 to obtain the GNU version if necessary.
1732 Building ZFS pools on top of zvols is prohibited by default. That
1733 feature has never worked safely; it's always been prone to deadlocks.
1734 Using a zvol as the backing store for a VM guest's virtual disk will
1735 still work, even if the guest is using ZFS. Legacy behavior can be
1736 restored by setting vfs.zfs.vol.recursive=1.
1739 The NONE and HPN patches has been removed from OpenSSH. They are
1740 still available in the security/openssh-portable port.
1743 With the addition of ypldap(8), a new _ypldap user is now required
1744 during installworld. "mergemaster -p" can be used to add the user
1745 prior to installworld, as documented in the handbook.
1748 The tftp loader (pxeboot) now uses the option root-path directive. As a
1749 consequence it no longer looks for a pxeboot.4th file on the tftp
1750 server. Instead it uses the regular /boot infrastructure as with the
1754 The code to start recording plug and play data into the modules has
1755 been committed. While the old tools will properly build a new kernel,
1756 a number of warnings about "unknown metadata record 4" will be produced
1757 for an older kldxref. To avoid such warnings, make sure to rebuild
1758 the kernel toolchain (or world). Make sure that you have r292078 or
1759 later when trying to build 292077 or later before rebuilding.
1762 Debug data files are now built by default with 'make buildworld' and
1763 installed with 'make installworld'. This facilitates debugging but
1764 requires more disk space both during the build and for the installed
1765 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1769 r291527 changed the internal interface between the nfsd.ko and
1770 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1771 __FreeBSD_version has been bumped because of this.
1774 Add support for unicode collation strings leads to a change of
1775 order of files listed by ls(1) for example. To get back to the old
1776 behaviour, set LC_COLLATE environment variable to "C".
1778 Databases administrators will need to reindex their databases given
1779 collation results will be different.
1781 Due to a bug in install(1) it is recommended to remove the ancient
1782 locales before running make installworld.
1784 rm -rf /usr/share/locale/*
1787 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1788 libcrypto.so.7 or libssl.so.7 must be recompiled.
1791 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1792 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1793 should be replaced with isp_2400 and isp_2500 modules respectively.
1796 The build previously allowed using 'make -n' to not recurse into
1797 sub-directories while showing what commands would be executed, and
1798 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1799 and 'make -N' will not.
1802 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1803 and etcupdate will now use this file. A custom sendmail.cf is now
1804 updated via this mechanism rather than via installworld. If you had
1805 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1806 want to remove the exclusion or change it to "always install".
1807 /etc/mail/sendmail.cf is now managed the same way regardless of
1808 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1809 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1812 Compatibility shims for legacy ATA device names have been removed.
1813 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1814 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1815 environment variables, /dev/ad* and /dev/ar* symbolic links.
1818 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1819 Please see the 20141231 entry below for information about prerequisites
1820 and upgrading, if you are not already using clang 3.5.0 or higher.
1823 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1824 and renamed from .symbols to .debug. This reduces the size requirements
1825 on the boot partition or file system and provides consistency with
1826 userland debug files.
1828 When using the supported kernel installation method the
1829 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1830 as is done with /boot/kernel.
1832 Developers wishing to maintain the historical behavior of installing
1833 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1836 The wireless drivers had undergone changes that remove the 'parent
1837 interface' from the ifconfig -l output. The rc.d network scripts
1838 used to check presence of a parent interface in the list, so old
1839 scripts would fail to start wireless networking. Thus, etcupdate(3)
1840 or mergemaster(8) run is required after kernel update, to update your
1841 rc.d scripts in /etc.
1844 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1845 These configurations are now automatically interpreted as
1846 'scrub fragment reassemble'.
1849 Kernel-loadable modules for the random(4) device are back. To use
1850 them, the kernel must have
1853 options RANDOM_LOADABLE
1855 kldload(8) can then be used to load random_fortuna.ko
1856 or random_yarrow.ko. Please note that due to the indirect
1857 function calls that the loadable modules need to provide,
1858 the build-in variants will be slightly more efficient.
1860 The random(4) kernel option RANDOM_DUMMY has been retired due to
1861 unpopularity. It was not all that useful anyway.
1864 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1865 Control over building the ELF Tool Chain tools is now provided by
1866 the WITHOUT_TOOLCHAIN knob.
1869 The polarity of Pulse Per Second (PPS) capture events with the
1870 uart(4) driver has been corrected. Prior to this change the PPS
1871 "assert" event corresponded to the trailing edge of a positive PPS
1872 pulse and the "clear" event was the leading edge of the next pulse.
1874 As the width of a PPS pulse in a typical GPS receiver is on the
1875 order of 1 millisecond, most users will not notice any significant
1876 difference with this change.
1878 Anyone who has compensated for the historical polarity reversal by
1879 configuring a negative offset equal to the pulse width will need to
1880 remove that workaround.
1883 The default group assigned to /dev/dri entries has been changed
1884 from 'wheel' to 'video' with the id of '44'. If you want to have
1885 access to the dri devices please add yourself to the video group
1888 # pw groupmod video -m $USER
1891 The menu.rc and loader.rc files will now be replaced during
1892 upgrades. Please migrate local changes to menu.rc.local and
1893 loader.rc.local instead.
1896 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1897 strings and strip have been removed. The src.conf(5) knob
1898 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1901 As ZFS requires more kernel stack pages than is the default on some
1902 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1903 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1905 Please consider using 'options KSTACK_PAGES=X' where X is greater
1906 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1909 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1910 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1911 default, i.e., they will not contain "::". For example, instead
1912 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1913 to have a more specific match, such as different map entries for
1914 IPv6:0:0 vs IPv6:0. This change requires that configuration
1915 data (including maps, files, classes, custom ruleset, etc.) must
1916 use the same format, so make certain such configuration data is
1917 upgrading. As a very simple check search for patterns like
1918 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1919 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1920 the cf option UseCompressedIPv6Addresses.
1923 The default kernel entropy-processing algorithm is now
1924 Fortuna, replacing Yarrow.
1926 Assuming you have 'device random' in your kernel config
1927 file, the configurations allow a kernel option to override
1928 this default. You may choose *ONE* of:
1930 options RANDOM_YARROW # Legacy /dev/random algorithm.
1931 options RANDOM_DUMMY # Blocking-only driver.
1933 If you have neither, you get Fortuna. For most people,
1934 read no further, Fortuna will give a /dev/random that works
1935 like it always used to, and the difference will be irrelevant.
1937 If you remove 'device random', you get *NO* kernel-processed
1938 entropy at all. This may be acceptable to folks building
1939 embedded systems, but has complications. Carry on reading,
1940 and it is assumed you know what you need.
1942 *PLEASE* read random(4) and random(9) if you are in the
1943 habit of tweaking kernel configs, and/or if you are a member
1944 of the embedded community, wanting specific and not-usual
1945 behaviour from your security subsystems.
1947 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1948 random', you will NOT have a functioning /dev/random, and
1949 many cryptographic features will not work, including SSH.
1950 You may also find strange behaviour from the random(3) set
1951 of library functions, in particular sranddev(3), srandomdev(3)
1952 and arc4random(3). The reason for this is that the KERN_ARND
1953 sysctl only returns entropy if it thinks it has some to
1954 share, and with RANDOM_DUMMY or no 'device random' this
1958 An additional fix for the issue described in the 20150614 sendmail
1959 entry below has been committed in revision 284717.
1962 FreeBSD's old make (fmake) has been removed from the system. It is
1963 available as the devel/fmake port or via pkg install fmake.
1966 The fix for the issue described in the 20150614 sendmail entry
1967 below has been committed in revision 284436. The work
1968 around described in that entry is no longer needed unless the
1969 default setting is overridden by a confDH_PARAMETERS configuration
1970 setting of '5' or pointing to a 512 bit DH parameter file.
1973 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1974 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1975 and devel/kyua to version 0.20+ and adjust any calling code to work
1976 with Kyuafile and kyua.
1979 The import of openssl to address the FreeBSD-SA-15:10.openssl
1980 security advisory includes a change which rejects handshakes
1981 with DH parameters below 768 bits. sendmail releases prior
1982 to 8.15.2 (not yet released), defaulted to a 512 bit
1983 DH parameter setting for client connections. To work around
1984 this interoperability, sendmail can be configured to use a
1985 2048 bit DH parameter by:
1987 1. Edit /etc/mail/`hostname`.mc
1988 2. If a setting for confDH_PARAMETERS does not exist or
1989 exists and is set to a string beginning with '5',
1990 replace it with '2'.
1991 3. If a setting for confDH_PARAMETERS exists and is set to
1992 a file path, create a new file with:
1993 openssl dhparam -out /path/to/file 2048
1994 4. Rebuild the .cf file:
1995 cd /etc/mail/; make; make install
1996 5. Restart sendmail:
1997 cd /etc/mail/; make restart
1999 A sendmail patch is coming, at which time this file will be
2003 Generation of legacy formatted entries have been disabled by default
2004 in pwd_mkdb(8), as all base system consumers of the legacy formatted
2005 entries were converted to use the new format by default when the new,
2006 machine independent format have been added and supported since FreeBSD
2009 Please see the pwd_mkdb(8) manual page for further details.
2012 Clang and llvm have been upgraded to 3.6.1 release. Please see the
2013 20141231 entry below for information about prerequisites and upgrading,
2014 if you are not already using 3.5.0 or higher.
2017 TI platform code switched to using vendor DTS files and this update
2018 may break existing systems running on Beaglebone, Beaglebone Black,
2021 - dtb files should be regenerated/reinstalled. Filenames are the
2022 same but content is different now
2023 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
2024 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
2025 addressing scheme is now pin 25 on /dev/gpioc3.
2026 - Pandaboard: /etc/ttys should be updated, serial console device is
2027 now /dev/ttyu2, not /dev/ttyu0
2030 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
2031 If you need the GNU extension from groff soelim(1), install groff
2032 from package: pkg install groff, or via ports: textproc/groff.
2035 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
2036 defined in symlink(7); previously symlinks were silently ignored.
2039 The const qualifier has been removed from iconv(3) to comply with
2040 POSIX. The ports tree is aware of this from r384038 onwards.
2043 Libraries specified by LIBADD in Makefiles must have a corresponding
2044 DPADD_<lib> variable to ensure correct dependencies. This is now
2045 enforced in src.libnames.mk.
2048 From legacy ata(4) driver was removed support for SATA controllers
2049 supported by more functional drivers ahci(4), siis(4) and mvs(4).
2050 Kernel modules ataahci and ataadaptec were removed completely,
2051 replaced by ahci and mvs modules respectively.
2054 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
2055 the 20141231 entry below for information about prerequisites and
2056 upgrading, if you are not already using 3.5.0 or higher.
2059 The 32-bit PowerPC kernel has been changed to a position-independent
2060 executable. This can only be booted with a version of loader(8)
2061 newer than January 31, 2015, so make sure to update both world and
2062 kernel before rebooting.
2065 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
2066 but before r278950, the RNG was not seeded properly. Immediately
2067 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
2068 ssh keys or openssl keys) that were generated w/ a kernel from that
2069 range. This does not affect programs that directly used /dev/random
2070 or /dev/urandom. All userland uses of arc4random(3) are affected.
2073 The autofs(4) ABI was changed in order to restore binary compatibility
2074 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
2075 with the new kernel.
2078 The powerpc64 kernel has been changed to a position-independent
2079 executable. This can only be booted with a new version of loader(8),
2080 so make sure to update both world and kernel before rebooting.
2083 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
2084 only release, no new features have been added. Please see the 20141231
2085 entry below for information about prerequisites and upgrading, if you
2086 are not already using 3.5.0.
2089 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
2090 taken from the ELF Tool Chain project rather than GNU binutils. They
2091 should be drop-in replacements, with the addition of arm64 support.
2092 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
2093 binutils tools, if necessary. See 20150805 for updated information.
2096 The default Unbound configuration now enables remote control
2097 using a local socket. Users who have already enabled the
2098 local_unbound service should regenerate their configuration
2099 by running "service local_unbound setup" as root.
2102 The GNU texinfo and GNU info pages have been removed.
2103 To be able to view GNU info pages please install texinfo from ports.
2106 Clang, llvm and lldb have been upgraded to 3.5.0 release.
2108 As of this release, a prerequisite for building clang, llvm and lldb is
2109 a C++11 capable compiler and C++11 standard library. This means that to
2110 be able to successfully build the cross-tools stage of buildworld, with
2111 clang as the bootstrap compiler, your system compiler or cross compiler
2112 should either be clang 3.3 or later, or gcc 4.8 or later, and your
2113 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
2116 On any standard FreeBSD 10.x or 11.x installation, where clang and
2117 libc++ are on by default (that is, on x86 or arm), this should work out
2120 On 9.x installations where clang is enabled by default, e.g. on x86 and
2121 powerpc, libc++ will not be enabled by default, so libc++ should be
2122 built (with clang) and installed first. If both clang and libc++ are
2123 missing, build clang first, then use it to build libc++.
2125 On 8.x and earlier installations, upgrade to 9.x first, and then follow
2126 the instructions for 9.x above.
2128 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
2129 default, and do not build clang.
2131 Many embedded systems are resource constrained, and will not be able to
2132 build clang in a reasonable time, or in some cases at all. In those
2133 cases, cross building bootable systems on amd64 is a workaround.
2135 This new version of clang introduces a number of new warnings, of which
2136 the following are most likely to appear:
2140 This warns in two cases, for both C and C++:
2141 * When the code is trying to take the absolute value of an unsigned
2142 quantity, which is effectively a no-op, and almost never what was
2143 intended. The code should be fixed, if at all possible. If you are
2144 sure that the unsigned quantity can be safely cast to signed, without
2145 loss of information or undefined behavior, you can add an explicit
2146 cast, or disable the warning.
2148 * When the code is trying to take an absolute value, but the called
2149 abs() variant is for the wrong type, which can lead to truncation.
2150 If you want to disable the warning instead of fixing the code, please
2151 make sure that truncation will not occur, or it might lead to unwanted
2154 -Wtautological-undefined-compare and
2155 -Wundefined-bool-conversion
2157 These warn when C++ code is trying to compare 'this' against NULL, while
2158 'this' should never be NULL in well-defined C++ code. However, there is
2159 some legacy (pre C++11) code out there, which actively abuses this
2160 feature, which was less strictly defined in previous C++ versions.
2162 Squid and openjdk do this, for example. The warning can be turned off
2163 for C++98 and earlier, but compiling the code in C++11 mode might result
2164 in unexpected behavior; for example, the parts of the program that are
2165 unreachable could be optimized away.
2168 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
2169 kernel sources have been removed. The .h files remain, since some
2170 utilities include them. This will need to be fixed later.
2171 If "mount -t oldnfs ..." is attempted, it will fail.
2172 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
2173 the utilities will report errors.
2176 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
2177 directories to top level SUBDIR variable when their parent
2178 directory is included in LOCAL_DIRS. Users with build systems with
2179 such hierarchies and without SUBDIR entries in the parent
2180 directory Makefiles should add them or add the directories to
2184 faith(4) and faithd(8) have been removed from the base system. Faith
2185 has been obsolete for a very long time.
2188 vt(4), the new console driver, is enabled by default. It brings
2189 support for Unicode and double-width characters, as well as
2190 support for UEFI and integration with the KMS kernel video
2193 You may need to update your console settings in /etc/rc.conf,
2194 most probably the keymap. During boot, /etc/rc.d/syscons will
2195 indicate what you need to do.
2197 vt(4) still has issues and lacks some features compared to
2198 syscons(4). See the wiki for up-to-date information:
2199 https://wiki.freebsd.org/Newcons
2201 If you want to keep using syscons(4), you can do so by adding
2202 the following line to /boot/loader.conf:
2206 pjdfstest has been integrated into kyua as an opt-in test suite.
2207 Please see share/doc/pjdfstest/README for more details on how to
2211 gperf has been removed from the base system for architectures
2212 that use clang. Ports that require gperf will obtain it from the
2216 pjdfstest has been moved from tools/regression/pjdfstest to
2220 At svn r271982, The default linux compat kernel ABI has been adjusted
2221 to 2.6.18 in support of the linux-c6 compat ports infrastructure
2222 update. If you wish to continue using the linux-f10 compat ports,
2223 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
2224 encouraged to update their linux-compat packages to linux-c6 during
2225 their next update cycle.
2228 The ofwfb driver, used to provide a graphics console on PowerPC when
2229 using vt(4), no longer allows mmap() of all physical memory. This
2230 will prevent Xorg on PowerPC with some ATI graphics cards from
2231 initializing properly unless x11-servers/xorg-server is updated to
2235 The xdev targets have been converted to using TARGET and
2236 TARGET_ARCH instead of XDEV and XDEV_ARCH.
2239 The default unbound configuration has been modified to address
2240 issues with reverse lookups on networks that use private
2241 address ranges. If you use the local_unbound service, run
2242 "service local_unbound setup" as root to regenerate your
2243 configuration, then "service local_unbound reload" to load the
2247 The GNU texinfo and GNU info pages are not built and installed
2248 anymore, WITH_INFO knob has been added to allow to built and install
2250 UPDATE: see 20150102 entry on texinfo's removal
2253 The GNU readline library is now an INTERNALLIB - that is, it is
2254 statically linked into consumers (GDB and variants) in the base
2255 system, and the shared library is no longer installed. The
2256 devel/readline port is available for third party software that
2260 The Itanium architecture (ia64) has been removed from the list of
2261 known architectures. This is the first step in the removal of the
2265 Commit r268115 has added NFSv4.1 server support, merged from
2266 projects/nfsv4.1-server. Since this includes changes to the
2267 internal interfaces between the NFS related modules, a full
2268 build of the kernel and modules will be necessary.
2269 __FreeBSD_version has been bumped.
2272 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
2273 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
2274 which differs from the behaviour controlled by this knob.)
2277 Maximal length of the serial number in CTL was increased from 16 to
2278 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
2279 and ctld, need to be rebuilt to work with a new kernel.
2282 The libatf-c and libatf-c++ major versions were downgraded to 0 and
2283 1 respectively to match the upstream numbers. They were out of
2284 sync because, when they were originally added to FreeBSD, the
2285 upstream versions were not respected. These libraries are private
2286 and not yet built by default, so renumbering them should be a
2287 non-issue. However, unclean source trees will yield broken test
2288 programs once the operator executes "make delete-old-libs" after a
2289 "make installworld".
2291 Additionally, the atf-sh binary was made private by moving it into
2292 /usr/libexec/. Already-built shell test programs will keep the
2293 path to the old binary so they will break after "make delete-old"
2296 If you are using WITH_TESTS=yes (not the default), wipe the object
2297 tree and rebuild from scratch to prevent spurious test failures.
2298 This is only needed once: the misnumbered libraries and misplaced
2299 binaries have been added to OptionalObsoleteFiles.inc so they will
2300 be removed during a clean upgrade.
2303 Clang and llvm have been upgraded to 3.4.1 release.
2306 We bogusly installed src.opts.mk in /usr/share/mk. This file should
2307 be removed to avoid issues in the future (and has been added to
2311 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
2312 past, it affected all builds that used the bsd.*.mk files. The old
2313 behavior was a bug, but people may have relied upon it. To get this
2314 behavior back, you can .include /etc/src.conf from /etc/make.conf
2315 (which is still global and isn't changed). This also changes the
2316 behavior of incremental builds inside the tree of individual
2317 directories. Set MAKESYSPATH to ".../share/mk" to do that.
2318 Although this has survived make universe and some upgrade scenarios,
2319 other upgrade scenarios may have broken. At least one form of
2320 temporary breakage was fixed with MAKESYSPATH settings for buildworld
2321 as well... In cases where MAKESYSPATH isn't working with this
2322 setting, you'll need to set it to the full path to your tree.
2324 One side effect of all this cleaning up is that bsd.compiler.mk
2325 is no longer implicitly included by bsd.own.mk. If you wish to
2326 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
2330 The lindev device has been removed since /dev/full has been made a
2331 standard device. __FreeBSD_version has been bumped.
2334 The knob WITHOUT_VI was added to the base system, which controls
2335 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
2336 in order to reorder files share/termcap and didn't build ex(1) as a
2337 build tool, so building/installing with WITH_VI is highly advised for
2338 build hosts for older releases.
2340 This issue has been fixed in stable/9 and stable/10 in r277022 and
2341 r276991, respectively.
2344 The YES_HESIOD knob has been removed. It has been obsolete for
2345 a decade. Please move to using WITH_HESIOD instead or your builds
2346 will silently lack HESIOD.
2349 The uart(4) driver has been changed with respect to its handling
2350 of the low-level console. Previously the uart(4) driver prevented
2351 any process from changing the baudrate or the CLOCAL and HUPCL
2352 control flags. By removing the restrictions, operators can make
2353 changes to the serial console port without having to reboot.
2354 However, when getty(8) is started on the serial device that is
2355 associated with the low-level console, a misconfigured terminal
2356 line in /etc/ttys will now have a real impact.
2357 Before upgrading the kernel, make sure that /etc/ttys has the
2358 serial console device configured as 3wire without baudrate to
2359 preserve the previous behaviour. E.g:
2360 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
2363 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
2364 to improve performance. To re-enable it, if needed, run rpcbind
2365 with command line option -W.
2368 Switched back to the GPL dtc compiler due to updates in the upstream
2369 dts files not being supported by the BSDL dtc compiler. You will need
2370 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
2371 may result while building dtb files during a kernel build if you fail
2372 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
2375 Clang and llvm have been upgraded to 3.4 release.
2378 The nve(4) driver has been removed. Please use the nfe(4) driver
2379 for NVIDIA nForce MCP Ethernet adapters instead.
2382 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
2383 This could cause certain C++ applications using shared libraries built
2384 against the previous version of libc++ to crash. The incompatibility
2385 has now been fixed, but any C++ applications or shared libraries built
2386 between r261283 and r261801 should be recompiled.
2389 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
2390 capability mode support. Please note that enabling the feature in
2391 kernel is still highly recommended.
2394 OpenSSH is now built with sandbox support, and will use sandbox as
2395 the default privilege separation method. This requires Capsicum
2396 capability mode support in kernel.
2399 The libelf and libdwarf libraries have been updated to newer
2400 versions from upstream. Shared library version numbers for
2401 these two libraries were bumped. Any ports or binaries
2402 requiring these two libraries should be recompiled.
2403 __FreeBSD_version is bumped to 1100006.
2406 If a Makefile in a tests/ directory was auto-generating a Kyuafile
2407 instead of providing an explicit one, this would prevent such
2408 Makefile from providing its own Kyuafile in the future during
2409 NO_CLEAN builds. This has been fixed in the Makefiles but manual
2410 intervention is needed to clean an objdir if you use NO_CLEAN:
2411 # find /usr/obj -name Kyuafile | xargs rm -f
2414 The behavior of gss_pseudo_random() for the krb5 mechanism
2415 has changed, for applications requesting a longer random string
2416 than produced by the underlying enctype's pseudo-random() function.
2417 In particular, the random string produced from a session key of
2418 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
2419 be different at the 17th octet and later, after this change.
2420 The counter used in the PRF+ construction is now encoded as a
2421 big-endian integer in accordance with RFC 4402.
2422 __FreeBSD_version is bumped to 1100004.
2425 The WITHOUT_ATF build knob has been removed and its functionality
2426 has been subsumed into the more generic WITHOUT_TESTS. If you were
2427 using the former to disable the build of the ATF libraries, you
2428 should change your settings to use the latter.
2431 The default version of mtree is nmtree which is obtained from
2432 NetBSD. The output is generally the same, but may vary
2433 slightly. If you found you need identical output adding
2434 "-F freebsd9" to the command line should do the trick. For the
2435 time being, the old mtree is available as fmtree.
2438 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
2439 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
2440 1.1.4_8 and verify bsdyml not linked in, before running "make
2442 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
2444 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
2447 The stable/10 branch has been created in subversion from head
2454 Sometimes, obscure build problems are the result of environment
2455 poisoning. This can happen because the make utility reads its
2456 environment when searching for values for global variables. To run
2457 your build attempts in an "environmental clean room", prefix all make
2458 commands with 'env -i '. See the env(1) manual page for more details.
2459 Occasionally a build failure will occur with "make -j" due to a race
2460 condition. If this happens try building again without -j, and please
2461 report a bug if it happens consistently.
2463 When upgrading from one major version to another it is generally best to
2464 upgrade to the latest code in the currently installed branch first, then
2465 do an upgrade to the new branch. This is the best-tested upgrade path,
2466 and has the highest probability of being successful. Please try this
2467 approach if you encounter problems with a major version upgrade. Since
2468 the stable 4.x branch point, one has generally been able to upgrade from
2469 anywhere in the most recent stable branch to head / current (or even the
2470 last couple of stable branches). See the top of this file when there's
2473 The update process will emit an error on an attempt to perform a build
2474 or install from a FreeBSD version below the earliest supported version.
2475 When updating from an older version the update should be performed one
2476 major release at a time, including running `make delete-old` at each
2479 When upgrading a live system, having a root shell around before
2480 installing anything can help undo problems. Not having a root shell
2481 around can lead to problems if pam has changed too much from your
2482 starting point to allow continued authentication after the upgrade.
2484 This file should be read as a log of events. When a later event changes
2485 information of a prior event, the prior event should not be deleted.
2486 Instead, a pointer to the entry with the new information should be
2487 placed in the old entry. Readers of this file should also sanity check
2488 older entries before relying on them blindly. Authors of new entries
2489 should write them with this in mind.
2493 When upgrading the boot ZFS pool to a new version, always follow
2496 1.) recompile and reinstall the ZFS boot loader and boot block
2497 (this is part of "make buildworld" and "make installworld")
2499 2.) update the ZFS boot block on your boot drive
2501 The following example updates the ZFS boot block on the
2502 freebsd-boot partition of a GPT partitioned drive ada0:
2503 "gpart bootcode -p /boot/gptzfsboot -i $N ada0"
2504 The value $N will typically be 1 (if booting from BIOS) or 2 (if
2507 Non-boot pools do not need these updates.
2511 If you are updating from a prior version of FreeBSD (even one just
2512 a few days old), you should follow this procedure. It is the most
2513 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2515 make kernel-toolchain
2516 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2517 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2519 To test a kernel once
2520 ---------------------
2521 If you just want to boot a kernel once (because you are not sure
2522 if it works, or if you want to boot a known bad kernel to provide
2523 debugging information) run
2524 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2525 nextboot -k testkernel
2527 To rebuild everything and install it on the current system.
2528 -----------------------------------------------------------
2529 # Note: sometimes if you are running current you gotta do more than
2530 # is listed here if you are upgrading from a really old current.
2532 <make sure you have good level 0 dumps>
2534 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2535 make installkernel KERNCONF=YOUR_KERNEL_HERE
2537 <reboot in single user> [3]
2544 To cross-install current onto a separate partition
2545 --------------------------------------------------
2546 # In this approach we use a separate partition to hold
2547 # current's root, 'usr', and 'var' directories. A partition
2548 # holding "/", "/usr" and "/var" should be about 2GB in
2551 <make sure you have good level 0 dumps>
2554 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2555 <maybe newfs current's root partition>
2556 <mount current's root partition on directory ${CURRENT_ROOT}>
2557 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
2558 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2559 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2560 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2561 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2562 <reboot into current>
2563 <do a "native" rebuild/install as described in the previous section>
2564 <maybe install compatibility libraries from ports/misc/compat*>
2568 To upgrade in-place from stable to current
2569 ----------------------------------------------
2570 <make sure you have good level 0 dumps>
2572 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
2573 make installkernel KERNCONF=YOUR_KERNEL_HERE
2575 <reboot in single user> [3]
2582 Make sure that you've read the UPDATING file to understand the
2583 tweaks to various things you need. At this point in the life
2584 cycle of current, things change often and you are on your own
2585 to cope. The defaults can also change, so please read ALL of
2586 the UPDATING entries.
2588 Also, if you are tracking -current, you must be subscribed to
2589 freebsd-current@freebsd.org. Make sure that before you update
2590 your sources that you have read and understood all the recent
2591 messages there. If in doubt, please track -stable which has
2592 much fewer pitfalls.
2594 [1] If you have third party modules, such as vmware, you should disable
2595 them at this point so they don't crash your system on
2596 reboot. Alternatively, you should rebuild all the modules you have in
2597 your system and install them as well. If you are running -current, you
2598 should seriously consider placing all sources to all the modules for
2599 your system (or symlinks to them) in /usr/local/sys/modules so this
2600 happens automatically. If all your modules come from ports, then adding
2601 the port origin directories to PORTS_MODULES instead is also automatic
2603 PORTS_MODULES+=x11/nvidia-driver
2605 [3] From the bootblocks, boot -s, and then do
2609 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed
2610 cd src # full path to source
2611 adjkerntz -i # if CMOS is wall time
2612 Also, when doing a major release upgrade, it is required that you boot
2613 into single user mode to do the installworld.
2615 [4] Note: This step is non-optional. Failure to do this step
2616 can result in a significant reduction in the functionality of the
2617 system. Attempting to do it by hand is not recommended and those
2618 that pursue this avenue should read this file carefully, as well
2619 as the archives of freebsd-current and freebsd-hackers mailing lists
2620 for potential gotchas. The -U option is also useful to consider.
2621 See mergemaster(8) for more information.
2623 [5] Usually this step is a no-op. However, from time to time
2624 you may need to do this if you get unknown user in the following
2625 step. It never hurts to do it all the time. You may need to
2626 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2627 install) after the buildworld before this step if you last updated
2628 from current before 20130425 or from -stable before 20130430.
2630 [6] This only deletes old files and directories. Old libraries
2631 can be deleted by "make delete-old-libs", but you have to make
2632 sure that no program is using those libraries anymore.
2634 [8] The new kernel must be able to run existing binaries used by an
2635 installworld. When upgrading across major versions, the new kernel's
2636 configuration must include the correct COMPAT_FREEBSD<n> option for
2637 existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure
2638 to do so may leave you with a system that is hard to boot to recover. A
2639 GENERIC kernel will include suitable compatibility options to run
2640 binaries from older branches. Note that the ability to run binaries
2641 from unsupported branches is not guaranteed.
2643 Make sure that you merge any new devices from GENERIC since the
2644 last time you updated your kernel config file. Options also
2645 change over time, so you may need to adjust your custom kernels
2648 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2649 "?=" instead of the "=" assignment operator, so that buildworld can
2650 override the CPUTYPE if it needs to.
2652 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2653 not on the command line, or in /etc/make.conf. buildworld will
2654 warn if it is improperly defined.
2657 This file contains a list, in reverse chronological order, of major
2658 breakages in tracking -current. It is not guaranteed to be a complete
2659 list of such breakages, and only contains entries since September 23, 2011.
2660 If you need to see UPDATING entries from before that date, you will need
2661 to fetch an UPDATING file from an older FreeBSD release.
2663 Copyright information:
2665 Copyright 1998-2009 M. Warner Losh <imp@FreeBSD.org>
2667 Redistribution, publication, translation and use, with or without
2668 modification, in full or in part, in any form or format of this
2669 document are permitted without further permission from the author.
2671 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2672 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2673 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2674 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2675 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2676 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2677 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2678 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2679 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2680 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2681 POSSIBILITY OF SUCH DAMAGE.
2683 Contact Warner Losh if you have any questions about your use of