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