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 configuation 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 comitted. Bump __FreeBSD_version to 1400015 to be able to detect this.
219 Commit ca179c4d74f2 changed the package in which the OpenSSL
220 libraries and utilities are packaged.
221 It is recommended for pkgbase user to do:
222 pkg install -f FreeBSD-openssl
223 before pkg upgrade otherwise some dependencies might not be met
224 and pkg will stop working as libssl will not be present anymore
228 Commit 875977314881 changed the internal KAPI between
229 the nfsd and nfscommon modules. As such these modules
230 need to be rebuilt from sources.
231 Without this patch in your NFSv4.1/4.2 server, enabling
232 delegations by setting vfs.nfsd.issue_delegations non-zero
236 Commit 7763814fc9c2 changed the internal KAPI between
237 the krpc and NFS. As such, the krpc, nfscommon and
238 nfscl modules must all be rebuilt from sources.
239 Without this patch, NFSv4.1/4.2 mounts should not
240 be done with the nfscbd(8) daemon running, to avoid
241 needing a working back channel for server->client RPCs.
244 Commit 01ae8969a9ee fixed the NFSv4.1/4.2 server so that it
245 handles binding of the back channel as required by RFC5661.
246 Until this patch is in your server, avoid use of the "nconnects"
247 mount option for Linux NFSv4.1/4.2 mounts.
250 For 64-bit architectures the base system is now built with Position
251 Independent Executable (PIE) support enabled by default. It may be
252 disabled using the WITHOUT_PIE knob. A clean build is required.
255 Various LinuxKPI functionality was added which conflicts with DRM.
256 Please update your drm-kmod port to after the __FreeBSD_verison 1400003
260 PC Card attachments for all devices have been removed. In the case of
261 wi and cmx, the entire drivers were removed because they were only
262 PC Card devices. FreeBSD_version 1300134 should be used for this
263 since it was bumped so recently.
266 Transport-independent parts of HID support have been split off the USB
267 code in to separate subsystem. Kernel configs which include one of
268 ums, ukbd, uhid, atp, wsp, wmt, uaudio, ugold or ucycom drivers should
269 be updated with adding of "device hid" line.
272 ncurses installation has been modified to only keep the widechar
273 enabled version. Incremental build is broken for that change, so it
274 requires a clean build.
277 The FreeBSD project has migrated from Subversion to Git. Temporary
278 instructions can be found at
279 https://github.com/bsdimp/freebsd-git-docs/blob/main/src-cvt.md
280 and other documents in that repo.
283 The services database has been updated to cover more of the basic
284 services expected in a modern system. The database is big enough
285 that it will cause issues in mergemaster in Releases previous to
286 12.2 and 11.3, or in very old current systems from before r358154.
289 Obsolete in-tree GDB 6.1.1 has been removed. GDB (including kgdb)
290 may be installed from ports or packages.
293 ping6 has been merged into ping. It can now be called as "ping -6".
294 See ping(8) for details.
297 Default value of net.add_addr_allfibs has been changed to 0.
298 If you have multi-fib configuration and rely on existence of all
299 interface routes in every fib, you need to set the above sysctl to 1.
302 The internal pre-processor in the calendar(1) program has been
303 extended to support more C pre-processor commands (e.g. #ifdef, #else,
304 and #undef) and to detect unbalanced conditional statements.
305 Error messages have been extended to include the filename and line
306 number if processing stops to help fixing malformed data files.
309 All the data files for the calendar(1) program, except calendar.freebsd,
310 have been moved to the deskutils/calendar-data port, much like the
311 jewish calendar entries were moved to deskutils/hebcal years ago. After
312 make delete-old-files, you need to install it to retain full
313 functionality. calendar(1) will issue a reminder for files it can't
317 LINT files are no longer generated. We now include the relevant NOTES
318 files. Note: This may cause conflicts with updating in some cases.
319 find sys -name LINT\* -delete
320 is suggested across this commit to remove the generated LINT files.
322 If you have tried to update with generated files there, the svn
323 command you want to un-auger the tree is
326 and then do the above find from the top level. Substitute 'amd64'
327 above with where the error message indicates a conflict.
330 OpenZFS support has been integrated. Do not upgrade root pools until
331 the loader is updated to support zstd. Furthermore, we caution against
332 'zpool upgrade' for the next few weeks. The change should be transparent
333 unless you want to use new features.
335 Not all "NO_CLEAN" build scenarios work across these changes. Many
336 scenarios have been tested and fixed, but rebuilding kernels without
337 rebuilding world may fail.
339 The ZFS cache file has moved from /boot to /etc to match the OpenZFS
340 upstream default. A fallback to /boot has been added for mountroot.
342 Pool auto import behavior at boot has been moved from the kernel module
343 to an explicit "zpool import -a" in one of the rc scripts enabled by
344 zfs_enable=YES. This means your non-root zpools won't auto import until
345 you upgrade your /etc/rc.d files.
348 The resume code now notifies devd with the 'kernel' system
349 rather than the old 'kern' subsystem to be consistent with
350 other use. The old notification will be created as well, but
351 will be removed prior to FreeBSD 14.0.
354 r362275 changed the internal API between the kernel RPC and the
355 NFS modules. As such, all the modules must be recompiled from
359 r364330 modified the internal API used between the NFS modules.
360 As such, all the NFS modules must be re-compiled from sources.
363 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
364 been upgraded to 11.0.0. Please see the 20141231 entry below for
365 information about prerequisites and upgrading, if you are not already
366 using clang 3.5.0 or higher.
369 r364092 modified the internal ABI used between the kernel NFS
370 modules. As such, all of these modules need to be rebuilt
371 from sources, so a version bump was done.
374 Makefile.inc has been updated to work around the issue documented in
375 20200729. It was a case where the optimization of using symbolic links
376 to point to binaries created a situation where we'd run new binaries
377 with old libraries starting midway through the installworld process.
380 r363679 has redefined some undefined behavior in regcomp(3); notably,
381 extraneous escapes of most ordinary characters will no longer be
382 accepted. An exp-run has identified all of the problems with this in
383 ports, but other non-ports software may need extra escapes removed to
384 continue to function.
386 Because of this change, installworld may encounter the following error
387 from rtld: Undefined symbol "regcomp@FBSD_1.6" -- It is imperative that
388 you do not halt installworld. Instead, let it run to completion (whether
389 successful or not) and run installworld once more.
392 A new implementation of bc and dc has been imported in r362681. This
393 implementation corrects non-conformant behavior of the previous bc
394 and adds GNU bc compatible options. It offers a number of extensions,
395 is much faster on large values, and has support for message catalogs
396 (a number of languages are already supported, contributions of further
397 languages welcome). The option WITHOUT_GH_BC can be used to build the
398 world with the previous versions of bc and dc.
401 r362639 changed the internal API used between the NFS kernel modules.
402 As such, they all need to be rebuilt from sources.
405 r362158 changed the arguments for VFS_CHECKEXP(). As such, any
406 out of tree file systems need to be modified and rebuilt.
407 Also, any file systems that are modules must be rebuilt.
410 read(2) of a directory fd is now rejected by default. root may
411 re-enable it for system root only on non-ZFS filesystems with the
412 security.bsd.allow_read_dir sysctl(8) MIB if
413 security.bsd.suser_enabled=1.
415 It may be advised to setup aliases for grep to default to `-d skip` if
416 commonly non-recursively grepping a list that includes directories and
417 the potential for the resulting stderr output is not tolerable. Example
418 aliases are now installed, commented out, in /root/.cshrc and
422 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
423 been upgraded to 10.0.1. Please see the 20141231 entry below for
424 information about prerequisites and upgrading, if you are not already
425 using clang 3.5.0 or higher.
428 Support for obsolete compilers has been removed from the build system.
429 Clang 6 and GCC 6.4 are the minimum supported versions.
432 closefrom(2) has been moved under COMPAT12, and replaced in libc with a
433 stub that calls close_range(2). If using a custom kernel configuration,
434 you may want to ensure that the COMPAT_FREEBSD12 option is included, as
435 a slightly older -CURRENT userland and older FreeBSD userlands may not
436 be functional without closefrom(2).
439 Upstream DTS from Linux 5.6 was merged and they now have the SID
440 and THS (Secure ID controller and THermal Sensor) node present.
441 The DTB overlays have now been removed from the tree for the H3/H5 and
442 A64 SoCs and the aw_sid and aw_thermal driver have been updated to
443 deal with upstream DTS. If you are using those overlays you need to
444 remove them from loader.conf and update the DTBs on the FAT partition.
447 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
448 been upgraded to 10.0.0. Please see the 20141231 entry below for
449 information about prerequisites and upgrading, if you are not already
450 using clang 3.5.0 or higher.
453 The amd(8) automount daemon has been removed from the source tree.
454 As of FreeBSD 10.1 autofs(5) is the preferred tool for automounting.
455 amd is still available in the sysutils/am-utils port.
458 Removed brooktree driver (bktr.4) from the tree.
461 The WITH_GPL_DTC option has been removed. The BSD-licenced device tree
462 compiler in usr.bin/dtc is used on all architectures which use dtc, and
463 the GPL dtc is available (if needed) from the sysutils/dtc port.
466 The WITHOUT_LLVM_LIBUNWIND option has been removed. LLVM's libunwind
467 is used by all supported CPU architectures.
470 GCC 4.2.1 has been removed from the tree. The WITH_GCC,
471 WITH_GCC_BOOTSTRAP, and WITH_GNUCXX options are no longer available.
472 Users who wish to build FreeBSD with GCC must use the external toolchain
476 ncurses has been updated to a newer version (6.2-20200215). Given the ABI
477 has changed, users will have to rebuild all the ports that are linked to
481 The size of struct vnet and the magic cookie have changed.
482 Users need to recompile libkvm and all modules using VIMAGE
483 together with their new kernel.
486 Defining the long deprecated NO_CTF, NO_DEBUG_FILES, NO_INSTALLLIB,
487 NO_MAN, NO_PROFILE, and NO_WARNS variables is now an error. Update
488 your Makefiles and scripts to define MK_<var>=no instead as required.
490 One exception to this is that program or library Makefiles should
491 define MAN to empty rather than setting MK_MAN=no.
494 Clang/LLVM is now the default compiler and LLD the default
498 make universe no longer uses GCC 4.2.1 on any architectures.
499 Architectures not supported by in-tree Clang/LLVM require an
500 external toolchain package.
503 GCC 4.2.1 is now not built by default, as part of the GCC 4.2.1
504 retirement plan. Specifically, the GCC, GCC_BOOTSTRAP, and GNUCXX
505 options default to off for all supported CPU architectures. As a
506 short-term transition aid they may be enabled via WITH_* options.
507 GCC 4.2.1 is expected to be removed from the tree on 2020-03-31.
510 Support for armv5 has been disconnected and is being removed. The
511 machine combination MACHINE=arm MACHINE_ARCH=arm is no longer valid.
512 You must now use a MACHINE_ARCH of armv6 or armv7. The default
513 MACHINE_ARCH for MACHINE=arm is now armv7.
516 Clang/LLVM is now the default compiler for all powerpc architectures.
517 LLD is now the default linker for powerpc64. The change for powerpc64
518 also includes a change to the ELFv2 ABI, incompatible with the existing
522 Kernel-loadable random(4) modules are no longer unloadable.
525 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
526 been upgraded to 9.0.1. Please see the 20141231 entry below for
527 information about prerequisites and upgrading, if you are not already
528 using clang 3.5.0 or higher.
531 r355677 has modified the internal interface used between the
532 NFS modules in the kernel. As such, they must all be upgraded
533 simultaneously. I will do a version bump for this.
536 The root certificates of the Mozilla CA Certificate Store have been
537 imported into the base system and can be managed with the certctl(8)
538 utility. If you have installed the security/ca_root_nss port or package
539 with the ETCSYMLINK option (the default), be advised that there may be
540 differences between those included in the port and those included in
541 base due to differences in nss branch used as well as general update
542 frequency. Note also that certctl(8) cannot manage certs in the
543 format used by the security/ca_root_nss port.
546 The amd(8) automount daemon has been disabled by default, and will be
547 removed in the future. As of FreeBSD 10.1 the autofs(5) is available
551 The nctgpio and wbwd drivers have been moved to the superio bus.
552 If you have one of these drivers in a kernel configuration, then
553 you should add device superio to it. If you use one of these drivers
554 as a module and you compile a custom set of modules, then you should
555 add superio to the set.
558 KPIs for network drivers to access interface addresses have changed.
559 Users need to recompile NIC driver modules together with kernel.
562 The net.link.tap.user_open sysctl no longer prevents user opening of
563 already created /dev/tapNN devices. Access is still controlled by
564 node permissions, just like tun devices. The net.link.tap.user_open
565 sysctl is now used only to allow users to perform devfs cloning of
566 tap devices, and the subsequent open may not succeed if the user is not
567 in the appropriate group. This sysctl may be deprecated/removed
568 completely in the future.
571 mips, powerpc, and sparc64 are no longer built as part of
572 universe / tinderbox unless MAKE_OBSOLETE_GCC is defined. If
573 not defined, mips, powerpc, and sparc64 builds will look for
574 the xtoolchain binaries and if installed use them for universe
575 builds. As llvm 9.0 becomes vetted for these architectures, they
576 will be removed from the list.
579 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
580 been upgraded to 9.0.0. Please see the 20141231 entry below for
581 information about prerequisites and upgrading, if you are not already
582 using clang 3.5.0 or higher.
585 The hpt27xx, hptmv, hptnr, and hptrr drivers have been removed from
586 GENERIC. They are available as modules and can be loaded by adding
587 to /boot/loader.conf hpt27xx_load="YES", hptmv_load="YES",
588 hptnr_load="YES", or hptrr_load="YES", respectively.
591 ntpd no longer by default locks its pages in memory, allowing them
592 to be paged out by the kernel. Use rlimit memlock to restore
593 historic BSD behaviour. For example, add "rlimit memlock 32"
594 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
597 Several of ping6's options have been renamed for better consistency
598 with ping. If you use any of -ARWXaghmrtwx, you must update your
599 scripts. See ping6(8) for details.
602 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
603 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
604 been removed from mount_fusefs(8). You can safely remove them from
605 your scripts, because they had no effect.
607 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
608 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
609 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
610 sysctls have been removed. If you felt the need to set any of them to
611 a non-default value, please tell asomers@FreeBSD.org why.
614 Default permissions on the /var/account/acct file (and copies of it
615 rotated by periodic daily scripts) are changed from 0644 to 0640
616 because the file contains sensitive information that should not be
617 world-readable. If the /var/account directory must be created by
618 rc.d/accounting, the mode used is now 0750. Admins who use the
619 accounting feature are encouraged to change the mode of an existing
620 /var/account directory to 0750 or 0700.
623 Entropy collection and the /dev/random device are no longer optional
624 components. The "device random" option has been removed.
625 Implementations of distilling algorithms can still be made loadable
626 with "options RANDOM_LOADABLE" (e.g., random_fortuna.ko).
629 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
630 been upgraded to 8.0.1. Please see the 20141231 entry below for
631 information about prerequisites and upgrading, if you are not already
632 using clang 3.5.0 or higher.
635 A fix was applied to i386 kernel modules to avoid panics with
636 dpcpu or vnet. Users need to recompile i386 kernel modules
637 having pcpu or vnet sections or they will refuse to load.
640 User-wired pages now have their own counter,
641 vm.stats.vm.v_user_wire_count. The vm.max_wired sysctl was renamed
642 to vm.max_user_wired and changed from an unsigned int to an unsigned
643 long. bhyve VMs wired with the -S are now subject to the user
644 wiring limit; the vm.max_user_wired sysctl may need to be tuned to
645 avoid running into the limit.
648 The IPSEC option has been removed from GENERIC. Users requiring
649 ipsec(4) must now load the ipsec(4) kernel module.
652 The tap(4) driver has been folded into tun(4), and the module has been
653 renamed to tuntap. You should update any kld_list="if_tap" or
654 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
655 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
656 module instead, and "device tap" or "device tun" entries in kernel
657 config files to select the tuntap device instead.
660 The following knobs have been added related to tradeoffs between
661 safe use of the random device and availability in the absence of
664 kern.random.initial_seeding.bypass_before_seeding: tunable; set
665 non-zero to bypass the random device prior to seeding, or zero to
666 block random requests until the random device is initially seeded.
667 For now, set to 1 (unsafe) by default to restore pre-r346250 boot
668 availability properties.
670 kern.random.initial_seeding.read_random_bypassed_before_seeding:
671 read-only diagnostic sysctl that is set when bypass is enabled and
672 read_random(9) is bypassed, to enable programmatic handling of this
673 initial condition, if desired.
675 kern.random.initial_seeding.arc4random_bypassed_before_seeding:
676 Similar to the above, but for for arc4random(9) initial seeding.
678 kern.random.initial_seeding.disable_bypass_warnings: tunable; set
679 non-zero to disable warnings in dmesg when the same conditions are
680 met as for the diagnostic sysctls above. Defaults to zero, i.e.,
681 produce warnings in dmesg when the conditions are met.
684 The loadable random module KPI has changed; the random_infra_init()
685 routine now requires a 3rd function pointer for a bool (*)(void)
686 method that returns true if the random device is seeded (and
687 therefore unblocked).
690 r345895 reverts r320698. This implies that an nfsuserd(8) daemon
691 built from head sources between r320757 (July 6, 2017) and
692 r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
693 is added to the command line.
694 nfsuserd daemons built from head sources that are post-r338192 are
695 not affected and should continue to work.
698 The fuse(4) module has been renamed to fusefs(4) for consistency with
699 other filesystems. You should update any kld_load="fuse" entries in
700 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
701 "options FUSE" entries in kernel config files.
704 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
705 8.0.0. Please see the 20141231 entry below for information about
706 prerequisites and upgrading, if you are not already using clang 3.5.0
710 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
711 compiled into your custom kernel, add 'device xz' statement to the
715 drm and drm2 have been removed from the tree. Please see
716 https://wiki.freebsd.org/Graphics for the latest information on
717 migrating to the drm ports.
720 Iflib is no longer unconditionally compiled into the kernel. Drivers
721 using iflib and statically compiled into the kernel, now require
722 the 'device iflib' config option. For the same drivers loaded as
723 modules on kernels not having 'device iflib', the iflib.ko module
724 is loaded automatically.
727 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
728 options no longer exist since r343219 and r343427 respectively;
729 nothing uses them, so they should be just removed from custom
733 r342635 changes the way efibootmgr(8) works by requiring users to add
734 the -b (bootnum) parameter for commands where the bootnum was previously
735 specified with each option. For example 'efibootmgr -B 0001' is now
736 'efibootmgr -B -b 0001'.
739 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
740 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
741 servers that have vfs.nfsd.nfs_privport set will only allow mounts
742 from clients using a reserved port. Since both the FreeBSD and Linux
743 NFSv4 clients use reserved ports by default, this should not affect
747 The XLP config has been removed. We can't support 64-bit atomics in this
748 kernel because it is running in 32-bit mode. XLP users must transition
749 to running a 64-bit kernel (XLP64 or XLPN32).
751 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
752 the preferred emulator today and we don't need two different ones.
754 The old sibyte / swarm / Broadcom BCM1250 support has been
755 removed from the mips port.
758 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
759 7.0.1. Please see the 20141231 entry below for information about
760 prerequisites and upgrading, if you are not already using clang 3.5.0
764 Remove the timed and netdate programs from the base tree. Setting
765 the time with these daemons has been obsolete for over a decade.
768 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
769 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
770 it produces broken binaries when ifuncs are in use. Users needing
771 GNU ld should install the binutils port or package.
774 The BSD crtbegin and crtend code has been enabled by default. It has
775 had extensive testing on amd64, arm64, and i386. It can be disabled
776 by building a world with -DWITHOUT_BSD_CRTBEGIN.
779 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
780 has been converted to a port (misc/ctm) and will be removed from
781 FreeBSD-13. It is available as a package (ctm) for all supported
785 The default newsyslog.conf(5) file has been changed to only include
786 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
787 the filenames end in '.conf' and do not begin with a '.'.
789 You should check the configuration files in these two directories match
790 this naming convention. You can verify which configuration files are
791 being included using the command:
795 Ports for the DRM modules have been simplified. Now, amd64 users should
796 just install the drm-kmod port. All others should install
799 Graphics hardware that's newer than about 2010 usually works with
800 drm-kmod. For hardware older than 2013, however, some users will need
801 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
802 than 2008 usually only works in drm-legacy-kmod. The graphics team can
803 only commit to hardware made since 2013 due to the complexity of the
804 market and difficulty to test all the older cards effectively. If you
805 have hardware supported by drm-kmod, you are strongly encouraged to use
806 that as you will get better support.
808 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
809 elsewhere, the drm and drm2 modules will be eliminated from the src base
810 soon (with a limited exception for arm). Please update to the package
811 asap and report any issues to x11@freebsd.org.
813 Generally, anybody using the drm*-kmod packages should add
814 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
815 cross-threading surprises, especially with automatic driver
816 loading from X11 startup. These will become the defaults in 13-current
820 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
821 custom kernel and module loading configuration files must be updated
822 accordingly. Moreover, interfaces previous presented as ixlvN to the
823 system are now exposed as iavfN and network configuration files must
824 be adjusted as necessary.
827 OpenSSL has been updated to version 1.1.1. This update included
828 additional various API changes throughout the base system. It is
829 important to rebuild third-party software after upgrading. The value
830 of __FreeBSD_version has been bumped accordingly.
833 The legacy DRM modules and drivers have now been added to the loader's
834 module blacklist, in favor of loading them with kld_list in rc.conf(5).
835 The module blacklist may be overridden with the loader.conf(5)
836 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
840 The cam(4) based nda(4) driver will be used over nvd(4) by default on
841 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
842 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
843 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
847 Reproducible build mode is now on by default, in preparation for
848 FreeBSD 12.0. This eliminates build metadata such as the user,
849 host, and time from the kernel (and uname), unless the working tree
850 corresponds to a modified checkout from a version control system.
851 The previous behavior can be obtained by setting the /etc/src.conf
852 knob WITHOUT_REPRODUCIBLE_BUILD.
855 The Yarrow CSPRNG has been removed from the kernel as it has not been
856 supported by its designers since at least 2003. Fortuna has been the
857 default since FreeBSD-11.
860 devctl freeze/thaw have gone into the tree, the rc scripts have been
861 updated to use them and devmatch has been changed. You should update
862 kernel, userland and rc scripts all at the same time.
865 The default interpreter has been switched from 4th to Lua.
866 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
867 interpreter. If you have custom FORTH code you will need to set
868 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
869 src.conf for the build. This will create default hard links between
870 loader and loader_4th instead of loader and loader_lua, the new default.
871 If you are using UEFI it will create the proper hard link to loader.efi.
873 bhyve uses userboot.so. It remains 4th-only until some issues are solved
874 regarding coexisting with multiple versions of FreeBSD are resolved.
877 ls(1) now respects the COLORTERM environment variable used in other
878 systems and software to indicate that a colored terminal is both
879 supported and desired. If ls(1) is suddenly emitting colors, they may
880 be disabled again by either removing the unwanted COLORTERM from your
881 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
882 may not be observed in a future release.
885 The default pager for most commands has been changed to "less". To
886 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
890 The jedec_ts(4) driver has been removed. A superset of its functionality
891 is available in the jedec_dimm(4) driver, and the manpage for that
892 driver includes migration instructions. If you have "device jedec_ts"
893 in your kernel configuration file, it must be removed.
896 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
897 This should have no effect if the kernel is booted via BIOS/legacy boot.
898 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
899 has a buggy firmware that prevents a successful boot due to use of
903 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
904 support has been removed from the tree. These ports were
905 obsolete and/or known to be broken for many years.
908 loader.efi has been augmented to participate more fully in the
909 UEFI boot manager protocol. loader.efi will now look at the
910 BootXXXX environment variable to determine if a specific kernel
911 or root partition was specified. XXXX is derived from BootCurrent.
912 efibootmgr(8) manages these standard UEFI variables.
915 zfsloader's functionality has now been folded into loader.
916 zfsloader is no longer necessary once you've updated your
917 boot blocks. For a transition period, we will install a
918 hardlink for zfsloader to loader to allow a smooth transition
919 until the boot blocks can be updated (hard link because old
920 zfs boot blocks don't understand symlinks).
923 ARM64 now have efifb support, if you want to have serial console
924 on your arm64 board when an screen is connected and the bootloader
925 setup a frame buffer for us to use, just add :
929 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
930 an screen connected as the firmware will setup a frame buffer are that
931 u-boot will expose as an EFI frame buffer.
934 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
935 or take steps to update /etc/passwd before doing installworld on
936 existing systems. Do not skip the "mergemaster -Fp" step before
937 installworld, as described in the update procedures near the bottom
938 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
939 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
940 the ntp config file contain options that change file/dir locations.
941 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
942 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
943 taking steps to ensure that all required files/dirs are accessible
947 Big endian arm support has been removed.
950 The static environment setup in kernel configs is no longer mutually
951 exclusive with the loader(8) environment by default. In order to
952 restore the previous default behavior of disabling the loader(8)
953 environment if a static environment is present, you must specify
954 loader_env.disabled=1 in the static environment.
957 The ABI of syscalls used by management tools like sockstat and
958 netstat has been broken to allow 32-bit binaries to work on
959 64-bit kernels without modification. These programs will need
960 to match the kernel in order to function. External programs may
961 require minor modifications to accommodate a change of type in
962 structures from pointers to 64-bit virtual addresses.
965 On i386 and amd64 atomics are now inlined. Out of tree modules using
966 atomics will need to be rebuilt.
969 The '%I' format in the kern.corefile sysctl limits the number of
970 core files that a process can generate to the number stored in the
971 debug.ncores sysctl. The '%I' format is replaced by the single digit
972 index. Previously, if all indexes were taken the kernel would overwrite
973 only a core file with the highest index in a filename.
974 Currently the system will create a new core file if there is a free
975 index or if all slots are taken it will overwrite the oldest one.
978 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
979 6.0.1. Please see the 20141231 entry below for information about
980 prerequisites and upgrading, if you are not already using clang 3.5.0
984 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
985 needed to be changed to work with it. This change was made with r335763
986 and requires a mergemaster / etcupdate / etc to update the installed
990 r334930 changed the interface between the NFS modules, so they all
991 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
994 As of r334391 lld is the default amd64 system linker; it is installed
995 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
999 The kernel / userland interface for devinfo changed, so you'll
1000 need a new kernel and userland as a pair for it to work (rebuilding
1001 lib/libdevinfo is all that's required). devinfo and devmatch will
1002 not work, but everything else will when there's a mismatch.
1005 The on-disk format for hwpmc callchain records has changed to include
1006 threadid corresponding to a given record. This changes the field offsets
1007 and thus requires that libpmcstat be rebuilt before using a kernel
1011 The vxge(4) driver has been removed. This driver was introduced into
1012 HEAD one week before the Exar left the Ethernet market and is not
1013 known to be used. If you have device vxge in your kernel config file
1017 The amd64 kernel now requires a ld that supports ifunc to produce a
1018 working kernel, either lld or a newer binutils. lld is built by default
1019 on amd64, and the 'buildkernel' target uses it automatically. However,
1020 it is not the default linker, so building the kernel the traditional
1021 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
1022 binutils port/package). lld will soon be default, and this requirement
1025 NOTE: As of r334391 lld is the default system linker on amd64, and no
1026 workaround is necessary.
1029 The nxge(4) driver has been removed. This driver was for PCI-X 10g
1030 cards made by s2io/Neterion. The company was acquired by Exar and
1031 no longer sells or supports Ethernet products. If you have device
1032 nxge in your kernel config file it must be removed.
1035 The tz database (tzdb) has been updated to 2018e. This version more
1036 correctly models time stamps in time zones with negative DST such as
1037 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
1038 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
1039 time zone abbreviations and the tm_isdst flag.
1042 The ixgb(4) driver has been removed. This driver was for an early and
1043 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
1044 quickly shifted to the long lived ixgbe family. If you have device
1045 ixgb in your kernel config file it must be removed.
1048 The lmc(4) driver has been removed. This was a WAN interface
1049 card that was already reportedly rare in 2003, and had an ambiguous
1050 license. If you have device lmc in your kernel config file it must
1054 Support for Arcnet networks has been removed. If you have device
1055 arcnet or device cm in your kernel config file they must be
1059 Support for FDDI networks has been removed. If you have device
1060 fddi or device fpa in your kernel config file they must be
1064 In addition to supporting RFC 3164 formatted messages, the
1065 syslogd(8) service is now capable of parsing RFC 5424 formatted
1066 log messages. The main benefit of using RFC 5424 is that clients
1067 may now send log messages with timestamps containing year numbers,
1068 microseconds and time zone offsets.
1070 Similarly, the syslog(3) C library function has been altered to
1071 send RFC 5424 formatted messages to the local system logging
1072 daemon. On systems using syslogd(8), this change should have no
1073 negative impact, as long as syslogd(8) and the C library are
1074 updated at the same time. On systems using a different system
1075 logging daemon, it may be necessary to make configuration
1076 adjustments, depending on the software used.
1078 When using syslog-ng, add the 'syslog-protocol' flag to local
1079 input sources to enable parsing of RFC 5424 formatted messages:
1082 unix-dgram("/var/run/log" flags(syslog-protocol));
1085 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
1086 of the 'imuxsock' module to let messages be processed by the
1087 regular RFC 3164/5424 parsing pipeline:
1089 module(load="imuxsock" SysSock.UseSpecialParser="off")
1091 Do note that these changes only affect communication between local
1092 applications and syslogd(8). The format that syslogd(8) uses to
1093 store messages on disk or forward messages to other systems
1094 remains unchanged. syslogd(8) still uses RFC 3164 for these
1095 purposes. Options to customize this behaviour will be added in the
1096 future. Utilities that process log files stored in /var/log are
1097 thus expected to continue to function as before.
1099 __FreeBSD_version has been incremented to 1200061 to denote this
1103 Support for token ring networks has been removed. If you
1104 have "device token" in your kernel config you should remove
1105 it. No device drivers supported token ring.
1108 makefs was modified to be able to tag ISO9660 El Torito boot catalog
1109 entries as EFI instead of overloading the i386 tag as done previously.
1110 The amd64 mkisoimages.sh script used to build amd64 ISO images for
1111 release was updated to use this. This may mean that makefs must be
1112 updated before "make cdrom" can be run in the release directory. This
1113 should be as simple as:
1115 $ cd $SRCDIR/usr.sbin/makefs
1116 $ make depend all install
1119 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
1120 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
1121 Co-existence for the transition period will come shortly. Booting is a
1122 complex environment and test coverage for Lua-enabled loaders has been
1123 thin, so it would be prudent to assume it might not work and make
1124 provisions for backup boot methods.
1127 devmatch functionality has been turned on in devd. It will automatically
1128 load drivers for unattached devices. This may cause unexpected drivers
1129 to be loaded. Please report any problems to current@ and
1133 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
1134 6.0.0. Please see the 20141231 entry below for information about
1135 prerequisites and upgrading, if you are not already using clang 3.5.0
1139 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
1140 This means it is used to link the kernel and userland libraries and
1141 executables, but is not yet installed as /usr/bin/ld by default.
1143 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
1144 WITHOUT_LLD_BOOTSTRAP=yes
1147 On i386, pmtimer has been removed. Its functionality has been folded
1148 into apm. It was a no-op on ACPI in current for a while now (but was
1149 still needed on i386 in FreeBSD 11 and earlier). Users may need to
1150 remove it from kernel config files.
1153 The use of RSS hash from the network card aka flowid has been
1154 disabled by default for lagg(4) as it's currently incompatible with
1155 the lacp and loadbalance protocols.
1157 This can be re-enabled by setting the following in loader.conf:
1158 net.link.lagg.default_use_flowid="1"
1161 The SW_WATCHDOG option is no longer necessary to enable the
1162 hardclock-based software watchdog if no hardware watchdog is
1163 configured. As before, SW_WATCHDOG will cause the software
1164 watchdog to be enabled even if a hardware watchdog is configured.
1167 r326887 fixes the issue described in the 20171214 UPDATING entry.
1168 r326888 flips the switch back to building GELI support always.
1171 r362593 broke ZFS + GELI support for reasons unknown. However,
1172 it also broke ZFS support generally, so GELI has been turned off
1173 by default as the lesser evil in r326857. If you boot off ZFS and/or
1174 GELI, it might not be a good time to update.
1177 PowerPC users must update loader(8) by rebuilding world before
1178 installing a new kernel, as the protocol connecting them has
1179 changed. Without the update, loader metadata will not be passed
1180 successfully to the kernel and users will have to enter their
1181 root partition at the kernel mountroot prompt to continue booting.
1182 Newer versions of loader can boot old kernels without issue.
1185 The LOADER_FIREWIRE_SUPPORT build variable has been renamed to
1186 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
1187 to WITH/OUT_LOADER_GELI.
1190 The naive and non-compliant support of posix_fallocate(2) in ZFS
1191 has been removed as of r325320. The system call now returns EINVAL
1192 when used on a ZFS file. Although the new behavior complies with the
1193 standard, some consumers are not prepared to cope with it.
1194 One known victim is lld prior to r325420.
1197 Building in a FreeBSD src checkout will automatically create object
1198 directories now rather than store files in the current directory if
1199 'make obj' was not ran. Calling 'make obj' is no longer necessary.
1200 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
1201 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
1205 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
1206 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
1207 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
1208 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
1209 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
1210 The UNIFIED_OBJDIR option is a transitional feature that will be
1211 removed for 12.0 release; please migrate to the new format for any
1212 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
1213 than hardcoding paths.
1216 The native-xtools target no longer installs the files by default to the
1217 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
1218 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
1221 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
1222 options are changing from controlling the build if defined / undefined
1223 to controlling the build with explicit 'yes' or 'no' values. They will
1224 shift to WITH/WITHOUT options to match other options in the system.
1227 libstand has turned into a private library for sys/boot use only.
1228 It is no longer supported as a public interface outside of sys/boot.
1231 The arm port has split armv6 into armv6 and armv7. armv7 is now
1232 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
1233 and are running a kernel from before r324363, you will need to add
1234 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
1237 When building multiple kernels using KERNCONF, non-existent KERNCONF
1238 files will produce an error and buildkernel will fail. Previously
1239 missing KERNCONF files silently failed giving no indication as to
1240 why, only to subsequently discover during installkernel that the
1241 desired kernel was never built in the first place.
1244 The default serial number format for CTL LUNs has changed. This will
1245 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
1246 or iSCSI clients care about their LUNs' serial numbers. Users who
1247 require serial number stability should hardcode serial numbers in
1251 For 32-bit arm compiled for hard-float support, soft-floating point
1252 binaries now always get their shared libraries from
1253 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
1254 /usr/libsoft also existed). Only users with a hard-float ld.so, but
1255 soft-float everything else should be affected.
1258 The geli password typed at boot is now hidden. To restore the previous
1259 behavior, see geli(8) for configuration options.
1262 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
1263 sysctl values. Minor nit, but requires a rebuild of both world/kernel
1267 "make check" behavior (made in ^/head@r295380) has been changed to
1268 execute from a limited sandbox, as opposed to executing from
1272 - The "beforecheck" and "aftercheck" targets are now specified.
1273 - ${CHECKDIR} (added in commit noted above) has been removed.
1274 - Legacy behavior can be enabled by setting
1275 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
1277 If the limited sandbox mode is enabled, "make check" will execute
1278 "make distribution", then install, execute the tests, and clean up the
1279 sandbox if successful.
1281 The "make distribution" and "make install" targets are typically run as
1282 root to set appropriate permissions and ownership at installation time.
1283 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
1284 environment if executing "make check" with limited sandbox mode using
1285 an unprivileged user.
1288 Since the switch to GPT disk labels, fsck for UFS/FFS has been
1289 unable to automatically find alternate superblocks. As of r322297,
1290 the information needed to find alternate superblocks has been
1291 moved to the end of the area reserved for the boot block.
1292 Filesystems created with a newfs of this vintage or later
1293 will create the recovery information. If you have a filesystem
1294 created prior to this change and wish to have a recovery block
1295 created for your filesystem, you can do so by running fsck in
1296 foreground mode (i.e., do not use the -p or -y options). As it
1297 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
1298 to which you should answer yes.
1301 As of r321665, an NFSv4 server configuration that services
1302 Kerberos mounts or clients that do not support the uid/gid in
1303 owner/owner_group string capability, must explicitly enable
1304 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
1305 machine's /etc/rc.conf file.
1308 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
1309 Please see the 20141231 entry below for information about prerequisites
1310 and upgrading, if you are not already using clang 3.5.0 or higher.
1313 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
1314 r-commands (rlogin, rsh, etc.) to be built with the base system.
1317 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
1318 a very major ABI incompatible change, so users of FreeBSD/powerpc must
1319 be careful when performing source upgrades. It is best to run
1320 'make installworld' from an alternate root system, either a live
1321 CD/memory stick, or a temporary root partition. Additionally, all ports
1322 must be recompiled. powerpc64 is largely unaffected, except in the case
1323 of 32-bit compatibility. All 32-bit binaries will be affected.
1326 Forward compatibility for the "ino64" project have been committed. This
1327 will allow most new binaries to run on older kernels in a limited
1328 fashion. This prevents many of the common foot-shooting actions in the
1329 upgrade as well as the limited ability to roll back the kernel across
1330 the ino64 upgrade. Complicated use cases may not work properly, though
1331 enough simpler ones work to allow recovery in most situations.
1334 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
1335 if you require the GPL compiler.
1338 The internal ABI used for communication between the NFS kernel modules
1339 was changed by r320085, so __FreeBSD_version was bumped to
1340 ensure all the NFS related modules are updated together.
1343 The ABI of struct event was changed by extending the data
1344 member to 64bit and adding ext fields. For upgrade, same
1345 precautions as for the entry 20170523 "ino64" must be
1349 The GNU roff toolchain has been removed from base. To render manpages
1350 which are not supported by mandoc(1), man(1) can fallback on GNU roff
1351 from ports (and recommends to install it).
1352 To render roff(7) documents, consider using GNU roff from ports or the
1353 heirloom doctools roff toolchain from ports via pkg install groff or
1354 via pkg install heirloom-doctools.
1357 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
1358 smaller runtime footprint builds. This is useful for embedded systems
1359 which only require one chipset support.
1361 If you load it as a module, make sure this is in /boot/loader.conf:
1365 This will load the HAL, all chip/RF backends and if_ath_pci.
1366 If you have if_ath_pci in /boot/loader.conf, ensure it is after
1367 if_ath or it will not load any HAL chipset support.
1369 If you want to selectively load things (eg on cheaper ARM/MIPS
1370 platforms where RAM is at a premium) you should:
1373 * load the chip modules in question
1374 * load ath_rate, ath_dfs
1376 * load if_ath_pci and/or if_ath_ahb depending upon your particular
1377 bus bind type - this is where probe/attach is done.
1379 For further comments/feedback, poke adrian@ .
1382 The "ino64" 64-bit inode project has been committed, which extends
1383 a number of types to 64 bits. Upgrading in place requires care and
1384 adherence to the documented upgrade procedure.
1386 If using a custom kernel configuration ensure that the
1387 COMPAT_FREEBSD11 option is included (as during the upgrade the
1388 system will be running the ino64 kernel with the existing world).
1390 For the safest in-place upgrade begin by removing previous build
1391 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full
1392 procedure documented below under the heading "To rebuild everything and
1393 install it on the current system." Specifically, a reboot is required
1394 after installing the new kernel before installing world. While an
1395 installworld normally works by accident from multiuser after rebooting
1396 the proper kernel, there are many cases where this will fail across this
1397 upgrade and installworld from single user is required.
1400 The NATM framework including the en(4), fatm(4), hatm(4), and
1401 patm(4) devices has been removed. Consumers should plan a
1402 migration before the end-of-life date for FreeBSD 11.
1405 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
1406 diff has not been implemented, if those are needed a newer version of
1407 GNU diff is available via the diffutils package under the gdiff name.
1410 As of r316810 for ipfilter, keep frags is no longer assumed when
1411 keep state is specified in a rule. r316810 aligns ipfilter with
1412 documentation in man pages separating keep frags from keep state.
1413 This allows keep state to be specified without forcing keep frags
1414 and allows keep frags to be specified independently of keep state.
1415 To maintain previous behaviour, also specify keep frags with
1416 keep state (as documented in ipf.conf.5).
1419 arm64 builds now use the base system LLD 4.0.0 linker by default,
1420 instead of requiring that the aarch64-binutils port or package be
1421 installed. To continue using aarch64-binutils, set
1422 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
1425 The UDP optimization in entry 20160818 that added the sysctl
1426 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
1427 packets will no longer be treated as L3 broadcast packets.
1430 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
1431 use any explicitly assigned loopback address available in the jail
1432 instead of using the first assigned address of the jail.
1435 The ctl.ko module no longer implements the iSCSI target frontend:
1436 cfiscsi.ko does instead.
1438 If building cfiscsi.ko as a kernel module, the module can be loaded
1439 via one of the following methods:
1440 - `cfiscsi_load="YES"` in loader.conf(5).
1441 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
1442 - ctladm(8)/ctld(8), when compiled with iSCSI support
1443 (`WITH_ISCSI=yes` in src.conf(5))
1445 Please see cfiscsi(4) for more details.
1448 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
1449 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
1450 same source (previously, the dependency of mmcsd.ko on mmc.ko was
1451 missing, but mmcsd.ko now will refuse to load if it is incompatible
1455 The syntax of ipfw(8) named states was changed to avoid ambiguity.
1456 If you have used named states in the firewall rules, you need to modify
1457 them after installworld and before rebooting. Now named states must
1458 be prefixed with colon.
1461 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
1462 removed as the userland we provide cannot use them. The KMS version
1463 (sys/dev/drm2) supports the same hardware.
1466 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
1467 Please see the 20141231 entry below for information about prerequisites
1468 and upgrading, if you are not already using clang 3.5.0 or higher.
1471 The code that provides support for ZFS .zfs/ directory functionality
1472 has been reimplemented. It's not possible now to create a snapshot
1473 by mkdir under .zfs/snapshot/. That should be the only user visible
1477 EISA bus support has been removed. The WITH_EISA option is no longer
1481 MCA bus support has been removed.
1484 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
1485 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
1488 The EM_MULTIQUEUE kernel configuration option is deprecated now that
1489 the em(4) driver conforms to iflib specifications.
1492 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
1493 IFLIB. If you have a custom kernel configuration that excludes em(4)
1494 but you use igb(4), you need to re-add em(4) to your custom
1498 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
1499 Please see the 20141231 entry below for information about prerequisites
1500 and upgrading, if you are not already using clang 3.5.0 or higher.
1503 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
1504 Please see the 20141231 entry below for information about prerequisites
1505 and upgrading, if you are not already using clang 3.5.0 or higher.
1508 The layout of the pmap structure has changed for powerpc to put the pmap
1509 statistics at the front for all CPU variations. libkvm(3) and all tools
1510 that link against it need to be recompiled.
1513 isl(4) and cyapa(4) drivers now require a new driver,
1514 chromebook_platform(4), to work properly on Chromebook-class hardware.
1515 On other types of hardware the drivers may need to be configured using
1516 device hints. Please see the corresponding manual pages for details.
1519 The urtwn(4) driver was merged into rtwn(4) and now consists of
1520 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
1522 Also, firmware for RTL8188CE was renamed due to possible name
1523 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
1526 GNU rcs has been removed from base. It is available as packages:
1527 - rcs: Latest GPLv3 GNU rcs version.
1528 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
1532 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
1533 modules now requires that the kernel configuration contain the
1534 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
1537 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
1538 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
1541 Relocatable object files with the extension of .So have been renamed
1542 to use an extension of .pico instead. The purpose of this change is
1543 to avoid a name clash with shared libraries on case-insensitive file
1544 systems. On those file systems, foo.So is the same file as foo.so.
1547 GNU rcs has been turned off by default. It can (temporarily) be built
1548 again by adding WITH_RCS knob in src.conf.
1549 Otherwise, GNU rcs is available from packages:
1550 - rcs: Latest GPLv3 GNU rcs version.
1551 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
1554 The backup_uses_rcs functionality has been removed from rc.subr.
1557 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
1558 two separate components, QUEUE_MACRO_DEBUG_TRACE and
1559 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
1560 QUEUE_MACRO_DEBUG behavior.
1563 r304787 changed some ioctl interfaces between the iSCSI userspace
1564 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1565 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1569 The UDP receive code has been updated to only treat incoming UDP
1570 packets that were addressed to an L2 broadcast address as L3
1571 broadcast packets. It is not expected that this will affect any
1572 standards-conforming UDP application. The new behaviour can be
1573 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1577 Remove the openbsd_poll system call.
1578 __FreeBSD_version has been bumped because of this.
1581 The stable/11 branch has been created from head@r302406.
1584 The libc stub for the pipe(2) system call has been replaced with
1585 a wrapper that calls the pipe2(2) system call and the pipe(2)
1586 system call is now only implemented by the kernels that include
1587 "options COMPAT_FREEBSD10" in their config file (this is the
1588 default). Users should ensure that this option is enabled in
1589 their kernel or upgrade userspace to r302092 before upgrading their
1593 CAM now strips the leading spaces from each SCSI disk's serial number.
1594 This will affect users who create UFS filesystems on SCSI disks using
1595 those disk's diskid device nodes. For example, if /etc/fstab
1596 previously contained a line like
1597 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
1598 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
1599 transforms like gmirror may also be affected. ZFS users should
1603 The bitstring(3) API has been updated with new functionality and
1604 improved performance. But it is binary-incompatible with the old API.
1605 Objects built with the new headers may not be linked against objects
1606 built with the old headers.
1609 The brk and sbrk functions have been removed from libc on arm64.
1610 Binutils from ports has been updated to not link to these
1611 functions and should be updated to the latest version before
1612 installing a new libc.
1615 The armv6 port now defaults to hard float ABI. Limited support
1616 for running both hardfloat and soft float on the same system
1617 is available using the libraries installed with -DWITH_LIBSOFT.
1618 This has only been tested as an upgrade path for installworld
1619 and packages may fail or need manual intervention to run. New
1620 packages will be needed.
1622 To update an existing self-hosted armv6hf system, you must add
1623 TARGET_ARCH=armv6 on the make command line for both the build
1624 and the install steps.
1627 Kernel modules compiled outside of a kernel build now default to
1628 installing to /boot/modules instead of /boot/kernel. Many kernel
1629 modules built this way (such as those in ports) already overrode
1630 KMODDIR explicitly to install into /boot/modules. However,
1631 manually building and installing a module from /sys/modules will
1632 now install to /boot/modules instead of /boot/kernel.
1635 The CAM I/O scheduler has been committed to the kernel. There should be
1636 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1637 list of known rogues that claim support for this but actually corrupt
1638 data is believed to be complete, be on the lookout for data
1639 corruption. The known rogue list is believed to be complete:
1641 o Crucial MX100, M550 drives with MU01 firmware.
1642 o Micron M510 and M550 drives with MU01 firmware.
1643 o Micron M500 prior to MU07 firmware
1644 o Samsung 830, 840, and 850 all firmwares
1645 o FCCT M500 all firmwares
1647 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1648 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1649 updated firmware. Black listed drives will work correctly because these
1650 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1651 this list is the same as found in Linux, it's believed there are no
1652 other rogues in the market place. All other models from the above
1655 To be safe, if you are at all concerned, you can quirk each of your
1656 drives to prevent NCQ from being sent by setting:
1657 kern.cam.ada.X.quirks="0x2"
1658 in loader.conf. If the drive requires the 4k sector quirk, set the
1659 quirks entry to 0x3.
1662 The FAST_DEPEND build option has been removed and its functionality is
1663 now the one true way. The old mkdep(1) style of 'make depend' has
1664 been removed. See 20160311 for further details.
1667 Resource range types have grown from unsigned long to uintmax_t. All
1668 drivers, and anything using libdevinfo, need to be recompiled.
1671 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1672 builds. It no longer runs mkdep(1) during 'make depend', and the
1673 'make depend' stage can safely be skipped now as it is auto ran
1674 when building 'make all' and will generate all SRCS and DPSRCS before
1675 building anything else. Dependencies are gathered at compile time with
1676 -MF flags kept in separate .depend files per object file. Users should
1677 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1678 stale .depend files.
1681 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1682 kernel modules. Therefore, if you load any kernel modules at boot time,
1683 please install the boot loaders after you install the kernel, but before
1687 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1688 make installkernel KERNCONF=YOUR_KERNEL_HERE
1689 make -C sys/boot install
1690 <reboot in single user>
1692 Then follow the usual steps, described in the General Notes section,
1696 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1697 see the 20141231 entry below for information about prerequisites and
1698 upgrading, if you are not already using clang 3.5.0 or higher.
1701 The AIO subsystem is now a standard part of the kernel. The
1702 VFS_AIO kernel option and aio.ko kernel module have been removed.
1703 Due to stability concerns, asynchronous I/O requests are only
1704 permitted on sockets and raw disks by default. To enable
1705 asynchronous I/O requests on all file types, set the
1706 vfs.aio.enable_unsafe sysctl to a non-zero value.
1709 The ELF object manipulation tool objcopy is now provided by the
1710 ELF Tool Chain project rather than by GNU binutils. It should be a
1711 drop-in replacement, with the addition of arm64 support. The
1712 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1713 to obtain the GNU version if necessary.
1716 Building ZFS pools on top of zvols is prohibited by default. That
1717 feature has never worked safely; it's always been prone to deadlocks.
1718 Using a zvol as the backing store for a VM guest's virtual disk will
1719 still work, even if the guest is using ZFS. Legacy behavior can be
1720 restored by setting vfs.zfs.vol.recursive=1.
1723 The NONE and HPN patches has been removed from OpenSSH. They are
1724 still available in the security/openssh-portable port.
1727 With the addition of ypldap(8), a new _ypldap user is now required
1728 during installworld. "mergemaster -p" can be used to add the user
1729 prior to installworld, as documented in the handbook.
1732 The tftp loader (pxeboot) now uses the option root-path directive. As a
1733 consequence it no longer looks for a pxeboot.4th file on the tftp
1734 server. Instead it uses the regular /boot infrastructure as with the
1738 The code to start recording plug and play data into the modules has
1739 been committed. While the old tools will properly build a new kernel,
1740 a number of warnings about "unknown metadata record 4" will be produced
1741 for an older kldxref. To avoid such warnings, make sure to rebuild
1742 the kernel toolchain (or world). Make sure that you have r292078 or
1743 later when trying to build 292077 or later before rebuilding.
1746 Debug data files are now built by default with 'make buildworld' and
1747 installed with 'make installworld'. This facilitates debugging but
1748 requires more disk space both during the build and for the installed
1749 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1753 r291527 changed the internal interface between the nfsd.ko and
1754 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1755 __FreeBSD_version has been bumped because of this.
1758 Add support for unicode collation strings leads to a change of
1759 order of files listed by ls(1) for example. To get back to the old
1760 behaviour, set LC_COLLATE environment variable to "C".
1762 Databases administrators will need to reindex their databases given
1763 collation results will be different.
1765 Due to a bug in install(1) it is recommended to remove the ancient
1766 locales before running make installworld.
1768 rm -rf /usr/share/locale/*
1771 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1772 libcrypto.so.7 or libssl.so.7 must be recompiled.
1775 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1776 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1777 should be replaced with isp_2400 and isp_2500 modules respectively.
1780 The build previously allowed using 'make -n' to not recurse into
1781 sub-directories while showing what commands would be executed, and
1782 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1783 and 'make -N' will not.
1786 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1787 and etcupdate will now use this file. A custom sendmail.cf is now
1788 updated via this mechanism rather than via installworld. If you had
1789 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1790 want to remove the exclusion or change it to "always install".
1791 /etc/mail/sendmail.cf is now managed the same way regardless of
1792 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1793 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1796 Compatibility shims for legacy ATA device names have been removed.
1797 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1798 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1799 environment variables, /dev/ad* and /dev/ar* symbolic links.
1802 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1803 Please see the 20141231 entry below for information about prerequisites
1804 and upgrading, if you are not already using clang 3.5.0 or higher.
1807 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1808 and renamed from .symbols to .debug. This reduces the size requirements
1809 on the boot partition or file system and provides consistency with
1810 userland debug files.
1812 When using the supported kernel installation method the
1813 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1814 as is done with /boot/kernel.
1816 Developers wishing to maintain the historical behavior of installing
1817 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1820 The wireless drivers had undergone changes that remove the 'parent
1821 interface' from the ifconfig -l output. The rc.d network scripts
1822 used to check presence of a parent interface in the list, so old
1823 scripts would fail to start wireless networking. Thus, etcupdate(3)
1824 or mergemaster(8) run is required after kernel update, to update your
1825 rc.d scripts in /etc.
1828 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1829 These configurations are now automatically interpreted as
1830 'scrub fragment reassemble'.
1833 Kernel-loadable modules for the random(4) device are back. To use
1834 them, the kernel must have
1837 options RANDOM_LOADABLE
1839 kldload(8) can then be used to load random_fortuna.ko
1840 or random_yarrow.ko. Please note that due to the indirect
1841 function calls that the loadable modules need to provide,
1842 the build-in variants will be slightly more efficient.
1844 The random(4) kernel option RANDOM_DUMMY has been retired due to
1845 unpopularity. It was not all that useful anyway.
1848 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1849 Control over building the ELF Tool Chain tools is now provided by
1850 the WITHOUT_TOOLCHAIN knob.
1853 The polarity of Pulse Per Second (PPS) capture events with the
1854 uart(4) driver has been corrected. Prior to this change the PPS
1855 "assert" event corresponded to the trailing edge of a positive PPS
1856 pulse and the "clear" event was the leading edge of the next pulse.
1858 As the width of a PPS pulse in a typical GPS receiver is on the
1859 order of 1 millisecond, most users will not notice any significant
1860 difference with this change.
1862 Anyone who has compensated for the historical polarity reversal by
1863 configuring a negative offset equal to the pulse width will need to
1864 remove that workaround.
1867 The default group assigned to /dev/dri entries has been changed
1868 from 'wheel' to 'video' with the id of '44'. If you want to have
1869 access to the dri devices please add yourself to the video group
1872 # pw groupmod video -m $USER
1875 The menu.rc and loader.rc files will now be replaced during
1876 upgrades. Please migrate local changes to menu.rc.local and
1877 loader.rc.local instead.
1880 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1881 strings and strip have been removed. The src.conf(5) knob
1882 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1885 As ZFS requires more kernel stack pages than is the default on some
1886 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1887 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1889 Please consider using 'options KSTACK_PAGES=X' where X is greater
1890 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1893 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1894 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1895 default, i.e., they will not contain "::". For example, instead
1896 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1897 to have a more specific match, such as different map entries for
1898 IPv6:0:0 vs IPv6:0. This change requires that configuration
1899 data (including maps, files, classes, custom ruleset, etc.) must
1900 use the same format, so make certain such configuration data is
1901 upgrading. As a very simple check search for patterns like
1902 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1903 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1904 the cf option UseCompressedIPv6Addresses.
1907 The default kernel entropy-processing algorithm is now
1908 Fortuna, replacing Yarrow.
1910 Assuming you have 'device random' in your kernel config
1911 file, the configurations allow a kernel option to override
1912 this default. You may choose *ONE* of:
1914 options RANDOM_YARROW # Legacy /dev/random algorithm.
1915 options RANDOM_DUMMY # Blocking-only driver.
1917 If you have neither, you get Fortuna. For most people,
1918 read no further, Fortuna will give a /dev/random that works
1919 like it always used to, and the difference will be irrelevant.
1921 If you remove 'device random', you get *NO* kernel-processed
1922 entropy at all. This may be acceptable to folks building
1923 embedded systems, but has complications. Carry on reading,
1924 and it is assumed you know what you need.
1926 *PLEASE* read random(4) and random(9) if you are in the
1927 habit of tweaking kernel configs, and/or if you are a member
1928 of the embedded community, wanting specific and not-usual
1929 behaviour from your security subsystems.
1931 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1932 random', you will NOT have a functioning /dev/random, and
1933 many cryptographic features will not work, including SSH.
1934 You may also find strange behaviour from the random(3) set
1935 of library functions, in particular sranddev(3), srandomdev(3)
1936 and arc4random(3). The reason for this is that the KERN_ARND
1937 sysctl only returns entropy if it thinks it has some to
1938 share, and with RANDOM_DUMMY or no 'device random' this
1942 An additional fix for the issue described in the 20150614 sendmail
1943 entry below has been committed in revision 284717.
1946 FreeBSD's old make (fmake) has been removed from the system. It is
1947 available as the devel/fmake port or via pkg install fmake.
1950 The fix for the issue described in the 20150614 sendmail entry
1951 below has been committed in revision 284436. The work
1952 around described in that entry is no longer needed unless the
1953 default setting is overridden by a confDH_PARAMETERS configuration
1954 setting of '5' or pointing to a 512 bit DH parameter file.
1957 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1958 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1959 and devel/kyua to version 0.20+ and adjust any calling code to work
1960 with Kyuafile and kyua.
1963 The import of openssl to address the FreeBSD-SA-15:10.openssl
1964 security advisory includes a change which rejects handshakes
1965 with DH parameters below 768 bits. sendmail releases prior
1966 to 8.15.2 (not yet released), defaulted to a 512 bit
1967 DH parameter setting for client connections. To work around
1968 this interoperability, sendmail can be configured to use a
1969 2048 bit DH parameter by:
1971 1. Edit /etc/mail/`hostname`.mc
1972 2. If a setting for confDH_PARAMETERS does not exist or
1973 exists and is set to a string beginning with '5',
1974 replace it with '2'.
1975 3. If a setting for confDH_PARAMETERS exists and is set to
1976 a file path, create a new file with:
1977 openssl dhparam -out /path/to/file 2048
1978 4. Rebuild the .cf file:
1979 cd /etc/mail/; make; make install
1980 5. Restart sendmail:
1981 cd /etc/mail/; make restart
1983 A sendmail patch is coming, at which time this file will be
1987 Generation of legacy formatted entries have been disabled by default
1988 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1989 entries were converted to use the new format by default when the new,
1990 machine independent format have been added and supported since FreeBSD
1993 Please see the pwd_mkdb(8) manual page for further details.
1996 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1997 20141231 entry below for information about prerequisites and upgrading,
1998 if you are not already using 3.5.0 or higher.
2001 TI platform code switched to using vendor DTS files and this update
2002 may break existing systems running on Beaglebone, Beaglebone Black,
2005 - dtb files should be regenerated/reinstalled. Filenames are the
2006 same but content is different now
2007 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
2008 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
2009 addressing scheme is now pin 25 on /dev/gpioc3.
2010 - Pandaboard: /etc/ttys should be updated, serial console device is
2011 now /dev/ttyu2, not /dev/ttyu0
2014 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
2015 If you need the GNU extension from groff soelim(1), install groff
2016 from package: pkg install groff, or via ports: textproc/groff.
2019 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
2020 defined in symlink(7); previously symlinks were silently ignored.
2023 The const qualifier has been removed from iconv(3) to comply with
2024 POSIX. The ports tree is aware of this from r384038 onwards.
2027 Libraries specified by LIBADD in Makefiles must have a corresponding
2028 DPADD_<lib> variable to ensure correct dependencies. This is now
2029 enforced in src.libnames.mk.
2032 From legacy ata(4) driver was removed support for SATA controllers
2033 supported by more functional drivers ahci(4), siis(4) and mvs(4).
2034 Kernel modules ataahci and ataadaptec were removed completely,
2035 replaced by ahci and mvs modules respectively.
2038 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
2039 the 20141231 entry below for information about prerequisites and
2040 upgrading, if you are not already using 3.5.0 or higher.
2043 The 32-bit PowerPC kernel has been changed to a position-independent
2044 executable. This can only be booted with a version of loader(8)
2045 newer than January 31, 2015, so make sure to update both world and
2046 kernel before rebooting.
2049 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
2050 but before r278950, the RNG was not seeded properly. Immediately
2051 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
2052 ssh keys or openssl keys) that were generated w/ a kernel from that
2053 range. This does not affect programs that directly used /dev/random
2054 or /dev/urandom. All userland uses of arc4random(3) are affected.
2057 The autofs(4) ABI was changed in order to restore binary compatibility
2058 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
2059 with the new kernel.
2062 The powerpc64 kernel has been changed to a position-independent
2063 executable. This can only be booted with a new version of loader(8),
2064 so make sure to update both world and kernel before rebooting.
2067 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
2068 only release, no new features have been added. Please see the 20141231
2069 entry below for information about prerequisites and upgrading, if you
2070 are not already using 3.5.0.
2073 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
2074 taken from the ELF Tool Chain project rather than GNU binutils. They
2075 should be drop-in replacements, with the addition of arm64 support.
2076 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
2077 binutils tools, if necessary. See 20150805 for updated information.
2080 The default Unbound configuration now enables remote control
2081 using a local socket. Users who have already enabled the
2082 local_unbound service should regenerate their configuration
2083 by running "service local_unbound setup" as root.
2086 The GNU texinfo and GNU info pages have been removed.
2087 To be able to view GNU info pages please install texinfo from ports.
2090 Clang, llvm and lldb have been upgraded to 3.5.0 release.
2092 As of this release, a prerequisite for building clang, llvm and lldb is
2093 a C++11 capable compiler and C++11 standard library. This means that to
2094 be able to successfully build the cross-tools stage of buildworld, with
2095 clang as the bootstrap compiler, your system compiler or cross compiler
2096 should either be clang 3.3 or later, or gcc 4.8 or later, and your
2097 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
2100 On any standard FreeBSD 10.x or 11.x installation, where clang and
2101 libc++ are on by default (that is, on x86 or arm), this should work out
2104 On 9.x installations where clang is enabled by default, e.g. on x86 and
2105 powerpc, libc++ will not be enabled by default, so libc++ should be
2106 built (with clang) and installed first. If both clang and libc++ are
2107 missing, build clang first, then use it to build libc++.
2109 On 8.x and earlier installations, upgrade to 9.x first, and then follow
2110 the instructions for 9.x above.
2112 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
2113 default, and do not build clang.
2115 Many embedded systems are resource constrained, and will not be able to
2116 build clang in a reasonable time, or in some cases at all. In those
2117 cases, cross building bootable systems on amd64 is a workaround.
2119 This new version of clang introduces a number of new warnings, of which
2120 the following are most likely to appear:
2124 This warns in two cases, for both C and C++:
2125 * When the code is trying to take the absolute value of an unsigned
2126 quantity, which is effectively a no-op, and almost never what was
2127 intended. The code should be fixed, if at all possible. If you are
2128 sure that the unsigned quantity can be safely cast to signed, without
2129 loss of information or undefined behavior, you can add an explicit
2130 cast, or disable the warning.
2132 * When the code is trying to take an absolute value, but the called
2133 abs() variant is for the wrong type, which can lead to truncation.
2134 If you want to disable the warning instead of fixing the code, please
2135 make sure that truncation will not occur, or it might lead to unwanted
2138 -Wtautological-undefined-compare and
2139 -Wundefined-bool-conversion
2141 These warn when C++ code is trying to compare 'this' against NULL, while
2142 'this' should never be NULL in well-defined C++ code. However, there is
2143 some legacy (pre C++11) code out there, which actively abuses this
2144 feature, which was less strictly defined in previous C++ versions.
2146 Squid and openjdk do this, for example. The warning can be turned off
2147 for C++98 and earlier, but compiling the code in C++11 mode might result
2148 in unexpected behavior; for example, the parts of the program that are
2149 unreachable could be optimized away.
2152 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
2153 kernel sources have been removed. The .h files remain, since some
2154 utilities include them. This will need to be fixed later.
2155 If "mount -t oldnfs ..." is attempted, it will fail.
2156 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
2157 the utilities will report errors.
2160 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
2161 directories to top level SUBDIR variable when their parent
2162 directory is included in LOCAL_DIRS. Users with build systems with
2163 such hierarchies and without SUBDIR entries in the parent
2164 directory Makefiles should add them or add the directories to
2168 faith(4) and faithd(8) have been removed from the base system. Faith
2169 has been obsolete for a very long time.
2172 vt(4), the new console driver, is enabled by default. It brings
2173 support for Unicode and double-width characters, as well as
2174 support for UEFI and integration with the KMS kernel video
2177 You may need to update your console settings in /etc/rc.conf,
2178 most probably the keymap. During boot, /etc/rc.d/syscons will
2179 indicate what you need to do.
2181 vt(4) still has issues and lacks some features compared to
2182 syscons(4). See the wiki for up-to-date information:
2183 https://wiki.freebsd.org/Newcons
2185 If you want to keep using syscons(4), you can do so by adding
2186 the following line to /boot/loader.conf:
2190 pjdfstest has been integrated into kyua as an opt-in test suite.
2191 Please see share/doc/pjdfstest/README for more details on how to
2195 gperf has been removed from the base system for architectures
2196 that use clang. Ports that require gperf will obtain it from the
2200 pjdfstest has been moved from tools/regression/pjdfstest to
2204 At svn r271982, The default linux compat kernel ABI has been adjusted
2205 to 2.6.18 in support of the linux-c6 compat ports infrastructure
2206 update. If you wish to continue using the linux-f10 compat ports,
2207 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
2208 encouraged to update their linux-compat packages to linux-c6 during
2209 their next update cycle.
2212 The ofwfb driver, used to provide a graphics console on PowerPC when
2213 using vt(4), no longer allows mmap() of all physical memory. This
2214 will prevent Xorg on PowerPC with some ATI graphics cards from
2215 initializing properly unless x11-servers/xorg-server is updated to
2219 The xdev targets have been converted to using TARGET and
2220 TARGET_ARCH instead of XDEV and XDEV_ARCH.
2223 The default unbound configuration has been modified to address
2224 issues with reverse lookups on networks that use private
2225 address ranges. If you use the local_unbound service, run
2226 "service local_unbound setup" as root to regenerate your
2227 configuration, then "service local_unbound reload" to load the
2231 The GNU texinfo and GNU info pages are not built and installed
2232 anymore, WITH_INFO knob has been added to allow to built and install
2234 UPDATE: see 20150102 entry on texinfo's removal
2237 The GNU readline library is now an INTERNALLIB - that is, it is
2238 statically linked into consumers (GDB and variants) in the base
2239 system, and the shared library is no longer installed. The
2240 devel/readline port is available for third party software that
2244 The Itanium architecture (ia64) has been removed from the list of
2245 known architectures. This is the first step in the removal of the
2249 Commit r268115 has added NFSv4.1 server support, merged from
2250 projects/nfsv4.1-server. Since this includes changes to the
2251 internal interfaces between the NFS related modules, a full
2252 build of the kernel and modules will be necessary.
2253 __FreeBSD_version has been bumped.
2256 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
2257 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
2258 which differs from the behaviour controlled by this knob.)
2261 Maximal length of the serial number in CTL was increased from 16 to
2262 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
2263 and ctld, need to be rebuilt to work with a new kernel.
2266 The libatf-c and libatf-c++ major versions were downgraded to 0 and
2267 1 respectively to match the upstream numbers. They were out of
2268 sync because, when they were originally added to FreeBSD, the
2269 upstream versions were not respected. These libraries are private
2270 and not yet built by default, so renumbering them should be a
2271 non-issue. However, unclean source trees will yield broken test
2272 programs once the operator executes "make delete-old-libs" after a
2273 "make installworld".
2275 Additionally, the atf-sh binary was made private by moving it into
2276 /usr/libexec/. Already-built shell test programs will keep the
2277 path to the old binary so they will break after "make delete-old"
2280 If you are using WITH_TESTS=yes (not the default), wipe the object
2281 tree and rebuild from scratch to prevent spurious test failures.
2282 This is only needed once: the misnumbered libraries and misplaced
2283 binaries have been added to OptionalObsoleteFiles.inc so they will
2284 be removed during a clean upgrade.
2287 Clang and llvm have been upgraded to 3.4.1 release.
2290 We bogusly installed src.opts.mk in /usr/share/mk. This file should
2291 be removed to avoid issues in the future (and has been added to
2295 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
2296 past, it affected all builds that used the bsd.*.mk files. The old
2297 behavior was a bug, but people may have relied upon it. To get this
2298 behavior back, you can .include /etc/src.conf from /etc/make.conf
2299 (which is still global and isn't changed). This also changes the
2300 behavior of incremental builds inside the tree of individual
2301 directories. Set MAKESYSPATH to ".../share/mk" to do that.
2302 Although this has survived make universe and some upgrade scenarios,
2303 other upgrade scenarios may have broken. At least one form of
2304 temporary breakage was fixed with MAKESYSPATH settings for buildworld
2305 as well... In cases where MAKESYSPATH isn't working with this
2306 setting, you'll need to set it to the full path to your tree.
2308 One side effect of all this cleaning up is that bsd.compiler.mk
2309 is no longer implicitly included by bsd.own.mk. If you wish to
2310 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
2314 The lindev device has been removed since /dev/full has been made a
2315 standard device. __FreeBSD_version has been bumped.
2318 The knob WITHOUT_VI was added to the base system, which controls
2319 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
2320 in order to reorder files share/termcap and didn't build ex(1) as a
2321 build tool, so building/installing with WITH_VI is highly advised for
2322 build hosts for older releases.
2324 This issue has been fixed in stable/9 and stable/10 in r277022 and
2325 r276991, respectively.
2328 The YES_HESIOD knob has been removed. It has been obsolete for
2329 a decade. Please move to using WITH_HESIOD instead or your builds
2330 will silently lack HESIOD.
2333 The uart(4) driver has been changed with respect to its handling
2334 of the low-level console. Previously the uart(4) driver prevented
2335 any process from changing the baudrate or the CLOCAL and HUPCL
2336 control flags. By removing the restrictions, operators can make
2337 changes to the serial console port without having to reboot.
2338 However, when getty(8) is started on the serial device that is
2339 associated with the low-level console, a misconfigured terminal
2340 line in /etc/ttys will now have a real impact.
2341 Before upgrading the kernel, make sure that /etc/ttys has the
2342 serial console device configured as 3wire without baudrate to
2343 preserve the previous behaviour. E.g:
2344 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
2347 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
2348 to improve performance. To re-enable it, if needed, run rpcbind
2349 with command line option -W.
2352 Switched back to the GPL dtc compiler due to updates in the upstream
2353 dts files not being supported by the BSDL dtc compiler. You will need
2354 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
2355 may result while building dtb files during a kernel build if you fail
2356 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
2359 Clang and llvm have been upgraded to 3.4 release.
2362 The nve(4) driver has been removed. Please use the nfe(4) driver
2363 for NVIDIA nForce MCP Ethernet adapters instead.
2366 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
2367 This could cause certain C++ applications using shared libraries built
2368 against the previous version of libc++ to crash. The incompatibility
2369 has now been fixed, but any C++ applications or shared libraries built
2370 between r261283 and r261801 should be recompiled.
2373 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
2374 capability mode support. Please note that enabling the feature in
2375 kernel is still highly recommended.
2378 OpenSSH is now built with sandbox support, and will use sandbox as
2379 the default privilege separation method. This requires Capsicum
2380 capability mode support in kernel.
2383 The libelf and libdwarf libraries have been updated to newer
2384 versions from upstream. Shared library version numbers for
2385 these two libraries were bumped. Any ports or binaries
2386 requiring these two libraries should be recompiled.
2387 __FreeBSD_version is bumped to 1100006.
2390 If a Makefile in a tests/ directory was auto-generating a Kyuafile
2391 instead of providing an explicit one, this would prevent such
2392 Makefile from providing its own Kyuafile in the future during
2393 NO_CLEAN builds. This has been fixed in the Makefiles but manual
2394 intervention is needed to clean an objdir if you use NO_CLEAN:
2395 # find /usr/obj -name Kyuafile | xargs rm -f
2398 The behavior of gss_pseudo_random() for the krb5 mechanism
2399 has changed, for applications requesting a longer random string
2400 than produced by the underlying enctype's pseudo-random() function.
2401 In particular, the random string produced from a session key of
2402 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
2403 be different at the 17th octet and later, after this change.
2404 The counter used in the PRF+ construction is now encoded as a
2405 big-endian integer in accordance with RFC 4402.
2406 __FreeBSD_version is bumped to 1100004.
2409 The WITHOUT_ATF build knob has been removed and its functionality
2410 has been subsumed into the more generic WITHOUT_TESTS. If you were
2411 using the former to disable the build of the ATF libraries, you
2412 should change your settings to use the latter.
2415 The default version of mtree is nmtree which is obtained from
2416 NetBSD. The output is generally the same, but may vary
2417 slightly. If you found you need identical output adding
2418 "-F freebsd9" to the command line should do the trick. For the
2419 time being, the old mtree is available as fmtree.
2422 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
2423 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
2424 1.1.4_8 and verify bsdyml not linked in, before running "make
2426 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
2428 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
2431 The stable/10 branch has been created in subversion from head
2438 Sometimes, obscure build problems are the result of environment
2439 poisoning. This can happen because the make utility reads its
2440 environment when searching for values for global variables. To run
2441 your build attempts in an "environmental clean room", prefix all make
2442 commands with 'env -i '. See the env(1) manual page for more details.
2443 Occasionally a build failure will occur with "make -j" due to a race
2444 condition. If this happens try building again without -j, and please
2445 report a bug if it happens consistently.
2447 When upgrading from one major version to another it is generally best to
2448 upgrade to the latest code in the currently installed branch first, then
2449 do an upgrade to the new branch. This is the best-tested upgrade path,
2450 and has the highest probability of being successful. Please try this
2451 approach if you encounter problems with a major version upgrade. Since
2452 the stable 4.x branch point, one has generally been able to upgrade from
2453 anywhere in the most recent stable branch to head / current (or even the
2454 last couple of stable branches). See the top of this file when there's
2457 The update process will emit an error on an attempt to perform a build
2458 or install from a FreeBSD version below the earliest supported version.
2459 When updating from an older version the update should be performed one
2460 major release at a time, including running `make delete-old` at each
2463 When upgrading a live system, having a root shell around before
2464 installing anything can help undo problems. Not having a root shell
2465 around can lead to problems if pam has changed too much from your
2466 starting point to allow continued authentication after the upgrade.
2468 This file should be read as a log of events. When a later event changes
2469 information of a prior event, the prior event should not be deleted.
2470 Instead, a pointer to the entry with the new information should be
2471 placed in the old entry. Readers of this file should also sanity check
2472 older entries before relying on them blindly. Authors of new entries
2473 should write them with this in mind.
2477 When upgrading the boot ZFS pool to a new version, always follow
2480 1.) recompile and reinstall the ZFS boot loader and boot block
2481 (this is part of "make buildworld" and "make installworld")
2483 2.) update the ZFS boot block on your boot drive
2485 The following example updates the ZFS boot block on the
2486 freebsd-boot partition of a GPT partitioned drive ada0:
2487 "gpart bootcode -p /boot/gptzfsboot -i $N ada0"
2488 The value $N will typically be 1 (if booting from BIOS) or 2 (if
2491 Non-boot pools do not need these updates.
2495 If you are updating from a prior version of FreeBSD (even one just
2496 a few days old), you should follow this procedure. It is the most
2497 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2499 make kernel-toolchain
2500 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2501 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2503 To test a kernel once
2504 ---------------------
2505 If you just want to boot a kernel once (because you are not sure
2506 if it works, or if you want to boot a known bad kernel to provide
2507 debugging information) run
2508 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2509 nextboot -k testkernel
2511 To rebuild everything and install it on the current system.
2512 -----------------------------------------------------------
2513 # Note: sometimes if you are running current you gotta do more than
2514 # is listed here if you are upgrading from a really old current.
2516 <make sure you have good level 0 dumps>
2518 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2519 make installkernel KERNCONF=YOUR_KERNEL_HERE
2521 <reboot in single user> [3]
2528 To cross-install current onto a separate partition
2529 --------------------------------------------------
2530 # In this approach we use a separate partition to hold
2531 # current's root, 'usr', and 'var' directories. A partition
2532 # holding "/", "/usr" and "/var" should be about 2GB in
2535 <make sure you have good level 0 dumps>
2538 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2539 <maybe newfs current's root partition>
2540 <mount current's root partition on directory ${CURRENT_ROOT}>
2541 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
2542 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2543 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2544 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2545 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2546 <reboot into current>
2547 <do a "native" rebuild/install as described in the previous section>
2548 <maybe install compatibility libraries from ports/misc/compat*>
2552 To upgrade in-place from stable to current
2553 ----------------------------------------------
2554 <make sure you have good level 0 dumps>
2556 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
2557 make installkernel KERNCONF=YOUR_KERNEL_HERE
2559 <reboot in single user> [3]
2566 Make sure that you've read the UPDATING file to understand the
2567 tweaks to various things you need. At this point in the life
2568 cycle of current, things change often and you are on your own
2569 to cope. The defaults can also change, so please read ALL of
2570 the UPDATING entries.
2572 Also, if you are tracking -current, you must be subscribed to
2573 freebsd-current@freebsd.org. Make sure that before you update
2574 your sources that you have read and understood all the recent
2575 messages there. If in doubt, please track -stable which has
2576 much fewer pitfalls.
2578 [1] If you have third party modules, such as vmware, you should disable
2579 them at this point so they don't crash your system on
2580 reboot. Alternatively, you should rebuild all the modules you have in
2581 your system and install them as well. If you are running -current, you
2582 should seriously consider placing all sources to all the modules for
2583 your system (or symlinks to them) in /usr/local/sys/modules so this
2584 happens automatically. If all your modules come from ports, then adding
2585 the port origin directories to PORTS_MODULES instead is also automatic
2587 PORTS_MODULES+=x11/nvidia-driver
2589 [3] From the bootblocks, boot -s, and then do
2593 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed
2594 cd src # full path to source
2595 adjkerntz -i # if CMOS is wall time
2596 Also, when doing a major release upgrade, it is required that you boot
2597 into single user mode to do the installworld.
2599 [4] Note: This step is non-optional. Failure to do this step
2600 can result in a significant reduction in the functionality of the
2601 system. Attempting to do it by hand is not recommended and those
2602 that pursue this avenue should read this file carefully, as well
2603 as the archives of freebsd-current and freebsd-hackers mailing lists
2604 for potential gotchas. See etcupdate(8) for more information.
2606 [5] Usually this step is a no-op. However, from time to time
2607 you may need to do this if you get unknown user in the following
2610 [6] This only deletes old files and directories. Old libraries
2611 can be deleted by "make delete-old-libs", but you have to make
2612 sure that no program is using those libraries anymore.
2614 [8] The new kernel must be able to run existing binaries used by an
2615 installworld. When upgrading across major versions, the new kernel's
2616 configuration must include the correct COMPAT_FREEBSD<n> option for
2617 existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure
2618 to do so may leave you with a system that is hard to boot to recover. A
2619 GENERIC kernel will include suitable compatibility options to run
2620 binaries from older branches. Note that the ability to run binaries
2621 from unsupported branches is not guaranteed.
2623 Make sure that you merge any new devices from GENERIC since the
2624 last time you updated your kernel config file. Options also
2625 change over time, so you may need to adjust your custom kernels
2628 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2629 "?=" instead of the "=" assignment operator, so that buildworld can
2630 override the CPUTYPE if it needs to.
2632 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2633 not on the command line, or in /etc/make.conf. buildworld will
2634 warn if it is improperly defined.
2637 This file contains a list, in reverse chronological order, of major
2638 breakages in tracking -current. It is not guaranteed to be a complete
2639 list of such breakages, and only contains entries since September 23, 2011.
2640 If you need to see UPDATING entries from before that date, you will need
2641 to fetch an UPDATING file from an older FreeBSD release.
2643 Copyright information:
2645 Copyright 1998-2009 M. Warner Losh <imp@FreeBSD.org>
2647 Redistribution, publication, translation and use, with or without
2648 modification, in full or in part, in any form or format of this
2649 document are permitted without further permission from the author.
2651 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2652 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2653 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2654 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2655 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2656 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2657 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2658 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2659 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2660 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2661 POSSIBILITY OF SUCH DAMAGE.
2663 Contact Warner Losh if you have any questions about your use of