1 Updating Information for users of FreeBSD-CURRENT.
3 This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>.
4 See end of file for further details. For commonly done items, please see the
5 COMMON ITEMS: section later in the file. These instructions assume that you
6 basically know what you are doing. If not, then please consult the FreeBSD
9 https://docs.freebsd.org/en/books/handbook/cutting-edge/#makeworld
11 Items affecting the ports and packages system can be found in
12 /usr/ports/UPDATING. Please read that file before updating system packages
15 NOTE TO PEOPLE WHO THINK THAT FreeBSD 15.x IS SLOW:
16 FreeBSD 15.x has many debugging features turned on, in both the kernel
17 and userland. These features attempt to detect incorrect use of
18 system primitives, and encourage loud failure through extra sanity
19 checking and fail stop semantics. They also substantially impact
20 system performance. If you want to do performance measurement,
21 benchmarking, and optimization, you'll want to turn them off. This
22 includes various WITNESS- related kernel options, INVARIANTS, malloc
23 debugging flags in userland, and various verbose features in the
24 kernel. Many developers choose to disable these features on build
25 machines to maximize performance. (To completely disable malloc
26 debugging, define WITH_MALLOC_PRODUCTION in /etc/src.conf and rebuild
27 world, or to merely disable the most expensive debugging functionality
28 at runtime, run "ln -s 'abort:false,junk:false' /etc/malloc.conf".)
31 dialog(1) has been replaced in base by bsddialog(1), while most of the
32 time replacing a dialog(1) call by a bsddialog(1) call works out of the
33 box, bsddialog(1) is not considered as a drop-in replacement for
36 If you do depend on dialog(1) functionality, please install cdialog
42 The EARLY_AP_STARTUP kernel option is mandatory on x86. The option
43 has been added to DEFAULTS, so it should automatically be included in
44 custom kernel configurations without any additional change.
47 A new loader tunable net.pf.default_to_drop allows pf(4)’s default
48 behaviour to be changed from pass to drop. Previously this required
49 recompiling the kernel with the option PF_DEFAULT_TO_DROP.
52 Enable splitting out pkgbase manpages into separate packages by
53 default. To disable this, set WITHOUT_MANSPLITPKG=yes in src.conf.
56 Move standard include files to the clibs-dev package and move clang
57 internal libraries and headers to clang and clang-dev. Upgrading systems
58 installed using pkgbase past this change involves extra steps to allow
61 pkg upgrade -y FreeBSD-utilities
62 pkg upgrade -y FreeBSD-utilities-dev
66 Enable vnet sysctl variables to be loader tunable. SYSCTLs which
67 belongs to VNETs can be initialized during early boot or module
68 loading if they are marked with CTLFLAG_TUN and there are
69 corresponding kernel environment variables.
72 The WITH_INIT_ALL_PATTERN and WITH_INIT_ALL_ZERO build options have
73 been replaced by INIT_ALL=pattern and INIT_ALL=zero respectively.
79 Serial communication (in boot loaders, kernel, and userland) has
80 been changed to default to 115200 bps, in line with common industry
81 practice and typcial firmware serial console redirection
84 Note that the early x86 BIOS bootloader (i.e., boot0sio) does not
85 support rates above 9600 bps and is not changed. boot0sio users may
86 set BOOT_COMCONSOLE_SPEED=9600 to use 9600 for all of the boot
87 components, or use the standard boot0 and have the boot2 stage start
88 with the serial port at 115200.
91 Following the general removal of MIPS support, the ath(4) AHB bus-
92 frontend has been removed, too, and building of the PCI support is
93 integrated with the ath(4) main module again. As a result, there's
94 no longer a need for if_ath_pci_load="YES" in /boot/loader.conf or
95 "device ath_pci" in the kernel configuration.
98 MAXCPU has been increased to 1024 in the amd64 GENERIC kernel config.
99 Out-of-tree kernel modules will need to be rebuilt.
102 CAM has been mechanically updated s/u_int(64|32|16|8)_t/uint\1_t/g
103 to move to the standard uintXX_t types from the old, traditional
104 BSD u_intXX_t types. This should be a NOP, but may cause problems
105 for out of tree changes. The SIMs were not updated since most of
106 the old u_intXX_t uses weren't due to CAM interfaces.
109 The heuristic for detecting old chromebooks with an EC bug that requires
110 atkbdc driver workarounds has changed. There should be no functional
111 change, but if your old chromebook's keyboard stops working, please
112 file a PR and assign it to imp.
115 OpenSSL has been updated to version 3.0, including changes throughout
116 the base system. It is important to rebuild third-party software
120 To enable pf rdr rules for connections initiated from the host, pf
121 filter rules can be optionally enabled for packets delivered
122 locally. This can change the behavior of rules which match packets
123 delivered to lo0. To enable this feature:
125 sysctl net.pf.filter_local=1
128 When enabled, its best to ensure that packets delivered locally are not
129 filtered, e.g. by adding a 'skip on lo' rule.
132 Improvements to libtacplus(8) mean that tacplus.conf(5) now
133 follows POSIX shell syntax rules. This may cause TACACS+
134 authentication to fail if the shared secret contains a single
135 quote, double quote, or backslash character which isn't
136 already properly quoted or escaped.
139 Belatedly switch the default nvme block device on x86 from nvd to nda.
140 nda created nvd compatibility links by default, so this should be a
141 nop. If this causes problems for your application, set hw.nvme.use_nvd=1
142 in your loader.conf or add `options NVME_USE_NVD=1` to your kernel
143 config. To disable the nvd compatibility aliases, add
144 kern.cam.nda.nvd_compat=0 to loader.conf. The default has been nda on
145 all non-x86 platforms for some time now. If you need to fall back,
146 please email imp@freebsd.org about why.
148 Encrypted swap partitions need to be changed from nvd to nda if you
149 migrate, or you need to use the above to switch back to nvd.
152 Remove portsnap(8). Users are encouraged to obtain the ports tree
156 Add jobs.mk to save typing. Enables -j${JOB_MAX} and logging
160 make -j${JOB_MAX} buildworld > ../buildworld.log 2>&1
162 where JOB_MAX is derrived from ncpus in local.sys.mk if not set in env.
165 Video related devices for some arm devices have been renamed.
166 If you have a custom kernel config and want to use hdmi output on
167 IMX6 board you need to add "device dwc_hdmi" "device imx6_hdmi" and
168 "device imx6_ipu" to it.
169 If you have a custom kernel config and want to use hdmi output on
170 TI AM335X board you need to add "device tda19988" to it.
171 If you add "device hdmi" in it you need to remove it as it doesn't
175 Introduce new kernel options KBD_DELAY1 and KBD_DELAY2. See atkbdc(4)
179 sshd now defaults to having X11Forwarding disabled, following upstream.
180 Administrators who wish to enable X11Forwarding should add
181 `X11Forwarding yes` to /etc/ssh/sshd_config.
184 Since commit 75d41cb6967 Huawei 3G/4G LTE Mobile Devices do not default
185 to ECM, but NCM mode and need u3g and ucom modules loaded. See cdce(4).
188 As of commit 7c40e2d5f685, the dependency on netlink(4) has been added
189 to the linux_common(4) module. Users relying on linux_common may need
190 to complile netlink(4) module if it is not present in their kernel.
193 The WITHOUT_CXX option has been removed. C++ components in the base
194 system are now built unconditionally.
197 LinuxKPI pci.h changes may require out-of-tree drivers to be recompiled.
198 Bump _FreeBSD_version to 1400078 to be able to detect this change.
201 llvm-objump is now always installed as objdump. Previously there was
202 no /usr/bin/objdump unless the WITH_LLVM_BINUTILS knob was used.
204 Some LLVM objdump options have a different output format compared to
205 GNU objdump; readelf is available for inspecting ELF files, and GNU
206 objdump is available from the devel/binutils port or package.
209 dma(8) has replaced sendmail(8) as the default mta. For people willing
210 to reenable sendmail(8):
212 $ cp /usr/share/examples/sendmail/mailer.conf /etc/mail/mailer.conf
214 and add sendmail_enable="YES" to rc.conf.
217 hw.bus.disable_failed_devices has changed from 'false' to 'true' by
218 default. Now if newbus succeeds in probing a device, but fails to attach
219 the device, we'll disable the device. In the past, we'd keep retrying
220 the device on each new driver loaded. To get that behavior now, one
221 needs to use devctl to re-enable the device, and reprobe it (or set
222 the sysctl/tunable hw.bus.disable_failed_devices=false).
224 NOTE: This was reverted 20221205 due to unexpected compatibility issues
227 pf no longer accepts 'scrub fragment crop' or 'scrub fragment drop-ovl'.
228 These configurations are no longer automatically reinterpreted as
229 'scrub fragment reassemble'.
232 The WITHOUT_CLANG_IS_CC option has been removed. When Clang is enabled
233 it is always installed as /usr/bin/cc (and c++, cpp).
236 Some programs have been moved into separate packages. It is recommended
237 for pkgbase users to do:
239 pkg install FreeBSD-dhclient FreeBSD-geom FreeBSD-resolvconf \
240 FreeBSD-devd FreeBSD-devmatch
242 after upgrading to restore all the component that were previously
246 OPIE has been removed from the base system. If needed, it can
247 be installed from ports (security/opie) or packages (opie).
248 Otherwise, make sure that your PAM policies do not reference
249 pam_opie or pam_opieaccess.
252 LinuxKPI pm.h changes require an update to the latest drm-kmod version
253 before re-compiling to avoid errors.
256 The macros provided for the manipulation of CPU sets (e.g. CPU_AND)
257 have been modified to take 2 source arguments instead of only 1.
258 Externally maintained sources that use these macros will have to
259 be adapted. The FreeBSD version has been bumped to 1400046 to
263 A number of the kernel include files are able to be included by
264 themselves. A test has been added to buildworld to enforce this.
267 Remove mips as a recognized target. This starts the decommissioning of
268 mips support in FreeBSD. mips related items will be removed wholesale in
269 the coming days and weeks.
271 This broke the NO_CLEAN build for some people. Either do a clean build
273 lib/clang/include/llvm/Config/Targets.def
274 lib/clang/include/llvm/Config/AsmParsers.def
275 lib/clang/include/llvm/Config/Disassemblers.def
276 lib/clang/include/llvm/Config/AsmPrinters.def
277 before the build to force everything to rebuild that needs to.
280 Unbound support for RFC8375: The special-use domain 'home.arpa' is
281 by default blocked. To unblock it use a local-zone nodefault
282 statement in unbound.conf:
283 local-zone: "home.arpa." nodefault
285 Or use another type of local-zone to override with your choice.
287 The reason for this is discussed in Section 6.1 of RFC8375:
288 Because 'home.arpa.' is not globally scoped and cannot be secured
289 using DNSSEC based on the root domain's trust anchor, there is no way
290 to tell, using a standard DNS query, in which homenet scope an answer
291 belongs. Consequently, users may experience surprising results with
292 such names when roaming to different homenets.
295 Commit b8d60729deef changed the TCP congestion control framework so
296 that any of the included congestion control modules could be
297 the single module built into the kernel. Previously newreno
298 was automatically built in through direct reference. As of
299 this commit you are required to declare at least one congestion
300 control module (e.g. 'options CC_NEWRENO') and to also declare a
301 default using the CC_DEFAULT option (e.g. options CC_DEFAULT="newreno\").
302 The GENERIC configuration includes CC_NEWRENO and defines newreno
303 as the default. If no congestion control option is built into the
304 kernel and you are including networking, the kernel compile will
305 fail. Also if no default is declared the kernel compile will fail.
308 Mips has been removed from universe builds. It will be removed from the
312 Commit f0c9847a6c47 changed the arguments for VOP_ALLOCATE.
313 The NFS modules must be rebuilt from sources and any out
314 of tree file systems that implement their own VOP_ALLOCATE
315 may need to be modified.
318 The synchronous PPP kernel driver sppp(4) has been removed.
319 The cp(4) and ce(4) drivers are now always compiled with netgraph(4)
320 support, formerly enabled by NETGRAPH_CRONYX option.
323 sh(1) is now the default shell for the root user. To force root to use
324 the csh shell, please run the following command as root:
329 Ncurses distribution has been split between libtinfow and libncurses
330 with libncurses.so becoming a linker (ld) script to seamlessly link
331 to libtinfow as needed. Bump _FreeBSD_version to 1400035 to reflect
335 As of commit 8160a0f62be6, the dummynet module no longer depends on the
336 ipfw module. Dummynet can now be used by pf as well as ipfw. As such
337 users who relied on this dependency may need to include ipfw in the
338 list of modules to load on their systems.
341 As of commit 903873ce1560, the mixer(8) utility has got a slightly
342 new syntax. Please refer to the mixer(8) manual page for more
343 information. The old mixer utility can be installed from ports:
344 audio/freebsd-13-mixer
347 As of commit 55089ef4f8bb, the global variable nfs_maxcopyrange has
348 been deleted from the nfscommon.ko. As such, nfsd.ko must be built
349 from up to date sources to avoid an undefined reference when
353 As of commit 62ca9fc1ad56 OpenSSL no longer enables kernel TLS
354 by default. Users can enable kernel TLS via the "KTLS" SSL
355 option. This can be enabled globally by using a custom
356 OpenSSL config file via OPENSSL_CONF or via an
357 application-specific configuration option for applications
358 which permit setting SSL options via SSL_CONF_cmd(3).
361 Commit 3ad1e1c1ce20 changed the internal KAPI between the NFS
362 modules. Therefore, all need to be rebuilt from sources.
365 Commit b69019c14cd8 removes pf's DIOCGETSTATESNV ioctl.
366 As of be70c7a50d32 it is no longer used by userspace, but it does mean
367 users may not be able to enumerate pf states if they update the kernel
368 past b69019c14cd8 without first updating userspace past be70c7a50d32.
371 As of commit 01ad0c007964 if_bridge member interfaces can no longer
372 change their MTU. Changing the MTU of the bridge itself will change the
373 MTU on all member interfaces instead.
376 Commit ee29e6f31111 changed the internal KAPI between the nfscommon
377 and nfsd modules. Therefore, both need to be rebuilt from sources.
378 Bump __FreeBSD_version to 1400026 for this KAPI change.
381 The 20210707 awk update brought in a change in behavior. This has
382 been corrected as of d4d252c49976. Between these dates, if you
383 installed a new awk binary, you may not be able to build a new
384 kernel because the change in behavior affected the genoffset
385 script used to build the kernel. If you did update, the fix is
386 to update your sources past the above hash and do
389 % sudo -E make install
390 to enable building kernels again.
393 Commit 1e0a518d6548 changed the internal KAPI between the NFS
394 modules. They all need to be rebuilt from sources. I did not
395 bump __FreeBSD_version, since it was bumped recently.
398 awk has been updated to the latest one-true-awk version 20210215.
399 This contains a number of minor bug fixes.
402 The NFSv4 client now uses the highest minor version of NFSv4
403 supported by the NFSv4 server by default instead of minor version 0,
405 The "minorversion" mount option may be used to override this default.
408 Bump __FreeBSD_version to 1400024 for LinuxKPI changes.
409 Most notably netdev.h can change now as the (last) dependencies
410 (mlx4/ofed) are now using struct ifnet directly, but also for PCI
411 additions and others.
414 The directory "blacklisted" under /usr/share/certs/ has been
415 renamed to "untrusted".
418 svnlite has been removed from base. Should you need svn for any reason
419 please install the svn package or port.
422 Commit e1a907a25cfa changed the internal KAPI between the krpc
423 and nfsserver. As such, both modules must be rebuilt from
424 sources. Bump __FreeBSD_version to 1400022.
427 The an(4) driver has been removed from FreeBSD.
430 The vendor/openzfs branch was renamed to vendor/openzfs/legacy to
431 start tracking OpenZFS upstream more closely. Please see
432 https://lists.freebsd.org/archives/freebsd-current/2021-June/000153.html
433 for details on how to correct any errors that might result. The
434 short version is that you need to remove the old branch locally:
435 git update-ref -d refs/remotes/freebsd/vendor/openzfs
436 (assuming your upstream origin is named 'freebsd').
439 Commits 17accc08ae15 and de102f870501 add new files to LinuxKPI
440 which break drm-kmod. In addition various other additions where
441 committed. Bump __FreeBSD_version to 1400015 to be able to
445 Commit ca179c4d74f2 changed the package in which the OpenSSL
446 libraries and utilities are packaged.
447 It is recommended for pkgbase user to do:
448 pkg install -f FreeBSD-openssl
449 before pkg upgrade otherwise some dependencies might not be met
450 and pkg will stop working as libssl will not be present anymore
454 Commit 875977314881 changed the internal KAPI between
455 the nfsd and nfscommon modules. As such these modules
456 need to be rebuilt from sources.
457 Without this patch in your NFSv4.1/4.2 server, enabling
458 delegations by setting vfs.nfsd.issue_delegations non-zero
462 Commit 7763814fc9c2 changed the internal KAPI between
463 the krpc and NFS. As such, the krpc, nfscommon and
464 nfscl modules must all be rebuilt from sources.
465 Without this patch, NFSv4.1/4.2 mounts should not
466 be done with the nfscbd(8) daemon running, to avoid
467 needing a working back channel for server->client RPCs.
470 Commit 01ae8969a9ee fixed the NFSv4.1/4.2 server so that it
471 handles binding of the back channel as required by RFC5661.
472 Until this patch is in your server, avoid use of the "nconnects"
473 mount option for Linux NFSv4.1/4.2 mounts.
476 For 64-bit architectures the base system is now built with Position
477 Independent Executable (PIE) support enabled by default. It may be
478 disabled using the WITHOUT_PIE knob. A clean build is required.
481 Various LinuxKPI functionality was added which conflicts with DRM.
482 Please update your drm-kmod port to after the __FreeBSD_version 1400003
486 PC Card attachments for all devices have been removed. In the case of
487 wi and cmx, the entire drivers were removed because they were only
488 PC Card devices. FreeBSD_version 1300134 should be used for this
489 since it was bumped so recently.
492 Transport-independent parts of HID support have been split off the USB
493 code in to separate subsystem. Kernel configs which include one of
494 ums, ukbd, uhid, atp, wsp, wmt, uaudio, ugold or ucycom drivers should
495 be updated with adding of "device hid" line.
498 ncurses installation has been modified to only keep the widechar
499 enabled version. Incremental build is broken for that change, so it
500 requires a clean build.
503 The FreeBSD project has migrated from Subversion to Git. Temporary
504 instructions can be found at
505 https://github.com/bsdimp/freebsd-git-docs/blob/main/src-cvt.md
506 and other documents in that repo.
509 The services database has been updated to cover more of the basic
510 services expected in a modern system. The database is big enough
511 that it will cause issues in mergemaster in Releases previous to
512 12.2 and 11.3, or in very old current systems from before r358154.
515 Obsolete in-tree GDB 6.1.1 has been removed. GDB (including kgdb)
516 may be installed from ports or packages.
519 ping6 has been merged into ping. It can now be called as "ping -6".
520 See ping(8) for details.
523 Default value of net.add_addr_allfibs has been changed to 0.
524 If you have multi-fib configuration and rely on existence of all
525 interface routes in every fib, you need to set the above sysctl to 1.
528 The internal pre-processor in the calendar(1) program has been
529 extended to support more C pre-processor commands (e.g. #ifdef, #else,
530 and #undef) and to detect unbalanced conditional statements.
531 Error messages have been extended to include the filename and line
532 number if processing stops to help fixing malformed data files.
535 All the data files for the calendar(1) program, except calendar.freebsd,
536 have been moved to the deskutils/calendar-data port, much like the
537 jewish calendar entries were moved to deskutils/hebcal years ago. After
538 make delete-old-files, you need to install it to retain full
539 functionality. calendar(1) will issue a reminder for files it can't
543 LINT files are no longer generated. We now include the relevant NOTES
544 files. Note: This may cause conflicts with updating in some cases.
545 find sys -name LINT\* -delete
546 is suggested across this commit to remove the generated LINT files.
548 If you have tried to update with generated files there, the svn
549 command you want to un-auger the tree is
552 and then do the above find from the top level. Substitute 'amd64'
553 above with where the error message indicates a conflict.
556 OpenZFS support has been integrated. Do not upgrade root pools until
557 the loader is updated to support zstd. Furthermore, we caution against
558 'zpool upgrade' for the next few weeks. The change should be transparent
559 unless you want to use new features.
561 Not all "NO_CLEAN" build scenarios work across these changes. Many
562 scenarios have been tested and fixed, but rebuilding kernels without
563 rebuilding world may fail.
565 The ZFS cache file has moved from /boot to /etc to match the OpenZFS
566 upstream default. A fallback to /boot has been added for mountroot.
568 Pool auto import behavior at boot has been moved from the kernel module
569 to an explicit "zpool import -a" in one of the rc scripts enabled by
570 zfs_enable=YES. This means your non-root zpools won't auto import until
571 you upgrade your /etc/rc.d files.
574 The resume code now notifies devd with the 'kernel' system
575 rather than the old 'kern' subsystem to be consistent with
576 other use. The old notification will be created as well, but
577 will be removed prior to FreeBSD 14.0.
580 r362275 changed the internal API between the kernel RPC and the
581 NFS modules. As such, all the modules must be recompiled from
585 r364330 modified the internal API used between the NFS modules.
586 As such, all the NFS modules must be re-compiled from sources.
589 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
590 been upgraded to 11.0.0. Please see the 20141231 entry below for
591 information about prerequisites and upgrading, if you are not already
592 using clang 3.5.0 or higher.
595 r364092 modified the internal ABI used between the kernel NFS
596 modules. As such, all of these modules need to be rebuilt
597 from sources, so a version bump was done.
600 Makefile.inc has been updated to work around the issue documented in
601 20200729. It was a case where the optimization of using symbolic links
602 to point to binaries created a situation where we'd run new binaries
603 with old libraries starting midway through the installworld process.
606 r363679 has redefined some undefined behavior in regcomp(3); notably,
607 extraneous escapes of most ordinary characters will no longer be
608 accepted. An exp-run has identified all of the problems with this in
609 ports, but other non-ports software may need extra escapes removed to
610 continue to function.
612 Because of this change, installworld may encounter the following error
613 from rtld: Undefined symbol "regcomp@FBSD_1.6" -- It is imperative that
614 you do not halt installworld. Instead, let it run to completion (whether
615 successful or not) and run installworld once more.
618 A new implementation of bc and dc has been imported in r362681. This
619 implementation corrects non-conformant behavior of the previous bc
620 and adds GNU bc compatible options. It offers a number of extensions,
621 is much faster on large values, and has support for message catalogs
622 (a number of languages are already supported, contributions of further
623 languages welcome). The option WITHOUT_GH_BC can be used to build the
624 world with the previous versions of bc and dc.
627 r362639 changed the internal API used between the NFS kernel modules.
628 As such, they all need to be rebuilt from sources.
631 r362158 changed the arguments for VFS_CHECKEXP(). As such, any
632 out of tree file systems need to be modified and rebuilt.
633 Also, any file systems that are modules must be rebuilt.
636 read(2) of a directory fd is now rejected by default. root may
637 re-enable it for system root only on non-ZFS filesystems with the
638 security.bsd.allow_read_dir sysctl(8) MIB if
639 security.bsd.suser_enabled=1.
641 It may be advised to setup aliases for grep to default to `-d skip` if
642 commonly non-recursively grepping a list that includes directories and
643 the potential for the resulting stderr output is not tolerable. Example
644 aliases are now installed, commented out, in /root/.cshrc and
648 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
649 been upgraded to 10.0.1. Please see the 20141231 entry below for
650 information about prerequisites and upgrading, if you are not already
651 using clang 3.5.0 or higher.
654 Support for obsolete compilers has been removed from the build system.
655 Clang 6 and GCC 6.4 are the minimum supported versions.
658 closefrom(2) has been moved under COMPAT12, and replaced in libc with a
659 stub that calls close_range(2). If using a custom kernel configuration,
660 you may want to ensure that the COMPAT_FREEBSD12 option is included, as
661 a slightly older -CURRENT userland and older FreeBSD userlands may not
662 be functional without closefrom(2).
665 Upstream DTS from Linux 5.6 was merged and they now have the SID
666 and THS (Secure ID controller and THermal Sensor) node present.
667 The DTB overlays have now been removed from the tree for the H3/H5 and
668 A64 SoCs and the aw_sid and aw_thermal driver have been updated to
669 deal with upstream DTS. If you are using those overlays you need to
670 remove them from loader.conf and update the DTBs on the FAT partition.
673 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
674 been upgraded to 10.0.0. Please see the 20141231 entry below for
675 information about prerequisites and upgrading, if you are not already
676 using clang 3.5.0 or higher.
679 The amd(8) automount daemon has been removed from the source tree.
680 As of FreeBSD 10.1 autofs(5) is the preferred tool for automounting.
681 amd is still available in the sysutils/am-utils port.
684 Removed brooktree driver (bktr.4) from the tree.
687 The WITH_GPL_DTC option has been removed. The BSD-licenced device tree
688 compiler in usr.bin/dtc is used on all architectures which use dtc, and
689 the GPL dtc is available (if needed) from the sysutils/dtc port.
692 The WITHOUT_LLVM_LIBUNWIND option has been removed. LLVM's libunwind
693 is used by all supported CPU architectures.
696 GCC 4.2.1 has been removed from the tree. The WITH_GCC,
697 WITH_GCC_BOOTSTRAP, and WITH_GNUCXX options are no longer available.
698 Users who wish to build FreeBSD with GCC must use the external toolchain
702 ncurses has been updated to a newer version (6.2-20200215). Given the ABI
703 has changed, users will have to rebuild all the ports that are linked to
707 The size of struct vnet and the magic cookie have changed.
708 Users need to recompile libkvm and all modules using VIMAGE
709 together with their new kernel.
712 Defining the long deprecated NO_CTF, NO_DEBUG_FILES, NO_INSTALLLIB,
713 NO_MAN, NO_PROFILE, and NO_WARNS variables is now an error. Update
714 your Makefiles and scripts to define MK_<var>=no instead as required.
716 One exception to this is that program or library Makefiles should
717 define MAN to empty rather than setting MK_MAN=no.
720 Clang/LLVM is now the default compiler and LLD the default
724 make universe no longer uses GCC 4.2.1 on any architectures.
725 Architectures not supported by in-tree Clang/LLVM require an
726 external toolchain package.
729 GCC 4.2.1 is now not built by default, as part of the GCC 4.2.1
730 retirement plan. Specifically, the GCC, GCC_BOOTSTRAP, and GNUCXX
731 options default to off for all supported CPU architectures. As a
732 short-term transition aid they may be enabled via WITH_* options.
733 GCC 4.2.1 is expected to be removed from the tree on 2020-03-31.
736 Support for armv5 has been disconnected and is being removed. The
737 machine combination MACHINE=arm MACHINE_ARCH=arm is no longer valid.
738 You must now use a MACHINE_ARCH of armv6 or armv7. The default
739 MACHINE_ARCH for MACHINE=arm is now armv7.
742 Clang/LLVM is now the default compiler for all powerpc architectures.
743 LLD is now the default linker for powerpc64. The change for powerpc64
744 also includes a change to the ELFv2 ABI, incompatible with the existing
748 Kernel-loadable random(4) modules are no longer unloadable.
751 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
752 been upgraded to 9.0.1. Please see the 20141231 entry below for
753 information about prerequisites and upgrading, if you are not already
754 using clang 3.5.0 or higher.
757 r355677 has modified the internal interface used between the
758 NFS modules in the kernel. As such, they must all be upgraded
759 simultaneously. I will do a version bump for this.
762 The root certificates of the Mozilla CA Certificate Store have been
763 imported into the base system and can be managed with the certctl(8)
764 utility. If you have installed the security/ca_root_nss port or package
765 with the ETCSYMLINK option (the default), be advised that there may be
766 differences between those included in the port and those included in
767 base due to differences in nss branch used as well as general update
768 frequency. Note also that certctl(8) cannot manage certs in the
769 format used by the security/ca_root_nss port.
772 The amd(8) automount daemon has been disabled by default, and will be
773 removed in the future. As of FreeBSD 10.1 the autofs(5) is available
777 The nctgpio and wbwd drivers have been moved to the superio bus.
778 If you have one of these drivers in a kernel configuration, then
779 you should add device superio to it. If you use one of these drivers
780 as a module and you compile a custom set of modules, then you should
781 add superio to the set.
784 KPIs for network drivers to access interface addresses have changed.
785 Users need to recompile NIC driver modules together with kernel.
788 The net.link.tap.user_open sysctl no longer prevents user opening of
789 already created /dev/tapNN devices. Access is still controlled by
790 node permissions, just like tun devices. The net.link.tap.user_open
791 sysctl is now used only to allow users to perform devfs cloning of
792 tap devices, and the subsequent open may not succeed if the user is not
793 in the appropriate group. This sysctl may be deprecated/removed
794 completely in the future.
797 mips, powerpc, and sparc64 are no longer built as part of
798 universe / tinderbox unless MAKE_OBSOLETE_GCC is defined. If
799 not defined, mips, powerpc, and sparc64 builds will look for
800 the xtoolchain binaries and if installed use them for universe
801 builds. As llvm 9.0 becomes vetted for these architectures, they
802 will be removed from the list.
805 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
806 been upgraded to 9.0.0. Please see the 20141231 entry below for
807 information about prerequisites and upgrading, if you are not already
808 using clang 3.5.0 or higher.
811 The hpt27xx, hptmv, hptnr, and hptrr drivers have been removed from
812 GENERIC. They are available as modules and can be loaded by adding
813 to /boot/loader.conf hpt27xx_load="YES", hptmv_load="YES",
814 hptnr_load="YES", or hptrr_load="YES", respectively.
817 ntpd no longer by default locks its pages in memory, allowing them
818 to be paged out by the kernel. Use rlimit memlock to restore
819 historic BSD behaviour. For example, add "rlimit memlock 32"
820 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
823 Several of ping6's options have been renamed for better consistency
824 with ping. If you use any of -ARWXaghmrtwx, you must update your
825 scripts. See ping6(8) for details.
828 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
829 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
830 been removed from mount_fusefs(8). You can safely remove them from
831 your scripts, because they had no effect.
833 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
834 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
835 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
836 sysctls have been removed. If you felt the need to set any of them to
837 a non-default value, please tell asomers@FreeBSD.org why.
840 Default permissions on the /var/account/acct file (and copies of it
841 rotated by periodic daily scripts) are changed from 0644 to 0640
842 because the file contains sensitive information that should not be
843 world-readable. If the /var/account directory must be created by
844 rc.d/accounting, the mode used is now 0750. Admins who use the
845 accounting feature are encouraged to change the mode of an existing
846 /var/account directory to 0750 or 0700.
849 Entropy collection and the /dev/random device are no longer optional
850 components. The "device random" option has been removed.
851 Implementations of distilling algorithms can still be made loadable
852 with "options RANDOM_LOADABLE" (e.g., random_fortuna.ko).
855 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
856 been upgraded to 8.0.1. Please see the 20141231 entry below for
857 information about prerequisites and upgrading, if you are not already
858 using clang 3.5.0 or higher.
861 A fix was applied to i386 kernel modules to avoid panics with
862 dpcpu or vnet. Users need to recompile i386 kernel modules
863 having pcpu or vnet sections or they will refuse to load.
866 User-wired pages now have their own counter,
867 vm.stats.vm.v_user_wire_count. The vm.max_wired sysctl was renamed
868 to vm.max_user_wired and changed from an unsigned int to an unsigned
869 long. bhyve VMs wired with the -S are now subject to the user
870 wiring limit; the vm.max_user_wired sysctl may need to be tuned to
871 avoid running into the limit.
874 The IPSEC option has been removed from GENERIC. Users requiring
875 ipsec(4) must now load the ipsec(4) kernel module.
878 The tap(4) driver has been folded into tun(4), and the module has been
879 renamed to tuntap. You should update any kld_list="if_tap" or
880 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
881 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
882 module instead, and "device tap" or "device tun" entries in kernel
883 config files to select the tuntap device instead.
886 The following knobs have been added related to tradeoffs between
887 safe use of the random device and availability in the absence of
890 kern.random.initial_seeding.bypass_before_seeding: tunable; set
891 non-zero to bypass the random device prior to seeding, or zero to
892 block random requests until the random device is initially seeded.
893 For now, set to 1 (unsafe) by default to restore pre-r346250 boot
894 availability properties.
896 kern.random.initial_seeding.read_random_bypassed_before_seeding:
897 read-only diagnostic sysctl that is set when bypass is enabled and
898 read_random(9) is bypassed, to enable programmatic handling of this
899 initial condition, if desired.
901 kern.random.initial_seeding.arc4random_bypassed_before_seeding:
902 Similar to the above, but for arc4random(9) initial seeding.
904 kern.random.initial_seeding.disable_bypass_warnings: tunable; set
905 non-zero to disable warnings in dmesg when the same conditions are
906 met as for the diagnostic sysctls above. Defaults to zero, i.e.,
907 produce warnings in dmesg when the conditions are met.
910 The loadable random module KPI has changed; the random_infra_init()
911 routine now requires a 3rd function pointer for a bool (*)(void)
912 method that returns true if the random device is seeded (and
913 therefore unblocked).
916 r345895 reverts r320698. This implies that an nfsuserd(8) daemon
917 built from head sources between r320757 (July 6, 2017) and
918 r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
919 is added to the command line.
920 nfsuserd daemons built from head sources that are post-r338192 are
921 not affected and should continue to work.
924 The fuse(4) module has been renamed to fusefs(4) for consistency with
925 other filesystems. You should update any kld_load="fuse" entries in
926 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
927 "options FUSE" entries in kernel config files.
930 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
931 8.0.0. Please see the 20141231 entry below for information about
932 prerequisites and upgrading, if you are not already using clang 3.5.0
936 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
937 compiled into your custom kernel, add 'device xz' statement to the
941 drm and drm2 have been removed from the tree. Please see
942 https://wiki.freebsd.org/Graphics for the latest information on
943 migrating to the drm ports.
946 Iflib is no longer unconditionally compiled into the kernel. Drivers
947 using iflib and statically compiled into the kernel, now require
948 the 'device iflib' config option. For the same drivers loaded as
949 modules on kernels not having 'device iflib', the iflib.ko module
950 is loaded automatically.
953 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
954 options no longer exist since r343219 and r343427 respectively;
955 nothing uses them, so they should be just removed from custom
959 r342635 changes the way efibootmgr(8) works by requiring users to add
960 the -b (bootnum) parameter for commands where the bootnum was previously
961 specified with each option. For example 'efibootmgr -B 0001' is now
962 'efibootmgr -B -b 0001'.
965 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
966 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
967 servers that have vfs.nfsd.nfs_privport set will only allow mounts
968 from clients using a reserved port. Since both the FreeBSD and Linux
969 NFSv4 clients use reserved ports by default, this should not affect
973 The XLP config has been removed. We can't support 64-bit atomics in this
974 kernel because it is running in 32-bit mode. XLP users must transition
975 to running a 64-bit kernel (XLP64 or XLPN32).
977 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
978 the preferred emulator today and we don't need two different ones.
980 The old sibyte / swarm / Broadcom BCM1250 support has been
981 removed from the mips port.
984 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
985 7.0.1. Please see the 20141231 entry below for information about
986 prerequisites and upgrading, if you are not already using clang 3.5.0
990 Remove the timed and netdate programs from the base tree. Setting
991 the time with these daemons has been obsolete for over a decade.
994 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
995 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
996 it produces broken binaries when ifuncs are in use. Users needing
997 GNU ld should install the binutils port or package.
1000 The BSD crtbegin and crtend code has been enabled by default. It has
1001 had extensive testing on amd64, arm64, and i386. It can be disabled
1002 by building a world with -DWITHOUT_BSD_CRTBEGIN.
1005 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
1006 has been converted to a port (misc/ctm) and will be removed from
1007 FreeBSD-13. It is available as a package (ctm) for all supported
1011 The default newsyslog.conf(5) file has been changed to only include
1012 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
1013 the filenames end in '.conf' and do not begin with a '.'.
1015 You should check the configuration files in these two directories match
1016 this naming convention. You can verify which configuration files are
1017 being included using the command:
1021 Ports for the DRM modules have been simplified. Now, amd64 users should
1022 just install the drm-kmod port. All others should install
1025 Graphics hardware that's newer than about 2010 usually works with
1026 drm-kmod. For hardware older than 2013, however, some users will need
1027 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
1028 than 2008 usually only works in drm-legacy-kmod. The graphics team can
1029 only commit to hardware made since 2013 due to the complexity of the
1030 market and difficulty to test all the older cards effectively. If you
1031 have hardware supported by drm-kmod, you are strongly encouraged to use
1032 that as you will get better support.
1034 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
1035 elsewhere, the drm and drm2 modules will be eliminated from the src base
1036 soon (with a limited exception for arm). Please update to the package
1037 asap and report any issues to x11@freebsd.org.
1039 Generally, anybody using the drm*-kmod packages should add
1040 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
1041 cross-threading surprises, especially with automatic driver
1042 loading from X11 startup. These will become the defaults in 13-current
1046 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
1047 custom kernel and module loading configuration files must be updated
1048 accordingly. Moreover, interfaces previous presented as ixlvN to the
1049 system are now exposed as iavfN and network configuration files must
1050 be adjusted as necessary.
1053 OpenSSL has been updated to version 1.1.1. This update included
1054 additional various API changes throughout the base system. It is
1055 important to rebuild third-party software after upgrading. The value
1056 of __FreeBSD_version has been bumped accordingly.
1059 The legacy DRM modules and drivers have now been added to the loader's
1060 module blacklist, in favor of loading them with kld_list in rc.conf(5).
1061 The module blacklist may be overridden with the loader.conf(5)
1062 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
1066 The cam(4) based nda(4) driver will be used over nvd(4) by default on
1067 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
1068 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
1069 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
1073 Reproducible build mode is now on by default, in preparation for
1074 FreeBSD 12.0. This eliminates build metadata such as the user,
1075 host, and time from the kernel (and uname), unless the working tree
1076 corresponds to a modified checkout from a version control system.
1077 The previous behavior can be obtained by setting the /etc/src.conf
1078 knob WITHOUT_REPRODUCIBLE_BUILD.
1081 The Yarrow CSPRNG has been removed from the kernel as it has not been
1082 supported by its designers since at least 2003. Fortuna has been the
1083 default since FreeBSD-11.
1086 devctl freeze/thaw have gone into the tree, the rc scripts have been
1087 updated to use them and devmatch has been changed. You should update
1088 kernel, userland and rc scripts all at the same time.
1091 The default interpreter has been switched from 4th to Lua.
1092 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
1093 interpreter. If you have custom FORTH code you will need to set
1094 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
1095 src.conf for the build. This will create default hard links between
1096 loader and loader_4th instead of loader and loader_lua, the new default.
1097 If you are using UEFI it will create the proper hard link to loader.efi.
1099 bhyve uses userboot.so. It remains 4th-only until some issues are solved
1100 regarding coexisting with multiple versions of FreeBSD are resolved.
1103 ls(1) now respects the COLORTERM environment variable used in other
1104 systems and software to indicate that a colored terminal is both
1105 supported and desired. If ls(1) is suddenly emitting colors, they may
1106 be disabled again by either removing the unwanted COLORTERM from your
1107 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
1108 may not be observed in a future release.
1111 The default pager for most commands has been changed to "less". To
1112 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
1116 The jedec_ts(4) driver has been removed. A superset of its functionality
1117 is available in the jedec_dimm(4) driver, and the manpage for that
1118 driver includes migration instructions. If you have "device jedec_ts"
1119 in your kernel configuration file, it must be removed.
1122 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
1123 This should have no effect if the kernel is booted via BIOS/legacy boot.
1124 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
1125 has a buggy firmware that prevents a successful boot due to use of
1129 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
1130 support has been removed from the tree. These ports were
1131 obsolete and/or known to be broken for many years.
1134 loader.efi has been augmented to participate more fully in the
1135 UEFI boot manager protocol. loader.efi will now look at the
1136 BootXXXX environment variable to determine if a specific kernel
1137 or root partition was specified. XXXX is derived from BootCurrent.
1138 efibootmgr(8) manages these standard UEFI variables.
1141 zfsloader's functionality has now been folded into loader.
1142 zfsloader is no longer necessary once you've updated your
1143 boot blocks. For a transition period, we will install a
1144 hardlink for zfsloader to loader to allow a smooth transition
1145 until the boot blocks can be updated (hard link because old
1146 zfs boot blocks don't understand symlinks).
1149 ARM64 now have efifb support, if you want to have serial console
1150 on your arm64 board when an screen is connected and the bootloader
1151 setup a frame buffer for us to use, just add :
1154 in /boot/loader.conf
1155 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
1156 an screen connected as the firmware will setup a frame buffer are that
1157 u-boot will expose as an EFI frame buffer.
1160 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
1161 or take steps to update /etc/passwd before doing installworld on
1162 existing systems. Do not skip the "mergemaster -Fp" step before
1163 installworld, as described in the update procedures near the bottom
1164 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
1165 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
1166 the ntp config file contain options that change file/dir locations.
1167 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
1168 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
1169 taking steps to ensure that all required files/dirs are accessible
1173 Big endian arm support has been removed.
1176 The static environment setup in kernel configs is no longer mutually
1177 exclusive with the loader(8) environment by default. In order to
1178 restore the previous default behavior of disabling the loader(8)
1179 environment if a static environment is present, you must specify
1180 loader_env.disabled=1 in the static environment.
1183 The ABI of syscalls used by management tools like sockstat and
1184 netstat has been broken to allow 32-bit binaries to work on
1185 64-bit kernels without modification. These programs will need
1186 to match the kernel in order to function. External programs may
1187 require minor modifications to accommodate a change of type in
1188 structures from pointers to 64-bit virtual addresses.
1191 On i386 and amd64 atomics are now inlined. Out of tree modules using
1192 atomics will need to be rebuilt.
1195 The '%I' format in the kern.corefile sysctl limits the number of
1196 core files that a process can generate to the number stored in the
1197 debug.ncores sysctl. The '%I' format is replaced by the single digit
1198 index. Previously, if all indexes were taken the kernel would overwrite
1199 only a core file with the highest index in a filename.
1200 Currently the system will create a new core file if there is a free
1201 index or if all slots are taken it will overwrite the oldest one.
1204 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
1205 6.0.1. Please see the 20141231 entry below for information about
1206 prerequisites and upgrading, if you are not already using clang 3.5.0
1210 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
1211 needed to be changed to work with it. This change was made with r335763
1212 and requires a mergemaster / etcupdate / etc to update the installed
1216 r334930 changed the interface between the NFS modules, so they all
1217 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
1220 As of r334391 lld is the default amd64 system linker; it is installed
1221 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
1225 The kernel / userland interface for devinfo changed, so you'll
1226 need a new kernel and userland as a pair for it to work (rebuilding
1227 lib/libdevinfo is all that's required). devinfo and devmatch will
1228 not work, but everything else will when there's a mismatch.
1231 The on-disk format for hwpmc callchain records has changed to include
1232 threadid corresponding to a given record. This changes the field offsets
1233 and thus requires that libpmcstat be rebuilt before using a kernel
1237 The vxge(4) driver has been removed. This driver was introduced into
1238 HEAD one week before the Exar left the Ethernet market and is not
1239 known to be used. If you have device vxge in your kernel config file
1243 The amd64 kernel now requires a ld that supports ifunc to produce a
1244 working kernel, either lld or a newer binutils. lld is built by default
1245 on amd64, and the 'buildkernel' target uses it automatically. However,
1246 it is not the default linker, so building the kernel the traditional
1247 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
1248 binutils port/package). lld will soon be default, and this requirement
1251 NOTE: As of r334391 lld is the default system linker on amd64, and no
1252 workaround is necessary.
1255 The nxge(4) driver has been removed. This driver was for PCI-X 10g
1256 cards made by s2io/Neterion. The company was acquired by Exar and
1257 no longer sells or supports Ethernet products. If you have device
1258 nxge in your kernel config file it must be removed.
1261 The tz database (tzdb) has been updated to 2018e. This version more
1262 correctly models time stamps in time zones with negative DST such as
1263 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
1264 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
1265 time zone abbreviations and the tm_isdst flag.
1268 The ixgb(4) driver has been removed. This driver was for an early and
1269 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
1270 quickly shifted to the long lived ixgbe family. If you have device
1271 ixgb in your kernel config file it must be removed.
1274 The lmc(4) driver has been removed. This was a WAN interface
1275 card that was already reportedly rare in 2003, and had an ambiguous
1276 license. If you have device lmc in your kernel config file it must
1280 Support for Arcnet networks has been removed. If you have device
1281 arcnet or device cm in your kernel config file they must be
1285 Support for FDDI networks has been removed. If you have device
1286 fddi or device fpa in your kernel config file they must be
1290 In addition to supporting RFC 3164 formatted messages, the
1291 syslogd(8) service is now capable of parsing RFC 5424 formatted
1292 log messages. The main benefit of using RFC 5424 is that clients
1293 may now send log messages with timestamps containing year numbers,
1294 microseconds and time zone offsets.
1296 Similarly, the syslog(3) C library function has been altered to
1297 send RFC 5424 formatted messages to the local system logging
1298 daemon. On systems using syslogd(8), this change should have no
1299 negative impact, as long as syslogd(8) and the C library are
1300 updated at the same time. On systems using a different system
1301 logging daemon, it may be necessary to make configuration
1302 adjustments, depending on the software used.
1304 When using syslog-ng, add the 'syslog-protocol' flag to local
1305 input sources to enable parsing of RFC 5424 formatted messages:
1308 unix-dgram("/var/run/log" flags(syslog-protocol));
1311 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
1312 of the 'imuxsock' module to let messages be processed by the
1313 regular RFC 3164/5424 parsing pipeline:
1315 module(load="imuxsock" SysSock.UseSpecialParser="off")
1317 Do note that these changes only affect communication between local
1318 applications and syslogd(8). The format that syslogd(8) uses to
1319 store messages on disk or forward messages to other systems
1320 remains unchanged. syslogd(8) still uses RFC 3164 for these
1321 purposes. Options to customize this behaviour will be added in the
1322 future. Utilities that process log files stored in /var/log are
1323 thus expected to continue to function as before.
1325 __FreeBSD_version has been incremented to 1200061 to denote this
1329 Support for token ring networks has been removed. If you
1330 have "device token" in your kernel config you should remove
1331 it. No device drivers supported token ring.
1334 makefs was modified to be able to tag ISO9660 El Torito boot catalog
1335 entries as EFI instead of overloading the i386 tag as done previously.
1336 The amd64 mkisoimages.sh script used to build amd64 ISO images for
1337 release was updated to use this. This may mean that makefs must be
1338 updated before "make cdrom" can be run in the release directory. This
1339 should be as simple as:
1341 $ cd $SRCDIR/usr.sbin/makefs
1342 $ make depend all install
1345 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
1346 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
1347 Co-existence for the transition period will come shortly. Booting is a
1348 complex environment and test coverage for Lua-enabled loaders has been
1349 thin, so it would be prudent to assume it might not work and make
1350 provisions for backup boot methods.
1353 devmatch functionality has been turned on in devd. It will automatically
1354 load drivers for unattached devices. This may cause unexpected drivers
1355 to be loaded. Please report any problems to current@ and
1359 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
1360 6.0.0. Please see the 20141231 entry below for information about
1361 prerequisites and upgrading, if you are not already using clang 3.5.0
1365 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
1366 This means it is used to link the kernel and userland libraries and
1367 executables, but is not yet installed as /usr/bin/ld by default.
1369 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
1370 WITHOUT_LLD_BOOTSTRAP=yes
1373 On i386, pmtimer has been removed. Its functionality has been folded
1374 into apm. It was a no-op on ACPI in current for a while now (but was
1375 still needed on i386 in FreeBSD 11 and earlier). Users may need to
1376 remove it from kernel config files.
1379 The use of RSS hash from the network card aka flowid has been
1380 disabled by default for lagg(4) as it's currently incompatible with
1381 the lacp and loadbalance protocols.
1383 This can be re-enabled by setting the following in loader.conf:
1384 net.link.lagg.default_use_flowid="1"
1387 The SW_WATCHDOG option is no longer necessary to enable the
1388 hardclock-based software watchdog if no hardware watchdog is
1389 configured. As before, SW_WATCHDOG will cause the software
1390 watchdog to be enabled even if a hardware watchdog is configured.
1393 r326887 fixes the issue described in the 20171214 UPDATING entry.
1394 r326888 flips the switch back to building GELI support always.
1397 r362593 broke ZFS + GELI support for reasons unknown. However,
1398 it also broke ZFS support generally, so GELI has been turned off
1399 by default as the lesser evil in r326857. If you boot off ZFS and/or
1400 GELI, it might not be a good time to update.
1403 PowerPC users must update loader(8) by rebuilding world before
1404 installing a new kernel, as the protocol connecting them has
1405 changed. Without the update, loader metadata will not be passed
1406 successfully to the kernel and users will have to enter their
1407 root partition at the kernel mountroot prompt to continue booting.
1408 Newer versions of loader can boot old kernels without issue.
1411 The LOADER_FIREWIRE_SUPPORT build variable has been renamed to
1412 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
1413 to WITH/OUT_LOADER_GELI.
1416 The naive and non-compliant support of posix_fallocate(2) in ZFS
1417 has been removed as of r325320. The system call now returns EINVAL
1418 when used on a ZFS file. Although the new behavior complies with the
1419 standard, some consumers are not prepared to cope with it.
1420 One known victim is lld prior to r325420.
1423 Building in a FreeBSD src checkout will automatically create object
1424 directories now rather than store files in the current directory if
1425 'make obj' was not ran. Calling 'make obj' is no longer necessary.
1426 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
1427 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
1431 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
1432 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
1433 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
1434 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
1435 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
1436 The UNIFIED_OBJDIR option is a transitional feature that will be
1437 removed for 12.0 release; please migrate to the new format for any
1438 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
1439 than hardcoding paths.
1442 The native-xtools target no longer installs the files by default to the
1443 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
1444 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
1447 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
1448 options are changing from controlling the build if defined / undefined
1449 to controlling the build with explicit 'yes' or 'no' values. They will
1450 shift to WITH/WITHOUT options to match other options in the system.
1453 libstand has turned into a private library for sys/boot use only.
1454 It is no longer supported as a public interface outside of sys/boot.
1457 The arm port has split armv6 into armv6 and armv7. armv7 is now
1458 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
1459 and are running a kernel from before r324363, you will need to add
1460 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
1463 When building multiple kernels using KERNCONF, non-existent KERNCONF
1464 files will produce an error and buildkernel will fail. Previously
1465 missing KERNCONF files silently failed giving no indication as to
1466 why, only to subsequently discover during installkernel that the
1467 desired kernel was never built in the first place.
1470 The default serial number format for CTL LUNs has changed. This will
1471 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
1472 or iSCSI clients care about their LUNs' serial numbers. Users who
1473 require serial number stability should hardcode serial numbers in
1477 For 32-bit arm compiled for hard-float support, soft-floating point
1478 binaries now always get their shared libraries from
1479 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
1480 /usr/libsoft also existed). Only users with a hard-float ld.so, but
1481 soft-float everything else should be affected.
1484 The geli password typed at boot is now hidden. To restore the previous
1485 behavior, see geli(8) for configuration options.
1488 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
1489 sysctl values. Minor nit, but requires a rebuild of both world/kernel
1493 "make check" behavior (made in ^/head@r295380) has been changed to
1494 execute from a limited sandbox, as opposed to executing from
1498 - The "beforecheck" and "aftercheck" targets are now specified.
1499 - ${CHECKDIR} (added in commit noted above) has been removed.
1500 - Legacy behavior can be enabled by setting
1501 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
1503 If the limited sandbox mode is enabled, "make check" will execute
1504 "make distribution", then install, execute the tests, and clean up the
1505 sandbox if successful.
1507 The "make distribution" and "make install" targets are typically run as
1508 root to set appropriate permissions and ownership at installation time.
1509 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
1510 environment if executing "make check" with limited sandbox mode using
1511 an unprivileged user.
1514 Since the switch to GPT disk labels, fsck for UFS/FFS has been
1515 unable to automatically find alternate superblocks. As of r322297,
1516 the information needed to find alternate superblocks has been
1517 moved to the end of the area reserved for the boot block.
1518 Filesystems created with a newfs of this vintage or later
1519 will create the recovery information. If you have a filesystem
1520 created prior to this change and wish to have a recovery block
1521 created for your filesystem, you can do so by running fsck in
1522 foreground mode (i.e., do not use the -p or -y options). As it
1523 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
1524 to which you should answer yes.
1527 As of r321665, an NFSv4 server configuration that services
1528 Kerberos mounts or clients that do not support the uid/gid in
1529 owner/owner_group string capability, must explicitly enable
1530 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
1531 machine's /etc/rc.conf file.
1534 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
1535 Please see the 20141231 entry below for information about prerequisites
1536 and upgrading, if you are not already using clang 3.5.0 or higher.
1539 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
1540 r-commands (rlogin, rsh, etc.) to be built with the base system.
1543 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
1544 a very major ABI incompatible change, so users of FreeBSD/powerpc must
1545 be careful when performing source upgrades. It is best to run
1546 'make installworld' from an alternate root system, either a live
1547 CD/memory stick, or a temporary root partition. Additionally, all ports
1548 must be recompiled. powerpc64 is largely unaffected, except in the case
1549 of 32-bit compatibility. All 32-bit binaries will be affected.
1552 Forward compatibility for the "ino64" project have been committed. This
1553 will allow most new binaries to run on older kernels in a limited
1554 fashion. This prevents many of the common foot-shooting actions in the
1555 upgrade as well as the limited ability to roll back the kernel across
1556 the ino64 upgrade. Complicated use cases may not work properly, though
1557 enough simpler ones work to allow recovery in most situations.
1560 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
1561 if you require the GPL compiler.
1564 The internal ABI used for communication between the NFS kernel modules
1565 was changed by r320085, so __FreeBSD_version was bumped to
1566 ensure all the NFS related modules are updated together.
1569 The ABI of struct event was changed by extending the data
1570 member to 64bit and adding ext fields. For upgrade, same
1571 precautions as for the entry 20170523 "ino64" must be
1575 The GNU roff toolchain has been removed from base. To render manpages
1576 which are not supported by mandoc(1), man(1) can fallback on GNU roff
1577 from ports (and recommends to install it).
1578 To render roff(7) documents, consider using GNU roff from ports or the
1579 heirloom doctools roff toolchain from ports via pkg install groff or
1580 via pkg install heirloom-doctools.
1583 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
1584 smaller runtime footprint builds. This is useful for embedded systems
1585 which only require one chipset support.
1587 If you load it as a module, make sure this is in /boot/loader.conf:
1591 This will load the HAL, all chip/RF backends and if_ath_pci.
1592 If you have if_ath_pci in /boot/loader.conf, ensure it is after
1593 if_ath or it will not load any HAL chipset support.
1595 If you want to selectively load things (eg on cheaper ARM/MIPS
1596 platforms where RAM is at a premium) you should:
1599 * load the chip modules in question
1600 * load ath_rate, ath_dfs
1602 * load if_ath_pci and/or if_ath_ahb depending upon your particular
1603 bus bind type - this is where probe/attach is done.
1605 For further comments/feedback, poke adrian@ .
1608 The "ino64" 64-bit inode project has been committed, which extends
1609 a number of types to 64 bits. Upgrading in place requires care and
1610 adherence to the documented upgrade procedure.
1612 If using a custom kernel configuration ensure that the
1613 COMPAT_FREEBSD11 option is included (as during the upgrade the
1614 system will be running the ino64 kernel with the existing world).
1616 For the safest in-place upgrade begin by removing previous build
1617 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full
1618 procedure documented below under the heading "To rebuild everything and
1619 install it on the current system." Specifically, a reboot is required
1620 after installing the new kernel before installing world. While an
1621 installworld normally works by accident from multiuser after rebooting
1622 the proper kernel, there are many cases where this will fail across this
1623 upgrade and installworld from single user is required.
1626 The NATM framework including the en(4), fatm(4), hatm(4), and
1627 patm(4) devices has been removed. Consumers should plan a
1628 migration before the end-of-life date for FreeBSD 11.
1631 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
1632 diff has not been implemented, if those are needed a newer version of
1633 GNU diff is available via the diffutils package under the gdiff name.
1636 As of r316810 for ipfilter, keep frags is no longer assumed when
1637 keep state is specified in a rule. r316810 aligns ipfilter with
1638 documentation in man pages separating keep frags from keep state.
1639 This allows keep state to be specified without forcing keep frags
1640 and allows keep frags to be specified independently of keep state.
1641 To maintain previous behaviour, also specify keep frags with
1642 keep state (as documented in ipf.conf.5).
1645 arm64 builds now use the base system LLD 4.0.0 linker by default,
1646 instead of requiring that the aarch64-binutils port or package be
1647 installed. To continue using aarch64-binutils, set
1648 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
1651 The UDP optimization in entry 20160818 that added the sysctl
1652 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
1653 packets will no longer be treated as L3 broadcast packets.
1656 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
1657 use any explicitly assigned loopback address available in the jail
1658 instead of using the first assigned address of the jail.
1661 The ctl.ko module no longer implements the iSCSI target frontend:
1662 cfiscsi.ko does instead.
1664 If building cfiscsi.ko as a kernel module, the module can be loaded
1665 via one of the following methods:
1666 - `cfiscsi_load="YES"` in loader.conf(5).
1667 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
1668 - ctladm(8)/ctld(8), when compiled with iSCSI support
1669 (`WITH_ISCSI=yes` in src.conf(5))
1671 Please see cfiscsi(4) for more details.
1674 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
1675 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
1676 same source (previously, the dependency of mmcsd.ko on mmc.ko was
1677 missing, but mmcsd.ko now will refuse to load if it is incompatible
1681 The syntax of ipfw(8) named states was changed to avoid ambiguity.
1682 If you have used named states in the firewall rules, you need to modify
1683 them after installworld and before rebooting. Now named states must
1684 be prefixed with colon.
1687 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
1688 removed as the userland we provide cannot use them. The KMS version
1689 (sys/dev/drm2) supports the same hardware.
1692 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
1693 Please see the 20141231 entry below for information about prerequisites
1694 and upgrading, if you are not already using clang 3.5.0 or higher.
1697 The code that provides support for ZFS .zfs/ directory functionality
1698 has been reimplemented. It's not possible now to create a snapshot
1699 by mkdir under .zfs/snapshot/. That should be the only user visible
1703 EISA bus support has been removed. The WITH_EISA option is no longer
1707 MCA bus support has been removed.
1710 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
1711 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
1714 The EM_MULTIQUEUE kernel configuration option is deprecated now that
1715 the em(4) driver conforms to iflib specifications.
1718 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
1719 IFLIB. If you have a custom kernel configuration that excludes em(4)
1720 but you use igb(4), you need to re-add em(4) to your custom
1724 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
1725 Please see the 20141231 entry below for information about prerequisites
1726 and upgrading, if you are not already using clang 3.5.0 or higher.
1729 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
1730 Please see the 20141231 entry below for information about prerequisites
1731 and upgrading, if you are not already using clang 3.5.0 or higher.
1734 The layout of the pmap structure has changed for powerpc to put the pmap
1735 statistics at the front for all CPU variations. libkvm(3) and all tools
1736 that link against it need to be recompiled.
1739 isl(4) and cyapa(4) drivers now require a new driver,
1740 chromebook_platform(4), to work properly on Chromebook-class hardware.
1741 On other types of hardware the drivers may need to be configured using
1742 device hints. Please see the corresponding manual pages for details.
1745 The urtwn(4) driver was merged into rtwn(4) and now consists of
1746 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
1748 Also, firmware for RTL8188CE was renamed due to possible name
1749 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
1752 GNU rcs has been removed from base. It is available as packages:
1753 - rcs: Latest GPLv3 GNU rcs version.
1754 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
1758 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
1759 modules now requires that the kernel configuration contain the
1760 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
1763 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
1764 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
1767 Relocatable object files with the extension of .So have been renamed
1768 to use an extension of .pico instead. The purpose of this change is
1769 to avoid a name clash with shared libraries on case-insensitive file
1770 systems. On those file systems, foo.So is the same file as foo.so.
1773 GNU rcs has been turned off by default. It can (temporarily) be built
1774 again by adding WITH_RCS knob in src.conf.
1775 Otherwise, GNU rcs is available from packages:
1776 - rcs: Latest GPLv3 GNU rcs version.
1777 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
1780 The backup_uses_rcs functionality has been removed from rc.subr.
1783 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
1784 two separate components, QUEUE_MACRO_DEBUG_TRACE and
1785 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
1786 QUEUE_MACRO_DEBUG behavior.
1789 r304787 changed some ioctl interfaces between the iSCSI userspace
1790 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1791 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1795 The UDP receive code has been updated to only treat incoming UDP
1796 packets that were addressed to an L2 broadcast address as L3
1797 broadcast packets. It is not expected that this will affect any
1798 standards-conforming UDP application. The new behaviour can be
1799 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1803 Remove the openbsd_poll system call.
1804 __FreeBSD_version has been bumped because of this.
1807 The stable/11 branch has been created from head@r302406.
1809 After branch N is created, entries older than the N-2 branch point are removed
1810 from this file. After stable/14 is branched and current becomes FreeBSD 15,
1811 entries older than stable/12 branch point will be removed from current's
1818 Sometimes, obscure build problems are the result of environment
1819 poisoning. This can happen because the make utility reads its
1820 environment when searching for values for global variables. To run
1821 your build attempts in an "environmental clean room", prefix all make
1822 commands with 'env -i '. See the env(1) manual page for more details.
1823 Occasionally a build failure will occur with "make -j" due to a race
1824 condition. If this happens try building again without -j, and please
1825 report a bug if it happens consistently.
1827 When upgrading from one major version to another it is generally best to
1828 upgrade to the latest code in the currently installed branch first, then
1829 do an upgrade to the new branch. This is the best-tested upgrade path,
1830 and has the highest probability of being successful. Please try this
1831 approach if you encounter problems with a major version upgrade. Since
1832 the stable 4.x branch point, one has generally been able to upgrade from
1833 anywhere in the most recent stable branch to head / current (or even the
1834 last couple of stable branches). See the top of this file when there's
1837 The update process will emit an error on an attempt to perform a build
1838 or install from a FreeBSD version below the earliest supported version.
1839 When updating from an older version the update should be performed one
1840 major release at a time, including running `make delete-old` at each
1843 When upgrading a live system, having a root shell around before
1844 installing anything can help undo problems. Not having a root shell
1845 around can lead to problems if pam has changed too much from your
1846 starting point to allow continued authentication after the upgrade.
1848 This file should be read as a log of events. When a later event changes
1849 information of a prior event, the prior event should not be deleted.
1850 Instead, a pointer to the entry with the new information should be
1851 placed in the old entry. Readers of this file should also sanity check
1852 older entries before relying on them blindly. Authors of new entries
1853 should write them with this in mind.
1857 When upgrading the boot ZFS pool to a new version (via zpool upgrade),
1858 always follow these three steps:
1860 1) recompile and reinstall the ZFS boot loader and boot block
1861 (this is part of "make buildworld" and "make installworld")
1863 2) update the ZFS boot block on your boot drive (only required when
1864 doing a zpool upgrade):
1866 When booting on x86 via BIOS, use the following to update the ZFS boot
1867 block on the freebsd-boot partition of a GPT partitioned drive ada0:
1868 gpart bootcode -p /boot/gptzfsboot -i $N ada0
1869 The value $N will typically be 1. For EFI booting, see EFI notes.
1871 3) zpool upgrade the root pool. New bootblocks will work with old
1872 pools, but not vice versa, so they need to be updated before any
1875 Non-boot pools do not need these updates.
1880 There are two locations the boot loader can be installed into. The
1881 current location (and the default) is \efi\freebsd\loader.efi and using
1882 efibootmgr(8) to configure it. The old location, that must be used on
1883 deficient systems that don't honor efibootmgr(8) protocols, is the
1884 fallback location of \EFI\BOOT\BOOTxxx.EFI. Generally, you will copy
1885 /boot/loader.efi to this location, but on systems installed a long time
1886 ago the ESP may be too small and /boot/boot1.efi may be needed unless
1887 the ESP has been expanded in the meantime.
1889 Recent systems will have the ESP mounted on /boot/efi, but older ones
1890 may not have it mounted at all, or mounted in a different
1891 location. Older arm SD images with MBR used /boot/msdos as the
1892 mountpoint. The ESP is a MSDOS filesystem.
1894 The EFI boot loader rarely needs to be updated. For ZFS booting,
1895 however, you must update loader.efi before you do 'zpool upgrade' the
1896 root zpool, otherwise the old loader.efi may reject the upgraded zpool
1897 since it does not automatically understand some new features.
1899 See loader.efi(8) and uefi(8) for more details.
1903 If you are updating from a prior version of FreeBSD (even one just
1904 a few days old), you should follow this procedure. It is the most
1905 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1907 make kernel-toolchain
1908 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1909 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1911 To test a kernel once
1912 ---------------------
1913 If you just want to boot a kernel once (because you are not sure
1914 if it works, or if you want to boot a known bad kernel to provide
1915 debugging information) run
1916 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1917 nextboot -k testkernel
1919 To rebuild everything and install it on the current system.
1920 -----------------------------------------------------------
1921 # Note: sometimes if you are running current you gotta do more than
1922 # is listed here if you are upgrading from a really old current.
1924 <make sure you have good level 0 dumps>
1926 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1927 make installkernel KERNCONF=YOUR_KERNEL_HERE
1929 <reboot in single user> [3]
1936 To cross-install current onto a separate partition
1937 --------------------------------------------------
1938 # In this approach we use a separate partition to hold
1939 # current's root, 'usr', and 'var' directories. A partition
1940 # holding "/", "/usr" and "/var" should be about 2GB in
1943 <make sure you have good level 0 dumps>
1946 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1947 <maybe newfs current's root partition>
1948 <mount current's root partition on directory ${CURRENT_ROOT}>
1949 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1950 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1951 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1952 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1953 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1954 <reboot into current>
1955 <do a "native" rebuild/install as described in the previous section>
1956 <maybe install compatibility libraries from ports/misc/compat*>
1960 To upgrade in-place from stable to current
1961 ----------------------------------------------
1962 <make sure you have good level 0 dumps>
1964 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1965 make installkernel KERNCONF=YOUR_KERNEL_HERE
1967 <reboot in single user> [3]
1974 Make sure that you've read the UPDATING file to understand the
1975 tweaks to various things you need. At this point in the life
1976 cycle of current, things change often and you are on your own
1977 to cope. The defaults can also change, so please read ALL of
1978 the UPDATING entries.
1980 Also, if you are tracking -current, you must be subscribed to
1981 freebsd-current@freebsd.org. Make sure that before you update
1982 your sources that you have read and understood all the recent
1983 messages there. If in doubt, please track -stable which has
1984 much fewer pitfalls.
1986 [1] If you have third party modules, such as vmware, you should disable
1987 them at this point so they don't crash your system on
1988 reboot. Alternatively, you should rebuild all the modules you have in
1989 your system and install them as well. If you are running -current, you
1990 should seriously consider placing all sources to all the modules for
1991 your system (or symlinks to them) in /usr/local/sys/modules so this
1992 happens automatically. If all your modules come from ports, then adding
1993 the port origin directories to PORTS_MODULES instead is also automatic
1995 PORTS_MODULES+=x11/nvidia-driver
1997 [3] From the bootblocks, boot -s, and then do
2001 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed
2002 cd src # full path to source
2003 adjkerntz -i # if CMOS is wall time
2004 Also, when doing a major release upgrade, it is required that you boot
2005 into single user mode to do the installworld.
2007 [4] Note: This step is non-optional. Failure to do this step
2008 can result in a significant reduction in the functionality of the
2009 system. Attempting to do it by hand is not recommended and those
2010 that pursue this avenue should read this file carefully, as well
2011 as the archives of freebsd-current and freebsd-hackers mailing lists
2012 for potential gotchas. See etcupdate(8) for more information.
2014 [5] Usually this step is a no-op. However, from time to time
2015 you may need to do this if you get unknown user in the following
2018 [6] This only deletes old files and directories. Old libraries
2019 can be deleted by "make delete-old-libs", but you have to make
2020 sure that no program is using those libraries anymore.
2022 [8] The new kernel must be able to run existing binaries used by an
2023 installworld. When upgrading across major versions, the new kernel's
2024 configuration must include the correct COMPAT_FREEBSD<n> option for
2025 existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure
2026 to do so may leave you with a system that is hard to boot to recover. A
2027 GENERIC kernel will include suitable compatibility options to run
2028 binaries from older branches. Note that the ability to run binaries
2029 from unsupported branches is not guaranteed.
2031 Make sure that you merge any new devices from GENERIC since the
2032 last time you updated your kernel config file. Options also
2033 change over time, so you may need to adjust your custom kernels
2036 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2037 "?=" instead of the "=" assignment operator, so that buildworld can
2038 override the CPUTYPE if it needs to.
2040 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2041 not on the command line, or in /etc/make.conf. buildworld will
2042 warn if it is improperly defined.
2045 This file contains a list, in reverse chronological order, of major
2046 breakages in tracking -current. It is not guaranteed to be a complete
2047 list of such breakages, and only contains entries since September 23, 2011.
2048 If you need to see UPDATING entries from before that date, you will need
2049 to fetch an UPDATING file from an older FreeBSD release.
2051 Copyright information:
2053 Copyright 1998-2009 M. Warner Losh <imp@FreeBSD.org>
2055 Redistribution, publication, translation and use, with or without
2056 modification, in full or in part, in any form or format of this
2057 document are permitted without further permission from the author.
2059 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2060 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2061 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2062 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2063 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2064 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2065 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2066 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2067 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2068 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2069 POSSIBILITY OF SUCH DAMAGE.
2071 Contact Warner Losh if you have any questions about your use of