1 Updating Information for FreeBSD current users.
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 The macros provided for the manipulation of CPU sets (e.g. CPU_AND)
32 have been modified to take 2 source arguments instead of only 1.
33 Externally maintained sources that use these macros will have to
34 be adapted. The FreeBSD version has been bumped to 1400046 to
38 A number of the kernel include files are able to be included by
39 themselves. A test has been added to buildworld to enforce this.
42 Remove mips as a recognized target. This starts the decommissioning of
43 mips support in FreeBSD. mips related items will be removed wholesale in
44 the coming days and weeks.
46 This broke the NO_CLEAN build for some people. Either do a clean build
48 lib/clang/include/llvm/Config/Targets.def
49 lib/clang/include/llvm/Config/AsmParsers.def
50 lib/clang/include/llvm/Config/Disassemblers.def
51 lib/clang/include/llvm/Config/AsmPrinters.def
52 before the build to force everything to rebuild that needs to.
55 Unbound support for RFC8375: The special-use domain 'home.arpa' is
56 by default blocked. To unblock it use a local-zone nodefault
57 statement in unbound.conf:
58 local-zone: "home.arpa." nodefault
60 Or use another type of local-zone to override with your choice.
62 The reason for this is discussed in Section 6.1 of RFC8375:
63 Because 'home.arpa.' is not globally scoped and cannot be secured
64 using DNSSEC based on the root domain's trust anchor, there is no way
65 to tell, using a standard DNS query, in which homenet scope an answer
66 belongs. Consequently, users may experience surprising results with
67 such names when roaming to different homenets.
70 Commit b8d60729deef changed the TCP congestion control framework so
71 that any of the included congestion control modules could be
72 the single module built into the kernel. Previously newreno
73 was automatically built in through direct reference. As of
74 this commit you are required to declare at least one congestion
75 control module (e.g. 'options CC_NEWRENO') and to also declare a
76 default using the CC_DEFAULT option (e.g. options CC_DEFAULT="newreno\").
77 The GENERIC configuration includes CC_NEWRENO and defines newreno
78 as the default. If no congestion control option is built into the
79 kernel and you are including networking, the kernel compile will
80 fail. Also if no default is declared the kernel compile will fail.
83 Mips has been removed from universe builds. It will be removed from the
87 Commit f0c9847a6c47 changed the arguments for VOP_ALLOCATE.
88 The NFS modules must be rebuilt from sources and any out
89 of tree file systems that implement their own VOP_ALLOCATE
90 may need to be modified.
93 The synchronous PPP kernel driver sppp(4) has been removed.
94 The cp(4) and ce(4) drivers are now always compiled with netgraph(4)
95 support, formerly enabled by NETGRAPH_CRONYX option.
98 sh(1) is now the default shell for the root user. To force root to use
99 the csh shell, please run the following command as root:
104 Ncurses distribution has been split between libtinfow and libncurses
105 with libncurses.so becoming a linker (ld) script to seamlessly link
106 to libtinfow as needed. Bump _FreeBSD_version to 1400035 to reflect
110 As of commit 8160a0f62be6, the dummynet module no longer depends on the
111 ipfw module. Dummynet can now be used by pf as well as ipfw. As such
112 users who relied on this dependency may need to include ipfw in the
113 list of modules to load on their systems.
116 As of commit 903873ce1560, the mixer(8) utility has got a slightly
117 new syntax. Please refer to the mixer(8) manual page for more
118 information. The old mixer utility can be installed from ports:
119 audio/freebsd-13-mixer
122 As of commit 55089ef4f8bb, the global variable nfs_maxcopyrange has
123 been deleted from the nfscommon.ko. As such, nfsd.ko must be built
124 from up to date sources to avoid an undefined reference when
128 As of commit 62ca9fc1ad56 OpenSSL no longer enables kernel TLS
129 by default. Users can enable kernel TLS via the "KTLS" SSL
130 option. This can be enabled globally by using a custom
131 OpenSSL config file via OPENSSL_CONF or via an
132 application-specific configuration option for applications
133 which permit setting SSL options via SSL_CONF_cmd(3).
136 Commit 3ad1e1c1ce20 changed the internal KAPI between the NFS
137 modules. Therefore, all need to be rebuilt from sources.
140 Commit b69019c14cd8 removes pf's DIOCGETSTATESNV ioctl.
141 As of be70c7a50d32 it is no longer used by userspace, but it does mean
142 users may not be able to enumerate pf states if they update the kernel
143 past b69019c14cd8 without first updating userspace past be70c7a50d32.
146 As of commit 01ad0c007964 if_bridge member interfaces can no longer
147 change their MTU. Changing the MTU of the bridge itself will change the
148 MTU on all member interfaces instead.
151 Commit ee29e6f31111 changed the internal KAPI between the nfscommon
152 and nfsd modules. Therefore, both need to be rebuilt from sources.
153 Bump __FreeBSD_version to 1400026 for this KAPI change.
156 The 20210707 awk update brought in a change in behavior. This has
157 been corrected as of d4d252c49976. Between these dates, if you
158 installed a new awk binary, you may not be able to build a new
159 kernel because the change in behavior affected the genoffset
160 script used to build the kernel. If you did update, the fix is
161 to update your sources past the above hash and do
164 % sudo -E make install
165 to enable building kernels again.
168 Commit 1e0a518d6548 changed the internal KAPI between the NFS
169 modules. They all need to be rebuilt from sources. I did not
170 bump __FreeBSD_version, since it was bumped recently.
173 awk has been updated to the latest one-true-awk version 20210215.
174 This contains a number of minor bug fixes.
177 The NFSv4 client now uses the highest minor version of NFSv4
178 supported by the NFSv4 server by default instead of minor version 0,
180 The "minorversion" mount option may be used to override this default.
183 Bump __FreeBSD_version to 1400024 for LinuxKPI changes.
184 Most notably netdev.h can change now as the (last) dependencies
185 (mlx4/ofed) are now using struct ifnet directly, but also for PCI
186 additions and others.
189 The directory "blacklisted" under /usr/share/certs/ has been
190 renamed to "untrusted".
193 svnlite has been removed from base. Should you need svn for any reason
194 please install the svn package or port.
197 Commit e1a907a25cfa changed the internal KAPI between the krpc
198 and nfsserver. As such, both modules must be rebuilt from
199 sources. Bump __FreeBSD_version to 1400022.
202 The an(4) driver has been removed from FreeBSD.
205 The vendor/openzfs branch was renamed to vendor/openzfs/legacy to
206 start tracking OpenZFS upstream more closely. Please see
207 https://lists.freebsd.org/archives/freebsd-current/2021-June/000153.html
208 for details on how to correct any errors that might result. The
209 short version is that you need to remove the old branch locally:
210 git update-ref -d refs/remotes/freebsd/vendor/openzfs
211 (assuming your upstream origin is named 'freebsd').
214 Commits 17accc08ae15 and de102f870501 add new files to LinuxKPI
215 which break drm-kmod. In addition various other additions where
216 committed. Bump __FreeBSD_version to 1400015 to be able to
220 Commit ca179c4d74f2 changed the package in which the OpenSSL
221 libraries and utilities are packaged.
222 It is recommended for pkgbase user to do:
223 pkg install -f FreeBSD-openssl
224 before pkg upgrade otherwise some dependencies might not be met
225 and pkg will stop working as libssl will not be present anymore
229 Commit 875977314881 changed the internal KAPI between
230 the nfsd and nfscommon modules. As such these modules
231 need to be rebuilt from sources.
232 Without this patch in your NFSv4.1/4.2 server, enabling
233 delegations by setting vfs.nfsd.issue_delegations non-zero
237 Commit 7763814fc9c2 changed the internal KAPI between
238 the krpc and NFS. As such, the krpc, nfscommon and
239 nfscl modules must all be rebuilt from sources.
240 Without this patch, NFSv4.1/4.2 mounts should not
241 be done with the nfscbd(8) daemon running, to avoid
242 needing a working back channel for server->client RPCs.
245 Commit 01ae8969a9ee fixed the NFSv4.1/4.2 server so that it
246 handles binding of the back channel as required by RFC5661.
247 Until this patch is in your server, avoid use of the "nconnects"
248 mount option for Linux NFSv4.1/4.2 mounts.
251 For 64-bit architectures the base system is now built with Position
252 Independent Executable (PIE) support enabled by default. It may be
253 disabled using the WITHOUT_PIE knob. A clean build is required.
256 Various LinuxKPI functionality was added which conflicts with DRM.
257 Please update your drm-kmod port to after the __FreeBSD_version 1400003
261 PC Card attachments for all devices have been removed. In the case of
262 wi and cmx, the entire drivers were removed because they were only
263 PC Card devices. FreeBSD_version 1300134 should be used for this
264 since it was bumped so recently.
267 Transport-independent parts of HID support have been split off the USB
268 code in to separate subsystem. Kernel configs which include one of
269 ums, ukbd, uhid, atp, wsp, wmt, uaudio, ugold or ucycom drivers should
270 be updated with adding of "device hid" line.
273 ncurses installation has been modified to only keep the widechar
274 enabled version. Incremental build is broken for that change, so it
275 requires a clean build.
278 The FreeBSD project has migrated from Subversion to Git. Temporary
279 instructions can be found at
280 https://github.com/bsdimp/freebsd-git-docs/blob/main/src-cvt.md
281 and other documents in that repo.
284 The services database has been updated to cover more of the basic
285 services expected in a modern system. The database is big enough
286 that it will cause issues in mergemaster in Releases previous to
287 12.2 and 11.3, or in very old current systems from before r358154.
290 Obsolete in-tree GDB 6.1.1 has been removed. GDB (including kgdb)
291 may be installed from ports or packages.
294 ping6 has been merged into ping. It can now be called as "ping -6".
295 See ping(8) for details.
298 Default value of net.add_addr_allfibs has been changed to 0.
299 If you have multi-fib configuration and rely on existence of all
300 interface routes in every fib, you need to set the above sysctl to 1.
303 The internal pre-processor in the calendar(1) program has been
304 extended to support more C pre-processor commands (e.g. #ifdef, #else,
305 and #undef) and to detect unbalanced conditional statements.
306 Error messages have been extended to include the filename and line
307 number if processing stops to help fixing malformed data files.
310 All the data files for the calendar(1) program, except calendar.freebsd,
311 have been moved to the deskutils/calendar-data port, much like the
312 jewish calendar entries were moved to deskutils/hebcal years ago. After
313 make delete-old-files, you need to install it to retain full
314 functionality. calendar(1) will issue a reminder for files it can't
318 LINT files are no longer generated. We now include the relevant NOTES
319 files. Note: This may cause conflicts with updating in some cases.
320 find sys -name LINT\* -delete
321 is suggested across this commit to remove the generated LINT files.
323 If you have tried to update with generated files there, the svn
324 command you want to un-auger the tree is
327 and then do the above find from the top level. Substitute 'amd64'
328 above with where the error message indicates a conflict.
331 OpenZFS support has been integrated. Do not upgrade root pools until
332 the loader is updated to support zstd. Furthermore, we caution against
333 'zpool upgrade' for the next few weeks. The change should be transparent
334 unless you want to use new features.
336 Not all "NO_CLEAN" build scenarios work across these changes. Many
337 scenarios have been tested and fixed, but rebuilding kernels without
338 rebuilding world may fail.
340 The ZFS cache file has moved from /boot to /etc to match the OpenZFS
341 upstream default. A fallback to /boot has been added for mountroot.
343 Pool auto import behavior at boot has been moved from the kernel module
344 to an explicit "zpool import -a" in one of the rc scripts enabled by
345 zfs_enable=YES. This means your non-root zpools won't auto import until
346 you upgrade your /etc/rc.d files.
349 The resume code now notifies devd with the 'kernel' system
350 rather than the old 'kern' subsystem to be consistent with
351 other use. The old notification will be created as well, but
352 will be removed prior to FreeBSD 14.0.
355 r362275 changed the internal API between the kernel RPC and the
356 NFS modules. As such, all the modules must be recompiled from
360 r364330 modified the internal API used between the NFS modules.
361 As such, all the NFS modules must be re-compiled from sources.
364 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
365 been upgraded to 11.0.0. Please see the 20141231 entry below for
366 information about prerequisites and upgrading, if you are not already
367 using clang 3.5.0 or higher.
370 r364092 modified the internal ABI used between the kernel NFS
371 modules. As such, all of these modules need to be rebuilt
372 from sources, so a version bump was done.
375 Makefile.inc has been updated to work around the issue documented in
376 20200729. It was a case where the optimization of using symbolic links
377 to point to binaries created a situation where we'd run new binaries
378 with old libraries starting midway through the installworld process.
381 r363679 has redefined some undefined behavior in regcomp(3); notably,
382 extraneous escapes of most ordinary characters will no longer be
383 accepted. An exp-run has identified all of the problems with this in
384 ports, but other non-ports software may need extra escapes removed to
385 continue to function.
387 Because of this change, installworld may encounter the following error
388 from rtld: Undefined symbol "regcomp@FBSD_1.6" -- It is imperative that
389 you do not halt installworld. Instead, let it run to completion (whether
390 successful or not) and run installworld once more.
393 A new implementation of bc and dc has been imported in r362681. This
394 implementation corrects non-conformant behavior of the previous bc
395 and adds GNU bc compatible options. It offers a number of extensions,
396 is much faster on large values, and has support for message catalogs
397 (a number of languages are already supported, contributions of further
398 languages welcome). The option WITHOUT_GH_BC can be used to build the
399 world with the previous versions of bc and dc.
402 r362639 changed the internal API used between the NFS kernel modules.
403 As such, they all need to be rebuilt from sources.
406 r362158 changed the arguments for VFS_CHECKEXP(). As such, any
407 out of tree file systems need to be modified and rebuilt.
408 Also, any file systems that are modules must be rebuilt.
411 read(2) of a directory fd is now rejected by default. root may
412 re-enable it for system root only on non-ZFS filesystems with the
413 security.bsd.allow_read_dir sysctl(8) MIB if
414 security.bsd.suser_enabled=1.
416 It may be advised to setup aliases for grep to default to `-d skip` if
417 commonly non-recursively grepping a list that includes directories and
418 the potential for the resulting stderr output is not tolerable. Example
419 aliases are now installed, commented out, in /root/.cshrc and
423 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
424 been upgraded to 10.0.1. Please see the 20141231 entry below for
425 information about prerequisites and upgrading, if you are not already
426 using clang 3.5.0 or higher.
429 Support for obsolete compilers has been removed from the build system.
430 Clang 6 and GCC 6.4 are the minimum supported versions.
433 closefrom(2) has been moved under COMPAT12, and replaced in libc with a
434 stub that calls close_range(2). If using a custom kernel configuration,
435 you may want to ensure that the COMPAT_FREEBSD12 option is included, as
436 a slightly older -CURRENT userland and older FreeBSD userlands may not
437 be functional without closefrom(2).
440 Upstream DTS from Linux 5.6 was merged and they now have the SID
441 and THS (Secure ID controller and THermal Sensor) node present.
442 The DTB overlays have now been removed from the tree for the H3/H5 and
443 A64 SoCs and the aw_sid and aw_thermal driver have been updated to
444 deal with upstream DTS. If you are using those overlays you need to
445 remove them from loader.conf and update the DTBs on the FAT partition.
448 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
449 been upgraded to 10.0.0. Please see the 20141231 entry below for
450 information about prerequisites and upgrading, if you are not already
451 using clang 3.5.0 or higher.
454 The amd(8) automount daemon has been removed from the source tree.
455 As of FreeBSD 10.1 autofs(5) is the preferred tool for automounting.
456 amd is still available in the sysutils/am-utils port.
459 Removed brooktree driver (bktr.4) from the tree.
462 The WITH_GPL_DTC option has been removed. The BSD-licenced device tree
463 compiler in usr.bin/dtc is used on all architectures which use dtc, and
464 the GPL dtc is available (if needed) from the sysutils/dtc port.
467 The WITHOUT_LLVM_LIBUNWIND option has been removed. LLVM's libunwind
468 is used by all supported CPU architectures.
471 GCC 4.2.1 has been removed from the tree. The WITH_GCC,
472 WITH_GCC_BOOTSTRAP, and WITH_GNUCXX options are no longer available.
473 Users who wish to build FreeBSD with GCC must use the external toolchain
477 ncurses has been updated to a newer version (6.2-20200215). Given the ABI
478 has changed, users will have to rebuild all the ports that are linked to
482 The size of struct vnet and the magic cookie have changed.
483 Users need to recompile libkvm and all modules using VIMAGE
484 together with their new kernel.
487 Defining the long deprecated NO_CTF, NO_DEBUG_FILES, NO_INSTALLLIB,
488 NO_MAN, NO_PROFILE, and NO_WARNS variables is now an error. Update
489 your Makefiles and scripts to define MK_<var>=no instead as required.
491 One exception to this is that program or library Makefiles should
492 define MAN to empty rather than setting MK_MAN=no.
495 Clang/LLVM is now the default compiler and LLD the default
499 make universe no longer uses GCC 4.2.1 on any architectures.
500 Architectures not supported by in-tree Clang/LLVM require an
501 external toolchain package.
504 GCC 4.2.1 is now not built by default, as part of the GCC 4.2.1
505 retirement plan. Specifically, the GCC, GCC_BOOTSTRAP, and GNUCXX
506 options default to off for all supported CPU architectures. As a
507 short-term transition aid they may be enabled via WITH_* options.
508 GCC 4.2.1 is expected to be removed from the tree on 2020-03-31.
511 Support for armv5 has been disconnected and is being removed. The
512 machine combination MACHINE=arm MACHINE_ARCH=arm is no longer valid.
513 You must now use a MACHINE_ARCH of armv6 or armv7. The default
514 MACHINE_ARCH for MACHINE=arm is now armv7.
517 Clang/LLVM is now the default compiler for all powerpc architectures.
518 LLD is now the default linker for powerpc64. The change for powerpc64
519 also includes a change to the ELFv2 ABI, incompatible with the existing
523 Kernel-loadable random(4) modules are no longer unloadable.
526 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
527 been upgraded to 9.0.1. Please see the 20141231 entry below for
528 information about prerequisites and upgrading, if you are not already
529 using clang 3.5.0 or higher.
532 r355677 has modified the internal interface used between the
533 NFS modules in the kernel. As such, they must all be upgraded
534 simultaneously. I will do a version bump for this.
537 The root certificates of the Mozilla CA Certificate Store have been
538 imported into the base system and can be managed with the certctl(8)
539 utility. If you have installed the security/ca_root_nss port or package
540 with the ETCSYMLINK option (the default), be advised that there may be
541 differences between those included in the port and those included in
542 base due to differences in nss branch used as well as general update
543 frequency. Note also that certctl(8) cannot manage certs in the
544 format used by the security/ca_root_nss port.
547 The amd(8) automount daemon has been disabled by default, and will be
548 removed in the future. As of FreeBSD 10.1 the autofs(5) is available
552 The nctgpio and wbwd drivers have been moved to the superio bus.
553 If you have one of these drivers in a kernel configuration, then
554 you should add device superio to it. If you use one of these drivers
555 as a module and you compile a custom set of modules, then you should
556 add superio to the set.
559 KPIs for network drivers to access interface addresses have changed.
560 Users need to recompile NIC driver modules together with kernel.
563 The net.link.tap.user_open sysctl no longer prevents user opening of
564 already created /dev/tapNN devices. Access is still controlled by
565 node permissions, just like tun devices. The net.link.tap.user_open
566 sysctl is now used only to allow users to perform devfs cloning of
567 tap devices, and the subsequent open may not succeed if the user is not
568 in the appropriate group. This sysctl may be deprecated/removed
569 completely in the future.
572 mips, powerpc, and sparc64 are no longer built as part of
573 universe / tinderbox unless MAKE_OBSOLETE_GCC is defined. If
574 not defined, mips, powerpc, and sparc64 builds will look for
575 the xtoolchain binaries and if installed use them for universe
576 builds. As llvm 9.0 becomes vetted for these architectures, they
577 will be removed from the list.
580 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
581 been upgraded to 9.0.0. Please see the 20141231 entry below for
582 information about prerequisites and upgrading, if you are not already
583 using clang 3.5.0 or higher.
586 The hpt27xx, hptmv, hptnr, and hptrr drivers have been removed from
587 GENERIC. They are available as modules and can be loaded by adding
588 to /boot/loader.conf hpt27xx_load="YES", hptmv_load="YES",
589 hptnr_load="YES", or hptrr_load="YES", respectively.
592 ntpd no longer by default locks its pages in memory, allowing them
593 to be paged out by the kernel. Use rlimit memlock to restore
594 historic BSD behaviour. For example, add "rlimit memlock 32"
595 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
598 Several of ping6's options have been renamed for better consistency
599 with ping. If you use any of -ARWXaghmrtwx, you must update your
600 scripts. See ping6(8) for details.
603 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
604 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
605 been removed from mount_fusefs(8). You can safely remove them from
606 your scripts, because they had no effect.
608 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
609 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
610 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
611 sysctls have been removed. If you felt the need to set any of them to
612 a non-default value, please tell asomers@FreeBSD.org why.
615 Default permissions on the /var/account/acct file (and copies of it
616 rotated by periodic daily scripts) are changed from 0644 to 0640
617 because the file contains sensitive information that should not be
618 world-readable. If the /var/account directory must be created by
619 rc.d/accounting, the mode used is now 0750. Admins who use the
620 accounting feature are encouraged to change the mode of an existing
621 /var/account directory to 0750 or 0700.
624 Entropy collection and the /dev/random device are no longer optional
625 components. The "device random" option has been removed.
626 Implementations of distilling algorithms can still be made loadable
627 with "options RANDOM_LOADABLE" (e.g., random_fortuna.ko).
630 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
631 been upgraded to 8.0.1. Please see the 20141231 entry below for
632 information about prerequisites and upgrading, if you are not already
633 using clang 3.5.0 or higher.
636 A fix was applied to i386 kernel modules to avoid panics with
637 dpcpu or vnet. Users need to recompile i386 kernel modules
638 having pcpu or vnet sections or they will refuse to load.
641 User-wired pages now have their own counter,
642 vm.stats.vm.v_user_wire_count. The vm.max_wired sysctl was renamed
643 to vm.max_user_wired and changed from an unsigned int to an unsigned
644 long. bhyve VMs wired with the -S are now subject to the user
645 wiring limit; the vm.max_user_wired sysctl may need to be tuned to
646 avoid running into the limit.
649 The IPSEC option has been removed from GENERIC. Users requiring
650 ipsec(4) must now load the ipsec(4) kernel module.
653 The tap(4) driver has been folded into tun(4), and the module has been
654 renamed to tuntap. You should update any kld_list="if_tap" or
655 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
656 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
657 module instead, and "device tap" or "device tun" entries in kernel
658 config files to select the tuntap device instead.
661 The following knobs have been added related to tradeoffs between
662 safe use of the random device and availability in the absence of
665 kern.random.initial_seeding.bypass_before_seeding: tunable; set
666 non-zero to bypass the random device prior to seeding, or zero to
667 block random requests until the random device is initially seeded.
668 For now, set to 1 (unsafe) by default to restore pre-r346250 boot
669 availability properties.
671 kern.random.initial_seeding.read_random_bypassed_before_seeding:
672 read-only diagnostic sysctl that is set when bypass is enabled and
673 read_random(9) is bypassed, to enable programmatic handling of this
674 initial condition, if desired.
676 kern.random.initial_seeding.arc4random_bypassed_before_seeding:
677 Similar to the above, but for arc4random(9) initial seeding.
679 kern.random.initial_seeding.disable_bypass_warnings: tunable; set
680 non-zero to disable warnings in dmesg when the same conditions are
681 met as for the diagnostic sysctls above. Defaults to zero, i.e.,
682 produce warnings in dmesg when the conditions are met.
685 The loadable random module KPI has changed; the random_infra_init()
686 routine now requires a 3rd function pointer for a bool (*)(void)
687 method that returns true if the random device is seeded (and
688 therefore unblocked).
691 r345895 reverts r320698. This implies that an nfsuserd(8) daemon
692 built from head sources between r320757 (July 6, 2017) and
693 r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
694 is added to the command line.
695 nfsuserd daemons built from head sources that are post-r338192 are
696 not affected and should continue to work.
699 The fuse(4) module has been renamed to fusefs(4) for consistency with
700 other filesystems. You should update any kld_load="fuse" entries in
701 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
702 "options FUSE" entries in kernel config files.
705 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
706 8.0.0. Please see the 20141231 entry below for information about
707 prerequisites and upgrading, if you are not already using clang 3.5.0
711 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
712 compiled into your custom kernel, add 'device xz' statement to the
716 drm and drm2 have been removed from the tree. Please see
717 https://wiki.freebsd.org/Graphics for the latest information on
718 migrating to the drm ports.
721 Iflib is no longer unconditionally compiled into the kernel. Drivers
722 using iflib and statically compiled into the kernel, now require
723 the 'device iflib' config option. For the same drivers loaded as
724 modules on kernels not having 'device iflib', the iflib.ko module
725 is loaded automatically.
728 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
729 options no longer exist since r343219 and r343427 respectively;
730 nothing uses them, so they should be just removed from custom
734 r342635 changes the way efibootmgr(8) works by requiring users to add
735 the -b (bootnum) parameter for commands where the bootnum was previously
736 specified with each option. For example 'efibootmgr -B 0001' is now
737 'efibootmgr -B -b 0001'.
740 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
741 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
742 servers that have vfs.nfsd.nfs_privport set will only allow mounts
743 from clients using a reserved port. Since both the FreeBSD and Linux
744 NFSv4 clients use reserved ports by default, this should not affect
748 The XLP config has been removed. We can't support 64-bit atomics in this
749 kernel because it is running in 32-bit mode. XLP users must transition
750 to running a 64-bit kernel (XLP64 or XLPN32).
752 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
753 the preferred emulator today and we don't need two different ones.
755 The old sibyte / swarm / Broadcom BCM1250 support has been
756 removed from the mips port.
759 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
760 7.0.1. Please see the 20141231 entry below for information about
761 prerequisites and upgrading, if you are not already using clang 3.5.0
765 Remove the timed and netdate programs from the base tree. Setting
766 the time with these daemons has been obsolete for over a decade.
769 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
770 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
771 it produces broken binaries when ifuncs are in use. Users needing
772 GNU ld should install the binutils port or package.
775 The BSD crtbegin and crtend code has been enabled by default. It has
776 had extensive testing on amd64, arm64, and i386. It can be disabled
777 by building a world with -DWITHOUT_BSD_CRTBEGIN.
780 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
781 has been converted to a port (misc/ctm) and will be removed from
782 FreeBSD-13. It is available as a package (ctm) for all supported
786 The default newsyslog.conf(5) file has been changed to only include
787 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
788 the filenames end in '.conf' and do not begin with a '.'.
790 You should check the configuration files in these two directories match
791 this naming convention. You can verify which configuration files are
792 being included using the command:
796 Ports for the DRM modules have been simplified. Now, amd64 users should
797 just install the drm-kmod port. All others should install
800 Graphics hardware that's newer than about 2010 usually works with
801 drm-kmod. For hardware older than 2013, however, some users will need
802 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
803 than 2008 usually only works in drm-legacy-kmod. The graphics team can
804 only commit to hardware made since 2013 due to the complexity of the
805 market and difficulty to test all the older cards effectively. If you
806 have hardware supported by drm-kmod, you are strongly encouraged to use
807 that as you will get better support.
809 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
810 elsewhere, the drm and drm2 modules will be eliminated from the src base
811 soon (with a limited exception for arm). Please update to the package
812 asap and report any issues to x11@freebsd.org.
814 Generally, anybody using the drm*-kmod packages should add
815 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
816 cross-threading surprises, especially with automatic driver
817 loading from X11 startup. These will become the defaults in 13-current
821 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
822 custom kernel and module loading configuration files must be updated
823 accordingly. Moreover, interfaces previous presented as ixlvN to the
824 system are now exposed as iavfN and network configuration files must
825 be adjusted as necessary.
828 OpenSSL has been updated to version 1.1.1. This update included
829 additional various API changes throughout the base system. It is
830 important to rebuild third-party software after upgrading. The value
831 of __FreeBSD_version has been bumped accordingly.
834 The legacy DRM modules and drivers have now been added to the loader's
835 module blacklist, in favor of loading them with kld_list in rc.conf(5).
836 The module blacklist may be overridden with the loader.conf(5)
837 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
841 The cam(4) based nda(4) driver will be used over nvd(4) by default on
842 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
843 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
844 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
848 Reproducible build mode is now on by default, in preparation for
849 FreeBSD 12.0. This eliminates build metadata such as the user,
850 host, and time from the kernel (and uname), unless the working tree
851 corresponds to a modified checkout from a version control system.
852 The previous behavior can be obtained by setting the /etc/src.conf
853 knob WITHOUT_REPRODUCIBLE_BUILD.
856 The Yarrow CSPRNG has been removed from the kernel as it has not been
857 supported by its designers since at least 2003. Fortuna has been the
858 default since FreeBSD-11.
861 devctl freeze/thaw have gone into the tree, the rc scripts have been
862 updated to use them and devmatch has been changed. You should update
863 kernel, userland and rc scripts all at the same time.
866 The default interpreter has been switched from 4th to Lua.
867 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
868 interpreter. If you have custom FORTH code you will need to set
869 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
870 src.conf for the build. This will create default hard links between
871 loader and loader_4th instead of loader and loader_lua, the new default.
872 If you are using UEFI it will create the proper hard link to loader.efi.
874 bhyve uses userboot.so. It remains 4th-only until some issues are solved
875 regarding coexisting with multiple versions of FreeBSD are resolved.
878 ls(1) now respects the COLORTERM environment variable used in other
879 systems and software to indicate that a colored terminal is both
880 supported and desired. If ls(1) is suddenly emitting colors, they may
881 be disabled again by either removing the unwanted COLORTERM from your
882 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
883 may not be observed in a future release.
886 The default pager for most commands has been changed to "less". To
887 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
891 The jedec_ts(4) driver has been removed. A superset of its functionality
892 is available in the jedec_dimm(4) driver, and the manpage for that
893 driver includes migration instructions. If you have "device jedec_ts"
894 in your kernel configuration file, it must be removed.
897 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
898 This should have no effect if the kernel is booted via BIOS/legacy boot.
899 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
900 has a buggy firmware that prevents a successful boot due to use of
904 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
905 support has been removed from the tree. These ports were
906 obsolete and/or known to be broken for many years.
909 loader.efi has been augmented to participate more fully in the
910 UEFI boot manager protocol. loader.efi will now look at the
911 BootXXXX environment variable to determine if a specific kernel
912 or root partition was specified. XXXX is derived from BootCurrent.
913 efibootmgr(8) manages these standard UEFI variables.
916 zfsloader's functionality has now been folded into loader.
917 zfsloader is no longer necessary once you've updated your
918 boot blocks. For a transition period, we will install a
919 hardlink for zfsloader to loader to allow a smooth transition
920 until the boot blocks can be updated (hard link because old
921 zfs boot blocks don't understand symlinks).
924 ARM64 now have efifb support, if you want to have serial console
925 on your arm64 board when an screen is connected and the bootloader
926 setup a frame buffer for us to use, just add :
930 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
931 an screen connected as the firmware will setup a frame buffer are that
932 u-boot will expose as an EFI frame buffer.
935 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
936 or take steps to update /etc/passwd before doing installworld on
937 existing systems. Do not skip the "mergemaster -Fp" step before
938 installworld, as described in the update procedures near the bottom
939 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
940 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
941 the ntp config file contain options that change file/dir locations.
942 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
943 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
944 taking steps to ensure that all required files/dirs are accessible
948 Big endian arm support has been removed.
951 The static environment setup in kernel configs is no longer mutually
952 exclusive with the loader(8) environment by default. In order to
953 restore the previous default behavior of disabling the loader(8)
954 environment if a static environment is present, you must specify
955 loader_env.disabled=1 in the static environment.
958 The ABI of syscalls used by management tools like sockstat and
959 netstat has been broken to allow 32-bit binaries to work on
960 64-bit kernels without modification. These programs will need
961 to match the kernel in order to function. External programs may
962 require minor modifications to accommodate a change of type in
963 structures from pointers to 64-bit virtual addresses.
966 On i386 and amd64 atomics are now inlined. Out of tree modules using
967 atomics will need to be rebuilt.
970 The '%I' format in the kern.corefile sysctl limits the number of
971 core files that a process can generate to the number stored in the
972 debug.ncores sysctl. The '%I' format is replaced by the single digit
973 index. Previously, if all indexes were taken the kernel would overwrite
974 only a core file with the highest index in a filename.
975 Currently the system will create a new core file if there is a free
976 index or if all slots are taken it will overwrite the oldest one.
979 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
980 6.0.1. Please see the 20141231 entry below for information about
981 prerequisites and upgrading, if you are not already using clang 3.5.0
985 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
986 needed to be changed to work with it. This change was made with r335763
987 and requires a mergemaster / etcupdate / etc to update the installed
991 r334930 changed the interface between the NFS modules, so they all
992 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
995 As of r334391 lld is the default amd64 system linker; it is installed
996 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
1000 The kernel / userland interface for devinfo changed, so you'll
1001 need a new kernel and userland as a pair for it to work (rebuilding
1002 lib/libdevinfo is all that's required). devinfo and devmatch will
1003 not work, but everything else will when there's a mismatch.
1006 The on-disk format for hwpmc callchain records has changed to include
1007 threadid corresponding to a given record. This changes the field offsets
1008 and thus requires that libpmcstat be rebuilt before using a kernel
1012 The vxge(4) driver has been removed. This driver was introduced into
1013 HEAD one week before the Exar left the Ethernet market and is not
1014 known to be used. If you have device vxge in your kernel config file
1018 The amd64 kernel now requires a ld that supports ifunc to produce a
1019 working kernel, either lld or a newer binutils. lld is built by default
1020 on amd64, and the 'buildkernel' target uses it automatically. However,
1021 it is not the default linker, so building the kernel the traditional
1022 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
1023 binutils port/package). lld will soon be default, and this requirement
1026 NOTE: As of r334391 lld is the default system linker on amd64, and no
1027 workaround is necessary.
1030 The nxge(4) driver has been removed. This driver was for PCI-X 10g
1031 cards made by s2io/Neterion. The company was acquired by Exar and
1032 no longer sells or supports Ethernet products. If you have device
1033 nxge in your kernel config file it must be removed.
1036 The tz database (tzdb) has been updated to 2018e. This version more
1037 correctly models time stamps in time zones with negative DST such as
1038 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
1039 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
1040 time zone abbreviations and the tm_isdst flag.
1043 The ixgb(4) driver has been removed. This driver was for an early and
1044 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
1045 quickly shifted to the long lived ixgbe family. If you have device
1046 ixgb in your kernel config file it must be removed.
1049 The lmc(4) driver has been removed. This was a WAN interface
1050 card that was already reportedly rare in 2003, and had an ambiguous
1051 license. If you have device lmc in your kernel config file it must
1055 Support for Arcnet networks has been removed. If you have device
1056 arcnet or device cm in your kernel config file they must be
1060 Support for FDDI networks has been removed. If you have device
1061 fddi or device fpa in your kernel config file they must be
1065 In addition to supporting RFC 3164 formatted messages, the
1066 syslogd(8) service is now capable of parsing RFC 5424 formatted
1067 log messages. The main benefit of using RFC 5424 is that clients
1068 may now send log messages with timestamps containing year numbers,
1069 microseconds and time zone offsets.
1071 Similarly, the syslog(3) C library function has been altered to
1072 send RFC 5424 formatted messages to the local system logging
1073 daemon. On systems using syslogd(8), this change should have no
1074 negative impact, as long as syslogd(8) and the C library are
1075 updated at the same time. On systems using a different system
1076 logging daemon, it may be necessary to make configuration
1077 adjustments, depending on the software used.
1079 When using syslog-ng, add the 'syslog-protocol' flag to local
1080 input sources to enable parsing of RFC 5424 formatted messages:
1083 unix-dgram("/var/run/log" flags(syslog-protocol));
1086 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
1087 of the 'imuxsock' module to let messages be processed by the
1088 regular RFC 3164/5424 parsing pipeline:
1090 module(load="imuxsock" SysSock.UseSpecialParser="off")
1092 Do note that these changes only affect communication between local
1093 applications and syslogd(8). The format that syslogd(8) uses to
1094 store messages on disk or forward messages to other systems
1095 remains unchanged. syslogd(8) still uses RFC 3164 for these
1096 purposes. Options to customize this behaviour will be added in the
1097 future. Utilities that process log files stored in /var/log are
1098 thus expected to continue to function as before.
1100 __FreeBSD_version has been incremented to 1200061 to denote this
1104 Support for token ring networks has been removed. If you
1105 have "device token" in your kernel config you should remove
1106 it. No device drivers supported token ring.
1109 makefs was modified to be able to tag ISO9660 El Torito boot catalog
1110 entries as EFI instead of overloading the i386 tag as done previously.
1111 The amd64 mkisoimages.sh script used to build amd64 ISO images for
1112 release was updated to use this. This may mean that makefs must be
1113 updated before "make cdrom" can be run in the release directory. This
1114 should be as simple as:
1116 $ cd $SRCDIR/usr.sbin/makefs
1117 $ make depend all install
1120 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
1121 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
1122 Co-existence for the transition period will come shortly. Booting is a
1123 complex environment and test coverage for Lua-enabled loaders has been
1124 thin, so it would be prudent to assume it might not work and make
1125 provisions for backup boot methods.
1128 devmatch functionality has been turned on in devd. It will automatically
1129 load drivers for unattached devices. This may cause unexpected drivers
1130 to be loaded. Please report any problems to current@ and
1134 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
1135 6.0.0. Please see the 20141231 entry below for information about
1136 prerequisites and upgrading, if you are not already using clang 3.5.0
1140 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
1141 This means it is used to link the kernel and userland libraries and
1142 executables, but is not yet installed as /usr/bin/ld by default.
1144 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
1145 WITHOUT_LLD_BOOTSTRAP=yes
1148 On i386, pmtimer has been removed. Its functionality has been folded
1149 into apm. It was a no-op on ACPI in current for a while now (but was
1150 still needed on i386 in FreeBSD 11 and earlier). Users may need to
1151 remove it from kernel config files.
1154 The use of RSS hash from the network card aka flowid has been
1155 disabled by default for lagg(4) as it's currently incompatible with
1156 the lacp and loadbalance protocols.
1158 This can be re-enabled by setting the following in loader.conf:
1159 net.link.lagg.default_use_flowid="1"
1162 The SW_WATCHDOG option is no longer necessary to enable the
1163 hardclock-based software watchdog if no hardware watchdog is
1164 configured. As before, SW_WATCHDOG will cause the software
1165 watchdog to be enabled even if a hardware watchdog is configured.
1168 r326887 fixes the issue described in the 20171214 UPDATING entry.
1169 r326888 flips the switch back to building GELI support always.
1172 r362593 broke ZFS + GELI support for reasons unknown. However,
1173 it also broke ZFS support generally, so GELI has been turned off
1174 by default as the lesser evil in r326857. If you boot off ZFS and/or
1175 GELI, it might not be a good time to update.
1178 PowerPC users must update loader(8) by rebuilding world before
1179 installing a new kernel, as the protocol connecting them has
1180 changed. Without the update, loader metadata will not be passed
1181 successfully to the kernel and users will have to enter their
1182 root partition at the kernel mountroot prompt to continue booting.
1183 Newer versions of loader can boot old kernels without issue.
1186 The LOADER_FIREWIRE_SUPPORT build variable has been renamed to
1187 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
1188 to WITH/OUT_LOADER_GELI.
1191 The naive and non-compliant support of posix_fallocate(2) in ZFS
1192 has been removed as of r325320. The system call now returns EINVAL
1193 when used on a ZFS file. Although the new behavior complies with the
1194 standard, some consumers are not prepared to cope with it.
1195 One known victim is lld prior to r325420.
1198 Building in a FreeBSD src checkout will automatically create object
1199 directories now rather than store files in the current directory if
1200 'make obj' was not ran. Calling 'make obj' is no longer necessary.
1201 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
1202 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
1206 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
1207 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
1208 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
1209 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
1210 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
1211 The UNIFIED_OBJDIR option is a transitional feature that will be
1212 removed for 12.0 release; please migrate to the new format for any
1213 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
1214 than hardcoding paths.
1217 The native-xtools target no longer installs the files by default to the
1218 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
1219 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
1222 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
1223 options are changing from controlling the build if defined / undefined
1224 to controlling the build with explicit 'yes' or 'no' values. They will
1225 shift to WITH/WITHOUT options to match other options in the system.
1228 libstand has turned into a private library for sys/boot use only.
1229 It is no longer supported as a public interface outside of sys/boot.
1232 The arm port has split armv6 into armv6 and armv7. armv7 is now
1233 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
1234 and are running a kernel from before r324363, you will need to add
1235 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
1238 When building multiple kernels using KERNCONF, non-existent KERNCONF
1239 files will produce an error and buildkernel will fail. Previously
1240 missing KERNCONF files silently failed giving no indication as to
1241 why, only to subsequently discover during installkernel that the
1242 desired kernel was never built in the first place.
1245 The default serial number format for CTL LUNs has changed. This will
1246 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
1247 or iSCSI clients care about their LUNs' serial numbers. Users who
1248 require serial number stability should hardcode serial numbers in
1252 For 32-bit arm compiled for hard-float support, soft-floating point
1253 binaries now always get their shared libraries from
1254 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
1255 /usr/libsoft also existed). Only users with a hard-float ld.so, but
1256 soft-float everything else should be affected.
1259 The geli password typed at boot is now hidden. To restore the previous
1260 behavior, see geli(8) for configuration options.
1263 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
1264 sysctl values. Minor nit, but requires a rebuild of both world/kernel
1268 "make check" behavior (made in ^/head@r295380) has been changed to
1269 execute from a limited sandbox, as opposed to executing from
1273 - The "beforecheck" and "aftercheck" targets are now specified.
1274 - ${CHECKDIR} (added in commit noted above) has been removed.
1275 - Legacy behavior can be enabled by setting
1276 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
1278 If the limited sandbox mode is enabled, "make check" will execute
1279 "make distribution", then install, execute the tests, and clean up the
1280 sandbox if successful.
1282 The "make distribution" and "make install" targets are typically run as
1283 root to set appropriate permissions and ownership at installation time.
1284 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
1285 environment if executing "make check" with limited sandbox mode using
1286 an unprivileged user.
1289 Since the switch to GPT disk labels, fsck for UFS/FFS has been
1290 unable to automatically find alternate superblocks. As of r322297,
1291 the information needed to find alternate superblocks has been
1292 moved to the end of the area reserved for the boot block.
1293 Filesystems created with a newfs of this vintage or later
1294 will create the recovery information. If you have a filesystem
1295 created prior to this change and wish to have a recovery block
1296 created for your filesystem, you can do so by running fsck in
1297 foreground mode (i.e., do not use the -p or -y options). As it
1298 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
1299 to which you should answer yes.
1302 As of r321665, an NFSv4 server configuration that services
1303 Kerberos mounts or clients that do not support the uid/gid in
1304 owner/owner_group string capability, must explicitly enable
1305 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
1306 machine's /etc/rc.conf file.
1309 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
1310 Please see the 20141231 entry below for information about prerequisites
1311 and upgrading, if you are not already using clang 3.5.0 or higher.
1314 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
1315 r-commands (rlogin, rsh, etc.) to be built with the base system.
1318 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
1319 a very major ABI incompatible change, so users of FreeBSD/powerpc must
1320 be careful when performing source upgrades. It is best to run
1321 'make installworld' from an alternate root system, either a live
1322 CD/memory stick, or a temporary root partition. Additionally, all ports
1323 must be recompiled. powerpc64 is largely unaffected, except in the case
1324 of 32-bit compatibility. All 32-bit binaries will be affected.
1327 Forward compatibility for the "ino64" project have been committed. This
1328 will allow most new binaries to run on older kernels in a limited
1329 fashion. This prevents many of the common foot-shooting actions in the
1330 upgrade as well as the limited ability to roll back the kernel across
1331 the ino64 upgrade. Complicated use cases may not work properly, though
1332 enough simpler ones work to allow recovery in most situations.
1335 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
1336 if you require the GPL compiler.
1339 The internal ABI used for communication between the NFS kernel modules
1340 was changed by r320085, so __FreeBSD_version was bumped to
1341 ensure all the NFS related modules are updated together.
1344 The ABI of struct event was changed by extending the data
1345 member to 64bit and adding ext fields. For upgrade, same
1346 precautions as for the entry 20170523 "ino64" must be
1350 The GNU roff toolchain has been removed from base. To render manpages
1351 which are not supported by mandoc(1), man(1) can fallback on GNU roff
1352 from ports (and recommends to install it).
1353 To render roff(7) documents, consider using GNU roff from ports or the
1354 heirloom doctools roff toolchain from ports via pkg install groff or
1355 via pkg install heirloom-doctools.
1358 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
1359 smaller runtime footprint builds. This is useful for embedded systems
1360 which only require one chipset support.
1362 If you load it as a module, make sure this is in /boot/loader.conf:
1366 This will load the HAL, all chip/RF backends and if_ath_pci.
1367 If you have if_ath_pci in /boot/loader.conf, ensure it is after
1368 if_ath or it will not load any HAL chipset support.
1370 If you want to selectively load things (eg on cheaper ARM/MIPS
1371 platforms where RAM is at a premium) you should:
1374 * load the chip modules in question
1375 * load ath_rate, ath_dfs
1377 * load if_ath_pci and/or if_ath_ahb depending upon your particular
1378 bus bind type - this is where probe/attach is done.
1380 For further comments/feedback, poke adrian@ .
1383 The "ino64" 64-bit inode project has been committed, which extends
1384 a number of types to 64 bits. Upgrading in place requires care and
1385 adherence to the documented upgrade procedure.
1387 If using a custom kernel configuration ensure that the
1388 COMPAT_FREEBSD11 option is included (as during the upgrade the
1389 system will be running the ino64 kernel with the existing world).
1391 For the safest in-place upgrade begin by removing previous build
1392 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full
1393 procedure documented below under the heading "To rebuild everything and
1394 install it on the current system." Specifically, a reboot is required
1395 after installing the new kernel before installing world. While an
1396 installworld normally works by accident from multiuser after rebooting
1397 the proper kernel, there are many cases where this will fail across this
1398 upgrade and installworld from single user is required.
1401 The NATM framework including the en(4), fatm(4), hatm(4), and
1402 patm(4) devices has been removed. Consumers should plan a
1403 migration before the end-of-life date for FreeBSD 11.
1406 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
1407 diff has not been implemented, if those are needed a newer version of
1408 GNU diff is available via the diffutils package under the gdiff name.
1411 As of r316810 for ipfilter, keep frags is no longer assumed when
1412 keep state is specified in a rule. r316810 aligns ipfilter with
1413 documentation in man pages separating keep frags from keep state.
1414 This allows keep state to be specified without forcing keep frags
1415 and allows keep frags to be specified independently of keep state.
1416 To maintain previous behaviour, also specify keep frags with
1417 keep state (as documented in ipf.conf.5).
1420 arm64 builds now use the base system LLD 4.0.0 linker by default,
1421 instead of requiring that the aarch64-binutils port or package be
1422 installed. To continue using aarch64-binutils, set
1423 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
1426 The UDP optimization in entry 20160818 that added the sysctl
1427 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
1428 packets will no longer be treated as L3 broadcast packets.
1431 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
1432 use any explicitly assigned loopback address available in the jail
1433 instead of using the first assigned address of the jail.
1436 The ctl.ko module no longer implements the iSCSI target frontend:
1437 cfiscsi.ko does instead.
1439 If building cfiscsi.ko as a kernel module, the module can be loaded
1440 via one of the following methods:
1441 - `cfiscsi_load="YES"` in loader.conf(5).
1442 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
1443 - ctladm(8)/ctld(8), when compiled with iSCSI support
1444 (`WITH_ISCSI=yes` in src.conf(5))
1446 Please see cfiscsi(4) for more details.
1449 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
1450 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
1451 same source (previously, the dependency of mmcsd.ko on mmc.ko was
1452 missing, but mmcsd.ko now will refuse to load if it is incompatible
1456 The syntax of ipfw(8) named states was changed to avoid ambiguity.
1457 If you have used named states in the firewall rules, you need to modify
1458 them after installworld and before rebooting. Now named states must
1459 be prefixed with colon.
1462 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
1463 removed as the userland we provide cannot use them. The KMS version
1464 (sys/dev/drm2) supports the same hardware.
1467 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
1468 Please see the 20141231 entry below for information about prerequisites
1469 and upgrading, if you are not already using clang 3.5.0 or higher.
1472 The code that provides support for ZFS .zfs/ directory functionality
1473 has been reimplemented. It's not possible now to create a snapshot
1474 by mkdir under .zfs/snapshot/. That should be the only user visible
1478 EISA bus support has been removed. The WITH_EISA option is no longer
1482 MCA bus support has been removed.
1485 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
1486 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
1489 The EM_MULTIQUEUE kernel configuration option is deprecated now that
1490 the em(4) driver conforms to iflib specifications.
1493 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
1494 IFLIB. If you have a custom kernel configuration that excludes em(4)
1495 but you use igb(4), you need to re-add em(4) to your custom
1499 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
1500 Please see the 20141231 entry below for information about prerequisites
1501 and upgrading, if you are not already using clang 3.5.0 or higher.
1504 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
1505 Please see the 20141231 entry below for information about prerequisites
1506 and upgrading, if you are not already using clang 3.5.0 or higher.
1509 The layout of the pmap structure has changed for powerpc to put the pmap
1510 statistics at the front for all CPU variations. libkvm(3) and all tools
1511 that link against it need to be recompiled.
1514 isl(4) and cyapa(4) drivers now require a new driver,
1515 chromebook_platform(4), to work properly on Chromebook-class hardware.
1516 On other types of hardware the drivers may need to be configured using
1517 device hints. Please see the corresponding manual pages for details.
1520 The urtwn(4) driver was merged into rtwn(4) and now consists of
1521 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
1523 Also, firmware for RTL8188CE was renamed due to possible name
1524 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
1527 GNU rcs has been removed from base. It is available as packages:
1528 - rcs: Latest GPLv3 GNU rcs version.
1529 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
1533 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
1534 modules now requires that the kernel configuration contain the
1535 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
1538 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
1539 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
1542 Relocatable object files with the extension of .So have been renamed
1543 to use an extension of .pico instead. The purpose of this change is
1544 to avoid a name clash with shared libraries on case-insensitive file
1545 systems. On those file systems, foo.So is the same file as foo.so.
1548 GNU rcs has been turned off by default. It can (temporarily) be built
1549 again by adding WITH_RCS knob in src.conf.
1550 Otherwise, GNU rcs is available from packages:
1551 - rcs: Latest GPLv3 GNU rcs version.
1552 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
1555 The backup_uses_rcs functionality has been removed from rc.subr.
1558 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
1559 two separate components, QUEUE_MACRO_DEBUG_TRACE and
1560 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
1561 QUEUE_MACRO_DEBUG behavior.
1564 r304787 changed some ioctl interfaces between the iSCSI userspace
1565 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1566 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1570 The UDP receive code has been updated to only treat incoming UDP
1571 packets that were addressed to an L2 broadcast address as L3
1572 broadcast packets. It is not expected that this will affect any
1573 standards-conforming UDP application. The new behaviour can be
1574 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1578 Remove the openbsd_poll system call.
1579 __FreeBSD_version has been bumped because of this.
1582 The stable/11 branch has been created from head@r302406.
1585 The libc stub for the pipe(2) system call has been replaced with
1586 a wrapper that calls the pipe2(2) system call and the pipe(2)
1587 system call is now only implemented by the kernels that include
1588 "options COMPAT_FREEBSD10" in their config file (this is the
1589 default). Users should ensure that this option is enabled in
1590 their kernel or upgrade userspace to r302092 before upgrading their
1594 CAM now strips the leading spaces from each SCSI disk's serial number.
1595 This will affect users who create UFS filesystems on SCSI disks using
1596 those disk's diskid device nodes. For example, if /etc/fstab
1597 previously contained a line like
1598 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
1599 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
1600 transforms like gmirror may also be affected. ZFS users should
1604 The bitstring(3) API has been updated with new functionality and
1605 improved performance. But it is binary-incompatible with the old API.
1606 Objects built with the new headers may not be linked against objects
1607 built with the old headers.
1610 The brk and sbrk functions have been removed from libc on arm64.
1611 Binutils from ports has been updated to not link to these
1612 functions and should be updated to the latest version before
1613 installing a new libc.
1616 The armv6 port now defaults to hard float ABI. Limited support
1617 for running both hardfloat and soft float on the same system
1618 is available using the libraries installed with -DWITH_LIBSOFT.
1619 This has only been tested as an upgrade path for installworld
1620 and packages may fail or need manual intervention to run. New
1621 packages will be needed.
1623 To update an existing self-hosted armv6hf system, you must add
1624 TARGET_ARCH=armv6 on the make command line for both the build
1625 and the install steps.
1628 Kernel modules compiled outside of a kernel build now default to
1629 installing to /boot/modules instead of /boot/kernel. Many kernel
1630 modules built this way (such as those in ports) already overrode
1631 KMODDIR explicitly to install into /boot/modules. However,
1632 manually building and installing a module from /sys/modules will
1633 now install to /boot/modules instead of /boot/kernel.
1636 The CAM I/O scheduler has been committed to the kernel. There should be
1637 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1638 list of known rogues that claim support for this but actually corrupt
1639 data is believed to be complete, be on the lookout for data
1640 corruption. The known rogue list is believed to be complete:
1642 o Crucial MX100, M550 drives with MU01 firmware.
1643 o Micron M510 and M550 drives with MU01 firmware.
1644 o Micron M500 prior to MU07 firmware
1645 o Samsung 830, 840, and 850 all firmwares
1646 o FCCT M500 all firmwares
1648 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1649 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1650 updated firmware. Black listed drives will work correctly because these
1651 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1652 this list is the same as found in Linux, it's believed there are no
1653 other rogues in the market place. All other models from the above
1656 To be safe, if you are at all concerned, you can quirk each of your
1657 drives to prevent NCQ from being sent by setting:
1658 kern.cam.ada.X.quirks="0x2"
1659 in loader.conf. If the drive requires the 4k sector quirk, set the
1660 quirks entry to 0x3.
1663 The FAST_DEPEND build option has been removed and its functionality is
1664 now the one true way. The old mkdep(1) style of 'make depend' has
1665 been removed. See 20160311 for further details.
1668 Resource range types have grown from unsigned long to uintmax_t. All
1669 drivers, and anything using libdevinfo, need to be recompiled.
1672 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1673 builds. It no longer runs mkdep(1) during 'make depend', and the
1674 'make depend' stage can safely be skipped now as it is auto ran
1675 when building 'make all' and will generate all SRCS and DPSRCS before
1676 building anything else. Dependencies are gathered at compile time with
1677 -MF flags kept in separate .depend files per object file. Users should
1678 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1679 stale .depend files.
1682 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1683 kernel modules. Therefore, if you load any kernel modules at boot time,
1684 please install the boot loaders after you install the kernel, but before
1688 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1689 make installkernel KERNCONF=YOUR_KERNEL_HERE
1690 make -C sys/boot install
1691 <reboot in single user>
1693 Then follow the usual steps, described in the General Notes section,
1697 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1698 see the 20141231 entry below for information about prerequisites and
1699 upgrading, if you are not already using clang 3.5.0 or higher.
1702 The AIO subsystem is now a standard part of the kernel. The
1703 VFS_AIO kernel option and aio.ko kernel module have been removed.
1704 Due to stability concerns, asynchronous I/O requests are only
1705 permitted on sockets and raw disks by default. To enable
1706 asynchronous I/O requests on all file types, set the
1707 vfs.aio.enable_unsafe sysctl to a non-zero value.
1710 The ELF object manipulation tool objcopy is now provided by the
1711 ELF Tool Chain project rather than by GNU binutils. It should be a
1712 drop-in replacement, with the addition of arm64 support. The
1713 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1714 to obtain the GNU version if necessary.
1717 Building ZFS pools on top of zvols is prohibited by default. That
1718 feature has never worked safely; it's always been prone to deadlocks.
1719 Using a zvol as the backing store for a VM guest's virtual disk will
1720 still work, even if the guest is using ZFS. Legacy behavior can be
1721 restored by setting vfs.zfs.vol.recursive=1.
1724 The NONE and HPN patches has been removed from OpenSSH. They are
1725 still available in the security/openssh-portable port.
1728 With the addition of ypldap(8), a new _ypldap user is now required
1729 during installworld. "mergemaster -p" can be used to add the user
1730 prior to installworld, as documented in the handbook.
1733 The tftp loader (pxeboot) now uses the option root-path directive. As a
1734 consequence it no longer looks for a pxeboot.4th file on the tftp
1735 server. Instead it uses the regular /boot infrastructure as with the
1739 The code to start recording plug and play data into the modules has
1740 been committed. While the old tools will properly build a new kernel,
1741 a number of warnings about "unknown metadata record 4" will be produced
1742 for an older kldxref. To avoid such warnings, make sure to rebuild
1743 the kernel toolchain (or world). Make sure that you have r292078 or
1744 later when trying to build 292077 or later before rebuilding.
1747 Debug data files are now built by default with 'make buildworld' and
1748 installed with 'make installworld'. This facilitates debugging but
1749 requires more disk space both during the build and for the installed
1750 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1754 r291527 changed the internal interface between the nfsd.ko and
1755 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1756 __FreeBSD_version has been bumped because of this.
1759 Add support for unicode collation strings leads to a change of
1760 order of files listed by ls(1) for example. To get back to the old
1761 behaviour, set LC_COLLATE environment variable to "C".
1763 Databases administrators will need to reindex their databases given
1764 collation results will be different.
1766 Due to a bug in install(1) it is recommended to remove the ancient
1767 locales before running make installworld.
1769 rm -rf /usr/share/locale/*
1772 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1773 libcrypto.so.7 or libssl.so.7 must be recompiled.
1776 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1777 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1778 should be replaced with isp_2400 and isp_2500 modules respectively.
1781 The build previously allowed using 'make -n' to not recurse into
1782 sub-directories while showing what commands would be executed, and
1783 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1784 and 'make -N' will not.
1787 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1788 and etcupdate will now use this file. A custom sendmail.cf is now
1789 updated via this mechanism rather than via installworld. If you had
1790 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1791 want to remove the exclusion or change it to "always install".
1792 /etc/mail/sendmail.cf is now managed the same way regardless of
1793 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1794 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1797 Compatibility shims for legacy ATA device names have been removed.
1798 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1799 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1800 environment variables, /dev/ad* and /dev/ar* symbolic links.
1803 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1804 Please see the 20141231 entry below for information about prerequisites
1805 and upgrading, if you are not already using clang 3.5.0 or higher.
1808 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1809 and renamed from .symbols to .debug. This reduces the size requirements
1810 on the boot partition or file system and provides consistency with
1811 userland debug files.
1813 When using the supported kernel installation method the
1814 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1815 as is done with /boot/kernel.
1817 Developers wishing to maintain the historical behavior of installing
1818 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1821 The wireless drivers had undergone changes that remove the 'parent
1822 interface' from the ifconfig -l output. The rc.d network scripts
1823 used to check presence of a parent interface in the list, so old
1824 scripts would fail to start wireless networking. Thus, etcupdate(3)
1825 or mergemaster(8) run is required after kernel update, to update your
1826 rc.d scripts in /etc.
1829 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1830 These configurations are now automatically interpreted as
1831 'scrub fragment reassemble'.
1834 Kernel-loadable modules for the random(4) device are back. To use
1835 them, the kernel must have
1838 options RANDOM_LOADABLE
1840 kldload(8) can then be used to load random_fortuna.ko
1841 or random_yarrow.ko. Please note that due to the indirect
1842 function calls that the loadable modules need to provide,
1843 the build-in variants will be slightly more efficient.
1845 The random(4) kernel option RANDOM_DUMMY has been retired due to
1846 unpopularity. It was not all that useful anyway.
1849 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1850 Control over building the ELF Tool Chain tools is now provided by
1851 the WITHOUT_TOOLCHAIN knob.
1854 The polarity of Pulse Per Second (PPS) capture events with the
1855 uart(4) driver has been corrected. Prior to this change the PPS
1856 "assert" event corresponded to the trailing edge of a positive PPS
1857 pulse and the "clear" event was the leading edge of the next pulse.
1859 As the width of a PPS pulse in a typical GPS receiver is on the
1860 order of 1 millisecond, most users will not notice any significant
1861 difference with this change.
1863 Anyone who has compensated for the historical polarity reversal by
1864 configuring a negative offset equal to the pulse width will need to
1865 remove that workaround.
1868 The default group assigned to /dev/dri entries has been changed
1869 from 'wheel' to 'video' with the id of '44'. If you want to have
1870 access to the dri devices please add yourself to the video group
1873 # pw groupmod video -m $USER
1876 The menu.rc and loader.rc files will now be replaced during
1877 upgrades. Please migrate local changes to menu.rc.local and
1878 loader.rc.local instead.
1881 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1882 strings and strip have been removed. The src.conf(5) knob
1883 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1886 As ZFS requires more kernel stack pages than is the default on some
1887 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1888 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1890 Please consider using 'options KSTACK_PAGES=X' where X is greater
1891 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1894 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1895 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1896 default, i.e., they will not contain "::". For example, instead
1897 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1898 to have a more specific match, such as different map entries for
1899 IPv6:0:0 vs IPv6:0. This change requires that configuration
1900 data (including maps, files, classes, custom ruleset, etc.) must
1901 use the same format, so make certain such configuration data is
1902 upgrading. As a very simple check search for patterns like
1903 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1904 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1905 the cf option UseCompressedIPv6Addresses.
1908 The default kernel entropy-processing algorithm is now
1909 Fortuna, replacing Yarrow.
1911 Assuming you have 'device random' in your kernel config
1912 file, the configurations allow a kernel option to override
1913 this default. You may choose *ONE* of:
1915 options RANDOM_YARROW # Legacy /dev/random algorithm.
1916 options RANDOM_DUMMY # Blocking-only driver.
1918 If you have neither, you get Fortuna. For most people,
1919 read no further, Fortuna will give a /dev/random that works
1920 like it always used to, and the difference will be irrelevant.
1922 If you remove 'device random', you get *NO* kernel-processed
1923 entropy at all. This may be acceptable to folks building
1924 embedded systems, but has complications. Carry on reading,
1925 and it is assumed you know what you need.
1927 *PLEASE* read random(4) and random(9) if you are in the
1928 habit of tweaking kernel configs, and/or if you are a member
1929 of the embedded community, wanting specific and not-usual
1930 behaviour from your security subsystems.
1932 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1933 random', you will NOT have a functioning /dev/random, and
1934 many cryptographic features will not work, including SSH.
1935 You may also find strange behaviour from the random(3) set
1936 of library functions, in particular sranddev(3), srandomdev(3)
1937 and arc4random(3). The reason for this is that the KERN_ARND
1938 sysctl only returns entropy if it thinks it has some to
1939 share, and with RANDOM_DUMMY or no 'device random' this
1943 An additional fix for the issue described in the 20150614 sendmail
1944 entry below has been committed in revision 284717.
1947 FreeBSD's old make (fmake) has been removed from the system. It is
1948 available as the devel/fmake port or via pkg install fmake.
1951 The fix for the issue described in the 20150614 sendmail entry
1952 below has been committed in revision 284436. The work
1953 around described in that entry is no longer needed unless the
1954 default setting is overridden by a confDH_PARAMETERS configuration
1955 setting of '5' or pointing to a 512 bit DH parameter file.
1958 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1959 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1960 and devel/kyua to version 0.20+ and adjust any calling code to work
1961 with Kyuafile and kyua.
1964 The import of openssl to address the FreeBSD-SA-15:10.openssl
1965 security advisory includes a change which rejects handshakes
1966 with DH parameters below 768 bits. sendmail releases prior
1967 to 8.15.2 (not yet released), defaulted to a 512 bit
1968 DH parameter setting for client connections. To work around
1969 this interoperability, sendmail can be configured to use a
1970 2048 bit DH parameter by:
1972 1. Edit /etc/mail/`hostname`.mc
1973 2. If a setting for confDH_PARAMETERS does not exist or
1974 exists and is set to a string beginning with '5',
1975 replace it with '2'.
1976 3. If a setting for confDH_PARAMETERS exists and is set to
1977 a file path, create a new file with:
1978 openssl dhparam -out /path/to/file 2048
1979 4. Rebuild the .cf file:
1980 cd /etc/mail/; make; make install
1981 5. Restart sendmail:
1982 cd /etc/mail/; make restart
1984 A sendmail patch is coming, at which time this file will be
1988 Generation of legacy formatted entries have been disabled by default
1989 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1990 entries were converted to use the new format by default when the new,
1991 machine independent format have been added and supported since FreeBSD
1994 Please see the pwd_mkdb(8) manual page for further details.
1997 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1998 20141231 entry below for information about prerequisites and upgrading,
1999 if you are not already using 3.5.0 or higher.
2002 TI platform code switched to using vendor DTS files and this update
2003 may break existing systems running on Beaglebone, Beaglebone Black,
2006 - dtb files should be regenerated/reinstalled. Filenames are the
2007 same but content is different now
2008 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
2009 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
2010 addressing scheme is now pin 25 on /dev/gpioc3.
2011 - Pandaboard: /etc/ttys should be updated, serial console device is
2012 now /dev/ttyu2, not /dev/ttyu0
2015 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
2016 If you need the GNU extension from groff soelim(1), install groff
2017 from package: pkg install groff, or via ports: textproc/groff.
2020 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
2021 defined in symlink(7); previously symlinks were silently ignored.
2024 The const qualifier has been removed from iconv(3) to comply with
2025 POSIX. The ports tree is aware of this from r384038 onwards.
2028 Libraries specified by LIBADD in Makefiles must have a corresponding
2029 DPADD_<lib> variable to ensure correct dependencies. This is now
2030 enforced in src.libnames.mk.
2033 From legacy ata(4) driver was removed support for SATA controllers
2034 supported by more functional drivers ahci(4), siis(4) and mvs(4).
2035 Kernel modules ataahci and ataadaptec were removed completely,
2036 replaced by ahci and mvs modules respectively.
2039 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
2040 the 20141231 entry below for information about prerequisites and
2041 upgrading, if you are not already using 3.5.0 or higher.
2044 The 32-bit PowerPC kernel has been changed to a position-independent
2045 executable. This can only be booted with a version of loader(8)
2046 newer than January 31, 2015, so make sure to update both world and
2047 kernel before rebooting.
2050 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
2051 but before r278950, the RNG was not seeded properly. Immediately
2052 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
2053 ssh keys or openssl keys) that were generated w/ a kernel from that
2054 range. This does not affect programs that directly used /dev/random
2055 or /dev/urandom. All userland uses of arc4random(3) are affected.
2058 The autofs(4) ABI was changed in order to restore binary compatibility
2059 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
2060 with the new kernel.
2063 The powerpc64 kernel has been changed to a position-independent
2064 executable. This can only be booted with a new version of loader(8),
2065 so make sure to update both world and kernel before rebooting.
2068 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
2069 only release, no new features have been added. Please see the 20141231
2070 entry below for information about prerequisites and upgrading, if you
2071 are not already using 3.5.0.
2074 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
2075 taken from the ELF Tool Chain project rather than GNU binutils. They
2076 should be drop-in replacements, with the addition of arm64 support.
2077 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
2078 binutils tools, if necessary. See 20150805 for updated information.
2081 The default Unbound configuration now enables remote control
2082 using a local socket. Users who have already enabled the
2083 local_unbound service should regenerate their configuration
2084 by running "service local_unbound setup" as root.
2087 The GNU texinfo and GNU info pages have been removed.
2088 To be able to view GNU info pages please install texinfo from ports.
2091 Clang, llvm and lldb have been upgraded to 3.5.0 release.
2093 As of this release, a prerequisite for building clang, llvm and lldb is
2094 a C++11 capable compiler and C++11 standard library. This means that to
2095 be able to successfully build the cross-tools stage of buildworld, with
2096 clang as the bootstrap compiler, your system compiler or cross compiler
2097 should either be clang 3.3 or later, or gcc 4.8 or later, and your
2098 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
2101 On any standard FreeBSD 10.x or 11.x installation, where clang and
2102 libc++ are on by default (that is, on x86 or arm), this should work out
2105 On 9.x installations where clang is enabled by default, e.g. on x86 and
2106 powerpc, libc++ will not be enabled by default, so libc++ should be
2107 built (with clang) and installed first. If both clang and libc++ are
2108 missing, build clang first, then use it to build libc++.
2110 On 8.x and earlier installations, upgrade to 9.x first, and then follow
2111 the instructions for 9.x above.
2113 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
2114 default, and do not build clang.
2116 Many embedded systems are resource constrained, and will not be able to
2117 build clang in a reasonable time, or in some cases at all. In those
2118 cases, cross building bootable systems on amd64 is a workaround.
2120 This new version of clang introduces a number of new warnings, of which
2121 the following are most likely to appear:
2125 This warns in two cases, for both C and C++:
2126 * When the code is trying to take the absolute value of an unsigned
2127 quantity, which is effectively a no-op, and almost never what was
2128 intended. The code should be fixed, if at all possible. If you are
2129 sure that the unsigned quantity can be safely cast to signed, without
2130 loss of information or undefined behavior, you can add an explicit
2131 cast, or disable the warning.
2133 * When the code is trying to take an absolute value, but the called
2134 abs() variant is for the wrong type, which can lead to truncation.
2135 If you want to disable the warning instead of fixing the code, please
2136 make sure that truncation will not occur, or it might lead to unwanted
2139 -Wtautological-undefined-compare and
2140 -Wundefined-bool-conversion
2142 These warn when C++ code is trying to compare 'this' against NULL, while
2143 'this' should never be NULL in well-defined C++ code. However, there is
2144 some legacy (pre C++11) code out there, which actively abuses this
2145 feature, which was less strictly defined in previous C++ versions.
2147 Squid and openjdk do this, for example. The warning can be turned off
2148 for C++98 and earlier, but compiling the code in C++11 mode might result
2149 in unexpected behavior; for example, the parts of the program that are
2150 unreachable could be optimized away.
2153 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
2154 kernel sources have been removed. The .h files remain, since some
2155 utilities include them. This will need to be fixed later.
2156 If "mount -t oldnfs ..." is attempted, it will fail.
2157 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
2158 the utilities will report errors.
2161 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
2162 directories to top level SUBDIR variable when their parent
2163 directory is included in LOCAL_DIRS. Users with build systems with
2164 such hierarchies and without SUBDIR entries in the parent
2165 directory Makefiles should add them or add the directories to
2169 faith(4) and faithd(8) have been removed from the base system. Faith
2170 has been obsolete for a very long time.
2173 vt(4), the new console driver, is enabled by default. It brings
2174 support for Unicode and double-width characters, as well as
2175 support for UEFI and integration with the KMS kernel video
2178 You may need to update your console settings in /etc/rc.conf,
2179 most probably the keymap. During boot, /etc/rc.d/syscons will
2180 indicate what you need to do.
2182 vt(4) still has issues and lacks some features compared to
2183 syscons(4). See the wiki for up-to-date information:
2184 https://wiki.freebsd.org/Newcons
2186 If you want to keep using syscons(4), you can do so by adding
2187 the following line to /boot/loader.conf:
2191 pjdfstest has been integrated into kyua as an opt-in test suite.
2192 Please see share/doc/pjdfstest/README for more details on how to
2196 gperf has been removed from the base system for architectures
2197 that use clang. Ports that require gperf will obtain it from the
2201 pjdfstest has been moved from tools/regression/pjdfstest to
2205 At svn r271982, The default linux compat kernel ABI has been adjusted
2206 to 2.6.18 in support of the linux-c6 compat ports infrastructure
2207 update. If you wish to continue using the linux-f10 compat ports,
2208 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
2209 encouraged to update their linux-compat packages to linux-c6 during
2210 their next update cycle.
2213 The ofwfb driver, used to provide a graphics console on PowerPC when
2214 using vt(4), no longer allows mmap() of all physical memory. This
2215 will prevent Xorg on PowerPC with some ATI graphics cards from
2216 initializing properly unless x11-servers/xorg-server is updated to
2220 The xdev targets have been converted to using TARGET and
2221 TARGET_ARCH instead of XDEV and XDEV_ARCH.
2224 The default unbound configuration has been modified to address
2225 issues with reverse lookups on networks that use private
2226 address ranges. If you use the local_unbound service, run
2227 "service local_unbound setup" as root to regenerate your
2228 configuration, then "service local_unbound reload" to load the
2232 The GNU texinfo and GNU info pages are not built and installed
2233 anymore, WITH_INFO knob has been added to allow to built and install
2235 UPDATE: see 20150102 entry on texinfo's removal
2238 The GNU readline library is now an INTERNALLIB - that is, it is
2239 statically linked into consumers (GDB and variants) in the base
2240 system, and the shared library is no longer installed. The
2241 devel/readline port is available for third party software that
2245 The Itanium architecture (ia64) has been removed from the list of
2246 known architectures. This is the first step in the removal of the
2250 Commit r268115 has added NFSv4.1 server support, merged from
2251 projects/nfsv4.1-server. Since this includes changes to the
2252 internal interfaces between the NFS related modules, a full
2253 build of the kernel and modules will be necessary.
2254 __FreeBSD_version has been bumped.
2257 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
2258 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
2259 which differs from the behaviour controlled by this knob.)
2262 Maximal length of the serial number in CTL was increased from 16 to
2263 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
2264 and ctld, need to be rebuilt to work with a new kernel.
2267 The libatf-c and libatf-c++ major versions were downgraded to 0 and
2268 1 respectively to match the upstream numbers. They were out of
2269 sync because, when they were originally added to FreeBSD, the
2270 upstream versions were not respected. These libraries are private
2271 and not yet built by default, so renumbering them should be a
2272 non-issue. However, unclean source trees will yield broken test
2273 programs once the operator executes "make delete-old-libs" after a
2274 "make installworld".
2276 Additionally, the atf-sh binary was made private by moving it into
2277 /usr/libexec/. Already-built shell test programs will keep the
2278 path to the old binary so they will break after "make delete-old"
2281 If you are using WITH_TESTS=yes (not the default), wipe the object
2282 tree and rebuild from scratch to prevent spurious test failures.
2283 This is only needed once: the misnumbered libraries and misplaced
2284 binaries have been added to OptionalObsoleteFiles.inc so they will
2285 be removed during a clean upgrade.
2288 Clang and llvm have been upgraded to 3.4.1 release.
2291 We bogusly installed src.opts.mk in /usr/share/mk. This file should
2292 be removed to avoid issues in the future (and has been added to
2296 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
2297 past, it affected all builds that used the bsd.*.mk files. The old
2298 behavior was a bug, but people may have relied upon it. To get this
2299 behavior back, you can .include /etc/src.conf from /etc/make.conf
2300 (which is still global and isn't changed). This also changes the
2301 behavior of incremental builds inside the tree of individual
2302 directories. Set MAKESYSPATH to ".../share/mk" to do that.
2303 Although this has survived make universe and some upgrade scenarios,
2304 other upgrade scenarios may have broken. At least one form of
2305 temporary breakage was fixed with MAKESYSPATH settings for buildworld
2306 as well... In cases where MAKESYSPATH isn't working with this
2307 setting, you'll need to set it to the full path to your tree.
2309 One side effect of all this cleaning up is that bsd.compiler.mk
2310 is no longer implicitly included by bsd.own.mk. If you wish to
2311 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
2315 The lindev device has been removed since /dev/full has been made a
2316 standard device. __FreeBSD_version has been bumped.
2319 The knob WITHOUT_VI was added to the base system, which controls
2320 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
2321 in order to reorder files share/termcap and didn't build ex(1) as a
2322 build tool, so building/installing with WITH_VI is highly advised for
2323 build hosts for older releases.
2325 This issue has been fixed in stable/9 and stable/10 in r277022 and
2326 r276991, respectively.
2329 The YES_HESIOD knob has been removed. It has been obsolete for
2330 a decade. Please move to using WITH_HESIOD instead or your builds
2331 will silently lack HESIOD.
2334 The uart(4) driver has been changed with respect to its handling
2335 of the low-level console. Previously the uart(4) driver prevented
2336 any process from changing the baudrate or the CLOCAL and HUPCL
2337 control flags. By removing the restrictions, operators can make
2338 changes to the serial console port without having to reboot.
2339 However, when getty(8) is started on the serial device that is
2340 associated with the low-level console, a misconfigured terminal
2341 line in /etc/ttys will now have a real impact.
2342 Before upgrading the kernel, make sure that /etc/ttys has the
2343 serial console device configured as 3wire without baudrate to
2344 preserve the previous behaviour. E.g:
2345 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
2348 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
2349 to improve performance. To re-enable it, if needed, run rpcbind
2350 with command line option -W.
2353 Switched back to the GPL dtc compiler due to updates in the upstream
2354 dts files not being supported by the BSDL dtc compiler. You will need
2355 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
2356 may result while building dtb files during a kernel build if you fail
2357 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
2360 Clang and llvm have been upgraded to 3.4 release.
2363 The nve(4) driver has been removed. Please use the nfe(4) driver
2364 for NVIDIA nForce MCP Ethernet adapters instead.
2367 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
2368 This could cause certain C++ applications using shared libraries built
2369 against the previous version of libc++ to crash. The incompatibility
2370 has now been fixed, but any C++ applications or shared libraries built
2371 between r261283 and r261801 should be recompiled.
2374 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
2375 capability mode support. Please note that enabling the feature in
2376 kernel is still highly recommended.
2379 OpenSSH is now built with sandbox support, and will use sandbox as
2380 the default privilege separation method. This requires Capsicum
2381 capability mode support in kernel.
2384 The libelf and libdwarf libraries have been updated to newer
2385 versions from upstream. Shared library version numbers for
2386 these two libraries were bumped. Any ports or binaries
2387 requiring these two libraries should be recompiled.
2388 __FreeBSD_version is bumped to 1100006.
2391 If a Makefile in a tests/ directory was auto-generating a Kyuafile
2392 instead of providing an explicit one, this would prevent such
2393 Makefile from providing its own Kyuafile in the future during
2394 NO_CLEAN builds. This has been fixed in the Makefiles but manual
2395 intervention is needed to clean an objdir if you use NO_CLEAN:
2396 # find /usr/obj -name Kyuafile | xargs rm -f
2399 The behavior of gss_pseudo_random() for the krb5 mechanism
2400 has changed, for applications requesting a longer random string
2401 than produced by the underlying enctype's pseudo-random() function.
2402 In particular, the random string produced from a session key of
2403 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
2404 be different at the 17th octet and later, after this change.
2405 The counter used in the PRF+ construction is now encoded as a
2406 big-endian integer in accordance with RFC 4402.
2407 __FreeBSD_version is bumped to 1100004.
2410 The WITHOUT_ATF build knob has been removed and its functionality
2411 has been subsumed into the more generic WITHOUT_TESTS. If you were
2412 using the former to disable the build of the ATF libraries, you
2413 should change your settings to use the latter.
2416 The default version of mtree is nmtree which is obtained from
2417 NetBSD. The output is generally the same, but may vary
2418 slightly. If you found you need identical output adding
2419 "-F freebsd9" to the command line should do the trick. For the
2420 time being, the old mtree is available as fmtree.
2423 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
2424 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
2425 1.1.4_8 and verify bsdyml not linked in, before running "make
2427 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
2429 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
2432 The stable/10 branch has been created in subversion from head
2439 Sometimes, obscure build problems are the result of environment
2440 poisoning. This can happen because the make utility reads its
2441 environment when searching for values for global variables. To run
2442 your build attempts in an "environmental clean room", prefix all make
2443 commands with 'env -i '. See the env(1) manual page for more details.
2444 Occasionally a build failure will occur with "make -j" due to a race
2445 condition. If this happens try building again without -j, and please
2446 report a bug if it happens consistently.
2448 When upgrading from one major version to another it is generally best to
2449 upgrade to the latest code in the currently installed branch first, then
2450 do an upgrade to the new branch. This is the best-tested upgrade path,
2451 and has the highest probability of being successful. Please try this
2452 approach if you encounter problems with a major version upgrade. Since
2453 the stable 4.x branch point, one has generally been able to upgrade from
2454 anywhere in the most recent stable branch to head / current (or even the
2455 last couple of stable branches). See the top of this file when there's
2458 The update process will emit an error on an attempt to perform a build
2459 or install from a FreeBSD version below the earliest supported version.
2460 When updating from an older version the update should be performed one
2461 major release at a time, including running `make delete-old` at each
2464 When upgrading a live system, having a root shell around before
2465 installing anything can help undo problems. Not having a root shell
2466 around can lead to problems if pam has changed too much from your
2467 starting point to allow continued authentication after the upgrade.
2469 This file should be read as a log of events. When a later event changes
2470 information of a prior event, the prior event should not be deleted.
2471 Instead, a pointer to the entry with the new information should be
2472 placed in the old entry. Readers of this file should also sanity check
2473 older entries before relying on them blindly. Authors of new entries
2474 should write them with this in mind.
2478 When upgrading the boot ZFS pool to a new version, always follow
2481 1.) recompile and reinstall the ZFS boot loader and boot block
2482 (this is part of "make buildworld" and "make installworld")
2484 2.) update the ZFS boot block on your boot drive
2486 The following example updates the ZFS boot block on the
2487 freebsd-boot partition of a GPT partitioned drive ada0:
2488 "gpart bootcode -p /boot/gptzfsboot -i $N ada0"
2489 The value $N will typically be 1 (if booting from BIOS) or 2 (if
2492 Non-boot pools do not need these updates.
2496 If you are updating from a prior version of FreeBSD (even one just
2497 a few days old), you should follow this procedure. It is the most
2498 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2500 make kernel-toolchain
2501 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2502 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2504 To test a kernel once
2505 ---------------------
2506 If you just want to boot a kernel once (because you are not sure
2507 if it works, or if you want to boot a known bad kernel to provide
2508 debugging information) run
2509 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2510 nextboot -k testkernel
2512 To rebuild everything and install it on the current system.
2513 -----------------------------------------------------------
2514 # Note: sometimes if you are running current you gotta do more than
2515 # is listed here if you are upgrading from a really old current.
2517 <make sure you have good level 0 dumps>
2519 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2520 make installkernel KERNCONF=YOUR_KERNEL_HERE
2522 <reboot in single user> [3]
2529 To cross-install current onto a separate partition
2530 --------------------------------------------------
2531 # In this approach we use a separate partition to hold
2532 # current's root, 'usr', and 'var' directories. A partition
2533 # holding "/", "/usr" and "/var" should be about 2GB in
2536 <make sure you have good level 0 dumps>
2539 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2540 <maybe newfs current's root partition>
2541 <mount current's root partition on directory ${CURRENT_ROOT}>
2542 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
2543 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2544 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2545 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2546 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2547 <reboot into current>
2548 <do a "native" rebuild/install as described in the previous section>
2549 <maybe install compatibility libraries from ports/misc/compat*>
2553 To upgrade in-place from stable to current
2554 ----------------------------------------------
2555 <make sure you have good level 0 dumps>
2557 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
2558 make installkernel KERNCONF=YOUR_KERNEL_HERE
2560 <reboot in single user> [3]
2567 Make sure that you've read the UPDATING file to understand the
2568 tweaks to various things you need. At this point in the life
2569 cycle of current, things change often and you are on your own
2570 to cope. The defaults can also change, so please read ALL of
2571 the UPDATING entries.
2573 Also, if you are tracking -current, you must be subscribed to
2574 freebsd-current@freebsd.org. Make sure that before you update
2575 your sources that you have read and understood all the recent
2576 messages there. If in doubt, please track -stable which has
2577 much fewer pitfalls.
2579 [1] If you have third party modules, such as vmware, you should disable
2580 them at this point so they don't crash your system on
2581 reboot. Alternatively, you should rebuild all the modules you have in
2582 your system and install them as well. If you are running -current, you
2583 should seriously consider placing all sources to all the modules for
2584 your system (or symlinks to them) in /usr/local/sys/modules so this
2585 happens automatically. If all your modules come from ports, then adding
2586 the port origin directories to PORTS_MODULES instead is also automatic
2588 PORTS_MODULES+=x11/nvidia-driver
2590 [3] From the bootblocks, boot -s, and then do
2594 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed
2595 cd src # full path to source
2596 adjkerntz -i # if CMOS is wall time
2597 Also, when doing a major release upgrade, it is required that you boot
2598 into single user mode to do the installworld.
2600 [4] Note: This step is non-optional. Failure to do this step
2601 can result in a significant reduction in the functionality of the
2602 system. Attempting to do it by hand is not recommended and those
2603 that pursue this avenue should read this file carefully, as well
2604 as the archives of freebsd-current and freebsd-hackers mailing lists
2605 for potential gotchas. See etcupdate(8) for more information.
2607 [5] Usually this step is a no-op. However, from time to time
2608 you may need to do this if you get unknown user in the following
2611 [6] This only deletes old files and directories. Old libraries
2612 can be deleted by "make delete-old-libs", but you have to make
2613 sure that no program is using those libraries anymore.
2615 [8] The new kernel must be able to run existing binaries used by an
2616 installworld. When upgrading across major versions, the new kernel's
2617 configuration must include the correct COMPAT_FREEBSD<n> option for
2618 existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure
2619 to do so may leave you with a system that is hard to boot to recover. A
2620 GENERIC kernel will include suitable compatibility options to run
2621 binaries from older branches. Note that the ability to run binaries
2622 from unsupported branches is not guaranteed.
2624 Make sure that you merge any new devices from GENERIC since the
2625 last time you updated your kernel config file. Options also
2626 change over time, so you may need to adjust your custom kernels
2629 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2630 "?=" instead of the "=" assignment operator, so that buildworld can
2631 override the CPUTYPE if it needs to.
2633 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2634 not on the command line, or in /etc/make.conf. buildworld will
2635 warn if it is improperly defined.
2638 This file contains a list, in reverse chronological order, of major
2639 breakages in tracking -current. It is not guaranteed to be a complete
2640 list of such breakages, and only contains entries since September 23, 2011.
2641 If you need to see UPDATING entries from before that date, you will need
2642 to fetch an UPDATING file from an older FreeBSD release.
2644 Copyright information:
2646 Copyright 1998-2009 M. Warner Losh <imp@FreeBSD.org>
2648 Redistribution, publication, translation and use, with or without
2649 modification, in full or in part, in any form or format of this
2650 document are permitted without further permission from the author.
2652 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2653 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2654 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2655 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2656 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2657 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2658 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2659 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2660 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2661 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2662 POSSIBILITY OF SUCH DAMAGE.
2664 Contact Warner Losh if you have any questions about your use of