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 The WITH_INIT_ALL_PATTERN and WITH_INIT_ALL_ZERO build options have
32 been replaced by INIT_ALL=pattern and INIT_ALL=zero respectively.
38 Serial communication (in boot loaders, kernel, and userland) has
39 been changed to default to 115200 bps, in line with common industry
40 practice and typcial firmware serial console redirection
43 Note that the early x86 BIOS bootloader (i.e., boot0sio) does not
44 support rates above 9600 bps and is not changed. boot0sio users may
45 set BOOT_COMCONSOLE_SPEED=9600 to use 9600 for all of the boot
46 components, or use the standard boot0 and have the boot2 stage start
47 with the serial port at 115200.
50 Following the general removal of MIPS support, the ath(4) AHB bus-
51 frontend has been removed, too, and building of the PCI support is
52 integrated with the ath(4) main module again. As a result, there's
53 no longer a need for if_ath_pci_load="YES" in /boot/loader.conf or
54 "device ath_pci" in the kernel configuration.
57 MAXCPU has been increased to 1024 in the amd64 GENERIC kernel config.
58 Out-of-tree kernel modules will need to be rebuilt.
61 CAM has been mechanically updated s/u_int(64|32|16|8)_t/uint\1_t/g
62 to move to the standard uintXX_t types from the old, traditional
63 BSD u_intXX_t types. This should be a NOP, but may cause problems
64 for out of tree changes. The SIMs were not updated since most of
65 the old u_intXX_t uses weren't due to CAM interfaces.
68 The heuristic for detecting old chromebooks with an EC bug that requires
69 atkbdc driver workarounds has changed. There should be no functional
70 change, but if your old chromebook's keyboard stops working, please
71 file a PR and assign it to imp.
74 OpenSSL has been updated to version 3.0, including changes throughout
75 the base system. It is important to rebuild third-party software
79 To enable pf rdr rules for connections initiated from the host, pf
80 filter rules can be optionally enabled for packets delivered
81 locally. This can change the behavior of rules which match packets
82 delivered to lo0. To enable this feature:
84 sysctl net.pf.filter_local=1
87 When enabled, its best to ensure that packets delivered locally are not
88 filtered, e.g. by adding a 'skip on lo' rule.
91 Improvements to libtacplus(8) mean that tacplus.conf(5) now
92 follows POSIX shell syntax rules. This may cause TACACS+
93 authentication to fail if the shared secret contains a single
94 quote, double quote, or backslash character which isn't
95 already properly quoted or escaped.
98 Belatedly switch the default nvme block device on x86 from nvd to nda.
99 nda created nvd compatibility links by default, so this should be a
100 nop. If this causes problems for your application, set hw.nvme.use_nvd=1
101 in your loader.conf or add `options NVME_USE_NVD=1` to your kernel
102 config. To disable the nvd compatibility aliases, add
103 kern.cam.nda.nvd_compat=0 to loader.conf. The default has been nda on
104 all non-x86 platforms for some time now. If you need to fall back,
105 please email imp@freebsd.org about why.
107 Encrypted swap partitions need to be changed from nvd to nda if you
108 migrate, or you need to use the above to switch back to nvd.
111 Remove portsnap(8). Users are encouraged to obtain the ports tree
115 Add jobs.mk to save typing. Enables -j${JOB_MAX} and logging
119 make -j${JOB_MAX} buildworld > ../buildworld.log 2>&1
121 where JOB_MAX is derrived from ncpus in local.sys.mk if not set in env.
124 Video related devices for some arm devices have been renamed.
125 If you have a custom kernel config and want to use hdmi output on
126 IMX6 board you need to add "device dwc_hdmi" "device imx6_hdmi" and
127 "device imx6_ipu" to it.
128 If you have a custom kernel config and want to use hdmi output on
129 TI AM335X board you need to add "device tda19988" to it.
130 If you add "device hdmi" in it you need to remove it as it doesn't
134 Introduce new kernel options KBD_DELAY1 and KBD_DELAY2. See atkbdc(4)
138 sshd now defaults to having X11Forwarding disabled, following upstream.
139 Administrators who wish to enable X11Forwarding should add
140 `X11Forwarding yes` to /etc/ssh/sshd_config.
143 Since commit 75d41cb6967 Huawei 3G/4G LTE Mobile Devices do not default
144 to ECM, but NCM mode and need u3g and ucom modules loaded. See cdce(4).
147 As of commit 7c40e2d5f685, the dependency on netlink(4) has been added
148 to the linux_common(4) module. Users relying on linux_common may need
149 to complile netlink(4) module if it is not present in their kernel.
152 The WITHOUT_CXX option has been removed. C++ components in the base
153 system are now built unconditionally.
156 LinuxKPI pci.h changes may require out-of-tree drivers to be recompiled.
157 Bump _FreeBSD_version to 1400078 to be able to detect this change.
160 llvm-objump is now always installed as objdump. Previously there was
161 no /usr/bin/objdump unless the WITH_LLVM_BINUTILS knob was used.
163 Some LLVM objdump options have a different output format compared to
164 GNU objdump; readelf is available for inspecting ELF files, and GNU
165 objdump is available from the devel/binutils port or package.
168 dma(8) has replaced sendmail(8) as the default mta. For people willing
169 to reenable sendmail(8):
171 $ cp /usr/share/examples/sendmail/mailer.conf /etc/mail/mailer.conf
173 and add sendmail_enable="YES" to rc.conf.
176 hw.bus.disable_failed_devices has changed from 'false' to 'true' by
177 default. Now if newbus succeeds in probing a device, but fails to attach
178 the device, we'll disable the device. In the past, we'd keep retrying
179 the device on each new driver loaded. To get that behavior now, one
180 needs to use devctl to re-enable the device, and reprobe it (or set
181 the sysctl/tunable hw.bus.disable_failed_devices=false).
183 NOTE: This was reverted 20221205 due to unexpected compatibility issues
186 pf no longer accepts 'scrub fragment crop' or 'scrub fragment drop-ovl'.
187 These configurations are no longer automatically reinterpreted as
188 'scrub fragment reassemble'.
191 The WITHOUT_CLANG_IS_CC option has been removed. When Clang is enabled
192 it is always installed as /usr/bin/cc (and c++, cpp).
195 Some programs have been moved into separate packages. It is recommended
196 for pkgbase users to do:
198 pkg install FreeBSD-dhclient FreeBSD-geom FreeBSD-resolvconf \
199 FreeBSD-devd FreeBSD-devmatch
201 after upgrading to restore all the component that were previously
205 LinuxKPI pm.h changes require an update to the latest drm-kmod version
206 before re-compiling to avoid errors.
209 The macros provided for the manipulation of CPU sets (e.g. CPU_AND)
210 have been modified to take 2 source arguments instead of only 1.
211 Externally maintained sources that use these macros will have to
212 be adapted. The FreeBSD version has been bumped to 1400046 to
216 A number of the kernel include files are able to be included by
217 themselves. A test has been added to buildworld to enforce this.
220 Remove mips as a recognized target. This starts the decommissioning of
221 mips support in FreeBSD. mips related items will be removed wholesale in
222 the coming days and weeks.
224 This broke the NO_CLEAN build for some people. Either do a clean build
226 lib/clang/include/llvm/Config/Targets.def
227 lib/clang/include/llvm/Config/AsmParsers.def
228 lib/clang/include/llvm/Config/Disassemblers.def
229 lib/clang/include/llvm/Config/AsmPrinters.def
230 before the build to force everything to rebuild that needs to.
233 Unbound support for RFC8375: The special-use domain 'home.arpa' is
234 by default blocked. To unblock it use a local-zone nodefault
235 statement in unbound.conf:
236 local-zone: "home.arpa." nodefault
238 Or use another type of local-zone to override with your choice.
240 The reason for this is discussed in Section 6.1 of RFC8375:
241 Because 'home.arpa.' is not globally scoped and cannot be secured
242 using DNSSEC based on the root domain's trust anchor, there is no way
243 to tell, using a standard DNS query, in which homenet scope an answer
244 belongs. Consequently, users may experience surprising results with
245 such names when roaming to different homenets.
248 Commit b8d60729deef changed the TCP congestion control framework so
249 that any of the included congestion control modules could be
250 the single module built into the kernel. Previously newreno
251 was automatically built in through direct reference. As of
252 this commit you are required to declare at least one congestion
253 control module (e.g. 'options CC_NEWRENO') and to also declare a
254 default using the CC_DEFAULT option (e.g. options CC_DEFAULT="newreno\").
255 The GENERIC configuration includes CC_NEWRENO and defines newreno
256 as the default. If no congestion control option is built into the
257 kernel and you are including networking, the kernel compile will
258 fail. Also if no default is declared the kernel compile will fail.
261 Mips has been removed from universe builds. It will be removed from the
265 Commit f0c9847a6c47 changed the arguments for VOP_ALLOCATE.
266 The NFS modules must be rebuilt from sources and any out
267 of tree file systems that implement their own VOP_ALLOCATE
268 may need to be modified.
271 The synchronous PPP kernel driver sppp(4) has been removed.
272 The cp(4) and ce(4) drivers are now always compiled with netgraph(4)
273 support, formerly enabled by NETGRAPH_CRONYX option.
276 sh(1) is now the default shell for the root user. To force root to use
277 the csh shell, please run the following command as root:
282 Ncurses distribution has been split between libtinfow and libncurses
283 with libncurses.so becoming a linker (ld) script to seamlessly link
284 to libtinfow as needed. Bump _FreeBSD_version to 1400035 to reflect
288 As of commit 8160a0f62be6, the dummynet module no longer depends on the
289 ipfw module. Dummynet can now be used by pf as well as ipfw. As such
290 users who relied on this dependency may need to include ipfw in the
291 list of modules to load on their systems.
294 As of commit 903873ce1560, the mixer(8) utility has got a slightly
295 new syntax. Please refer to the mixer(8) manual page for more
296 information. The old mixer utility can be installed from ports:
297 audio/freebsd-13-mixer
300 As of commit 55089ef4f8bb, the global variable nfs_maxcopyrange has
301 been deleted from the nfscommon.ko. As such, nfsd.ko must be built
302 from up to date sources to avoid an undefined reference when
306 As of commit 62ca9fc1ad56 OpenSSL no longer enables kernel TLS
307 by default. Users can enable kernel TLS via the "KTLS" SSL
308 option. This can be enabled globally by using a custom
309 OpenSSL config file via OPENSSL_CONF or via an
310 application-specific configuration option for applications
311 which permit setting SSL options via SSL_CONF_cmd(3).
314 Commit 3ad1e1c1ce20 changed the internal KAPI between the NFS
315 modules. Therefore, all need to be rebuilt from sources.
318 Commit b69019c14cd8 removes pf's DIOCGETSTATESNV ioctl.
319 As of be70c7a50d32 it is no longer used by userspace, but it does mean
320 users may not be able to enumerate pf states if they update the kernel
321 past b69019c14cd8 without first updating userspace past be70c7a50d32.
324 As of commit 01ad0c007964 if_bridge member interfaces can no longer
325 change their MTU. Changing the MTU of the bridge itself will change the
326 MTU on all member interfaces instead.
329 Commit ee29e6f31111 changed the internal KAPI between the nfscommon
330 and nfsd modules. Therefore, both need to be rebuilt from sources.
331 Bump __FreeBSD_version to 1400026 for this KAPI change.
334 The 20210707 awk update brought in a change in behavior. This has
335 been corrected as of d4d252c49976. Between these dates, if you
336 installed a new awk binary, you may not be able to build a new
337 kernel because the change in behavior affected the genoffset
338 script used to build the kernel. If you did update, the fix is
339 to update your sources past the above hash and do
342 % sudo -E make install
343 to enable building kernels again.
346 Commit 1e0a518d6548 changed the internal KAPI between the NFS
347 modules. They all need to be rebuilt from sources. I did not
348 bump __FreeBSD_version, since it was bumped recently.
351 awk has been updated to the latest one-true-awk version 20210215.
352 This contains a number of minor bug fixes.
355 The NFSv4 client now uses the highest minor version of NFSv4
356 supported by the NFSv4 server by default instead of minor version 0,
358 The "minorversion" mount option may be used to override this default.
361 Bump __FreeBSD_version to 1400024 for LinuxKPI changes.
362 Most notably netdev.h can change now as the (last) dependencies
363 (mlx4/ofed) are now using struct ifnet directly, but also for PCI
364 additions and others.
367 The directory "blacklisted" under /usr/share/certs/ has been
368 renamed to "untrusted".
371 svnlite has been removed from base. Should you need svn for any reason
372 please install the svn package or port.
375 Commit e1a907a25cfa changed the internal KAPI between the krpc
376 and nfsserver. As such, both modules must be rebuilt from
377 sources. Bump __FreeBSD_version to 1400022.
380 The an(4) driver has been removed from FreeBSD.
383 The vendor/openzfs branch was renamed to vendor/openzfs/legacy to
384 start tracking OpenZFS upstream more closely. Please see
385 https://lists.freebsd.org/archives/freebsd-current/2021-June/000153.html
386 for details on how to correct any errors that might result. The
387 short version is that you need to remove the old branch locally:
388 git update-ref -d refs/remotes/freebsd/vendor/openzfs
389 (assuming your upstream origin is named 'freebsd').
392 Commits 17accc08ae15 and de102f870501 add new files to LinuxKPI
393 which break drm-kmod. In addition various other additions where
394 committed. Bump __FreeBSD_version to 1400015 to be able to
398 Commit ca179c4d74f2 changed the package in which the OpenSSL
399 libraries and utilities are packaged.
400 It is recommended for pkgbase user to do:
401 pkg install -f FreeBSD-openssl
402 before pkg upgrade otherwise some dependencies might not be met
403 and pkg will stop working as libssl will not be present anymore
407 Commit 875977314881 changed the internal KAPI between
408 the nfsd and nfscommon modules. As such these modules
409 need to be rebuilt from sources.
410 Without this patch in your NFSv4.1/4.2 server, enabling
411 delegations by setting vfs.nfsd.issue_delegations non-zero
415 Commit 7763814fc9c2 changed the internal KAPI between
416 the krpc and NFS. As such, the krpc, nfscommon and
417 nfscl modules must all be rebuilt from sources.
418 Without this patch, NFSv4.1/4.2 mounts should not
419 be done with the nfscbd(8) daemon running, to avoid
420 needing a working back channel for server->client RPCs.
423 Commit 01ae8969a9ee fixed the NFSv4.1/4.2 server so that it
424 handles binding of the back channel as required by RFC5661.
425 Until this patch is in your server, avoid use of the "nconnects"
426 mount option for Linux NFSv4.1/4.2 mounts.
429 For 64-bit architectures the base system is now built with Position
430 Independent Executable (PIE) support enabled by default. It may be
431 disabled using the WITHOUT_PIE knob. A clean build is required.
434 Various LinuxKPI functionality was added which conflicts with DRM.
435 Please update your drm-kmod port to after the __FreeBSD_version 1400003
439 PC Card attachments for all devices have been removed. In the case of
440 wi and cmx, the entire drivers were removed because they were only
441 PC Card devices. FreeBSD_version 1300134 should be used for this
442 since it was bumped so recently.
445 Transport-independent parts of HID support have been split off the USB
446 code in to separate subsystem. Kernel configs which include one of
447 ums, ukbd, uhid, atp, wsp, wmt, uaudio, ugold or ucycom drivers should
448 be updated with adding of "device hid" line.
451 ncurses installation has been modified to only keep the widechar
452 enabled version. Incremental build is broken for that change, so it
453 requires a clean build.
456 The FreeBSD project has migrated from Subversion to Git. Temporary
457 instructions can be found at
458 https://github.com/bsdimp/freebsd-git-docs/blob/main/src-cvt.md
459 and other documents in that repo.
462 The services database has been updated to cover more of the basic
463 services expected in a modern system. The database is big enough
464 that it will cause issues in mergemaster in Releases previous to
465 12.2 and 11.3, or in very old current systems from before r358154.
468 Obsolete in-tree GDB 6.1.1 has been removed. GDB (including kgdb)
469 may be installed from ports or packages.
472 ping6 has been merged into ping. It can now be called as "ping -6".
473 See ping(8) for details.
476 Default value of net.add_addr_allfibs has been changed to 0.
477 If you have multi-fib configuration and rely on existence of all
478 interface routes in every fib, you need to set the above sysctl to 1.
481 The internal pre-processor in the calendar(1) program has been
482 extended to support more C pre-processor commands (e.g. #ifdef, #else,
483 and #undef) and to detect unbalanced conditional statements.
484 Error messages have been extended to include the filename and line
485 number if processing stops to help fixing malformed data files.
488 All the data files for the calendar(1) program, except calendar.freebsd,
489 have been moved to the deskutils/calendar-data port, much like the
490 jewish calendar entries were moved to deskutils/hebcal years ago. After
491 make delete-old-files, you need to install it to retain full
492 functionality. calendar(1) will issue a reminder for files it can't
496 LINT files are no longer generated. We now include the relevant NOTES
497 files. Note: This may cause conflicts with updating in some cases.
498 find sys -name LINT\* -delete
499 is suggested across this commit to remove the generated LINT files.
501 If you have tried to update with generated files there, the svn
502 command you want to un-auger the tree is
505 and then do the above find from the top level. Substitute 'amd64'
506 above with where the error message indicates a conflict.
509 OpenZFS support has been integrated. Do not upgrade root pools until
510 the loader is updated to support zstd. Furthermore, we caution against
511 'zpool upgrade' for the next few weeks. The change should be transparent
512 unless you want to use new features.
514 Not all "NO_CLEAN" build scenarios work across these changes. Many
515 scenarios have been tested and fixed, but rebuilding kernels without
516 rebuilding world may fail.
518 The ZFS cache file has moved from /boot to /etc to match the OpenZFS
519 upstream default. A fallback to /boot has been added for mountroot.
521 Pool auto import behavior at boot has been moved from the kernel module
522 to an explicit "zpool import -a" in one of the rc scripts enabled by
523 zfs_enable=YES. This means your non-root zpools won't auto import until
524 you upgrade your /etc/rc.d files.
527 The resume code now notifies devd with the 'kernel' system
528 rather than the old 'kern' subsystem to be consistent with
529 other use. The old notification will be created as well, but
530 will be removed prior to FreeBSD 14.0.
533 r362275 changed the internal API between the kernel RPC and the
534 NFS modules. As such, all the modules must be recompiled from
538 r364330 modified the internal API used between the NFS modules.
539 As such, all the NFS modules must be re-compiled from sources.
542 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
543 been upgraded to 11.0.0. Please see the 20141231 entry below for
544 information about prerequisites and upgrading, if you are not already
545 using clang 3.5.0 or higher.
548 r364092 modified the internal ABI used between the kernel NFS
549 modules. As such, all of these modules need to be rebuilt
550 from sources, so a version bump was done.
553 Makefile.inc has been updated to work around the issue documented in
554 20200729. It was a case where the optimization of using symbolic links
555 to point to binaries created a situation where we'd run new binaries
556 with old libraries starting midway through the installworld process.
559 r363679 has redefined some undefined behavior in regcomp(3); notably,
560 extraneous escapes of most ordinary characters will no longer be
561 accepted. An exp-run has identified all of the problems with this in
562 ports, but other non-ports software may need extra escapes removed to
563 continue to function.
565 Because of this change, installworld may encounter the following error
566 from rtld: Undefined symbol "regcomp@FBSD_1.6" -- It is imperative that
567 you do not halt installworld. Instead, let it run to completion (whether
568 successful or not) and run installworld once more.
571 A new implementation of bc and dc has been imported in r362681. This
572 implementation corrects non-conformant behavior of the previous bc
573 and adds GNU bc compatible options. It offers a number of extensions,
574 is much faster on large values, and has support for message catalogs
575 (a number of languages are already supported, contributions of further
576 languages welcome). The option WITHOUT_GH_BC can be used to build the
577 world with the previous versions of bc and dc.
580 r362639 changed the internal API used between the NFS kernel modules.
581 As such, they all need to be rebuilt from sources.
584 r362158 changed the arguments for VFS_CHECKEXP(). As such, any
585 out of tree file systems need to be modified and rebuilt.
586 Also, any file systems that are modules must be rebuilt.
589 read(2) of a directory fd is now rejected by default. root may
590 re-enable it for system root only on non-ZFS filesystems with the
591 security.bsd.allow_read_dir sysctl(8) MIB if
592 security.bsd.suser_enabled=1.
594 It may be advised to setup aliases for grep to default to `-d skip` if
595 commonly non-recursively grepping a list that includes directories and
596 the potential for the resulting stderr output is not tolerable. Example
597 aliases are now installed, commented out, in /root/.cshrc and
601 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
602 been upgraded to 10.0.1. Please see the 20141231 entry below for
603 information about prerequisites and upgrading, if you are not already
604 using clang 3.5.0 or higher.
607 Support for obsolete compilers has been removed from the build system.
608 Clang 6 and GCC 6.4 are the minimum supported versions.
611 closefrom(2) has been moved under COMPAT12, and replaced in libc with a
612 stub that calls close_range(2). If using a custom kernel configuration,
613 you may want to ensure that the COMPAT_FREEBSD12 option is included, as
614 a slightly older -CURRENT userland and older FreeBSD userlands may not
615 be functional without closefrom(2).
618 Upstream DTS from Linux 5.6 was merged and they now have the SID
619 and THS (Secure ID controller and THermal Sensor) node present.
620 The DTB overlays have now been removed from the tree for the H3/H5 and
621 A64 SoCs and the aw_sid and aw_thermal driver have been updated to
622 deal with upstream DTS. If you are using those overlays you need to
623 remove them from loader.conf and update the DTBs on the FAT partition.
626 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
627 been upgraded to 10.0.0. Please see the 20141231 entry below for
628 information about prerequisites and upgrading, if you are not already
629 using clang 3.5.0 or higher.
632 The amd(8) automount daemon has been removed from the source tree.
633 As of FreeBSD 10.1 autofs(5) is the preferred tool for automounting.
634 amd is still available in the sysutils/am-utils port.
637 Removed brooktree driver (bktr.4) from the tree.
640 The WITH_GPL_DTC option has been removed. The BSD-licenced device tree
641 compiler in usr.bin/dtc is used on all architectures which use dtc, and
642 the GPL dtc is available (if needed) from the sysutils/dtc port.
645 The WITHOUT_LLVM_LIBUNWIND option has been removed. LLVM's libunwind
646 is used by all supported CPU architectures.
649 GCC 4.2.1 has been removed from the tree. The WITH_GCC,
650 WITH_GCC_BOOTSTRAP, and WITH_GNUCXX options are no longer available.
651 Users who wish to build FreeBSD with GCC must use the external toolchain
655 ncurses has been updated to a newer version (6.2-20200215). Given the ABI
656 has changed, users will have to rebuild all the ports that are linked to
660 The size of struct vnet and the magic cookie have changed.
661 Users need to recompile libkvm and all modules using VIMAGE
662 together with their new kernel.
665 Defining the long deprecated NO_CTF, NO_DEBUG_FILES, NO_INSTALLLIB,
666 NO_MAN, NO_PROFILE, and NO_WARNS variables is now an error. Update
667 your Makefiles and scripts to define MK_<var>=no instead as required.
669 One exception to this is that program or library Makefiles should
670 define MAN to empty rather than setting MK_MAN=no.
673 Clang/LLVM is now the default compiler and LLD the default
677 make universe no longer uses GCC 4.2.1 on any architectures.
678 Architectures not supported by in-tree Clang/LLVM require an
679 external toolchain package.
682 GCC 4.2.1 is now not built by default, as part of the GCC 4.2.1
683 retirement plan. Specifically, the GCC, GCC_BOOTSTRAP, and GNUCXX
684 options default to off for all supported CPU architectures. As a
685 short-term transition aid they may be enabled via WITH_* options.
686 GCC 4.2.1 is expected to be removed from the tree on 2020-03-31.
689 Support for armv5 has been disconnected and is being removed. The
690 machine combination MACHINE=arm MACHINE_ARCH=arm is no longer valid.
691 You must now use a MACHINE_ARCH of armv6 or armv7. The default
692 MACHINE_ARCH for MACHINE=arm is now armv7.
695 Clang/LLVM is now the default compiler for all powerpc architectures.
696 LLD is now the default linker for powerpc64. The change for powerpc64
697 also includes a change to the ELFv2 ABI, incompatible with the existing
701 Kernel-loadable random(4) modules are no longer unloadable.
704 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
705 been upgraded to 9.0.1. Please see the 20141231 entry below for
706 information about prerequisites and upgrading, if you are not already
707 using clang 3.5.0 or higher.
710 r355677 has modified the internal interface used between the
711 NFS modules in the kernel. As such, they must all be upgraded
712 simultaneously. I will do a version bump for this.
715 The root certificates of the Mozilla CA Certificate Store have been
716 imported into the base system and can be managed with the certctl(8)
717 utility. If you have installed the security/ca_root_nss port or package
718 with the ETCSYMLINK option (the default), be advised that there may be
719 differences between those included in the port and those included in
720 base due to differences in nss branch used as well as general update
721 frequency. Note also that certctl(8) cannot manage certs in the
722 format used by the security/ca_root_nss port.
725 The amd(8) automount daemon has been disabled by default, and will be
726 removed in the future. As of FreeBSD 10.1 the autofs(5) is available
730 The nctgpio and wbwd drivers have been moved to the superio bus.
731 If you have one of these drivers in a kernel configuration, then
732 you should add device superio to it. If you use one of these drivers
733 as a module and you compile a custom set of modules, then you should
734 add superio to the set.
737 KPIs for network drivers to access interface addresses have changed.
738 Users need to recompile NIC driver modules together with kernel.
741 The net.link.tap.user_open sysctl no longer prevents user opening of
742 already created /dev/tapNN devices. Access is still controlled by
743 node permissions, just like tun devices. The net.link.tap.user_open
744 sysctl is now used only to allow users to perform devfs cloning of
745 tap devices, and the subsequent open may not succeed if the user is not
746 in the appropriate group. This sysctl may be deprecated/removed
747 completely in the future.
750 mips, powerpc, and sparc64 are no longer built as part of
751 universe / tinderbox unless MAKE_OBSOLETE_GCC is defined. If
752 not defined, mips, powerpc, and sparc64 builds will look for
753 the xtoolchain binaries and if installed use them for universe
754 builds. As llvm 9.0 becomes vetted for these architectures, they
755 will be removed from the list.
758 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
759 been upgraded to 9.0.0. Please see the 20141231 entry below for
760 information about prerequisites and upgrading, if you are not already
761 using clang 3.5.0 or higher.
764 The hpt27xx, hptmv, hptnr, and hptrr drivers have been removed from
765 GENERIC. They are available as modules and can be loaded by adding
766 to /boot/loader.conf hpt27xx_load="YES", hptmv_load="YES",
767 hptnr_load="YES", or hptrr_load="YES", respectively.
770 ntpd no longer by default locks its pages in memory, allowing them
771 to be paged out by the kernel. Use rlimit memlock to restore
772 historic BSD behaviour. For example, add "rlimit memlock 32"
773 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
776 Several of ping6's options have been renamed for better consistency
777 with ping. If you use any of -ARWXaghmrtwx, you must update your
778 scripts. See ping6(8) for details.
781 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
782 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
783 been removed from mount_fusefs(8). You can safely remove them from
784 your scripts, because they had no effect.
786 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
787 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
788 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
789 sysctls have been removed. If you felt the need to set any of them to
790 a non-default value, please tell asomers@FreeBSD.org why.
793 Default permissions on the /var/account/acct file (and copies of it
794 rotated by periodic daily scripts) are changed from 0644 to 0640
795 because the file contains sensitive information that should not be
796 world-readable. If the /var/account directory must be created by
797 rc.d/accounting, the mode used is now 0750. Admins who use the
798 accounting feature are encouraged to change the mode of an existing
799 /var/account directory to 0750 or 0700.
802 Entropy collection and the /dev/random device are no longer optional
803 components. The "device random" option has been removed.
804 Implementations of distilling algorithms can still be made loadable
805 with "options RANDOM_LOADABLE" (e.g., random_fortuna.ko).
808 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
809 been upgraded to 8.0.1. Please see the 20141231 entry below for
810 information about prerequisites and upgrading, if you are not already
811 using clang 3.5.0 or higher.
814 A fix was applied to i386 kernel modules to avoid panics with
815 dpcpu or vnet. Users need to recompile i386 kernel modules
816 having pcpu or vnet sections or they will refuse to load.
819 User-wired pages now have their own counter,
820 vm.stats.vm.v_user_wire_count. The vm.max_wired sysctl was renamed
821 to vm.max_user_wired and changed from an unsigned int to an unsigned
822 long. bhyve VMs wired with the -S are now subject to the user
823 wiring limit; the vm.max_user_wired sysctl may need to be tuned to
824 avoid running into the limit.
827 The IPSEC option has been removed from GENERIC. Users requiring
828 ipsec(4) must now load the ipsec(4) kernel module.
831 The tap(4) driver has been folded into tun(4), and the module has been
832 renamed to tuntap. You should update any kld_list="if_tap" or
833 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
834 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
835 module instead, and "device tap" or "device tun" entries in kernel
836 config files to select the tuntap device instead.
839 The following knobs have been added related to tradeoffs between
840 safe use of the random device and availability in the absence of
843 kern.random.initial_seeding.bypass_before_seeding: tunable; set
844 non-zero to bypass the random device prior to seeding, or zero to
845 block random requests until the random device is initially seeded.
846 For now, set to 1 (unsafe) by default to restore pre-r346250 boot
847 availability properties.
849 kern.random.initial_seeding.read_random_bypassed_before_seeding:
850 read-only diagnostic sysctl that is set when bypass is enabled and
851 read_random(9) is bypassed, to enable programmatic handling of this
852 initial condition, if desired.
854 kern.random.initial_seeding.arc4random_bypassed_before_seeding:
855 Similar to the above, but for arc4random(9) initial seeding.
857 kern.random.initial_seeding.disable_bypass_warnings: tunable; set
858 non-zero to disable warnings in dmesg when the same conditions are
859 met as for the diagnostic sysctls above. Defaults to zero, i.e.,
860 produce warnings in dmesg when the conditions are met.
863 The loadable random module KPI has changed; the random_infra_init()
864 routine now requires a 3rd function pointer for a bool (*)(void)
865 method that returns true if the random device is seeded (and
866 therefore unblocked).
869 r345895 reverts r320698. This implies that an nfsuserd(8) daemon
870 built from head sources between r320757 (July 6, 2017) and
871 r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
872 is added to the command line.
873 nfsuserd daemons built from head sources that are post-r338192 are
874 not affected and should continue to work.
877 The fuse(4) module has been renamed to fusefs(4) for consistency with
878 other filesystems. You should update any kld_load="fuse" entries in
879 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
880 "options FUSE" entries in kernel config files.
883 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
884 8.0.0. Please see the 20141231 entry below for information about
885 prerequisites and upgrading, if you are not already using clang 3.5.0
889 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
890 compiled into your custom kernel, add 'device xz' statement to the
894 drm and drm2 have been removed from the tree. Please see
895 https://wiki.freebsd.org/Graphics for the latest information on
896 migrating to the drm ports.
899 Iflib is no longer unconditionally compiled into the kernel. Drivers
900 using iflib and statically compiled into the kernel, now require
901 the 'device iflib' config option. For the same drivers loaded as
902 modules on kernels not having 'device iflib', the iflib.ko module
903 is loaded automatically.
906 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
907 options no longer exist since r343219 and r343427 respectively;
908 nothing uses them, so they should be just removed from custom
912 r342635 changes the way efibootmgr(8) works by requiring users to add
913 the -b (bootnum) parameter for commands where the bootnum was previously
914 specified with each option. For example 'efibootmgr -B 0001' is now
915 'efibootmgr -B -b 0001'.
918 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
919 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
920 servers that have vfs.nfsd.nfs_privport set will only allow mounts
921 from clients using a reserved port. Since both the FreeBSD and Linux
922 NFSv4 clients use reserved ports by default, this should not affect
926 The XLP config has been removed. We can't support 64-bit atomics in this
927 kernel because it is running in 32-bit mode. XLP users must transition
928 to running a 64-bit kernel (XLP64 or XLPN32).
930 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
931 the preferred emulator today and we don't need two different ones.
933 The old sibyte / swarm / Broadcom BCM1250 support has been
934 removed from the mips port.
937 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
938 7.0.1. Please see the 20141231 entry below for information about
939 prerequisites and upgrading, if you are not already using clang 3.5.0
943 Remove the timed and netdate programs from the base tree. Setting
944 the time with these daemons has been obsolete for over a decade.
947 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
948 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
949 it produces broken binaries when ifuncs are in use. Users needing
950 GNU ld should install the binutils port or package.
953 The BSD crtbegin and crtend code has been enabled by default. It has
954 had extensive testing on amd64, arm64, and i386. It can be disabled
955 by building a world with -DWITHOUT_BSD_CRTBEGIN.
958 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
959 has been converted to a port (misc/ctm) and will be removed from
960 FreeBSD-13. It is available as a package (ctm) for all supported
964 The default newsyslog.conf(5) file has been changed to only include
965 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
966 the filenames end in '.conf' and do not begin with a '.'.
968 You should check the configuration files in these two directories match
969 this naming convention. You can verify which configuration files are
970 being included using the command:
974 Ports for the DRM modules have been simplified. Now, amd64 users should
975 just install the drm-kmod port. All others should install
978 Graphics hardware that's newer than about 2010 usually works with
979 drm-kmod. For hardware older than 2013, however, some users will need
980 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
981 than 2008 usually only works in drm-legacy-kmod. The graphics team can
982 only commit to hardware made since 2013 due to the complexity of the
983 market and difficulty to test all the older cards effectively. If you
984 have hardware supported by drm-kmod, you are strongly encouraged to use
985 that as you will get better support.
987 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
988 elsewhere, the drm and drm2 modules will be eliminated from the src base
989 soon (with a limited exception for arm). Please update to the package
990 asap and report any issues to x11@freebsd.org.
992 Generally, anybody using the drm*-kmod packages should add
993 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
994 cross-threading surprises, especially with automatic driver
995 loading from X11 startup. These will become the defaults in 13-current
999 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
1000 custom kernel and module loading configuration files must be updated
1001 accordingly. Moreover, interfaces previous presented as ixlvN to the
1002 system are now exposed as iavfN and network configuration files must
1003 be adjusted as necessary.
1006 OpenSSL has been updated to version 1.1.1. This update included
1007 additional various API changes throughout the base system. It is
1008 important to rebuild third-party software after upgrading. The value
1009 of __FreeBSD_version has been bumped accordingly.
1012 The legacy DRM modules and drivers have now been added to the loader's
1013 module blacklist, in favor of loading them with kld_list in rc.conf(5).
1014 The module blacklist may be overridden with the loader.conf(5)
1015 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
1019 The cam(4) based nda(4) driver will be used over nvd(4) by default on
1020 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
1021 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
1022 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
1026 Reproducible build mode is now on by default, in preparation for
1027 FreeBSD 12.0. This eliminates build metadata such as the user,
1028 host, and time from the kernel (and uname), unless the working tree
1029 corresponds to a modified checkout from a version control system.
1030 The previous behavior can be obtained by setting the /etc/src.conf
1031 knob WITHOUT_REPRODUCIBLE_BUILD.
1034 The Yarrow CSPRNG has been removed from the kernel as it has not been
1035 supported by its designers since at least 2003. Fortuna has been the
1036 default since FreeBSD-11.
1039 devctl freeze/thaw have gone into the tree, the rc scripts have been
1040 updated to use them and devmatch has been changed. You should update
1041 kernel, userland and rc scripts all at the same time.
1044 The default interpreter has been switched from 4th to Lua.
1045 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
1046 interpreter. If you have custom FORTH code you will need to set
1047 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
1048 src.conf for the build. This will create default hard links between
1049 loader and loader_4th instead of loader and loader_lua, the new default.
1050 If you are using UEFI it will create the proper hard link to loader.efi.
1052 bhyve uses userboot.so. It remains 4th-only until some issues are solved
1053 regarding coexisting with multiple versions of FreeBSD are resolved.
1056 ls(1) now respects the COLORTERM environment variable used in other
1057 systems and software to indicate that a colored terminal is both
1058 supported and desired. If ls(1) is suddenly emitting colors, they may
1059 be disabled again by either removing the unwanted COLORTERM from your
1060 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
1061 may not be observed in a future release.
1064 The default pager for most commands has been changed to "less". To
1065 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
1069 The jedec_ts(4) driver has been removed. A superset of its functionality
1070 is available in the jedec_dimm(4) driver, and the manpage for that
1071 driver includes migration instructions. If you have "device jedec_ts"
1072 in your kernel configuration file, it must be removed.
1075 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
1076 This should have no effect if the kernel is booted via BIOS/legacy boot.
1077 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
1078 has a buggy firmware that prevents a successful boot due to use of
1082 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
1083 support has been removed from the tree. These ports were
1084 obsolete and/or known to be broken for many years.
1087 loader.efi has been augmented to participate more fully in the
1088 UEFI boot manager protocol. loader.efi will now look at the
1089 BootXXXX environment variable to determine if a specific kernel
1090 or root partition was specified. XXXX is derived from BootCurrent.
1091 efibootmgr(8) manages these standard UEFI variables.
1094 zfsloader's functionality has now been folded into loader.
1095 zfsloader is no longer necessary once you've updated your
1096 boot blocks. For a transition period, we will install a
1097 hardlink for zfsloader to loader to allow a smooth transition
1098 until the boot blocks can be updated (hard link because old
1099 zfs boot blocks don't understand symlinks).
1102 ARM64 now have efifb support, if you want to have serial console
1103 on your arm64 board when an screen is connected and the bootloader
1104 setup a frame buffer for us to use, just add :
1107 in /boot/loader.conf
1108 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
1109 an screen connected as the firmware will setup a frame buffer are that
1110 u-boot will expose as an EFI frame buffer.
1113 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
1114 or take steps to update /etc/passwd before doing installworld on
1115 existing systems. Do not skip the "mergemaster -Fp" step before
1116 installworld, as described in the update procedures near the bottom
1117 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
1118 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
1119 the ntp config file contain options that change file/dir locations.
1120 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
1121 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
1122 taking steps to ensure that all required files/dirs are accessible
1126 Big endian arm support has been removed.
1129 The static environment setup in kernel configs is no longer mutually
1130 exclusive with the loader(8) environment by default. In order to
1131 restore the previous default behavior of disabling the loader(8)
1132 environment if a static environment is present, you must specify
1133 loader_env.disabled=1 in the static environment.
1136 The ABI of syscalls used by management tools like sockstat and
1137 netstat has been broken to allow 32-bit binaries to work on
1138 64-bit kernels without modification. These programs will need
1139 to match the kernel in order to function. External programs may
1140 require minor modifications to accommodate a change of type in
1141 structures from pointers to 64-bit virtual addresses.
1144 On i386 and amd64 atomics are now inlined. Out of tree modules using
1145 atomics will need to be rebuilt.
1148 The '%I' format in the kern.corefile sysctl limits the number of
1149 core files that a process can generate to the number stored in the
1150 debug.ncores sysctl. The '%I' format is replaced by the single digit
1151 index. Previously, if all indexes were taken the kernel would overwrite
1152 only a core file with the highest index in a filename.
1153 Currently the system will create a new core file if there is a free
1154 index or if all slots are taken it will overwrite the oldest one.
1157 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
1158 6.0.1. Please see the 20141231 entry below for information about
1159 prerequisites and upgrading, if you are not already using clang 3.5.0
1163 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
1164 needed to be changed to work with it. This change was made with r335763
1165 and requires a mergemaster / etcupdate / etc to update the installed
1169 r334930 changed the interface between the NFS modules, so they all
1170 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
1173 As of r334391 lld is the default amd64 system linker; it is installed
1174 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
1178 The kernel / userland interface for devinfo changed, so you'll
1179 need a new kernel and userland as a pair for it to work (rebuilding
1180 lib/libdevinfo is all that's required). devinfo and devmatch will
1181 not work, but everything else will when there's a mismatch.
1184 The on-disk format for hwpmc callchain records has changed to include
1185 threadid corresponding to a given record. This changes the field offsets
1186 and thus requires that libpmcstat be rebuilt before using a kernel
1190 The vxge(4) driver has been removed. This driver was introduced into
1191 HEAD one week before the Exar left the Ethernet market and is not
1192 known to be used. If you have device vxge in your kernel config file
1196 The amd64 kernel now requires a ld that supports ifunc to produce a
1197 working kernel, either lld or a newer binutils. lld is built by default
1198 on amd64, and the 'buildkernel' target uses it automatically. However,
1199 it is not the default linker, so building the kernel the traditional
1200 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
1201 binutils port/package). lld will soon be default, and this requirement
1204 NOTE: As of r334391 lld is the default system linker on amd64, and no
1205 workaround is necessary.
1208 The nxge(4) driver has been removed. This driver was for PCI-X 10g
1209 cards made by s2io/Neterion. The company was acquired by Exar and
1210 no longer sells or supports Ethernet products. If you have device
1211 nxge in your kernel config file it must be removed.
1214 The tz database (tzdb) has been updated to 2018e. This version more
1215 correctly models time stamps in time zones with negative DST such as
1216 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
1217 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
1218 time zone abbreviations and the tm_isdst flag.
1221 The ixgb(4) driver has been removed. This driver was for an early and
1222 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
1223 quickly shifted to the long lived ixgbe family. If you have device
1224 ixgb in your kernel config file it must be removed.
1227 The lmc(4) driver has been removed. This was a WAN interface
1228 card that was already reportedly rare in 2003, and had an ambiguous
1229 license. If you have device lmc in your kernel config file it must
1233 Support for Arcnet networks has been removed. If you have device
1234 arcnet or device cm in your kernel config file they must be
1238 Support for FDDI networks has been removed. If you have device
1239 fddi or device fpa in your kernel config file they must be
1243 In addition to supporting RFC 3164 formatted messages, the
1244 syslogd(8) service is now capable of parsing RFC 5424 formatted
1245 log messages. The main benefit of using RFC 5424 is that clients
1246 may now send log messages with timestamps containing year numbers,
1247 microseconds and time zone offsets.
1249 Similarly, the syslog(3) C library function has been altered to
1250 send RFC 5424 formatted messages to the local system logging
1251 daemon. On systems using syslogd(8), this change should have no
1252 negative impact, as long as syslogd(8) and the C library are
1253 updated at the same time. On systems using a different system
1254 logging daemon, it may be necessary to make configuration
1255 adjustments, depending on the software used.
1257 When using syslog-ng, add the 'syslog-protocol' flag to local
1258 input sources to enable parsing of RFC 5424 formatted messages:
1261 unix-dgram("/var/run/log" flags(syslog-protocol));
1264 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
1265 of the 'imuxsock' module to let messages be processed by the
1266 regular RFC 3164/5424 parsing pipeline:
1268 module(load="imuxsock" SysSock.UseSpecialParser="off")
1270 Do note that these changes only affect communication between local
1271 applications and syslogd(8). The format that syslogd(8) uses to
1272 store messages on disk or forward messages to other systems
1273 remains unchanged. syslogd(8) still uses RFC 3164 for these
1274 purposes. Options to customize this behaviour will be added in the
1275 future. Utilities that process log files stored in /var/log are
1276 thus expected to continue to function as before.
1278 __FreeBSD_version has been incremented to 1200061 to denote this
1282 Support for token ring networks has been removed. If you
1283 have "device token" in your kernel config you should remove
1284 it. No device drivers supported token ring.
1287 makefs was modified to be able to tag ISO9660 El Torito boot catalog
1288 entries as EFI instead of overloading the i386 tag as done previously.
1289 The amd64 mkisoimages.sh script used to build amd64 ISO images for
1290 release was updated to use this. This may mean that makefs must be
1291 updated before "make cdrom" can be run in the release directory. This
1292 should be as simple as:
1294 $ cd $SRCDIR/usr.sbin/makefs
1295 $ make depend all install
1298 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
1299 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
1300 Co-existence for the transition period will come shortly. Booting is a
1301 complex environment and test coverage for Lua-enabled loaders has been
1302 thin, so it would be prudent to assume it might not work and make
1303 provisions for backup boot methods.
1306 devmatch functionality has been turned on in devd. It will automatically
1307 load drivers for unattached devices. This may cause unexpected drivers
1308 to be loaded. Please report any problems to current@ and
1312 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
1313 6.0.0. Please see the 20141231 entry below for information about
1314 prerequisites and upgrading, if you are not already using clang 3.5.0
1318 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
1319 This means it is used to link the kernel and userland libraries and
1320 executables, but is not yet installed as /usr/bin/ld by default.
1322 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
1323 WITHOUT_LLD_BOOTSTRAP=yes
1326 On i386, pmtimer has been removed. Its functionality has been folded
1327 into apm. It was a no-op on ACPI in current for a while now (but was
1328 still needed on i386 in FreeBSD 11 and earlier). Users may need to
1329 remove it from kernel config files.
1332 The use of RSS hash from the network card aka flowid has been
1333 disabled by default for lagg(4) as it's currently incompatible with
1334 the lacp and loadbalance protocols.
1336 This can be re-enabled by setting the following in loader.conf:
1337 net.link.lagg.default_use_flowid="1"
1340 The SW_WATCHDOG option is no longer necessary to enable the
1341 hardclock-based software watchdog if no hardware watchdog is
1342 configured. As before, SW_WATCHDOG will cause the software
1343 watchdog to be enabled even if a hardware watchdog is configured.
1346 r326887 fixes the issue described in the 20171214 UPDATING entry.
1347 r326888 flips the switch back to building GELI support always.
1350 r362593 broke ZFS + GELI support for reasons unknown. However,
1351 it also broke ZFS support generally, so GELI has been turned off
1352 by default as the lesser evil in r326857. If you boot off ZFS and/or
1353 GELI, it might not be a good time to update.
1356 PowerPC users must update loader(8) by rebuilding world before
1357 installing a new kernel, as the protocol connecting them has
1358 changed. Without the update, loader metadata will not be passed
1359 successfully to the kernel and users will have to enter their
1360 root partition at the kernel mountroot prompt to continue booting.
1361 Newer versions of loader can boot old kernels without issue.
1364 The LOADER_FIREWIRE_SUPPORT build variable has been renamed to
1365 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
1366 to WITH/OUT_LOADER_GELI.
1369 The naive and non-compliant support of posix_fallocate(2) in ZFS
1370 has been removed as of r325320. The system call now returns EINVAL
1371 when used on a ZFS file. Although the new behavior complies with the
1372 standard, some consumers are not prepared to cope with it.
1373 One known victim is lld prior to r325420.
1376 Building in a FreeBSD src checkout will automatically create object
1377 directories now rather than store files in the current directory if
1378 'make obj' was not ran. Calling 'make obj' is no longer necessary.
1379 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
1380 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
1384 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
1385 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
1386 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
1387 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
1388 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
1389 The UNIFIED_OBJDIR option is a transitional feature that will be
1390 removed for 12.0 release; please migrate to the new format for any
1391 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
1392 than hardcoding paths.
1395 The native-xtools target no longer installs the files by default to the
1396 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
1397 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
1400 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
1401 options are changing from controlling the build if defined / undefined
1402 to controlling the build with explicit 'yes' or 'no' values. They will
1403 shift to WITH/WITHOUT options to match other options in the system.
1406 libstand has turned into a private library for sys/boot use only.
1407 It is no longer supported as a public interface outside of sys/boot.
1410 The arm port has split armv6 into armv6 and armv7. armv7 is now
1411 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
1412 and are running a kernel from before r324363, you will need to add
1413 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
1416 When building multiple kernels using KERNCONF, non-existent KERNCONF
1417 files will produce an error and buildkernel will fail. Previously
1418 missing KERNCONF files silently failed giving no indication as to
1419 why, only to subsequently discover during installkernel that the
1420 desired kernel was never built in the first place.
1423 The default serial number format for CTL LUNs has changed. This will
1424 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
1425 or iSCSI clients care about their LUNs' serial numbers. Users who
1426 require serial number stability should hardcode serial numbers in
1430 For 32-bit arm compiled for hard-float support, soft-floating point
1431 binaries now always get their shared libraries from
1432 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
1433 /usr/libsoft also existed). Only users with a hard-float ld.so, but
1434 soft-float everything else should be affected.
1437 The geli password typed at boot is now hidden. To restore the previous
1438 behavior, see geli(8) for configuration options.
1441 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
1442 sysctl values. Minor nit, but requires a rebuild of both world/kernel
1446 "make check" behavior (made in ^/head@r295380) has been changed to
1447 execute from a limited sandbox, as opposed to executing from
1451 - The "beforecheck" and "aftercheck" targets are now specified.
1452 - ${CHECKDIR} (added in commit noted above) has been removed.
1453 - Legacy behavior can be enabled by setting
1454 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
1456 If the limited sandbox mode is enabled, "make check" will execute
1457 "make distribution", then install, execute the tests, and clean up the
1458 sandbox if successful.
1460 The "make distribution" and "make install" targets are typically run as
1461 root to set appropriate permissions and ownership at installation time.
1462 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
1463 environment if executing "make check" with limited sandbox mode using
1464 an unprivileged user.
1467 Since the switch to GPT disk labels, fsck for UFS/FFS has been
1468 unable to automatically find alternate superblocks. As of r322297,
1469 the information needed to find alternate superblocks has been
1470 moved to the end of the area reserved for the boot block.
1471 Filesystems created with a newfs of this vintage or later
1472 will create the recovery information. If you have a filesystem
1473 created prior to this change and wish to have a recovery block
1474 created for your filesystem, you can do so by running fsck in
1475 foreground mode (i.e., do not use the -p or -y options). As it
1476 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
1477 to which you should answer yes.
1480 As of r321665, an NFSv4 server configuration that services
1481 Kerberos mounts or clients that do not support the uid/gid in
1482 owner/owner_group string capability, must explicitly enable
1483 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
1484 machine's /etc/rc.conf file.
1487 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
1488 Please see the 20141231 entry below for information about prerequisites
1489 and upgrading, if you are not already using clang 3.5.0 or higher.
1492 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
1493 r-commands (rlogin, rsh, etc.) to be built with the base system.
1496 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
1497 a very major ABI incompatible change, so users of FreeBSD/powerpc must
1498 be careful when performing source upgrades. It is best to run
1499 'make installworld' from an alternate root system, either a live
1500 CD/memory stick, or a temporary root partition. Additionally, all ports
1501 must be recompiled. powerpc64 is largely unaffected, except in the case
1502 of 32-bit compatibility. All 32-bit binaries will be affected.
1505 Forward compatibility for the "ino64" project have been committed. This
1506 will allow most new binaries to run on older kernels in a limited
1507 fashion. This prevents many of the common foot-shooting actions in the
1508 upgrade as well as the limited ability to roll back the kernel across
1509 the ino64 upgrade. Complicated use cases may not work properly, though
1510 enough simpler ones work to allow recovery in most situations.
1513 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
1514 if you require the GPL compiler.
1517 The internal ABI used for communication between the NFS kernel modules
1518 was changed by r320085, so __FreeBSD_version was bumped to
1519 ensure all the NFS related modules are updated together.
1522 The ABI of struct event was changed by extending the data
1523 member to 64bit and adding ext fields. For upgrade, same
1524 precautions as for the entry 20170523 "ino64" must be
1528 The GNU roff toolchain has been removed from base. To render manpages
1529 which are not supported by mandoc(1), man(1) can fallback on GNU roff
1530 from ports (and recommends to install it).
1531 To render roff(7) documents, consider using GNU roff from ports or the
1532 heirloom doctools roff toolchain from ports via pkg install groff or
1533 via pkg install heirloom-doctools.
1536 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
1537 smaller runtime footprint builds. This is useful for embedded systems
1538 which only require one chipset support.
1540 If you load it as a module, make sure this is in /boot/loader.conf:
1544 This will load the HAL, all chip/RF backends and if_ath_pci.
1545 If you have if_ath_pci in /boot/loader.conf, ensure it is after
1546 if_ath or it will not load any HAL chipset support.
1548 If you want to selectively load things (eg on cheaper ARM/MIPS
1549 platforms where RAM is at a premium) you should:
1552 * load the chip modules in question
1553 * load ath_rate, ath_dfs
1555 * load if_ath_pci and/or if_ath_ahb depending upon your particular
1556 bus bind type - this is where probe/attach is done.
1558 For further comments/feedback, poke adrian@ .
1561 The "ino64" 64-bit inode project has been committed, which extends
1562 a number of types to 64 bits. Upgrading in place requires care and
1563 adherence to the documented upgrade procedure.
1565 If using a custom kernel configuration ensure that the
1566 COMPAT_FREEBSD11 option is included (as during the upgrade the
1567 system will be running the ino64 kernel with the existing world).
1569 For the safest in-place upgrade begin by removing previous build
1570 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full
1571 procedure documented below under the heading "To rebuild everything and
1572 install it on the current system." Specifically, a reboot is required
1573 after installing the new kernel before installing world. While an
1574 installworld normally works by accident from multiuser after rebooting
1575 the proper kernel, there are many cases where this will fail across this
1576 upgrade and installworld from single user is required.
1579 The NATM framework including the en(4), fatm(4), hatm(4), and
1580 patm(4) devices has been removed. Consumers should plan a
1581 migration before the end-of-life date for FreeBSD 11.
1584 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
1585 diff has not been implemented, if those are needed a newer version of
1586 GNU diff is available via the diffutils package under the gdiff name.
1589 As of r316810 for ipfilter, keep frags is no longer assumed when
1590 keep state is specified in a rule. r316810 aligns ipfilter with
1591 documentation in man pages separating keep frags from keep state.
1592 This allows keep state to be specified without forcing keep frags
1593 and allows keep frags to be specified independently of keep state.
1594 To maintain previous behaviour, also specify keep frags with
1595 keep state (as documented in ipf.conf.5).
1598 arm64 builds now use the base system LLD 4.0.0 linker by default,
1599 instead of requiring that the aarch64-binutils port or package be
1600 installed. To continue using aarch64-binutils, set
1601 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
1604 The UDP optimization in entry 20160818 that added the sysctl
1605 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
1606 packets will no longer be treated as L3 broadcast packets.
1609 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
1610 use any explicitly assigned loopback address available in the jail
1611 instead of using the first assigned address of the jail.
1614 The ctl.ko module no longer implements the iSCSI target frontend:
1615 cfiscsi.ko does instead.
1617 If building cfiscsi.ko as a kernel module, the module can be loaded
1618 via one of the following methods:
1619 - `cfiscsi_load="YES"` in loader.conf(5).
1620 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
1621 - ctladm(8)/ctld(8), when compiled with iSCSI support
1622 (`WITH_ISCSI=yes` in src.conf(5))
1624 Please see cfiscsi(4) for more details.
1627 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
1628 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
1629 same source (previously, the dependency of mmcsd.ko on mmc.ko was
1630 missing, but mmcsd.ko now will refuse to load if it is incompatible
1634 The syntax of ipfw(8) named states was changed to avoid ambiguity.
1635 If you have used named states in the firewall rules, you need to modify
1636 them after installworld and before rebooting. Now named states must
1637 be prefixed with colon.
1640 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
1641 removed as the userland we provide cannot use them. The KMS version
1642 (sys/dev/drm2) supports the same hardware.
1645 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
1646 Please see the 20141231 entry below for information about prerequisites
1647 and upgrading, if you are not already using clang 3.5.0 or higher.
1650 The code that provides support for ZFS .zfs/ directory functionality
1651 has been reimplemented. It's not possible now to create a snapshot
1652 by mkdir under .zfs/snapshot/. That should be the only user visible
1656 EISA bus support has been removed. The WITH_EISA option is no longer
1660 MCA bus support has been removed.
1663 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
1664 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
1667 The EM_MULTIQUEUE kernel configuration option is deprecated now that
1668 the em(4) driver conforms to iflib specifications.
1671 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
1672 IFLIB. If you have a custom kernel configuration that excludes em(4)
1673 but you use igb(4), you need to re-add em(4) to your custom
1677 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
1678 Please see the 20141231 entry below for information about prerequisites
1679 and upgrading, if you are not already using clang 3.5.0 or higher.
1682 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
1683 Please see the 20141231 entry below for information about prerequisites
1684 and upgrading, if you are not already using clang 3.5.0 or higher.
1687 The layout of the pmap structure has changed for powerpc to put the pmap
1688 statistics at the front for all CPU variations. libkvm(3) and all tools
1689 that link against it need to be recompiled.
1692 isl(4) and cyapa(4) drivers now require a new driver,
1693 chromebook_platform(4), to work properly on Chromebook-class hardware.
1694 On other types of hardware the drivers may need to be configured using
1695 device hints. Please see the corresponding manual pages for details.
1698 The urtwn(4) driver was merged into rtwn(4) and now consists of
1699 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
1701 Also, firmware for RTL8188CE was renamed due to possible name
1702 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
1705 GNU rcs has been removed from base. It is available as packages:
1706 - rcs: Latest GPLv3 GNU rcs version.
1707 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
1711 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
1712 modules now requires that the kernel configuration contain the
1713 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
1716 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
1717 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
1720 Relocatable object files with the extension of .So have been renamed
1721 to use an extension of .pico instead. The purpose of this change is
1722 to avoid a name clash with shared libraries on case-insensitive file
1723 systems. On those file systems, foo.So is the same file as foo.so.
1726 GNU rcs has been turned off by default. It can (temporarily) be built
1727 again by adding WITH_RCS knob in src.conf.
1728 Otherwise, GNU rcs is available from packages:
1729 - rcs: Latest GPLv3 GNU rcs version.
1730 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
1733 The backup_uses_rcs functionality has been removed from rc.subr.
1736 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
1737 two separate components, QUEUE_MACRO_DEBUG_TRACE and
1738 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
1739 QUEUE_MACRO_DEBUG behavior.
1742 r304787 changed some ioctl interfaces between the iSCSI userspace
1743 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1744 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1748 The UDP receive code has been updated to only treat incoming UDP
1749 packets that were addressed to an L2 broadcast address as L3
1750 broadcast packets. It is not expected that this will affect any
1751 standards-conforming UDP application. The new behaviour can be
1752 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1756 Remove the openbsd_poll system call.
1757 __FreeBSD_version has been bumped because of this.
1760 The stable/11 branch has been created from head@r302406.
1762 After branch N is created, entries older than the N-2 branch point are removed
1763 from this file. After stable/14 is branched and current becomes FreeBSD 15,
1764 entries older than stable/12 branch point will be removed from current's
1771 Sometimes, obscure build problems are the result of environment
1772 poisoning. This can happen because the make utility reads its
1773 environment when searching for values for global variables. To run
1774 your build attempts in an "environmental clean room", prefix all make
1775 commands with 'env -i '. See the env(1) manual page for more details.
1776 Occasionally a build failure will occur with "make -j" due to a race
1777 condition. If this happens try building again without -j, and please
1778 report a bug if it happens consistently.
1780 When upgrading from one major version to another it is generally best to
1781 upgrade to the latest code in the currently installed branch first, then
1782 do an upgrade to the new branch. This is the best-tested upgrade path,
1783 and has the highest probability of being successful. Please try this
1784 approach if you encounter problems with a major version upgrade. Since
1785 the stable 4.x branch point, one has generally been able to upgrade from
1786 anywhere in the most recent stable branch to head / current (or even the
1787 last couple of stable branches). See the top of this file when there's
1790 The update process will emit an error on an attempt to perform a build
1791 or install from a FreeBSD version below the earliest supported version.
1792 When updating from an older version the update should be performed one
1793 major release at a time, including running `make delete-old` at each
1796 When upgrading a live system, having a root shell around before
1797 installing anything can help undo problems. Not having a root shell
1798 around can lead to problems if pam has changed too much from your
1799 starting point to allow continued authentication after the upgrade.
1801 This file should be read as a log of events. When a later event changes
1802 information of a prior event, the prior event should not be deleted.
1803 Instead, a pointer to the entry with the new information should be
1804 placed in the old entry. Readers of this file should also sanity check
1805 older entries before relying on them blindly. Authors of new entries
1806 should write them with this in mind.
1810 When upgrading the boot ZFS pool to a new version (via zpool upgrade),
1811 always follow these three steps:
1813 1) recompile and reinstall the ZFS boot loader and boot block
1814 (this is part of "make buildworld" and "make installworld")
1816 2) update the ZFS boot block on your boot drive (only required when
1817 doing a zpool upgrade):
1819 When booting on x86 via BIOS, use the following to update the ZFS boot
1820 block on the freebsd-boot partition of a GPT partitioned drive ada0:
1821 gpart bootcode -p /boot/gptzfsboot -i $N ada0
1822 The value $N will typically be 1. For EFI booting, see EFI notes.
1824 3) zpool upgrade the root pool. New bootblocks will work with old
1825 pools, but not vice versa, so they need to be updated before any
1828 Non-boot pools do not need these updates.
1833 There are two locations the boot loader can be installed into. The
1834 current location (and the default) is \efi\freebsd\loader.efi and using
1835 efibootmgr(8) to configure it. The old location, that must be used on
1836 deficient systems that don't honor efibootmgr(8) protocols, is the
1837 fallback location of \EFI\BOOT\BOOTxxx.EFI. Generally, you will copy
1838 /boot/loader.efi to this location, but on systems installed a long time
1839 ago the ESP may be too small and /boot/boot1.efi may be needed unless
1840 the ESP has been expanded in the meantime.
1842 Recent systems will have the ESP mounted on /boot/efi, but older ones
1843 may not have it mounted at all, or mounted in a different
1844 location. Older arm SD images with MBR used /boot/msdos as the
1845 mountpoint. The ESP is a MSDOS filesystem.
1847 The EFI boot loader rarely needs to be updated. For ZFS booting,
1848 however, you must update loader.efi before you do 'zpool upgrade' the
1849 root zpool, otherwise the old loader.efi may reject the upgraded zpool
1850 since it does not automatically understand some new features.
1852 See loader.efi(8) and uefi(8) for more details.
1856 If you are updating from a prior version of FreeBSD (even one just
1857 a few days old), you should follow this procedure. It is the most
1858 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1860 make kernel-toolchain
1861 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1862 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1864 To test a kernel once
1865 ---------------------
1866 If you just want to boot a kernel once (because you are not sure
1867 if it works, or if you want to boot a known bad kernel to provide
1868 debugging information) run
1869 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1870 nextboot -k testkernel
1872 To rebuild everything and install it on the current system.
1873 -----------------------------------------------------------
1874 # Note: sometimes if you are running current you gotta do more than
1875 # is listed here if you are upgrading from a really old current.
1877 <make sure you have good level 0 dumps>
1879 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1880 make installkernel KERNCONF=YOUR_KERNEL_HERE
1882 <reboot in single user> [3]
1889 To cross-install current onto a separate partition
1890 --------------------------------------------------
1891 # In this approach we use a separate partition to hold
1892 # current's root, 'usr', and 'var' directories. A partition
1893 # holding "/", "/usr" and "/var" should be about 2GB in
1896 <make sure you have good level 0 dumps>
1899 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1900 <maybe newfs current's root partition>
1901 <mount current's root partition on directory ${CURRENT_ROOT}>
1902 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1903 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1904 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1905 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1906 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1907 <reboot into current>
1908 <do a "native" rebuild/install as described in the previous section>
1909 <maybe install compatibility libraries from ports/misc/compat*>
1913 To upgrade in-place from stable to current
1914 ----------------------------------------------
1915 <make sure you have good level 0 dumps>
1917 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1918 make installkernel KERNCONF=YOUR_KERNEL_HERE
1920 <reboot in single user> [3]
1927 Make sure that you've read the UPDATING file to understand the
1928 tweaks to various things you need. At this point in the life
1929 cycle of current, things change often and you are on your own
1930 to cope. The defaults can also change, so please read ALL of
1931 the UPDATING entries.
1933 Also, if you are tracking -current, you must be subscribed to
1934 freebsd-current@freebsd.org. Make sure that before you update
1935 your sources that you have read and understood all the recent
1936 messages there. If in doubt, please track -stable which has
1937 much fewer pitfalls.
1939 [1] If you have third party modules, such as vmware, you should disable
1940 them at this point so they don't crash your system on
1941 reboot. Alternatively, you should rebuild all the modules you have in
1942 your system and install them as well. If you are running -current, you
1943 should seriously consider placing all sources to all the modules for
1944 your system (or symlinks to them) in /usr/local/sys/modules so this
1945 happens automatically. If all your modules come from ports, then adding
1946 the port origin directories to PORTS_MODULES instead is also automatic
1948 PORTS_MODULES+=x11/nvidia-driver
1950 [3] From the bootblocks, boot -s, and then do
1954 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed
1955 cd src # full path to source
1956 adjkerntz -i # if CMOS is wall time
1957 Also, when doing a major release upgrade, it is required that you boot
1958 into single user mode to do the installworld.
1960 [4] Note: This step is non-optional. Failure to do this step
1961 can result in a significant reduction in the functionality of the
1962 system. Attempting to do it by hand is not recommended and those
1963 that pursue this avenue should read this file carefully, as well
1964 as the archives of freebsd-current and freebsd-hackers mailing lists
1965 for potential gotchas. See etcupdate(8) for more information.
1967 [5] Usually this step is a no-op. However, from time to time
1968 you may need to do this if you get unknown user in the following
1971 [6] This only deletes old files and directories. Old libraries
1972 can be deleted by "make delete-old-libs", but you have to make
1973 sure that no program is using those libraries anymore.
1975 [8] The new kernel must be able to run existing binaries used by an
1976 installworld. When upgrading across major versions, the new kernel's
1977 configuration must include the correct COMPAT_FREEBSD<n> option for
1978 existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure
1979 to do so may leave you with a system that is hard to boot to recover. A
1980 GENERIC kernel will include suitable compatibility options to run
1981 binaries from older branches. Note that the ability to run binaries
1982 from unsupported branches is not guaranteed.
1984 Make sure that you merge any new devices from GENERIC since the
1985 last time you updated your kernel config file. Options also
1986 change over time, so you may need to adjust your custom kernels
1989 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1990 "?=" instead of the "=" assignment operator, so that buildworld can
1991 override the CPUTYPE if it needs to.
1993 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1994 not on the command line, or in /etc/make.conf. buildworld will
1995 warn if it is improperly defined.
1998 This file contains a list, in reverse chronological order, of major
1999 breakages in tracking -current. It is not guaranteed to be a complete
2000 list of such breakages, and only contains entries since September 23, 2011.
2001 If you need to see UPDATING entries from before that date, you will need
2002 to fetch an UPDATING file from an older FreeBSD release.
2004 Copyright information:
2006 Copyright 1998-2009 M. Warner Losh <imp@FreeBSD.org>
2008 Redistribution, publication, translation and use, with or without
2009 modification, in full or in part, in any form or format of this
2010 document are permitted without further permission from the author.
2012 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2013 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2014 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2015 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2016 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2017 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2018 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2019 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2020 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2021 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2022 POSSIBILITY OF SUCH DAMAGE.
2024 Contact Warner Losh if you have any questions about your use of