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".)
34 Serial communication (in boot loaders, kernel, and userland) has
35 been changed to default to 115200 bps, in line with common industry
36 practice and typcial firmware serial console redirection
39 Note that the early x86 BIOS bootloader (i.e., boot0sio) does not
40 support rates above 9600 bps and is not changed. boot0sio users may
41 set BOOT_COMCONSOLE_SPEED=9600 to use 9600 for all of the boot
42 components, or use the standard boot0 and have the boot2 stage start
43 with the serial port at 115200.
46 Following the general removal of MIPS support, the ath(4) AHB bus-
47 frontend has been removed, too, and building of the PCI support is
48 integrated with the ath(4) main module again. As a result, there's
49 no longer a need for if_ath_pci_load="YES" in /boot/loader.conf or
50 "device ath_pci" in the kernel configuration.
53 MAXCPU has been increased to 1024 in the amd64 GENERIC kernel config.
54 Out-of-tree kernel modules will need to be rebuilt.
57 CAM has been mechanically updated s/u_int(64|32|16|8)_t/uint\1_t/g
58 to move to the standard uintXX_t types from the old, traditional
59 BSD u_intXX_t types. This should be a NOP, but may cause problems
60 for out of tree changes. The SIMs were not updated since most of
61 the old u_intXX_t uses weren't due to CAM interfaces.
64 The heuristic for detecting old chromebooks with an EC bug that requires
65 atkbdc driver workarounds has changed. There should be no functional
66 change, but if your old chromebook's keyboard stops working, please
67 file a PR and assign it to imp.
70 OpenSSL has been updated to version 3.0, including changes throughout
71 the base system. It is important to rebuild third-party software
75 To enable pf rdr rules for connections initiated from the host, pf
76 filter rules can be optionally enabled for packets delivered
77 locally. This can change the behavior of rules which match packets
78 delivered to lo0. To enable this feature:
80 sysctl net.pf.filter_local=1
83 When enabled, its best to ensure that packets delivered locally are not
84 filtered, e.g. by adding a 'skip on lo' rule.
87 Improvements to libtacplus(8) mean that tacplus.conf(5) now
88 follows POSIX shell syntax rules. This may cause TACACS+
89 authentication to fail if the shared secret contains a single
90 quote, double quote, or backslash character which isn't
91 already properly quoted or escaped.
94 Belatedly switch the default nvme block device on x86 from nvd to nda.
95 nda created nvd compatibility links by default, so this should be a
96 nop. If this causes problems for your application, set hw.nvme.use_nvd=1
97 in your loader.conf or add `options NVME_USE_NVD=1` to your kernel
98 config. To disable the nvd compatibility aliases, add
99 kern.cam.nda.nvd_compat=0 to loader.conf. The default has been nda on
100 all non-x86 platforms for some time now. If you need to fall back,
101 please email imp@freebsd.org about why.
103 Encrypted swap partitions need to be changed from nvd to nda if you
104 migrate, or you need to use the above to switch back to nvd.
107 Remove portsnap(8). Users are encouraged to obtain the ports tree
111 Add jobs.mk to save typing. Enables -j${JOB_MAX} and logging
115 make -j${JOB_MAX} buildworld > ../buildworld.log 2>&1
117 where JOB_MAX is derrived from ncpus in local.sys.mk if not set in env.
120 Video related devices for some arm devices have been renamed.
121 If you have a custom kernel config and want to use hdmi output on
122 IMX6 board you need to add "device dwc_hdmi" "device imx6_hdmi" and
123 "device imx6_ipu" to it.
124 If you have a custom kernel config and want to use hdmi output on
125 TI AM335X board you need to add "device tda19988" to it.
126 If you add "device hdmi" in it you need to remove it as it doesn't
130 Introduce new kernel options KBD_DELAY1 and KBD_DELAY2. See atkbdc(4)
134 sshd now defaults to having X11Forwarding disabled, following upstream.
135 Administrators who wish to enable X11Forwarding should add
136 `X11Forwarding yes` to /etc/ssh/sshd_config.
139 Since commit 75d41cb6967 Huawei 3G/4G LTE Mobile Devices do not default
140 to ECM, but NCM mode and need u3g and ucom modules loaded. See cdce(4).
143 As of commit 7c40e2d5f685, the dependency on netlink(4) has been added
144 to the linux_common(4) module. Users relying on linux_common may need
145 to complile netlink(4) module if it is not present in their kernel.
148 The WITHOUT_CXX option has been removed. C++ components in the base
149 system are now built unconditionally.
152 LinuxKPI pci.h changes may require out-of-tree drivers to be recompiled.
153 Bump _FreeBSD_version to 1400078 to be able to detect this change.
156 llvm-objump is now always installed as objdump. Previously there was
157 no /usr/bin/objdump unless the WITH_LLVM_BINUTILS knob was used.
159 Some LLVM objdump options have a different output format compared to
160 GNU objdump; readelf is available for inspecting ELF files, and GNU
161 objdump is available from the devel/binutils port or package.
164 dma(8) has replaced sendmail(8) as the default mta. For people willing
165 to reenable sendmail(8):
167 $ cp /usr/share/examples/sendmail/mailer.conf /etc/mail/mailer.conf
169 and add sendmail_enable="YES" to rc.conf.
172 hw.bus.disable_failed_devices has changed from 'false' to 'true' by
173 default. Now if newbus succeeds in probing a device, but fails to attach
174 the device, we'll disable the device. In the past, we'd keep retrying
175 the device on each new driver loaded. To get that behavior now, one
176 needs to use devctl to re-enable the device, and reprobe it (or set
177 the sysctl/tunable hw.bus.disable_failed_devices=false).
179 NOTE: This was reverted 20221205 due to unexpected compatibility issues
182 pf no longer accepts 'scrub fragment crop' or 'scrub fragment drop-ovl'.
183 These configurations are no longer automatically reinterpreted as
184 'scrub fragment reassemble'.
187 The WITHOUT_CLANG_IS_CC option has been removed. When Clang is enabled
188 it is always installed as /usr/bin/cc (and c++, cpp).
191 Some programs have been moved into separate packages. It is recommended
192 for pkgbase users to do:
194 pkg install FreeBSD-dhclient FreeBSD-geom FreeBSD-resolvconf \
195 FreeBSD-devd FreeBSD-devmatch
197 after upgrading to restore all the component that were previously
201 LinuxKPI pm.h changes require an update to the latest drm-kmod version
202 before re-compiling to avoid errors.
205 The macros provided for the manipulation of CPU sets (e.g. CPU_AND)
206 have been modified to take 2 source arguments instead of only 1.
207 Externally maintained sources that use these macros will have to
208 be adapted. The FreeBSD version has been bumped to 1400046 to
212 A number of the kernel include files are able to be included by
213 themselves. A test has been added to buildworld to enforce this.
216 Remove mips as a recognized target. This starts the decommissioning of
217 mips support in FreeBSD. mips related items will be removed wholesale in
218 the coming days and weeks.
220 This broke the NO_CLEAN build for some people. Either do a clean build
222 lib/clang/include/llvm/Config/Targets.def
223 lib/clang/include/llvm/Config/AsmParsers.def
224 lib/clang/include/llvm/Config/Disassemblers.def
225 lib/clang/include/llvm/Config/AsmPrinters.def
226 before the build to force everything to rebuild that needs to.
229 Unbound support for RFC8375: The special-use domain 'home.arpa' is
230 by default blocked. To unblock it use a local-zone nodefault
231 statement in unbound.conf:
232 local-zone: "home.arpa." nodefault
234 Or use another type of local-zone to override with your choice.
236 The reason for this is discussed in Section 6.1 of RFC8375:
237 Because 'home.arpa.' is not globally scoped and cannot be secured
238 using DNSSEC based on the root domain's trust anchor, there is no way
239 to tell, using a standard DNS query, in which homenet scope an answer
240 belongs. Consequently, users may experience surprising results with
241 such names when roaming to different homenets.
244 Commit b8d60729deef changed the TCP congestion control framework so
245 that any of the included congestion control modules could be
246 the single module built into the kernel. Previously newreno
247 was automatically built in through direct reference. As of
248 this commit you are required to declare at least one congestion
249 control module (e.g. 'options CC_NEWRENO') and to also declare a
250 default using the CC_DEFAULT option (e.g. options CC_DEFAULT="newreno\").
251 The GENERIC configuration includes CC_NEWRENO and defines newreno
252 as the default. If no congestion control option is built into the
253 kernel and you are including networking, the kernel compile will
254 fail. Also if no default is declared the kernel compile will fail.
257 Mips has been removed from universe builds. It will be removed from the
261 Commit f0c9847a6c47 changed the arguments for VOP_ALLOCATE.
262 The NFS modules must be rebuilt from sources and any out
263 of tree file systems that implement their own VOP_ALLOCATE
264 may need to be modified.
267 The synchronous PPP kernel driver sppp(4) has been removed.
268 The cp(4) and ce(4) drivers are now always compiled with netgraph(4)
269 support, formerly enabled by NETGRAPH_CRONYX option.
272 sh(1) is now the default shell for the root user. To force root to use
273 the csh shell, please run the following command as root:
278 Ncurses distribution has been split between libtinfow and libncurses
279 with libncurses.so becoming a linker (ld) script to seamlessly link
280 to libtinfow as needed. Bump _FreeBSD_version to 1400035 to reflect
284 As of commit 8160a0f62be6, the dummynet module no longer depends on the
285 ipfw module. Dummynet can now be used by pf as well as ipfw. As such
286 users who relied on this dependency may need to include ipfw in the
287 list of modules to load on their systems.
290 As of commit 903873ce1560, the mixer(8) utility has got a slightly
291 new syntax. Please refer to the mixer(8) manual page for more
292 information. The old mixer utility can be installed from ports:
293 audio/freebsd-13-mixer
296 As of commit 55089ef4f8bb, the global variable nfs_maxcopyrange has
297 been deleted from the nfscommon.ko. As such, nfsd.ko must be built
298 from up to date sources to avoid an undefined reference when
302 As of commit 62ca9fc1ad56 OpenSSL no longer enables kernel TLS
303 by default. Users can enable kernel TLS via the "KTLS" SSL
304 option. This can be enabled globally by using a custom
305 OpenSSL config file via OPENSSL_CONF or via an
306 application-specific configuration option for applications
307 which permit setting SSL options via SSL_CONF_cmd(3).
310 Commit 3ad1e1c1ce20 changed the internal KAPI between the NFS
311 modules. Therefore, all need to be rebuilt from sources.
314 Commit b69019c14cd8 removes pf's DIOCGETSTATESNV ioctl.
315 As of be70c7a50d32 it is no longer used by userspace, but it does mean
316 users may not be able to enumerate pf states if they update the kernel
317 past b69019c14cd8 without first updating userspace past be70c7a50d32.
320 As of commit 01ad0c007964 if_bridge member interfaces can no longer
321 change their MTU. Changing the MTU of the bridge itself will change the
322 MTU on all member interfaces instead.
325 Commit ee29e6f31111 changed the internal KAPI between the nfscommon
326 and nfsd modules. Therefore, both need to be rebuilt from sources.
327 Bump __FreeBSD_version to 1400026 for this KAPI change.
330 The 20210707 awk update brought in a change in behavior. This has
331 been corrected as of d4d252c49976. Between these dates, if you
332 installed a new awk binary, you may not be able to build a new
333 kernel because the change in behavior affected the genoffset
334 script used to build the kernel. If you did update, the fix is
335 to update your sources past the above hash and do
338 % sudo -E make install
339 to enable building kernels again.
342 Commit 1e0a518d6548 changed the internal KAPI between the NFS
343 modules. They all need to be rebuilt from sources. I did not
344 bump __FreeBSD_version, since it was bumped recently.
347 awk has been updated to the latest one-true-awk version 20210215.
348 This contains a number of minor bug fixes.
351 The NFSv4 client now uses the highest minor version of NFSv4
352 supported by the NFSv4 server by default instead of minor version 0,
354 The "minorversion" mount option may be used to override this default.
357 Bump __FreeBSD_version to 1400024 for LinuxKPI changes.
358 Most notably netdev.h can change now as the (last) dependencies
359 (mlx4/ofed) are now using struct ifnet directly, but also for PCI
360 additions and others.
363 The directory "blacklisted" under /usr/share/certs/ has been
364 renamed to "untrusted".
367 svnlite has been removed from base. Should you need svn for any reason
368 please install the svn package or port.
371 Commit e1a907a25cfa changed the internal KAPI between the krpc
372 and nfsserver. As such, both modules must be rebuilt from
373 sources. Bump __FreeBSD_version to 1400022.
376 The an(4) driver has been removed from FreeBSD.
379 The vendor/openzfs branch was renamed to vendor/openzfs/legacy to
380 start tracking OpenZFS upstream more closely. Please see
381 https://lists.freebsd.org/archives/freebsd-current/2021-June/000153.html
382 for details on how to correct any errors that might result. The
383 short version is that you need to remove the old branch locally:
384 git update-ref -d refs/remotes/freebsd/vendor/openzfs
385 (assuming your upstream origin is named 'freebsd').
388 Commits 17accc08ae15 and de102f870501 add new files to LinuxKPI
389 which break drm-kmod. In addition various other additions where
390 committed. Bump __FreeBSD_version to 1400015 to be able to
394 Commit ca179c4d74f2 changed the package in which the OpenSSL
395 libraries and utilities are packaged.
396 It is recommended for pkgbase user to do:
397 pkg install -f FreeBSD-openssl
398 before pkg upgrade otherwise some dependencies might not be met
399 and pkg will stop working as libssl will not be present anymore
403 Commit 875977314881 changed the internal KAPI between
404 the nfsd and nfscommon modules. As such these modules
405 need to be rebuilt from sources.
406 Without this patch in your NFSv4.1/4.2 server, enabling
407 delegations by setting vfs.nfsd.issue_delegations non-zero
411 Commit 7763814fc9c2 changed the internal KAPI between
412 the krpc and NFS. As such, the krpc, nfscommon and
413 nfscl modules must all be rebuilt from sources.
414 Without this patch, NFSv4.1/4.2 mounts should not
415 be done with the nfscbd(8) daemon running, to avoid
416 needing a working back channel for server->client RPCs.
419 Commit 01ae8969a9ee fixed the NFSv4.1/4.2 server so that it
420 handles binding of the back channel as required by RFC5661.
421 Until this patch is in your server, avoid use of the "nconnects"
422 mount option for Linux NFSv4.1/4.2 mounts.
425 For 64-bit architectures the base system is now built with Position
426 Independent Executable (PIE) support enabled by default. It may be
427 disabled using the WITHOUT_PIE knob. A clean build is required.
430 Various LinuxKPI functionality was added which conflicts with DRM.
431 Please update your drm-kmod port to after the __FreeBSD_version 1400003
435 PC Card attachments for all devices have been removed. In the case of
436 wi and cmx, the entire drivers were removed because they were only
437 PC Card devices. FreeBSD_version 1300134 should be used for this
438 since it was bumped so recently.
441 Transport-independent parts of HID support have been split off the USB
442 code in to separate subsystem. Kernel configs which include one of
443 ums, ukbd, uhid, atp, wsp, wmt, uaudio, ugold or ucycom drivers should
444 be updated with adding of "device hid" line.
447 ncurses installation has been modified to only keep the widechar
448 enabled version. Incremental build is broken for that change, so it
449 requires a clean build.
452 The FreeBSD project has migrated from Subversion to Git. Temporary
453 instructions can be found at
454 https://github.com/bsdimp/freebsd-git-docs/blob/main/src-cvt.md
455 and other documents in that repo.
458 The services database has been updated to cover more of the basic
459 services expected in a modern system. The database is big enough
460 that it will cause issues in mergemaster in Releases previous to
461 12.2 and 11.3, or in very old current systems from before r358154.
464 Obsolete in-tree GDB 6.1.1 has been removed. GDB (including kgdb)
465 may be installed from ports or packages.
468 ping6 has been merged into ping. It can now be called as "ping -6".
469 See ping(8) for details.
472 Default value of net.add_addr_allfibs has been changed to 0.
473 If you have multi-fib configuration and rely on existence of all
474 interface routes in every fib, you need to set the above sysctl to 1.
477 The internal pre-processor in the calendar(1) program has been
478 extended to support more C pre-processor commands (e.g. #ifdef, #else,
479 and #undef) and to detect unbalanced conditional statements.
480 Error messages have been extended to include the filename and line
481 number if processing stops to help fixing malformed data files.
484 All the data files for the calendar(1) program, except calendar.freebsd,
485 have been moved to the deskutils/calendar-data port, much like the
486 jewish calendar entries were moved to deskutils/hebcal years ago. After
487 make delete-old-files, you need to install it to retain full
488 functionality. calendar(1) will issue a reminder for files it can't
492 LINT files are no longer generated. We now include the relevant NOTES
493 files. Note: This may cause conflicts with updating in some cases.
494 find sys -name LINT\* -delete
495 is suggested across this commit to remove the generated LINT files.
497 If you have tried to update with generated files there, the svn
498 command you want to un-auger the tree is
501 and then do the above find from the top level. Substitute 'amd64'
502 above with where the error message indicates a conflict.
505 OpenZFS support has been integrated. Do not upgrade root pools until
506 the loader is updated to support zstd. Furthermore, we caution against
507 'zpool upgrade' for the next few weeks. The change should be transparent
508 unless you want to use new features.
510 Not all "NO_CLEAN" build scenarios work across these changes. Many
511 scenarios have been tested and fixed, but rebuilding kernels without
512 rebuilding world may fail.
514 The ZFS cache file has moved from /boot to /etc to match the OpenZFS
515 upstream default. A fallback to /boot has been added for mountroot.
517 Pool auto import behavior at boot has been moved from the kernel module
518 to an explicit "zpool import -a" in one of the rc scripts enabled by
519 zfs_enable=YES. This means your non-root zpools won't auto import until
520 you upgrade your /etc/rc.d files.
523 The resume code now notifies devd with the 'kernel' system
524 rather than the old 'kern' subsystem to be consistent with
525 other use. The old notification will be created as well, but
526 will be removed prior to FreeBSD 14.0.
529 r362275 changed the internal API between the kernel RPC and the
530 NFS modules. As such, all the modules must be recompiled from
534 r364330 modified the internal API used between the NFS modules.
535 As such, all the NFS modules must be re-compiled from sources.
538 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
539 been upgraded to 11.0.0. Please see the 20141231 entry below for
540 information about prerequisites and upgrading, if you are not already
541 using clang 3.5.0 or higher.
544 r364092 modified the internal ABI used between the kernel NFS
545 modules. As such, all of these modules need to be rebuilt
546 from sources, so a version bump was done.
549 Makefile.inc has been updated to work around the issue documented in
550 20200729. It was a case where the optimization of using symbolic links
551 to point to binaries created a situation where we'd run new binaries
552 with old libraries starting midway through the installworld process.
555 r363679 has redefined some undefined behavior in regcomp(3); notably,
556 extraneous escapes of most ordinary characters will no longer be
557 accepted. An exp-run has identified all of the problems with this in
558 ports, but other non-ports software may need extra escapes removed to
559 continue to function.
561 Because of this change, installworld may encounter the following error
562 from rtld: Undefined symbol "regcomp@FBSD_1.6" -- It is imperative that
563 you do not halt installworld. Instead, let it run to completion (whether
564 successful or not) and run installworld once more.
567 A new implementation of bc and dc has been imported in r362681. This
568 implementation corrects non-conformant behavior of the previous bc
569 and adds GNU bc compatible options. It offers a number of extensions,
570 is much faster on large values, and has support for message catalogs
571 (a number of languages are already supported, contributions of further
572 languages welcome). The option WITHOUT_GH_BC can be used to build the
573 world with the previous versions of bc and dc.
576 r362639 changed the internal API used between the NFS kernel modules.
577 As such, they all need to be rebuilt from sources.
580 r362158 changed the arguments for VFS_CHECKEXP(). As such, any
581 out of tree file systems need to be modified and rebuilt.
582 Also, any file systems that are modules must be rebuilt.
585 read(2) of a directory fd is now rejected by default. root may
586 re-enable it for system root only on non-ZFS filesystems with the
587 security.bsd.allow_read_dir sysctl(8) MIB if
588 security.bsd.suser_enabled=1.
590 It may be advised to setup aliases for grep to default to `-d skip` if
591 commonly non-recursively grepping a list that includes directories and
592 the potential for the resulting stderr output is not tolerable. Example
593 aliases are now installed, commented out, in /root/.cshrc and
597 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
598 been upgraded to 10.0.1. Please see the 20141231 entry below for
599 information about prerequisites and upgrading, if you are not already
600 using clang 3.5.0 or higher.
603 Support for obsolete compilers has been removed from the build system.
604 Clang 6 and GCC 6.4 are the minimum supported versions.
607 closefrom(2) has been moved under COMPAT12, and replaced in libc with a
608 stub that calls close_range(2). If using a custom kernel configuration,
609 you may want to ensure that the COMPAT_FREEBSD12 option is included, as
610 a slightly older -CURRENT userland and older FreeBSD userlands may not
611 be functional without closefrom(2).
614 Upstream DTS from Linux 5.6 was merged and they now have the SID
615 and THS (Secure ID controller and THermal Sensor) node present.
616 The DTB overlays have now been removed from the tree for the H3/H5 and
617 A64 SoCs and the aw_sid and aw_thermal driver have been updated to
618 deal with upstream DTS. If you are using those overlays you need to
619 remove them from loader.conf and update the DTBs on the FAT partition.
622 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
623 been upgraded to 10.0.0. Please see the 20141231 entry below for
624 information about prerequisites and upgrading, if you are not already
625 using clang 3.5.0 or higher.
628 The amd(8) automount daemon has been removed from the source tree.
629 As of FreeBSD 10.1 autofs(5) is the preferred tool for automounting.
630 amd is still available in the sysutils/am-utils port.
633 Removed brooktree driver (bktr.4) from the tree.
636 The WITH_GPL_DTC option has been removed. The BSD-licenced device tree
637 compiler in usr.bin/dtc is used on all architectures which use dtc, and
638 the GPL dtc is available (if needed) from the sysutils/dtc port.
641 The WITHOUT_LLVM_LIBUNWIND option has been removed. LLVM's libunwind
642 is used by all supported CPU architectures.
645 GCC 4.2.1 has been removed from the tree. The WITH_GCC,
646 WITH_GCC_BOOTSTRAP, and WITH_GNUCXX options are no longer available.
647 Users who wish to build FreeBSD with GCC must use the external toolchain
651 ncurses has been updated to a newer version (6.2-20200215). Given the ABI
652 has changed, users will have to rebuild all the ports that are linked to
656 The size of struct vnet and the magic cookie have changed.
657 Users need to recompile libkvm and all modules using VIMAGE
658 together with their new kernel.
661 Defining the long deprecated NO_CTF, NO_DEBUG_FILES, NO_INSTALLLIB,
662 NO_MAN, NO_PROFILE, and NO_WARNS variables is now an error. Update
663 your Makefiles and scripts to define MK_<var>=no instead as required.
665 One exception to this is that program or library Makefiles should
666 define MAN to empty rather than setting MK_MAN=no.
669 Clang/LLVM is now the default compiler and LLD the default
673 make universe no longer uses GCC 4.2.1 on any architectures.
674 Architectures not supported by in-tree Clang/LLVM require an
675 external toolchain package.
678 GCC 4.2.1 is now not built by default, as part of the GCC 4.2.1
679 retirement plan. Specifically, the GCC, GCC_BOOTSTRAP, and GNUCXX
680 options default to off for all supported CPU architectures. As a
681 short-term transition aid they may be enabled via WITH_* options.
682 GCC 4.2.1 is expected to be removed from the tree on 2020-03-31.
685 Support for armv5 has been disconnected and is being removed. The
686 machine combination MACHINE=arm MACHINE_ARCH=arm is no longer valid.
687 You must now use a MACHINE_ARCH of armv6 or armv7. The default
688 MACHINE_ARCH for MACHINE=arm is now armv7.
691 Clang/LLVM is now the default compiler for all powerpc architectures.
692 LLD is now the default linker for powerpc64. The change for powerpc64
693 also includes a change to the ELFv2 ABI, incompatible with the existing
697 Kernel-loadable random(4) modules are no longer unloadable.
700 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
701 been upgraded to 9.0.1. Please see the 20141231 entry below for
702 information about prerequisites and upgrading, if you are not already
703 using clang 3.5.0 or higher.
706 r355677 has modified the internal interface used between the
707 NFS modules in the kernel. As such, they must all be upgraded
708 simultaneously. I will do a version bump for this.
711 The root certificates of the Mozilla CA Certificate Store have been
712 imported into the base system and can be managed with the certctl(8)
713 utility. If you have installed the security/ca_root_nss port or package
714 with the ETCSYMLINK option (the default), be advised that there may be
715 differences between those included in the port and those included in
716 base due to differences in nss branch used as well as general update
717 frequency. Note also that certctl(8) cannot manage certs in the
718 format used by the security/ca_root_nss port.
721 The amd(8) automount daemon has been disabled by default, and will be
722 removed in the future. As of FreeBSD 10.1 the autofs(5) is available
726 The nctgpio and wbwd drivers have been moved to the superio bus.
727 If you have one of these drivers in a kernel configuration, then
728 you should add device superio to it. If you use one of these drivers
729 as a module and you compile a custom set of modules, then you should
730 add superio to the set.
733 KPIs for network drivers to access interface addresses have changed.
734 Users need to recompile NIC driver modules together with kernel.
737 The net.link.tap.user_open sysctl no longer prevents user opening of
738 already created /dev/tapNN devices. Access is still controlled by
739 node permissions, just like tun devices. The net.link.tap.user_open
740 sysctl is now used only to allow users to perform devfs cloning of
741 tap devices, and the subsequent open may not succeed if the user is not
742 in the appropriate group. This sysctl may be deprecated/removed
743 completely in the future.
746 mips, powerpc, and sparc64 are no longer built as part of
747 universe / tinderbox unless MAKE_OBSOLETE_GCC is defined. If
748 not defined, mips, powerpc, and sparc64 builds will look for
749 the xtoolchain binaries and if installed use them for universe
750 builds. As llvm 9.0 becomes vetted for these architectures, they
751 will be removed from the list.
754 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
755 been upgraded to 9.0.0. Please see the 20141231 entry below for
756 information about prerequisites and upgrading, if you are not already
757 using clang 3.5.0 or higher.
760 The hpt27xx, hptmv, hptnr, and hptrr drivers have been removed from
761 GENERIC. They are available as modules and can be loaded by adding
762 to /boot/loader.conf hpt27xx_load="YES", hptmv_load="YES",
763 hptnr_load="YES", or hptrr_load="YES", respectively.
766 ntpd no longer by default locks its pages in memory, allowing them
767 to be paged out by the kernel. Use rlimit memlock to restore
768 historic BSD behaviour. For example, add "rlimit memlock 32"
769 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
772 Several of ping6's options have been renamed for better consistency
773 with ping. If you use any of -ARWXaghmrtwx, you must update your
774 scripts. See ping6(8) for details.
777 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
778 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
779 been removed from mount_fusefs(8). You can safely remove them from
780 your scripts, because they had no effect.
782 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
783 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
784 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
785 sysctls have been removed. If you felt the need to set any of them to
786 a non-default value, please tell asomers@FreeBSD.org why.
789 Default permissions on the /var/account/acct file (and copies of it
790 rotated by periodic daily scripts) are changed from 0644 to 0640
791 because the file contains sensitive information that should not be
792 world-readable. If the /var/account directory must be created by
793 rc.d/accounting, the mode used is now 0750. Admins who use the
794 accounting feature are encouraged to change the mode of an existing
795 /var/account directory to 0750 or 0700.
798 Entropy collection and the /dev/random device are no longer optional
799 components. The "device random" option has been removed.
800 Implementations of distilling algorithms can still be made loadable
801 with "options RANDOM_LOADABLE" (e.g., random_fortuna.ko).
804 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
805 been upgraded to 8.0.1. Please see the 20141231 entry below for
806 information about prerequisites and upgrading, if you are not already
807 using clang 3.5.0 or higher.
810 A fix was applied to i386 kernel modules to avoid panics with
811 dpcpu or vnet. Users need to recompile i386 kernel modules
812 having pcpu or vnet sections or they will refuse to load.
815 User-wired pages now have their own counter,
816 vm.stats.vm.v_user_wire_count. The vm.max_wired sysctl was renamed
817 to vm.max_user_wired and changed from an unsigned int to an unsigned
818 long. bhyve VMs wired with the -S are now subject to the user
819 wiring limit; the vm.max_user_wired sysctl may need to be tuned to
820 avoid running into the limit.
823 The IPSEC option has been removed from GENERIC. Users requiring
824 ipsec(4) must now load the ipsec(4) kernel module.
827 The tap(4) driver has been folded into tun(4), and the module has been
828 renamed to tuntap. You should update any kld_list="if_tap" or
829 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
830 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
831 module instead, and "device tap" or "device tun" entries in kernel
832 config files to select the tuntap device instead.
835 The following knobs have been added related to tradeoffs between
836 safe use of the random device and availability in the absence of
839 kern.random.initial_seeding.bypass_before_seeding: tunable; set
840 non-zero to bypass the random device prior to seeding, or zero to
841 block random requests until the random device is initially seeded.
842 For now, set to 1 (unsafe) by default to restore pre-r346250 boot
843 availability properties.
845 kern.random.initial_seeding.read_random_bypassed_before_seeding:
846 read-only diagnostic sysctl that is set when bypass is enabled and
847 read_random(9) is bypassed, to enable programmatic handling of this
848 initial condition, if desired.
850 kern.random.initial_seeding.arc4random_bypassed_before_seeding:
851 Similar to the above, but for arc4random(9) initial seeding.
853 kern.random.initial_seeding.disable_bypass_warnings: tunable; set
854 non-zero to disable warnings in dmesg when the same conditions are
855 met as for the diagnostic sysctls above. Defaults to zero, i.e.,
856 produce warnings in dmesg when the conditions are met.
859 The loadable random module KPI has changed; the random_infra_init()
860 routine now requires a 3rd function pointer for a bool (*)(void)
861 method that returns true if the random device is seeded (and
862 therefore unblocked).
865 r345895 reverts r320698. This implies that an nfsuserd(8) daemon
866 built from head sources between r320757 (July 6, 2017) and
867 r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
868 is added to the command line.
869 nfsuserd daemons built from head sources that are post-r338192 are
870 not affected and should continue to work.
873 The fuse(4) module has been renamed to fusefs(4) for consistency with
874 other filesystems. You should update any kld_load="fuse" entries in
875 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
876 "options FUSE" entries in kernel config files.
879 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
880 8.0.0. Please see the 20141231 entry below for information about
881 prerequisites and upgrading, if you are not already using clang 3.5.0
885 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
886 compiled into your custom kernel, add 'device xz' statement to the
890 drm and drm2 have been removed from the tree. Please see
891 https://wiki.freebsd.org/Graphics for the latest information on
892 migrating to the drm ports.
895 Iflib is no longer unconditionally compiled into the kernel. Drivers
896 using iflib and statically compiled into the kernel, now require
897 the 'device iflib' config option. For the same drivers loaded as
898 modules on kernels not having 'device iflib', the iflib.ko module
899 is loaded automatically.
902 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
903 options no longer exist since r343219 and r343427 respectively;
904 nothing uses them, so they should be just removed from custom
908 r342635 changes the way efibootmgr(8) works by requiring users to add
909 the -b (bootnum) parameter for commands where the bootnum was previously
910 specified with each option. For example 'efibootmgr -B 0001' is now
911 'efibootmgr -B -b 0001'.
914 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
915 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
916 servers that have vfs.nfsd.nfs_privport set will only allow mounts
917 from clients using a reserved port. Since both the FreeBSD and Linux
918 NFSv4 clients use reserved ports by default, this should not affect
922 The XLP config has been removed. We can't support 64-bit atomics in this
923 kernel because it is running in 32-bit mode. XLP users must transition
924 to running a 64-bit kernel (XLP64 or XLPN32).
926 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
927 the preferred emulator today and we don't need two different ones.
929 The old sibyte / swarm / Broadcom BCM1250 support has been
930 removed from the mips port.
933 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
934 7.0.1. Please see the 20141231 entry below for information about
935 prerequisites and upgrading, if you are not already using clang 3.5.0
939 Remove the timed and netdate programs from the base tree. Setting
940 the time with these daemons has been obsolete for over a decade.
943 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
944 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
945 it produces broken binaries when ifuncs are in use. Users needing
946 GNU ld should install the binutils port or package.
949 The BSD crtbegin and crtend code has been enabled by default. It has
950 had extensive testing on amd64, arm64, and i386. It can be disabled
951 by building a world with -DWITHOUT_BSD_CRTBEGIN.
954 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
955 has been converted to a port (misc/ctm) and will be removed from
956 FreeBSD-13. It is available as a package (ctm) for all supported
960 The default newsyslog.conf(5) file has been changed to only include
961 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
962 the filenames end in '.conf' and do not begin with a '.'.
964 You should check the configuration files in these two directories match
965 this naming convention. You can verify which configuration files are
966 being included using the command:
970 Ports for the DRM modules have been simplified. Now, amd64 users should
971 just install the drm-kmod port. All others should install
974 Graphics hardware that's newer than about 2010 usually works with
975 drm-kmod. For hardware older than 2013, however, some users will need
976 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
977 than 2008 usually only works in drm-legacy-kmod. The graphics team can
978 only commit to hardware made since 2013 due to the complexity of the
979 market and difficulty to test all the older cards effectively. If you
980 have hardware supported by drm-kmod, you are strongly encouraged to use
981 that as you will get better support.
983 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
984 elsewhere, the drm and drm2 modules will be eliminated from the src base
985 soon (with a limited exception for arm). Please update to the package
986 asap and report any issues to x11@freebsd.org.
988 Generally, anybody using the drm*-kmod packages should add
989 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
990 cross-threading surprises, especially with automatic driver
991 loading from X11 startup. These will become the defaults in 13-current
995 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
996 custom kernel and module loading configuration files must be updated
997 accordingly. Moreover, interfaces previous presented as ixlvN to the
998 system are now exposed as iavfN and network configuration files must
999 be adjusted as necessary.
1002 OpenSSL has been updated to version 1.1.1. This update included
1003 additional various API changes throughout the base system. It is
1004 important to rebuild third-party software after upgrading. The value
1005 of __FreeBSD_version has been bumped accordingly.
1008 The legacy DRM modules and drivers have now been added to the loader's
1009 module blacklist, in favor of loading them with kld_list in rc.conf(5).
1010 The module blacklist may be overridden with the loader.conf(5)
1011 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
1015 The cam(4) based nda(4) driver will be used over nvd(4) by default on
1016 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
1017 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
1018 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
1022 Reproducible build mode is now on by default, in preparation for
1023 FreeBSD 12.0. This eliminates build metadata such as the user,
1024 host, and time from the kernel (and uname), unless the working tree
1025 corresponds to a modified checkout from a version control system.
1026 The previous behavior can be obtained by setting the /etc/src.conf
1027 knob WITHOUT_REPRODUCIBLE_BUILD.
1030 The Yarrow CSPRNG has been removed from the kernel as it has not been
1031 supported by its designers since at least 2003. Fortuna has been the
1032 default since FreeBSD-11.
1035 devctl freeze/thaw have gone into the tree, the rc scripts have been
1036 updated to use them and devmatch has been changed. You should update
1037 kernel, userland and rc scripts all at the same time.
1040 The default interpreter has been switched from 4th to Lua.
1041 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
1042 interpreter. If you have custom FORTH code you will need to set
1043 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
1044 src.conf for the build. This will create default hard links between
1045 loader and loader_4th instead of loader and loader_lua, the new default.
1046 If you are using UEFI it will create the proper hard link to loader.efi.
1048 bhyve uses userboot.so. It remains 4th-only until some issues are solved
1049 regarding coexisting with multiple versions of FreeBSD are resolved.
1052 ls(1) now respects the COLORTERM environment variable used in other
1053 systems and software to indicate that a colored terminal is both
1054 supported and desired. If ls(1) is suddenly emitting colors, they may
1055 be disabled again by either removing the unwanted COLORTERM from your
1056 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
1057 may not be observed in a future release.
1060 The default pager for most commands has been changed to "less". To
1061 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
1065 The jedec_ts(4) driver has been removed. A superset of its functionality
1066 is available in the jedec_dimm(4) driver, and the manpage for that
1067 driver includes migration instructions. If you have "device jedec_ts"
1068 in your kernel configuration file, it must be removed.
1071 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
1072 This should have no effect if the kernel is booted via BIOS/legacy boot.
1073 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
1074 has a buggy firmware that prevents a successful boot due to use of
1078 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
1079 support has been removed from the tree. These ports were
1080 obsolete and/or known to be broken for many years.
1083 loader.efi has been augmented to participate more fully in the
1084 UEFI boot manager protocol. loader.efi will now look at the
1085 BootXXXX environment variable to determine if a specific kernel
1086 or root partition was specified. XXXX is derived from BootCurrent.
1087 efibootmgr(8) manages these standard UEFI variables.
1090 zfsloader's functionality has now been folded into loader.
1091 zfsloader is no longer necessary once you've updated your
1092 boot blocks. For a transition period, we will install a
1093 hardlink for zfsloader to loader to allow a smooth transition
1094 until the boot blocks can be updated (hard link because old
1095 zfs boot blocks don't understand symlinks).
1098 ARM64 now have efifb support, if you want to have serial console
1099 on your arm64 board when an screen is connected and the bootloader
1100 setup a frame buffer for us to use, just add :
1103 in /boot/loader.conf
1104 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
1105 an screen connected as the firmware will setup a frame buffer are that
1106 u-boot will expose as an EFI frame buffer.
1109 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
1110 or take steps to update /etc/passwd before doing installworld on
1111 existing systems. Do not skip the "mergemaster -Fp" step before
1112 installworld, as described in the update procedures near the bottom
1113 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
1114 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
1115 the ntp config file contain options that change file/dir locations.
1116 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
1117 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
1118 taking steps to ensure that all required files/dirs are accessible
1122 Big endian arm support has been removed.
1125 The static environment setup in kernel configs is no longer mutually
1126 exclusive with the loader(8) environment by default. In order to
1127 restore the previous default behavior of disabling the loader(8)
1128 environment if a static environment is present, you must specify
1129 loader_env.disabled=1 in the static environment.
1132 The ABI of syscalls used by management tools like sockstat and
1133 netstat has been broken to allow 32-bit binaries to work on
1134 64-bit kernels without modification. These programs will need
1135 to match the kernel in order to function. External programs may
1136 require minor modifications to accommodate a change of type in
1137 structures from pointers to 64-bit virtual addresses.
1140 On i386 and amd64 atomics are now inlined. Out of tree modules using
1141 atomics will need to be rebuilt.
1144 The '%I' format in the kern.corefile sysctl limits the number of
1145 core files that a process can generate to the number stored in the
1146 debug.ncores sysctl. The '%I' format is replaced by the single digit
1147 index. Previously, if all indexes were taken the kernel would overwrite
1148 only a core file with the highest index in a filename.
1149 Currently the system will create a new core file if there is a free
1150 index or if all slots are taken it will overwrite the oldest one.
1153 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
1154 6.0.1. Please see the 20141231 entry below for information about
1155 prerequisites and upgrading, if you are not already using clang 3.5.0
1159 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
1160 needed to be changed to work with it. This change was made with r335763
1161 and requires a mergemaster / etcupdate / etc to update the installed
1165 r334930 changed the interface between the NFS modules, so they all
1166 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
1169 As of r334391 lld is the default amd64 system linker; it is installed
1170 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
1174 The kernel / userland interface for devinfo changed, so you'll
1175 need a new kernel and userland as a pair for it to work (rebuilding
1176 lib/libdevinfo is all that's required). devinfo and devmatch will
1177 not work, but everything else will when there's a mismatch.
1180 The on-disk format for hwpmc callchain records has changed to include
1181 threadid corresponding to a given record. This changes the field offsets
1182 and thus requires that libpmcstat be rebuilt before using a kernel
1186 The vxge(4) driver has been removed. This driver was introduced into
1187 HEAD one week before the Exar left the Ethernet market and is not
1188 known to be used. If you have device vxge in your kernel config file
1192 The amd64 kernel now requires a ld that supports ifunc to produce a
1193 working kernel, either lld or a newer binutils. lld is built by default
1194 on amd64, and the 'buildkernel' target uses it automatically. However,
1195 it is not the default linker, so building the kernel the traditional
1196 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
1197 binutils port/package). lld will soon be default, and this requirement
1200 NOTE: As of r334391 lld is the default system linker on amd64, and no
1201 workaround is necessary.
1204 The nxge(4) driver has been removed. This driver was for PCI-X 10g
1205 cards made by s2io/Neterion. The company was acquired by Exar and
1206 no longer sells or supports Ethernet products. If you have device
1207 nxge in your kernel config file it must be removed.
1210 The tz database (tzdb) has been updated to 2018e. This version more
1211 correctly models time stamps in time zones with negative DST such as
1212 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
1213 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
1214 time zone abbreviations and the tm_isdst flag.
1217 The ixgb(4) driver has been removed. This driver was for an early and
1218 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
1219 quickly shifted to the long lived ixgbe family. If you have device
1220 ixgb in your kernel config file it must be removed.
1223 The lmc(4) driver has been removed. This was a WAN interface
1224 card that was already reportedly rare in 2003, and had an ambiguous
1225 license. If you have device lmc in your kernel config file it must
1229 Support for Arcnet networks has been removed. If you have device
1230 arcnet or device cm in your kernel config file they must be
1234 Support for FDDI networks has been removed. If you have device
1235 fddi or device fpa in your kernel config file they must be
1239 In addition to supporting RFC 3164 formatted messages, the
1240 syslogd(8) service is now capable of parsing RFC 5424 formatted
1241 log messages. The main benefit of using RFC 5424 is that clients
1242 may now send log messages with timestamps containing year numbers,
1243 microseconds and time zone offsets.
1245 Similarly, the syslog(3) C library function has been altered to
1246 send RFC 5424 formatted messages to the local system logging
1247 daemon. On systems using syslogd(8), this change should have no
1248 negative impact, as long as syslogd(8) and the C library are
1249 updated at the same time. On systems using a different system
1250 logging daemon, it may be necessary to make configuration
1251 adjustments, depending on the software used.
1253 When using syslog-ng, add the 'syslog-protocol' flag to local
1254 input sources to enable parsing of RFC 5424 formatted messages:
1257 unix-dgram("/var/run/log" flags(syslog-protocol));
1260 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
1261 of the 'imuxsock' module to let messages be processed by the
1262 regular RFC 3164/5424 parsing pipeline:
1264 module(load="imuxsock" SysSock.UseSpecialParser="off")
1266 Do note that these changes only affect communication between local
1267 applications and syslogd(8). The format that syslogd(8) uses to
1268 store messages on disk or forward messages to other systems
1269 remains unchanged. syslogd(8) still uses RFC 3164 for these
1270 purposes. Options to customize this behaviour will be added in the
1271 future. Utilities that process log files stored in /var/log are
1272 thus expected to continue to function as before.
1274 __FreeBSD_version has been incremented to 1200061 to denote this
1278 Support for token ring networks has been removed. If you
1279 have "device token" in your kernel config you should remove
1280 it. No device drivers supported token ring.
1283 makefs was modified to be able to tag ISO9660 El Torito boot catalog
1284 entries as EFI instead of overloading the i386 tag as done previously.
1285 The amd64 mkisoimages.sh script used to build amd64 ISO images for
1286 release was updated to use this. This may mean that makefs must be
1287 updated before "make cdrom" can be run in the release directory. This
1288 should be as simple as:
1290 $ cd $SRCDIR/usr.sbin/makefs
1291 $ make depend all install
1294 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
1295 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
1296 Co-existence for the transition period will come shortly. Booting is a
1297 complex environment and test coverage for Lua-enabled loaders has been
1298 thin, so it would be prudent to assume it might not work and make
1299 provisions for backup boot methods.
1302 devmatch functionality has been turned on in devd. It will automatically
1303 load drivers for unattached devices. This may cause unexpected drivers
1304 to be loaded. Please report any problems to current@ and
1308 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
1309 6.0.0. Please see the 20141231 entry below for information about
1310 prerequisites and upgrading, if you are not already using clang 3.5.0
1314 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
1315 This means it is used to link the kernel and userland libraries and
1316 executables, but is not yet installed as /usr/bin/ld by default.
1318 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
1319 WITHOUT_LLD_BOOTSTRAP=yes
1322 On i386, pmtimer has been removed. Its functionality has been folded
1323 into apm. It was a no-op on ACPI in current for a while now (but was
1324 still needed on i386 in FreeBSD 11 and earlier). Users may need to
1325 remove it from kernel config files.
1328 The use of RSS hash from the network card aka flowid has been
1329 disabled by default for lagg(4) as it's currently incompatible with
1330 the lacp and loadbalance protocols.
1332 This can be re-enabled by setting the following in loader.conf:
1333 net.link.lagg.default_use_flowid="1"
1336 The SW_WATCHDOG option is no longer necessary to enable the
1337 hardclock-based software watchdog if no hardware watchdog is
1338 configured. As before, SW_WATCHDOG will cause the software
1339 watchdog to be enabled even if a hardware watchdog is configured.
1342 r326887 fixes the issue described in the 20171214 UPDATING entry.
1343 r326888 flips the switch back to building GELI support always.
1346 r362593 broke ZFS + GELI support for reasons unknown. However,
1347 it also broke ZFS support generally, so GELI has been turned off
1348 by default as the lesser evil in r326857. If you boot off ZFS and/or
1349 GELI, it might not be a good time to update.
1352 PowerPC users must update loader(8) by rebuilding world before
1353 installing a new kernel, as the protocol connecting them has
1354 changed. Without the update, loader metadata will not be passed
1355 successfully to the kernel and users will have to enter their
1356 root partition at the kernel mountroot prompt to continue booting.
1357 Newer versions of loader can boot old kernels without issue.
1360 The LOADER_FIREWIRE_SUPPORT build variable has been renamed to
1361 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
1362 to WITH/OUT_LOADER_GELI.
1365 The naive and non-compliant support of posix_fallocate(2) in ZFS
1366 has been removed as of r325320. The system call now returns EINVAL
1367 when used on a ZFS file. Although the new behavior complies with the
1368 standard, some consumers are not prepared to cope with it.
1369 One known victim is lld prior to r325420.
1372 Building in a FreeBSD src checkout will automatically create object
1373 directories now rather than store files in the current directory if
1374 'make obj' was not ran. Calling 'make obj' is no longer necessary.
1375 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
1376 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
1380 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
1381 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
1382 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
1383 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
1384 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
1385 The UNIFIED_OBJDIR option is a transitional feature that will be
1386 removed for 12.0 release; please migrate to the new format for any
1387 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
1388 than hardcoding paths.
1391 The native-xtools target no longer installs the files by default to the
1392 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
1393 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
1396 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
1397 options are changing from controlling the build if defined / undefined
1398 to controlling the build with explicit 'yes' or 'no' values. They will
1399 shift to WITH/WITHOUT options to match other options in the system.
1402 libstand has turned into a private library for sys/boot use only.
1403 It is no longer supported as a public interface outside of sys/boot.
1406 The arm port has split armv6 into armv6 and armv7. armv7 is now
1407 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
1408 and are running a kernel from before r324363, you will need to add
1409 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
1412 When building multiple kernels using KERNCONF, non-existent KERNCONF
1413 files will produce an error and buildkernel will fail. Previously
1414 missing KERNCONF files silently failed giving no indication as to
1415 why, only to subsequently discover during installkernel that the
1416 desired kernel was never built in the first place.
1419 The default serial number format for CTL LUNs has changed. This will
1420 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
1421 or iSCSI clients care about their LUNs' serial numbers. Users who
1422 require serial number stability should hardcode serial numbers in
1426 For 32-bit arm compiled for hard-float support, soft-floating point
1427 binaries now always get their shared libraries from
1428 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
1429 /usr/libsoft also existed). Only users with a hard-float ld.so, but
1430 soft-float everything else should be affected.
1433 The geli password typed at boot is now hidden. To restore the previous
1434 behavior, see geli(8) for configuration options.
1437 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
1438 sysctl values. Minor nit, but requires a rebuild of both world/kernel
1442 "make check" behavior (made in ^/head@r295380) has been changed to
1443 execute from a limited sandbox, as opposed to executing from
1447 - The "beforecheck" and "aftercheck" targets are now specified.
1448 - ${CHECKDIR} (added in commit noted above) has been removed.
1449 - Legacy behavior can be enabled by setting
1450 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
1452 If the limited sandbox mode is enabled, "make check" will execute
1453 "make distribution", then install, execute the tests, and clean up the
1454 sandbox if successful.
1456 The "make distribution" and "make install" targets are typically run as
1457 root to set appropriate permissions and ownership at installation time.
1458 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
1459 environment if executing "make check" with limited sandbox mode using
1460 an unprivileged user.
1463 Since the switch to GPT disk labels, fsck for UFS/FFS has been
1464 unable to automatically find alternate superblocks. As of r322297,
1465 the information needed to find alternate superblocks has been
1466 moved to the end of the area reserved for the boot block.
1467 Filesystems created with a newfs of this vintage or later
1468 will create the recovery information. If you have a filesystem
1469 created prior to this change and wish to have a recovery block
1470 created for your filesystem, you can do so by running fsck in
1471 foreground mode (i.e., do not use the -p or -y options). As it
1472 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
1473 to which you should answer yes.
1476 As of r321665, an NFSv4 server configuration that services
1477 Kerberos mounts or clients that do not support the uid/gid in
1478 owner/owner_group string capability, must explicitly enable
1479 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
1480 machine's /etc/rc.conf file.
1483 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
1484 Please see the 20141231 entry below for information about prerequisites
1485 and upgrading, if you are not already using clang 3.5.0 or higher.
1488 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
1489 r-commands (rlogin, rsh, etc.) to be built with the base system.
1492 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
1493 a very major ABI incompatible change, so users of FreeBSD/powerpc must
1494 be careful when performing source upgrades. It is best to run
1495 'make installworld' from an alternate root system, either a live
1496 CD/memory stick, or a temporary root partition. Additionally, all ports
1497 must be recompiled. powerpc64 is largely unaffected, except in the case
1498 of 32-bit compatibility. All 32-bit binaries will be affected.
1501 Forward compatibility for the "ino64" project have been committed. This
1502 will allow most new binaries to run on older kernels in a limited
1503 fashion. This prevents many of the common foot-shooting actions in the
1504 upgrade as well as the limited ability to roll back the kernel across
1505 the ino64 upgrade. Complicated use cases may not work properly, though
1506 enough simpler ones work to allow recovery in most situations.
1509 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
1510 if you require the GPL compiler.
1513 The internal ABI used for communication between the NFS kernel modules
1514 was changed by r320085, so __FreeBSD_version was bumped to
1515 ensure all the NFS related modules are updated together.
1518 The ABI of struct event was changed by extending the data
1519 member to 64bit and adding ext fields. For upgrade, same
1520 precautions as for the entry 20170523 "ino64" must be
1524 The GNU roff toolchain has been removed from base. To render manpages
1525 which are not supported by mandoc(1), man(1) can fallback on GNU roff
1526 from ports (and recommends to install it).
1527 To render roff(7) documents, consider using GNU roff from ports or the
1528 heirloom doctools roff toolchain from ports via pkg install groff or
1529 via pkg install heirloom-doctools.
1532 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
1533 smaller runtime footprint builds. This is useful for embedded systems
1534 which only require one chipset support.
1536 If you load it as a module, make sure this is in /boot/loader.conf:
1540 This will load the HAL, all chip/RF backends and if_ath_pci.
1541 If you have if_ath_pci in /boot/loader.conf, ensure it is after
1542 if_ath or it will not load any HAL chipset support.
1544 If you want to selectively load things (eg on cheaper ARM/MIPS
1545 platforms where RAM is at a premium) you should:
1548 * load the chip modules in question
1549 * load ath_rate, ath_dfs
1551 * load if_ath_pci and/or if_ath_ahb depending upon your particular
1552 bus bind type - this is where probe/attach is done.
1554 For further comments/feedback, poke adrian@ .
1557 The "ino64" 64-bit inode project has been committed, which extends
1558 a number of types to 64 bits. Upgrading in place requires care and
1559 adherence to the documented upgrade procedure.
1561 If using a custom kernel configuration ensure that the
1562 COMPAT_FREEBSD11 option is included (as during the upgrade the
1563 system will be running the ino64 kernel with the existing world).
1565 For the safest in-place upgrade begin by removing previous build
1566 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full
1567 procedure documented below under the heading "To rebuild everything and
1568 install it on the current system." Specifically, a reboot is required
1569 after installing the new kernel before installing world. While an
1570 installworld normally works by accident from multiuser after rebooting
1571 the proper kernel, there are many cases where this will fail across this
1572 upgrade and installworld from single user is required.
1575 The NATM framework including the en(4), fatm(4), hatm(4), and
1576 patm(4) devices has been removed. Consumers should plan a
1577 migration before the end-of-life date for FreeBSD 11.
1580 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
1581 diff has not been implemented, if those are needed a newer version of
1582 GNU diff is available via the diffutils package under the gdiff name.
1585 As of r316810 for ipfilter, keep frags is no longer assumed when
1586 keep state is specified in a rule. r316810 aligns ipfilter with
1587 documentation in man pages separating keep frags from keep state.
1588 This allows keep state to be specified without forcing keep frags
1589 and allows keep frags to be specified independently of keep state.
1590 To maintain previous behaviour, also specify keep frags with
1591 keep state (as documented in ipf.conf.5).
1594 arm64 builds now use the base system LLD 4.0.0 linker by default,
1595 instead of requiring that the aarch64-binutils port or package be
1596 installed. To continue using aarch64-binutils, set
1597 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
1600 The UDP optimization in entry 20160818 that added the sysctl
1601 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
1602 packets will no longer be treated as L3 broadcast packets.
1605 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
1606 use any explicitly assigned loopback address available in the jail
1607 instead of using the first assigned address of the jail.
1610 The ctl.ko module no longer implements the iSCSI target frontend:
1611 cfiscsi.ko does instead.
1613 If building cfiscsi.ko as a kernel module, the module can be loaded
1614 via one of the following methods:
1615 - `cfiscsi_load="YES"` in loader.conf(5).
1616 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
1617 - ctladm(8)/ctld(8), when compiled with iSCSI support
1618 (`WITH_ISCSI=yes` in src.conf(5))
1620 Please see cfiscsi(4) for more details.
1623 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
1624 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
1625 same source (previously, the dependency of mmcsd.ko on mmc.ko was
1626 missing, but mmcsd.ko now will refuse to load if it is incompatible
1630 The syntax of ipfw(8) named states was changed to avoid ambiguity.
1631 If you have used named states in the firewall rules, you need to modify
1632 them after installworld and before rebooting. Now named states must
1633 be prefixed with colon.
1636 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
1637 removed as the userland we provide cannot use them. The KMS version
1638 (sys/dev/drm2) supports the same hardware.
1641 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
1642 Please see the 20141231 entry below for information about prerequisites
1643 and upgrading, if you are not already using clang 3.5.0 or higher.
1646 The code that provides support for ZFS .zfs/ directory functionality
1647 has been reimplemented. It's not possible now to create a snapshot
1648 by mkdir under .zfs/snapshot/. That should be the only user visible
1652 EISA bus support has been removed. The WITH_EISA option is no longer
1656 MCA bus support has been removed.
1659 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
1660 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
1663 The EM_MULTIQUEUE kernel configuration option is deprecated now that
1664 the em(4) driver conforms to iflib specifications.
1667 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
1668 IFLIB. If you have a custom kernel configuration that excludes em(4)
1669 but you use igb(4), you need to re-add em(4) to your custom
1673 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
1674 Please see the 20141231 entry below for information about prerequisites
1675 and upgrading, if you are not already using clang 3.5.0 or higher.
1678 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
1679 Please see the 20141231 entry below for information about prerequisites
1680 and upgrading, if you are not already using clang 3.5.0 or higher.
1683 The layout of the pmap structure has changed for powerpc to put the pmap
1684 statistics at the front for all CPU variations. libkvm(3) and all tools
1685 that link against it need to be recompiled.
1688 isl(4) and cyapa(4) drivers now require a new driver,
1689 chromebook_platform(4), to work properly on Chromebook-class hardware.
1690 On other types of hardware the drivers may need to be configured using
1691 device hints. Please see the corresponding manual pages for details.
1694 The urtwn(4) driver was merged into rtwn(4) and now consists of
1695 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
1697 Also, firmware for RTL8188CE was renamed due to possible name
1698 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
1701 GNU rcs has been removed from base. It is available as packages:
1702 - rcs: Latest GPLv3 GNU rcs version.
1703 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
1707 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
1708 modules now requires that the kernel configuration contain the
1709 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
1712 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
1713 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
1716 Relocatable object files with the extension of .So have been renamed
1717 to use an extension of .pico instead. The purpose of this change is
1718 to avoid a name clash with shared libraries on case-insensitive file
1719 systems. On those file systems, foo.So is the same file as foo.so.
1722 GNU rcs has been turned off by default. It can (temporarily) be built
1723 again by adding WITH_RCS knob in src.conf.
1724 Otherwise, GNU rcs is available from packages:
1725 - rcs: Latest GPLv3 GNU rcs version.
1726 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
1729 The backup_uses_rcs functionality has been removed from rc.subr.
1732 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
1733 two separate components, QUEUE_MACRO_DEBUG_TRACE and
1734 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
1735 QUEUE_MACRO_DEBUG behavior.
1738 r304787 changed some ioctl interfaces between the iSCSI userspace
1739 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1740 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1744 The UDP receive code has been updated to only treat incoming UDP
1745 packets that were addressed to an L2 broadcast address as L3
1746 broadcast packets. It is not expected that this will affect any
1747 standards-conforming UDP application. The new behaviour can be
1748 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1752 Remove the openbsd_poll system call.
1753 __FreeBSD_version has been bumped because of this.
1756 The stable/11 branch has been created from head@r302406.
1758 After branch N is created, entries older than the N-2 branch point are removed
1759 from this file. After stable/14 is branched and current becomes FreeBSD 15,
1760 entries older than stable/12 branch point will be removed from current's
1767 Sometimes, obscure build problems are the result of environment
1768 poisoning. This can happen because the make utility reads its
1769 environment when searching for values for global variables. To run
1770 your build attempts in an "environmental clean room", prefix all make
1771 commands with 'env -i '. See the env(1) manual page for more details.
1772 Occasionally a build failure will occur with "make -j" due to a race
1773 condition. If this happens try building again without -j, and please
1774 report a bug if it happens consistently.
1776 When upgrading from one major version to another it is generally best to
1777 upgrade to the latest code in the currently installed branch first, then
1778 do an upgrade to the new branch. This is the best-tested upgrade path,
1779 and has the highest probability of being successful. Please try this
1780 approach if you encounter problems with a major version upgrade. Since
1781 the stable 4.x branch point, one has generally been able to upgrade from
1782 anywhere in the most recent stable branch to head / current (or even the
1783 last couple of stable branches). See the top of this file when there's
1786 The update process will emit an error on an attempt to perform a build
1787 or install from a FreeBSD version below the earliest supported version.
1788 When updating from an older version the update should be performed one
1789 major release at a time, including running `make delete-old` at each
1792 When upgrading a live system, having a root shell around before
1793 installing anything can help undo problems. Not having a root shell
1794 around can lead to problems if pam has changed too much from your
1795 starting point to allow continued authentication after the upgrade.
1797 This file should be read as a log of events. When a later event changes
1798 information of a prior event, the prior event should not be deleted.
1799 Instead, a pointer to the entry with the new information should be
1800 placed in the old entry. Readers of this file should also sanity check
1801 older entries before relying on them blindly. Authors of new entries
1802 should write them with this in mind.
1806 When upgrading the boot ZFS pool to a new version (via zpool upgrade),
1807 always follow these three steps:
1809 1) recompile and reinstall the ZFS boot loader and boot block
1810 (this is part of "make buildworld" and "make installworld")
1812 2) update the ZFS boot block on your boot drive (only required when
1813 doing a zpool upgrade):
1815 When booting on x86 via BIOS, use the following to update the ZFS boot
1816 block on the freebsd-boot partition of a GPT partitioned drive ada0:
1817 gpart bootcode -p /boot/gptzfsboot -i $N ada0
1818 The value $N will typically be 1. For EFI booting, see EFI notes.
1820 3) zpool upgrade the root pool. New bootblocks will work with old
1821 pools, but not vice versa, so they need to be updated before any
1824 Non-boot pools do not need these updates.
1829 There are two locations the boot loader can be installed into. The
1830 current location (and the default) is \efi\freebsd\loader.efi and using
1831 efibootmgr(8) to configure it. The old location, that must be used on
1832 deficient systems that don't honor efibootmgr(8) protocols, is the
1833 fallback location of \EFI\BOOT\BOOTxxx.EFI. Generally, you will copy
1834 /boot/loader.efi to this location, but on systems installed a long time
1835 ago the ESP may be too small and /boot/boot1.efi may be needed unless
1836 the ESP has been expanded in the meantime.
1838 Recent systems will have the ESP mounted on /boot/efi, but older ones
1839 may not have it mounted at all, or mounted in a different
1840 location. Older arm SD images with MBR used /boot/msdos as the
1841 mountpoint. The ESP is a MSDOS filesystem.
1843 The EFI boot loader rarely needs to be updated. For ZFS booting,
1844 however, you must update loader.efi before you do 'zpool upgrade' the
1845 root zpool, otherwise the old loader.efi may reject the upgraded zpool
1846 since it does not automatically understand some new features.
1848 See loader.efi(8) and uefi(8) for more details.
1852 If you are updating from a prior version of FreeBSD (even one just
1853 a few days old), you should follow this procedure. It is the most
1854 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1856 make kernel-toolchain
1857 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1858 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1860 To test a kernel once
1861 ---------------------
1862 If you just want to boot a kernel once (because you are not sure
1863 if it works, or if you want to boot a known bad kernel to provide
1864 debugging information) run
1865 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1866 nextboot -k testkernel
1868 To rebuild everything and install it on the current system.
1869 -----------------------------------------------------------
1870 # Note: sometimes if you are running current you gotta do more than
1871 # is listed here if you are upgrading from a really old current.
1873 <make sure you have good level 0 dumps>
1875 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1876 make installkernel KERNCONF=YOUR_KERNEL_HERE
1878 <reboot in single user> [3]
1885 To cross-install current onto a separate partition
1886 --------------------------------------------------
1887 # In this approach we use a separate partition to hold
1888 # current's root, 'usr', and 'var' directories. A partition
1889 # holding "/", "/usr" and "/var" should be about 2GB in
1892 <make sure you have good level 0 dumps>
1895 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1896 <maybe newfs current's root partition>
1897 <mount current's root partition on directory ${CURRENT_ROOT}>
1898 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1899 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1900 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1901 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1902 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1903 <reboot into current>
1904 <do a "native" rebuild/install as described in the previous section>
1905 <maybe install compatibility libraries from ports/misc/compat*>
1909 To upgrade in-place from stable to current
1910 ----------------------------------------------
1911 <make sure you have good level 0 dumps>
1913 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1914 make installkernel KERNCONF=YOUR_KERNEL_HERE
1916 <reboot in single user> [3]
1923 Make sure that you've read the UPDATING file to understand the
1924 tweaks to various things you need. At this point in the life
1925 cycle of current, things change often and you are on your own
1926 to cope. The defaults can also change, so please read ALL of
1927 the UPDATING entries.
1929 Also, if you are tracking -current, you must be subscribed to
1930 freebsd-current@freebsd.org. Make sure that before you update
1931 your sources that you have read and understood all the recent
1932 messages there. If in doubt, please track -stable which has
1933 much fewer pitfalls.
1935 [1] If you have third party modules, such as vmware, you should disable
1936 them at this point so they don't crash your system on
1937 reboot. Alternatively, you should rebuild all the modules you have in
1938 your system and install them as well. If you are running -current, you
1939 should seriously consider placing all sources to all the modules for
1940 your system (or symlinks to them) in /usr/local/sys/modules so this
1941 happens automatically. If all your modules come from ports, then adding
1942 the port origin directories to PORTS_MODULES instead is also automatic
1944 PORTS_MODULES+=x11/nvidia-driver
1946 [3] From the bootblocks, boot -s, and then do
1950 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed
1951 cd src # full path to source
1952 adjkerntz -i # if CMOS is wall time
1953 Also, when doing a major release upgrade, it is required that you boot
1954 into single user mode to do the installworld.
1956 [4] Note: This step is non-optional. Failure to do this step
1957 can result in a significant reduction in the functionality of the
1958 system. Attempting to do it by hand is not recommended and those
1959 that pursue this avenue should read this file carefully, as well
1960 as the archives of freebsd-current and freebsd-hackers mailing lists
1961 for potential gotchas. See etcupdate(8) for more information.
1963 [5] Usually this step is a no-op. However, from time to time
1964 you may need to do this if you get unknown user in the following
1967 [6] This only deletes old files and directories. Old libraries
1968 can be deleted by "make delete-old-libs", but you have to make
1969 sure that no program is using those libraries anymore.
1971 [8] The new kernel must be able to run existing binaries used by an
1972 installworld. When upgrading across major versions, the new kernel's
1973 configuration must include the correct COMPAT_FREEBSD<n> option for
1974 existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure
1975 to do so may leave you with a system that is hard to boot to recover. A
1976 GENERIC kernel will include suitable compatibility options to run
1977 binaries from older branches. Note that the ability to run binaries
1978 from unsupported branches is not guaranteed.
1980 Make sure that you merge any new devices from GENERIC since the
1981 last time you updated your kernel config file. Options also
1982 change over time, so you may need to adjust your custom kernels
1985 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1986 "?=" instead of the "=" assignment operator, so that buildworld can
1987 override the CPUTYPE if it needs to.
1989 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1990 not on the command line, or in /etc/make.conf. buildworld will
1991 warn if it is improperly defined.
1994 This file contains a list, in reverse chronological order, of major
1995 breakages in tracking -current. It is not guaranteed to be a complete
1996 list of such breakages, and only contains entries since September 23, 2011.
1997 If you need to see UPDATING entries from before that date, you will need
1998 to fetch an UPDATING file from an older FreeBSD release.
2000 Copyright information:
2002 Copyright 1998-2009 M. Warner Losh <imp@FreeBSD.org>
2004 Redistribution, publication, translation and use, with or without
2005 modification, in full or in part, in any form or format of this
2006 document are permitted without further permission from the author.
2008 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2009 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2010 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2011 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2012 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2013 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2014 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2015 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2016 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2017 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2018 POSSIBILITY OF SUCH DAMAGE.
2020 Contact Warner Losh if you have any questions about your use of