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 WITH_MALLOC_PRODUCTION in /etc/src.conf and rebuild
26 world, or to merely disable the most expensive debugging functionality
27 at runtime, run "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. A fallback to /boot has been added for mountroot.
42 Pool auto import behavior at boot has been moved from the kernel module
43 to an explicit "zpool import -a" in one of the rc scripts enabled by
44 zfs_enable=YES. This means your non-root zpools won't auto import until
45 you upgrade your /etc/rc.d files.
48 The resume code now notifies devd with the 'kernel' system
49 rather than the old 'kern' subsystem to be consistent with
50 other use. The old notification will be created as well, but
51 will be removed prior to FreeBSD 14.0.
54 r362275 changed the internal API between the kernel RPC and the
55 NFS modules. As such, all the modules must be recompiled from
59 r364330 modified the internal API used between the NFS modules.
60 As such, all the NFS modules must be re-compiled from sources.
63 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
64 been upgraded to 11.0.0. Please see the 20141231 entry below for
65 information about prerequisites and upgrading, if you are not already
66 using clang 3.5.0 or higher.
69 r364092 modified the internal ABI used between the kernel NFS
70 modules. As such, all of these modules need to be rebuilt
71 from sources, so a version bump was done.
74 Makefile.inc has been updated to work around the issue documented in
75 20200729. It was a case where the optimization of using symbolic links
76 to point to binaries created a situation where we'd run new binaries
77 with old libraries starting midway through the installworld process.
80 r363679 has redefined some undefined behavior in regcomp(3); notably,
81 extraneous escapes of most ordinary characters will no longer be
82 accepted. An exp-run has identified all of the problems with this in
83 ports, but other non-ports software may need extra escapes removed to
86 Because of this change, installworld may encounter the following error
87 from rtld: Undefined symbol "regcomp@FBSD_1.6" -- It is imperative that
88 you do not halt installworld. Instead, let it run to completion (whether
89 successful or not) and run installworld once more.
92 A new implementation of bc and dc has been imorted in r362681. This
93 implementation corrects non-conformant behavior of the previous bc
94 and adds GNU bc compatible options. It offers a number of extensions,
95 is much faster on large values, and has support for message catalogs
96 (a number of languages are already supported, contributions of further
97 languages welcome). The option WITHOUT_GH_BC can be used to build the
98 world with the previous versions of bc and dc.
101 r362639 changed the internal API used between the NFS kernel modules.
102 As such, they all need to be rebuilt from sources.
105 r362158 changed the arguments for VFS_CHECKEXP(). As such, any
106 out of tree file systems need to be modified and rebuilt.
107 Also, any file systems that are modules must be rebuilt.
110 read(2) of a directory fd is now rejected by default. root may
111 re-enable it for system root only on non-ZFS filesystems with the
112 security.bsd.allow_read_dir sysctl(8) MIB if
113 security.bsd.suser_enabled=1.
115 It may be advised to setup aliases for grep to default to `-d skip` if
116 commonly non-recursively grepping a list that includes directories and
117 the potential for the resulting stderr output is not tolerable. Example
118 aliases are now installed, commented out, in /root/.cshrc and
122 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
123 been upgraded to 10.0.1. Please see the 20141231 entry below for
124 information about prerequisites and upgrading, if you are not already
125 using clang 3.5.0 or higher.
128 Support for obsolete compilers has been removed from the build system.
129 Clang 6 and GCC 6.4 are the minimum supported versions.
132 closefrom(2) has been moved under COMPAT12, and replaced in libc with a
133 stub that calls close_range(2). If using a custom kernel configuration,
134 you may want to ensure that the COMPAT_FREEBSD12 option is included, as
135 a slightly older -CURRENT userland and older FreeBSD userlands may not
136 be functional without closefrom(2).
139 Upstream DTS from Linux 5.6 was merged and they now have the SID
140 and THS (Secure ID controller and THermal Sensor) node present.
141 The DTB overlays have now been removed from the tree for the H3/H5 and
142 A64 SoCs and the aw_sid and aw_thermal driver have been updated to
143 deal with upstream DTS. If you are using those overlays you need to
144 remove them from loader.conf and update the DTBs on the FAT partition.
147 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
148 been upgraded to 10.0.0. Please see the 20141231 entry below for
149 information about prerequisites and upgrading, if you are not already
150 using clang 3.5.0 or higher.
153 The amd(8) automount daemon has been removed from the source tree.
154 As of FreeBSD 10.1 autofs(5) is the preferred tool for automounting.
155 amd is still available in the sysutils/am-utils port.
158 Removed brooktree driver (bktr.4) from the tree.
161 The WITH_GPL_DTC option has been removed. The BSD-licenced device tree
162 compiler in usr.bin/dtc is used on all architectures which use dtc, and
163 the GPL dtc is available (if needed) from the sysutils/dtc port.
166 The WITHOUT_LLVM_LIBUNWIND option has been removed. LLVM's libunwind
167 is used by all supported CPU architectures.
170 GCC 4.2.1 has been removed from the tree. The WITH_GCC,
171 WITH_GCC_BOOTSTRAP, and WITH_GNUCXX options are no longer available.
172 Users who wish to build FreeBSD with GCC must use the external toolchain
176 ncurses has been updated to a newer version (6.2-20200215). Given the ABI
177 has changed, users will have to rebuild all the ports that are linked to
181 The size of struct vnet and the magic cookie have changed.
182 Users need to recompile libkvm and all modules using VIMAGE
183 together with their new kernel.
186 Defining the long deprecated NO_CTF, NO_DEBUG_FILES, NO_INSTALLLIB,
187 NO_MAN, NO_PROFILE, and NO_WARNS variables is now an error. Update
188 your Makefiles and scripts to define MK_<var>=no instead as required.
190 One exception to this is that program or library Makefiles should
191 define MAN to empty rather than setting MK_MAN=no.
194 Clang/LLVM is now the default compiler and LLD the default
198 make universe no longer uses GCC 4.2.1 on any architectures.
199 Architectures not supported by in-tree Clang/LLVM require an
200 external toolchain package.
203 GCC 4.2.1 is now not built by default, as part of the GCC 4.2.1
204 retirement plan. Specifically, the GCC, GCC_BOOTSTRAP, and GNUCXX
205 options default to off for all supported CPU architectures. As a
206 short-term transition aid they may be enabled via WITH_* options.
207 GCC 4.2.1 is expected to be removed from the tree on 2020-03-31.
210 Support for armv5 has been disconnected and is being removed. The
211 machine combination MACHINE=arm MACHINE_ARCH=arm is no longer valid.
212 You must now use a MACHINE_ARCH of armv6 or armv7. The default
213 MACHINE_ARCH for MACHINE=arm is now armv7.
216 Clang/LLVM is now the default compiler for all powerpc architectures.
217 LLD is now the default linker for powerpc64. The change for powerpc64
218 also includes a change to the ELFv2 ABI, incompatible with the existing
222 Kernel-loadable random(4) modules are no longer unloadable.
225 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
226 been upgraded to 9.0.1. Please see the 20141231 entry below for
227 information about prerequisites and upgrading, if you are not already
228 using clang 3.5.0 or higher.
231 r355677 has modified the internal interface used between the
232 NFS modules in the kernel. As such, they must all be upgraded
233 simultaneously. I will do a version bump for this.
236 The root certificates of the Mozilla CA Certificate Store have been
237 imported into the base system and can be managed with the certctl(8)
238 utility. If you have installed the security/ca_root_nss port or package
239 with the ETCSYMLINK option (the default), be advised that there may be
240 differences between those included in the port and those included in
241 base due to differences in nss branch used as well as general update
242 frequency. Note also that certctl(8) cannot manage certs in the
243 format used by the security/ca_root_nss port.
246 The amd(8) automount daemon has been disabled by default, and will be
247 removed in the future. As of FreeBSD 10.1 the autofs(5) is available
251 The nctgpio and wbwd drivers have been moved to the superio bus.
252 If you have one of these drivers in a kernel configuration, then
253 you should add device superio to it. If you use one of these drivers
254 as a module and you compile a custom set of modules, then you should
255 add superio to the set.
258 KPIs for network drivers to access interface addresses have changed.
259 Users need to recompile NIC driver modules together with kernel.
262 The net.link.tap.user_open sysctl no longer prevents user opening of
263 already created /dev/tapNN devices. Access is still controlled by
264 node permissions, just like tun devices. The net.link.tap.user_open
265 sysctl is now used only to allow users to perform devfs cloning of
266 tap devices, and the subsequent open may not succeed if the user is not
267 in the appropriate group. This sysctl may be deprecated/removed
268 completely in the future.
271 mips, powerpc, and sparc64 are no longer built as part of
272 universe / tinderbox unless MAKE_OBSOLETE_GCC is defined. If
273 not defined, mips, powerpc, and sparc64 builds will look for
274 the xtoolchain binaries and if installed use them for universe
275 builds. As llvm 9.0 becomes vetted for these architectures, they
276 will be removed from the list.
279 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
280 been upgraded to 9.0.0. Please see the 20141231 entry below for
281 information about prerequisites and upgrading, if you are not already
282 using clang 3.5.0 or higher.
285 The hpt27xx, hptmv, hptnr, and hptrr drivers have been removed from
286 GENERIC. They are available as modules and can be loaded by adding
287 to /boot/loader.conf hpt27xx_load="YES", hptmv_load="YES",
288 hptnr_load="YES", or hptrr_load="YES", respectively.
291 ntpd no longer by default locks its pages in memory, allowing them
292 to be paged out by the kernel. Use rlimit memlock to restore
293 historic BSD behaviour. For example, add "rlimit memlock 32"
294 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
297 Several of ping6's options have been renamed for better consistency
298 with ping. If you use any of -ARWXaghmrtwx, you must update your
299 scripts. See ping6(8) for details.
302 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
303 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
304 been removed from mount_fusefs(8). You can safely remove them from
305 your scripts, because they had no effect.
307 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
308 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
309 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
310 sysctls have been removed. If you felt the need to set any of them to
311 a non-default value, please tell asomers@FreeBSD.org why.
314 Default permissions on the /var/account/acct file (and copies of it
315 rotated by periodic daily scripts) are changed from 0644 to 0640
316 because the file contains sensitive information that should not be
317 world-readable. If the /var/account directory must be created by
318 rc.d/accounting, the mode used is now 0750. Admins who use the
319 accounting feature are encouraged to change the mode of an existing
320 /var/account directory to 0750 or 0700.
323 Entropy collection and the /dev/random device are no longer optional
324 components. The "device random" option has been removed.
325 Implementations of distilling algorithms can still be made loadable
326 with "options RANDOM_LOADABLE" (e.g., random_fortuna.ko).
329 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
330 been upgraded to 8.0.1. Please see the 20141231 entry below for
331 information about prerequisites and upgrading, if you are not already
332 using clang 3.5.0 or higher.
335 A fix was applied to i386 kernel modules to avoid panics with
336 dpcpu or vnet. Users need to recompile i386 kernel modules
337 having pcpu or vnet sections or they will refuse to load.
340 User-wired pages now have their own counter,
341 vm.stats.vm.v_user_wire_count. The vm.max_wired sysctl was renamed
342 to vm.max_user_wired and changed from an unsigned int to an unsigned
343 long. bhyve VMs wired with the -S are now subject to the user
344 wiring limit; the vm.max_user_wired sysctl may need to be tuned to
345 avoid running into the limit.
348 The IPSEC option has been removed from GENERIC. Users requiring
349 ipsec(4) must now load the ipsec(4) kernel module.
352 The tap(4) driver has been folded into tun(4), and the module has been
353 renamed to tuntap. You should update any kld_list="if_tap" or
354 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
355 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
356 module instead, and "device tap" or "device tun" entries in kernel
357 config files to select the tuntap device instead.
360 The following knobs have been added related to tradeoffs between
361 safe use of the random device and availability in the absence of
364 kern.random.initial_seeding.bypass_before_seeding: tunable; set
365 non-zero to bypass the random device prior to seeding, or zero to
366 block random requests until the random device is initially seeded.
367 For now, set to 1 (unsafe) by default to restore pre-r346250 boot
368 availability properties.
370 kern.random.initial_seeding.read_random_bypassed_before_seeding:
371 read-only diagnostic sysctl that is set when bypass is enabled and
372 read_random(9) is bypassed, to enable programmatic handling of this
373 initial condition, if desired.
375 kern.random.initial_seeding.arc4random_bypassed_before_seeding:
376 Similar to the above, but for for arc4random(9) initial seeding.
378 kern.random.initial_seeding.disable_bypass_warnings: tunable; set
379 non-zero to disable warnings in dmesg when the same conditions are
380 met as for the diagnostic sysctls above. Defaults to zero, i.e.,
381 produce warnings in dmesg when the conditions are met.
384 The loadable random module KPI has changed; the random_infra_init()
385 routine now requires a 3rd function pointer for a bool (*)(void)
386 method that returns true if the random device is seeded (and
387 therefore unblocked).
390 r345895 reverts r320698. This implies that an nfsuserd(8) daemon
391 built from head sources between r320757 (July 6, 2017) and
392 r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
393 is added to the command line.
394 nfsuserd daemons built from head sources that are post-r338192 are
395 not affected and should continue to work.
398 The fuse(4) module has been renamed to fusefs(4) for consistency with
399 other filesystems. You should update any kld_load="fuse" entries in
400 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
401 "options FUSE" entries in kernel config files.
404 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
405 8.0.0. Please see the 20141231 entry below for information about
406 prerequisites and upgrading, if you are not already using clang 3.5.0
410 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
411 compiled into your custom kernel, add 'device xz' statement to the
415 drm and drm2 have been removed from the tree. Please see
416 https://wiki.freebsd.org/Graphics for the latest information on
417 migrating to the drm ports.
420 Iflib is no longer unconditionally compiled into the kernel. Drivers
421 using iflib and statically compiled into the kernel, now require
422 the 'device iflib' config option. For the same drivers loaded as
423 modules on kernels not having 'device iflib', the iflib.ko module
424 is loaded automatically.
427 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
428 options no longer exist since r343219 and r343427 respectively;
429 nothing uses them, so they should be just removed from custom
433 r342635 changes the way efibootmgr(8) works by requiring users to add
434 the -b (bootnum) parameter for commands where the bootnum was previously
435 specified with each option. For example 'efibootmgr -B 0001' is now
436 'efibootmgr -B -b 0001'.
439 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
440 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
441 servers that have vfs.nfsd.nfs_privport set will only allow mounts
442 from clients using a reserved port#. Since both the FreeBSD and Linux
443 NFSv4 clients use reserved port#s by default, this should not affect
447 The XLP config has been removed. We can't support 64-bit atomics in this
448 kernel because it is running in 32-bit mode. XLP users must transition
449 to running a 64-bit kernel (XLP64 or XLPN32).
451 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
452 the preferred emulator today and we don't need two different ones.
454 The old sibyte / swarm / Broadcom BCM1250 support has been
455 removed from the mips port.
458 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
459 7.0.1. Please see the 20141231 entry below for information about
460 prerequisites and upgrading, if you are not already using clang 3.5.0
464 Remove the timed and netdate programs from the base tree. Setting
465 the time with these daemons has been obsolete for over a decade.
468 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
469 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
470 it produces broken binaries when ifuncs are in use. Users needing
471 GNU ld should install the binutils port or package.
474 The BSD crtbegin and crtend code has been enabled by default. It has
475 had extensive testing on amd64, arm64, and i386. It can be disabled
476 by building a world with -DWITHOUT_BSD_CRTBEGIN.
479 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
480 has been converted to a port (misc/ctm) and will be removed from
481 FreeBSD-13. It is available as a package (ctm) for all supported
485 The default newsyslog.conf(5) file has been changed to only include
486 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
487 the filenames end in '.conf' and do not begin with a '.'.
489 You should check the configuration files in these two directories match
490 this naming convention. You can verify which configuration files are
491 being included using the command:
495 Ports for the DRM modules have been simplified. Now, amd64 users should
496 just install the drm-kmod port. All others should install
499 Graphics hardware that's newer than about 2010 usually works with
500 drm-kmod. For hardware older than 2013, however, some users will need
501 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
502 than 2008 usually only works in drm-legacy-kmod. The graphics team can
503 only commit to hardware made since 2013 due to the complexity of the
504 market and difficulty to test all the older cards effectively. If you
505 have hardware supported by drm-kmod, you are strongly encouraged to use
506 that as you will get better support.
508 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
509 elsewhere, the drm and drm2 modules will be eliminated from the src base
510 soon (with a limited exception for arm). Please update to the package
511 asap and report any issues to x11@freebsd.org.
513 Generally, anybody using the drm*-kmod packages should add
514 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
515 cross-threading surprises, especially with automatic driver
516 loading from X11 startup. These will become the defaults in 13-current
520 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
521 custom kernel and module loading configuration files must be updated
522 accordingly. Moreover, interfaces previous presented as ixlvN to the
523 system are now exposed as iavfN and network configuration files must
524 be adjusted as necessary.
527 OpenSSL has been updated to version 1.1.1. This update included
528 additional various API changes throughout the base system. It is
529 important to rebuild third-party software after upgrading. The value
530 of __FreeBSD_version has been bumped accordingly.
533 The legacy DRM modules and drivers have now been added to the loader's
534 module blacklist, in favor of loading them with kld_list in rc.conf(5).
535 The module blacklist may be overridden with the loader.conf(5)
536 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
540 The cam(4) based nda(4) driver will be used over nvd(4) by default on
541 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
542 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
543 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
547 Reproducible build mode is now on by default, in preparation for
548 FreeBSD 12.0. This eliminates build metadata such as the user,
549 host, and time from the kernel (and uname), unless the working tree
550 corresponds to a modified checkout from a version control system.
551 The previous behavior can be obtained by setting the /etc/src.conf
552 knob WITHOUT_REPRODUCIBLE_BUILD.
555 The Yarrow CSPRNG has been removed from the kernel as it has not been
556 supported by its designers since at least 2003. Fortuna has been the
557 default since FreeBSD-11.
560 devctl freeze/thaw have gone into the tree, the rc scripts have been
561 updated to use them and devmatch has been changed. You should update
562 kernel, userland and rc scripts all at the same time.
565 The default interpreter has been switched from 4th to Lua.
566 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
567 interpreter. If you have custom FORTH code you will need to set
568 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
569 src.conf for the build. This will create default hard links between
570 loader and loader_4th instead of loader and loader_lua, the new default.
571 If you are using UEFI it will create the proper hard link to loader.efi.
573 bhyve uses userboot.so. It remains 4th-only until some issues are solved
574 regarding coexisting with multiple versions of FreeBSD are resolved.
577 ls(1) now respects the COLORTERM environment variable used in other
578 systems and software to indicate that a colored terminal is both
579 supported and desired. If ls(1) is suddenly emitting colors, they may
580 be disabled again by either removing the unwanted COLORTERM from your
581 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
582 may not be observed in a future release.
585 The default pager for most commands has been changed to "less". To
586 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
590 The jedec_ts(4) driver has been removed. A superset of its functionality
591 is available in the jedec_dimm(4) driver, and the manpage for that
592 driver includes migration instructions. If you have "device jedec_ts"
593 in your kernel configuration file, it must be removed.
596 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
597 This should have no effect if the kernel is booted via BIOS/legacy boot.
598 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
599 has a buggy firmware that prevents a successful boot due to use of
603 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
604 support has been removed from the tree. These ports were
605 obsolete and/or known to be broken for many years.
608 loader.efi has been augmented to participate more fully in the
609 UEFI boot manager protocol. loader.efi will now look at the
610 BootXXXX environment variable to determine if a specific kernel
611 or root partition was specified. XXXX is derived from BootCurrent.
612 efibootmgr(8) manages these standard UEFI variables.
615 zfsloader's functionality has now been folded into loader.
616 zfsloader is no longer necessary once you've updated your
617 boot blocks. For a transition period, we will install a
618 hardlink for zfsloader to loader to allow a smooth transition
619 until the boot blocks can be updated (hard link because old
620 zfs boot blocks don't understand symlinks).
623 ARM64 now have efifb support, if you want to have serial console
624 on your arm64 board when an screen is connected and the bootloader
625 setup a frame buffer for us to use, just add :
629 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
630 an screen connected as the firmware will setup a frame buffer are that
631 u-boot will expose as an EFI frame buffer.
634 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
635 or take steps to update /etc/passwd before doing installworld on
636 existing systems. Do not skip the "mergemaster -Fp" step before
637 installworld, as described in the update procedures near the bottom
638 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
639 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
640 the ntp config file contain options that change file/dir locations.
641 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
642 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
643 taking steps to ensure that all required files/dirs are accessible
647 Big endian arm support has been removed.
650 The static environment setup in kernel configs is no longer mutually
651 exclusive with the loader(8) environment by default. In order to
652 restore the previous default behavior of disabling the loader(8)
653 environment if a static environment is present, you must specify
654 loader_env.disabled=1 in the static environment.
657 The ABI of syscalls used by management tools like sockstat and
658 netstat has been broken to allow 32-bit binaries to work on
659 64-bit kernels without modification. These programs will need
660 to match the kernel in order to function. External programs may
661 require minor modifications to accommodate a change of type in
662 structures from pointers to 64-bit virtual addresses.
665 On i386 and amd64 atomics are now inlined. Out of tree modules using
666 atomics will need to be rebuilt.
669 The '%I' format in the kern.corefile sysctl limits the number of
670 core files that a process can generate to the number stored in the
671 debug.ncores sysctl. The '%I' format is replaced by the single digit
672 index. Previously, if all indexes were taken the kernel would overwrite
673 only a core file with the highest index in a filename.
674 Currently the system will create a new core file if there is a free
675 index or if all slots are taken it will overwrite the oldest one.
678 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
679 6.0.1. Please see the 20141231 entry below for information about
680 prerequisites and upgrading, if you are not already using clang 3.5.0
684 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
685 needed to be changed to work with it. This change was made with r335763
686 and requires a mergemaster / etcupdate / etc to update the installed
690 r334930 changed the interface between the NFS modules, so they all
691 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
694 As of r334391 lld is the default amd64 system linker; it is installed
695 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
699 The kernel / userland interface for devinfo changed, so you'll
700 need a new kernel and userland as a pair for it to work (rebuilding
701 lib/libdevinfo is all that's required). devinfo and devmatch will
702 not work, but everything else will when there's a mismatch.
705 The on-disk format for hwpmc callchain records has changed to include
706 threadid corresponding to a given record. This changes the field offsets
707 and thus requires that libpmcstat be rebuilt before using a kernel
711 The vxge(4) driver has been removed. This driver was introduced into
712 HEAD one week before the Exar left the Ethernet market and is not
713 known to be used. If you have device vxge in your kernel config file
717 The amd64 kernel now requires a ld that supports ifunc to produce a
718 working kernel, either lld or a newer binutils. lld is built by default
719 on amd64, and the 'buildkernel' target uses it automatically. However,
720 it is not the default linker, so building the kernel the traditional
721 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
722 binutils port/package). lld will soon be default, and this requirement
725 NOTE: As of r334391 lld is the default system linker on amd64, and no
726 workaround is necessary.
729 The nxge(4) driver has been removed. This driver was for PCI-X 10g
730 cards made by s2io/Neterion. The company was acquired by Exar and
731 no longer sells or supports Ethernet products. If you have device
732 nxge in your kernel config file it must be removed.
735 The tz database (tzdb) has been updated to 2018e. This version more
736 correctly models time stamps in time zones with negative DST such as
737 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
738 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
739 time zone abbreviations and the tm_isdst flag.
742 The ixgb(4) driver has been removed. This driver was for an early and
743 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
744 quickly shifted to the long lived ixgbe family. If you have device
745 ixgb in your kernel config file it must be removed.
748 The lmc(4) driver has been removed. This was a WAN interface
749 card that was already reportedly rare in 2003, and had an ambiguous
750 license. If you have device lmc in your kernel config file it must
754 Support for Arcnet networks has been removed. If you have device
755 arcnet or device cm in your kernel config file they must be
759 Support for FDDI networks has been removed. If you have device
760 fddi or device fpa in your kernel config file they must be
764 In addition to supporting RFC 3164 formatted messages, the
765 syslogd(8) service is now capable of parsing RFC 5424 formatted
766 log messages. The main benefit of using RFC 5424 is that clients
767 may now send log messages with timestamps containing year numbers,
768 microseconds and time zone offsets.
770 Similarly, the syslog(3) C library function has been altered to
771 send RFC 5424 formatted messages to the local system logging
772 daemon. On systems using syslogd(8), this change should have no
773 negative impact, as long as syslogd(8) and the C library are
774 updated at the same time. On systems using a different system
775 logging daemon, it may be necessary to make configuration
776 adjustments, depending on the software used.
778 When using syslog-ng, add the 'syslog-protocol' flag to local
779 input sources to enable parsing of RFC 5424 formatted messages:
782 unix-dgram("/var/run/log" flags(syslog-protocol));
785 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
786 of the 'imuxsock' module to let messages be processed by the
787 regular RFC 3164/5424 parsing pipeline:
789 module(load="imuxsock" SysSock.UseSpecialParser="off")
791 Do note that these changes only affect communication between local
792 applications and syslogd(8). The format that syslogd(8) uses to
793 store messages on disk or forward messages to other systems
794 remains unchanged. syslogd(8) still uses RFC 3164 for these
795 purposes. Options to customize this behaviour will be added in the
796 future. Utilities that process log files stored in /var/log are
797 thus expected to continue to function as before.
799 __FreeBSD_version has been incremented to 1200061 to denote this
803 Support for token ring networks has been removed. If you
804 have "device token" in your kernel config you should remove
805 it. No device drivers supported token ring.
808 makefs was modified to be able to tag ISO9660 El Torito boot catalog
809 entries as EFI instead of overloading the i386 tag as done previously.
810 The amd64 mkisoimages.sh script used to build amd64 ISO images for
811 release was updated to use this. This may mean that makefs must be
812 updated before "make cdrom" can be run in the release directory. This
813 should be as simple as:
815 $ cd $SRCDIR/usr.sbin/makefs
816 $ make depend all install
819 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
820 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
821 Co-existence for the transition period will come shortly. Booting is a
822 complex environment and test coverage for Lua-enabled loaders has been
823 thin, so it would be prudent to assume it might not work and make
824 provisions for backup boot methods.
827 devmatch functionality has been turned on in devd. It will automatically
828 load drivers for unattached devices. This may cause unexpected drivers
829 to be loaded. Please report any problems to current@ and
833 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
834 6.0.0. Please see the 20141231 entry below for information about
835 prerequisites and upgrading, if you are not already using clang 3.5.0
839 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
840 This means it is used to link the kernel and userland libraries and
841 executables, but is not yet installed as /usr/bin/ld by default.
843 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
844 WITHOUT_LLD_BOOTSTRAP=yes
847 On i386, pmtimer has been removed. Its functionality has been folded
848 into apm. It was a no-op on ACPI in current for a while now (but was
849 still needed on i386 in FreeBSD 11 and earlier). Users may need to
850 remove it from kernel config files.
853 The use of RSS hash from the network card aka flowid has been
854 disabled by default for lagg(4) as it's currently incompatible with
855 the lacp and loadbalance protocols.
857 This can be re-enabled by setting the following in loader.conf:
858 net.link.lagg.default_use_flowid="1"
861 The SW_WATCHDOG option is no longer necessary to enable the
862 hardclock-based software watchdog if no hardware watchdog is
863 configured. As before, SW_WATCHDOG will cause the software
864 watchdog to be enabled even if a hardware watchdog is configured.
867 r326887 fixes the issue described in the 20171214 UPDATING entry.
868 r326888 flips the switch back to building GELI support always.
871 r362593 broke ZFS + GELI support for reasons unknown. However,
872 it also broke ZFS support generally, so GELI has been turned off
873 by default as the lesser evil in r326857. If you boot off ZFS and/or
874 GELI, it might not be a good time to update.
877 PowerPC users must update loader(8) by rebuilding world before
878 installing a new kernel, as the protocol connecting them has
879 changed. Without the update, loader metadata will not be passed
880 successfully to the kernel and users will have to enter their
881 root partition at the kernel mountroot prompt to continue booting.
882 Newer versions of loader can boot old kernels without issue.
885 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
886 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
887 to WITH/OUT_LOADER_GELI.
890 The naive and non-compliant support of posix_fallocate(2) in ZFS
891 has been removed as of r325320. The system call now returns EINVAL
892 when used on a ZFS file. Although the new behavior complies with the
893 standard, some consumers are not prepared to cope with it.
894 One known victim is lld prior to r325420.
897 Building in a FreeBSD src checkout will automatically create object
898 directories now rather than store files in the current directory if
899 'make obj' was not ran. Calling 'make obj' is no longer necessary.
900 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
901 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
905 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
906 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
907 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
908 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
909 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
910 The UNIFIED_OBJDIR option is a transitional feature that will be
911 removed for 12.0 release; please migrate to the new format for any
912 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
913 than hardcoding paths.
916 The native-xtools target no longer installs the files by default to the
917 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
918 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
921 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
922 options are changing from controlling the build if defined / undefined
923 to controlling the build with explicit 'yes' or 'no' values. They will
924 shift to WITH/WITHOUT options to match other options in the system.
927 libstand has turned into a private library for sys/boot use only.
928 It is no longer supported as a public interface outside of sys/boot.
931 The arm port has split armv6 into armv6 and armv7. armv7 is now
932 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
933 and are running a kernel from before r324363, you will need to add
934 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
937 When building multiple kernels using KERNCONF, non-existent KERNCONF
938 files will produce an error and buildkernel will fail. Previously
939 missing KERNCONF files silently failed giving no indication as to
940 why, only to subsequently discover during installkernel that the
941 desired kernel was never built in the first place.
944 The default serial number format for CTL LUNs has changed. This will
945 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
946 or iSCSI clients care about their LUNs' serial numbers. Users who
947 require serial number stability should hardcode serial numbers in
951 For 32-bit arm compiled for hard-float support, soft-floating point
952 binaries now always get their shared libraries from
953 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
954 /usr/libsoft also existed). Only users with a hard-float ld.so, but
955 soft-float everything else should be affected.
958 The geli password typed at boot is now hidden. To restore the previous
959 behavior, see geli(8) for configuration options.
962 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
963 sysctl values. Minor nit, but requires a rebuild of both world/kernel
967 "make check" behavior (made in ^/head@r295380) has been changed to
968 execute from a limited sandbox, as opposed to executing from
972 - The "beforecheck" and "aftercheck" targets are now specified.
973 - ${CHECKDIR} (added in commit noted above) has been removed.
974 - Legacy behavior can be enabled by setting
975 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
977 If the limited sandbox mode is enabled, "make check" will execute
978 "make distribution", then install, execute the tests, and clean up the
979 sandbox if successful.
981 The "make distribution" and "make install" targets are typically run as
982 root to set appropriate permissions and ownership at installation time.
983 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
984 environment if executing "make check" with limited sandbox mode using
985 an unprivileged user.
988 Since the switch to GPT disk labels, fsck for UFS/FFS has been
989 unable to automatically find alternate superblocks. As of r322297,
990 the information needed to find alternate superblocks has been
991 moved to the end of the area reserved for the boot block.
992 Filesystems created with a newfs of this vintage or later
993 will create the recovery information. If you have a filesystem
994 created prior to this change and wish to have a recovery block
995 created for your filesystem, you can do so by running fsck in
996 foreground mode (i.e., do not use the -p or -y options). As it
997 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
998 to which you should answer yes.
1001 As of r321665, an NFSv4 server configuration that services
1002 Kerberos mounts or clients that do not support the uid/gid in
1003 owner/owner_group string capability, must explicitly enable
1004 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
1005 machine's /etc/rc.conf file.
1008 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
1009 Please see the 20141231 entry below for information about prerequisites
1010 and upgrading, if you are not already using clang 3.5.0 or higher.
1013 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
1014 r-commands (rlogin, rsh, etc.) to be built with the base system.
1017 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
1018 a very major ABI incompatible change, so users of FreeBSD/powerpc must
1019 be careful when performing source upgrades. It is best to run
1020 'make installworld' from an alternate root system, either a live
1021 CD/memory stick, or a temporary root partition. Additionally, all ports
1022 must be recompiled. powerpc64 is largely unaffected, except in the case
1023 of 32-bit compatibility. All 32-bit binaries will be affected.
1026 Forward compatibility for the "ino64" project have been committed. This
1027 will allow most new binaries to run on older kernels in a limited
1028 fashion. This prevents many of the common foot-shooting actions in the
1029 upgrade as well as the limited ability to roll back the kernel across
1030 the ino64 upgrade. Complicated use cases may not work properly, though
1031 enough simpler ones work to allow recovery in most situations.
1034 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
1035 if you require the GPL compiler.
1038 The internal ABI used for communication between the NFS kernel modules
1039 was changed by r320085, so __FreeBSD_version was bumped to
1040 ensure all the NFS related modules are updated together.
1043 The ABI of struct event was changed by extending the data
1044 member to 64bit and adding ext fields. For upgrade, same
1045 precautions as for the entry 20170523 "ino64" must be
1049 The GNU roff toolchain has been removed from base. To render manpages
1050 which are not supported by mandoc(1), man(1) can fallback on GNU roff
1051 from ports (and recommends to install it).
1052 To render roff(7) documents, consider using GNU roff from ports or the
1053 heirloom doctools roff toolchain from ports via pkg install groff or
1054 via pkg install heirloom-doctools.
1057 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
1058 smaller runtime footprint builds. This is useful for embedded systems
1059 which only require one chipset support.
1061 If you load it as a module, make sure this is in /boot/loader.conf:
1065 This will load the HAL, all chip/RF backends and if_ath_pci.
1066 If you have if_ath_pci in /boot/loader.conf, ensure it is after
1067 if_ath or it will not load any HAL chipset support.
1069 If you want to selectively load things (eg on ye cheape ARM/MIPS
1070 platforms where RAM is at a premium) you should:
1073 * load the chip modules in question
1074 * load ath_rate, ath_dfs
1076 * load if_ath_pci and/or if_ath_ahb depending upon your particular
1077 bus bind type - this is where probe/attach is done.
1079 For further comments/feedback, poke adrian@ .
1082 The "ino64" 64-bit inode project has been committed, which extends
1083 a number of types to 64 bits. Upgrading in place requires care and
1084 adherence to the documented upgrade procedure.
1086 If using a custom kernel configuration ensure that the
1087 COMPAT_FREEBSD11 option is included (as during the upgrade the
1088 system will be running the ino64 kernel with the existing world).
1090 For the safest in-place upgrade begin by removing previous build
1091 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full
1092 procedure documented below under the heading "To rebuild everything and
1093 install it on the current system." Specifically, a reboot is required
1094 after installing the new kernel before installing world. While an
1095 installworld normally works by accident from multiuser after rebooting
1096 the proper kernel, there are many cases where this will fail across this
1097 upgrade and installworld from single user is required.
1100 The NATM framework including the en(4), fatm(4), hatm(4), and
1101 patm(4) devices has been removed. Consumers should plan a
1102 migration before the end-of-life date for FreeBSD 11.
1105 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
1106 diff has not been implemented, if those are needed a newer version of
1107 GNU diff is available via the diffutils package under the gdiff name.
1110 As of r316810 for ipfilter, keep frags is no longer assumed when
1111 keep state is specified in a rule. r316810 aligns ipfilter with
1112 documentation in man pages separating keep frags from keep state.
1113 This allows keep state to be specified without forcing keep frags
1114 and allows keep frags to be specified independently of keep state.
1115 To maintain previous behaviour, also specify keep frags with
1116 keep state (as documented in ipf.conf.5).
1119 arm64 builds now use the base system LLD 4.0.0 linker by default,
1120 instead of requiring that the aarch64-binutils port or package be
1121 installed. To continue using aarch64-binutils, set
1122 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
1125 The UDP optimization in entry 20160818 that added the sysctl
1126 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
1127 packets will no longer be treated as L3 broadcast packets.
1130 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
1131 use any explicitly assigned loopback address available in the jail
1132 instead of using the first assigned address of the jail.
1135 The ctl.ko module no longer implements the iSCSI target frontend:
1136 cfiscsi.ko does instead.
1138 If building cfiscsi.ko as a kernel module, the module can be loaded
1139 via one of the following methods:
1140 - `cfiscsi_load="YES"` in loader.conf(5).
1141 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
1142 - ctladm(8)/ctld(8), when compiled with iSCSI support
1143 (`WITH_ISCSI=yes` in src.conf(5))
1145 Please see cfiscsi(4) for more details.
1148 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
1149 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
1150 same source (previously, the dependency of mmcsd.ko on mmc.ko was
1151 missing, but mmcsd.ko now will refuse to load if it is incompatible
1155 The syntax of ipfw(8) named states was changed to avoid ambiguity.
1156 If you have used named states in the firewall rules, you need to modify
1157 them after installworld and before rebooting. Now named states must
1158 be prefixed with colon.
1161 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
1162 removed as the userland we provide cannot use them. The KMS version
1163 (sys/dev/drm2) supports the same hardware.
1166 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
1167 Please see the 20141231 entry below for information about prerequisites
1168 and upgrading, if you are not already using clang 3.5.0 or higher.
1171 The code that provides support for ZFS .zfs/ directory functionality
1172 has been reimplemented. It's not possible now to create a snapshot
1173 by mkdir under .zfs/snapshot/. That should be the only user visible
1177 EISA bus support has been removed. The WITH_EISA option is no longer
1181 MCA bus support has been removed.
1184 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
1185 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
1188 The EM_MULTIQUEUE kernel configuration option is deprecated now that
1189 the em(4) driver conforms to iflib specifications.
1192 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
1193 IFLIB. If you have a custom kernel configuration that excludes em(4)
1194 but you use igb(4), you need to re-add em(4) to your custom
1198 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
1199 Please see the 20141231 entry below for information about prerequisites
1200 and upgrading, if you are not already using clang 3.5.0 or higher.
1203 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
1204 Please see the 20141231 entry below for information about prerequisites
1205 and upgrading, if you are not already using clang 3.5.0 or higher.
1208 The layout of the pmap structure has changed for powerpc to put the pmap
1209 statistics at the front for all CPU variations. libkvm(3) and all tools
1210 that link against it need to be recompiled.
1213 isl(4) and cyapa(4) drivers now require a new driver,
1214 chromebook_platform(4), to work properly on Chromebook-class hardware.
1215 On other types of hardware the drivers may need to be configured using
1216 device hints. Please see the corresponding manual pages for details.
1219 The urtwn(4) driver was merged into rtwn(4) and now consists of
1220 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
1222 Also, firmware for RTL8188CE was renamed due to possible name
1223 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
1226 GNU rcs has been removed from base. It is available as packages:
1227 - rcs: Latest GPLv3 GNU rcs version.
1228 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
1232 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
1233 modules now requires that the kernel configuration contain the
1234 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
1237 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
1238 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
1241 Relocatable object files with the extension of .So have been renamed
1242 to use an extension of .pico instead. The purpose of this change is
1243 to avoid a name clash with shared libraries on case-insensitive file
1244 systems. On those file systems, foo.So is the same file as foo.so.
1247 GNU rcs has been turned off by default. It can (temporarily) be built
1248 again by adding WITH_RCS knob in src.conf.
1249 Otherwise, GNU rcs is available from packages:
1250 - rcs: Latest GPLv3 GNU rcs version.
1251 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
1254 The backup_uses_rcs functionality has been removed from rc.subr.
1257 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
1258 two separate components, QUEUE_MACRO_DEBUG_TRACE and
1259 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
1260 QUEUE_MACRO_DEBUG behavior.
1263 r304787 changed some ioctl interfaces between the iSCSI userspace
1264 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1265 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1269 The UDP receive code has been updated to only treat incoming UDP
1270 packets that were addressed to an L2 broadcast address as L3
1271 broadcast packets. It is not expected that this will affect any
1272 standards-conforming UDP application. The new behaviour can be
1273 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1277 Remove the openbsd_poll system call.
1278 __FreeBSD_version has been bumped because of this.
1281 The stable/11 branch has been created from head@r302406.
1284 The libc stub for the pipe(2) system call has been replaced with
1285 a wrapper that calls the pipe2(2) system call and the pipe(2)
1286 system call is now only implemented by the kernels that include
1287 "options COMPAT_FREEBSD10" in their config file (this is the
1288 default). Users should ensure that this option is enabled in
1289 their kernel or upgrade userspace to r302092 before upgrading their
1293 CAM will now strip leading spaces from SCSI disks' serial numbers.
1294 This will affect users who create UFS filesystems on SCSI disks using
1295 those disk's diskid device nodes. For example, if /etc/fstab
1296 previously contained a line like
1297 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
1298 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
1299 transforms like gmirror may also be affected. ZFS users should
1303 The bitstring(3) API has been updated with new functionality and
1304 improved performance. But it is binary-incompatible with the old API.
1305 Objects built with the new headers may not be linked against objects
1306 built with the old headers.
1309 The brk and sbrk functions have been removed from libc on arm64.
1310 Binutils from ports has been updated to not link to these
1311 functions and should be updated to the latest version before
1312 installing a new libc.
1315 The armv6 port now defaults to hard float ABI. Limited support
1316 for running both hardfloat and soft float on the same system
1317 is available using the libraries installed with -DWITH_LIBSOFT.
1318 This has only been tested as an upgrade path for installworld
1319 and packages may fail or need manual intervention to run. New
1320 packages will be needed.
1322 To update an existing self-hosted armv6hf system, you must add
1323 TARGET_ARCH=armv6 on the make command line for both the build
1324 and the install steps.
1327 Kernel modules compiled outside of a kernel build now default to
1328 installing to /boot/modules instead of /boot/kernel. Many kernel
1329 modules built this way (such as those in ports) already overrode
1330 KMODDIR explicitly to install into /boot/modules. However,
1331 manually building and installing a module from /sys/modules will
1332 now install to /boot/modules instead of /boot/kernel.
1335 The CAM I/O scheduler has been committed to the kernel. There should be
1336 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1337 list of known rogues that claim support for this but actually corrupt
1338 data is believed to be complete, be on the lookout for data
1339 corruption. The known rogue list is believed to be complete:
1341 o Crucial MX100, M550 drives with MU01 firmware.
1342 o Micron M510 and M550 drives with MU01 firmware.
1343 o Micron M500 prior to MU07 firmware
1344 o Samsung 830, 840, and 850 all firmwares
1345 o FCCT M500 all firmwares
1347 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1348 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1349 updated firmware. Black listed drives will work correctly because these
1350 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1351 this list is the same as found in Linux, it's believed there are no
1352 other rogues in the market place. All other models from the above
1355 To be safe, if you are at all concerned, you can quirk each of your
1356 drives to prevent NCQ from being sent by setting:
1357 kern.cam.ada.X.quirks="0x2"
1358 in loader.conf. If the drive requires the 4k sector quirk, set the
1359 quirks entry to 0x3.
1362 The FAST_DEPEND build option has been removed and its functionality is
1363 now the one true way. The old mkdep(1) style of 'make depend' has
1364 been removed. See 20160311 for further details.
1367 Resource range types have grown from unsigned long to uintmax_t. All
1368 drivers, and anything using libdevinfo, need to be recompiled.
1371 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1372 builds. It no longer runs mkdep(1) during 'make depend', and the
1373 'make depend' stage can safely be skipped now as it is auto ran
1374 when building 'make all' and will generate all SRCS and DPSRCS before
1375 building anything else. Dependencies are gathered at compile time with
1376 -MF flags kept in separate .depend files per object file. Users should
1377 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1378 stale .depend files.
1381 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1382 kernel modules. Therefore, if you load any kernel modules at boot time,
1383 please install the boot loaders after you install the kernel, but before
1387 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1388 make installkernel KERNCONF=YOUR_KERNEL_HERE
1389 make -C sys/boot install
1390 <reboot in single user>
1392 Then follow the usual steps, described in the General Notes section,
1396 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1397 see the 20141231 entry below for information about prerequisites and
1398 upgrading, if you are not already using clang 3.5.0 or higher.
1401 The AIO subsystem is now a standard part of the kernel. The
1402 VFS_AIO kernel option and aio.ko kernel module have been removed.
1403 Due to stability concerns, asynchronous I/O requests are only
1404 permitted on sockets and raw disks by default. To enable
1405 asynchronous I/O requests on all file types, set the
1406 vfs.aio.enable_unsafe sysctl to a non-zero value.
1409 The ELF object manipulation tool objcopy is now provided by the
1410 ELF Tool Chain project rather than by GNU binutils. It should be a
1411 drop-in replacement, with the addition of arm64 support. The
1412 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1413 to obtain the GNU version if necessary.
1416 Building ZFS pools on top of zvols is prohibited by default. That
1417 feature has never worked safely; it's always been prone to deadlocks.
1418 Using a zvol as the backing store for a VM guest's virtual disk will
1419 still work, even if the guest is using ZFS. Legacy behavior can be
1420 restored by setting vfs.zfs.vol.recursive=1.
1423 The NONE and HPN patches has been removed from OpenSSH. They are
1424 still available in the security/openssh-portable port.
1427 With the addition of ypldap(8), a new _ypldap user is now required
1428 during installworld. "mergemaster -p" can be used to add the user
1429 prior to installworld, as documented in the handbook.
1432 The tftp loader (pxeboot) now uses the option root-path directive. As a
1433 consequence it no longer looks for a pxeboot.4th file on the tftp
1434 server. Instead it uses the regular /boot infrastructure as with the
1438 The code to start recording plug and play data into the modules has
1439 been committed. While the old tools will properly build a new kernel,
1440 a number of warnings about "unknown metadata record 4" will be produced
1441 for an older kldxref. To avoid such warnings, make sure to rebuild
1442 the kernel toolchain (or world). Make sure that you have r292078 or
1443 later when trying to build 292077 or later before rebuilding.
1446 Debug data files are now built by default with 'make buildworld' and
1447 installed with 'make installworld'. This facilitates debugging but
1448 requires more disk space both during the build and for the installed
1449 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1453 r291527 changed the internal interface between the nfsd.ko and
1454 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1455 __FreeBSD_version has been bumped because of this.
1458 Add support for unicode collation strings leads to a change of
1459 order of files listed by ls(1) for example. To get back to the old
1460 behaviour, set LC_COLLATE environment variable to "C".
1462 Databases administrators will need to reindex their databases given
1463 collation results will be different.
1465 Due to a bug in install(1) it is recommended to remove the ancient
1466 locales before running make installworld.
1468 rm -rf /usr/share/locale/*
1471 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1472 libcrypto.so.7 or libssl.so.7 must be recompiled.
1475 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1476 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1477 should be replaced with isp_2400 and isp_2500 modules respectively.
1480 The build previously allowed using 'make -n' to not recurse into
1481 sub-directories while showing what commands would be executed, and
1482 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1483 and 'make -N' will not.
1486 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1487 and etcupdate will now use this file. A custom sendmail.cf is now
1488 updated via this mechanism rather than via installworld. If you had
1489 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1490 want to remove the exclusion or change it to "always install".
1491 /etc/mail/sendmail.cf is now managed the same way regardless of
1492 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1493 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1496 Compatibility shims for legacy ATA device names have been removed.
1497 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1498 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1499 environment variables, /dev/ad* and /dev/ar* symbolic links.
1502 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1503 Please see the 20141231 entry below for information about prerequisites
1504 and upgrading, if you are not already using clang 3.5.0 or higher.
1507 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1508 and renamed from .symbols to .debug. This reduces the size requirements
1509 on the boot partition or file system and provides consistency with
1510 userland debug files.
1512 When using the supported kernel installation method the
1513 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1514 as is done with /boot/kernel.
1516 Developers wishing to maintain the historical behavior of installing
1517 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1520 The wireless drivers had undergone changes that remove the 'parent
1521 interface' from the ifconfig -l output. The rc.d network scripts
1522 used to check presence of a parent interface in the list, so old
1523 scripts would fail to start wireless networking. Thus, etcupdate(3)
1524 or mergemaster(8) run is required after kernel update, to update your
1525 rc.d scripts in /etc.
1528 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1529 These configurations are now automatically interpreted as
1530 'scrub fragment reassemble'.
1533 Kernel-loadable modules for the random(4) device are back. To use
1534 them, the kernel must have
1537 options RANDOM_LOADABLE
1539 kldload(8) can then be used to load random_fortuna.ko
1540 or random_yarrow.ko. Please note that due to the indirect
1541 function calls that the loadable modules need to provide,
1542 the build-in variants will be slightly more efficient.
1544 The random(4) kernel option RANDOM_DUMMY has been retired due to
1545 unpopularity. It was not all that useful anyway.
1548 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1549 Control over building the ELF Tool Chain tools is now provided by
1550 the WITHOUT_TOOLCHAIN knob.
1553 The polarity of Pulse Per Second (PPS) capture events with the
1554 uart(4) driver has been corrected. Prior to this change the PPS
1555 "assert" event corresponded to the trailing edge of a positive PPS
1556 pulse and the "clear" event was the leading edge of the next pulse.
1558 As the width of a PPS pulse in a typical GPS receiver is on the
1559 order of 1 millisecond, most users will not notice any significant
1560 difference with this change.
1562 Anyone who has compensated for the historical polarity reversal by
1563 configuring a negative offset equal to the pulse width will need to
1564 remove that workaround.
1567 The default group assigned to /dev/dri entries has been changed
1568 from 'wheel' to 'video' with the id of '44'. If you want to have
1569 access to the dri devices please add yourself to the video group
1572 # pw groupmod video -m $USER
1575 The menu.rc and loader.rc files will now be replaced during
1576 upgrades. Please migrate local changes to menu.rc.local and
1577 loader.rc.local instead.
1580 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1581 strings and strip have been removed. The src.conf(5) knob
1582 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1585 As ZFS requires more kernel stack pages than is the default on some
1586 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1587 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1589 Please consider using 'options KSTACK_PAGES=X' where X is greater
1590 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1593 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1594 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1595 default, i.e., they will not contain "::". For example, instead
1596 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1597 to have a more specific match, such as different map entries for
1598 IPv6:0:0 vs IPv6:0. This change requires that configuration
1599 data (including maps, files, classes, custom ruleset, etc.) must
1600 use the same format, so make certain such configuration data is
1601 upgrading. As a very simple check search for patterns like
1602 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1603 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1604 the cf option UseCompressedIPv6Addresses.
1607 The default kernel entropy-processing algorithm is now
1608 Fortuna, replacing Yarrow.
1610 Assuming you have 'device random' in your kernel config
1611 file, the configurations allow a kernel option to override
1612 this default. You may choose *ONE* of:
1614 options RANDOM_YARROW # Legacy /dev/random algorithm.
1615 options RANDOM_DUMMY # Blocking-only driver.
1617 If you have neither, you get Fortuna. For most people,
1618 read no further, Fortuna will give a /dev/random that works
1619 like it always used to, and the difference will be irrelevant.
1621 If you remove 'device random', you get *NO* kernel-processed
1622 entropy at all. This may be acceptable to folks building
1623 embedded systems, but has complications. Carry on reading,
1624 and it is assumed you know what you need.
1626 *PLEASE* read random(4) and random(9) if you are in the
1627 habit of tweaking kernel configs, and/or if you are a member
1628 of the embedded community, wanting specific and not-usual
1629 behaviour from your security subsystems.
1631 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1632 random', you will NOT have a functioning /dev/random, and
1633 many cryptographic features will not work, including SSH.
1634 You may also find strange behaviour from the random(3) set
1635 of library functions, in particular sranddev(3), srandomdev(3)
1636 and arc4random(3). The reason for this is that the KERN_ARND
1637 sysctl only returns entropy if it thinks it has some to
1638 share, and with RANDOM_DUMMY or no 'device random' this
1642 An additional fix for the issue described in the 20150614 sendmail
1643 entry below has been committed in revision 284717.
1646 FreeBSD's old make (fmake) has been removed from the system. It is
1647 available as the devel/fmake port or via pkg install fmake.
1650 The fix for the issue described in the 20150614 sendmail entry
1651 below has been committed in revision 284436. The work
1652 around described in that entry is no longer needed unless the
1653 default setting is overridden by a confDH_PARAMETERS configuration
1654 setting of '5' or pointing to a 512 bit DH parameter file.
1657 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1658 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1659 and devel/kyua to version 0.20+ and adjust any calling code to work
1660 with Kyuafile and kyua.
1663 The import of openssl to address the FreeBSD-SA-15:10.openssl
1664 security advisory includes a change which rejects handshakes
1665 with DH parameters below 768 bits. sendmail releases prior
1666 to 8.15.2 (not yet released), defaulted to a 512 bit
1667 DH parameter setting for client connections. To work around
1668 this interoperability, sendmail can be configured to use a
1669 2048 bit DH parameter by:
1671 1. Edit /etc/mail/`hostname`.mc
1672 2. If a setting for confDH_PARAMETERS does not exist or
1673 exists and is set to a string beginning with '5',
1674 replace it with '2'.
1675 3. If a setting for confDH_PARAMETERS exists and is set to
1676 a file path, create a new file with:
1677 openssl dhparam -out /path/to/file 2048
1678 4. Rebuild the .cf file:
1679 cd /etc/mail/; make; make install
1680 5. Restart sendmail:
1681 cd /etc/mail/; make restart
1683 A sendmail patch is coming, at which time this file will be
1687 Generation of legacy formatted entries have been disabled by default
1688 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1689 entries were converted to use the new format by default when the new,
1690 machine independent format have been added and supported since FreeBSD
1693 Please see the pwd_mkdb(8) manual page for further details.
1696 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1697 20141231 entry below for information about prerequisites and upgrading,
1698 if you are not already using 3.5.0 or higher.
1701 TI platform code switched to using vendor DTS files and this update
1702 may break existing systems running on Beaglebone, Beaglebone Black,
1705 - dtb files should be regenerated/reinstalled. Filenames are the
1706 same but content is different now
1707 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1708 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1709 addressing scheme is now pin 25 on /dev/gpioc3.
1710 - Pandaboard: /etc/ttys should be updated, serial console device is
1711 now /dev/ttyu2, not /dev/ttyu0
1714 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1715 If you need the GNU extension from groff soelim(1), install groff
1716 from package: pkg install groff, or via ports: textproc/groff.
1719 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1720 defined in symlink(7); previously symlinks were silently ignored.
1723 The const qualifier has been removed from iconv(3) to comply with
1724 POSIX. The ports tree is aware of this from r384038 onwards.
1727 Libraries specified by LIBADD in Makefiles must have a corresponding
1728 DPADD_<lib> variable to ensure correct dependencies. This is now
1729 enforced in src.libnames.mk.
1732 From legacy ata(4) driver was removed support for SATA controllers
1733 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1734 Kernel modules ataahci and ataadaptec were removed completely,
1735 replaced by ahci and mvs modules respectively.
1738 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1739 the 20141231 entry below for information about prerequisites and
1740 upgrading, if you are not already using 3.5.0 or higher.
1743 The 32-bit PowerPC kernel has been changed to a position-independent
1744 executable. This can only be booted with a version of loader(8)
1745 newer than January 31, 2015, so make sure to update both world and
1746 kernel before rebooting.
1749 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1750 but before r278950, the RNG was not seeded properly. Immediately
1751 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1752 ssh keys or openssl keys) that were generated w/ a kernel from that
1753 range. This does not affect programs that directly used /dev/random
1754 or /dev/urandom. All userland uses of arc4random(3) are affected.
1757 The autofs(4) ABI was changed in order to restore binary compatibility
1758 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1759 with the new kernel.
1762 The powerpc64 kernel has been changed to a position-independent
1763 executable. This can only be booted with a new version of loader(8),
1764 so make sure to update both world and kernel before rebooting.
1767 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1768 only release, no new features have been added. Please see the 20141231
1769 entry below for information about prerequisites and upgrading, if you
1770 are not already using 3.5.0.
1773 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1774 taken from the ELF Tool Chain project rather than GNU binutils. They
1775 should be drop-in replacements, with the addition of arm64 support.
1776 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1777 binutils tools, if necessary. See 20150805 for updated information.
1780 The default Unbound configuration now enables remote control
1781 using a local socket. Users who have already enabled the
1782 local_unbound service should regenerate their configuration
1783 by running "service local_unbound setup" as root.
1786 The GNU texinfo and GNU info pages have been removed.
1787 To be able to view GNU info pages please install texinfo from ports.
1790 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1792 As of this release, a prerequisite for building clang, llvm and lldb is
1793 a C++11 capable compiler and C++11 standard library. This means that to
1794 be able to successfully build the cross-tools stage of buildworld, with
1795 clang as the bootstrap compiler, your system compiler or cross compiler
1796 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1797 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1800 On any standard FreeBSD 10.x or 11.x installation, where clang and
1801 libc++ are on by default (that is, on x86 or arm), this should work out
1804 On 9.x installations where clang is enabled by default, e.g. on x86 and
1805 powerpc, libc++ will not be enabled by default, so libc++ should be
1806 built (with clang) and installed first. If both clang and libc++ are
1807 missing, build clang first, then use it to build libc++.
1809 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1810 the instructions for 9.x above.
1812 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1813 default, and do not build clang.
1815 Many embedded systems are resource constrained, and will not be able to
1816 build clang in a reasonable time, or in some cases at all. In those
1817 cases, cross building bootable systems on amd64 is a workaround.
1819 This new version of clang introduces a number of new warnings, of which
1820 the following are most likely to appear:
1824 This warns in two cases, for both C and C++:
1825 * When the code is trying to take the absolute value of an unsigned
1826 quantity, which is effectively a no-op, and almost never what was
1827 intended. The code should be fixed, if at all possible. If you are
1828 sure that the unsigned quantity can be safely cast to signed, without
1829 loss of information or undefined behavior, you can add an explicit
1830 cast, or disable the warning.
1832 * When the code is trying to take an absolute value, but the called
1833 abs() variant is for the wrong type, which can lead to truncation.
1834 If you want to disable the warning instead of fixing the code, please
1835 make sure that truncation will not occur, or it might lead to unwanted
1838 -Wtautological-undefined-compare and
1839 -Wundefined-bool-conversion
1841 These warn when C++ code is trying to compare 'this' against NULL, while
1842 'this' should never be NULL in well-defined C++ code. However, there is
1843 some legacy (pre C++11) code out there, which actively abuses this
1844 feature, which was less strictly defined in previous C++ versions.
1846 Squid and openjdk do this, for example. The warning can be turned off
1847 for C++98 and earlier, but compiling the code in C++11 mode might result
1848 in unexpected behavior; for example, the parts of the program that are
1849 unreachable could be optimized away.
1852 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1853 kernel sources have been removed. The .h files remain, since some
1854 utilities include them. This will need to be fixed later.
1855 If "mount -t oldnfs ..." is attempted, it will fail.
1856 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1857 the utilities will report errors.
1860 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1861 directories to top level SUBDIR variable when their parent
1862 directory is included in LOCAL_DIRS. Users with build systems with
1863 such hierarchies and without SUBDIR entries in the parent
1864 directory Makefiles should add them or add the directories to
1868 faith(4) and faithd(8) have been removed from the base system. Faith
1869 has been obsolete for a very long time.
1872 vt(4), the new console driver, is enabled by default. It brings
1873 support for Unicode and double-width characters, as well as
1874 support for UEFI and integration with the KMS kernel video
1877 You may need to update your console settings in /etc/rc.conf,
1878 most probably the keymap. During boot, /etc/rc.d/syscons will
1879 indicate what you need to do.
1881 vt(4) still has issues and lacks some features compared to
1882 syscons(4). See the wiki for up-to-date information:
1883 https://wiki.freebsd.org/Newcons
1885 If you want to keep using syscons(4), you can do so by adding
1886 the following line to /boot/loader.conf:
1890 pjdfstest has been integrated into kyua as an opt-in test suite.
1891 Please see share/doc/pjdfstest/README for more details on how to
1895 gperf has been removed from the base system for architectures
1896 that use clang. Ports that require gperf will obtain it from the
1900 pjdfstest has been moved from tools/regression/pjdfstest to
1904 At svn r271982, The default linux compat kernel ABI has been adjusted
1905 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1906 update. If you wish to continue using the linux-f10 compat ports,
1907 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1908 encouraged to update their linux-compat packages to linux-c6 during
1909 their next update cycle.
1912 The ofwfb driver, used to provide a graphics console on PowerPC when
1913 using vt(4), no longer allows mmap() of all physical memory. This
1914 will prevent Xorg on PowerPC with some ATI graphics cards from
1915 initializing properly unless x11-servers/xorg-server is updated to
1919 The xdev targets have been converted to using TARGET and
1920 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1923 The default unbound configuration has been modified to address
1924 issues with reverse lookups on networks that use private
1925 address ranges. If you use the local_unbound service, run
1926 "service local_unbound setup" as root to regenerate your
1927 configuration, then "service local_unbound reload" to load the
1931 The GNU texinfo and GNU info pages are not built and installed
1932 anymore, WITH_INFO knob has been added to allow to built and install
1934 UPDATE: see 20150102 entry on texinfo's removal
1937 The GNU readline library is now an INTERNALLIB - that is, it is
1938 statically linked into consumers (GDB and variants) in the base
1939 system, and the shared library is no longer installed. The
1940 devel/readline port is available for third party software that
1944 The Itanium architecture (ia64) has been removed from the list of
1945 known architectures. This is the first step in the removal of the
1949 Commit r268115 has added NFSv4.1 server support, merged from
1950 projects/nfsv4.1-server. Since this includes changes to the
1951 internal interfaces between the NFS related modules, a full
1952 build of the kernel and modules will be necessary.
1953 __FreeBSD_version has been bumped.
1956 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1957 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1958 which differs from the behaviour controlled by this knob.)
1961 Maximal length of the serial number in CTL was increased from 16 to
1962 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1963 and ctld, need to be rebuilt to work with a new kernel.
1966 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1967 1 respectively to match the upstream numbers. They were out of
1968 sync because, when they were originally added to FreeBSD, the
1969 upstream versions were not respected. These libraries are private
1970 and not yet built by default, so renumbering them should be a
1971 non-issue. However, unclean source trees will yield broken test
1972 programs once the operator executes "make delete-old-libs" after a
1973 "make installworld".
1975 Additionally, the atf-sh binary was made private by moving it into
1976 /usr/libexec/. Already-built shell test programs will keep the
1977 path to the old binary so they will break after "make delete-old"
1980 If you are using WITH_TESTS=yes (not the default), wipe the object
1981 tree and rebuild from scratch to prevent spurious test failures.
1982 This is only needed once: the misnumbered libraries and misplaced
1983 binaries have been added to OptionalObsoleteFiles.inc so they will
1984 be removed during a clean upgrade.
1987 Clang and llvm have been upgraded to 3.4.1 release.
1990 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1991 be removed to avoid issues in the future (and has been added to
1995 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1996 past, it affected all builds that used the bsd.*.mk files. The old
1997 behavior was a bug, but people may have relied upon it. To get this
1998 behavior back, you can .include /etc/src.conf from /etc/make.conf
1999 (which is still global and isn't changed). This also changes the
2000 behavior of incremental builds inside the tree of individual
2001 directories. Set MAKESYSPATH to ".../share/mk" to do that.
2002 Although this has survived make universe and some upgrade scenarios,
2003 other upgrade scenarios may have broken. At least one form of
2004 temporary breakage was fixed with MAKESYSPATH settings for buildworld
2005 as well... In cases where MAKESYSPATH isn't working with this
2006 setting, you'll need to set it to the full path to your tree.
2008 One side effect of all this cleaning up is that bsd.compiler.mk
2009 is no longer implicitly included by bsd.own.mk. If you wish to
2010 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
2014 The lindev device has been removed since /dev/full has been made a
2015 standard device. __FreeBSD_version has been bumped.
2018 The knob WITHOUT_VI was added to the base system, which controls
2019 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
2020 in order to reorder files share/termcap and didn't build ex(1) as a
2021 build tool, so building/installing with WITH_VI is highly advised for
2022 build hosts for older releases.
2024 This issue has been fixed in stable/9 and stable/10 in r277022 and
2025 r276991, respectively.
2028 The YES_HESIOD knob has been removed. It has been obsolete for
2029 a decade. Please move to using WITH_HESIOD instead or your builds
2030 will silently lack HESIOD.
2033 The uart(4) driver has been changed with respect to its handling
2034 of the low-level console. Previously the uart(4) driver prevented
2035 any process from changing the baudrate or the CLOCAL and HUPCL
2036 control flags. By removing the restrictions, operators can make
2037 changes to the serial console port without having to reboot.
2038 However, when getty(8) is started on the serial device that is
2039 associated with the low-level console, a misconfigured terminal
2040 line in /etc/ttys will now have a real impact.
2041 Before upgrading the kernel, make sure that /etc/ttys has the
2042 serial console device configured as 3wire without baudrate to
2043 preserve the previous behaviour. E.g:
2044 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
2047 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
2048 to improve performance. To re-enable it, if needed, run rpcbind
2049 with command line option -W.
2052 Switched back to the GPL dtc compiler due to updates in the upstream
2053 dts files not being supported by the BSDL dtc compiler. You will need
2054 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
2055 may result while building dtb files during a kernel build if you fail
2056 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
2059 Clang and llvm have been upgraded to 3.4 release.
2062 The nve(4) driver has been removed. Please use the nfe(4) driver
2063 for NVIDIA nForce MCP Ethernet adapters instead.
2066 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
2067 This could cause certain C++ applications using shared libraries built
2068 against the previous version of libc++ to crash. The incompatibility
2069 has now been fixed, but any C++ applications or shared libraries built
2070 between r261283 and r261801 should be recompiled.
2073 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
2074 capability mode support. Please note that enabling the feature in
2075 kernel is still highly recommended.
2078 OpenSSH is now built with sandbox support, and will use sandbox as
2079 the default privilege separation method. This requires Capsicum
2080 capability mode support in kernel.
2083 The libelf and libdwarf libraries have been updated to newer
2084 versions from upstream. Shared library version numbers for
2085 these two libraries were bumped. Any ports or binaries
2086 requiring these two libraries should be recompiled.
2087 __FreeBSD_version is bumped to 1100006.
2090 If a Makefile in a tests/ directory was auto-generating a Kyuafile
2091 instead of providing an explicit one, this would prevent such
2092 Makefile from providing its own Kyuafile in the future during
2093 NO_CLEAN builds. This has been fixed in the Makefiles but manual
2094 intervention is needed to clean an objdir if you use NO_CLEAN:
2095 # find /usr/obj -name Kyuafile | xargs rm -f
2098 The behavior of gss_pseudo_random() for the krb5 mechanism
2099 has changed, for applications requesting a longer random string
2100 than produced by the underlying enctype's pseudo-random() function.
2101 In particular, the random string produced from a session key of
2102 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
2103 be different at the 17th octet and later, after this change.
2104 The counter used in the PRF+ construction is now encoded as a
2105 big-endian integer in accordance with RFC 4402.
2106 __FreeBSD_version is bumped to 1100004.
2109 The WITHOUT_ATF build knob has been removed and its functionality
2110 has been subsumed into the more generic WITHOUT_TESTS. If you were
2111 using the former to disable the build of the ATF libraries, you
2112 should change your settings to use the latter.
2115 The default version of mtree is nmtree which is obtained from
2116 NetBSD. The output is generally the same, but may vary
2117 slightly. If you found you need identical output adding
2118 "-F freebsd9" to the command line should do the trick. For the
2119 time being, the old mtree is available as fmtree.
2122 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
2123 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
2124 1.1.4_8 and verify bsdyml not linked in, before running "make
2126 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
2128 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
2131 The stable/10 branch has been created in subversion from head
2138 Sometimes, obscure build problems are the result of environment
2139 poisoning. This can happen because the make utility reads its
2140 environment when searching for values for global variables. To run
2141 your build attempts in an "environmental clean room", prefix all make
2142 commands with 'env -i '. See the env(1) manual page for more details.
2143 Occasionally a build failure will occur with "make -j" due to a race
2144 condition. If this happens try building again without -j, and please
2145 report a bug if it happens consistently.
2147 When upgrading from one major version to another it is generally best to
2148 upgrade to the latest code in the currently installed branch first, then
2149 do an upgrade to the new branch. This is the best-tested upgrade path,
2150 and has the highest probability of being successful. Please try this
2151 approach if you encounter problems with a major version upgrade. Since
2152 the stable 4.x branch point, one has generally been able to upgrade from
2153 anywhere in the most recent stable branch to head / current (or even the
2154 last couple of stable branches). See the top of this file when there's
2157 The update process will emit an error on an attempt to perform a build
2158 or install from a FreeBSD version below the earliest supported version.
2159 When updating from an older version the update should be performed one
2160 major release at a time, including running `make delete-old` at each
2163 When upgrading a live system, having a root shell around before
2164 installing anything can help undo problems. Not having a root shell
2165 around can lead to problems if pam has changed too much from your
2166 starting point to allow continued authentication after the upgrade.
2168 This file should be read as a log of events. When a later event changes
2169 information of a prior event, the prior event should not be deleted.
2170 Instead, a pointer to the entry with the new information should be
2171 placed in the old entry. Readers of this file should also sanity check
2172 older entries before relying on them blindly. Authors of new entries
2173 should write them with this in mind.
2177 When upgrading the boot ZFS pool to a new version, always follow
2180 1.) recompile and reinstall the ZFS boot loader and boot block
2181 (this is part of "make buildworld" and "make installworld")
2183 2.) update the ZFS boot block on your boot drive
2185 The following example updates the ZFS boot block on the first
2186 partition (freebsd-boot) of a GPT partitioned drive ada0:
2187 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
2189 Non-boot pools do not need these updates.
2193 If you are updating from a prior version of FreeBSD (even one just
2194 a few days old), you should follow this procedure. It is the most
2195 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2197 make kernel-toolchain
2198 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2199 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2201 To test a kernel once
2202 ---------------------
2203 If you just want to boot a kernel once (because you are not sure
2204 if it works, or if you want to boot a known bad kernel to provide
2205 debugging information) run
2206 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2207 nextboot -k testkernel
2209 To rebuild everything and install it on the current system.
2210 -----------------------------------------------------------
2211 # Note: sometimes if you are running current you gotta do more than
2212 # is listed here if you are upgrading from a really old current.
2214 <make sure you have good level 0 dumps>
2216 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2217 make installkernel KERNCONF=YOUR_KERNEL_HERE
2219 <reboot in single user> [3]
2226 To cross-install current onto a separate partition
2227 --------------------------------------------------
2228 # In this approach we use a separate partition to hold
2229 # current's root, 'usr', and 'var' directories. A partition
2230 # holding "/", "/usr" and "/var" should be about 2GB in
2233 <make sure you have good level 0 dumps>
2236 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2237 <maybe newfs current's root partition>
2238 <mount current's root partition on directory ${CURRENT_ROOT}>
2239 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
2240 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2241 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2242 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2243 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2244 <reboot into current>
2245 <do a "native" rebuild/install as described in the previous section>
2246 <maybe install compatibility libraries from ports/misc/compat*>
2250 To upgrade in-place from stable to current
2251 ----------------------------------------------
2252 <make sure you have good level 0 dumps>
2254 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
2255 make installkernel KERNCONF=YOUR_KERNEL_HERE
2257 <reboot in single user> [3]
2264 Make sure that you've read the UPDATING file to understand the
2265 tweaks to various things you need. At this point in the life
2266 cycle of current, things change often and you are on your own
2267 to cope. The defaults can also change, so please read ALL of
2268 the UPDATING entries.
2270 Also, if you are tracking -current, you must be subscribed to
2271 freebsd-current@freebsd.org. Make sure that before you update
2272 your sources that you have read and understood all the recent
2273 messages there. If in doubt, please track -stable which has
2274 much fewer pitfalls.
2276 [1] If you have third party modules, such as vmware, you
2277 should disable them at this point so they don't crash your
2280 [3] From the bootblocks, boot -s, and then do
2284 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed
2285 cd src # full path to source
2286 adjkerntz -i # if CMOS is wall time
2287 Also, when doing a major release upgrade, it is required that
2288 you boot into single user mode to do the installworld.
2290 [4] Note: This step is non-optional. Failure to do this step
2291 can result in a significant reduction in the functionality of the
2292 system. Attempting to do it by hand is not recommended and those
2293 that pursue this avenue should read this file carefully, as well
2294 as the archives of freebsd-current and freebsd-hackers mailing lists
2295 for potential gotchas. The -U option is also useful to consider.
2296 See mergemaster(8) for more information.
2298 [5] Usually this step is a no-op. However, from time to time
2299 you may need to do this if you get unknown user in the following
2300 step. It never hurts to do it all the time. You may need to
2301 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2302 install) after the buildworld before this step if you last updated
2303 from current before 20130425 or from -stable before 20130430.
2305 [6] This only deletes old files and directories. Old libraries
2306 can be deleted by "make delete-old-libs", but you have to make
2307 sure that no program is using those libraries anymore.
2309 [8] The new kernel must be able to run existing binaries used by an
2310 installworld. When upgrading across major versions, the new kernel's
2311 configuration must include the correct COMPAT_FREEBSD<n> option for
2312 existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure
2313 to do so may leave you with a system that is hard to boot to recover. A
2314 GENERIC kernel will include suitable compatibility options to run
2315 binaries from older branches. Note that the ability to run binaries
2316 from unsupported branches is not guaranteed.
2318 Make sure that you merge any new devices from GENERIC since the
2319 last time you updated your kernel config file. Options also
2320 change over time, so you may need to adjust your custom kernels
2323 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2324 "?=" instead of the "=" assignment operator, so that buildworld can
2325 override the CPUTYPE if it needs to.
2327 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2328 not on the command line, or in /etc/make.conf. buildworld will
2329 warn if it is improperly defined.
2332 This file contains a list, in reverse chronological order, of major
2333 breakages in tracking -current. It is not guaranteed to be a complete
2334 list of such breakages, and only contains entries since September 23, 2011.
2335 If you need to see UPDATING entries from before that date, you will need
2336 to fetch an UPDATING file from an older FreeBSD release.
2338 Copyright information:
2340 Copyright 1998-2009 M. Warner Losh <imp@FreeBSD.org>
2342 Redistribution, publication, translation and use, with or without
2343 modification, in full or in part, in any form or format of this
2344 document are permitted without further permission from the author.
2346 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2347 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2348 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2349 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2350 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2351 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2352 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2353 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2354 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2355 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2356 POSSIBILITY OF SUCH DAMAGE.
2358 Contact Warner Losh if you have any questions about your use of