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 If you have an arm64 system that uses ACPI, you will need to update your
32 loader.efi in the ESP when you update past this point. Detection of ACPI
33 was moved earlier in the binary so the scripts could use it, but old
34 binaries don't have this, so we default to 'no ACPI' in this case.
37 The WITHOUT_LLD_IS_LD option has been removed. When LLD is enabled
38 it is always installed as /usr/bin/ld.
41 Forward compatibility (running the new code on old kernels) for the
42 "ino64" project have been removed. The need for it has passed long ago.
45 Commit 57ce37f9dcd0 changed the internal KAPI between the
46 nfscommon and nfscl modules. Both must be rebuilt from sources.
49 dialog(1) has been replaced in base by bsddialog(1), while most of the
50 time replacing a dialog(1) call by a bsddialog(1) call works out of the
51 box, bsddialog(1) is not considered as a drop-in replacement for
54 If you do depend on dialog(1) functionality, please install cdialog
60 The EARLY_AP_STARTUP kernel option is mandatory on x86. The option
61 has been added to DEFAULTS, so it should automatically be included in
62 custom kernel configurations without any additional change.
65 A new loader tunable net.pf.default_to_drop allows pf(4)’s default
66 behaviour to be changed from pass to drop. Previously this required
67 recompiling the kernel with the option PF_DEFAULT_TO_DROP.
70 Enable splitting out pkgbase manpages into separate packages by
71 default. To disable this, set WITHOUT_MANSPLITPKG=yes in src.conf.
74 Move standard include files to the clibs-dev package and move clang
75 internal libraries and headers to clang and clang-dev. Upgrading systems
76 installed using pkgbase past this change involves extra steps to allow
79 pkg upgrade -y FreeBSD-utilities
80 pkg upgrade -y FreeBSD-utilities-dev
84 Enable vnet sysctl variables to be loader tunable. SYSCTLs which
85 belongs to VNETs can be initialized during early boot or module
86 loading if they are marked with CTLFLAG_TUN and there are
87 corresponding kernel environment variables.
90 The WITH_INIT_ALL_PATTERN and WITH_INIT_ALL_ZERO build options have
91 been replaced by INIT_ALL=pattern and INIT_ALL=zero respectively.
97 Serial communication (in boot loaders, kernel, and userland) has
98 been changed to default to 115200 bps, in line with common industry
99 practice and typcial firmware serial console redirection
102 Note that the early x86 BIOS bootloader (i.e., boot0sio) does not
103 support rates above 9600 bps and is not changed. boot0sio users may
104 set BOOT_COMCONSOLE_SPEED=9600 to use 9600 for all of the boot
105 components, or use the standard boot0 and have the boot2 stage start
106 with the serial port at 115200.
109 Following the general removal of MIPS support, the ath(4) AHB bus-
110 frontend has been removed, too, and building of the PCI support is
111 integrated with the ath(4) main module again. As a result, there's
112 no longer a need for if_ath_pci_load="YES" in /boot/loader.conf or
113 "device ath_pci" in the kernel configuration.
116 MAXCPU has been increased to 1024 in the amd64 GENERIC kernel config.
117 Out-of-tree kernel modules will need to be rebuilt.
120 CAM has been mechanically updated s/u_int(64|32|16|8)_t/uint\1_t/g
121 to move to the standard uintXX_t types from the old, traditional
122 BSD u_intXX_t types. This should be a NOP, but may cause problems
123 for out of tree changes. The SIMs were not updated since most of
124 the old u_intXX_t uses weren't due to CAM interfaces.
127 stable/14 branch created.
130 The heuristic for detecting old chromebooks with an EC bug that requires
131 atkbdc driver workarounds has changed. There should be no functional
132 change, but if your old chromebook's keyboard stops working, please
133 file a PR and assign it to imp.
136 OpenSSL has been updated to version 3.0, including changes throughout
137 the base system. It is important to rebuild third-party software
141 To enable pf rdr rules for connections initiated from the host, pf
142 filter rules can be optionally enabled for packets delivered
143 locally. This can change the behavior of rules which match packets
144 delivered to lo0. To enable this feature:
146 sysctl net.pf.filter_local=1
149 When enabled, its best to ensure that packets delivered locally are not
150 filtered, e.g. by adding a 'skip on lo' rule.
153 Improvements to libtacplus(8) mean that tacplus.conf(5) now
154 follows POSIX shell syntax rules. This may cause TACACS+
155 authentication to fail if the shared secret contains a single
156 quote, double quote, or backslash character which isn't
157 already properly quoted or escaped.
160 Belatedly switch the default nvme block device on x86 from nvd to nda.
161 nda created nvd compatibility links by default, so this should be a
162 nop. If this causes problems for your application, set hw.nvme.use_nvd=1
163 in your loader.conf or add `options NVME_USE_NVD=1` to your kernel
164 config. To disable the nvd compatibility aliases, add
165 kern.cam.nda.nvd_compat=0 to loader.conf. The default has been nda on
166 all non-x86 platforms for some time now. If you need to fall back,
167 please email imp@freebsd.org about why.
169 Encrypted swap partitions need to be changed from nvd to nda if you
170 migrate, or you need to use the above to switch back to nvd.
173 Remove portsnap(8). Users are encouraged to obtain the ports tree
177 Add jobs.mk to save typing. Enables -j${JOB_MAX} and logging
181 make -j${JOB_MAX} buildworld > ../buildworld.log 2>&1
183 where JOB_MAX is derrived from ncpus in local.sys.mk if not set in env.
186 Video related devices for some arm devices have been renamed.
187 If you have a custom kernel config and want to use hdmi output on
188 IMX6 board you need to add "device dwc_hdmi" "device imx6_hdmi" and
189 "device imx6_ipu" to it.
190 If you have a custom kernel config and want to use hdmi output on
191 TI AM335X board you need to add "device tda19988" to it.
192 If you add "device hdmi" in it you need to remove it as it doesn't
196 Introduce new kernel options KBD_DELAY1 and KBD_DELAY2. See atkbdc(4)
200 sshd now defaults to having X11Forwarding disabled, following upstream.
201 Administrators who wish to enable X11Forwarding should add
202 `X11Forwarding yes` to /etc/ssh/sshd_config.
205 Since commit 75d41cb6967 Huawei 3G/4G LTE Mobile Devices do not default
206 to ECM, but NCM mode and need u3g and ucom modules loaded. See cdce(4).
209 As of commit 7c40e2d5f685, the dependency on netlink(4) has been added
210 to the linux_common(4) module. Users relying on linux_common may need
211 to complile netlink(4) module if it is not present in their kernel.
214 The WITHOUT_CXX option has been removed. C++ components in the base
215 system are now built unconditionally.
218 LinuxKPI pci.h changes may require out-of-tree drivers to be recompiled.
219 Bump _FreeBSD_version to 1400078 to be able to detect this change.
222 llvm-objump is now always installed as objdump. Previously there was
223 no /usr/bin/objdump unless the WITH_LLVM_BINUTILS knob was used.
225 Some LLVM objdump options have a different output format compared to
226 GNU objdump; readelf is available for inspecting ELF files, and GNU
227 objdump is available from the devel/binutils port or package.
230 dma(8) has replaced sendmail(8) as the default mta. For people willing
231 to reenable sendmail(8):
233 $ cp /usr/share/examples/sendmail/mailer.conf /etc/mail/mailer.conf
235 and add sendmail_enable="YES" to rc.conf.
238 hw.bus.disable_failed_devices has changed from 'false' to 'true' by
239 default. Now if newbus succeeds in probing a device, but fails to attach
240 the device, we'll disable the device. In the past, we'd keep retrying
241 the device on each new driver loaded. To get that behavior now, one
242 needs to use devctl to re-enable the device, and reprobe it (or set
243 the sysctl/tunable hw.bus.disable_failed_devices=false).
245 NOTE: This was reverted 20221205 due to unexpected compatibility issues
248 pf no longer accepts 'scrub fragment crop' or 'scrub fragment drop-ovl'.
249 These configurations are no longer automatically reinterpreted as
250 'scrub fragment reassemble'.
253 The WITHOUT_CLANG_IS_CC option has been removed. When Clang is enabled
254 it is always installed as /usr/bin/cc (and c++, cpp).
257 Some programs have been moved into separate packages. It is recommended
258 for pkgbase users to do:
260 pkg install FreeBSD-dhclient FreeBSD-geom FreeBSD-resolvconf \
261 FreeBSD-devd FreeBSD-devmatch
263 after upgrading to restore all the component that were previously
267 OPIE has been removed from the base system. If needed, it can
268 be installed from ports (security/opie) or packages (opie).
269 Otherwise, make sure that your PAM policies do not reference
270 pam_opie or pam_opieaccess.
273 LinuxKPI pm.h changes require an update to the latest drm-kmod version
274 before re-compiling to avoid errors.
277 The macros provided for the manipulation of CPU sets (e.g. CPU_AND)
278 have been modified to take 2 source arguments instead of only 1.
279 Externally maintained sources that use these macros will have to
280 be adapted. The FreeBSD version has been bumped to 1400046 to
284 A number of the kernel include files are able to be included by
285 themselves. A test has been added to buildworld to enforce this.
288 Remove mips as a recognized target. This starts the decommissioning of
289 mips support in FreeBSD. mips related items will be removed wholesale in
290 the coming days and weeks.
292 This broke the NO_CLEAN build for some people. Either do a clean build
294 lib/clang/include/llvm/Config/Targets.def
295 lib/clang/include/llvm/Config/AsmParsers.def
296 lib/clang/include/llvm/Config/Disassemblers.def
297 lib/clang/include/llvm/Config/AsmPrinters.def
298 before the build to force everything to rebuild that needs to.
301 Unbound support for RFC8375: The special-use domain 'home.arpa' is
302 by default blocked. To unblock it use a local-zone nodefault
303 statement in unbound.conf:
304 local-zone: "home.arpa." nodefault
306 Or use another type of local-zone to override with your choice.
308 The reason for this is discussed in Section 6.1 of RFC8375:
309 Because 'home.arpa.' is not globally scoped and cannot be secured
310 using DNSSEC based on the root domain's trust anchor, there is no way
311 to tell, using a standard DNS query, in which homenet scope an answer
312 belongs. Consequently, users may experience surprising results with
313 such names when roaming to different homenets.
316 Commit b8d60729deef changed the TCP congestion control framework so
317 that any of the included congestion control modules could be
318 the single module built into the kernel. Previously newreno
319 was automatically built in through direct reference. As of
320 this commit you are required to declare at least one congestion
321 control module (e.g. 'options CC_NEWRENO') and to also declare a
322 default using the CC_DEFAULT option (e.g. options CC_DEFAULT="newreno\").
323 The GENERIC configuration includes CC_NEWRENO and defines newreno
324 as the default. If no congestion control option is built into the
325 kernel and you are including networking, the kernel compile will
326 fail. Also if no default is declared the kernel compile will fail.
329 Mips has been removed from universe builds. It will be removed from the
333 Commit f0c9847a6c47 changed the arguments for VOP_ALLOCATE.
334 The NFS modules must be rebuilt from sources and any out
335 of tree file systems that implement their own VOP_ALLOCATE
336 may need to be modified.
339 The synchronous PPP kernel driver sppp(4) has been removed.
340 The cp(4) and ce(4) drivers are now always compiled with netgraph(4)
341 support, formerly enabled by NETGRAPH_CRONYX option.
344 sh(1) is now the default shell for the root user. To force root to use
345 the csh shell, please run the following command as root:
350 Ncurses distribution has been split between libtinfow and libncurses
351 with libncurses.so becoming a linker (ld) script to seamlessly link
352 to libtinfow as needed. Bump _FreeBSD_version to 1400035 to reflect
356 As of commit 8160a0f62be6, the dummynet module no longer depends on the
357 ipfw module. Dummynet can now be used by pf as well as ipfw. As such
358 users who relied on this dependency may need to include ipfw in the
359 list of modules to load on their systems.
362 As of commit 903873ce1560, the mixer(8) utility has got a slightly
363 new syntax. Please refer to the mixer(8) manual page for more
364 information. The old mixer utility can be installed from ports:
365 audio/freebsd-13-mixer
368 As of commit 55089ef4f8bb, the global variable nfs_maxcopyrange has
369 been deleted from the nfscommon.ko. As such, nfsd.ko must be built
370 from up to date sources to avoid an undefined reference when
374 As of commit 62ca9fc1ad56 OpenSSL no longer enables kernel TLS
375 by default. Users can enable kernel TLS via the "KTLS" SSL
376 option. This can be enabled globally by using a custom
377 OpenSSL config file via OPENSSL_CONF or via an
378 application-specific configuration option for applications
379 which permit setting SSL options via SSL_CONF_cmd(3).
382 Commit 3ad1e1c1ce20 changed the internal KAPI between the NFS
383 modules. Therefore, all need to be rebuilt from sources.
386 Commit b69019c14cd8 removes pf's DIOCGETSTATESNV ioctl.
387 As of be70c7a50d32 it is no longer used by userspace, but it does mean
388 users may not be able to enumerate pf states if they update the kernel
389 past b69019c14cd8 without first updating userspace past be70c7a50d32.
392 As of commit 01ad0c007964 if_bridge member interfaces can no longer
393 change their MTU. Changing the MTU of the bridge itself will change the
394 MTU on all member interfaces instead.
397 Commit ee29e6f31111 changed the internal KAPI between the nfscommon
398 and nfsd modules. Therefore, both need to be rebuilt from sources.
399 Bump __FreeBSD_version to 1400026 for this KAPI change.
402 The 20210707 awk update brought in a change in behavior. This has
403 been corrected as of d4d252c49976. Between these dates, if you
404 installed a new awk binary, you may not be able to build a new
405 kernel because the change in behavior affected the genoffset
406 script used to build the kernel. If you did update, the fix is
407 to update your sources past the above hash and do
410 % sudo -E make install
411 to enable building kernels again.
414 Commit 1e0a518d6548 changed the internal KAPI between the NFS
415 modules. They all need to be rebuilt from sources. I did not
416 bump __FreeBSD_version, since it was bumped recently.
419 awk has been updated to the latest one-true-awk version 20210215.
420 This contains a number of minor bug fixes.
423 The NFSv4 client now uses the highest minor version of NFSv4
424 supported by the NFSv4 server by default instead of minor version 0,
426 The "minorversion" mount option may be used to override this default.
429 Bump __FreeBSD_version to 1400024 for LinuxKPI changes.
430 Most notably netdev.h can change now as the (last) dependencies
431 (mlx4/ofed) are now using struct ifnet directly, but also for PCI
432 additions and others.
435 The directory "blacklisted" under /usr/share/certs/ has been
436 renamed to "untrusted".
439 svnlite has been removed from base. Should you need svn for any reason
440 please install the svn package or port.
443 Commit e1a907a25cfa changed the internal KAPI between the krpc
444 and nfsserver. As such, both modules must be rebuilt from
445 sources. Bump __FreeBSD_version to 1400022.
448 The an(4) driver has been removed from FreeBSD.
451 The vendor/openzfs branch was renamed to vendor/openzfs/legacy to
452 start tracking OpenZFS upstream more closely. Please see
453 https://lists.freebsd.org/archives/freebsd-current/2021-June/000153.html
454 for details on how to correct any errors that might result. The
455 short version is that you need to remove the old branch locally:
456 git update-ref -d refs/remotes/freebsd/vendor/openzfs
457 (assuming your upstream origin is named 'freebsd').
460 Commits 17accc08ae15 and de102f870501 add new files to LinuxKPI
461 which break drm-kmod. In addition various other additions where
462 committed. Bump __FreeBSD_version to 1400015 to be able to
466 Commit ca179c4d74f2 changed the package in which the OpenSSL
467 libraries and utilities are packaged.
468 It is recommended for pkgbase user to do:
469 pkg install -f FreeBSD-openssl
470 before pkg upgrade otherwise some dependencies might not be met
471 and pkg will stop working as libssl will not be present anymore
475 Commit 875977314881 changed the internal KAPI between
476 the nfsd and nfscommon modules. As such these modules
477 need to be rebuilt from sources.
478 Without this patch in your NFSv4.1/4.2 server, enabling
479 delegations by setting vfs.nfsd.issue_delegations non-zero
483 Commit 7763814fc9c2 changed the internal KAPI between
484 the krpc and NFS. As such, the krpc, nfscommon and
485 nfscl modules must all be rebuilt from sources.
486 Without this patch, NFSv4.1/4.2 mounts should not
487 be done with the nfscbd(8) daemon running, to avoid
488 needing a working back channel for server->client RPCs.
491 Commit 01ae8969a9ee fixed the NFSv4.1/4.2 server so that it
492 handles binding of the back channel as required by RFC5661.
493 Until this patch is in your server, avoid use of the "nconnects"
494 mount option for Linux NFSv4.1/4.2 mounts.
497 For 64-bit architectures the base system is now built with Position
498 Independent Executable (PIE) support enabled by default. It may be
499 disabled using the WITHOUT_PIE knob. A clean build is required.
502 Various LinuxKPI functionality was added which conflicts with DRM.
503 Please update your drm-kmod port to after the __FreeBSD_version 1400003
507 stable/13 branch created.
510 PC Card attachments for all devices have been removed. In the case of
511 wi and cmx, the entire drivers were removed because they were only
512 PC Card devices. FreeBSD_version 1300134 should be used for this
513 since it was bumped so recently.
516 Transport-independent parts of HID support have been split off the USB
517 code in to separate subsystem. Kernel configs which include one of
518 ums, ukbd, uhid, atp, wsp, wmt, uaudio, ugold or ucycom drivers should
519 be updated with adding of "device hid" line.
522 ncurses installation has been modified to only keep the widechar
523 enabled version. Incremental build is broken for that change, so it
524 requires a clean build.
527 The FreeBSD project has migrated from Subversion to Git. Temporary
528 instructions can be found at
529 https://github.com/bsdimp/freebsd-git-docs/blob/main/src-cvt.md
530 and other documents in that repo.
533 The services database has been updated to cover more of the basic
534 services expected in a modern system. The database is big enough
535 that it will cause issues in mergemaster in Releases previous to
536 12.2 and 11.3, or in very old current systems from before r358154.
539 Obsolete in-tree GDB 6.1.1 has been removed. GDB (including kgdb)
540 may be installed from ports or packages.
543 ping6 has been merged into ping. It can now be called as "ping -6".
544 See ping(8) for details.
547 Default value of net.add_addr_allfibs has been changed to 0.
548 If you have multi-fib configuration and rely on existence of all
549 interface routes in every fib, you need to set the above sysctl to 1.
552 The internal pre-processor in the calendar(1) program has been
553 extended to support more C pre-processor commands (e.g. #ifdef, #else,
554 and #undef) and to detect unbalanced conditional statements.
555 Error messages have been extended to include the filename and line
556 number if processing stops to help fixing malformed data files.
559 All the data files for the calendar(1) program, except calendar.freebsd,
560 have been moved to the deskutils/calendar-data port, much like the
561 jewish calendar entries were moved to deskutils/hebcal years ago. After
562 make delete-old-files, you need to install it to retain full
563 functionality. calendar(1) will issue a reminder for files it can't
567 LINT files are no longer generated. We now include the relevant NOTES
568 files. Note: This may cause conflicts with updating in some cases.
569 find sys -name LINT\* -delete
570 is suggested across this commit to remove the generated LINT files.
572 If you have tried to update with generated files there, the svn
573 command you want to un-auger the tree is
576 and then do the above find from the top level. Substitute 'amd64'
577 above with where the error message indicates a conflict.
580 OpenZFS support has been integrated. Do not upgrade root pools until
581 the loader is updated to support zstd. Furthermore, we caution against
582 'zpool upgrade' for the next few weeks. The change should be transparent
583 unless you want to use new features.
585 Not all "NO_CLEAN" build scenarios work across these changes. Many
586 scenarios have been tested and fixed, but rebuilding kernels without
587 rebuilding world may fail.
589 The ZFS cache file has moved from /boot to /etc to match the OpenZFS
590 upstream default. A fallback to /boot has been added for mountroot.
592 Pool auto import behavior at boot has been moved from the kernel module
593 to an explicit "zpool import -a" in one of the rc scripts enabled by
594 zfs_enable=YES. This means your non-root zpools won't auto import until
595 you upgrade your /etc/rc.d files.
598 The resume code now notifies devd with the 'kernel' system
599 rather than the old 'kern' subsystem to be consistent with
600 other use. The old notification will be created as well, but
601 will be removed prior to FreeBSD 14.0.
604 r362275 changed the internal API between the kernel RPC and the
605 NFS modules. As such, all the modules must be recompiled from
609 r364330 modified the internal API used between the NFS modules.
610 As such, all the NFS modules must be re-compiled from sources.
613 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
614 been upgraded to 11.0.0. Please see the 20141231 entry below for
615 information about prerequisites and upgrading, if you are not already
616 using clang 3.5.0 or higher.
619 r364092 modified the internal ABI used between the kernel NFS
620 modules. As such, all of these modules need to be rebuilt
621 from sources, so a version bump was done.
624 Makefile.inc has been updated to work around the issue documented in
625 20200729. It was a case where the optimization of using symbolic links
626 to point to binaries created a situation where we'd run new binaries
627 with old libraries starting midway through the installworld process.
630 r363679 has redefined some undefined behavior in regcomp(3); notably,
631 extraneous escapes of most ordinary characters will no longer be
632 accepted. An exp-run has identified all of the problems with this in
633 ports, but other non-ports software may need extra escapes removed to
634 continue to function.
636 Because of this change, installworld may encounter the following error
637 from rtld: Undefined symbol "regcomp@FBSD_1.6" -- It is imperative that
638 you do not halt installworld. Instead, let it run to completion (whether
639 successful or not) and run installworld once more.
642 A new implementation of bc and dc has been imported in r362681. This
643 implementation corrects non-conformant behavior of the previous bc
644 and adds GNU bc compatible options. It offers a number of extensions,
645 is much faster on large values, and has support for message catalogs
646 (a number of languages are already supported, contributions of further
647 languages welcome). The option WITHOUT_GH_BC can be used to build the
648 world with the previous versions of bc and dc.
651 r362639 changed the internal API used between the NFS kernel modules.
652 As such, they all need to be rebuilt from sources.
655 r362158 changed the arguments for VFS_CHECKEXP(). As such, any
656 out of tree file systems need to be modified and rebuilt.
657 Also, any file systems that are modules must be rebuilt.
660 read(2) of a directory fd is now rejected by default. root may
661 re-enable it for system root only on non-ZFS filesystems with the
662 security.bsd.allow_read_dir sysctl(8) MIB if
663 security.bsd.suser_enabled=1.
665 It may be advised to setup aliases for grep to default to `-d skip` if
666 commonly non-recursively grepping a list that includes directories and
667 the potential for the resulting stderr output is not tolerable. Example
668 aliases are now installed, commented out, in /root/.cshrc and
672 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
673 been upgraded to 10.0.1. Please see the 20141231 entry below for
674 information about prerequisites and upgrading, if you are not already
675 using clang 3.5.0 or higher.
678 Support for obsolete compilers has been removed from the build system.
679 Clang 6 and GCC 6.4 are the minimum supported versions.
682 closefrom(2) has been moved under COMPAT12, and replaced in libc with a
683 stub that calls close_range(2). If using a custom kernel configuration,
684 you may want to ensure that the COMPAT_FREEBSD12 option is included, as
685 a slightly older -CURRENT userland and older FreeBSD userlands may not
686 be functional without closefrom(2).
689 Upstream DTS from Linux 5.6 was merged and they now have the SID
690 and THS (Secure ID controller and THermal Sensor) node present.
691 The DTB overlays have now been removed from the tree for the H3/H5 and
692 A64 SoCs and the aw_sid and aw_thermal driver have been updated to
693 deal with upstream DTS. If you are using those overlays you need to
694 remove them from loader.conf and update the DTBs on the FAT partition.
697 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
698 been upgraded to 10.0.0. Please see the 20141231 entry below for
699 information about prerequisites and upgrading, if you are not already
700 using clang 3.5.0 or higher.
703 The amd(8) automount daemon has been removed from the source tree.
704 As of FreeBSD 10.1 autofs(5) is the preferred tool for automounting.
705 amd is still available in the sysutils/am-utils port.
708 Removed brooktree driver (bktr.4) from the tree.
711 The WITH_GPL_DTC option has been removed. The BSD-licenced device tree
712 compiler in usr.bin/dtc is used on all architectures which use dtc, and
713 the GPL dtc is available (if needed) from the sysutils/dtc port.
716 The WITHOUT_LLVM_LIBUNWIND option has been removed. LLVM's libunwind
717 is used by all supported CPU architectures.
720 GCC 4.2.1 has been removed from the tree. The WITH_GCC,
721 WITH_GCC_BOOTSTRAP, and WITH_GNUCXX options are no longer available.
722 Users who wish to build FreeBSD with GCC must use the external toolchain
726 ncurses has been updated to a newer version (6.2-20200215). Given the ABI
727 has changed, users will have to rebuild all the ports that are linked to
731 The size of struct vnet and the magic cookie have changed.
732 Users need to recompile libkvm and all modules using VIMAGE
733 together with their new kernel.
736 Defining the long deprecated NO_CTF, NO_DEBUG_FILES, NO_INSTALLLIB,
737 NO_MAN, NO_PROFILE, and NO_WARNS variables is now an error. Update
738 your Makefiles and scripts to define MK_<var>=no instead as required.
740 One exception to this is that program or library Makefiles should
741 define MAN to empty rather than setting MK_MAN=no.
744 Clang/LLVM is now the default compiler and LLD the default
748 make universe no longer uses GCC 4.2.1 on any architectures.
749 Architectures not supported by in-tree Clang/LLVM require an
750 external toolchain package.
753 GCC 4.2.1 is now not built by default, as part of the GCC 4.2.1
754 retirement plan. Specifically, the GCC, GCC_BOOTSTRAP, and GNUCXX
755 options default to off for all supported CPU architectures. As a
756 short-term transition aid they may be enabled via WITH_* options.
757 GCC 4.2.1 is expected to be removed from the tree on 2020-03-31.
760 Support for armv5 has been disconnected and is being removed. The
761 machine combination MACHINE=arm MACHINE_ARCH=arm is no longer valid.
762 You must now use a MACHINE_ARCH of armv6 or armv7. The default
763 MACHINE_ARCH for MACHINE=arm is now armv7.
766 Clang/LLVM is now the default compiler for all powerpc architectures.
767 LLD is now the default linker for powerpc64. The change for powerpc64
768 also includes a change to the ELFv2 ABI, incompatible with the existing
772 Kernel-loadable random(4) modules are no longer unloadable.
775 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
776 been upgraded to 9.0.1. Please see the 20141231 entry below for
777 information about prerequisites and upgrading, if you are not already
778 using clang 3.5.0 or higher.
781 r355677 has modified the internal interface used between the
782 NFS modules in the kernel. As such, they must all be upgraded
783 simultaneously. I will do a version bump for this.
786 The root certificates of the Mozilla CA Certificate Store have been
787 imported into the base system and can be managed with the certctl(8)
788 utility. If you have installed the security/ca_root_nss port or package
789 with the ETCSYMLINK option (the default), be advised that there may be
790 differences between those included in the port and those included in
791 base due to differences in nss branch used as well as general update
792 frequency. Note also that certctl(8) cannot manage certs in the
793 format used by the security/ca_root_nss port.
796 The amd(8) automount daemon has been disabled by default, and will be
797 removed in the future. As of FreeBSD 10.1 the autofs(5) is available
801 The nctgpio and wbwd drivers have been moved to the superio bus.
802 If you have one of these drivers in a kernel configuration, then
803 you should add device superio to it. If you use one of these drivers
804 as a module and you compile a custom set of modules, then you should
805 add superio to the set.
808 KPIs for network drivers to access interface addresses have changed.
809 Users need to recompile NIC driver modules together with kernel.
812 The net.link.tap.user_open sysctl no longer prevents user opening of
813 already created /dev/tapNN devices. Access is still controlled by
814 node permissions, just like tun devices. The net.link.tap.user_open
815 sysctl is now used only to allow users to perform devfs cloning of
816 tap devices, and the subsequent open may not succeed if the user is not
817 in the appropriate group. This sysctl may be deprecated/removed
818 completely in the future.
821 mips, powerpc, and sparc64 are no longer built as part of
822 universe / tinderbox unless MAKE_OBSOLETE_GCC is defined. If
823 not defined, mips, powerpc, and sparc64 builds will look for
824 the xtoolchain binaries and if installed use them for universe
825 builds. As llvm 9.0 becomes vetted for these architectures, they
826 will be removed from the list.
829 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
830 been upgraded to 9.0.0. Please see the 20141231 entry below for
831 information about prerequisites and upgrading, if you are not already
832 using clang 3.5.0 or higher.
835 The hpt27xx, hptmv, hptnr, and hptrr drivers have been removed from
836 GENERIC. They are available as modules and can be loaded by adding
837 to /boot/loader.conf hpt27xx_load="YES", hptmv_load="YES",
838 hptnr_load="YES", or hptrr_load="YES", respectively.
841 ntpd no longer by default locks its pages in memory, allowing them
842 to be paged out by the kernel. Use rlimit memlock to restore
843 historic BSD behaviour. For example, add "rlimit memlock 32"
844 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
847 Several of ping6's options have been renamed for better consistency
848 with ping. If you use any of -ARWXaghmrtwx, you must update your
849 scripts. See ping6(8) for details.
852 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
853 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
854 been removed from mount_fusefs(8). You can safely remove them from
855 your scripts, because they had no effect.
857 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
858 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
859 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
860 sysctls have been removed. If you felt the need to set any of them to
861 a non-default value, please tell asomers@FreeBSD.org why.
864 Default permissions on the /var/account/acct file (and copies of it
865 rotated by periodic daily scripts) are changed from 0644 to 0640
866 because the file contains sensitive information that should not be
867 world-readable. If the /var/account directory must be created by
868 rc.d/accounting, the mode used is now 0750. Admins who use the
869 accounting feature are encouraged to change the mode of an existing
870 /var/account directory to 0750 or 0700.
873 Entropy collection and the /dev/random device are no longer optional
874 components. The "device random" option has been removed.
875 Implementations of distilling algorithms can still be made loadable
876 with "options RANDOM_LOADABLE" (e.g., random_fortuna.ko).
879 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
880 been upgraded to 8.0.1. Please see the 20141231 entry below for
881 information about prerequisites and upgrading, if you are not already
882 using clang 3.5.0 or higher.
885 A fix was applied to i386 kernel modules to avoid panics with
886 dpcpu or vnet. Users need to recompile i386 kernel modules
887 having pcpu or vnet sections or they will refuse to load.
890 User-wired pages now have their own counter,
891 vm.stats.vm.v_user_wire_count. The vm.max_wired sysctl was renamed
892 to vm.max_user_wired and changed from an unsigned int to an unsigned
893 long. bhyve VMs wired with the -S are now subject to the user
894 wiring limit; the vm.max_user_wired sysctl may need to be tuned to
895 avoid running into the limit.
898 The IPSEC option has been removed from GENERIC. Users requiring
899 ipsec(4) must now load the ipsec(4) kernel module.
902 The tap(4) driver has been folded into tun(4), and the module has been
903 renamed to tuntap. You should update any kld_list="if_tap" or
904 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
905 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
906 module instead, and "device tap" or "device tun" entries in kernel
907 config files to select the tuntap device instead.
910 The following knobs have been added related to tradeoffs between
911 safe use of the random device and availability in the absence of
914 kern.random.initial_seeding.bypass_before_seeding: tunable; set
915 non-zero to bypass the random device prior to seeding, or zero to
916 block random requests until the random device is initially seeded.
917 For now, set to 1 (unsafe) by default to restore pre-r346250 boot
918 availability properties.
920 kern.random.initial_seeding.read_random_bypassed_before_seeding:
921 read-only diagnostic sysctl that is set when bypass is enabled and
922 read_random(9) is bypassed, to enable programmatic handling of this
923 initial condition, if desired.
925 kern.random.initial_seeding.arc4random_bypassed_before_seeding:
926 Similar to the above, but for arc4random(9) initial seeding.
928 kern.random.initial_seeding.disable_bypass_warnings: tunable; set
929 non-zero to disable warnings in dmesg when the same conditions are
930 met as for the diagnostic sysctls above. Defaults to zero, i.e.,
931 produce warnings in dmesg when the conditions are met.
934 The loadable random module KPI has changed; the random_infra_init()
935 routine now requires a 3rd function pointer for a bool (*)(void)
936 method that returns true if the random device is seeded (and
937 therefore unblocked).
940 r345895 reverts r320698. This implies that an nfsuserd(8) daemon
941 built from head sources between r320757 (July 6, 2017) and
942 r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
943 is added to the command line.
944 nfsuserd daemons built from head sources that are post-r338192 are
945 not affected and should continue to work.
948 The fuse(4) module has been renamed to fusefs(4) for consistency with
949 other filesystems. You should update any kld_load="fuse" entries in
950 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
951 "options FUSE" entries in kernel config files.
954 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
955 8.0.0. Please see the 20141231 entry below for information about
956 prerequisites and upgrading, if you are not already using clang 3.5.0
960 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
961 compiled into your custom kernel, add 'device xz' statement to the
965 drm and drm2 have been removed from the tree. Please see
966 https://wiki.freebsd.org/Graphics for the latest information on
967 migrating to the drm ports.
970 Iflib is no longer unconditionally compiled into the kernel. Drivers
971 using iflib and statically compiled into the kernel, now require
972 the 'device iflib' config option. For the same drivers loaded as
973 modules on kernels not having 'device iflib', the iflib.ko module
974 is loaded automatically.
977 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
978 options no longer exist since r343219 and r343427 respectively;
979 nothing uses them, so they should be just removed from custom
983 r342635 changes the way efibootmgr(8) works by requiring users to add
984 the -b (bootnum) parameter for commands where the bootnum was previously
985 specified with each option. For example 'efibootmgr -B 0001' is now
986 'efibootmgr -B -b 0001'.
989 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
990 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
991 servers that have vfs.nfsd.nfs_privport set will only allow mounts
992 from clients using a reserved port. Since both the FreeBSD and Linux
993 NFSv4 clients use reserved ports by default, this should not affect
997 The XLP config has been removed. We can't support 64-bit atomics in this
998 kernel because it is running in 32-bit mode. XLP users must transition
999 to running a 64-bit kernel (XLP64 or XLPN32).
1001 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
1002 the preferred emulator today and we don't need two different ones.
1004 The old sibyte / swarm / Broadcom BCM1250 support has been
1005 removed from the mips port.
1008 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
1009 7.0.1. Please see the 20141231 entry below for information about
1010 prerequisites and upgrading, if you are not already using clang 3.5.0
1014 Remove the timed and netdate programs from the base tree. Setting
1015 the time with these daemons has been obsolete for over a decade.
1018 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
1019 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
1020 it produces broken binaries when ifuncs are in use. Users needing
1021 GNU ld should install the binutils port or package.
1024 The BSD crtbegin and crtend code has been enabled by default. It has
1025 had extensive testing on amd64, arm64, and i386. It can be disabled
1026 by building a world with -DWITHOUT_BSD_CRTBEGIN.
1029 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
1030 has been converted to a port (misc/ctm) and will be removed from
1031 FreeBSD-13. It is available as a package (ctm) for all supported
1035 The default newsyslog.conf(5) file has been changed to only include
1036 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
1037 the filenames end in '.conf' and do not begin with a '.'.
1039 You should check the configuration files in these two directories match
1040 this naming convention. You can verify which configuration files are
1041 being included using the command:
1045 Stable/12 was branched created.
1048 Ports for the DRM modules have been simplified. Now, amd64 users should
1049 just install the drm-kmod port. All others should install
1052 Graphics hardware that's newer than about 2010 usually works with
1053 drm-kmod. For hardware older than 2013, however, some users will need
1054 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
1055 than 2008 usually only works in drm-legacy-kmod. The graphics team can
1056 only commit to hardware made since 2013 due to the complexity of the
1057 market and difficulty to test all the older cards effectively. If you
1058 have hardware supported by drm-kmod, you are strongly encouraged to use
1059 that as you will get better support.
1061 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
1062 elsewhere, the drm and drm2 modules will be eliminated from the src base
1063 soon (with a limited exception for arm). Please update to the package
1064 asap and report any issues to x11@freebsd.org.
1066 Generally, anybody using the drm*-kmod packages should add
1067 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
1068 cross-threading surprises, especially with automatic driver
1069 loading from X11 startup. These will become the defaults in 13-current
1073 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
1074 custom kernel and module loading configuration files must be updated
1075 accordingly. Moreover, interfaces previous presented as ixlvN to the
1076 system are now exposed as iavfN and network configuration files must
1077 be adjusted as necessary.
1080 OpenSSL has been updated to version 1.1.1. This update included
1081 additional various API changes throughout the base system. It is
1082 important to rebuild third-party software after upgrading. The value
1083 of __FreeBSD_version has been bumped accordingly.
1086 The legacy DRM modules and drivers have now been added to the loader's
1087 module blacklist, in favor of loading them with kld_list in rc.conf(5).
1088 The module blacklist may be overridden with the loader.conf(5)
1089 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
1093 The cam(4) based nda(4) driver will be used over nvd(4) by default on
1094 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
1095 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
1096 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
1100 Reproducible build mode is now on by default, in preparation for
1101 FreeBSD 12.0. This eliminates build metadata such as the user,
1102 host, and time from the kernel (and uname), unless the working tree
1103 corresponds to a modified checkout from a version control system.
1104 The previous behavior can be obtained by setting the /etc/src.conf
1105 knob WITHOUT_REPRODUCIBLE_BUILD.
1108 The Yarrow CSPRNG has been removed from the kernel as it has not been
1109 supported by its designers since at least 2003. Fortuna has been the
1110 default since FreeBSD-11.
1113 devctl freeze/thaw have gone into the tree, the rc scripts have been
1114 updated to use them and devmatch has been changed. You should update
1115 kernel, userland and rc scripts all at the same time.
1118 The default interpreter has been switched from 4th to Lua.
1119 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
1120 interpreter. If you have custom FORTH code you will need to set
1121 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
1122 src.conf for the build. This will create default hard links between
1123 loader and loader_4th instead of loader and loader_lua, the new default.
1124 If you are using UEFI it will create the proper hard link to loader.efi.
1126 bhyve uses userboot.so. It remains 4th-only until some issues are solved
1127 regarding coexisting with multiple versions of FreeBSD are resolved.
1130 ls(1) now respects the COLORTERM environment variable used in other
1131 systems and software to indicate that a colored terminal is both
1132 supported and desired. If ls(1) is suddenly emitting colors, they may
1133 be disabled again by either removing the unwanted COLORTERM from your
1134 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
1135 may not be observed in a future release.
1138 The default pager for most commands has been changed to "less". To
1139 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
1143 The jedec_ts(4) driver has been removed. A superset of its functionality
1144 is available in the jedec_dimm(4) driver, and the manpage for that
1145 driver includes migration instructions. If you have "device jedec_ts"
1146 in your kernel configuration file, it must be removed.
1149 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
1150 This should have no effect if the kernel is booted via BIOS/legacy boot.
1151 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
1152 has a buggy firmware that prevents a successful boot due to use of
1156 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
1157 support has been removed from the tree. These ports were
1158 obsolete and/or known to be broken for many years.
1161 loader.efi has been augmented to participate more fully in the
1162 UEFI boot manager protocol. loader.efi will now look at the
1163 BootXXXX environment variable to determine if a specific kernel
1164 or root partition was specified. XXXX is derived from BootCurrent.
1165 efibootmgr(8) manages these standard UEFI variables.
1168 zfsloader's functionality has now been folded into loader.
1169 zfsloader is no longer necessary once you've updated your
1170 boot blocks. For a transition period, we will install a
1171 hardlink for zfsloader to loader to allow a smooth transition
1172 until the boot blocks can be updated (hard link because old
1173 zfs boot blocks don't understand symlinks).
1176 ARM64 now have efifb support, if you want to have serial console
1177 on your arm64 board when an screen is connected and the bootloader
1178 setup a frame buffer for us to use, just add :
1181 in /boot/loader.conf
1182 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
1183 an screen connected as the firmware will setup a frame buffer are that
1184 u-boot will expose as an EFI frame buffer.
1187 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
1188 or take steps to update /etc/passwd before doing installworld on
1189 existing systems. Do not skip the "mergemaster -Fp" step before
1190 installworld, as described in the update procedures near the bottom
1191 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
1192 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
1193 the ntp config file contain options that change file/dir locations.
1194 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
1195 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
1196 taking steps to ensure that all required files/dirs are accessible
1200 Big endian arm support has been removed.
1203 The static environment setup in kernel configs is no longer mutually
1204 exclusive with the loader(8) environment by default. In order to
1205 restore the previous default behavior of disabling the loader(8)
1206 environment if a static environment is present, you must specify
1207 loader_env.disabled=1 in the static environment.
1210 The ABI of syscalls used by management tools like sockstat and
1211 netstat has been broken to allow 32-bit binaries to work on
1212 64-bit kernels without modification. These programs will need
1213 to match the kernel in order to function. External programs may
1214 require minor modifications to accommodate a change of type in
1215 structures from pointers to 64-bit virtual addresses.
1218 On i386 and amd64 atomics are now inlined. Out of tree modules using
1219 atomics will need to be rebuilt.
1222 The '%I' format in the kern.corefile sysctl limits the number of
1223 core files that a process can generate to the number stored in the
1224 debug.ncores sysctl. The '%I' format is replaced by the single digit
1225 index. Previously, if all indexes were taken the kernel would overwrite
1226 only a core file with the highest index in a filename.
1227 Currently the system will create a new core file if there is a free
1228 index or if all slots are taken it will overwrite the oldest one.
1231 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
1232 6.0.1. Please see the 20141231 entry below for information about
1233 prerequisites and upgrading, if you are not already using clang 3.5.0
1237 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
1238 needed to be changed to work with it. This change was made with r335763
1239 and requires a mergemaster / etcupdate / etc to update the installed
1243 r334930 changed the interface between the NFS modules, so they all
1244 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
1247 As of r334391 lld is the default amd64 system linker; it is installed
1248 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
1252 The kernel / userland interface for devinfo changed, so you'll
1253 need a new kernel and userland as a pair for it to work (rebuilding
1254 lib/libdevinfo is all that's required). devinfo and devmatch will
1255 not work, but everything else will when there's a mismatch.
1258 The on-disk format for hwpmc callchain records has changed to include
1259 threadid corresponding to a given record. This changes the field offsets
1260 and thus requires that libpmcstat be rebuilt before using a kernel
1264 The vxge(4) driver has been removed. This driver was introduced into
1265 HEAD one week before the Exar left the Ethernet market and is not
1266 known to be used. If you have device vxge in your kernel config file
1270 The amd64 kernel now requires a ld that supports ifunc to produce a
1271 working kernel, either lld or a newer binutils. lld is built by default
1272 on amd64, and the 'buildkernel' target uses it automatically. However,
1273 it is not the default linker, so building the kernel the traditional
1274 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
1275 binutils port/package). lld will soon be default, and this requirement
1278 NOTE: As of r334391 lld is the default system linker on amd64, and no
1279 workaround is necessary.
1282 The nxge(4) driver has been removed. This driver was for PCI-X 10g
1283 cards made by s2io/Neterion. The company was acquired by Exar and
1284 no longer sells or supports Ethernet products. If you have device
1285 nxge in your kernel config file it must be removed.
1288 The tz database (tzdb) has been updated to 2018e. This version more
1289 correctly models time stamps in time zones with negative DST such as
1290 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
1291 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
1292 time zone abbreviations and the tm_isdst flag.
1295 The ixgb(4) driver has been removed. This driver was for an early and
1296 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
1297 quickly shifted to the long lived ixgbe family. If you have device
1298 ixgb in your kernel config file it must be removed.
1301 The lmc(4) driver has been removed. This was a WAN interface
1302 card that was already reportedly rare in 2003, and had an ambiguous
1303 license. If you have device lmc in your kernel config file it must
1307 Support for Arcnet networks has been removed. If you have device
1308 arcnet or device cm in your kernel config file they must be
1312 Support for FDDI networks has been removed. If you have device
1313 fddi or device fpa in your kernel config file they must be
1317 In addition to supporting RFC 3164 formatted messages, the
1318 syslogd(8) service is now capable of parsing RFC 5424 formatted
1319 log messages. The main benefit of using RFC 5424 is that clients
1320 may now send log messages with timestamps containing year numbers,
1321 microseconds and time zone offsets.
1323 Similarly, the syslog(3) C library function has been altered to
1324 send RFC 5424 formatted messages to the local system logging
1325 daemon. On systems using syslogd(8), this change should have no
1326 negative impact, as long as syslogd(8) and the C library are
1327 updated at the same time. On systems using a different system
1328 logging daemon, it may be necessary to make configuration
1329 adjustments, depending on the software used.
1331 When using syslog-ng, add the 'syslog-protocol' flag to local
1332 input sources to enable parsing of RFC 5424 formatted messages:
1335 unix-dgram("/var/run/log" flags(syslog-protocol));
1338 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
1339 of the 'imuxsock' module to let messages be processed by the
1340 regular RFC 3164/5424 parsing pipeline:
1342 module(load="imuxsock" SysSock.UseSpecialParser="off")
1344 Do note that these changes only affect communication between local
1345 applications and syslogd(8). The format that syslogd(8) uses to
1346 store messages on disk or forward messages to other systems
1347 remains unchanged. syslogd(8) still uses RFC 3164 for these
1348 purposes. Options to customize this behaviour will be added in the
1349 future. Utilities that process log files stored in /var/log are
1350 thus expected to continue to function as before.
1352 __FreeBSD_version has been incremented to 1200061 to denote this
1356 Support for token ring networks has been removed. If you
1357 have "device token" in your kernel config you should remove
1358 it. No device drivers supported token ring.
1361 makefs was modified to be able to tag ISO9660 El Torito boot catalog
1362 entries as EFI instead of overloading the i386 tag as done previously.
1363 The amd64 mkisoimages.sh script used to build amd64 ISO images for
1364 release was updated to use this. This may mean that makefs must be
1365 updated before "make cdrom" can be run in the release directory. This
1366 should be as simple as:
1368 $ cd $SRCDIR/usr.sbin/makefs
1369 $ make depend all install
1372 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
1373 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
1374 Co-existence for the transition period will come shortly. Booting is a
1375 complex environment and test coverage for Lua-enabled loaders has been
1376 thin, so it would be prudent to assume it might not work and make
1377 provisions for backup boot methods.
1380 devmatch functionality has been turned on in devd. It will automatically
1381 load drivers for unattached devices. This may cause unexpected drivers
1382 to be loaded. Please report any problems to current@ and
1386 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
1387 6.0.0. Please see the 20141231 entry below for information about
1388 prerequisites and upgrading, if you are not already using clang 3.5.0
1392 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
1393 This means it is used to link the kernel and userland libraries and
1394 executables, but is not yet installed as /usr/bin/ld by default.
1396 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
1397 WITHOUT_LLD_BOOTSTRAP=yes
1400 On i386, pmtimer has been removed. Its functionality has been folded
1401 into apm. It was a no-op on ACPI in current for a while now (but was
1402 still needed on i386 in FreeBSD 11 and earlier). Users may need to
1403 remove it from kernel config files.
1406 The use of RSS hash from the network card aka flowid has been
1407 disabled by default for lagg(4) as it's currently incompatible with
1408 the lacp and loadbalance protocols.
1410 This can be re-enabled by setting the following in loader.conf:
1411 net.link.lagg.default_use_flowid="1"
1414 The SW_WATCHDOG option is no longer necessary to enable the
1415 hardclock-based software watchdog if no hardware watchdog is
1416 configured. As before, SW_WATCHDOG will cause the software
1417 watchdog to be enabled even if a hardware watchdog is configured.
1420 r326887 fixes the issue described in the 20171214 UPDATING entry.
1421 r326888 flips the switch back to building GELI support always.
1424 r362593 broke ZFS + GELI support for reasons unknown. However,
1425 it also broke ZFS support generally, so GELI has been turned off
1426 by default as the lesser evil in r326857. If you boot off ZFS and/or
1427 GELI, it might not be a good time to update.
1430 PowerPC users must update loader(8) by rebuilding world before
1431 installing a new kernel, as the protocol connecting them has
1432 changed. Without the update, loader metadata will not be passed
1433 successfully to the kernel and users will have to enter their
1434 root partition at the kernel mountroot prompt to continue booting.
1435 Newer versions of loader can boot old kernels without issue.
1438 The LOADER_FIREWIRE_SUPPORT build variable has been renamed to
1439 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
1440 to WITH/OUT_LOADER_GELI.
1443 The naive and non-compliant support of posix_fallocate(2) in ZFS
1444 has been removed as of r325320. The system call now returns EINVAL
1445 when used on a ZFS file. Although the new behavior complies with the
1446 standard, some consumers are not prepared to cope with it.
1447 One known victim is lld prior to r325420.
1450 Building in a FreeBSD src checkout will automatically create object
1451 directories now rather than store files in the current directory if
1452 'make obj' was not ran. Calling 'make obj' is no longer necessary.
1453 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
1454 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
1458 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
1459 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
1460 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
1461 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
1462 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
1463 The UNIFIED_OBJDIR option is a transitional feature that will be
1464 removed for 12.0 release; please migrate to the new format for any
1465 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
1466 than hardcoding paths.
1469 The native-xtools target no longer installs the files by default to the
1470 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
1471 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
1474 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
1475 options are changing from controlling the build if defined / undefined
1476 to controlling the build with explicit 'yes' or 'no' values. They will
1477 shift to WITH/WITHOUT options to match other options in the system.
1480 libstand has turned into a private library for sys/boot use only.
1481 It is no longer supported as a public interface outside of sys/boot.
1484 The arm port has split armv6 into armv6 and armv7. armv7 is now
1485 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
1486 and are running a kernel from before r324363, you will need to add
1487 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
1490 When building multiple kernels using KERNCONF, non-existent KERNCONF
1491 files will produce an error and buildkernel will fail. Previously
1492 missing KERNCONF files silently failed giving no indication as to
1493 why, only to subsequently discover during installkernel that the
1494 desired kernel was never built in the first place.
1497 The default serial number format for CTL LUNs has changed. This will
1498 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
1499 or iSCSI clients care about their LUNs' serial numbers. Users who
1500 require serial number stability should hardcode serial numbers in
1504 For 32-bit arm compiled for hard-float support, soft-floating point
1505 binaries now always get their shared libraries from
1506 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
1507 /usr/libsoft also existed). Only users with a hard-float ld.so, but
1508 soft-float everything else should be affected.
1511 The geli password typed at boot is now hidden. To restore the previous
1512 behavior, see geli(8) for configuration options.
1515 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
1516 sysctl values. Minor nit, but requires a rebuild of both world/kernel
1520 "make check" behavior (made in ^/head@r295380) has been changed to
1521 execute from a limited sandbox, as opposed to executing from
1525 - The "beforecheck" and "aftercheck" targets are now specified.
1526 - ${CHECKDIR} (added in commit noted above) has been removed.
1527 - Legacy behavior can be enabled by setting
1528 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
1530 If the limited sandbox mode is enabled, "make check" will execute
1531 "make distribution", then install, execute the tests, and clean up the
1532 sandbox if successful.
1534 The "make distribution" and "make install" targets are typically run as
1535 root to set appropriate permissions and ownership at installation time.
1536 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
1537 environment if executing "make check" with limited sandbox mode using
1538 an unprivileged user.
1541 Since the switch to GPT disk labels, fsck for UFS/FFS has been
1542 unable to automatically find alternate superblocks. As of r322297,
1543 the information needed to find alternate superblocks has been
1544 moved to the end of the area reserved for the boot block.
1545 Filesystems created with a newfs of this vintage or later
1546 will create the recovery information. If you have a filesystem
1547 created prior to this change and wish to have a recovery block
1548 created for your filesystem, you can do so by running fsck in
1549 foreground mode (i.e., do not use the -p or -y options). As it
1550 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
1551 to which you should answer yes.
1554 As of r321665, an NFSv4 server configuration that services
1555 Kerberos mounts or clients that do not support the uid/gid in
1556 owner/owner_group string capability, must explicitly enable
1557 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
1558 machine's /etc/rc.conf file.
1561 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
1562 Please see the 20141231 entry below for information about prerequisites
1563 and upgrading, if you are not already using clang 3.5.0 or higher.
1566 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
1567 r-commands (rlogin, rsh, etc.) to be built with the base system.
1570 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
1571 a very major ABI incompatible change, so users of FreeBSD/powerpc must
1572 be careful when performing source upgrades. It is best to run
1573 'make installworld' from an alternate root system, either a live
1574 CD/memory stick, or a temporary root partition. Additionally, all ports
1575 must be recompiled. powerpc64 is largely unaffected, except in the case
1576 of 32-bit compatibility. All 32-bit binaries will be affected.
1579 Forward compatibility for the "ino64" project have been committed. This
1580 will allow most new binaries to run on older kernels in a limited
1581 fashion. This prevents many of the common foot-shooting actions in the
1582 upgrade as well as the limited ability to roll back the kernel across
1583 the ino64 upgrade. Complicated use cases may not work properly, though
1584 enough simpler ones work to allow recovery in most situations.
1587 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
1588 if you require the GPL compiler.
1591 Forward compatibility for the "ino64" project have been committed. This
1592 will allow most new binaries to run on older kernels in a limited
1593 fashion. This prevents many of the common foot-shooting actions in the
1594 upgrade as well as the limited ability to roll back the kernel across
1595 the ino64 upgrade. Complicated use cases may not work properly, though
1596 enough simpler ones work to allow recovery in most situations.
1599 The internal ABI used for communication between the NFS kernel modules
1600 was changed by r320085, so __FreeBSD_version was bumped to
1601 ensure all the NFS related modules are updated together.
1604 The ABI of struct event was changed by extending the data
1605 member to 64bit and adding ext fields. For upgrade, same
1606 precautions as for the entry 20170523 "ino64" must be
1610 The GNU roff toolchain has been removed from base. To render manpages
1611 which are not supported by mandoc(1), man(1) can fallback on GNU roff
1612 from ports (and recommends to install it).
1613 To render roff(7) documents, consider using GNU roff from ports or the
1614 heirloom doctools roff toolchain from ports via pkg install groff or
1615 via pkg install heirloom-doctools.
1618 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
1619 smaller runtime footprint builds. This is useful for embedded systems
1620 which only require one chipset support.
1622 If you load it as a module, make sure this is in /boot/loader.conf:
1626 This will load the HAL, all chip/RF backends and if_ath_pci.
1627 If you have if_ath_pci in /boot/loader.conf, ensure it is after
1628 if_ath or it will not load any HAL chipset support.
1630 If you want to selectively load things (eg on cheaper ARM/MIPS
1631 platforms where RAM is at a premium) you should:
1634 * load the chip modules in question
1635 * load ath_rate, ath_dfs
1637 * load if_ath_pci and/or if_ath_ahb depending upon your particular
1638 bus bind type - this is where probe/attach is done.
1640 For further comments/feedback, poke adrian@ .
1643 The "ino64" 64-bit inode project has been committed, which extends
1644 a number of types to 64 bits. Upgrading in place requires care and
1645 adherence to the documented upgrade procedure.
1647 If using a custom kernel configuration ensure that the
1648 COMPAT_FREEBSD11 option is included (as during the upgrade the
1649 system will be running the ino64 kernel with the existing world).
1651 For the safest in-place upgrade begin by removing previous build
1652 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full
1653 procedure documented below under the heading "To rebuild everything and
1654 install it on the current system." Specifically, a reboot is required
1655 after installing the new kernel before installing world. While an
1656 installworld normally works by accident from multiuser after rebooting
1657 the proper kernel, there are many cases where this will fail across this
1658 upgrade and installworld from single user is required.
1661 The NATM framework including the en(4), fatm(4), hatm(4), and
1662 patm(4) devices has been removed. Consumers should plan a
1663 migration before the end-of-life date for FreeBSD 11.
1666 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
1667 diff has not been implemented, if those are needed a newer version of
1668 GNU diff is available via the diffutils package under the gdiff name.
1671 As of r316810 for ipfilter, keep frags is no longer assumed when
1672 keep state is specified in a rule. r316810 aligns ipfilter with
1673 documentation in man pages separating keep frags from keep state.
1674 This allows keep state to be specified without forcing keep frags
1675 and allows keep frags to be specified independently of keep state.
1676 To maintain previous behaviour, also specify keep frags with
1677 keep state (as documented in ipf.conf.5).
1680 arm64 builds now use the base system LLD 4.0.0 linker by default,
1681 instead of requiring that the aarch64-binutils port or package be
1682 installed. To continue using aarch64-binutils, set
1683 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
1686 The UDP optimization in entry 20160818 that added the sysctl
1687 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
1688 packets will no longer be treated as L3 broadcast packets.
1691 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
1692 use any explicitly assigned loopback address available in the jail
1693 instead of using the first assigned address of the jail.
1696 The ctl.ko module no longer implements the iSCSI target frontend:
1697 cfiscsi.ko does instead.
1699 If building cfiscsi.ko as a kernel module, the module can be loaded
1700 via one of the following methods:
1701 - `cfiscsi_load="YES"` in loader.conf(5).
1702 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
1703 - ctladm(8)/ctld(8), when compiled with iSCSI support
1704 (`WITH_ISCSI=yes` in src.conf(5))
1706 Please see cfiscsi(4) for more details.
1709 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
1710 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
1711 same source (previously, the dependency of mmcsd.ko on mmc.ko was
1712 missing, but mmcsd.ko now will refuse to load if it is incompatible
1716 The syntax of ipfw(8) named states was changed to avoid ambiguity.
1717 If you have used named states in the firewall rules, you need to modify
1718 them after installworld and before rebooting. Now named states must
1719 be prefixed with colon.
1722 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
1723 removed as the userland we provide cannot use them. The KMS version
1724 (sys/dev/drm2) supports the same hardware.
1727 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
1728 Please see the 20141231 entry below for information about prerequisites
1729 and upgrading, if you are not already using clang 3.5.0 or higher.
1732 The code that provides support for ZFS .zfs/ directory functionality
1733 has been reimplemented. It's not possible now to create a snapshot
1734 by mkdir under .zfs/snapshot/. That should be the only user visible
1738 EISA bus support has been removed. The WITH_EISA option is no longer
1742 MCA bus support has been removed.
1745 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
1746 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
1749 The EM_MULTIQUEUE kernel configuration option is deprecated now that
1750 the em(4) driver conforms to iflib specifications.
1753 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
1754 IFLIB. If you have a custom kernel configuration that excludes em(4)
1755 but you use igb(4), you need to re-add em(4) to your custom
1759 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
1760 Please see the 20141231 entry below for information about prerequisites
1761 and upgrading, if you are not already using clang 3.5.0 or higher.
1764 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
1765 Please see the 20141231 entry below for information about prerequisites
1766 and upgrading, if you are not already using clang 3.5.0 or higher.
1769 The layout of the pmap structure has changed for powerpc to put the pmap
1770 statistics at the front for all CPU variations. libkvm(3) and all tools
1771 that link against it need to be recompiled.
1774 isl(4) and cyapa(4) drivers now require a new driver,
1775 chromebook_platform(4), to work properly on Chromebook-class hardware.
1776 On other types of hardware the drivers may need to be configured using
1777 device hints. Please see the corresponding manual pages for details.
1780 The urtwn(4) driver was merged into rtwn(4) and now consists of
1781 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
1783 Also, firmware for RTL8188CE was renamed due to possible name
1784 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
1787 GNU rcs has been removed from base. It is available as packages:
1788 - rcs: Latest GPLv3 GNU rcs version.
1789 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
1793 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
1794 modules now requires that the kernel configuration contain the
1795 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
1798 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
1799 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
1802 Relocatable object files with the extension of .So have been renamed
1803 to use an extension of .pico instead. The purpose of this change is
1804 to avoid a name clash with shared libraries on case-insensitive file
1805 systems. On those file systems, foo.So is the same file as foo.so.
1808 GNU rcs has been turned off by default. It can (temporarily) be built
1809 again by adding WITH_RCS knob in src.conf.
1810 Otherwise, GNU rcs is available from packages:
1811 - rcs: Latest GPLv3 GNU rcs version.
1812 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
1815 The backup_uses_rcs functionality has been removed from rc.subr.
1818 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
1819 two separate components, QUEUE_MACRO_DEBUG_TRACE and
1820 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
1821 QUEUE_MACRO_DEBUG behavior.
1824 r304787 changed some ioctl interfaces between the iSCSI userspace
1825 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1826 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1830 The UDP receive code has been updated to only treat incoming UDP
1831 packets that were addressed to an L2 broadcast address as L3
1832 broadcast packets. It is not expected that this will affect any
1833 standards-conforming UDP application. The new behaviour can be
1834 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1838 Remove the openbsd_poll system call.
1839 __FreeBSD_version has been bumped because of this.
1842 The stable/11 branch has been created from head@r302406.
1844 After branch N is created, entries older than the N-2 branch point are removed
1845 from this file. After stable/14 is branched and current becomes FreeBSD 15,
1846 entries older than stable/12 branch point will be removed from current's
1853 Sometimes, obscure build problems are the result of environment
1854 poisoning. This can happen because the make utility reads its
1855 environment when searching for values for global variables. To run
1856 your build attempts in an "environmental clean room", prefix all make
1857 commands with 'env -i '. See the env(1) manual page for more details.
1858 Occasionally a build failure will occur with "make -j" due to a race
1859 condition. If this happens try building again without -j, and please
1860 report a bug if it happens consistently.
1862 When upgrading from one major version to another it is generally best to
1863 upgrade to the latest code in the currently installed branch first, then
1864 do an upgrade to the new branch. This is the best-tested upgrade path,
1865 and has the highest probability of being successful. Please try this
1866 approach if you encounter problems with a major version upgrade. Since
1867 the stable 4.x branch point, one has generally been able to upgrade from
1868 anywhere in the most recent stable branch to head / current (or even the
1869 last couple of stable branches). See the top of this file when there's
1872 The update process will emit an error on an attempt to perform a build
1873 or install from a FreeBSD version below the earliest supported version.
1874 When updating from an older version the update should be performed one
1875 major release at a time, including running `make delete-old` at each
1878 When upgrading a live system, having a root shell around before
1879 installing anything can help undo problems. Not having a root shell
1880 around can lead to problems if pam has changed too much from your
1881 starting point to allow continued authentication after the upgrade.
1883 This file should be read as a log of events. When a later event changes
1884 information of a prior event, the prior event should not be deleted.
1885 Instead, a pointer to the entry with the new information should be
1886 placed in the old entry. Readers of this file should also sanity check
1887 older entries before relying on them blindly. Authors of new entries
1888 should write them with this in mind.
1892 When upgrading the boot ZFS pool to a new version (via zpool upgrade),
1893 always follow these three steps:
1895 1) recompile and reinstall the ZFS boot loader and boot block
1896 (this is part of "make buildworld" and "make installworld")
1898 2) update the ZFS boot block on your boot drive (only required when
1899 doing a zpool upgrade):
1901 When booting on x86 via BIOS, use the following to update the ZFS boot
1902 block on the freebsd-boot partition of a GPT partitioned drive ada0:
1903 gpart bootcode -p /boot/gptzfsboot -i $N ada0
1904 The value $N will typically be 1. For EFI booting, see EFI notes.
1906 3) zpool upgrade the root pool. New bootblocks will work with old
1907 pools, but not vice versa, so they need to be updated before any
1910 Non-boot pools do not need these updates.
1915 There are two locations the boot loader can be installed into. The
1916 current location (and the default) is \efi\freebsd\loader.efi and using
1917 efibootmgr(8) to configure it. The old location, that must be used on
1918 deficient systems that don't honor efibootmgr(8) protocols, is the
1919 fallback location of \EFI\BOOT\BOOTxxx.EFI. Generally, you will copy
1920 /boot/loader.efi to this location, but on systems installed a long time
1921 ago the ESP may be too small and /boot/boot1.efi may be needed unless
1922 the ESP has been expanded in the meantime.
1924 Recent systems will have the ESP mounted on /boot/efi, but older ones
1925 may not have it mounted at all, or mounted in a different
1926 location. Older arm SD images with MBR used /boot/msdos as the
1927 mountpoint. The ESP is a MSDOS filesystem.
1929 The EFI boot loader rarely needs to be updated. For ZFS booting,
1930 however, you must update loader.efi before you do 'zpool upgrade' the
1931 root zpool, otherwise the old loader.efi may reject the upgraded zpool
1932 since it does not automatically understand some new features.
1934 See loader.efi(8) and uefi(8) for more details.
1938 If you are updating from a prior version of FreeBSD (even one just
1939 a few days old), you should follow this procedure. It is the most
1940 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1942 make kernel-toolchain
1943 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1944 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1946 To test a kernel once
1947 ---------------------
1948 If you just want to boot a kernel once (because you are not sure
1949 if it works, or if you want to boot a known bad kernel to provide
1950 debugging information) run
1951 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1952 nextboot -k testkernel
1954 To rebuild everything and install it on the current system.
1955 -----------------------------------------------------------
1956 # Note: sometimes if you are running current you gotta do more than
1957 # is listed here if you are upgrading from a really old current.
1959 <make sure you have good level 0 dumps>
1961 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1962 make installkernel KERNCONF=YOUR_KERNEL_HERE
1964 <reboot in single user> [3]
1971 To cross-install current onto a separate partition
1972 --------------------------------------------------
1973 # In this approach we use a separate partition to hold
1974 # current's root, 'usr', and 'var' directories. A partition
1975 # holding "/", "/usr" and "/var" should be about 2GB in
1978 <make sure you have good level 0 dumps>
1981 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1982 <maybe newfs current's root partition>
1983 <mount current's root partition on directory ${CURRENT_ROOT}>
1984 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1985 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1986 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1987 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1988 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1989 <reboot into current>
1990 <do a "native" rebuild/install as described in the previous section>
1991 <maybe install compatibility libraries from ports/misc/compat*>
1995 To upgrade in-place from stable to current
1996 ----------------------------------------------
1997 <make sure you have good level 0 dumps>
1999 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
2000 make installkernel KERNCONF=YOUR_KERNEL_HERE
2002 <reboot in single user> [3]
2009 Make sure that you've read the UPDATING file to understand the
2010 tweaks to various things you need. At this point in the life
2011 cycle of current, things change often and you are on your own
2012 to cope. The defaults can also change, so please read ALL of
2013 the UPDATING entries.
2015 Also, if you are tracking -current, you must be subscribed to
2016 freebsd-current@freebsd.org. Make sure that before you update
2017 your sources that you have read and understood all the recent
2018 messages there. If in doubt, please track -stable which has
2019 much fewer pitfalls.
2021 [1] If you have third party modules, such as vmware, you should disable
2022 them at this point so they don't crash your system on
2023 reboot. Alternatively, you should rebuild all the modules you have in
2024 your system and install them as well. If you are running -current, you
2025 should seriously consider placing all sources to all the modules for
2026 your system (or symlinks to them) in /usr/local/sys/modules so this
2027 happens automatically. If all your modules come from ports, then adding
2028 the port origin directories to PORTS_MODULES instead is also automatic
2030 PORTS_MODULES+=x11/nvidia-driver
2032 [3] From the bootblocks, boot -s, and then do
2036 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed
2037 cd src # full path to source
2038 adjkerntz -i # if CMOS is wall time
2039 Also, when doing a major release upgrade, it is required that you boot
2040 into single user mode to do the installworld.
2042 [4] Note: This step is non-optional. Failure to do this step
2043 can result in a significant reduction in the functionality of the
2044 system. Attempting to do it by hand is not recommended and those
2045 that pursue this avenue should read this file carefully, as well
2046 as the archives of freebsd-current and freebsd-hackers mailing lists
2047 for potential gotchas. See etcupdate(8) for more information.
2049 [5] Usually this step is a no-op. However, from time to time
2050 you may need to do this if you get unknown user in the following
2053 [6] This only deletes old files and directories. Old libraries
2054 can be deleted by "make delete-old-libs", but you have to make
2055 sure that no program is using those libraries anymore.
2057 [8] The new kernel must be able to run existing binaries used by an
2058 installworld. When upgrading across major versions, the new kernel's
2059 configuration must include the correct COMPAT_FREEBSD<n> option for
2060 existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure
2061 to do so may leave you with a system that is hard to boot to recover. A
2062 GENERIC kernel will include suitable compatibility options to run
2063 binaries from older branches. Note that the ability to run binaries
2064 from unsupported branches is not guaranteed.
2066 Make sure that you merge any new devices from GENERIC since the
2067 last time you updated your kernel config file. Options also
2068 change over time, so you may need to adjust your custom kernels
2071 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2072 "?=" instead of the "=" assignment operator, so that buildworld can
2073 override the CPUTYPE if it needs to.
2075 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2076 not on the command line, or in /etc/make.conf. buildworld will
2077 warn if it is improperly defined.
2080 This file contains a list, in reverse chronological order, of major
2081 breakages in tracking -current. It is not guaranteed to be a complete
2082 list of such breakages, and only contains entries since September 23, 2011.
2083 If you need to see UPDATING entries from before that date, you will need
2084 to fetch an UPDATING file from an older FreeBSD release.
2086 Copyright information:
2088 Copyright 1998-2009 M. Warner Losh <imp@FreeBSD.org>
2090 Redistribution, publication, translation and use, with or without
2091 modification, in full or in part, in any form or format of this
2092 document are permitted without further permission from the author.
2094 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2095 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2096 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2097 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2098 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2099 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2100 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2101 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2102 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2103 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2104 POSSIBILITY OF SUCH DAMAGE.
2106 Contact Warner Losh if you have any questions about your use of