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 sendmail 8.18.1 has been imported and merged. This version enforces
32 stricter RFC compliance by default, especially with respect to line
33 endings. This may cause issues with receiving messages from
34 non-compliant MTAs; please see the first 8.18.1 release note in
35 contrib/sendmail/RELEASE_NOTES for mitigations.
38 Commit cc760de2183f changed the internal interface between
39 the nfscommon and nfscl modules. As such, both need to be
40 rebuilt from sources. Therefore, __FreeBSD_version was
44 If you have an arm64 system that uses ACPI, you will need to update your
45 loader.efi in the ESP when you update past this point. Detection of ACPI
46 was moved earlier in the binary so the scripts could use it, but old
47 binaries don't have this, so we default to 'no ACPI' in this case. You can
48 undisable ACPI by doing
49 OK unset hint.acpi.0.disabled
50 This can also be used to recover any other system that was updated in the
51 small window where amd64 was also broken.
54 The WITHOUT_LLD_IS_LD option has been removed. When LLD is enabled
55 it is always installed as /usr/bin/ld.
58 Forward compatibility (running the new code on old kernels) for the
59 "ino64" project have been removed. The need for it has passed long ago.
62 Commit 57ce37f9dcd0 changed the internal KAPI between the
63 nfscommon and nfscl modules. Both must be rebuilt from sources.
66 dialog(1) has been replaced in base by bsddialog(1), while most of the
67 time replacing a dialog(1) call by a bsddialog(1) call works out of the
68 box, bsddialog(1) is not considered as a drop-in replacement for
71 If you do depend on dialog(1) functionality, please install cdialog
77 The EARLY_AP_STARTUP kernel option is mandatory on x86. The option
78 has been added to DEFAULTS, so it should automatically be included in
79 custom kernel configurations without any additional change.
82 A new loader tunable net.pf.default_to_drop allows pf(4)’s default
83 behaviour to be changed from pass to drop. Previously this required
84 recompiling the kernel with the option PF_DEFAULT_TO_DROP.
87 Enable splitting out pkgbase manpages into separate packages by
88 default. To disable this, set WITHOUT_MANSPLITPKG=yes in src.conf.
91 Move standard include files to the clibs-dev package and move clang
92 internal libraries and headers to clang and clang-dev. Upgrading systems
93 installed using pkgbase past this change involves extra steps to allow
96 pkg upgrade -y FreeBSD-utilities
97 pkg upgrade -y FreeBSD-utilities-dev
101 Enable vnet sysctl variables to be loader tunable. SYSCTLs which
102 belongs to VNETs can be initialized during early boot or module
103 loading if they are marked with CTLFLAG_TUN and there are
104 corresponding kernel environment variables.
107 The WITH_INIT_ALL_PATTERN and WITH_INIT_ALL_ZERO build options have
108 been replaced by INIT_ALL=pattern and INIT_ALL=zero respectively.
111 FreeBSD 15.0-CURRENT.
114 Serial communication (in boot loaders, kernel, and userland) has
115 been changed to default to 115200 bps, in line with common industry
116 practice and typcial firmware serial console redirection
119 Note that the early x86 BIOS bootloader (i.e., boot0sio) does not
120 support rates above 9600 bps and is not changed. boot0sio users may
121 set BOOT_COMCONSOLE_SPEED=9600 to use 9600 for all of the boot
122 components, or use the standard boot0 and have the boot2 stage start
123 with the serial port at 115200.
126 Following the general removal of MIPS support, the ath(4) AHB bus-
127 frontend has been removed, too, and building of the PCI support is
128 integrated with the ath(4) main module again. As a result, there's
129 no longer a need for if_ath_pci_load="YES" in /boot/loader.conf or
130 "device ath_pci" in the kernel configuration.
133 MAXCPU has been increased to 1024 in the amd64 GENERIC kernel config.
134 Out-of-tree kernel modules will need to be rebuilt.
137 CAM has been mechanically updated s/u_int(64|32|16|8)_t/uint\1_t/g
138 to move to the standard uintXX_t types from the old, traditional
139 BSD u_intXX_t types. This should be a NOP, but may cause problems
140 for out of tree changes. The SIMs were not updated since most of
141 the old u_intXX_t uses weren't due to CAM interfaces.
144 stable/14 branch created.
147 The heuristic for detecting old chromebooks with an EC bug that requires
148 atkbdc driver workarounds has changed. There should be no functional
149 change, but if your old chromebook's keyboard stops working, please
150 file a PR and assign it to imp.
153 OpenSSL has been updated to version 3.0, including changes throughout
154 the base system. It is important to rebuild third-party software
158 To enable pf rdr rules for connections initiated from the host, pf
159 filter rules can be optionally enabled for packets delivered
160 locally. This can change the behavior of rules which match packets
161 delivered to lo0. To enable this feature:
163 sysctl net.pf.filter_local=1
166 When enabled, its best to ensure that packets delivered locally are not
167 filtered, e.g. by adding a 'skip on lo' rule.
170 Improvements to libtacplus(8) mean that tacplus.conf(5) now
171 follows POSIX shell syntax rules. This may cause TACACS+
172 authentication to fail if the shared secret contains a single
173 quote, double quote, or backslash character which isn't
174 already properly quoted or escaped.
177 Belatedly switch the default nvme block device on x86 from nvd to nda.
178 nda created nvd compatibility links by default, so this should be a
179 nop. If this causes problems for your application, set hw.nvme.use_nvd=1
180 in your loader.conf or add `options NVME_USE_NVD=1` to your kernel
181 config. To disable the nvd compatibility aliases, add
182 kern.cam.nda.nvd_compat=0 to loader.conf. The default has been nda on
183 all non-x86 platforms for some time now. If you need to fall back,
184 please email imp@freebsd.org about why.
186 Encrypted swap partitions need to be changed from nvd to nda if you
187 migrate, or you need to use the above to switch back to nvd.
190 Remove portsnap(8). Users are encouraged to obtain the ports tree
194 Add jobs.mk to save typing. Enables -j${JOB_MAX} and logging
198 make -j${JOB_MAX} buildworld > ../buildworld.log 2>&1
200 where JOB_MAX is derrived from ncpus in local.sys.mk if not set in env.
203 Video related devices for some arm devices have been renamed.
204 If you have a custom kernel config and want to use hdmi output on
205 IMX6 board you need to add "device dwc_hdmi" "device imx6_hdmi" and
206 "device imx6_ipu" to it.
207 If you have a custom kernel config and want to use hdmi output on
208 TI AM335X board you need to add "device tda19988" to it.
209 If you add "device hdmi" in it you need to remove it as it doesn't
213 Introduce new kernel options KBD_DELAY1 and KBD_DELAY2. See atkbdc(4)
217 sshd now defaults to having X11Forwarding disabled, following upstream.
218 Administrators who wish to enable X11Forwarding should add
219 `X11Forwarding yes` to /etc/ssh/sshd_config.
222 Since commit 75d41cb6967 Huawei 3G/4G LTE Mobile Devices do not default
223 to ECM, but NCM mode and need u3g and ucom modules loaded. See cdce(4).
226 As of commit 7c40e2d5f685, the dependency on netlink(4) has been added
227 to the linux_common(4) module. Users relying on linux_common may need
228 to complile netlink(4) module if it is not present in their kernel.
231 The WITHOUT_CXX option has been removed. C++ components in the base
232 system are now built unconditionally.
235 LinuxKPI pci.h changes may require out-of-tree drivers to be recompiled.
236 Bump _FreeBSD_version to 1400078 to be able to detect this change.
239 llvm-objump is now always installed as objdump. Previously there was
240 no /usr/bin/objdump unless the WITH_LLVM_BINUTILS knob was used.
242 Some LLVM objdump options have a different output format compared to
243 GNU objdump; readelf is available for inspecting ELF files, and GNU
244 objdump is available from the devel/binutils port or package.
247 dma(8) has replaced sendmail(8) as the default mta. For people willing
248 to reenable sendmail(8):
250 $ cp /usr/share/examples/sendmail/mailer.conf /etc/mail/mailer.conf
252 and add sendmail_enable="YES" to rc.conf.
255 hw.bus.disable_failed_devices has changed from 'false' to 'true' by
256 default. Now if newbus succeeds in probing a device, but fails to attach
257 the device, we'll disable the device. In the past, we'd keep retrying
258 the device on each new driver loaded. To get that behavior now, one
259 needs to use devctl to re-enable the device, and reprobe it (or set
260 the sysctl/tunable hw.bus.disable_failed_devices=false).
262 NOTE: This was reverted 20221205 due to unexpected compatibility issues
265 pf no longer accepts 'scrub fragment crop' or 'scrub fragment drop-ovl'.
266 These configurations are no longer automatically reinterpreted as
267 'scrub fragment reassemble'.
270 The WITHOUT_CLANG_IS_CC option has been removed. When Clang is enabled
271 it is always installed as /usr/bin/cc (and c++, cpp).
274 Some programs have been moved into separate packages. It is recommended
275 for pkgbase users to do:
277 pkg install FreeBSD-dhclient FreeBSD-geom FreeBSD-resolvconf \
278 FreeBSD-devd FreeBSD-devmatch
280 after upgrading to restore all the component that were previously
284 OPIE has been removed from the base system. If needed, it can
285 be installed from ports (security/opie) or packages (opie).
286 Otherwise, make sure that your PAM policies do not reference
287 pam_opie or pam_opieaccess.
290 LinuxKPI pm.h changes require an update to the latest drm-kmod version
291 before re-compiling to avoid errors.
294 The macros provided for the manipulation of CPU sets (e.g. CPU_AND)
295 have been modified to take 2 source arguments instead of only 1.
296 Externally maintained sources that use these macros will have to
297 be adapted. The FreeBSD version has been bumped to 1400046 to
301 A number of the kernel include files are able to be included by
302 themselves. A test has been added to buildworld to enforce this.
305 Remove mips as a recognized target. This starts the decommissioning of
306 mips support in FreeBSD. mips related items will be removed wholesale in
307 the coming days and weeks.
309 This broke the NO_CLEAN build for some people. Either do a clean build
311 lib/clang/include/llvm/Config/Targets.def
312 lib/clang/include/llvm/Config/AsmParsers.def
313 lib/clang/include/llvm/Config/Disassemblers.def
314 lib/clang/include/llvm/Config/AsmPrinters.def
315 before the build to force everything to rebuild that needs to.
318 Unbound support for RFC8375: The special-use domain 'home.arpa' is
319 by default blocked. To unblock it use a local-zone nodefault
320 statement in unbound.conf:
321 local-zone: "home.arpa." nodefault
323 Or use another type of local-zone to override with your choice.
325 The reason for this is discussed in Section 6.1 of RFC8375:
326 Because 'home.arpa.' is not globally scoped and cannot be secured
327 using DNSSEC based on the root domain's trust anchor, there is no way
328 to tell, using a standard DNS query, in which homenet scope an answer
329 belongs. Consequently, users may experience surprising results with
330 such names when roaming to different homenets.
333 Commit b8d60729deef changed the TCP congestion control framework so
334 that any of the included congestion control modules could be
335 the single module built into the kernel. Previously newreno
336 was automatically built in through direct reference. As of
337 this commit you are required to declare at least one congestion
338 control module (e.g. 'options CC_NEWRENO') and to also declare a
339 default using the CC_DEFAULT option (e.g. options CC_DEFAULT="newreno\").
340 The GENERIC configuration includes CC_NEWRENO and defines newreno
341 as the default. If no congestion control option is built into the
342 kernel and you are including networking, the kernel compile will
343 fail. Also if no default is declared the kernel compile will fail.
346 Mips has been removed from universe builds. It will be removed from the
350 Commit f0c9847a6c47 changed the arguments for VOP_ALLOCATE.
351 The NFS modules must be rebuilt from sources and any out
352 of tree file systems that implement their own VOP_ALLOCATE
353 may need to be modified.
356 The synchronous PPP kernel driver sppp(4) has been removed.
357 The cp(4) and ce(4) drivers are now always compiled with netgraph(4)
358 support, formerly enabled by NETGRAPH_CRONYX option.
361 sh(1) is now the default shell for the root user. To force root to use
362 the csh shell, please run the following command as root:
367 Ncurses distribution has been split between libtinfow and libncurses
368 with libncurses.so becoming a linker (ld) script to seamlessly link
369 to libtinfow as needed. Bump _FreeBSD_version to 1400035 to reflect
373 As of commit 8160a0f62be6, the dummynet module no longer depends on the
374 ipfw module. Dummynet can now be used by pf as well as ipfw. As such
375 users who relied on this dependency may need to include ipfw in the
376 list of modules to load on their systems.
379 As of commit 903873ce1560, the mixer(8) utility has got a slightly
380 new syntax. Please refer to the mixer(8) manual page for more
381 information. The old mixer utility can be installed from ports:
382 audio/freebsd-13-mixer
385 As of commit 55089ef4f8bb, the global variable nfs_maxcopyrange has
386 been deleted from the nfscommon.ko. As such, nfsd.ko must be built
387 from up to date sources to avoid an undefined reference when
391 As of commit 62ca9fc1ad56 OpenSSL no longer enables kernel TLS
392 by default. Users can enable kernel TLS via the "KTLS" SSL
393 option. This can be enabled globally by using a custom
394 OpenSSL config file via OPENSSL_CONF or via an
395 application-specific configuration option for applications
396 which permit setting SSL options via SSL_CONF_cmd(3).
399 Commit 3ad1e1c1ce20 changed the internal KAPI between the NFS
400 modules. Therefore, all need to be rebuilt from sources.
403 Commit b69019c14cd8 removes pf's DIOCGETSTATESNV ioctl.
404 As of be70c7a50d32 it is no longer used by userspace, but it does mean
405 users may not be able to enumerate pf states if they update the kernel
406 past b69019c14cd8 without first updating userspace past be70c7a50d32.
409 As of commit 01ad0c007964 if_bridge member interfaces can no longer
410 change their MTU. Changing the MTU of the bridge itself will change the
411 MTU on all member interfaces instead.
414 Commit ee29e6f31111 changed the internal KAPI between the nfscommon
415 and nfsd modules. Therefore, both need to be rebuilt from sources.
416 Bump __FreeBSD_version to 1400026 for this KAPI change.
419 The 20210707 awk update brought in a change in behavior. This has
420 been corrected as of d4d252c49976. Between these dates, if you
421 installed a new awk binary, you may not be able to build a new
422 kernel because the change in behavior affected the genoffset
423 script used to build the kernel. If you did update, the fix is
424 to update your sources past the above hash and do
427 % sudo -E make install
428 to enable building kernels again.
431 Commit 1e0a518d6548 changed the internal KAPI between the NFS
432 modules. They all need to be rebuilt from sources. I did not
433 bump __FreeBSD_version, since it was bumped recently.
436 awk has been updated to the latest one-true-awk version 20210215.
437 This contains a number of minor bug fixes.
440 The NFSv4 client now uses the highest minor version of NFSv4
441 supported by the NFSv4 server by default instead of minor version 0,
443 The "minorversion" mount option may be used to override this default.
446 Bump __FreeBSD_version to 1400024 for LinuxKPI changes.
447 Most notably netdev.h can change now as the (last) dependencies
448 (mlx4/ofed) are now using struct ifnet directly, but also for PCI
449 additions and others.
452 The directory "blacklisted" under /usr/share/certs/ has been
453 renamed to "untrusted".
456 svnlite has been removed from base. Should you need svn for any reason
457 please install the svn package or port.
460 Commit e1a907a25cfa changed the internal KAPI between the krpc
461 and nfsserver. As such, both modules must be rebuilt from
462 sources. Bump __FreeBSD_version to 1400022.
465 The an(4) driver has been removed from FreeBSD.
468 The vendor/openzfs branch was renamed to vendor/openzfs/legacy to
469 start tracking OpenZFS upstream more closely. Please see
470 https://lists.freebsd.org/archives/freebsd-current/2021-June/000153.html
471 for details on how to correct any errors that might result. The
472 short version is that you need to remove the old branch locally:
473 git update-ref -d refs/remotes/freebsd/vendor/openzfs
474 (assuming your upstream origin is named 'freebsd').
477 Commits 17accc08ae15 and de102f870501 add new files to LinuxKPI
478 which break drm-kmod. In addition various other additions where
479 committed. Bump __FreeBSD_version to 1400015 to be able to
483 Commit ca179c4d74f2 changed the package in which the OpenSSL
484 libraries and utilities are packaged.
485 It is recommended for pkgbase user to do:
486 pkg install -f FreeBSD-openssl
487 before pkg upgrade otherwise some dependencies might not be met
488 and pkg will stop working as libssl will not be present anymore
492 Commit 875977314881 changed the internal KAPI between
493 the nfsd and nfscommon modules. As such these modules
494 need to be rebuilt from sources.
495 Without this patch in your NFSv4.1/4.2 server, enabling
496 delegations by setting vfs.nfsd.issue_delegations non-zero
500 Commit 7763814fc9c2 changed the internal KAPI between
501 the krpc and NFS. As such, the krpc, nfscommon and
502 nfscl modules must all be rebuilt from sources.
503 Without this patch, NFSv4.1/4.2 mounts should not
504 be done with the nfscbd(8) daemon running, to avoid
505 needing a working back channel for server->client RPCs.
508 Commit 01ae8969a9ee fixed the NFSv4.1/4.2 server so that it
509 handles binding of the back channel as required by RFC5661.
510 Until this patch is in your server, avoid use of the "nconnects"
511 mount option for Linux NFSv4.1/4.2 mounts.
514 For 64-bit architectures the base system is now built with Position
515 Independent Executable (PIE) support enabled by default. It may be
516 disabled using the WITHOUT_PIE knob. A clean build is required.
519 Various LinuxKPI functionality was added which conflicts with DRM.
520 Please update your drm-kmod port to after the __FreeBSD_version 1400003
524 stable/13 branch created.
527 PC Card attachments for all devices have been removed. In the case of
528 wi and cmx, the entire drivers were removed because they were only
529 PC Card devices. FreeBSD_version 1300134 should be used for this
530 since it was bumped so recently.
533 Transport-independent parts of HID support have been split off the USB
534 code in to separate subsystem. Kernel configs which include one of
535 ums, ukbd, uhid, atp, wsp, wmt, uaudio, ugold or ucycom drivers should
536 be updated with adding of "device hid" line.
539 ncurses installation has been modified to only keep the widechar
540 enabled version. Incremental build is broken for that change, so it
541 requires a clean build.
544 The FreeBSD project has migrated from Subversion to Git. Temporary
545 instructions can be found at
546 https://github.com/bsdimp/freebsd-git-docs/blob/main/src-cvt.md
547 and other documents in that repo.
550 The services database has been updated to cover more of the basic
551 services expected in a modern system. The database is big enough
552 that it will cause issues in mergemaster in Releases previous to
553 12.2 and 11.3, or in very old current systems from before r358154.
556 Obsolete in-tree GDB 6.1.1 has been removed. GDB (including kgdb)
557 may be installed from ports or packages.
560 ping6 has been merged into ping. It can now be called as "ping -6".
561 See ping(8) for details.
564 Default value of net.add_addr_allfibs has been changed to 0.
565 If you have multi-fib configuration and rely on existence of all
566 interface routes in every fib, you need to set the above sysctl to 1.
569 The internal pre-processor in the calendar(1) program has been
570 extended to support more C pre-processor commands (e.g. #ifdef, #else,
571 and #undef) and to detect unbalanced conditional statements.
572 Error messages have been extended to include the filename and line
573 number if processing stops to help fixing malformed data files.
576 All the data files for the calendar(1) program, except calendar.freebsd,
577 have been moved to the deskutils/calendar-data port, much like the
578 jewish calendar entries were moved to deskutils/hebcal years ago. After
579 make delete-old-files, you need to install it to retain full
580 functionality. calendar(1) will issue a reminder for files it can't
584 LINT files are no longer generated. We now include the relevant NOTES
585 files. Note: This may cause conflicts with updating in some cases.
586 find sys -name LINT\* -delete
587 is suggested across this commit to remove the generated LINT files.
589 If you have tried to update with generated files there, the svn
590 command you want to un-auger the tree is
593 and then do the above find from the top level. Substitute 'amd64'
594 above with where the error message indicates a conflict.
597 OpenZFS support has been integrated. Do not upgrade root pools until
598 the loader is updated to support zstd. Furthermore, we caution against
599 'zpool upgrade' for the next few weeks. The change should be transparent
600 unless you want to use new features.
602 Not all "NO_CLEAN" build scenarios work across these changes. Many
603 scenarios have been tested and fixed, but rebuilding kernels without
604 rebuilding world may fail.
606 The ZFS cache file has moved from /boot to /etc to match the OpenZFS
607 upstream default. A fallback to /boot has been added for mountroot.
609 Pool auto import behavior at boot has been moved from the kernel module
610 to an explicit "zpool import -a" in one of the rc scripts enabled by
611 zfs_enable=YES. This means your non-root zpools won't auto import until
612 you upgrade your /etc/rc.d files.
615 The resume code now notifies devd with the 'kernel' system
616 rather than the old 'kern' subsystem to be consistent with
617 other use. The old notification will be created as well, but
618 will be removed prior to FreeBSD 14.0.
621 r362275 changed the internal API between the kernel RPC and the
622 NFS modules. As such, all the modules must be recompiled from
626 r364330 modified the internal API used between the NFS modules.
627 As such, all the NFS modules must be re-compiled from sources.
630 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
631 been upgraded to 11.0.0. Please see the 20141231 entry below for
632 information about prerequisites and upgrading, if you are not already
633 using clang 3.5.0 or higher.
636 r364092 modified the internal ABI used between the kernel NFS
637 modules. As such, all of these modules need to be rebuilt
638 from sources, so a version bump was done.
641 Makefile.inc has been updated to work around the issue documented in
642 20200729. It was a case where the optimization of using symbolic links
643 to point to binaries created a situation where we'd run new binaries
644 with old libraries starting midway through the installworld process.
647 r363679 has redefined some undefined behavior in regcomp(3); notably,
648 extraneous escapes of most ordinary characters will no longer be
649 accepted. An exp-run has identified all of the problems with this in
650 ports, but other non-ports software may need extra escapes removed to
651 continue to function.
653 Because of this change, installworld may encounter the following error
654 from rtld: Undefined symbol "regcomp@FBSD_1.6" -- It is imperative that
655 you do not halt installworld. Instead, let it run to completion (whether
656 successful or not) and run installworld once more.
659 A new implementation of bc and dc has been imported in r362681. This
660 implementation corrects non-conformant behavior of the previous bc
661 and adds GNU bc compatible options. It offers a number of extensions,
662 is much faster on large values, and has support for message catalogs
663 (a number of languages are already supported, contributions of further
664 languages welcome). The option WITHOUT_GH_BC can be used to build the
665 world with the previous versions of bc and dc.
668 r362639 changed the internal API used between the NFS kernel modules.
669 As such, they all need to be rebuilt from sources.
672 r362158 changed the arguments for VFS_CHECKEXP(). As such, any
673 out of tree file systems need to be modified and rebuilt.
674 Also, any file systems that are modules must be rebuilt.
677 read(2) of a directory fd is now rejected by default. root may
678 re-enable it for system root only on non-ZFS filesystems with the
679 security.bsd.allow_read_dir sysctl(8) MIB if
680 security.bsd.suser_enabled=1.
682 It may be advised to setup aliases for grep to default to `-d skip` if
683 commonly non-recursively grepping a list that includes directories and
684 the potential for the resulting stderr output is not tolerable. Example
685 aliases are now installed, commented out, in /root/.cshrc and
689 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
690 been upgraded to 10.0.1. Please see the 20141231 entry below for
691 information about prerequisites and upgrading, if you are not already
692 using clang 3.5.0 or higher.
695 Support for obsolete compilers has been removed from the build system.
696 Clang 6 and GCC 6.4 are the minimum supported versions.
699 closefrom(2) has been moved under COMPAT12, and replaced in libc with a
700 stub that calls close_range(2). If using a custom kernel configuration,
701 you may want to ensure that the COMPAT_FREEBSD12 option is included, as
702 a slightly older -CURRENT userland and older FreeBSD userlands may not
703 be functional without closefrom(2).
706 Upstream DTS from Linux 5.6 was merged and they now have the SID
707 and THS (Secure ID controller and THermal Sensor) node present.
708 The DTB overlays have now been removed from the tree for the H3/H5 and
709 A64 SoCs and the aw_sid and aw_thermal driver have been updated to
710 deal with upstream DTS. If you are using those overlays you need to
711 remove them from loader.conf and update the DTBs on the FAT partition.
714 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
715 been upgraded to 10.0.0. Please see the 20141231 entry below for
716 information about prerequisites and upgrading, if you are not already
717 using clang 3.5.0 or higher.
720 The amd(8) automount daemon has been removed from the source tree.
721 As of FreeBSD 10.1 autofs(5) is the preferred tool for automounting.
722 amd is still available in the sysutils/am-utils port.
725 Removed brooktree driver (bktr.4) from the tree.
728 The WITH_GPL_DTC option has been removed. The BSD-licenced device tree
729 compiler in usr.bin/dtc is used on all architectures which use dtc, and
730 the GPL dtc is available (if needed) from the sysutils/dtc port.
733 The WITHOUT_LLVM_LIBUNWIND option has been removed. LLVM's libunwind
734 is used by all supported CPU architectures.
737 GCC 4.2.1 has been removed from the tree. The WITH_GCC,
738 WITH_GCC_BOOTSTRAP, and WITH_GNUCXX options are no longer available.
739 Users who wish to build FreeBSD with GCC must use the external toolchain
743 ncurses has been updated to a newer version (6.2-20200215). Given the ABI
744 has changed, users will have to rebuild all the ports that are linked to
748 The size of struct vnet and the magic cookie have changed.
749 Users need to recompile libkvm and all modules using VIMAGE
750 together with their new kernel.
753 Defining the long deprecated NO_CTF, NO_DEBUG_FILES, NO_INSTALLLIB,
754 NO_MAN, NO_PROFILE, and NO_WARNS variables is now an error. Update
755 your Makefiles and scripts to define MK_<var>=no instead as required.
757 One exception to this is that program or library Makefiles should
758 define MAN to empty rather than setting MK_MAN=no.
761 Clang/LLVM is now the default compiler and LLD the default
765 make universe no longer uses GCC 4.2.1 on any architectures.
766 Architectures not supported by in-tree Clang/LLVM require an
767 external toolchain package.
770 GCC 4.2.1 is now not built by default, as part of the GCC 4.2.1
771 retirement plan. Specifically, the GCC, GCC_BOOTSTRAP, and GNUCXX
772 options default to off for all supported CPU architectures. As a
773 short-term transition aid they may be enabled via WITH_* options.
774 GCC 4.2.1 is expected to be removed from the tree on 2020-03-31.
777 Support for armv5 has been disconnected and is being removed. The
778 machine combination MACHINE=arm MACHINE_ARCH=arm is no longer valid.
779 You must now use a MACHINE_ARCH of armv6 or armv7. The default
780 MACHINE_ARCH for MACHINE=arm is now armv7.
783 Clang/LLVM is now the default compiler for all powerpc architectures.
784 LLD is now the default linker for powerpc64. The change for powerpc64
785 also includes a change to the ELFv2 ABI, incompatible with the existing
789 Kernel-loadable random(4) modules are no longer unloadable.
792 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
793 been upgraded to 9.0.1. Please see the 20141231 entry below for
794 information about prerequisites and upgrading, if you are not already
795 using clang 3.5.0 or higher.
798 r355677 has modified the internal interface used between the
799 NFS modules in the kernel. As such, they must all be upgraded
800 simultaneously. I will do a version bump for this.
803 The root certificates of the Mozilla CA Certificate Store have been
804 imported into the base system and can be managed with the certctl(8)
805 utility. If you have installed the security/ca_root_nss port or package
806 with the ETCSYMLINK option (the default), be advised that there may be
807 differences between those included in the port and those included in
808 base due to differences in nss branch used as well as general update
809 frequency. Note also that certctl(8) cannot manage certs in the
810 format used by the security/ca_root_nss port.
813 The amd(8) automount daemon has been disabled by default, and will be
814 removed in the future. As of FreeBSD 10.1 the autofs(5) is available
818 The nctgpio and wbwd drivers have been moved to the superio bus.
819 If you have one of these drivers in a kernel configuration, then
820 you should add device superio to it. If you use one of these drivers
821 as a module and you compile a custom set of modules, then you should
822 add superio to the set.
825 KPIs for network drivers to access interface addresses have changed.
826 Users need to recompile NIC driver modules together with kernel.
829 The net.link.tap.user_open sysctl no longer prevents user opening of
830 already created /dev/tapNN devices. Access is still controlled by
831 node permissions, just like tun devices. The net.link.tap.user_open
832 sysctl is now used only to allow users to perform devfs cloning of
833 tap devices, and the subsequent open may not succeed if the user is not
834 in the appropriate group. This sysctl may be deprecated/removed
835 completely in the future.
838 mips, powerpc, and sparc64 are no longer built as part of
839 universe / tinderbox unless MAKE_OBSOLETE_GCC is defined. If
840 not defined, mips, powerpc, and sparc64 builds will look for
841 the xtoolchain binaries and if installed use them for universe
842 builds. As llvm 9.0 becomes vetted for these architectures, they
843 will be removed from the list.
846 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
847 been upgraded to 9.0.0. Please see the 20141231 entry below for
848 information about prerequisites and upgrading, if you are not already
849 using clang 3.5.0 or higher.
852 The hpt27xx, hptmv, hptnr, and hptrr drivers have been removed from
853 GENERIC. They are available as modules and can be loaded by adding
854 to /boot/loader.conf hpt27xx_load="YES", hptmv_load="YES",
855 hptnr_load="YES", or hptrr_load="YES", respectively.
858 ntpd no longer by default locks its pages in memory, allowing them
859 to be paged out by the kernel. Use rlimit memlock to restore
860 historic BSD behaviour. For example, add "rlimit memlock 32"
861 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
864 Several of ping6's options have been renamed for better consistency
865 with ping. If you use any of -ARWXaghmrtwx, you must update your
866 scripts. See ping6(8) for details.
869 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
870 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
871 been removed from mount_fusefs(8). You can safely remove them from
872 your scripts, because they had no effect.
874 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
875 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
876 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
877 sysctls have been removed. If you felt the need to set any of them to
878 a non-default value, please tell asomers@FreeBSD.org why.
881 Default permissions on the /var/account/acct file (and copies of it
882 rotated by periodic daily scripts) are changed from 0644 to 0640
883 because the file contains sensitive information that should not be
884 world-readable. If the /var/account directory must be created by
885 rc.d/accounting, the mode used is now 0750. Admins who use the
886 accounting feature are encouraged to change the mode of an existing
887 /var/account directory to 0750 or 0700.
890 Entropy collection and the /dev/random device are no longer optional
891 components. The "device random" option has been removed.
892 Implementations of distilling algorithms can still be made loadable
893 with "options RANDOM_LOADABLE" (e.g., random_fortuna.ko).
896 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
897 been upgraded to 8.0.1. Please see the 20141231 entry below for
898 information about prerequisites and upgrading, if you are not already
899 using clang 3.5.0 or higher.
902 A fix was applied to i386 kernel modules to avoid panics with
903 dpcpu or vnet. Users need to recompile i386 kernel modules
904 having pcpu or vnet sections or they will refuse to load.
907 User-wired pages now have their own counter,
908 vm.stats.vm.v_user_wire_count. The vm.max_wired sysctl was renamed
909 to vm.max_user_wired and changed from an unsigned int to an unsigned
910 long. bhyve VMs wired with the -S are now subject to the user
911 wiring limit; the vm.max_user_wired sysctl may need to be tuned to
912 avoid running into the limit.
915 The IPSEC option has been removed from GENERIC. Users requiring
916 ipsec(4) must now load the ipsec(4) kernel module.
919 The tap(4) driver has been folded into tun(4), and the module has been
920 renamed to tuntap. You should update any kld_list="if_tap" or
921 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
922 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
923 module instead, and "device tap" or "device tun" entries in kernel
924 config files to select the tuntap device instead.
927 The following knobs have been added related to tradeoffs between
928 safe use of the random device and availability in the absence of
931 kern.random.initial_seeding.bypass_before_seeding: tunable; set
932 non-zero to bypass the random device prior to seeding, or zero to
933 block random requests until the random device is initially seeded.
934 For now, set to 1 (unsafe) by default to restore pre-r346250 boot
935 availability properties.
937 kern.random.initial_seeding.read_random_bypassed_before_seeding:
938 read-only diagnostic sysctl that is set when bypass is enabled and
939 read_random(9) is bypassed, to enable programmatic handling of this
940 initial condition, if desired.
942 kern.random.initial_seeding.arc4random_bypassed_before_seeding:
943 Similar to the above, but for arc4random(9) initial seeding.
945 kern.random.initial_seeding.disable_bypass_warnings: tunable; set
946 non-zero to disable warnings in dmesg when the same conditions are
947 met as for the diagnostic sysctls above. Defaults to zero, i.e.,
948 produce warnings in dmesg when the conditions are met.
951 The loadable random module KPI has changed; the random_infra_init()
952 routine now requires a 3rd function pointer for a bool (*)(void)
953 method that returns true if the random device is seeded (and
954 therefore unblocked).
957 r345895 reverts r320698. This implies that an nfsuserd(8) daemon
958 built from head sources between r320757 (July 6, 2017) and
959 r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
960 is added to the command line.
961 nfsuserd daemons built from head sources that are post-r338192 are
962 not affected and should continue to work.
965 The fuse(4) module has been renamed to fusefs(4) for consistency with
966 other filesystems. You should update any kld_load="fuse" entries in
967 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
968 "options FUSE" entries in kernel config files.
971 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
972 8.0.0. Please see the 20141231 entry below for information about
973 prerequisites and upgrading, if you are not already using clang 3.5.0
977 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
978 compiled into your custom kernel, add 'device xz' statement to the
982 drm and drm2 have been removed from the tree. Please see
983 https://wiki.freebsd.org/Graphics for the latest information on
984 migrating to the drm ports.
987 Iflib is no longer unconditionally compiled into the kernel. Drivers
988 using iflib and statically compiled into the kernel, now require
989 the 'device iflib' config option. For the same drivers loaded as
990 modules on kernels not having 'device iflib', the iflib.ko module
991 is loaded automatically.
994 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
995 options no longer exist since r343219 and r343427 respectively;
996 nothing uses them, so they should be just removed from custom
1000 r342635 changes the way efibootmgr(8) works by requiring users to add
1001 the -b (bootnum) parameter for commands where the bootnum was previously
1002 specified with each option. For example 'efibootmgr -B 0001' is now
1003 'efibootmgr -B -b 0001'.
1006 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
1007 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
1008 servers that have vfs.nfsd.nfs_privport set will only allow mounts
1009 from clients using a reserved port. Since both the FreeBSD and Linux
1010 NFSv4 clients use reserved ports by default, this should not affect
1014 The XLP config has been removed. We can't support 64-bit atomics in this
1015 kernel because it is running in 32-bit mode. XLP users must transition
1016 to running a 64-bit kernel (XLP64 or XLPN32).
1018 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
1019 the preferred emulator today and we don't need two different ones.
1021 The old sibyte / swarm / Broadcom BCM1250 support has been
1022 removed from the mips port.
1025 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
1026 7.0.1. Please see the 20141231 entry below for information about
1027 prerequisites and upgrading, if you are not already using clang 3.5.0
1031 Remove the timed and netdate programs from the base tree. Setting
1032 the time with these daemons has been obsolete for over a decade.
1035 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
1036 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
1037 it produces broken binaries when ifuncs are in use. Users needing
1038 GNU ld should install the binutils port or package.
1041 The BSD crtbegin and crtend code has been enabled by default. It has
1042 had extensive testing on amd64, arm64, and i386. It can be disabled
1043 by building a world with -DWITHOUT_BSD_CRTBEGIN.
1046 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
1047 has been converted to a port (misc/ctm) and will be removed from
1048 FreeBSD-13. It is available as a package (ctm) for all supported
1052 The default newsyslog.conf(5) file has been changed to only include
1053 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
1054 the filenames end in '.conf' and do not begin with a '.'.
1056 You should check the configuration files in these two directories match
1057 this naming convention. You can verify which configuration files are
1058 being included using the command:
1062 Stable/12 was branched created.
1065 Ports for the DRM modules have been simplified. Now, amd64 users should
1066 just install the drm-kmod port. All others should install
1069 Graphics hardware that's newer than about 2010 usually works with
1070 drm-kmod. For hardware older than 2013, however, some users will need
1071 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
1072 than 2008 usually only works in drm-legacy-kmod. The graphics team can
1073 only commit to hardware made since 2013 due to the complexity of the
1074 market and difficulty to test all the older cards effectively. If you
1075 have hardware supported by drm-kmod, you are strongly encouraged to use
1076 that as you will get better support.
1078 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
1079 elsewhere, the drm and drm2 modules will be eliminated from the src base
1080 soon (with a limited exception for arm). Please update to the package
1081 asap and report any issues to x11@freebsd.org.
1083 Generally, anybody using the drm*-kmod packages should add
1084 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
1085 cross-threading surprises, especially with automatic driver
1086 loading from X11 startup. These will become the defaults in 13-current
1090 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
1091 custom kernel and module loading configuration files must be updated
1092 accordingly. Moreover, interfaces previous presented as ixlvN to the
1093 system are now exposed as iavfN and network configuration files must
1094 be adjusted as necessary.
1097 OpenSSL has been updated to version 1.1.1. This update included
1098 additional various API changes throughout the base system. It is
1099 important to rebuild third-party software after upgrading. The value
1100 of __FreeBSD_version has been bumped accordingly.
1103 The legacy DRM modules and drivers have now been added to the loader's
1104 module blacklist, in favor of loading them with kld_list in rc.conf(5).
1105 The module blacklist may be overridden with the loader.conf(5)
1106 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
1110 The cam(4) based nda(4) driver will be used over nvd(4) by default on
1111 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
1112 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
1113 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
1117 Reproducible build mode is now on by default, in preparation for
1118 FreeBSD 12.0. This eliminates build metadata such as the user,
1119 host, and time from the kernel (and uname), unless the working tree
1120 corresponds to a modified checkout from a version control system.
1121 The previous behavior can be obtained by setting the /etc/src.conf
1122 knob WITHOUT_REPRODUCIBLE_BUILD.
1125 The Yarrow CSPRNG has been removed from the kernel as it has not been
1126 supported by its designers since at least 2003. Fortuna has been the
1127 default since FreeBSD-11.
1130 devctl freeze/thaw have gone into the tree, the rc scripts have been
1131 updated to use them and devmatch has been changed. You should update
1132 kernel, userland and rc scripts all at the same time.
1135 The default interpreter has been switched from 4th to Lua.
1136 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
1137 interpreter. If you have custom FORTH code you will need to set
1138 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
1139 src.conf for the build. This will create default hard links between
1140 loader and loader_4th instead of loader and loader_lua, the new default.
1141 If you are using UEFI it will create the proper hard link to loader.efi.
1143 bhyve uses userboot.so. It remains 4th-only until some issues are solved
1144 regarding coexisting with multiple versions of FreeBSD are resolved.
1147 ls(1) now respects the COLORTERM environment variable used in other
1148 systems and software to indicate that a colored terminal is both
1149 supported and desired. If ls(1) is suddenly emitting colors, they may
1150 be disabled again by either removing the unwanted COLORTERM from your
1151 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
1152 may not be observed in a future release.
1155 The default pager for most commands has been changed to "less". To
1156 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
1160 The jedec_ts(4) driver has been removed. A superset of its functionality
1161 is available in the jedec_dimm(4) driver, and the manpage for that
1162 driver includes migration instructions. If you have "device jedec_ts"
1163 in your kernel configuration file, it must be removed.
1166 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
1167 This should have no effect if the kernel is booted via BIOS/legacy boot.
1168 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
1169 has a buggy firmware that prevents a successful boot due to use of
1173 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
1174 support has been removed from the tree. These ports were
1175 obsolete and/or known to be broken for many years.
1178 loader.efi has been augmented to participate more fully in the
1179 UEFI boot manager protocol. loader.efi will now look at the
1180 BootXXXX environment variable to determine if a specific kernel
1181 or root partition was specified. XXXX is derived from BootCurrent.
1182 efibootmgr(8) manages these standard UEFI variables.
1185 zfsloader's functionality has now been folded into loader.
1186 zfsloader is no longer necessary once you've updated your
1187 boot blocks. For a transition period, we will install a
1188 hardlink for zfsloader to loader to allow a smooth transition
1189 until the boot blocks can be updated (hard link because old
1190 zfs boot blocks don't understand symlinks).
1193 ARM64 now have efifb support, if you want to have serial console
1194 on your arm64 board when an screen is connected and the bootloader
1195 setup a frame buffer for us to use, just add :
1198 in /boot/loader.conf
1199 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
1200 an screen connected as the firmware will setup a frame buffer are that
1201 u-boot will expose as an EFI frame buffer.
1204 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
1205 or take steps to update /etc/passwd before doing installworld on
1206 existing systems. Do not skip the "mergemaster -Fp" step before
1207 installworld, as described in the update procedures near the bottom
1208 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
1209 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
1210 the ntp config file contain options that change file/dir locations.
1211 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
1212 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
1213 taking steps to ensure that all required files/dirs are accessible
1217 Big endian arm support has been removed.
1220 The static environment setup in kernel configs is no longer mutually
1221 exclusive with the loader(8) environment by default. In order to
1222 restore the previous default behavior of disabling the loader(8)
1223 environment if a static environment is present, you must specify
1224 loader_env.disabled=1 in the static environment.
1227 The ABI of syscalls used by management tools like sockstat and
1228 netstat has been broken to allow 32-bit binaries to work on
1229 64-bit kernels without modification. These programs will need
1230 to match the kernel in order to function. External programs may
1231 require minor modifications to accommodate a change of type in
1232 structures from pointers to 64-bit virtual addresses.
1235 On i386 and amd64 atomics are now inlined. Out of tree modules using
1236 atomics will need to be rebuilt.
1239 The '%I' format in the kern.corefile sysctl limits the number of
1240 core files that a process can generate to the number stored in the
1241 debug.ncores sysctl. The '%I' format is replaced by the single digit
1242 index. Previously, if all indexes were taken the kernel would overwrite
1243 only a core file with the highest index in a filename.
1244 Currently the system will create a new core file if there is a free
1245 index or if all slots are taken it will overwrite the oldest one.
1248 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
1249 6.0.1. Please see the 20141231 entry below for information about
1250 prerequisites and upgrading, if you are not already using clang 3.5.0
1254 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
1255 needed to be changed to work with it. This change was made with r335763
1256 and requires a mergemaster / etcupdate / etc to update the installed
1260 r334930 changed the interface between the NFS modules, so they all
1261 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
1264 As of r334391 lld is the default amd64 system linker; it is installed
1265 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
1269 The kernel / userland interface for devinfo changed, so you'll
1270 need a new kernel and userland as a pair for it to work (rebuilding
1271 lib/libdevinfo is all that's required). devinfo and devmatch will
1272 not work, but everything else will when there's a mismatch.
1275 The on-disk format for hwpmc callchain records has changed to include
1276 threadid corresponding to a given record. This changes the field offsets
1277 and thus requires that libpmcstat be rebuilt before using a kernel
1281 The vxge(4) driver has been removed. This driver was introduced into
1282 HEAD one week before the Exar left the Ethernet market and is not
1283 known to be used. If you have device vxge in your kernel config file
1287 The amd64 kernel now requires a ld that supports ifunc to produce a
1288 working kernel, either lld or a newer binutils. lld is built by default
1289 on amd64, and the 'buildkernel' target uses it automatically. However,
1290 it is not the default linker, so building the kernel the traditional
1291 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
1292 binutils port/package). lld will soon be default, and this requirement
1295 NOTE: As of r334391 lld is the default system linker on amd64, and no
1296 workaround is necessary.
1299 The nxge(4) driver has been removed. This driver was for PCI-X 10g
1300 cards made by s2io/Neterion. The company was acquired by Exar and
1301 no longer sells or supports Ethernet products. If you have device
1302 nxge in your kernel config file it must be removed.
1305 The tz database (tzdb) has been updated to 2018e. This version more
1306 correctly models time stamps in time zones with negative DST such as
1307 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
1308 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
1309 time zone abbreviations and the tm_isdst flag.
1312 The ixgb(4) driver has been removed. This driver was for an early and
1313 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
1314 quickly shifted to the long lived ixgbe family. If you have device
1315 ixgb in your kernel config file it must be removed.
1318 The lmc(4) driver has been removed. This was a WAN interface
1319 card that was already reportedly rare in 2003, and had an ambiguous
1320 license. If you have device lmc in your kernel config file it must
1324 Support for Arcnet networks has been removed. If you have device
1325 arcnet or device cm in your kernel config file they must be
1329 Support for FDDI networks has been removed. If you have device
1330 fddi or device fpa in your kernel config file they must be
1334 In addition to supporting RFC 3164 formatted messages, the
1335 syslogd(8) service is now capable of parsing RFC 5424 formatted
1336 log messages. The main benefit of using RFC 5424 is that clients
1337 may now send log messages with timestamps containing year numbers,
1338 microseconds and time zone offsets.
1340 Similarly, the syslog(3) C library function has been altered to
1341 send RFC 5424 formatted messages to the local system logging
1342 daemon. On systems using syslogd(8), this change should have no
1343 negative impact, as long as syslogd(8) and the C library are
1344 updated at the same time. On systems using a different system
1345 logging daemon, it may be necessary to make configuration
1346 adjustments, depending on the software used.
1348 When using syslog-ng, add the 'syslog-protocol' flag to local
1349 input sources to enable parsing of RFC 5424 formatted messages:
1352 unix-dgram("/var/run/log" flags(syslog-protocol));
1355 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
1356 of the 'imuxsock' module to let messages be processed by the
1357 regular RFC 3164/5424 parsing pipeline:
1359 module(load="imuxsock" SysSock.UseSpecialParser="off")
1361 Do note that these changes only affect communication between local
1362 applications and syslogd(8). The format that syslogd(8) uses to
1363 store messages on disk or forward messages to other systems
1364 remains unchanged. syslogd(8) still uses RFC 3164 for these
1365 purposes. Options to customize this behaviour will be added in the
1366 future. Utilities that process log files stored in /var/log are
1367 thus expected to continue to function as before.
1369 __FreeBSD_version has been incremented to 1200061 to denote this
1373 Support for token ring networks has been removed. If you
1374 have "device token" in your kernel config you should remove
1375 it. No device drivers supported token ring.
1378 makefs was modified to be able to tag ISO9660 El Torito boot catalog
1379 entries as EFI instead of overloading the i386 tag as done previously.
1380 The amd64 mkisoimages.sh script used to build amd64 ISO images for
1381 release was updated to use this. This may mean that makefs must be
1382 updated before "make cdrom" can be run in the release directory. This
1383 should be as simple as:
1385 $ cd $SRCDIR/usr.sbin/makefs
1386 $ make depend all install
1389 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
1390 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
1391 Co-existence for the transition period will come shortly. Booting is a
1392 complex environment and test coverage for Lua-enabled loaders has been
1393 thin, so it would be prudent to assume it might not work and make
1394 provisions for backup boot methods.
1397 devmatch functionality has been turned on in devd. It will automatically
1398 load drivers for unattached devices. This may cause unexpected drivers
1399 to be loaded. Please report any problems to current@ and
1403 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
1404 6.0.0. Please see the 20141231 entry below for information about
1405 prerequisites and upgrading, if you are not already using clang 3.5.0
1409 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
1410 This means it is used to link the kernel and userland libraries and
1411 executables, but is not yet installed as /usr/bin/ld by default.
1413 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
1414 WITHOUT_LLD_BOOTSTRAP=yes
1417 On i386, pmtimer has been removed. Its functionality has been folded
1418 into apm. It was a no-op on ACPI in current for a while now (but was
1419 still needed on i386 in FreeBSD 11 and earlier). Users may need to
1420 remove it from kernel config files.
1423 The use of RSS hash from the network card aka flowid has been
1424 disabled by default for lagg(4) as it's currently incompatible with
1425 the lacp and loadbalance protocols.
1427 This can be re-enabled by setting the following in loader.conf:
1428 net.link.lagg.default_use_flowid="1"
1431 The SW_WATCHDOG option is no longer necessary to enable the
1432 hardclock-based software watchdog if no hardware watchdog is
1433 configured. As before, SW_WATCHDOG will cause the software
1434 watchdog to be enabled even if a hardware watchdog is configured.
1437 r326887 fixes the issue described in the 20171214 UPDATING entry.
1438 r326888 flips the switch back to building GELI support always.
1441 r362593 broke ZFS + GELI support for reasons unknown. However,
1442 it also broke ZFS support generally, so GELI has been turned off
1443 by default as the lesser evil in r326857. If you boot off ZFS and/or
1444 GELI, it might not be a good time to update.
1447 PowerPC users must update loader(8) by rebuilding world before
1448 installing a new kernel, as the protocol connecting them has
1449 changed. Without the update, loader metadata will not be passed
1450 successfully to the kernel and users will have to enter their
1451 root partition at the kernel mountroot prompt to continue booting.
1452 Newer versions of loader can boot old kernels without issue.
1455 The LOADER_FIREWIRE_SUPPORT build variable has been renamed to
1456 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
1457 to WITH/OUT_LOADER_GELI.
1460 The naive and non-compliant support of posix_fallocate(2) in ZFS
1461 has been removed as of r325320. The system call now returns EINVAL
1462 when used on a ZFS file. Although the new behavior complies with the
1463 standard, some consumers are not prepared to cope with it.
1464 One known victim is lld prior to r325420.
1467 Building in a FreeBSD src checkout will automatically create object
1468 directories now rather than store files in the current directory if
1469 'make obj' was not ran. Calling 'make obj' is no longer necessary.
1470 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
1471 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
1475 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
1476 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
1477 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
1478 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
1479 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
1480 The UNIFIED_OBJDIR option is a transitional feature that will be
1481 removed for 12.0 release; please migrate to the new format for any
1482 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
1483 than hardcoding paths.
1486 The native-xtools target no longer installs the files by default to the
1487 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
1488 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
1491 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
1492 options are changing from controlling the build if defined / undefined
1493 to controlling the build with explicit 'yes' or 'no' values. They will
1494 shift to WITH/WITHOUT options to match other options in the system.
1497 libstand has turned into a private library for sys/boot use only.
1498 It is no longer supported as a public interface outside of sys/boot.
1501 The arm port has split armv6 into armv6 and armv7. armv7 is now
1502 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
1503 and are running a kernel from before r324363, you will need to add
1504 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
1507 When building multiple kernels using KERNCONF, non-existent KERNCONF
1508 files will produce an error and buildkernel will fail. Previously
1509 missing KERNCONF files silently failed giving no indication as to
1510 why, only to subsequently discover during installkernel that the
1511 desired kernel was never built in the first place.
1514 The default serial number format for CTL LUNs has changed. This will
1515 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
1516 or iSCSI clients care about their LUNs' serial numbers. Users who
1517 require serial number stability should hardcode serial numbers in
1521 For 32-bit arm compiled for hard-float support, soft-floating point
1522 binaries now always get their shared libraries from
1523 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
1524 /usr/libsoft also existed). Only users with a hard-float ld.so, but
1525 soft-float everything else should be affected.
1528 The geli password typed at boot is now hidden. To restore the previous
1529 behavior, see geli(8) for configuration options.
1532 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
1533 sysctl values. Minor nit, but requires a rebuild of both world/kernel
1537 "make check" behavior (made in ^/head@r295380) has been changed to
1538 execute from a limited sandbox, as opposed to executing from
1542 - The "beforecheck" and "aftercheck" targets are now specified.
1543 - ${CHECKDIR} (added in commit noted above) has been removed.
1544 - Legacy behavior can be enabled by setting
1545 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
1547 If the limited sandbox mode is enabled, "make check" will execute
1548 "make distribution", then install, execute the tests, and clean up the
1549 sandbox if successful.
1551 The "make distribution" and "make install" targets are typically run as
1552 root to set appropriate permissions and ownership at installation time.
1553 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
1554 environment if executing "make check" with limited sandbox mode using
1555 an unprivileged user.
1558 Since the switch to GPT disk labels, fsck for UFS/FFS has been
1559 unable to automatically find alternate superblocks. As of r322297,
1560 the information needed to find alternate superblocks has been
1561 moved to the end of the area reserved for the boot block.
1562 Filesystems created with a newfs of this vintage or later
1563 will create the recovery information. If you have a filesystem
1564 created prior to this change and wish to have a recovery block
1565 created for your filesystem, you can do so by running fsck in
1566 foreground mode (i.e., do not use the -p or -y options). As it
1567 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
1568 to which you should answer yes.
1571 As of r321665, an NFSv4 server configuration that services
1572 Kerberos mounts or clients that do not support the uid/gid in
1573 owner/owner_group string capability, must explicitly enable
1574 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
1575 machine's /etc/rc.conf file.
1578 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
1579 Please see the 20141231 entry below for information about prerequisites
1580 and upgrading, if you are not already using clang 3.5.0 or higher.
1583 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
1584 r-commands (rlogin, rsh, etc.) to be built with the base system.
1587 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
1588 a very major ABI incompatible change, so users of FreeBSD/powerpc must
1589 be careful when performing source upgrades. It is best to run
1590 'make installworld' from an alternate root system, either a live
1591 CD/memory stick, or a temporary root partition. Additionally, all ports
1592 must be recompiled. powerpc64 is largely unaffected, except in the case
1593 of 32-bit compatibility. All 32-bit binaries will be affected.
1596 Forward compatibility for the "ino64" project have been committed. This
1597 will allow most new binaries to run on older kernels in a limited
1598 fashion. This prevents many of the common foot-shooting actions in the
1599 upgrade as well as the limited ability to roll back the kernel across
1600 the ino64 upgrade. Complicated use cases may not work properly, though
1601 enough simpler ones work to allow recovery in most situations.
1604 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
1605 if you require the GPL compiler.
1608 Forward compatibility for the "ino64" project have been committed. This
1609 will allow most new binaries to run on older kernels in a limited
1610 fashion. This prevents many of the common foot-shooting actions in the
1611 upgrade as well as the limited ability to roll back the kernel across
1612 the ino64 upgrade. Complicated use cases may not work properly, though
1613 enough simpler ones work to allow recovery in most situations.
1616 The internal ABI used for communication between the NFS kernel modules
1617 was changed by r320085, so __FreeBSD_version was bumped to
1618 ensure all the NFS related modules are updated together.
1621 The ABI of struct event was changed by extending the data
1622 member to 64bit and adding ext fields. For upgrade, same
1623 precautions as for the entry 20170523 "ino64" must be
1627 The GNU roff toolchain has been removed from base. To render manpages
1628 which are not supported by mandoc(1), man(1) can fallback on GNU roff
1629 from ports (and recommends to install it).
1630 To render roff(7) documents, consider using GNU roff from ports or the
1631 heirloom doctools roff toolchain from ports via pkg install groff or
1632 via pkg install heirloom-doctools.
1635 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
1636 smaller runtime footprint builds. This is useful for embedded systems
1637 which only require one chipset support.
1639 If you load it as a module, make sure this is in /boot/loader.conf:
1643 This will load the HAL, all chip/RF backends and if_ath_pci.
1644 If you have if_ath_pci in /boot/loader.conf, ensure it is after
1645 if_ath or it will not load any HAL chipset support.
1647 If you want to selectively load things (eg on cheaper ARM/MIPS
1648 platforms where RAM is at a premium) you should:
1651 * load the chip modules in question
1652 * load ath_rate, ath_dfs
1654 * load if_ath_pci and/or if_ath_ahb depending upon your particular
1655 bus bind type - this is where probe/attach is done.
1657 For further comments/feedback, poke adrian@ .
1660 The "ino64" 64-bit inode project has been committed, which extends
1661 a number of types to 64 bits. Upgrading in place requires care and
1662 adherence to the documented upgrade procedure.
1664 If using a custom kernel configuration ensure that the
1665 COMPAT_FREEBSD11 option is included (as during the upgrade the
1666 system will be running the ino64 kernel with the existing world).
1668 For the safest in-place upgrade begin by removing previous build
1669 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full
1670 procedure documented below under the heading "To rebuild everything and
1671 install it on the current system." Specifically, a reboot is required
1672 after installing the new kernel before installing world. While an
1673 installworld normally works by accident from multiuser after rebooting
1674 the proper kernel, there are many cases where this will fail across this
1675 upgrade and installworld from single user is required.
1678 The NATM framework including the en(4), fatm(4), hatm(4), and
1679 patm(4) devices has been removed. Consumers should plan a
1680 migration before the end-of-life date for FreeBSD 11.
1683 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
1684 diff has not been implemented, if those are needed a newer version of
1685 GNU diff is available via the diffutils package under the gdiff name.
1688 As of r316810 for ipfilter, keep frags is no longer assumed when
1689 keep state is specified in a rule. r316810 aligns ipfilter with
1690 documentation in man pages separating keep frags from keep state.
1691 This allows keep state to be specified without forcing keep frags
1692 and allows keep frags to be specified independently of keep state.
1693 To maintain previous behaviour, also specify keep frags with
1694 keep state (as documented in ipf.conf.5).
1697 arm64 builds now use the base system LLD 4.0.0 linker by default,
1698 instead of requiring that the aarch64-binutils port or package be
1699 installed. To continue using aarch64-binutils, set
1700 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
1703 The UDP optimization in entry 20160818 that added the sysctl
1704 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
1705 packets will no longer be treated as L3 broadcast packets.
1708 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
1709 use any explicitly assigned loopback address available in the jail
1710 instead of using the first assigned address of the jail.
1713 The ctl.ko module no longer implements the iSCSI target frontend:
1714 cfiscsi.ko does instead.
1716 If building cfiscsi.ko as a kernel module, the module can be loaded
1717 via one of the following methods:
1718 - `cfiscsi_load="YES"` in loader.conf(5).
1719 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
1720 - ctladm(8)/ctld(8), when compiled with iSCSI support
1721 (`WITH_ISCSI=yes` in src.conf(5))
1723 Please see cfiscsi(4) for more details.
1726 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
1727 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
1728 same source (previously, the dependency of mmcsd.ko on mmc.ko was
1729 missing, but mmcsd.ko now will refuse to load if it is incompatible
1733 The syntax of ipfw(8) named states was changed to avoid ambiguity.
1734 If you have used named states in the firewall rules, you need to modify
1735 them after installworld and before rebooting. Now named states must
1736 be prefixed with colon.
1739 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
1740 removed as the userland we provide cannot use them. The KMS version
1741 (sys/dev/drm2) supports the same hardware.
1744 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
1745 Please see the 20141231 entry below for information about prerequisites
1746 and upgrading, if you are not already using clang 3.5.0 or higher.
1749 The code that provides support for ZFS .zfs/ directory functionality
1750 has been reimplemented. It's not possible now to create a snapshot
1751 by mkdir under .zfs/snapshot/. That should be the only user visible
1755 EISA bus support has been removed. The WITH_EISA option is no longer
1759 MCA bus support has been removed.
1762 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
1763 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
1766 The EM_MULTIQUEUE kernel configuration option is deprecated now that
1767 the em(4) driver conforms to iflib specifications.
1770 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
1771 IFLIB. If you have a custom kernel configuration that excludes em(4)
1772 but you use igb(4), you need to re-add em(4) to your custom
1776 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
1777 Please see the 20141231 entry below for information about prerequisites
1778 and upgrading, if you are not already using clang 3.5.0 or higher.
1781 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
1782 Please see the 20141231 entry below for information about prerequisites
1783 and upgrading, if you are not already using clang 3.5.0 or higher.
1786 The layout of the pmap structure has changed for powerpc to put the pmap
1787 statistics at the front for all CPU variations. libkvm(3) and all tools
1788 that link against it need to be recompiled.
1791 isl(4) and cyapa(4) drivers now require a new driver,
1792 chromebook_platform(4), to work properly on Chromebook-class hardware.
1793 On other types of hardware the drivers may need to be configured using
1794 device hints. Please see the corresponding manual pages for details.
1797 The urtwn(4) driver was merged into rtwn(4) and now consists of
1798 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
1800 Also, firmware for RTL8188CE was renamed due to possible name
1801 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
1804 GNU rcs has been removed from base. It is available as packages:
1805 - rcs: Latest GPLv3 GNU rcs version.
1806 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
1810 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
1811 modules now requires that the kernel configuration contain the
1812 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
1815 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
1816 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
1819 Relocatable object files with the extension of .So have been renamed
1820 to use an extension of .pico instead. The purpose of this change is
1821 to avoid a name clash with shared libraries on case-insensitive file
1822 systems. On those file systems, foo.So is the same file as foo.so.
1825 GNU rcs has been turned off by default. It can (temporarily) be built
1826 again by adding WITH_RCS knob in src.conf.
1827 Otherwise, GNU rcs is available from packages:
1828 - rcs: Latest GPLv3 GNU rcs version.
1829 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
1832 The backup_uses_rcs functionality has been removed from rc.subr.
1835 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
1836 two separate components, QUEUE_MACRO_DEBUG_TRACE and
1837 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
1838 QUEUE_MACRO_DEBUG behavior.
1841 r304787 changed some ioctl interfaces between the iSCSI userspace
1842 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1843 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1847 The UDP receive code has been updated to only treat incoming UDP
1848 packets that were addressed to an L2 broadcast address as L3
1849 broadcast packets. It is not expected that this will affect any
1850 standards-conforming UDP application. The new behaviour can be
1851 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1855 Remove the openbsd_poll system call.
1856 __FreeBSD_version has been bumped because of this.
1859 The stable/11 branch has been created from head@r302406.
1861 After branch N is created, entries older than the N-2 branch point are removed
1862 from this file. After stable/14 is branched and current becomes FreeBSD 15,
1863 entries older than stable/12 branch point will be removed from current's
1870 Sometimes, obscure build problems are the result of environment
1871 poisoning. This can happen because the make utility reads its
1872 environment when searching for values for global variables. To run
1873 your build attempts in an "environmental clean room", prefix all make
1874 commands with 'env -i '. See the env(1) manual page for more details.
1875 Occasionally a build failure will occur with "make -j" due to a race
1876 condition. If this happens try building again without -j, and please
1877 report a bug if it happens consistently.
1879 When upgrading from one major version to another it is generally best to
1880 upgrade to the latest code in the currently installed branch first, then
1881 do an upgrade to the new branch. This is the best-tested upgrade path,
1882 and has the highest probability of being successful. Please try this
1883 approach if you encounter problems with a major version upgrade. Since
1884 the stable 4.x branch point, one has generally been able to upgrade from
1885 anywhere in the most recent stable branch to head / current (or even the
1886 last couple of stable branches). See the top of this file when there's
1889 The update process will emit an error on an attempt to perform a build
1890 or install from a FreeBSD version below the earliest supported version.
1891 When updating from an older version the update should be performed one
1892 major release at a time, including running `make delete-old` at each
1895 When upgrading a live system, having a root shell around before
1896 installing anything can help undo problems. Not having a root shell
1897 around can lead to problems if pam has changed too much from your
1898 starting point to allow continued authentication after the upgrade.
1900 This file should be read as a log of events. When a later event changes
1901 information of a prior event, the prior event should not be deleted.
1902 Instead, a pointer to the entry with the new information should be
1903 placed in the old entry. Readers of this file should also sanity check
1904 older entries before relying on them blindly. Authors of new entries
1905 should write them with this in mind.
1909 When upgrading the boot ZFS pool to a new version (via zpool upgrade),
1910 always follow these three steps:
1912 1) recompile and reinstall the ZFS boot loader and boot block
1913 (this is part of "make buildworld" and "make installworld")
1915 2) update the ZFS boot block on your boot drive (only required when
1916 doing a zpool upgrade):
1918 When booting on x86 via BIOS, use the following to update the ZFS boot
1919 block on the freebsd-boot partition of a GPT partitioned drive ada0:
1920 gpart bootcode -p /boot/gptzfsboot -i $N ada0
1921 The value $N will typically be 1. For EFI booting, see EFI notes.
1923 3) zpool upgrade the root pool. New bootblocks will work with old
1924 pools, but not vice versa, so they need to be updated before any
1927 Non-boot pools do not need these updates.
1932 There are two locations the boot loader can be installed into. The
1933 current location (and the default) is \efi\freebsd\loader.efi and using
1934 efibootmgr(8) to configure it. The old location, that must be used on
1935 deficient systems that don't honor efibootmgr(8) protocols, is the
1936 fallback location of \EFI\BOOT\BOOTxxx.EFI. Generally, you will copy
1937 /boot/loader.efi to this location, but on systems installed a long time
1938 ago the ESP may be too small and /boot/boot1.efi may be needed unless
1939 the ESP has been expanded in the meantime.
1941 Recent systems will have the ESP mounted on /boot/efi, but older ones
1942 may not have it mounted at all, or mounted in a different
1943 location. Older arm SD images with MBR used /boot/msdos as the
1944 mountpoint. The ESP is a MSDOS filesystem.
1946 The EFI boot loader rarely needs to be updated. For ZFS booting,
1947 however, you must update loader.efi before you do 'zpool upgrade' the
1948 root zpool, otherwise the old loader.efi may reject the upgraded zpool
1949 since it does not automatically understand some new features.
1951 See loader.efi(8) and uefi(8) for more details.
1955 If you are updating from a prior version of FreeBSD (even one just
1956 a few days old), you should follow this procedure. It is the most
1957 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1959 make kernel-toolchain
1960 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1961 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1963 To test a kernel once
1964 ---------------------
1965 If you just want to boot a kernel once (because you are not sure
1966 if it works, or if you want to boot a known bad kernel to provide
1967 debugging information) run
1968 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1969 nextboot -k testkernel
1971 To rebuild everything and install it on the current system.
1972 -----------------------------------------------------------
1973 # Note: sometimes if you are running current you gotta do more than
1974 # is listed here if you are upgrading from a really old current.
1976 <make sure you have good level 0 dumps>
1978 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1979 make installkernel KERNCONF=YOUR_KERNEL_HERE
1981 <reboot in single user> [3]
1988 To cross-install current onto a separate partition
1989 --------------------------------------------------
1990 # In this approach we use a separate partition to hold
1991 # current's root, 'usr', and 'var' directories. A partition
1992 # holding "/", "/usr" and "/var" should be about 2GB in
1995 <make sure you have good level 0 dumps>
1998 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1999 <maybe newfs current's root partition>
2000 <mount current's root partition on directory ${CURRENT_ROOT}>
2001 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
2002 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2003 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2004 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2005 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2006 <reboot into current>
2007 <do a "native" rebuild/install as described in the previous section>
2008 <maybe install compatibility libraries from ports/misc/compat*>
2012 To upgrade in-place from stable to current
2013 ----------------------------------------------
2014 <make sure you have good level 0 dumps>
2016 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
2017 make installkernel KERNCONF=YOUR_KERNEL_HERE
2019 <reboot in single user> [3]
2026 Make sure that you've read the UPDATING file to understand the
2027 tweaks to various things you need. At this point in the life
2028 cycle of current, things change often and you are on your own
2029 to cope. The defaults can also change, so please read ALL of
2030 the UPDATING entries.
2032 Also, if you are tracking -current, you must be subscribed to
2033 freebsd-current@freebsd.org. Make sure that before you update
2034 your sources that you have read and understood all the recent
2035 messages there. If in doubt, please track -stable which has
2036 much fewer pitfalls.
2038 [1] If you have third party modules, such as vmware, you should disable
2039 them at this point so they don't crash your system on
2040 reboot. Alternatively, you should rebuild all the modules you have in
2041 your system and install them as well. If you are running -current, you
2042 should seriously consider placing all sources to all the modules for
2043 your system (or symlinks to them) in /usr/local/sys/modules so this
2044 happens automatically. If all your modules come from ports, then adding
2045 the port origin directories to PORTS_MODULES instead is also automatic
2047 PORTS_MODULES+=x11/nvidia-driver
2049 [3] From the bootblocks, boot -s, and then do
2053 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed
2054 cd src # full path to source
2055 adjkerntz -i # if CMOS is wall time
2056 Also, when doing a major release upgrade, it is required that you boot
2057 into single user mode to do the installworld.
2059 [4] Note: This step is non-optional. Failure to do this step
2060 can result in a significant reduction in the functionality of the
2061 system. Attempting to do it by hand is not recommended and those
2062 that pursue this avenue should read this file carefully, as well
2063 as the archives of freebsd-current and freebsd-hackers mailing lists
2064 for potential gotchas. See etcupdate(8) for more information.
2066 [5] Usually this step is a no-op. However, from time to time
2067 you may need to do this if you get unknown user in the following
2070 [6] This only deletes old files and directories. Old libraries
2071 can be deleted by "make delete-old-libs", but you have to make
2072 sure that no program is using those libraries anymore.
2074 [8] The new kernel must be able to run existing binaries used by an
2075 installworld. When upgrading across major versions, the new kernel's
2076 configuration must include the correct COMPAT_FREEBSD<n> option for
2077 existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure
2078 to do so may leave you with a system that is hard to boot to recover. A
2079 GENERIC kernel will include suitable compatibility options to run
2080 binaries from older branches. Note that the ability to run binaries
2081 from unsupported branches is not guaranteed.
2083 Make sure that you merge any new devices from GENERIC since the
2084 last time you updated your kernel config file. Options also
2085 change over time, so you may need to adjust your custom kernels
2088 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2089 "?=" instead of the "=" assignment operator, so that buildworld can
2090 override the CPUTYPE if it needs to.
2092 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2093 not on the command line, or in /etc/make.conf. buildworld will
2094 warn if it is improperly defined.
2097 This file contains a list, in reverse chronological order, of major
2098 breakages in tracking -current. It is not guaranteed to be a complete
2099 list of such breakages, and only contains entries since September 23, 2011.
2100 If you need to see UPDATING entries from before that date, you will need
2101 to fetch an UPDATING file from an older FreeBSD release.
2103 Copyright information:
2105 Copyright 1998-2009 M. Warner Losh <imp@FreeBSD.org>
2107 Redistribution, publication, translation and use, with or without
2108 modification, in full or in part, in any form or format of this
2109 document are permitted without further permission from the author.
2111 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2112 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2113 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2114 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2115 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2116 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2117 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2118 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2119 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2120 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2121 POSSIBILITY OF SUCH DAMAGE.
2123 Contact Warner Losh if you have any questions about your use of