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 Commit b8d60729deef changed the TCP congestion control framework so
32 that any of the included congestion control modules could be
33 the single module built into the kernel. Previously newreno
34 was automatically built in through direct reference. Has of
35 this commit you are required to declare at least one congestion
36 control module (e.g. 'options CC_NEWRENO') and to also delcare a
37 default using the CC_DEFAULT option (e.g. options CC_DEFAULT="newreno\").
38 The GENERIC configuation includes CC_NEWRENO and defines newreno
39 as the default. If no congestion control option is built into the
40 kernel and you are including networking, the kernel compile will
41 fail. Also if no default is declared the kernel compile will fail.
44 Commit f0c9847a6c47 changed the arguments for VOP_ALLOCATE.
45 The NFS modules must be rebuilt from sources and any out
46 of tree file systems that implement their own VOP_ALLOCATE
47 may need to be modified.
50 The synchronous PPP kernel driver sppp(4) has been removed.
51 The cp(4) and ce(4) drivers are now always compiled with netgraph(4)
52 support, formerly enabled by NETGRAPH_CRONYX option.
55 sh(1) is now the default shell for the root user. To force root to use
56 the csh shell, please run the following command as root:
61 Ncurses distribution has been split between libtinfow and libncurses
62 with libncurses.so becoming a linker (ld) script to seamlessly link
63 to libtinfow as needed. Bump _FreeBSD_version to 1400035 to reflect
67 As of commit 8160a0f62be6, the dummynet module no longer depends on the
68 ipfw module. Dummynet can now be used by pf as well as ipfw. As such
69 users who relied on this dependency may need to include ipfw in the
70 list of modules to load on their systems.
73 As of commit 903873ce1560, the mixer(8) utility has got a slightly
74 new syntax. Please refer to the mixer(8) manual page for more
75 information. The old mixer utility can be installed from ports:
76 audio/freebsd-13-mixer
79 As of commit 55089ef4f8bb, the global variable nfs_maxcopyrange has
80 been deleted from the nfscommon.ko. As such, nfsd.ko must be built
81 from up to date sources to avoid an undefined reference when
85 As of commit 62ca9fc1ad56 OpenSSL no longer enables kernel TLS
86 by default. Users can enable kernel TLS via the "KTLS" SSL
87 option. This can be enabled globally by using a custom
88 OpenSSL config file via OPENSSL_CONF or via an
89 application-specific configuration option for applications
90 which permit setting SSL options via SSL_CONF_cmd(3).
93 Commit 3ad1e1c1ce20 changed the internal KAPI between the NFS
94 modules. Therefore, all need to be rebuilt from sources.
97 Commit b69019c14cd8 removes pf's DIOCGETSTATESNV ioctl.
98 As of be70c7a50d32 it is no longer used by userspace, but it does mean
99 users may not be able to enumerate pf states if they update the kernel
100 past b69019c14cd8 without first updating userspace past be70c7a50d32.
103 As of commit 01ad0c007964 if_bridge member interfaces can no longer
104 change their MTU. Changing the MTU of the bridge itself will change the
105 MTU on all member interfaces instead.
108 Commit ee29e6f31111 changed the internal KAPI between the nfscommon
109 and nfsd modules. Therefore, both need to be rebuilt from sources.
110 Bump __FreeBSD_version to 1400026 for this KAPI change.
113 The 20210707 awk update brought in a change in behavior. This has
114 been corrected as of d4d252c49976. Between these dates, if you
115 installed a new awk binary, you may not be able to build a new
116 kernel because the change in behavior affected the genoffset
117 script used to build the kernel. If you did update, the fix is
118 to update your sources past the above hash and do
121 % sudo -E make install
122 to enable building kernels again.
125 Commit 1e0a518d6548 changed the internal KAPI between the NFS
126 modules. They all need to be rebuilt from sources. I did not
127 bump __FreeBSD_version, since it was bumped recently.
130 awk has been updated to the latest one-true-awk version 20210215.
131 This contains a number of minor bug fixes.
134 The NFSv4 client now uses the highest minor version of NFSv4
135 supported by the NFSv4 server by default instead of minor version 0,
137 The "minorversion" mount option may be used to override this default.
140 Bump __FreeBSD_version to 1400024 for LinuxKPI changes.
141 Most notably netdev.h can change now as the (last) dependencies
142 (mlx4/ofed) are now using struct ifnet directly, but also for PCI
143 additions and others.
146 The directory "blacklisted" under /usr/share/certs/ has been
147 renamed to "untrusted".
150 svnlite has been removed from base. Should you need svn for any reason
151 please install the svn package or port.
154 Commit e1a907a25cfa changed the internal KAPI between the krpc
155 and nfsserver. As such, both modules must be rebuilt from
156 sources. Bump __FreeBSD_version to 1400022.
159 The an(4) driver has been removed from FreeBSD.
162 The vendor/openzfs branch was renamed to vendor/openzfs/legacy to
163 start tracking OpenZFS upstream more closely. Please see
164 https://lists.freebsd.org/archives/freebsd-current/2021-June/000153.html
165 for details on how to correct any errors that might result. The
166 short version is that you need to remove the old branch locally:
167 git update-ref -d refs/remotes/freebsd/vendor/openzfs
168 (assuming your upstream origin is named 'freebsd').
171 Commits 17accc08ae15 and de102f870501 add new files to LinuxKPI
172 which break drm-kmod. In addition various other additions where
173 comitted. Bump __FreeBSD_version to 1400015 to be able to detect this.
176 Commit ca179c4d74f2 changed the package in which the OpenSSL
177 libraries and utilities are packaged.
178 It is recommended for pkgbase user to do:
179 pkg install -f FreeBSD-openssl
180 before pkg upgrade otherwise some dependencies might not be met
181 and pkg will stop working as libssl will not be present anymore
185 Commit 875977314881 changed the internal KAPI between
186 the nfsd and nfscommon modules. As such these modules
187 need to be rebuilt from sources.
188 Without this patch in your NFSv4.1/4.2 server, enabling
189 delegations by setting vfs.nfsd.issue_delegations non-zero
193 Commit 7763814fc9c2 changed the internal KAPI between
194 the krpc and NFS. As such, the krpc, nfscommon and
195 nfscl modules must all be rebuilt from sources.
196 Without this patch, NFSv4.1/4.2 mounts should not
197 be done with the nfscbd(8) daemon running, to avoid
198 needing a working back channel for server->client RPCs.
201 Commit 01ae8969a9ee fixed the NFSv4.1/4.2 server so that it
202 handles binding of the back channel as required by RFC5661.
203 Until this patch is in your server, avoid use of the "nconnects"
204 mount option for Linux NFSv4.1/4.2 mounts.
207 For 64-bit architectures the base system is now built with Position
208 Independent Executable (PIE) support enabled by default. It may be
209 disabled using the WITHOUT_PIE knob. A clean build is required.
212 Various LinuxKPI functionality was added which conflicts with DRM.
213 Please update your drm-kmod port to after the __FreeBSD_verison 1400003
217 PC Card attachments for all devices have been removed. In the case of
218 wi and cmx, the entire drivers were removed because they were only
219 PC Card devices. FreeBSD_version 1300134 should be used for this
220 since it was bumped so recently.
223 Transport-independent parts of HID support have been split off the USB
224 code in to separate subsystem. Kernel configs which include one of
225 ums, ukbd, uhid, atp, wsp, wmt, uaudio, ugold or ucycom drivers should
226 be updated with adding of "device hid" line.
229 ncurses installation has been modified to only keep the widechar
230 enabled version. Incremental build is broken for that change, so it
231 requires a clean build.
234 The FreeBSD project has migrated from Subversion to Git. Temporary
235 instructions can be found at
236 https://github.com/bsdimp/freebsd-git-docs/blob/main/src-cvt.md
237 and other documents in that repo.
240 The services database has been updated to cover more of the basic
241 services expected in a modern system. The database is big enough
242 that it will cause issues in mergemaster in Releases previous to
243 12.2 and 11.3, or in very old current systems from before r358154.
246 Obsolete in-tree GDB 6.1.1 has been removed. GDB (including kgdb)
247 may be installed from ports or packages.
250 ping6 has been merged into ping. It can now be called as "ping -6".
251 See ping(8) for details.
254 Default value of net.add_addr_allfibs has been changed to 0.
255 If you have multi-fib configuration and rely on existence of all
256 interface routes in every fib, you need to set the above sysctl to 1.
259 The internal pre-processor in the calendar(1) program has been
260 extended to support more C pre-processor commands (e.g. #ifdef, #else,
261 and #undef) and to detect unbalanced conditional statements.
262 Error messages have been extended to include the filename and line
263 number if processing stops to help fixing malformed data files.
266 All the data files for the calendar(1) program, except calendar.freebsd,
267 have been moved to the deskutils/calendar-data port, much like the
268 jewish calendar entries were moved to deskutils/hebcal years ago. After
269 make delete-old-files, you need to install it to retain full
270 functionality. calendar(1) will issue a reminder for files it can't
274 LINT files are no longer generated. We now include the relevant NOTES
275 files. Note: This may cause conflicts with updating in some cases.
276 find sys -name LINT\* -delete
277 is suggested across this commit to remove the generated LINT files.
279 If you have tried to update with generated files there, the svn
280 command you want to un-auger the tree is
283 and then do the above find from the top level. Substitute 'amd64'
284 above with where the error message indicates a conflict.
287 OpenZFS support has been integrated. Do not upgrade root pools until
288 the loader is updated to support zstd. Furthermore, we caution against
289 'zpool upgrade' for the next few weeks. The change should be transparent
290 unless you want to use new features.
292 Not all "NO_CLEAN" build scenarios work across these changes. Many
293 scenarios have been tested and fixed, but rebuilding kernels without
294 rebuilding world may fail.
296 The ZFS cache file has moved from /boot to /etc to match the OpenZFS
297 upstream default. A fallback to /boot has been added for mountroot.
299 Pool auto import behavior at boot has been moved from the kernel module
300 to an explicit "zpool import -a" in one of the rc scripts enabled by
301 zfs_enable=YES. This means your non-root zpools won't auto import until
302 you upgrade your /etc/rc.d files.
305 The resume code now notifies devd with the 'kernel' system
306 rather than the old 'kern' subsystem to be consistent with
307 other use. The old notification will be created as well, but
308 will be removed prior to FreeBSD 14.0.
311 r362275 changed the internal API between the kernel RPC and the
312 NFS modules. As such, all the modules must be recompiled from
316 r364330 modified the internal API used between the NFS modules.
317 As such, all the NFS modules must be re-compiled from sources.
320 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
321 been upgraded to 11.0.0. Please see the 20141231 entry below for
322 information about prerequisites and upgrading, if you are not already
323 using clang 3.5.0 or higher.
326 r364092 modified the internal ABI used between the kernel NFS
327 modules. As such, all of these modules need to be rebuilt
328 from sources, so a version bump was done.
331 Makefile.inc has been updated to work around the issue documented in
332 20200729. It was a case where the optimization of using symbolic links
333 to point to binaries created a situation where we'd run new binaries
334 with old libraries starting midway through the installworld process.
337 r363679 has redefined some undefined behavior in regcomp(3); notably,
338 extraneous escapes of most ordinary characters will no longer be
339 accepted. An exp-run has identified all of the problems with this in
340 ports, but other non-ports software may need extra escapes removed to
341 continue to function.
343 Because of this change, installworld may encounter the following error
344 from rtld: Undefined symbol "regcomp@FBSD_1.6" -- It is imperative that
345 you do not halt installworld. Instead, let it run to completion (whether
346 successful or not) and run installworld once more.
349 A new implementation of bc and dc has been imported in r362681. This
350 implementation corrects non-conformant behavior of the previous bc
351 and adds GNU bc compatible options. It offers a number of extensions,
352 is much faster on large values, and has support for message catalogs
353 (a number of languages are already supported, contributions of further
354 languages welcome). The option WITHOUT_GH_BC can be used to build the
355 world with the previous versions of bc and dc.
358 r362639 changed the internal API used between the NFS kernel modules.
359 As such, they all need to be rebuilt from sources.
362 r362158 changed the arguments for VFS_CHECKEXP(). As such, any
363 out of tree file systems need to be modified and rebuilt.
364 Also, any file systems that are modules must be rebuilt.
367 read(2) of a directory fd is now rejected by default. root may
368 re-enable it for system root only on non-ZFS filesystems with the
369 security.bsd.allow_read_dir sysctl(8) MIB if
370 security.bsd.suser_enabled=1.
372 It may be advised to setup aliases for grep to default to `-d skip` if
373 commonly non-recursively grepping a list that includes directories and
374 the potential for the resulting stderr output is not tolerable. Example
375 aliases are now installed, commented out, in /root/.cshrc and
379 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
380 been upgraded to 10.0.1. Please see the 20141231 entry below for
381 information about prerequisites and upgrading, if you are not already
382 using clang 3.5.0 or higher.
385 Support for obsolete compilers has been removed from the build system.
386 Clang 6 and GCC 6.4 are the minimum supported versions.
389 closefrom(2) has been moved under COMPAT12, and replaced in libc with a
390 stub that calls close_range(2). If using a custom kernel configuration,
391 you may want to ensure that the COMPAT_FREEBSD12 option is included, as
392 a slightly older -CURRENT userland and older FreeBSD userlands may not
393 be functional without closefrom(2).
396 Upstream DTS from Linux 5.6 was merged and they now have the SID
397 and THS (Secure ID controller and THermal Sensor) node present.
398 The DTB overlays have now been removed from the tree for the H3/H5 and
399 A64 SoCs and the aw_sid and aw_thermal driver have been updated to
400 deal with upstream DTS. If you are using those overlays you need to
401 remove them from loader.conf and update the DTBs on the FAT partition.
404 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
405 been upgraded to 10.0.0. Please see the 20141231 entry below for
406 information about prerequisites and upgrading, if you are not already
407 using clang 3.5.0 or higher.
410 The amd(8) automount daemon has been removed from the source tree.
411 As of FreeBSD 10.1 autofs(5) is the preferred tool for automounting.
412 amd is still available in the sysutils/am-utils port.
415 Removed brooktree driver (bktr.4) from the tree.
418 The WITH_GPL_DTC option has been removed. The BSD-licenced device tree
419 compiler in usr.bin/dtc is used on all architectures which use dtc, and
420 the GPL dtc is available (if needed) from the sysutils/dtc port.
423 The WITHOUT_LLVM_LIBUNWIND option has been removed. LLVM's libunwind
424 is used by all supported CPU architectures.
427 GCC 4.2.1 has been removed from the tree. The WITH_GCC,
428 WITH_GCC_BOOTSTRAP, and WITH_GNUCXX options are no longer available.
429 Users who wish to build FreeBSD with GCC must use the external toolchain
433 ncurses has been updated to a newer version (6.2-20200215). Given the ABI
434 has changed, users will have to rebuild all the ports that are linked to
438 The size of struct vnet and the magic cookie have changed.
439 Users need to recompile libkvm and all modules using VIMAGE
440 together with their new kernel.
443 Defining the long deprecated NO_CTF, NO_DEBUG_FILES, NO_INSTALLLIB,
444 NO_MAN, NO_PROFILE, and NO_WARNS variables is now an error. Update
445 your Makefiles and scripts to define MK_<var>=no instead as required.
447 One exception to this is that program or library Makefiles should
448 define MAN to empty rather than setting MK_MAN=no.
451 Clang/LLVM is now the default compiler and LLD the default
455 make universe no longer uses GCC 4.2.1 on any architectures.
456 Architectures not supported by in-tree Clang/LLVM require an
457 external toolchain package.
460 GCC 4.2.1 is now not built by default, as part of the GCC 4.2.1
461 retirement plan. Specifically, the GCC, GCC_BOOTSTRAP, and GNUCXX
462 options default to off for all supported CPU architectures. As a
463 short-term transition aid they may be enabled via WITH_* options.
464 GCC 4.2.1 is expected to be removed from the tree on 2020-03-31.
467 Support for armv5 has been disconnected and is being removed. The
468 machine combination MACHINE=arm MACHINE_ARCH=arm is no longer valid.
469 You must now use a MACHINE_ARCH of armv6 or armv7. The default
470 MACHINE_ARCH for MACHINE=arm is now armv7.
473 Clang/LLVM is now the default compiler for all powerpc architectures.
474 LLD is now the default linker for powerpc64. The change for powerpc64
475 also includes a change to the ELFv2 ABI, incompatible with the existing
479 Kernel-loadable random(4) modules are no longer unloadable.
482 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
483 been upgraded to 9.0.1. Please see the 20141231 entry below for
484 information about prerequisites and upgrading, if you are not already
485 using clang 3.5.0 or higher.
488 r355677 has modified the internal interface used between the
489 NFS modules in the kernel. As such, they must all be upgraded
490 simultaneously. I will do a version bump for this.
493 The root certificates of the Mozilla CA Certificate Store have been
494 imported into the base system and can be managed with the certctl(8)
495 utility. If you have installed the security/ca_root_nss port or package
496 with the ETCSYMLINK option (the default), be advised that there may be
497 differences between those included in the port and those included in
498 base due to differences in nss branch used as well as general update
499 frequency. Note also that certctl(8) cannot manage certs in the
500 format used by the security/ca_root_nss port.
503 The amd(8) automount daemon has been disabled by default, and will be
504 removed in the future. As of FreeBSD 10.1 the autofs(5) is available
508 The nctgpio and wbwd drivers have been moved to the superio bus.
509 If you have one of these drivers in a kernel configuration, then
510 you should add device superio to it. If you use one of these drivers
511 as a module and you compile a custom set of modules, then you should
512 add superio to the set.
515 KPIs for network drivers to access interface addresses have changed.
516 Users need to recompile NIC driver modules together with kernel.
519 The net.link.tap.user_open sysctl no longer prevents user opening of
520 already created /dev/tapNN devices. Access is still controlled by
521 node permissions, just like tun devices. The net.link.tap.user_open
522 sysctl is now used only to allow users to perform devfs cloning of
523 tap devices, and the subsequent open may not succeed if the user is not
524 in the appropriate group. This sysctl may be deprecated/removed
525 completely in the future.
528 mips, powerpc, and sparc64 are no longer built as part of
529 universe / tinderbox unless MAKE_OBSOLETE_GCC is defined. If
530 not defined, mips, powerpc, and sparc64 builds will look for
531 the xtoolchain binaries and if installed use them for universe
532 builds. As llvm 9.0 becomes vetted for these architectures, they
533 will be removed from the list.
536 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
537 been upgraded to 9.0.0. Please see the 20141231 entry below for
538 information about prerequisites and upgrading, if you are not already
539 using clang 3.5.0 or higher.
542 The hpt27xx, hptmv, hptnr, and hptrr drivers have been removed from
543 GENERIC. They are available as modules and can be loaded by adding
544 to /boot/loader.conf hpt27xx_load="YES", hptmv_load="YES",
545 hptnr_load="YES", or hptrr_load="YES", respectively.
548 ntpd no longer by default locks its pages in memory, allowing them
549 to be paged out by the kernel. Use rlimit memlock to restore
550 historic BSD behaviour. For example, add "rlimit memlock 32"
551 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
554 Several of ping6's options have been renamed for better consistency
555 with ping. If you use any of -ARWXaghmrtwx, you must update your
556 scripts. See ping6(8) for details.
559 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
560 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
561 been removed from mount_fusefs(8). You can safely remove them from
562 your scripts, because they had no effect.
564 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
565 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
566 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
567 sysctls have been removed. If you felt the need to set any of them to
568 a non-default value, please tell asomers@FreeBSD.org why.
571 Default permissions on the /var/account/acct file (and copies of it
572 rotated by periodic daily scripts) are changed from 0644 to 0640
573 because the file contains sensitive information that should not be
574 world-readable. If the /var/account directory must be created by
575 rc.d/accounting, the mode used is now 0750. Admins who use the
576 accounting feature are encouraged to change the mode of an existing
577 /var/account directory to 0750 or 0700.
580 Entropy collection and the /dev/random device are no longer optional
581 components. The "device random" option has been removed.
582 Implementations of distilling algorithms can still be made loadable
583 with "options RANDOM_LOADABLE" (e.g., random_fortuna.ko).
586 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
587 been upgraded to 8.0.1. Please see the 20141231 entry below for
588 information about prerequisites and upgrading, if you are not already
589 using clang 3.5.0 or higher.
592 A fix was applied to i386 kernel modules to avoid panics with
593 dpcpu or vnet. Users need to recompile i386 kernel modules
594 having pcpu or vnet sections or they will refuse to load.
597 User-wired pages now have their own counter,
598 vm.stats.vm.v_user_wire_count. The vm.max_wired sysctl was renamed
599 to vm.max_user_wired and changed from an unsigned int to an unsigned
600 long. bhyve VMs wired with the -S are now subject to the user
601 wiring limit; the vm.max_user_wired sysctl may need to be tuned to
602 avoid running into the limit.
605 The IPSEC option has been removed from GENERIC. Users requiring
606 ipsec(4) must now load the ipsec(4) kernel module.
609 The tap(4) driver has been folded into tun(4), and the module has been
610 renamed to tuntap. You should update any kld_list="if_tap" or
611 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
612 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
613 module instead, and "device tap" or "device tun" entries in kernel
614 config files to select the tuntap device instead.
617 The following knobs have been added related to tradeoffs between
618 safe use of the random device and availability in the absence of
621 kern.random.initial_seeding.bypass_before_seeding: tunable; set
622 non-zero to bypass the random device prior to seeding, or zero to
623 block random requests until the random device is initially seeded.
624 For now, set to 1 (unsafe) by default to restore pre-r346250 boot
625 availability properties.
627 kern.random.initial_seeding.read_random_bypassed_before_seeding:
628 read-only diagnostic sysctl that is set when bypass is enabled and
629 read_random(9) is bypassed, to enable programmatic handling of this
630 initial condition, if desired.
632 kern.random.initial_seeding.arc4random_bypassed_before_seeding:
633 Similar to the above, but for for arc4random(9) initial seeding.
635 kern.random.initial_seeding.disable_bypass_warnings: tunable; set
636 non-zero to disable warnings in dmesg when the same conditions are
637 met as for the diagnostic sysctls above. Defaults to zero, i.e.,
638 produce warnings in dmesg when the conditions are met.
641 The loadable random module KPI has changed; the random_infra_init()
642 routine now requires a 3rd function pointer for a bool (*)(void)
643 method that returns true if the random device is seeded (and
644 therefore unblocked).
647 r345895 reverts r320698. This implies that an nfsuserd(8) daemon
648 built from head sources between r320757 (July 6, 2017) and
649 r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
650 is added to the command line.
651 nfsuserd daemons built from head sources that are post-r338192 are
652 not affected and should continue to work.
655 The fuse(4) module has been renamed to fusefs(4) for consistency with
656 other filesystems. You should update any kld_load="fuse" entries in
657 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
658 "options FUSE" entries in kernel config files.
661 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
662 8.0.0. Please see the 20141231 entry below for information about
663 prerequisites and upgrading, if you are not already using clang 3.5.0
667 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
668 compiled into your custom kernel, add 'device xz' statement to the
672 drm and drm2 have been removed from the tree. Please see
673 https://wiki.freebsd.org/Graphics for the latest information on
674 migrating to the drm ports.
677 Iflib is no longer unconditionally compiled into the kernel. Drivers
678 using iflib and statically compiled into the kernel, now require
679 the 'device iflib' config option. For the same drivers loaded as
680 modules on kernels not having 'device iflib', the iflib.ko module
681 is loaded automatically.
684 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
685 options no longer exist since r343219 and r343427 respectively;
686 nothing uses them, so they should be just removed from custom
690 r342635 changes the way efibootmgr(8) works by requiring users to add
691 the -b (bootnum) parameter for commands where the bootnum was previously
692 specified with each option. For example 'efibootmgr -B 0001' is now
693 'efibootmgr -B -b 0001'.
696 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
697 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
698 servers that have vfs.nfsd.nfs_privport set will only allow mounts
699 from clients using a reserved port. Since both the FreeBSD and Linux
700 NFSv4 clients use reserved ports by default, this should not affect
704 The XLP config has been removed. We can't support 64-bit atomics in this
705 kernel because it is running in 32-bit mode. XLP users must transition
706 to running a 64-bit kernel (XLP64 or XLPN32).
708 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
709 the preferred emulator today and we don't need two different ones.
711 The old sibyte / swarm / Broadcom BCM1250 support has been
712 removed from the mips port.
715 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
716 7.0.1. Please see the 20141231 entry below for information about
717 prerequisites and upgrading, if you are not already using clang 3.5.0
721 Remove the timed and netdate programs from the base tree. Setting
722 the time with these daemons has been obsolete for over a decade.
725 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
726 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
727 it produces broken binaries when ifuncs are in use. Users needing
728 GNU ld should install the binutils port or package.
731 The BSD crtbegin and crtend code has been enabled by default. It has
732 had extensive testing on amd64, arm64, and i386. It can be disabled
733 by building a world with -DWITHOUT_BSD_CRTBEGIN.
736 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
737 has been converted to a port (misc/ctm) and will be removed from
738 FreeBSD-13. It is available as a package (ctm) for all supported
742 The default newsyslog.conf(5) file has been changed to only include
743 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
744 the filenames end in '.conf' and do not begin with a '.'.
746 You should check the configuration files in these two directories match
747 this naming convention. You can verify which configuration files are
748 being included using the command:
752 Ports for the DRM modules have been simplified. Now, amd64 users should
753 just install the drm-kmod port. All others should install
756 Graphics hardware that's newer than about 2010 usually works with
757 drm-kmod. For hardware older than 2013, however, some users will need
758 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
759 than 2008 usually only works in drm-legacy-kmod. The graphics team can
760 only commit to hardware made since 2013 due to the complexity of the
761 market and difficulty to test all the older cards effectively. If you
762 have hardware supported by drm-kmod, you are strongly encouraged to use
763 that as you will get better support.
765 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
766 elsewhere, the drm and drm2 modules will be eliminated from the src base
767 soon (with a limited exception for arm). Please update to the package
768 asap and report any issues to x11@freebsd.org.
770 Generally, anybody using the drm*-kmod packages should add
771 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
772 cross-threading surprises, especially with automatic driver
773 loading from X11 startup. These will become the defaults in 13-current
777 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
778 custom kernel and module loading configuration files must be updated
779 accordingly. Moreover, interfaces previous presented as ixlvN to the
780 system are now exposed as iavfN and network configuration files must
781 be adjusted as necessary.
784 OpenSSL has been updated to version 1.1.1. This update included
785 additional various API changes throughout the base system. It is
786 important to rebuild third-party software after upgrading. The value
787 of __FreeBSD_version has been bumped accordingly.
790 The legacy DRM modules and drivers have now been added to the loader's
791 module blacklist, in favor of loading them with kld_list in rc.conf(5).
792 The module blacklist may be overridden with the loader.conf(5)
793 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
797 The cam(4) based nda(4) driver will be used over nvd(4) by default on
798 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
799 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
800 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
804 Reproducible build mode is now on by default, in preparation for
805 FreeBSD 12.0. This eliminates build metadata such as the user,
806 host, and time from the kernel (and uname), unless the working tree
807 corresponds to a modified checkout from a version control system.
808 The previous behavior can be obtained by setting the /etc/src.conf
809 knob WITHOUT_REPRODUCIBLE_BUILD.
812 The Yarrow CSPRNG has been removed from the kernel as it has not been
813 supported by its designers since at least 2003. Fortuna has been the
814 default since FreeBSD-11.
817 devctl freeze/thaw have gone into the tree, the rc scripts have been
818 updated to use them and devmatch has been changed. You should update
819 kernel, userland and rc scripts all at the same time.
822 The default interpreter has been switched from 4th to Lua.
823 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
824 interpreter. If you have custom FORTH code you will need to set
825 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
826 src.conf for the build. This will create default hard links between
827 loader and loader_4th instead of loader and loader_lua, the new default.
828 If you are using UEFI it will create the proper hard link to loader.efi.
830 bhyve uses userboot.so. It remains 4th-only until some issues are solved
831 regarding coexisting with multiple versions of FreeBSD are resolved.
834 ls(1) now respects the COLORTERM environment variable used in other
835 systems and software to indicate that a colored terminal is both
836 supported and desired. If ls(1) is suddenly emitting colors, they may
837 be disabled again by either removing the unwanted COLORTERM from your
838 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
839 may not be observed in a future release.
842 The default pager for most commands has been changed to "less". To
843 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
847 The jedec_ts(4) driver has been removed. A superset of its functionality
848 is available in the jedec_dimm(4) driver, and the manpage for that
849 driver includes migration instructions. If you have "device jedec_ts"
850 in your kernel configuration file, it must be removed.
853 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
854 This should have no effect if the kernel is booted via BIOS/legacy boot.
855 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
856 has a buggy firmware that prevents a successful boot due to use of
860 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
861 support has been removed from the tree. These ports were
862 obsolete and/or known to be broken for many years.
865 loader.efi has been augmented to participate more fully in the
866 UEFI boot manager protocol. loader.efi will now look at the
867 BootXXXX environment variable to determine if a specific kernel
868 or root partition was specified. XXXX is derived from BootCurrent.
869 efibootmgr(8) manages these standard UEFI variables.
872 zfsloader's functionality has now been folded into loader.
873 zfsloader is no longer necessary once you've updated your
874 boot blocks. For a transition period, we will install a
875 hardlink for zfsloader to loader to allow a smooth transition
876 until the boot blocks can be updated (hard link because old
877 zfs boot blocks don't understand symlinks).
880 ARM64 now have efifb support, if you want to have serial console
881 on your arm64 board when an screen is connected and the bootloader
882 setup a frame buffer for us to use, just add :
886 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
887 an screen connected as the firmware will setup a frame buffer are that
888 u-boot will expose as an EFI frame buffer.
891 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
892 or take steps to update /etc/passwd before doing installworld on
893 existing systems. Do not skip the "mergemaster -Fp" step before
894 installworld, as described in the update procedures near the bottom
895 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
896 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
897 the ntp config file contain options that change file/dir locations.
898 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
899 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
900 taking steps to ensure that all required files/dirs are accessible
904 Big endian arm support has been removed.
907 The static environment setup in kernel configs is no longer mutually
908 exclusive with the loader(8) environment by default. In order to
909 restore the previous default behavior of disabling the loader(8)
910 environment if a static environment is present, you must specify
911 loader_env.disabled=1 in the static environment.
914 The ABI of syscalls used by management tools like sockstat and
915 netstat has been broken to allow 32-bit binaries to work on
916 64-bit kernels without modification. These programs will need
917 to match the kernel in order to function. External programs may
918 require minor modifications to accommodate a change of type in
919 structures from pointers to 64-bit virtual addresses.
922 On i386 and amd64 atomics are now inlined. Out of tree modules using
923 atomics will need to be rebuilt.
926 The '%I' format in the kern.corefile sysctl limits the number of
927 core files that a process can generate to the number stored in the
928 debug.ncores sysctl. The '%I' format is replaced by the single digit
929 index. Previously, if all indexes were taken the kernel would overwrite
930 only a core file with the highest index in a filename.
931 Currently the system will create a new core file if there is a free
932 index or if all slots are taken it will overwrite the oldest one.
935 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
936 6.0.1. Please see the 20141231 entry below for information about
937 prerequisites and upgrading, if you are not already using clang 3.5.0
941 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
942 needed to be changed to work with it. This change was made with r335763
943 and requires a mergemaster / etcupdate / etc to update the installed
947 r334930 changed the interface between the NFS modules, so they all
948 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
951 As of r334391 lld is the default amd64 system linker; it is installed
952 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
956 The kernel / userland interface for devinfo changed, so you'll
957 need a new kernel and userland as a pair for it to work (rebuilding
958 lib/libdevinfo is all that's required). devinfo and devmatch will
959 not work, but everything else will when there's a mismatch.
962 The on-disk format for hwpmc callchain records has changed to include
963 threadid corresponding to a given record. This changes the field offsets
964 and thus requires that libpmcstat be rebuilt before using a kernel
968 The vxge(4) driver has been removed. This driver was introduced into
969 HEAD one week before the Exar left the Ethernet market and is not
970 known to be used. If you have device vxge in your kernel config file
974 The amd64 kernel now requires a ld that supports ifunc to produce a
975 working kernel, either lld or a newer binutils. lld is built by default
976 on amd64, and the 'buildkernel' target uses it automatically. However,
977 it is not the default linker, so building the kernel the traditional
978 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
979 binutils port/package). lld will soon be default, and this requirement
982 NOTE: As of r334391 lld is the default system linker on amd64, and no
983 workaround is necessary.
986 The nxge(4) driver has been removed. This driver was for PCI-X 10g
987 cards made by s2io/Neterion. The company was acquired by Exar and
988 no longer sells or supports Ethernet products. If you have device
989 nxge in your kernel config file it must be removed.
992 The tz database (tzdb) has been updated to 2018e. This version more
993 correctly models time stamps in time zones with negative DST such as
994 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
995 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
996 time zone abbreviations and the tm_isdst flag.
999 The ixgb(4) driver has been removed. This driver was for an early and
1000 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
1001 quickly shifted to the long lived ixgbe family. If you have device
1002 ixgb in your kernel config file it must be removed.
1005 The lmc(4) driver has been removed. This was a WAN interface
1006 card that was already reportedly rare in 2003, and had an ambiguous
1007 license. If you have device lmc in your kernel config file it must
1011 Support for Arcnet networks has been removed. If you have device
1012 arcnet or device cm in your kernel config file they must be
1016 Support for FDDI networks has been removed. If you have device
1017 fddi or device fpa in your kernel config file they must be
1021 In addition to supporting RFC 3164 formatted messages, the
1022 syslogd(8) service is now capable of parsing RFC 5424 formatted
1023 log messages. The main benefit of using RFC 5424 is that clients
1024 may now send log messages with timestamps containing year numbers,
1025 microseconds and time zone offsets.
1027 Similarly, the syslog(3) C library function has been altered to
1028 send RFC 5424 formatted messages to the local system logging
1029 daemon. On systems using syslogd(8), this change should have no
1030 negative impact, as long as syslogd(8) and the C library are
1031 updated at the same time. On systems using a different system
1032 logging daemon, it may be necessary to make configuration
1033 adjustments, depending on the software used.
1035 When using syslog-ng, add the 'syslog-protocol' flag to local
1036 input sources to enable parsing of RFC 5424 formatted messages:
1039 unix-dgram("/var/run/log" flags(syslog-protocol));
1042 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
1043 of the 'imuxsock' module to let messages be processed by the
1044 regular RFC 3164/5424 parsing pipeline:
1046 module(load="imuxsock" SysSock.UseSpecialParser="off")
1048 Do note that these changes only affect communication between local
1049 applications and syslogd(8). The format that syslogd(8) uses to
1050 store messages on disk or forward messages to other systems
1051 remains unchanged. syslogd(8) still uses RFC 3164 for these
1052 purposes. Options to customize this behaviour will be added in the
1053 future. Utilities that process log files stored in /var/log are
1054 thus expected to continue to function as before.
1056 __FreeBSD_version has been incremented to 1200061 to denote this
1060 Support for token ring networks has been removed. If you
1061 have "device token" in your kernel config you should remove
1062 it. No device drivers supported token ring.
1065 makefs was modified to be able to tag ISO9660 El Torito boot catalog
1066 entries as EFI instead of overloading the i386 tag as done previously.
1067 The amd64 mkisoimages.sh script used to build amd64 ISO images for
1068 release was updated to use this. This may mean that makefs must be
1069 updated before "make cdrom" can be run in the release directory. This
1070 should be as simple as:
1072 $ cd $SRCDIR/usr.sbin/makefs
1073 $ make depend all install
1076 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
1077 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
1078 Co-existence for the transition period will come shortly. Booting is a
1079 complex environment and test coverage for Lua-enabled loaders has been
1080 thin, so it would be prudent to assume it might not work and make
1081 provisions for backup boot methods.
1084 devmatch functionality has been turned on in devd. It will automatically
1085 load drivers for unattached devices. This may cause unexpected drivers
1086 to be loaded. Please report any problems to current@ and
1090 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
1091 6.0.0. Please see the 20141231 entry below for information about
1092 prerequisites and upgrading, if you are not already using clang 3.5.0
1096 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
1097 This means it is used to link the kernel and userland libraries and
1098 executables, but is not yet installed as /usr/bin/ld by default.
1100 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
1101 WITHOUT_LLD_BOOTSTRAP=yes
1104 On i386, pmtimer has been removed. Its functionality has been folded
1105 into apm. It was a no-op on ACPI in current for a while now (but was
1106 still needed on i386 in FreeBSD 11 and earlier). Users may need to
1107 remove it from kernel config files.
1110 The use of RSS hash from the network card aka flowid has been
1111 disabled by default for lagg(4) as it's currently incompatible with
1112 the lacp and loadbalance protocols.
1114 This can be re-enabled by setting the following in loader.conf:
1115 net.link.lagg.default_use_flowid="1"
1118 The SW_WATCHDOG option is no longer necessary to enable the
1119 hardclock-based software watchdog if no hardware watchdog is
1120 configured. As before, SW_WATCHDOG will cause the software
1121 watchdog to be enabled even if a hardware watchdog is configured.
1124 r326887 fixes the issue described in the 20171214 UPDATING entry.
1125 r326888 flips the switch back to building GELI support always.
1128 r362593 broke ZFS + GELI support for reasons unknown. However,
1129 it also broke ZFS support generally, so GELI has been turned off
1130 by default as the lesser evil in r326857. If you boot off ZFS and/or
1131 GELI, it might not be a good time to update.
1134 PowerPC users must update loader(8) by rebuilding world before
1135 installing a new kernel, as the protocol connecting them has
1136 changed. Without the update, loader metadata will not be passed
1137 successfully to the kernel and users will have to enter their
1138 root partition at the kernel mountroot prompt to continue booting.
1139 Newer versions of loader can boot old kernels without issue.
1142 The LOADER_FIREWIRE_SUPPORT build variable has been renamed to
1143 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
1144 to WITH/OUT_LOADER_GELI.
1147 The naive and non-compliant support of posix_fallocate(2) in ZFS
1148 has been removed as of r325320. The system call now returns EINVAL
1149 when used on a ZFS file. Although the new behavior complies with the
1150 standard, some consumers are not prepared to cope with it.
1151 One known victim is lld prior to r325420.
1154 Building in a FreeBSD src checkout will automatically create object
1155 directories now rather than store files in the current directory if
1156 'make obj' was not ran. Calling 'make obj' is no longer necessary.
1157 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
1158 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
1162 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
1163 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
1164 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
1165 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
1166 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
1167 The UNIFIED_OBJDIR option is a transitional feature that will be
1168 removed for 12.0 release; please migrate to the new format for any
1169 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
1170 than hardcoding paths.
1173 The native-xtools target no longer installs the files by default to the
1174 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
1175 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
1178 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
1179 options are changing from controlling the build if defined / undefined
1180 to controlling the build with explicit 'yes' or 'no' values. They will
1181 shift to WITH/WITHOUT options to match other options in the system.
1184 libstand has turned into a private library for sys/boot use only.
1185 It is no longer supported as a public interface outside of sys/boot.
1188 The arm port has split armv6 into armv6 and armv7. armv7 is now
1189 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
1190 and are running a kernel from before r324363, you will need to add
1191 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
1194 When building multiple kernels using KERNCONF, non-existent KERNCONF
1195 files will produce an error and buildkernel will fail. Previously
1196 missing KERNCONF files silently failed giving no indication as to
1197 why, only to subsequently discover during installkernel that the
1198 desired kernel was never built in the first place.
1201 The default serial number format for CTL LUNs has changed. This will
1202 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
1203 or iSCSI clients care about their LUNs' serial numbers. Users who
1204 require serial number stability should hardcode serial numbers in
1208 For 32-bit arm compiled for hard-float support, soft-floating point
1209 binaries now always get their shared libraries from
1210 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
1211 /usr/libsoft also existed). Only users with a hard-float ld.so, but
1212 soft-float everything else should be affected.
1215 The geli password typed at boot is now hidden. To restore the previous
1216 behavior, see geli(8) for configuration options.
1219 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
1220 sysctl values. Minor nit, but requires a rebuild of both world/kernel
1224 "make check" behavior (made in ^/head@r295380) has been changed to
1225 execute from a limited sandbox, as opposed to executing from
1229 - The "beforecheck" and "aftercheck" targets are now specified.
1230 - ${CHECKDIR} (added in commit noted above) has been removed.
1231 - Legacy behavior can be enabled by setting
1232 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
1234 If the limited sandbox mode is enabled, "make check" will execute
1235 "make distribution", then install, execute the tests, and clean up the
1236 sandbox if successful.
1238 The "make distribution" and "make install" targets are typically run as
1239 root to set appropriate permissions and ownership at installation time.
1240 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
1241 environment if executing "make check" with limited sandbox mode using
1242 an unprivileged user.
1245 Since the switch to GPT disk labels, fsck for UFS/FFS has been
1246 unable to automatically find alternate superblocks. As of r322297,
1247 the information needed to find alternate superblocks has been
1248 moved to the end of the area reserved for the boot block.
1249 Filesystems created with a newfs of this vintage or later
1250 will create the recovery information. If you have a filesystem
1251 created prior to this change and wish to have a recovery block
1252 created for your filesystem, you can do so by running fsck in
1253 foreground mode (i.e., do not use the -p or -y options). As it
1254 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
1255 to which you should answer yes.
1258 As of r321665, an NFSv4 server configuration that services
1259 Kerberos mounts or clients that do not support the uid/gid in
1260 owner/owner_group string capability, must explicitly enable
1261 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
1262 machine's /etc/rc.conf file.
1265 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
1266 Please see the 20141231 entry below for information about prerequisites
1267 and upgrading, if you are not already using clang 3.5.0 or higher.
1270 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
1271 r-commands (rlogin, rsh, etc.) to be built with the base system.
1274 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
1275 a very major ABI incompatible change, so users of FreeBSD/powerpc must
1276 be careful when performing source upgrades. It is best to run
1277 'make installworld' from an alternate root system, either a live
1278 CD/memory stick, or a temporary root partition. Additionally, all ports
1279 must be recompiled. powerpc64 is largely unaffected, except in the case
1280 of 32-bit compatibility. All 32-bit binaries will be affected.
1283 Forward compatibility for the "ino64" project have been committed. This
1284 will allow most new binaries to run on older kernels in a limited
1285 fashion. This prevents many of the common foot-shooting actions in the
1286 upgrade as well as the limited ability to roll back the kernel across
1287 the ino64 upgrade. Complicated use cases may not work properly, though
1288 enough simpler ones work to allow recovery in most situations.
1291 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
1292 if you require the GPL compiler.
1295 The internal ABI used for communication between the NFS kernel modules
1296 was changed by r320085, so __FreeBSD_version was bumped to
1297 ensure all the NFS related modules are updated together.
1300 The ABI of struct event was changed by extending the data
1301 member to 64bit and adding ext fields. For upgrade, same
1302 precautions as for the entry 20170523 "ino64" must be
1306 The GNU roff toolchain has been removed from base. To render manpages
1307 which are not supported by mandoc(1), man(1) can fallback on GNU roff
1308 from ports (and recommends to install it).
1309 To render roff(7) documents, consider using GNU roff from ports or the
1310 heirloom doctools roff toolchain from ports via pkg install groff or
1311 via pkg install heirloom-doctools.
1314 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
1315 smaller runtime footprint builds. This is useful for embedded systems
1316 which only require one chipset support.
1318 If you load it as a module, make sure this is in /boot/loader.conf:
1322 This will load the HAL, all chip/RF backends and if_ath_pci.
1323 If you have if_ath_pci in /boot/loader.conf, ensure it is after
1324 if_ath or it will not load any HAL chipset support.
1326 If you want to selectively load things (eg on cheaper ARM/MIPS
1327 platforms where RAM is at a premium) you should:
1330 * load the chip modules in question
1331 * load ath_rate, ath_dfs
1333 * load if_ath_pci and/or if_ath_ahb depending upon your particular
1334 bus bind type - this is where probe/attach is done.
1336 For further comments/feedback, poke adrian@ .
1339 The "ino64" 64-bit inode project has been committed, which extends
1340 a number of types to 64 bits. Upgrading in place requires care and
1341 adherence to the documented upgrade procedure.
1343 If using a custom kernel configuration ensure that the
1344 COMPAT_FREEBSD11 option is included (as during the upgrade the
1345 system will be running the ino64 kernel with the existing world).
1347 For the safest in-place upgrade begin by removing previous build
1348 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full
1349 procedure documented below under the heading "To rebuild everything and
1350 install it on the current system." Specifically, a reboot is required
1351 after installing the new kernel before installing world. While an
1352 installworld normally works by accident from multiuser after rebooting
1353 the proper kernel, there are many cases where this will fail across this
1354 upgrade and installworld from single user is required.
1357 The NATM framework including the en(4), fatm(4), hatm(4), and
1358 patm(4) devices has been removed. Consumers should plan a
1359 migration before the end-of-life date for FreeBSD 11.
1362 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
1363 diff has not been implemented, if those are needed a newer version of
1364 GNU diff is available via the diffutils package under the gdiff name.
1367 As of r316810 for ipfilter, keep frags is no longer assumed when
1368 keep state is specified in a rule. r316810 aligns ipfilter with
1369 documentation in man pages separating keep frags from keep state.
1370 This allows keep state to be specified without forcing keep frags
1371 and allows keep frags to be specified independently of keep state.
1372 To maintain previous behaviour, also specify keep frags with
1373 keep state (as documented in ipf.conf.5).
1376 arm64 builds now use the base system LLD 4.0.0 linker by default,
1377 instead of requiring that the aarch64-binutils port or package be
1378 installed. To continue using aarch64-binutils, set
1379 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
1382 The UDP optimization in entry 20160818 that added the sysctl
1383 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
1384 packets will no longer be treated as L3 broadcast packets.
1387 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
1388 use any explicitly assigned loopback address available in the jail
1389 instead of using the first assigned address of the jail.
1392 The ctl.ko module no longer implements the iSCSI target frontend:
1393 cfiscsi.ko does instead.
1395 If building cfiscsi.ko as a kernel module, the module can be loaded
1396 via one of the following methods:
1397 - `cfiscsi_load="YES"` in loader.conf(5).
1398 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
1399 - ctladm(8)/ctld(8), when compiled with iSCSI support
1400 (`WITH_ISCSI=yes` in src.conf(5))
1402 Please see cfiscsi(4) for more details.
1405 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
1406 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
1407 same source (previously, the dependency of mmcsd.ko on mmc.ko was
1408 missing, but mmcsd.ko now will refuse to load if it is incompatible
1412 The syntax of ipfw(8) named states was changed to avoid ambiguity.
1413 If you have used named states in the firewall rules, you need to modify
1414 them after installworld and before rebooting. Now named states must
1415 be prefixed with colon.
1418 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
1419 removed as the userland we provide cannot use them. The KMS version
1420 (sys/dev/drm2) supports the same hardware.
1423 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
1424 Please see the 20141231 entry below for information about prerequisites
1425 and upgrading, if you are not already using clang 3.5.0 or higher.
1428 The code that provides support for ZFS .zfs/ directory functionality
1429 has been reimplemented. It's not possible now to create a snapshot
1430 by mkdir under .zfs/snapshot/. That should be the only user visible
1434 EISA bus support has been removed. The WITH_EISA option is no longer
1438 MCA bus support has been removed.
1441 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
1442 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
1445 The EM_MULTIQUEUE kernel configuration option is deprecated now that
1446 the em(4) driver conforms to iflib specifications.
1449 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
1450 IFLIB. If you have a custom kernel configuration that excludes em(4)
1451 but you use igb(4), you need to re-add em(4) to your custom
1455 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
1456 Please see the 20141231 entry below for information about prerequisites
1457 and upgrading, if you are not already using clang 3.5.0 or higher.
1460 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
1461 Please see the 20141231 entry below for information about prerequisites
1462 and upgrading, if you are not already using clang 3.5.0 or higher.
1465 The layout of the pmap structure has changed for powerpc to put the pmap
1466 statistics at the front for all CPU variations. libkvm(3) and all tools
1467 that link against it need to be recompiled.
1470 isl(4) and cyapa(4) drivers now require a new driver,
1471 chromebook_platform(4), to work properly on Chromebook-class hardware.
1472 On other types of hardware the drivers may need to be configured using
1473 device hints. Please see the corresponding manual pages for details.
1476 The urtwn(4) driver was merged into rtwn(4) and now consists of
1477 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
1479 Also, firmware for RTL8188CE was renamed due to possible name
1480 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
1483 GNU rcs has been removed from base. It is available as packages:
1484 - rcs: Latest GPLv3 GNU rcs version.
1485 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
1489 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
1490 modules now requires that the kernel configuration contain the
1491 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
1494 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
1495 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
1498 Relocatable object files with the extension of .So have been renamed
1499 to use an extension of .pico instead. The purpose of this change is
1500 to avoid a name clash with shared libraries on case-insensitive file
1501 systems. On those file systems, foo.So is the same file as foo.so.
1504 GNU rcs has been turned off by default. It can (temporarily) be built
1505 again by adding WITH_RCS knob in src.conf.
1506 Otherwise, GNU rcs is available from packages:
1507 - rcs: Latest GPLv3 GNU rcs version.
1508 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
1511 The backup_uses_rcs functionality has been removed from rc.subr.
1514 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
1515 two separate components, QUEUE_MACRO_DEBUG_TRACE and
1516 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
1517 QUEUE_MACRO_DEBUG behavior.
1520 r304787 changed some ioctl interfaces between the iSCSI userspace
1521 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1522 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1526 The UDP receive code has been updated to only treat incoming UDP
1527 packets that were addressed to an L2 broadcast address as L3
1528 broadcast packets. It is not expected that this will affect any
1529 standards-conforming UDP application. The new behaviour can be
1530 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1534 Remove the openbsd_poll system call.
1535 __FreeBSD_version has been bumped because of this.
1538 The stable/11 branch has been created from head@r302406.
1541 The libc stub for the pipe(2) system call has been replaced with
1542 a wrapper that calls the pipe2(2) system call and the pipe(2)
1543 system call is now only implemented by the kernels that include
1544 "options COMPAT_FREEBSD10" in their config file (this is the
1545 default). Users should ensure that this option is enabled in
1546 their kernel or upgrade userspace to r302092 before upgrading their
1550 CAM now strips the leading spaces from each SCSI disk's serial number.
1551 This will affect users who create UFS filesystems on SCSI disks using
1552 those disk's diskid device nodes. For example, if /etc/fstab
1553 previously contained a line like
1554 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
1555 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
1556 transforms like gmirror may also be affected. ZFS users should
1560 The bitstring(3) API has been updated with new functionality and
1561 improved performance. But it is binary-incompatible with the old API.
1562 Objects built with the new headers may not be linked against objects
1563 built with the old headers.
1566 The brk and sbrk functions have been removed from libc on arm64.
1567 Binutils from ports has been updated to not link to these
1568 functions and should be updated to the latest version before
1569 installing a new libc.
1572 The armv6 port now defaults to hard float ABI. Limited support
1573 for running both hardfloat and soft float on the same system
1574 is available using the libraries installed with -DWITH_LIBSOFT.
1575 This has only been tested as an upgrade path for installworld
1576 and packages may fail or need manual intervention to run. New
1577 packages will be needed.
1579 To update an existing self-hosted armv6hf system, you must add
1580 TARGET_ARCH=armv6 on the make command line for both the build
1581 and the install steps.
1584 Kernel modules compiled outside of a kernel build now default to
1585 installing to /boot/modules instead of /boot/kernel. Many kernel
1586 modules built this way (such as those in ports) already overrode
1587 KMODDIR explicitly to install into /boot/modules. However,
1588 manually building and installing a module from /sys/modules will
1589 now install to /boot/modules instead of /boot/kernel.
1592 The CAM I/O scheduler has been committed to the kernel. There should be
1593 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1594 list of known rogues that claim support for this but actually corrupt
1595 data is believed to be complete, be on the lookout for data
1596 corruption. The known rogue list is believed to be complete:
1598 o Crucial MX100, M550 drives with MU01 firmware.
1599 o Micron M510 and M550 drives with MU01 firmware.
1600 o Micron M500 prior to MU07 firmware
1601 o Samsung 830, 840, and 850 all firmwares
1602 o FCCT M500 all firmwares
1604 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1605 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1606 updated firmware. Black listed drives will work correctly because these
1607 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1608 this list is the same as found in Linux, it's believed there are no
1609 other rogues in the market place. All other models from the above
1612 To be safe, if you are at all concerned, you can quirk each of your
1613 drives to prevent NCQ from being sent by setting:
1614 kern.cam.ada.X.quirks="0x2"
1615 in loader.conf. If the drive requires the 4k sector quirk, set the
1616 quirks entry to 0x3.
1619 The FAST_DEPEND build option has been removed and its functionality is
1620 now the one true way. The old mkdep(1) style of 'make depend' has
1621 been removed. See 20160311 for further details.
1624 Resource range types have grown from unsigned long to uintmax_t. All
1625 drivers, and anything using libdevinfo, need to be recompiled.
1628 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1629 builds. It no longer runs mkdep(1) during 'make depend', and the
1630 'make depend' stage can safely be skipped now as it is auto ran
1631 when building 'make all' and will generate all SRCS and DPSRCS before
1632 building anything else. Dependencies are gathered at compile time with
1633 -MF flags kept in separate .depend files per object file. Users should
1634 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1635 stale .depend files.
1638 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1639 kernel modules. Therefore, if you load any kernel modules at boot time,
1640 please install the boot loaders after you install the kernel, but before
1644 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1645 make installkernel KERNCONF=YOUR_KERNEL_HERE
1646 make -C sys/boot install
1647 <reboot in single user>
1649 Then follow the usual steps, described in the General Notes section,
1653 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1654 see the 20141231 entry below for information about prerequisites and
1655 upgrading, if you are not already using clang 3.5.0 or higher.
1658 The AIO subsystem is now a standard part of the kernel. The
1659 VFS_AIO kernel option and aio.ko kernel module have been removed.
1660 Due to stability concerns, asynchronous I/O requests are only
1661 permitted on sockets and raw disks by default. To enable
1662 asynchronous I/O requests on all file types, set the
1663 vfs.aio.enable_unsafe sysctl to a non-zero value.
1666 The ELF object manipulation tool objcopy is now provided by the
1667 ELF Tool Chain project rather than by GNU binutils. It should be a
1668 drop-in replacement, with the addition of arm64 support. The
1669 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1670 to obtain the GNU version if necessary.
1673 Building ZFS pools on top of zvols is prohibited by default. That
1674 feature has never worked safely; it's always been prone to deadlocks.
1675 Using a zvol as the backing store for a VM guest's virtual disk will
1676 still work, even if the guest is using ZFS. Legacy behavior can be
1677 restored by setting vfs.zfs.vol.recursive=1.
1680 The NONE and HPN patches has been removed from OpenSSH. They are
1681 still available in the security/openssh-portable port.
1684 With the addition of ypldap(8), a new _ypldap user is now required
1685 during installworld. "mergemaster -p" can be used to add the user
1686 prior to installworld, as documented in the handbook.
1689 The tftp loader (pxeboot) now uses the option root-path directive. As a
1690 consequence it no longer looks for a pxeboot.4th file on the tftp
1691 server. Instead it uses the regular /boot infrastructure as with the
1695 The code to start recording plug and play data into the modules has
1696 been committed. While the old tools will properly build a new kernel,
1697 a number of warnings about "unknown metadata record 4" will be produced
1698 for an older kldxref. To avoid such warnings, make sure to rebuild
1699 the kernel toolchain (or world). Make sure that you have r292078 or
1700 later when trying to build 292077 or later before rebuilding.
1703 Debug data files are now built by default with 'make buildworld' and
1704 installed with 'make installworld'. This facilitates debugging but
1705 requires more disk space both during the build and for the installed
1706 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1710 r291527 changed the internal interface between the nfsd.ko and
1711 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1712 __FreeBSD_version has been bumped because of this.
1715 Add support for unicode collation strings leads to a change of
1716 order of files listed by ls(1) for example. To get back to the old
1717 behaviour, set LC_COLLATE environment variable to "C".
1719 Databases administrators will need to reindex their databases given
1720 collation results will be different.
1722 Due to a bug in install(1) it is recommended to remove the ancient
1723 locales before running make installworld.
1725 rm -rf /usr/share/locale/*
1728 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1729 libcrypto.so.7 or libssl.so.7 must be recompiled.
1732 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1733 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1734 should be replaced with isp_2400 and isp_2500 modules respectively.
1737 The build previously allowed using 'make -n' to not recurse into
1738 sub-directories while showing what commands would be executed, and
1739 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1740 and 'make -N' will not.
1743 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1744 and etcupdate will now use this file. A custom sendmail.cf is now
1745 updated via this mechanism rather than via installworld. If you had
1746 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1747 want to remove the exclusion or change it to "always install".
1748 /etc/mail/sendmail.cf is now managed the same way regardless of
1749 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1750 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1753 Compatibility shims for legacy ATA device names have been removed.
1754 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1755 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1756 environment variables, /dev/ad* and /dev/ar* symbolic links.
1759 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1760 Please see the 20141231 entry below for information about prerequisites
1761 and upgrading, if you are not already using clang 3.5.0 or higher.
1764 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1765 and renamed from .symbols to .debug. This reduces the size requirements
1766 on the boot partition or file system and provides consistency with
1767 userland debug files.
1769 When using the supported kernel installation method the
1770 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1771 as is done with /boot/kernel.
1773 Developers wishing to maintain the historical behavior of installing
1774 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1777 The wireless drivers had undergone changes that remove the 'parent
1778 interface' from the ifconfig -l output. The rc.d network scripts
1779 used to check presence of a parent interface in the list, so old
1780 scripts would fail to start wireless networking. Thus, etcupdate(3)
1781 or mergemaster(8) run is required after kernel update, to update your
1782 rc.d scripts in /etc.
1785 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1786 These configurations are now automatically interpreted as
1787 'scrub fragment reassemble'.
1790 Kernel-loadable modules for the random(4) device are back. To use
1791 them, the kernel must have
1794 options RANDOM_LOADABLE
1796 kldload(8) can then be used to load random_fortuna.ko
1797 or random_yarrow.ko. Please note that due to the indirect
1798 function calls that the loadable modules need to provide,
1799 the build-in variants will be slightly more efficient.
1801 The random(4) kernel option RANDOM_DUMMY has been retired due to
1802 unpopularity. It was not all that useful anyway.
1805 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1806 Control over building the ELF Tool Chain tools is now provided by
1807 the WITHOUT_TOOLCHAIN knob.
1810 The polarity of Pulse Per Second (PPS) capture events with the
1811 uart(4) driver has been corrected. Prior to this change the PPS
1812 "assert" event corresponded to the trailing edge of a positive PPS
1813 pulse and the "clear" event was the leading edge of the next pulse.
1815 As the width of a PPS pulse in a typical GPS receiver is on the
1816 order of 1 millisecond, most users will not notice any significant
1817 difference with this change.
1819 Anyone who has compensated for the historical polarity reversal by
1820 configuring a negative offset equal to the pulse width will need to
1821 remove that workaround.
1824 The default group assigned to /dev/dri entries has been changed
1825 from 'wheel' to 'video' with the id of '44'. If you want to have
1826 access to the dri devices please add yourself to the video group
1829 # pw groupmod video -m $USER
1832 The menu.rc and loader.rc files will now be replaced during
1833 upgrades. Please migrate local changes to menu.rc.local and
1834 loader.rc.local instead.
1837 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1838 strings and strip have been removed. The src.conf(5) knob
1839 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1842 As ZFS requires more kernel stack pages than is the default on some
1843 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1844 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1846 Please consider using 'options KSTACK_PAGES=X' where X is greater
1847 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1850 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1851 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1852 default, i.e., they will not contain "::". For example, instead
1853 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1854 to have a more specific match, such as different map entries for
1855 IPv6:0:0 vs IPv6:0. This change requires that configuration
1856 data (including maps, files, classes, custom ruleset, etc.) must
1857 use the same format, so make certain such configuration data is
1858 upgrading. As a very simple check search for patterns like
1859 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1860 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1861 the cf option UseCompressedIPv6Addresses.
1864 The default kernel entropy-processing algorithm is now
1865 Fortuna, replacing Yarrow.
1867 Assuming you have 'device random' in your kernel config
1868 file, the configurations allow a kernel option to override
1869 this default. You may choose *ONE* of:
1871 options RANDOM_YARROW # Legacy /dev/random algorithm.
1872 options RANDOM_DUMMY # Blocking-only driver.
1874 If you have neither, you get Fortuna. For most people,
1875 read no further, Fortuna will give a /dev/random that works
1876 like it always used to, and the difference will be irrelevant.
1878 If you remove 'device random', you get *NO* kernel-processed
1879 entropy at all. This may be acceptable to folks building
1880 embedded systems, but has complications. Carry on reading,
1881 and it is assumed you know what you need.
1883 *PLEASE* read random(4) and random(9) if you are in the
1884 habit of tweaking kernel configs, and/or if you are a member
1885 of the embedded community, wanting specific and not-usual
1886 behaviour from your security subsystems.
1888 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1889 random', you will NOT have a functioning /dev/random, and
1890 many cryptographic features will not work, including SSH.
1891 You may also find strange behaviour from the random(3) set
1892 of library functions, in particular sranddev(3), srandomdev(3)
1893 and arc4random(3). The reason for this is that the KERN_ARND
1894 sysctl only returns entropy if it thinks it has some to
1895 share, and with RANDOM_DUMMY or no 'device random' this
1899 An additional fix for the issue described in the 20150614 sendmail
1900 entry below has been committed in revision 284717.
1903 FreeBSD's old make (fmake) has been removed from the system. It is
1904 available as the devel/fmake port or via pkg install fmake.
1907 The fix for the issue described in the 20150614 sendmail entry
1908 below has been committed in revision 284436. The work
1909 around described in that entry is no longer needed unless the
1910 default setting is overridden by a confDH_PARAMETERS configuration
1911 setting of '5' or pointing to a 512 bit DH parameter file.
1914 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1915 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1916 and devel/kyua to version 0.20+ and adjust any calling code to work
1917 with Kyuafile and kyua.
1920 The import of openssl to address the FreeBSD-SA-15:10.openssl
1921 security advisory includes a change which rejects handshakes
1922 with DH parameters below 768 bits. sendmail releases prior
1923 to 8.15.2 (not yet released), defaulted to a 512 bit
1924 DH parameter setting for client connections. To work around
1925 this interoperability, sendmail can be configured to use a
1926 2048 bit DH parameter by:
1928 1. Edit /etc/mail/`hostname`.mc
1929 2. If a setting for confDH_PARAMETERS does not exist or
1930 exists and is set to a string beginning with '5',
1931 replace it with '2'.
1932 3. If a setting for confDH_PARAMETERS exists and is set to
1933 a file path, create a new file with:
1934 openssl dhparam -out /path/to/file 2048
1935 4. Rebuild the .cf file:
1936 cd /etc/mail/; make; make install
1937 5. Restart sendmail:
1938 cd /etc/mail/; make restart
1940 A sendmail patch is coming, at which time this file will be
1944 Generation of legacy formatted entries have been disabled by default
1945 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1946 entries were converted to use the new format by default when the new,
1947 machine independent format have been added and supported since FreeBSD
1950 Please see the pwd_mkdb(8) manual page for further details.
1953 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1954 20141231 entry below for information about prerequisites and upgrading,
1955 if you are not already using 3.5.0 or higher.
1958 TI platform code switched to using vendor DTS files and this update
1959 may break existing systems running on Beaglebone, Beaglebone Black,
1962 - dtb files should be regenerated/reinstalled. Filenames are the
1963 same but content is different now
1964 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1965 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1966 addressing scheme is now pin 25 on /dev/gpioc3.
1967 - Pandaboard: /etc/ttys should be updated, serial console device is
1968 now /dev/ttyu2, not /dev/ttyu0
1971 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1972 If you need the GNU extension from groff soelim(1), install groff
1973 from package: pkg install groff, or via ports: textproc/groff.
1976 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1977 defined in symlink(7); previously symlinks were silently ignored.
1980 The const qualifier has been removed from iconv(3) to comply with
1981 POSIX. The ports tree is aware of this from r384038 onwards.
1984 Libraries specified by LIBADD in Makefiles must have a corresponding
1985 DPADD_<lib> variable to ensure correct dependencies. This is now
1986 enforced in src.libnames.mk.
1989 From legacy ata(4) driver was removed support for SATA controllers
1990 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1991 Kernel modules ataahci and ataadaptec were removed completely,
1992 replaced by ahci and mvs modules respectively.
1995 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1996 the 20141231 entry below for information about prerequisites and
1997 upgrading, if you are not already using 3.5.0 or higher.
2000 The 32-bit PowerPC kernel has been changed to a position-independent
2001 executable. This can only be booted with a version of loader(8)
2002 newer than January 31, 2015, so make sure to update both world and
2003 kernel before rebooting.
2006 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
2007 but before r278950, the RNG was not seeded properly. Immediately
2008 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
2009 ssh keys or openssl keys) that were generated w/ a kernel from that
2010 range. This does not affect programs that directly used /dev/random
2011 or /dev/urandom. All userland uses of arc4random(3) are affected.
2014 The autofs(4) ABI was changed in order to restore binary compatibility
2015 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
2016 with the new kernel.
2019 The powerpc64 kernel has been changed to a position-independent
2020 executable. This can only be booted with a new version of loader(8),
2021 so make sure to update both world and kernel before rebooting.
2024 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
2025 only release, no new features have been added. Please see the 20141231
2026 entry below for information about prerequisites and upgrading, if you
2027 are not already using 3.5.0.
2030 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
2031 taken from the ELF Tool Chain project rather than GNU binutils. They
2032 should be drop-in replacements, with the addition of arm64 support.
2033 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
2034 binutils tools, if necessary. See 20150805 for updated information.
2037 The default Unbound configuration now enables remote control
2038 using a local socket. Users who have already enabled the
2039 local_unbound service should regenerate their configuration
2040 by running "service local_unbound setup" as root.
2043 The GNU texinfo and GNU info pages have been removed.
2044 To be able to view GNU info pages please install texinfo from ports.
2047 Clang, llvm and lldb have been upgraded to 3.5.0 release.
2049 As of this release, a prerequisite for building clang, llvm and lldb is
2050 a C++11 capable compiler and C++11 standard library. This means that to
2051 be able to successfully build the cross-tools stage of buildworld, with
2052 clang as the bootstrap compiler, your system compiler or cross compiler
2053 should either be clang 3.3 or later, or gcc 4.8 or later, and your
2054 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
2057 On any standard FreeBSD 10.x or 11.x installation, where clang and
2058 libc++ are on by default (that is, on x86 or arm), this should work out
2061 On 9.x installations where clang is enabled by default, e.g. on x86 and
2062 powerpc, libc++ will not be enabled by default, so libc++ should be
2063 built (with clang) and installed first. If both clang and libc++ are
2064 missing, build clang first, then use it to build libc++.
2066 On 8.x and earlier installations, upgrade to 9.x first, and then follow
2067 the instructions for 9.x above.
2069 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
2070 default, and do not build clang.
2072 Many embedded systems are resource constrained, and will not be able to
2073 build clang in a reasonable time, or in some cases at all. In those
2074 cases, cross building bootable systems on amd64 is a workaround.
2076 This new version of clang introduces a number of new warnings, of which
2077 the following are most likely to appear:
2081 This warns in two cases, for both C and C++:
2082 * When the code is trying to take the absolute value of an unsigned
2083 quantity, which is effectively a no-op, and almost never what was
2084 intended. The code should be fixed, if at all possible. If you are
2085 sure that the unsigned quantity can be safely cast to signed, without
2086 loss of information or undefined behavior, you can add an explicit
2087 cast, or disable the warning.
2089 * When the code is trying to take an absolute value, but the called
2090 abs() variant is for the wrong type, which can lead to truncation.
2091 If you want to disable the warning instead of fixing the code, please
2092 make sure that truncation will not occur, or it might lead to unwanted
2095 -Wtautological-undefined-compare and
2096 -Wundefined-bool-conversion
2098 These warn when C++ code is trying to compare 'this' against NULL, while
2099 'this' should never be NULL in well-defined C++ code. However, there is
2100 some legacy (pre C++11) code out there, which actively abuses this
2101 feature, which was less strictly defined in previous C++ versions.
2103 Squid and openjdk do this, for example. The warning can be turned off
2104 for C++98 and earlier, but compiling the code in C++11 mode might result
2105 in unexpected behavior; for example, the parts of the program that are
2106 unreachable could be optimized away.
2109 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
2110 kernel sources have been removed. The .h files remain, since some
2111 utilities include them. This will need to be fixed later.
2112 If "mount -t oldnfs ..." is attempted, it will fail.
2113 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
2114 the utilities will report errors.
2117 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
2118 directories to top level SUBDIR variable when their parent
2119 directory is included in LOCAL_DIRS. Users with build systems with
2120 such hierarchies and without SUBDIR entries in the parent
2121 directory Makefiles should add them or add the directories to
2125 faith(4) and faithd(8) have been removed from the base system. Faith
2126 has been obsolete for a very long time.
2129 vt(4), the new console driver, is enabled by default. It brings
2130 support for Unicode and double-width characters, as well as
2131 support for UEFI and integration with the KMS kernel video
2134 You may need to update your console settings in /etc/rc.conf,
2135 most probably the keymap. During boot, /etc/rc.d/syscons will
2136 indicate what you need to do.
2138 vt(4) still has issues and lacks some features compared to
2139 syscons(4). See the wiki for up-to-date information:
2140 https://wiki.freebsd.org/Newcons
2142 If you want to keep using syscons(4), you can do so by adding
2143 the following line to /boot/loader.conf:
2147 pjdfstest has been integrated into kyua as an opt-in test suite.
2148 Please see share/doc/pjdfstest/README for more details on how to
2152 gperf has been removed from the base system for architectures
2153 that use clang. Ports that require gperf will obtain it from the
2157 pjdfstest has been moved from tools/regression/pjdfstest to
2161 At svn r271982, The default linux compat kernel ABI has been adjusted
2162 to 2.6.18 in support of the linux-c6 compat ports infrastructure
2163 update. If you wish to continue using the linux-f10 compat ports,
2164 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
2165 encouraged to update their linux-compat packages to linux-c6 during
2166 their next update cycle.
2169 The ofwfb driver, used to provide a graphics console on PowerPC when
2170 using vt(4), no longer allows mmap() of all physical memory. This
2171 will prevent Xorg on PowerPC with some ATI graphics cards from
2172 initializing properly unless x11-servers/xorg-server is updated to
2176 The xdev targets have been converted to using TARGET and
2177 TARGET_ARCH instead of XDEV and XDEV_ARCH.
2180 The default unbound configuration has been modified to address
2181 issues with reverse lookups on networks that use private
2182 address ranges. If you use the local_unbound service, run
2183 "service local_unbound setup" as root to regenerate your
2184 configuration, then "service local_unbound reload" to load the
2188 The GNU texinfo and GNU info pages are not built and installed
2189 anymore, WITH_INFO knob has been added to allow to built and install
2191 UPDATE: see 20150102 entry on texinfo's removal
2194 The GNU readline library is now an INTERNALLIB - that is, it is
2195 statically linked into consumers (GDB and variants) in the base
2196 system, and the shared library is no longer installed. The
2197 devel/readline port is available for third party software that
2201 The Itanium architecture (ia64) has been removed from the list of
2202 known architectures. This is the first step in the removal of the
2206 Commit r268115 has added NFSv4.1 server support, merged from
2207 projects/nfsv4.1-server. Since this includes changes to the
2208 internal interfaces between the NFS related modules, a full
2209 build of the kernel and modules will be necessary.
2210 __FreeBSD_version has been bumped.
2213 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
2214 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
2215 which differs from the behaviour controlled by this knob.)
2218 Maximal length of the serial number in CTL was increased from 16 to
2219 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
2220 and ctld, need to be rebuilt to work with a new kernel.
2223 The libatf-c and libatf-c++ major versions were downgraded to 0 and
2224 1 respectively to match the upstream numbers. They were out of
2225 sync because, when they were originally added to FreeBSD, the
2226 upstream versions were not respected. These libraries are private
2227 and not yet built by default, so renumbering them should be a
2228 non-issue. However, unclean source trees will yield broken test
2229 programs once the operator executes "make delete-old-libs" after a
2230 "make installworld".
2232 Additionally, the atf-sh binary was made private by moving it into
2233 /usr/libexec/. Already-built shell test programs will keep the
2234 path to the old binary so they will break after "make delete-old"
2237 If you are using WITH_TESTS=yes (not the default), wipe the object
2238 tree and rebuild from scratch to prevent spurious test failures.
2239 This is only needed once: the misnumbered libraries and misplaced
2240 binaries have been added to OptionalObsoleteFiles.inc so they will
2241 be removed during a clean upgrade.
2244 Clang and llvm have been upgraded to 3.4.1 release.
2247 We bogusly installed src.opts.mk in /usr/share/mk. This file should
2248 be removed to avoid issues in the future (and has been added to
2252 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
2253 past, it affected all builds that used the bsd.*.mk files. The old
2254 behavior was a bug, but people may have relied upon it. To get this
2255 behavior back, you can .include /etc/src.conf from /etc/make.conf
2256 (which is still global and isn't changed). This also changes the
2257 behavior of incremental builds inside the tree of individual
2258 directories. Set MAKESYSPATH to ".../share/mk" to do that.
2259 Although this has survived make universe and some upgrade scenarios,
2260 other upgrade scenarios may have broken. At least one form of
2261 temporary breakage was fixed with MAKESYSPATH settings for buildworld
2262 as well... In cases where MAKESYSPATH isn't working with this
2263 setting, you'll need to set it to the full path to your tree.
2265 One side effect of all this cleaning up is that bsd.compiler.mk
2266 is no longer implicitly included by bsd.own.mk. If you wish to
2267 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
2271 The lindev device has been removed since /dev/full has been made a
2272 standard device. __FreeBSD_version has been bumped.
2275 The knob WITHOUT_VI was added to the base system, which controls
2276 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
2277 in order to reorder files share/termcap and didn't build ex(1) as a
2278 build tool, so building/installing with WITH_VI is highly advised for
2279 build hosts for older releases.
2281 This issue has been fixed in stable/9 and stable/10 in r277022 and
2282 r276991, respectively.
2285 The YES_HESIOD knob has been removed. It has been obsolete for
2286 a decade. Please move to using WITH_HESIOD instead or your builds
2287 will silently lack HESIOD.
2290 The uart(4) driver has been changed with respect to its handling
2291 of the low-level console. Previously the uart(4) driver prevented
2292 any process from changing the baudrate or the CLOCAL and HUPCL
2293 control flags. By removing the restrictions, operators can make
2294 changes to the serial console port without having to reboot.
2295 However, when getty(8) is started on the serial device that is
2296 associated with the low-level console, a misconfigured terminal
2297 line in /etc/ttys will now have a real impact.
2298 Before upgrading the kernel, make sure that /etc/ttys has the
2299 serial console device configured as 3wire without baudrate to
2300 preserve the previous behaviour. E.g:
2301 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
2304 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
2305 to improve performance. To re-enable it, if needed, run rpcbind
2306 with command line option -W.
2309 Switched back to the GPL dtc compiler due to updates in the upstream
2310 dts files not being supported by the BSDL dtc compiler. You will need
2311 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
2312 may result while building dtb files during a kernel build if you fail
2313 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
2316 Clang and llvm have been upgraded to 3.4 release.
2319 The nve(4) driver has been removed. Please use the nfe(4) driver
2320 for NVIDIA nForce MCP Ethernet adapters instead.
2323 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
2324 This could cause certain C++ applications using shared libraries built
2325 against the previous version of libc++ to crash. The incompatibility
2326 has now been fixed, but any C++ applications or shared libraries built
2327 between r261283 and r261801 should be recompiled.
2330 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
2331 capability mode support. Please note that enabling the feature in
2332 kernel is still highly recommended.
2335 OpenSSH is now built with sandbox support, and will use sandbox as
2336 the default privilege separation method. This requires Capsicum
2337 capability mode support in kernel.
2340 The libelf and libdwarf libraries have been updated to newer
2341 versions from upstream. Shared library version numbers for
2342 these two libraries were bumped. Any ports or binaries
2343 requiring these two libraries should be recompiled.
2344 __FreeBSD_version is bumped to 1100006.
2347 If a Makefile in a tests/ directory was auto-generating a Kyuafile
2348 instead of providing an explicit one, this would prevent such
2349 Makefile from providing its own Kyuafile in the future during
2350 NO_CLEAN builds. This has been fixed in the Makefiles but manual
2351 intervention is needed to clean an objdir if you use NO_CLEAN:
2352 # find /usr/obj -name Kyuafile | xargs rm -f
2355 The behavior of gss_pseudo_random() for the krb5 mechanism
2356 has changed, for applications requesting a longer random string
2357 than produced by the underlying enctype's pseudo-random() function.
2358 In particular, the random string produced from a session key of
2359 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
2360 be different at the 17th octet and later, after this change.
2361 The counter used in the PRF+ construction is now encoded as a
2362 big-endian integer in accordance with RFC 4402.
2363 __FreeBSD_version is bumped to 1100004.
2366 The WITHOUT_ATF build knob has been removed and its functionality
2367 has been subsumed into the more generic WITHOUT_TESTS. If you were
2368 using the former to disable the build of the ATF libraries, you
2369 should change your settings to use the latter.
2372 The default version of mtree is nmtree which is obtained from
2373 NetBSD. The output is generally the same, but may vary
2374 slightly. If you found you need identical output adding
2375 "-F freebsd9" to the command line should do the trick. For the
2376 time being, the old mtree is available as fmtree.
2379 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
2380 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
2381 1.1.4_8 and verify bsdyml not linked in, before running "make
2383 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
2385 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
2388 The stable/10 branch has been created in subversion from head
2395 Sometimes, obscure build problems are the result of environment
2396 poisoning. This can happen because the make utility reads its
2397 environment when searching for values for global variables. To run
2398 your build attempts in an "environmental clean room", prefix all make
2399 commands with 'env -i '. See the env(1) manual page for more details.
2400 Occasionally a build failure will occur with "make -j" due to a race
2401 condition. If this happens try building again without -j, and please
2402 report a bug if it happens consistently.
2404 When upgrading from one major version to another it is generally best to
2405 upgrade to the latest code in the currently installed branch first, then
2406 do an upgrade to the new branch. This is the best-tested upgrade path,
2407 and has the highest probability of being successful. Please try this
2408 approach if you encounter problems with a major version upgrade. Since
2409 the stable 4.x branch point, one has generally been able to upgrade from
2410 anywhere in the most recent stable branch to head / current (or even the
2411 last couple of stable branches). See the top of this file when there's
2414 The update process will emit an error on an attempt to perform a build
2415 or install from a FreeBSD version below the earliest supported version.
2416 When updating from an older version the update should be performed one
2417 major release at a time, including running `make delete-old` at each
2420 When upgrading a live system, having a root shell around before
2421 installing anything can help undo problems. Not having a root shell
2422 around can lead to problems if pam has changed too much from your
2423 starting point to allow continued authentication after the upgrade.
2425 This file should be read as a log of events. When a later event changes
2426 information of a prior event, the prior event should not be deleted.
2427 Instead, a pointer to the entry with the new information should be
2428 placed in the old entry. Readers of this file should also sanity check
2429 older entries before relying on them blindly. Authors of new entries
2430 should write them with this in mind.
2434 When upgrading the boot ZFS pool to a new version, always follow
2437 1.) recompile and reinstall the ZFS boot loader and boot block
2438 (this is part of "make buildworld" and "make installworld")
2440 2.) update the ZFS boot block on your boot drive
2442 The following example updates the ZFS boot block on the
2443 freebsd-boot partition of a GPT partitioned drive ada0:
2444 "gpart bootcode -p /boot/gptzfsboot -i $N ada0"
2445 The value $N will typically be 1 (if booting from BIOS) or 2 (if
2448 Non-boot pools do not need these updates.
2452 If you are updating from a prior version of FreeBSD (even one just
2453 a few days old), you should follow this procedure. It is the most
2454 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2456 make kernel-toolchain
2457 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2458 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2460 To test a kernel once
2461 ---------------------
2462 If you just want to boot a kernel once (because you are not sure
2463 if it works, or if you want to boot a known bad kernel to provide
2464 debugging information) run
2465 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2466 nextboot -k testkernel
2468 To rebuild everything and install it on the current system.
2469 -----------------------------------------------------------
2470 # Note: sometimes if you are running current you gotta do more than
2471 # is listed here if you are upgrading from a really old current.
2473 <make sure you have good level 0 dumps>
2475 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2476 make installkernel KERNCONF=YOUR_KERNEL_HERE
2478 <reboot in single user> [3]
2485 To cross-install current onto a separate partition
2486 --------------------------------------------------
2487 # In this approach we use a separate partition to hold
2488 # current's root, 'usr', and 'var' directories. A partition
2489 # holding "/", "/usr" and "/var" should be about 2GB in
2492 <make sure you have good level 0 dumps>
2495 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2496 <maybe newfs current's root partition>
2497 <mount current's root partition on directory ${CURRENT_ROOT}>
2498 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
2499 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2500 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2501 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2502 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2503 <reboot into current>
2504 <do a "native" rebuild/install as described in the previous section>
2505 <maybe install compatibility libraries from ports/misc/compat*>
2509 To upgrade in-place from stable to current
2510 ----------------------------------------------
2511 <make sure you have good level 0 dumps>
2513 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
2514 make installkernel KERNCONF=YOUR_KERNEL_HERE
2516 <reboot in single user> [3]
2523 Make sure that you've read the UPDATING file to understand the
2524 tweaks to various things you need. At this point in the life
2525 cycle of current, things change often and you are on your own
2526 to cope. The defaults can also change, so please read ALL of
2527 the UPDATING entries.
2529 Also, if you are tracking -current, you must be subscribed to
2530 freebsd-current@freebsd.org. Make sure that before you update
2531 your sources that you have read and understood all the recent
2532 messages there. If in doubt, please track -stable which has
2533 much fewer pitfalls.
2535 [1] If you have third party modules, such as vmware, you should disable
2536 them at this point so they don't crash your system on
2537 reboot. Alternatively, you should rebuild all the modules you have in
2538 your system and install them as well. If you are running -current, you
2539 should seriously consider placing all sources to all the modules for
2540 your system (or symlinks to them) in /usr/local/sys/modules so this
2541 happens automatically. If all your modules come from ports, then adding
2542 the port origin directories to PORTS_MODULES instead is also automatic
2544 PORTS_MODULES+=x11/nvidia-driver
2546 [3] From the bootblocks, boot -s, and then do
2550 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed
2551 cd src # full path to source
2552 adjkerntz -i # if CMOS is wall time
2553 Also, when doing a major release upgrade, it is required that you boot
2554 into single user mode to do the installworld.
2556 [4] Note: This step is non-optional. Failure to do this step
2557 can result in a significant reduction in the functionality of the
2558 system. Attempting to do it by hand is not recommended and those
2559 that pursue this avenue should read this file carefully, as well
2560 as the archives of freebsd-current and freebsd-hackers mailing lists
2561 for potential gotchas. See etcupdate(8) for more information.
2563 [5] Usually this step is a no-op. However, from time to time
2564 you may need to do this if you get unknown user in the following
2567 [6] This only deletes old files and directories. Old libraries
2568 can be deleted by "make delete-old-libs", but you have to make
2569 sure that no program is using those libraries anymore.
2571 [8] The new kernel must be able to run existing binaries used by an
2572 installworld. When upgrading across major versions, the new kernel's
2573 configuration must include the correct COMPAT_FREEBSD<n> option for
2574 existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure
2575 to do so may leave you with a system that is hard to boot to recover. A
2576 GENERIC kernel will include suitable compatibility options to run
2577 binaries from older branches. Note that the ability to run binaries
2578 from unsupported branches is not guaranteed.
2580 Make sure that you merge any new devices from GENERIC since the
2581 last time you updated your kernel config file. Options also
2582 change over time, so you may need to adjust your custom kernels
2585 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2586 "?=" instead of the "=" assignment operator, so that buildworld can
2587 override the CPUTYPE if it needs to.
2589 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2590 not on the command line, or in /etc/make.conf. buildworld will
2591 warn if it is improperly defined.
2594 This file contains a list, in reverse chronological order, of major
2595 breakages in tracking -current. It is not guaranteed to be a complete
2596 list of such breakages, and only contains entries since September 23, 2011.
2597 If you need to see UPDATING entries from before that date, you will need
2598 to fetch an UPDATING file from an older FreeBSD release.
2600 Copyright information:
2602 Copyright 1998-2009 M. Warner Losh <imp@FreeBSD.org>
2604 Redistribution, publication, translation and use, with or without
2605 modification, in full or in part, in any form or format of this
2606 document are permitted without further permission from the author.
2608 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2609 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2610 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2611 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2612 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2613 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2614 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2615 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2616 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2617 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2618 POSSIBILITY OF SUCH DAMAGE.
2620 Contact Warner Losh if you have any questions about your use of