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 Commit cc760de2183f changed the internal interface between
32 the nfscommon and nfscl modules. As such, both need to be
33 rebuilt from sources. Therefore, __FreeBSD_version was
37 If you have an arm64 system that uses ACPI, you will need to update your
38 loader.efi in the ESP when you update past this point. Detection of ACPI
39 was moved earlier in the binary so the scripts could use it, but old
40 binaries don't have this, so we default to 'no ACPI' in this case. You can
41 undisable ACPI by doing
42 OK unset hint.acpi.0.disabled
43 This can also be used to recover any other system that was updated in the
44 small window where amd64 was also broken.
47 The WITHOUT_LLD_IS_LD option has been removed. When LLD is enabled
48 it is always installed as /usr/bin/ld.
51 Forward compatibility (running the new code on old kernels) for the
52 "ino64" project have been removed. The need for it has passed long ago.
55 Commit 57ce37f9dcd0 changed the internal KAPI between the
56 nfscommon and nfscl modules. Both must be rebuilt from sources.
59 dialog(1) has been replaced in base by bsddialog(1), while most of the
60 time replacing a dialog(1) call by a bsddialog(1) call works out of the
61 box, bsddialog(1) is not considered as a drop-in replacement for
64 If you do depend on dialog(1) functionality, please install cdialog
70 The EARLY_AP_STARTUP kernel option is mandatory on x86. The option
71 has been added to DEFAULTS, so it should automatically be included in
72 custom kernel configurations without any additional change.
75 A new loader tunable net.pf.default_to_drop allows pf(4)’s default
76 behaviour to be changed from pass to drop. Previously this required
77 recompiling the kernel with the option PF_DEFAULT_TO_DROP.
80 Enable splitting out pkgbase manpages into separate packages by
81 default. To disable this, set WITHOUT_MANSPLITPKG=yes in src.conf.
84 Move standard include files to the clibs-dev package and move clang
85 internal libraries and headers to clang and clang-dev. Upgrading systems
86 installed using pkgbase past this change involves extra steps to allow
89 pkg upgrade -y FreeBSD-utilities
90 pkg upgrade -y FreeBSD-utilities-dev
94 Enable vnet sysctl variables to be loader tunable. SYSCTLs which
95 belongs to VNETs can be initialized during early boot or module
96 loading if they are marked with CTLFLAG_TUN and there are
97 corresponding kernel environment variables.
100 The WITH_INIT_ALL_PATTERN and WITH_INIT_ALL_ZERO build options have
101 been replaced by INIT_ALL=pattern and INIT_ALL=zero respectively.
104 FreeBSD 15.0-CURRENT.
107 Serial communication (in boot loaders, kernel, and userland) has
108 been changed to default to 115200 bps, in line with common industry
109 practice and typcial firmware serial console redirection
112 Note that the early x86 BIOS bootloader (i.e., boot0sio) does not
113 support rates above 9600 bps and is not changed. boot0sio users may
114 set BOOT_COMCONSOLE_SPEED=9600 to use 9600 for all of the boot
115 components, or use the standard boot0 and have the boot2 stage start
116 with the serial port at 115200.
119 Following the general removal of MIPS support, the ath(4) AHB bus-
120 frontend has been removed, too, and building of the PCI support is
121 integrated with the ath(4) main module again. As a result, there's
122 no longer a need for if_ath_pci_load="YES" in /boot/loader.conf or
123 "device ath_pci" in the kernel configuration.
126 MAXCPU has been increased to 1024 in the amd64 GENERIC kernel config.
127 Out-of-tree kernel modules will need to be rebuilt.
130 CAM has been mechanically updated s/u_int(64|32|16|8)_t/uint\1_t/g
131 to move to the standard uintXX_t types from the old, traditional
132 BSD u_intXX_t types. This should be a NOP, but may cause problems
133 for out of tree changes. The SIMs were not updated since most of
134 the old u_intXX_t uses weren't due to CAM interfaces.
137 stable/14 branch created.
140 The heuristic for detecting old chromebooks with an EC bug that requires
141 atkbdc driver workarounds has changed. There should be no functional
142 change, but if your old chromebook's keyboard stops working, please
143 file a PR and assign it to imp.
146 OpenSSL has been updated to version 3.0, including changes throughout
147 the base system. It is important to rebuild third-party software
151 To enable pf rdr rules for connections initiated from the host, pf
152 filter rules can be optionally enabled for packets delivered
153 locally. This can change the behavior of rules which match packets
154 delivered to lo0. To enable this feature:
156 sysctl net.pf.filter_local=1
159 When enabled, its best to ensure that packets delivered locally are not
160 filtered, e.g. by adding a 'skip on lo' rule.
163 Improvements to libtacplus(8) mean that tacplus.conf(5) now
164 follows POSIX shell syntax rules. This may cause TACACS+
165 authentication to fail if the shared secret contains a single
166 quote, double quote, or backslash character which isn't
167 already properly quoted or escaped.
170 Belatedly switch the default nvme block device on x86 from nvd to nda.
171 nda created nvd compatibility links by default, so this should be a
172 nop. If this causes problems for your application, set hw.nvme.use_nvd=1
173 in your loader.conf or add `options NVME_USE_NVD=1` to your kernel
174 config. To disable the nvd compatibility aliases, add
175 kern.cam.nda.nvd_compat=0 to loader.conf. The default has been nda on
176 all non-x86 platforms for some time now. If you need to fall back,
177 please email imp@freebsd.org about why.
179 Encrypted swap partitions need to be changed from nvd to nda if you
180 migrate, or you need to use the above to switch back to nvd.
183 Remove portsnap(8). Users are encouraged to obtain the ports tree
187 Add jobs.mk to save typing. Enables -j${JOB_MAX} and logging
191 make -j${JOB_MAX} buildworld > ../buildworld.log 2>&1
193 where JOB_MAX is derrived from ncpus in local.sys.mk if not set in env.
196 Video related devices for some arm devices have been renamed.
197 If you have a custom kernel config and want to use hdmi output on
198 IMX6 board you need to add "device dwc_hdmi" "device imx6_hdmi" and
199 "device imx6_ipu" to it.
200 If you have a custom kernel config and want to use hdmi output on
201 TI AM335X board you need to add "device tda19988" to it.
202 If you add "device hdmi" in it you need to remove it as it doesn't
206 Introduce new kernel options KBD_DELAY1 and KBD_DELAY2. See atkbdc(4)
210 sshd now defaults to having X11Forwarding disabled, following upstream.
211 Administrators who wish to enable X11Forwarding should add
212 `X11Forwarding yes` to /etc/ssh/sshd_config.
215 Since commit 75d41cb6967 Huawei 3G/4G LTE Mobile Devices do not default
216 to ECM, but NCM mode and need u3g and ucom modules loaded. See cdce(4).
219 As of commit 7c40e2d5f685, the dependency on netlink(4) has been added
220 to the linux_common(4) module. Users relying on linux_common may need
221 to complile netlink(4) module if it is not present in their kernel.
224 The WITHOUT_CXX option has been removed. C++ components in the base
225 system are now built unconditionally.
228 LinuxKPI pci.h changes may require out-of-tree drivers to be recompiled.
229 Bump _FreeBSD_version to 1400078 to be able to detect this change.
232 llvm-objump is now always installed as objdump. Previously there was
233 no /usr/bin/objdump unless the WITH_LLVM_BINUTILS knob was used.
235 Some LLVM objdump options have a different output format compared to
236 GNU objdump; readelf is available for inspecting ELF files, and GNU
237 objdump is available from the devel/binutils port or package.
240 dma(8) has replaced sendmail(8) as the default mta. For people willing
241 to reenable sendmail(8):
243 $ cp /usr/share/examples/sendmail/mailer.conf /etc/mail/mailer.conf
245 and add sendmail_enable="YES" to rc.conf.
248 hw.bus.disable_failed_devices has changed from 'false' to 'true' by
249 default. Now if newbus succeeds in probing a device, but fails to attach
250 the device, we'll disable the device. In the past, we'd keep retrying
251 the device on each new driver loaded. To get that behavior now, one
252 needs to use devctl to re-enable the device, and reprobe it (or set
253 the sysctl/tunable hw.bus.disable_failed_devices=false).
255 NOTE: This was reverted 20221205 due to unexpected compatibility issues
258 pf no longer accepts 'scrub fragment crop' or 'scrub fragment drop-ovl'.
259 These configurations are no longer automatically reinterpreted as
260 'scrub fragment reassemble'.
263 The WITHOUT_CLANG_IS_CC option has been removed. When Clang is enabled
264 it is always installed as /usr/bin/cc (and c++, cpp).
267 Some programs have been moved into separate packages. It is recommended
268 for pkgbase users to do:
270 pkg install FreeBSD-dhclient FreeBSD-geom FreeBSD-resolvconf \
271 FreeBSD-devd FreeBSD-devmatch
273 after upgrading to restore all the component that were previously
277 OPIE has been removed from the base system. If needed, it can
278 be installed from ports (security/opie) or packages (opie).
279 Otherwise, make sure that your PAM policies do not reference
280 pam_opie or pam_opieaccess.
283 LinuxKPI pm.h changes require an update to the latest drm-kmod version
284 before re-compiling to avoid errors.
287 The macros provided for the manipulation of CPU sets (e.g. CPU_AND)
288 have been modified to take 2 source arguments instead of only 1.
289 Externally maintained sources that use these macros will have to
290 be adapted. The FreeBSD version has been bumped to 1400046 to
294 A number of the kernel include files are able to be included by
295 themselves. A test has been added to buildworld to enforce this.
298 Remove mips as a recognized target. This starts the decommissioning of
299 mips support in FreeBSD. mips related items will be removed wholesale in
300 the coming days and weeks.
302 This broke the NO_CLEAN build for some people. Either do a clean build
304 lib/clang/include/llvm/Config/Targets.def
305 lib/clang/include/llvm/Config/AsmParsers.def
306 lib/clang/include/llvm/Config/Disassemblers.def
307 lib/clang/include/llvm/Config/AsmPrinters.def
308 before the build to force everything to rebuild that needs to.
311 Unbound support for RFC8375: The special-use domain 'home.arpa' is
312 by default blocked. To unblock it use a local-zone nodefault
313 statement in unbound.conf:
314 local-zone: "home.arpa." nodefault
316 Or use another type of local-zone to override with your choice.
318 The reason for this is discussed in Section 6.1 of RFC8375:
319 Because 'home.arpa.' is not globally scoped and cannot be secured
320 using DNSSEC based on the root domain's trust anchor, there is no way
321 to tell, using a standard DNS query, in which homenet scope an answer
322 belongs. Consequently, users may experience surprising results with
323 such names when roaming to different homenets.
326 Commit b8d60729deef changed the TCP congestion control framework so
327 that any of the included congestion control modules could be
328 the single module built into the kernel. Previously newreno
329 was automatically built in through direct reference. As of
330 this commit you are required to declare at least one congestion
331 control module (e.g. 'options CC_NEWRENO') and to also declare a
332 default using the CC_DEFAULT option (e.g. options CC_DEFAULT="newreno\").
333 The GENERIC configuration includes CC_NEWRENO and defines newreno
334 as the default. If no congestion control option is built into the
335 kernel and you are including networking, the kernel compile will
336 fail. Also if no default is declared the kernel compile will fail.
339 Mips has been removed from universe builds. It will be removed from the
343 Commit f0c9847a6c47 changed the arguments for VOP_ALLOCATE.
344 The NFS modules must be rebuilt from sources and any out
345 of tree file systems that implement their own VOP_ALLOCATE
346 may need to be modified.
349 The synchronous PPP kernel driver sppp(4) has been removed.
350 The cp(4) and ce(4) drivers are now always compiled with netgraph(4)
351 support, formerly enabled by NETGRAPH_CRONYX option.
354 sh(1) is now the default shell for the root user. To force root to use
355 the csh shell, please run the following command as root:
360 Ncurses distribution has been split between libtinfow and libncurses
361 with libncurses.so becoming a linker (ld) script to seamlessly link
362 to libtinfow as needed. Bump _FreeBSD_version to 1400035 to reflect
366 As of commit 8160a0f62be6, the dummynet module no longer depends on the
367 ipfw module. Dummynet can now be used by pf as well as ipfw. As such
368 users who relied on this dependency may need to include ipfw in the
369 list of modules to load on their systems.
372 As of commit 903873ce1560, the mixer(8) utility has got a slightly
373 new syntax. Please refer to the mixer(8) manual page for more
374 information. The old mixer utility can be installed from ports:
375 audio/freebsd-13-mixer
378 As of commit 55089ef4f8bb, the global variable nfs_maxcopyrange has
379 been deleted from the nfscommon.ko. As such, nfsd.ko must be built
380 from up to date sources to avoid an undefined reference when
384 As of commit 62ca9fc1ad56 OpenSSL no longer enables kernel TLS
385 by default. Users can enable kernel TLS via the "KTLS" SSL
386 option. This can be enabled globally by using a custom
387 OpenSSL config file via OPENSSL_CONF or via an
388 application-specific configuration option for applications
389 which permit setting SSL options via SSL_CONF_cmd(3).
392 Commit 3ad1e1c1ce20 changed the internal KAPI between the NFS
393 modules. Therefore, all need to be rebuilt from sources.
396 Commit b69019c14cd8 removes pf's DIOCGETSTATESNV ioctl.
397 As of be70c7a50d32 it is no longer used by userspace, but it does mean
398 users may not be able to enumerate pf states if they update the kernel
399 past b69019c14cd8 without first updating userspace past be70c7a50d32.
402 As of commit 01ad0c007964 if_bridge member interfaces can no longer
403 change their MTU. Changing the MTU of the bridge itself will change the
404 MTU on all member interfaces instead.
407 Commit ee29e6f31111 changed the internal KAPI between the nfscommon
408 and nfsd modules. Therefore, both need to be rebuilt from sources.
409 Bump __FreeBSD_version to 1400026 for this KAPI change.
412 The 20210707 awk update brought in a change in behavior. This has
413 been corrected as of d4d252c49976. Between these dates, if you
414 installed a new awk binary, you may not be able to build a new
415 kernel because the change in behavior affected the genoffset
416 script used to build the kernel. If you did update, the fix is
417 to update your sources past the above hash and do
420 % sudo -E make install
421 to enable building kernels again.
424 Commit 1e0a518d6548 changed the internal KAPI between the NFS
425 modules. They all need to be rebuilt from sources. I did not
426 bump __FreeBSD_version, since it was bumped recently.
429 awk has been updated to the latest one-true-awk version 20210215.
430 This contains a number of minor bug fixes.
433 The NFSv4 client now uses the highest minor version of NFSv4
434 supported by the NFSv4 server by default instead of minor version 0,
436 The "minorversion" mount option may be used to override this default.
439 Bump __FreeBSD_version to 1400024 for LinuxKPI changes.
440 Most notably netdev.h can change now as the (last) dependencies
441 (mlx4/ofed) are now using struct ifnet directly, but also for PCI
442 additions and others.
445 The directory "blacklisted" under /usr/share/certs/ has been
446 renamed to "untrusted".
449 svnlite has been removed from base. Should you need svn for any reason
450 please install the svn package or port.
453 Commit e1a907a25cfa changed the internal KAPI between the krpc
454 and nfsserver. As such, both modules must be rebuilt from
455 sources. Bump __FreeBSD_version to 1400022.
458 The an(4) driver has been removed from FreeBSD.
461 The vendor/openzfs branch was renamed to vendor/openzfs/legacy to
462 start tracking OpenZFS upstream more closely. Please see
463 https://lists.freebsd.org/archives/freebsd-current/2021-June/000153.html
464 for details on how to correct any errors that might result. The
465 short version is that you need to remove the old branch locally:
466 git update-ref -d refs/remotes/freebsd/vendor/openzfs
467 (assuming your upstream origin is named 'freebsd').
470 Commits 17accc08ae15 and de102f870501 add new files to LinuxKPI
471 which break drm-kmod. In addition various other additions where
472 committed. Bump __FreeBSD_version to 1400015 to be able to
476 Commit ca179c4d74f2 changed the package in which the OpenSSL
477 libraries and utilities are packaged.
478 It is recommended for pkgbase user to do:
479 pkg install -f FreeBSD-openssl
480 before pkg upgrade otherwise some dependencies might not be met
481 and pkg will stop working as libssl will not be present anymore
485 Commit 875977314881 changed the internal KAPI between
486 the nfsd and nfscommon modules. As such these modules
487 need to be rebuilt from sources.
488 Without this patch in your NFSv4.1/4.2 server, enabling
489 delegations by setting vfs.nfsd.issue_delegations non-zero
493 Commit 7763814fc9c2 changed the internal KAPI between
494 the krpc and NFS. As such, the krpc, nfscommon and
495 nfscl modules must all be rebuilt from sources.
496 Without this patch, NFSv4.1/4.2 mounts should not
497 be done with the nfscbd(8) daemon running, to avoid
498 needing a working back channel for server->client RPCs.
501 Commit 01ae8969a9ee fixed the NFSv4.1/4.2 server so that it
502 handles binding of the back channel as required by RFC5661.
503 Until this patch is in your server, avoid use of the "nconnects"
504 mount option for Linux NFSv4.1/4.2 mounts.
507 For 64-bit architectures the base system is now built with Position
508 Independent Executable (PIE) support enabled by default. It may be
509 disabled using the WITHOUT_PIE knob. A clean build is required.
512 Various LinuxKPI functionality was added which conflicts with DRM.
513 Please update your drm-kmod port to after the __FreeBSD_version 1400003
517 stable/13 branch created.
520 PC Card attachments for all devices have been removed. In the case of
521 wi and cmx, the entire drivers were removed because they were only
522 PC Card devices. FreeBSD_version 1300134 should be used for this
523 since it was bumped so recently.
526 Transport-independent parts of HID support have been split off the USB
527 code in to separate subsystem. Kernel configs which include one of
528 ums, ukbd, uhid, atp, wsp, wmt, uaudio, ugold or ucycom drivers should
529 be updated with adding of "device hid" line.
532 ncurses installation has been modified to only keep the widechar
533 enabled version. Incremental build is broken for that change, so it
534 requires a clean build.
537 The FreeBSD project has migrated from Subversion to Git. Temporary
538 instructions can be found at
539 https://github.com/bsdimp/freebsd-git-docs/blob/main/src-cvt.md
540 and other documents in that repo.
543 The services database has been updated to cover more of the basic
544 services expected in a modern system. The database is big enough
545 that it will cause issues in mergemaster in Releases previous to
546 12.2 and 11.3, or in very old current systems from before r358154.
549 Obsolete in-tree GDB 6.1.1 has been removed. GDB (including kgdb)
550 may be installed from ports or packages.
553 ping6 has been merged into ping. It can now be called as "ping -6".
554 See ping(8) for details.
557 Default value of net.add_addr_allfibs has been changed to 0.
558 If you have multi-fib configuration and rely on existence of all
559 interface routes in every fib, you need to set the above sysctl to 1.
562 The internal pre-processor in the calendar(1) program has been
563 extended to support more C pre-processor commands (e.g. #ifdef, #else,
564 and #undef) and to detect unbalanced conditional statements.
565 Error messages have been extended to include the filename and line
566 number if processing stops to help fixing malformed data files.
569 All the data files for the calendar(1) program, except calendar.freebsd,
570 have been moved to the deskutils/calendar-data port, much like the
571 jewish calendar entries were moved to deskutils/hebcal years ago. After
572 make delete-old-files, you need to install it to retain full
573 functionality. calendar(1) will issue a reminder for files it can't
577 LINT files are no longer generated. We now include the relevant NOTES
578 files. Note: This may cause conflicts with updating in some cases.
579 find sys -name LINT\* -delete
580 is suggested across this commit to remove the generated LINT files.
582 If you have tried to update with generated files there, the svn
583 command you want to un-auger the tree is
586 and then do the above find from the top level. Substitute 'amd64'
587 above with where the error message indicates a conflict.
590 OpenZFS support has been integrated. Do not upgrade root pools until
591 the loader is updated to support zstd. Furthermore, we caution against
592 'zpool upgrade' for the next few weeks. The change should be transparent
593 unless you want to use new features.
595 Not all "NO_CLEAN" build scenarios work across these changes. Many
596 scenarios have been tested and fixed, but rebuilding kernels without
597 rebuilding world may fail.
599 The ZFS cache file has moved from /boot to /etc to match the OpenZFS
600 upstream default. A fallback to /boot has been added for mountroot.
602 Pool auto import behavior at boot has been moved from the kernel module
603 to an explicit "zpool import -a" in one of the rc scripts enabled by
604 zfs_enable=YES. This means your non-root zpools won't auto import until
605 you upgrade your /etc/rc.d files.
608 The resume code now notifies devd with the 'kernel' system
609 rather than the old 'kern' subsystem to be consistent with
610 other use. The old notification will be created as well, but
611 will be removed prior to FreeBSD 14.0.
614 r362275 changed the internal API between the kernel RPC and the
615 NFS modules. As such, all the modules must be recompiled from
619 r364330 modified the internal API used between the NFS modules.
620 As such, all the NFS modules must be re-compiled from sources.
623 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
624 been upgraded to 11.0.0. Please see the 20141231 entry below for
625 information about prerequisites and upgrading, if you are not already
626 using clang 3.5.0 or higher.
629 r364092 modified the internal ABI used between the kernel NFS
630 modules. As such, all of these modules need to be rebuilt
631 from sources, so a version bump was done.
634 Makefile.inc has been updated to work around the issue documented in
635 20200729. It was a case where the optimization of using symbolic links
636 to point to binaries created a situation where we'd run new binaries
637 with old libraries starting midway through the installworld process.
640 r363679 has redefined some undefined behavior in regcomp(3); notably,
641 extraneous escapes of most ordinary characters will no longer be
642 accepted. An exp-run has identified all of the problems with this in
643 ports, but other non-ports software may need extra escapes removed to
644 continue to function.
646 Because of this change, installworld may encounter the following error
647 from rtld: Undefined symbol "regcomp@FBSD_1.6" -- It is imperative that
648 you do not halt installworld. Instead, let it run to completion (whether
649 successful or not) and run installworld once more.
652 A new implementation of bc and dc has been imported in r362681. This
653 implementation corrects non-conformant behavior of the previous bc
654 and adds GNU bc compatible options. It offers a number of extensions,
655 is much faster on large values, and has support for message catalogs
656 (a number of languages are already supported, contributions of further
657 languages welcome). The option WITHOUT_GH_BC can be used to build the
658 world with the previous versions of bc and dc.
661 r362639 changed the internal API used between the NFS kernel modules.
662 As such, they all need to be rebuilt from sources.
665 r362158 changed the arguments for VFS_CHECKEXP(). As such, any
666 out of tree file systems need to be modified and rebuilt.
667 Also, any file systems that are modules must be rebuilt.
670 read(2) of a directory fd is now rejected by default. root may
671 re-enable it for system root only on non-ZFS filesystems with the
672 security.bsd.allow_read_dir sysctl(8) MIB if
673 security.bsd.suser_enabled=1.
675 It may be advised to setup aliases for grep to default to `-d skip` if
676 commonly non-recursively grepping a list that includes directories and
677 the potential for the resulting stderr output is not tolerable. Example
678 aliases are now installed, commented out, in /root/.cshrc and
682 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
683 been upgraded to 10.0.1. Please see the 20141231 entry below for
684 information about prerequisites and upgrading, if you are not already
685 using clang 3.5.0 or higher.
688 Support for obsolete compilers has been removed from the build system.
689 Clang 6 and GCC 6.4 are the minimum supported versions.
692 closefrom(2) has been moved under COMPAT12, and replaced in libc with a
693 stub that calls close_range(2). If using a custom kernel configuration,
694 you may want to ensure that the COMPAT_FREEBSD12 option is included, as
695 a slightly older -CURRENT userland and older FreeBSD userlands may not
696 be functional without closefrom(2).
699 Upstream DTS from Linux 5.6 was merged and they now have the SID
700 and THS (Secure ID controller and THermal Sensor) node present.
701 The DTB overlays have now been removed from the tree for the H3/H5 and
702 A64 SoCs and the aw_sid and aw_thermal driver have been updated to
703 deal with upstream DTS. If you are using those overlays you need to
704 remove them from loader.conf and update the DTBs on the FAT partition.
707 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
708 been upgraded to 10.0.0. Please see the 20141231 entry below for
709 information about prerequisites and upgrading, if you are not already
710 using clang 3.5.0 or higher.
713 The amd(8) automount daemon has been removed from the source tree.
714 As of FreeBSD 10.1 autofs(5) is the preferred tool for automounting.
715 amd is still available in the sysutils/am-utils port.
718 Removed brooktree driver (bktr.4) from the tree.
721 The WITH_GPL_DTC option has been removed. The BSD-licenced device tree
722 compiler in usr.bin/dtc is used on all architectures which use dtc, and
723 the GPL dtc is available (if needed) from the sysutils/dtc port.
726 The WITHOUT_LLVM_LIBUNWIND option has been removed. LLVM's libunwind
727 is used by all supported CPU architectures.
730 GCC 4.2.1 has been removed from the tree. The WITH_GCC,
731 WITH_GCC_BOOTSTRAP, and WITH_GNUCXX options are no longer available.
732 Users who wish to build FreeBSD with GCC must use the external toolchain
736 ncurses has been updated to a newer version (6.2-20200215). Given the ABI
737 has changed, users will have to rebuild all the ports that are linked to
741 The size of struct vnet and the magic cookie have changed.
742 Users need to recompile libkvm and all modules using VIMAGE
743 together with their new kernel.
746 Defining the long deprecated NO_CTF, NO_DEBUG_FILES, NO_INSTALLLIB,
747 NO_MAN, NO_PROFILE, and NO_WARNS variables is now an error. Update
748 your Makefiles and scripts to define MK_<var>=no instead as required.
750 One exception to this is that program or library Makefiles should
751 define MAN to empty rather than setting MK_MAN=no.
754 Clang/LLVM is now the default compiler and LLD the default
758 make universe no longer uses GCC 4.2.1 on any architectures.
759 Architectures not supported by in-tree Clang/LLVM require an
760 external toolchain package.
763 GCC 4.2.1 is now not built by default, as part of the GCC 4.2.1
764 retirement plan. Specifically, the GCC, GCC_BOOTSTRAP, and GNUCXX
765 options default to off for all supported CPU architectures. As a
766 short-term transition aid they may be enabled via WITH_* options.
767 GCC 4.2.1 is expected to be removed from the tree on 2020-03-31.
770 Support for armv5 has been disconnected and is being removed. The
771 machine combination MACHINE=arm MACHINE_ARCH=arm is no longer valid.
772 You must now use a MACHINE_ARCH of armv6 or armv7. The default
773 MACHINE_ARCH for MACHINE=arm is now armv7.
776 Clang/LLVM is now the default compiler for all powerpc architectures.
777 LLD is now the default linker for powerpc64. The change for powerpc64
778 also includes a change to the ELFv2 ABI, incompatible with the existing
782 Kernel-loadable random(4) modules are no longer unloadable.
785 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
786 been upgraded to 9.0.1. Please see the 20141231 entry below for
787 information about prerequisites and upgrading, if you are not already
788 using clang 3.5.0 or higher.
791 r355677 has modified the internal interface used between the
792 NFS modules in the kernel. As such, they must all be upgraded
793 simultaneously. I will do a version bump for this.
796 The root certificates of the Mozilla CA Certificate Store have been
797 imported into the base system and can be managed with the certctl(8)
798 utility. If you have installed the security/ca_root_nss port or package
799 with the ETCSYMLINK option (the default), be advised that there may be
800 differences between those included in the port and those included in
801 base due to differences in nss branch used as well as general update
802 frequency. Note also that certctl(8) cannot manage certs in the
803 format used by the security/ca_root_nss port.
806 The amd(8) automount daemon has been disabled by default, and will be
807 removed in the future. As of FreeBSD 10.1 the autofs(5) is available
811 The nctgpio and wbwd drivers have been moved to the superio bus.
812 If you have one of these drivers in a kernel configuration, then
813 you should add device superio to it. If you use one of these drivers
814 as a module and you compile a custom set of modules, then you should
815 add superio to the set.
818 KPIs for network drivers to access interface addresses have changed.
819 Users need to recompile NIC driver modules together with kernel.
822 The net.link.tap.user_open sysctl no longer prevents user opening of
823 already created /dev/tapNN devices. Access is still controlled by
824 node permissions, just like tun devices. The net.link.tap.user_open
825 sysctl is now used only to allow users to perform devfs cloning of
826 tap devices, and the subsequent open may not succeed if the user is not
827 in the appropriate group. This sysctl may be deprecated/removed
828 completely in the future.
831 mips, powerpc, and sparc64 are no longer built as part of
832 universe / tinderbox unless MAKE_OBSOLETE_GCC is defined. If
833 not defined, mips, powerpc, and sparc64 builds will look for
834 the xtoolchain binaries and if installed use them for universe
835 builds. As llvm 9.0 becomes vetted for these architectures, they
836 will be removed from the list.
839 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
840 been upgraded to 9.0.0. Please see the 20141231 entry below for
841 information about prerequisites and upgrading, if you are not already
842 using clang 3.5.0 or higher.
845 The hpt27xx, hptmv, hptnr, and hptrr drivers have been removed from
846 GENERIC. They are available as modules and can be loaded by adding
847 to /boot/loader.conf hpt27xx_load="YES", hptmv_load="YES",
848 hptnr_load="YES", or hptrr_load="YES", respectively.
851 ntpd no longer by default locks its pages in memory, allowing them
852 to be paged out by the kernel. Use rlimit memlock to restore
853 historic BSD behaviour. For example, add "rlimit memlock 32"
854 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
857 Several of ping6's options have been renamed for better consistency
858 with ping. If you use any of -ARWXaghmrtwx, you must update your
859 scripts. See ping6(8) for details.
862 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
863 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
864 been removed from mount_fusefs(8). You can safely remove them from
865 your scripts, because they had no effect.
867 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
868 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
869 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
870 sysctls have been removed. If you felt the need to set any of them to
871 a non-default value, please tell asomers@FreeBSD.org why.
874 Default permissions on the /var/account/acct file (and copies of it
875 rotated by periodic daily scripts) are changed from 0644 to 0640
876 because the file contains sensitive information that should not be
877 world-readable. If the /var/account directory must be created by
878 rc.d/accounting, the mode used is now 0750. Admins who use the
879 accounting feature are encouraged to change the mode of an existing
880 /var/account directory to 0750 or 0700.
883 Entropy collection and the /dev/random device are no longer optional
884 components. The "device random" option has been removed.
885 Implementations of distilling algorithms can still be made loadable
886 with "options RANDOM_LOADABLE" (e.g., random_fortuna.ko).
889 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
890 been upgraded to 8.0.1. Please see the 20141231 entry below for
891 information about prerequisites and upgrading, if you are not already
892 using clang 3.5.0 or higher.
895 A fix was applied to i386 kernel modules to avoid panics with
896 dpcpu or vnet. Users need to recompile i386 kernel modules
897 having pcpu or vnet sections or they will refuse to load.
900 User-wired pages now have their own counter,
901 vm.stats.vm.v_user_wire_count. The vm.max_wired sysctl was renamed
902 to vm.max_user_wired and changed from an unsigned int to an unsigned
903 long. bhyve VMs wired with the -S are now subject to the user
904 wiring limit; the vm.max_user_wired sysctl may need to be tuned to
905 avoid running into the limit.
908 The IPSEC option has been removed from GENERIC. Users requiring
909 ipsec(4) must now load the ipsec(4) kernel module.
912 The tap(4) driver has been folded into tun(4), and the module has been
913 renamed to tuntap. You should update any kld_list="if_tap" or
914 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
915 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
916 module instead, and "device tap" or "device tun" entries in kernel
917 config files to select the tuntap device instead.
920 The following knobs have been added related to tradeoffs between
921 safe use of the random device and availability in the absence of
924 kern.random.initial_seeding.bypass_before_seeding: tunable; set
925 non-zero to bypass the random device prior to seeding, or zero to
926 block random requests until the random device is initially seeded.
927 For now, set to 1 (unsafe) by default to restore pre-r346250 boot
928 availability properties.
930 kern.random.initial_seeding.read_random_bypassed_before_seeding:
931 read-only diagnostic sysctl that is set when bypass is enabled and
932 read_random(9) is bypassed, to enable programmatic handling of this
933 initial condition, if desired.
935 kern.random.initial_seeding.arc4random_bypassed_before_seeding:
936 Similar to the above, but for arc4random(9) initial seeding.
938 kern.random.initial_seeding.disable_bypass_warnings: tunable; set
939 non-zero to disable warnings in dmesg when the same conditions are
940 met as for the diagnostic sysctls above. Defaults to zero, i.e.,
941 produce warnings in dmesg when the conditions are met.
944 The loadable random module KPI has changed; the random_infra_init()
945 routine now requires a 3rd function pointer for a bool (*)(void)
946 method that returns true if the random device is seeded (and
947 therefore unblocked).
950 r345895 reverts r320698. This implies that an nfsuserd(8) daemon
951 built from head sources between r320757 (July 6, 2017) and
952 r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
953 is added to the command line.
954 nfsuserd daemons built from head sources that are post-r338192 are
955 not affected and should continue to work.
958 The fuse(4) module has been renamed to fusefs(4) for consistency with
959 other filesystems. You should update any kld_load="fuse" entries in
960 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
961 "options FUSE" entries in kernel config files.
964 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
965 8.0.0. Please see the 20141231 entry below for information about
966 prerequisites and upgrading, if you are not already using clang 3.5.0
970 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
971 compiled into your custom kernel, add 'device xz' statement to the
975 drm and drm2 have been removed from the tree. Please see
976 https://wiki.freebsd.org/Graphics for the latest information on
977 migrating to the drm ports.
980 Iflib is no longer unconditionally compiled into the kernel. Drivers
981 using iflib and statically compiled into the kernel, now require
982 the 'device iflib' config option. For the same drivers loaded as
983 modules on kernels not having 'device iflib', the iflib.ko module
984 is loaded automatically.
987 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
988 options no longer exist since r343219 and r343427 respectively;
989 nothing uses them, so they should be just removed from custom
993 r342635 changes the way efibootmgr(8) works by requiring users to add
994 the -b (bootnum) parameter for commands where the bootnum was previously
995 specified with each option. For example 'efibootmgr -B 0001' is now
996 'efibootmgr -B -b 0001'.
999 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
1000 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
1001 servers that have vfs.nfsd.nfs_privport set will only allow mounts
1002 from clients using a reserved port. Since both the FreeBSD and Linux
1003 NFSv4 clients use reserved ports by default, this should not affect
1007 The XLP config has been removed. We can't support 64-bit atomics in this
1008 kernel because it is running in 32-bit mode. XLP users must transition
1009 to running a 64-bit kernel (XLP64 or XLPN32).
1011 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
1012 the preferred emulator today and we don't need two different ones.
1014 The old sibyte / swarm / Broadcom BCM1250 support has been
1015 removed from the mips port.
1018 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
1019 7.0.1. Please see the 20141231 entry below for information about
1020 prerequisites and upgrading, if you are not already using clang 3.5.0
1024 Remove the timed and netdate programs from the base tree. Setting
1025 the time with these daemons has been obsolete for over a decade.
1028 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
1029 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
1030 it produces broken binaries when ifuncs are in use. Users needing
1031 GNU ld should install the binutils port or package.
1034 The BSD crtbegin and crtend code has been enabled by default. It has
1035 had extensive testing on amd64, arm64, and i386. It can be disabled
1036 by building a world with -DWITHOUT_BSD_CRTBEGIN.
1039 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
1040 has been converted to a port (misc/ctm) and will be removed from
1041 FreeBSD-13. It is available as a package (ctm) for all supported
1045 The default newsyslog.conf(5) file has been changed to only include
1046 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
1047 the filenames end in '.conf' and do not begin with a '.'.
1049 You should check the configuration files in these two directories match
1050 this naming convention. You can verify which configuration files are
1051 being included using the command:
1055 Stable/12 was branched created.
1058 Ports for the DRM modules have been simplified. Now, amd64 users should
1059 just install the drm-kmod port. All others should install
1062 Graphics hardware that's newer than about 2010 usually works with
1063 drm-kmod. For hardware older than 2013, however, some users will need
1064 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
1065 than 2008 usually only works in drm-legacy-kmod. The graphics team can
1066 only commit to hardware made since 2013 due to the complexity of the
1067 market and difficulty to test all the older cards effectively. If you
1068 have hardware supported by drm-kmod, you are strongly encouraged to use
1069 that as you will get better support.
1071 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
1072 elsewhere, the drm and drm2 modules will be eliminated from the src base
1073 soon (with a limited exception for arm). Please update to the package
1074 asap and report any issues to x11@freebsd.org.
1076 Generally, anybody using the drm*-kmod packages should add
1077 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
1078 cross-threading surprises, especially with automatic driver
1079 loading from X11 startup. These will become the defaults in 13-current
1083 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
1084 custom kernel and module loading configuration files must be updated
1085 accordingly. Moreover, interfaces previous presented as ixlvN to the
1086 system are now exposed as iavfN and network configuration files must
1087 be adjusted as necessary.
1090 OpenSSL has been updated to version 1.1.1. This update included
1091 additional various API changes throughout the base system. It is
1092 important to rebuild third-party software after upgrading. The value
1093 of __FreeBSD_version has been bumped accordingly.
1096 The legacy DRM modules and drivers have now been added to the loader's
1097 module blacklist, in favor of loading them with kld_list in rc.conf(5).
1098 The module blacklist may be overridden with the loader.conf(5)
1099 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
1103 The cam(4) based nda(4) driver will be used over nvd(4) by default on
1104 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
1105 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
1106 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
1110 Reproducible build mode is now on by default, in preparation for
1111 FreeBSD 12.0. This eliminates build metadata such as the user,
1112 host, and time from the kernel (and uname), unless the working tree
1113 corresponds to a modified checkout from a version control system.
1114 The previous behavior can be obtained by setting the /etc/src.conf
1115 knob WITHOUT_REPRODUCIBLE_BUILD.
1118 The Yarrow CSPRNG has been removed from the kernel as it has not been
1119 supported by its designers since at least 2003. Fortuna has been the
1120 default since FreeBSD-11.
1123 devctl freeze/thaw have gone into the tree, the rc scripts have been
1124 updated to use them and devmatch has been changed. You should update
1125 kernel, userland and rc scripts all at the same time.
1128 The default interpreter has been switched from 4th to Lua.
1129 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
1130 interpreter. If you have custom FORTH code you will need to set
1131 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
1132 src.conf for the build. This will create default hard links between
1133 loader and loader_4th instead of loader and loader_lua, the new default.
1134 If you are using UEFI it will create the proper hard link to loader.efi.
1136 bhyve uses userboot.so. It remains 4th-only until some issues are solved
1137 regarding coexisting with multiple versions of FreeBSD are resolved.
1140 ls(1) now respects the COLORTERM environment variable used in other
1141 systems and software to indicate that a colored terminal is both
1142 supported and desired. If ls(1) is suddenly emitting colors, they may
1143 be disabled again by either removing the unwanted COLORTERM from your
1144 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
1145 may not be observed in a future release.
1148 The default pager for most commands has been changed to "less". To
1149 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
1153 The jedec_ts(4) driver has been removed. A superset of its functionality
1154 is available in the jedec_dimm(4) driver, and the manpage for that
1155 driver includes migration instructions. If you have "device jedec_ts"
1156 in your kernel configuration file, it must be removed.
1159 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
1160 This should have no effect if the kernel is booted via BIOS/legacy boot.
1161 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
1162 has a buggy firmware that prevents a successful boot due to use of
1166 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
1167 support has been removed from the tree. These ports were
1168 obsolete and/or known to be broken for many years.
1171 loader.efi has been augmented to participate more fully in the
1172 UEFI boot manager protocol. loader.efi will now look at the
1173 BootXXXX environment variable to determine if a specific kernel
1174 or root partition was specified. XXXX is derived from BootCurrent.
1175 efibootmgr(8) manages these standard UEFI variables.
1178 zfsloader's functionality has now been folded into loader.
1179 zfsloader is no longer necessary once you've updated your
1180 boot blocks. For a transition period, we will install a
1181 hardlink for zfsloader to loader to allow a smooth transition
1182 until the boot blocks can be updated (hard link because old
1183 zfs boot blocks don't understand symlinks).
1186 ARM64 now have efifb support, if you want to have serial console
1187 on your arm64 board when an screen is connected and the bootloader
1188 setup a frame buffer for us to use, just add :
1191 in /boot/loader.conf
1192 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
1193 an screen connected as the firmware will setup a frame buffer are that
1194 u-boot will expose as an EFI frame buffer.
1197 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
1198 or take steps to update /etc/passwd before doing installworld on
1199 existing systems. Do not skip the "mergemaster -Fp" step before
1200 installworld, as described in the update procedures near the bottom
1201 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
1202 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
1203 the ntp config file contain options that change file/dir locations.
1204 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
1205 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
1206 taking steps to ensure that all required files/dirs are accessible
1210 Big endian arm support has been removed.
1213 The static environment setup in kernel configs is no longer mutually
1214 exclusive with the loader(8) environment by default. In order to
1215 restore the previous default behavior of disabling the loader(8)
1216 environment if a static environment is present, you must specify
1217 loader_env.disabled=1 in the static environment.
1220 The ABI of syscalls used by management tools like sockstat and
1221 netstat has been broken to allow 32-bit binaries to work on
1222 64-bit kernels without modification. These programs will need
1223 to match the kernel in order to function. External programs may
1224 require minor modifications to accommodate a change of type in
1225 structures from pointers to 64-bit virtual addresses.
1228 On i386 and amd64 atomics are now inlined. Out of tree modules using
1229 atomics will need to be rebuilt.
1232 The '%I' format in the kern.corefile sysctl limits the number of
1233 core files that a process can generate to the number stored in the
1234 debug.ncores sysctl. The '%I' format is replaced by the single digit
1235 index. Previously, if all indexes were taken the kernel would overwrite
1236 only a core file with the highest index in a filename.
1237 Currently the system will create a new core file if there is a free
1238 index or if all slots are taken it will overwrite the oldest one.
1241 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
1242 6.0.1. Please see the 20141231 entry below for information about
1243 prerequisites and upgrading, if you are not already using clang 3.5.0
1247 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
1248 needed to be changed to work with it. This change was made with r335763
1249 and requires a mergemaster / etcupdate / etc to update the installed
1253 r334930 changed the interface between the NFS modules, so they all
1254 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
1257 As of r334391 lld is the default amd64 system linker; it is installed
1258 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
1262 The kernel / userland interface for devinfo changed, so you'll
1263 need a new kernel and userland as a pair for it to work (rebuilding
1264 lib/libdevinfo is all that's required). devinfo and devmatch will
1265 not work, but everything else will when there's a mismatch.
1268 The on-disk format for hwpmc callchain records has changed to include
1269 threadid corresponding to a given record. This changes the field offsets
1270 and thus requires that libpmcstat be rebuilt before using a kernel
1274 The vxge(4) driver has been removed. This driver was introduced into
1275 HEAD one week before the Exar left the Ethernet market and is not
1276 known to be used. If you have device vxge in your kernel config file
1280 The amd64 kernel now requires a ld that supports ifunc to produce a
1281 working kernel, either lld or a newer binutils. lld is built by default
1282 on amd64, and the 'buildkernel' target uses it automatically. However,
1283 it is not the default linker, so building the kernel the traditional
1284 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
1285 binutils port/package). lld will soon be default, and this requirement
1288 NOTE: As of r334391 lld is the default system linker on amd64, and no
1289 workaround is necessary.
1292 The nxge(4) driver has been removed. This driver was for PCI-X 10g
1293 cards made by s2io/Neterion. The company was acquired by Exar and
1294 no longer sells or supports Ethernet products. If you have device
1295 nxge in your kernel config file it must be removed.
1298 The tz database (tzdb) has been updated to 2018e. This version more
1299 correctly models time stamps in time zones with negative DST such as
1300 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
1301 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
1302 time zone abbreviations and the tm_isdst flag.
1305 The ixgb(4) driver has been removed. This driver was for an early and
1306 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
1307 quickly shifted to the long lived ixgbe family. If you have device
1308 ixgb in your kernel config file it must be removed.
1311 The lmc(4) driver has been removed. This was a WAN interface
1312 card that was already reportedly rare in 2003, and had an ambiguous
1313 license. If you have device lmc in your kernel config file it must
1317 Support for Arcnet networks has been removed. If you have device
1318 arcnet or device cm in your kernel config file they must be
1322 Support for FDDI networks has been removed. If you have device
1323 fddi or device fpa in your kernel config file they must be
1327 In addition to supporting RFC 3164 formatted messages, the
1328 syslogd(8) service is now capable of parsing RFC 5424 formatted
1329 log messages. The main benefit of using RFC 5424 is that clients
1330 may now send log messages with timestamps containing year numbers,
1331 microseconds and time zone offsets.
1333 Similarly, the syslog(3) C library function has been altered to
1334 send RFC 5424 formatted messages to the local system logging
1335 daemon. On systems using syslogd(8), this change should have no
1336 negative impact, as long as syslogd(8) and the C library are
1337 updated at the same time. On systems using a different system
1338 logging daemon, it may be necessary to make configuration
1339 adjustments, depending on the software used.
1341 When using syslog-ng, add the 'syslog-protocol' flag to local
1342 input sources to enable parsing of RFC 5424 formatted messages:
1345 unix-dgram("/var/run/log" flags(syslog-protocol));
1348 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
1349 of the 'imuxsock' module to let messages be processed by the
1350 regular RFC 3164/5424 parsing pipeline:
1352 module(load="imuxsock" SysSock.UseSpecialParser="off")
1354 Do note that these changes only affect communication between local
1355 applications and syslogd(8). The format that syslogd(8) uses to
1356 store messages on disk or forward messages to other systems
1357 remains unchanged. syslogd(8) still uses RFC 3164 for these
1358 purposes. Options to customize this behaviour will be added in the
1359 future. Utilities that process log files stored in /var/log are
1360 thus expected to continue to function as before.
1362 __FreeBSD_version has been incremented to 1200061 to denote this
1366 Support for token ring networks has been removed. If you
1367 have "device token" in your kernel config you should remove
1368 it. No device drivers supported token ring.
1371 makefs was modified to be able to tag ISO9660 El Torito boot catalog
1372 entries as EFI instead of overloading the i386 tag as done previously.
1373 The amd64 mkisoimages.sh script used to build amd64 ISO images for
1374 release was updated to use this. This may mean that makefs must be
1375 updated before "make cdrom" can be run in the release directory. This
1376 should be as simple as:
1378 $ cd $SRCDIR/usr.sbin/makefs
1379 $ make depend all install
1382 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
1383 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
1384 Co-existence for the transition period will come shortly. Booting is a
1385 complex environment and test coverage for Lua-enabled loaders has been
1386 thin, so it would be prudent to assume it might not work and make
1387 provisions for backup boot methods.
1390 devmatch functionality has been turned on in devd. It will automatically
1391 load drivers for unattached devices. This may cause unexpected drivers
1392 to be loaded. Please report any problems to current@ and
1396 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
1397 6.0.0. Please see the 20141231 entry below for information about
1398 prerequisites and upgrading, if you are not already using clang 3.5.0
1402 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
1403 This means it is used to link the kernel and userland libraries and
1404 executables, but is not yet installed as /usr/bin/ld by default.
1406 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
1407 WITHOUT_LLD_BOOTSTRAP=yes
1410 On i386, pmtimer has been removed. Its functionality has been folded
1411 into apm. It was a no-op on ACPI in current for a while now (but was
1412 still needed on i386 in FreeBSD 11 and earlier). Users may need to
1413 remove it from kernel config files.
1416 The use of RSS hash from the network card aka flowid has been
1417 disabled by default for lagg(4) as it's currently incompatible with
1418 the lacp and loadbalance protocols.
1420 This can be re-enabled by setting the following in loader.conf:
1421 net.link.lagg.default_use_flowid="1"
1424 The SW_WATCHDOG option is no longer necessary to enable the
1425 hardclock-based software watchdog if no hardware watchdog is
1426 configured. As before, SW_WATCHDOG will cause the software
1427 watchdog to be enabled even if a hardware watchdog is configured.
1430 r326887 fixes the issue described in the 20171214 UPDATING entry.
1431 r326888 flips the switch back to building GELI support always.
1434 r362593 broke ZFS + GELI support for reasons unknown. However,
1435 it also broke ZFS support generally, so GELI has been turned off
1436 by default as the lesser evil in r326857. If you boot off ZFS and/or
1437 GELI, it might not be a good time to update.
1440 PowerPC users must update loader(8) by rebuilding world before
1441 installing a new kernel, as the protocol connecting them has
1442 changed. Without the update, loader metadata will not be passed
1443 successfully to the kernel and users will have to enter their
1444 root partition at the kernel mountroot prompt to continue booting.
1445 Newer versions of loader can boot old kernels without issue.
1448 The LOADER_FIREWIRE_SUPPORT build variable has been renamed to
1449 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
1450 to WITH/OUT_LOADER_GELI.
1453 The naive and non-compliant support of posix_fallocate(2) in ZFS
1454 has been removed as of r325320. The system call now returns EINVAL
1455 when used on a ZFS file. Although the new behavior complies with the
1456 standard, some consumers are not prepared to cope with it.
1457 One known victim is lld prior to r325420.
1460 Building in a FreeBSD src checkout will automatically create object
1461 directories now rather than store files in the current directory if
1462 'make obj' was not ran. Calling 'make obj' is no longer necessary.
1463 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
1464 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
1468 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
1469 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
1470 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
1471 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
1472 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
1473 The UNIFIED_OBJDIR option is a transitional feature that will be
1474 removed for 12.0 release; please migrate to the new format for any
1475 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
1476 than hardcoding paths.
1479 The native-xtools target no longer installs the files by default to the
1480 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
1481 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
1484 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
1485 options are changing from controlling the build if defined / undefined
1486 to controlling the build with explicit 'yes' or 'no' values. They will
1487 shift to WITH/WITHOUT options to match other options in the system.
1490 libstand has turned into a private library for sys/boot use only.
1491 It is no longer supported as a public interface outside of sys/boot.
1494 The arm port has split armv6 into armv6 and armv7. armv7 is now
1495 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
1496 and are running a kernel from before r324363, you will need to add
1497 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
1500 When building multiple kernels using KERNCONF, non-existent KERNCONF
1501 files will produce an error and buildkernel will fail. Previously
1502 missing KERNCONF files silently failed giving no indication as to
1503 why, only to subsequently discover during installkernel that the
1504 desired kernel was never built in the first place.
1507 The default serial number format for CTL LUNs has changed. This will
1508 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
1509 or iSCSI clients care about their LUNs' serial numbers. Users who
1510 require serial number stability should hardcode serial numbers in
1514 For 32-bit arm compiled for hard-float support, soft-floating point
1515 binaries now always get their shared libraries from
1516 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
1517 /usr/libsoft also existed). Only users with a hard-float ld.so, but
1518 soft-float everything else should be affected.
1521 The geli password typed at boot is now hidden. To restore the previous
1522 behavior, see geli(8) for configuration options.
1525 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
1526 sysctl values. Minor nit, but requires a rebuild of both world/kernel
1530 "make check" behavior (made in ^/head@r295380) has been changed to
1531 execute from a limited sandbox, as opposed to executing from
1535 - The "beforecheck" and "aftercheck" targets are now specified.
1536 - ${CHECKDIR} (added in commit noted above) has been removed.
1537 - Legacy behavior can be enabled by setting
1538 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
1540 If the limited sandbox mode is enabled, "make check" will execute
1541 "make distribution", then install, execute the tests, and clean up the
1542 sandbox if successful.
1544 The "make distribution" and "make install" targets are typically run as
1545 root to set appropriate permissions and ownership at installation time.
1546 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
1547 environment if executing "make check" with limited sandbox mode using
1548 an unprivileged user.
1551 Since the switch to GPT disk labels, fsck for UFS/FFS has been
1552 unable to automatically find alternate superblocks. As of r322297,
1553 the information needed to find alternate superblocks has been
1554 moved to the end of the area reserved for the boot block.
1555 Filesystems created with a newfs of this vintage or later
1556 will create the recovery information. If you have a filesystem
1557 created prior to this change and wish to have a recovery block
1558 created for your filesystem, you can do so by running fsck in
1559 foreground mode (i.e., do not use the -p or -y options). As it
1560 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
1561 to which you should answer yes.
1564 As of r321665, an NFSv4 server configuration that services
1565 Kerberos mounts or clients that do not support the uid/gid in
1566 owner/owner_group string capability, must explicitly enable
1567 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
1568 machine's /etc/rc.conf file.
1571 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
1572 Please see the 20141231 entry below for information about prerequisites
1573 and upgrading, if you are not already using clang 3.5.0 or higher.
1576 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
1577 r-commands (rlogin, rsh, etc.) to be built with the base system.
1580 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
1581 a very major ABI incompatible change, so users of FreeBSD/powerpc must
1582 be careful when performing source upgrades. It is best to run
1583 'make installworld' from an alternate root system, either a live
1584 CD/memory stick, or a temporary root partition. Additionally, all ports
1585 must be recompiled. powerpc64 is largely unaffected, except in the case
1586 of 32-bit compatibility. All 32-bit binaries will be affected.
1589 Forward compatibility for the "ino64" project have been committed. This
1590 will allow most new binaries to run on older kernels in a limited
1591 fashion. This prevents many of the common foot-shooting actions in the
1592 upgrade as well as the limited ability to roll back the kernel across
1593 the ino64 upgrade. Complicated use cases may not work properly, though
1594 enough simpler ones work to allow recovery in most situations.
1597 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
1598 if you require the GPL compiler.
1601 Forward compatibility for the "ino64" project have been committed. This
1602 will allow most new binaries to run on older kernels in a limited
1603 fashion. This prevents many of the common foot-shooting actions in the
1604 upgrade as well as the limited ability to roll back the kernel across
1605 the ino64 upgrade. Complicated use cases may not work properly, though
1606 enough simpler ones work to allow recovery in most situations.
1609 The internal ABI used for communication between the NFS kernel modules
1610 was changed by r320085, so __FreeBSD_version was bumped to
1611 ensure all the NFS related modules are updated together.
1614 The ABI of struct event was changed by extending the data
1615 member to 64bit and adding ext fields. For upgrade, same
1616 precautions as for the entry 20170523 "ino64" must be
1620 The GNU roff toolchain has been removed from base. To render manpages
1621 which are not supported by mandoc(1), man(1) can fallback on GNU roff
1622 from ports (and recommends to install it).
1623 To render roff(7) documents, consider using GNU roff from ports or the
1624 heirloom doctools roff toolchain from ports via pkg install groff or
1625 via pkg install heirloom-doctools.
1628 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
1629 smaller runtime footprint builds. This is useful for embedded systems
1630 which only require one chipset support.
1632 If you load it as a module, make sure this is in /boot/loader.conf:
1636 This will load the HAL, all chip/RF backends and if_ath_pci.
1637 If you have if_ath_pci in /boot/loader.conf, ensure it is after
1638 if_ath or it will not load any HAL chipset support.
1640 If you want to selectively load things (eg on cheaper ARM/MIPS
1641 platforms where RAM is at a premium) you should:
1644 * load the chip modules in question
1645 * load ath_rate, ath_dfs
1647 * load if_ath_pci and/or if_ath_ahb depending upon your particular
1648 bus bind type - this is where probe/attach is done.
1650 For further comments/feedback, poke adrian@ .
1653 The "ino64" 64-bit inode project has been committed, which extends
1654 a number of types to 64 bits. Upgrading in place requires care and
1655 adherence to the documented upgrade procedure.
1657 If using a custom kernel configuration ensure that the
1658 COMPAT_FREEBSD11 option is included (as during the upgrade the
1659 system will be running the ino64 kernel with the existing world).
1661 For the safest in-place upgrade begin by removing previous build
1662 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full
1663 procedure documented below under the heading "To rebuild everything and
1664 install it on the current system." Specifically, a reboot is required
1665 after installing the new kernel before installing world. While an
1666 installworld normally works by accident from multiuser after rebooting
1667 the proper kernel, there are many cases where this will fail across this
1668 upgrade and installworld from single user is required.
1671 The NATM framework including the en(4), fatm(4), hatm(4), and
1672 patm(4) devices has been removed. Consumers should plan a
1673 migration before the end-of-life date for FreeBSD 11.
1676 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
1677 diff has not been implemented, if those are needed a newer version of
1678 GNU diff is available via the diffutils package under the gdiff name.
1681 As of r316810 for ipfilter, keep frags is no longer assumed when
1682 keep state is specified in a rule. r316810 aligns ipfilter with
1683 documentation in man pages separating keep frags from keep state.
1684 This allows keep state to be specified without forcing keep frags
1685 and allows keep frags to be specified independently of keep state.
1686 To maintain previous behaviour, also specify keep frags with
1687 keep state (as documented in ipf.conf.5).
1690 arm64 builds now use the base system LLD 4.0.0 linker by default,
1691 instead of requiring that the aarch64-binutils port or package be
1692 installed. To continue using aarch64-binutils, set
1693 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
1696 The UDP optimization in entry 20160818 that added the sysctl
1697 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
1698 packets will no longer be treated as L3 broadcast packets.
1701 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
1702 use any explicitly assigned loopback address available in the jail
1703 instead of using the first assigned address of the jail.
1706 The ctl.ko module no longer implements the iSCSI target frontend:
1707 cfiscsi.ko does instead.
1709 If building cfiscsi.ko as a kernel module, the module can be loaded
1710 via one of the following methods:
1711 - `cfiscsi_load="YES"` in loader.conf(5).
1712 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
1713 - ctladm(8)/ctld(8), when compiled with iSCSI support
1714 (`WITH_ISCSI=yes` in src.conf(5))
1716 Please see cfiscsi(4) for more details.
1719 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
1720 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
1721 same source (previously, the dependency of mmcsd.ko on mmc.ko was
1722 missing, but mmcsd.ko now will refuse to load if it is incompatible
1726 The syntax of ipfw(8) named states was changed to avoid ambiguity.
1727 If you have used named states in the firewall rules, you need to modify
1728 them after installworld and before rebooting. Now named states must
1729 be prefixed with colon.
1732 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
1733 removed as the userland we provide cannot use them. The KMS version
1734 (sys/dev/drm2) supports the same hardware.
1737 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
1738 Please see the 20141231 entry below for information about prerequisites
1739 and upgrading, if you are not already using clang 3.5.0 or higher.
1742 The code that provides support for ZFS .zfs/ directory functionality
1743 has been reimplemented. It's not possible now to create a snapshot
1744 by mkdir under .zfs/snapshot/. That should be the only user visible
1748 EISA bus support has been removed. The WITH_EISA option is no longer
1752 MCA bus support has been removed.
1755 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
1756 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
1759 The EM_MULTIQUEUE kernel configuration option is deprecated now that
1760 the em(4) driver conforms to iflib specifications.
1763 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
1764 IFLIB. If you have a custom kernel configuration that excludes em(4)
1765 but you use igb(4), you need to re-add em(4) to your custom
1769 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
1770 Please see the 20141231 entry below for information about prerequisites
1771 and upgrading, if you are not already using clang 3.5.0 or higher.
1774 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
1775 Please see the 20141231 entry below for information about prerequisites
1776 and upgrading, if you are not already using clang 3.5.0 or higher.
1779 The layout of the pmap structure has changed for powerpc to put the pmap
1780 statistics at the front for all CPU variations. libkvm(3) and all tools
1781 that link against it need to be recompiled.
1784 isl(4) and cyapa(4) drivers now require a new driver,
1785 chromebook_platform(4), to work properly on Chromebook-class hardware.
1786 On other types of hardware the drivers may need to be configured using
1787 device hints. Please see the corresponding manual pages for details.
1790 The urtwn(4) driver was merged into rtwn(4) and now consists of
1791 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
1793 Also, firmware for RTL8188CE was renamed due to possible name
1794 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
1797 GNU rcs has been removed from base. It is available as packages:
1798 - rcs: Latest GPLv3 GNU rcs version.
1799 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
1803 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
1804 modules now requires that the kernel configuration contain the
1805 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
1808 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
1809 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
1812 Relocatable object files with the extension of .So have been renamed
1813 to use an extension of .pico instead. The purpose of this change is
1814 to avoid a name clash with shared libraries on case-insensitive file
1815 systems. On those file systems, foo.So is the same file as foo.so.
1818 GNU rcs has been turned off by default. It can (temporarily) be built
1819 again by adding WITH_RCS knob in src.conf.
1820 Otherwise, GNU rcs is available from packages:
1821 - rcs: Latest GPLv3 GNU rcs version.
1822 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
1825 The backup_uses_rcs functionality has been removed from rc.subr.
1828 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
1829 two separate components, QUEUE_MACRO_DEBUG_TRACE and
1830 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
1831 QUEUE_MACRO_DEBUG behavior.
1834 r304787 changed some ioctl interfaces between the iSCSI userspace
1835 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1836 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1840 The UDP receive code has been updated to only treat incoming UDP
1841 packets that were addressed to an L2 broadcast address as L3
1842 broadcast packets. It is not expected that this will affect any
1843 standards-conforming UDP application. The new behaviour can be
1844 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1848 Remove the openbsd_poll system call.
1849 __FreeBSD_version has been bumped because of this.
1852 The stable/11 branch has been created from head@r302406.
1854 After branch N is created, entries older than the N-2 branch point are removed
1855 from this file. After stable/14 is branched and current becomes FreeBSD 15,
1856 entries older than stable/12 branch point will be removed from current's
1863 Sometimes, obscure build problems are the result of environment
1864 poisoning. This can happen because the make utility reads its
1865 environment when searching for values for global variables. To run
1866 your build attempts in an "environmental clean room", prefix all make
1867 commands with 'env -i '. See the env(1) manual page for more details.
1868 Occasionally a build failure will occur with "make -j" due to a race
1869 condition. If this happens try building again without -j, and please
1870 report a bug if it happens consistently.
1872 When upgrading from one major version to another it is generally best to
1873 upgrade to the latest code in the currently installed branch first, then
1874 do an upgrade to the new branch. This is the best-tested upgrade path,
1875 and has the highest probability of being successful. Please try this
1876 approach if you encounter problems with a major version upgrade. Since
1877 the stable 4.x branch point, one has generally been able to upgrade from
1878 anywhere in the most recent stable branch to head / current (or even the
1879 last couple of stable branches). See the top of this file when there's
1882 The update process will emit an error on an attempt to perform a build
1883 or install from a FreeBSD version below the earliest supported version.
1884 When updating from an older version the update should be performed one
1885 major release at a time, including running `make delete-old` at each
1888 When upgrading a live system, having a root shell around before
1889 installing anything can help undo problems. Not having a root shell
1890 around can lead to problems if pam has changed too much from your
1891 starting point to allow continued authentication after the upgrade.
1893 This file should be read as a log of events. When a later event changes
1894 information of a prior event, the prior event should not be deleted.
1895 Instead, a pointer to the entry with the new information should be
1896 placed in the old entry. Readers of this file should also sanity check
1897 older entries before relying on them blindly. Authors of new entries
1898 should write them with this in mind.
1902 When upgrading the boot ZFS pool to a new version (via zpool upgrade),
1903 always follow these three steps:
1905 1) recompile and reinstall the ZFS boot loader and boot block
1906 (this is part of "make buildworld" and "make installworld")
1908 2) update the ZFS boot block on your boot drive (only required when
1909 doing a zpool upgrade):
1911 When booting on x86 via BIOS, use the following to update the ZFS boot
1912 block on the freebsd-boot partition of a GPT partitioned drive ada0:
1913 gpart bootcode -p /boot/gptzfsboot -i $N ada0
1914 The value $N will typically be 1. For EFI booting, see EFI notes.
1916 3) zpool upgrade the root pool. New bootblocks will work with old
1917 pools, but not vice versa, so they need to be updated before any
1920 Non-boot pools do not need these updates.
1925 There are two locations the boot loader can be installed into. The
1926 current location (and the default) is \efi\freebsd\loader.efi and using
1927 efibootmgr(8) to configure it. The old location, that must be used on
1928 deficient systems that don't honor efibootmgr(8) protocols, is the
1929 fallback location of \EFI\BOOT\BOOTxxx.EFI. Generally, you will copy
1930 /boot/loader.efi to this location, but on systems installed a long time
1931 ago the ESP may be too small and /boot/boot1.efi may be needed unless
1932 the ESP has been expanded in the meantime.
1934 Recent systems will have the ESP mounted on /boot/efi, but older ones
1935 may not have it mounted at all, or mounted in a different
1936 location. Older arm SD images with MBR used /boot/msdos as the
1937 mountpoint. The ESP is a MSDOS filesystem.
1939 The EFI boot loader rarely needs to be updated. For ZFS booting,
1940 however, you must update loader.efi before you do 'zpool upgrade' the
1941 root zpool, otherwise the old loader.efi may reject the upgraded zpool
1942 since it does not automatically understand some new features.
1944 See loader.efi(8) and uefi(8) for more details.
1948 If you are updating from a prior version of FreeBSD (even one just
1949 a few days old), you should follow this procedure. It is the most
1950 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1952 make kernel-toolchain
1953 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1954 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1956 To test a kernel once
1957 ---------------------
1958 If you just want to boot a kernel once (because you are not sure
1959 if it works, or if you want to boot a known bad kernel to provide
1960 debugging information) run
1961 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1962 nextboot -k testkernel
1964 To rebuild everything and install it on the current system.
1965 -----------------------------------------------------------
1966 # Note: sometimes if you are running current you gotta do more than
1967 # is listed here if you are upgrading from a really old current.
1969 <make sure you have good level 0 dumps>
1971 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1972 make installkernel KERNCONF=YOUR_KERNEL_HERE
1974 <reboot in single user> [3]
1981 To cross-install current onto a separate partition
1982 --------------------------------------------------
1983 # In this approach we use a separate partition to hold
1984 # current's root, 'usr', and 'var' directories. A partition
1985 # holding "/", "/usr" and "/var" should be about 2GB in
1988 <make sure you have good level 0 dumps>
1991 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1992 <maybe newfs current's root partition>
1993 <mount current's root partition on directory ${CURRENT_ROOT}>
1994 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1995 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1996 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1997 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1998 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1999 <reboot into current>
2000 <do a "native" rebuild/install as described in the previous section>
2001 <maybe install compatibility libraries from ports/misc/compat*>
2005 To upgrade in-place from stable to current
2006 ----------------------------------------------
2007 <make sure you have good level 0 dumps>
2009 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
2010 make installkernel KERNCONF=YOUR_KERNEL_HERE
2012 <reboot in single user> [3]
2019 Make sure that you've read the UPDATING file to understand the
2020 tweaks to various things you need. At this point in the life
2021 cycle of current, things change often and you are on your own
2022 to cope. The defaults can also change, so please read ALL of
2023 the UPDATING entries.
2025 Also, if you are tracking -current, you must be subscribed to
2026 freebsd-current@freebsd.org. Make sure that before you update
2027 your sources that you have read and understood all the recent
2028 messages there. If in doubt, please track -stable which has
2029 much fewer pitfalls.
2031 [1] If you have third party modules, such as vmware, you should disable
2032 them at this point so they don't crash your system on
2033 reboot. Alternatively, you should rebuild all the modules you have in
2034 your system and install them as well. If you are running -current, you
2035 should seriously consider placing all sources to all the modules for
2036 your system (or symlinks to them) in /usr/local/sys/modules so this
2037 happens automatically. If all your modules come from ports, then adding
2038 the port origin directories to PORTS_MODULES instead is also automatic
2040 PORTS_MODULES+=x11/nvidia-driver
2042 [3] From the bootblocks, boot -s, and then do
2046 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed
2047 cd src # full path to source
2048 adjkerntz -i # if CMOS is wall time
2049 Also, when doing a major release upgrade, it is required that you boot
2050 into single user mode to do the installworld.
2052 [4] Note: This step is non-optional. Failure to do this step
2053 can result in a significant reduction in the functionality of the
2054 system. Attempting to do it by hand is not recommended and those
2055 that pursue this avenue should read this file carefully, as well
2056 as the archives of freebsd-current and freebsd-hackers mailing lists
2057 for potential gotchas. See etcupdate(8) for more information.
2059 [5] Usually this step is a no-op. However, from time to time
2060 you may need to do this if you get unknown user in the following
2063 [6] This only deletes old files and directories. Old libraries
2064 can be deleted by "make delete-old-libs", but you have to make
2065 sure that no program is using those libraries anymore.
2067 [8] The new kernel must be able to run existing binaries used by an
2068 installworld. When upgrading across major versions, the new kernel's
2069 configuration must include the correct COMPAT_FREEBSD<n> option for
2070 existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure
2071 to do so may leave you with a system that is hard to boot to recover. A
2072 GENERIC kernel will include suitable compatibility options to run
2073 binaries from older branches. Note that the ability to run binaries
2074 from unsupported branches is not guaranteed.
2076 Make sure that you merge any new devices from GENERIC since the
2077 last time you updated your kernel config file. Options also
2078 change over time, so you may need to adjust your custom kernels
2081 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2082 "?=" instead of the "=" assignment operator, so that buildworld can
2083 override the CPUTYPE if it needs to.
2085 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2086 not on the command line, or in /etc/make.conf. buildworld will
2087 warn if it is improperly defined.
2090 This file contains a list, in reverse chronological order, of major
2091 breakages in tracking -current. It is not guaranteed to be a complete
2092 list of such breakages, and only contains entries since September 23, 2011.
2093 If you need to see UPDATING entries from before that date, you will need
2094 to fetch an UPDATING file from an older FreeBSD release.
2096 Copyright information:
2098 Copyright 1998-2009 M. Warner Losh <imp@FreeBSD.org>
2100 Redistribution, publication, translation and use, with or without
2101 modification, in full or in part, in any form or format of this
2102 document are permitted without further permission from the author.
2104 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2105 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2106 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2107 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2108 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2109 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2110 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2111 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2112 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2113 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2114 POSSIBILITY OF SUCH DAMAGE.
2116 Contact Warner Losh if you have any questions about your use of