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 14.x IS SLOW:
16 FreeBSD 14.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 The heuristic for detecting old chromebooks with an EC bug that requires
32 atkbdc driver workarounds has changed. There should be no functional
33 change, but if your old chromebook's keyboard stops working, please
34 file a PR and assign it to imp.
37 OpenSSL has been updated to version 3.0, including changes throughout
38 the base system. It is important to rebuild third-party software
42 To enable pf rdr rules for connections initiated from the host, pf
43 filter rules can be optionally enabled for packets delivered
44 locally. This can change the behavior of rules which match packets
45 delivered to lo0. To enable this feature:
47 sysctl net.pf.filter_local=1
50 When enabled, its best to ensure that packets delivered locally are not
51 filtered, e.g. by adding a 'skip on lo' rule.
54 Improvements to libtacplus(8) mean that tacplus.conf(5) now
55 follows POSIX shell syntax rules. This may cause TACACS+
56 authentication to fail if the shared secret contains a single
57 quote, double quote, or backslash character which isn't
58 already properly quoted or escaped.
61 Belatedly switch the default nvme block device on x86 from nvd to nda.
62 nda created nvd compatibility links by default, so this should be a
63 nop. If this causes problems for your application, set hw.nvme.use_nvd=1
64 in your loader.conf or add `options NVME_USE_NVD=1` to your kernel
65 config. To disable the nvd compatibility aliases, add
66 kern.cam.nda.nvd_compat=0 to loader.conf. The default has been nda on
67 all non-x86 platforms for some time now. If you need to fall back,
68 please email imp@freebsd.org about why.
71 Remove portsnap(8). Users are encouraged to obtain the ports tree
75 Add jobs.mk to save typing. Enables -j${JOB_MAX} and logging
79 make -j${JOB_MAX} buildworld > ../buildworld.log 2>&1
81 where JOB_MAX is derrived from ncpus in local.sys.mk if not set in env.
84 Video related devices for some arm devices have been renamed.
85 If you have a custom kernel config and want to use hdmi output on
86 IMX6 board you need to add "device dwc_hdmi" "device imx6_hdmi" and
87 "device imx6_ipu" to it.
88 If you have a custom kernel config and want to use hdmi output on
89 TI AM335X board you need to add "device tda19988" to it.
90 If you add "device hdmi" in it you need to remove it as it doesn't
94 Introduce new kernel options KBD_DELAY1 and KBD_DELAY2. See atkbdc(4)
98 sshd now defaults to having X11Forwarding disabled, following upstream.
99 Administrators who wish to enable X11Forwarding should add
100 `X11Forwarding yes` to /etc/ssh/sshd_config.
103 Since commit 75d41cb6967 Huawei 3G/4G LTE Mobile Devices do not default
104 to ECM, but NCM mode and need u3g and ucom modules loaded. See cdce(4).
107 As of commit 7c40e2d5f685, the dependency on netlink(4) has been added
108 to the linux_common(4) module. Users relying on linux_common may need
109 to complile netlink(4) module if it is not present in their kernel.
112 The WITHOUT_CXX option has been removed. C++ components in the base
113 system are now built unconditionally.
116 LinuxKPI pci.h changes may require out-of-tree drivers to be recompiled.
117 Bump _FreeBSD_version to 1400078 to be able to detect this change.
120 llvm-objump is now always installed as objdump. Previously there was
121 no /usr/bin/objdump unless the WITH_LLVM_BINUTILS knob was used.
123 Some LLVM objdump options have a different output format compared to
124 GNU objdump; readelf is available for inspecting ELF files, and GNU
125 objdump is available from the devel/binutils port or package.
128 dma(8) has replaced sendmail(8) as the default mta. For people willing
129 to reenable sendmail(8):
131 $ cp /usr/share/examples/sendmail/mailer.conf /etc/mail/mailer.conf
133 and add sendmail_enable="YES" to rc.conf.
136 hw.bus.disable_failed_devices has changed from 'false' to 'true' by
137 default. Now if newbus succeeds in probing a device, but fails to attach
138 the device, we'll disable the device. In the past, we'd keep retrying
139 the device on each new driver loaded. To get that behavior now, one
140 needs to use devctl to re-enable the device, and reprobe it (or set
141 the sysctl/tunable hw.bus.disable_failed_devices=false).
143 NOTE: This was reverted 20221205 due to unexpected compatibility issues
146 pf no longer accepts 'scrub fragment crop' or 'scrub fragment drop-ovl'.
147 These configurations are no longer automatically reinterpreted as
148 'scrub fragment reassemble'.
151 The WITHOUT_CLANG_IS_CC option has been removed. When Clang is enabled
152 it is always installed as /usr/bin/cc (and c++, cpp).
155 Some programs have been moved into separate packages. It is recommended
156 for pkgbase users to do:
158 pkg install FreeBSD-dhclient FreeBSD-geom FreeBSD-resolvconf \
159 FreeBSD-devd FreeBSD-devmatch
161 after upgrading to restore all the component that were previously
165 LinuxKPI pm.h changes require an update to the latest drm-kmod version
166 before re-compiling to avoid errors.
169 The macros provided for the manipulation of CPU sets (e.g. CPU_AND)
170 have been modified to take 2 source arguments instead of only 1.
171 Externally maintained sources that use these macros will have to
172 be adapted. The FreeBSD version has been bumped to 1400046 to
176 A number of the kernel include files are able to be included by
177 themselves. A test has been added to buildworld to enforce this.
180 Remove mips as a recognized target. This starts the decommissioning of
181 mips support in FreeBSD. mips related items will be removed wholesale in
182 the coming days and weeks.
184 This broke the NO_CLEAN build for some people. Either do a clean build
186 lib/clang/include/llvm/Config/Targets.def
187 lib/clang/include/llvm/Config/AsmParsers.def
188 lib/clang/include/llvm/Config/Disassemblers.def
189 lib/clang/include/llvm/Config/AsmPrinters.def
190 before the build to force everything to rebuild that needs to.
193 Unbound support for RFC8375: The special-use domain 'home.arpa' is
194 by default blocked. To unblock it use a local-zone nodefault
195 statement in unbound.conf:
196 local-zone: "home.arpa." nodefault
198 Or use another type of local-zone to override with your choice.
200 The reason for this is discussed in Section 6.1 of RFC8375:
201 Because 'home.arpa.' is not globally scoped and cannot be secured
202 using DNSSEC based on the root domain's trust anchor, there is no way
203 to tell, using a standard DNS query, in which homenet scope an answer
204 belongs. Consequently, users may experience surprising results with
205 such names when roaming to different homenets.
208 Commit b8d60729deef changed the TCP congestion control framework so
209 that any of the included congestion control modules could be
210 the single module built into the kernel. Previously newreno
211 was automatically built in through direct reference. As of
212 this commit you are required to declare at least one congestion
213 control module (e.g. 'options CC_NEWRENO') and to also declare a
214 default using the CC_DEFAULT option (e.g. options CC_DEFAULT="newreno\").
215 The GENERIC configuration includes CC_NEWRENO and defines newreno
216 as the default. If no congestion control option is built into the
217 kernel and you are including networking, the kernel compile will
218 fail. Also if no default is declared the kernel compile will fail.
221 Mips has been removed from universe builds. It will be removed from the
225 Commit f0c9847a6c47 changed the arguments for VOP_ALLOCATE.
226 The NFS modules must be rebuilt from sources and any out
227 of tree file systems that implement their own VOP_ALLOCATE
228 may need to be modified.
231 The synchronous PPP kernel driver sppp(4) has been removed.
232 The cp(4) and ce(4) drivers are now always compiled with netgraph(4)
233 support, formerly enabled by NETGRAPH_CRONYX option.
236 sh(1) is now the default shell for the root user. To force root to use
237 the csh shell, please run the following command as root:
242 Ncurses distribution has been split between libtinfow and libncurses
243 with libncurses.so becoming a linker (ld) script to seamlessly link
244 to libtinfow as needed. Bump _FreeBSD_version to 1400035 to reflect
248 As of commit 8160a0f62be6, the dummynet module no longer depends on the
249 ipfw module. Dummynet can now be used by pf as well as ipfw. As such
250 users who relied on this dependency may need to include ipfw in the
251 list of modules to load on their systems.
254 As of commit 903873ce1560, the mixer(8) utility has got a slightly
255 new syntax. Please refer to the mixer(8) manual page for more
256 information. The old mixer utility can be installed from ports:
257 audio/freebsd-13-mixer
260 As of commit 55089ef4f8bb, the global variable nfs_maxcopyrange has
261 been deleted from the nfscommon.ko. As such, nfsd.ko must be built
262 from up to date sources to avoid an undefined reference when
266 As of commit 62ca9fc1ad56 OpenSSL no longer enables kernel TLS
267 by default. Users can enable kernel TLS via the "KTLS" SSL
268 option. This can be enabled globally by using a custom
269 OpenSSL config file via OPENSSL_CONF or via an
270 application-specific configuration option for applications
271 which permit setting SSL options via SSL_CONF_cmd(3).
274 Commit 3ad1e1c1ce20 changed the internal KAPI between the NFS
275 modules. Therefore, all need to be rebuilt from sources.
278 Commit b69019c14cd8 removes pf's DIOCGETSTATESNV ioctl.
279 As of be70c7a50d32 it is no longer used by userspace, but it does mean
280 users may not be able to enumerate pf states if they update the kernel
281 past b69019c14cd8 without first updating userspace past be70c7a50d32.
284 As of commit 01ad0c007964 if_bridge member interfaces can no longer
285 change their MTU. Changing the MTU of the bridge itself will change the
286 MTU on all member interfaces instead.
289 Commit ee29e6f31111 changed the internal KAPI between the nfscommon
290 and nfsd modules. Therefore, both need to be rebuilt from sources.
291 Bump __FreeBSD_version to 1400026 for this KAPI change.
294 The 20210707 awk update brought in a change in behavior. This has
295 been corrected as of d4d252c49976. Between these dates, if you
296 installed a new awk binary, you may not be able to build a new
297 kernel because the change in behavior affected the genoffset
298 script used to build the kernel. If you did update, the fix is
299 to update your sources past the above hash and do
302 % sudo -E make install
303 to enable building kernels again.
306 Commit 1e0a518d6548 changed the internal KAPI between the NFS
307 modules. They all need to be rebuilt from sources. I did not
308 bump __FreeBSD_version, since it was bumped recently.
311 awk has been updated to the latest one-true-awk version 20210215.
312 This contains a number of minor bug fixes.
315 The NFSv4 client now uses the highest minor version of NFSv4
316 supported by the NFSv4 server by default instead of minor version 0,
318 The "minorversion" mount option may be used to override this default.
321 Bump __FreeBSD_version to 1400024 for LinuxKPI changes.
322 Most notably netdev.h can change now as the (last) dependencies
323 (mlx4/ofed) are now using struct ifnet directly, but also for PCI
324 additions and others.
327 The directory "blacklisted" under /usr/share/certs/ has been
328 renamed to "untrusted".
331 svnlite has been removed from base. Should you need svn for any reason
332 please install the svn package or port.
335 Commit e1a907a25cfa changed the internal KAPI between the krpc
336 and nfsserver. As such, both modules must be rebuilt from
337 sources. Bump __FreeBSD_version to 1400022.
340 The an(4) driver has been removed from FreeBSD.
343 The vendor/openzfs branch was renamed to vendor/openzfs/legacy to
344 start tracking OpenZFS upstream more closely. Please see
345 https://lists.freebsd.org/archives/freebsd-current/2021-June/000153.html
346 for details on how to correct any errors that might result. The
347 short version is that you need to remove the old branch locally:
348 git update-ref -d refs/remotes/freebsd/vendor/openzfs
349 (assuming your upstream origin is named 'freebsd').
352 Commits 17accc08ae15 and de102f870501 add new files to LinuxKPI
353 which break drm-kmod. In addition various other additions where
354 committed. Bump __FreeBSD_version to 1400015 to be able to
358 Commit ca179c4d74f2 changed the package in which the OpenSSL
359 libraries and utilities are packaged.
360 It is recommended for pkgbase user to do:
361 pkg install -f FreeBSD-openssl
362 before pkg upgrade otherwise some dependencies might not be met
363 and pkg will stop working as libssl will not be present anymore
367 Commit 875977314881 changed the internal KAPI between
368 the nfsd and nfscommon modules. As such these modules
369 need to be rebuilt from sources.
370 Without this patch in your NFSv4.1/4.2 server, enabling
371 delegations by setting vfs.nfsd.issue_delegations non-zero
375 Commit 7763814fc9c2 changed the internal KAPI between
376 the krpc and NFS. As such, the krpc, nfscommon and
377 nfscl modules must all be rebuilt from sources.
378 Without this patch, NFSv4.1/4.2 mounts should not
379 be done with the nfscbd(8) daemon running, to avoid
380 needing a working back channel for server->client RPCs.
383 Commit 01ae8969a9ee fixed the NFSv4.1/4.2 server so that it
384 handles binding of the back channel as required by RFC5661.
385 Until this patch is in your server, avoid use of the "nconnects"
386 mount option for Linux NFSv4.1/4.2 mounts.
389 For 64-bit architectures the base system is now built with Position
390 Independent Executable (PIE) support enabled by default. It may be
391 disabled using the WITHOUT_PIE knob. A clean build is required.
394 Various LinuxKPI functionality was added which conflicts with DRM.
395 Please update your drm-kmod port to after the __FreeBSD_version 1400003
399 PC Card attachments for all devices have been removed. In the case of
400 wi and cmx, the entire drivers were removed because they were only
401 PC Card devices. FreeBSD_version 1300134 should be used for this
402 since it was bumped so recently.
405 Transport-independent parts of HID support have been split off the USB
406 code in to separate subsystem. Kernel configs which include one of
407 ums, ukbd, uhid, atp, wsp, wmt, uaudio, ugold or ucycom drivers should
408 be updated with adding of "device hid" line.
411 ncurses installation has been modified to only keep the widechar
412 enabled version. Incremental build is broken for that change, so it
413 requires a clean build.
416 The FreeBSD project has migrated from Subversion to Git. Temporary
417 instructions can be found at
418 https://github.com/bsdimp/freebsd-git-docs/blob/main/src-cvt.md
419 and other documents in that repo.
422 The services database has been updated to cover more of the basic
423 services expected in a modern system. The database is big enough
424 that it will cause issues in mergemaster in Releases previous to
425 12.2 and 11.3, or in very old current systems from before r358154.
428 Obsolete in-tree GDB 6.1.1 has been removed. GDB (including kgdb)
429 may be installed from ports or packages.
432 ping6 has been merged into ping. It can now be called as "ping -6".
433 See ping(8) for details.
436 Default value of net.add_addr_allfibs has been changed to 0.
437 If you have multi-fib configuration and rely on existence of all
438 interface routes in every fib, you need to set the above sysctl to 1.
441 The internal pre-processor in the calendar(1) program has been
442 extended to support more C pre-processor commands (e.g. #ifdef, #else,
443 and #undef) and to detect unbalanced conditional statements.
444 Error messages have been extended to include the filename and line
445 number if processing stops to help fixing malformed data files.
448 All the data files for the calendar(1) program, except calendar.freebsd,
449 have been moved to the deskutils/calendar-data port, much like the
450 jewish calendar entries were moved to deskutils/hebcal years ago. After
451 make delete-old-files, you need to install it to retain full
452 functionality. calendar(1) will issue a reminder for files it can't
456 LINT files are no longer generated. We now include the relevant NOTES
457 files. Note: This may cause conflicts with updating in some cases.
458 find sys -name LINT\* -delete
459 is suggested across this commit to remove the generated LINT files.
461 If you have tried to update with generated files there, the svn
462 command you want to un-auger the tree is
465 and then do the above find from the top level. Substitute 'amd64'
466 above with where the error message indicates a conflict.
469 OpenZFS support has been integrated. Do not upgrade root pools until
470 the loader is updated to support zstd. Furthermore, we caution against
471 'zpool upgrade' for the next few weeks. The change should be transparent
472 unless you want to use new features.
474 Not all "NO_CLEAN" build scenarios work across these changes. Many
475 scenarios have been tested and fixed, but rebuilding kernels without
476 rebuilding world may fail.
478 The ZFS cache file has moved from /boot to /etc to match the OpenZFS
479 upstream default. A fallback to /boot has been added for mountroot.
481 Pool auto import behavior at boot has been moved from the kernel module
482 to an explicit "zpool import -a" in one of the rc scripts enabled by
483 zfs_enable=YES. This means your non-root zpools won't auto import until
484 you upgrade your /etc/rc.d files.
487 The resume code now notifies devd with the 'kernel' system
488 rather than the old 'kern' subsystem to be consistent with
489 other use. The old notification will be created as well, but
490 will be removed prior to FreeBSD 14.0.
493 r362275 changed the internal API between the kernel RPC and the
494 NFS modules. As such, all the modules must be recompiled from
498 r364330 modified the internal API used between the NFS modules.
499 As such, all the NFS modules must be re-compiled from sources.
502 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
503 been upgraded to 11.0.0. Please see the 20141231 entry below for
504 information about prerequisites and upgrading, if you are not already
505 using clang 3.5.0 or higher.
508 r364092 modified the internal ABI used between the kernel NFS
509 modules. As such, all of these modules need to be rebuilt
510 from sources, so a version bump was done.
513 Makefile.inc has been updated to work around the issue documented in
514 20200729. It was a case where the optimization of using symbolic links
515 to point to binaries created a situation where we'd run new binaries
516 with old libraries starting midway through the installworld process.
519 r363679 has redefined some undefined behavior in regcomp(3); notably,
520 extraneous escapes of most ordinary characters will no longer be
521 accepted. An exp-run has identified all of the problems with this in
522 ports, but other non-ports software may need extra escapes removed to
523 continue to function.
525 Because of this change, installworld may encounter the following error
526 from rtld: Undefined symbol "regcomp@FBSD_1.6" -- It is imperative that
527 you do not halt installworld. Instead, let it run to completion (whether
528 successful or not) and run installworld once more.
531 A new implementation of bc and dc has been imported in r362681. This
532 implementation corrects non-conformant behavior of the previous bc
533 and adds GNU bc compatible options. It offers a number of extensions,
534 is much faster on large values, and has support for message catalogs
535 (a number of languages are already supported, contributions of further
536 languages welcome). The option WITHOUT_GH_BC can be used to build the
537 world with the previous versions of bc and dc.
540 r362639 changed the internal API used between the NFS kernel modules.
541 As such, they all need to be rebuilt from sources.
544 r362158 changed the arguments for VFS_CHECKEXP(). As such, any
545 out of tree file systems need to be modified and rebuilt.
546 Also, any file systems that are modules must be rebuilt.
549 read(2) of a directory fd is now rejected by default. root may
550 re-enable it for system root only on non-ZFS filesystems with the
551 security.bsd.allow_read_dir sysctl(8) MIB if
552 security.bsd.suser_enabled=1.
554 It may be advised to setup aliases for grep to default to `-d skip` if
555 commonly non-recursively grepping a list that includes directories and
556 the potential for the resulting stderr output is not tolerable. Example
557 aliases are now installed, commented out, in /root/.cshrc and
561 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
562 been upgraded to 10.0.1. Please see the 20141231 entry below for
563 information about prerequisites and upgrading, if you are not already
564 using clang 3.5.0 or higher.
567 Support for obsolete compilers has been removed from the build system.
568 Clang 6 and GCC 6.4 are the minimum supported versions.
571 closefrom(2) has been moved under COMPAT12, and replaced in libc with a
572 stub that calls close_range(2). If using a custom kernel configuration,
573 you may want to ensure that the COMPAT_FREEBSD12 option is included, as
574 a slightly older -CURRENT userland and older FreeBSD userlands may not
575 be functional without closefrom(2).
578 Upstream DTS from Linux 5.6 was merged and they now have the SID
579 and THS (Secure ID controller and THermal Sensor) node present.
580 The DTB overlays have now been removed from the tree for the H3/H5 and
581 A64 SoCs and the aw_sid and aw_thermal driver have been updated to
582 deal with upstream DTS. If you are using those overlays you need to
583 remove them from loader.conf and update the DTBs on the FAT partition.
586 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
587 been upgraded to 10.0.0. Please see the 20141231 entry below for
588 information about prerequisites and upgrading, if you are not already
589 using clang 3.5.0 or higher.
592 The amd(8) automount daemon has been removed from the source tree.
593 As of FreeBSD 10.1 autofs(5) is the preferred tool for automounting.
594 amd is still available in the sysutils/am-utils port.
597 Removed brooktree driver (bktr.4) from the tree.
600 The WITH_GPL_DTC option has been removed. The BSD-licenced device tree
601 compiler in usr.bin/dtc is used on all architectures which use dtc, and
602 the GPL dtc is available (if needed) from the sysutils/dtc port.
605 The WITHOUT_LLVM_LIBUNWIND option has been removed. LLVM's libunwind
606 is used by all supported CPU architectures.
609 GCC 4.2.1 has been removed from the tree. The WITH_GCC,
610 WITH_GCC_BOOTSTRAP, and WITH_GNUCXX options are no longer available.
611 Users who wish to build FreeBSD with GCC must use the external toolchain
615 ncurses has been updated to a newer version (6.2-20200215). Given the ABI
616 has changed, users will have to rebuild all the ports that are linked to
620 The size of struct vnet and the magic cookie have changed.
621 Users need to recompile libkvm and all modules using VIMAGE
622 together with their new kernel.
625 Defining the long deprecated NO_CTF, NO_DEBUG_FILES, NO_INSTALLLIB,
626 NO_MAN, NO_PROFILE, and NO_WARNS variables is now an error. Update
627 your Makefiles and scripts to define MK_<var>=no instead as required.
629 One exception to this is that program or library Makefiles should
630 define MAN to empty rather than setting MK_MAN=no.
633 Clang/LLVM is now the default compiler and LLD the default
637 make universe no longer uses GCC 4.2.1 on any architectures.
638 Architectures not supported by in-tree Clang/LLVM require an
639 external toolchain package.
642 GCC 4.2.1 is now not built by default, as part of the GCC 4.2.1
643 retirement plan. Specifically, the GCC, GCC_BOOTSTRAP, and GNUCXX
644 options default to off for all supported CPU architectures. As a
645 short-term transition aid they may be enabled via WITH_* options.
646 GCC 4.2.1 is expected to be removed from the tree on 2020-03-31.
649 Support for armv5 has been disconnected and is being removed. The
650 machine combination MACHINE=arm MACHINE_ARCH=arm is no longer valid.
651 You must now use a MACHINE_ARCH of armv6 or armv7. The default
652 MACHINE_ARCH for MACHINE=arm is now armv7.
655 Clang/LLVM is now the default compiler for all powerpc architectures.
656 LLD is now the default linker for powerpc64. The change for powerpc64
657 also includes a change to the ELFv2 ABI, incompatible with the existing
661 Kernel-loadable random(4) modules are no longer unloadable.
664 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
665 been upgraded to 9.0.1. Please see the 20141231 entry below for
666 information about prerequisites and upgrading, if you are not already
667 using clang 3.5.0 or higher.
670 r355677 has modified the internal interface used between the
671 NFS modules in the kernel. As such, they must all be upgraded
672 simultaneously. I will do a version bump for this.
675 The root certificates of the Mozilla CA Certificate Store have been
676 imported into the base system and can be managed with the certctl(8)
677 utility. If you have installed the security/ca_root_nss port or package
678 with the ETCSYMLINK option (the default), be advised that there may be
679 differences between those included in the port and those included in
680 base due to differences in nss branch used as well as general update
681 frequency. Note also that certctl(8) cannot manage certs in the
682 format used by the security/ca_root_nss port.
685 The amd(8) automount daemon has been disabled by default, and will be
686 removed in the future. As of FreeBSD 10.1 the autofs(5) is available
690 The nctgpio and wbwd drivers have been moved to the superio bus.
691 If you have one of these drivers in a kernel configuration, then
692 you should add device superio to it. If you use one of these drivers
693 as a module and you compile a custom set of modules, then you should
694 add superio to the set.
697 KPIs for network drivers to access interface addresses have changed.
698 Users need to recompile NIC driver modules together with kernel.
701 The net.link.tap.user_open sysctl no longer prevents user opening of
702 already created /dev/tapNN devices. Access is still controlled by
703 node permissions, just like tun devices. The net.link.tap.user_open
704 sysctl is now used only to allow users to perform devfs cloning of
705 tap devices, and the subsequent open may not succeed if the user is not
706 in the appropriate group. This sysctl may be deprecated/removed
707 completely in the future.
710 mips, powerpc, and sparc64 are no longer built as part of
711 universe / tinderbox unless MAKE_OBSOLETE_GCC is defined. If
712 not defined, mips, powerpc, and sparc64 builds will look for
713 the xtoolchain binaries and if installed use them for universe
714 builds. As llvm 9.0 becomes vetted for these architectures, they
715 will be removed from the list.
718 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
719 been upgraded to 9.0.0. Please see the 20141231 entry below for
720 information about prerequisites and upgrading, if you are not already
721 using clang 3.5.0 or higher.
724 The hpt27xx, hptmv, hptnr, and hptrr drivers have been removed from
725 GENERIC. They are available as modules and can be loaded by adding
726 to /boot/loader.conf hpt27xx_load="YES", hptmv_load="YES",
727 hptnr_load="YES", or hptrr_load="YES", respectively.
730 ntpd no longer by default locks its pages in memory, allowing them
731 to be paged out by the kernel. Use rlimit memlock to restore
732 historic BSD behaviour. For example, add "rlimit memlock 32"
733 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
736 Several of ping6's options have been renamed for better consistency
737 with ping. If you use any of -ARWXaghmrtwx, you must update your
738 scripts. See ping6(8) for details.
741 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
742 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
743 been removed from mount_fusefs(8). You can safely remove them from
744 your scripts, because they had no effect.
746 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
747 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
748 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
749 sysctls have been removed. If you felt the need to set any of them to
750 a non-default value, please tell asomers@FreeBSD.org why.
753 Default permissions on the /var/account/acct file (and copies of it
754 rotated by periodic daily scripts) are changed from 0644 to 0640
755 because the file contains sensitive information that should not be
756 world-readable. If the /var/account directory must be created by
757 rc.d/accounting, the mode used is now 0750. Admins who use the
758 accounting feature are encouraged to change the mode of an existing
759 /var/account directory to 0750 or 0700.
762 Entropy collection and the /dev/random device are no longer optional
763 components. The "device random" option has been removed.
764 Implementations of distilling algorithms can still be made loadable
765 with "options RANDOM_LOADABLE" (e.g., random_fortuna.ko).
768 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
769 been upgraded to 8.0.1. Please see the 20141231 entry below for
770 information about prerequisites and upgrading, if you are not already
771 using clang 3.5.0 or higher.
774 A fix was applied to i386 kernel modules to avoid panics with
775 dpcpu or vnet. Users need to recompile i386 kernel modules
776 having pcpu or vnet sections or they will refuse to load.
779 User-wired pages now have their own counter,
780 vm.stats.vm.v_user_wire_count. The vm.max_wired sysctl was renamed
781 to vm.max_user_wired and changed from an unsigned int to an unsigned
782 long. bhyve VMs wired with the -S are now subject to the user
783 wiring limit; the vm.max_user_wired sysctl may need to be tuned to
784 avoid running into the limit.
787 The IPSEC option has been removed from GENERIC. Users requiring
788 ipsec(4) must now load the ipsec(4) kernel module.
791 The tap(4) driver has been folded into tun(4), and the module has been
792 renamed to tuntap. You should update any kld_list="if_tap" or
793 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
794 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
795 module instead, and "device tap" or "device tun" entries in kernel
796 config files to select the tuntap device instead.
799 The following knobs have been added related to tradeoffs between
800 safe use of the random device and availability in the absence of
803 kern.random.initial_seeding.bypass_before_seeding: tunable; set
804 non-zero to bypass the random device prior to seeding, or zero to
805 block random requests until the random device is initially seeded.
806 For now, set to 1 (unsafe) by default to restore pre-r346250 boot
807 availability properties.
809 kern.random.initial_seeding.read_random_bypassed_before_seeding:
810 read-only diagnostic sysctl that is set when bypass is enabled and
811 read_random(9) is bypassed, to enable programmatic handling of this
812 initial condition, if desired.
814 kern.random.initial_seeding.arc4random_bypassed_before_seeding:
815 Similar to the above, but for arc4random(9) initial seeding.
817 kern.random.initial_seeding.disable_bypass_warnings: tunable; set
818 non-zero to disable warnings in dmesg when the same conditions are
819 met as for the diagnostic sysctls above. Defaults to zero, i.e.,
820 produce warnings in dmesg when the conditions are met.
823 The loadable random module KPI has changed; the random_infra_init()
824 routine now requires a 3rd function pointer for a bool (*)(void)
825 method that returns true if the random device is seeded (and
826 therefore unblocked).
829 r345895 reverts r320698. This implies that an nfsuserd(8) daemon
830 built from head sources between r320757 (July 6, 2017) and
831 r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
832 is added to the command line.
833 nfsuserd daemons built from head sources that are post-r338192 are
834 not affected and should continue to work.
837 The fuse(4) module has been renamed to fusefs(4) for consistency with
838 other filesystems. You should update any kld_load="fuse" entries in
839 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
840 "options FUSE" entries in kernel config files.
843 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
844 8.0.0. Please see the 20141231 entry below for information about
845 prerequisites and upgrading, if you are not already using clang 3.5.0
849 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
850 compiled into your custom kernel, add 'device xz' statement to the
854 drm and drm2 have been removed from the tree. Please see
855 https://wiki.freebsd.org/Graphics for the latest information on
856 migrating to the drm ports.
859 Iflib is no longer unconditionally compiled into the kernel. Drivers
860 using iflib and statically compiled into the kernel, now require
861 the 'device iflib' config option. For the same drivers loaded as
862 modules on kernels not having 'device iflib', the iflib.ko module
863 is loaded automatically.
866 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
867 options no longer exist since r343219 and r343427 respectively;
868 nothing uses them, so they should be just removed from custom
872 r342635 changes the way efibootmgr(8) works by requiring users to add
873 the -b (bootnum) parameter for commands where the bootnum was previously
874 specified with each option. For example 'efibootmgr -B 0001' is now
875 'efibootmgr -B -b 0001'.
878 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
879 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
880 servers that have vfs.nfsd.nfs_privport set will only allow mounts
881 from clients using a reserved port. Since both the FreeBSD and Linux
882 NFSv4 clients use reserved ports by default, this should not affect
886 The XLP config has been removed. We can't support 64-bit atomics in this
887 kernel because it is running in 32-bit mode. XLP users must transition
888 to running a 64-bit kernel (XLP64 or XLPN32).
890 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
891 the preferred emulator today and we don't need two different ones.
893 The old sibyte / swarm / Broadcom BCM1250 support has been
894 removed from the mips port.
897 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
898 7.0.1. Please see the 20141231 entry below for information about
899 prerequisites and upgrading, if you are not already using clang 3.5.0
903 Remove the timed and netdate programs from the base tree. Setting
904 the time with these daemons has been obsolete for over a decade.
907 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
908 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
909 it produces broken binaries when ifuncs are in use. Users needing
910 GNU ld should install the binutils port or package.
913 The BSD crtbegin and crtend code has been enabled by default. It has
914 had extensive testing on amd64, arm64, and i386. It can be disabled
915 by building a world with -DWITHOUT_BSD_CRTBEGIN.
918 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
919 has been converted to a port (misc/ctm) and will be removed from
920 FreeBSD-13. It is available as a package (ctm) for all supported
924 The default newsyslog.conf(5) file has been changed to only include
925 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
926 the filenames end in '.conf' and do not begin with a '.'.
928 You should check the configuration files in these two directories match
929 this naming convention. You can verify which configuration files are
930 being included using the command:
934 Ports for the DRM modules have been simplified. Now, amd64 users should
935 just install the drm-kmod port. All others should install
938 Graphics hardware that's newer than about 2010 usually works with
939 drm-kmod. For hardware older than 2013, however, some users will need
940 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
941 than 2008 usually only works in drm-legacy-kmod. The graphics team can
942 only commit to hardware made since 2013 due to the complexity of the
943 market and difficulty to test all the older cards effectively. If you
944 have hardware supported by drm-kmod, you are strongly encouraged to use
945 that as you will get better support.
947 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
948 elsewhere, the drm and drm2 modules will be eliminated from the src base
949 soon (with a limited exception for arm). Please update to the package
950 asap and report any issues to x11@freebsd.org.
952 Generally, anybody using the drm*-kmod packages should add
953 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
954 cross-threading surprises, especially with automatic driver
955 loading from X11 startup. These will become the defaults in 13-current
959 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
960 custom kernel and module loading configuration files must be updated
961 accordingly. Moreover, interfaces previous presented as ixlvN to the
962 system are now exposed as iavfN and network configuration files must
963 be adjusted as necessary.
966 OpenSSL has been updated to version 1.1.1. This update included
967 additional various API changes throughout the base system. It is
968 important to rebuild third-party software after upgrading. The value
969 of __FreeBSD_version has been bumped accordingly.
972 The legacy DRM modules and drivers have now been added to the loader's
973 module blacklist, in favor of loading them with kld_list in rc.conf(5).
974 The module blacklist may be overridden with the loader.conf(5)
975 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
979 The cam(4) based nda(4) driver will be used over nvd(4) by default on
980 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
981 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
982 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
986 Reproducible build mode is now on by default, in preparation for
987 FreeBSD 12.0. This eliminates build metadata such as the user,
988 host, and time from the kernel (and uname), unless the working tree
989 corresponds to a modified checkout from a version control system.
990 The previous behavior can be obtained by setting the /etc/src.conf
991 knob WITHOUT_REPRODUCIBLE_BUILD.
994 The Yarrow CSPRNG has been removed from the kernel as it has not been
995 supported by its designers since at least 2003. Fortuna has been the
996 default since FreeBSD-11.
999 devctl freeze/thaw have gone into the tree, the rc scripts have been
1000 updated to use them and devmatch has been changed. You should update
1001 kernel, userland and rc scripts all at the same time.
1004 The default interpreter has been switched from 4th to Lua.
1005 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
1006 interpreter. If you have custom FORTH code you will need to set
1007 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
1008 src.conf for the build. This will create default hard links between
1009 loader and loader_4th instead of loader and loader_lua, the new default.
1010 If you are using UEFI it will create the proper hard link to loader.efi.
1012 bhyve uses userboot.so. It remains 4th-only until some issues are solved
1013 regarding coexisting with multiple versions of FreeBSD are resolved.
1016 ls(1) now respects the COLORTERM environment variable used in other
1017 systems and software to indicate that a colored terminal is both
1018 supported and desired. If ls(1) is suddenly emitting colors, they may
1019 be disabled again by either removing the unwanted COLORTERM from your
1020 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
1021 may not be observed in a future release.
1024 The default pager for most commands has been changed to "less". To
1025 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
1029 The jedec_ts(4) driver has been removed. A superset of its functionality
1030 is available in the jedec_dimm(4) driver, and the manpage for that
1031 driver includes migration instructions. If you have "device jedec_ts"
1032 in your kernel configuration file, it must be removed.
1035 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
1036 This should have no effect if the kernel is booted via BIOS/legacy boot.
1037 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
1038 has a buggy firmware that prevents a successful boot due to use of
1042 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
1043 support has been removed from the tree. These ports were
1044 obsolete and/or known to be broken for many years.
1047 loader.efi has been augmented to participate more fully in the
1048 UEFI boot manager protocol. loader.efi will now look at the
1049 BootXXXX environment variable to determine if a specific kernel
1050 or root partition was specified. XXXX is derived from BootCurrent.
1051 efibootmgr(8) manages these standard UEFI variables.
1054 zfsloader's functionality has now been folded into loader.
1055 zfsloader is no longer necessary once you've updated your
1056 boot blocks. For a transition period, we will install a
1057 hardlink for zfsloader to loader to allow a smooth transition
1058 until the boot blocks can be updated (hard link because old
1059 zfs boot blocks don't understand symlinks).
1062 ARM64 now have efifb support, if you want to have serial console
1063 on your arm64 board when an screen is connected and the bootloader
1064 setup a frame buffer for us to use, just add :
1067 in /boot/loader.conf
1068 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
1069 an screen connected as the firmware will setup a frame buffer are that
1070 u-boot will expose as an EFI frame buffer.
1073 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
1074 or take steps to update /etc/passwd before doing installworld on
1075 existing systems. Do not skip the "mergemaster -Fp" step before
1076 installworld, as described in the update procedures near the bottom
1077 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
1078 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
1079 the ntp config file contain options that change file/dir locations.
1080 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
1081 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
1082 taking steps to ensure that all required files/dirs are accessible
1086 Big endian arm support has been removed.
1089 The static environment setup in kernel configs is no longer mutually
1090 exclusive with the loader(8) environment by default. In order to
1091 restore the previous default behavior of disabling the loader(8)
1092 environment if a static environment is present, you must specify
1093 loader_env.disabled=1 in the static environment.
1096 The ABI of syscalls used by management tools like sockstat and
1097 netstat has been broken to allow 32-bit binaries to work on
1098 64-bit kernels without modification. These programs will need
1099 to match the kernel in order to function. External programs may
1100 require minor modifications to accommodate a change of type in
1101 structures from pointers to 64-bit virtual addresses.
1104 On i386 and amd64 atomics are now inlined. Out of tree modules using
1105 atomics will need to be rebuilt.
1108 The '%I' format in the kern.corefile sysctl limits the number of
1109 core files that a process can generate to the number stored in the
1110 debug.ncores sysctl. The '%I' format is replaced by the single digit
1111 index. Previously, if all indexes were taken the kernel would overwrite
1112 only a core file with the highest index in a filename.
1113 Currently the system will create a new core file if there is a free
1114 index or if all slots are taken it will overwrite the oldest one.
1117 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
1118 6.0.1. Please see the 20141231 entry below for information about
1119 prerequisites and upgrading, if you are not already using clang 3.5.0
1123 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
1124 needed to be changed to work with it. This change was made with r335763
1125 and requires a mergemaster / etcupdate / etc to update the installed
1129 r334930 changed the interface between the NFS modules, so they all
1130 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
1133 As of r334391 lld is the default amd64 system linker; it is installed
1134 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
1138 The kernel / userland interface for devinfo changed, so you'll
1139 need a new kernel and userland as a pair for it to work (rebuilding
1140 lib/libdevinfo is all that's required). devinfo and devmatch will
1141 not work, but everything else will when there's a mismatch.
1144 The on-disk format for hwpmc callchain records has changed to include
1145 threadid corresponding to a given record. This changes the field offsets
1146 and thus requires that libpmcstat be rebuilt before using a kernel
1150 The vxge(4) driver has been removed. This driver was introduced into
1151 HEAD one week before the Exar left the Ethernet market and is not
1152 known to be used. If you have device vxge in your kernel config file
1156 The amd64 kernel now requires a ld that supports ifunc to produce a
1157 working kernel, either lld or a newer binutils. lld is built by default
1158 on amd64, and the 'buildkernel' target uses it automatically. However,
1159 it is not the default linker, so building the kernel the traditional
1160 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
1161 binutils port/package). lld will soon be default, and this requirement
1164 NOTE: As of r334391 lld is the default system linker on amd64, and no
1165 workaround is necessary.
1168 The nxge(4) driver has been removed. This driver was for PCI-X 10g
1169 cards made by s2io/Neterion. The company was acquired by Exar and
1170 no longer sells or supports Ethernet products. If you have device
1171 nxge in your kernel config file it must be removed.
1174 The tz database (tzdb) has been updated to 2018e. This version more
1175 correctly models time stamps in time zones with negative DST such as
1176 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
1177 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
1178 time zone abbreviations and the tm_isdst flag.
1181 The ixgb(4) driver has been removed. This driver was for an early and
1182 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
1183 quickly shifted to the long lived ixgbe family. If you have device
1184 ixgb in your kernel config file it must be removed.
1187 The lmc(4) driver has been removed. This was a WAN interface
1188 card that was already reportedly rare in 2003, and had an ambiguous
1189 license. If you have device lmc in your kernel config file it must
1193 Support for Arcnet networks has been removed. If you have device
1194 arcnet or device cm in your kernel config file they must be
1198 Support for FDDI networks has been removed. If you have device
1199 fddi or device fpa in your kernel config file they must be
1203 In addition to supporting RFC 3164 formatted messages, the
1204 syslogd(8) service is now capable of parsing RFC 5424 formatted
1205 log messages. The main benefit of using RFC 5424 is that clients
1206 may now send log messages with timestamps containing year numbers,
1207 microseconds and time zone offsets.
1209 Similarly, the syslog(3) C library function has been altered to
1210 send RFC 5424 formatted messages to the local system logging
1211 daemon. On systems using syslogd(8), this change should have no
1212 negative impact, as long as syslogd(8) and the C library are
1213 updated at the same time. On systems using a different system
1214 logging daemon, it may be necessary to make configuration
1215 adjustments, depending on the software used.
1217 When using syslog-ng, add the 'syslog-protocol' flag to local
1218 input sources to enable parsing of RFC 5424 formatted messages:
1221 unix-dgram("/var/run/log" flags(syslog-protocol));
1224 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
1225 of the 'imuxsock' module to let messages be processed by the
1226 regular RFC 3164/5424 parsing pipeline:
1228 module(load="imuxsock" SysSock.UseSpecialParser="off")
1230 Do note that these changes only affect communication between local
1231 applications and syslogd(8). The format that syslogd(8) uses to
1232 store messages on disk or forward messages to other systems
1233 remains unchanged. syslogd(8) still uses RFC 3164 for these
1234 purposes. Options to customize this behaviour will be added in the
1235 future. Utilities that process log files stored in /var/log are
1236 thus expected to continue to function as before.
1238 __FreeBSD_version has been incremented to 1200061 to denote this
1242 Support for token ring networks has been removed. If you
1243 have "device token" in your kernel config you should remove
1244 it. No device drivers supported token ring.
1247 makefs was modified to be able to tag ISO9660 El Torito boot catalog
1248 entries as EFI instead of overloading the i386 tag as done previously.
1249 The amd64 mkisoimages.sh script used to build amd64 ISO images for
1250 release was updated to use this. This may mean that makefs must be
1251 updated before "make cdrom" can be run in the release directory. This
1252 should be as simple as:
1254 $ cd $SRCDIR/usr.sbin/makefs
1255 $ make depend all install
1258 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
1259 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
1260 Co-existence for the transition period will come shortly. Booting is a
1261 complex environment and test coverage for Lua-enabled loaders has been
1262 thin, so it would be prudent to assume it might not work and make
1263 provisions for backup boot methods.
1266 devmatch functionality has been turned on in devd. It will automatically
1267 load drivers for unattached devices. This may cause unexpected drivers
1268 to be loaded. Please report any problems to current@ and
1272 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
1273 6.0.0. Please see the 20141231 entry below for information about
1274 prerequisites and upgrading, if you are not already using clang 3.5.0
1278 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
1279 This means it is used to link the kernel and userland libraries and
1280 executables, but is not yet installed as /usr/bin/ld by default.
1282 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
1283 WITHOUT_LLD_BOOTSTRAP=yes
1286 On i386, pmtimer has been removed. Its functionality has been folded
1287 into apm. It was a no-op on ACPI in current for a while now (but was
1288 still needed on i386 in FreeBSD 11 and earlier). Users may need to
1289 remove it from kernel config files.
1292 The use of RSS hash from the network card aka flowid has been
1293 disabled by default for lagg(4) as it's currently incompatible with
1294 the lacp and loadbalance protocols.
1296 This can be re-enabled by setting the following in loader.conf:
1297 net.link.lagg.default_use_flowid="1"
1300 The SW_WATCHDOG option is no longer necessary to enable the
1301 hardclock-based software watchdog if no hardware watchdog is
1302 configured. As before, SW_WATCHDOG will cause the software
1303 watchdog to be enabled even if a hardware watchdog is configured.
1306 r326887 fixes the issue described in the 20171214 UPDATING entry.
1307 r326888 flips the switch back to building GELI support always.
1310 r362593 broke ZFS + GELI support for reasons unknown. However,
1311 it also broke ZFS support generally, so GELI has been turned off
1312 by default as the lesser evil in r326857. If you boot off ZFS and/or
1313 GELI, it might not be a good time to update.
1316 PowerPC users must update loader(8) by rebuilding world before
1317 installing a new kernel, as the protocol connecting them has
1318 changed. Without the update, loader metadata will not be passed
1319 successfully to the kernel and users will have to enter their
1320 root partition at the kernel mountroot prompt to continue booting.
1321 Newer versions of loader can boot old kernels without issue.
1324 The LOADER_FIREWIRE_SUPPORT build variable has been renamed to
1325 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
1326 to WITH/OUT_LOADER_GELI.
1329 The naive and non-compliant support of posix_fallocate(2) in ZFS
1330 has been removed as of r325320. The system call now returns EINVAL
1331 when used on a ZFS file. Although the new behavior complies with the
1332 standard, some consumers are not prepared to cope with it.
1333 One known victim is lld prior to r325420.
1336 Building in a FreeBSD src checkout will automatically create object
1337 directories now rather than store files in the current directory if
1338 'make obj' was not ran. Calling 'make obj' is no longer necessary.
1339 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
1340 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
1344 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
1345 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
1346 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
1347 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
1348 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
1349 The UNIFIED_OBJDIR option is a transitional feature that will be
1350 removed for 12.0 release; please migrate to the new format for any
1351 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
1352 than hardcoding paths.
1355 The native-xtools target no longer installs the files by default to the
1356 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
1357 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
1360 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
1361 options are changing from controlling the build if defined / undefined
1362 to controlling the build with explicit 'yes' or 'no' values. They will
1363 shift to WITH/WITHOUT options to match other options in the system.
1366 libstand has turned into a private library for sys/boot use only.
1367 It is no longer supported as a public interface outside of sys/boot.
1370 The arm port has split armv6 into armv6 and armv7. armv7 is now
1371 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
1372 and are running a kernel from before r324363, you will need to add
1373 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
1376 When building multiple kernels using KERNCONF, non-existent KERNCONF
1377 files will produce an error and buildkernel will fail. Previously
1378 missing KERNCONF files silently failed giving no indication as to
1379 why, only to subsequently discover during installkernel that the
1380 desired kernel was never built in the first place.
1383 The default serial number format for CTL LUNs has changed. This will
1384 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
1385 or iSCSI clients care about their LUNs' serial numbers. Users who
1386 require serial number stability should hardcode serial numbers in
1390 For 32-bit arm compiled for hard-float support, soft-floating point
1391 binaries now always get their shared libraries from
1392 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
1393 /usr/libsoft also existed). Only users with a hard-float ld.so, but
1394 soft-float everything else should be affected.
1397 The geli password typed at boot is now hidden. To restore the previous
1398 behavior, see geli(8) for configuration options.
1401 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
1402 sysctl values. Minor nit, but requires a rebuild of both world/kernel
1406 "make check" behavior (made in ^/head@r295380) has been changed to
1407 execute from a limited sandbox, as opposed to executing from
1411 - The "beforecheck" and "aftercheck" targets are now specified.
1412 - ${CHECKDIR} (added in commit noted above) has been removed.
1413 - Legacy behavior can be enabled by setting
1414 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
1416 If the limited sandbox mode is enabled, "make check" will execute
1417 "make distribution", then install, execute the tests, and clean up the
1418 sandbox if successful.
1420 The "make distribution" and "make install" targets are typically run as
1421 root to set appropriate permissions and ownership at installation time.
1422 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
1423 environment if executing "make check" with limited sandbox mode using
1424 an unprivileged user.
1427 Since the switch to GPT disk labels, fsck for UFS/FFS has been
1428 unable to automatically find alternate superblocks. As of r322297,
1429 the information needed to find alternate superblocks has been
1430 moved to the end of the area reserved for the boot block.
1431 Filesystems created with a newfs of this vintage or later
1432 will create the recovery information. If you have a filesystem
1433 created prior to this change and wish to have a recovery block
1434 created for your filesystem, you can do so by running fsck in
1435 foreground mode (i.e., do not use the -p or -y options). As it
1436 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
1437 to which you should answer yes.
1440 As of r321665, an NFSv4 server configuration that services
1441 Kerberos mounts or clients that do not support the uid/gid in
1442 owner/owner_group string capability, must explicitly enable
1443 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
1444 machine's /etc/rc.conf file.
1447 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
1448 Please see the 20141231 entry below for information about prerequisites
1449 and upgrading, if you are not already using clang 3.5.0 or higher.
1452 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
1453 r-commands (rlogin, rsh, etc.) to be built with the base system.
1456 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
1457 a very major ABI incompatible change, so users of FreeBSD/powerpc must
1458 be careful when performing source upgrades. It is best to run
1459 'make installworld' from an alternate root system, either a live
1460 CD/memory stick, or a temporary root partition. Additionally, all ports
1461 must be recompiled. powerpc64 is largely unaffected, except in the case
1462 of 32-bit compatibility. All 32-bit binaries will be affected.
1465 Forward compatibility for the "ino64" project have been committed. This
1466 will allow most new binaries to run on older kernels in a limited
1467 fashion. This prevents many of the common foot-shooting actions in the
1468 upgrade as well as the limited ability to roll back the kernel across
1469 the ino64 upgrade. Complicated use cases may not work properly, though
1470 enough simpler ones work to allow recovery in most situations.
1473 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
1474 if you require the GPL compiler.
1477 The internal ABI used for communication between the NFS kernel modules
1478 was changed by r320085, so __FreeBSD_version was bumped to
1479 ensure all the NFS related modules are updated together.
1482 The ABI of struct event was changed by extending the data
1483 member to 64bit and adding ext fields. For upgrade, same
1484 precautions as for the entry 20170523 "ino64" must be
1488 The GNU roff toolchain has been removed from base. To render manpages
1489 which are not supported by mandoc(1), man(1) can fallback on GNU roff
1490 from ports (and recommends to install it).
1491 To render roff(7) documents, consider using GNU roff from ports or the
1492 heirloom doctools roff toolchain from ports via pkg install groff or
1493 via pkg install heirloom-doctools.
1496 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
1497 smaller runtime footprint builds. This is useful for embedded systems
1498 which only require one chipset support.
1500 If you load it as a module, make sure this is in /boot/loader.conf:
1504 This will load the HAL, all chip/RF backends and if_ath_pci.
1505 If you have if_ath_pci in /boot/loader.conf, ensure it is after
1506 if_ath or it will not load any HAL chipset support.
1508 If you want to selectively load things (eg on cheaper ARM/MIPS
1509 platforms where RAM is at a premium) you should:
1512 * load the chip modules in question
1513 * load ath_rate, ath_dfs
1515 * load if_ath_pci and/or if_ath_ahb depending upon your particular
1516 bus bind type - this is where probe/attach is done.
1518 For further comments/feedback, poke adrian@ .
1521 The "ino64" 64-bit inode project has been committed, which extends
1522 a number of types to 64 bits. Upgrading in place requires care and
1523 adherence to the documented upgrade procedure.
1525 If using a custom kernel configuration ensure that the
1526 COMPAT_FREEBSD11 option is included (as during the upgrade the
1527 system will be running the ino64 kernel with the existing world).
1529 For the safest in-place upgrade begin by removing previous build
1530 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full
1531 procedure documented below under the heading "To rebuild everything and
1532 install it on the current system." Specifically, a reboot is required
1533 after installing the new kernel before installing world. While an
1534 installworld normally works by accident from multiuser after rebooting
1535 the proper kernel, there are many cases where this will fail across this
1536 upgrade and installworld from single user is required.
1539 The NATM framework including the en(4), fatm(4), hatm(4), and
1540 patm(4) devices has been removed. Consumers should plan a
1541 migration before the end-of-life date for FreeBSD 11.
1544 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
1545 diff has not been implemented, if those are needed a newer version of
1546 GNU diff is available via the diffutils package under the gdiff name.
1549 As of r316810 for ipfilter, keep frags is no longer assumed when
1550 keep state is specified in a rule. r316810 aligns ipfilter with
1551 documentation in man pages separating keep frags from keep state.
1552 This allows keep state to be specified without forcing keep frags
1553 and allows keep frags to be specified independently of keep state.
1554 To maintain previous behaviour, also specify keep frags with
1555 keep state (as documented in ipf.conf.5).
1558 arm64 builds now use the base system LLD 4.0.0 linker by default,
1559 instead of requiring that the aarch64-binutils port or package be
1560 installed. To continue using aarch64-binutils, set
1561 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
1564 The UDP optimization in entry 20160818 that added the sysctl
1565 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
1566 packets will no longer be treated as L3 broadcast packets.
1569 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
1570 use any explicitly assigned loopback address available in the jail
1571 instead of using the first assigned address of the jail.
1574 The ctl.ko module no longer implements the iSCSI target frontend:
1575 cfiscsi.ko does instead.
1577 If building cfiscsi.ko as a kernel module, the module can be loaded
1578 via one of the following methods:
1579 - `cfiscsi_load="YES"` in loader.conf(5).
1580 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
1581 - ctladm(8)/ctld(8), when compiled with iSCSI support
1582 (`WITH_ISCSI=yes` in src.conf(5))
1584 Please see cfiscsi(4) for more details.
1587 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
1588 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
1589 same source (previously, the dependency of mmcsd.ko on mmc.ko was
1590 missing, but mmcsd.ko now will refuse to load if it is incompatible
1594 The syntax of ipfw(8) named states was changed to avoid ambiguity.
1595 If you have used named states in the firewall rules, you need to modify
1596 them after installworld and before rebooting. Now named states must
1597 be prefixed with colon.
1600 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
1601 removed as the userland we provide cannot use them. The KMS version
1602 (sys/dev/drm2) supports the same hardware.
1605 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
1606 Please see the 20141231 entry below for information about prerequisites
1607 and upgrading, if you are not already using clang 3.5.0 or higher.
1610 The code that provides support for ZFS .zfs/ directory functionality
1611 has been reimplemented. It's not possible now to create a snapshot
1612 by mkdir under .zfs/snapshot/. That should be the only user visible
1616 EISA bus support has been removed. The WITH_EISA option is no longer
1620 MCA bus support has been removed.
1623 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
1624 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
1627 The EM_MULTIQUEUE kernel configuration option is deprecated now that
1628 the em(4) driver conforms to iflib specifications.
1631 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
1632 IFLIB. If you have a custom kernel configuration that excludes em(4)
1633 but you use igb(4), you need to re-add em(4) to your custom
1637 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
1638 Please see the 20141231 entry below for information about prerequisites
1639 and upgrading, if you are not already using clang 3.5.0 or higher.
1642 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
1643 Please see the 20141231 entry below for information about prerequisites
1644 and upgrading, if you are not already using clang 3.5.0 or higher.
1647 The layout of the pmap structure has changed for powerpc to put the pmap
1648 statistics at the front for all CPU variations. libkvm(3) and all tools
1649 that link against it need to be recompiled.
1652 isl(4) and cyapa(4) drivers now require a new driver,
1653 chromebook_platform(4), to work properly on Chromebook-class hardware.
1654 On other types of hardware the drivers may need to be configured using
1655 device hints. Please see the corresponding manual pages for details.
1658 The urtwn(4) driver was merged into rtwn(4) and now consists of
1659 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
1661 Also, firmware for RTL8188CE was renamed due to possible name
1662 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
1665 GNU rcs has been removed from base. It is available as packages:
1666 - rcs: Latest GPLv3 GNU rcs version.
1667 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
1671 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
1672 modules now requires that the kernel configuration contain the
1673 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
1676 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
1677 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
1680 Relocatable object files with the extension of .So have been renamed
1681 to use an extension of .pico instead. The purpose of this change is
1682 to avoid a name clash with shared libraries on case-insensitive file
1683 systems. On those file systems, foo.So is the same file as foo.so.
1686 GNU rcs has been turned off by default. It can (temporarily) be built
1687 again by adding WITH_RCS knob in src.conf.
1688 Otherwise, GNU rcs is available from packages:
1689 - rcs: Latest GPLv3 GNU rcs version.
1690 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
1693 The backup_uses_rcs functionality has been removed from rc.subr.
1696 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
1697 two separate components, QUEUE_MACRO_DEBUG_TRACE and
1698 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
1699 QUEUE_MACRO_DEBUG behavior.
1702 r304787 changed some ioctl interfaces between the iSCSI userspace
1703 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1704 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1708 The UDP receive code has been updated to only treat incoming UDP
1709 packets that were addressed to an L2 broadcast address as L3
1710 broadcast packets. It is not expected that this will affect any
1711 standards-conforming UDP application. The new behaviour can be
1712 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1716 Remove the openbsd_poll system call.
1717 __FreeBSD_version has been bumped because of this.
1720 The stable/11 branch has been created from head@r302406.
1722 After branch N is created, entries older than the N-2 branch point are removed
1723 from this file. After stable/14 is branched and current becomes FreeBSD 15,
1724 entries older than stable/12 branch point will be removed from current's
1731 Sometimes, obscure build problems are the result of environment
1732 poisoning. This can happen because the make utility reads its
1733 environment when searching for values for global variables. To run
1734 your build attempts in an "environmental clean room", prefix all make
1735 commands with 'env -i '. See the env(1) manual page for more details.
1736 Occasionally a build failure will occur with "make -j" due to a race
1737 condition. If this happens try building again without -j, and please
1738 report a bug if it happens consistently.
1740 When upgrading from one major version to another it is generally best to
1741 upgrade to the latest code in the currently installed branch first, then
1742 do an upgrade to the new branch. This is the best-tested upgrade path,
1743 and has the highest probability of being successful. Please try this
1744 approach if you encounter problems with a major version upgrade. Since
1745 the stable 4.x branch point, one has generally been able to upgrade from
1746 anywhere in the most recent stable branch to head / current (or even the
1747 last couple of stable branches). See the top of this file when there's
1750 The update process will emit an error on an attempt to perform a build
1751 or install from a FreeBSD version below the earliest supported version.
1752 When updating from an older version the update should be performed one
1753 major release at a time, including running `make delete-old` at each
1756 When upgrading a live system, having a root shell around before
1757 installing anything can help undo problems. Not having a root shell
1758 around can lead to problems if pam has changed too much from your
1759 starting point to allow continued authentication after the upgrade.
1761 This file should be read as a log of events. When a later event changes
1762 information of a prior event, the prior event should not be deleted.
1763 Instead, a pointer to the entry with the new information should be
1764 placed in the old entry. Readers of this file should also sanity check
1765 older entries before relying on them blindly. Authors of new entries
1766 should write them with this in mind.
1770 When upgrading the boot ZFS pool to a new version (via zpool upgrade),
1771 always follow these three steps:
1773 1) recompile and reinstall the ZFS boot loader and boot block
1774 (this is part of "make buildworld" and "make installworld")
1776 2) update the ZFS boot block on your boot drive (only required when
1777 doing a zpool upgrade):
1779 When booting on x86 via BIOS, use the following to update the ZFS boot
1780 block on the freebsd-boot partition of a GPT partitioned drive ada0:
1781 gpart bootcode -p /boot/gptzfsboot -i $N ada0
1782 The value $N will typically be 1. For EFI booting, see EFI notes.
1784 3) zpool upgrade the root pool. New bootblocks will work with old
1785 pools, but not vice versa, so they need to be updated before any
1788 Non-boot pools do not need these updates.
1793 There are two locations the boot loader can be installed into. The
1794 current location (and the default) is \efi\freebsd\loader.efi and using
1795 efibootmgr(8) to configure it. The old location, that must be used on
1796 deficient systems that don't honor efibootmgr(8) protocols, is the
1797 fallback location of \EFI\BOOT\BOOTxxx.EFI. Generally, you will copy
1798 /boot/loader.efi to this location, but on systems installed a long time
1799 ago the ESP may be too small and /boot/boot1.efi may be needed unless
1800 the ESP has been expanded in the meantime.
1802 Recent systems will have the ESP mounted on /boot/efi, but older ones
1803 may not have it mounted at all, or mounted in a different
1804 location. Older arm SD images with MBR used /boot/msdos as the
1805 mountpoint. The ESP is a MSDOS filesystem.
1807 The EFI boot loader rarely needs to be updated. For ZFS booting,
1808 however, you must update loader.efi before you do 'zpool upgrade' the
1809 root zpool, otherwise the old loader.efi may reject the upgraded zpool
1810 since it does not automatically understand some new features.
1812 See loader.efi(8) and uefi(8) for more details.
1816 If you are updating from a prior version of FreeBSD (even one just
1817 a few days old), you should follow this procedure. It is the most
1818 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1820 make kernel-toolchain
1821 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1822 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1824 To test a kernel once
1825 ---------------------
1826 If you just want to boot a kernel once (because you are not sure
1827 if it works, or if you want to boot a known bad kernel to provide
1828 debugging information) run
1829 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1830 nextboot -k testkernel
1832 To rebuild everything and install it on the current system.
1833 -----------------------------------------------------------
1834 # Note: sometimes if you are running current you gotta do more than
1835 # is listed here if you are upgrading from a really old current.
1837 <make sure you have good level 0 dumps>
1839 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1840 make installkernel KERNCONF=YOUR_KERNEL_HERE
1842 <reboot in single user> [3]
1849 To cross-install current onto a separate partition
1850 --------------------------------------------------
1851 # In this approach we use a separate partition to hold
1852 # current's root, 'usr', and 'var' directories. A partition
1853 # holding "/", "/usr" and "/var" should be about 2GB in
1856 <make sure you have good level 0 dumps>
1859 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1860 <maybe newfs current's root partition>
1861 <mount current's root partition on directory ${CURRENT_ROOT}>
1862 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1863 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1864 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1865 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1866 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1867 <reboot into current>
1868 <do a "native" rebuild/install as described in the previous section>
1869 <maybe install compatibility libraries from ports/misc/compat*>
1873 To upgrade in-place from stable to current
1874 ----------------------------------------------
1875 <make sure you have good level 0 dumps>
1877 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1878 make installkernel KERNCONF=YOUR_KERNEL_HERE
1880 <reboot in single user> [3]
1887 Make sure that you've read the UPDATING file to understand the
1888 tweaks to various things you need. At this point in the life
1889 cycle of current, things change often and you are on your own
1890 to cope. The defaults can also change, so please read ALL of
1891 the UPDATING entries.
1893 Also, if you are tracking -current, you must be subscribed to
1894 freebsd-current@freebsd.org. Make sure that before you update
1895 your sources that you have read and understood all the recent
1896 messages there. If in doubt, please track -stable which has
1897 much fewer pitfalls.
1899 [1] If you have third party modules, such as vmware, you should disable
1900 them at this point so they don't crash your system on
1901 reboot. Alternatively, you should rebuild all the modules you have in
1902 your system and install them as well. If you are running -current, you
1903 should seriously consider placing all sources to all the modules for
1904 your system (or symlinks to them) in /usr/local/sys/modules so this
1905 happens automatically. If all your modules come from ports, then adding
1906 the port origin directories to PORTS_MODULES instead is also automatic
1908 PORTS_MODULES+=x11/nvidia-driver
1910 [3] From the bootblocks, boot -s, and then do
1914 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed
1915 cd src # full path to source
1916 adjkerntz -i # if CMOS is wall time
1917 Also, when doing a major release upgrade, it is required that you boot
1918 into single user mode to do the installworld.
1920 [4] Note: This step is non-optional. Failure to do this step
1921 can result in a significant reduction in the functionality of the
1922 system. Attempting to do it by hand is not recommended and those
1923 that pursue this avenue should read this file carefully, as well
1924 as the archives of freebsd-current and freebsd-hackers mailing lists
1925 for potential gotchas. See etcupdate(8) for more information.
1927 [5] Usually this step is a no-op. However, from time to time
1928 you may need to do this if you get unknown user in the following
1931 [6] This only deletes old files and directories. Old libraries
1932 can be deleted by "make delete-old-libs", but you have to make
1933 sure that no program is using those libraries anymore.
1935 [8] The new kernel must be able to run existing binaries used by an
1936 installworld. When upgrading across major versions, the new kernel's
1937 configuration must include the correct COMPAT_FREEBSD<n> option for
1938 existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure
1939 to do so may leave you with a system that is hard to boot to recover. A
1940 GENERIC kernel will include suitable compatibility options to run
1941 binaries from older branches. Note that the ability to run binaries
1942 from unsupported branches is not guaranteed.
1944 Make sure that you merge any new devices from GENERIC since the
1945 last time you updated your kernel config file. Options also
1946 change over time, so you may need to adjust your custom kernels
1949 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1950 "?=" instead of the "=" assignment operator, so that buildworld can
1951 override the CPUTYPE if it needs to.
1953 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1954 not on the command line, or in /etc/make.conf. buildworld will
1955 warn if it is improperly defined.
1958 This file contains a list, in reverse chronological order, of major
1959 breakages in tracking -current. It is not guaranteed to be a complete
1960 list of such breakages, and only contains entries since September 23, 2011.
1961 If you need to see UPDATING entries from before that date, you will need
1962 to fetch an UPDATING file from an older FreeBSD release.
1964 Copyright information:
1966 Copyright 1998-2009 M. Warner Losh <imp@FreeBSD.org>
1968 Redistribution, publication, translation and use, with or without
1969 modification, in full or in part, in any form or format of this
1970 document are permitted without further permission from the author.
1972 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1973 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1974 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1975 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1976 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1977 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1978 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1979 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1980 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1981 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1982 POSSIBILITY OF SUCH DAMAGE.
1984 Contact Warner Losh if you have any questions about your use of