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://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
11 Items affecting the ports and packages system can be found in
12 /usr/ports/UPDATING. Please read that file before running portupgrade.
14 NOTE TO PEOPLE WHO THINK THAT FreeBSD 13.x IS SLOW:
15 FreeBSD 13.x has many debugging features turned on, in both the kernel
16 and userland. These features attempt to detect incorrect use of
17 system primitives, and encourage loud failure through extra sanity
18 checking and fail stop semantics. They also substantially impact
19 system performance. If you want to do performance measurement,
20 benchmarking, and optimization, you'll want to turn them off. This
21 includes various WITNESS- related kernel options, INVARIANTS, malloc
22 debugging flags in userland, and various verbose features in the
23 kernel. Many developers choose to disable these features on build
24 machines to maximize performance. (To completely disable malloc
25 debugging, define MALLOC_PRODUCTION in /etc/make.conf, or to merely
26 disable the most expensive debugging functionality run
27 "ln -s 'abort:false,junk:false' /etc/malloc.conf".)
30 OpenZFS support has been integrated. Do not upgrade root pools until
31 the loader is updated to support zstd. Furthermore, we caution against
32 'zpool upgrade' for the next few weeks. The change should be transparent
33 unless you want to use new features.
35 Not all "NO_CLEAN" build scenarios work across these changes. Many
36 scenarios have been tested and fixed, but rebuilding kernels without
37 rebuilding world may fail.
39 The ZFS cache file has moved from /boot to /etc to match the OpenZFS
40 upstream default. This means your zpool won't auto import until you
41 upgrade your /etc/rc.d files or you import them manually.
44 The resume code now notifies devd with the 'kernel' system
45 rather than the old 'kern' subsystem to be consistent with
46 other use. The old notification will be created as well, but
47 will be removed prior to FreeBSD 14.0.
50 r362275 changed the internal API between the kernel RPC and the
51 NFS modules. As such, all the modules must be recompiled from
55 r364330 modified the internal API used between the NFS modules.
56 As such, all the NFS modules must be re-compiled from sources.
59 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
60 been upgraded to 11.0.0. Please see the 20141231 entry below for
61 information about prerequisites and upgrading, if you are not already
62 using clang 3.5.0 or higher.
65 r364092 modified the internal ABI used between the kernel NFS
66 modules. As such, all of these modules need to be rebuilt
67 from sources, so a version bump was done.
70 Makefile.inc has been updated to work around the issue documented in
71 20200729. It was a case where the optimization of using symbolic links
72 to point to binaries created a situation where we'd run new binaries
73 with old libraries starting midway through the installworld process.
76 r363679 has redefined some undefined behavior in regcomp(3); notably,
77 extraneous escapes of most ordinary characters will no longer be
78 accepted. An exp-run has identified all of the problems with this in
79 ports, but other non-ports software may need extra escapes removed to
82 Because of this change, installworld may encounter the following error
83 from rtld: Undefined symbol "regcomp@FBSD_1.6" -- It is imperative that
84 you do not halt installworld. Instead, let it run to completion (whether
85 successful or not) and run installworld once more.
88 A new implementation of bc and dc has been imorted in r362681. This
89 implementation corrects non-conformant behavior of the previous bc
90 and adds GNU bc compatible options. It offers a number of extensions,
91 is much faster on large values, and has support for message catalogs
92 (a number of languages are already supported, contributions of further
93 languages welcome). The option WITHOUT_GH_BC can be used to build the
94 world with the previous versions of bc and dc.
97 r362639 changed the internal API used between the NFS kernel modules.
98 As such, they all need to be rebuilt from sources.
101 r362158 changed the arguments for VFS_CHECKEXP(). As such, any
102 out of tree file systems need to be modified and rebuilt.
103 Also, any file systems that are modules must be rebuilt.
106 read(2) of a directory fd is now rejected by default. root may
107 re-enable it for system root only on non-ZFS filesystems with the
108 security.bsd.allow_read_dir sysctl(8) MIB if
109 security.bsd.suser_enabled=1.
111 It may be advised to setup aliases for grep to default to `-d skip` if
112 commonly non-recursively grepping a list that includes directories and
113 the potential for the resulting stderr output is not tolerable. Example
114 aliases are now installed, commented out, in /root/.cshrc and
118 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
119 been upgraded to 10.0.1. Please see the 20141231 entry below for
120 information about prerequisites and upgrading, if you are not already
121 using clang 3.5.0 or higher.
124 Support for obsolete compilers has been removed from the build system.
125 Clang 6 and GCC 6.4 are the minimum supported versions.
128 closefrom(2) has been moved under COMPAT12, and replaced in libc with a
129 stub that calls close_range(2). If using a custom kernel configuration,
130 you may want to ensure that the COMPAT_FREEBSD12 option is included, as
131 a slightly older -CURRENT userland and older FreeBSD userlands may not
132 be functional without closefrom(2).
135 Upstream DTS from Linux 5.6 was merged and they now have the SID
136 and THS (Secure ID controller and THermal Sensor) node present.
137 The DTB overlays have now been removed from the tree for the H3/H5 and
138 A64 SoCs and the aw_sid and aw_thermal driver have been updated to
139 deal with upstream DTS. If you are using those overlays you need to
140 remove them from loader.conf and update the DTBs on the FAT partition.
143 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
144 been upgraded to 10.0.0. Please see the 20141231 entry below for
145 information about prerequisites and upgrading, if you are not already
146 using clang 3.5.0 or higher.
149 The amd(8) automount daemon has been removed from the source tree.
150 As of FreeBSD 10.1 autofs(5) is the preferred tool for automounting.
151 amd is still available in the sysutils/am-utils port.
154 Removed brooktree driver (bktr.4) from the tree.
157 The WITH_GPL_DTC option has been removed. The BSD-licenced device tree
158 compiler in usr.bin/dtc is used on all architectures which use dtc, and
159 the GPL dtc is available (if needed) from the sysutils/dtc port.
162 The WITHOUT_LLVM_LIBUNWIND option has been removed. LLVM's libunwind
163 is used by all supported CPU architectures.
166 GCC 4.2.1 has been removed from the tree. The WITH_GCC,
167 WITH_GCC_BOOTSTRAP, and WITH_GNUCXX options are no longer available.
168 Users who wish to build FreeBSD with GCC must use the external toolchain
172 ncurses has been updated to a newer version (6.2-20200215). Given the ABI
173 has changed, users will have to rebuild all the ports that are linked to
177 The size of struct vnet and the magic cookie have changed.
178 Users need to recompile libkvm and all modules using VIMAGE
179 together with their new kernel.
182 Defining the long deprecated NO_CTF, NO_DEBUG_FILES, NO_INSTALLLIB,
183 NO_MAN, NO_PROFILE, and NO_WARNS variables is now an error. Update
184 your Makefiles and scripts to define MK_<var>=no instead as required.
186 One exception to this is that program or library Makefiles should
187 define MAN to empty rather than setting MK_MAN=no.
190 Clang/LLVM is now the default compiler and LLD the default
194 make universe no longer uses GCC 4.2.1 on any architectures.
195 Architectures not supported by in-tree Clang/LLVM require an
196 external toolchain package.
199 GCC 4.2.1 is now not built by default, as part of the GCC 4.2.1
200 retirement plan. Specifically, the GCC, GCC_BOOTSTRAP, and GNUCXX
201 options default to off for all supported CPU architectures. As a
202 short-term transition aid they may be enabled via WITH_* options.
203 GCC 4.2.1 is expected to be removed from the tree on 2020-03-31.
206 Support for armv5 has been disconnected and is being removed. The
207 machine combination MACHINE=arm MACHINE_ARCH=arm is no longer valid.
208 You must now use a MACHINE_ARCH of armv6 or armv7. The default
209 MACHINE_ARCH for MACHINE=arm is now armv7.
212 Clang/LLVM is now the default compiler for all powerpc architectures.
213 LLD is now the default linker for powerpc64. The change for powerpc64
214 also includes a change to the ELFv2 ABI, incompatible with the existing
218 Kernel-loadable random(4) modules are no longer unloadable.
221 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
222 been upgraded to 9.0.1. Please see the 20141231 entry below for
223 information about prerequisites and upgrading, if you are not already
224 using clang 3.5.0 or higher.
227 r355677 has modified the internal interface used between the
228 NFS modules in the kernel. As such, they must all be upgraded
229 simultaneously. I will do a version bump for this.
232 The root certificates of the Mozilla CA Certificate Store have been
233 imported into the base system and can be managed with the certctl(8)
234 utility. If you have installed the security/ca_root_nss port or package
235 with the ETCSYMLINK option (the default), be advised that there may be
236 differences between those included in the port and those included in
237 base due to differences in nss branch used as well as general update
238 frequency. Note also that certctl(8) cannot manage certs in the
239 format used by the security/ca_root_nss port.
242 The amd(8) automount daemon has been disabled by default, and will be
243 removed in the future. As of FreeBSD 10.1 the autofs(5) is available
247 The nctgpio and wbwd drivers have been moved to the superio bus.
248 If you have one of these drivers in a kernel configuration, then
249 you should add device superio to it. If you use one of these drivers
250 as a module and you compile a custom set of modules, then you should
251 add superio to the set.
254 KPIs for network drivers to access interface addresses have changed.
255 Users need to recompile NIC driver modules together with kernel.
258 The net.link.tap.user_open sysctl no longer prevents user opening of
259 already created /dev/tapNN devices. Access is still controlled by
260 node permissions, just like tun devices. The net.link.tap.user_open
261 sysctl is now used only to allow users to perform devfs cloning of
262 tap devices, and the subsequent open may not succeed if the user is not
263 in the appropriate group. This sysctl may be deprecated/removed
264 completely in the future.
267 mips, powerpc, and sparc64 are no longer built as part of
268 universe / tinderbox unless MAKE_OBSOLETE_GCC is defined. If
269 not defined, mips, powerpc, and sparc64 builds will look for
270 the xtoolchain binaries and if installed use them for universe
271 builds. As llvm 9.0 becomes vetted for these architectures, they
272 will be removed from the list.
275 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
276 been upgraded to 9.0.0. Please see the 20141231 entry below for
277 information about prerequisites and upgrading, if you are not already
278 using clang 3.5.0 or higher.
281 The hpt27xx, hptmv, hptnr, and hptrr drivers have been removed from
282 GENERIC. They are available as modules and can be loaded by adding
283 to /boot/loader.conf hpt27xx_load="YES", hptmv_load="YES",
284 hptnr_load="YES", or hptrr_load="YES", respectively.
287 ntpd no longer by default locks its pages in memory, allowing them
288 to be paged out by the kernel. Use rlimit memlock to restore
289 historic BSD behaviour. For example, add "rlimit memlock 32"
290 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
293 Several of ping6's options have been renamed for better consistency
294 with ping. If you use any of -ARWXaghmrtwx, you must update your
295 scripts. See ping6(8) for details.
298 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
299 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
300 been removed from mount_fusefs(8). You can safely remove them from
301 your scripts, because they had no effect.
303 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
304 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
305 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
306 sysctls have been removed. If you felt the need to set any of them to
307 a non-default value, please tell asomers@FreeBSD.org why.
310 Default permissions on the /var/account/acct file (and copies of it
311 rotated by periodic daily scripts) are changed from 0644 to 0640
312 because the file contains sensitive information that should not be
313 world-readable. If the /var/account directory must be created by
314 rc.d/accounting, the mode used is now 0750. Admins who use the
315 accounting feature are encouraged to change the mode of an existing
316 /var/account directory to 0750 or 0700.
319 Entropy collection and the /dev/random device are no longer optional
320 components. The "device random" option has been removed.
321 Implementations of distilling algorithms can still be made loadable
322 with "options RANDOM_LOADABLE" (e.g., random_fortuna.ko).
325 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
326 been upgraded to 8.0.1. Please see the 20141231 entry below for
327 information about prerequisites and upgrading, if you are not already
328 using clang 3.5.0 or higher.
331 A fix was applied to i386 kernel modules to avoid panics with
332 dpcpu or vnet. Users need to recompile i386 kernel modules
333 having pcpu or vnet sections or they will refuse to load.
336 User-wired pages now have their own counter,
337 vm.stats.vm.v_user_wire_count. The vm.max_wired sysctl was renamed
338 to vm.max_user_wired and changed from an unsigned int to an unsigned
339 long. bhyve VMs wired with the -S are now subject to the user
340 wiring limit; the vm.max_user_wired sysctl may need to be tuned to
341 avoid running into the limit.
344 The IPSEC option has been removed from GENERIC. Users requiring
345 ipsec(4) must now load the ipsec(4) kernel module.
348 The tap(4) driver has been folded into tun(4), and the module has been
349 renamed to tuntap. You should update any kld_list="if_tap" or
350 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
351 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
352 module instead, and "device tap" or "device tun" entries in kernel
353 config files to select the tuntap device instead.
356 The following knobs have been added related to tradeoffs between
357 safe use of the random device and availability in the absence of
360 kern.random.initial_seeding.bypass_before_seeding: tunable; set
361 non-zero to bypass the random device prior to seeding, or zero to
362 block random requests until the random device is initially seeded.
363 For now, set to 1 (unsafe) by default to restore pre-r346250 boot
364 availability properties.
366 kern.random.initial_seeding.read_random_bypassed_before_seeding:
367 read-only diagnostic sysctl that is set when bypass is enabled and
368 read_random(9) is bypassed, to enable programmatic handling of this
369 initial condition, if desired.
371 kern.random.initial_seeding.arc4random_bypassed_before_seeding:
372 Similar to the above, but for for arc4random(9) initial seeding.
374 kern.random.initial_seeding.disable_bypass_warnings: tunable; set
375 non-zero to disable warnings in dmesg when the same conditions are
376 met as for the diagnostic sysctls above. Defaults to zero, i.e.,
377 produce warnings in dmesg when the conditions are met.
380 The loadable random module KPI has changed; the random_infra_init()
381 routine now requires a 3rd function pointer for a bool (*)(void)
382 method that returns true if the random device is seeded (and
383 therefore unblocked).
386 r345895 reverts r320698. This implies that an nfsuserd(8) daemon
387 built from head sources between r320757 (July 6, 2017) and
388 r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
389 is added to the command line.
390 nfsuserd daemons built from head sources that are post-r338192 are
391 not affected and should continue to work.
394 The fuse(4) module has been renamed to fusefs(4) for consistency with
395 other filesystems. You should update any kld_load="fuse" entries in
396 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
397 "options FUSE" entries in kernel config files.
400 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
401 8.0.0. Please see the 20141231 entry below for information about
402 prerequisites and upgrading, if you are not already using clang 3.5.0
406 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
407 compiled into your custom kernel, add 'device xz' statement to the
411 drm and drm2 have been removed from the tree. Please see
412 https://wiki.freebsd.org/Graphics for the latest information on
413 migrating to the drm ports.
416 Iflib is no longer unconditionally compiled into the kernel. Drivers
417 using iflib and statically compiled into the kernel, now require
418 the 'device iflib' config option. For the same drivers loaded as
419 modules on kernels not having 'device iflib', the iflib.ko module
420 is loaded automatically.
423 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
424 options no longer exist since r343219 and r343427 respectively;
425 nothing uses them, so they should be just removed from custom
429 r342635 changes the way efibootmgr(8) works by requiring users to add
430 the -b (bootnum) parameter for commands where the bootnum was previously
431 specified with each option. For example 'efibootmgr -B 0001' is now
432 'efibootmgr -B -b 0001'.
435 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
436 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
437 servers that have vfs.nfsd.nfs_privport set will only allow mounts
438 from clients using a reserved port#. Since both the FreeBSD and Linux
439 NFSv4 clients use reserved port#s by default, this should not affect
443 The XLP config has been removed. We can't support 64-bit atomics in this
444 kernel because it is running in 32-bit mode. XLP users must transition
445 to running a 64-bit kernel (XLP64 or XLPN32).
447 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
448 the preferred emulator today and we don't need two different ones.
450 The old sibyte / swarm / Broadcom BCM1250 support has been
451 removed from the mips port.
454 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
455 7.0.1. Please see the 20141231 entry below for information about
456 prerequisites and upgrading, if you are not already using clang 3.5.0
460 Remove the timed and netdate programs from the base tree. Setting
461 the time with these daemons has been obsolete for over a decade.
464 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
465 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
466 it produces broken binaries when ifuncs are in use. Users needing
467 GNU ld should install the binutils port or package.
470 The BSD crtbegin and crtend code has been enabled by default. It has
471 had extensive testing on amd64, arm64, and i386. It can be disabled
472 by building a world with -DWITHOUT_BSD_CRTBEGIN.
475 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
476 has been converted to a port (misc/ctm) and will be removed from
477 FreeBSD-13. It is available as a package (ctm) for all supported
481 The default newsyslog.conf(5) file has been changed to only include
482 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
483 the filenames end in '.conf' and do not begin with a '.'.
485 You should check the configuration files in these two directories match
486 this naming convention. You can verify which configuration files are
487 being included using the command:
491 Ports for the DRM modules have been simplified. Now, amd64 users should
492 just install the drm-kmod port. All others should install
495 Graphics hardware that's newer than about 2010 usually works with
496 drm-kmod. For hardware older than 2013, however, some users will need
497 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
498 than 2008 usually only works in drm-legacy-kmod. The graphics team can
499 only commit to hardware made since 2013 due to the complexity of the
500 market and difficulty to test all the older cards effectively. If you
501 have hardware supported by drm-kmod, you are strongly encouraged to use
502 that as you will get better support.
504 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
505 elsewhere, the drm and drm2 modules will be eliminated from the src base
506 soon (with a limited exception for arm). Please update to the package
507 asap and report any issues to x11@freebsd.org.
509 Generally, anybody using the drm*-kmod packages should add
510 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
511 cross-threading surprises, especially with automatic driver
512 loading from X11 startup. These will become the defaults in 13-current
516 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
517 custom kernel and module loading configuration files must be updated
518 accordingly. Moreover, interfaces previous presented as ixlvN to the
519 system are now exposed as iavfN and network configuration files must
520 be adjusted as necessary.
523 OpenSSL has been updated to version 1.1.1. This update included
524 additional various API changes throughout the base system. It is
525 important to rebuild third-party software after upgrading. The value
526 of __FreeBSD_version has been bumped accordingly.
529 The legacy DRM modules and drivers have now been added to the loader's
530 module blacklist, in favor of loading them with kld_list in rc.conf(5).
531 The module blacklist may be overridden with the loader.conf(5)
532 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
536 The cam(4) based nda(4) driver will be used over nvd(4) by default on
537 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
538 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
539 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
543 Reproducible build mode is now on by default, in preparation for
544 FreeBSD 12.0. This eliminates build metadata such as the user,
545 host, and time from the kernel (and uname), unless the working tree
546 corresponds to a modified checkout from a version control system.
547 The previous behavior can be obtained by setting the /etc/src.conf
548 knob WITHOUT_REPRODUCIBLE_BUILD.
551 The Yarrow CSPRNG has been removed from the kernel as it has not been
552 supported by its designers since at least 2003. Fortuna has been the
553 default since FreeBSD-11.
556 devctl freeze/thaw have gone into the tree, the rc scripts have been
557 updated to use them and devmatch has been changed. You should update
558 kernel, userland and rc scripts all at the same time.
561 The default interpreter has been switched from 4th to Lua.
562 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
563 interpreter. If you have custom FORTH code you will need to set
564 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
565 src.conf for the build. This will create default hard links between
566 loader and loader_4th instead of loader and loader_lua, the new default.
567 If you are using UEFI it will create the proper hard link to loader.efi.
569 bhyve uses userboot.so. It remains 4th-only until some issues are solved
570 regarding coexisting with multiple versions of FreeBSD are resolved.
573 ls(1) now respects the COLORTERM environment variable used in other
574 systems and software to indicate that a colored terminal is both
575 supported and desired. If ls(1) is suddenly emitting colors, they may
576 be disabled again by either removing the unwanted COLORTERM from your
577 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
578 may not be observed in a future release.
581 The default pager for most commands has been changed to "less". To
582 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
586 The jedec_ts(4) driver has been removed. A superset of its functionality
587 is available in the jedec_dimm(4) driver, and the manpage for that
588 driver includes migration instructions. If you have "device jedec_ts"
589 in your kernel configuration file, it must be removed.
592 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
593 This should have no effect if the kernel is booted via BIOS/legacy boot.
594 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
595 has a buggy firmware that prevents a successful boot due to use of
599 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
600 support has been removed from the tree. These ports were
601 obsolete and/or known to be broken for many years.
604 loader.efi has been augmented to participate more fully in the
605 UEFI boot manager protocol. loader.efi will now look at the
606 BootXXXX environment variable to determine if a specific kernel
607 or root partition was specified. XXXX is derived from BootCurrent.
608 efibootmgr(8) manages these standard UEFI variables.
611 zfsloader's functionality has now been folded into loader.
612 zfsloader is no longer necessary once you've updated your
613 boot blocks. For a transition period, we will install a
614 hardlink for zfsloader to loader to allow a smooth transition
615 until the boot blocks can be updated (hard link because old
616 zfs boot blocks don't understand symlinks).
619 ARM64 now have efifb support, if you want to have serial console
620 on your arm64 board when an screen is connected and the bootloader
621 setup a frame buffer for us to use, just add :
625 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
626 an screen connected as the firmware will setup a frame buffer are that
627 u-boot will expose as an EFI frame buffer.
630 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
631 or take steps to update /etc/passwd before doing installworld on
632 existing systems. Do not skip the "mergemaster -Fp" step before
633 installworld, as described in the update procedures near the bottom
634 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
635 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
636 the ntp config file contain options that change file/dir locations.
637 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
638 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
639 taking steps to ensure that all required files/dirs are accessible
643 Big endian arm support has been removed.
646 The static environment setup in kernel configs is no longer mutually
647 exclusive with the loader(8) environment by default. In order to
648 restore the previous default behavior of disabling the loader(8)
649 environment if a static environment is present, you must specify
650 loader_env.disabled=1 in the static environment.
653 The ABI of syscalls used by management tools like sockstat and
654 netstat has been broken to allow 32-bit binaries to work on
655 64-bit kernels without modification. These programs will need
656 to match the kernel in order to function. External programs may
657 require minor modifications to accommodate a change of type in
658 structures from pointers to 64-bit virtual addresses.
661 On i386 and amd64 atomics are now inlined. Out of tree modules using
662 atomics will need to be rebuilt.
665 The '%I' format in the kern.corefile sysctl limits the number of
666 core files that a process can generate to the number stored in the
667 debug.ncores sysctl. The '%I' format is replaced by the single digit
668 index. Previously, if all indexes were taken the kernel would overwrite
669 only a core file with the highest index in a filename.
670 Currently the system will create a new core file if there is a free
671 index or if all slots are taken it will overwrite the oldest one.
674 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
675 6.0.1. Please see the 20141231 entry below for information about
676 prerequisites and upgrading, if you are not already using clang 3.5.0
680 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
681 needed to be changed to work with it. This change was made with r335763
682 and requires a mergemaster / etcupdate / etc to update the installed
686 r334930 changed the interface between the NFS modules, so they all
687 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
690 As of r334391 lld is the default amd64 system linker; it is installed
691 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
695 The kernel / userland interface for devinfo changed, so you'll
696 need a new kernel and userland as a pair for it to work (rebuilding
697 lib/libdevinfo is all that's required). devinfo and devmatch will
698 not work, but everything else will when there's a mismatch.
701 The on-disk format for hwpmc callchain records has changed to include
702 threadid corresponding to a given record. This changes the field offsets
703 and thus requires that libpmcstat be rebuilt before using a kernel
707 The vxge(4) driver has been removed. This driver was introduced into
708 HEAD one week before the Exar left the Ethernet market and is not
709 known to be used. If you have device vxge in your kernel config file
713 The amd64 kernel now requires a ld that supports ifunc to produce a
714 working kernel, either lld or a newer binutils. lld is built by default
715 on amd64, and the 'buildkernel' target uses it automatically. However,
716 it is not the default linker, so building the kernel the traditional
717 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
718 binutils port/package). lld will soon be default, and this requirement
721 NOTE: As of r334391 lld is the default system linker on amd64, and no
722 workaround is necessary.
725 The nxge(4) driver has been removed. This driver was for PCI-X 10g
726 cards made by s2io/Neterion. The company was acquired by Exar and
727 no longer sells or supports Ethernet products. If you have device
728 nxge in your kernel config file it must be removed.
731 The tz database (tzdb) has been updated to 2018e. This version more
732 correctly models time stamps in time zones with negative DST such as
733 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
734 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
735 time zone abbreviations and the tm_isdst flag.
738 The ixgb(4) driver has been removed. This driver was for an early and
739 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
740 quickly shifted to the long lived ixgbe family. If you have device
741 ixgb in your kernel config file it must be removed.
744 The lmc(4) driver has been removed. This was a WAN interface
745 card that was already reportedly rare in 2003, and had an ambiguous
746 license. If you have device lmc in your kernel config file it must
750 Support for Arcnet networks has been removed. If you have device
751 arcnet or device cm in your kernel config file they must be
755 Support for FDDI networks has been removed. If you have device
756 fddi or device fpa in your kernel config file they must be
760 In addition to supporting RFC 3164 formatted messages, the
761 syslogd(8) service is now capable of parsing RFC 5424 formatted
762 log messages. The main benefit of using RFC 5424 is that clients
763 may now send log messages with timestamps containing year numbers,
764 microseconds and time zone offsets.
766 Similarly, the syslog(3) C library function has been altered to
767 send RFC 5424 formatted messages to the local system logging
768 daemon. On systems using syslogd(8), this change should have no
769 negative impact, as long as syslogd(8) and the C library are
770 updated at the same time. On systems using a different system
771 logging daemon, it may be necessary to make configuration
772 adjustments, depending on the software used.
774 When using syslog-ng, add the 'syslog-protocol' flag to local
775 input sources to enable parsing of RFC 5424 formatted messages:
778 unix-dgram("/var/run/log" flags(syslog-protocol));
781 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
782 of the 'imuxsock' module to let messages be processed by the
783 regular RFC 3164/5424 parsing pipeline:
785 module(load="imuxsock" SysSock.UseSpecialParser="off")
787 Do note that these changes only affect communication between local
788 applications and syslogd(8). The format that syslogd(8) uses to
789 store messages on disk or forward messages to other systems
790 remains unchanged. syslogd(8) still uses RFC 3164 for these
791 purposes. Options to customize this behaviour will be added in the
792 future. Utilities that process log files stored in /var/log are
793 thus expected to continue to function as before.
795 __FreeBSD_version has been incremented to 1200061 to denote this
799 Support for token ring networks has been removed. If you
800 have "device token" in your kernel config you should remove
801 it. No device drivers supported token ring.
804 makefs was modified to be able to tag ISO9660 El Torito boot catalog
805 entries as EFI instead of overloading the i386 tag as done previously.
806 The amd64 mkisoimages.sh script used to build amd64 ISO images for
807 release was updated to use this. This may mean that makefs must be
808 updated before "make cdrom" can be run in the release directory. This
809 should be as simple as:
811 $ cd $SRCDIR/usr.sbin/makefs
812 $ make depend all install
815 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
816 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
817 Co-existence for the transition period will come shortly. Booting is a
818 complex environment and test coverage for Lua-enabled loaders has been
819 thin, so it would be prudent to assume it might not work and make
820 provisions for backup boot methods.
823 devmatch functionality has been turned on in devd. It will automatically
824 load drivers for unattached devices. This may cause unexpected drivers
825 to be loaded. Please report any problems to current@ and
829 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
830 6.0.0. Please see the 20141231 entry below for information about
831 prerequisites and upgrading, if you are not already using clang 3.5.0
835 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
836 This means it is used to link the kernel and userland libraries and
837 executables, but is not yet installed as /usr/bin/ld by default.
839 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
840 WITHOUT_LLD_BOOTSTRAP=yes
843 On i386, pmtimer has been removed. Its functionality has been folded
844 into apm. It was a no-op on ACPI in current for a while now (but was
845 still needed on i386 in FreeBSD 11 and earlier). Users may need to
846 remove it from kernel config files.
849 The use of RSS hash from the network card aka flowid has been
850 disabled by default for lagg(4) as it's currently incompatible with
851 the lacp and loadbalance protocols.
853 This can be re-enabled by setting the following in loader.conf:
854 net.link.lagg.default_use_flowid="1"
857 The SW_WATCHDOG option is no longer necessary to enable the
858 hardclock-based software watchdog if no hardware watchdog is
859 configured. As before, SW_WATCHDOG will cause the software
860 watchdog to be enabled even if a hardware watchdog is configured.
863 r326887 fixes the issue described in the 20171214 UPDATING entry.
864 r326888 flips the switch back to building GELI support always.
867 r362593 broke ZFS + GELI support for reasons unknown. However,
868 it also broke ZFS support generally, so GELI has been turned off
869 by default as the lesser evil in r326857. If you boot off ZFS and/or
870 GELI, it might not be a good time to update.
873 PowerPC users must update loader(8) by rebuilding world before
874 installing a new kernel, as the protocol connecting them has
875 changed. Without the update, loader metadata will not be passed
876 successfully to the kernel and users will have to enter their
877 root partition at the kernel mountroot prompt to continue booting.
878 Newer versions of loader can boot old kernels without issue.
881 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
882 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
883 to WITH/OUT_LOADER_GELI.
886 The naive and non-compliant support of posix_fallocate(2) in ZFS
887 has been removed as of r325320. The system call now returns EINVAL
888 when used on a ZFS file. Although the new behavior complies with the
889 standard, some consumers are not prepared to cope with it.
890 One known victim is lld prior to r325420.
893 Building in a FreeBSD src checkout will automatically create object
894 directories now rather than store files in the current directory if
895 'make obj' was not ran. Calling 'make obj' is no longer necessary.
896 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
897 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
901 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
902 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
903 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
904 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
905 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
906 The UNIFIED_OBJDIR option is a transitional feature that will be
907 removed for 12.0 release; please migrate to the new format for any
908 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
909 than hardcoding paths.
912 The native-xtools target no longer installs the files by default to the
913 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
914 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
917 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
918 options are changing from controlling the build if defined / undefined
919 to controlling the build with explicit 'yes' or 'no' values. They will
920 shift to WITH/WITHOUT options to match other options in the system.
923 libstand has turned into a private library for sys/boot use only.
924 It is no longer supported as a public interface outside of sys/boot.
927 The arm port has split armv6 into armv6 and armv7. armv7 is now
928 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
929 and are running a kernel from before r324363, you will need to add
930 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
933 When building multiple kernels using KERNCONF, non-existent KERNCONF
934 files will produce an error and buildkernel will fail. Previously
935 missing KERNCONF files silently failed giving no indication as to
936 why, only to subsequently discover during installkernel that the
937 desired kernel was never built in the first place.
940 The default serial number format for CTL LUNs has changed. This will
941 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
942 or iSCSI clients care about their LUNs' serial numbers. Users who
943 require serial number stability should hardcode serial numbers in
947 For 32-bit arm compiled for hard-float support, soft-floating point
948 binaries now always get their shared libraries from
949 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
950 /usr/libsoft also existed). Only users with a hard-float ld.so, but
951 soft-float everything else should be affected.
954 The geli password typed at boot is now hidden. To restore the previous
955 behavior, see geli(8) for configuration options.
958 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
959 sysctl values. Minor nit, but requires a rebuild of both world/kernel
963 "make check" behavior (made in ^/head@r295380) has been changed to
964 execute from a limited sandbox, as opposed to executing from
968 - The "beforecheck" and "aftercheck" targets are now specified.
969 - ${CHECKDIR} (added in commit noted above) has been removed.
970 - Legacy behavior can be enabled by setting
971 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
973 If the limited sandbox mode is enabled, "make check" will execute
974 "make distribution", then install, execute the tests, and clean up the
975 sandbox if successful.
977 The "make distribution" and "make install" targets are typically run as
978 root to set appropriate permissions and ownership at installation time.
979 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
980 environment if executing "make check" with limited sandbox mode using
981 an unprivileged user.
984 Since the switch to GPT disk labels, fsck for UFS/FFS has been
985 unable to automatically find alternate superblocks. As of r322297,
986 the information needed to find alternate superblocks has been
987 moved to the end of the area reserved for the boot block.
988 Filesystems created with a newfs of this vintage or later
989 will create the recovery information. If you have a filesystem
990 created prior to this change and wish to have a recovery block
991 created for your filesystem, you can do so by running fsck in
992 foreground mode (i.e., do not use the -p or -y options). As it
993 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
994 to which you should answer yes.
997 As of r321665, an NFSv4 server configuration that services
998 Kerberos mounts or clients that do not support the uid/gid in
999 owner/owner_group string capability, must explicitly enable
1000 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
1001 machine's /etc/rc.conf file.
1004 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
1005 Please see the 20141231 entry below for information about prerequisites
1006 and upgrading, if you are not already using clang 3.5.0 or higher.
1009 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
1010 r-commands (rlogin, rsh, etc.) to be built with the base system.
1013 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
1014 a very major ABI incompatible change, so users of FreeBSD/powerpc must
1015 be careful when performing source upgrades. It is best to run
1016 'make installworld' from an alternate root system, either a live
1017 CD/memory stick, or a temporary root partition. Additionally, all ports
1018 must be recompiled. powerpc64 is largely unaffected, except in the case
1019 of 32-bit compatibility. All 32-bit binaries will be affected.
1022 Forward compatibility for the "ino64" project have been committed. This
1023 will allow most new binaries to run on older kernels in a limited
1024 fashion. This prevents many of the common foot-shooting actions in the
1025 upgrade as well as the limited ability to roll back the kernel across
1026 the ino64 upgrade. Complicated use cases may not work properly, though
1027 enough simpler ones work to allow recovery in most situations.
1030 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
1031 if you require the GPL compiler.
1034 The internal ABI used for communication between the NFS kernel modules
1035 was changed by r320085, so __FreeBSD_version was bumped to
1036 ensure all the NFS related modules are updated together.
1039 The ABI of struct event was changed by extending the data
1040 member to 64bit and adding ext fields. For upgrade, same
1041 precautions as for the entry 20170523 "ino64" must be
1045 The GNU roff toolchain has been removed from base. To render manpages
1046 which are not supported by mandoc(1), man(1) can fallback on GNU roff
1047 from ports (and recommends to install it).
1048 To render roff(7) documents, consider using GNU roff from ports or the
1049 heirloom doctools roff toolchain from ports via pkg install groff or
1050 via pkg install heirloom-doctools.
1053 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
1054 smaller runtime footprint builds. This is useful for embedded systems
1055 which only require one chipset support.
1057 If you load it as a module, make sure this is in /boot/loader.conf:
1061 This will load the HAL, all chip/RF backends and if_ath_pci.
1062 If you have if_ath_pci in /boot/loader.conf, ensure it is after
1063 if_ath or it will not load any HAL chipset support.
1065 If you want to selectively load things (eg on ye cheape ARM/MIPS
1066 platforms where RAM is at a premium) you should:
1069 * load the chip modules in question
1070 * load ath_rate, ath_dfs
1072 * load if_ath_pci and/or if_ath_ahb depending upon your particular
1073 bus bind type - this is where probe/attach is done.
1075 For further comments/feedback, poke adrian@ .
1078 The "ino64" 64-bit inode project has been committed, which extends
1079 a number of types to 64 bits. Upgrading in place requires care and
1080 adherence to the documented upgrade procedure.
1082 If using a custom kernel configuration ensure that the
1083 COMPAT_FREEBSD11 option is included (as during the upgrade the
1084 system will be running the ino64 kernel with the existing world).
1086 For the safest in-place upgrade begin by removing previous build
1087 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full
1088 procedure documented below under the heading "To rebuild everything and
1089 install it on the current system." Specifically, a reboot is required
1090 after installing the new kernel before installing world. While an
1091 installworld normally works by accident from multiuser after rebooting
1092 the proper kernel, there are many cases where this will fail across this
1093 upgrade and installworld from single user is required.
1096 The NATM framework including the en(4), fatm(4), hatm(4), and
1097 patm(4) devices has been removed. Consumers should plan a
1098 migration before the end-of-life date for FreeBSD 11.
1101 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
1102 diff has not been implemented, if those are needed a newer version of
1103 GNU diff is available via the diffutils package under the gdiff name.
1106 As of r316810 for ipfilter, keep frags is no longer assumed when
1107 keep state is specified in a rule. r316810 aligns ipfilter with
1108 documentation in man pages separating keep frags from keep state.
1109 This allows keep state to be specified without forcing keep frags
1110 and allows keep frags to be specified independently of keep state.
1111 To maintain previous behaviour, also specify keep frags with
1112 keep state (as documented in ipf.conf.5).
1115 arm64 builds now use the base system LLD 4.0.0 linker by default,
1116 instead of requiring that the aarch64-binutils port or package be
1117 installed. To continue using aarch64-binutils, set
1118 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
1121 The UDP optimization in entry 20160818 that added the sysctl
1122 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
1123 packets will no longer be treated as L3 broadcast packets.
1126 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
1127 use any explicitly assigned loopback address available in the jail
1128 instead of using the first assigned address of the jail.
1131 The ctl.ko module no longer implements the iSCSI target frontend:
1132 cfiscsi.ko does instead.
1134 If building cfiscsi.ko as a kernel module, the module can be loaded
1135 via one of the following methods:
1136 - `cfiscsi_load="YES"` in loader.conf(5).
1137 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
1138 - ctladm(8)/ctld(8), when compiled with iSCSI support
1139 (`WITH_ISCSI=yes` in src.conf(5))
1141 Please see cfiscsi(4) for more details.
1144 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
1145 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
1146 same source (previously, the dependency of mmcsd.ko on mmc.ko was
1147 missing, but mmcsd.ko now will refuse to load if it is incompatible
1151 The syntax of ipfw(8) named states was changed to avoid ambiguity.
1152 If you have used named states in the firewall rules, you need to modify
1153 them after installworld and before rebooting. Now named states must
1154 be prefixed with colon.
1157 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
1158 removed as the userland we provide cannot use them. The KMS version
1159 (sys/dev/drm2) supports the same hardware.
1162 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
1163 Please see the 20141231 entry below for information about prerequisites
1164 and upgrading, if you are not already using clang 3.5.0 or higher.
1167 The code that provides support for ZFS .zfs/ directory functionality
1168 has been reimplemented. It's not possible now to create a snapshot
1169 by mkdir under .zfs/snapshot/. That should be the only user visible
1173 EISA bus support has been removed. The WITH_EISA option is no longer
1177 MCA bus support has been removed.
1180 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
1181 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
1184 The EM_MULTIQUEUE kernel configuration option is deprecated now that
1185 the em(4) driver conforms to iflib specifications.
1188 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
1189 IFLIB. If you have a custom kernel configuration that excludes em(4)
1190 but you use igb(4), you need to re-add em(4) to your custom
1194 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
1195 Please see the 20141231 entry below for information about prerequisites
1196 and upgrading, if you are not already using clang 3.5.0 or higher.
1199 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
1200 Please see the 20141231 entry below for information about prerequisites
1201 and upgrading, if you are not already using clang 3.5.0 or higher.
1204 The layout of the pmap structure has changed for powerpc to put the pmap
1205 statistics at the front for all CPU variations. libkvm(3) and all tools
1206 that link against it need to be recompiled.
1209 isl(4) and cyapa(4) drivers now require a new driver,
1210 chromebook_platform(4), to work properly on Chromebook-class hardware.
1211 On other types of hardware the drivers may need to be configured using
1212 device hints. Please see the corresponding manual pages for details.
1215 The urtwn(4) driver was merged into rtwn(4) and now consists of
1216 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
1218 Also, firmware for RTL8188CE was renamed due to possible name
1219 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
1222 GNU rcs has been removed from base. It is available as packages:
1223 - rcs: Latest GPLv3 GNU rcs version.
1224 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
1228 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
1229 modules now requires that the kernel configuration contain the
1230 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
1233 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
1234 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
1237 Relocatable object files with the extension of .So have been renamed
1238 to use an extension of .pico instead. The purpose of this change is
1239 to avoid a name clash with shared libraries on case-insensitive file
1240 systems. On those file systems, foo.So is the same file as foo.so.
1243 GNU rcs has been turned off by default. It can (temporarily) be built
1244 again by adding WITH_RCS knob in src.conf.
1245 Otherwise, GNU rcs is available from packages:
1246 - rcs: Latest GPLv3 GNU rcs version.
1247 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
1250 The backup_uses_rcs functionality has been removed from rc.subr.
1253 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
1254 two separate components, QUEUE_MACRO_DEBUG_TRACE and
1255 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
1256 QUEUE_MACRO_DEBUG behavior.
1259 r304787 changed some ioctl interfaces between the iSCSI userspace
1260 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1261 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1265 The UDP receive code has been updated to only treat incoming UDP
1266 packets that were addressed to an L2 broadcast address as L3
1267 broadcast packets. It is not expected that this will affect any
1268 standards-conforming UDP application. The new behaviour can be
1269 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1273 Remove the openbsd_poll system call.
1274 __FreeBSD_version has been bumped because of this.
1277 The stable/11 branch has been created from head@r302406.
1280 The libc stub for the pipe(2) system call has been replaced with
1281 a wrapper that calls the pipe2(2) system call and the pipe(2)
1282 system call is now only implemented by the kernels that include
1283 "options COMPAT_FREEBSD10" in their config file (this is the
1284 default). Users should ensure that this option is enabled in
1285 their kernel or upgrade userspace to r302092 before upgrading their
1289 CAM will now strip leading spaces from SCSI disks' serial numbers.
1290 This will affect users who create UFS filesystems on SCSI disks using
1291 those disk's diskid device nodes. For example, if /etc/fstab
1292 previously contained a line like
1293 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
1294 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
1295 transforms like gmirror may also be affected. ZFS users should
1299 The bitstring(3) API has been updated with new functionality and
1300 improved performance. But it is binary-incompatible with the old API.
1301 Objects built with the new headers may not be linked against objects
1302 built with the old headers.
1305 The brk and sbrk functions have been removed from libc on arm64.
1306 Binutils from ports has been updated to not link to these
1307 functions and should be updated to the latest version before
1308 installing a new libc.
1311 The armv6 port now defaults to hard float ABI. Limited support
1312 for running both hardfloat and soft float on the same system
1313 is available using the libraries installed with -DWITH_LIBSOFT.
1314 This has only been tested as an upgrade path for installworld
1315 and packages may fail or need manual intervention to run. New
1316 packages will be needed.
1318 To update an existing self-hosted armv6hf system, you must add
1319 TARGET_ARCH=armv6 on the make command line for both the build
1320 and the install steps.
1323 Kernel modules compiled outside of a kernel build now default to
1324 installing to /boot/modules instead of /boot/kernel. Many kernel
1325 modules built this way (such as those in ports) already overrode
1326 KMODDIR explicitly to install into /boot/modules. However,
1327 manually building and installing a module from /sys/modules will
1328 now install to /boot/modules instead of /boot/kernel.
1331 The CAM I/O scheduler has been committed to the kernel. There should be
1332 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1333 list of known rogues that claim support for this but actually corrupt
1334 data is believed to be complete, be on the lookout for data
1335 corruption. The known rogue list is believed to be complete:
1337 o Crucial MX100, M550 drives with MU01 firmware.
1338 o Micron M510 and M550 drives with MU01 firmware.
1339 o Micron M500 prior to MU07 firmware
1340 o Samsung 830, 840, and 850 all firmwares
1341 o FCCT M500 all firmwares
1343 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1344 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1345 updated firmware. Black listed drives will work correctly because these
1346 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1347 this list is the same as found in Linux, it's believed there are no
1348 other rogues in the market place. All other models from the above
1351 To be safe, if you are at all concerned, you can quirk each of your
1352 drives to prevent NCQ from being sent by setting:
1353 kern.cam.ada.X.quirks="0x2"
1354 in loader.conf. If the drive requires the 4k sector quirk, set the
1355 quirks entry to 0x3.
1358 The FAST_DEPEND build option has been removed and its functionality is
1359 now the one true way. The old mkdep(1) style of 'make depend' has
1360 been removed. See 20160311 for further details.
1363 Resource range types have grown from unsigned long to uintmax_t. All
1364 drivers, and anything using libdevinfo, need to be recompiled.
1367 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1368 builds. It no longer runs mkdep(1) during 'make depend', and the
1369 'make depend' stage can safely be skipped now as it is auto ran
1370 when building 'make all' and will generate all SRCS and DPSRCS before
1371 building anything else. Dependencies are gathered at compile time with
1372 -MF flags kept in separate .depend files per object file. Users should
1373 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1374 stale .depend files.
1377 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1378 kernel modules. Therefore, if you load any kernel modules at boot time,
1379 please install the boot loaders after you install the kernel, but before
1383 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1384 make installkernel KERNCONF=YOUR_KERNEL_HERE
1385 make -C sys/boot install
1386 <reboot in single user>
1388 Then follow the usual steps, described in the General Notes section,
1392 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1393 see the 20141231 entry below for information about prerequisites and
1394 upgrading, if you are not already using clang 3.5.0 or higher.
1397 The AIO subsystem is now a standard part of the kernel. The
1398 VFS_AIO kernel option and aio.ko kernel module have been removed.
1399 Due to stability concerns, asynchronous I/O requests are only
1400 permitted on sockets and raw disks by default. To enable
1401 asynchronous I/O requests on all file types, set the
1402 vfs.aio.enable_unsafe sysctl to a non-zero value.
1405 The ELF object manipulation tool objcopy is now provided by the
1406 ELF Tool Chain project rather than by GNU binutils. It should be a
1407 drop-in replacement, with the addition of arm64 support. The
1408 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1409 to obtain the GNU version if necessary.
1412 Building ZFS pools on top of zvols is prohibited by default. That
1413 feature has never worked safely; it's always been prone to deadlocks.
1414 Using a zvol as the backing store for a VM guest's virtual disk will
1415 still work, even if the guest is using ZFS. Legacy behavior can be
1416 restored by setting vfs.zfs.vol.recursive=1.
1419 The NONE and HPN patches has been removed from OpenSSH. They are
1420 still available in the security/openssh-portable port.
1423 With the addition of ypldap(8), a new _ypldap user is now required
1424 during installworld. "mergemaster -p" can be used to add the user
1425 prior to installworld, as documented in the handbook.
1428 The tftp loader (pxeboot) now uses the option root-path directive. As a
1429 consequence it no longer looks for a pxeboot.4th file on the tftp
1430 server. Instead it uses the regular /boot infrastructure as with the
1434 The code to start recording plug and play data into the modules has
1435 been committed. While the old tools will properly build a new kernel,
1436 a number of warnings about "unknown metadata record 4" will be produced
1437 for an older kldxref. To avoid such warnings, make sure to rebuild
1438 the kernel toolchain (or world). Make sure that you have r292078 or
1439 later when trying to build 292077 or later before rebuilding.
1442 Debug data files are now built by default with 'make buildworld' and
1443 installed with 'make installworld'. This facilitates debugging but
1444 requires more disk space both during the build and for the installed
1445 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1449 r291527 changed the internal interface between the nfsd.ko and
1450 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1451 __FreeBSD_version has been bumped because of this.
1454 Add support for unicode collation strings leads to a change of
1455 order of files listed by ls(1) for example. To get back to the old
1456 behaviour, set LC_COLLATE environment variable to "C".
1458 Databases administrators will need to reindex their databases given
1459 collation results will be different.
1461 Due to a bug in install(1) it is recommended to remove the ancient
1462 locales before running make installworld.
1464 rm -rf /usr/share/locale/*
1467 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1468 libcrypto.so.7 or libssl.so.7 must be recompiled.
1471 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1472 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1473 should be replaced with isp_2400 and isp_2500 modules respectively.
1476 The build previously allowed using 'make -n' to not recurse into
1477 sub-directories while showing what commands would be executed, and
1478 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1479 and 'make -N' will not.
1482 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1483 and etcupdate will now use this file. A custom sendmail.cf is now
1484 updated via this mechanism rather than via installworld. If you had
1485 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1486 want to remove the exclusion or change it to "always install".
1487 /etc/mail/sendmail.cf is now managed the same way regardless of
1488 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1489 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1492 Compatibility shims for legacy ATA device names have been removed.
1493 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1494 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1495 environment variables, /dev/ad* and /dev/ar* symbolic links.
1498 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1499 Please see the 20141231 entry below for information about prerequisites
1500 and upgrading, if you are not already using clang 3.5.0 or higher.
1503 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1504 and renamed from .symbols to .debug. This reduces the size requirements
1505 on the boot partition or file system and provides consistency with
1506 userland debug files.
1508 When using the supported kernel installation method the
1509 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1510 as is done with /boot/kernel.
1512 Developers wishing to maintain the historical behavior of installing
1513 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1516 The wireless drivers had undergone changes that remove the 'parent
1517 interface' from the ifconfig -l output. The rc.d network scripts
1518 used to check presence of a parent interface in the list, so old
1519 scripts would fail to start wireless networking. Thus, etcupdate(3)
1520 or mergemaster(8) run is required after kernel update, to update your
1521 rc.d scripts in /etc.
1524 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1525 These configurations are now automatically interpreted as
1526 'scrub fragment reassemble'.
1529 Kernel-loadable modules for the random(4) device are back. To use
1530 them, the kernel must have
1533 options RANDOM_LOADABLE
1535 kldload(8) can then be used to load random_fortuna.ko
1536 or random_yarrow.ko. Please note that due to the indirect
1537 function calls that the loadable modules need to provide,
1538 the build-in variants will be slightly more efficient.
1540 The random(4) kernel option RANDOM_DUMMY has been retired due to
1541 unpopularity. It was not all that useful anyway.
1544 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1545 Control over building the ELF Tool Chain tools is now provided by
1546 the WITHOUT_TOOLCHAIN knob.
1549 The polarity of Pulse Per Second (PPS) capture events with the
1550 uart(4) driver has been corrected. Prior to this change the PPS
1551 "assert" event corresponded to the trailing edge of a positive PPS
1552 pulse and the "clear" event was the leading edge of the next pulse.
1554 As the width of a PPS pulse in a typical GPS receiver is on the
1555 order of 1 millisecond, most users will not notice any significant
1556 difference with this change.
1558 Anyone who has compensated for the historical polarity reversal by
1559 configuring a negative offset equal to the pulse width will need to
1560 remove that workaround.
1563 The default group assigned to /dev/dri entries has been changed
1564 from 'wheel' to 'video' with the id of '44'. If you want to have
1565 access to the dri devices please add yourself to the video group
1568 # pw groupmod video -m $USER
1571 The menu.rc and loader.rc files will now be replaced during
1572 upgrades. Please migrate local changes to menu.rc.local and
1573 loader.rc.local instead.
1576 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1577 strings and strip have been removed. The src.conf(5) knob
1578 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1581 As ZFS requires more kernel stack pages than is the default on some
1582 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1583 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1585 Please consider using 'options KSTACK_PAGES=X' where X is greater
1586 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1589 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1590 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1591 default, i.e., they will not contain "::". For example, instead
1592 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1593 to have a more specific match, such as different map entries for
1594 IPv6:0:0 vs IPv6:0. This change requires that configuration
1595 data (including maps, files, classes, custom ruleset, etc.) must
1596 use the same format, so make certain such configuration data is
1597 upgrading. As a very simple check search for patterns like
1598 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1599 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1600 the cf option UseCompressedIPv6Addresses.
1603 The default kernel entropy-processing algorithm is now
1604 Fortuna, replacing Yarrow.
1606 Assuming you have 'device random' in your kernel config
1607 file, the configurations allow a kernel option to override
1608 this default. You may choose *ONE* of:
1610 options RANDOM_YARROW # Legacy /dev/random algorithm.
1611 options RANDOM_DUMMY # Blocking-only driver.
1613 If you have neither, you get Fortuna. For most people,
1614 read no further, Fortuna will give a /dev/random that works
1615 like it always used to, and the difference will be irrelevant.
1617 If you remove 'device random', you get *NO* kernel-processed
1618 entropy at all. This may be acceptable to folks building
1619 embedded systems, but has complications. Carry on reading,
1620 and it is assumed you know what you need.
1622 *PLEASE* read random(4) and random(9) if you are in the
1623 habit of tweaking kernel configs, and/or if you are a member
1624 of the embedded community, wanting specific and not-usual
1625 behaviour from your security subsystems.
1627 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1628 random', you will NOT have a functioning /dev/random, and
1629 many cryptographic features will not work, including SSH.
1630 You may also find strange behaviour from the random(3) set
1631 of library functions, in particular sranddev(3), srandomdev(3)
1632 and arc4random(3). The reason for this is that the KERN_ARND
1633 sysctl only returns entropy if it thinks it has some to
1634 share, and with RANDOM_DUMMY or no 'device random' this
1638 An additional fix for the issue described in the 20150614 sendmail
1639 entry below has been committed in revision 284717.
1642 FreeBSD's old make (fmake) has been removed from the system. It is
1643 available as the devel/fmake port or via pkg install fmake.
1646 The fix for the issue described in the 20150614 sendmail entry
1647 below has been committed in revision 284436. The work
1648 around described in that entry is no longer needed unless the
1649 default setting is overridden by a confDH_PARAMETERS configuration
1650 setting of '5' or pointing to a 512 bit DH parameter file.
1653 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1654 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1655 and devel/kyua to version 0.20+ and adjust any calling code to work
1656 with Kyuafile and kyua.
1659 The import of openssl to address the FreeBSD-SA-15:10.openssl
1660 security advisory includes a change which rejects handshakes
1661 with DH parameters below 768 bits. sendmail releases prior
1662 to 8.15.2 (not yet released), defaulted to a 512 bit
1663 DH parameter setting for client connections. To work around
1664 this interoperability, sendmail can be configured to use a
1665 2048 bit DH parameter by:
1667 1. Edit /etc/mail/`hostname`.mc
1668 2. If a setting for confDH_PARAMETERS does not exist or
1669 exists and is set to a string beginning with '5',
1670 replace it with '2'.
1671 3. If a setting for confDH_PARAMETERS exists and is set to
1672 a file path, create a new file with:
1673 openssl dhparam -out /path/to/file 2048
1674 4. Rebuild the .cf file:
1675 cd /etc/mail/; make; make install
1676 5. Restart sendmail:
1677 cd /etc/mail/; make restart
1679 A sendmail patch is coming, at which time this file will be
1683 Generation of legacy formatted entries have been disabled by default
1684 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1685 entries were converted to use the new format by default when the new,
1686 machine independent format have been added and supported since FreeBSD
1689 Please see the pwd_mkdb(8) manual page for further details.
1692 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1693 20141231 entry below for information about prerequisites and upgrading,
1694 if you are not already using 3.5.0 or higher.
1697 TI platform code switched to using vendor DTS files and this update
1698 may break existing systems running on Beaglebone, Beaglebone Black,
1701 - dtb files should be regenerated/reinstalled. Filenames are the
1702 same but content is different now
1703 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1704 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1705 addressing scheme is now pin 25 on /dev/gpioc3.
1706 - Pandaboard: /etc/ttys should be updated, serial console device is
1707 now /dev/ttyu2, not /dev/ttyu0
1710 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1711 If you need the GNU extension from groff soelim(1), install groff
1712 from package: pkg install groff, or via ports: textproc/groff.
1715 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1716 defined in symlink(7); previously symlinks were silently ignored.
1719 The const qualifier has been removed from iconv(3) to comply with
1720 POSIX. The ports tree is aware of this from r384038 onwards.
1723 Libraries specified by LIBADD in Makefiles must have a corresponding
1724 DPADD_<lib> variable to ensure correct dependencies. This is now
1725 enforced in src.libnames.mk.
1728 From legacy ata(4) driver was removed support for SATA controllers
1729 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1730 Kernel modules ataahci and ataadaptec were removed completely,
1731 replaced by ahci and mvs modules respectively.
1734 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1735 the 20141231 entry below for information about prerequisites and
1736 upgrading, if you are not already using 3.5.0 or higher.
1739 The 32-bit PowerPC kernel has been changed to a position-independent
1740 executable. This can only be booted with a version of loader(8)
1741 newer than January 31, 2015, so make sure to update both world and
1742 kernel before rebooting.
1745 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1746 but before r278950, the RNG was not seeded properly. Immediately
1747 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1748 ssh keys or openssl keys) that were generated w/ a kernel from that
1749 range. This does not affect programs that directly used /dev/random
1750 or /dev/urandom. All userland uses of arc4random(3) are affected.
1753 The autofs(4) ABI was changed in order to restore binary compatibility
1754 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1755 with the new kernel.
1758 The powerpc64 kernel has been changed to a position-independent
1759 executable. This can only be booted with a new version of loader(8),
1760 so make sure to update both world and kernel before rebooting.
1763 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1764 only release, no new features have been added. Please see the 20141231
1765 entry below for information about prerequisites and upgrading, if you
1766 are not already using 3.5.0.
1769 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1770 taken from the ELF Tool Chain project rather than GNU binutils. They
1771 should be drop-in replacements, with the addition of arm64 support.
1772 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1773 binutils tools, if necessary. See 20150805 for updated information.
1776 The default Unbound configuration now enables remote control
1777 using a local socket. Users who have already enabled the
1778 local_unbound service should regenerate their configuration
1779 by running "service local_unbound setup" as root.
1782 The GNU texinfo and GNU info pages have been removed.
1783 To be able to view GNU info pages please install texinfo from ports.
1786 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1788 As of this release, a prerequisite for building clang, llvm and lldb is
1789 a C++11 capable compiler and C++11 standard library. This means that to
1790 be able to successfully build the cross-tools stage of buildworld, with
1791 clang as the bootstrap compiler, your system compiler or cross compiler
1792 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1793 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1796 On any standard FreeBSD 10.x or 11.x installation, where clang and
1797 libc++ are on by default (that is, on x86 or arm), this should work out
1800 On 9.x installations where clang is enabled by default, e.g. on x86 and
1801 powerpc, libc++ will not be enabled by default, so libc++ should be
1802 built (with clang) and installed first. If both clang and libc++ are
1803 missing, build clang first, then use it to build libc++.
1805 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1806 the instructions for 9.x above.
1808 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1809 default, and do not build clang.
1811 Many embedded systems are resource constrained, and will not be able to
1812 build clang in a reasonable time, or in some cases at all. In those
1813 cases, cross building bootable systems on amd64 is a workaround.
1815 This new version of clang introduces a number of new warnings, of which
1816 the following are most likely to appear:
1820 This warns in two cases, for both C and C++:
1821 * When the code is trying to take the absolute value of an unsigned
1822 quantity, which is effectively a no-op, and almost never what was
1823 intended. The code should be fixed, if at all possible. If you are
1824 sure that the unsigned quantity can be safely cast to signed, without
1825 loss of information or undefined behavior, you can add an explicit
1826 cast, or disable the warning.
1828 * When the code is trying to take an absolute value, but the called
1829 abs() variant is for the wrong type, which can lead to truncation.
1830 If you want to disable the warning instead of fixing the code, please
1831 make sure that truncation will not occur, or it might lead to unwanted
1834 -Wtautological-undefined-compare and
1835 -Wundefined-bool-conversion
1837 These warn when C++ code is trying to compare 'this' against NULL, while
1838 'this' should never be NULL in well-defined C++ code. However, there is
1839 some legacy (pre C++11) code out there, which actively abuses this
1840 feature, which was less strictly defined in previous C++ versions.
1842 Squid and openjdk do this, for example. The warning can be turned off
1843 for C++98 and earlier, but compiling the code in C++11 mode might result
1844 in unexpected behavior; for example, the parts of the program that are
1845 unreachable could be optimized away.
1848 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1849 kernel sources have been removed. The .h files remain, since some
1850 utilities include them. This will need to be fixed later.
1851 If "mount -t oldnfs ..." is attempted, it will fail.
1852 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1853 the utilities will report errors.
1856 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1857 directories to top level SUBDIR variable when their parent
1858 directory is included in LOCAL_DIRS. Users with build systems with
1859 such hierarchies and without SUBDIR entries in the parent
1860 directory Makefiles should add them or add the directories to
1864 faith(4) and faithd(8) have been removed from the base system. Faith
1865 has been obsolete for a very long time.
1868 vt(4), the new console driver, is enabled by default. It brings
1869 support for Unicode and double-width characters, as well as
1870 support for UEFI and integration with the KMS kernel video
1873 You may need to update your console settings in /etc/rc.conf,
1874 most probably the keymap. During boot, /etc/rc.d/syscons will
1875 indicate what you need to do.
1877 vt(4) still has issues and lacks some features compared to
1878 syscons(4). See the wiki for up-to-date information:
1879 https://wiki.freebsd.org/Newcons
1881 If you want to keep using syscons(4), you can do so by adding
1882 the following line to /boot/loader.conf:
1886 pjdfstest has been integrated into kyua as an opt-in test suite.
1887 Please see share/doc/pjdfstest/README for more details on how to
1891 gperf has been removed from the base system for architectures
1892 that use clang. Ports that require gperf will obtain it from the
1896 pjdfstest has been moved from tools/regression/pjdfstest to
1900 At svn r271982, The default linux compat kernel ABI has been adjusted
1901 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1902 update. If you wish to continue using the linux-f10 compat ports,
1903 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1904 encouraged to update their linux-compat packages to linux-c6 during
1905 their next update cycle.
1908 The ofwfb driver, used to provide a graphics console on PowerPC when
1909 using vt(4), no longer allows mmap() of all physical memory. This
1910 will prevent Xorg on PowerPC with some ATI graphics cards from
1911 initializing properly unless x11-servers/xorg-server is updated to
1915 The xdev targets have been converted to using TARGET and
1916 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1919 The default unbound configuration has been modified to address
1920 issues with reverse lookups on networks that use private
1921 address ranges. If you use the local_unbound service, run
1922 "service local_unbound setup" as root to regenerate your
1923 configuration, then "service local_unbound reload" to load the
1927 The GNU texinfo and GNU info pages are not built and installed
1928 anymore, WITH_INFO knob has been added to allow to built and install
1930 UPDATE: see 20150102 entry on texinfo's removal
1933 The GNU readline library is now an INTERNALLIB - that is, it is
1934 statically linked into consumers (GDB and variants) in the base
1935 system, and the shared library is no longer installed. The
1936 devel/readline port is available for third party software that
1940 The Itanium architecture (ia64) has been removed from the list of
1941 known architectures. This is the first step in the removal of the
1945 Commit r268115 has added NFSv4.1 server support, merged from
1946 projects/nfsv4.1-server. Since this includes changes to the
1947 internal interfaces between the NFS related modules, a full
1948 build of the kernel and modules will be necessary.
1949 __FreeBSD_version has been bumped.
1952 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1953 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1954 which differs from the behaviour controlled by this knob.)
1957 Maximal length of the serial number in CTL was increased from 16 to
1958 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1959 and ctld, need to be rebuilt to work with a new kernel.
1962 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1963 1 respectively to match the upstream numbers. They were out of
1964 sync because, when they were originally added to FreeBSD, the
1965 upstream versions were not respected. These libraries are private
1966 and not yet built by default, so renumbering them should be a
1967 non-issue. However, unclean source trees will yield broken test
1968 programs once the operator executes "make delete-old-libs" after a
1969 "make installworld".
1971 Additionally, the atf-sh binary was made private by moving it into
1972 /usr/libexec/. Already-built shell test programs will keep the
1973 path to the old binary so they will break after "make delete-old"
1976 If you are using WITH_TESTS=yes (not the default), wipe the object
1977 tree and rebuild from scratch to prevent spurious test failures.
1978 This is only needed once: the misnumbered libraries and misplaced
1979 binaries have been added to OptionalObsoleteFiles.inc so they will
1980 be removed during a clean upgrade.
1983 Clang and llvm have been upgraded to 3.4.1 release.
1986 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1987 be removed to avoid issues in the future (and has been added to
1991 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1992 past, it affected all builds that used the bsd.*.mk files. The old
1993 behavior was a bug, but people may have relied upon it. To get this
1994 behavior back, you can .include /etc/src.conf from /etc/make.conf
1995 (which is still global and isn't changed). This also changes the
1996 behavior of incremental builds inside the tree of individual
1997 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1998 Although this has survived make universe and some upgrade scenarios,
1999 other upgrade scenarios may have broken. At least one form of
2000 temporary breakage was fixed with MAKESYSPATH settings for buildworld
2001 as well... In cases where MAKESYSPATH isn't working with this
2002 setting, you'll need to set it to the full path to your tree.
2004 One side effect of all this cleaning up is that bsd.compiler.mk
2005 is no longer implicitly included by bsd.own.mk. If you wish to
2006 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
2010 The lindev device has been removed since /dev/full has been made a
2011 standard device. __FreeBSD_version has been bumped.
2014 The knob WITHOUT_VI was added to the base system, which controls
2015 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
2016 in order to reorder files share/termcap and didn't build ex(1) as a
2017 build tool, so building/installing with WITH_VI is highly advised for
2018 build hosts for older releases.
2020 This issue has been fixed in stable/9 and stable/10 in r277022 and
2021 r276991, respectively.
2024 The YES_HESIOD knob has been removed. It has been obsolete for
2025 a decade. Please move to using WITH_HESIOD instead or your builds
2026 will silently lack HESIOD.
2029 The uart(4) driver has been changed with respect to its handling
2030 of the low-level console. Previously the uart(4) driver prevented
2031 any process from changing the baudrate or the CLOCAL and HUPCL
2032 control flags. By removing the restrictions, operators can make
2033 changes to the serial console port without having to reboot.
2034 However, when getty(8) is started on the serial device that is
2035 associated with the low-level console, a misconfigured terminal
2036 line in /etc/ttys will now have a real impact.
2037 Before upgrading the kernel, make sure that /etc/ttys has the
2038 serial console device configured as 3wire without baudrate to
2039 preserve the previous behaviour. E.g:
2040 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
2043 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
2044 to improve performance. To re-enable it, if needed, run rpcbind
2045 with command line option -W.
2048 Switched back to the GPL dtc compiler due to updates in the upstream
2049 dts files not being supported by the BSDL dtc compiler. You will need
2050 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
2051 may result while building dtb files during a kernel build if you fail
2052 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
2055 Clang and llvm have been upgraded to 3.4 release.
2058 The nve(4) driver has been removed. Please use the nfe(4) driver
2059 for NVIDIA nForce MCP Ethernet adapters instead.
2062 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
2063 This could cause certain C++ applications using shared libraries built
2064 against the previous version of libc++ to crash. The incompatibility
2065 has now been fixed, but any C++ applications or shared libraries built
2066 between r261283 and r261801 should be recompiled.
2069 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
2070 capability mode support. Please note that enabling the feature in
2071 kernel is still highly recommended.
2074 OpenSSH is now built with sandbox support, and will use sandbox as
2075 the default privilege separation method. This requires Capsicum
2076 capability mode support in kernel.
2079 The libelf and libdwarf libraries have been updated to newer
2080 versions from upstream. Shared library version numbers for
2081 these two libraries were bumped. Any ports or binaries
2082 requiring these two libraries should be recompiled.
2083 __FreeBSD_version is bumped to 1100006.
2086 If a Makefile in a tests/ directory was auto-generating a Kyuafile
2087 instead of providing an explicit one, this would prevent such
2088 Makefile from providing its own Kyuafile in the future during
2089 NO_CLEAN builds. This has been fixed in the Makefiles but manual
2090 intervention is needed to clean an objdir if you use NO_CLEAN:
2091 # find /usr/obj -name Kyuafile | xargs rm -f
2094 The behavior of gss_pseudo_random() for the krb5 mechanism
2095 has changed, for applications requesting a longer random string
2096 than produced by the underlying enctype's pseudo-random() function.
2097 In particular, the random string produced from a session key of
2098 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
2099 be different at the 17th octet and later, after this change.
2100 The counter used in the PRF+ construction is now encoded as a
2101 big-endian integer in accordance with RFC 4402.
2102 __FreeBSD_version is bumped to 1100004.
2105 The WITHOUT_ATF build knob has been removed and its functionality
2106 has been subsumed into the more generic WITHOUT_TESTS. If you were
2107 using the former to disable the build of the ATF libraries, you
2108 should change your settings to use the latter.
2111 The default version of mtree is nmtree which is obtained from
2112 NetBSD. The output is generally the same, but may vary
2113 slightly. If you found you need identical output adding
2114 "-F freebsd9" to the command line should do the trick. For the
2115 time being, the old mtree is available as fmtree.
2118 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
2119 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
2120 1.1.4_8 and verify bsdyml not linked in, before running "make
2122 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
2124 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
2127 The stable/10 branch has been created in subversion from head
2134 Sometimes, obscure build problems are the result of environment
2135 poisoning. This can happen because the make utility reads its
2136 environment when searching for values for global variables. To run
2137 your build attempts in an "environmental clean room", prefix all make
2138 commands with 'env -i '. See the env(1) manual page for more details.
2139 Occasionally a build failure will occur with "make -j" due to a race
2140 condition. If this happens try building again without -j, and please
2141 report a bug if it happens consistently.
2143 When upgrading from one major version to another it is generally best to
2144 upgrade to the latest code in the currently installed branch first, then
2145 do an upgrade to the new branch. This is the best-tested upgrade path,
2146 and has the highest probability of being successful. Please try this
2147 approach if you encounter problems with a major version upgrade. Since
2148 the stable 4.x branch point, one has generally been able to upgrade from
2149 anywhere in the most recent stable branch to head / current (or even the
2150 last couple of stable branches). See the top of this file when there's
2153 The update process will emit an error on an attempt to perform a build
2154 or install from a FreeBSD version below the earliest supported version.
2155 When updating from an older version the update should be performed one
2156 major release at a time, including running `make delete-old` at each
2159 When upgrading a live system, having a root shell around before
2160 installing anything can help undo problems. Not having a root shell
2161 around can lead to problems if pam has changed too much from your
2162 starting point to allow continued authentication after the upgrade.
2164 This file should be read as a log of events. When a later event changes
2165 information of a prior event, the prior event should not be deleted.
2166 Instead, a pointer to the entry with the new information should be
2167 placed in the old entry. Readers of this file should also sanity check
2168 older entries before relying on them blindly. Authors of new entries
2169 should write them with this in mind.
2173 When upgrading the boot ZFS pool to a new version, always follow
2176 1.) recompile and reinstall the ZFS boot loader and boot block
2177 (this is part of "make buildworld" and "make installworld")
2179 2.) update the ZFS boot block on your boot drive
2181 The following example updates the ZFS boot block on the first
2182 partition (freebsd-boot) of a GPT partitioned drive ada0:
2183 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
2185 Non-boot pools do not need these updates.
2189 If you are updating from a prior version of FreeBSD (even one just
2190 a few days old), you should follow this procedure. It is the most
2191 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2193 make kernel-toolchain
2194 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2195 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2197 To test a kernel once
2198 ---------------------
2199 If you just want to boot a kernel once (because you are not sure
2200 if it works, or if you want to boot a known bad kernel to provide
2201 debugging information) run
2202 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2203 nextboot -k testkernel
2205 To rebuild everything and install it on the current system.
2206 -----------------------------------------------------------
2207 # Note: sometimes if you are running current you gotta do more than
2208 # is listed here if you are upgrading from a really old current.
2210 <make sure you have good level 0 dumps>
2212 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2213 make installkernel KERNCONF=YOUR_KERNEL_HERE
2215 <reboot in single user> [3]
2222 To cross-install current onto a separate partition
2223 --------------------------------------------------
2224 # In this approach we use a separate partition to hold
2225 # current's root, 'usr', and 'var' directories. A partition
2226 # holding "/", "/usr" and "/var" should be about 2GB in
2229 <make sure you have good level 0 dumps>
2232 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2233 <maybe newfs current's root partition>
2234 <mount current's root partition on directory ${CURRENT_ROOT}>
2235 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
2236 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2237 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2238 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2239 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2240 <reboot into current>
2241 <do a "native" rebuild/install as described in the previous section>
2242 <maybe install compatibility libraries from ports/misc/compat*>
2246 To upgrade in-place from stable to current
2247 ----------------------------------------------
2248 <make sure you have good level 0 dumps>
2250 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
2251 make installkernel KERNCONF=YOUR_KERNEL_HERE
2253 <reboot in single user> [3]
2260 Make sure that you've read the UPDATING file to understand the
2261 tweaks to various things you need. At this point in the life
2262 cycle of current, things change often and you are on your own
2263 to cope. The defaults can also change, so please read ALL of
2264 the UPDATING entries.
2266 Also, if you are tracking -current, you must be subscribed to
2267 freebsd-current@freebsd.org. Make sure that before you update
2268 your sources that you have read and understood all the recent
2269 messages there. If in doubt, please track -stable which has
2270 much fewer pitfalls.
2272 [1] If you have third party modules, such as vmware, you
2273 should disable them at this point so they don't crash your
2276 [3] From the bootblocks, boot -s, and then do
2280 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed
2281 cd src # full path to source
2282 adjkerntz -i # if CMOS is wall time
2283 Also, when doing a major release upgrade, it is required that
2284 you boot into single user mode to do the installworld.
2286 [4] Note: This step is non-optional. Failure to do this step
2287 can result in a significant reduction in the functionality of the
2288 system. Attempting to do it by hand is not recommended and those
2289 that pursue this avenue should read this file carefully, as well
2290 as the archives of freebsd-current and freebsd-hackers mailing lists
2291 for potential gotchas. The -U option is also useful to consider.
2292 See mergemaster(8) for more information.
2294 [5] Usually this step is a no-op. However, from time to time
2295 you may need to do this if you get unknown user in the following
2296 step. It never hurts to do it all the time. You may need to
2297 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2298 install) after the buildworld before this step if you last updated
2299 from current before 20130425 or from -stable before 20130430.
2301 [6] This only deletes old files and directories. Old libraries
2302 can be deleted by "make delete-old-libs", but you have to make
2303 sure that no program is using those libraries anymore.
2305 [8] The new kernel must be able to run existing binaries used by an
2306 installworld. When upgrading across major versions, the new kernel's
2307 configuration must include the correct COMPAT_FREEBSD<n> option for
2308 existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure
2309 to do so may leave you with a system that is hard to boot to recover. A
2310 GENERIC kernel will include suitable compatibility options to run
2311 binaries from older branches. Note that the ability to run binaries
2312 from unsupported branches is not guaranteed.
2314 Make sure that you merge any new devices from GENERIC since the
2315 last time you updated your kernel config file. Options also
2316 change over time, so you may need to adjust your custom kernels
2319 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2320 "?=" instead of the "=" assignment operator, so that buildworld can
2321 override the CPUTYPE if it needs to.
2323 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2324 not on the command line, or in /etc/make.conf. buildworld will
2325 warn if it is improperly defined.
2328 This file contains a list, in reverse chronological order, of major
2329 breakages in tracking -current. It is not guaranteed to be a complete
2330 list of such breakages, and only contains entries since September 23, 2011.
2331 If you need to see UPDATING entries from before that date, you will need
2332 to fetch an UPDATING file from an older FreeBSD release.
2334 Copyright information:
2336 Copyright 1998-2009 M. Warner Losh <imp@FreeBSD.org>
2338 Redistribution, publication, translation and use, with or without
2339 modification, in full or in part, in any form or format of this
2340 document are permitted without further permission from the author.
2342 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2343 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2344 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2345 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2346 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2347 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2348 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2349 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2350 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2351 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2352 POSSIBILITY OF SUCH DAMAGE.
2354 Contact Warner Losh if you have any questions about your use of