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 Commit 57ce37f9dcd0 changed the internal KAPI between the
32 nfscommon and nfscl modules. Both must be rebuilt from sources.
35 dialog(1) has been replaced in base by bsddialog(1), while most of the
36 time replacing a dialog(1) call by a bsddialog(1) call works out of the
37 box, bsddialog(1) is not considered as a drop-in replacement for
40 If you do depend on dialog(1) functionality, please install cdialog
46 The EARLY_AP_STARTUP kernel option is mandatory on x86. The option
47 has been added to DEFAULTS, so it should automatically be included in
48 custom kernel configurations without any additional change.
51 A new loader tunable net.pf.default_to_drop allows pf(4)’s default
52 behaviour to be changed from pass to drop. Previously this required
53 recompiling the kernel with the option PF_DEFAULT_TO_DROP.
56 Enable splitting out pkgbase manpages into separate packages by
57 default. To disable this, set WITHOUT_MANSPLITPKG=yes in src.conf.
60 Move standard include files to the clibs-dev package and move clang
61 internal libraries and headers to clang and clang-dev. Upgrading systems
62 installed using pkgbase past this change involves extra steps to allow
65 pkg upgrade -y FreeBSD-utilities
66 pkg upgrade -y FreeBSD-utilities-dev
70 Enable vnet sysctl variables to be loader tunable. SYSCTLs which
71 belongs to VNETs can be initialized during early boot or module
72 loading if they are marked with CTLFLAG_TUN and there are
73 corresponding kernel environment variables.
76 The WITH_INIT_ALL_PATTERN and WITH_INIT_ALL_ZERO build options have
77 been replaced by INIT_ALL=pattern and INIT_ALL=zero respectively.
83 Serial communication (in boot loaders, kernel, and userland) has
84 been changed to default to 115200 bps, in line with common industry
85 practice and typcial firmware serial console redirection
88 Note that the early x86 BIOS bootloader (i.e., boot0sio) does not
89 support rates above 9600 bps and is not changed. boot0sio users may
90 set BOOT_COMCONSOLE_SPEED=9600 to use 9600 for all of the boot
91 components, or use the standard boot0 and have the boot2 stage start
92 with the serial port at 115200.
95 Following the general removal of MIPS support, the ath(4) AHB bus-
96 frontend has been removed, too, and building of the PCI support is
97 integrated with the ath(4) main module again. As a result, there's
98 no longer a need for if_ath_pci_load="YES" in /boot/loader.conf or
99 "device ath_pci" in the kernel configuration.
102 MAXCPU has been increased to 1024 in the amd64 GENERIC kernel config.
103 Out-of-tree kernel modules will need to be rebuilt.
106 CAM has been mechanically updated s/u_int(64|32|16|8)_t/uint\1_t/g
107 to move to the standard uintXX_t types from the old, traditional
108 BSD u_intXX_t types. This should be a NOP, but may cause problems
109 for out of tree changes. The SIMs were not updated since most of
110 the old u_intXX_t uses weren't due to CAM interfaces.
113 The heuristic for detecting old chromebooks with an EC bug that requires
114 atkbdc driver workarounds has changed. There should be no functional
115 change, but if your old chromebook's keyboard stops working, please
116 file a PR and assign it to imp.
119 OpenSSL has been updated to version 3.0, including changes throughout
120 the base system. It is important to rebuild third-party software
124 To enable pf rdr rules for connections initiated from the host, pf
125 filter rules can be optionally enabled for packets delivered
126 locally. This can change the behavior of rules which match packets
127 delivered to lo0. To enable this feature:
129 sysctl net.pf.filter_local=1
132 When enabled, its best to ensure that packets delivered locally are not
133 filtered, e.g. by adding a 'skip on lo' rule.
136 Improvements to libtacplus(8) mean that tacplus.conf(5) now
137 follows POSIX shell syntax rules. This may cause TACACS+
138 authentication to fail if the shared secret contains a single
139 quote, double quote, or backslash character which isn't
140 already properly quoted or escaped.
143 Belatedly switch the default nvme block device on x86 from nvd to nda.
144 nda created nvd compatibility links by default, so this should be a
145 nop. If this causes problems for your application, set hw.nvme.use_nvd=1
146 in your loader.conf or add `options NVME_USE_NVD=1` to your kernel
147 config. To disable the nvd compatibility aliases, add
148 kern.cam.nda.nvd_compat=0 to loader.conf. The default has been nda on
149 all non-x86 platforms for some time now. If you need to fall back,
150 please email imp@freebsd.org about why.
152 Encrypted swap partitions need to be changed from nvd to nda if you
153 migrate, or you need to use the above to switch back to nvd.
156 Remove portsnap(8). Users are encouraged to obtain the ports tree
160 Add jobs.mk to save typing. Enables -j${JOB_MAX} and logging
164 make -j${JOB_MAX} buildworld > ../buildworld.log 2>&1
166 where JOB_MAX is derrived from ncpus in local.sys.mk if not set in env.
169 Video related devices for some arm devices have been renamed.
170 If you have a custom kernel config and want to use hdmi output on
171 IMX6 board you need to add "device dwc_hdmi" "device imx6_hdmi" and
172 "device imx6_ipu" to it.
173 If you have a custom kernel config and want to use hdmi output on
174 TI AM335X board you need to add "device tda19988" to it.
175 If you add "device hdmi" in it you need to remove it as it doesn't
179 Introduce new kernel options KBD_DELAY1 and KBD_DELAY2. See atkbdc(4)
183 sshd now defaults to having X11Forwarding disabled, following upstream.
184 Administrators who wish to enable X11Forwarding should add
185 `X11Forwarding yes` to /etc/ssh/sshd_config.
188 Since commit 75d41cb6967 Huawei 3G/4G LTE Mobile Devices do not default
189 to ECM, but NCM mode and need u3g and ucom modules loaded. See cdce(4).
192 As of commit 7c40e2d5f685, the dependency on netlink(4) has been added
193 to the linux_common(4) module. Users relying on linux_common may need
194 to complile netlink(4) module if it is not present in their kernel.
197 The WITHOUT_CXX option has been removed. C++ components in the base
198 system are now built unconditionally.
201 LinuxKPI pci.h changes may require out-of-tree drivers to be recompiled.
202 Bump _FreeBSD_version to 1400078 to be able to detect this change.
205 llvm-objump is now always installed as objdump. Previously there was
206 no /usr/bin/objdump unless the WITH_LLVM_BINUTILS knob was used.
208 Some LLVM objdump options have a different output format compared to
209 GNU objdump; readelf is available for inspecting ELF files, and GNU
210 objdump is available from the devel/binutils port or package.
213 dma(8) has replaced sendmail(8) as the default mta. For people willing
214 to reenable sendmail(8):
216 $ cp /usr/share/examples/sendmail/mailer.conf /etc/mail/mailer.conf
218 and add sendmail_enable="YES" to rc.conf.
221 hw.bus.disable_failed_devices has changed from 'false' to 'true' by
222 default. Now if newbus succeeds in probing a device, but fails to attach
223 the device, we'll disable the device. In the past, we'd keep retrying
224 the device on each new driver loaded. To get that behavior now, one
225 needs to use devctl to re-enable the device, and reprobe it (or set
226 the sysctl/tunable hw.bus.disable_failed_devices=false).
228 NOTE: This was reverted 20221205 due to unexpected compatibility issues
231 pf no longer accepts 'scrub fragment crop' or 'scrub fragment drop-ovl'.
232 These configurations are no longer automatically reinterpreted as
233 'scrub fragment reassemble'.
236 The WITHOUT_CLANG_IS_CC option has been removed. When Clang is enabled
237 it is always installed as /usr/bin/cc (and c++, cpp).
240 Some programs have been moved into separate packages. It is recommended
241 for pkgbase users to do:
243 pkg install FreeBSD-dhclient FreeBSD-geom FreeBSD-resolvconf \
244 FreeBSD-devd FreeBSD-devmatch
246 after upgrading to restore all the component that were previously
250 OPIE has been removed from the base system. If needed, it can
251 be installed from ports (security/opie) or packages (opie).
252 Otherwise, make sure that your PAM policies do not reference
253 pam_opie or pam_opieaccess.
256 LinuxKPI pm.h changes require an update to the latest drm-kmod version
257 before re-compiling to avoid errors.
260 The macros provided for the manipulation of CPU sets (e.g. CPU_AND)
261 have been modified to take 2 source arguments instead of only 1.
262 Externally maintained sources that use these macros will have to
263 be adapted. The FreeBSD version has been bumped to 1400046 to
267 A number of the kernel include files are able to be included by
268 themselves. A test has been added to buildworld to enforce this.
271 Remove mips as a recognized target. This starts the decommissioning of
272 mips support in FreeBSD. mips related items will be removed wholesale in
273 the coming days and weeks.
275 This broke the NO_CLEAN build for some people. Either do a clean build
277 lib/clang/include/llvm/Config/Targets.def
278 lib/clang/include/llvm/Config/AsmParsers.def
279 lib/clang/include/llvm/Config/Disassemblers.def
280 lib/clang/include/llvm/Config/AsmPrinters.def
281 before the build to force everything to rebuild that needs to.
284 Unbound support for RFC8375: The special-use domain 'home.arpa' is
285 by default blocked. To unblock it use a local-zone nodefault
286 statement in unbound.conf:
287 local-zone: "home.arpa." nodefault
289 Or use another type of local-zone to override with your choice.
291 The reason for this is discussed in Section 6.1 of RFC8375:
292 Because 'home.arpa.' is not globally scoped and cannot be secured
293 using DNSSEC based on the root domain's trust anchor, there is no way
294 to tell, using a standard DNS query, in which homenet scope an answer
295 belongs. Consequently, users may experience surprising results with
296 such names when roaming to different homenets.
299 Commit b8d60729deef changed the TCP congestion control framework so
300 that any of the included congestion control modules could be
301 the single module built into the kernel. Previously newreno
302 was automatically built in through direct reference. As of
303 this commit you are required to declare at least one congestion
304 control module (e.g. 'options CC_NEWRENO') and to also declare a
305 default using the CC_DEFAULT option (e.g. options CC_DEFAULT="newreno\").
306 The GENERIC configuration includes CC_NEWRENO and defines newreno
307 as the default. If no congestion control option is built into the
308 kernel and you are including networking, the kernel compile will
309 fail. Also if no default is declared the kernel compile will fail.
312 Mips has been removed from universe builds. It will be removed from the
316 Commit f0c9847a6c47 changed the arguments for VOP_ALLOCATE.
317 The NFS modules must be rebuilt from sources and any out
318 of tree file systems that implement their own VOP_ALLOCATE
319 may need to be modified.
322 The synchronous PPP kernel driver sppp(4) has been removed.
323 The cp(4) and ce(4) drivers are now always compiled with netgraph(4)
324 support, formerly enabled by NETGRAPH_CRONYX option.
327 sh(1) is now the default shell for the root user. To force root to use
328 the csh shell, please run the following command as root:
333 Ncurses distribution has been split between libtinfow and libncurses
334 with libncurses.so becoming a linker (ld) script to seamlessly link
335 to libtinfow as needed. Bump _FreeBSD_version to 1400035 to reflect
339 As of commit 8160a0f62be6, the dummynet module no longer depends on the
340 ipfw module. Dummynet can now be used by pf as well as ipfw. As such
341 users who relied on this dependency may need to include ipfw in the
342 list of modules to load on their systems.
345 As of commit 903873ce1560, the mixer(8) utility has got a slightly
346 new syntax. Please refer to the mixer(8) manual page for more
347 information. The old mixer utility can be installed from ports:
348 audio/freebsd-13-mixer
351 As of commit 55089ef4f8bb, the global variable nfs_maxcopyrange has
352 been deleted from the nfscommon.ko. As such, nfsd.ko must be built
353 from up to date sources to avoid an undefined reference when
357 As of commit 62ca9fc1ad56 OpenSSL no longer enables kernel TLS
358 by default. Users can enable kernel TLS via the "KTLS" SSL
359 option. This can be enabled globally by using a custom
360 OpenSSL config file via OPENSSL_CONF or via an
361 application-specific configuration option for applications
362 which permit setting SSL options via SSL_CONF_cmd(3).
365 Commit 3ad1e1c1ce20 changed the internal KAPI between the NFS
366 modules. Therefore, all need to be rebuilt from sources.
369 Commit b69019c14cd8 removes pf's DIOCGETSTATESNV ioctl.
370 As of be70c7a50d32 it is no longer used by userspace, but it does mean
371 users may not be able to enumerate pf states if they update the kernel
372 past b69019c14cd8 without first updating userspace past be70c7a50d32.
375 As of commit 01ad0c007964 if_bridge member interfaces can no longer
376 change their MTU. Changing the MTU of the bridge itself will change the
377 MTU on all member interfaces instead.
380 Commit ee29e6f31111 changed the internal KAPI between the nfscommon
381 and nfsd modules. Therefore, both need to be rebuilt from sources.
382 Bump __FreeBSD_version to 1400026 for this KAPI change.
385 The 20210707 awk update brought in a change in behavior. This has
386 been corrected as of d4d252c49976. Between these dates, if you
387 installed a new awk binary, you may not be able to build a new
388 kernel because the change in behavior affected the genoffset
389 script used to build the kernel. If you did update, the fix is
390 to update your sources past the above hash and do
393 % sudo -E make install
394 to enable building kernels again.
397 Commit 1e0a518d6548 changed the internal KAPI between the NFS
398 modules. They all need to be rebuilt from sources. I did not
399 bump __FreeBSD_version, since it was bumped recently.
402 awk has been updated to the latest one-true-awk version 20210215.
403 This contains a number of minor bug fixes.
406 The NFSv4 client now uses the highest minor version of NFSv4
407 supported by the NFSv4 server by default instead of minor version 0,
409 The "minorversion" mount option may be used to override this default.
412 Bump __FreeBSD_version to 1400024 for LinuxKPI changes.
413 Most notably netdev.h can change now as the (last) dependencies
414 (mlx4/ofed) are now using struct ifnet directly, but also for PCI
415 additions and others.
418 The directory "blacklisted" under /usr/share/certs/ has been
419 renamed to "untrusted".
422 svnlite has been removed from base. Should you need svn for any reason
423 please install the svn package or port.
426 Commit e1a907a25cfa changed the internal KAPI between the krpc
427 and nfsserver. As such, both modules must be rebuilt from
428 sources. Bump __FreeBSD_version to 1400022.
431 The an(4) driver has been removed from FreeBSD.
434 The vendor/openzfs branch was renamed to vendor/openzfs/legacy to
435 start tracking OpenZFS upstream more closely. Please see
436 https://lists.freebsd.org/archives/freebsd-current/2021-June/000153.html
437 for details on how to correct any errors that might result. The
438 short version is that you need to remove the old branch locally:
439 git update-ref -d refs/remotes/freebsd/vendor/openzfs
440 (assuming your upstream origin is named 'freebsd').
443 Commits 17accc08ae15 and de102f870501 add new files to LinuxKPI
444 which break drm-kmod. In addition various other additions where
445 committed. Bump __FreeBSD_version to 1400015 to be able to
449 Commit ca179c4d74f2 changed the package in which the OpenSSL
450 libraries and utilities are packaged.
451 It is recommended for pkgbase user to do:
452 pkg install -f FreeBSD-openssl
453 before pkg upgrade otherwise some dependencies might not be met
454 and pkg will stop working as libssl will not be present anymore
458 Commit 875977314881 changed the internal KAPI between
459 the nfsd and nfscommon modules. As such these modules
460 need to be rebuilt from sources.
461 Without this patch in your NFSv4.1/4.2 server, enabling
462 delegations by setting vfs.nfsd.issue_delegations non-zero
466 Commit 7763814fc9c2 changed the internal KAPI between
467 the krpc and NFS. As such, the krpc, nfscommon and
468 nfscl modules must all be rebuilt from sources.
469 Without this patch, NFSv4.1/4.2 mounts should not
470 be done with the nfscbd(8) daemon running, to avoid
471 needing a working back channel for server->client RPCs.
474 Commit 01ae8969a9ee fixed the NFSv4.1/4.2 server so that it
475 handles binding of the back channel as required by RFC5661.
476 Until this patch is in your server, avoid use of the "nconnects"
477 mount option for Linux NFSv4.1/4.2 mounts.
480 For 64-bit architectures the base system is now built with Position
481 Independent Executable (PIE) support enabled by default. It may be
482 disabled using the WITHOUT_PIE knob. A clean build is required.
485 Various LinuxKPI functionality was added which conflicts with DRM.
486 Please update your drm-kmod port to after the __FreeBSD_version 1400003
490 PC Card attachments for all devices have been removed. In the case of
491 wi and cmx, the entire drivers were removed because they were only
492 PC Card devices. FreeBSD_version 1300134 should be used for this
493 since it was bumped so recently.
496 Transport-independent parts of HID support have been split off the USB
497 code in to separate subsystem. Kernel configs which include one of
498 ums, ukbd, uhid, atp, wsp, wmt, uaudio, ugold or ucycom drivers should
499 be updated with adding of "device hid" line.
502 ncurses installation has been modified to only keep the widechar
503 enabled version. Incremental build is broken for that change, so it
504 requires a clean build.
507 The FreeBSD project has migrated from Subversion to Git. Temporary
508 instructions can be found at
509 https://github.com/bsdimp/freebsd-git-docs/blob/main/src-cvt.md
510 and other documents in that repo.
513 The services database has been updated to cover more of the basic
514 services expected in a modern system. The database is big enough
515 that it will cause issues in mergemaster in Releases previous to
516 12.2 and 11.3, or in very old current systems from before r358154.
519 Obsolete in-tree GDB 6.1.1 has been removed. GDB (including kgdb)
520 may be installed from ports or packages.
523 ping6 has been merged into ping. It can now be called as "ping -6".
524 See ping(8) for details.
527 Default value of net.add_addr_allfibs has been changed to 0.
528 If you have multi-fib configuration and rely on existence of all
529 interface routes in every fib, you need to set the above sysctl to 1.
532 The internal pre-processor in the calendar(1) program has been
533 extended to support more C pre-processor commands (e.g. #ifdef, #else,
534 and #undef) and to detect unbalanced conditional statements.
535 Error messages have been extended to include the filename and line
536 number if processing stops to help fixing malformed data files.
539 All the data files for the calendar(1) program, except calendar.freebsd,
540 have been moved to the deskutils/calendar-data port, much like the
541 jewish calendar entries were moved to deskutils/hebcal years ago. After
542 make delete-old-files, you need to install it to retain full
543 functionality. calendar(1) will issue a reminder for files it can't
547 LINT files are no longer generated. We now include the relevant NOTES
548 files. Note: This may cause conflicts with updating in some cases.
549 find sys -name LINT\* -delete
550 is suggested across this commit to remove the generated LINT files.
552 If you have tried to update with generated files there, the svn
553 command you want to un-auger the tree is
556 and then do the above find from the top level. Substitute 'amd64'
557 above with where the error message indicates a conflict.
560 OpenZFS support has been integrated. Do not upgrade root pools until
561 the loader is updated to support zstd. Furthermore, we caution against
562 'zpool upgrade' for the next few weeks. The change should be transparent
563 unless you want to use new features.
565 Not all "NO_CLEAN" build scenarios work across these changes. Many
566 scenarios have been tested and fixed, but rebuilding kernels without
567 rebuilding world may fail.
569 The ZFS cache file has moved from /boot to /etc to match the OpenZFS
570 upstream default. A fallback to /boot has been added for mountroot.
572 Pool auto import behavior at boot has been moved from the kernel module
573 to an explicit "zpool import -a" in one of the rc scripts enabled by
574 zfs_enable=YES. This means your non-root zpools won't auto import until
575 you upgrade your /etc/rc.d files.
578 The resume code now notifies devd with the 'kernel' system
579 rather than the old 'kern' subsystem to be consistent with
580 other use. The old notification will be created as well, but
581 will be removed prior to FreeBSD 14.0.
584 r362275 changed the internal API between the kernel RPC and the
585 NFS modules. As such, all the modules must be recompiled from
589 r364330 modified the internal API used between the NFS modules.
590 As such, all the NFS modules must be re-compiled from sources.
593 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
594 been upgraded to 11.0.0. Please see the 20141231 entry below for
595 information about prerequisites and upgrading, if you are not already
596 using clang 3.5.0 or higher.
599 r364092 modified the internal ABI used between the kernel NFS
600 modules. As such, all of these modules need to be rebuilt
601 from sources, so a version bump was done.
604 Makefile.inc has been updated to work around the issue documented in
605 20200729. It was a case where the optimization of using symbolic links
606 to point to binaries created a situation where we'd run new binaries
607 with old libraries starting midway through the installworld process.
610 r363679 has redefined some undefined behavior in regcomp(3); notably,
611 extraneous escapes of most ordinary characters will no longer be
612 accepted. An exp-run has identified all of the problems with this in
613 ports, but other non-ports software may need extra escapes removed to
614 continue to function.
616 Because of this change, installworld may encounter the following error
617 from rtld: Undefined symbol "regcomp@FBSD_1.6" -- It is imperative that
618 you do not halt installworld. Instead, let it run to completion (whether
619 successful or not) and run installworld once more.
622 A new implementation of bc and dc has been imported in r362681. This
623 implementation corrects non-conformant behavior of the previous bc
624 and adds GNU bc compatible options. It offers a number of extensions,
625 is much faster on large values, and has support for message catalogs
626 (a number of languages are already supported, contributions of further
627 languages welcome). The option WITHOUT_GH_BC can be used to build the
628 world with the previous versions of bc and dc.
631 r362639 changed the internal API used between the NFS kernel modules.
632 As such, they all need to be rebuilt from sources.
635 r362158 changed the arguments for VFS_CHECKEXP(). As such, any
636 out of tree file systems need to be modified and rebuilt.
637 Also, any file systems that are modules must be rebuilt.
640 read(2) of a directory fd is now rejected by default. root may
641 re-enable it for system root only on non-ZFS filesystems with the
642 security.bsd.allow_read_dir sysctl(8) MIB if
643 security.bsd.suser_enabled=1.
645 It may be advised to setup aliases for grep to default to `-d skip` if
646 commonly non-recursively grepping a list that includes directories and
647 the potential for the resulting stderr output is not tolerable. Example
648 aliases are now installed, commented out, in /root/.cshrc and
652 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
653 been upgraded to 10.0.1. Please see the 20141231 entry below for
654 information about prerequisites and upgrading, if you are not already
655 using clang 3.5.0 or higher.
658 Support for obsolete compilers has been removed from the build system.
659 Clang 6 and GCC 6.4 are the minimum supported versions.
662 closefrom(2) has been moved under COMPAT12, and replaced in libc with a
663 stub that calls close_range(2). If using a custom kernel configuration,
664 you may want to ensure that the COMPAT_FREEBSD12 option is included, as
665 a slightly older -CURRENT userland and older FreeBSD userlands may not
666 be functional without closefrom(2).
669 Upstream DTS from Linux 5.6 was merged and they now have the SID
670 and THS (Secure ID controller and THermal Sensor) node present.
671 The DTB overlays have now been removed from the tree for the H3/H5 and
672 A64 SoCs and the aw_sid and aw_thermal driver have been updated to
673 deal with upstream DTS. If you are using those overlays you need to
674 remove them from loader.conf and update the DTBs on the FAT partition.
677 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
678 been upgraded to 10.0.0. Please see the 20141231 entry below for
679 information about prerequisites and upgrading, if you are not already
680 using clang 3.5.0 or higher.
683 The amd(8) automount daemon has been removed from the source tree.
684 As of FreeBSD 10.1 autofs(5) is the preferred tool for automounting.
685 amd is still available in the sysutils/am-utils port.
688 Removed brooktree driver (bktr.4) from the tree.
691 The WITH_GPL_DTC option has been removed. The BSD-licenced device tree
692 compiler in usr.bin/dtc is used on all architectures which use dtc, and
693 the GPL dtc is available (if needed) from the sysutils/dtc port.
696 The WITHOUT_LLVM_LIBUNWIND option has been removed. LLVM's libunwind
697 is used by all supported CPU architectures.
700 GCC 4.2.1 has been removed from the tree. The WITH_GCC,
701 WITH_GCC_BOOTSTRAP, and WITH_GNUCXX options are no longer available.
702 Users who wish to build FreeBSD with GCC must use the external toolchain
706 ncurses has been updated to a newer version (6.2-20200215). Given the ABI
707 has changed, users will have to rebuild all the ports that are linked to
711 The size of struct vnet and the magic cookie have changed.
712 Users need to recompile libkvm and all modules using VIMAGE
713 together with their new kernel.
716 Defining the long deprecated NO_CTF, NO_DEBUG_FILES, NO_INSTALLLIB,
717 NO_MAN, NO_PROFILE, and NO_WARNS variables is now an error. Update
718 your Makefiles and scripts to define MK_<var>=no instead as required.
720 One exception to this is that program or library Makefiles should
721 define MAN to empty rather than setting MK_MAN=no.
724 Clang/LLVM is now the default compiler and LLD the default
728 make universe no longer uses GCC 4.2.1 on any architectures.
729 Architectures not supported by in-tree Clang/LLVM require an
730 external toolchain package.
733 GCC 4.2.1 is now not built by default, as part of the GCC 4.2.1
734 retirement plan. Specifically, the GCC, GCC_BOOTSTRAP, and GNUCXX
735 options default to off for all supported CPU architectures. As a
736 short-term transition aid they may be enabled via WITH_* options.
737 GCC 4.2.1 is expected to be removed from the tree on 2020-03-31.
740 Support for armv5 has been disconnected and is being removed. The
741 machine combination MACHINE=arm MACHINE_ARCH=arm is no longer valid.
742 You must now use a MACHINE_ARCH of armv6 or armv7. The default
743 MACHINE_ARCH for MACHINE=arm is now armv7.
746 Clang/LLVM is now the default compiler for all powerpc architectures.
747 LLD is now the default linker for powerpc64. The change for powerpc64
748 also includes a change to the ELFv2 ABI, incompatible with the existing
752 Kernel-loadable random(4) modules are no longer unloadable.
755 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
756 been upgraded to 9.0.1. Please see the 20141231 entry below for
757 information about prerequisites and upgrading, if you are not already
758 using clang 3.5.0 or higher.
761 r355677 has modified the internal interface used between the
762 NFS modules in the kernel. As such, they must all be upgraded
763 simultaneously. I will do a version bump for this.
766 The root certificates of the Mozilla CA Certificate Store have been
767 imported into the base system and can be managed with the certctl(8)
768 utility. If you have installed the security/ca_root_nss port or package
769 with the ETCSYMLINK option (the default), be advised that there may be
770 differences between those included in the port and those included in
771 base due to differences in nss branch used as well as general update
772 frequency. Note also that certctl(8) cannot manage certs in the
773 format used by the security/ca_root_nss port.
776 The amd(8) automount daemon has been disabled by default, and will be
777 removed in the future. As of FreeBSD 10.1 the autofs(5) is available
781 The nctgpio and wbwd drivers have been moved to the superio bus.
782 If you have one of these drivers in a kernel configuration, then
783 you should add device superio to it. If you use one of these drivers
784 as a module and you compile a custom set of modules, then you should
785 add superio to the set.
788 KPIs for network drivers to access interface addresses have changed.
789 Users need to recompile NIC driver modules together with kernel.
792 The net.link.tap.user_open sysctl no longer prevents user opening of
793 already created /dev/tapNN devices. Access is still controlled by
794 node permissions, just like tun devices. The net.link.tap.user_open
795 sysctl is now used only to allow users to perform devfs cloning of
796 tap devices, and the subsequent open may not succeed if the user is not
797 in the appropriate group. This sysctl may be deprecated/removed
798 completely in the future.
801 mips, powerpc, and sparc64 are no longer built as part of
802 universe / tinderbox unless MAKE_OBSOLETE_GCC is defined. If
803 not defined, mips, powerpc, and sparc64 builds will look for
804 the xtoolchain binaries and if installed use them for universe
805 builds. As llvm 9.0 becomes vetted for these architectures, they
806 will be removed from the list.
809 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
810 been upgraded to 9.0.0. Please see the 20141231 entry below for
811 information about prerequisites and upgrading, if you are not already
812 using clang 3.5.0 or higher.
815 The hpt27xx, hptmv, hptnr, and hptrr drivers have been removed from
816 GENERIC. They are available as modules and can be loaded by adding
817 to /boot/loader.conf hpt27xx_load="YES", hptmv_load="YES",
818 hptnr_load="YES", or hptrr_load="YES", respectively.
821 ntpd no longer by default locks its pages in memory, allowing them
822 to be paged out by the kernel. Use rlimit memlock to restore
823 historic BSD behaviour. For example, add "rlimit memlock 32"
824 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
827 Several of ping6's options have been renamed for better consistency
828 with ping. If you use any of -ARWXaghmrtwx, you must update your
829 scripts. See ping6(8) for details.
832 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
833 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
834 been removed from mount_fusefs(8). You can safely remove them from
835 your scripts, because they had no effect.
837 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
838 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
839 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
840 sysctls have been removed. If you felt the need to set any of them to
841 a non-default value, please tell asomers@FreeBSD.org why.
844 Default permissions on the /var/account/acct file (and copies of it
845 rotated by periodic daily scripts) are changed from 0644 to 0640
846 because the file contains sensitive information that should not be
847 world-readable. If the /var/account directory must be created by
848 rc.d/accounting, the mode used is now 0750. Admins who use the
849 accounting feature are encouraged to change the mode of an existing
850 /var/account directory to 0750 or 0700.
853 Entropy collection and the /dev/random device are no longer optional
854 components. The "device random" option has been removed.
855 Implementations of distilling algorithms can still be made loadable
856 with "options RANDOM_LOADABLE" (e.g., random_fortuna.ko).
859 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
860 been upgraded to 8.0.1. Please see the 20141231 entry below for
861 information about prerequisites and upgrading, if you are not already
862 using clang 3.5.0 or higher.
865 A fix was applied to i386 kernel modules to avoid panics with
866 dpcpu or vnet. Users need to recompile i386 kernel modules
867 having pcpu or vnet sections or they will refuse to load.
870 User-wired pages now have their own counter,
871 vm.stats.vm.v_user_wire_count. The vm.max_wired sysctl was renamed
872 to vm.max_user_wired and changed from an unsigned int to an unsigned
873 long. bhyve VMs wired with the -S are now subject to the user
874 wiring limit; the vm.max_user_wired sysctl may need to be tuned to
875 avoid running into the limit.
878 The IPSEC option has been removed from GENERIC. Users requiring
879 ipsec(4) must now load the ipsec(4) kernel module.
882 The tap(4) driver has been folded into tun(4), and the module has been
883 renamed to tuntap. You should update any kld_list="if_tap" or
884 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
885 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
886 module instead, and "device tap" or "device tun" entries in kernel
887 config files to select the tuntap device instead.
890 The following knobs have been added related to tradeoffs between
891 safe use of the random device and availability in the absence of
894 kern.random.initial_seeding.bypass_before_seeding: tunable; set
895 non-zero to bypass the random device prior to seeding, or zero to
896 block random requests until the random device is initially seeded.
897 For now, set to 1 (unsafe) by default to restore pre-r346250 boot
898 availability properties.
900 kern.random.initial_seeding.read_random_bypassed_before_seeding:
901 read-only diagnostic sysctl that is set when bypass is enabled and
902 read_random(9) is bypassed, to enable programmatic handling of this
903 initial condition, if desired.
905 kern.random.initial_seeding.arc4random_bypassed_before_seeding:
906 Similar to the above, but for arc4random(9) initial seeding.
908 kern.random.initial_seeding.disable_bypass_warnings: tunable; set
909 non-zero to disable warnings in dmesg when the same conditions are
910 met as for the diagnostic sysctls above. Defaults to zero, i.e.,
911 produce warnings in dmesg when the conditions are met.
914 The loadable random module KPI has changed; the random_infra_init()
915 routine now requires a 3rd function pointer for a bool (*)(void)
916 method that returns true if the random device is seeded (and
917 therefore unblocked).
920 r345895 reverts r320698. This implies that an nfsuserd(8) daemon
921 built from head sources between r320757 (July 6, 2017) and
922 r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
923 is added to the command line.
924 nfsuserd daemons built from head sources that are post-r338192 are
925 not affected and should continue to work.
928 The fuse(4) module has been renamed to fusefs(4) for consistency with
929 other filesystems. You should update any kld_load="fuse" entries in
930 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
931 "options FUSE" entries in kernel config files.
934 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
935 8.0.0. Please see the 20141231 entry below for information about
936 prerequisites and upgrading, if you are not already using clang 3.5.0
940 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
941 compiled into your custom kernel, add 'device xz' statement to the
945 drm and drm2 have been removed from the tree. Please see
946 https://wiki.freebsd.org/Graphics for the latest information on
947 migrating to the drm ports.
950 Iflib is no longer unconditionally compiled into the kernel. Drivers
951 using iflib and statically compiled into the kernel, now require
952 the 'device iflib' config option. For the same drivers loaded as
953 modules on kernels not having 'device iflib', the iflib.ko module
954 is loaded automatically.
957 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
958 options no longer exist since r343219 and r343427 respectively;
959 nothing uses them, so they should be just removed from custom
963 r342635 changes the way efibootmgr(8) works by requiring users to add
964 the -b (bootnum) parameter for commands where the bootnum was previously
965 specified with each option. For example 'efibootmgr -B 0001' is now
966 'efibootmgr -B -b 0001'.
969 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
970 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
971 servers that have vfs.nfsd.nfs_privport set will only allow mounts
972 from clients using a reserved port. Since both the FreeBSD and Linux
973 NFSv4 clients use reserved ports by default, this should not affect
977 The XLP config has been removed. We can't support 64-bit atomics in this
978 kernel because it is running in 32-bit mode. XLP users must transition
979 to running a 64-bit kernel (XLP64 or XLPN32).
981 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
982 the preferred emulator today and we don't need two different ones.
984 The old sibyte / swarm / Broadcom BCM1250 support has been
985 removed from the mips port.
988 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
989 7.0.1. Please see the 20141231 entry below for information about
990 prerequisites and upgrading, if you are not already using clang 3.5.0
994 Remove the timed and netdate programs from the base tree. Setting
995 the time with these daemons has been obsolete for over a decade.
998 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
999 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
1000 it produces broken binaries when ifuncs are in use. Users needing
1001 GNU ld should install the binutils port or package.
1004 The BSD crtbegin and crtend code has been enabled by default. It has
1005 had extensive testing on amd64, arm64, and i386. It can be disabled
1006 by building a world with -DWITHOUT_BSD_CRTBEGIN.
1009 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
1010 has been converted to a port (misc/ctm) and will be removed from
1011 FreeBSD-13. It is available as a package (ctm) for all supported
1015 The default newsyslog.conf(5) file has been changed to only include
1016 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
1017 the filenames end in '.conf' and do not begin with a '.'.
1019 You should check the configuration files in these two directories match
1020 this naming convention. You can verify which configuration files are
1021 being included using the command:
1025 Ports for the DRM modules have been simplified. Now, amd64 users should
1026 just install the drm-kmod port. All others should install
1029 Graphics hardware that's newer than about 2010 usually works with
1030 drm-kmod. For hardware older than 2013, however, some users will need
1031 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
1032 than 2008 usually only works in drm-legacy-kmod. The graphics team can
1033 only commit to hardware made since 2013 due to the complexity of the
1034 market and difficulty to test all the older cards effectively. If you
1035 have hardware supported by drm-kmod, you are strongly encouraged to use
1036 that as you will get better support.
1038 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
1039 elsewhere, the drm and drm2 modules will be eliminated from the src base
1040 soon (with a limited exception for arm). Please update to the package
1041 asap and report any issues to x11@freebsd.org.
1043 Generally, anybody using the drm*-kmod packages should add
1044 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
1045 cross-threading surprises, especially with automatic driver
1046 loading from X11 startup. These will become the defaults in 13-current
1050 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
1051 custom kernel and module loading configuration files must be updated
1052 accordingly. Moreover, interfaces previous presented as ixlvN to the
1053 system are now exposed as iavfN and network configuration files must
1054 be adjusted as necessary.
1057 OpenSSL has been updated to version 1.1.1. This update included
1058 additional various API changes throughout the base system. It is
1059 important to rebuild third-party software after upgrading. The value
1060 of __FreeBSD_version has been bumped accordingly.
1063 The legacy DRM modules and drivers have now been added to the loader's
1064 module blacklist, in favor of loading them with kld_list in rc.conf(5).
1065 The module blacklist may be overridden with the loader.conf(5)
1066 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
1070 The cam(4) based nda(4) driver will be used over nvd(4) by default on
1071 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
1072 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
1073 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
1077 Reproducible build mode is now on by default, in preparation for
1078 FreeBSD 12.0. This eliminates build metadata such as the user,
1079 host, and time from the kernel (and uname), unless the working tree
1080 corresponds to a modified checkout from a version control system.
1081 The previous behavior can be obtained by setting the /etc/src.conf
1082 knob WITHOUT_REPRODUCIBLE_BUILD.
1085 The Yarrow CSPRNG has been removed from the kernel as it has not been
1086 supported by its designers since at least 2003. Fortuna has been the
1087 default since FreeBSD-11.
1090 devctl freeze/thaw have gone into the tree, the rc scripts have been
1091 updated to use them and devmatch has been changed. You should update
1092 kernel, userland and rc scripts all at the same time.
1095 The default interpreter has been switched from 4th to Lua.
1096 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
1097 interpreter. If you have custom FORTH code you will need to set
1098 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
1099 src.conf for the build. This will create default hard links between
1100 loader and loader_4th instead of loader and loader_lua, the new default.
1101 If you are using UEFI it will create the proper hard link to loader.efi.
1103 bhyve uses userboot.so. It remains 4th-only until some issues are solved
1104 regarding coexisting with multiple versions of FreeBSD are resolved.
1107 ls(1) now respects the COLORTERM environment variable used in other
1108 systems and software to indicate that a colored terminal is both
1109 supported and desired. If ls(1) is suddenly emitting colors, they may
1110 be disabled again by either removing the unwanted COLORTERM from your
1111 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
1112 may not be observed in a future release.
1115 The default pager for most commands has been changed to "less". To
1116 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
1120 The jedec_ts(4) driver has been removed. A superset of its functionality
1121 is available in the jedec_dimm(4) driver, and the manpage for that
1122 driver includes migration instructions. If you have "device jedec_ts"
1123 in your kernel configuration file, it must be removed.
1126 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
1127 This should have no effect if the kernel is booted via BIOS/legacy boot.
1128 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
1129 has a buggy firmware that prevents a successful boot due to use of
1133 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
1134 support has been removed from the tree. These ports were
1135 obsolete and/or known to be broken for many years.
1138 loader.efi has been augmented to participate more fully in the
1139 UEFI boot manager protocol. loader.efi will now look at the
1140 BootXXXX environment variable to determine if a specific kernel
1141 or root partition was specified. XXXX is derived from BootCurrent.
1142 efibootmgr(8) manages these standard UEFI variables.
1145 zfsloader's functionality has now been folded into loader.
1146 zfsloader is no longer necessary once you've updated your
1147 boot blocks. For a transition period, we will install a
1148 hardlink for zfsloader to loader to allow a smooth transition
1149 until the boot blocks can be updated (hard link because old
1150 zfs boot blocks don't understand symlinks).
1153 ARM64 now have efifb support, if you want to have serial console
1154 on your arm64 board when an screen is connected and the bootloader
1155 setup a frame buffer for us to use, just add :
1158 in /boot/loader.conf
1159 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
1160 an screen connected as the firmware will setup a frame buffer are that
1161 u-boot will expose as an EFI frame buffer.
1164 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
1165 or take steps to update /etc/passwd before doing installworld on
1166 existing systems. Do not skip the "mergemaster -Fp" step before
1167 installworld, as described in the update procedures near the bottom
1168 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
1169 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
1170 the ntp config file contain options that change file/dir locations.
1171 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
1172 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
1173 taking steps to ensure that all required files/dirs are accessible
1177 Big endian arm support has been removed.
1180 The static environment setup in kernel configs is no longer mutually
1181 exclusive with the loader(8) environment by default. In order to
1182 restore the previous default behavior of disabling the loader(8)
1183 environment if a static environment is present, you must specify
1184 loader_env.disabled=1 in the static environment.
1187 The ABI of syscalls used by management tools like sockstat and
1188 netstat has been broken to allow 32-bit binaries to work on
1189 64-bit kernels without modification. These programs will need
1190 to match the kernel in order to function. External programs may
1191 require minor modifications to accommodate a change of type in
1192 structures from pointers to 64-bit virtual addresses.
1195 On i386 and amd64 atomics are now inlined. Out of tree modules using
1196 atomics will need to be rebuilt.
1199 The '%I' format in the kern.corefile sysctl limits the number of
1200 core files that a process can generate to the number stored in the
1201 debug.ncores sysctl. The '%I' format is replaced by the single digit
1202 index. Previously, if all indexes were taken the kernel would overwrite
1203 only a core file with the highest index in a filename.
1204 Currently the system will create a new core file if there is a free
1205 index or if all slots are taken it will overwrite the oldest one.
1208 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
1209 6.0.1. Please see the 20141231 entry below for information about
1210 prerequisites and upgrading, if you are not already using clang 3.5.0
1214 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
1215 needed to be changed to work with it. This change was made with r335763
1216 and requires a mergemaster / etcupdate / etc to update the installed
1220 r334930 changed the interface between the NFS modules, so they all
1221 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
1224 As of r334391 lld is the default amd64 system linker; it is installed
1225 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
1229 The kernel / userland interface for devinfo changed, so you'll
1230 need a new kernel and userland as a pair for it to work (rebuilding
1231 lib/libdevinfo is all that's required). devinfo and devmatch will
1232 not work, but everything else will when there's a mismatch.
1235 The on-disk format for hwpmc callchain records has changed to include
1236 threadid corresponding to a given record. This changes the field offsets
1237 and thus requires that libpmcstat be rebuilt before using a kernel
1241 The vxge(4) driver has been removed. This driver was introduced into
1242 HEAD one week before the Exar left the Ethernet market and is not
1243 known to be used. If you have device vxge in your kernel config file
1247 The amd64 kernel now requires a ld that supports ifunc to produce a
1248 working kernel, either lld or a newer binutils. lld is built by default
1249 on amd64, and the 'buildkernel' target uses it automatically. However,
1250 it is not the default linker, so building the kernel the traditional
1251 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
1252 binutils port/package). lld will soon be default, and this requirement
1255 NOTE: As of r334391 lld is the default system linker on amd64, and no
1256 workaround is necessary.
1259 The nxge(4) driver has been removed. This driver was for PCI-X 10g
1260 cards made by s2io/Neterion. The company was acquired by Exar and
1261 no longer sells or supports Ethernet products. If you have device
1262 nxge in your kernel config file it must be removed.
1265 The tz database (tzdb) has been updated to 2018e. This version more
1266 correctly models time stamps in time zones with negative DST such as
1267 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
1268 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
1269 time zone abbreviations and the tm_isdst flag.
1272 The ixgb(4) driver has been removed. This driver was for an early and
1273 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
1274 quickly shifted to the long lived ixgbe family. If you have device
1275 ixgb in your kernel config file it must be removed.
1278 The lmc(4) driver has been removed. This was a WAN interface
1279 card that was already reportedly rare in 2003, and had an ambiguous
1280 license. If you have device lmc in your kernel config file it must
1284 Support for Arcnet networks has been removed. If you have device
1285 arcnet or device cm in your kernel config file they must be
1289 Support for FDDI networks has been removed. If you have device
1290 fddi or device fpa in your kernel config file they must be
1294 In addition to supporting RFC 3164 formatted messages, the
1295 syslogd(8) service is now capable of parsing RFC 5424 formatted
1296 log messages. The main benefit of using RFC 5424 is that clients
1297 may now send log messages with timestamps containing year numbers,
1298 microseconds and time zone offsets.
1300 Similarly, the syslog(3) C library function has been altered to
1301 send RFC 5424 formatted messages to the local system logging
1302 daemon. On systems using syslogd(8), this change should have no
1303 negative impact, as long as syslogd(8) and the C library are
1304 updated at the same time. On systems using a different system
1305 logging daemon, it may be necessary to make configuration
1306 adjustments, depending on the software used.
1308 When using syslog-ng, add the 'syslog-protocol' flag to local
1309 input sources to enable parsing of RFC 5424 formatted messages:
1312 unix-dgram("/var/run/log" flags(syslog-protocol));
1315 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
1316 of the 'imuxsock' module to let messages be processed by the
1317 regular RFC 3164/5424 parsing pipeline:
1319 module(load="imuxsock" SysSock.UseSpecialParser="off")
1321 Do note that these changes only affect communication between local
1322 applications and syslogd(8). The format that syslogd(8) uses to
1323 store messages on disk or forward messages to other systems
1324 remains unchanged. syslogd(8) still uses RFC 3164 for these
1325 purposes. Options to customize this behaviour will be added in the
1326 future. Utilities that process log files stored in /var/log are
1327 thus expected to continue to function as before.
1329 __FreeBSD_version has been incremented to 1200061 to denote this
1333 Support for token ring networks has been removed. If you
1334 have "device token" in your kernel config you should remove
1335 it. No device drivers supported token ring.
1338 makefs was modified to be able to tag ISO9660 El Torito boot catalog
1339 entries as EFI instead of overloading the i386 tag as done previously.
1340 The amd64 mkisoimages.sh script used to build amd64 ISO images for
1341 release was updated to use this. This may mean that makefs must be
1342 updated before "make cdrom" can be run in the release directory. This
1343 should be as simple as:
1345 $ cd $SRCDIR/usr.sbin/makefs
1346 $ make depend all install
1349 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
1350 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
1351 Co-existence for the transition period will come shortly. Booting is a
1352 complex environment and test coverage for Lua-enabled loaders has been
1353 thin, so it would be prudent to assume it might not work and make
1354 provisions for backup boot methods.
1357 devmatch functionality has been turned on in devd. It will automatically
1358 load drivers for unattached devices. This may cause unexpected drivers
1359 to be loaded. Please report any problems to current@ and
1363 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
1364 6.0.0. Please see the 20141231 entry below for information about
1365 prerequisites and upgrading, if you are not already using clang 3.5.0
1369 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
1370 This means it is used to link the kernel and userland libraries and
1371 executables, but is not yet installed as /usr/bin/ld by default.
1373 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
1374 WITHOUT_LLD_BOOTSTRAP=yes
1377 On i386, pmtimer has been removed. Its functionality has been folded
1378 into apm. It was a no-op on ACPI in current for a while now (but was
1379 still needed on i386 in FreeBSD 11 and earlier). Users may need to
1380 remove it from kernel config files.
1383 The use of RSS hash from the network card aka flowid has been
1384 disabled by default for lagg(4) as it's currently incompatible with
1385 the lacp and loadbalance protocols.
1387 This can be re-enabled by setting the following in loader.conf:
1388 net.link.lagg.default_use_flowid="1"
1391 The SW_WATCHDOG option is no longer necessary to enable the
1392 hardclock-based software watchdog if no hardware watchdog is
1393 configured. As before, SW_WATCHDOG will cause the software
1394 watchdog to be enabled even if a hardware watchdog is configured.
1397 r326887 fixes the issue described in the 20171214 UPDATING entry.
1398 r326888 flips the switch back to building GELI support always.
1401 r362593 broke ZFS + GELI support for reasons unknown. However,
1402 it also broke ZFS support generally, so GELI has been turned off
1403 by default as the lesser evil in r326857. If you boot off ZFS and/or
1404 GELI, it might not be a good time to update.
1407 PowerPC users must update loader(8) by rebuilding world before
1408 installing a new kernel, as the protocol connecting them has
1409 changed. Without the update, loader metadata will not be passed
1410 successfully to the kernel and users will have to enter their
1411 root partition at the kernel mountroot prompt to continue booting.
1412 Newer versions of loader can boot old kernels without issue.
1415 The LOADER_FIREWIRE_SUPPORT build variable has been renamed to
1416 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
1417 to WITH/OUT_LOADER_GELI.
1420 The naive and non-compliant support of posix_fallocate(2) in ZFS
1421 has been removed as of r325320. The system call now returns EINVAL
1422 when used on a ZFS file. Although the new behavior complies with the
1423 standard, some consumers are not prepared to cope with it.
1424 One known victim is lld prior to r325420.
1427 Building in a FreeBSD src checkout will automatically create object
1428 directories now rather than store files in the current directory if
1429 'make obj' was not ran. Calling 'make obj' is no longer necessary.
1430 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
1431 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
1435 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
1436 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
1437 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
1438 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
1439 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
1440 The UNIFIED_OBJDIR option is a transitional feature that will be
1441 removed for 12.0 release; please migrate to the new format for any
1442 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
1443 than hardcoding paths.
1446 The native-xtools target no longer installs the files by default to the
1447 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
1448 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
1451 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
1452 options are changing from controlling the build if defined / undefined
1453 to controlling the build with explicit 'yes' or 'no' values. They will
1454 shift to WITH/WITHOUT options to match other options in the system.
1457 libstand has turned into a private library for sys/boot use only.
1458 It is no longer supported as a public interface outside of sys/boot.
1461 The arm port has split armv6 into armv6 and armv7. armv7 is now
1462 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
1463 and are running a kernel from before r324363, you will need to add
1464 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
1467 When building multiple kernels using KERNCONF, non-existent KERNCONF
1468 files will produce an error and buildkernel will fail. Previously
1469 missing KERNCONF files silently failed giving no indication as to
1470 why, only to subsequently discover during installkernel that the
1471 desired kernel was never built in the first place.
1474 The default serial number format for CTL LUNs has changed. This will
1475 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
1476 or iSCSI clients care about their LUNs' serial numbers. Users who
1477 require serial number stability should hardcode serial numbers in
1481 For 32-bit arm compiled for hard-float support, soft-floating point
1482 binaries now always get their shared libraries from
1483 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
1484 /usr/libsoft also existed). Only users with a hard-float ld.so, but
1485 soft-float everything else should be affected.
1488 The geli password typed at boot is now hidden. To restore the previous
1489 behavior, see geli(8) for configuration options.
1492 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
1493 sysctl values. Minor nit, but requires a rebuild of both world/kernel
1497 "make check" behavior (made in ^/head@r295380) has been changed to
1498 execute from a limited sandbox, as opposed to executing from
1502 - The "beforecheck" and "aftercheck" targets are now specified.
1503 - ${CHECKDIR} (added in commit noted above) has been removed.
1504 - Legacy behavior can be enabled by setting
1505 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
1507 If the limited sandbox mode is enabled, "make check" will execute
1508 "make distribution", then install, execute the tests, and clean up the
1509 sandbox if successful.
1511 The "make distribution" and "make install" targets are typically run as
1512 root to set appropriate permissions and ownership at installation time.
1513 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
1514 environment if executing "make check" with limited sandbox mode using
1515 an unprivileged user.
1518 Since the switch to GPT disk labels, fsck for UFS/FFS has been
1519 unable to automatically find alternate superblocks. As of r322297,
1520 the information needed to find alternate superblocks has been
1521 moved to the end of the area reserved for the boot block.
1522 Filesystems created with a newfs of this vintage or later
1523 will create the recovery information. If you have a filesystem
1524 created prior to this change and wish to have a recovery block
1525 created for your filesystem, you can do so by running fsck in
1526 foreground mode (i.e., do not use the -p or -y options). As it
1527 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
1528 to which you should answer yes.
1531 As of r321665, an NFSv4 server configuration that services
1532 Kerberos mounts or clients that do not support the uid/gid in
1533 owner/owner_group string capability, must explicitly enable
1534 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
1535 machine's /etc/rc.conf file.
1538 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
1539 Please see the 20141231 entry below for information about prerequisites
1540 and upgrading, if you are not already using clang 3.5.0 or higher.
1543 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
1544 r-commands (rlogin, rsh, etc.) to be built with the base system.
1547 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
1548 a very major ABI incompatible change, so users of FreeBSD/powerpc must
1549 be careful when performing source upgrades. It is best to run
1550 'make installworld' from an alternate root system, either a live
1551 CD/memory stick, or a temporary root partition. Additionally, all ports
1552 must be recompiled. powerpc64 is largely unaffected, except in the case
1553 of 32-bit compatibility. All 32-bit binaries will be affected.
1556 Forward compatibility for the "ino64" project have been committed. This
1557 will allow most new binaries to run on older kernels in a limited
1558 fashion. This prevents many of the common foot-shooting actions in the
1559 upgrade as well as the limited ability to roll back the kernel across
1560 the ino64 upgrade. Complicated use cases may not work properly, though
1561 enough simpler ones work to allow recovery in most situations.
1564 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
1565 if you require the GPL compiler.
1568 The internal ABI used for communication between the NFS kernel modules
1569 was changed by r320085, so __FreeBSD_version was bumped to
1570 ensure all the NFS related modules are updated together.
1573 The ABI of struct event was changed by extending the data
1574 member to 64bit and adding ext fields. For upgrade, same
1575 precautions as for the entry 20170523 "ino64" must be
1579 The GNU roff toolchain has been removed from base. To render manpages
1580 which are not supported by mandoc(1), man(1) can fallback on GNU roff
1581 from ports (and recommends to install it).
1582 To render roff(7) documents, consider using GNU roff from ports or the
1583 heirloom doctools roff toolchain from ports via pkg install groff or
1584 via pkg install heirloom-doctools.
1587 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
1588 smaller runtime footprint builds. This is useful for embedded systems
1589 which only require one chipset support.
1591 If you load it as a module, make sure this is in /boot/loader.conf:
1595 This will load the HAL, all chip/RF backends and if_ath_pci.
1596 If you have if_ath_pci in /boot/loader.conf, ensure it is after
1597 if_ath or it will not load any HAL chipset support.
1599 If you want to selectively load things (eg on cheaper ARM/MIPS
1600 platforms where RAM is at a premium) you should:
1603 * load the chip modules in question
1604 * load ath_rate, ath_dfs
1606 * load if_ath_pci and/or if_ath_ahb depending upon your particular
1607 bus bind type - this is where probe/attach is done.
1609 For further comments/feedback, poke adrian@ .
1612 The "ino64" 64-bit inode project has been committed, which extends
1613 a number of types to 64 bits. Upgrading in place requires care and
1614 adherence to the documented upgrade procedure.
1616 If using a custom kernel configuration ensure that the
1617 COMPAT_FREEBSD11 option is included (as during the upgrade the
1618 system will be running the ino64 kernel with the existing world).
1620 For the safest in-place upgrade begin by removing previous build
1621 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full
1622 procedure documented below under the heading "To rebuild everything and
1623 install it on the current system." Specifically, a reboot is required
1624 after installing the new kernel before installing world. While an
1625 installworld normally works by accident from multiuser after rebooting
1626 the proper kernel, there are many cases where this will fail across this
1627 upgrade and installworld from single user is required.
1630 The NATM framework including the en(4), fatm(4), hatm(4), and
1631 patm(4) devices has been removed. Consumers should plan a
1632 migration before the end-of-life date for FreeBSD 11.
1635 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
1636 diff has not been implemented, if those are needed a newer version of
1637 GNU diff is available via the diffutils package under the gdiff name.
1640 As of r316810 for ipfilter, keep frags is no longer assumed when
1641 keep state is specified in a rule. r316810 aligns ipfilter with
1642 documentation in man pages separating keep frags from keep state.
1643 This allows keep state to be specified without forcing keep frags
1644 and allows keep frags to be specified independently of keep state.
1645 To maintain previous behaviour, also specify keep frags with
1646 keep state (as documented in ipf.conf.5).
1649 arm64 builds now use the base system LLD 4.0.0 linker by default,
1650 instead of requiring that the aarch64-binutils port or package be
1651 installed. To continue using aarch64-binutils, set
1652 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
1655 The UDP optimization in entry 20160818 that added the sysctl
1656 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
1657 packets will no longer be treated as L3 broadcast packets.
1660 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
1661 use any explicitly assigned loopback address available in the jail
1662 instead of using the first assigned address of the jail.
1665 The ctl.ko module no longer implements the iSCSI target frontend:
1666 cfiscsi.ko does instead.
1668 If building cfiscsi.ko as a kernel module, the module can be loaded
1669 via one of the following methods:
1670 - `cfiscsi_load="YES"` in loader.conf(5).
1671 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
1672 - ctladm(8)/ctld(8), when compiled with iSCSI support
1673 (`WITH_ISCSI=yes` in src.conf(5))
1675 Please see cfiscsi(4) for more details.
1678 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
1679 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
1680 same source (previously, the dependency of mmcsd.ko on mmc.ko was
1681 missing, but mmcsd.ko now will refuse to load if it is incompatible
1685 The syntax of ipfw(8) named states was changed to avoid ambiguity.
1686 If you have used named states in the firewall rules, you need to modify
1687 them after installworld and before rebooting. Now named states must
1688 be prefixed with colon.
1691 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
1692 removed as the userland we provide cannot use them. The KMS version
1693 (sys/dev/drm2) supports the same hardware.
1696 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
1697 Please see the 20141231 entry below for information about prerequisites
1698 and upgrading, if you are not already using clang 3.5.0 or higher.
1701 The code that provides support for ZFS .zfs/ directory functionality
1702 has been reimplemented. It's not possible now to create a snapshot
1703 by mkdir under .zfs/snapshot/. That should be the only user visible
1707 EISA bus support has been removed. The WITH_EISA option is no longer
1711 MCA bus support has been removed.
1714 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
1715 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
1718 The EM_MULTIQUEUE kernel configuration option is deprecated now that
1719 the em(4) driver conforms to iflib specifications.
1722 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
1723 IFLIB. If you have a custom kernel configuration that excludes em(4)
1724 but you use igb(4), you need to re-add em(4) to your custom
1728 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
1729 Please see the 20141231 entry below for information about prerequisites
1730 and upgrading, if you are not already using clang 3.5.0 or higher.
1733 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
1734 Please see the 20141231 entry below for information about prerequisites
1735 and upgrading, if you are not already using clang 3.5.0 or higher.
1738 The layout of the pmap structure has changed for powerpc to put the pmap
1739 statistics at the front for all CPU variations. libkvm(3) and all tools
1740 that link against it need to be recompiled.
1743 isl(4) and cyapa(4) drivers now require a new driver,
1744 chromebook_platform(4), to work properly on Chromebook-class hardware.
1745 On other types of hardware the drivers may need to be configured using
1746 device hints. Please see the corresponding manual pages for details.
1749 The urtwn(4) driver was merged into rtwn(4) and now consists of
1750 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
1752 Also, firmware for RTL8188CE was renamed due to possible name
1753 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
1756 GNU rcs has been removed from base. It is available as packages:
1757 - rcs: Latest GPLv3 GNU rcs version.
1758 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
1762 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
1763 modules now requires that the kernel configuration contain the
1764 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
1767 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
1768 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
1771 Relocatable object files with the extension of .So have been renamed
1772 to use an extension of .pico instead. The purpose of this change is
1773 to avoid a name clash with shared libraries on case-insensitive file
1774 systems. On those file systems, foo.So is the same file as foo.so.
1777 GNU rcs has been turned off by default. It can (temporarily) be built
1778 again by adding WITH_RCS knob in src.conf.
1779 Otherwise, GNU rcs is available from packages:
1780 - rcs: Latest GPLv3 GNU rcs version.
1781 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
1784 The backup_uses_rcs functionality has been removed from rc.subr.
1787 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
1788 two separate components, QUEUE_MACRO_DEBUG_TRACE and
1789 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
1790 QUEUE_MACRO_DEBUG behavior.
1793 r304787 changed some ioctl interfaces between the iSCSI userspace
1794 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1795 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1799 The UDP receive code has been updated to only treat incoming UDP
1800 packets that were addressed to an L2 broadcast address as L3
1801 broadcast packets. It is not expected that this will affect any
1802 standards-conforming UDP application. The new behaviour can be
1803 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1807 Remove the openbsd_poll system call.
1808 __FreeBSD_version has been bumped because of this.
1811 The stable/11 branch has been created from head@r302406.
1813 After branch N is created, entries older than the N-2 branch point are removed
1814 from this file. After stable/14 is branched and current becomes FreeBSD 15,
1815 entries older than stable/12 branch point will be removed from current's
1822 Sometimes, obscure build problems are the result of environment
1823 poisoning. This can happen because the make utility reads its
1824 environment when searching for values for global variables. To run
1825 your build attempts in an "environmental clean room", prefix all make
1826 commands with 'env -i '. See the env(1) manual page for more details.
1827 Occasionally a build failure will occur with "make -j" due to a race
1828 condition. If this happens try building again without -j, and please
1829 report a bug if it happens consistently.
1831 When upgrading from one major version to another it is generally best to
1832 upgrade to the latest code in the currently installed branch first, then
1833 do an upgrade to the new branch. This is the best-tested upgrade path,
1834 and has the highest probability of being successful. Please try this
1835 approach if you encounter problems with a major version upgrade. Since
1836 the stable 4.x branch point, one has generally been able to upgrade from
1837 anywhere in the most recent stable branch to head / current (or even the
1838 last couple of stable branches). See the top of this file when there's
1841 The update process will emit an error on an attempt to perform a build
1842 or install from a FreeBSD version below the earliest supported version.
1843 When updating from an older version the update should be performed one
1844 major release at a time, including running `make delete-old` at each
1847 When upgrading a live system, having a root shell around before
1848 installing anything can help undo problems. Not having a root shell
1849 around can lead to problems if pam has changed too much from your
1850 starting point to allow continued authentication after the upgrade.
1852 This file should be read as a log of events. When a later event changes
1853 information of a prior event, the prior event should not be deleted.
1854 Instead, a pointer to the entry with the new information should be
1855 placed in the old entry. Readers of this file should also sanity check
1856 older entries before relying on them blindly. Authors of new entries
1857 should write them with this in mind.
1861 When upgrading the boot ZFS pool to a new version (via zpool upgrade),
1862 always follow these three steps:
1864 1) recompile and reinstall the ZFS boot loader and boot block
1865 (this is part of "make buildworld" and "make installworld")
1867 2) update the ZFS boot block on your boot drive (only required when
1868 doing a zpool upgrade):
1870 When booting on x86 via BIOS, use the following to update the ZFS boot
1871 block on the freebsd-boot partition of a GPT partitioned drive ada0:
1872 gpart bootcode -p /boot/gptzfsboot -i $N ada0
1873 The value $N will typically be 1. For EFI booting, see EFI notes.
1875 3) zpool upgrade the root pool. New bootblocks will work with old
1876 pools, but not vice versa, so they need to be updated before any
1879 Non-boot pools do not need these updates.
1884 There are two locations the boot loader can be installed into. The
1885 current location (and the default) is \efi\freebsd\loader.efi and using
1886 efibootmgr(8) to configure it. The old location, that must be used on
1887 deficient systems that don't honor efibootmgr(8) protocols, is the
1888 fallback location of \EFI\BOOT\BOOTxxx.EFI. Generally, you will copy
1889 /boot/loader.efi to this location, but on systems installed a long time
1890 ago the ESP may be too small and /boot/boot1.efi may be needed unless
1891 the ESP has been expanded in the meantime.
1893 Recent systems will have the ESP mounted on /boot/efi, but older ones
1894 may not have it mounted at all, or mounted in a different
1895 location. Older arm SD images with MBR used /boot/msdos as the
1896 mountpoint. The ESP is a MSDOS filesystem.
1898 The EFI boot loader rarely needs to be updated. For ZFS booting,
1899 however, you must update loader.efi before you do 'zpool upgrade' the
1900 root zpool, otherwise the old loader.efi may reject the upgraded zpool
1901 since it does not automatically understand some new features.
1903 See loader.efi(8) and uefi(8) for more details.
1907 If you are updating from a prior version of FreeBSD (even one just
1908 a few days old), you should follow this procedure. It is the most
1909 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1911 make kernel-toolchain
1912 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1913 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1915 To test a kernel once
1916 ---------------------
1917 If you just want to boot a kernel once (because you are not sure
1918 if it works, or if you want to boot a known bad kernel to provide
1919 debugging information) run
1920 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1921 nextboot -k testkernel
1923 To rebuild everything and install it on the current system.
1924 -----------------------------------------------------------
1925 # Note: sometimes if you are running current you gotta do more than
1926 # is listed here if you are upgrading from a really old current.
1928 <make sure you have good level 0 dumps>
1930 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1931 make installkernel KERNCONF=YOUR_KERNEL_HERE
1933 <reboot in single user> [3]
1940 To cross-install current onto a separate partition
1941 --------------------------------------------------
1942 # In this approach we use a separate partition to hold
1943 # current's root, 'usr', and 'var' directories. A partition
1944 # holding "/", "/usr" and "/var" should be about 2GB in
1947 <make sure you have good level 0 dumps>
1950 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1951 <maybe newfs current's root partition>
1952 <mount current's root partition on directory ${CURRENT_ROOT}>
1953 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1954 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1955 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1956 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1957 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1958 <reboot into current>
1959 <do a "native" rebuild/install as described in the previous section>
1960 <maybe install compatibility libraries from ports/misc/compat*>
1964 To upgrade in-place from stable to current
1965 ----------------------------------------------
1966 <make sure you have good level 0 dumps>
1968 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1969 make installkernel KERNCONF=YOUR_KERNEL_HERE
1971 <reboot in single user> [3]
1978 Make sure that you've read the UPDATING file to understand the
1979 tweaks to various things you need. At this point in the life
1980 cycle of current, things change often and you are on your own
1981 to cope. The defaults can also change, so please read ALL of
1982 the UPDATING entries.
1984 Also, if you are tracking -current, you must be subscribed to
1985 freebsd-current@freebsd.org. Make sure that before you update
1986 your sources that you have read and understood all the recent
1987 messages there. If in doubt, please track -stable which has
1988 much fewer pitfalls.
1990 [1] If you have third party modules, such as vmware, you should disable
1991 them at this point so they don't crash your system on
1992 reboot. Alternatively, you should rebuild all the modules you have in
1993 your system and install them as well. If you are running -current, you
1994 should seriously consider placing all sources to all the modules for
1995 your system (or symlinks to them) in /usr/local/sys/modules so this
1996 happens automatically. If all your modules come from ports, then adding
1997 the port origin directories to PORTS_MODULES instead is also automatic
1999 PORTS_MODULES+=x11/nvidia-driver
2001 [3] From the bootblocks, boot -s, and then do
2005 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed
2006 cd src # full path to source
2007 adjkerntz -i # if CMOS is wall time
2008 Also, when doing a major release upgrade, it is required that you boot
2009 into single user mode to do the installworld.
2011 [4] Note: This step is non-optional. Failure to do this step
2012 can result in a significant reduction in the functionality of the
2013 system. Attempting to do it by hand is not recommended and those
2014 that pursue this avenue should read this file carefully, as well
2015 as the archives of freebsd-current and freebsd-hackers mailing lists
2016 for potential gotchas. See etcupdate(8) for more information.
2018 [5] Usually this step is a no-op. However, from time to time
2019 you may need to do this if you get unknown user in the following
2022 [6] This only deletes old files and directories. Old libraries
2023 can be deleted by "make delete-old-libs", but you have to make
2024 sure that no program is using those libraries anymore.
2026 [8] The new kernel must be able to run existing binaries used by an
2027 installworld. When upgrading across major versions, the new kernel's
2028 configuration must include the correct COMPAT_FREEBSD<n> option for
2029 existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure
2030 to do so may leave you with a system that is hard to boot to recover. A
2031 GENERIC kernel will include suitable compatibility options to run
2032 binaries from older branches. Note that the ability to run binaries
2033 from unsupported branches is not guaranteed.
2035 Make sure that you merge any new devices from GENERIC since the
2036 last time you updated your kernel config file. Options also
2037 change over time, so you may need to adjust your custom kernels
2040 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2041 "?=" instead of the "=" assignment operator, so that buildworld can
2042 override the CPUTYPE if it needs to.
2044 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2045 not on the command line, or in /etc/make.conf. buildworld will
2046 warn if it is improperly defined.
2049 This file contains a list, in reverse chronological order, of major
2050 breakages in tracking -current. It is not guaranteed to be a complete
2051 list of such breakages, and only contains entries since September 23, 2011.
2052 If you need to see UPDATING entries from before that date, you will need
2053 to fetch an UPDATING file from an older FreeBSD release.
2055 Copyright information:
2057 Copyright 1998-2009 M. Warner Losh <imp@FreeBSD.org>
2059 Redistribution, publication, translation and use, with or without
2060 modification, in full or in part, in any form or format of this
2061 document are permitted without further permission from the author.
2063 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2064 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2065 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2066 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2067 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2068 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2069 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2070 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2071 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2072 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2073 POSSIBILITY OF SUCH DAMAGE.
2075 Contact Warner Losh if you have any questions about your use of