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 Some programs have been moved into separate packages. It is recommended
32 for pkgbase users to do:
34 pkg install FreeBSD-dhclient FreeBSD-geom FreeBSD-resolvconf \
35 FreeBSD-devd FreeBSD-devmatch
37 after upgrading to restore all the component that were previously
41 LinuxKPI pm.h changes require an update to the latest drm-kmod version
42 before re-compiling to avoid errors.
45 The macros provided for the manipulation of CPU sets (e.g. CPU_AND)
46 have been modified to take 2 source arguments instead of only 1.
47 Externally maintained sources that use these macros will have to
48 be adapted. The FreeBSD version has been bumped to 1400046 to
52 A number of the kernel include files are able to be included by
53 themselves. A test has been added to buildworld to enforce this.
56 Remove mips as a recognized target. This starts the decommissioning of
57 mips support in FreeBSD. mips related items will be removed wholesale in
58 the coming days and weeks.
60 This broke the NO_CLEAN build for some people. Either do a clean build
62 lib/clang/include/llvm/Config/Targets.def
63 lib/clang/include/llvm/Config/AsmParsers.def
64 lib/clang/include/llvm/Config/Disassemblers.def
65 lib/clang/include/llvm/Config/AsmPrinters.def
66 before the build to force everything to rebuild that needs to.
69 Unbound support for RFC8375: The special-use domain 'home.arpa' is
70 by default blocked. To unblock it use a local-zone nodefault
71 statement in unbound.conf:
72 local-zone: "home.arpa." nodefault
74 Or use another type of local-zone to override with your choice.
76 The reason for this is discussed in Section 6.1 of RFC8375:
77 Because 'home.arpa.' is not globally scoped and cannot be secured
78 using DNSSEC based on the root domain's trust anchor, there is no way
79 to tell, using a standard DNS query, in which homenet scope an answer
80 belongs. Consequently, users may experience surprising results with
81 such names when roaming to different homenets.
84 Commit b8d60729deef changed the TCP congestion control framework so
85 that any of the included congestion control modules could be
86 the single module built into the kernel. Previously newreno
87 was automatically built in through direct reference. As of
88 this commit you are required to declare at least one congestion
89 control module (e.g. 'options CC_NEWRENO') and to also declare a
90 default using the CC_DEFAULT option (e.g. options CC_DEFAULT="newreno\").
91 The GENERIC configuration includes CC_NEWRENO and defines newreno
92 as the default. If no congestion control option is built into the
93 kernel and you are including networking, the kernel compile will
94 fail. Also if no default is declared the kernel compile will fail.
97 Mips has been removed from universe builds. It will be removed from the
101 Commit f0c9847a6c47 changed the arguments for VOP_ALLOCATE.
102 The NFS modules must be rebuilt from sources and any out
103 of tree file systems that implement their own VOP_ALLOCATE
104 may need to be modified.
107 The synchronous PPP kernel driver sppp(4) has been removed.
108 The cp(4) and ce(4) drivers are now always compiled with netgraph(4)
109 support, formerly enabled by NETGRAPH_CRONYX option.
112 sh(1) is now the default shell for the root user. To force root to use
113 the csh shell, please run the following command as root:
118 Ncurses distribution has been split between libtinfow and libncurses
119 with libncurses.so becoming a linker (ld) script to seamlessly link
120 to libtinfow as needed. Bump _FreeBSD_version to 1400035 to reflect
124 As of commit 8160a0f62be6, the dummynet module no longer depends on the
125 ipfw module. Dummynet can now be used by pf as well as ipfw. As such
126 users who relied on this dependency may need to include ipfw in the
127 list of modules to load on their systems.
130 As of commit 903873ce1560, the mixer(8) utility has got a slightly
131 new syntax. Please refer to the mixer(8) manual page for more
132 information. The old mixer utility can be installed from ports:
133 audio/freebsd-13-mixer
136 As of commit 55089ef4f8bb, the global variable nfs_maxcopyrange has
137 been deleted from the nfscommon.ko. As such, nfsd.ko must be built
138 from up to date sources to avoid an undefined reference when
142 As of commit 62ca9fc1ad56 OpenSSL no longer enables kernel TLS
143 by default. Users can enable kernel TLS via the "KTLS" SSL
144 option. This can be enabled globally by using a custom
145 OpenSSL config file via OPENSSL_CONF or via an
146 application-specific configuration option for applications
147 which permit setting SSL options via SSL_CONF_cmd(3).
150 Commit 3ad1e1c1ce20 changed the internal KAPI between the NFS
151 modules. Therefore, all need to be rebuilt from sources.
154 Commit b69019c14cd8 removes pf's DIOCGETSTATESNV ioctl.
155 As of be70c7a50d32 it is no longer used by userspace, but it does mean
156 users may not be able to enumerate pf states if they update the kernel
157 past b69019c14cd8 without first updating userspace past be70c7a50d32.
160 As of commit 01ad0c007964 if_bridge member interfaces can no longer
161 change their MTU. Changing the MTU of the bridge itself will change the
162 MTU on all member interfaces instead.
165 Commit ee29e6f31111 changed the internal KAPI between the nfscommon
166 and nfsd modules. Therefore, both need to be rebuilt from sources.
167 Bump __FreeBSD_version to 1400026 for this KAPI change.
170 The 20210707 awk update brought in a change in behavior. This has
171 been corrected as of d4d252c49976. Between these dates, if you
172 installed a new awk binary, you may not be able to build a new
173 kernel because the change in behavior affected the genoffset
174 script used to build the kernel. If you did update, the fix is
175 to update your sources past the above hash and do
178 % sudo -E make install
179 to enable building kernels again.
182 Commit 1e0a518d6548 changed the internal KAPI between the NFS
183 modules. They all need to be rebuilt from sources. I did not
184 bump __FreeBSD_version, since it was bumped recently.
187 awk has been updated to the latest one-true-awk version 20210215.
188 This contains a number of minor bug fixes.
191 The NFSv4 client now uses the highest minor version of NFSv4
192 supported by the NFSv4 server by default instead of minor version 0,
194 The "minorversion" mount option may be used to override this default.
197 Bump __FreeBSD_version to 1400024 for LinuxKPI changes.
198 Most notably netdev.h can change now as the (last) dependencies
199 (mlx4/ofed) are now using struct ifnet directly, but also for PCI
200 additions and others.
203 The directory "blacklisted" under /usr/share/certs/ has been
204 renamed to "untrusted".
207 svnlite has been removed from base. Should you need svn for any reason
208 please install the svn package or port.
211 Commit e1a907a25cfa changed the internal KAPI between the krpc
212 and nfsserver. As such, both modules must be rebuilt from
213 sources. Bump __FreeBSD_version to 1400022.
216 The an(4) driver has been removed from FreeBSD.
219 The vendor/openzfs branch was renamed to vendor/openzfs/legacy to
220 start tracking OpenZFS upstream more closely. Please see
221 https://lists.freebsd.org/archives/freebsd-current/2021-June/000153.html
222 for details on how to correct any errors that might result. The
223 short version is that you need to remove the old branch locally:
224 git update-ref -d refs/remotes/freebsd/vendor/openzfs
225 (assuming your upstream origin is named 'freebsd').
228 Commits 17accc08ae15 and de102f870501 add new files to LinuxKPI
229 which break drm-kmod. In addition various other additions where
230 committed. Bump __FreeBSD_version to 1400015 to be able to
234 Commit ca179c4d74f2 changed the package in which the OpenSSL
235 libraries and utilities are packaged.
236 It is recommended for pkgbase user to do:
237 pkg install -f FreeBSD-openssl
238 before pkg upgrade otherwise some dependencies might not be met
239 and pkg will stop working as libssl will not be present anymore
243 Commit 875977314881 changed the internal KAPI between
244 the nfsd and nfscommon modules. As such these modules
245 need to be rebuilt from sources.
246 Without this patch in your NFSv4.1/4.2 server, enabling
247 delegations by setting vfs.nfsd.issue_delegations non-zero
251 Commit 7763814fc9c2 changed the internal KAPI between
252 the krpc and NFS. As such, the krpc, nfscommon and
253 nfscl modules must all be rebuilt from sources.
254 Without this patch, NFSv4.1/4.2 mounts should not
255 be done with the nfscbd(8) daemon running, to avoid
256 needing a working back channel for server->client RPCs.
259 Commit 01ae8969a9ee fixed the NFSv4.1/4.2 server so that it
260 handles binding of the back channel as required by RFC5661.
261 Until this patch is in your server, avoid use of the "nconnects"
262 mount option for Linux NFSv4.1/4.2 mounts.
265 For 64-bit architectures the base system is now built with Position
266 Independent Executable (PIE) support enabled by default. It may be
267 disabled using the WITHOUT_PIE knob. A clean build is required.
270 Various LinuxKPI functionality was added which conflicts with DRM.
271 Please update your drm-kmod port to after the __FreeBSD_version 1400003
275 PC Card attachments for all devices have been removed. In the case of
276 wi and cmx, the entire drivers were removed because they were only
277 PC Card devices. FreeBSD_version 1300134 should be used for this
278 since it was bumped so recently.
281 Transport-independent parts of HID support have been split off the USB
282 code in to separate subsystem. Kernel configs which include one of
283 ums, ukbd, uhid, atp, wsp, wmt, uaudio, ugold or ucycom drivers should
284 be updated with adding of "device hid" line.
287 ncurses installation has been modified to only keep the widechar
288 enabled version. Incremental build is broken for that change, so it
289 requires a clean build.
292 The FreeBSD project has migrated from Subversion to Git. Temporary
293 instructions can be found at
294 https://github.com/bsdimp/freebsd-git-docs/blob/main/src-cvt.md
295 and other documents in that repo.
298 The services database has been updated to cover more of the basic
299 services expected in a modern system. The database is big enough
300 that it will cause issues in mergemaster in Releases previous to
301 12.2 and 11.3, or in very old current systems from before r358154.
304 Obsolete in-tree GDB 6.1.1 has been removed. GDB (including kgdb)
305 may be installed from ports or packages.
308 ping6 has been merged into ping. It can now be called as "ping -6".
309 See ping(8) for details.
312 Default value of net.add_addr_allfibs has been changed to 0.
313 If you have multi-fib configuration and rely on existence of all
314 interface routes in every fib, you need to set the above sysctl to 1.
317 The internal pre-processor in the calendar(1) program has been
318 extended to support more C pre-processor commands (e.g. #ifdef, #else,
319 and #undef) and to detect unbalanced conditional statements.
320 Error messages have been extended to include the filename and line
321 number if processing stops to help fixing malformed data files.
324 All the data files for the calendar(1) program, except calendar.freebsd,
325 have been moved to the deskutils/calendar-data port, much like the
326 jewish calendar entries were moved to deskutils/hebcal years ago. After
327 make delete-old-files, you need to install it to retain full
328 functionality. calendar(1) will issue a reminder for files it can't
332 LINT files are no longer generated. We now include the relevant NOTES
333 files. Note: This may cause conflicts with updating in some cases.
334 find sys -name LINT\* -delete
335 is suggested across this commit to remove the generated LINT files.
337 If you have tried to update with generated files there, the svn
338 command you want to un-auger the tree is
341 and then do the above find from the top level. Substitute 'amd64'
342 above with where the error message indicates a conflict.
345 OpenZFS support has been integrated. Do not upgrade root pools until
346 the loader is updated to support zstd. Furthermore, we caution against
347 'zpool upgrade' for the next few weeks. The change should be transparent
348 unless you want to use new features.
350 Not all "NO_CLEAN" build scenarios work across these changes. Many
351 scenarios have been tested and fixed, but rebuilding kernels without
352 rebuilding world may fail.
354 The ZFS cache file has moved from /boot to /etc to match the OpenZFS
355 upstream default. A fallback to /boot has been added for mountroot.
357 Pool auto import behavior at boot has been moved from the kernel module
358 to an explicit "zpool import -a" in one of the rc scripts enabled by
359 zfs_enable=YES. This means your non-root zpools won't auto import until
360 you upgrade your /etc/rc.d files.
363 The resume code now notifies devd with the 'kernel' system
364 rather than the old 'kern' subsystem to be consistent with
365 other use. The old notification will be created as well, but
366 will be removed prior to FreeBSD 14.0.
369 r362275 changed the internal API between the kernel RPC and the
370 NFS modules. As such, all the modules must be recompiled from
374 r364330 modified the internal API used between the NFS modules.
375 As such, all the NFS modules must be re-compiled from sources.
378 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
379 been upgraded to 11.0.0. Please see the 20141231 entry below for
380 information about prerequisites and upgrading, if you are not already
381 using clang 3.5.0 or higher.
384 r364092 modified the internal ABI used between the kernel NFS
385 modules. As such, all of these modules need to be rebuilt
386 from sources, so a version bump was done.
389 Makefile.inc has been updated to work around the issue documented in
390 20200729. It was a case where the optimization of using symbolic links
391 to point to binaries created a situation where we'd run new binaries
392 with old libraries starting midway through the installworld process.
395 r363679 has redefined some undefined behavior in regcomp(3); notably,
396 extraneous escapes of most ordinary characters will no longer be
397 accepted. An exp-run has identified all of the problems with this in
398 ports, but other non-ports software may need extra escapes removed to
399 continue to function.
401 Because of this change, installworld may encounter the following error
402 from rtld: Undefined symbol "regcomp@FBSD_1.6" -- It is imperative that
403 you do not halt installworld. Instead, let it run to completion (whether
404 successful or not) and run installworld once more.
407 A new implementation of bc and dc has been imported in r362681. This
408 implementation corrects non-conformant behavior of the previous bc
409 and adds GNU bc compatible options. It offers a number of extensions,
410 is much faster on large values, and has support for message catalogs
411 (a number of languages are already supported, contributions of further
412 languages welcome). The option WITHOUT_GH_BC can be used to build the
413 world with the previous versions of bc and dc.
416 r362639 changed the internal API used between the NFS kernel modules.
417 As such, they all need to be rebuilt from sources.
420 r362158 changed the arguments for VFS_CHECKEXP(). As such, any
421 out of tree file systems need to be modified and rebuilt.
422 Also, any file systems that are modules must be rebuilt.
425 read(2) of a directory fd is now rejected by default. root may
426 re-enable it for system root only on non-ZFS filesystems with the
427 security.bsd.allow_read_dir sysctl(8) MIB if
428 security.bsd.suser_enabled=1.
430 It may be advised to setup aliases for grep to default to `-d skip` if
431 commonly non-recursively grepping a list that includes directories and
432 the potential for the resulting stderr output is not tolerable. Example
433 aliases are now installed, commented out, in /root/.cshrc and
437 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
438 been upgraded to 10.0.1. Please see the 20141231 entry below for
439 information about prerequisites and upgrading, if you are not already
440 using clang 3.5.0 or higher.
443 Support for obsolete compilers has been removed from the build system.
444 Clang 6 and GCC 6.4 are the minimum supported versions.
447 closefrom(2) has been moved under COMPAT12, and replaced in libc with a
448 stub that calls close_range(2). If using a custom kernel configuration,
449 you may want to ensure that the COMPAT_FREEBSD12 option is included, as
450 a slightly older -CURRENT userland and older FreeBSD userlands may not
451 be functional without closefrom(2).
454 Upstream DTS from Linux 5.6 was merged and they now have the SID
455 and THS (Secure ID controller and THermal Sensor) node present.
456 The DTB overlays have now been removed from the tree for the H3/H5 and
457 A64 SoCs and the aw_sid and aw_thermal driver have been updated to
458 deal with upstream DTS. If you are using those overlays you need to
459 remove them from loader.conf and update the DTBs on the FAT partition.
462 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
463 been upgraded to 10.0.0. Please see the 20141231 entry below for
464 information about prerequisites and upgrading, if you are not already
465 using clang 3.5.0 or higher.
468 The amd(8) automount daemon has been removed from the source tree.
469 As of FreeBSD 10.1 autofs(5) is the preferred tool for automounting.
470 amd is still available in the sysutils/am-utils port.
473 Removed brooktree driver (bktr.4) from the tree.
476 The WITH_GPL_DTC option has been removed. The BSD-licenced device tree
477 compiler in usr.bin/dtc is used on all architectures which use dtc, and
478 the GPL dtc is available (if needed) from the sysutils/dtc port.
481 The WITHOUT_LLVM_LIBUNWIND option has been removed. LLVM's libunwind
482 is used by all supported CPU architectures.
485 GCC 4.2.1 has been removed from the tree. The WITH_GCC,
486 WITH_GCC_BOOTSTRAP, and WITH_GNUCXX options are no longer available.
487 Users who wish to build FreeBSD with GCC must use the external toolchain
491 ncurses has been updated to a newer version (6.2-20200215). Given the ABI
492 has changed, users will have to rebuild all the ports that are linked to
496 The size of struct vnet and the magic cookie have changed.
497 Users need to recompile libkvm and all modules using VIMAGE
498 together with their new kernel.
501 Defining the long deprecated NO_CTF, NO_DEBUG_FILES, NO_INSTALLLIB,
502 NO_MAN, NO_PROFILE, and NO_WARNS variables is now an error. Update
503 your Makefiles and scripts to define MK_<var>=no instead as required.
505 One exception to this is that program or library Makefiles should
506 define MAN to empty rather than setting MK_MAN=no.
509 Clang/LLVM is now the default compiler and LLD the default
513 make universe no longer uses GCC 4.2.1 on any architectures.
514 Architectures not supported by in-tree Clang/LLVM require an
515 external toolchain package.
518 GCC 4.2.1 is now not built by default, as part of the GCC 4.2.1
519 retirement plan. Specifically, the GCC, GCC_BOOTSTRAP, and GNUCXX
520 options default to off for all supported CPU architectures. As a
521 short-term transition aid they may be enabled via WITH_* options.
522 GCC 4.2.1 is expected to be removed from the tree on 2020-03-31.
525 Support for armv5 has been disconnected and is being removed. The
526 machine combination MACHINE=arm MACHINE_ARCH=arm is no longer valid.
527 You must now use a MACHINE_ARCH of armv6 or armv7. The default
528 MACHINE_ARCH for MACHINE=arm is now armv7.
531 Clang/LLVM is now the default compiler for all powerpc architectures.
532 LLD is now the default linker for powerpc64. The change for powerpc64
533 also includes a change to the ELFv2 ABI, incompatible with the existing
537 Kernel-loadable random(4) modules are no longer unloadable.
540 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
541 been upgraded to 9.0.1. Please see the 20141231 entry below for
542 information about prerequisites and upgrading, if you are not already
543 using clang 3.5.0 or higher.
546 r355677 has modified the internal interface used between the
547 NFS modules in the kernel. As such, they must all be upgraded
548 simultaneously. I will do a version bump for this.
551 The root certificates of the Mozilla CA Certificate Store have been
552 imported into the base system and can be managed with the certctl(8)
553 utility. If you have installed the security/ca_root_nss port or package
554 with the ETCSYMLINK option (the default), be advised that there may be
555 differences between those included in the port and those included in
556 base due to differences in nss branch used as well as general update
557 frequency. Note also that certctl(8) cannot manage certs in the
558 format used by the security/ca_root_nss port.
561 The amd(8) automount daemon has been disabled by default, and will be
562 removed in the future. As of FreeBSD 10.1 the autofs(5) is available
566 The nctgpio and wbwd drivers have been moved to the superio bus.
567 If you have one of these drivers in a kernel configuration, then
568 you should add device superio to it. If you use one of these drivers
569 as a module and you compile a custom set of modules, then you should
570 add superio to the set.
573 KPIs for network drivers to access interface addresses have changed.
574 Users need to recompile NIC driver modules together with kernel.
577 The net.link.tap.user_open sysctl no longer prevents user opening of
578 already created /dev/tapNN devices. Access is still controlled by
579 node permissions, just like tun devices. The net.link.tap.user_open
580 sysctl is now used only to allow users to perform devfs cloning of
581 tap devices, and the subsequent open may not succeed if the user is not
582 in the appropriate group. This sysctl may be deprecated/removed
583 completely in the future.
586 mips, powerpc, and sparc64 are no longer built as part of
587 universe / tinderbox unless MAKE_OBSOLETE_GCC is defined. If
588 not defined, mips, powerpc, and sparc64 builds will look for
589 the xtoolchain binaries and if installed use them for universe
590 builds. As llvm 9.0 becomes vetted for these architectures, they
591 will be removed from the list.
594 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
595 been upgraded to 9.0.0. Please see the 20141231 entry below for
596 information about prerequisites and upgrading, if you are not already
597 using clang 3.5.0 or higher.
600 The hpt27xx, hptmv, hptnr, and hptrr drivers have been removed from
601 GENERIC. They are available as modules and can be loaded by adding
602 to /boot/loader.conf hpt27xx_load="YES", hptmv_load="YES",
603 hptnr_load="YES", or hptrr_load="YES", respectively.
606 ntpd no longer by default locks its pages in memory, allowing them
607 to be paged out by the kernel. Use rlimit memlock to restore
608 historic BSD behaviour. For example, add "rlimit memlock 32"
609 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
612 Several of ping6's options have been renamed for better consistency
613 with ping. If you use any of -ARWXaghmrtwx, you must update your
614 scripts. See ping6(8) for details.
617 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
618 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
619 been removed from mount_fusefs(8). You can safely remove them from
620 your scripts, because they had no effect.
622 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
623 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
624 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
625 sysctls have been removed. If you felt the need to set any of them to
626 a non-default value, please tell asomers@FreeBSD.org why.
629 Default permissions on the /var/account/acct file (and copies of it
630 rotated by periodic daily scripts) are changed from 0644 to 0640
631 because the file contains sensitive information that should not be
632 world-readable. If the /var/account directory must be created by
633 rc.d/accounting, the mode used is now 0750. Admins who use the
634 accounting feature are encouraged to change the mode of an existing
635 /var/account directory to 0750 or 0700.
638 Entropy collection and the /dev/random device are no longer optional
639 components. The "device random" option has been removed.
640 Implementations of distilling algorithms can still be made loadable
641 with "options RANDOM_LOADABLE" (e.g., random_fortuna.ko).
644 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
645 been upgraded to 8.0.1. Please see the 20141231 entry below for
646 information about prerequisites and upgrading, if you are not already
647 using clang 3.5.0 or higher.
650 A fix was applied to i386 kernel modules to avoid panics with
651 dpcpu or vnet. Users need to recompile i386 kernel modules
652 having pcpu or vnet sections or they will refuse to load.
655 User-wired pages now have their own counter,
656 vm.stats.vm.v_user_wire_count. The vm.max_wired sysctl was renamed
657 to vm.max_user_wired and changed from an unsigned int to an unsigned
658 long. bhyve VMs wired with the -S are now subject to the user
659 wiring limit; the vm.max_user_wired sysctl may need to be tuned to
660 avoid running into the limit.
663 The IPSEC option has been removed from GENERIC. Users requiring
664 ipsec(4) must now load the ipsec(4) kernel module.
667 The tap(4) driver has been folded into tun(4), and the module has been
668 renamed to tuntap. You should update any kld_list="if_tap" or
669 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
670 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
671 module instead, and "device tap" or "device tun" entries in kernel
672 config files to select the tuntap device instead.
675 The following knobs have been added related to tradeoffs between
676 safe use of the random device and availability in the absence of
679 kern.random.initial_seeding.bypass_before_seeding: tunable; set
680 non-zero to bypass the random device prior to seeding, or zero to
681 block random requests until the random device is initially seeded.
682 For now, set to 1 (unsafe) by default to restore pre-r346250 boot
683 availability properties.
685 kern.random.initial_seeding.read_random_bypassed_before_seeding:
686 read-only diagnostic sysctl that is set when bypass is enabled and
687 read_random(9) is bypassed, to enable programmatic handling of this
688 initial condition, if desired.
690 kern.random.initial_seeding.arc4random_bypassed_before_seeding:
691 Similar to the above, but for arc4random(9) initial seeding.
693 kern.random.initial_seeding.disable_bypass_warnings: tunable; set
694 non-zero to disable warnings in dmesg when the same conditions are
695 met as for the diagnostic sysctls above. Defaults to zero, i.e.,
696 produce warnings in dmesg when the conditions are met.
699 The loadable random module KPI has changed; the random_infra_init()
700 routine now requires a 3rd function pointer for a bool (*)(void)
701 method that returns true if the random device is seeded (and
702 therefore unblocked).
705 r345895 reverts r320698. This implies that an nfsuserd(8) daemon
706 built from head sources between r320757 (July 6, 2017) and
707 r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
708 is added to the command line.
709 nfsuserd daemons built from head sources that are post-r338192 are
710 not affected and should continue to work.
713 The fuse(4) module has been renamed to fusefs(4) for consistency with
714 other filesystems. You should update any kld_load="fuse" entries in
715 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
716 "options FUSE" entries in kernel config files.
719 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
720 8.0.0. Please see the 20141231 entry below for information about
721 prerequisites and upgrading, if you are not already using clang 3.5.0
725 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
726 compiled into your custom kernel, add 'device xz' statement to the
730 drm and drm2 have been removed from the tree. Please see
731 https://wiki.freebsd.org/Graphics for the latest information on
732 migrating to the drm ports.
735 Iflib is no longer unconditionally compiled into the kernel. Drivers
736 using iflib and statically compiled into the kernel, now require
737 the 'device iflib' config option. For the same drivers loaded as
738 modules on kernels not having 'device iflib', the iflib.ko module
739 is loaded automatically.
742 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
743 options no longer exist since r343219 and r343427 respectively;
744 nothing uses them, so they should be just removed from custom
748 r342635 changes the way efibootmgr(8) works by requiring users to add
749 the -b (bootnum) parameter for commands where the bootnum was previously
750 specified with each option. For example 'efibootmgr -B 0001' is now
751 'efibootmgr -B -b 0001'.
754 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
755 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
756 servers that have vfs.nfsd.nfs_privport set will only allow mounts
757 from clients using a reserved port. Since both the FreeBSD and Linux
758 NFSv4 clients use reserved ports by default, this should not affect
762 The XLP config has been removed. We can't support 64-bit atomics in this
763 kernel because it is running in 32-bit mode. XLP users must transition
764 to running a 64-bit kernel (XLP64 or XLPN32).
766 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
767 the preferred emulator today and we don't need two different ones.
769 The old sibyte / swarm / Broadcom BCM1250 support has been
770 removed from the mips port.
773 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
774 7.0.1. Please see the 20141231 entry below for information about
775 prerequisites and upgrading, if you are not already using clang 3.5.0
779 Remove the timed and netdate programs from the base tree. Setting
780 the time with these daemons has been obsolete for over a decade.
783 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
784 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
785 it produces broken binaries when ifuncs are in use. Users needing
786 GNU ld should install the binutils port or package.
789 The BSD crtbegin and crtend code has been enabled by default. It has
790 had extensive testing on amd64, arm64, and i386. It can be disabled
791 by building a world with -DWITHOUT_BSD_CRTBEGIN.
794 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
795 has been converted to a port (misc/ctm) and will be removed from
796 FreeBSD-13. It is available as a package (ctm) for all supported
800 The default newsyslog.conf(5) file has been changed to only include
801 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
802 the filenames end in '.conf' and do not begin with a '.'.
804 You should check the configuration files in these two directories match
805 this naming convention. You can verify which configuration files are
806 being included using the command:
810 Ports for the DRM modules have been simplified. Now, amd64 users should
811 just install the drm-kmod port. All others should install
814 Graphics hardware that's newer than about 2010 usually works with
815 drm-kmod. For hardware older than 2013, however, some users will need
816 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
817 than 2008 usually only works in drm-legacy-kmod. The graphics team can
818 only commit to hardware made since 2013 due to the complexity of the
819 market and difficulty to test all the older cards effectively. If you
820 have hardware supported by drm-kmod, you are strongly encouraged to use
821 that as you will get better support.
823 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
824 elsewhere, the drm and drm2 modules will be eliminated from the src base
825 soon (with a limited exception for arm). Please update to the package
826 asap and report any issues to x11@freebsd.org.
828 Generally, anybody using the drm*-kmod packages should add
829 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
830 cross-threading surprises, especially with automatic driver
831 loading from X11 startup. These will become the defaults in 13-current
835 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
836 custom kernel and module loading configuration files must be updated
837 accordingly. Moreover, interfaces previous presented as ixlvN to the
838 system are now exposed as iavfN and network configuration files must
839 be adjusted as necessary.
842 OpenSSL has been updated to version 1.1.1. This update included
843 additional various API changes throughout the base system. It is
844 important to rebuild third-party software after upgrading. The value
845 of __FreeBSD_version has been bumped accordingly.
848 The legacy DRM modules and drivers have now been added to the loader's
849 module blacklist, in favor of loading them with kld_list in rc.conf(5).
850 The module blacklist may be overridden with the loader.conf(5)
851 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
855 The cam(4) based nda(4) driver will be used over nvd(4) by default on
856 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
857 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
858 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
862 Reproducible build mode is now on by default, in preparation for
863 FreeBSD 12.0. This eliminates build metadata such as the user,
864 host, and time from the kernel (and uname), unless the working tree
865 corresponds to a modified checkout from a version control system.
866 The previous behavior can be obtained by setting the /etc/src.conf
867 knob WITHOUT_REPRODUCIBLE_BUILD.
870 The Yarrow CSPRNG has been removed from the kernel as it has not been
871 supported by its designers since at least 2003. Fortuna has been the
872 default since FreeBSD-11.
875 devctl freeze/thaw have gone into the tree, the rc scripts have been
876 updated to use them and devmatch has been changed. You should update
877 kernel, userland and rc scripts all at the same time.
880 The default interpreter has been switched from 4th to Lua.
881 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
882 interpreter. If you have custom FORTH code you will need to set
883 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
884 src.conf for the build. This will create default hard links between
885 loader and loader_4th instead of loader and loader_lua, the new default.
886 If you are using UEFI it will create the proper hard link to loader.efi.
888 bhyve uses userboot.so. It remains 4th-only until some issues are solved
889 regarding coexisting with multiple versions of FreeBSD are resolved.
892 ls(1) now respects the COLORTERM environment variable used in other
893 systems and software to indicate that a colored terminal is both
894 supported and desired. If ls(1) is suddenly emitting colors, they may
895 be disabled again by either removing the unwanted COLORTERM from your
896 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
897 may not be observed in a future release.
900 The default pager for most commands has been changed to "less". To
901 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
905 The jedec_ts(4) driver has been removed. A superset of its functionality
906 is available in the jedec_dimm(4) driver, and the manpage for that
907 driver includes migration instructions. If you have "device jedec_ts"
908 in your kernel configuration file, it must be removed.
911 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
912 This should have no effect if the kernel is booted via BIOS/legacy boot.
913 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
914 has a buggy firmware that prevents a successful boot due to use of
918 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
919 support has been removed from the tree. These ports were
920 obsolete and/or known to be broken for many years.
923 loader.efi has been augmented to participate more fully in the
924 UEFI boot manager protocol. loader.efi will now look at the
925 BootXXXX environment variable to determine if a specific kernel
926 or root partition was specified. XXXX is derived from BootCurrent.
927 efibootmgr(8) manages these standard UEFI variables.
930 zfsloader's functionality has now been folded into loader.
931 zfsloader is no longer necessary once you've updated your
932 boot blocks. For a transition period, we will install a
933 hardlink for zfsloader to loader to allow a smooth transition
934 until the boot blocks can be updated (hard link because old
935 zfs boot blocks don't understand symlinks).
938 ARM64 now have efifb support, if you want to have serial console
939 on your arm64 board when an screen is connected and the bootloader
940 setup a frame buffer for us to use, just add :
944 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
945 an screen connected as the firmware will setup a frame buffer are that
946 u-boot will expose as an EFI frame buffer.
949 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
950 or take steps to update /etc/passwd before doing installworld on
951 existing systems. Do not skip the "mergemaster -Fp" step before
952 installworld, as described in the update procedures near the bottom
953 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
954 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
955 the ntp config file contain options that change file/dir locations.
956 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
957 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
958 taking steps to ensure that all required files/dirs are accessible
962 Big endian arm support has been removed.
965 The static environment setup in kernel configs is no longer mutually
966 exclusive with the loader(8) environment by default. In order to
967 restore the previous default behavior of disabling the loader(8)
968 environment if a static environment is present, you must specify
969 loader_env.disabled=1 in the static environment.
972 The ABI of syscalls used by management tools like sockstat and
973 netstat has been broken to allow 32-bit binaries to work on
974 64-bit kernels without modification. These programs will need
975 to match the kernel in order to function. External programs may
976 require minor modifications to accommodate a change of type in
977 structures from pointers to 64-bit virtual addresses.
980 On i386 and amd64 atomics are now inlined. Out of tree modules using
981 atomics will need to be rebuilt.
984 The '%I' format in the kern.corefile sysctl limits the number of
985 core files that a process can generate to the number stored in the
986 debug.ncores sysctl. The '%I' format is replaced by the single digit
987 index. Previously, if all indexes were taken the kernel would overwrite
988 only a core file with the highest index in a filename.
989 Currently the system will create a new core file if there is a free
990 index or if all slots are taken it will overwrite the oldest one.
993 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
994 6.0.1. Please see the 20141231 entry below for information about
995 prerequisites and upgrading, if you are not already using clang 3.5.0
999 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
1000 needed to be changed to work with it. This change was made with r335763
1001 and requires a mergemaster / etcupdate / etc to update the installed
1005 r334930 changed the interface between the NFS modules, so they all
1006 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
1009 As of r334391 lld is the default amd64 system linker; it is installed
1010 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
1014 The kernel / userland interface for devinfo changed, so you'll
1015 need a new kernel and userland as a pair for it to work (rebuilding
1016 lib/libdevinfo is all that's required). devinfo and devmatch will
1017 not work, but everything else will when there's a mismatch.
1020 The on-disk format for hwpmc callchain records has changed to include
1021 threadid corresponding to a given record. This changes the field offsets
1022 and thus requires that libpmcstat be rebuilt before using a kernel
1026 The vxge(4) driver has been removed. This driver was introduced into
1027 HEAD one week before the Exar left the Ethernet market and is not
1028 known to be used. If you have device vxge in your kernel config file
1032 The amd64 kernel now requires a ld that supports ifunc to produce a
1033 working kernel, either lld or a newer binutils. lld is built by default
1034 on amd64, and the 'buildkernel' target uses it automatically. However,
1035 it is not the default linker, so building the kernel the traditional
1036 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
1037 binutils port/package). lld will soon be default, and this requirement
1040 NOTE: As of r334391 lld is the default system linker on amd64, and no
1041 workaround is necessary.
1044 The nxge(4) driver has been removed. This driver was for PCI-X 10g
1045 cards made by s2io/Neterion. The company was acquired by Exar and
1046 no longer sells or supports Ethernet products. If you have device
1047 nxge in your kernel config file it must be removed.
1050 The tz database (tzdb) has been updated to 2018e. This version more
1051 correctly models time stamps in time zones with negative DST such as
1052 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
1053 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
1054 time zone abbreviations and the tm_isdst flag.
1057 The ixgb(4) driver has been removed. This driver was for an early and
1058 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
1059 quickly shifted to the long lived ixgbe family. If you have device
1060 ixgb in your kernel config file it must be removed.
1063 The lmc(4) driver has been removed. This was a WAN interface
1064 card that was already reportedly rare in 2003, and had an ambiguous
1065 license. If you have device lmc in your kernel config file it must
1069 Support for Arcnet networks has been removed. If you have device
1070 arcnet or device cm in your kernel config file they must be
1074 Support for FDDI networks has been removed. If you have device
1075 fddi or device fpa in your kernel config file they must be
1079 In addition to supporting RFC 3164 formatted messages, the
1080 syslogd(8) service is now capable of parsing RFC 5424 formatted
1081 log messages. The main benefit of using RFC 5424 is that clients
1082 may now send log messages with timestamps containing year numbers,
1083 microseconds and time zone offsets.
1085 Similarly, the syslog(3) C library function has been altered to
1086 send RFC 5424 formatted messages to the local system logging
1087 daemon. On systems using syslogd(8), this change should have no
1088 negative impact, as long as syslogd(8) and the C library are
1089 updated at the same time. On systems using a different system
1090 logging daemon, it may be necessary to make configuration
1091 adjustments, depending on the software used.
1093 When using syslog-ng, add the 'syslog-protocol' flag to local
1094 input sources to enable parsing of RFC 5424 formatted messages:
1097 unix-dgram("/var/run/log" flags(syslog-protocol));
1100 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
1101 of the 'imuxsock' module to let messages be processed by the
1102 regular RFC 3164/5424 parsing pipeline:
1104 module(load="imuxsock" SysSock.UseSpecialParser="off")
1106 Do note that these changes only affect communication between local
1107 applications and syslogd(8). The format that syslogd(8) uses to
1108 store messages on disk or forward messages to other systems
1109 remains unchanged. syslogd(8) still uses RFC 3164 for these
1110 purposes. Options to customize this behaviour will be added in the
1111 future. Utilities that process log files stored in /var/log are
1112 thus expected to continue to function as before.
1114 __FreeBSD_version has been incremented to 1200061 to denote this
1118 Support for token ring networks has been removed. If you
1119 have "device token" in your kernel config you should remove
1120 it. No device drivers supported token ring.
1123 makefs was modified to be able to tag ISO9660 El Torito boot catalog
1124 entries as EFI instead of overloading the i386 tag as done previously.
1125 The amd64 mkisoimages.sh script used to build amd64 ISO images for
1126 release was updated to use this. This may mean that makefs must be
1127 updated before "make cdrom" can be run in the release directory. This
1128 should be as simple as:
1130 $ cd $SRCDIR/usr.sbin/makefs
1131 $ make depend all install
1134 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
1135 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
1136 Co-existence for the transition period will come shortly. Booting is a
1137 complex environment and test coverage for Lua-enabled loaders has been
1138 thin, so it would be prudent to assume it might not work and make
1139 provisions for backup boot methods.
1142 devmatch functionality has been turned on in devd. It will automatically
1143 load drivers for unattached devices. This may cause unexpected drivers
1144 to be loaded. Please report any problems to current@ and
1148 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
1149 6.0.0. Please see the 20141231 entry below for information about
1150 prerequisites and upgrading, if you are not already using clang 3.5.0
1154 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
1155 This means it is used to link the kernel and userland libraries and
1156 executables, but is not yet installed as /usr/bin/ld by default.
1158 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
1159 WITHOUT_LLD_BOOTSTRAP=yes
1162 On i386, pmtimer has been removed. Its functionality has been folded
1163 into apm. It was a no-op on ACPI in current for a while now (but was
1164 still needed on i386 in FreeBSD 11 and earlier). Users may need to
1165 remove it from kernel config files.
1168 The use of RSS hash from the network card aka flowid has been
1169 disabled by default for lagg(4) as it's currently incompatible with
1170 the lacp and loadbalance protocols.
1172 This can be re-enabled by setting the following in loader.conf:
1173 net.link.lagg.default_use_flowid="1"
1176 The SW_WATCHDOG option is no longer necessary to enable the
1177 hardclock-based software watchdog if no hardware watchdog is
1178 configured. As before, SW_WATCHDOG will cause the software
1179 watchdog to be enabled even if a hardware watchdog is configured.
1182 r326887 fixes the issue described in the 20171214 UPDATING entry.
1183 r326888 flips the switch back to building GELI support always.
1186 r362593 broke ZFS + GELI support for reasons unknown. However,
1187 it also broke ZFS support generally, so GELI has been turned off
1188 by default as the lesser evil in r326857. If you boot off ZFS and/or
1189 GELI, it might not be a good time to update.
1192 PowerPC users must update loader(8) by rebuilding world before
1193 installing a new kernel, as the protocol connecting them has
1194 changed. Without the update, loader metadata will not be passed
1195 successfully to the kernel and users will have to enter their
1196 root partition at the kernel mountroot prompt to continue booting.
1197 Newer versions of loader can boot old kernels without issue.
1200 The LOADER_FIREWIRE_SUPPORT build variable has been renamed to
1201 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
1202 to WITH/OUT_LOADER_GELI.
1205 The naive and non-compliant support of posix_fallocate(2) in ZFS
1206 has been removed as of r325320. The system call now returns EINVAL
1207 when used on a ZFS file. Although the new behavior complies with the
1208 standard, some consumers are not prepared to cope with it.
1209 One known victim is lld prior to r325420.
1212 Building in a FreeBSD src checkout will automatically create object
1213 directories now rather than store files in the current directory if
1214 'make obj' was not ran. Calling 'make obj' is no longer necessary.
1215 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
1216 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
1220 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
1221 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
1222 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
1223 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
1224 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
1225 The UNIFIED_OBJDIR option is a transitional feature that will be
1226 removed for 12.0 release; please migrate to the new format for any
1227 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
1228 than hardcoding paths.
1231 The native-xtools target no longer installs the files by default to the
1232 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
1233 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
1236 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
1237 options are changing from controlling the build if defined / undefined
1238 to controlling the build with explicit 'yes' or 'no' values. They will
1239 shift to WITH/WITHOUT options to match other options in the system.
1242 libstand has turned into a private library for sys/boot use only.
1243 It is no longer supported as a public interface outside of sys/boot.
1246 The arm port has split armv6 into armv6 and armv7. armv7 is now
1247 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
1248 and are running a kernel from before r324363, you will need to add
1249 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
1252 When building multiple kernels using KERNCONF, non-existent KERNCONF
1253 files will produce an error and buildkernel will fail. Previously
1254 missing KERNCONF files silently failed giving no indication as to
1255 why, only to subsequently discover during installkernel that the
1256 desired kernel was never built in the first place.
1259 The default serial number format for CTL LUNs has changed. This will
1260 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
1261 or iSCSI clients care about their LUNs' serial numbers. Users who
1262 require serial number stability should hardcode serial numbers in
1266 For 32-bit arm compiled for hard-float support, soft-floating point
1267 binaries now always get their shared libraries from
1268 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
1269 /usr/libsoft also existed). Only users with a hard-float ld.so, but
1270 soft-float everything else should be affected.
1273 The geli password typed at boot is now hidden. To restore the previous
1274 behavior, see geli(8) for configuration options.
1277 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
1278 sysctl values. Minor nit, but requires a rebuild of both world/kernel
1282 "make check" behavior (made in ^/head@r295380) has been changed to
1283 execute from a limited sandbox, as opposed to executing from
1287 - The "beforecheck" and "aftercheck" targets are now specified.
1288 - ${CHECKDIR} (added in commit noted above) has been removed.
1289 - Legacy behavior can be enabled by setting
1290 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
1292 If the limited sandbox mode is enabled, "make check" will execute
1293 "make distribution", then install, execute the tests, and clean up the
1294 sandbox if successful.
1296 The "make distribution" and "make install" targets are typically run as
1297 root to set appropriate permissions and ownership at installation time.
1298 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
1299 environment if executing "make check" with limited sandbox mode using
1300 an unprivileged user.
1303 Since the switch to GPT disk labels, fsck for UFS/FFS has been
1304 unable to automatically find alternate superblocks. As of r322297,
1305 the information needed to find alternate superblocks has been
1306 moved to the end of the area reserved for the boot block.
1307 Filesystems created with a newfs of this vintage or later
1308 will create the recovery information. If you have a filesystem
1309 created prior to this change and wish to have a recovery block
1310 created for your filesystem, you can do so by running fsck in
1311 foreground mode (i.e., do not use the -p or -y options). As it
1312 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
1313 to which you should answer yes.
1316 As of r321665, an NFSv4 server configuration that services
1317 Kerberos mounts or clients that do not support the uid/gid in
1318 owner/owner_group string capability, must explicitly enable
1319 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
1320 machine's /etc/rc.conf file.
1323 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
1324 Please see the 20141231 entry below for information about prerequisites
1325 and upgrading, if you are not already using clang 3.5.0 or higher.
1328 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
1329 r-commands (rlogin, rsh, etc.) to be built with the base system.
1332 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
1333 a very major ABI incompatible change, so users of FreeBSD/powerpc must
1334 be careful when performing source upgrades. It is best to run
1335 'make installworld' from an alternate root system, either a live
1336 CD/memory stick, or a temporary root partition. Additionally, all ports
1337 must be recompiled. powerpc64 is largely unaffected, except in the case
1338 of 32-bit compatibility. All 32-bit binaries will be affected.
1341 Forward compatibility for the "ino64" project have been committed. This
1342 will allow most new binaries to run on older kernels in a limited
1343 fashion. This prevents many of the common foot-shooting actions in the
1344 upgrade as well as the limited ability to roll back the kernel across
1345 the ino64 upgrade. Complicated use cases may not work properly, though
1346 enough simpler ones work to allow recovery in most situations.
1349 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
1350 if you require the GPL compiler.
1353 The internal ABI used for communication between the NFS kernel modules
1354 was changed by r320085, so __FreeBSD_version was bumped to
1355 ensure all the NFS related modules are updated together.
1358 The ABI of struct event was changed by extending the data
1359 member to 64bit and adding ext fields. For upgrade, same
1360 precautions as for the entry 20170523 "ino64" must be
1364 The GNU roff toolchain has been removed from base. To render manpages
1365 which are not supported by mandoc(1), man(1) can fallback on GNU roff
1366 from ports (and recommends to install it).
1367 To render roff(7) documents, consider using GNU roff from ports or the
1368 heirloom doctools roff toolchain from ports via pkg install groff or
1369 via pkg install heirloom-doctools.
1372 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
1373 smaller runtime footprint builds. This is useful for embedded systems
1374 which only require one chipset support.
1376 If you load it as a module, make sure this is in /boot/loader.conf:
1380 This will load the HAL, all chip/RF backends and if_ath_pci.
1381 If you have if_ath_pci in /boot/loader.conf, ensure it is after
1382 if_ath or it will not load any HAL chipset support.
1384 If you want to selectively load things (eg on cheaper ARM/MIPS
1385 platforms where RAM is at a premium) you should:
1388 * load the chip modules in question
1389 * load ath_rate, ath_dfs
1391 * load if_ath_pci and/or if_ath_ahb depending upon your particular
1392 bus bind type - this is where probe/attach is done.
1394 For further comments/feedback, poke adrian@ .
1397 The "ino64" 64-bit inode project has been committed, which extends
1398 a number of types to 64 bits. Upgrading in place requires care and
1399 adherence to the documented upgrade procedure.
1401 If using a custom kernel configuration ensure that the
1402 COMPAT_FREEBSD11 option is included (as during the upgrade the
1403 system will be running the ino64 kernel with the existing world).
1405 For the safest in-place upgrade begin by removing previous build
1406 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full
1407 procedure documented below under the heading "To rebuild everything and
1408 install it on the current system." Specifically, a reboot is required
1409 after installing the new kernel before installing world. While an
1410 installworld normally works by accident from multiuser after rebooting
1411 the proper kernel, there are many cases where this will fail across this
1412 upgrade and installworld from single user is required.
1415 The NATM framework including the en(4), fatm(4), hatm(4), and
1416 patm(4) devices has been removed. Consumers should plan a
1417 migration before the end-of-life date for FreeBSD 11.
1420 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
1421 diff has not been implemented, if those are needed a newer version of
1422 GNU diff is available via the diffutils package under the gdiff name.
1425 As of r316810 for ipfilter, keep frags is no longer assumed when
1426 keep state is specified in a rule. r316810 aligns ipfilter with
1427 documentation in man pages separating keep frags from keep state.
1428 This allows keep state to be specified without forcing keep frags
1429 and allows keep frags to be specified independently of keep state.
1430 To maintain previous behaviour, also specify keep frags with
1431 keep state (as documented in ipf.conf.5).
1434 arm64 builds now use the base system LLD 4.0.0 linker by default,
1435 instead of requiring that the aarch64-binutils port or package be
1436 installed. To continue using aarch64-binutils, set
1437 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
1440 The UDP optimization in entry 20160818 that added the sysctl
1441 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
1442 packets will no longer be treated as L3 broadcast packets.
1445 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
1446 use any explicitly assigned loopback address available in the jail
1447 instead of using the first assigned address of the jail.
1450 The ctl.ko module no longer implements the iSCSI target frontend:
1451 cfiscsi.ko does instead.
1453 If building cfiscsi.ko as a kernel module, the module can be loaded
1454 via one of the following methods:
1455 - `cfiscsi_load="YES"` in loader.conf(5).
1456 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
1457 - ctladm(8)/ctld(8), when compiled with iSCSI support
1458 (`WITH_ISCSI=yes` in src.conf(5))
1460 Please see cfiscsi(4) for more details.
1463 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
1464 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
1465 same source (previously, the dependency of mmcsd.ko on mmc.ko was
1466 missing, but mmcsd.ko now will refuse to load if it is incompatible
1470 The syntax of ipfw(8) named states was changed to avoid ambiguity.
1471 If you have used named states in the firewall rules, you need to modify
1472 them after installworld and before rebooting. Now named states must
1473 be prefixed with colon.
1476 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
1477 removed as the userland we provide cannot use them. The KMS version
1478 (sys/dev/drm2) supports the same hardware.
1481 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
1482 Please see the 20141231 entry below for information about prerequisites
1483 and upgrading, if you are not already using clang 3.5.0 or higher.
1486 The code that provides support for ZFS .zfs/ directory functionality
1487 has been reimplemented. It's not possible now to create a snapshot
1488 by mkdir under .zfs/snapshot/. That should be the only user visible
1492 EISA bus support has been removed. The WITH_EISA option is no longer
1496 MCA bus support has been removed.
1499 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
1500 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
1503 The EM_MULTIQUEUE kernel configuration option is deprecated now that
1504 the em(4) driver conforms to iflib specifications.
1507 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
1508 IFLIB. If you have a custom kernel configuration that excludes em(4)
1509 but you use igb(4), you need to re-add em(4) to your custom
1513 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
1514 Please see the 20141231 entry below for information about prerequisites
1515 and upgrading, if you are not already using clang 3.5.0 or higher.
1518 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
1519 Please see the 20141231 entry below for information about prerequisites
1520 and upgrading, if you are not already using clang 3.5.0 or higher.
1523 The layout of the pmap structure has changed for powerpc to put the pmap
1524 statistics at the front for all CPU variations. libkvm(3) and all tools
1525 that link against it need to be recompiled.
1528 isl(4) and cyapa(4) drivers now require a new driver,
1529 chromebook_platform(4), to work properly on Chromebook-class hardware.
1530 On other types of hardware the drivers may need to be configured using
1531 device hints. Please see the corresponding manual pages for details.
1534 The urtwn(4) driver was merged into rtwn(4) and now consists of
1535 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
1537 Also, firmware for RTL8188CE was renamed due to possible name
1538 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
1541 GNU rcs has been removed from base. It is available as packages:
1542 - rcs: Latest GPLv3 GNU rcs version.
1543 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
1547 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
1548 modules now requires that the kernel configuration contain the
1549 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
1552 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
1553 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
1556 Relocatable object files with the extension of .So have been renamed
1557 to use an extension of .pico instead. The purpose of this change is
1558 to avoid a name clash with shared libraries on case-insensitive file
1559 systems. On those file systems, foo.So is the same file as foo.so.
1562 GNU rcs has been turned off by default. It can (temporarily) be built
1563 again by adding WITH_RCS knob in src.conf.
1564 Otherwise, GNU rcs is available from packages:
1565 - rcs: Latest GPLv3 GNU rcs version.
1566 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
1569 The backup_uses_rcs functionality has been removed from rc.subr.
1572 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
1573 two separate components, QUEUE_MACRO_DEBUG_TRACE and
1574 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
1575 QUEUE_MACRO_DEBUG behavior.
1578 r304787 changed some ioctl interfaces between the iSCSI userspace
1579 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1580 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1584 The UDP receive code has been updated to only treat incoming UDP
1585 packets that were addressed to an L2 broadcast address as L3
1586 broadcast packets. It is not expected that this will affect any
1587 standards-conforming UDP application. The new behaviour can be
1588 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1592 Remove the openbsd_poll system call.
1593 __FreeBSD_version has been bumped because of this.
1596 The stable/11 branch has been created from head@r302406.
1599 The libc stub for the pipe(2) system call has been replaced with
1600 a wrapper that calls the pipe2(2) system call and the pipe(2)
1601 system call is now only implemented by the kernels that include
1602 "options COMPAT_FREEBSD10" in their config file (this is the
1603 default). Users should ensure that this option is enabled in
1604 their kernel or upgrade userspace to r302092 before upgrading their
1608 CAM now strips the leading spaces from each SCSI disk's serial number.
1609 This will affect users who create UFS filesystems on SCSI disks using
1610 those disk's diskid device nodes. For example, if /etc/fstab
1611 previously contained a line like
1612 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
1613 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
1614 transforms like gmirror may also be affected. ZFS users should
1618 The bitstring(3) API has been updated with new functionality and
1619 improved performance. But it is binary-incompatible with the old API.
1620 Objects built with the new headers may not be linked against objects
1621 built with the old headers.
1624 The brk and sbrk functions have been removed from libc on arm64.
1625 Binutils from ports has been updated to not link to these
1626 functions and should be updated to the latest version before
1627 installing a new libc.
1630 The armv6 port now defaults to hard float ABI. Limited support
1631 for running both hardfloat and soft float on the same system
1632 is available using the libraries installed with -DWITH_LIBSOFT.
1633 This has only been tested as an upgrade path for installworld
1634 and packages may fail or need manual intervention to run. New
1635 packages will be needed.
1637 To update an existing self-hosted armv6hf system, you must add
1638 TARGET_ARCH=armv6 on the make command line for both the build
1639 and the install steps.
1642 Kernel modules compiled outside of a kernel build now default to
1643 installing to /boot/modules instead of /boot/kernel. Many kernel
1644 modules built this way (such as those in ports) already overrode
1645 KMODDIR explicitly to install into /boot/modules. However,
1646 manually building and installing a module from /sys/modules will
1647 now install to /boot/modules instead of /boot/kernel.
1650 The CAM I/O scheduler has been committed to the kernel. There should be
1651 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1652 list of known rogues that claim support for this but actually corrupt
1653 data is believed to be complete, be on the lookout for data
1654 corruption. The known rogue list is believed to be complete:
1656 o Crucial MX100, M550 drives with MU01 firmware.
1657 o Micron M510 and M550 drives with MU01 firmware.
1658 o Micron M500 prior to MU07 firmware
1659 o Samsung 830, 840, and 850 all firmwares
1660 o FCCT M500 all firmwares
1662 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1663 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1664 updated firmware. Black listed drives will work correctly because these
1665 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1666 this list is the same as found in Linux, it's believed there are no
1667 other rogues in the market place. All other models from the above
1670 To be safe, if you are at all concerned, you can quirk each of your
1671 drives to prevent NCQ from being sent by setting:
1672 kern.cam.ada.X.quirks="0x2"
1673 in loader.conf. If the drive requires the 4k sector quirk, set the
1674 quirks entry to 0x3.
1677 The FAST_DEPEND build option has been removed and its functionality is
1678 now the one true way. The old mkdep(1) style of 'make depend' has
1679 been removed. See 20160311 for further details.
1682 Resource range types have grown from unsigned long to uintmax_t. All
1683 drivers, and anything using libdevinfo, need to be recompiled.
1686 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1687 builds. It no longer runs mkdep(1) during 'make depend', and the
1688 'make depend' stage can safely be skipped now as it is auto ran
1689 when building 'make all' and will generate all SRCS and DPSRCS before
1690 building anything else. Dependencies are gathered at compile time with
1691 -MF flags kept in separate .depend files per object file. Users should
1692 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1693 stale .depend files.
1696 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1697 kernel modules. Therefore, if you load any kernel modules at boot time,
1698 please install the boot loaders after you install the kernel, but before
1702 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1703 make installkernel KERNCONF=YOUR_KERNEL_HERE
1704 make -C sys/boot install
1705 <reboot in single user>
1707 Then follow the usual steps, described in the General Notes section,
1711 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1712 see the 20141231 entry below for information about prerequisites and
1713 upgrading, if you are not already using clang 3.5.0 or higher.
1716 The AIO subsystem is now a standard part of the kernel. The
1717 VFS_AIO kernel option and aio.ko kernel module have been removed.
1718 Due to stability concerns, asynchronous I/O requests are only
1719 permitted on sockets and raw disks by default. To enable
1720 asynchronous I/O requests on all file types, set the
1721 vfs.aio.enable_unsafe sysctl to a non-zero value.
1724 The ELF object manipulation tool objcopy is now provided by the
1725 ELF Tool Chain project rather than by GNU binutils. It should be a
1726 drop-in replacement, with the addition of arm64 support. The
1727 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1728 to obtain the GNU version if necessary.
1731 Building ZFS pools on top of zvols is prohibited by default. That
1732 feature has never worked safely; it's always been prone to deadlocks.
1733 Using a zvol as the backing store for a VM guest's virtual disk will
1734 still work, even if the guest is using ZFS. Legacy behavior can be
1735 restored by setting vfs.zfs.vol.recursive=1.
1738 The NONE and HPN patches has been removed from OpenSSH. They are
1739 still available in the security/openssh-portable port.
1742 With the addition of ypldap(8), a new _ypldap user is now required
1743 during installworld. "mergemaster -p" can be used to add the user
1744 prior to installworld, as documented in the handbook.
1747 The tftp loader (pxeboot) now uses the option root-path directive. As a
1748 consequence it no longer looks for a pxeboot.4th file on the tftp
1749 server. Instead it uses the regular /boot infrastructure as with the
1753 The code to start recording plug and play data into the modules has
1754 been committed. While the old tools will properly build a new kernel,
1755 a number of warnings about "unknown metadata record 4" will be produced
1756 for an older kldxref. To avoid such warnings, make sure to rebuild
1757 the kernel toolchain (or world). Make sure that you have r292078 or
1758 later when trying to build 292077 or later before rebuilding.
1761 Debug data files are now built by default with 'make buildworld' and
1762 installed with 'make installworld'. This facilitates debugging but
1763 requires more disk space both during the build and for the installed
1764 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1768 r291527 changed the internal interface between the nfsd.ko and
1769 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1770 __FreeBSD_version has been bumped because of this.
1773 Add support for unicode collation strings leads to a change of
1774 order of files listed by ls(1) for example. To get back to the old
1775 behaviour, set LC_COLLATE environment variable to "C".
1777 Databases administrators will need to reindex their databases given
1778 collation results will be different.
1780 Due to a bug in install(1) it is recommended to remove the ancient
1781 locales before running make installworld.
1783 rm -rf /usr/share/locale/*
1786 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1787 libcrypto.so.7 or libssl.so.7 must be recompiled.
1790 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1791 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1792 should be replaced with isp_2400 and isp_2500 modules respectively.
1795 The build previously allowed using 'make -n' to not recurse into
1796 sub-directories while showing what commands would be executed, and
1797 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1798 and 'make -N' will not.
1801 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1802 and etcupdate will now use this file. A custom sendmail.cf is now
1803 updated via this mechanism rather than via installworld. If you had
1804 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1805 want to remove the exclusion or change it to "always install".
1806 /etc/mail/sendmail.cf is now managed the same way regardless of
1807 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1808 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1811 Compatibility shims for legacy ATA device names have been removed.
1812 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1813 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1814 environment variables, /dev/ad* and /dev/ar* symbolic links.
1817 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1818 Please see the 20141231 entry below for information about prerequisites
1819 and upgrading, if you are not already using clang 3.5.0 or higher.
1822 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1823 and renamed from .symbols to .debug. This reduces the size requirements
1824 on the boot partition or file system and provides consistency with
1825 userland debug files.
1827 When using the supported kernel installation method the
1828 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1829 as is done with /boot/kernel.
1831 Developers wishing to maintain the historical behavior of installing
1832 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1835 The wireless drivers had undergone changes that remove the 'parent
1836 interface' from the ifconfig -l output. The rc.d network scripts
1837 used to check presence of a parent interface in the list, so old
1838 scripts would fail to start wireless networking. Thus, etcupdate(3)
1839 or mergemaster(8) run is required after kernel update, to update your
1840 rc.d scripts in /etc.
1843 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1844 These configurations are now automatically interpreted as
1845 'scrub fragment reassemble'.
1848 Kernel-loadable modules for the random(4) device are back. To use
1849 them, the kernel must have
1852 options RANDOM_LOADABLE
1854 kldload(8) can then be used to load random_fortuna.ko
1855 or random_yarrow.ko. Please note that due to the indirect
1856 function calls that the loadable modules need to provide,
1857 the build-in variants will be slightly more efficient.
1859 The random(4) kernel option RANDOM_DUMMY has been retired due to
1860 unpopularity. It was not all that useful anyway.
1863 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1864 Control over building the ELF Tool Chain tools is now provided by
1865 the WITHOUT_TOOLCHAIN knob.
1868 The polarity of Pulse Per Second (PPS) capture events with the
1869 uart(4) driver has been corrected. Prior to this change the PPS
1870 "assert" event corresponded to the trailing edge of a positive PPS
1871 pulse and the "clear" event was the leading edge of the next pulse.
1873 As the width of a PPS pulse in a typical GPS receiver is on the
1874 order of 1 millisecond, most users will not notice any significant
1875 difference with this change.
1877 Anyone who has compensated for the historical polarity reversal by
1878 configuring a negative offset equal to the pulse width will need to
1879 remove that workaround.
1882 The default group assigned to /dev/dri entries has been changed
1883 from 'wheel' to 'video' with the id of '44'. If you want to have
1884 access to the dri devices please add yourself to the video group
1887 # pw groupmod video -m $USER
1890 The menu.rc and loader.rc files will now be replaced during
1891 upgrades. Please migrate local changes to menu.rc.local and
1892 loader.rc.local instead.
1895 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1896 strings and strip have been removed. The src.conf(5) knob
1897 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1900 As ZFS requires more kernel stack pages than is the default on some
1901 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1902 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1904 Please consider using 'options KSTACK_PAGES=X' where X is greater
1905 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1908 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1909 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1910 default, i.e., they will not contain "::". For example, instead
1911 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1912 to have a more specific match, such as different map entries for
1913 IPv6:0:0 vs IPv6:0. This change requires that configuration
1914 data (including maps, files, classes, custom ruleset, etc.) must
1915 use the same format, so make certain such configuration data is
1916 upgrading. As a very simple check search for patterns like
1917 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1918 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1919 the cf option UseCompressedIPv6Addresses.
1922 The default kernel entropy-processing algorithm is now
1923 Fortuna, replacing Yarrow.
1925 Assuming you have 'device random' in your kernel config
1926 file, the configurations allow a kernel option to override
1927 this default. You may choose *ONE* of:
1929 options RANDOM_YARROW # Legacy /dev/random algorithm.
1930 options RANDOM_DUMMY # Blocking-only driver.
1932 If you have neither, you get Fortuna. For most people,
1933 read no further, Fortuna will give a /dev/random that works
1934 like it always used to, and the difference will be irrelevant.
1936 If you remove 'device random', you get *NO* kernel-processed
1937 entropy at all. This may be acceptable to folks building
1938 embedded systems, but has complications. Carry on reading,
1939 and it is assumed you know what you need.
1941 *PLEASE* read random(4) and random(9) if you are in the
1942 habit of tweaking kernel configs, and/or if you are a member
1943 of the embedded community, wanting specific and not-usual
1944 behaviour from your security subsystems.
1946 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1947 random', you will NOT have a functioning /dev/random, and
1948 many cryptographic features will not work, including SSH.
1949 You may also find strange behaviour from the random(3) set
1950 of library functions, in particular sranddev(3), srandomdev(3)
1951 and arc4random(3). The reason for this is that the KERN_ARND
1952 sysctl only returns entropy if it thinks it has some to
1953 share, and with RANDOM_DUMMY or no 'device random' this
1957 An additional fix for the issue described in the 20150614 sendmail
1958 entry below has been committed in revision 284717.
1961 FreeBSD's old make (fmake) has been removed from the system. It is
1962 available as the devel/fmake port or via pkg install fmake.
1965 The fix for the issue described in the 20150614 sendmail entry
1966 below has been committed in revision 284436. The work
1967 around described in that entry is no longer needed unless the
1968 default setting is overridden by a confDH_PARAMETERS configuration
1969 setting of '5' or pointing to a 512 bit DH parameter file.
1972 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1973 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1974 and devel/kyua to version 0.20+ and adjust any calling code to work
1975 with Kyuafile and kyua.
1978 The import of openssl to address the FreeBSD-SA-15:10.openssl
1979 security advisory includes a change which rejects handshakes
1980 with DH parameters below 768 bits. sendmail releases prior
1981 to 8.15.2 (not yet released), defaulted to a 512 bit
1982 DH parameter setting for client connections. To work around
1983 this interoperability, sendmail can be configured to use a
1984 2048 bit DH parameter by:
1986 1. Edit /etc/mail/`hostname`.mc
1987 2. If a setting for confDH_PARAMETERS does not exist or
1988 exists and is set to a string beginning with '5',
1989 replace it with '2'.
1990 3. If a setting for confDH_PARAMETERS exists and is set to
1991 a file path, create a new file with:
1992 openssl dhparam -out /path/to/file 2048
1993 4. Rebuild the .cf file:
1994 cd /etc/mail/; make; make install
1995 5. Restart sendmail:
1996 cd /etc/mail/; make restart
1998 A sendmail patch is coming, at which time this file will be
2002 Generation of legacy formatted entries have been disabled by default
2003 in pwd_mkdb(8), as all base system consumers of the legacy formatted
2004 entries were converted to use the new format by default when the new,
2005 machine independent format have been added and supported since FreeBSD
2008 Please see the pwd_mkdb(8) manual page for further details.
2011 Clang and llvm have been upgraded to 3.6.1 release. Please see the
2012 20141231 entry below for information about prerequisites and upgrading,
2013 if you are not already using 3.5.0 or higher.
2016 TI platform code switched to using vendor DTS files and this update
2017 may break existing systems running on Beaglebone, Beaglebone Black,
2020 - dtb files should be regenerated/reinstalled. Filenames are the
2021 same but content is different now
2022 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
2023 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
2024 addressing scheme is now pin 25 on /dev/gpioc3.
2025 - Pandaboard: /etc/ttys should be updated, serial console device is
2026 now /dev/ttyu2, not /dev/ttyu0
2029 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
2030 If you need the GNU extension from groff soelim(1), install groff
2031 from package: pkg install groff, or via ports: textproc/groff.
2034 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
2035 defined in symlink(7); previously symlinks were silently ignored.
2038 The const qualifier has been removed from iconv(3) to comply with
2039 POSIX. The ports tree is aware of this from r384038 onwards.
2042 Libraries specified by LIBADD in Makefiles must have a corresponding
2043 DPADD_<lib> variable to ensure correct dependencies. This is now
2044 enforced in src.libnames.mk.
2047 From legacy ata(4) driver was removed support for SATA controllers
2048 supported by more functional drivers ahci(4), siis(4) and mvs(4).
2049 Kernel modules ataahci and ataadaptec were removed completely,
2050 replaced by ahci and mvs modules respectively.
2053 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
2054 the 20141231 entry below for information about prerequisites and
2055 upgrading, if you are not already using 3.5.0 or higher.
2058 The 32-bit PowerPC kernel has been changed to a position-independent
2059 executable. This can only be booted with a version of loader(8)
2060 newer than January 31, 2015, so make sure to update both world and
2061 kernel before rebooting.
2064 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
2065 but before r278950, the RNG was not seeded properly. Immediately
2066 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
2067 ssh keys or openssl keys) that were generated w/ a kernel from that
2068 range. This does not affect programs that directly used /dev/random
2069 or /dev/urandom. All userland uses of arc4random(3) are affected.
2072 The autofs(4) ABI was changed in order to restore binary compatibility
2073 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
2074 with the new kernel.
2077 The powerpc64 kernel has been changed to a position-independent
2078 executable. This can only be booted with a new version of loader(8),
2079 so make sure to update both world and kernel before rebooting.
2082 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
2083 only release, no new features have been added. Please see the 20141231
2084 entry below for information about prerequisites and upgrading, if you
2085 are not already using 3.5.0.
2088 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
2089 taken from the ELF Tool Chain project rather than GNU binutils. They
2090 should be drop-in replacements, with the addition of arm64 support.
2091 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
2092 binutils tools, if necessary. See 20150805 for updated information.
2095 The default Unbound configuration now enables remote control
2096 using a local socket. Users who have already enabled the
2097 local_unbound service should regenerate their configuration
2098 by running "service local_unbound setup" as root.
2101 The GNU texinfo and GNU info pages have been removed.
2102 To be able to view GNU info pages please install texinfo from ports.
2105 Clang, llvm and lldb have been upgraded to 3.5.0 release.
2107 As of this release, a prerequisite for building clang, llvm and lldb is
2108 a C++11 capable compiler and C++11 standard library. This means that to
2109 be able to successfully build the cross-tools stage of buildworld, with
2110 clang as the bootstrap compiler, your system compiler or cross compiler
2111 should either be clang 3.3 or later, or gcc 4.8 or later, and your
2112 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
2115 On any standard FreeBSD 10.x or 11.x installation, where clang and
2116 libc++ are on by default (that is, on x86 or arm), this should work out
2119 On 9.x installations where clang is enabled by default, e.g. on x86 and
2120 powerpc, libc++ will not be enabled by default, so libc++ should be
2121 built (with clang) and installed first. If both clang and libc++ are
2122 missing, build clang first, then use it to build libc++.
2124 On 8.x and earlier installations, upgrade to 9.x first, and then follow
2125 the instructions for 9.x above.
2127 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
2128 default, and do not build clang.
2130 Many embedded systems are resource constrained, and will not be able to
2131 build clang in a reasonable time, or in some cases at all. In those
2132 cases, cross building bootable systems on amd64 is a workaround.
2134 This new version of clang introduces a number of new warnings, of which
2135 the following are most likely to appear:
2139 This warns in two cases, for both C and C++:
2140 * When the code is trying to take the absolute value of an unsigned
2141 quantity, which is effectively a no-op, and almost never what was
2142 intended. The code should be fixed, if at all possible. If you are
2143 sure that the unsigned quantity can be safely cast to signed, without
2144 loss of information or undefined behavior, you can add an explicit
2145 cast, or disable the warning.
2147 * When the code is trying to take an absolute value, but the called
2148 abs() variant is for the wrong type, which can lead to truncation.
2149 If you want to disable the warning instead of fixing the code, please
2150 make sure that truncation will not occur, or it might lead to unwanted
2153 -Wtautological-undefined-compare and
2154 -Wundefined-bool-conversion
2156 These warn when C++ code is trying to compare 'this' against NULL, while
2157 'this' should never be NULL in well-defined C++ code. However, there is
2158 some legacy (pre C++11) code out there, which actively abuses this
2159 feature, which was less strictly defined in previous C++ versions.
2161 Squid and openjdk do this, for example. The warning can be turned off
2162 for C++98 and earlier, but compiling the code in C++11 mode might result
2163 in unexpected behavior; for example, the parts of the program that are
2164 unreachable could be optimized away.
2167 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
2168 kernel sources have been removed. The .h files remain, since some
2169 utilities include them. This will need to be fixed later.
2170 If "mount -t oldnfs ..." is attempted, it will fail.
2171 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
2172 the utilities will report errors.
2175 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
2176 directories to top level SUBDIR variable when their parent
2177 directory is included in LOCAL_DIRS. Users with build systems with
2178 such hierarchies and without SUBDIR entries in the parent
2179 directory Makefiles should add them or add the directories to
2183 faith(4) and faithd(8) have been removed from the base system. Faith
2184 has been obsolete for a very long time.
2187 vt(4), the new console driver, is enabled by default. It brings
2188 support for Unicode and double-width characters, as well as
2189 support for UEFI and integration with the KMS kernel video
2192 You may need to update your console settings in /etc/rc.conf,
2193 most probably the keymap. During boot, /etc/rc.d/syscons will
2194 indicate what you need to do.
2196 vt(4) still has issues and lacks some features compared to
2197 syscons(4). See the wiki for up-to-date information:
2198 https://wiki.freebsd.org/Newcons
2200 If you want to keep using syscons(4), you can do so by adding
2201 the following line to /boot/loader.conf:
2205 pjdfstest has been integrated into kyua as an opt-in test suite.
2206 Please see share/doc/pjdfstest/README for more details on how to
2210 gperf has been removed from the base system for architectures
2211 that use clang. Ports that require gperf will obtain it from the
2215 pjdfstest has been moved from tools/regression/pjdfstest to
2219 At svn r271982, The default linux compat kernel ABI has been adjusted
2220 to 2.6.18 in support of the linux-c6 compat ports infrastructure
2221 update. If you wish to continue using the linux-f10 compat ports,
2222 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
2223 encouraged to update their linux-compat packages to linux-c6 during
2224 their next update cycle.
2227 The ofwfb driver, used to provide a graphics console on PowerPC when
2228 using vt(4), no longer allows mmap() of all physical memory. This
2229 will prevent Xorg on PowerPC with some ATI graphics cards from
2230 initializing properly unless x11-servers/xorg-server is updated to
2234 The xdev targets have been converted to using TARGET and
2235 TARGET_ARCH instead of XDEV and XDEV_ARCH.
2238 The default unbound configuration has been modified to address
2239 issues with reverse lookups on networks that use private
2240 address ranges. If you use the local_unbound service, run
2241 "service local_unbound setup" as root to regenerate your
2242 configuration, then "service local_unbound reload" to load the
2246 The GNU texinfo and GNU info pages are not built and installed
2247 anymore, WITH_INFO knob has been added to allow to built and install
2249 UPDATE: see 20150102 entry on texinfo's removal
2252 The GNU readline library is now an INTERNALLIB - that is, it is
2253 statically linked into consumers (GDB and variants) in the base
2254 system, and the shared library is no longer installed. The
2255 devel/readline port is available for third party software that
2259 The Itanium architecture (ia64) has been removed from the list of
2260 known architectures. This is the first step in the removal of the
2264 Commit r268115 has added NFSv4.1 server support, merged from
2265 projects/nfsv4.1-server. Since this includes changes to the
2266 internal interfaces between the NFS related modules, a full
2267 build of the kernel and modules will be necessary.
2268 __FreeBSD_version has been bumped.
2271 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
2272 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
2273 which differs from the behaviour controlled by this knob.)
2276 Maximal length of the serial number in CTL was increased from 16 to
2277 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
2278 and ctld, need to be rebuilt to work with a new kernel.
2281 The libatf-c and libatf-c++ major versions were downgraded to 0 and
2282 1 respectively to match the upstream numbers. They were out of
2283 sync because, when they were originally added to FreeBSD, the
2284 upstream versions were not respected. These libraries are private
2285 and not yet built by default, so renumbering them should be a
2286 non-issue. However, unclean source trees will yield broken test
2287 programs once the operator executes "make delete-old-libs" after a
2288 "make installworld".
2290 Additionally, the atf-sh binary was made private by moving it into
2291 /usr/libexec/. Already-built shell test programs will keep the
2292 path to the old binary so they will break after "make delete-old"
2295 If you are using WITH_TESTS=yes (not the default), wipe the object
2296 tree and rebuild from scratch to prevent spurious test failures.
2297 This is only needed once: the misnumbered libraries and misplaced
2298 binaries have been added to OptionalObsoleteFiles.inc so they will
2299 be removed during a clean upgrade.
2302 Clang and llvm have been upgraded to 3.4.1 release.
2305 We bogusly installed src.opts.mk in /usr/share/mk. This file should
2306 be removed to avoid issues in the future (and has been added to
2310 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
2311 past, it affected all builds that used the bsd.*.mk files. The old
2312 behavior was a bug, but people may have relied upon it. To get this
2313 behavior back, you can .include /etc/src.conf from /etc/make.conf
2314 (which is still global and isn't changed). This also changes the
2315 behavior of incremental builds inside the tree of individual
2316 directories. Set MAKESYSPATH to ".../share/mk" to do that.
2317 Although this has survived make universe and some upgrade scenarios,
2318 other upgrade scenarios may have broken. At least one form of
2319 temporary breakage was fixed with MAKESYSPATH settings for buildworld
2320 as well... In cases where MAKESYSPATH isn't working with this
2321 setting, you'll need to set it to the full path to your tree.
2323 One side effect of all this cleaning up is that bsd.compiler.mk
2324 is no longer implicitly included by bsd.own.mk. If you wish to
2325 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
2329 The lindev device has been removed since /dev/full has been made a
2330 standard device. __FreeBSD_version has been bumped.
2333 The knob WITHOUT_VI was added to the base system, which controls
2334 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
2335 in order to reorder files share/termcap and didn't build ex(1) as a
2336 build tool, so building/installing with WITH_VI is highly advised for
2337 build hosts for older releases.
2339 This issue has been fixed in stable/9 and stable/10 in r277022 and
2340 r276991, respectively.
2343 The YES_HESIOD knob has been removed. It has been obsolete for
2344 a decade. Please move to using WITH_HESIOD instead or your builds
2345 will silently lack HESIOD.
2348 The uart(4) driver has been changed with respect to its handling
2349 of the low-level console. Previously the uart(4) driver prevented
2350 any process from changing the baudrate or the CLOCAL and HUPCL
2351 control flags. By removing the restrictions, operators can make
2352 changes to the serial console port without having to reboot.
2353 However, when getty(8) is started on the serial device that is
2354 associated with the low-level console, a misconfigured terminal
2355 line in /etc/ttys will now have a real impact.
2356 Before upgrading the kernel, make sure that /etc/ttys has the
2357 serial console device configured as 3wire without baudrate to
2358 preserve the previous behaviour. E.g:
2359 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
2362 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
2363 to improve performance. To re-enable it, if needed, run rpcbind
2364 with command line option -W.
2367 Switched back to the GPL dtc compiler due to updates in the upstream
2368 dts files not being supported by the BSDL dtc compiler. You will need
2369 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
2370 may result while building dtb files during a kernel build if you fail
2371 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
2374 Clang and llvm have been upgraded to 3.4 release.
2377 The nve(4) driver has been removed. Please use the nfe(4) driver
2378 for NVIDIA nForce MCP Ethernet adapters instead.
2381 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
2382 This could cause certain C++ applications using shared libraries built
2383 against the previous version of libc++ to crash. The incompatibility
2384 has now been fixed, but any C++ applications or shared libraries built
2385 between r261283 and r261801 should be recompiled.
2388 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
2389 capability mode support. Please note that enabling the feature in
2390 kernel is still highly recommended.
2393 OpenSSH is now built with sandbox support, and will use sandbox as
2394 the default privilege separation method. This requires Capsicum
2395 capability mode support in kernel.
2398 The libelf and libdwarf libraries have been updated to newer
2399 versions from upstream. Shared library version numbers for
2400 these two libraries were bumped. Any ports or binaries
2401 requiring these two libraries should be recompiled.
2402 __FreeBSD_version is bumped to 1100006.
2405 If a Makefile in a tests/ directory was auto-generating a Kyuafile
2406 instead of providing an explicit one, this would prevent such
2407 Makefile from providing its own Kyuafile in the future during
2408 NO_CLEAN builds. This has been fixed in the Makefiles but manual
2409 intervention is needed to clean an objdir if you use NO_CLEAN:
2410 # find /usr/obj -name Kyuafile | xargs rm -f
2413 The behavior of gss_pseudo_random() for the krb5 mechanism
2414 has changed, for applications requesting a longer random string
2415 than produced by the underlying enctype's pseudo-random() function.
2416 In particular, the random string produced from a session key of
2417 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
2418 be different at the 17th octet and later, after this change.
2419 The counter used in the PRF+ construction is now encoded as a
2420 big-endian integer in accordance with RFC 4402.
2421 __FreeBSD_version is bumped to 1100004.
2424 The WITHOUT_ATF build knob has been removed and its functionality
2425 has been subsumed into the more generic WITHOUT_TESTS. If you were
2426 using the former to disable the build of the ATF libraries, you
2427 should change your settings to use the latter.
2430 The default version of mtree is nmtree which is obtained from
2431 NetBSD. The output is generally the same, but may vary
2432 slightly. If you found you need identical output adding
2433 "-F freebsd9" to the command line should do the trick. For the
2434 time being, the old mtree is available as fmtree.
2437 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
2438 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
2439 1.1.4_8 and verify bsdyml not linked in, before running "make
2441 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
2443 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
2446 The stable/10 branch has been created in subversion from head
2453 Sometimes, obscure build problems are the result of environment
2454 poisoning. This can happen because the make utility reads its
2455 environment when searching for values for global variables. To run
2456 your build attempts in an "environmental clean room", prefix all make
2457 commands with 'env -i '. See the env(1) manual page for more details.
2458 Occasionally a build failure will occur with "make -j" due to a race
2459 condition. If this happens try building again without -j, and please
2460 report a bug if it happens consistently.
2462 When upgrading from one major version to another it is generally best to
2463 upgrade to the latest code in the currently installed branch first, then
2464 do an upgrade to the new branch. This is the best-tested upgrade path,
2465 and has the highest probability of being successful. Please try this
2466 approach if you encounter problems with a major version upgrade. Since
2467 the stable 4.x branch point, one has generally been able to upgrade from
2468 anywhere in the most recent stable branch to head / current (or even the
2469 last couple of stable branches). See the top of this file when there's
2472 The update process will emit an error on an attempt to perform a build
2473 or install from a FreeBSD version below the earliest supported version.
2474 When updating from an older version the update should be performed one
2475 major release at a time, including running `make delete-old` at each
2478 When upgrading a live system, having a root shell around before
2479 installing anything can help undo problems. Not having a root shell
2480 around can lead to problems if pam has changed too much from your
2481 starting point to allow continued authentication after the upgrade.
2483 This file should be read as a log of events. When a later event changes
2484 information of a prior event, the prior event should not be deleted.
2485 Instead, a pointer to the entry with the new information should be
2486 placed in the old entry. Readers of this file should also sanity check
2487 older entries before relying on them blindly. Authors of new entries
2488 should write them with this in mind.
2492 When upgrading the boot ZFS pool to a new version, always follow
2495 1.) recompile and reinstall the ZFS boot loader and boot block
2496 (this is part of "make buildworld" and "make installworld")
2498 2.) update the ZFS boot block on your boot drive
2500 The following example updates the ZFS boot block on the
2501 freebsd-boot partition of a GPT partitioned drive ada0:
2502 "gpart bootcode -p /boot/gptzfsboot -i $N ada0"
2503 The value $N will typically be 1 (if booting from BIOS) or 2 (if
2506 Non-boot pools do not need these updates.
2510 If you are updating from a prior version of FreeBSD (even one just
2511 a few days old), you should follow this procedure. It is the most
2512 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2514 make kernel-toolchain
2515 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2516 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2518 To test a kernel once
2519 ---------------------
2520 If you just want to boot a kernel once (because you are not sure
2521 if it works, or if you want to boot a known bad kernel to provide
2522 debugging information) run
2523 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2524 nextboot -k testkernel
2526 To rebuild everything and install it on the current system.
2527 -----------------------------------------------------------
2528 # Note: sometimes if you are running current you gotta do more than
2529 # is listed here if you are upgrading from a really old current.
2531 <make sure you have good level 0 dumps>
2533 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2534 make installkernel KERNCONF=YOUR_KERNEL_HERE
2536 <reboot in single user> [3]
2543 To cross-install current onto a separate partition
2544 --------------------------------------------------
2545 # In this approach we use a separate partition to hold
2546 # current's root, 'usr', and 'var' directories. A partition
2547 # holding "/", "/usr" and "/var" should be about 2GB in
2550 <make sure you have good level 0 dumps>
2553 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2554 <maybe newfs current's root partition>
2555 <mount current's root partition on directory ${CURRENT_ROOT}>
2556 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
2557 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2558 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2559 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2560 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2561 <reboot into current>
2562 <do a "native" rebuild/install as described in the previous section>
2563 <maybe install compatibility libraries from ports/misc/compat*>
2567 To upgrade in-place from stable to current
2568 ----------------------------------------------
2569 <make sure you have good level 0 dumps>
2571 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
2572 make installkernel KERNCONF=YOUR_KERNEL_HERE
2574 <reboot in single user> [3]
2581 Make sure that you've read the UPDATING file to understand the
2582 tweaks to various things you need. At this point in the life
2583 cycle of current, things change often and you are on your own
2584 to cope. The defaults can also change, so please read ALL of
2585 the UPDATING entries.
2587 Also, if you are tracking -current, you must be subscribed to
2588 freebsd-current@freebsd.org. Make sure that before you update
2589 your sources that you have read and understood all the recent
2590 messages there. If in doubt, please track -stable which has
2591 much fewer pitfalls.
2593 [1] If you have third party modules, such as vmware, you should disable
2594 them at this point so they don't crash your system on
2595 reboot. Alternatively, you should rebuild all the modules you have in
2596 your system and install them as well. If you are running -current, you
2597 should seriously consider placing all sources to all the modules for
2598 your system (or symlinks to them) in /usr/local/sys/modules so this
2599 happens automatically. If all your modules come from ports, then adding
2600 the port origin directories to PORTS_MODULES instead is also automatic
2602 PORTS_MODULES+=x11/nvidia-driver
2604 [3] From the bootblocks, boot -s, and then do
2608 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed
2609 cd src # full path to source
2610 adjkerntz -i # if CMOS is wall time
2611 Also, when doing a major release upgrade, it is required that you boot
2612 into single user mode to do the installworld.
2614 [4] Note: This step is non-optional. Failure to do this step
2615 can result in a significant reduction in the functionality of the
2616 system. Attempting to do it by hand is not recommended and those
2617 that pursue this avenue should read this file carefully, as well
2618 as the archives of freebsd-current and freebsd-hackers mailing lists
2619 for potential gotchas. See etcupdate(8) for more information.
2621 [5] Usually this step is a no-op. However, from time to time
2622 you may need to do this if you get unknown user in the following
2625 [6] This only deletes old files and directories. Old libraries
2626 can be deleted by "make delete-old-libs", but you have to make
2627 sure that no program is using those libraries anymore.
2629 [8] The new kernel must be able to run existing binaries used by an
2630 installworld. When upgrading across major versions, the new kernel's
2631 configuration must include the correct COMPAT_FREEBSD<n> option for
2632 existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure
2633 to do so may leave you with a system that is hard to boot to recover. A
2634 GENERIC kernel will include suitable compatibility options to run
2635 binaries from older branches. Note that the ability to run binaries
2636 from unsupported branches is not guaranteed.
2638 Make sure that you merge any new devices from GENERIC since the
2639 last time you updated your kernel config file. Options also
2640 change over time, so you may need to adjust your custom kernels
2643 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2644 "?=" instead of the "=" assignment operator, so that buildworld can
2645 override the CPUTYPE if it needs to.
2647 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2648 not on the command line, or in /etc/make.conf. buildworld will
2649 warn if it is improperly defined.
2652 This file contains a list, in reverse chronological order, of major
2653 breakages in tracking -current. It is not guaranteed to be a complete
2654 list of such breakages, and only contains entries since September 23, 2011.
2655 If you need to see UPDATING entries from before that date, you will need
2656 to fetch an UPDATING file from an older FreeBSD release.
2658 Copyright information:
2660 Copyright 1998-2009 M. Warner Losh <imp@FreeBSD.org>
2662 Redistribution, publication, translation and use, with or without
2663 modification, in full or in part, in any form or format of this
2664 document are permitted without further permission from the author.
2666 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2667 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2668 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2669 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2670 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2671 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2672 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2673 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2674 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2675 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2676 POSSIBILITY OF SUCH DAMAGE.
2678 Contact Warner Losh if you have any questions about your use of