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 stable/14 branch created.
116 The heuristic for detecting old chromebooks with an EC bug that requires
117 atkbdc driver workarounds has changed. There should be no functional
118 change, but if your old chromebook's keyboard stops working, please
119 file a PR and assign it to imp.
122 OpenSSL has been updated to version 3.0, including changes throughout
123 the base system. It is important to rebuild third-party software
127 To enable pf rdr rules for connections initiated from the host, pf
128 filter rules can be optionally enabled for packets delivered
129 locally. This can change the behavior of rules which match packets
130 delivered to lo0. To enable this feature:
132 sysctl net.pf.filter_local=1
135 When enabled, its best to ensure that packets delivered locally are not
136 filtered, e.g. by adding a 'skip on lo' rule.
139 Improvements to libtacplus(8) mean that tacplus.conf(5) now
140 follows POSIX shell syntax rules. This may cause TACACS+
141 authentication to fail if the shared secret contains a single
142 quote, double quote, or backslash character which isn't
143 already properly quoted or escaped.
146 Belatedly switch the default nvme block device on x86 from nvd to nda.
147 nda created nvd compatibility links by default, so this should be a
148 nop. If this causes problems for your application, set hw.nvme.use_nvd=1
149 in your loader.conf or add `options NVME_USE_NVD=1` to your kernel
150 config. To disable the nvd compatibility aliases, add
151 kern.cam.nda.nvd_compat=0 to loader.conf. The default has been nda on
152 all non-x86 platforms for some time now. If you need to fall back,
153 please email imp@freebsd.org about why.
155 Encrypted swap partitions need to be changed from nvd to nda if you
156 migrate, or you need to use the above to switch back to nvd.
159 Remove portsnap(8). Users are encouraged to obtain the ports tree
163 Add jobs.mk to save typing. Enables -j${JOB_MAX} and logging
167 make -j${JOB_MAX} buildworld > ../buildworld.log 2>&1
169 where JOB_MAX is derrived from ncpus in local.sys.mk if not set in env.
172 Video related devices for some arm devices have been renamed.
173 If you have a custom kernel config and want to use hdmi output on
174 IMX6 board you need to add "device dwc_hdmi" "device imx6_hdmi" and
175 "device imx6_ipu" to it.
176 If you have a custom kernel config and want to use hdmi output on
177 TI AM335X board you need to add "device tda19988" to it.
178 If you add "device hdmi" in it you need to remove it as it doesn't
182 Introduce new kernel options KBD_DELAY1 and KBD_DELAY2. See atkbdc(4)
186 sshd now defaults to having X11Forwarding disabled, following upstream.
187 Administrators who wish to enable X11Forwarding should add
188 `X11Forwarding yes` to /etc/ssh/sshd_config.
191 Since commit 75d41cb6967 Huawei 3G/4G LTE Mobile Devices do not default
192 to ECM, but NCM mode and need u3g and ucom modules loaded. See cdce(4).
195 As of commit 7c40e2d5f685, the dependency on netlink(4) has been added
196 to the linux_common(4) module. Users relying on linux_common may need
197 to complile netlink(4) module if it is not present in their kernel.
200 The WITHOUT_CXX option has been removed. C++ components in the base
201 system are now built unconditionally.
204 LinuxKPI pci.h changes may require out-of-tree drivers to be recompiled.
205 Bump _FreeBSD_version to 1400078 to be able to detect this change.
208 llvm-objump is now always installed as objdump. Previously there was
209 no /usr/bin/objdump unless the WITH_LLVM_BINUTILS knob was used.
211 Some LLVM objdump options have a different output format compared to
212 GNU objdump; readelf is available for inspecting ELF files, and GNU
213 objdump is available from the devel/binutils port or package.
216 dma(8) has replaced sendmail(8) as the default mta. For people willing
217 to reenable sendmail(8):
219 $ cp /usr/share/examples/sendmail/mailer.conf /etc/mail/mailer.conf
221 and add sendmail_enable="YES" to rc.conf.
224 hw.bus.disable_failed_devices has changed from 'false' to 'true' by
225 default. Now if newbus succeeds in probing a device, but fails to attach
226 the device, we'll disable the device. In the past, we'd keep retrying
227 the device on each new driver loaded. To get that behavior now, one
228 needs to use devctl to re-enable the device, and reprobe it (or set
229 the sysctl/tunable hw.bus.disable_failed_devices=false).
231 NOTE: This was reverted 20221205 due to unexpected compatibility issues
234 pf no longer accepts 'scrub fragment crop' or 'scrub fragment drop-ovl'.
235 These configurations are no longer automatically reinterpreted as
236 'scrub fragment reassemble'.
239 The WITHOUT_CLANG_IS_CC option has been removed. When Clang is enabled
240 it is always installed as /usr/bin/cc (and c++, cpp).
243 Some programs have been moved into separate packages. It is recommended
244 for pkgbase users to do:
246 pkg install FreeBSD-dhclient FreeBSD-geom FreeBSD-resolvconf \
247 FreeBSD-devd FreeBSD-devmatch
249 after upgrading to restore all the component that were previously
253 OPIE has been removed from the base system. If needed, it can
254 be installed from ports (security/opie) or packages (opie).
255 Otherwise, make sure that your PAM policies do not reference
256 pam_opie or pam_opieaccess.
259 LinuxKPI pm.h changes require an update to the latest drm-kmod version
260 before re-compiling to avoid errors.
263 The macros provided for the manipulation of CPU sets (e.g. CPU_AND)
264 have been modified to take 2 source arguments instead of only 1.
265 Externally maintained sources that use these macros will have to
266 be adapted. The FreeBSD version has been bumped to 1400046 to
270 A number of the kernel include files are able to be included by
271 themselves. A test has been added to buildworld to enforce this.
274 Remove mips as a recognized target. This starts the decommissioning of
275 mips support in FreeBSD. mips related items will be removed wholesale in
276 the coming days and weeks.
278 This broke the NO_CLEAN build for some people. Either do a clean build
280 lib/clang/include/llvm/Config/Targets.def
281 lib/clang/include/llvm/Config/AsmParsers.def
282 lib/clang/include/llvm/Config/Disassemblers.def
283 lib/clang/include/llvm/Config/AsmPrinters.def
284 before the build to force everything to rebuild that needs to.
287 Unbound support for RFC8375: The special-use domain 'home.arpa' is
288 by default blocked. To unblock it use a local-zone nodefault
289 statement in unbound.conf:
290 local-zone: "home.arpa." nodefault
292 Or use another type of local-zone to override with your choice.
294 The reason for this is discussed in Section 6.1 of RFC8375:
295 Because 'home.arpa.' is not globally scoped and cannot be secured
296 using DNSSEC based on the root domain's trust anchor, there is no way
297 to tell, using a standard DNS query, in which homenet scope an answer
298 belongs. Consequently, users may experience surprising results with
299 such names when roaming to different homenets.
302 Commit b8d60729deef changed the TCP congestion control framework so
303 that any of the included congestion control modules could be
304 the single module built into the kernel. Previously newreno
305 was automatically built in through direct reference. As of
306 this commit you are required to declare at least one congestion
307 control module (e.g. 'options CC_NEWRENO') and to also declare a
308 default using the CC_DEFAULT option (e.g. options CC_DEFAULT="newreno\").
309 The GENERIC configuration includes CC_NEWRENO and defines newreno
310 as the default. If no congestion control option is built into the
311 kernel and you are including networking, the kernel compile will
312 fail. Also if no default is declared the kernel compile will fail.
315 Mips has been removed from universe builds. It will be removed from the
319 Commit f0c9847a6c47 changed the arguments for VOP_ALLOCATE.
320 The NFS modules must be rebuilt from sources and any out
321 of tree file systems that implement their own VOP_ALLOCATE
322 may need to be modified.
325 The synchronous PPP kernel driver sppp(4) has been removed.
326 The cp(4) and ce(4) drivers are now always compiled with netgraph(4)
327 support, formerly enabled by NETGRAPH_CRONYX option.
330 sh(1) is now the default shell for the root user. To force root to use
331 the csh shell, please run the following command as root:
336 Ncurses distribution has been split between libtinfow and libncurses
337 with libncurses.so becoming a linker (ld) script to seamlessly link
338 to libtinfow as needed. Bump _FreeBSD_version to 1400035 to reflect
342 As of commit 8160a0f62be6, the dummynet module no longer depends on the
343 ipfw module. Dummynet can now be used by pf as well as ipfw. As such
344 users who relied on this dependency may need to include ipfw in the
345 list of modules to load on their systems.
348 As of commit 903873ce1560, the mixer(8) utility has got a slightly
349 new syntax. Please refer to the mixer(8) manual page for more
350 information. The old mixer utility can be installed from ports:
351 audio/freebsd-13-mixer
354 As of commit 55089ef4f8bb, the global variable nfs_maxcopyrange has
355 been deleted from the nfscommon.ko. As such, nfsd.ko must be built
356 from up to date sources to avoid an undefined reference when
360 As of commit 62ca9fc1ad56 OpenSSL no longer enables kernel TLS
361 by default. Users can enable kernel TLS via the "KTLS" SSL
362 option. This can be enabled globally by using a custom
363 OpenSSL config file via OPENSSL_CONF or via an
364 application-specific configuration option for applications
365 which permit setting SSL options via SSL_CONF_cmd(3).
368 Commit 3ad1e1c1ce20 changed the internal KAPI between the NFS
369 modules. Therefore, all need to be rebuilt from sources.
372 Commit b69019c14cd8 removes pf's DIOCGETSTATESNV ioctl.
373 As of be70c7a50d32 it is no longer used by userspace, but it does mean
374 users may not be able to enumerate pf states if they update the kernel
375 past b69019c14cd8 without first updating userspace past be70c7a50d32.
378 As of commit 01ad0c007964 if_bridge member interfaces can no longer
379 change their MTU. Changing the MTU of the bridge itself will change the
380 MTU on all member interfaces instead.
383 Commit ee29e6f31111 changed the internal KAPI between the nfscommon
384 and nfsd modules. Therefore, both need to be rebuilt from sources.
385 Bump __FreeBSD_version to 1400026 for this KAPI change.
388 The 20210707 awk update brought in a change in behavior. This has
389 been corrected as of d4d252c49976. Between these dates, if you
390 installed a new awk binary, you may not be able to build a new
391 kernel because the change in behavior affected the genoffset
392 script used to build the kernel. If you did update, the fix is
393 to update your sources past the above hash and do
396 % sudo -E make install
397 to enable building kernels again.
400 Commit 1e0a518d6548 changed the internal KAPI between the NFS
401 modules. They all need to be rebuilt from sources. I did not
402 bump __FreeBSD_version, since it was bumped recently.
405 awk has been updated to the latest one-true-awk version 20210215.
406 This contains a number of minor bug fixes.
409 The NFSv4 client now uses the highest minor version of NFSv4
410 supported by the NFSv4 server by default instead of minor version 0,
412 The "minorversion" mount option may be used to override this default.
415 Bump __FreeBSD_version to 1400024 for LinuxKPI changes.
416 Most notably netdev.h can change now as the (last) dependencies
417 (mlx4/ofed) are now using struct ifnet directly, but also for PCI
418 additions and others.
421 The directory "blacklisted" under /usr/share/certs/ has been
422 renamed to "untrusted".
425 svnlite has been removed from base. Should you need svn for any reason
426 please install the svn package or port.
429 Commit e1a907a25cfa changed the internal KAPI between the krpc
430 and nfsserver. As such, both modules must be rebuilt from
431 sources. Bump __FreeBSD_version to 1400022.
434 The an(4) driver has been removed from FreeBSD.
437 The vendor/openzfs branch was renamed to vendor/openzfs/legacy to
438 start tracking OpenZFS upstream more closely. Please see
439 https://lists.freebsd.org/archives/freebsd-current/2021-June/000153.html
440 for details on how to correct any errors that might result. The
441 short version is that you need to remove the old branch locally:
442 git update-ref -d refs/remotes/freebsd/vendor/openzfs
443 (assuming your upstream origin is named 'freebsd').
446 Commits 17accc08ae15 and de102f870501 add new files to LinuxKPI
447 which break drm-kmod. In addition various other additions where
448 committed. Bump __FreeBSD_version to 1400015 to be able to
452 Commit ca179c4d74f2 changed the package in which the OpenSSL
453 libraries and utilities are packaged.
454 It is recommended for pkgbase user to do:
455 pkg install -f FreeBSD-openssl
456 before pkg upgrade otherwise some dependencies might not be met
457 and pkg will stop working as libssl will not be present anymore
461 Commit 875977314881 changed the internal KAPI between
462 the nfsd and nfscommon modules. As such these modules
463 need to be rebuilt from sources.
464 Without this patch in your NFSv4.1/4.2 server, enabling
465 delegations by setting vfs.nfsd.issue_delegations non-zero
469 Commit 7763814fc9c2 changed the internal KAPI between
470 the krpc and NFS. As such, the krpc, nfscommon and
471 nfscl modules must all be rebuilt from sources.
472 Without this patch, NFSv4.1/4.2 mounts should not
473 be done with the nfscbd(8) daemon running, to avoid
474 needing a working back channel for server->client RPCs.
477 Commit 01ae8969a9ee fixed the NFSv4.1/4.2 server so that it
478 handles binding of the back channel as required by RFC5661.
479 Until this patch is in your server, avoid use of the "nconnects"
480 mount option for Linux NFSv4.1/4.2 mounts.
483 For 64-bit architectures the base system is now built with Position
484 Independent Executable (PIE) support enabled by default. It may be
485 disabled using the WITHOUT_PIE knob. A clean build is required.
488 Various LinuxKPI functionality was added which conflicts with DRM.
489 Please update your drm-kmod port to after the __FreeBSD_version 1400003
493 stable/13 branch created.
496 PC Card attachments for all devices have been removed. In the case of
497 wi and cmx, the entire drivers were removed because they were only
498 PC Card devices. FreeBSD_version 1300134 should be used for this
499 since it was bumped so recently.
502 Transport-independent parts of HID support have been split off the USB
503 code in to separate subsystem. Kernel configs which include one of
504 ums, ukbd, uhid, atp, wsp, wmt, uaudio, ugold or ucycom drivers should
505 be updated with adding of "device hid" line.
508 ncurses installation has been modified to only keep the widechar
509 enabled version. Incremental build is broken for that change, so it
510 requires a clean build.
513 The FreeBSD project has migrated from Subversion to Git. Temporary
514 instructions can be found at
515 https://github.com/bsdimp/freebsd-git-docs/blob/main/src-cvt.md
516 and other documents in that repo.
519 The services database has been updated to cover more of the basic
520 services expected in a modern system. The database is big enough
521 that it will cause issues in mergemaster in Releases previous to
522 12.2 and 11.3, or in very old current systems from before r358154.
525 Obsolete in-tree GDB 6.1.1 has been removed. GDB (including kgdb)
526 may be installed from ports or packages.
529 ping6 has been merged into ping. It can now be called as "ping -6".
530 See ping(8) for details.
533 Default value of net.add_addr_allfibs has been changed to 0.
534 If you have multi-fib configuration and rely on existence of all
535 interface routes in every fib, you need to set the above sysctl to 1.
538 The internal pre-processor in the calendar(1) program has been
539 extended to support more C pre-processor commands (e.g. #ifdef, #else,
540 and #undef) and to detect unbalanced conditional statements.
541 Error messages have been extended to include the filename and line
542 number if processing stops to help fixing malformed data files.
545 All the data files for the calendar(1) program, except calendar.freebsd,
546 have been moved to the deskutils/calendar-data port, much like the
547 jewish calendar entries were moved to deskutils/hebcal years ago. After
548 make delete-old-files, you need to install it to retain full
549 functionality. calendar(1) will issue a reminder for files it can't
553 LINT files are no longer generated. We now include the relevant NOTES
554 files. Note: This may cause conflicts with updating in some cases.
555 find sys -name LINT\* -delete
556 is suggested across this commit to remove the generated LINT files.
558 If you have tried to update with generated files there, the svn
559 command you want to un-auger the tree is
562 and then do the above find from the top level. Substitute 'amd64'
563 above with where the error message indicates a conflict.
566 OpenZFS support has been integrated. Do not upgrade root pools until
567 the loader is updated to support zstd. Furthermore, we caution against
568 'zpool upgrade' for the next few weeks. The change should be transparent
569 unless you want to use new features.
571 Not all "NO_CLEAN" build scenarios work across these changes. Many
572 scenarios have been tested and fixed, but rebuilding kernels without
573 rebuilding world may fail.
575 The ZFS cache file has moved from /boot to /etc to match the OpenZFS
576 upstream default. A fallback to /boot has been added for mountroot.
578 Pool auto import behavior at boot has been moved from the kernel module
579 to an explicit "zpool import -a" in one of the rc scripts enabled by
580 zfs_enable=YES. This means your non-root zpools won't auto import until
581 you upgrade your /etc/rc.d files.
584 The resume code now notifies devd with the 'kernel' system
585 rather than the old 'kern' subsystem to be consistent with
586 other use. The old notification will be created as well, but
587 will be removed prior to FreeBSD 14.0.
590 r362275 changed the internal API between the kernel RPC and the
591 NFS modules. As such, all the modules must be recompiled from
595 r364330 modified the internal API used between the NFS modules.
596 As such, all the NFS modules must be re-compiled from sources.
599 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
600 been upgraded to 11.0.0. Please see the 20141231 entry below for
601 information about prerequisites and upgrading, if you are not already
602 using clang 3.5.0 or higher.
605 r364092 modified the internal ABI used between the kernel NFS
606 modules. As such, all of these modules need to be rebuilt
607 from sources, so a version bump was done.
610 Makefile.inc has been updated to work around the issue documented in
611 20200729. It was a case where the optimization of using symbolic links
612 to point to binaries created a situation where we'd run new binaries
613 with old libraries starting midway through the installworld process.
616 r363679 has redefined some undefined behavior in regcomp(3); notably,
617 extraneous escapes of most ordinary characters will no longer be
618 accepted. An exp-run has identified all of the problems with this in
619 ports, but other non-ports software may need extra escapes removed to
620 continue to function.
622 Because of this change, installworld may encounter the following error
623 from rtld: Undefined symbol "regcomp@FBSD_1.6" -- It is imperative that
624 you do not halt installworld. Instead, let it run to completion (whether
625 successful or not) and run installworld once more.
628 A new implementation of bc and dc has been imported in r362681. This
629 implementation corrects non-conformant behavior of the previous bc
630 and adds GNU bc compatible options. It offers a number of extensions,
631 is much faster on large values, and has support for message catalogs
632 (a number of languages are already supported, contributions of further
633 languages welcome). The option WITHOUT_GH_BC can be used to build the
634 world with the previous versions of bc and dc.
637 r362639 changed the internal API used between the NFS kernel modules.
638 As such, they all need to be rebuilt from sources.
641 r362158 changed the arguments for VFS_CHECKEXP(). As such, any
642 out of tree file systems need to be modified and rebuilt.
643 Also, any file systems that are modules must be rebuilt.
646 read(2) of a directory fd is now rejected by default. root may
647 re-enable it for system root only on non-ZFS filesystems with the
648 security.bsd.allow_read_dir sysctl(8) MIB if
649 security.bsd.suser_enabled=1.
651 It may be advised to setup aliases for grep to default to `-d skip` if
652 commonly non-recursively grepping a list that includes directories and
653 the potential for the resulting stderr output is not tolerable. Example
654 aliases are now installed, commented out, in /root/.cshrc and
658 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
659 been upgraded to 10.0.1. Please see the 20141231 entry below for
660 information about prerequisites and upgrading, if you are not already
661 using clang 3.5.0 or higher.
664 Support for obsolete compilers has been removed from the build system.
665 Clang 6 and GCC 6.4 are the minimum supported versions.
668 closefrom(2) has been moved under COMPAT12, and replaced in libc with a
669 stub that calls close_range(2). If using a custom kernel configuration,
670 you may want to ensure that the COMPAT_FREEBSD12 option is included, as
671 a slightly older -CURRENT userland and older FreeBSD userlands may not
672 be functional without closefrom(2).
675 Upstream DTS from Linux 5.6 was merged and they now have the SID
676 and THS (Secure ID controller and THermal Sensor) node present.
677 The DTB overlays have now been removed from the tree for the H3/H5 and
678 A64 SoCs and the aw_sid and aw_thermal driver have been updated to
679 deal with upstream DTS. If you are using those overlays you need to
680 remove them from loader.conf and update the DTBs on the FAT partition.
683 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
684 been upgraded to 10.0.0. Please see the 20141231 entry below for
685 information about prerequisites and upgrading, if you are not already
686 using clang 3.5.0 or higher.
689 The amd(8) automount daemon has been removed from the source tree.
690 As of FreeBSD 10.1 autofs(5) is the preferred tool for automounting.
691 amd is still available in the sysutils/am-utils port.
694 Removed brooktree driver (bktr.4) from the tree.
697 The WITH_GPL_DTC option has been removed. The BSD-licenced device tree
698 compiler in usr.bin/dtc is used on all architectures which use dtc, and
699 the GPL dtc is available (if needed) from the sysutils/dtc port.
702 The WITHOUT_LLVM_LIBUNWIND option has been removed. LLVM's libunwind
703 is used by all supported CPU architectures.
706 GCC 4.2.1 has been removed from the tree. The WITH_GCC,
707 WITH_GCC_BOOTSTRAP, and WITH_GNUCXX options are no longer available.
708 Users who wish to build FreeBSD with GCC must use the external toolchain
712 ncurses has been updated to a newer version (6.2-20200215). Given the ABI
713 has changed, users will have to rebuild all the ports that are linked to
717 The size of struct vnet and the magic cookie have changed.
718 Users need to recompile libkvm and all modules using VIMAGE
719 together with their new kernel.
722 Defining the long deprecated NO_CTF, NO_DEBUG_FILES, NO_INSTALLLIB,
723 NO_MAN, NO_PROFILE, and NO_WARNS variables is now an error. Update
724 your Makefiles and scripts to define MK_<var>=no instead as required.
726 One exception to this is that program or library Makefiles should
727 define MAN to empty rather than setting MK_MAN=no.
730 Clang/LLVM is now the default compiler and LLD the default
734 make universe no longer uses GCC 4.2.1 on any architectures.
735 Architectures not supported by in-tree Clang/LLVM require an
736 external toolchain package.
739 GCC 4.2.1 is now not built by default, as part of the GCC 4.2.1
740 retirement plan. Specifically, the GCC, GCC_BOOTSTRAP, and GNUCXX
741 options default to off for all supported CPU architectures. As a
742 short-term transition aid they may be enabled via WITH_* options.
743 GCC 4.2.1 is expected to be removed from the tree on 2020-03-31.
746 Support for armv5 has been disconnected and is being removed. The
747 machine combination MACHINE=arm MACHINE_ARCH=arm is no longer valid.
748 You must now use a MACHINE_ARCH of armv6 or armv7. The default
749 MACHINE_ARCH for MACHINE=arm is now armv7.
752 Clang/LLVM is now the default compiler for all powerpc architectures.
753 LLD is now the default linker for powerpc64. The change for powerpc64
754 also includes a change to the ELFv2 ABI, incompatible with the existing
758 Kernel-loadable random(4) modules are no longer unloadable.
761 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
762 been upgraded to 9.0.1. Please see the 20141231 entry below for
763 information about prerequisites and upgrading, if you are not already
764 using clang 3.5.0 or higher.
767 r355677 has modified the internal interface used between the
768 NFS modules in the kernel. As such, they must all be upgraded
769 simultaneously. I will do a version bump for this.
772 The root certificates of the Mozilla CA Certificate Store have been
773 imported into the base system and can be managed with the certctl(8)
774 utility. If you have installed the security/ca_root_nss port or package
775 with the ETCSYMLINK option (the default), be advised that there may be
776 differences between those included in the port and those included in
777 base due to differences in nss branch used as well as general update
778 frequency. Note also that certctl(8) cannot manage certs in the
779 format used by the security/ca_root_nss port.
782 The amd(8) automount daemon has been disabled by default, and will be
783 removed in the future. As of FreeBSD 10.1 the autofs(5) is available
787 The nctgpio and wbwd drivers have been moved to the superio bus.
788 If you have one of these drivers in a kernel configuration, then
789 you should add device superio to it. If you use one of these drivers
790 as a module and you compile a custom set of modules, then you should
791 add superio to the set.
794 KPIs for network drivers to access interface addresses have changed.
795 Users need to recompile NIC driver modules together with kernel.
798 The net.link.tap.user_open sysctl no longer prevents user opening of
799 already created /dev/tapNN devices. Access is still controlled by
800 node permissions, just like tun devices. The net.link.tap.user_open
801 sysctl is now used only to allow users to perform devfs cloning of
802 tap devices, and the subsequent open may not succeed if the user is not
803 in the appropriate group. This sysctl may be deprecated/removed
804 completely in the future.
807 mips, powerpc, and sparc64 are no longer built as part of
808 universe / tinderbox unless MAKE_OBSOLETE_GCC is defined. If
809 not defined, mips, powerpc, and sparc64 builds will look for
810 the xtoolchain binaries and if installed use them for universe
811 builds. As llvm 9.0 becomes vetted for these architectures, they
812 will be removed from the list.
815 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
816 been upgraded to 9.0.0. Please see the 20141231 entry below for
817 information about prerequisites and upgrading, if you are not already
818 using clang 3.5.0 or higher.
821 The hpt27xx, hptmv, hptnr, and hptrr drivers have been removed from
822 GENERIC. They are available as modules and can be loaded by adding
823 to /boot/loader.conf hpt27xx_load="YES", hptmv_load="YES",
824 hptnr_load="YES", or hptrr_load="YES", respectively.
827 ntpd no longer by default locks its pages in memory, allowing them
828 to be paged out by the kernel. Use rlimit memlock to restore
829 historic BSD behaviour. For example, add "rlimit memlock 32"
830 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
833 Several of ping6's options have been renamed for better consistency
834 with ping. If you use any of -ARWXaghmrtwx, you must update your
835 scripts. See ping6(8) for details.
838 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
839 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
840 been removed from mount_fusefs(8). You can safely remove them from
841 your scripts, because they had no effect.
843 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
844 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
845 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
846 sysctls have been removed. If you felt the need to set any of them to
847 a non-default value, please tell asomers@FreeBSD.org why.
850 Default permissions on the /var/account/acct file (and copies of it
851 rotated by periodic daily scripts) are changed from 0644 to 0640
852 because the file contains sensitive information that should not be
853 world-readable. If the /var/account directory must be created by
854 rc.d/accounting, the mode used is now 0750. Admins who use the
855 accounting feature are encouraged to change the mode of an existing
856 /var/account directory to 0750 or 0700.
859 Entropy collection and the /dev/random device are no longer optional
860 components. The "device random" option has been removed.
861 Implementations of distilling algorithms can still be made loadable
862 with "options RANDOM_LOADABLE" (e.g., random_fortuna.ko).
865 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
866 been upgraded to 8.0.1. Please see the 20141231 entry below for
867 information about prerequisites and upgrading, if you are not already
868 using clang 3.5.0 or higher.
871 A fix was applied to i386 kernel modules to avoid panics with
872 dpcpu or vnet. Users need to recompile i386 kernel modules
873 having pcpu or vnet sections or they will refuse to load.
876 User-wired pages now have their own counter,
877 vm.stats.vm.v_user_wire_count. The vm.max_wired sysctl was renamed
878 to vm.max_user_wired and changed from an unsigned int to an unsigned
879 long. bhyve VMs wired with the -S are now subject to the user
880 wiring limit; the vm.max_user_wired sysctl may need to be tuned to
881 avoid running into the limit.
884 The IPSEC option has been removed from GENERIC. Users requiring
885 ipsec(4) must now load the ipsec(4) kernel module.
888 The tap(4) driver has been folded into tun(4), and the module has been
889 renamed to tuntap. You should update any kld_list="if_tap" or
890 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
891 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
892 module instead, and "device tap" or "device tun" entries in kernel
893 config files to select the tuntap device instead.
896 The following knobs have been added related to tradeoffs between
897 safe use of the random device and availability in the absence of
900 kern.random.initial_seeding.bypass_before_seeding: tunable; set
901 non-zero to bypass the random device prior to seeding, or zero to
902 block random requests until the random device is initially seeded.
903 For now, set to 1 (unsafe) by default to restore pre-r346250 boot
904 availability properties.
906 kern.random.initial_seeding.read_random_bypassed_before_seeding:
907 read-only diagnostic sysctl that is set when bypass is enabled and
908 read_random(9) is bypassed, to enable programmatic handling of this
909 initial condition, if desired.
911 kern.random.initial_seeding.arc4random_bypassed_before_seeding:
912 Similar to the above, but for arc4random(9) initial seeding.
914 kern.random.initial_seeding.disable_bypass_warnings: tunable; set
915 non-zero to disable warnings in dmesg when the same conditions are
916 met as for the diagnostic sysctls above. Defaults to zero, i.e.,
917 produce warnings in dmesg when the conditions are met.
920 The loadable random module KPI has changed; the random_infra_init()
921 routine now requires a 3rd function pointer for a bool (*)(void)
922 method that returns true if the random device is seeded (and
923 therefore unblocked).
926 r345895 reverts r320698. This implies that an nfsuserd(8) daemon
927 built from head sources between r320757 (July 6, 2017) and
928 r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
929 is added to the command line.
930 nfsuserd daemons built from head sources that are post-r338192 are
931 not affected and should continue to work.
934 The fuse(4) module has been renamed to fusefs(4) for consistency with
935 other filesystems. You should update any kld_load="fuse" entries in
936 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
937 "options FUSE" entries in kernel config files.
940 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
941 8.0.0. Please see the 20141231 entry below for information about
942 prerequisites and upgrading, if you are not already using clang 3.5.0
946 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
947 compiled into your custom kernel, add 'device xz' statement to the
951 drm and drm2 have been removed from the tree. Please see
952 https://wiki.freebsd.org/Graphics for the latest information on
953 migrating to the drm ports.
956 Iflib is no longer unconditionally compiled into the kernel. Drivers
957 using iflib and statically compiled into the kernel, now require
958 the 'device iflib' config option. For the same drivers loaded as
959 modules on kernels not having 'device iflib', the iflib.ko module
960 is loaded automatically.
963 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
964 options no longer exist since r343219 and r343427 respectively;
965 nothing uses them, so they should be just removed from custom
969 r342635 changes the way efibootmgr(8) works by requiring users to add
970 the -b (bootnum) parameter for commands where the bootnum was previously
971 specified with each option. For example 'efibootmgr -B 0001' is now
972 'efibootmgr -B -b 0001'.
975 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
976 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
977 servers that have vfs.nfsd.nfs_privport set will only allow mounts
978 from clients using a reserved port. Since both the FreeBSD and Linux
979 NFSv4 clients use reserved ports by default, this should not affect
983 The XLP config has been removed. We can't support 64-bit atomics in this
984 kernel because it is running in 32-bit mode. XLP users must transition
985 to running a 64-bit kernel (XLP64 or XLPN32).
987 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
988 the preferred emulator today and we don't need two different ones.
990 The old sibyte / swarm / Broadcom BCM1250 support has been
991 removed from the mips port.
994 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
995 7.0.1. Please see the 20141231 entry below for information about
996 prerequisites and upgrading, if you are not already using clang 3.5.0
1000 Remove the timed and netdate programs from the base tree. Setting
1001 the time with these daemons has been obsolete for over a decade.
1004 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
1005 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
1006 it produces broken binaries when ifuncs are in use. Users needing
1007 GNU ld should install the binutils port or package.
1010 The BSD crtbegin and crtend code has been enabled by default. It has
1011 had extensive testing on amd64, arm64, and i386. It can be disabled
1012 by building a world with -DWITHOUT_BSD_CRTBEGIN.
1015 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
1016 has been converted to a port (misc/ctm) and will be removed from
1017 FreeBSD-13. It is available as a package (ctm) for all supported
1021 The default newsyslog.conf(5) file has been changed to only include
1022 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
1023 the filenames end in '.conf' and do not begin with a '.'.
1025 You should check the configuration files in these two directories match
1026 this naming convention. You can verify which configuration files are
1027 being included using the command:
1031 Stable/12 was branched created.
1034 Ports for the DRM modules have been simplified. Now, amd64 users should
1035 just install the drm-kmod port. All others should install
1038 Graphics hardware that's newer than about 2010 usually works with
1039 drm-kmod. For hardware older than 2013, however, some users will need
1040 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
1041 than 2008 usually only works in drm-legacy-kmod. The graphics team can
1042 only commit to hardware made since 2013 due to the complexity of the
1043 market and difficulty to test all the older cards effectively. If you
1044 have hardware supported by drm-kmod, you are strongly encouraged to use
1045 that as you will get better support.
1047 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
1048 elsewhere, the drm and drm2 modules will be eliminated from the src base
1049 soon (with a limited exception for arm). Please update to the package
1050 asap and report any issues to x11@freebsd.org.
1052 Generally, anybody using the drm*-kmod packages should add
1053 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
1054 cross-threading surprises, especially with automatic driver
1055 loading from X11 startup. These will become the defaults in 13-current
1059 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
1060 custom kernel and module loading configuration files must be updated
1061 accordingly. Moreover, interfaces previous presented as ixlvN to the
1062 system are now exposed as iavfN and network configuration files must
1063 be adjusted as necessary.
1066 OpenSSL has been updated to version 1.1.1. This update included
1067 additional various API changes throughout the base system. It is
1068 important to rebuild third-party software after upgrading. The value
1069 of __FreeBSD_version has been bumped accordingly.
1072 The legacy DRM modules and drivers have now been added to the loader's
1073 module blacklist, in favor of loading them with kld_list in rc.conf(5).
1074 The module blacklist may be overridden with the loader.conf(5)
1075 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
1079 The cam(4) based nda(4) driver will be used over nvd(4) by default on
1080 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
1081 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
1082 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
1086 Reproducible build mode is now on by default, in preparation for
1087 FreeBSD 12.0. This eliminates build metadata such as the user,
1088 host, and time from the kernel (and uname), unless the working tree
1089 corresponds to a modified checkout from a version control system.
1090 The previous behavior can be obtained by setting the /etc/src.conf
1091 knob WITHOUT_REPRODUCIBLE_BUILD.
1094 The Yarrow CSPRNG has been removed from the kernel as it has not been
1095 supported by its designers since at least 2003. Fortuna has been the
1096 default since FreeBSD-11.
1099 devctl freeze/thaw have gone into the tree, the rc scripts have been
1100 updated to use them and devmatch has been changed. You should update
1101 kernel, userland and rc scripts all at the same time.
1104 The default interpreter has been switched from 4th to Lua.
1105 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
1106 interpreter. If you have custom FORTH code you will need to set
1107 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
1108 src.conf for the build. This will create default hard links between
1109 loader and loader_4th instead of loader and loader_lua, the new default.
1110 If you are using UEFI it will create the proper hard link to loader.efi.
1112 bhyve uses userboot.so. It remains 4th-only until some issues are solved
1113 regarding coexisting with multiple versions of FreeBSD are resolved.
1116 ls(1) now respects the COLORTERM environment variable used in other
1117 systems and software to indicate that a colored terminal is both
1118 supported and desired. If ls(1) is suddenly emitting colors, they may
1119 be disabled again by either removing the unwanted COLORTERM from your
1120 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
1121 may not be observed in a future release.
1124 The default pager for most commands has been changed to "less". To
1125 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
1129 The jedec_ts(4) driver has been removed. A superset of its functionality
1130 is available in the jedec_dimm(4) driver, and the manpage for that
1131 driver includes migration instructions. If you have "device jedec_ts"
1132 in your kernel configuration file, it must be removed.
1135 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
1136 This should have no effect if the kernel is booted via BIOS/legacy boot.
1137 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
1138 has a buggy firmware that prevents a successful boot due to use of
1142 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
1143 support has been removed from the tree. These ports were
1144 obsolete and/or known to be broken for many years.
1147 loader.efi has been augmented to participate more fully in the
1148 UEFI boot manager protocol. loader.efi will now look at the
1149 BootXXXX environment variable to determine if a specific kernel
1150 or root partition was specified. XXXX is derived from BootCurrent.
1151 efibootmgr(8) manages these standard UEFI variables.
1154 zfsloader's functionality has now been folded into loader.
1155 zfsloader is no longer necessary once you've updated your
1156 boot blocks. For a transition period, we will install a
1157 hardlink for zfsloader to loader to allow a smooth transition
1158 until the boot blocks can be updated (hard link because old
1159 zfs boot blocks don't understand symlinks).
1162 ARM64 now have efifb support, if you want to have serial console
1163 on your arm64 board when an screen is connected and the bootloader
1164 setup a frame buffer for us to use, just add :
1167 in /boot/loader.conf
1168 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
1169 an screen connected as the firmware will setup a frame buffer are that
1170 u-boot will expose as an EFI frame buffer.
1173 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
1174 or take steps to update /etc/passwd before doing installworld on
1175 existing systems. Do not skip the "mergemaster -Fp" step before
1176 installworld, as described in the update procedures near the bottom
1177 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
1178 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
1179 the ntp config file contain options that change file/dir locations.
1180 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
1181 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
1182 taking steps to ensure that all required files/dirs are accessible
1186 Big endian arm support has been removed.
1189 The static environment setup in kernel configs is no longer mutually
1190 exclusive with the loader(8) environment by default. In order to
1191 restore the previous default behavior of disabling the loader(8)
1192 environment if a static environment is present, you must specify
1193 loader_env.disabled=1 in the static environment.
1196 The ABI of syscalls used by management tools like sockstat and
1197 netstat has been broken to allow 32-bit binaries to work on
1198 64-bit kernels without modification. These programs will need
1199 to match the kernel in order to function. External programs may
1200 require minor modifications to accommodate a change of type in
1201 structures from pointers to 64-bit virtual addresses.
1204 On i386 and amd64 atomics are now inlined. Out of tree modules using
1205 atomics will need to be rebuilt.
1208 The '%I' format in the kern.corefile sysctl limits the number of
1209 core files that a process can generate to the number stored in the
1210 debug.ncores sysctl. The '%I' format is replaced by the single digit
1211 index. Previously, if all indexes were taken the kernel would overwrite
1212 only a core file with the highest index in a filename.
1213 Currently the system will create a new core file if there is a free
1214 index or if all slots are taken it will overwrite the oldest one.
1217 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
1218 6.0.1. Please see the 20141231 entry below for information about
1219 prerequisites and upgrading, if you are not already using clang 3.5.0
1223 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
1224 needed to be changed to work with it. This change was made with r335763
1225 and requires a mergemaster / etcupdate / etc to update the installed
1229 r334930 changed the interface between the NFS modules, so they all
1230 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
1233 As of r334391 lld is the default amd64 system linker; it is installed
1234 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
1238 The kernel / userland interface for devinfo changed, so you'll
1239 need a new kernel and userland as a pair for it to work (rebuilding
1240 lib/libdevinfo is all that's required). devinfo and devmatch will
1241 not work, but everything else will when there's a mismatch.
1244 The on-disk format for hwpmc callchain records has changed to include
1245 threadid corresponding to a given record. This changes the field offsets
1246 and thus requires that libpmcstat be rebuilt before using a kernel
1250 The vxge(4) driver has been removed. This driver was introduced into
1251 HEAD one week before the Exar left the Ethernet market and is not
1252 known to be used. If you have device vxge in your kernel config file
1256 The amd64 kernel now requires a ld that supports ifunc to produce a
1257 working kernel, either lld or a newer binutils. lld is built by default
1258 on amd64, and the 'buildkernel' target uses it automatically. However,
1259 it is not the default linker, so building the kernel the traditional
1260 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
1261 binutils port/package). lld will soon be default, and this requirement
1264 NOTE: As of r334391 lld is the default system linker on amd64, and no
1265 workaround is necessary.
1268 The nxge(4) driver has been removed. This driver was for PCI-X 10g
1269 cards made by s2io/Neterion. The company was acquired by Exar and
1270 no longer sells or supports Ethernet products. If you have device
1271 nxge in your kernel config file it must be removed.
1274 The tz database (tzdb) has been updated to 2018e. This version more
1275 correctly models time stamps in time zones with negative DST such as
1276 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
1277 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
1278 time zone abbreviations and the tm_isdst flag.
1281 The ixgb(4) driver has been removed. This driver was for an early and
1282 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
1283 quickly shifted to the long lived ixgbe family. If you have device
1284 ixgb in your kernel config file it must be removed.
1287 The lmc(4) driver has been removed. This was a WAN interface
1288 card that was already reportedly rare in 2003, and had an ambiguous
1289 license. If you have device lmc in your kernel config file it must
1293 Support for Arcnet networks has been removed. If you have device
1294 arcnet or device cm in your kernel config file they must be
1298 Support for FDDI networks has been removed. If you have device
1299 fddi or device fpa in your kernel config file they must be
1303 In addition to supporting RFC 3164 formatted messages, the
1304 syslogd(8) service is now capable of parsing RFC 5424 formatted
1305 log messages. The main benefit of using RFC 5424 is that clients
1306 may now send log messages with timestamps containing year numbers,
1307 microseconds and time zone offsets.
1309 Similarly, the syslog(3) C library function has been altered to
1310 send RFC 5424 formatted messages to the local system logging
1311 daemon. On systems using syslogd(8), this change should have no
1312 negative impact, as long as syslogd(8) and the C library are
1313 updated at the same time. On systems using a different system
1314 logging daemon, it may be necessary to make configuration
1315 adjustments, depending on the software used.
1317 When using syslog-ng, add the 'syslog-protocol' flag to local
1318 input sources to enable parsing of RFC 5424 formatted messages:
1321 unix-dgram("/var/run/log" flags(syslog-protocol));
1324 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
1325 of the 'imuxsock' module to let messages be processed by the
1326 regular RFC 3164/5424 parsing pipeline:
1328 module(load="imuxsock" SysSock.UseSpecialParser="off")
1330 Do note that these changes only affect communication between local
1331 applications and syslogd(8). The format that syslogd(8) uses to
1332 store messages on disk or forward messages to other systems
1333 remains unchanged. syslogd(8) still uses RFC 3164 for these
1334 purposes. Options to customize this behaviour will be added in the
1335 future. Utilities that process log files stored in /var/log are
1336 thus expected to continue to function as before.
1338 __FreeBSD_version has been incremented to 1200061 to denote this
1342 Support for token ring networks has been removed. If you
1343 have "device token" in your kernel config you should remove
1344 it. No device drivers supported token ring.
1347 makefs was modified to be able to tag ISO9660 El Torito boot catalog
1348 entries as EFI instead of overloading the i386 tag as done previously.
1349 The amd64 mkisoimages.sh script used to build amd64 ISO images for
1350 release was updated to use this. This may mean that makefs must be
1351 updated before "make cdrom" can be run in the release directory. This
1352 should be as simple as:
1354 $ cd $SRCDIR/usr.sbin/makefs
1355 $ make depend all install
1358 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
1359 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
1360 Co-existence for the transition period will come shortly. Booting is a
1361 complex environment and test coverage for Lua-enabled loaders has been
1362 thin, so it would be prudent to assume it might not work and make
1363 provisions for backup boot methods.
1366 devmatch functionality has been turned on in devd. It will automatically
1367 load drivers for unattached devices. This may cause unexpected drivers
1368 to be loaded. Please report any problems to current@ and
1372 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
1373 6.0.0. Please see the 20141231 entry below for information about
1374 prerequisites and upgrading, if you are not already using clang 3.5.0
1378 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
1379 This means it is used to link the kernel and userland libraries and
1380 executables, but is not yet installed as /usr/bin/ld by default.
1382 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
1383 WITHOUT_LLD_BOOTSTRAP=yes
1386 On i386, pmtimer has been removed. Its functionality has been folded
1387 into apm. It was a no-op on ACPI in current for a while now (but was
1388 still needed on i386 in FreeBSD 11 and earlier). Users may need to
1389 remove it from kernel config files.
1392 The use of RSS hash from the network card aka flowid has been
1393 disabled by default for lagg(4) as it's currently incompatible with
1394 the lacp and loadbalance protocols.
1396 This can be re-enabled by setting the following in loader.conf:
1397 net.link.lagg.default_use_flowid="1"
1400 The SW_WATCHDOG option is no longer necessary to enable the
1401 hardclock-based software watchdog if no hardware watchdog is
1402 configured. As before, SW_WATCHDOG will cause the software
1403 watchdog to be enabled even if a hardware watchdog is configured.
1406 r326887 fixes the issue described in the 20171214 UPDATING entry.
1407 r326888 flips the switch back to building GELI support always.
1410 r362593 broke ZFS + GELI support for reasons unknown. However,
1411 it also broke ZFS support generally, so GELI has been turned off
1412 by default as the lesser evil in r326857. If you boot off ZFS and/or
1413 GELI, it might not be a good time to update.
1416 PowerPC users must update loader(8) by rebuilding world before
1417 installing a new kernel, as the protocol connecting them has
1418 changed. Without the update, loader metadata will not be passed
1419 successfully to the kernel and users will have to enter their
1420 root partition at the kernel mountroot prompt to continue booting.
1421 Newer versions of loader can boot old kernels without issue.
1424 The LOADER_FIREWIRE_SUPPORT build variable has been renamed to
1425 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
1426 to WITH/OUT_LOADER_GELI.
1429 The naive and non-compliant support of posix_fallocate(2) in ZFS
1430 has been removed as of r325320. The system call now returns EINVAL
1431 when used on a ZFS file. Although the new behavior complies with the
1432 standard, some consumers are not prepared to cope with it.
1433 One known victim is lld prior to r325420.
1436 Building in a FreeBSD src checkout will automatically create object
1437 directories now rather than store files in the current directory if
1438 'make obj' was not ran. Calling 'make obj' is no longer necessary.
1439 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
1440 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
1444 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
1445 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
1446 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
1447 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
1448 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
1449 The UNIFIED_OBJDIR option is a transitional feature that will be
1450 removed for 12.0 release; please migrate to the new format for any
1451 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
1452 than hardcoding paths.
1455 The native-xtools target no longer installs the files by default to the
1456 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
1457 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
1460 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
1461 options are changing from controlling the build if defined / undefined
1462 to controlling the build with explicit 'yes' or 'no' values. They will
1463 shift to WITH/WITHOUT options to match other options in the system.
1466 libstand has turned into a private library for sys/boot use only.
1467 It is no longer supported as a public interface outside of sys/boot.
1470 The arm port has split armv6 into armv6 and armv7. armv7 is now
1471 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
1472 and are running a kernel from before r324363, you will need to add
1473 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
1476 When building multiple kernels using KERNCONF, non-existent KERNCONF
1477 files will produce an error and buildkernel will fail. Previously
1478 missing KERNCONF files silently failed giving no indication as to
1479 why, only to subsequently discover during installkernel that the
1480 desired kernel was never built in the first place.
1483 The default serial number format for CTL LUNs has changed. This will
1484 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
1485 or iSCSI clients care about their LUNs' serial numbers. Users who
1486 require serial number stability should hardcode serial numbers in
1490 For 32-bit arm compiled for hard-float support, soft-floating point
1491 binaries now always get their shared libraries from
1492 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
1493 /usr/libsoft also existed). Only users with a hard-float ld.so, but
1494 soft-float everything else should be affected.
1497 The geli password typed at boot is now hidden. To restore the previous
1498 behavior, see geli(8) for configuration options.
1501 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
1502 sysctl values. Minor nit, but requires a rebuild of both world/kernel
1506 "make check" behavior (made in ^/head@r295380) has been changed to
1507 execute from a limited sandbox, as opposed to executing from
1511 - The "beforecheck" and "aftercheck" targets are now specified.
1512 - ${CHECKDIR} (added in commit noted above) has been removed.
1513 - Legacy behavior can be enabled by setting
1514 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
1516 If the limited sandbox mode is enabled, "make check" will execute
1517 "make distribution", then install, execute the tests, and clean up the
1518 sandbox if successful.
1520 The "make distribution" and "make install" targets are typically run as
1521 root to set appropriate permissions and ownership at installation time.
1522 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
1523 environment if executing "make check" with limited sandbox mode using
1524 an unprivileged user.
1527 Since the switch to GPT disk labels, fsck for UFS/FFS has been
1528 unable to automatically find alternate superblocks. As of r322297,
1529 the information needed to find alternate superblocks has been
1530 moved to the end of the area reserved for the boot block.
1531 Filesystems created with a newfs of this vintage or later
1532 will create the recovery information. If you have a filesystem
1533 created prior to this change and wish to have a recovery block
1534 created for your filesystem, you can do so by running fsck in
1535 foreground mode (i.e., do not use the -p or -y options). As it
1536 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
1537 to which you should answer yes.
1540 As of r321665, an NFSv4 server configuration that services
1541 Kerberos mounts or clients that do not support the uid/gid in
1542 owner/owner_group string capability, must explicitly enable
1543 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
1544 machine's /etc/rc.conf file.
1547 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
1548 Please see the 20141231 entry below for information about prerequisites
1549 and upgrading, if you are not already using clang 3.5.0 or higher.
1552 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
1553 r-commands (rlogin, rsh, etc.) to be built with the base system.
1556 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
1557 a very major ABI incompatible change, so users of FreeBSD/powerpc must
1558 be careful when performing source upgrades. It is best to run
1559 'make installworld' from an alternate root system, either a live
1560 CD/memory stick, or a temporary root partition. Additionally, all ports
1561 must be recompiled. powerpc64 is largely unaffected, except in the case
1562 of 32-bit compatibility. All 32-bit binaries will be affected.
1565 Forward compatibility for the "ino64" project have been committed. This
1566 will allow most new binaries to run on older kernels in a limited
1567 fashion. This prevents many of the common foot-shooting actions in the
1568 upgrade as well as the limited ability to roll back the kernel across
1569 the ino64 upgrade. Complicated use cases may not work properly, though
1570 enough simpler ones work to allow recovery in most situations.
1573 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
1574 if you require the GPL compiler.
1577 The internal ABI used for communication between the NFS kernel modules
1578 was changed by r320085, so __FreeBSD_version was bumped to
1579 ensure all the NFS related modules are updated together.
1582 The ABI of struct event was changed by extending the data
1583 member to 64bit and adding ext fields. For upgrade, same
1584 precautions as for the entry 20170523 "ino64" must be
1588 The GNU roff toolchain has been removed from base. To render manpages
1589 which are not supported by mandoc(1), man(1) can fallback on GNU roff
1590 from ports (and recommends to install it).
1591 To render roff(7) documents, consider using GNU roff from ports or the
1592 heirloom doctools roff toolchain from ports via pkg install groff or
1593 via pkg install heirloom-doctools.
1596 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
1597 smaller runtime footprint builds. This is useful for embedded systems
1598 which only require one chipset support.
1600 If you load it as a module, make sure this is in /boot/loader.conf:
1604 This will load the HAL, all chip/RF backends and if_ath_pci.
1605 If you have if_ath_pci in /boot/loader.conf, ensure it is after
1606 if_ath or it will not load any HAL chipset support.
1608 If you want to selectively load things (eg on cheaper ARM/MIPS
1609 platforms where RAM is at a premium) you should:
1612 * load the chip modules in question
1613 * load ath_rate, ath_dfs
1615 * load if_ath_pci and/or if_ath_ahb depending upon your particular
1616 bus bind type - this is where probe/attach is done.
1618 For further comments/feedback, poke adrian@ .
1621 The "ino64" 64-bit inode project has been committed, which extends
1622 a number of types to 64 bits. Upgrading in place requires care and
1623 adherence to the documented upgrade procedure.
1625 If using a custom kernel configuration ensure that the
1626 COMPAT_FREEBSD11 option is included (as during the upgrade the
1627 system will be running the ino64 kernel with the existing world).
1629 For the safest in-place upgrade begin by removing previous build
1630 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full
1631 procedure documented below under the heading "To rebuild everything and
1632 install it on the current system." Specifically, a reboot is required
1633 after installing the new kernel before installing world. While an
1634 installworld normally works by accident from multiuser after rebooting
1635 the proper kernel, there are many cases where this will fail across this
1636 upgrade and installworld from single user is required.
1639 The NATM framework including the en(4), fatm(4), hatm(4), and
1640 patm(4) devices has been removed. Consumers should plan a
1641 migration before the end-of-life date for FreeBSD 11.
1644 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
1645 diff has not been implemented, if those are needed a newer version of
1646 GNU diff is available via the diffutils package under the gdiff name.
1649 As of r316810 for ipfilter, keep frags is no longer assumed when
1650 keep state is specified in a rule. r316810 aligns ipfilter with
1651 documentation in man pages separating keep frags from keep state.
1652 This allows keep state to be specified without forcing keep frags
1653 and allows keep frags to be specified independently of keep state.
1654 To maintain previous behaviour, also specify keep frags with
1655 keep state (as documented in ipf.conf.5).
1658 arm64 builds now use the base system LLD 4.0.0 linker by default,
1659 instead of requiring that the aarch64-binutils port or package be
1660 installed. To continue using aarch64-binutils, set
1661 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
1664 The UDP optimization in entry 20160818 that added the sysctl
1665 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
1666 packets will no longer be treated as L3 broadcast packets.
1669 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
1670 use any explicitly assigned loopback address available in the jail
1671 instead of using the first assigned address of the jail.
1674 The ctl.ko module no longer implements the iSCSI target frontend:
1675 cfiscsi.ko does instead.
1677 If building cfiscsi.ko as a kernel module, the module can be loaded
1678 via one of the following methods:
1679 - `cfiscsi_load="YES"` in loader.conf(5).
1680 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
1681 - ctladm(8)/ctld(8), when compiled with iSCSI support
1682 (`WITH_ISCSI=yes` in src.conf(5))
1684 Please see cfiscsi(4) for more details.
1687 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
1688 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
1689 same source (previously, the dependency of mmcsd.ko on mmc.ko was
1690 missing, but mmcsd.ko now will refuse to load if it is incompatible
1694 The syntax of ipfw(8) named states was changed to avoid ambiguity.
1695 If you have used named states in the firewall rules, you need to modify
1696 them after installworld and before rebooting. Now named states must
1697 be prefixed with colon.
1700 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
1701 removed as the userland we provide cannot use them. The KMS version
1702 (sys/dev/drm2) supports the same hardware.
1705 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
1706 Please see the 20141231 entry below for information about prerequisites
1707 and upgrading, if you are not already using clang 3.5.0 or higher.
1710 The code that provides support for ZFS .zfs/ directory functionality
1711 has been reimplemented. It's not possible now to create a snapshot
1712 by mkdir under .zfs/snapshot/. That should be the only user visible
1716 EISA bus support has been removed. The WITH_EISA option is no longer
1720 MCA bus support has been removed.
1723 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
1724 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
1727 The EM_MULTIQUEUE kernel configuration option is deprecated now that
1728 the em(4) driver conforms to iflib specifications.
1731 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
1732 IFLIB. If you have a custom kernel configuration that excludes em(4)
1733 but you use igb(4), you need to re-add em(4) to your custom
1737 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
1738 Please see the 20141231 entry below for information about prerequisites
1739 and upgrading, if you are not already using clang 3.5.0 or higher.
1742 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
1743 Please see the 20141231 entry below for information about prerequisites
1744 and upgrading, if you are not already using clang 3.5.0 or higher.
1747 The layout of the pmap structure has changed for powerpc to put the pmap
1748 statistics at the front for all CPU variations. libkvm(3) and all tools
1749 that link against it need to be recompiled.
1752 isl(4) and cyapa(4) drivers now require a new driver,
1753 chromebook_platform(4), to work properly on Chromebook-class hardware.
1754 On other types of hardware the drivers may need to be configured using
1755 device hints. Please see the corresponding manual pages for details.
1758 The urtwn(4) driver was merged into rtwn(4) and now consists of
1759 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
1761 Also, firmware for RTL8188CE was renamed due to possible name
1762 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
1765 GNU rcs has been removed from base. It is available as packages:
1766 - rcs: Latest GPLv3 GNU rcs version.
1767 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
1771 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
1772 modules now requires that the kernel configuration contain the
1773 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
1776 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
1777 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
1780 Relocatable object files with the extension of .So have been renamed
1781 to use an extension of .pico instead. The purpose of this change is
1782 to avoid a name clash with shared libraries on case-insensitive file
1783 systems. On those file systems, foo.So is the same file as foo.so.
1786 GNU rcs has been turned off by default. It can (temporarily) be built
1787 again by adding WITH_RCS knob in src.conf.
1788 Otherwise, GNU rcs is available from packages:
1789 - rcs: Latest GPLv3 GNU rcs version.
1790 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
1793 The backup_uses_rcs functionality has been removed from rc.subr.
1796 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
1797 two separate components, QUEUE_MACRO_DEBUG_TRACE and
1798 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
1799 QUEUE_MACRO_DEBUG behavior.
1802 r304787 changed some ioctl interfaces between the iSCSI userspace
1803 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1804 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1808 The UDP receive code has been updated to only treat incoming UDP
1809 packets that were addressed to an L2 broadcast address as L3
1810 broadcast packets. It is not expected that this will affect any
1811 standards-conforming UDP application. The new behaviour can be
1812 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1816 Remove the openbsd_poll system call.
1817 __FreeBSD_version has been bumped because of this.
1820 The stable/11 branch has been created from head@r302406.
1822 After branch N is created, entries older than the N-2 branch point are removed
1823 from this file. After stable/14 is branched and current becomes FreeBSD 15,
1824 entries older than stable/12 branch point will be removed from current's
1831 Sometimes, obscure build problems are the result of environment
1832 poisoning. This can happen because the make utility reads its
1833 environment when searching for values for global variables. To run
1834 your build attempts in an "environmental clean room", prefix all make
1835 commands with 'env -i '. See the env(1) manual page for more details.
1836 Occasionally a build failure will occur with "make -j" due to a race
1837 condition. If this happens try building again without -j, and please
1838 report a bug if it happens consistently.
1840 When upgrading from one major version to another it is generally best to
1841 upgrade to the latest code in the currently installed branch first, then
1842 do an upgrade to the new branch. This is the best-tested upgrade path,
1843 and has the highest probability of being successful. Please try this
1844 approach if you encounter problems with a major version upgrade. Since
1845 the stable 4.x branch point, one has generally been able to upgrade from
1846 anywhere in the most recent stable branch to head / current (or even the
1847 last couple of stable branches). See the top of this file when there's
1850 The update process will emit an error on an attempt to perform a build
1851 or install from a FreeBSD version below the earliest supported version.
1852 When updating from an older version the update should be performed one
1853 major release at a time, including running `make delete-old` at each
1856 When upgrading a live system, having a root shell around before
1857 installing anything can help undo problems. Not having a root shell
1858 around can lead to problems if pam has changed too much from your
1859 starting point to allow continued authentication after the upgrade.
1861 This file should be read as a log of events. When a later event changes
1862 information of a prior event, the prior event should not be deleted.
1863 Instead, a pointer to the entry with the new information should be
1864 placed in the old entry. Readers of this file should also sanity check
1865 older entries before relying on them blindly. Authors of new entries
1866 should write them with this in mind.
1870 When upgrading the boot ZFS pool to a new version (via zpool upgrade),
1871 always follow these three steps:
1873 1) recompile and reinstall the ZFS boot loader and boot block
1874 (this is part of "make buildworld" and "make installworld")
1876 2) update the ZFS boot block on your boot drive (only required when
1877 doing a zpool upgrade):
1879 When booting on x86 via BIOS, use the following to update the ZFS boot
1880 block on the freebsd-boot partition of a GPT partitioned drive ada0:
1881 gpart bootcode -p /boot/gptzfsboot -i $N ada0
1882 The value $N will typically be 1. For EFI booting, see EFI notes.
1884 3) zpool upgrade the root pool. New bootblocks will work with old
1885 pools, but not vice versa, so they need to be updated before any
1888 Non-boot pools do not need these updates.
1893 There are two locations the boot loader can be installed into. The
1894 current location (and the default) is \efi\freebsd\loader.efi and using
1895 efibootmgr(8) to configure it. The old location, that must be used on
1896 deficient systems that don't honor efibootmgr(8) protocols, is the
1897 fallback location of \EFI\BOOT\BOOTxxx.EFI. Generally, you will copy
1898 /boot/loader.efi to this location, but on systems installed a long time
1899 ago the ESP may be too small and /boot/boot1.efi may be needed unless
1900 the ESP has been expanded in the meantime.
1902 Recent systems will have the ESP mounted on /boot/efi, but older ones
1903 may not have it mounted at all, or mounted in a different
1904 location. Older arm SD images with MBR used /boot/msdos as the
1905 mountpoint. The ESP is a MSDOS filesystem.
1907 The EFI boot loader rarely needs to be updated. For ZFS booting,
1908 however, you must update loader.efi before you do 'zpool upgrade' the
1909 root zpool, otherwise the old loader.efi may reject the upgraded zpool
1910 since it does not automatically understand some new features.
1912 See loader.efi(8) and uefi(8) for more details.
1916 If you are updating from a prior version of FreeBSD (even one just
1917 a few days old), you should follow this procedure. It is the most
1918 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1920 make kernel-toolchain
1921 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1922 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1924 To test a kernel once
1925 ---------------------
1926 If you just want to boot a kernel once (because you are not sure
1927 if it works, or if you want to boot a known bad kernel to provide
1928 debugging information) run
1929 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1930 nextboot -k testkernel
1932 To rebuild everything and install it on the current system.
1933 -----------------------------------------------------------
1934 # Note: sometimes if you are running current you gotta do more than
1935 # is listed here if you are upgrading from a really old current.
1937 <make sure you have good level 0 dumps>
1939 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1940 make installkernel KERNCONF=YOUR_KERNEL_HERE
1942 <reboot in single user> [3]
1949 To cross-install current onto a separate partition
1950 --------------------------------------------------
1951 # In this approach we use a separate partition to hold
1952 # current's root, 'usr', and 'var' directories. A partition
1953 # holding "/", "/usr" and "/var" should be about 2GB in
1956 <make sure you have good level 0 dumps>
1959 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1960 <maybe newfs current's root partition>
1961 <mount current's root partition on directory ${CURRENT_ROOT}>
1962 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1963 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1964 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1965 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1966 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1967 <reboot into current>
1968 <do a "native" rebuild/install as described in the previous section>
1969 <maybe install compatibility libraries from ports/misc/compat*>
1973 To upgrade in-place from stable to current
1974 ----------------------------------------------
1975 <make sure you have good level 0 dumps>
1977 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1978 make installkernel KERNCONF=YOUR_KERNEL_HERE
1980 <reboot in single user> [3]
1987 Make sure that you've read the UPDATING file to understand the
1988 tweaks to various things you need. At this point in the life
1989 cycle of current, things change often and you are on your own
1990 to cope. The defaults can also change, so please read ALL of
1991 the UPDATING entries.
1993 Also, if you are tracking -current, you must be subscribed to
1994 freebsd-current@freebsd.org. Make sure that before you update
1995 your sources that you have read and understood all the recent
1996 messages there. If in doubt, please track -stable which has
1997 much fewer pitfalls.
1999 [1] If you have third party modules, such as vmware, you should disable
2000 them at this point so they don't crash your system on
2001 reboot. Alternatively, you should rebuild all the modules you have in
2002 your system and install them as well. If you are running -current, you
2003 should seriously consider placing all sources to all the modules for
2004 your system (or symlinks to them) in /usr/local/sys/modules so this
2005 happens automatically. If all your modules come from ports, then adding
2006 the port origin directories to PORTS_MODULES instead is also automatic
2008 PORTS_MODULES+=x11/nvidia-driver
2010 [3] From the bootblocks, boot -s, and then do
2014 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed
2015 cd src # full path to source
2016 adjkerntz -i # if CMOS is wall time
2017 Also, when doing a major release upgrade, it is required that you boot
2018 into single user mode to do the installworld.
2020 [4] Note: This step is non-optional. Failure to do this step
2021 can result in a significant reduction in the functionality of the
2022 system. Attempting to do it by hand is not recommended and those
2023 that pursue this avenue should read this file carefully, as well
2024 as the archives of freebsd-current and freebsd-hackers mailing lists
2025 for potential gotchas. See etcupdate(8) for more information.
2027 [5] Usually this step is a no-op. However, from time to time
2028 you may need to do this if you get unknown user in the following
2031 [6] This only deletes old files and directories. Old libraries
2032 can be deleted by "make delete-old-libs", but you have to make
2033 sure that no program is using those libraries anymore.
2035 [8] The new kernel must be able to run existing binaries used by an
2036 installworld. When upgrading across major versions, the new kernel's
2037 configuration must include the correct COMPAT_FREEBSD<n> option for
2038 existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure
2039 to do so may leave you with a system that is hard to boot to recover. A
2040 GENERIC kernel will include suitable compatibility options to run
2041 binaries from older branches. Note that the ability to run binaries
2042 from unsupported branches is not guaranteed.
2044 Make sure that you merge any new devices from GENERIC since the
2045 last time you updated your kernel config file. Options also
2046 change over time, so you may need to adjust your custom kernels
2049 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2050 "?=" instead of the "=" assignment operator, so that buildworld can
2051 override the CPUTYPE if it needs to.
2053 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2054 not on the command line, or in /etc/make.conf. buildworld will
2055 warn if it is improperly defined.
2058 This file contains a list, in reverse chronological order, of major
2059 breakages in tracking -current. It is not guaranteed to be a complete
2060 list of such breakages, and only contains entries since September 23, 2011.
2061 If you need to see UPDATING entries from before that date, you will need
2062 to fetch an UPDATING file from an older FreeBSD release.
2064 Copyright information:
2066 Copyright 1998-2009 M. Warner Losh <imp@FreeBSD.org>
2068 Redistribution, publication, translation and use, with or without
2069 modification, in full or in part, in any form or format of this
2070 document are permitted without further permission from the author.
2072 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2073 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2074 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2075 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2076 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2077 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2078 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2079 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2080 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2081 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2082 POSSIBILITY OF SUCH DAMAGE.
2084 Contact Warner Losh if you have any questions about your use of