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 EARLY_AP_STARTUP kernel option is mandatory on x86. The option
32 has been added to DEFAULTS, so it should automatically be included in
33 custom kernel configurations without any additional change.
36 A new loader tunable net.pf.default_to_drop allows pf(4)’s default
37 behaviour to be changed from pass to drop. Previously this required
38 recompiling the kernel with the option PF_DEFAULT_TO_DROP.
41 Enable splitting out pkgbase manpages into separate packages by
42 default. To disable this, set WITHOUT_MANSPLITPKG=yes in src.conf.
45 Move standard include files to the clibs-dev package and move clang
46 internal libraries and headers to clang and clang-dev. Upgrading systems
47 installed using pkgbase past this change involves extra steps to allow
50 pkg upgrade -y FreeBSD-utilities
51 pkg upgrade -y FreeBSD-utilities-dev
55 Enable vnet sysctl variables to be loader tunable. SYSCTLs which
56 belongs to VNETs can be initialized during early boot or module
57 loading if they are marked with CTLFLAG_TUN and there are
58 corresponding kernel environment variables.
61 The WITH_INIT_ALL_PATTERN and WITH_INIT_ALL_ZERO build options have
62 been replaced by INIT_ALL=pattern and INIT_ALL=zero respectively.
68 Serial communication (in boot loaders, kernel, and userland) has
69 been changed to default to 115200 bps, in line with common industry
70 practice and typcial firmware serial console redirection
73 Note that the early x86 BIOS bootloader (i.e., boot0sio) does not
74 support rates above 9600 bps and is not changed. boot0sio users may
75 set BOOT_COMCONSOLE_SPEED=9600 to use 9600 for all of the boot
76 components, or use the standard boot0 and have the boot2 stage start
77 with the serial port at 115200.
80 Following the general removal of MIPS support, the ath(4) AHB bus-
81 frontend has been removed, too, and building of the PCI support is
82 integrated with the ath(4) main module again. As a result, there's
83 no longer a need for if_ath_pci_load="YES" in /boot/loader.conf or
84 "device ath_pci" in the kernel configuration.
87 MAXCPU has been increased to 1024 in the amd64 GENERIC kernel config.
88 Out-of-tree kernel modules will need to be rebuilt.
91 CAM has been mechanically updated s/u_int(64|32|16|8)_t/uint\1_t/g
92 to move to the standard uintXX_t types from the old, traditional
93 BSD u_intXX_t types. This should be a NOP, but may cause problems
94 for out of tree changes. The SIMs were not updated since most of
95 the old u_intXX_t uses weren't due to CAM interfaces.
98 The heuristic for detecting old chromebooks with an EC bug that requires
99 atkbdc driver workarounds has changed. There should be no functional
100 change, but if your old chromebook's keyboard stops working, please
101 file a PR and assign it to imp.
104 OpenSSL has been updated to version 3.0, including changes throughout
105 the base system. It is important to rebuild third-party software
109 To enable pf rdr rules for connections initiated from the host, pf
110 filter rules can be optionally enabled for packets delivered
111 locally. This can change the behavior of rules which match packets
112 delivered to lo0. To enable this feature:
114 sysctl net.pf.filter_local=1
117 When enabled, its best to ensure that packets delivered locally are not
118 filtered, e.g. by adding a 'skip on lo' rule.
121 Improvements to libtacplus(8) mean that tacplus.conf(5) now
122 follows POSIX shell syntax rules. This may cause TACACS+
123 authentication to fail if the shared secret contains a single
124 quote, double quote, or backslash character which isn't
125 already properly quoted or escaped.
128 Belatedly switch the default nvme block device on x86 from nvd to nda.
129 nda created nvd compatibility links by default, so this should be a
130 nop. If this causes problems for your application, set hw.nvme.use_nvd=1
131 in your loader.conf or add `options NVME_USE_NVD=1` to your kernel
132 config. To disable the nvd compatibility aliases, add
133 kern.cam.nda.nvd_compat=0 to loader.conf. The default has been nda on
134 all non-x86 platforms for some time now. If you need to fall back,
135 please email imp@freebsd.org about why.
137 Encrypted swap partitions need to be changed from nvd to nda if you
138 migrate, or you need to use the above to switch back to nvd.
141 Remove portsnap(8). Users are encouraged to obtain the ports tree
145 Add jobs.mk to save typing. Enables -j${JOB_MAX} and logging
149 make -j${JOB_MAX} buildworld > ../buildworld.log 2>&1
151 where JOB_MAX is derrived from ncpus in local.sys.mk if not set in env.
154 Video related devices for some arm devices have been renamed.
155 If you have a custom kernel config and want to use hdmi output on
156 IMX6 board you need to add "device dwc_hdmi" "device imx6_hdmi" and
157 "device imx6_ipu" to it.
158 If you have a custom kernel config and want to use hdmi output on
159 TI AM335X board you need to add "device tda19988" to it.
160 If you add "device hdmi" in it you need to remove it as it doesn't
164 Introduce new kernel options KBD_DELAY1 and KBD_DELAY2. See atkbdc(4)
168 sshd now defaults to having X11Forwarding disabled, following upstream.
169 Administrators who wish to enable X11Forwarding should add
170 `X11Forwarding yes` to /etc/ssh/sshd_config.
173 Since commit 75d41cb6967 Huawei 3G/4G LTE Mobile Devices do not default
174 to ECM, but NCM mode and need u3g and ucom modules loaded. See cdce(4).
177 As of commit 7c40e2d5f685, the dependency on netlink(4) has been added
178 to the linux_common(4) module. Users relying on linux_common may need
179 to complile netlink(4) module if it is not present in their kernel.
182 The WITHOUT_CXX option has been removed. C++ components in the base
183 system are now built unconditionally.
186 LinuxKPI pci.h changes may require out-of-tree drivers to be recompiled.
187 Bump _FreeBSD_version to 1400078 to be able to detect this change.
190 llvm-objump is now always installed as objdump. Previously there was
191 no /usr/bin/objdump unless the WITH_LLVM_BINUTILS knob was used.
193 Some LLVM objdump options have a different output format compared to
194 GNU objdump; readelf is available for inspecting ELF files, and GNU
195 objdump is available from the devel/binutils port or package.
198 dma(8) has replaced sendmail(8) as the default mta. For people willing
199 to reenable sendmail(8):
201 $ cp /usr/share/examples/sendmail/mailer.conf /etc/mail/mailer.conf
203 and add sendmail_enable="YES" to rc.conf.
206 hw.bus.disable_failed_devices has changed from 'false' to 'true' by
207 default. Now if newbus succeeds in probing a device, but fails to attach
208 the device, we'll disable the device. In the past, we'd keep retrying
209 the device on each new driver loaded. To get that behavior now, one
210 needs to use devctl to re-enable the device, and reprobe it (or set
211 the sysctl/tunable hw.bus.disable_failed_devices=false).
213 NOTE: This was reverted 20221205 due to unexpected compatibility issues
216 pf no longer accepts 'scrub fragment crop' or 'scrub fragment drop-ovl'.
217 These configurations are no longer automatically reinterpreted as
218 'scrub fragment reassemble'.
221 The WITHOUT_CLANG_IS_CC option has been removed. When Clang is enabled
222 it is always installed as /usr/bin/cc (and c++, cpp).
225 Some programs have been moved into separate packages. It is recommended
226 for pkgbase users to do:
228 pkg install FreeBSD-dhclient FreeBSD-geom FreeBSD-resolvconf \
229 FreeBSD-devd FreeBSD-devmatch
231 after upgrading to restore all the component that were previously
235 OPIE has been removed from the base system. If needed, it can
236 be installed from ports (security/opie) or packages (opie).
237 Otherwise, make sure that your PAM policies do not reference
238 pam_opie or pam_opieaccess.
241 LinuxKPI pm.h changes require an update to the latest drm-kmod version
242 before re-compiling to avoid errors.
245 The macros provided for the manipulation of CPU sets (e.g. CPU_AND)
246 have been modified to take 2 source arguments instead of only 1.
247 Externally maintained sources that use these macros will have to
248 be adapted. The FreeBSD version has been bumped to 1400046 to
252 A number of the kernel include files are able to be included by
253 themselves. A test has been added to buildworld to enforce this.
256 Remove mips as a recognized target. This starts the decommissioning of
257 mips support in FreeBSD. mips related items will be removed wholesale in
258 the coming days and weeks.
260 This broke the NO_CLEAN build for some people. Either do a clean build
262 lib/clang/include/llvm/Config/Targets.def
263 lib/clang/include/llvm/Config/AsmParsers.def
264 lib/clang/include/llvm/Config/Disassemblers.def
265 lib/clang/include/llvm/Config/AsmPrinters.def
266 before the build to force everything to rebuild that needs to.
269 Unbound support for RFC8375: The special-use domain 'home.arpa' is
270 by default blocked. To unblock it use a local-zone nodefault
271 statement in unbound.conf:
272 local-zone: "home.arpa." nodefault
274 Or use another type of local-zone to override with your choice.
276 The reason for this is discussed in Section 6.1 of RFC8375:
277 Because 'home.arpa.' is not globally scoped and cannot be secured
278 using DNSSEC based on the root domain's trust anchor, there is no way
279 to tell, using a standard DNS query, in which homenet scope an answer
280 belongs. Consequently, users may experience surprising results with
281 such names when roaming to different homenets.
284 Commit b8d60729deef changed the TCP congestion control framework so
285 that any of the included congestion control modules could be
286 the single module built into the kernel. Previously newreno
287 was automatically built in through direct reference. As of
288 this commit you are required to declare at least one congestion
289 control module (e.g. 'options CC_NEWRENO') and to also declare a
290 default using the CC_DEFAULT option (e.g. options CC_DEFAULT="newreno\").
291 The GENERIC configuration includes CC_NEWRENO and defines newreno
292 as the default. If no congestion control option is built into the
293 kernel and you are including networking, the kernel compile will
294 fail. Also if no default is declared the kernel compile will fail.
297 Mips has been removed from universe builds. It will be removed from the
301 Commit f0c9847a6c47 changed the arguments for VOP_ALLOCATE.
302 The NFS modules must be rebuilt from sources and any out
303 of tree file systems that implement their own VOP_ALLOCATE
304 may need to be modified.
307 The synchronous PPP kernel driver sppp(4) has been removed.
308 The cp(4) and ce(4) drivers are now always compiled with netgraph(4)
309 support, formerly enabled by NETGRAPH_CRONYX option.
312 sh(1) is now the default shell for the root user. To force root to use
313 the csh shell, please run the following command as root:
318 Ncurses distribution has been split between libtinfow and libncurses
319 with libncurses.so becoming a linker (ld) script to seamlessly link
320 to libtinfow as needed. Bump _FreeBSD_version to 1400035 to reflect
324 As of commit 8160a0f62be6, the dummynet module no longer depends on the
325 ipfw module. Dummynet can now be used by pf as well as ipfw. As such
326 users who relied on this dependency may need to include ipfw in the
327 list of modules to load on their systems.
330 As of commit 903873ce1560, the mixer(8) utility has got a slightly
331 new syntax. Please refer to the mixer(8) manual page for more
332 information. The old mixer utility can be installed from ports:
333 audio/freebsd-13-mixer
336 As of commit 55089ef4f8bb, the global variable nfs_maxcopyrange has
337 been deleted from the nfscommon.ko. As such, nfsd.ko must be built
338 from up to date sources to avoid an undefined reference when
342 As of commit 62ca9fc1ad56 OpenSSL no longer enables kernel TLS
343 by default. Users can enable kernel TLS via the "KTLS" SSL
344 option. This can be enabled globally by using a custom
345 OpenSSL config file via OPENSSL_CONF or via an
346 application-specific configuration option for applications
347 which permit setting SSL options via SSL_CONF_cmd(3).
350 Commit 3ad1e1c1ce20 changed the internal KAPI between the NFS
351 modules. Therefore, all need to be rebuilt from sources.
354 Commit b69019c14cd8 removes pf's DIOCGETSTATESNV ioctl.
355 As of be70c7a50d32 it is no longer used by userspace, but it does mean
356 users may not be able to enumerate pf states if they update the kernel
357 past b69019c14cd8 without first updating userspace past be70c7a50d32.
360 As of commit 01ad0c007964 if_bridge member interfaces can no longer
361 change their MTU. Changing the MTU of the bridge itself will change the
362 MTU on all member interfaces instead.
365 Commit ee29e6f31111 changed the internal KAPI between the nfscommon
366 and nfsd modules. Therefore, both need to be rebuilt from sources.
367 Bump __FreeBSD_version to 1400026 for this KAPI change.
370 The 20210707 awk update brought in a change in behavior. This has
371 been corrected as of d4d252c49976. Between these dates, if you
372 installed a new awk binary, you may not be able to build a new
373 kernel because the change in behavior affected the genoffset
374 script used to build the kernel. If you did update, the fix is
375 to update your sources past the above hash and do
378 % sudo -E make install
379 to enable building kernels again.
382 Commit 1e0a518d6548 changed the internal KAPI between the NFS
383 modules. They all need to be rebuilt from sources. I did not
384 bump __FreeBSD_version, since it was bumped recently.
387 awk has been updated to the latest one-true-awk version 20210215.
388 This contains a number of minor bug fixes.
391 The NFSv4 client now uses the highest minor version of NFSv4
392 supported by the NFSv4 server by default instead of minor version 0,
394 The "minorversion" mount option may be used to override this default.
397 Bump __FreeBSD_version to 1400024 for LinuxKPI changes.
398 Most notably netdev.h can change now as the (last) dependencies
399 (mlx4/ofed) are now using struct ifnet directly, but also for PCI
400 additions and others.
403 The directory "blacklisted" under /usr/share/certs/ has been
404 renamed to "untrusted".
407 svnlite has been removed from base. Should you need svn for any reason
408 please install the svn package or port.
411 Commit e1a907a25cfa changed the internal KAPI between the krpc
412 and nfsserver. As such, both modules must be rebuilt from
413 sources. Bump __FreeBSD_version to 1400022.
416 The an(4) driver has been removed from FreeBSD.
419 The vendor/openzfs branch was renamed to vendor/openzfs/legacy to
420 start tracking OpenZFS upstream more closely. Please see
421 https://lists.freebsd.org/archives/freebsd-current/2021-June/000153.html
422 for details on how to correct any errors that might result. The
423 short version is that you need to remove the old branch locally:
424 git update-ref -d refs/remotes/freebsd/vendor/openzfs
425 (assuming your upstream origin is named 'freebsd').
428 Commits 17accc08ae15 and de102f870501 add new files to LinuxKPI
429 which break drm-kmod. In addition various other additions where
430 committed. Bump __FreeBSD_version to 1400015 to be able to
434 Commit ca179c4d74f2 changed the package in which the OpenSSL
435 libraries and utilities are packaged.
436 It is recommended for pkgbase user to do:
437 pkg install -f FreeBSD-openssl
438 before pkg upgrade otherwise some dependencies might not be met
439 and pkg will stop working as libssl will not be present anymore
443 Commit 875977314881 changed the internal KAPI between
444 the nfsd and nfscommon modules. As such these modules
445 need to be rebuilt from sources.
446 Without this patch in your NFSv4.1/4.2 server, enabling
447 delegations by setting vfs.nfsd.issue_delegations non-zero
451 Commit 7763814fc9c2 changed the internal KAPI between
452 the krpc and NFS. As such, the krpc, nfscommon and
453 nfscl modules must all be rebuilt from sources.
454 Without this patch, NFSv4.1/4.2 mounts should not
455 be done with the nfscbd(8) daemon running, to avoid
456 needing a working back channel for server->client RPCs.
459 Commit 01ae8969a9ee fixed the NFSv4.1/4.2 server so that it
460 handles binding of the back channel as required by RFC5661.
461 Until this patch is in your server, avoid use of the "nconnects"
462 mount option for Linux NFSv4.1/4.2 mounts.
465 For 64-bit architectures the base system is now built with Position
466 Independent Executable (PIE) support enabled by default. It may be
467 disabled using the WITHOUT_PIE knob. A clean build is required.
470 Various LinuxKPI functionality was added which conflicts with DRM.
471 Please update your drm-kmod port to after the __FreeBSD_version 1400003
475 PC Card attachments for all devices have been removed. In the case of
476 wi and cmx, the entire drivers were removed because they were only
477 PC Card devices. FreeBSD_version 1300134 should be used for this
478 since it was bumped so recently.
481 Transport-independent parts of HID support have been split off the USB
482 code in to separate subsystem. Kernel configs which include one of
483 ums, ukbd, uhid, atp, wsp, wmt, uaudio, ugold or ucycom drivers should
484 be updated with adding of "device hid" line.
487 ncurses installation has been modified to only keep the widechar
488 enabled version. Incremental build is broken for that change, so it
489 requires a clean build.
492 The FreeBSD project has migrated from Subversion to Git. Temporary
493 instructions can be found at
494 https://github.com/bsdimp/freebsd-git-docs/blob/main/src-cvt.md
495 and other documents in that repo.
498 The services database has been updated to cover more of the basic
499 services expected in a modern system. The database is big enough
500 that it will cause issues in mergemaster in Releases previous to
501 12.2 and 11.3, or in very old current systems from before r358154.
504 Obsolete in-tree GDB 6.1.1 has been removed. GDB (including kgdb)
505 may be installed from ports or packages.
508 ping6 has been merged into ping. It can now be called as "ping -6".
509 See ping(8) for details.
512 Default value of net.add_addr_allfibs has been changed to 0.
513 If you have multi-fib configuration and rely on existence of all
514 interface routes in every fib, you need to set the above sysctl to 1.
517 The internal pre-processor in the calendar(1) program has been
518 extended to support more C pre-processor commands (e.g. #ifdef, #else,
519 and #undef) and to detect unbalanced conditional statements.
520 Error messages have been extended to include the filename and line
521 number if processing stops to help fixing malformed data files.
524 All the data files for the calendar(1) program, except calendar.freebsd,
525 have been moved to the deskutils/calendar-data port, much like the
526 jewish calendar entries were moved to deskutils/hebcal years ago. After
527 make delete-old-files, you need to install it to retain full
528 functionality. calendar(1) will issue a reminder for files it can't
532 LINT files are no longer generated. We now include the relevant NOTES
533 files. Note: This may cause conflicts with updating in some cases.
534 find sys -name LINT\* -delete
535 is suggested across this commit to remove the generated LINT files.
537 If you have tried to update with generated files there, the svn
538 command you want to un-auger the tree is
541 and then do the above find from the top level. Substitute 'amd64'
542 above with where the error message indicates a conflict.
545 OpenZFS support has been integrated. Do not upgrade root pools until
546 the loader is updated to support zstd. Furthermore, we caution against
547 'zpool upgrade' for the next few weeks. The change should be transparent
548 unless you want to use new features.
550 Not all "NO_CLEAN" build scenarios work across these changes. Many
551 scenarios have been tested and fixed, but rebuilding kernels without
552 rebuilding world may fail.
554 The ZFS cache file has moved from /boot to /etc to match the OpenZFS
555 upstream default. A fallback to /boot has been added for mountroot.
557 Pool auto import behavior at boot has been moved from the kernel module
558 to an explicit "zpool import -a" in one of the rc scripts enabled by
559 zfs_enable=YES. This means your non-root zpools won't auto import until
560 you upgrade your /etc/rc.d files.
563 The resume code now notifies devd with the 'kernel' system
564 rather than the old 'kern' subsystem to be consistent with
565 other use. The old notification will be created as well, but
566 will be removed prior to FreeBSD 14.0.
569 r362275 changed the internal API between the kernel RPC and the
570 NFS modules. As such, all the modules must be recompiled from
574 r364330 modified the internal API used between the NFS modules.
575 As such, all the NFS modules must be re-compiled from sources.
578 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
579 been upgraded to 11.0.0. Please see the 20141231 entry below for
580 information about prerequisites and upgrading, if you are not already
581 using clang 3.5.0 or higher.
584 r364092 modified the internal ABI used between the kernel NFS
585 modules. As such, all of these modules need to be rebuilt
586 from sources, so a version bump was done.
589 Makefile.inc has been updated to work around the issue documented in
590 20200729. It was a case where the optimization of using symbolic links
591 to point to binaries created a situation where we'd run new binaries
592 with old libraries starting midway through the installworld process.
595 r363679 has redefined some undefined behavior in regcomp(3); notably,
596 extraneous escapes of most ordinary characters will no longer be
597 accepted. An exp-run has identified all of the problems with this in
598 ports, but other non-ports software may need extra escapes removed to
599 continue to function.
601 Because of this change, installworld may encounter the following error
602 from rtld: Undefined symbol "regcomp@FBSD_1.6" -- It is imperative that
603 you do not halt installworld. Instead, let it run to completion (whether
604 successful or not) and run installworld once more.
607 A new implementation of bc and dc has been imported in r362681. This
608 implementation corrects non-conformant behavior of the previous bc
609 and adds GNU bc compatible options. It offers a number of extensions,
610 is much faster on large values, and has support for message catalogs
611 (a number of languages are already supported, contributions of further
612 languages welcome). The option WITHOUT_GH_BC can be used to build the
613 world with the previous versions of bc and dc.
616 r362639 changed the internal API used between the NFS kernel modules.
617 As such, they all need to be rebuilt from sources.
620 r362158 changed the arguments for VFS_CHECKEXP(). As such, any
621 out of tree file systems need to be modified and rebuilt.
622 Also, any file systems that are modules must be rebuilt.
625 read(2) of a directory fd is now rejected by default. root may
626 re-enable it for system root only on non-ZFS filesystems with the
627 security.bsd.allow_read_dir sysctl(8) MIB if
628 security.bsd.suser_enabled=1.
630 It may be advised to setup aliases for grep to default to `-d skip` if
631 commonly non-recursively grepping a list that includes directories and
632 the potential for the resulting stderr output is not tolerable. Example
633 aliases are now installed, commented out, in /root/.cshrc and
637 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
638 been upgraded to 10.0.1. Please see the 20141231 entry below for
639 information about prerequisites and upgrading, if you are not already
640 using clang 3.5.0 or higher.
643 Support for obsolete compilers has been removed from the build system.
644 Clang 6 and GCC 6.4 are the minimum supported versions.
647 closefrom(2) has been moved under COMPAT12, and replaced in libc with a
648 stub that calls close_range(2). If using a custom kernel configuration,
649 you may want to ensure that the COMPAT_FREEBSD12 option is included, as
650 a slightly older -CURRENT userland and older FreeBSD userlands may not
651 be functional without closefrom(2).
654 Upstream DTS from Linux 5.6 was merged and they now have the SID
655 and THS (Secure ID controller and THermal Sensor) node present.
656 The DTB overlays have now been removed from the tree for the H3/H5 and
657 A64 SoCs and the aw_sid and aw_thermal driver have been updated to
658 deal with upstream DTS. If you are using those overlays you need to
659 remove them from loader.conf and update the DTBs on the FAT partition.
662 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
663 been upgraded to 10.0.0. Please see the 20141231 entry below for
664 information about prerequisites and upgrading, if you are not already
665 using clang 3.5.0 or higher.
668 The amd(8) automount daemon has been removed from the source tree.
669 As of FreeBSD 10.1 autofs(5) is the preferred tool for automounting.
670 amd is still available in the sysutils/am-utils port.
673 Removed brooktree driver (bktr.4) from the tree.
676 The WITH_GPL_DTC option has been removed. The BSD-licenced device tree
677 compiler in usr.bin/dtc is used on all architectures which use dtc, and
678 the GPL dtc is available (if needed) from the sysutils/dtc port.
681 The WITHOUT_LLVM_LIBUNWIND option has been removed. LLVM's libunwind
682 is used by all supported CPU architectures.
685 GCC 4.2.1 has been removed from the tree. The WITH_GCC,
686 WITH_GCC_BOOTSTRAP, and WITH_GNUCXX options are no longer available.
687 Users who wish to build FreeBSD with GCC must use the external toolchain
691 ncurses has been updated to a newer version (6.2-20200215). Given the ABI
692 has changed, users will have to rebuild all the ports that are linked to
696 The size of struct vnet and the magic cookie have changed.
697 Users need to recompile libkvm and all modules using VIMAGE
698 together with their new kernel.
701 Defining the long deprecated NO_CTF, NO_DEBUG_FILES, NO_INSTALLLIB,
702 NO_MAN, NO_PROFILE, and NO_WARNS variables is now an error. Update
703 your Makefiles and scripts to define MK_<var>=no instead as required.
705 One exception to this is that program or library Makefiles should
706 define MAN to empty rather than setting MK_MAN=no.
709 Clang/LLVM is now the default compiler and LLD the default
713 make universe no longer uses GCC 4.2.1 on any architectures.
714 Architectures not supported by in-tree Clang/LLVM require an
715 external toolchain package.
718 GCC 4.2.1 is now not built by default, as part of the GCC 4.2.1
719 retirement plan. Specifically, the GCC, GCC_BOOTSTRAP, and GNUCXX
720 options default to off for all supported CPU architectures. As a
721 short-term transition aid they may be enabled via WITH_* options.
722 GCC 4.2.1 is expected to be removed from the tree on 2020-03-31.
725 Support for armv5 has been disconnected and is being removed. The
726 machine combination MACHINE=arm MACHINE_ARCH=arm is no longer valid.
727 You must now use a MACHINE_ARCH of armv6 or armv7. The default
728 MACHINE_ARCH for MACHINE=arm is now armv7.
731 Clang/LLVM is now the default compiler for all powerpc architectures.
732 LLD is now the default linker for powerpc64. The change for powerpc64
733 also includes a change to the ELFv2 ABI, incompatible with the existing
737 Kernel-loadable random(4) modules are no longer unloadable.
740 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
741 been upgraded to 9.0.1. Please see the 20141231 entry below for
742 information about prerequisites and upgrading, if you are not already
743 using clang 3.5.0 or higher.
746 r355677 has modified the internal interface used between the
747 NFS modules in the kernel. As such, they must all be upgraded
748 simultaneously. I will do a version bump for this.
751 The root certificates of the Mozilla CA Certificate Store have been
752 imported into the base system and can be managed with the certctl(8)
753 utility. If you have installed the security/ca_root_nss port or package
754 with the ETCSYMLINK option (the default), be advised that there may be
755 differences between those included in the port and those included in
756 base due to differences in nss branch used as well as general update
757 frequency. Note also that certctl(8) cannot manage certs in the
758 format used by the security/ca_root_nss port.
761 The amd(8) automount daemon has been disabled by default, and will be
762 removed in the future. As of FreeBSD 10.1 the autofs(5) is available
766 The nctgpio and wbwd drivers have been moved to the superio bus.
767 If you have one of these drivers in a kernel configuration, then
768 you should add device superio to it. If you use one of these drivers
769 as a module and you compile a custom set of modules, then you should
770 add superio to the set.
773 KPIs for network drivers to access interface addresses have changed.
774 Users need to recompile NIC driver modules together with kernel.
777 The net.link.tap.user_open sysctl no longer prevents user opening of
778 already created /dev/tapNN devices. Access is still controlled by
779 node permissions, just like tun devices. The net.link.tap.user_open
780 sysctl is now used only to allow users to perform devfs cloning of
781 tap devices, and the subsequent open may not succeed if the user is not
782 in the appropriate group. This sysctl may be deprecated/removed
783 completely in the future.
786 mips, powerpc, and sparc64 are no longer built as part of
787 universe / tinderbox unless MAKE_OBSOLETE_GCC is defined. If
788 not defined, mips, powerpc, and sparc64 builds will look for
789 the xtoolchain binaries and if installed use them for universe
790 builds. As llvm 9.0 becomes vetted for these architectures, they
791 will be removed from the list.
794 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
795 been upgraded to 9.0.0. Please see the 20141231 entry below for
796 information about prerequisites and upgrading, if you are not already
797 using clang 3.5.0 or higher.
800 The hpt27xx, hptmv, hptnr, and hptrr drivers have been removed from
801 GENERIC. They are available as modules and can be loaded by adding
802 to /boot/loader.conf hpt27xx_load="YES", hptmv_load="YES",
803 hptnr_load="YES", or hptrr_load="YES", respectively.
806 ntpd no longer by default locks its pages in memory, allowing them
807 to be paged out by the kernel. Use rlimit memlock to restore
808 historic BSD behaviour. For example, add "rlimit memlock 32"
809 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
812 Several of ping6's options have been renamed for better consistency
813 with ping. If you use any of -ARWXaghmrtwx, you must update your
814 scripts. See ping6(8) for details.
817 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
818 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
819 been removed from mount_fusefs(8). You can safely remove them from
820 your scripts, because they had no effect.
822 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
823 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
824 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
825 sysctls have been removed. If you felt the need to set any of them to
826 a non-default value, please tell asomers@FreeBSD.org why.
829 Default permissions on the /var/account/acct file (and copies of it
830 rotated by periodic daily scripts) are changed from 0644 to 0640
831 because the file contains sensitive information that should not be
832 world-readable. If the /var/account directory must be created by
833 rc.d/accounting, the mode used is now 0750. Admins who use the
834 accounting feature are encouraged to change the mode of an existing
835 /var/account directory to 0750 or 0700.
838 Entropy collection and the /dev/random device are no longer optional
839 components. The "device random" option has been removed.
840 Implementations of distilling algorithms can still be made loadable
841 with "options RANDOM_LOADABLE" (e.g., random_fortuna.ko).
844 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
845 been upgraded to 8.0.1. Please see the 20141231 entry below for
846 information about prerequisites and upgrading, if you are not already
847 using clang 3.5.0 or higher.
850 A fix was applied to i386 kernel modules to avoid panics with
851 dpcpu or vnet. Users need to recompile i386 kernel modules
852 having pcpu or vnet sections or they will refuse to load.
855 User-wired pages now have their own counter,
856 vm.stats.vm.v_user_wire_count. The vm.max_wired sysctl was renamed
857 to vm.max_user_wired and changed from an unsigned int to an unsigned
858 long. bhyve VMs wired with the -S are now subject to the user
859 wiring limit; the vm.max_user_wired sysctl may need to be tuned to
860 avoid running into the limit.
863 The IPSEC option has been removed from GENERIC. Users requiring
864 ipsec(4) must now load the ipsec(4) kernel module.
867 The tap(4) driver has been folded into tun(4), and the module has been
868 renamed to tuntap. You should update any kld_list="if_tap" or
869 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
870 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
871 module instead, and "device tap" or "device tun" entries in kernel
872 config files to select the tuntap device instead.
875 The following knobs have been added related to tradeoffs between
876 safe use of the random device and availability in the absence of
879 kern.random.initial_seeding.bypass_before_seeding: tunable; set
880 non-zero to bypass the random device prior to seeding, or zero to
881 block random requests until the random device is initially seeded.
882 For now, set to 1 (unsafe) by default to restore pre-r346250 boot
883 availability properties.
885 kern.random.initial_seeding.read_random_bypassed_before_seeding:
886 read-only diagnostic sysctl that is set when bypass is enabled and
887 read_random(9) is bypassed, to enable programmatic handling of this
888 initial condition, if desired.
890 kern.random.initial_seeding.arc4random_bypassed_before_seeding:
891 Similar to the above, but for arc4random(9) initial seeding.
893 kern.random.initial_seeding.disable_bypass_warnings: tunable; set
894 non-zero to disable warnings in dmesg when the same conditions are
895 met as for the diagnostic sysctls above. Defaults to zero, i.e.,
896 produce warnings in dmesg when the conditions are met.
899 The loadable random module KPI has changed; the random_infra_init()
900 routine now requires a 3rd function pointer for a bool (*)(void)
901 method that returns true if the random device is seeded (and
902 therefore unblocked).
905 r345895 reverts r320698. This implies that an nfsuserd(8) daemon
906 built from head sources between r320757 (July 6, 2017) and
907 r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
908 is added to the command line.
909 nfsuserd daemons built from head sources that are post-r338192 are
910 not affected and should continue to work.
913 The fuse(4) module has been renamed to fusefs(4) for consistency with
914 other filesystems. You should update any kld_load="fuse" entries in
915 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
916 "options FUSE" entries in kernel config files.
919 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
920 8.0.0. Please see the 20141231 entry below for information about
921 prerequisites and upgrading, if you are not already using clang 3.5.0
925 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
926 compiled into your custom kernel, add 'device xz' statement to the
930 drm and drm2 have been removed from the tree. Please see
931 https://wiki.freebsd.org/Graphics for the latest information on
932 migrating to the drm ports.
935 Iflib is no longer unconditionally compiled into the kernel. Drivers
936 using iflib and statically compiled into the kernel, now require
937 the 'device iflib' config option. For the same drivers loaded as
938 modules on kernels not having 'device iflib', the iflib.ko module
939 is loaded automatically.
942 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
943 options no longer exist since r343219 and r343427 respectively;
944 nothing uses them, so they should be just removed from custom
948 r342635 changes the way efibootmgr(8) works by requiring users to add
949 the -b (bootnum) parameter for commands where the bootnum was previously
950 specified with each option. For example 'efibootmgr -B 0001' is now
951 'efibootmgr -B -b 0001'.
954 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
955 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
956 servers that have vfs.nfsd.nfs_privport set will only allow mounts
957 from clients using a reserved port. Since both the FreeBSD and Linux
958 NFSv4 clients use reserved ports by default, this should not affect
962 The XLP config has been removed. We can't support 64-bit atomics in this
963 kernel because it is running in 32-bit mode. XLP users must transition
964 to running a 64-bit kernel (XLP64 or XLPN32).
966 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
967 the preferred emulator today and we don't need two different ones.
969 The old sibyte / swarm / Broadcom BCM1250 support has been
970 removed from the mips port.
973 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
974 7.0.1. Please see the 20141231 entry below for information about
975 prerequisites and upgrading, if you are not already using clang 3.5.0
979 Remove the timed and netdate programs from the base tree. Setting
980 the time with these daemons has been obsolete for over a decade.
983 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
984 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
985 it produces broken binaries when ifuncs are in use. Users needing
986 GNU ld should install the binutils port or package.
989 The BSD crtbegin and crtend code has been enabled by default. It has
990 had extensive testing on amd64, arm64, and i386. It can be disabled
991 by building a world with -DWITHOUT_BSD_CRTBEGIN.
994 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
995 has been converted to a port (misc/ctm) and will be removed from
996 FreeBSD-13. It is available as a package (ctm) for all supported
1000 The default newsyslog.conf(5) file has been changed to only include
1001 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
1002 the filenames end in '.conf' and do not begin with a '.'.
1004 You should check the configuration files in these two directories match
1005 this naming convention. You can verify which configuration files are
1006 being included using the command:
1010 Ports for the DRM modules have been simplified. Now, amd64 users should
1011 just install the drm-kmod port. All others should install
1014 Graphics hardware that's newer than about 2010 usually works with
1015 drm-kmod. For hardware older than 2013, however, some users will need
1016 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
1017 than 2008 usually only works in drm-legacy-kmod. The graphics team can
1018 only commit to hardware made since 2013 due to the complexity of the
1019 market and difficulty to test all the older cards effectively. If you
1020 have hardware supported by drm-kmod, you are strongly encouraged to use
1021 that as you will get better support.
1023 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
1024 elsewhere, the drm and drm2 modules will be eliminated from the src base
1025 soon (with a limited exception for arm). Please update to the package
1026 asap and report any issues to x11@freebsd.org.
1028 Generally, anybody using the drm*-kmod packages should add
1029 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
1030 cross-threading surprises, especially with automatic driver
1031 loading from X11 startup. These will become the defaults in 13-current
1035 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
1036 custom kernel and module loading configuration files must be updated
1037 accordingly. Moreover, interfaces previous presented as ixlvN to the
1038 system are now exposed as iavfN and network configuration files must
1039 be adjusted as necessary.
1042 OpenSSL has been updated to version 1.1.1. This update included
1043 additional various API changes throughout the base system. It is
1044 important to rebuild third-party software after upgrading. The value
1045 of __FreeBSD_version has been bumped accordingly.
1048 The legacy DRM modules and drivers have now been added to the loader's
1049 module blacklist, in favor of loading them with kld_list in rc.conf(5).
1050 The module blacklist may be overridden with the loader.conf(5)
1051 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
1055 The cam(4) based nda(4) driver will be used over nvd(4) by default on
1056 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
1057 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
1058 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
1062 Reproducible build mode is now on by default, in preparation for
1063 FreeBSD 12.0. This eliminates build metadata such as the user,
1064 host, and time from the kernel (and uname), unless the working tree
1065 corresponds to a modified checkout from a version control system.
1066 The previous behavior can be obtained by setting the /etc/src.conf
1067 knob WITHOUT_REPRODUCIBLE_BUILD.
1070 The Yarrow CSPRNG has been removed from the kernel as it has not been
1071 supported by its designers since at least 2003. Fortuna has been the
1072 default since FreeBSD-11.
1075 devctl freeze/thaw have gone into the tree, the rc scripts have been
1076 updated to use them and devmatch has been changed. You should update
1077 kernel, userland and rc scripts all at the same time.
1080 The default interpreter has been switched from 4th to Lua.
1081 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
1082 interpreter. If you have custom FORTH code you will need to set
1083 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
1084 src.conf for the build. This will create default hard links between
1085 loader and loader_4th instead of loader and loader_lua, the new default.
1086 If you are using UEFI it will create the proper hard link to loader.efi.
1088 bhyve uses userboot.so. It remains 4th-only until some issues are solved
1089 regarding coexisting with multiple versions of FreeBSD are resolved.
1092 ls(1) now respects the COLORTERM environment variable used in other
1093 systems and software to indicate that a colored terminal is both
1094 supported and desired. If ls(1) is suddenly emitting colors, they may
1095 be disabled again by either removing the unwanted COLORTERM from your
1096 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
1097 may not be observed in a future release.
1100 The default pager for most commands has been changed to "less". To
1101 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
1105 The jedec_ts(4) driver has been removed. A superset of its functionality
1106 is available in the jedec_dimm(4) driver, and the manpage for that
1107 driver includes migration instructions. If you have "device jedec_ts"
1108 in your kernel configuration file, it must be removed.
1111 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
1112 This should have no effect if the kernel is booted via BIOS/legacy boot.
1113 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
1114 has a buggy firmware that prevents a successful boot due to use of
1118 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
1119 support has been removed from the tree. These ports were
1120 obsolete and/or known to be broken for many years.
1123 loader.efi has been augmented to participate more fully in the
1124 UEFI boot manager protocol. loader.efi will now look at the
1125 BootXXXX environment variable to determine if a specific kernel
1126 or root partition was specified. XXXX is derived from BootCurrent.
1127 efibootmgr(8) manages these standard UEFI variables.
1130 zfsloader's functionality has now been folded into loader.
1131 zfsloader is no longer necessary once you've updated your
1132 boot blocks. For a transition period, we will install a
1133 hardlink for zfsloader to loader to allow a smooth transition
1134 until the boot blocks can be updated (hard link because old
1135 zfs boot blocks don't understand symlinks).
1138 ARM64 now have efifb support, if you want to have serial console
1139 on your arm64 board when an screen is connected and the bootloader
1140 setup a frame buffer for us to use, just add :
1143 in /boot/loader.conf
1144 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
1145 an screen connected as the firmware will setup a frame buffer are that
1146 u-boot will expose as an EFI frame buffer.
1149 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
1150 or take steps to update /etc/passwd before doing installworld on
1151 existing systems. Do not skip the "mergemaster -Fp" step before
1152 installworld, as described in the update procedures near the bottom
1153 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
1154 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
1155 the ntp config file contain options that change file/dir locations.
1156 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
1157 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
1158 taking steps to ensure that all required files/dirs are accessible
1162 Big endian arm support has been removed.
1165 The static environment setup in kernel configs is no longer mutually
1166 exclusive with the loader(8) environment by default. In order to
1167 restore the previous default behavior of disabling the loader(8)
1168 environment if a static environment is present, you must specify
1169 loader_env.disabled=1 in the static environment.
1172 The ABI of syscalls used by management tools like sockstat and
1173 netstat has been broken to allow 32-bit binaries to work on
1174 64-bit kernels without modification. These programs will need
1175 to match the kernel in order to function. External programs may
1176 require minor modifications to accommodate a change of type in
1177 structures from pointers to 64-bit virtual addresses.
1180 On i386 and amd64 atomics are now inlined. Out of tree modules using
1181 atomics will need to be rebuilt.
1184 The '%I' format in the kern.corefile sysctl limits the number of
1185 core files that a process can generate to the number stored in the
1186 debug.ncores sysctl. The '%I' format is replaced by the single digit
1187 index. Previously, if all indexes were taken the kernel would overwrite
1188 only a core file with the highest index in a filename.
1189 Currently the system will create a new core file if there is a free
1190 index or if all slots are taken it will overwrite the oldest one.
1193 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
1194 6.0.1. Please see the 20141231 entry below for information about
1195 prerequisites and upgrading, if you are not already using clang 3.5.0
1199 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
1200 needed to be changed to work with it. This change was made with r335763
1201 and requires a mergemaster / etcupdate / etc to update the installed
1205 r334930 changed the interface between the NFS modules, so they all
1206 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
1209 As of r334391 lld is the default amd64 system linker; it is installed
1210 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
1214 The kernel / userland interface for devinfo changed, so you'll
1215 need a new kernel and userland as a pair for it to work (rebuilding
1216 lib/libdevinfo is all that's required). devinfo and devmatch will
1217 not work, but everything else will when there's a mismatch.
1220 The on-disk format for hwpmc callchain records has changed to include
1221 threadid corresponding to a given record. This changes the field offsets
1222 and thus requires that libpmcstat be rebuilt before using a kernel
1226 The vxge(4) driver has been removed. This driver was introduced into
1227 HEAD one week before the Exar left the Ethernet market and is not
1228 known to be used. If you have device vxge in your kernel config file
1232 The amd64 kernel now requires a ld that supports ifunc to produce a
1233 working kernel, either lld or a newer binutils. lld is built by default
1234 on amd64, and the 'buildkernel' target uses it automatically. However,
1235 it is not the default linker, so building the kernel the traditional
1236 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
1237 binutils port/package). lld will soon be default, and this requirement
1240 NOTE: As of r334391 lld is the default system linker on amd64, and no
1241 workaround is necessary.
1244 The nxge(4) driver has been removed. This driver was for PCI-X 10g
1245 cards made by s2io/Neterion. The company was acquired by Exar and
1246 no longer sells or supports Ethernet products. If you have device
1247 nxge in your kernel config file it must be removed.
1250 The tz database (tzdb) has been updated to 2018e. This version more
1251 correctly models time stamps in time zones with negative DST such as
1252 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
1253 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
1254 time zone abbreviations and the tm_isdst flag.
1257 The ixgb(4) driver has been removed. This driver was for an early and
1258 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
1259 quickly shifted to the long lived ixgbe family. If you have device
1260 ixgb in your kernel config file it must be removed.
1263 The lmc(4) driver has been removed. This was a WAN interface
1264 card that was already reportedly rare in 2003, and had an ambiguous
1265 license. If you have device lmc in your kernel config file it must
1269 Support for Arcnet networks has been removed. If you have device
1270 arcnet or device cm in your kernel config file they must be
1274 Support for FDDI networks has been removed. If you have device
1275 fddi or device fpa in your kernel config file they must be
1279 In addition to supporting RFC 3164 formatted messages, the
1280 syslogd(8) service is now capable of parsing RFC 5424 formatted
1281 log messages. The main benefit of using RFC 5424 is that clients
1282 may now send log messages with timestamps containing year numbers,
1283 microseconds and time zone offsets.
1285 Similarly, the syslog(3) C library function has been altered to
1286 send RFC 5424 formatted messages to the local system logging
1287 daemon. On systems using syslogd(8), this change should have no
1288 negative impact, as long as syslogd(8) and the C library are
1289 updated at the same time. On systems using a different system
1290 logging daemon, it may be necessary to make configuration
1291 adjustments, depending on the software used.
1293 When using syslog-ng, add the 'syslog-protocol' flag to local
1294 input sources to enable parsing of RFC 5424 formatted messages:
1297 unix-dgram("/var/run/log" flags(syslog-protocol));
1300 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
1301 of the 'imuxsock' module to let messages be processed by the
1302 regular RFC 3164/5424 parsing pipeline:
1304 module(load="imuxsock" SysSock.UseSpecialParser="off")
1306 Do note that these changes only affect communication between local
1307 applications and syslogd(8). The format that syslogd(8) uses to
1308 store messages on disk or forward messages to other systems
1309 remains unchanged. syslogd(8) still uses RFC 3164 for these
1310 purposes. Options to customize this behaviour will be added in the
1311 future. Utilities that process log files stored in /var/log are
1312 thus expected to continue to function as before.
1314 __FreeBSD_version has been incremented to 1200061 to denote this
1318 Support for token ring networks has been removed. If you
1319 have "device token" in your kernel config you should remove
1320 it. No device drivers supported token ring.
1323 makefs was modified to be able to tag ISO9660 El Torito boot catalog
1324 entries as EFI instead of overloading the i386 tag as done previously.
1325 The amd64 mkisoimages.sh script used to build amd64 ISO images for
1326 release was updated to use this. This may mean that makefs must be
1327 updated before "make cdrom" can be run in the release directory. This
1328 should be as simple as:
1330 $ cd $SRCDIR/usr.sbin/makefs
1331 $ make depend all install
1334 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
1335 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
1336 Co-existence for the transition period will come shortly. Booting is a
1337 complex environment and test coverage for Lua-enabled loaders has been
1338 thin, so it would be prudent to assume it might not work and make
1339 provisions for backup boot methods.
1342 devmatch functionality has been turned on in devd. It will automatically
1343 load drivers for unattached devices. This may cause unexpected drivers
1344 to be loaded. Please report any problems to current@ and
1348 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
1349 6.0.0. Please see the 20141231 entry below for information about
1350 prerequisites and upgrading, if you are not already using clang 3.5.0
1354 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
1355 This means it is used to link the kernel and userland libraries and
1356 executables, but is not yet installed as /usr/bin/ld by default.
1358 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
1359 WITHOUT_LLD_BOOTSTRAP=yes
1362 On i386, pmtimer has been removed. Its functionality has been folded
1363 into apm. It was a no-op on ACPI in current for a while now (but was
1364 still needed on i386 in FreeBSD 11 and earlier). Users may need to
1365 remove it from kernel config files.
1368 The use of RSS hash from the network card aka flowid has been
1369 disabled by default for lagg(4) as it's currently incompatible with
1370 the lacp and loadbalance protocols.
1372 This can be re-enabled by setting the following in loader.conf:
1373 net.link.lagg.default_use_flowid="1"
1376 The SW_WATCHDOG option is no longer necessary to enable the
1377 hardclock-based software watchdog if no hardware watchdog is
1378 configured. As before, SW_WATCHDOG will cause the software
1379 watchdog to be enabled even if a hardware watchdog is configured.
1382 r326887 fixes the issue described in the 20171214 UPDATING entry.
1383 r326888 flips the switch back to building GELI support always.
1386 r362593 broke ZFS + GELI support for reasons unknown. However,
1387 it also broke ZFS support generally, so GELI has been turned off
1388 by default as the lesser evil in r326857. If you boot off ZFS and/or
1389 GELI, it might not be a good time to update.
1392 PowerPC users must update loader(8) by rebuilding world before
1393 installing a new kernel, as the protocol connecting them has
1394 changed. Without the update, loader metadata will not be passed
1395 successfully to the kernel and users will have to enter their
1396 root partition at the kernel mountroot prompt to continue booting.
1397 Newer versions of loader can boot old kernels without issue.
1400 The LOADER_FIREWIRE_SUPPORT build variable has been renamed to
1401 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
1402 to WITH/OUT_LOADER_GELI.
1405 The naive and non-compliant support of posix_fallocate(2) in ZFS
1406 has been removed as of r325320. The system call now returns EINVAL
1407 when used on a ZFS file. Although the new behavior complies with the
1408 standard, some consumers are not prepared to cope with it.
1409 One known victim is lld prior to r325420.
1412 Building in a FreeBSD src checkout will automatically create object
1413 directories now rather than store files in the current directory if
1414 'make obj' was not ran. Calling 'make obj' is no longer necessary.
1415 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
1416 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
1420 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
1421 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
1422 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
1423 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
1424 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
1425 The UNIFIED_OBJDIR option is a transitional feature that will be
1426 removed for 12.0 release; please migrate to the new format for any
1427 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
1428 than hardcoding paths.
1431 The native-xtools target no longer installs the files by default to the
1432 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
1433 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
1436 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
1437 options are changing from controlling the build if defined / undefined
1438 to controlling the build with explicit 'yes' or 'no' values. They will
1439 shift to WITH/WITHOUT options to match other options in the system.
1442 libstand has turned into a private library for sys/boot use only.
1443 It is no longer supported as a public interface outside of sys/boot.
1446 The arm port has split armv6 into armv6 and armv7. armv7 is now
1447 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
1448 and are running a kernel from before r324363, you will need to add
1449 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
1452 When building multiple kernels using KERNCONF, non-existent KERNCONF
1453 files will produce an error and buildkernel will fail. Previously
1454 missing KERNCONF files silently failed giving no indication as to
1455 why, only to subsequently discover during installkernel that the
1456 desired kernel was never built in the first place.
1459 The default serial number format for CTL LUNs has changed. This will
1460 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
1461 or iSCSI clients care about their LUNs' serial numbers. Users who
1462 require serial number stability should hardcode serial numbers in
1466 For 32-bit arm compiled for hard-float support, soft-floating point
1467 binaries now always get their shared libraries from
1468 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
1469 /usr/libsoft also existed). Only users with a hard-float ld.so, but
1470 soft-float everything else should be affected.
1473 The geli password typed at boot is now hidden. To restore the previous
1474 behavior, see geli(8) for configuration options.
1477 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
1478 sysctl values. Minor nit, but requires a rebuild of both world/kernel
1482 "make check" behavior (made in ^/head@r295380) has been changed to
1483 execute from a limited sandbox, as opposed to executing from
1487 - The "beforecheck" and "aftercheck" targets are now specified.
1488 - ${CHECKDIR} (added in commit noted above) has been removed.
1489 - Legacy behavior can be enabled by setting
1490 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
1492 If the limited sandbox mode is enabled, "make check" will execute
1493 "make distribution", then install, execute the tests, and clean up the
1494 sandbox if successful.
1496 The "make distribution" and "make install" targets are typically run as
1497 root to set appropriate permissions and ownership at installation time.
1498 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
1499 environment if executing "make check" with limited sandbox mode using
1500 an unprivileged user.
1503 Since the switch to GPT disk labels, fsck for UFS/FFS has been
1504 unable to automatically find alternate superblocks. As of r322297,
1505 the information needed to find alternate superblocks has been
1506 moved to the end of the area reserved for the boot block.
1507 Filesystems created with a newfs of this vintage or later
1508 will create the recovery information. If you have a filesystem
1509 created prior to this change and wish to have a recovery block
1510 created for your filesystem, you can do so by running fsck in
1511 foreground mode (i.e., do not use the -p or -y options). As it
1512 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
1513 to which you should answer yes.
1516 As of r321665, an NFSv4 server configuration that services
1517 Kerberos mounts or clients that do not support the uid/gid in
1518 owner/owner_group string capability, must explicitly enable
1519 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
1520 machine's /etc/rc.conf file.
1523 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
1524 Please see the 20141231 entry below for information about prerequisites
1525 and upgrading, if you are not already using clang 3.5.0 or higher.
1528 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
1529 r-commands (rlogin, rsh, etc.) to be built with the base system.
1532 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
1533 a very major ABI incompatible change, so users of FreeBSD/powerpc must
1534 be careful when performing source upgrades. It is best to run
1535 'make installworld' from an alternate root system, either a live
1536 CD/memory stick, or a temporary root partition. Additionally, all ports
1537 must be recompiled. powerpc64 is largely unaffected, except in the case
1538 of 32-bit compatibility. All 32-bit binaries will be affected.
1541 Forward compatibility for the "ino64" project have been committed. This
1542 will allow most new binaries to run on older kernels in a limited
1543 fashion. This prevents many of the common foot-shooting actions in the
1544 upgrade as well as the limited ability to roll back the kernel across
1545 the ino64 upgrade. Complicated use cases may not work properly, though
1546 enough simpler ones work to allow recovery in most situations.
1549 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
1550 if you require the GPL compiler.
1553 The internal ABI used for communication between the NFS kernel modules
1554 was changed by r320085, so __FreeBSD_version was bumped to
1555 ensure all the NFS related modules are updated together.
1558 The ABI of struct event was changed by extending the data
1559 member to 64bit and adding ext fields. For upgrade, same
1560 precautions as for the entry 20170523 "ino64" must be
1564 The GNU roff toolchain has been removed from base. To render manpages
1565 which are not supported by mandoc(1), man(1) can fallback on GNU roff
1566 from ports (and recommends to install it).
1567 To render roff(7) documents, consider using GNU roff from ports or the
1568 heirloom doctools roff toolchain from ports via pkg install groff or
1569 via pkg install heirloom-doctools.
1572 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
1573 smaller runtime footprint builds. This is useful for embedded systems
1574 which only require one chipset support.
1576 If you load it as a module, make sure this is in /boot/loader.conf:
1580 This will load the HAL, all chip/RF backends and if_ath_pci.
1581 If you have if_ath_pci in /boot/loader.conf, ensure it is after
1582 if_ath or it will not load any HAL chipset support.
1584 If you want to selectively load things (eg on cheaper ARM/MIPS
1585 platforms where RAM is at a premium) you should:
1588 * load the chip modules in question
1589 * load ath_rate, ath_dfs
1591 * load if_ath_pci and/or if_ath_ahb depending upon your particular
1592 bus bind type - this is where probe/attach is done.
1594 For further comments/feedback, poke adrian@ .
1597 The "ino64" 64-bit inode project has been committed, which extends
1598 a number of types to 64 bits. Upgrading in place requires care and
1599 adherence to the documented upgrade procedure.
1601 If using a custom kernel configuration ensure that the
1602 COMPAT_FREEBSD11 option is included (as during the upgrade the
1603 system will be running the ino64 kernel with the existing world).
1605 For the safest in-place upgrade begin by removing previous build
1606 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full
1607 procedure documented below under the heading "To rebuild everything and
1608 install it on the current system." Specifically, a reboot is required
1609 after installing the new kernel before installing world. While an
1610 installworld normally works by accident from multiuser after rebooting
1611 the proper kernel, there are many cases where this will fail across this
1612 upgrade and installworld from single user is required.
1615 The NATM framework including the en(4), fatm(4), hatm(4), and
1616 patm(4) devices has been removed. Consumers should plan a
1617 migration before the end-of-life date for FreeBSD 11.
1620 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
1621 diff has not been implemented, if those are needed a newer version of
1622 GNU diff is available via the diffutils package under the gdiff name.
1625 As of r316810 for ipfilter, keep frags is no longer assumed when
1626 keep state is specified in a rule. r316810 aligns ipfilter with
1627 documentation in man pages separating keep frags from keep state.
1628 This allows keep state to be specified without forcing keep frags
1629 and allows keep frags to be specified independently of keep state.
1630 To maintain previous behaviour, also specify keep frags with
1631 keep state (as documented in ipf.conf.5).
1634 arm64 builds now use the base system LLD 4.0.0 linker by default,
1635 instead of requiring that the aarch64-binutils port or package be
1636 installed. To continue using aarch64-binutils, set
1637 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
1640 The UDP optimization in entry 20160818 that added the sysctl
1641 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
1642 packets will no longer be treated as L3 broadcast packets.
1645 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
1646 use any explicitly assigned loopback address available in the jail
1647 instead of using the first assigned address of the jail.
1650 The ctl.ko module no longer implements the iSCSI target frontend:
1651 cfiscsi.ko does instead.
1653 If building cfiscsi.ko as a kernel module, the module can be loaded
1654 via one of the following methods:
1655 - `cfiscsi_load="YES"` in loader.conf(5).
1656 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
1657 - ctladm(8)/ctld(8), when compiled with iSCSI support
1658 (`WITH_ISCSI=yes` in src.conf(5))
1660 Please see cfiscsi(4) for more details.
1663 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
1664 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
1665 same source (previously, the dependency of mmcsd.ko on mmc.ko was
1666 missing, but mmcsd.ko now will refuse to load if it is incompatible
1670 The syntax of ipfw(8) named states was changed to avoid ambiguity.
1671 If you have used named states in the firewall rules, you need to modify
1672 them after installworld and before rebooting. Now named states must
1673 be prefixed with colon.
1676 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
1677 removed as the userland we provide cannot use them. The KMS version
1678 (sys/dev/drm2) supports the same hardware.
1681 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
1682 Please see the 20141231 entry below for information about prerequisites
1683 and upgrading, if you are not already using clang 3.5.0 or higher.
1686 The code that provides support for ZFS .zfs/ directory functionality
1687 has been reimplemented. It's not possible now to create a snapshot
1688 by mkdir under .zfs/snapshot/. That should be the only user visible
1692 EISA bus support has been removed. The WITH_EISA option is no longer
1696 MCA bus support has been removed.
1699 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
1700 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
1703 The EM_MULTIQUEUE kernel configuration option is deprecated now that
1704 the em(4) driver conforms to iflib specifications.
1707 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
1708 IFLIB. If you have a custom kernel configuration that excludes em(4)
1709 but you use igb(4), you need to re-add em(4) to your custom
1713 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
1714 Please see the 20141231 entry below for information about prerequisites
1715 and upgrading, if you are not already using clang 3.5.0 or higher.
1718 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
1719 Please see the 20141231 entry below for information about prerequisites
1720 and upgrading, if you are not already using clang 3.5.0 or higher.
1723 The layout of the pmap structure has changed for powerpc to put the pmap
1724 statistics at the front for all CPU variations. libkvm(3) and all tools
1725 that link against it need to be recompiled.
1728 isl(4) and cyapa(4) drivers now require a new driver,
1729 chromebook_platform(4), to work properly on Chromebook-class hardware.
1730 On other types of hardware the drivers may need to be configured using
1731 device hints. Please see the corresponding manual pages for details.
1734 The urtwn(4) driver was merged into rtwn(4) and now consists of
1735 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
1737 Also, firmware for RTL8188CE was renamed due to possible name
1738 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
1741 GNU rcs has been removed from base. It is available as packages:
1742 - rcs: Latest GPLv3 GNU rcs version.
1743 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
1747 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
1748 modules now requires that the kernel configuration contain the
1749 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
1752 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
1753 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
1756 Relocatable object files with the extension of .So have been renamed
1757 to use an extension of .pico instead. The purpose of this change is
1758 to avoid a name clash with shared libraries on case-insensitive file
1759 systems. On those file systems, foo.So is the same file as foo.so.
1762 GNU rcs has been turned off by default. It can (temporarily) be built
1763 again by adding WITH_RCS knob in src.conf.
1764 Otherwise, GNU rcs is available from packages:
1765 - rcs: Latest GPLv3 GNU rcs version.
1766 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
1769 The backup_uses_rcs functionality has been removed from rc.subr.
1772 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
1773 two separate components, QUEUE_MACRO_DEBUG_TRACE and
1774 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
1775 QUEUE_MACRO_DEBUG behavior.
1778 r304787 changed some ioctl interfaces between the iSCSI userspace
1779 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1780 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1784 The UDP receive code has been updated to only treat incoming UDP
1785 packets that were addressed to an L2 broadcast address as L3
1786 broadcast packets. It is not expected that this will affect any
1787 standards-conforming UDP application. The new behaviour can be
1788 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1792 Remove the openbsd_poll system call.
1793 __FreeBSD_version has been bumped because of this.
1796 The stable/11 branch has been created from head@r302406.
1798 After branch N is created, entries older than the N-2 branch point are removed
1799 from this file. After stable/14 is branched and current becomes FreeBSD 15,
1800 entries older than stable/12 branch point will be removed from current's
1807 Sometimes, obscure build problems are the result of environment
1808 poisoning. This can happen because the make utility reads its
1809 environment when searching for values for global variables. To run
1810 your build attempts in an "environmental clean room", prefix all make
1811 commands with 'env -i '. See the env(1) manual page for more details.
1812 Occasionally a build failure will occur with "make -j" due to a race
1813 condition. If this happens try building again without -j, and please
1814 report a bug if it happens consistently.
1816 When upgrading from one major version to another it is generally best to
1817 upgrade to the latest code in the currently installed branch first, then
1818 do an upgrade to the new branch. This is the best-tested upgrade path,
1819 and has the highest probability of being successful. Please try this
1820 approach if you encounter problems with a major version upgrade. Since
1821 the stable 4.x branch point, one has generally been able to upgrade from
1822 anywhere in the most recent stable branch to head / current (or even the
1823 last couple of stable branches). See the top of this file when there's
1826 The update process will emit an error on an attempt to perform a build
1827 or install from a FreeBSD version below the earliest supported version.
1828 When updating from an older version the update should be performed one
1829 major release at a time, including running `make delete-old` at each
1832 When upgrading a live system, having a root shell around before
1833 installing anything can help undo problems. Not having a root shell
1834 around can lead to problems if pam has changed too much from your
1835 starting point to allow continued authentication after the upgrade.
1837 This file should be read as a log of events. When a later event changes
1838 information of a prior event, the prior event should not be deleted.
1839 Instead, a pointer to the entry with the new information should be
1840 placed in the old entry. Readers of this file should also sanity check
1841 older entries before relying on them blindly. Authors of new entries
1842 should write them with this in mind.
1846 When upgrading the boot ZFS pool to a new version (via zpool upgrade),
1847 always follow these three steps:
1849 1) recompile and reinstall the ZFS boot loader and boot block
1850 (this is part of "make buildworld" and "make installworld")
1852 2) update the ZFS boot block on your boot drive (only required when
1853 doing a zpool upgrade):
1855 When booting on x86 via BIOS, use the following to update the ZFS boot
1856 block on the freebsd-boot partition of a GPT partitioned drive ada0:
1857 gpart bootcode -p /boot/gptzfsboot -i $N ada0
1858 The value $N will typically be 1. For EFI booting, see EFI notes.
1860 3) zpool upgrade the root pool. New bootblocks will work with old
1861 pools, but not vice versa, so they need to be updated before any
1864 Non-boot pools do not need these updates.
1869 There are two locations the boot loader can be installed into. The
1870 current location (and the default) is \efi\freebsd\loader.efi and using
1871 efibootmgr(8) to configure it. The old location, that must be used on
1872 deficient systems that don't honor efibootmgr(8) protocols, is the
1873 fallback location of \EFI\BOOT\BOOTxxx.EFI. Generally, you will copy
1874 /boot/loader.efi to this location, but on systems installed a long time
1875 ago the ESP may be too small and /boot/boot1.efi may be needed unless
1876 the ESP has been expanded in the meantime.
1878 Recent systems will have the ESP mounted on /boot/efi, but older ones
1879 may not have it mounted at all, or mounted in a different
1880 location. Older arm SD images with MBR used /boot/msdos as the
1881 mountpoint. The ESP is a MSDOS filesystem.
1883 The EFI boot loader rarely needs to be updated. For ZFS booting,
1884 however, you must update loader.efi before you do 'zpool upgrade' the
1885 root zpool, otherwise the old loader.efi may reject the upgraded zpool
1886 since it does not automatically understand some new features.
1888 See loader.efi(8) and uefi(8) for more details.
1892 If you are updating from a prior version of FreeBSD (even one just
1893 a few days old), you should follow this procedure. It is the most
1894 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1896 make kernel-toolchain
1897 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1898 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1900 To test a kernel once
1901 ---------------------
1902 If you just want to boot a kernel once (because you are not sure
1903 if it works, or if you want to boot a known bad kernel to provide
1904 debugging information) run
1905 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1906 nextboot -k testkernel
1908 To rebuild everything and install it on the current system.
1909 -----------------------------------------------------------
1910 # Note: sometimes if you are running current you gotta do more than
1911 # is listed here if you are upgrading from a really old current.
1913 <make sure you have good level 0 dumps>
1915 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1916 make installkernel KERNCONF=YOUR_KERNEL_HERE
1918 <reboot in single user> [3]
1925 To cross-install current onto a separate partition
1926 --------------------------------------------------
1927 # In this approach we use a separate partition to hold
1928 # current's root, 'usr', and 'var' directories. A partition
1929 # holding "/", "/usr" and "/var" should be about 2GB in
1932 <make sure you have good level 0 dumps>
1935 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1936 <maybe newfs current's root partition>
1937 <mount current's root partition on directory ${CURRENT_ROOT}>
1938 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1939 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1940 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1941 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1942 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1943 <reboot into current>
1944 <do a "native" rebuild/install as described in the previous section>
1945 <maybe install compatibility libraries from ports/misc/compat*>
1949 To upgrade in-place from stable to current
1950 ----------------------------------------------
1951 <make sure you have good level 0 dumps>
1953 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1954 make installkernel KERNCONF=YOUR_KERNEL_HERE
1956 <reboot in single user> [3]
1963 Make sure that you've read the UPDATING file to understand the
1964 tweaks to various things you need. At this point in the life
1965 cycle of current, things change often and you are on your own
1966 to cope. The defaults can also change, so please read ALL of
1967 the UPDATING entries.
1969 Also, if you are tracking -current, you must be subscribed to
1970 freebsd-current@freebsd.org. Make sure that before you update
1971 your sources that you have read and understood all the recent
1972 messages there. If in doubt, please track -stable which has
1973 much fewer pitfalls.
1975 [1] If you have third party modules, such as vmware, you should disable
1976 them at this point so they don't crash your system on
1977 reboot. Alternatively, you should rebuild all the modules you have in
1978 your system and install them as well. If you are running -current, you
1979 should seriously consider placing all sources to all the modules for
1980 your system (or symlinks to them) in /usr/local/sys/modules so this
1981 happens automatically. If all your modules come from ports, then adding
1982 the port origin directories to PORTS_MODULES instead is also automatic
1984 PORTS_MODULES+=x11/nvidia-driver
1986 [3] From the bootblocks, boot -s, and then do
1990 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed
1991 cd src # full path to source
1992 adjkerntz -i # if CMOS is wall time
1993 Also, when doing a major release upgrade, it is required that you boot
1994 into single user mode to do the installworld.
1996 [4] Note: This step is non-optional. Failure to do this step
1997 can result in a significant reduction in the functionality of the
1998 system. Attempting to do it by hand is not recommended and those
1999 that pursue this avenue should read this file carefully, as well
2000 as the archives of freebsd-current and freebsd-hackers mailing lists
2001 for potential gotchas. See etcupdate(8) for more information.
2003 [5] Usually this step is a no-op. However, from time to time
2004 you may need to do this if you get unknown user in the following
2007 [6] This only deletes old files and directories. Old libraries
2008 can be deleted by "make delete-old-libs", but you have to make
2009 sure that no program is using those libraries anymore.
2011 [8] The new kernel must be able to run existing binaries used by an
2012 installworld. When upgrading across major versions, the new kernel's
2013 configuration must include the correct COMPAT_FREEBSD<n> option for
2014 existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure
2015 to do so may leave you with a system that is hard to boot to recover. A
2016 GENERIC kernel will include suitable compatibility options to run
2017 binaries from older branches. Note that the ability to run binaries
2018 from unsupported branches is not guaranteed.
2020 Make sure that you merge any new devices from GENERIC since the
2021 last time you updated your kernel config file. Options also
2022 change over time, so you may need to adjust your custom kernels
2025 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2026 "?=" instead of the "=" assignment operator, so that buildworld can
2027 override the CPUTYPE if it needs to.
2029 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2030 not on the command line, or in /etc/make.conf. buildworld will
2031 warn if it is improperly defined.
2034 This file contains a list, in reverse chronological order, of major
2035 breakages in tracking -current. It is not guaranteed to be a complete
2036 list of such breakages, and only contains entries since September 23, 2011.
2037 If you need to see UPDATING entries from before that date, you will need
2038 to fetch an UPDATING file from an older FreeBSD release.
2040 Copyright information:
2042 Copyright 1998-2009 M. Warner Losh <imp@FreeBSD.org>
2044 Redistribution, publication, translation and use, with or without
2045 modification, in full or in part, in any form or format of this
2046 document are permitted without further permission from the author.
2048 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2049 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2050 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2051 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2052 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2053 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2054 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2055 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2056 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2057 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2058 POSSIBILITY OF SUCH DAMAGE.
2060 Contact Warner Losh if you have any questions about your use of