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 14.x IS SLOW:
16 FreeBSD 14.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 CAM has been mechanically updated s/u_int(64|32|16|8)_t/uint\1_t/g
32 to move to the standard uintXX_t types from the old, traditional
33 BSD u_intXX_t types. This should be a NOP, but may cause problems
34 for out of tree changes. The SIMs were not updated since most of
35 the old u_intXX_t uses weren't due to CAM interfaces.
38 The heuristic for detecting old chromebooks with an EC bug that requires
39 atkbdc driver workarounds has changed. There should be no functional
40 change, but if your old chromebook's keyboard stops working, please
41 file a PR and assign it to imp.
44 OpenSSL has been updated to version 3.0, including changes throughout
45 the base system. It is important to rebuild third-party software
49 To enable pf rdr rules for connections initiated from the host, pf
50 filter rules can be optionally enabled for packets delivered
51 locally. This can change the behavior of rules which match packets
52 delivered to lo0. To enable this feature:
54 sysctl net.pf.filter_local=1
57 When enabled, its best to ensure that packets delivered locally are not
58 filtered, e.g. by adding a 'skip on lo' rule.
61 Improvements to libtacplus(8) mean that tacplus.conf(5) now
62 follows POSIX shell syntax rules. This may cause TACACS+
63 authentication to fail if the shared secret contains a single
64 quote, double quote, or backslash character which isn't
65 already properly quoted or escaped.
68 Belatedly switch the default nvme block device on x86 from nvd to nda.
69 nda created nvd compatibility links by default, so this should be a
70 nop. If this causes problems for your application, set hw.nvme.use_nvd=1
71 in your loader.conf or add `options NVME_USE_NVD=1` to your kernel
72 config. To disable the nvd compatibility aliases, add
73 kern.cam.nda.nvd_compat=0 to loader.conf. The default has been nda on
74 all non-x86 platforms for some time now. If you need to fall back,
75 please email imp@freebsd.org about why.
78 Remove portsnap(8). Users are encouraged to obtain the ports tree
82 Add jobs.mk to save typing. Enables -j${JOB_MAX} and logging
86 make -j${JOB_MAX} buildworld > ../buildworld.log 2>&1
88 where JOB_MAX is derrived from ncpus in local.sys.mk if not set in env.
91 Video related devices for some arm devices have been renamed.
92 If you have a custom kernel config and want to use hdmi output on
93 IMX6 board you need to add "device dwc_hdmi" "device imx6_hdmi" and
94 "device imx6_ipu" to it.
95 If you have a custom kernel config and want to use hdmi output on
96 TI AM335X board you need to add "device tda19988" to it.
97 If you add "device hdmi" in it you need to remove it as it doesn't
101 Introduce new kernel options KBD_DELAY1 and KBD_DELAY2. See atkbdc(4)
105 sshd now defaults to having X11Forwarding disabled, following upstream.
106 Administrators who wish to enable X11Forwarding should add
107 `X11Forwarding yes` to /etc/ssh/sshd_config.
110 Since commit 75d41cb6967 Huawei 3G/4G LTE Mobile Devices do not default
111 to ECM, but NCM mode and need u3g and ucom modules loaded. See cdce(4).
114 As of commit 7c40e2d5f685, the dependency on netlink(4) has been added
115 to the linux_common(4) module. Users relying on linux_common may need
116 to complile netlink(4) module if it is not present in their kernel.
119 The WITHOUT_CXX option has been removed. C++ components in the base
120 system are now built unconditionally.
123 LinuxKPI pci.h changes may require out-of-tree drivers to be recompiled.
124 Bump _FreeBSD_version to 1400078 to be able to detect this change.
127 llvm-objump is now always installed as objdump. Previously there was
128 no /usr/bin/objdump unless the WITH_LLVM_BINUTILS knob was used.
130 Some LLVM objdump options have a different output format compared to
131 GNU objdump; readelf is available for inspecting ELF files, and GNU
132 objdump is available from the devel/binutils port or package.
135 dma(8) has replaced sendmail(8) as the default mta. For people willing
136 to reenable sendmail(8):
138 $ cp /usr/share/examples/sendmail/mailer.conf /etc/mail/mailer.conf
140 and add sendmail_enable="YES" to rc.conf.
143 hw.bus.disable_failed_devices has changed from 'false' to 'true' by
144 default. Now if newbus succeeds in probing a device, but fails to attach
145 the device, we'll disable the device. In the past, we'd keep retrying
146 the device on each new driver loaded. To get that behavior now, one
147 needs to use devctl to re-enable the device, and reprobe it (or set
148 the sysctl/tunable hw.bus.disable_failed_devices=false).
150 NOTE: This was reverted 20221205 due to unexpected compatibility issues
153 pf no longer accepts 'scrub fragment crop' or 'scrub fragment drop-ovl'.
154 These configurations are no longer automatically reinterpreted as
155 'scrub fragment reassemble'.
158 The WITHOUT_CLANG_IS_CC option has been removed. When Clang is enabled
159 it is always installed as /usr/bin/cc (and c++, cpp).
162 Some programs have been moved into separate packages. It is recommended
163 for pkgbase users to do:
165 pkg install FreeBSD-dhclient FreeBSD-geom FreeBSD-resolvconf \
166 FreeBSD-devd FreeBSD-devmatch
168 after upgrading to restore all the component that were previously
172 LinuxKPI pm.h changes require an update to the latest drm-kmod version
173 before re-compiling to avoid errors.
176 The macros provided for the manipulation of CPU sets (e.g. CPU_AND)
177 have been modified to take 2 source arguments instead of only 1.
178 Externally maintained sources that use these macros will have to
179 be adapted. The FreeBSD version has been bumped to 1400046 to
183 A number of the kernel include files are able to be included by
184 themselves. A test has been added to buildworld to enforce this.
187 Remove mips as a recognized target. This starts the decommissioning of
188 mips support in FreeBSD. mips related items will be removed wholesale in
189 the coming days and weeks.
191 This broke the NO_CLEAN build for some people. Either do a clean build
193 lib/clang/include/llvm/Config/Targets.def
194 lib/clang/include/llvm/Config/AsmParsers.def
195 lib/clang/include/llvm/Config/Disassemblers.def
196 lib/clang/include/llvm/Config/AsmPrinters.def
197 before the build to force everything to rebuild that needs to.
200 Unbound support for RFC8375: The special-use domain 'home.arpa' is
201 by default blocked. To unblock it use a local-zone nodefault
202 statement in unbound.conf:
203 local-zone: "home.arpa." nodefault
205 Or use another type of local-zone to override with your choice.
207 The reason for this is discussed in Section 6.1 of RFC8375:
208 Because 'home.arpa.' is not globally scoped and cannot be secured
209 using DNSSEC based on the root domain's trust anchor, there is no way
210 to tell, using a standard DNS query, in which homenet scope an answer
211 belongs. Consequently, users may experience surprising results with
212 such names when roaming to different homenets.
215 Commit b8d60729deef changed the TCP congestion control framework so
216 that any of the included congestion control modules could be
217 the single module built into the kernel. Previously newreno
218 was automatically built in through direct reference. As of
219 this commit you are required to declare at least one congestion
220 control module (e.g. 'options CC_NEWRENO') and to also declare a
221 default using the CC_DEFAULT option (e.g. options CC_DEFAULT="newreno\").
222 The GENERIC configuration includes CC_NEWRENO and defines newreno
223 as the default. If no congestion control option is built into the
224 kernel and you are including networking, the kernel compile will
225 fail. Also if no default is declared the kernel compile will fail.
228 Mips has been removed from universe builds. It will be removed from the
232 Commit f0c9847a6c47 changed the arguments for VOP_ALLOCATE.
233 The NFS modules must be rebuilt from sources and any out
234 of tree file systems that implement their own VOP_ALLOCATE
235 may need to be modified.
238 The synchronous PPP kernel driver sppp(4) has been removed.
239 The cp(4) and ce(4) drivers are now always compiled with netgraph(4)
240 support, formerly enabled by NETGRAPH_CRONYX option.
243 sh(1) is now the default shell for the root user. To force root to use
244 the csh shell, please run the following command as root:
249 Ncurses distribution has been split between libtinfow and libncurses
250 with libncurses.so becoming a linker (ld) script to seamlessly link
251 to libtinfow as needed. Bump _FreeBSD_version to 1400035 to reflect
255 As of commit 8160a0f62be6, the dummynet module no longer depends on the
256 ipfw module. Dummynet can now be used by pf as well as ipfw. As such
257 users who relied on this dependency may need to include ipfw in the
258 list of modules to load on their systems.
261 As of commit 903873ce1560, the mixer(8) utility has got a slightly
262 new syntax. Please refer to the mixer(8) manual page for more
263 information. The old mixer utility can be installed from ports:
264 audio/freebsd-13-mixer
267 As of commit 55089ef4f8bb, the global variable nfs_maxcopyrange has
268 been deleted from the nfscommon.ko. As such, nfsd.ko must be built
269 from up to date sources to avoid an undefined reference when
273 As of commit 62ca9fc1ad56 OpenSSL no longer enables kernel TLS
274 by default. Users can enable kernel TLS via the "KTLS" SSL
275 option. This can be enabled globally by using a custom
276 OpenSSL config file via OPENSSL_CONF or via an
277 application-specific configuration option for applications
278 which permit setting SSL options via SSL_CONF_cmd(3).
281 Commit 3ad1e1c1ce20 changed the internal KAPI between the NFS
282 modules. Therefore, all need to be rebuilt from sources.
285 Commit b69019c14cd8 removes pf's DIOCGETSTATESNV ioctl.
286 As of be70c7a50d32 it is no longer used by userspace, but it does mean
287 users may not be able to enumerate pf states if they update the kernel
288 past b69019c14cd8 without first updating userspace past be70c7a50d32.
291 As of commit 01ad0c007964 if_bridge member interfaces can no longer
292 change their MTU. Changing the MTU of the bridge itself will change the
293 MTU on all member interfaces instead.
296 Commit ee29e6f31111 changed the internal KAPI between the nfscommon
297 and nfsd modules. Therefore, both need to be rebuilt from sources.
298 Bump __FreeBSD_version to 1400026 for this KAPI change.
301 The 20210707 awk update brought in a change in behavior. This has
302 been corrected as of d4d252c49976. Between these dates, if you
303 installed a new awk binary, you may not be able to build a new
304 kernel because the change in behavior affected the genoffset
305 script used to build the kernel. If you did update, the fix is
306 to update your sources past the above hash and do
309 % sudo -E make install
310 to enable building kernels again.
313 Commit 1e0a518d6548 changed the internal KAPI between the NFS
314 modules. They all need to be rebuilt from sources. I did not
315 bump __FreeBSD_version, since it was bumped recently.
318 awk has been updated to the latest one-true-awk version 20210215.
319 This contains a number of minor bug fixes.
322 The NFSv4 client now uses the highest minor version of NFSv4
323 supported by the NFSv4 server by default instead of minor version 0,
325 The "minorversion" mount option may be used to override this default.
328 Bump __FreeBSD_version to 1400024 for LinuxKPI changes.
329 Most notably netdev.h can change now as the (last) dependencies
330 (mlx4/ofed) are now using struct ifnet directly, but also for PCI
331 additions and others.
334 The directory "blacklisted" under /usr/share/certs/ has been
335 renamed to "untrusted".
338 svnlite has been removed from base. Should you need svn for any reason
339 please install the svn package or port.
342 Commit e1a907a25cfa changed the internal KAPI between the krpc
343 and nfsserver. As such, both modules must be rebuilt from
344 sources. Bump __FreeBSD_version to 1400022.
347 The an(4) driver has been removed from FreeBSD.
350 The vendor/openzfs branch was renamed to vendor/openzfs/legacy to
351 start tracking OpenZFS upstream more closely. Please see
352 https://lists.freebsd.org/archives/freebsd-current/2021-June/000153.html
353 for details on how to correct any errors that might result. The
354 short version is that you need to remove the old branch locally:
355 git update-ref -d refs/remotes/freebsd/vendor/openzfs
356 (assuming your upstream origin is named 'freebsd').
359 Commits 17accc08ae15 and de102f870501 add new files to LinuxKPI
360 which break drm-kmod. In addition various other additions where
361 committed. Bump __FreeBSD_version to 1400015 to be able to
365 Commit ca179c4d74f2 changed the package in which the OpenSSL
366 libraries and utilities are packaged.
367 It is recommended for pkgbase user to do:
368 pkg install -f FreeBSD-openssl
369 before pkg upgrade otherwise some dependencies might not be met
370 and pkg will stop working as libssl will not be present anymore
374 Commit 875977314881 changed the internal KAPI between
375 the nfsd and nfscommon modules. As such these modules
376 need to be rebuilt from sources.
377 Without this patch in your NFSv4.1/4.2 server, enabling
378 delegations by setting vfs.nfsd.issue_delegations non-zero
382 Commit 7763814fc9c2 changed the internal KAPI between
383 the krpc and NFS. As such, the krpc, nfscommon and
384 nfscl modules must all be rebuilt from sources.
385 Without this patch, NFSv4.1/4.2 mounts should not
386 be done with the nfscbd(8) daemon running, to avoid
387 needing a working back channel for server->client RPCs.
390 Commit 01ae8969a9ee fixed the NFSv4.1/4.2 server so that it
391 handles binding of the back channel as required by RFC5661.
392 Until this patch is in your server, avoid use of the "nconnects"
393 mount option for Linux NFSv4.1/4.2 mounts.
396 For 64-bit architectures the base system is now built with Position
397 Independent Executable (PIE) support enabled by default. It may be
398 disabled using the WITHOUT_PIE knob. A clean build is required.
401 Various LinuxKPI functionality was added which conflicts with DRM.
402 Please update your drm-kmod port to after the __FreeBSD_version 1400003
406 PC Card attachments for all devices have been removed. In the case of
407 wi and cmx, the entire drivers were removed because they were only
408 PC Card devices. FreeBSD_version 1300134 should be used for this
409 since it was bumped so recently.
412 Transport-independent parts of HID support have been split off the USB
413 code in to separate subsystem. Kernel configs which include one of
414 ums, ukbd, uhid, atp, wsp, wmt, uaudio, ugold or ucycom drivers should
415 be updated with adding of "device hid" line.
418 ncurses installation has been modified to only keep the widechar
419 enabled version. Incremental build is broken for that change, so it
420 requires a clean build.
423 The FreeBSD project has migrated from Subversion to Git. Temporary
424 instructions can be found at
425 https://github.com/bsdimp/freebsd-git-docs/blob/main/src-cvt.md
426 and other documents in that repo.
429 The services database has been updated to cover more of the basic
430 services expected in a modern system. The database is big enough
431 that it will cause issues in mergemaster in Releases previous to
432 12.2 and 11.3, or in very old current systems from before r358154.
435 Obsolete in-tree GDB 6.1.1 has been removed. GDB (including kgdb)
436 may be installed from ports or packages.
439 ping6 has been merged into ping. It can now be called as "ping -6".
440 See ping(8) for details.
443 Default value of net.add_addr_allfibs has been changed to 0.
444 If you have multi-fib configuration and rely on existence of all
445 interface routes in every fib, you need to set the above sysctl to 1.
448 The internal pre-processor in the calendar(1) program has been
449 extended to support more C pre-processor commands (e.g. #ifdef, #else,
450 and #undef) and to detect unbalanced conditional statements.
451 Error messages have been extended to include the filename and line
452 number if processing stops to help fixing malformed data files.
455 All the data files for the calendar(1) program, except calendar.freebsd,
456 have been moved to the deskutils/calendar-data port, much like the
457 jewish calendar entries were moved to deskutils/hebcal years ago. After
458 make delete-old-files, you need to install it to retain full
459 functionality. calendar(1) will issue a reminder for files it can't
463 LINT files are no longer generated. We now include the relevant NOTES
464 files. Note: This may cause conflicts with updating in some cases.
465 find sys -name LINT\* -delete
466 is suggested across this commit to remove the generated LINT files.
468 If you have tried to update with generated files there, the svn
469 command you want to un-auger the tree is
472 and then do the above find from the top level. Substitute 'amd64'
473 above with where the error message indicates a conflict.
476 OpenZFS support has been integrated. Do not upgrade root pools until
477 the loader is updated to support zstd. Furthermore, we caution against
478 'zpool upgrade' for the next few weeks. The change should be transparent
479 unless you want to use new features.
481 Not all "NO_CLEAN" build scenarios work across these changes. Many
482 scenarios have been tested and fixed, but rebuilding kernels without
483 rebuilding world may fail.
485 The ZFS cache file has moved from /boot to /etc to match the OpenZFS
486 upstream default. A fallback to /boot has been added for mountroot.
488 Pool auto import behavior at boot has been moved from the kernel module
489 to an explicit "zpool import -a" in one of the rc scripts enabled by
490 zfs_enable=YES. This means your non-root zpools won't auto import until
491 you upgrade your /etc/rc.d files.
494 The resume code now notifies devd with the 'kernel' system
495 rather than the old 'kern' subsystem to be consistent with
496 other use. The old notification will be created as well, but
497 will be removed prior to FreeBSD 14.0.
500 r362275 changed the internal API between the kernel RPC and the
501 NFS modules. As such, all the modules must be recompiled from
505 r364330 modified the internal API used between the NFS modules.
506 As such, all the NFS modules must be re-compiled from sources.
509 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
510 been upgraded to 11.0.0. Please see the 20141231 entry below for
511 information about prerequisites and upgrading, if you are not already
512 using clang 3.5.0 or higher.
515 r364092 modified the internal ABI used between the kernel NFS
516 modules. As such, all of these modules need to be rebuilt
517 from sources, so a version bump was done.
520 Makefile.inc has been updated to work around the issue documented in
521 20200729. It was a case where the optimization of using symbolic links
522 to point to binaries created a situation where we'd run new binaries
523 with old libraries starting midway through the installworld process.
526 r363679 has redefined some undefined behavior in regcomp(3); notably,
527 extraneous escapes of most ordinary characters will no longer be
528 accepted. An exp-run has identified all of the problems with this in
529 ports, but other non-ports software may need extra escapes removed to
530 continue to function.
532 Because of this change, installworld may encounter the following error
533 from rtld: Undefined symbol "regcomp@FBSD_1.6" -- It is imperative that
534 you do not halt installworld. Instead, let it run to completion (whether
535 successful or not) and run installworld once more.
538 A new implementation of bc and dc has been imported in r362681. This
539 implementation corrects non-conformant behavior of the previous bc
540 and adds GNU bc compatible options. It offers a number of extensions,
541 is much faster on large values, and has support for message catalogs
542 (a number of languages are already supported, contributions of further
543 languages welcome). The option WITHOUT_GH_BC can be used to build the
544 world with the previous versions of bc and dc.
547 r362639 changed the internal API used between the NFS kernel modules.
548 As such, they all need to be rebuilt from sources.
551 r362158 changed the arguments for VFS_CHECKEXP(). As such, any
552 out of tree file systems need to be modified and rebuilt.
553 Also, any file systems that are modules must be rebuilt.
556 read(2) of a directory fd is now rejected by default. root may
557 re-enable it for system root only on non-ZFS filesystems with the
558 security.bsd.allow_read_dir sysctl(8) MIB if
559 security.bsd.suser_enabled=1.
561 It may be advised to setup aliases for grep to default to `-d skip` if
562 commonly non-recursively grepping a list that includes directories and
563 the potential for the resulting stderr output is not tolerable. Example
564 aliases are now installed, commented out, in /root/.cshrc and
568 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
569 been upgraded to 10.0.1. Please see the 20141231 entry below for
570 information about prerequisites and upgrading, if you are not already
571 using clang 3.5.0 or higher.
574 Support for obsolete compilers has been removed from the build system.
575 Clang 6 and GCC 6.4 are the minimum supported versions.
578 closefrom(2) has been moved under COMPAT12, and replaced in libc with a
579 stub that calls close_range(2). If using a custom kernel configuration,
580 you may want to ensure that the COMPAT_FREEBSD12 option is included, as
581 a slightly older -CURRENT userland and older FreeBSD userlands may not
582 be functional without closefrom(2).
585 Upstream DTS from Linux 5.6 was merged and they now have the SID
586 and THS (Secure ID controller and THermal Sensor) node present.
587 The DTB overlays have now been removed from the tree for the H3/H5 and
588 A64 SoCs and the aw_sid and aw_thermal driver have been updated to
589 deal with upstream DTS. If you are using those overlays you need to
590 remove them from loader.conf and update the DTBs on the FAT partition.
593 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
594 been upgraded to 10.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 The amd(8) automount daemon has been removed from the source tree.
600 As of FreeBSD 10.1 autofs(5) is the preferred tool for automounting.
601 amd is still available in the sysutils/am-utils port.
604 Removed brooktree driver (bktr.4) from the tree.
607 The WITH_GPL_DTC option has been removed. The BSD-licenced device tree
608 compiler in usr.bin/dtc is used on all architectures which use dtc, and
609 the GPL dtc is available (if needed) from the sysutils/dtc port.
612 The WITHOUT_LLVM_LIBUNWIND option has been removed. LLVM's libunwind
613 is used by all supported CPU architectures.
616 GCC 4.2.1 has been removed from the tree. The WITH_GCC,
617 WITH_GCC_BOOTSTRAP, and WITH_GNUCXX options are no longer available.
618 Users who wish to build FreeBSD with GCC must use the external toolchain
622 ncurses has been updated to a newer version (6.2-20200215). Given the ABI
623 has changed, users will have to rebuild all the ports that are linked to
627 The size of struct vnet and the magic cookie have changed.
628 Users need to recompile libkvm and all modules using VIMAGE
629 together with their new kernel.
632 Defining the long deprecated NO_CTF, NO_DEBUG_FILES, NO_INSTALLLIB,
633 NO_MAN, NO_PROFILE, and NO_WARNS variables is now an error. Update
634 your Makefiles and scripts to define MK_<var>=no instead as required.
636 One exception to this is that program or library Makefiles should
637 define MAN to empty rather than setting MK_MAN=no.
640 Clang/LLVM is now the default compiler and LLD the default
644 make universe no longer uses GCC 4.2.1 on any architectures.
645 Architectures not supported by in-tree Clang/LLVM require an
646 external toolchain package.
649 GCC 4.2.1 is now not built by default, as part of the GCC 4.2.1
650 retirement plan. Specifically, the GCC, GCC_BOOTSTRAP, and GNUCXX
651 options default to off for all supported CPU architectures. As a
652 short-term transition aid they may be enabled via WITH_* options.
653 GCC 4.2.1 is expected to be removed from the tree on 2020-03-31.
656 Support for armv5 has been disconnected and is being removed. The
657 machine combination MACHINE=arm MACHINE_ARCH=arm is no longer valid.
658 You must now use a MACHINE_ARCH of armv6 or armv7. The default
659 MACHINE_ARCH for MACHINE=arm is now armv7.
662 Clang/LLVM is now the default compiler for all powerpc architectures.
663 LLD is now the default linker for powerpc64. The change for powerpc64
664 also includes a change to the ELFv2 ABI, incompatible with the existing
668 Kernel-loadable random(4) modules are no longer unloadable.
671 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
672 been upgraded to 9.0.1. Please see the 20141231 entry below for
673 information about prerequisites and upgrading, if you are not already
674 using clang 3.5.0 or higher.
677 r355677 has modified the internal interface used between the
678 NFS modules in the kernel. As such, they must all be upgraded
679 simultaneously. I will do a version bump for this.
682 The root certificates of the Mozilla CA Certificate Store have been
683 imported into the base system and can be managed with the certctl(8)
684 utility. If you have installed the security/ca_root_nss port or package
685 with the ETCSYMLINK option (the default), be advised that there may be
686 differences between those included in the port and those included in
687 base due to differences in nss branch used as well as general update
688 frequency. Note also that certctl(8) cannot manage certs in the
689 format used by the security/ca_root_nss port.
692 The amd(8) automount daemon has been disabled by default, and will be
693 removed in the future. As of FreeBSD 10.1 the autofs(5) is available
697 The nctgpio and wbwd drivers have been moved to the superio bus.
698 If you have one of these drivers in a kernel configuration, then
699 you should add device superio to it. If you use one of these drivers
700 as a module and you compile a custom set of modules, then you should
701 add superio to the set.
704 KPIs for network drivers to access interface addresses have changed.
705 Users need to recompile NIC driver modules together with kernel.
708 The net.link.tap.user_open sysctl no longer prevents user opening of
709 already created /dev/tapNN devices. Access is still controlled by
710 node permissions, just like tun devices. The net.link.tap.user_open
711 sysctl is now used only to allow users to perform devfs cloning of
712 tap devices, and the subsequent open may not succeed if the user is not
713 in the appropriate group. This sysctl may be deprecated/removed
714 completely in the future.
717 mips, powerpc, and sparc64 are no longer built as part of
718 universe / tinderbox unless MAKE_OBSOLETE_GCC is defined. If
719 not defined, mips, powerpc, and sparc64 builds will look for
720 the xtoolchain binaries and if installed use them for universe
721 builds. As llvm 9.0 becomes vetted for these architectures, they
722 will be removed from the list.
725 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
726 been upgraded to 9.0.0. Please see the 20141231 entry below for
727 information about prerequisites and upgrading, if you are not already
728 using clang 3.5.0 or higher.
731 The hpt27xx, hptmv, hptnr, and hptrr drivers have been removed from
732 GENERIC. They are available as modules and can be loaded by adding
733 to /boot/loader.conf hpt27xx_load="YES", hptmv_load="YES",
734 hptnr_load="YES", or hptrr_load="YES", respectively.
737 ntpd no longer by default locks its pages in memory, allowing them
738 to be paged out by the kernel. Use rlimit memlock to restore
739 historic BSD behaviour. For example, add "rlimit memlock 32"
740 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
743 Several of ping6's options have been renamed for better consistency
744 with ping. If you use any of -ARWXaghmrtwx, you must update your
745 scripts. See ping6(8) for details.
748 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
749 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
750 been removed from mount_fusefs(8). You can safely remove them from
751 your scripts, because they had no effect.
753 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
754 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
755 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
756 sysctls have been removed. If you felt the need to set any of them to
757 a non-default value, please tell asomers@FreeBSD.org why.
760 Default permissions on the /var/account/acct file (and copies of it
761 rotated by periodic daily scripts) are changed from 0644 to 0640
762 because the file contains sensitive information that should not be
763 world-readable. If the /var/account directory must be created by
764 rc.d/accounting, the mode used is now 0750. Admins who use the
765 accounting feature are encouraged to change the mode of an existing
766 /var/account directory to 0750 or 0700.
769 Entropy collection and the /dev/random device are no longer optional
770 components. The "device random" option has been removed.
771 Implementations of distilling algorithms can still be made loadable
772 with "options RANDOM_LOADABLE" (e.g., random_fortuna.ko).
775 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
776 been upgraded to 8.0.1. Please see the 20141231 entry below for
777 information about prerequisites and upgrading, if you are not already
778 using clang 3.5.0 or higher.
781 A fix was applied to i386 kernel modules to avoid panics with
782 dpcpu or vnet. Users need to recompile i386 kernel modules
783 having pcpu or vnet sections or they will refuse to load.
786 User-wired pages now have their own counter,
787 vm.stats.vm.v_user_wire_count. The vm.max_wired sysctl was renamed
788 to vm.max_user_wired and changed from an unsigned int to an unsigned
789 long. bhyve VMs wired with the -S are now subject to the user
790 wiring limit; the vm.max_user_wired sysctl may need to be tuned to
791 avoid running into the limit.
794 The IPSEC option has been removed from GENERIC. Users requiring
795 ipsec(4) must now load the ipsec(4) kernel module.
798 The tap(4) driver has been folded into tun(4), and the module has been
799 renamed to tuntap. You should update any kld_list="if_tap" or
800 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
801 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
802 module instead, and "device tap" or "device tun" entries in kernel
803 config files to select the tuntap device instead.
806 The following knobs have been added related to tradeoffs between
807 safe use of the random device and availability in the absence of
810 kern.random.initial_seeding.bypass_before_seeding: tunable; set
811 non-zero to bypass the random device prior to seeding, or zero to
812 block random requests until the random device is initially seeded.
813 For now, set to 1 (unsafe) by default to restore pre-r346250 boot
814 availability properties.
816 kern.random.initial_seeding.read_random_bypassed_before_seeding:
817 read-only diagnostic sysctl that is set when bypass is enabled and
818 read_random(9) is bypassed, to enable programmatic handling of this
819 initial condition, if desired.
821 kern.random.initial_seeding.arc4random_bypassed_before_seeding:
822 Similar to the above, but for arc4random(9) initial seeding.
824 kern.random.initial_seeding.disable_bypass_warnings: tunable; set
825 non-zero to disable warnings in dmesg when the same conditions are
826 met as for the diagnostic sysctls above. Defaults to zero, i.e.,
827 produce warnings in dmesg when the conditions are met.
830 The loadable random module KPI has changed; the random_infra_init()
831 routine now requires a 3rd function pointer for a bool (*)(void)
832 method that returns true if the random device is seeded (and
833 therefore unblocked).
836 r345895 reverts r320698. This implies that an nfsuserd(8) daemon
837 built from head sources between r320757 (July 6, 2017) and
838 r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
839 is added to the command line.
840 nfsuserd daemons built from head sources that are post-r338192 are
841 not affected and should continue to work.
844 The fuse(4) module has been renamed to fusefs(4) for consistency with
845 other filesystems. You should update any kld_load="fuse" entries in
846 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
847 "options FUSE" entries in kernel config files.
850 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
851 8.0.0. Please see the 20141231 entry below for information about
852 prerequisites and upgrading, if you are not already using clang 3.5.0
856 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
857 compiled into your custom kernel, add 'device xz' statement to the
861 drm and drm2 have been removed from the tree. Please see
862 https://wiki.freebsd.org/Graphics for the latest information on
863 migrating to the drm ports.
866 Iflib is no longer unconditionally compiled into the kernel. Drivers
867 using iflib and statically compiled into the kernel, now require
868 the 'device iflib' config option. For the same drivers loaded as
869 modules on kernels not having 'device iflib', the iflib.ko module
870 is loaded automatically.
873 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
874 options no longer exist since r343219 and r343427 respectively;
875 nothing uses them, so they should be just removed from custom
879 r342635 changes the way efibootmgr(8) works by requiring users to add
880 the -b (bootnum) parameter for commands where the bootnum was previously
881 specified with each option. For example 'efibootmgr -B 0001' is now
882 'efibootmgr -B -b 0001'.
885 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
886 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
887 servers that have vfs.nfsd.nfs_privport set will only allow mounts
888 from clients using a reserved port. Since both the FreeBSD and Linux
889 NFSv4 clients use reserved ports by default, this should not affect
893 The XLP config has been removed. We can't support 64-bit atomics in this
894 kernel because it is running in 32-bit mode. XLP users must transition
895 to running a 64-bit kernel (XLP64 or XLPN32).
897 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
898 the preferred emulator today and we don't need two different ones.
900 The old sibyte / swarm / Broadcom BCM1250 support has been
901 removed from the mips port.
904 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
905 7.0.1. Please see the 20141231 entry below for information about
906 prerequisites and upgrading, if you are not already using clang 3.5.0
910 Remove the timed and netdate programs from the base tree. Setting
911 the time with these daemons has been obsolete for over a decade.
914 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
915 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
916 it produces broken binaries when ifuncs are in use. Users needing
917 GNU ld should install the binutils port or package.
920 The BSD crtbegin and crtend code has been enabled by default. It has
921 had extensive testing on amd64, arm64, and i386. It can be disabled
922 by building a world with -DWITHOUT_BSD_CRTBEGIN.
925 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
926 has been converted to a port (misc/ctm) and will be removed from
927 FreeBSD-13. It is available as a package (ctm) for all supported
931 The default newsyslog.conf(5) file has been changed to only include
932 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
933 the filenames end in '.conf' and do not begin with a '.'.
935 You should check the configuration files in these two directories match
936 this naming convention. You can verify which configuration files are
937 being included using the command:
941 Ports for the DRM modules have been simplified. Now, amd64 users should
942 just install the drm-kmod port. All others should install
945 Graphics hardware that's newer than about 2010 usually works with
946 drm-kmod. For hardware older than 2013, however, some users will need
947 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
948 than 2008 usually only works in drm-legacy-kmod. The graphics team can
949 only commit to hardware made since 2013 due to the complexity of the
950 market and difficulty to test all the older cards effectively. If you
951 have hardware supported by drm-kmod, you are strongly encouraged to use
952 that as you will get better support.
954 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
955 elsewhere, the drm and drm2 modules will be eliminated from the src base
956 soon (with a limited exception for arm). Please update to the package
957 asap and report any issues to x11@freebsd.org.
959 Generally, anybody using the drm*-kmod packages should add
960 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
961 cross-threading surprises, especially with automatic driver
962 loading from X11 startup. These will become the defaults in 13-current
966 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
967 custom kernel and module loading configuration files must be updated
968 accordingly. Moreover, interfaces previous presented as ixlvN to the
969 system are now exposed as iavfN and network configuration files must
970 be adjusted as necessary.
973 OpenSSL has been updated to version 1.1.1. This update included
974 additional various API changes throughout the base system. It is
975 important to rebuild third-party software after upgrading. The value
976 of __FreeBSD_version has been bumped accordingly.
979 The legacy DRM modules and drivers have now been added to the loader's
980 module blacklist, in favor of loading them with kld_list in rc.conf(5).
981 The module blacklist may be overridden with the loader.conf(5)
982 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
986 The cam(4) based nda(4) driver will be used over nvd(4) by default on
987 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
988 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
989 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
993 Reproducible build mode is now on by default, in preparation for
994 FreeBSD 12.0. This eliminates build metadata such as the user,
995 host, and time from the kernel (and uname), unless the working tree
996 corresponds to a modified checkout from a version control system.
997 The previous behavior can be obtained by setting the /etc/src.conf
998 knob WITHOUT_REPRODUCIBLE_BUILD.
1001 The Yarrow CSPRNG has been removed from the kernel as it has not been
1002 supported by its designers since at least 2003. Fortuna has been the
1003 default since FreeBSD-11.
1006 devctl freeze/thaw have gone into the tree, the rc scripts have been
1007 updated to use them and devmatch has been changed. You should update
1008 kernel, userland and rc scripts all at the same time.
1011 The default interpreter has been switched from 4th to Lua.
1012 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
1013 interpreter. If you have custom FORTH code you will need to set
1014 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
1015 src.conf for the build. This will create default hard links between
1016 loader and loader_4th instead of loader and loader_lua, the new default.
1017 If you are using UEFI it will create the proper hard link to loader.efi.
1019 bhyve uses userboot.so. It remains 4th-only until some issues are solved
1020 regarding coexisting with multiple versions of FreeBSD are resolved.
1023 ls(1) now respects the COLORTERM environment variable used in other
1024 systems and software to indicate that a colored terminal is both
1025 supported and desired. If ls(1) is suddenly emitting colors, they may
1026 be disabled again by either removing the unwanted COLORTERM from your
1027 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
1028 may not be observed in a future release.
1031 The default pager for most commands has been changed to "less". To
1032 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
1036 The jedec_ts(4) driver has been removed. A superset of its functionality
1037 is available in the jedec_dimm(4) driver, and the manpage for that
1038 driver includes migration instructions. If you have "device jedec_ts"
1039 in your kernel configuration file, it must be removed.
1042 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
1043 This should have no effect if the kernel is booted via BIOS/legacy boot.
1044 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
1045 has a buggy firmware that prevents a successful boot due to use of
1049 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
1050 support has been removed from the tree. These ports were
1051 obsolete and/or known to be broken for many years.
1054 loader.efi has been augmented to participate more fully in the
1055 UEFI boot manager protocol. loader.efi will now look at the
1056 BootXXXX environment variable to determine if a specific kernel
1057 or root partition was specified. XXXX is derived from BootCurrent.
1058 efibootmgr(8) manages these standard UEFI variables.
1061 zfsloader's functionality has now been folded into loader.
1062 zfsloader is no longer necessary once you've updated your
1063 boot blocks. For a transition period, we will install a
1064 hardlink for zfsloader to loader to allow a smooth transition
1065 until the boot blocks can be updated (hard link because old
1066 zfs boot blocks don't understand symlinks).
1069 ARM64 now have efifb support, if you want to have serial console
1070 on your arm64 board when an screen is connected and the bootloader
1071 setup a frame buffer for us to use, just add :
1074 in /boot/loader.conf
1075 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
1076 an screen connected as the firmware will setup a frame buffer are that
1077 u-boot will expose as an EFI frame buffer.
1080 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
1081 or take steps to update /etc/passwd before doing installworld on
1082 existing systems. Do not skip the "mergemaster -Fp" step before
1083 installworld, as described in the update procedures near the bottom
1084 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
1085 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
1086 the ntp config file contain options that change file/dir locations.
1087 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
1088 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
1089 taking steps to ensure that all required files/dirs are accessible
1093 Big endian arm support has been removed.
1096 The static environment setup in kernel configs is no longer mutually
1097 exclusive with the loader(8) environment by default. In order to
1098 restore the previous default behavior of disabling the loader(8)
1099 environment if a static environment is present, you must specify
1100 loader_env.disabled=1 in the static environment.
1103 The ABI of syscalls used by management tools like sockstat and
1104 netstat has been broken to allow 32-bit binaries to work on
1105 64-bit kernels without modification. These programs will need
1106 to match the kernel in order to function. External programs may
1107 require minor modifications to accommodate a change of type in
1108 structures from pointers to 64-bit virtual addresses.
1111 On i386 and amd64 atomics are now inlined. Out of tree modules using
1112 atomics will need to be rebuilt.
1115 The '%I' format in the kern.corefile sysctl limits the number of
1116 core files that a process can generate to the number stored in the
1117 debug.ncores sysctl. The '%I' format is replaced by the single digit
1118 index. Previously, if all indexes were taken the kernel would overwrite
1119 only a core file with the highest index in a filename.
1120 Currently the system will create a new core file if there is a free
1121 index or if all slots are taken it will overwrite the oldest one.
1124 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
1125 6.0.1. Please see the 20141231 entry below for information about
1126 prerequisites and upgrading, if you are not already using clang 3.5.0
1130 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
1131 needed to be changed to work with it. This change was made with r335763
1132 and requires a mergemaster / etcupdate / etc to update the installed
1136 r334930 changed the interface between the NFS modules, so they all
1137 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
1140 As of r334391 lld is the default amd64 system linker; it is installed
1141 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
1145 The kernel / userland interface for devinfo changed, so you'll
1146 need a new kernel and userland as a pair for it to work (rebuilding
1147 lib/libdevinfo is all that's required). devinfo and devmatch will
1148 not work, but everything else will when there's a mismatch.
1151 The on-disk format for hwpmc callchain records has changed to include
1152 threadid corresponding to a given record. This changes the field offsets
1153 and thus requires that libpmcstat be rebuilt before using a kernel
1157 The vxge(4) driver has been removed. This driver was introduced into
1158 HEAD one week before the Exar left the Ethernet market and is not
1159 known to be used. If you have device vxge in your kernel config file
1163 The amd64 kernel now requires a ld that supports ifunc to produce a
1164 working kernel, either lld or a newer binutils. lld is built by default
1165 on amd64, and the 'buildkernel' target uses it automatically. However,
1166 it is not the default linker, so building the kernel the traditional
1167 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
1168 binutils port/package). lld will soon be default, and this requirement
1171 NOTE: As of r334391 lld is the default system linker on amd64, and no
1172 workaround is necessary.
1175 The nxge(4) driver has been removed. This driver was for PCI-X 10g
1176 cards made by s2io/Neterion. The company was acquired by Exar and
1177 no longer sells or supports Ethernet products. If you have device
1178 nxge in your kernel config file it must be removed.
1181 The tz database (tzdb) has been updated to 2018e. This version more
1182 correctly models time stamps in time zones with negative DST such as
1183 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
1184 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
1185 time zone abbreviations and the tm_isdst flag.
1188 The ixgb(4) driver has been removed. This driver was for an early and
1189 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
1190 quickly shifted to the long lived ixgbe family. If you have device
1191 ixgb in your kernel config file it must be removed.
1194 The lmc(4) driver has been removed. This was a WAN interface
1195 card that was already reportedly rare in 2003, and had an ambiguous
1196 license. If you have device lmc in your kernel config file it must
1200 Support for Arcnet networks has been removed. If you have device
1201 arcnet or device cm in your kernel config file they must be
1205 Support for FDDI networks has been removed. If you have device
1206 fddi or device fpa in your kernel config file they must be
1210 In addition to supporting RFC 3164 formatted messages, the
1211 syslogd(8) service is now capable of parsing RFC 5424 formatted
1212 log messages. The main benefit of using RFC 5424 is that clients
1213 may now send log messages with timestamps containing year numbers,
1214 microseconds and time zone offsets.
1216 Similarly, the syslog(3) C library function has been altered to
1217 send RFC 5424 formatted messages to the local system logging
1218 daemon. On systems using syslogd(8), this change should have no
1219 negative impact, as long as syslogd(8) and the C library are
1220 updated at the same time. On systems using a different system
1221 logging daemon, it may be necessary to make configuration
1222 adjustments, depending on the software used.
1224 When using syslog-ng, add the 'syslog-protocol' flag to local
1225 input sources to enable parsing of RFC 5424 formatted messages:
1228 unix-dgram("/var/run/log" flags(syslog-protocol));
1231 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
1232 of the 'imuxsock' module to let messages be processed by the
1233 regular RFC 3164/5424 parsing pipeline:
1235 module(load="imuxsock" SysSock.UseSpecialParser="off")
1237 Do note that these changes only affect communication between local
1238 applications and syslogd(8). The format that syslogd(8) uses to
1239 store messages on disk or forward messages to other systems
1240 remains unchanged. syslogd(8) still uses RFC 3164 for these
1241 purposes. Options to customize this behaviour will be added in the
1242 future. Utilities that process log files stored in /var/log are
1243 thus expected to continue to function as before.
1245 __FreeBSD_version has been incremented to 1200061 to denote this
1249 Support for token ring networks has been removed. If you
1250 have "device token" in your kernel config you should remove
1251 it. No device drivers supported token ring.
1254 makefs was modified to be able to tag ISO9660 El Torito boot catalog
1255 entries as EFI instead of overloading the i386 tag as done previously.
1256 The amd64 mkisoimages.sh script used to build amd64 ISO images for
1257 release was updated to use this. This may mean that makefs must be
1258 updated before "make cdrom" can be run in the release directory. This
1259 should be as simple as:
1261 $ cd $SRCDIR/usr.sbin/makefs
1262 $ make depend all install
1265 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
1266 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
1267 Co-existence for the transition period will come shortly. Booting is a
1268 complex environment and test coverage for Lua-enabled loaders has been
1269 thin, so it would be prudent to assume it might not work and make
1270 provisions for backup boot methods.
1273 devmatch functionality has been turned on in devd. It will automatically
1274 load drivers for unattached devices. This may cause unexpected drivers
1275 to be loaded. Please report any problems to current@ and
1279 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
1280 6.0.0. Please see the 20141231 entry below for information about
1281 prerequisites and upgrading, if you are not already using clang 3.5.0
1285 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
1286 This means it is used to link the kernel and userland libraries and
1287 executables, but is not yet installed as /usr/bin/ld by default.
1289 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
1290 WITHOUT_LLD_BOOTSTRAP=yes
1293 On i386, pmtimer has been removed. Its functionality has been folded
1294 into apm. It was a no-op on ACPI in current for a while now (but was
1295 still needed on i386 in FreeBSD 11 and earlier). Users may need to
1296 remove it from kernel config files.
1299 The use of RSS hash from the network card aka flowid has been
1300 disabled by default for lagg(4) as it's currently incompatible with
1301 the lacp and loadbalance protocols.
1303 This can be re-enabled by setting the following in loader.conf:
1304 net.link.lagg.default_use_flowid="1"
1307 The SW_WATCHDOG option is no longer necessary to enable the
1308 hardclock-based software watchdog if no hardware watchdog is
1309 configured. As before, SW_WATCHDOG will cause the software
1310 watchdog to be enabled even if a hardware watchdog is configured.
1313 r326887 fixes the issue described in the 20171214 UPDATING entry.
1314 r326888 flips the switch back to building GELI support always.
1317 r362593 broke ZFS + GELI support for reasons unknown. However,
1318 it also broke ZFS support generally, so GELI has been turned off
1319 by default as the lesser evil in r326857. If you boot off ZFS and/or
1320 GELI, it might not be a good time to update.
1323 PowerPC users must update loader(8) by rebuilding world before
1324 installing a new kernel, as the protocol connecting them has
1325 changed. Without the update, loader metadata will not be passed
1326 successfully to the kernel and users will have to enter their
1327 root partition at the kernel mountroot prompt to continue booting.
1328 Newer versions of loader can boot old kernels without issue.
1331 The LOADER_FIREWIRE_SUPPORT build variable has been renamed to
1332 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
1333 to WITH/OUT_LOADER_GELI.
1336 The naive and non-compliant support of posix_fallocate(2) in ZFS
1337 has been removed as of r325320. The system call now returns EINVAL
1338 when used on a ZFS file. Although the new behavior complies with the
1339 standard, some consumers are not prepared to cope with it.
1340 One known victim is lld prior to r325420.
1343 Building in a FreeBSD src checkout will automatically create object
1344 directories now rather than store files in the current directory if
1345 'make obj' was not ran. Calling 'make obj' is no longer necessary.
1346 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
1347 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
1351 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
1352 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
1353 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
1354 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
1355 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
1356 The UNIFIED_OBJDIR option is a transitional feature that will be
1357 removed for 12.0 release; please migrate to the new format for any
1358 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
1359 than hardcoding paths.
1362 The native-xtools target no longer installs the files by default to the
1363 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
1364 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
1367 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
1368 options are changing from controlling the build if defined / undefined
1369 to controlling the build with explicit 'yes' or 'no' values. They will
1370 shift to WITH/WITHOUT options to match other options in the system.
1373 libstand has turned into a private library for sys/boot use only.
1374 It is no longer supported as a public interface outside of sys/boot.
1377 The arm port has split armv6 into armv6 and armv7. armv7 is now
1378 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
1379 and are running a kernel from before r324363, you will need to add
1380 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
1383 When building multiple kernels using KERNCONF, non-existent KERNCONF
1384 files will produce an error and buildkernel will fail. Previously
1385 missing KERNCONF files silently failed giving no indication as to
1386 why, only to subsequently discover during installkernel that the
1387 desired kernel was never built in the first place.
1390 The default serial number format for CTL LUNs has changed. This will
1391 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
1392 or iSCSI clients care about their LUNs' serial numbers. Users who
1393 require serial number stability should hardcode serial numbers in
1397 For 32-bit arm compiled for hard-float support, soft-floating point
1398 binaries now always get their shared libraries from
1399 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
1400 /usr/libsoft also existed). Only users with a hard-float ld.so, but
1401 soft-float everything else should be affected.
1404 The geli password typed at boot is now hidden. To restore the previous
1405 behavior, see geli(8) for configuration options.
1408 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
1409 sysctl values. Minor nit, but requires a rebuild of both world/kernel
1413 "make check" behavior (made in ^/head@r295380) has been changed to
1414 execute from a limited sandbox, as opposed to executing from
1418 - The "beforecheck" and "aftercheck" targets are now specified.
1419 - ${CHECKDIR} (added in commit noted above) has been removed.
1420 - Legacy behavior can be enabled by setting
1421 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
1423 If the limited sandbox mode is enabled, "make check" will execute
1424 "make distribution", then install, execute the tests, and clean up the
1425 sandbox if successful.
1427 The "make distribution" and "make install" targets are typically run as
1428 root to set appropriate permissions and ownership at installation time.
1429 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
1430 environment if executing "make check" with limited sandbox mode using
1431 an unprivileged user.
1434 Since the switch to GPT disk labels, fsck for UFS/FFS has been
1435 unable to automatically find alternate superblocks. As of r322297,
1436 the information needed to find alternate superblocks has been
1437 moved to the end of the area reserved for the boot block.
1438 Filesystems created with a newfs of this vintage or later
1439 will create the recovery information. If you have a filesystem
1440 created prior to this change and wish to have a recovery block
1441 created for your filesystem, you can do so by running fsck in
1442 foreground mode (i.e., do not use the -p or -y options). As it
1443 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
1444 to which you should answer yes.
1447 As of r321665, an NFSv4 server configuration that services
1448 Kerberos mounts or clients that do not support the uid/gid in
1449 owner/owner_group string capability, must explicitly enable
1450 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
1451 machine's /etc/rc.conf file.
1454 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
1455 Please see the 20141231 entry below for information about prerequisites
1456 and upgrading, if you are not already using clang 3.5.0 or higher.
1459 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
1460 r-commands (rlogin, rsh, etc.) to be built with the base system.
1463 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
1464 a very major ABI incompatible change, so users of FreeBSD/powerpc must
1465 be careful when performing source upgrades. It is best to run
1466 'make installworld' from an alternate root system, either a live
1467 CD/memory stick, or a temporary root partition. Additionally, all ports
1468 must be recompiled. powerpc64 is largely unaffected, except in the case
1469 of 32-bit compatibility. All 32-bit binaries will be affected.
1472 Forward compatibility for the "ino64" project have been committed. This
1473 will allow most new binaries to run on older kernels in a limited
1474 fashion. This prevents many of the common foot-shooting actions in the
1475 upgrade as well as the limited ability to roll back the kernel across
1476 the ino64 upgrade. Complicated use cases may not work properly, though
1477 enough simpler ones work to allow recovery in most situations.
1480 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
1481 if you require the GPL compiler.
1484 The internal ABI used for communication between the NFS kernel modules
1485 was changed by r320085, so __FreeBSD_version was bumped to
1486 ensure all the NFS related modules are updated together.
1489 The ABI of struct event was changed by extending the data
1490 member to 64bit and adding ext fields. For upgrade, same
1491 precautions as for the entry 20170523 "ino64" must be
1495 The GNU roff toolchain has been removed from base. To render manpages
1496 which are not supported by mandoc(1), man(1) can fallback on GNU roff
1497 from ports (and recommends to install it).
1498 To render roff(7) documents, consider using GNU roff from ports or the
1499 heirloom doctools roff toolchain from ports via pkg install groff or
1500 via pkg install heirloom-doctools.
1503 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
1504 smaller runtime footprint builds. This is useful for embedded systems
1505 which only require one chipset support.
1507 If you load it as a module, make sure this is in /boot/loader.conf:
1511 This will load the HAL, all chip/RF backends and if_ath_pci.
1512 If you have if_ath_pci in /boot/loader.conf, ensure it is after
1513 if_ath or it will not load any HAL chipset support.
1515 If you want to selectively load things (eg on cheaper ARM/MIPS
1516 platforms where RAM is at a premium) you should:
1519 * load the chip modules in question
1520 * load ath_rate, ath_dfs
1522 * load if_ath_pci and/or if_ath_ahb depending upon your particular
1523 bus bind type - this is where probe/attach is done.
1525 For further comments/feedback, poke adrian@ .
1528 The "ino64" 64-bit inode project has been committed, which extends
1529 a number of types to 64 bits. Upgrading in place requires care and
1530 adherence to the documented upgrade procedure.
1532 If using a custom kernel configuration ensure that the
1533 COMPAT_FREEBSD11 option is included (as during the upgrade the
1534 system will be running the ino64 kernel with the existing world).
1536 For the safest in-place upgrade begin by removing previous build
1537 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full
1538 procedure documented below under the heading "To rebuild everything and
1539 install it on the current system." Specifically, a reboot is required
1540 after installing the new kernel before installing world. While an
1541 installworld normally works by accident from multiuser after rebooting
1542 the proper kernel, there are many cases where this will fail across this
1543 upgrade and installworld from single user is required.
1546 The NATM framework including the en(4), fatm(4), hatm(4), and
1547 patm(4) devices has been removed. Consumers should plan a
1548 migration before the end-of-life date for FreeBSD 11.
1551 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
1552 diff has not been implemented, if those are needed a newer version of
1553 GNU diff is available via the diffutils package under the gdiff name.
1556 As of r316810 for ipfilter, keep frags is no longer assumed when
1557 keep state is specified in a rule. r316810 aligns ipfilter with
1558 documentation in man pages separating keep frags from keep state.
1559 This allows keep state to be specified without forcing keep frags
1560 and allows keep frags to be specified independently of keep state.
1561 To maintain previous behaviour, also specify keep frags with
1562 keep state (as documented in ipf.conf.5).
1565 arm64 builds now use the base system LLD 4.0.0 linker by default,
1566 instead of requiring that the aarch64-binutils port or package be
1567 installed. To continue using aarch64-binutils, set
1568 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
1571 The UDP optimization in entry 20160818 that added the sysctl
1572 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
1573 packets will no longer be treated as L3 broadcast packets.
1576 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
1577 use any explicitly assigned loopback address available in the jail
1578 instead of using the first assigned address of the jail.
1581 The ctl.ko module no longer implements the iSCSI target frontend:
1582 cfiscsi.ko does instead.
1584 If building cfiscsi.ko as a kernel module, the module can be loaded
1585 via one of the following methods:
1586 - `cfiscsi_load="YES"` in loader.conf(5).
1587 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
1588 - ctladm(8)/ctld(8), when compiled with iSCSI support
1589 (`WITH_ISCSI=yes` in src.conf(5))
1591 Please see cfiscsi(4) for more details.
1594 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
1595 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
1596 same source (previously, the dependency of mmcsd.ko on mmc.ko was
1597 missing, but mmcsd.ko now will refuse to load if it is incompatible
1601 The syntax of ipfw(8) named states was changed to avoid ambiguity.
1602 If you have used named states in the firewall rules, you need to modify
1603 them after installworld and before rebooting. Now named states must
1604 be prefixed with colon.
1607 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
1608 removed as the userland we provide cannot use them. The KMS version
1609 (sys/dev/drm2) supports the same hardware.
1612 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
1613 Please see the 20141231 entry below for information about prerequisites
1614 and upgrading, if you are not already using clang 3.5.0 or higher.
1617 The code that provides support for ZFS .zfs/ directory functionality
1618 has been reimplemented. It's not possible now to create a snapshot
1619 by mkdir under .zfs/snapshot/. That should be the only user visible
1623 EISA bus support has been removed. The WITH_EISA option is no longer
1627 MCA bus support has been removed.
1630 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
1631 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
1634 The EM_MULTIQUEUE kernel configuration option is deprecated now that
1635 the em(4) driver conforms to iflib specifications.
1638 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
1639 IFLIB. If you have a custom kernel configuration that excludes em(4)
1640 but you use igb(4), you need to re-add em(4) to your custom
1644 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
1645 Please see the 20141231 entry below for information about prerequisites
1646 and upgrading, if you are not already using clang 3.5.0 or higher.
1649 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
1650 Please see the 20141231 entry below for information about prerequisites
1651 and upgrading, if you are not already using clang 3.5.0 or higher.
1654 The layout of the pmap structure has changed for powerpc to put the pmap
1655 statistics at the front for all CPU variations. libkvm(3) and all tools
1656 that link against it need to be recompiled.
1659 isl(4) and cyapa(4) drivers now require a new driver,
1660 chromebook_platform(4), to work properly on Chromebook-class hardware.
1661 On other types of hardware the drivers may need to be configured using
1662 device hints. Please see the corresponding manual pages for details.
1665 The urtwn(4) driver was merged into rtwn(4) and now consists of
1666 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
1668 Also, firmware for RTL8188CE was renamed due to possible name
1669 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
1672 GNU rcs has been removed from base. It is available as packages:
1673 - rcs: Latest GPLv3 GNU rcs version.
1674 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
1678 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
1679 modules now requires that the kernel configuration contain the
1680 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
1683 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
1684 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
1687 Relocatable object files with the extension of .So have been renamed
1688 to use an extension of .pico instead. The purpose of this change is
1689 to avoid a name clash with shared libraries on case-insensitive file
1690 systems. On those file systems, foo.So is the same file as foo.so.
1693 GNU rcs has been turned off by default. It can (temporarily) be built
1694 again by adding WITH_RCS knob in src.conf.
1695 Otherwise, GNU rcs is available from packages:
1696 - rcs: Latest GPLv3 GNU rcs version.
1697 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
1700 The backup_uses_rcs functionality has been removed from rc.subr.
1703 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
1704 two separate components, QUEUE_MACRO_DEBUG_TRACE and
1705 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
1706 QUEUE_MACRO_DEBUG behavior.
1709 r304787 changed some ioctl interfaces between the iSCSI userspace
1710 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1711 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1715 The UDP receive code has been updated to only treat incoming UDP
1716 packets that were addressed to an L2 broadcast address as L3
1717 broadcast packets. It is not expected that this will affect any
1718 standards-conforming UDP application. The new behaviour can be
1719 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1723 Remove the openbsd_poll system call.
1724 __FreeBSD_version has been bumped because of this.
1727 The stable/11 branch has been created from head@r302406.
1729 After branch N is created, entries older than the N-2 branch point are removed
1730 from this file. After stable/14 is branched and current becomes FreeBSD 15,
1731 entries older than stable/12 branch point will be removed from current's
1738 Sometimes, obscure build problems are the result of environment
1739 poisoning. This can happen because the make utility reads its
1740 environment when searching for values for global variables. To run
1741 your build attempts in an "environmental clean room", prefix all make
1742 commands with 'env -i '. See the env(1) manual page for more details.
1743 Occasionally a build failure will occur with "make -j" due to a race
1744 condition. If this happens try building again without -j, and please
1745 report a bug if it happens consistently.
1747 When upgrading from one major version to another it is generally best to
1748 upgrade to the latest code in the currently installed branch first, then
1749 do an upgrade to the new branch. This is the best-tested upgrade path,
1750 and has the highest probability of being successful. Please try this
1751 approach if you encounter problems with a major version upgrade. Since
1752 the stable 4.x branch point, one has generally been able to upgrade from
1753 anywhere in the most recent stable branch to head / current (or even the
1754 last couple of stable branches). See the top of this file when there's
1757 The update process will emit an error on an attempt to perform a build
1758 or install from a FreeBSD version below the earliest supported version.
1759 When updating from an older version the update should be performed one
1760 major release at a time, including running `make delete-old` at each
1763 When upgrading a live system, having a root shell around before
1764 installing anything can help undo problems. Not having a root shell
1765 around can lead to problems if pam has changed too much from your
1766 starting point to allow continued authentication after the upgrade.
1768 This file should be read as a log of events. When a later event changes
1769 information of a prior event, the prior event should not be deleted.
1770 Instead, a pointer to the entry with the new information should be
1771 placed in the old entry. Readers of this file should also sanity check
1772 older entries before relying on them blindly. Authors of new entries
1773 should write them with this in mind.
1777 When upgrading the boot ZFS pool to a new version (via zpool upgrade),
1778 always follow these three steps:
1780 1) recompile and reinstall the ZFS boot loader and boot block
1781 (this is part of "make buildworld" and "make installworld")
1783 2) update the ZFS boot block on your boot drive (only required when
1784 doing a zpool upgrade):
1786 When booting on x86 via BIOS, use the following to update the ZFS boot
1787 block on the freebsd-boot partition of a GPT partitioned drive ada0:
1788 gpart bootcode -p /boot/gptzfsboot -i $N ada0
1789 The value $N will typically be 1. For EFI booting, see EFI notes.
1791 3) zpool upgrade the root pool. New bootblocks will work with old
1792 pools, but not vice versa, so they need to be updated before any
1795 Non-boot pools do not need these updates.
1800 There are two locations the boot loader can be installed into. The
1801 current location (and the default) is \efi\freebsd\loader.efi and using
1802 efibootmgr(8) to configure it. The old location, that must be used on
1803 deficient systems that don't honor efibootmgr(8) protocols, is the
1804 fallback location of \EFI\BOOT\BOOTxxx.EFI. Generally, you will copy
1805 /boot/loader.efi to this location, but on systems installed a long time
1806 ago the ESP may be too small and /boot/boot1.efi may be needed unless
1807 the ESP has been expanded in the meantime.
1809 Recent systems will have the ESP mounted on /boot/efi, but older ones
1810 may not have it mounted at all, or mounted in a different
1811 location. Older arm SD images with MBR used /boot/msdos as the
1812 mountpoint. The ESP is a MSDOS filesystem.
1814 The EFI boot loader rarely needs to be updated. For ZFS booting,
1815 however, you must update loader.efi before you do 'zpool upgrade' the
1816 root zpool, otherwise the old loader.efi may reject the upgraded zpool
1817 since it does not automatically understand some new features.
1819 See loader.efi(8) and uefi(8) for more details.
1823 If you are updating from a prior version of FreeBSD (even one just
1824 a few days old), you should follow this procedure. It is the most
1825 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1827 make kernel-toolchain
1828 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1829 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1831 To test a kernel once
1832 ---------------------
1833 If you just want to boot a kernel once (because you are not sure
1834 if it works, or if you want to boot a known bad kernel to provide
1835 debugging information) run
1836 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1837 nextboot -k testkernel
1839 To rebuild everything and install it on the current system.
1840 -----------------------------------------------------------
1841 # Note: sometimes if you are running current you gotta do more than
1842 # is listed here if you are upgrading from a really old current.
1844 <make sure you have good level 0 dumps>
1846 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1847 make installkernel KERNCONF=YOUR_KERNEL_HERE
1849 <reboot in single user> [3]
1856 To cross-install current onto a separate partition
1857 --------------------------------------------------
1858 # In this approach we use a separate partition to hold
1859 # current's root, 'usr', and 'var' directories. A partition
1860 # holding "/", "/usr" and "/var" should be about 2GB in
1863 <make sure you have good level 0 dumps>
1866 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1867 <maybe newfs current's root partition>
1868 <mount current's root partition on directory ${CURRENT_ROOT}>
1869 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1870 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1871 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1872 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1873 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1874 <reboot into current>
1875 <do a "native" rebuild/install as described in the previous section>
1876 <maybe install compatibility libraries from ports/misc/compat*>
1880 To upgrade in-place from stable to current
1881 ----------------------------------------------
1882 <make sure you have good level 0 dumps>
1884 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1885 make installkernel KERNCONF=YOUR_KERNEL_HERE
1887 <reboot in single user> [3]
1894 Make sure that you've read the UPDATING file to understand the
1895 tweaks to various things you need. At this point in the life
1896 cycle of current, things change often and you are on your own
1897 to cope. The defaults can also change, so please read ALL of
1898 the UPDATING entries.
1900 Also, if you are tracking -current, you must be subscribed to
1901 freebsd-current@freebsd.org. Make sure that before you update
1902 your sources that you have read and understood all the recent
1903 messages there. If in doubt, please track -stable which has
1904 much fewer pitfalls.
1906 [1] If you have third party modules, such as vmware, you should disable
1907 them at this point so they don't crash your system on
1908 reboot. Alternatively, you should rebuild all the modules you have in
1909 your system and install them as well. If you are running -current, you
1910 should seriously consider placing all sources to all the modules for
1911 your system (or symlinks to them) in /usr/local/sys/modules so this
1912 happens automatically. If all your modules come from ports, then adding
1913 the port origin directories to PORTS_MODULES instead is also automatic
1915 PORTS_MODULES+=x11/nvidia-driver
1917 [3] From the bootblocks, boot -s, and then do
1921 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed
1922 cd src # full path to source
1923 adjkerntz -i # if CMOS is wall time
1924 Also, when doing a major release upgrade, it is required that you boot
1925 into single user mode to do the installworld.
1927 [4] Note: This step is non-optional. Failure to do this step
1928 can result in a significant reduction in the functionality of the
1929 system. Attempting to do it by hand is not recommended and those
1930 that pursue this avenue should read this file carefully, as well
1931 as the archives of freebsd-current and freebsd-hackers mailing lists
1932 for potential gotchas. See etcupdate(8) for more information.
1934 [5] Usually this step is a no-op. However, from time to time
1935 you may need to do this if you get unknown user in the following
1938 [6] This only deletes old files and directories. Old libraries
1939 can be deleted by "make delete-old-libs", but you have to make
1940 sure that no program is using those libraries anymore.
1942 [8] The new kernel must be able to run existing binaries used by an
1943 installworld. When upgrading across major versions, the new kernel's
1944 configuration must include the correct COMPAT_FREEBSD<n> option for
1945 existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure
1946 to do so may leave you with a system that is hard to boot to recover. A
1947 GENERIC kernel will include suitable compatibility options to run
1948 binaries from older branches. Note that the ability to run binaries
1949 from unsupported branches is not guaranteed.
1951 Make sure that you merge any new devices from GENERIC since the
1952 last time you updated your kernel config file. Options also
1953 change over time, so you may need to adjust your custom kernels
1956 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1957 "?=" instead of the "=" assignment operator, so that buildworld can
1958 override the CPUTYPE if it needs to.
1960 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1961 not on the command line, or in /etc/make.conf. buildworld will
1962 warn if it is improperly defined.
1965 This file contains a list, in reverse chronological order, of major
1966 breakages in tracking -current. It is not guaranteed to be a complete
1967 list of such breakages, and only contains entries since September 23, 2011.
1968 If you need to see UPDATING entries from before that date, you will need
1969 to fetch an UPDATING file from an older FreeBSD release.
1971 Copyright information:
1973 Copyright 1998-2009 M. Warner Losh <imp@FreeBSD.org>
1975 Redistribution, publication, translation and use, with or without
1976 modification, in full or in part, in any form or format of this
1977 document are permitted without further permission from the author.
1979 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1980 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1981 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1982 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1983 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1984 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1985 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1986 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1987 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1988 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1989 POSSIBILITY OF SUCH DAMAGE.
1991 Contact Warner Losh if you have any questions about your use of