1 Updating Information for users of FreeBSD-CURRENT.
3 This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>.
4 See end of file for further details. For commonly done items, please see the
5 COMMON ITEMS: section later in the file. These instructions assume that you
6 basically know what you are doing. If not, then please consult the FreeBSD
9 https://docs.freebsd.org/en/books/handbook/cutting-edge/#makeworld
11 Items affecting the ports and packages system can be found in
12 /usr/ports/UPDATING. Please read that file before updating system packages
15 NOTE TO PEOPLE WHO THINK THAT FreeBSD 15.x IS SLOW:
16 FreeBSD 15.x has many debugging features turned on, in both the kernel
17 and userland. These features attempt to detect incorrect use of
18 system primitives, and encourage loud failure through extra sanity
19 checking and fail stop semantics. They also substantially impact
20 system performance. If you want to do performance measurement,
21 benchmarking, and optimization, you'll want to turn them off. This
22 includes various WITNESS- related kernel options, INVARIANTS, malloc
23 debugging flags in userland, and various verbose features in the
24 kernel. Many developers choose to disable these features on build
25 machines to maximize performance. (To completely disable malloc
26 debugging, define WITH_MALLOC_PRODUCTION in /etc/src.conf and rebuild
27 world, or to merely disable the most expensive debugging functionality
28 at runtime, run "ln -s 'abort:false,junk:false' /etc/malloc.conf".)
31 Forward compatibility (running the new code on old kernels) for the
32 "ino64" project have been removed. The need for it has passed long ago.
35 Commit 57ce37f9dcd0 changed the internal KAPI between the
36 nfscommon and nfscl modules. Both must be rebuilt from sources.
39 dialog(1) has been replaced in base by bsddialog(1), while most of the
40 time replacing a dialog(1) call by a bsddialog(1) call works out of the
41 box, bsddialog(1) is not considered as a drop-in replacement for
44 If you do depend on dialog(1) functionality, please install cdialog
50 The EARLY_AP_STARTUP kernel option is mandatory on x86. The option
51 has been added to DEFAULTS, so it should automatically be included in
52 custom kernel configurations without any additional change.
55 A new loader tunable net.pf.default_to_drop allows pf(4)’s default
56 behaviour to be changed from pass to drop. Previously this required
57 recompiling the kernel with the option PF_DEFAULT_TO_DROP.
60 Enable splitting out pkgbase manpages into separate packages by
61 default. To disable this, set WITHOUT_MANSPLITPKG=yes in src.conf.
64 Move standard include files to the clibs-dev package and move clang
65 internal libraries and headers to clang and clang-dev. Upgrading systems
66 installed using pkgbase past this change involves extra steps to allow
69 pkg upgrade -y FreeBSD-utilities
70 pkg upgrade -y FreeBSD-utilities-dev
74 Enable vnet sysctl variables to be loader tunable. SYSCTLs which
75 belongs to VNETs can be initialized during early boot or module
76 loading if they are marked with CTLFLAG_TUN and there are
77 corresponding kernel environment variables.
80 The WITH_INIT_ALL_PATTERN and WITH_INIT_ALL_ZERO build options have
81 been replaced by INIT_ALL=pattern and INIT_ALL=zero respectively.
87 Serial communication (in boot loaders, kernel, and userland) has
88 been changed to default to 115200 bps, in line with common industry
89 practice and typcial firmware serial console redirection
92 Note that the early x86 BIOS bootloader (i.e., boot0sio) does not
93 support rates above 9600 bps and is not changed. boot0sio users may
94 set BOOT_COMCONSOLE_SPEED=9600 to use 9600 for all of the boot
95 components, or use the standard boot0 and have the boot2 stage start
96 with the serial port at 115200.
99 Following the general removal of MIPS support, the ath(4) AHB bus-
100 frontend has been removed, too, and building of the PCI support is
101 integrated with the ath(4) main module again. As a result, there's
102 no longer a need for if_ath_pci_load="YES" in /boot/loader.conf or
103 "device ath_pci" in the kernel configuration.
106 MAXCPU has been increased to 1024 in the amd64 GENERIC kernel config.
107 Out-of-tree kernel modules will need to be rebuilt.
110 CAM has been mechanically updated s/u_int(64|32|16|8)_t/uint\1_t/g
111 to move to the standard uintXX_t types from the old, traditional
112 BSD u_intXX_t types. This should be a NOP, but may cause problems
113 for out of tree changes. The SIMs were not updated since most of
114 the old u_intXX_t uses weren't due to CAM interfaces.
117 stable/14 branch created.
120 The heuristic for detecting old chromebooks with an EC bug that requires
121 atkbdc driver workarounds has changed. There should be no functional
122 change, but if your old chromebook's keyboard stops working, please
123 file a PR and assign it to imp.
126 OpenSSL has been updated to version 3.0, including changes throughout
127 the base system. It is important to rebuild third-party software
131 To enable pf rdr rules for connections initiated from the host, pf
132 filter rules can be optionally enabled for packets delivered
133 locally. This can change the behavior of rules which match packets
134 delivered to lo0. To enable this feature:
136 sysctl net.pf.filter_local=1
139 When enabled, its best to ensure that packets delivered locally are not
140 filtered, e.g. by adding a 'skip on lo' rule.
143 Improvements to libtacplus(8) mean that tacplus.conf(5) now
144 follows POSIX shell syntax rules. This may cause TACACS+
145 authentication to fail if the shared secret contains a single
146 quote, double quote, or backslash character which isn't
147 already properly quoted or escaped.
150 Belatedly switch the default nvme block device on x86 from nvd to nda.
151 nda created nvd compatibility links by default, so this should be a
152 nop. If this causes problems for your application, set hw.nvme.use_nvd=1
153 in your loader.conf or add `options NVME_USE_NVD=1` to your kernel
154 config. To disable the nvd compatibility aliases, add
155 kern.cam.nda.nvd_compat=0 to loader.conf. The default has been nda on
156 all non-x86 platforms for some time now. If you need to fall back,
157 please email imp@freebsd.org about why.
159 Encrypted swap partitions need to be changed from nvd to nda if you
160 migrate, or you need to use the above to switch back to nvd.
163 Remove portsnap(8). Users are encouraged to obtain the ports tree
167 Add jobs.mk to save typing. Enables -j${JOB_MAX} and logging
171 make -j${JOB_MAX} buildworld > ../buildworld.log 2>&1
173 where JOB_MAX is derrived from ncpus in local.sys.mk if not set in env.
176 Video related devices for some arm devices have been renamed.
177 If you have a custom kernel config and want to use hdmi output on
178 IMX6 board you need to add "device dwc_hdmi" "device imx6_hdmi" and
179 "device imx6_ipu" to it.
180 If you have a custom kernel config and want to use hdmi output on
181 TI AM335X board you need to add "device tda19988" to it.
182 If you add "device hdmi" in it you need to remove it as it doesn't
186 Introduce new kernel options KBD_DELAY1 and KBD_DELAY2. See atkbdc(4)
190 sshd now defaults to having X11Forwarding disabled, following upstream.
191 Administrators who wish to enable X11Forwarding should add
192 `X11Forwarding yes` to /etc/ssh/sshd_config.
195 Since commit 75d41cb6967 Huawei 3G/4G LTE Mobile Devices do not default
196 to ECM, but NCM mode and need u3g and ucom modules loaded. See cdce(4).
199 As of commit 7c40e2d5f685, the dependency on netlink(4) has been added
200 to the linux_common(4) module. Users relying on linux_common may need
201 to complile netlink(4) module if it is not present in their kernel.
204 The WITHOUT_CXX option has been removed. C++ components in the base
205 system are now built unconditionally.
208 LinuxKPI pci.h changes may require out-of-tree drivers to be recompiled.
209 Bump _FreeBSD_version to 1400078 to be able to detect this change.
212 llvm-objump is now always installed as objdump. Previously there was
213 no /usr/bin/objdump unless the WITH_LLVM_BINUTILS knob was used.
215 Some LLVM objdump options have a different output format compared to
216 GNU objdump; readelf is available for inspecting ELF files, and GNU
217 objdump is available from the devel/binutils port or package.
220 dma(8) has replaced sendmail(8) as the default mta. For people willing
221 to reenable sendmail(8):
223 $ cp /usr/share/examples/sendmail/mailer.conf /etc/mail/mailer.conf
225 and add sendmail_enable="YES" to rc.conf.
228 hw.bus.disable_failed_devices has changed from 'false' to 'true' by
229 default. Now if newbus succeeds in probing a device, but fails to attach
230 the device, we'll disable the device. In the past, we'd keep retrying
231 the device on each new driver loaded. To get that behavior now, one
232 needs to use devctl to re-enable the device, and reprobe it (or set
233 the sysctl/tunable hw.bus.disable_failed_devices=false).
235 NOTE: This was reverted 20221205 due to unexpected compatibility issues
238 pf no longer accepts 'scrub fragment crop' or 'scrub fragment drop-ovl'.
239 These configurations are no longer automatically reinterpreted as
240 'scrub fragment reassemble'.
243 The WITHOUT_CLANG_IS_CC option has been removed. When Clang is enabled
244 it is always installed as /usr/bin/cc (and c++, cpp).
247 Some programs have been moved into separate packages. It is recommended
248 for pkgbase users to do:
250 pkg install FreeBSD-dhclient FreeBSD-geom FreeBSD-resolvconf \
251 FreeBSD-devd FreeBSD-devmatch
253 after upgrading to restore all the component that were previously
257 OPIE has been removed from the base system. If needed, it can
258 be installed from ports (security/opie) or packages (opie).
259 Otherwise, make sure that your PAM policies do not reference
260 pam_opie or pam_opieaccess.
263 LinuxKPI pm.h changes require an update to the latest drm-kmod version
264 before re-compiling to avoid errors.
267 The macros provided for the manipulation of CPU sets (e.g. CPU_AND)
268 have been modified to take 2 source arguments instead of only 1.
269 Externally maintained sources that use these macros will have to
270 be adapted. The FreeBSD version has been bumped to 1400046 to
274 A number of the kernel include files are able to be included by
275 themselves. A test has been added to buildworld to enforce this.
278 Remove mips as a recognized target. This starts the decommissioning of
279 mips support in FreeBSD. mips related items will be removed wholesale in
280 the coming days and weeks.
282 This broke the NO_CLEAN build for some people. Either do a clean build
284 lib/clang/include/llvm/Config/Targets.def
285 lib/clang/include/llvm/Config/AsmParsers.def
286 lib/clang/include/llvm/Config/Disassemblers.def
287 lib/clang/include/llvm/Config/AsmPrinters.def
288 before the build to force everything to rebuild that needs to.
291 Unbound support for RFC8375: The special-use domain 'home.arpa' is
292 by default blocked. To unblock it use a local-zone nodefault
293 statement in unbound.conf:
294 local-zone: "home.arpa." nodefault
296 Or use another type of local-zone to override with your choice.
298 The reason for this is discussed in Section 6.1 of RFC8375:
299 Because 'home.arpa.' is not globally scoped and cannot be secured
300 using DNSSEC based on the root domain's trust anchor, there is no way
301 to tell, using a standard DNS query, in which homenet scope an answer
302 belongs. Consequently, users may experience surprising results with
303 such names when roaming to different homenets.
306 Commit b8d60729deef changed the TCP congestion control framework so
307 that any of the included congestion control modules could be
308 the single module built into the kernel. Previously newreno
309 was automatically built in through direct reference. As of
310 this commit you are required to declare at least one congestion
311 control module (e.g. 'options CC_NEWRENO') and to also declare a
312 default using the CC_DEFAULT option (e.g. options CC_DEFAULT="newreno\").
313 The GENERIC configuration includes CC_NEWRENO and defines newreno
314 as the default. If no congestion control option is built into the
315 kernel and you are including networking, the kernel compile will
316 fail. Also if no default is declared the kernel compile will fail.
319 Mips has been removed from universe builds. It will be removed from the
323 Commit f0c9847a6c47 changed the arguments for VOP_ALLOCATE.
324 The NFS modules must be rebuilt from sources and any out
325 of tree file systems that implement their own VOP_ALLOCATE
326 may need to be modified.
329 The synchronous PPP kernel driver sppp(4) has been removed.
330 The cp(4) and ce(4) drivers are now always compiled with netgraph(4)
331 support, formerly enabled by NETGRAPH_CRONYX option.
334 sh(1) is now the default shell for the root user. To force root to use
335 the csh shell, please run the following command as root:
340 Ncurses distribution has been split between libtinfow and libncurses
341 with libncurses.so becoming a linker (ld) script to seamlessly link
342 to libtinfow as needed. Bump _FreeBSD_version to 1400035 to reflect
346 As of commit 8160a0f62be6, the dummynet module no longer depends on the
347 ipfw module. Dummynet can now be used by pf as well as ipfw. As such
348 users who relied on this dependency may need to include ipfw in the
349 list of modules to load on their systems.
352 As of commit 903873ce1560, the mixer(8) utility has got a slightly
353 new syntax. Please refer to the mixer(8) manual page for more
354 information. The old mixer utility can be installed from ports:
355 audio/freebsd-13-mixer
358 As of commit 55089ef4f8bb, the global variable nfs_maxcopyrange has
359 been deleted from the nfscommon.ko. As such, nfsd.ko must be built
360 from up to date sources to avoid an undefined reference when
364 As of commit 62ca9fc1ad56 OpenSSL no longer enables kernel TLS
365 by default. Users can enable kernel TLS via the "KTLS" SSL
366 option. This can be enabled globally by using a custom
367 OpenSSL config file via OPENSSL_CONF or via an
368 application-specific configuration option for applications
369 which permit setting SSL options via SSL_CONF_cmd(3).
372 Commit 3ad1e1c1ce20 changed the internal KAPI between the NFS
373 modules. Therefore, all need to be rebuilt from sources.
376 Commit b69019c14cd8 removes pf's DIOCGETSTATESNV ioctl.
377 As of be70c7a50d32 it is no longer used by userspace, but it does mean
378 users may not be able to enumerate pf states if they update the kernel
379 past b69019c14cd8 without first updating userspace past be70c7a50d32.
382 As of commit 01ad0c007964 if_bridge member interfaces can no longer
383 change their MTU. Changing the MTU of the bridge itself will change the
384 MTU on all member interfaces instead.
387 Commit ee29e6f31111 changed the internal KAPI between the nfscommon
388 and nfsd modules. Therefore, both need to be rebuilt from sources.
389 Bump __FreeBSD_version to 1400026 for this KAPI change.
392 The 20210707 awk update brought in a change in behavior. This has
393 been corrected as of d4d252c49976. Between these dates, if you
394 installed a new awk binary, you may not be able to build a new
395 kernel because the change in behavior affected the genoffset
396 script used to build the kernel. If you did update, the fix is
397 to update your sources past the above hash and do
400 % sudo -E make install
401 to enable building kernels again.
404 Commit 1e0a518d6548 changed the internal KAPI between the NFS
405 modules. They all need to be rebuilt from sources. I did not
406 bump __FreeBSD_version, since it was bumped recently.
409 awk has been updated to the latest one-true-awk version 20210215.
410 This contains a number of minor bug fixes.
413 The NFSv4 client now uses the highest minor version of NFSv4
414 supported by the NFSv4 server by default instead of minor version 0,
416 The "minorversion" mount option may be used to override this default.
419 Bump __FreeBSD_version to 1400024 for LinuxKPI changes.
420 Most notably netdev.h can change now as the (last) dependencies
421 (mlx4/ofed) are now using struct ifnet directly, but also for PCI
422 additions and others.
425 The directory "blacklisted" under /usr/share/certs/ has been
426 renamed to "untrusted".
429 svnlite has been removed from base. Should you need svn for any reason
430 please install the svn package or port.
433 Commit e1a907a25cfa changed the internal KAPI between the krpc
434 and nfsserver. As such, both modules must be rebuilt from
435 sources. Bump __FreeBSD_version to 1400022.
438 The an(4) driver has been removed from FreeBSD.
441 The vendor/openzfs branch was renamed to vendor/openzfs/legacy to
442 start tracking OpenZFS upstream more closely. Please see
443 https://lists.freebsd.org/archives/freebsd-current/2021-June/000153.html
444 for details on how to correct any errors that might result. The
445 short version is that you need to remove the old branch locally:
446 git update-ref -d refs/remotes/freebsd/vendor/openzfs
447 (assuming your upstream origin is named 'freebsd').
450 Commits 17accc08ae15 and de102f870501 add new files to LinuxKPI
451 which break drm-kmod. In addition various other additions where
452 committed. Bump __FreeBSD_version to 1400015 to be able to
456 Commit ca179c4d74f2 changed the package in which the OpenSSL
457 libraries and utilities are packaged.
458 It is recommended for pkgbase user to do:
459 pkg install -f FreeBSD-openssl
460 before pkg upgrade otherwise some dependencies might not be met
461 and pkg will stop working as libssl will not be present anymore
465 Commit 875977314881 changed the internal KAPI between
466 the nfsd and nfscommon modules. As such these modules
467 need to be rebuilt from sources.
468 Without this patch in your NFSv4.1/4.2 server, enabling
469 delegations by setting vfs.nfsd.issue_delegations non-zero
473 Commit 7763814fc9c2 changed the internal KAPI between
474 the krpc and NFS. As such, the krpc, nfscommon and
475 nfscl modules must all be rebuilt from sources.
476 Without this patch, NFSv4.1/4.2 mounts should not
477 be done with the nfscbd(8) daemon running, to avoid
478 needing a working back channel for server->client RPCs.
481 Commit 01ae8969a9ee fixed the NFSv4.1/4.2 server so that it
482 handles binding of the back channel as required by RFC5661.
483 Until this patch is in your server, avoid use of the "nconnects"
484 mount option for Linux NFSv4.1/4.2 mounts.
487 For 64-bit architectures the base system is now built with Position
488 Independent Executable (PIE) support enabled by default. It may be
489 disabled using the WITHOUT_PIE knob. A clean build is required.
492 Various LinuxKPI functionality was added which conflicts with DRM.
493 Please update your drm-kmod port to after the __FreeBSD_version 1400003
497 stable/13 branch created.
500 PC Card attachments for all devices have been removed. In the case of
501 wi and cmx, the entire drivers were removed because they were only
502 PC Card devices. FreeBSD_version 1300134 should be used for this
503 since it was bumped so recently.
506 Transport-independent parts of HID support have been split off the USB
507 code in to separate subsystem. Kernel configs which include one of
508 ums, ukbd, uhid, atp, wsp, wmt, uaudio, ugold or ucycom drivers should
509 be updated with adding of "device hid" line.
512 ncurses installation has been modified to only keep the widechar
513 enabled version. Incremental build is broken for that change, so it
514 requires a clean build.
517 The FreeBSD project has migrated from Subversion to Git. Temporary
518 instructions can be found at
519 https://github.com/bsdimp/freebsd-git-docs/blob/main/src-cvt.md
520 and other documents in that repo.
523 The services database has been updated to cover more of the basic
524 services expected in a modern system. The database is big enough
525 that it will cause issues in mergemaster in Releases previous to
526 12.2 and 11.3, or in very old current systems from before r358154.
529 Obsolete in-tree GDB 6.1.1 has been removed. GDB (including kgdb)
530 may be installed from ports or packages.
533 ping6 has been merged into ping. It can now be called as "ping -6".
534 See ping(8) for details.
537 Default value of net.add_addr_allfibs has been changed to 0.
538 If you have multi-fib configuration and rely on existence of all
539 interface routes in every fib, you need to set the above sysctl to 1.
542 The internal pre-processor in the calendar(1) program has been
543 extended to support more C pre-processor commands (e.g. #ifdef, #else,
544 and #undef) and to detect unbalanced conditional statements.
545 Error messages have been extended to include the filename and line
546 number if processing stops to help fixing malformed data files.
549 All the data files for the calendar(1) program, except calendar.freebsd,
550 have been moved to the deskutils/calendar-data port, much like the
551 jewish calendar entries were moved to deskutils/hebcal years ago. After
552 make delete-old-files, you need to install it to retain full
553 functionality. calendar(1) will issue a reminder for files it can't
557 LINT files are no longer generated. We now include the relevant NOTES
558 files. Note: This may cause conflicts with updating in some cases.
559 find sys -name LINT\* -delete
560 is suggested across this commit to remove the generated LINT files.
562 If you have tried to update with generated files there, the svn
563 command you want to un-auger the tree is
566 and then do the above find from the top level. Substitute 'amd64'
567 above with where the error message indicates a conflict.
570 OpenZFS support has been integrated. Do not upgrade root pools until
571 the loader is updated to support zstd. Furthermore, we caution against
572 'zpool upgrade' for the next few weeks. The change should be transparent
573 unless you want to use new features.
575 Not all "NO_CLEAN" build scenarios work across these changes. Many
576 scenarios have been tested and fixed, but rebuilding kernels without
577 rebuilding world may fail.
579 The ZFS cache file has moved from /boot to /etc to match the OpenZFS
580 upstream default. A fallback to /boot has been added for mountroot.
582 Pool auto import behavior at boot has been moved from the kernel module
583 to an explicit "zpool import -a" in one of the rc scripts enabled by
584 zfs_enable=YES. This means your non-root zpools won't auto import until
585 you upgrade your /etc/rc.d files.
588 The resume code now notifies devd with the 'kernel' system
589 rather than the old 'kern' subsystem to be consistent with
590 other use. The old notification will be created as well, but
591 will be removed prior to FreeBSD 14.0.
594 r362275 changed the internal API between the kernel RPC and the
595 NFS modules. As such, all the modules must be recompiled from
599 r364330 modified the internal API used between the NFS modules.
600 As such, all the NFS modules must be re-compiled from sources.
603 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
604 been upgraded to 11.0.0. Please see the 20141231 entry below for
605 information about prerequisites and upgrading, if you are not already
606 using clang 3.5.0 or higher.
609 r364092 modified the internal ABI used between the kernel NFS
610 modules. As such, all of these modules need to be rebuilt
611 from sources, so a version bump was done.
614 Makefile.inc has been updated to work around the issue documented in
615 20200729. It was a case where the optimization of using symbolic links
616 to point to binaries created a situation where we'd run new binaries
617 with old libraries starting midway through the installworld process.
620 r363679 has redefined some undefined behavior in regcomp(3); notably,
621 extraneous escapes of most ordinary characters will no longer be
622 accepted. An exp-run has identified all of the problems with this in
623 ports, but other non-ports software may need extra escapes removed to
624 continue to function.
626 Because of this change, installworld may encounter the following error
627 from rtld: Undefined symbol "regcomp@FBSD_1.6" -- It is imperative that
628 you do not halt installworld. Instead, let it run to completion (whether
629 successful or not) and run installworld once more.
632 A new implementation of bc and dc has been imported in r362681. This
633 implementation corrects non-conformant behavior of the previous bc
634 and adds GNU bc compatible options. It offers a number of extensions,
635 is much faster on large values, and has support for message catalogs
636 (a number of languages are already supported, contributions of further
637 languages welcome). The option WITHOUT_GH_BC can be used to build the
638 world with the previous versions of bc and dc.
641 r362639 changed the internal API used between the NFS kernel modules.
642 As such, they all need to be rebuilt from sources.
645 r362158 changed the arguments for VFS_CHECKEXP(). As such, any
646 out of tree file systems need to be modified and rebuilt.
647 Also, any file systems that are modules must be rebuilt.
650 read(2) of a directory fd is now rejected by default. root may
651 re-enable it for system root only on non-ZFS filesystems with the
652 security.bsd.allow_read_dir sysctl(8) MIB if
653 security.bsd.suser_enabled=1.
655 It may be advised to setup aliases for grep to default to `-d skip` if
656 commonly non-recursively grepping a list that includes directories and
657 the potential for the resulting stderr output is not tolerable. Example
658 aliases are now installed, commented out, in /root/.cshrc and
662 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
663 been upgraded to 10.0.1. Please see the 20141231 entry below for
664 information about prerequisites and upgrading, if you are not already
665 using clang 3.5.0 or higher.
668 Support for obsolete compilers has been removed from the build system.
669 Clang 6 and GCC 6.4 are the minimum supported versions.
672 closefrom(2) has been moved under COMPAT12, and replaced in libc with a
673 stub that calls close_range(2). If using a custom kernel configuration,
674 you may want to ensure that the COMPAT_FREEBSD12 option is included, as
675 a slightly older -CURRENT userland and older FreeBSD userlands may not
676 be functional without closefrom(2).
679 Upstream DTS from Linux 5.6 was merged and they now have the SID
680 and THS (Secure ID controller and THermal Sensor) node present.
681 The DTB overlays have now been removed from the tree for the H3/H5 and
682 A64 SoCs and the aw_sid and aw_thermal driver have been updated to
683 deal with upstream DTS. If you are using those overlays you need to
684 remove them from loader.conf and update the DTBs on the FAT partition.
687 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
688 been upgraded to 10.0.0. Please see the 20141231 entry below for
689 information about prerequisites and upgrading, if you are not already
690 using clang 3.5.0 or higher.
693 The amd(8) automount daemon has been removed from the source tree.
694 As of FreeBSD 10.1 autofs(5) is the preferred tool for automounting.
695 amd is still available in the sysutils/am-utils port.
698 Removed brooktree driver (bktr.4) from the tree.
701 The WITH_GPL_DTC option has been removed. The BSD-licenced device tree
702 compiler in usr.bin/dtc is used on all architectures which use dtc, and
703 the GPL dtc is available (if needed) from the sysutils/dtc port.
706 The WITHOUT_LLVM_LIBUNWIND option has been removed. LLVM's libunwind
707 is used by all supported CPU architectures.
710 GCC 4.2.1 has been removed from the tree. The WITH_GCC,
711 WITH_GCC_BOOTSTRAP, and WITH_GNUCXX options are no longer available.
712 Users who wish to build FreeBSD with GCC must use the external toolchain
716 ncurses has been updated to a newer version (6.2-20200215). Given the ABI
717 has changed, users will have to rebuild all the ports that are linked to
721 The size of struct vnet and the magic cookie have changed.
722 Users need to recompile libkvm and all modules using VIMAGE
723 together with their new kernel.
726 Defining the long deprecated NO_CTF, NO_DEBUG_FILES, NO_INSTALLLIB,
727 NO_MAN, NO_PROFILE, and NO_WARNS variables is now an error. Update
728 your Makefiles and scripts to define MK_<var>=no instead as required.
730 One exception to this is that program or library Makefiles should
731 define MAN to empty rather than setting MK_MAN=no.
734 Clang/LLVM is now the default compiler and LLD the default
738 make universe no longer uses GCC 4.2.1 on any architectures.
739 Architectures not supported by in-tree Clang/LLVM require an
740 external toolchain package.
743 GCC 4.2.1 is now not built by default, as part of the GCC 4.2.1
744 retirement plan. Specifically, the GCC, GCC_BOOTSTRAP, and GNUCXX
745 options default to off for all supported CPU architectures. As a
746 short-term transition aid they may be enabled via WITH_* options.
747 GCC 4.2.1 is expected to be removed from the tree on 2020-03-31.
750 Support for armv5 has been disconnected and is being removed. The
751 machine combination MACHINE=arm MACHINE_ARCH=arm is no longer valid.
752 You must now use a MACHINE_ARCH of armv6 or armv7. The default
753 MACHINE_ARCH for MACHINE=arm is now armv7.
756 Clang/LLVM is now the default compiler for all powerpc architectures.
757 LLD is now the default linker for powerpc64. The change for powerpc64
758 also includes a change to the ELFv2 ABI, incompatible with the existing
762 Kernel-loadable random(4) modules are no longer unloadable.
765 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
766 been upgraded to 9.0.1. Please see the 20141231 entry below for
767 information about prerequisites and upgrading, if you are not already
768 using clang 3.5.0 or higher.
771 r355677 has modified the internal interface used between the
772 NFS modules in the kernel. As such, they must all be upgraded
773 simultaneously. I will do a version bump for this.
776 The root certificates of the Mozilla CA Certificate Store have been
777 imported into the base system and can be managed with the certctl(8)
778 utility. If you have installed the security/ca_root_nss port or package
779 with the ETCSYMLINK option (the default), be advised that there may be
780 differences between those included in the port and those included in
781 base due to differences in nss branch used as well as general update
782 frequency. Note also that certctl(8) cannot manage certs in the
783 format used by the security/ca_root_nss port.
786 The amd(8) automount daemon has been disabled by default, and will be
787 removed in the future. As of FreeBSD 10.1 the autofs(5) is available
791 The nctgpio and wbwd drivers have been moved to the superio bus.
792 If you have one of these drivers in a kernel configuration, then
793 you should add device superio to it. If you use one of these drivers
794 as a module and you compile a custom set of modules, then you should
795 add superio to the set.
798 KPIs for network drivers to access interface addresses have changed.
799 Users need to recompile NIC driver modules together with kernel.
802 The net.link.tap.user_open sysctl no longer prevents user opening of
803 already created /dev/tapNN devices. Access is still controlled by
804 node permissions, just like tun devices. The net.link.tap.user_open
805 sysctl is now used only to allow users to perform devfs cloning of
806 tap devices, and the subsequent open may not succeed if the user is not
807 in the appropriate group. This sysctl may be deprecated/removed
808 completely in the future.
811 mips, powerpc, and sparc64 are no longer built as part of
812 universe / tinderbox unless MAKE_OBSOLETE_GCC is defined. If
813 not defined, mips, powerpc, and sparc64 builds will look for
814 the xtoolchain binaries and if installed use them for universe
815 builds. As llvm 9.0 becomes vetted for these architectures, they
816 will be removed from the list.
819 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
820 been upgraded to 9.0.0. Please see the 20141231 entry below for
821 information about prerequisites and upgrading, if you are not already
822 using clang 3.5.0 or higher.
825 The hpt27xx, hptmv, hptnr, and hptrr drivers have been removed from
826 GENERIC. They are available as modules and can be loaded by adding
827 to /boot/loader.conf hpt27xx_load="YES", hptmv_load="YES",
828 hptnr_load="YES", or hptrr_load="YES", respectively.
831 ntpd no longer by default locks its pages in memory, allowing them
832 to be paged out by the kernel. Use rlimit memlock to restore
833 historic BSD behaviour. For example, add "rlimit memlock 32"
834 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
837 Several of ping6's options have been renamed for better consistency
838 with ping. If you use any of -ARWXaghmrtwx, you must update your
839 scripts. See ping6(8) for details.
842 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
843 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
844 been removed from mount_fusefs(8). You can safely remove them from
845 your scripts, because they had no effect.
847 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
848 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
849 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
850 sysctls have been removed. If you felt the need to set any of them to
851 a non-default value, please tell asomers@FreeBSD.org why.
854 Default permissions on the /var/account/acct file (and copies of it
855 rotated by periodic daily scripts) are changed from 0644 to 0640
856 because the file contains sensitive information that should not be
857 world-readable. If the /var/account directory must be created by
858 rc.d/accounting, the mode used is now 0750. Admins who use the
859 accounting feature are encouraged to change the mode of an existing
860 /var/account directory to 0750 or 0700.
863 Entropy collection and the /dev/random device are no longer optional
864 components. The "device random" option has been removed.
865 Implementations of distilling algorithms can still be made loadable
866 with "options RANDOM_LOADABLE" (e.g., random_fortuna.ko).
869 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
870 been upgraded to 8.0.1. Please see the 20141231 entry below for
871 information about prerequisites and upgrading, if you are not already
872 using clang 3.5.0 or higher.
875 A fix was applied to i386 kernel modules to avoid panics with
876 dpcpu or vnet. Users need to recompile i386 kernel modules
877 having pcpu or vnet sections or they will refuse to load.
880 User-wired pages now have their own counter,
881 vm.stats.vm.v_user_wire_count. The vm.max_wired sysctl was renamed
882 to vm.max_user_wired and changed from an unsigned int to an unsigned
883 long. bhyve VMs wired with the -S are now subject to the user
884 wiring limit; the vm.max_user_wired sysctl may need to be tuned to
885 avoid running into the limit.
888 The IPSEC option has been removed from GENERIC. Users requiring
889 ipsec(4) must now load the ipsec(4) kernel module.
892 The tap(4) driver has been folded into tun(4), and the module has been
893 renamed to tuntap. You should update any kld_list="if_tap" or
894 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
895 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
896 module instead, and "device tap" or "device tun" entries in kernel
897 config files to select the tuntap device instead.
900 The following knobs have been added related to tradeoffs between
901 safe use of the random device and availability in the absence of
904 kern.random.initial_seeding.bypass_before_seeding: tunable; set
905 non-zero to bypass the random device prior to seeding, or zero to
906 block random requests until the random device is initially seeded.
907 For now, set to 1 (unsafe) by default to restore pre-r346250 boot
908 availability properties.
910 kern.random.initial_seeding.read_random_bypassed_before_seeding:
911 read-only diagnostic sysctl that is set when bypass is enabled and
912 read_random(9) is bypassed, to enable programmatic handling of this
913 initial condition, if desired.
915 kern.random.initial_seeding.arc4random_bypassed_before_seeding:
916 Similar to the above, but for arc4random(9) initial seeding.
918 kern.random.initial_seeding.disable_bypass_warnings: tunable; set
919 non-zero to disable warnings in dmesg when the same conditions are
920 met as for the diagnostic sysctls above. Defaults to zero, i.e.,
921 produce warnings in dmesg when the conditions are met.
924 The loadable random module KPI has changed; the random_infra_init()
925 routine now requires a 3rd function pointer for a bool (*)(void)
926 method that returns true if the random device is seeded (and
927 therefore unblocked).
930 r345895 reverts r320698. This implies that an nfsuserd(8) daemon
931 built from head sources between r320757 (July 6, 2017) and
932 r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
933 is added to the command line.
934 nfsuserd daemons built from head sources that are post-r338192 are
935 not affected and should continue to work.
938 The fuse(4) module has been renamed to fusefs(4) for consistency with
939 other filesystems. You should update any kld_load="fuse" entries in
940 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
941 "options FUSE" entries in kernel config files.
944 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
945 8.0.0. Please see the 20141231 entry below for information about
946 prerequisites and upgrading, if you are not already using clang 3.5.0
950 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
951 compiled into your custom kernel, add 'device xz' statement to the
955 drm and drm2 have been removed from the tree. Please see
956 https://wiki.freebsd.org/Graphics for the latest information on
957 migrating to the drm ports.
960 Iflib is no longer unconditionally compiled into the kernel. Drivers
961 using iflib and statically compiled into the kernel, now require
962 the 'device iflib' config option. For the same drivers loaded as
963 modules on kernels not having 'device iflib', the iflib.ko module
964 is loaded automatically.
967 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
968 options no longer exist since r343219 and r343427 respectively;
969 nothing uses them, so they should be just removed from custom
973 r342635 changes the way efibootmgr(8) works by requiring users to add
974 the -b (bootnum) parameter for commands where the bootnum was previously
975 specified with each option. For example 'efibootmgr -B 0001' is now
976 'efibootmgr -B -b 0001'.
979 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
980 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
981 servers that have vfs.nfsd.nfs_privport set will only allow mounts
982 from clients using a reserved port. Since both the FreeBSD and Linux
983 NFSv4 clients use reserved ports by default, this should not affect
987 The XLP config has been removed. We can't support 64-bit atomics in this
988 kernel because it is running in 32-bit mode. XLP users must transition
989 to running a 64-bit kernel (XLP64 or XLPN32).
991 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
992 the preferred emulator today and we don't need two different ones.
994 The old sibyte / swarm / Broadcom BCM1250 support has been
995 removed from the mips port.
998 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
999 7.0.1. Please see the 20141231 entry below for information about
1000 prerequisites and upgrading, if you are not already using clang 3.5.0
1004 Remove the timed and netdate programs from the base tree. Setting
1005 the time with these daemons has been obsolete for over a decade.
1008 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
1009 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
1010 it produces broken binaries when ifuncs are in use. Users needing
1011 GNU ld should install the binutils port or package.
1014 The BSD crtbegin and crtend code has been enabled by default. It has
1015 had extensive testing on amd64, arm64, and i386. It can be disabled
1016 by building a world with -DWITHOUT_BSD_CRTBEGIN.
1019 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
1020 has been converted to a port (misc/ctm) and will be removed from
1021 FreeBSD-13. It is available as a package (ctm) for all supported
1025 The default newsyslog.conf(5) file has been changed to only include
1026 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
1027 the filenames end in '.conf' and do not begin with a '.'.
1029 You should check the configuration files in these two directories match
1030 this naming convention. You can verify which configuration files are
1031 being included using the command:
1035 Stable/12 was branched created.
1038 Ports for the DRM modules have been simplified. Now, amd64 users should
1039 just install the drm-kmod port. All others should install
1042 Graphics hardware that's newer than about 2010 usually works with
1043 drm-kmod. For hardware older than 2013, however, some users will need
1044 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
1045 than 2008 usually only works in drm-legacy-kmod. The graphics team can
1046 only commit to hardware made since 2013 due to the complexity of the
1047 market and difficulty to test all the older cards effectively. If you
1048 have hardware supported by drm-kmod, you are strongly encouraged to use
1049 that as you will get better support.
1051 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
1052 elsewhere, the drm and drm2 modules will be eliminated from the src base
1053 soon (with a limited exception for arm). Please update to the package
1054 asap and report any issues to x11@freebsd.org.
1056 Generally, anybody using the drm*-kmod packages should add
1057 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
1058 cross-threading surprises, especially with automatic driver
1059 loading from X11 startup. These will become the defaults in 13-current
1063 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
1064 custom kernel and module loading configuration files must be updated
1065 accordingly. Moreover, interfaces previous presented as ixlvN to the
1066 system are now exposed as iavfN and network configuration files must
1067 be adjusted as necessary.
1070 OpenSSL has been updated to version 1.1.1. This update included
1071 additional various API changes throughout the base system. It is
1072 important to rebuild third-party software after upgrading. The value
1073 of __FreeBSD_version has been bumped accordingly.
1076 The legacy DRM modules and drivers have now been added to the loader's
1077 module blacklist, in favor of loading them with kld_list in rc.conf(5).
1078 The module blacklist may be overridden with the loader.conf(5)
1079 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
1083 The cam(4) based nda(4) driver will be used over nvd(4) by default on
1084 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
1085 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
1086 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
1090 Reproducible build mode is now on by default, in preparation for
1091 FreeBSD 12.0. This eliminates build metadata such as the user,
1092 host, and time from the kernel (and uname), unless the working tree
1093 corresponds to a modified checkout from a version control system.
1094 The previous behavior can be obtained by setting the /etc/src.conf
1095 knob WITHOUT_REPRODUCIBLE_BUILD.
1098 The Yarrow CSPRNG has been removed from the kernel as it has not been
1099 supported by its designers since at least 2003. Fortuna has been the
1100 default since FreeBSD-11.
1103 devctl freeze/thaw have gone into the tree, the rc scripts have been
1104 updated to use them and devmatch has been changed. You should update
1105 kernel, userland and rc scripts all at the same time.
1108 The default interpreter has been switched from 4th to Lua.
1109 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
1110 interpreter. If you have custom FORTH code you will need to set
1111 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
1112 src.conf for the build. This will create default hard links between
1113 loader and loader_4th instead of loader and loader_lua, the new default.
1114 If you are using UEFI it will create the proper hard link to loader.efi.
1116 bhyve uses userboot.so. It remains 4th-only until some issues are solved
1117 regarding coexisting with multiple versions of FreeBSD are resolved.
1120 ls(1) now respects the COLORTERM environment variable used in other
1121 systems and software to indicate that a colored terminal is both
1122 supported and desired. If ls(1) is suddenly emitting colors, they may
1123 be disabled again by either removing the unwanted COLORTERM from your
1124 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
1125 may not be observed in a future release.
1128 The default pager for most commands has been changed to "less". To
1129 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
1133 The jedec_ts(4) driver has been removed. A superset of its functionality
1134 is available in the jedec_dimm(4) driver, and the manpage for that
1135 driver includes migration instructions. If you have "device jedec_ts"
1136 in your kernel configuration file, it must be removed.
1139 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
1140 This should have no effect if the kernel is booted via BIOS/legacy boot.
1141 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
1142 has a buggy firmware that prevents a successful boot due to use of
1146 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
1147 support has been removed from the tree. These ports were
1148 obsolete and/or known to be broken for many years.
1151 loader.efi has been augmented to participate more fully in the
1152 UEFI boot manager protocol. loader.efi will now look at the
1153 BootXXXX environment variable to determine if a specific kernel
1154 or root partition was specified. XXXX is derived from BootCurrent.
1155 efibootmgr(8) manages these standard UEFI variables.
1158 zfsloader's functionality has now been folded into loader.
1159 zfsloader is no longer necessary once you've updated your
1160 boot blocks. For a transition period, we will install a
1161 hardlink for zfsloader to loader to allow a smooth transition
1162 until the boot blocks can be updated (hard link because old
1163 zfs boot blocks don't understand symlinks).
1166 ARM64 now have efifb support, if you want to have serial console
1167 on your arm64 board when an screen is connected and the bootloader
1168 setup a frame buffer for us to use, just add :
1171 in /boot/loader.conf
1172 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
1173 an screen connected as the firmware will setup a frame buffer are that
1174 u-boot will expose as an EFI frame buffer.
1177 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
1178 or take steps to update /etc/passwd before doing installworld on
1179 existing systems. Do not skip the "mergemaster -Fp" step before
1180 installworld, as described in the update procedures near the bottom
1181 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
1182 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
1183 the ntp config file contain options that change file/dir locations.
1184 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
1185 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
1186 taking steps to ensure that all required files/dirs are accessible
1190 Big endian arm support has been removed.
1193 The static environment setup in kernel configs is no longer mutually
1194 exclusive with the loader(8) environment by default. In order to
1195 restore the previous default behavior of disabling the loader(8)
1196 environment if a static environment is present, you must specify
1197 loader_env.disabled=1 in the static environment.
1200 The ABI of syscalls used by management tools like sockstat and
1201 netstat has been broken to allow 32-bit binaries to work on
1202 64-bit kernels without modification. These programs will need
1203 to match the kernel in order to function. External programs may
1204 require minor modifications to accommodate a change of type in
1205 structures from pointers to 64-bit virtual addresses.
1208 On i386 and amd64 atomics are now inlined. Out of tree modules using
1209 atomics will need to be rebuilt.
1212 The '%I' format in the kern.corefile sysctl limits the number of
1213 core files that a process can generate to the number stored in the
1214 debug.ncores sysctl. The '%I' format is replaced by the single digit
1215 index. Previously, if all indexes were taken the kernel would overwrite
1216 only a core file with the highest index in a filename.
1217 Currently the system will create a new core file if there is a free
1218 index or if all slots are taken it will overwrite the oldest one.
1221 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
1222 6.0.1. Please see the 20141231 entry below for information about
1223 prerequisites and upgrading, if you are not already using clang 3.5.0
1227 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
1228 needed to be changed to work with it. This change was made with r335763
1229 and requires a mergemaster / etcupdate / etc to update the installed
1233 r334930 changed the interface between the NFS modules, so they all
1234 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
1237 As of r334391 lld is the default amd64 system linker; it is installed
1238 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
1242 The kernel / userland interface for devinfo changed, so you'll
1243 need a new kernel and userland as a pair for it to work (rebuilding
1244 lib/libdevinfo is all that's required). devinfo and devmatch will
1245 not work, but everything else will when there's a mismatch.
1248 The on-disk format for hwpmc callchain records has changed to include
1249 threadid corresponding to a given record. This changes the field offsets
1250 and thus requires that libpmcstat be rebuilt before using a kernel
1254 The vxge(4) driver has been removed. This driver was introduced into
1255 HEAD one week before the Exar left the Ethernet market and is not
1256 known to be used. If you have device vxge in your kernel config file
1260 The amd64 kernel now requires a ld that supports ifunc to produce a
1261 working kernel, either lld or a newer binutils. lld is built by default
1262 on amd64, and the 'buildkernel' target uses it automatically. However,
1263 it is not the default linker, so building the kernel the traditional
1264 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
1265 binutils port/package). lld will soon be default, and this requirement
1268 NOTE: As of r334391 lld is the default system linker on amd64, and no
1269 workaround is necessary.
1272 The nxge(4) driver has been removed. This driver was for PCI-X 10g
1273 cards made by s2io/Neterion. The company was acquired by Exar and
1274 no longer sells or supports Ethernet products. If you have device
1275 nxge in your kernel config file it must be removed.
1278 The tz database (tzdb) has been updated to 2018e. This version more
1279 correctly models time stamps in time zones with negative DST such as
1280 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
1281 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
1282 time zone abbreviations and the tm_isdst flag.
1285 The ixgb(4) driver has been removed. This driver was for an early and
1286 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
1287 quickly shifted to the long lived ixgbe family. If you have device
1288 ixgb in your kernel config file it must be removed.
1291 The lmc(4) driver has been removed. This was a WAN interface
1292 card that was already reportedly rare in 2003, and had an ambiguous
1293 license. If you have device lmc in your kernel config file it must
1297 Support for Arcnet networks has been removed. If you have device
1298 arcnet or device cm in your kernel config file they must be
1302 Support for FDDI networks has been removed. If you have device
1303 fddi or device fpa in your kernel config file they must be
1307 In addition to supporting RFC 3164 formatted messages, the
1308 syslogd(8) service is now capable of parsing RFC 5424 formatted
1309 log messages. The main benefit of using RFC 5424 is that clients
1310 may now send log messages with timestamps containing year numbers,
1311 microseconds and time zone offsets.
1313 Similarly, the syslog(3) C library function has been altered to
1314 send RFC 5424 formatted messages to the local system logging
1315 daemon. On systems using syslogd(8), this change should have no
1316 negative impact, as long as syslogd(8) and the C library are
1317 updated at the same time. On systems using a different system
1318 logging daemon, it may be necessary to make configuration
1319 adjustments, depending on the software used.
1321 When using syslog-ng, add the 'syslog-protocol' flag to local
1322 input sources to enable parsing of RFC 5424 formatted messages:
1325 unix-dgram("/var/run/log" flags(syslog-protocol));
1328 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
1329 of the 'imuxsock' module to let messages be processed by the
1330 regular RFC 3164/5424 parsing pipeline:
1332 module(load="imuxsock" SysSock.UseSpecialParser="off")
1334 Do note that these changes only affect communication between local
1335 applications and syslogd(8). The format that syslogd(8) uses to
1336 store messages on disk or forward messages to other systems
1337 remains unchanged. syslogd(8) still uses RFC 3164 for these
1338 purposes. Options to customize this behaviour will be added in the
1339 future. Utilities that process log files stored in /var/log are
1340 thus expected to continue to function as before.
1342 __FreeBSD_version has been incremented to 1200061 to denote this
1346 Support for token ring networks has been removed. If you
1347 have "device token" in your kernel config you should remove
1348 it. No device drivers supported token ring.
1351 makefs was modified to be able to tag ISO9660 El Torito boot catalog
1352 entries as EFI instead of overloading the i386 tag as done previously.
1353 The amd64 mkisoimages.sh script used to build amd64 ISO images for
1354 release was updated to use this. This may mean that makefs must be
1355 updated before "make cdrom" can be run in the release directory. This
1356 should be as simple as:
1358 $ cd $SRCDIR/usr.sbin/makefs
1359 $ make depend all install
1362 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
1363 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
1364 Co-existence for the transition period will come shortly. Booting is a
1365 complex environment and test coverage for Lua-enabled loaders has been
1366 thin, so it would be prudent to assume it might not work and make
1367 provisions for backup boot methods.
1370 devmatch functionality has been turned on in devd. It will automatically
1371 load drivers for unattached devices. This may cause unexpected drivers
1372 to be loaded. Please report any problems to current@ and
1376 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
1377 6.0.0. Please see the 20141231 entry below for information about
1378 prerequisites and upgrading, if you are not already using clang 3.5.0
1382 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
1383 This means it is used to link the kernel and userland libraries and
1384 executables, but is not yet installed as /usr/bin/ld by default.
1386 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
1387 WITHOUT_LLD_BOOTSTRAP=yes
1390 On i386, pmtimer has been removed. Its functionality has been folded
1391 into apm. It was a no-op on ACPI in current for a while now (but was
1392 still needed on i386 in FreeBSD 11 and earlier). Users may need to
1393 remove it from kernel config files.
1396 The use of RSS hash from the network card aka flowid has been
1397 disabled by default for lagg(4) as it's currently incompatible with
1398 the lacp and loadbalance protocols.
1400 This can be re-enabled by setting the following in loader.conf:
1401 net.link.lagg.default_use_flowid="1"
1404 The SW_WATCHDOG option is no longer necessary to enable the
1405 hardclock-based software watchdog if no hardware watchdog is
1406 configured. As before, SW_WATCHDOG will cause the software
1407 watchdog to be enabled even if a hardware watchdog is configured.
1410 r326887 fixes the issue described in the 20171214 UPDATING entry.
1411 r326888 flips the switch back to building GELI support always.
1414 r362593 broke ZFS + GELI support for reasons unknown. However,
1415 it also broke ZFS support generally, so GELI has been turned off
1416 by default as the lesser evil in r326857. If you boot off ZFS and/or
1417 GELI, it might not be a good time to update.
1420 PowerPC users must update loader(8) by rebuilding world before
1421 installing a new kernel, as the protocol connecting them has
1422 changed. Without the update, loader metadata will not be passed
1423 successfully to the kernel and users will have to enter their
1424 root partition at the kernel mountroot prompt to continue booting.
1425 Newer versions of loader can boot old kernels without issue.
1428 The LOADER_FIREWIRE_SUPPORT build variable has been renamed to
1429 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
1430 to WITH/OUT_LOADER_GELI.
1433 The naive and non-compliant support of posix_fallocate(2) in ZFS
1434 has been removed as of r325320. The system call now returns EINVAL
1435 when used on a ZFS file. Although the new behavior complies with the
1436 standard, some consumers are not prepared to cope with it.
1437 One known victim is lld prior to r325420.
1440 Building in a FreeBSD src checkout will automatically create object
1441 directories now rather than store files in the current directory if
1442 'make obj' was not ran. Calling 'make obj' is no longer necessary.
1443 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
1444 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
1448 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
1449 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
1450 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
1451 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
1452 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
1453 The UNIFIED_OBJDIR option is a transitional feature that will be
1454 removed for 12.0 release; please migrate to the new format for any
1455 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
1456 than hardcoding paths.
1459 The native-xtools target no longer installs the files by default to the
1460 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
1461 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
1464 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
1465 options are changing from controlling the build if defined / undefined
1466 to controlling the build with explicit 'yes' or 'no' values. They will
1467 shift to WITH/WITHOUT options to match other options in the system.
1470 libstand has turned into a private library for sys/boot use only.
1471 It is no longer supported as a public interface outside of sys/boot.
1474 The arm port has split armv6 into armv6 and armv7. armv7 is now
1475 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
1476 and are running a kernel from before r324363, you will need to add
1477 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
1480 When building multiple kernels using KERNCONF, non-existent KERNCONF
1481 files will produce an error and buildkernel will fail. Previously
1482 missing KERNCONF files silently failed giving no indication as to
1483 why, only to subsequently discover during installkernel that the
1484 desired kernel was never built in the first place.
1487 The default serial number format for CTL LUNs has changed. This will
1488 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
1489 or iSCSI clients care about their LUNs' serial numbers. Users who
1490 require serial number stability should hardcode serial numbers in
1494 For 32-bit arm compiled for hard-float support, soft-floating point
1495 binaries now always get their shared libraries from
1496 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
1497 /usr/libsoft also existed). Only users with a hard-float ld.so, but
1498 soft-float everything else should be affected.
1501 The geli password typed at boot is now hidden. To restore the previous
1502 behavior, see geli(8) for configuration options.
1505 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
1506 sysctl values. Minor nit, but requires a rebuild of both world/kernel
1510 "make check" behavior (made in ^/head@r295380) has been changed to
1511 execute from a limited sandbox, as opposed to executing from
1515 - The "beforecheck" and "aftercheck" targets are now specified.
1516 - ${CHECKDIR} (added in commit noted above) has been removed.
1517 - Legacy behavior can be enabled by setting
1518 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
1520 If the limited sandbox mode is enabled, "make check" will execute
1521 "make distribution", then install, execute the tests, and clean up the
1522 sandbox if successful.
1524 The "make distribution" and "make install" targets are typically run as
1525 root to set appropriate permissions and ownership at installation time.
1526 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
1527 environment if executing "make check" with limited sandbox mode using
1528 an unprivileged user.
1531 Since the switch to GPT disk labels, fsck for UFS/FFS has been
1532 unable to automatically find alternate superblocks. As of r322297,
1533 the information needed to find alternate superblocks has been
1534 moved to the end of the area reserved for the boot block.
1535 Filesystems created with a newfs of this vintage or later
1536 will create the recovery information. If you have a filesystem
1537 created prior to this change and wish to have a recovery block
1538 created for your filesystem, you can do so by running fsck in
1539 foreground mode (i.e., do not use the -p or -y options). As it
1540 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
1541 to which you should answer yes.
1544 As of r321665, an NFSv4 server configuration that services
1545 Kerberos mounts or clients that do not support the uid/gid in
1546 owner/owner_group string capability, must explicitly enable
1547 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
1548 machine's /etc/rc.conf file.
1551 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
1552 Please see the 20141231 entry below for information about prerequisites
1553 and upgrading, if you are not already using clang 3.5.0 or higher.
1556 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
1557 r-commands (rlogin, rsh, etc.) to be built with the base system.
1560 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
1561 a very major ABI incompatible change, so users of FreeBSD/powerpc must
1562 be careful when performing source upgrades. It is best to run
1563 'make installworld' from an alternate root system, either a live
1564 CD/memory stick, or a temporary root partition. Additionally, all ports
1565 must be recompiled. powerpc64 is largely unaffected, except in the case
1566 of 32-bit compatibility. All 32-bit binaries will be affected.
1569 Forward compatibility for the "ino64" project have been committed. This
1570 will allow most new binaries to run on older kernels in a limited
1571 fashion. This prevents many of the common foot-shooting actions in the
1572 upgrade as well as the limited ability to roll back the kernel across
1573 the ino64 upgrade. Complicated use cases may not work properly, though
1574 enough simpler ones work to allow recovery in most situations.
1577 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
1578 if you require the GPL compiler.
1581 Forward compatibility for the "ino64" project have been committed. This
1582 will allow most new binaries to run on older kernels in a limited
1583 fashion. This prevents many of the common foot-shooting actions in the
1584 upgrade as well as the limited ability to roll back the kernel across
1585 the ino64 upgrade. Complicated use cases may not work properly, though
1586 enough simpler ones work to allow recovery in most situations.
1589 The internal ABI used for communication between the NFS kernel modules
1590 was changed by r320085, so __FreeBSD_version was bumped to
1591 ensure all the NFS related modules are updated together.
1594 The ABI of struct event was changed by extending the data
1595 member to 64bit and adding ext fields. For upgrade, same
1596 precautions as for the entry 20170523 "ino64" must be
1600 The GNU roff toolchain has been removed from base. To render manpages
1601 which are not supported by mandoc(1), man(1) can fallback on GNU roff
1602 from ports (and recommends to install it).
1603 To render roff(7) documents, consider using GNU roff from ports or the
1604 heirloom doctools roff toolchain from ports via pkg install groff or
1605 via pkg install heirloom-doctools.
1608 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
1609 smaller runtime footprint builds. This is useful for embedded systems
1610 which only require one chipset support.
1612 If you load it as a module, make sure this is in /boot/loader.conf:
1616 This will load the HAL, all chip/RF backends and if_ath_pci.
1617 If you have if_ath_pci in /boot/loader.conf, ensure it is after
1618 if_ath or it will not load any HAL chipset support.
1620 If you want to selectively load things (eg on cheaper ARM/MIPS
1621 platforms where RAM is at a premium) you should:
1624 * load the chip modules in question
1625 * load ath_rate, ath_dfs
1627 * load if_ath_pci and/or if_ath_ahb depending upon your particular
1628 bus bind type - this is where probe/attach is done.
1630 For further comments/feedback, poke adrian@ .
1633 The "ino64" 64-bit inode project has been committed, which extends
1634 a number of types to 64 bits. Upgrading in place requires care and
1635 adherence to the documented upgrade procedure.
1637 If using a custom kernel configuration ensure that the
1638 COMPAT_FREEBSD11 option is included (as during the upgrade the
1639 system will be running the ino64 kernel with the existing world).
1641 For the safest in-place upgrade begin by removing previous build
1642 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full
1643 procedure documented below under the heading "To rebuild everything and
1644 install it on the current system." Specifically, a reboot is required
1645 after installing the new kernel before installing world. While an
1646 installworld normally works by accident from multiuser after rebooting
1647 the proper kernel, there are many cases where this will fail across this
1648 upgrade and installworld from single user is required.
1651 The NATM framework including the en(4), fatm(4), hatm(4), and
1652 patm(4) devices has been removed. Consumers should plan a
1653 migration before the end-of-life date for FreeBSD 11.
1656 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
1657 diff has not been implemented, if those are needed a newer version of
1658 GNU diff is available via the diffutils package under the gdiff name.
1661 As of r316810 for ipfilter, keep frags is no longer assumed when
1662 keep state is specified in a rule. r316810 aligns ipfilter with
1663 documentation in man pages separating keep frags from keep state.
1664 This allows keep state to be specified without forcing keep frags
1665 and allows keep frags to be specified independently of keep state.
1666 To maintain previous behaviour, also specify keep frags with
1667 keep state (as documented in ipf.conf.5).
1670 arm64 builds now use the base system LLD 4.0.0 linker by default,
1671 instead of requiring that the aarch64-binutils port or package be
1672 installed. To continue using aarch64-binutils, set
1673 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
1676 The UDP optimization in entry 20160818 that added the sysctl
1677 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
1678 packets will no longer be treated as L3 broadcast packets.
1681 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
1682 use any explicitly assigned loopback address available in the jail
1683 instead of using the first assigned address of the jail.
1686 The ctl.ko module no longer implements the iSCSI target frontend:
1687 cfiscsi.ko does instead.
1689 If building cfiscsi.ko as a kernel module, the module can be loaded
1690 via one of the following methods:
1691 - `cfiscsi_load="YES"` in loader.conf(5).
1692 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
1693 - ctladm(8)/ctld(8), when compiled with iSCSI support
1694 (`WITH_ISCSI=yes` in src.conf(5))
1696 Please see cfiscsi(4) for more details.
1699 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
1700 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
1701 same source (previously, the dependency of mmcsd.ko on mmc.ko was
1702 missing, but mmcsd.ko now will refuse to load if it is incompatible
1706 The syntax of ipfw(8) named states was changed to avoid ambiguity.
1707 If you have used named states in the firewall rules, you need to modify
1708 them after installworld and before rebooting. Now named states must
1709 be prefixed with colon.
1712 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
1713 removed as the userland we provide cannot use them. The KMS version
1714 (sys/dev/drm2) supports the same hardware.
1717 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
1718 Please see the 20141231 entry below for information about prerequisites
1719 and upgrading, if you are not already using clang 3.5.0 or higher.
1722 The code that provides support for ZFS .zfs/ directory functionality
1723 has been reimplemented. It's not possible now to create a snapshot
1724 by mkdir under .zfs/snapshot/. That should be the only user visible
1728 EISA bus support has been removed. The WITH_EISA option is no longer
1732 MCA bus support has been removed.
1735 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
1736 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
1739 The EM_MULTIQUEUE kernel configuration option is deprecated now that
1740 the em(4) driver conforms to iflib specifications.
1743 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
1744 IFLIB. If you have a custom kernel configuration that excludes em(4)
1745 but you use igb(4), you need to re-add em(4) to your custom
1749 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
1750 Please see the 20141231 entry below for information about prerequisites
1751 and upgrading, if you are not already using clang 3.5.0 or higher.
1754 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
1755 Please see the 20141231 entry below for information about prerequisites
1756 and upgrading, if you are not already using clang 3.5.0 or higher.
1759 The layout of the pmap structure has changed for powerpc to put the pmap
1760 statistics at the front for all CPU variations. libkvm(3) and all tools
1761 that link against it need to be recompiled.
1764 isl(4) and cyapa(4) drivers now require a new driver,
1765 chromebook_platform(4), to work properly on Chromebook-class hardware.
1766 On other types of hardware the drivers may need to be configured using
1767 device hints. Please see the corresponding manual pages for details.
1770 The urtwn(4) driver was merged into rtwn(4) and now consists of
1771 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
1773 Also, firmware for RTL8188CE was renamed due to possible name
1774 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
1777 GNU rcs has been removed from base. It is available as packages:
1778 - rcs: Latest GPLv3 GNU rcs version.
1779 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
1783 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
1784 modules now requires that the kernel configuration contain the
1785 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
1788 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
1789 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
1792 Relocatable object files with the extension of .So have been renamed
1793 to use an extension of .pico instead. The purpose of this change is
1794 to avoid a name clash with shared libraries on case-insensitive file
1795 systems. On those file systems, foo.So is the same file as foo.so.
1798 GNU rcs has been turned off by default. It can (temporarily) be built
1799 again by adding WITH_RCS knob in src.conf.
1800 Otherwise, GNU rcs is available from packages:
1801 - rcs: Latest GPLv3 GNU rcs version.
1802 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
1805 The backup_uses_rcs functionality has been removed from rc.subr.
1808 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
1809 two separate components, QUEUE_MACRO_DEBUG_TRACE and
1810 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
1811 QUEUE_MACRO_DEBUG behavior.
1814 r304787 changed some ioctl interfaces between the iSCSI userspace
1815 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1816 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1820 The UDP receive code has been updated to only treat incoming UDP
1821 packets that were addressed to an L2 broadcast address as L3
1822 broadcast packets. It is not expected that this will affect any
1823 standards-conforming UDP application. The new behaviour can be
1824 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1828 Remove the openbsd_poll system call.
1829 __FreeBSD_version has been bumped because of this.
1832 The stable/11 branch has been created from head@r302406.
1834 After branch N is created, entries older than the N-2 branch point are removed
1835 from this file. After stable/14 is branched and current becomes FreeBSD 15,
1836 entries older than stable/12 branch point will be removed from current's
1843 Sometimes, obscure build problems are the result of environment
1844 poisoning. This can happen because the make utility reads its
1845 environment when searching for values for global variables. To run
1846 your build attempts in an "environmental clean room", prefix all make
1847 commands with 'env -i '. See the env(1) manual page for more details.
1848 Occasionally a build failure will occur with "make -j" due to a race
1849 condition. If this happens try building again without -j, and please
1850 report a bug if it happens consistently.
1852 When upgrading from one major version to another it is generally best to
1853 upgrade to the latest code in the currently installed branch first, then
1854 do an upgrade to the new branch. This is the best-tested upgrade path,
1855 and has the highest probability of being successful. Please try this
1856 approach if you encounter problems with a major version upgrade. Since
1857 the stable 4.x branch point, one has generally been able to upgrade from
1858 anywhere in the most recent stable branch to head / current (or even the
1859 last couple of stable branches). See the top of this file when there's
1862 The update process will emit an error on an attempt to perform a build
1863 or install from a FreeBSD version below the earliest supported version.
1864 When updating from an older version the update should be performed one
1865 major release at a time, including running `make delete-old` at each
1868 When upgrading a live system, having a root shell around before
1869 installing anything can help undo problems. Not having a root shell
1870 around can lead to problems if pam has changed too much from your
1871 starting point to allow continued authentication after the upgrade.
1873 This file should be read as a log of events. When a later event changes
1874 information of a prior event, the prior event should not be deleted.
1875 Instead, a pointer to the entry with the new information should be
1876 placed in the old entry. Readers of this file should also sanity check
1877 older entries before relying on them blindly. Authors of new entries
1878 should write them with this in mind.
1882 When upgrading the boot ZFS pool to a new version (via zpool upgrade),
1883 always follow these three steps:
1885 1) recompile and reinstall the ZFS boot loader and boot block
1886 (this is part of "make buildworld" and "make installworld")
1888 2) update the ZFS boot block on your boot drive (only required when
1889 doing a zpool upgrade):
1891 When booting on x86 via BIOS, use the following to update the ZFS boot
1892 block on the freebsd-boot partition of a GPT partitioned drive ada0:
1893 gpart bootcode -p /boot/gptzfsboot -i $N ada0
1894 The value $N will typically be 1. For EFI booting, see EFI notes.
1896 3) zpool upgrade the root pool. New bootblocks will work with old
1897 pools, but not vice versa, so they need to be updated before any
1900 Non-boot pools do not need these updates.
1905 There are two locations the boot loader can be installed into. The
1906 current location (and the default) is \efi\freebsd\loader.efi and using
1907 efibootmgr(8) to configure it. The old location, that must be used on
1908 deficient systems that don't honor efibootmgr(8) protocols, is the
1909 fallback location of \EFI\BOOT\BOOTxxx.EFI. Generally, you will copy
1910 /boot/loader.efi to this location, but on systems installed a long time
1911 ago the ESP may be too small and /boot/boot1.efi may be needed unless
1912 the ESP has been expanded in the meantime.
1914 Recent systems will have the ESP mounted on /boot/efi, but older ones
1915 may not have it mounted at all, or mounted in a different
1916 location. Older arm SD images with MBR used /boot/msdos as the
1917 mountpoint. The ESP is a MSDOS filesystem.
1919 The EFI boot loader rarely needs to be updated. For ZFS booting,
1920 however, you must update loader.efi before you do 'zpool upgrade' the
1921 root zpool, otherwise the old loader.efi may reject the upgraded zpool
1922 since it does not automatically understand some new features.
1924 See loader.efi(8) and uefi(8) for more details.
1928 If you are updating from a prior version of FreeBSD (even one just
1929 a few days old), you should follow this procedure. It is the most
1930 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1932 make kernel-toolchain
1933 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1934 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1936 To test a kernel once
1937 ---------------------
1938 If you just want to boot a kernel once (because you are not sure
1939 if it works, or if you want to boot a known bad kernel to provide
1940 debugging information) run
1941 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1942 nextboot -k testkernel
1944 To rebuild everything and install it on the current system.
1945 -----------------------------------------------------------
1946 # Note: sometimes if you are running current you gotta do more than
1947 # is listed here if you are upgrading from a really old current.
1949 <make sure you have good level 0 dumps>
1951 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1952 make installkernel KERNCONF=YOUR_KERNEL_HERE
1954 <reboot in single user> [3]
1961 To cross-install current onto a separate partition
1962 --------------------------------------------------
1963 # In this approach we use a separate partition to hold
1964 # current's root, 'usr', and 'var' directories. A partition
1965 # holding "/", "/usr" and "/var" should be about 2GB in
1968 <make sure you have good level 0 dumps>
1971 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1972 <maybe newfs current's root partition>
1973 <mount current's root partition on directory ${CURRENT_ROOT}>
1974 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1975 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1976 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1977 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1978 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1979 <reboot into current>
1980 <do a "native" rebuild/install as described in the previous section>
1981 <maybe install compatibility libraries from ports/misc/compat*>
1985 To upgrade in-place from stable to current
1986 ----------------------------------------------
1987 <make sure you have good level 0 dumps>
1989 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1990 make installkernel KERNCONF=YOUR_KERNEL_HERE
1992 <reboot in single user> [3]
1999 Make sure that you've read the UPDATING file to understand the
2000 tweaks to various things you need. At this point in the life
2001 cycle of current, things change often and you are on your own
2002 to cope. The defaults can also change, so please read ALL of
2003 the UPDATING entries.
2005 Also, if you are tracking -current, you must be subscribed to
2006 freebsd-current@freebsd.org. Make sure that before you update
2007 your sources that you have read and understood all the recent
2008 messages there. If in doubt, please track -stable which has
2009 much fewer pitfalls.
2011 [1] If you have third party modules, such as vmware, you should disable
2012 them at this point so they don't crash your system on
2013 reboot. Alternatively, you should rebuild all the modules you have in
2014 your system and install them as well. If you are running -current, you
2015 should seriously consider placing all sources to all the modules for
2016 your system (or symlinks to them) in /usr/local/sys/modules so this
2017 happens automatically. If all your modules come from ports, then adding
2018 the port origin directories to PORTS_MODULES instead is also automatic
2020 PORTS_MODULES+=x11/nvidia-driver
2022 [3] From the bootblocks, boot -s, and then do
2026 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed
2027 cd src # full path to source
2028 adjkerntz -i # if CMOS is wall time
2029 Also, when doing a major release upgrade, it is required that you boot
2030 into single user mode to do the installworld.
2032 [4] Note: This step is non-optional. Failure to do this step
2033 can result in a significant reduction in the functionality of the
2034 system. Attempting to do it by hand is not recommended and those
2035 that pursue this avenue should read this file carefully, as well
2036 as the archives of freebsd-current and freebsd-hackers mailing lists
2037 for potential gotchas. See etcupdate(8) for more information.
2039 [5] Usually this step is a no-op. However, from time to time
2040 you may need to do this if you get unknown user in the following
2043 [6] This only deletes old files and directories. Old libraries
2044 can be deleted by "make delete-old-libs", but you have to make
2045 sure that no program is using those libraries anymore.
2047 [8] The new kernel must be able to run existing binaries used by an
2048 installworld. When upgrading across major versions, the new kernel's
2049 configuration must include the correct COMPAT_FREEBSD<n> option for
2050 existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure
2051 to do so may leave you with a system that is hard to boot to recover. A
2052 GENERIC kernel will include suitable compatibility options to run
2053 binaries from older branches. Note that the ability to run binaries
2054 from unsupported branches is not guaranteed.
2056 Make sure that you merge any new devices from GENERIC since the
2057 last time you updated your kernel config file. Options also
2058 change over time, so you may need to adjust your custom kernels
2061 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2062 "?=" instead of the "=" assignment operator, so that buildworld can
2063 override the CPUTYPE if it needs to.
2065 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2066 not on the command line, or in /etc/make.conf. buildworld will
2067 warn if it is improperly defined.
2070 This file contains a list, in reverse chronological order, of major
2071 breakages in tracking -current. It is not guaranteed to be a complete
2072 list of such breakages, and only contains entries since September 23, 2011.
2073 If you need to see UPDATING entries from before that date, you will need
2074 to fetch an UPDATING file from an older FreeBSD release.
2076 Copyright information:
2078 Copyright 1998-2009 M. Warner Losh <imp@FreeBSD.org>
2080 Redistribution, publication, translation and use, with or without
2081 modification, in full or in part, in any form or format of this
2082 document are permitted without further permission from the author.
2084 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2085 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2086 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2087 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2088 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2089 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2090 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2091 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2092 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2093 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2094 POSSIBILITY OF SUCH DAMAGE.
2096 Contact Warner Losh if you have any questions about your use of