1 Updating Information for FreeBSD current users.
3 This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>.
4 See end of file for further details. For commonly done items, please see the
5 COMMON ITEMS: section later in the file. These instructions assume that you
6 basically know what you are doing. If not, then please consult the FreeBSD
9 https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
11 Items affecting the ports and packages system can be found in
12 /usr/ports/UPDATING. Please read that file before running portupgrade.
14 NOTE TO PEOPLE WHO THINK THAT FreeBSD 13.x IS SLOW:
15 FreeBSD 13.x has many debugging features turned on, in both the kernel
16 and userland. These features attempt to detect incorrect use of
17 system primitives, and encourage loud failure through extra sanity
18 checking and fail stop semantics. They also substantially impact
19 system performance. If you want to do performance measurement,
20 benchmarking, and optimization, you'll want to turn them off. This
21 includes various WITNESS- related kernel options, INVARIANTS, malloc
22 debugging flags in userland, and various verbose features in the
23 kernel. Many developers choose to disable these features on build
24 machines to maximize performance. (To completely disable malloc
25 debugging, define MALLOC_PRODUCTION in /etc/make.conf, or to merely
26 disable the most expensive debugging functionality run
27 "ln -s 'abort:false,junk:false' /etc/malloc.conf".)
30 r362275 changed the internal API between the kernel RPC and the
31 NFS modules. As such, all the modules must be recompiled from
35 r364330 modified the internal API used between the NFS modules.
36 As such, all the NFS modules must be re-compiled from sources.
39 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
40 been upgraded to 11.0.0. Please see the 20141231 entry below for
41 information about prerequisites and upgrading, if you are not already
42 using clang 3.5.0 or higher.
45 r364092 modified the internal ABI used between the kernel NFS
46 modules. As such, all of these modules need to be rebuilt
47 from sources, so a version bump was done.
50 Makefile.inc has been updated to work around the issue documented in
51 20200729. It was a case where the optimization of using symbolic links
52 to point to binaries created a situation where we'd run new binaries
53 with old libraries starting midway through the installworld process.
56 r363679 has redefined some undefined behavior in regcomp(3); notably,
57 extraneous escapes of most ordinary characters will no longer be
58 accepted. An exp-run has identified all of the problems with this in
59 ports, but other non-ports software may need extra escapes removed to
62 Because of this change, installworld may encounter the following error
63 from rtld: Undefined symbol "regcomp@FBSD_1.6" -- It is imperative that
64 you do not halt installworld. Instead, let it run to completion (whether
65 successful or not) and run installworld once more.
68 A new implementation of bc and dc has been imorted in r362681. This
69 implementation corrects non-conformant behavior of the previous bc
70 and adds GNU bc compatible options. It offers a number of extensions,
71 is much faster on large values, and has support for message catalogs
72 (a number of languages are already supported, contributions of further
73 languages welcome). The option WITHOUT_GH_BC can be used to build the
74 world with the previous versions of bc and dc.
77 r362639 changed the internal API used between the NFS kernel modules.
78 As such, they all need to be rebuilt from sources.
81 r362158 changed the arguments for VFS_CHECKEXP(). As such, any
82 out of tree file systems need to be modified and rebuilt.
83 Also, any file systems that are modules must be rebuilt.
86 read(2) of a directory fd is now rejected by default. root may
87 re-enable it for system root only on non-ZFS filesystems with the
88 security.bsd.allow_read_dir sysctl(8) MIB if
89 security.bsd.suser_enabled=1.
91 It may be advised to setup aliases for grep to default to `-d skip` if
92 commonly non-recursively grepping a list that includes directories and
93 the potential for the resulting stderr output is not tolerable. Example
94 aliases are now installed, commented out, in /root/.cshrc and
98 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
99 been upgraded to 10.0.1. Please see the 20141231 entry below for
100 information about prerequisites and upgrading, if you are not already
101 using clang 3.5.0 or higher.
104 Support for obsolete compilers has been removed from the build system.
105 Clang 6 and GCC 6.4 are the minimum supported versions.
108 closefrom(2) has been moved under COMPAT12, and replaced in libc with a
109 stub that calls close_range(2). If using a custom kernel configuration,
110 you may want to ensure that the COMPAT_FREEBSD12 option is included, as
111 a slightly older -CURRENT userland and older FreeBSD userlands may not
112 be functional without closefrom(2).
115 Upstream DTS from Linux 5.6 was merged and they now have the SID
116 and THS (Secure ID controller and THermal Sensor) node present.
117 The DTB overlays have now been removed from the tree for the H3/H5 and
118 A64 SoCs and the aw_sid and aw_thermal driver have been updated to
119 deal with upstream DTS. If you are using those overlays you need to
120 remove them from loader.conf and update the DTBs on the FAT partition.
123 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
124 been upgraded to 10.0.0. Please see the 20141231 entry below for
125 information about prerequisites and upgrading, if you are not already
126 using clang 3.5.0 or higher.
129 The amd(8) automount daemon has been removed from the source tree.
130 As of FreeBSD 10.1 autofs(5) is the preferred tool for automounting.
131 amd is still available in the sysutils/am-utils port.
134 Removed brooktree driver (bktr.4) from the tree.
137 The WITH_GPL_DTC option has been removed. The BSD-licenced device tree
138 compiler in usr.bin/dtc is used on all architectures which use dtc, and
139 the GPL dtc is available (if needed) from the sysutils/dtc port.
142 The WITHOUT_LLVM_LIBUNWIND option has been removed. LLVM's libunwind
143 is used by all supported CPU architectures.
146 GCC 4.2.1 has been removed from the tree. The WITH_GCC,
147 WITH_GCC_BOOTSTRAP, and WITH_GNUCXX options are no longer available.
148 Users who wish to build FreeBSD with GCC must use the external toolchain
152 ncurses has been updated to a newer version (6.2-20200215). Given the ABI
153 has changed, users will have to rebuild all the ports that are linked to
157 The size of struct vnet and the magic cookie have changed.
158 Users need to recompile libkvm and all modules using VIMAGE
159 together with their new kernel.
162 Defining the long deprecated NO_CTF, NO_DEBUG_FILES, NO_INSTALLLIB,
163 NO_MAN, NO_PROFILE, and NO_WARNS variables is now an error. Update
164 your Makefiles and scripts to define MK_<var>=no instead as required.
166 One exception to this is that program or library Makefiles should
167 define MAN to empty rather than setting MK_MAN=no.
170 Clang/LLVM is now the default compiler and LLD the default
174 make universe no longer uses GCC 4.2.1 on any architectures.
175 Architectures not supported by in-tree Clang/LLVM require an
176 external toolchain package.
179 GCC 4.2.1 is now not built by default, as part of the GCC 4.2.1
180 retirement plan. Specifically, the GCC, GCC_BOOTSTRAP, and GNUCXX
181 options default to off for all supported CPU architectures. As a
182 short-term transition aid they may be enabled via WITH_* options.
183 GCC 4.2.1 is expected to be removed from the tree on 2020-03-31.
186 Support for armv5 has been disconnected and is being removed. The
187 machine combination MACHINE=arm MACHINE_ARCH=arm is no longer valid.
188 You must now use a MACHINE_ARCH of armv6 or armv7. The default
189 MACHINE_ARCH for MACHINE=arm is now armv7.
192 Clang/LLVM is now the default compiler for all powerpc architectures.
193 LLD is now the default linker for powerpc64. The change for powerpc64
194 also includes a change to the ELFv2 ABI, incompatible with the existing
198 Kernel-loadable random(4) modules are no longer unloadable.
201 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
202 been upgraded to 9.0.1. Please see the 20141231 entry below for
203 information about prerequisites and upgrading, if you are not already
204 using clang 3.5.0 or higher.
207 r355677 has modified the internal interface used between the
208 NFS modules in the kernel. As such, they must all be upgraded
209 simultaneously. I will do a version bump for this.
212 The root certificates of the Mozilla CA Certificate Store have been
213 imported into the base system and can be managed with the certctl(8)
214 utility. If you have installed the security/ca_root_nss port or package
215 with the ETCSYMLINK option (the default), be advised that there may be
216 differences between those included in the port and those included in
217 base due to differences in nss branch used as well as general update
218 frequency. Note also that certctl(8) cannot manage certs in the
219 format used by the security/ca_root_nss port.
222 The amd(8) automount daemon has been disabled by default, and will be
223 removed in the future. As of FreeBSD 10.1 the autofs(5) is available
227 The nctgpio and wbwd drivers have been moved to the superio bus.
228 If you have one of these drivers in a kernel configuration, then
229 you should add device superio to it. If you use one of these drivers
230 as a module and you compile a custom set of modules, then you should
231 add superio to the set.
234 KPIs for network drivers to access interface addresses have changed.
235 Users need to recompile NIC driver modules together with kernel.
238 The net.link.tap.user_open sysctl no longer prevents user opening of
239 already created /dev/tapNN devices. Access is still controlled by
240 node permissions, just like tun devices. The net.link.tap.user_open
241 sysctl is now used only to allow users to perform devfs cloning of
242 tap devices, and the subsequent open may not succeed if the user is not
243 in the appropriate group. This sysctl may be deprecated/removed
244 completely in the future.
247 mips, powerpc, and sparc64 are no longer built as part of
248 universe / tinderbox unless MAKE_OBSOLETE_GCC is defined. If
249 not defined, mips, powerpc, and sparc64 builds will look for
250 the xtoolchain binaries and if installed use them for universe
251 builds. As llvm 9.0 becomes vetted for these architectures, they
252 will be removed from the list.
255 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
256 been upgraded to 9.0.0. Please see the 20141231 entry below for
257 information about prerequisites and upgrading, if you are not already
258 using clang 3.5.0 or higher.
261 The hpt27xx, hptmv, hptnr, and hptrr drivers have been removed from
262 GENERIC. They are available as modules and can be loaded by adding
263 to /boot/loader.conf hpt27xx_load="YES", hptmv_load="YES",
264 hptnr_load="YES", or hptrr_load="YES", respectively.
267 ntpd no longer by default locks its pages in memory, allowing them
268 to be paged out by the kernel. Use rlimit memlock to restore
269 historic BSD behaviour. For example, add "rlimit memlock 32"
270 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
273 Several of ping6's options have been renamed for better consistency
274 with ping. If you use any of -ARWXaghmrtwx, you must update your
275 scripts. See ping6(8) for details.
278 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
279 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
280 been removed from mount_fusefs(8). You can safely remove them from
281 your scripts, because they had no effect.
283 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
284 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
285 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
286 sysctls have been removed. If you felt the need to set any of them to
287 a non-default value, please tell asomers@FreeBSD.org why.
290 Default permissions on the /var/account/acct file (and copies of it
291 rotated by periodic daily scripts) are changed from 0644 to 0640
292 because the file contains sensitive information that should not be
293 world-readable. If the /var/account directory must be created by
294 rc.d/accounting, the mode used is now 0750. Admins who use the
295 accounting feature are encouraged to change the mode of an existing
296 /var/account directory to 0750 or 0700.
299 Entropy collection and the /dev/random device are no longer optional
300 components. The "device random" option has been removed.
301 Implementations of distilling algorithms can still be made loadable
302 with "options RANDOM_LOADABLE" (e.g., random_fortuna.ko).
305 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
306 been upgraded to 8.0.1. Please see the 20141231 entry below for
307 information about prerequisites and upgrading, if you are not already
308 using clang 3.5.0 or higher.
311 A fix was applied to i386 kernel modules to avoid panics with
312 dpcpu or vnet. Users need to recompile i386 kernel modules
313 having pcpu or vnet sections or they will refuse to load.
316 User-wired pages now have their own counter,
317 vm.stats.vm.v_user_wire_count. The vm.max_wired sysctl was renamed
318 to vm.max_user_wired and changed from an unsigned int to an unsigned
319 long. bhyve VMs wired with the -S are now subject to the user
320 wiring limit; the vm.max_user_wired sysctl may need to be tuned to
321 avoid running into the limit.
324 The IPSEC option has been removed from GENERIC. Users requiring
325 ipsec(4) must now load the ipsec(4) kernel module.
328 The tap(4) driver has been folded into tun(4), and the module has been
329 renamed to tuntap. You should update any kld_list="if_tap" or
330 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
331 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
332 module instead, and "device tap" or "device tun" entries in kernel
333 config files to select the tuntap device instead.
336 The following knobs have been added related to tradeoffs between
337 safe use of the random device and availability in the absence of
340 kern.random.initial_seeding.bypass_before_seeding: tunable; set
341 non-zero to bypass the random device prior to seeding, or zero to
342 block random requests until the random device is initially seeded.
343 For now, set to 1 (unsafe) by default to restore pre-r346250 boot
344 availability properties.
346 kern.random.initial_seeding.read_random_bypassed_before_seeding:
347 read-only diagnostic sysctl that is set when bypass is enabled and
348 read_random(9) is bypassed, to enable programmatic handling of this
349 initial condition, if desired.
351 kern.random.initial_seeding.arc4random_bypassed_before_seeding:
352 Similar to the above, but for for arc4random(9) initial seeding.
354 kern.random.initial_seeding.disable_bypass_warnings: tunable; set
355 non-zero to disable warnings in dmesg when the same conditions are
356 met as for the diagnostic sysctls above. Defaults to zero, i.e.,
357 produce warnings in dmesg when the conditions are met.
360 The loadable random module KPI has changed; the random_infra_init()
361 routine now requires a 3rd function pointer for a bool (*)(void)
362 method that returns true if the random device is seeded (and
363 therefore unblocked).
366 r345895 reverts r320698. This implies that an nfsuserd(8) daemon
367 built from head sources between r320757 (July 6, 2017) and
368 r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
369 is added to the command line.
370 nfsuserd daemons built from head sources that are post-r338192 are
371 not affected and should continue to work.
374 The fuse(4) module has been renamed to fusefs(4) for consistency with
375 other filesystems. You should update any kld_load="fuse" entries in
376 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
377 "options FUSE" entries in kernel config files.
380 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
381 8.0.0. Please see the 20141231 entry below for information about
382 prerequisites and upgrading, if you are not already using clang 3.5.0
386 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
387 compiled into your custom kernel, add 'device xz' statement to the
391 drm and drm2 have been removed from the tree. Please see
392 https://wiki.freebsd.org/Graphics for the latest information on
393 migrating to the drm ports.
396 Iflib is no longer unconditionally compiled into the kernel. Drivers
397 using iflib and statically compiled into the kernel, now require
398 the 'device iflib' config option. For the same drivers loaded as
399 modules on kernels not having 'device iflib', the iflib.ko module
400 is loaded automatically.
403 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
404 options no longer exist since r343219 and r343427 respectively;
405 nothing uses them, so they should be just removed from custom
409 r342635 changes the way efibootmgr(8) works by requiring users to add
410 the -b (bootnum) parameter for commands where the bootnum was previously
411 specified with each option. For example 'efibootmgr -B 0001' is now
412 'efibootmgr -B -b 0001'.
415 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
416 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
417 servers that have vfs.nfsd.nfs_privport set will only allow mounts
418 from clients using a reserved port#. Since both the FreeBSD and Linux
419 NFSv4 clients use reserved port#s by default, this should not affect
423 The XLP config has been removed. We can't support 64-bit atomics in this
424 kernel because it is running in 32-bit mode. XLP users must transition
425 to running a 64-bit kernel (XLP64 or XLPN32).
427 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
428 the preferred emulator today and we don't need two different ones.
430 The old sibyte / swarm / Broadcom BCM1250 support has been
431 removed from the mips port.
434 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
435 7.0.1. Please see the 20141231 entry below for information about
436 prerequisites and upgrading, if you are not already using clang 3.5.0
440 Remove the timed and netdate programs from the base tree. Setting
441 the time with these daemons has been obsolete for over a decade.
444 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
445 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
446 it produces broken binaries when ifuncs are in use. Users needing
447 GNU ld should install the binutils port or package.
450 The BSD crtbegin and crtend code has been enabled by default. It has
451 had extensive testing on amd64, arm64, and i386. It can be disabled
452 by building a world with -DWITHOUT_BSD_CRTBEGIN.
455 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
456 has been converted to a port (misc/ctm) and will be removed from
457 FreeBSD-13. It is available as a package (ctm) for all supported
461 The default newsyslog.conf(5) file has been changed to only include
462 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
463 the filenames end in '.conf' and do not begin with a '.'.
465 You should check the configuration files in these two directories match
466 this naming convention. You can verify which configuration files are
467 being included using the command:
471 Ports for the DRM modules have been simplified. Now, amd64 users should
472 just install the drm-kmod port. All others should install
475 Graphics hardware that's newer than about 2010 usually works with
476 drm-kmod. For hardware older than 2013, however, some users will need
477 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
478 than 2008 usually only works in drm-legacy-kmod. The graphics team can
479 only commit to hardware made since 2013 due to the complexity of the
480 market and difficulty to test all the older cards effectively. If you
481 have hardware supported by drm-kmod, you are strongly encouraged to use
482 that as you will get better support.
484 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
485 elsewhere, the drm and drm2 modules will be eliminated from the src base
486 soon (with a limited exception for arm). Please update to the package
487 asap and report any issues to x11@freebsd.org.
489 Generally, anybody using the drm*-kmod packages should add
490 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
491 cross-threading surprises, especially with automatic driver
492 loading from X11 startup. These will become the defaults in 13-current
496 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
497 custom kernel and module loading configuration files must be updated
498 accordingly. Moreover, interfaces previous presented as ixlvN to the
499 system are now exposed as iavfN and network configuration files must
500 be adjusted as necessary.
503 OpenSSL has been updated to version 1.1.1. This update included
504 additional various API changes throughout the base system. It is
505 important to rebuild third-party software after upgrading. The value
506 of __FreeBSD_version has been bumped accordingly.
509 The legacy DRM modules and drivers have now been added to the loader's
510 module blacklist, in favor of loading them with kld_list in rc.conf(5).
511 The module blacklist may be overridden with the loader.conf(5)
512 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
516 The cam(4) based nda(4) driver will be used over nvd(4) by default on
517 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
518 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
519 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
523 Reproducible build mode is now on by default, in preparation for
524 FreeBSD 12.0. This eliminates build metadata such as the user,
525 host, and time from the kernel (and uname), unless the working tree
526 corresponds to a modified checkout from a version control system.
527 The previous behavior can be obtained by setting the /etc/src.conf
528 knob WITHOUT_REPRODUCIBLE_BUILD.
531 The Yarrow CSPRNG has been removed from the kernel as it has not been
532 supported by its designers since at least 2003. Fortuna has been the
533 default since FreeBSD-11.
536 devctl freeze/thaw have gone into the tree, the rc scripts have been
537 updated to use them and devmatch has been changed. You should update
538 kernel, userland and rc scripts all at the same time.
541 The default interpreter has been switched from 4th to Lua.
542 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
543 interpreter. If you have custom FORTH code you will need to set
544 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
545 src.conf for the build. This will create default hard links between
546 loader and loader_4th instead of loader and loader_lua, the new default.
547 If you are using UEFI it will create the proper hard link to loader.efi.
549 bhyve uses userboot.so. It remains 4th-only until some issues are solved
550 regarding coexisting with multiple versions of FreeBSD are resolved.
553 ls(1) now respects the COLORTERM environment variable used in other
554 systems and software to indicate that a colored terminal is both
555 supported and desired. If ls(1) is suddenly emitting colors, they may
556 be disabled again by either removing the unwanted COLORTERM from your
557 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
558 may not be observed in a future release.
561 The default pager for most commands has been changed to "less". To
562 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
566 The jedec_ts(4) driver has been removed. A superset of its functionality
567 is available in the jedec_dimm(4) driver, and the manpage for that
568 driver includes migration instructions. If you have "device jedec_ts"
569 in your kernel configuration file, it must be removed.
572 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
573 This should have no effect if the kernel is booted via BIOS/legacy boot.
574 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
575 has a buggy firmware that prevents a successful boot due to use of
579 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
580 support has been removed from the tree. These ports were
581 obsolete and/or known to be broken for many years.
584 loader.efi has been augmented to participate more fully in the
585 UEFI boot manager protocol. loader.efi will now look at the
586 BootXXXX environment variable to determine if a specific kernel
587 or root partition was specified. XXXX is derived from BootCurrent.
588 efibootmgr(8) manages these standard UEFI variables.
591 zfsloader's functionality has now been folded into loader.
592 zfsloader is no longer necessary once you've updated your
593 boot blocks. For a transition period, we will install a
594 hardlink for zfsloader to loader to allow a smooth transition
595 until the boot blocks can be updated (hard link because old
596 zfs boot blocks don't understand symlinks).
599 ARM64 now have efifb support, if you want to have serial console
600 on your arm64 board when an screen is connected and the bootloader
601 setup a frame buffer for us to use, just add :
605 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
606 an screen connected as the firmware will setup a frame buffer are that
607 u-boot will expose as an EFI frame buffer.
610 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
611 or take steps to update /etc/passwd before doing installworld on
612 existing systems. Do not skip the "mergemaster -Fp" step before
613 installworld, as described in the update procedures near the bottom
614 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
615 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
616 the ntp config file contain options that change file/dir locations.
617 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
618 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
619 taking steps to ensure that all required files/dirs are accessible
623 Big endian arm support has been removed.
626 The static environment setup in kernel configs is no longer mutually
627 exclusive with the loader(8) environment by default. In order to
628 restore the previous default behavior of disabling the loader(8)
629 environment if a static environment is present, you must specify
630 loader_env.disabled=1 in the static environment.
633 The ABI of syscalls used by management tools like sockstat and
634 netstat has been broken to allow 32-bit binaries to work on
635 64-bit kernels without modification. These programs will need
636 to match the kernel in order to function. External programs may
637 require minor modifications to accommodate a change of type in
638 structures from pointers to 64-bit virtual addresses.
641 On i386 and amd64 atomics are now inlined. Out of tree modules using
642 atomics will need to be rebuilt.
645 The '%I' format in the kern.corefile sysctl limits the number of
646 core files that a process can generate to the number stored in the
647 debug.ncores sysctl. The '%I' format is replaced by the single digit
648 index. Previously, if all indexes were taken the kernel would overwrite
649 only a core file with the highest index in a filename.
650 Currently the system will create a new core file if there is a free
651 index or if all slots are taken it will overwrite the oldest one.
654 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
655 6.0.1. Please see the 20141231 entry below for information about
656 prerequisites and upgrading, if you are not already using clang 3.5.0
660 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
661 needed to be changed to work with it. This change was made with r335763
662 and requires a mergemaster / etcupdate / etc to update the installed
666 r334930 changed the interface between the NFS modules, so they all
667 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
670 As of r334391 lld is the default amd64 system linker; it is installed
671 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
675 The kernel / userland interface for devinfo changed, so you'll
676 need a new kernel and userland as a pair for it to work (rebuilding
677 lib/libdevinfo is all that's required). devinfo and devmatch will
678 not work, but everything else will when there's a mismatch.
681 The on-disk format for hwpmc callchain records has changed to include
682 threadid corresponding to a given record. This changes the field offsets
683 and thus requires that libpmcstat be rebuilt before using a kernel
687 The vxge(4) driver has been removed. This driver was introduced into
688 HEAD one week before the Exar left the Ethernet market and is not
689 known to be used. If you have device vxge in your kernel config file
693 The amd64 kernel now requires a ld that supports ifunc to produce a
694 working kernel, either lld or a newer binutils. lld is built by default
695 on amd64, and the 'buildkernel' target uses it automatically. However,
696 it is not the default linker, so building the kernel the traditional
697 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
698 binutils port/package). lld will soon be default, and this requirement
701 NOTE: As of r334391 lld is the default system linker on amd64, and no
702 workaround is necessary.
705 The nxge(4) driver has been removed. This driver was for PCI-X 10g
706 cards made by s2io/Neterion. The company was acquired by Exar and
707 no longer sells or supports Ethernet products. If you have device
708 nxge in your kernel config file it must be removed.
711 The tz database (tzdb) has been updated to 2018e. This version more
712 correctly models time stamps in time zones with negative DST such as
713 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
714 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
715 time zone abbreviations and the tm_isdst flag.
718 The ixgb(4) driver has been removed. This driver was for an early and
719 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
720 quickly shifted to the long lived ixgbe family. If you have device
721 ixgb in your kernel config file it must be removed.
724 The lmc(4) driver has been removed. This was a WAN interface
725 card that was already reportedly rare in 2003, and had an ambiguous
726 license. If you have device lmc in your kernel config file it must
730 Support for Arcnet networks has been removed. If you have device
731 arcnet or device cm in your kernel config file they must be
735 Support for FDDI networks has been removed. If you have device
736 fddi or device fpa in your kernel config file they must be
740 In addition to supporting RFC 3164 formatted messages, the
741 syslogd(8) service is now capable of parsing RFC 5424 formatted
742 log messages. The main benefit of using RFC 5424 is that clients
743 may now send log messages with timestamps containing year numbers,
744 microseconds and time zone offsets.
746 Similarly, the syslog(3) C library function has been altered to
747 send RFC 5424 formatted messages to the local system logging
748 daemon. On systems using syslogd(8), this change should have no
749 negative impact, as long as syslogd(8) and the C library are
750 updated at the same time. On systems using a different system
751 logging daemon, it may be necessary to make configuration
752 adjustments, depending on the software used.
754 When using syslog-ng, add the 'syslog-protocol' flag to local
755 input sources to enable parsing of RFC 5424 formatted messages:
758 unix-dgram("/var/run/log" flags(syslog-protocol));
761 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
762 of the 'imuxsock' module to let messages be processed by the
763 regular RFC 3164/5424 parsing pipeline:
765 module(load="imuxsock" SysSock.UseSpecialParser="off")
767 Do note that these changes only affect communication between local
768 applications and syslogd(8). The format that syslogd(8) uses to
769 store messages on disk or forward messages to other systems
770 remains unchanged. syslogd(8) still uses RFC 3164 for these
771 purposes. Options to customize this behaviour will be added in the
772 future. Utilities that process log files stored in /var/log are
773 thus expected to continue to function as before.
775 __FreeBSD_version has been incremented to 1200061 to denote this
779 Support for token ring networks has been removed. If you
780 have "device token" in your kernel config you should remove
781 it. No device drivers supported token ring.
784 makefs was modified to be able to tag ISO9660 El Torito boot catalog
785 entries as EFI instead of overloading the i386 tag as done previously.
786 The amd64 mkisoimages.sh script used to build amd64 ISO images for
787 release was updated to use this. This may mean that makefs must be
788 updated before "make cdrom" can be run in the release directory. This
789 should be as simple as:
791 $ cd $SRCDIR/usr.sbin/makefs
792 $ make depend all install
795 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
796 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
797 Co-existence for the transition period will come shortly. Booting is a
798 complex environment and test coverage for Lua-enabled loaders has been
799 thin, so it would be prudent to assume it might not work and make
800 provisions for backup boot methods.
803 devmatch functionality has been turned on in devd. It will automatically
804 load drivers for unattached devices. This may cause unexpected drivers
805 to be loaded. Please report any problems to current@ and
809 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
810 6.0.0. Please see the 20141231 entry below for information about
811 prerequisites and upgrading, if you are not already using clang 3.5.0
815 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
816 This means it is used to link the kernel and userland libraries and
817 executables, but is not yet installed as /usr/bin/ld by default.
819 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
820 WITHOUT_LLD_BOOTSTRAP=yes
823 On i386, pmtimer has been removed. Its functionality has been folded
824 into apm. It was a no-op on ACPI in current for a while now (but was
825 still needed on i386 in FreeBSD 11 and earlier). Users may need to
826 remove it from kernel config files.
829 The use of RSS hash from the network card aka flowid has been
830 disabled by default for lagg(4) as it's currently incompatible with
831 the lacp and loadbalance protocols.
833 This can be re-enabled by setting the following in loader.conf:
834 net.link.lagg.default_use_flowid="1"
837 The SW_WATCHDOG option is no longer necessary to enable the
838 hardclock-based software watchdog if no hardware watchdog is
839 configured. As before, SW_WATCHDOG will cause the software
840 watchdog to be enabled even if a hardware watchdog is configured.
843 r326887 fixes the issue described in the 20171214 UPDATING entry.
844 r326888 flips the switch back to building GELI support always.
847 r362593 broke ZFS + GELI support for reasons unknown. However,
848 it also broke ZFS support generally, so GELI has been turned off
849 by default as the lesser evil in r326857. If you boot off ZFS and/or
850 GELI, it might not be a good time to update.
853 PowerPC users must update loader(8) by rebuilding world before
854 installing a new kernel, as the protocol connecting them has
855 changed. Without the update, loader metadata will not be passed
856 successfully to the kernel and users will have to enter their
857 root partition at the kernel mountroot prompt to continue booting.
858 Newer versions of loader can boot old kernels without issue.
861 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
862 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
863 to WITH/OUT_LOADER_GELI.
866 The naive and non-compliant support of posix_fallocate(2) in ZFS
867 has been removed as of r325320. The system call now returns EINVAL
868 when used on a ZFS file. Although the new behavior complies with the
869 standard, some consumers are not prepared to cope with it.
870 One known victim is lld prior to r325420.
873 Building in a FreeBSD src checkout will automatically create object
874 directories now rather than store files in the current directory if
875 'make obj' was not ran. Calling 'make obj' is no longer necessary.
876 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
877 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
881 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
882 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
883 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
884 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
885 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
886 The UNIFIED_OBJDIR option is a transitional feature that will be
887 removed for 12.0 release; please migrate to the new format for any
888 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
889 than hardcoding paths.
892 The native-xtools target no longer installs the files by default to the
893 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
894 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
897 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
898 options are changing from controlling the build if defined / undefined
899 to controlling the build with explicit 'yes' or 'no' values. They will
900 shift to WITH/WITHOUT options to match other options in the system.
903 libstand has turned into a private library for sys/boot use only.
904 It is no longer supported as a public interface outside of sys/boot.
907 The arm port has split armv6 into armv6 and armv7. armv7 is now
908 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
909 and are running a kernel from before r324363, you will need to add
910 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
913 When building multiple kernels using KERNCONF, non-existent KERNCONF
914 files will produce an error and buildkernel will fail. Previously
915 missing KERNCONF files silently failed giving no indication as to
916 why, only to subsequently discover during installkernel that the
917 desired kernel was never built in the first place.
920 The default serial number format for CTL LUNs has changed. This will
921 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
922 or iSCSI clients care about their LUNs' serial numbers. Users who
923 require serial number stability should hardcode serial numbers in
927 For 32-bit arm compiled for hard-float support, soft-floating point
928 binaries now always get their shared libraries from
929 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
930 /usr/libsoft also existed). Only users with a hard-float ld.so, but
931 soft-float everything else should be affected.
934 The geli password typed at boot is now hidden. To restore the previous
935 behavior, see geli(8) for configuration options.
938 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
939 sysctl values. Minor nit, but requires a rebuild of both world/kernel
943 "make check" behavior (made in ^/head@r295380) has been changed to
944 execute from a limited sandbox, as opposed to executing from
948 - The "beforecheck" and "aftercheck" targets are now specified.
949 - ${CHECKDIR} (added in commit noted above) has been removed.
950 - Legacy behavior can be enabled by setting
951 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
953 If the limited sandbox mode is enabled, "make check" will execute
954 "make distribution", then install, execute the tests, and clean up the
955 sandbox if successful.
957 The "make distribution" and "make install" targets are typically run as
958 root to set appropriate permissions and ownership at installation time.
959 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
960 environment if executing "make check" with limited sandbox mode using
961 an unprivileged user.
964 Since the switch to GPT disk labels, fsck for UFS/FFS has been
965 unable to automatically find alternate superblocks. As of r322297,
966 the information needed to find alternate superblocks has been
967 moved to the end of the area reserved for the boot block.
968 Filesystems created with a newfs of this vintage or later
969 will create the recovery information. If you have a filesystem
970 created prior to this change and wish to have a recovery block
971 created for your filesystem, you can do so by running fsck in
972 foreground mode (i.e., do not use the -p or -y options). As it
973 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
974 to which you should answer yes.
977 As of r321665, an NFSv4 server configuration that services
978 Kerberos mounts or clients that do not support the uid/gid in
979 owner/owner_group string capability, must explicitly enable
980 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
981 machine's /etc/rc.conf file.
984 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
985 Please see the 20141231 entry below for information about prerequisites
986 and upgrading, if you are not already using clang 3.5.0 or higher.
989 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
990 r-commands (rlogin, rsh, etc.) to be built with the base system.
993 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
994 a very major ABI incompatible change, so users of FreeBSD/powerpc must
995 be careful when performing source upgrades. It is best to run
996 'make installworld' from an alternate root system, either a live
997 CD/memory stick, or a temporary root partition. Additionally, all ports
998 must be recompiled. powerpc64 is largely unaffected, except in the case
999 of 32-bit compatibility. All 32-bit binaries will be affected.
1002 Forward compatibility for the "ino64" project have been committed. This
1003 will allow most new binaries to run on older kernels in a limited
1004 fashion. This prevents many of the common foot-shooting actions in the
1005 upgrade as well as the limited ability to roll back the kernel across
1006 the ino64 upgrade. Complicated use cases may not work properly, though
1007 enough simpler ones work to allow recovery in most situations.
1010 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
1011 if you require the GPL compiler.
1014 The internal ABI used for communication between the NFS kernel modules
1015 was changed by r320085, so __FreeBSD_version was bumped to
1016 ensure all the NFS related modules are updated together.
1019 The ABI of struct event was changed by extending the data
1020 member to 64bit and adding ext fields. For upgrade, same
1021 precautions as for the entry 20170523 "ino64" must be
1025 The GNU roff toolchain has been removed from base. To render manpages
1026 which are not supported by mandoc(1), man(1) can fallback on GNU roff
1027 from ports (and recommends to install it).
1028 To render roff(7) documents, consider using GNU roff from ports or the
1029 heirloom doctools roff toolchain from ports via pkg install groff or
1030 via pkg install heirloom-doctools.
1033 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
1034 smaller runtime footprint builds. This is useful for embedded systems
1035 which only require one chipset support.
1037 If you load it as a module, make sure this is in /boot/loader.conf:
1041 This will load the HAL, all chip/RF backends and if_ath_pci.
1042 If you have if_ath_pci in /boot/loader.conf, ensure it is after
1043 if_ath or it will not load any HAL chipset support.
1045 If you want to selectively load things (eg on ye cheape ARM/MIPS
1046 platforms where RAM is at a premium) you should:
1049 * load the chip modules in question
1050 * load ath_rate, ath_dfs
1052 * load if_ath_pci and/or if_ath_ahb depending upon your particular
1053 bus bind type - this is where probe/attach is done.
1055 For further comments/feedback, poke adrian@ .
1058 The "ino64" 64-bit inode project has been committed, which extends
1059 a number of types to 64 bits. Upgrading in place requires care and
1060 adherence to the documented upgrade procedure.
1062 If using a custom kernel configuration ensure that the
1063 COMPAT_FREEBSD11 option is included (as during the upgrade the
1064 system will be running the ino64 kernel with the existing world).
1066 For the safest in-place upgrade begin by removing previous build
1067 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full
1068 procedure documented below under the heading "To rebuild everything and
1069 install it on the current system." Specifically, a reboot is required
1070 after installing the new kernel before installing world. While an
1071 installworld normally works by accident from multiuser after rebooting
1072 the proper kernel, there are many cases where this will fail across this
1073 upgrade and installworld from single user is required.
1076 The NATM framework including the en(4), fatm(4), hatm(4), and
1077 patm(4) devices has been removed. Consumers should plan a
1078 migration before the end-of-life date for FreeBSD 11.
1081 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
1082 diff has not been implemented, if those are needed a newer version of
1083 GNU diff is available via the diffutils package under the gdiff name.
1086 As of r316810 for ipfilter, keep frags is no longer assumed when
1087 keep state is specified in a rule. r316810 aligns ipfilter with
1088 documentation in man pages separating keep frags from keep state.
1089 This allows keep state to be specified without forcing keep frags
1090 and allows keep frags to be specified independently of keep state.
1091 To maintain previous behaviour, also specify keep frags with
1092 keep state (as documented in ipf.conf.5).
1095 arm64 builds now use the base system LLD 4.0.0 linker by default,
1096 instead of requiring that the aarch64-binutils port or package be
1097 installed. To continue using aarch64-binutils, set
1098 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
1101 The UDP optimization in entry 20160818 that added the sysctl
1102 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
1103 packets will no longer be treated as L3 broadcast packets.
1106 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
1107 use any explicitly assigned loopback address available in the jail
1108 instead of using the first assigned address of the jail.
1111 The ctl.ko module no longer implements the iSCSI target frontend:
1112 cfiscsi.ko does instead.
1114 If building cfiscsi.ko as a kernel module, the module can be loaded
1115 via one of the following methods:
1116 - `cfiscsi_load="YES"` in loader.conf(5).
1117 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
1118 - ctladm(8)/ctld(8), when compiled with iSCSI support
1119 (`WITH_ISCSI=yes` in src.conf(5))
1121 Please see cfiscsi(4) for more details.
1124 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
1125 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
1126 same source (previously, the dependency of mmcsd.ko on mmc.ko was
1127 missing, but mmcsd.ko now will refuse to load if it is incompatible
1131 The syntax of ipfw(8) named states was changed to avoid ambiguity.
1132 If you have used named states in the firewall rules, you need to modify
1133 them after installworld and before rebooting. Now named states must
1134 be prefixed with colon.
1137 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
1138 removed as the userland we provide cannot use them. The KMS version
1139 (sys/dev/drm2) supports the same hardware.
1142 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
1143 Please see the 20141231 entry below for information about prerequisites
1144 and upgrading, if you are not already using clang 3.5.0 or higher.
1147 The code that provides support for ZFS .zfs/ directory functionality
1148 has been reimplemented. It's not possible now to create a snapshot
1149 by mkdir under .zfs/snapshot/. That should be the only user visible
1153 EISA bus support has been removed. The WITH_EISA option is no longer
1157 MCA bus support has been removed.
1160 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
1161 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
1164 The EM_MULTIQUEUE kernel configuration option is deprecated now that
1165 the em(4) driver conforms to iflib specifications.
1168 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
1169 IFLIB. If you have a custom kernel configuration that excludes em(4)
1170 but you use igb(4), you need to re-add em(4) to your custom
1174 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
1175 Please see the 20141231 entry below for information about prerequisites
1176 and upgrading, if you are not already using clang 3.5.0 or higher.
1179 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
1180 Please see the 20141231 entry below for information about prerequisites
1181 and upgrading, if you are not already using clang 3.5.0 or higher.
1184 The layout of the pmap structure has changed for powerpc to put the pmap
1185 statistics at the front for all CPU variations. libkvm(3) and all tools
1186 that link against it need to be recompiled.
1189 isl(4) and cyapa(4) drivers now require a new driver,
1190 chromebook_platform(4), to work properly on Chromebook-class hardware.
1191 On other types of hardware the drivers may need to be configured using
1192 device hints. Please see the corresponding manual pages for details.
1195 The urtwn(4) driver was merged into rtwn(4) and now consists of
1196 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
1198 Also, firmware for RTL8188CE was renamed due to possible name
1199 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
1202 GNU rcs has been removed from base. It is available as packages:
1203 - rcs: Latest GPLv3 GNU rcs version.
1204 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
1208 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
1209 modules now requires that the kernel configuration contain the
1210 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
1213 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
1214 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
1217 Relocatable object files with the extension of .So have been renamed
1218 to use an extension of .pico instead. The purpose of this change is
1219 to avoid a name clash with shared libraries on case-insensitive file
1220 systems. On those file systems, foo.So is the same file as foo.so.
1223 GNU rcs has been turned off by default. It can (temporarily) be built
1224 again by adding WITH_RCS knob in src.conf.
1225 Otherwise, GNU rcs is available from packages:
1226 - rcs: Latest GPLv3 GNU rcs version.
1227 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
1230 The backup_uses_rcs functionality has been removed from rc.subr.
1233 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
1234 two separate components, QUEUE_MACRO_DEBUG_TRACE and
1235 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
1236 QUEUE_MACRO_DEBUG behavior.
1239 r304787 changed some ioctl interfaces between the iSCSI userspace
1240 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1241 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1245 The UDP receive code has been updated to only treat incoming UDP
1246 packets that were addressed to an L2 broadcast address as L3
1247 broadcast packets. It is not expected that this will affect any
1248 standards-conforming UDP application. The new behaviour can be
1249 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1253 Remove the openbsd_poll system call.
1254 __FreeBSD_version has been bumped because of this.
1257 The stable/11 branch has been created from head@r302406.
1260 The libc stub for the pipe(2) system call has been replaced with
1261 a wrapper that calls the pipe2(2) system call and the pipe(2)
1262 system call is now only implemented by the kernels that include
1263 "options COMPAT_FREEBSD10" in their config file (this is the
1264 default). Users should ensure that this option is enabled in
1265 their kernel or upgrade userspace to r302092 before upgrading their
1269 CAM will now strip leading spaces from SCSI disks' serial numbers.
1270 This will affect users who create UFS filesystems on SCSI disks using
1271 those disk's diskid device nodes. For example, if /etc/fstab
1272 previously contained a line like
1273 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
1274 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
1275 transforms like gmirror may also be affected. ZFS users should
1279 The bitstring(3) API has been updated with new functionality and
1280 improved performance. But it is binary-incompatible with the old API.
1281 Objects built with the new headers may not be linked against objects
1282 built with the old headers.
1285 The brk and sbrk functions have been removed from libc on arm64.
1286 Binutils from ports has been updated to not link to these
1287 functions and should be updated to the latest version before
1288 installing a new libc.
1291 The armv6 port now defaults to hard float ABI. Limited support
1292 for running both hardfloat and soft float on the same system
1293 is available using the libraries installed with -DWITH_LIBSOFT.
1294 This has only been tested as an upgrade path for installworld
1295 and packages may fail or need manual intervention to run. New
1296 packages will be needed.
1298 To update an existing self-hosted armv6hf system, you must add
1299 TARGET_ARCH=armv6 on the make command line for both the build
1300 and the install steps.
1303 Kernel modules compiled outside of a kernel build now default to
1304 installing to /boot/modules instead of /boot/kernel. Many kernel
1305 modules built this way (such as those in ports) already overrode
1306 KMODDIR explicitly to install into /boot/modules. However,
1307 manually building and installing a module from /sys/modules will
1308 now install to /boot/modules instead of /boot/kernel.
1311 The CAM I/O scheduler has been committed to the kernel. There should be
1312 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1313 list of known rogues that claim support for this but actually corrupt
1314 data is believed to be complete, be on the lookout for data
1315 corruption. The known rogue list is believed to be complete:
1317 o Crucial MX100, M550 drives with MU01 firmware.
1318 o Micron M510 and M550 drives with MU01 firmware.
1319 o Micron M500 prior to MU07 firmware
1320 o Samsung 830, 840, and 850 all firmwares
1321 o FCCT M500 all firmwares
1323 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1324 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1325 updated firmware. Black listed drives will work correctly because these
1326 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1327 this list is the same as found in Linux, it's believed there are no
1328 other rogues in the market place. All other models from the above
1331 To be safe, if you are at all concerned, you can quirk each of your
1332 drives to prevent NCQ from being sent by setting:
1333 kern.cam.ada.X.quirks="0x2"
1334 in loader.conf. If the drive requires the 4k sector quirk, set the
1335 quirks entry to 0x3.
1338 The FAST_DEPEND build option has been removed and its functionality is
1339 now the one true way. The old mkdep(1) style of 'make depend' has
1340 been removed. See 20160311 for further details.
1343 Resource range types have grown from unsigned long to uintmax_t. All
1344 drivers, and anything using libdevinfo, need to be recompiled.
1347 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1348 builds. It no longer runs mkdep(1) during 'make depend', and the
1349 'make depend' stage can safely be skipped now as it is auto ran
1350 when building 'make all' and will generate all SRCS and DPSRCS before
1351 building anything else. Dependencies are gathered at compile time with
1352 -MF flags kept in separate .depend files per object file. Users should
1353 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1354 stale .depend files.
1357 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1358 kernel modules. Therefore, if you load any kernel modules at boot time,
1359 please install the boot loaders after you install the kernel, but before
1363 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1364 make installkernel KERNCONF=YOUR_KERNEL_HERE
1365 make -C sys/boot install
1366 <reboot in single user>
1368 Then follow the usual steps, described in the General Notes section,
1372 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1373 see the 20141231 entry below for information about prerequisites and
1374 upgrading, if you are not already using clang 3.5.0 or higher.
1377 The AIO subsystem is now a standard part of the kernel. The
1378 VFS_AIO kernel option and aio.ko kernel module have been removed.
1379 Due to stability concerns, asynchronous I/O requests are only
1380 permitted on sockets and raw disks by default. To enable
1381 asynchronous I/O requests on all file types, set the
1382 vfs.aio.enable_unsafe sysctl to a non-zero value.
1385 The ELF object manipulation tool objcopy is now provided by the
1386 ELF Tool Chain project rather than by GNU binutils. It should be a
1387 drop-in replacement, with the addition of arm64 support. The
1388 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1389 to obtain the GNU version if necessary.
1392 Building ZFS pools on top of zvols is prohibited by default. That
1393 feature has never worked safely; it's always been prone to deadlocks.
1394 Using a zvol as the backing store for a VM guest's virtual disk will
1395 still work, even if the guest is using ZFS. Legacy behavior can be
1396 restored by setting vfs.zfs.vol.recursive=1.
1399 The NONE and HPN patches has been removed from OpenSSH. They are
1400 still available in the security/openssh-portable port.
1403 With the addition of ypldap(8), a new _ypldap user is now required
1404 during installworld. "mergemaster -p" can be used to add the user
1405 prior to installworld, as documented in the handbook.
1408 The tftp loader (pxeboot) now uses the option root-path directive. As a
1409 consequence it no longer looks for a pxeboot.4th file on the tftp
1410 server. Instead it uses the regular /boot infrastructure as with the
1414 The code to start recording plug and play data into the modules has
1415 been committed. While the old tools will properly build a new kernel,
1416 a number of warnings about "unknown metadata record 4" will be produced
1417 for an older kldxref. To avoid such warnings, make sure to rebuild
1418 the kernel toolchain (or world). Make sure that you have r292078 or
1419 later when trying to build 292077 or later before rebuilding.
1422 Debug data files are now built by default with 'make buildworld' and
1423 installed with 'make installworld'. This facilitates debugging but
1424 requires more disk space both during the build and for the installed
1425 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1429 r291527 changed the internal interface between the nfsd.ko and
1430 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1431 __FreeBSD_version has been bumped because of this.
1434 Add support for unicode collation strings leads to a change of
1435 order of files listed by ls(1) for example. To get back to the old
1436 behaviour, set LC_COLLATE environment variable to "C".
1438 Databases administrators will need to reindex their databases given
1439 collation results will be different.
1441 Due to a bug in install(1) it is recommended to remove the ancient
1442 locales before running make installworld.
1444 rm -rf /usr/share/locale/*
1447 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1448 libcrypto.so.7 or libssl.so.7 must be recompiled.
1451 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1452 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1453 should be replaced with isp_2400 and isp_2500 modules respectively.
1456 The build previously allowed using 'make -n' to not recurse into
1457 sub-directories while showing what commands would be executed, and
1458 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1459 and 'make -N' will not.
1462 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1463 and etcupdate will now use this file. A custom sendmail.cf is now
1464 updated via this mechanism rather than via installworld. If you had
1465 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1466 want to remove the exclusion or change it to "always install".
1467 /etc/mail/sendmail.cf is now managed the same way regardless of
1468 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1469 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1472 Compatibility shims for legacy ATA device names have been removed.
1473 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1474 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1475 environment variables, /dev/ad* and /dev/ar* symbolic links.
1478 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1479 Please see the 20141231 entry below for information about prerequisites
1480 and upgrading, if you are not already using clang 3.5.0 or higher.
1483 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1484 and renamed from .symbols to .debug. This reduces the size requirements
1485 on the boot partition or file system and provides consistency with
1486 userland debug files.
1488 When using the supported kernel installation method the
1489 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1490 as is done with /boot/kernel.
1492 Developers wishing to maintain the historical behavior of installing
1493 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1496 The wireless drivers had undergone changes that remove the 'parent
1497 interface' from the ifconfig -l output. The rc.d network scripts
1498 used to check presence of a parent interface in the list, so old
1499 scripts would fail to start wireless networking. Thus, etcupdate(3)
1500 or mergemaster(8) run is required after kernel update, to update your
1501 rc.d scripts in /etc.
1504 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1505 These configurations are now automatically interpreted as
1506 'scrub fragment reassemble'.
1509 Kernel-loadable modules for the random(4) device are back. To use
1510 them, the kernel must have
1513 options RANDOM_LOADABLE
1515 kldload(8) can then be used to load random_fortuna.ko
1516 or random_yarrow.ko. Please note that due to the indirect
1517 function calls that the loadable modules need to provide,
1518 the build-in variants will be slightly more efficient.
1520 The random(4) kernel option RANDOM_DUMMY has been retired due to
1521 unpopularity. It was not all that useful anyway.
1524 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1525 Control over building the ELF Tool Chain tools is now provided by
1526 the WITHOUT_TOOLCHAIN knob.
1529 The polarity of Pulse Per Second (PPS) capture events with the
1530 uart(4) driver has been corrected. Prior to this change the PPS
1531 "assert" event corresponded to the trailing edge of a positive PPS
1532 pulse and the "clear" event was the leading edge of the next pulse.
1534 As the width of a PPS pulse in a typical GPS receiver is on the
1535 order of 1 millisecond, most users will not notice any significant
1536 difference with this change.
1538 Anyone who has compensated for the historical polarity reversal by
1539 configuring a negative offset equal to the pulse width will need to
1540 remove that workaround.
1543 The default group assigned to /dev/dri entries has been changed
1544 from 'wheel' to 'video' with the id of '44'. If you want to have
1545 access to the dri devices please add yourself to the video group
1548 # pw groupmod video -m $USER
1551 The menu.rc and loader.rc files will now be replaced during
1552 upgrades. Please migrate local changes to menu.rc.local and
1553 loader.rc.local instead.
1556 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1557 strings and strip have been removed. The src.conf(5) knob
1558 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1561 As ZFS requires more kernel stack pages than is the default on some
1562 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1563 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1565 Please consider using 'options KSTACK_PAGES=X' where X is greater
1566 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1569 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1570 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1571 default, i.e., they will not contain "::". For example, instead
1572 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1573 to have a more specific match, such as different map entries for
1574 IPv6:0:0 vs IPv6:0. This change requires that configuration
1575 data (including maps, files, classes, custom ruleset, etc.) must
1576 use the same format, so make certain such configuration data is
1577 upgrading. As a very simple check search for patterns like
1578 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1579 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1580 the cf option UseCompressedIPv6Addresses.
1583 The default kernel entropy-processing algorithm is now
1584 Fortuna, replacing Yarrow.
1586 Assuming you have 'device random' in your kernel config
1587 file, the configurations allow a kernel option to override
1588 this default. You may choose *ONE* of:
1590 options RANDOM_YARROW # Legacy /dev/random algorithm.
1591 options RANDOM_DUMMY # Blocking-only driver.
1593 If you have neither, you get Fortuna. For most people,
1594 read no further, Fortuna will give a /dev/random that works
1595 like it always used to, and the difference will be irrelevant.
1597 If you remove 'device random', you get *NO* kernel-processed
1598 entropy at all. This may be acceptable to folks building
1599 embedded systems, but has complications. Carry on reading,
1600 and it is assumed you know what you need.
1602 *PLEASE* read random(4) and random(9) if you are in the
1603 habit of tweaking kernel configs, and/or if you are a member
1604 of the embedded community, wanting specific and not-usual
1605 behaviour from your security subsystems.
1607 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1608 random', you will NOT have a functioning /dev/random, and
1609 many cryptographic features will not work, including SSH.
1610 You may also find strange behaviour from the random(3) set
1611 of library functions, in particular sranddev(3), srandomdev(3)
1612 and arc4random(3). The reason for this is that the KERN_ARND
1613 sysctl only returns entropy if it thinks it has some to
1614 share, and with RANDOM_DUMMY or no 'device random' this
1618 An additional fix for the issue described in the 20150614 sendmail
1619 entry below has been committed in revision 284717.
1622 FreeBSD's old make (fmake) has been removed from the system. It is
1623 available as the devel/fmake port or via pkg install fmake.
1626 The fix for the issue described in the 20150614 sendmail entry
1627 below has been committed in revision 284436. The work
1628 around described in that entry is no longer needed unless the
1629 default setting is overridden by a confDH_PARAMETERS configuration
1630 setting of '5' or pointing to a 512 bit DH parameter file.
1633 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1634 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1635 and devel/kyua to version 0.20+ and adjust any calling code to work
1636 with Kyuafile and kyua.
1639 The import of openssl to address the FreeBSD-SA-15:10.openssl
1640 security advisory includes a change which rejects handshakes
1641 with DH parameters below 768 bits. sendmail releases prior
1642 to 8.15.2 (not yet released), defaulted to a 512 bit
1643 DH parameter setting for client connections. To work around
1644 this interoperability, sendmail can be configured to use a
1645 2048 bit DH parameter by:
1647 1. Edit /etc/mail/`hostname`.mc
1648 2. If a setting for confDH_PARAMETERS does not exist or
1649 exists and is set to a string beginning with '5',
1650 replace it with '2'.
1651 3. If a setting for confDH_PARAMETERS exists and is set to
1652 a file path, create a new file with:
1653 openssl dhparam -out /path/to/file 2048
1654 4. Rebuild the .cf file:
1655 cd /etc/mail/; make; make install
1656 5. Restart sendmail:
1657 cd /etc/mail/; make restart
1659 A sendmail patch is coming, at which time this file will be
1663 Generation of legacy formatted entries have been disabled by default
1664 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1665 entries were converted to use the new format by default when the new,
1666 machine independent format have been added and supported since FreeBSD
1669 Please see the pwd_mkdb(8) manual page for further details.
1672 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1673 20141231 entry below for information about prerequisites and upgrading,
1674 if you are not already using 3.5.0 or higher.
1677 TI platform code switched to using vendor DTS files and this update
1678 may break existing systems running on Beaglebone, Beaglebone Black,
1681 - dtb files should be regenerated/reinstalled. Filenames are the
1682 same but content is different now
1683 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1684 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1685 addressing scheme is now pin 25 on /dev/gpioc3.
1686 - Pandaboard: /etc/ttys should be updated, serial console device is
1687 now /dev/ttyu2, not /dev/ttyu0
1690 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1691 If you need the GNU extension from groff soelim(1), install groff
1692 from package: pkg install groff, or via ports: textproc/groff.
1695 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1696 defined in symlink(7); previously symlinks were silently ignored.
1699 The const qualifier has been removed from iconv(3) to comply with
1700 POSIX. The ports tree is aware of this from r384038 onwards.
1703 Libraries specified by LIBADD in Makefiles must have a corresponding
1704 DPADD_<lib> variable to ensure correct dependencies. This is now
1705 enforced in src.libnames.mk.
1708 From legacy ata(4) driver was removed support for SATA controllers
1709 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1710 Kernel modules ataahci and ataadaptec were removed completely,
1711 replaced by ahci and mvs modules respectively.
1714 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1715 the 20141231 entry below for information about prerequisites and
1716 upgrading, if you are not already using 3.5.0 or higher.
1719 The 32-bit PowerPC kernel has been changed to a position-independent
1720 executable. This can only be booted with a version of loader(8)
1721 newer than January 31, 2015, so make sure to update both world and
1722 kernel before rebooting.
1725 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1726 but before r278950, the RNG was not seeded properly. Immediately
1727 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1728 ssh keys or openssl keys) that were generated w/ a kernel from that
1729 range. This does not affect programs that directly used /dev/random
1730 or /dev/urandom. All userland uses of arc4random(3) are affected.
1733 The autofs(4) ABI was changed in order to restore binary compatibility
1734 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1735 with the new kernel.
1738 The powerpc64 kernel has been changed to a position-independent
1739 executable. This can only be booted with a new version of loader(8),
1740 so make sure to update both world and kernel before rebooting.
1743 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1744 only release, no new features have been added. Please see the 20141231
1745 entry below for information about prerequisites and upgrading, if you
1746 are not already using 3.5.0.
1749 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1750 taken from the ELF Tool Chain project rather than GNU binutils. They
1751 should be drop-in replacements, with the addition of arm64 support.
1752 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1753 binutils tools, if necessary. See 20150805 for updated information.
1756 The default Unbound configuration now enables remote control
1757 using a local socket. Users who have already enabled the
1758 local_unbound service should regenerate their configuration
1759 by running "service local_unbound setup" as root.
1762 The GNU texinfo and GNU info pages have been removed.
1763 To be able to view GNU info pages please install texinfo from ports.
1766 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1768 As of this release, a prerequisite for building clang, llvm and lldb is
1769 a C++11 capable compiler and C++11 standard library. This means that to
1770 be able to successfully build the cross-tools stage of buildworld, with
1771 clang as the bootstrap compiler, your system compiler or cross compiler
1772 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1773 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1776 On any standard FreeBSD 10.x or 11.x installation, where clang and
1777 libc++ are on by default (that is, on x86 or arm), this should work out
1780 On 9.x installations where clang is enabled by default, e.g. on x86 and
1781 powerpc, libc++ will not be enabled by default, so libc++ should be
1782 built (with clang) and installed first. If both clang and libc++ are
1783 missing, build clang first, then use it to build libc++.
1785 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1786 the instructions for 9.x above.
1788 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1789 default, and do not build clang.
1791 Many embedded systems are resource constrained, and will not be able to
1792 build clang in a reasonable time, or in some cases at all. In those
1793 cases, cross building bootable systems on amd64 is a workaround.
1795 This new version of clang introduces a number of new warnings, of which
1796 the following are most likely to appear:
1800 This warns in two cases, for both C and C++:
1801 * When the code is trying to take the absolute value of an unsigned
1802 quantity, which is effectively a no-op, and almost never what was
1803 intended. The code should be fixed, if at all possible. If you are
1804 sure that the unsigned quantity can be safely cast to signed, without
1805 loss of information or undefined behavior, you can add an explicit
1806 cast, or disable the warning.
1808 * When the code is trying to take an absolute value, but the called
1809 abs() variant is for the wrong type, which can lead to truncation.
1810 If you want to disable the warning instead of fixing the code, please
1811 make sure that truncation will not occur, or it might lead to unwanted
1814 -Wtautological-undefined-compare and
1815 -Wundefined-bool-conversion
1817 These warn when C++ code is trying to compare 'this' against NULL, while
1818 'this' should never be NULL in well-defined C++ code. However, there is
1819 some legacy (pre C++11) code out there, which actively abuses this
1820 feature, which was less strictly defined in previous C++ versions.
1822 Squid and openjdk do this, for example. The warning can be turned off
1823 for C++98 and earlier, but compiling the code in C++11 mode might result
1824 in unexpected behavior; for example, the parts of the program that are
1825 unreachable could be optimized away.
1828 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1829 kernel sources have been removed. The .h files remain, since some
1830 utilities include them. This will need to be fixed later.
1831 If "mount -t oldnfs ..." is attempted, it will fail.
1832 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1833 the utilities will report errors.
1836 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1837 directories to top level SUBDIR variable when their parent
1838 directory is included in LOCAL_DIRS. Users with build systems with
1839 such hierarchies and without SUBDIR entries in the parent
1840 directory Makefiles should add them or add the directories to
1844 faith(4) and faithd(8) have been removed from the base system. Faith
1845 has been obsolete for a very long time.
1848 vt(4), the new console driver, is enabled by default. It brings
1849 support for Unicode and double-width characters, as well as
1850 support for UEFI and integration with the KMS kernel video
1853 You may need to update your console settings in /etc/rc.conf,
1854 most probably the keymap. During boot, /etc/rc.d/syscons will
1855 indicate what you need to do.
1857 vt(4) still has issues and lacks some features compared to
1858 syscons(4). See the wiki for up-to-date information:
1859 https://wiki.freebsd.org/Newcons
1861 If you want to keep using syscons(4), you can do so by adding
1862 the following line to /boot/loader.conf:
1866 pjdfstest has been integrated into kyua as an opt-in test suite.
1867 Please see share/doc/pjdfstest/README for more details on how to
1871 gperf has been removed from the base system for architectures
1872 that use clang. Ports that require gperf will obtain it from the
1876 pjdfstest has been moved from tools/regression/pjdfstest to
1880 At svn r271982, The default linux compat kernel ABI has been adjusted
1881 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1882 update. If you wish to continue using the linux-f10 compat ports,
1883 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1884 encouraged to update their linux-compat packages to linux-c6 during
1885 their next update cycle.
1888 The ofwfb driver, used to provide a graphics console on PowerPC when
1889 using vt(4), no longer allows mmap() of all physical memory. This
1890 will prevent Xorg on PowerPC with some ATI graphics cards from
1891 initializing properly unless x11-servers/xorg-server is updated to
1895 The xdev targets have been converted to using TARGET and
1896 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1899 The default unbound configuration has been modified to address
1900 issues with reverse lookups on networks that use private
1901 address ranges. If you use the local_unbound service, run
1902 "service local_unbound setup" as root to regenerate your
1903 configuration, then "service local_unbound reload" to load the
1907 The GNU texinfo and GNU info pages are not built and installed
1908 anymore, WITH_INFO knob has been added to allow to built and install
1910 UPDATE: see 20150102 entry on texinfo's removal
1913 The GNU readline library is now an INTERNALLIB - that is, it is
1914 statically linked into consumers (GDB and variants) in the base
1915 system, and the shared library is no longer installed. The
1916 devel/readline port is available for third party software that
1920 The Itanium architecture (ia64) has been removed from the list of
1921 known architectures. This is the first step in the removal of the
1925 Commit r268115 has added NFSv4.1 server support, merged from
1926 projects/nfsv4.1-server. Since this includes changes to the
1927 internal interfaces between the NFS related modules, a full
1928 build of the kernel and modules will be necessary.
1929 __FreeBSD_version has been bumped.
1932 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1933 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1934 which differs from the behaviour controlled by this knob.)
1937 Maximal length of the serial number in CTL was increased from 16 to
1938 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1939 and ctld, need to be rebuilt to work with a new kernel.
1942 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1943 1 respectively to match the upstream numbers. They were out of
1944 sync because, when they were originally added to FreeBSD, the
1945 upstream versions were not respected. These libraries are private
1946 and not yet built by default, so renumbering them should be a
1947 non-issue. However, unclean source trees will yield broken test
1948 programs once the operator executes "make delete-old-libs" after a
1949 "make installworld".
1951 Additionally, the atf-sh binary was made private by moving it into
1952 /usr/libexec/. Already-built shell test programs will keep the
1953 path to the old binary so they will break after "make delete-old"
1956 If you are using WITH_TESTS=yes (not the default), wipe the object
1957 tree and rebuild from scratch to prevent spurious test failures.
1958 This is only needed once: the misnumbered libraries and misplaced
1959 binaries have been added to OptionalObsoleteFiles.inc so they will
1960 be removed during a clean upgrade.
1963 Clang and llvm have been upgraded to 3.4.1 release.
1966 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1967 be removed to avoid issues in the future (and has been added to
1971 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1972 past, it affected all builds that used the bsd.*.mk files. The old
1973 behavior was a bug, but people may have relied upon it. To get this
1974 behavior back, you can .include /etc/src.conf from /etc/make.conf
1975 (which is still global and isn't changed). This also changes the
1976 behavior of incremental builds inside the tree of individual
1977 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1978 Although this has survived make universe and some upgrade scenarios,
1979 other upgrade scenarios may have broken. At least one form of
1980 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1981 as well... In cases where MAKESYSPATH isn't working with this
1982 setting, you'll need to set it to the full path to your tree.
1984 One side effect of all this cleaning up is that bsd.compiler.mk
1985 is no longer implicitly included by bsd.own.mk. If you wish to
1986 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1990 The lindev device has been removed since /dev/full has been made a
1991 standard device. __FreeBSD_version has been bumped.
1994 The knob WITHOUT_VI was added to the base system, which controls
1995 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1996 in order to reorder files share/termcap and didn't build ex(1) as a
1997 build tool, so building/installing with WITH_VI is highly advised for
1998 build hosts for older releases.
2000 This issue has been fixed in stable/9 and stable/10 in r277022 and
2001 r276991, respectively.
2004 The YES_HESIOD knob has been removed. It has been obsolete for
2005 a decade. Please move to using WITH_HESIOD instead or your builds
2006 will silently lack HESIOD.
2009 The uart(4) driver has been changed with respect to its handling
2010 of the low-level console. Previously the uart(4) driver prevented
2011 any process from changing the baudrate or the CLOCAL and HUPCL
2012 control flags. By removing the restrictions, operators can make
2013 changes to the serial console port without having to reboot.
2014 However, when getty(8) is started on the serial device that is
2015 associated with the low-level console, a misconfigured terminal
2016 line in /etc/ttys will now have a real impact.
2017 Before upgrading the kernel, make sure that /etc/ttys has the
2018 serial console device configured as 3wire without baudrate to
2019 preserve the previous behaviour. E.g:
2020 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
2023 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
2024 to improve performance. To re-enable it, if needed, run rpcbind
2025 with command line option -W.
2028 Switched back to the GPL dtc compiler due to updates in the upstream
2029 dts files not being supported by the BSDL dtc compiler. You will need
2030 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
2031 may result while building dtb files during a kernel build if you fail
2032 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
2035 Clang and llvm have been upgraded to 3.4 release.
2038 The nve(4) driver has been removed. Please use the nfe(4) driver
2039 for NVIDIA nForce MCP Ethernet adapters instead.
2042 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
2043 This could cause certain C++ applications using shared libraries built
2044 against the previous version of libc++ to crash. The incompatibility
2045 has now been fixed, but any C++ applications or shared libraries built
2046 between r261283 and r261801 should be recompiled.
2049 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
2050 capability mode support. Please note that enabling the feature in
2051 kernel is still highly recommended.
2054 OpenSSH is now built with sandbox support, and will use sandbox as
2055 the default privilege separation method. This requires Capsicum
2056 capability mode support in kernel.
2059 The libelf and libdwarf libraries have been updated to newer
2060 versions from upstream. Shared library version numbers for
2061 these two libraries were bumped. Any ports or binaries
2062 requiring these two libraries should be recompiled.
2063 __FreeBSD_version is bumped to 1100006.
2066 If a Makefile in a tests/ directory was auto-generating a Kyuafile
2067 instead of providing an explicit one, this would prevent such
2068 Makefile from providing its own Kyuafile in the future during
2069 NO_CLEAN builds. This has been fixed in the Makefiles but manual
2070 intervention is needed to clean an objdir if you use NO_CLEAN:
2071 # find /usr/obj -name Kyuafile | xargs rm -f
2074 The behavior of gss_pseudo_random() for the krb5 mechanism
2075 has changed, for applications requesting a longer random string
2076 than produced by the underlying enctype's pseudo-random() function.
2077 In particular, the random string produced from a session key of
2078 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
2079 be different at the 17th octet and later, after this change.
2080 The counter used in the PRF+ construction is now encoded as a
2081 big-endian integer in accordance with RFC 4402.
2082 __FreeBSD_version is bumped to 1100004.
2085 The WITHOUT_ATF build knob has been removed and its functionality
2086 has been subsumed into the more generic WITHOUT_TESTS. If you were
2087 using the former to disable the build of the ATF libraries, you
2088 should change your settings to use the latter.
2091 The default version of mtree is nmtree which is obtained from
2092 NetBSD. The output is generally the same, but may vary
2093 slightly. If you found you need identical output adding
2094 "-F freebsd9" to the command line should do the trick. For the
2095 time being, the old mtree is available as fmtree.
2098 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
2099 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
2100 1.1.4_8 and verify bsdyml not linked in, before running "make
2102 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
2104 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
2107 The stable/10 branch has been created in subversion from head
2114 Sometimes, obscure build problems are the result of environment
2115 poisoning. This can happen because the make utility reads its
2116 environment when searching for values for global variables. To run
2117 your build attempts in an "environmental clean room", prefix all make
2118 commands with 'env -i '. See the env(1) manual page for more details.
2119 Occasionally a build failure will occur with "make -j" due to a race
2120 condition. If this happens try building again without -j, and please
2121 report a bug if it happens consistently.
2123 When upgrading from one major version to another it is generally best to
2124 upgrade to the latest code in the currently installed branch first, then
2125 do an upgrade to the new branch. This is the best-tested upgrade path,
2126 and has the highest probability of being successful. Please try this
2127 approach if you encounter problems with a major version upgrade. Since
2128 the stable 4.x branch point, one has generally been able to upgrade from
2129 anywhere in the most recent stable branch to head / current (or even the
2130 last couple of stable branches). See the top of this file when there's
2133 The update process will emit an error on an attempt to perform a build
2134 or install from a FreeBSD version below the earliest supported version.
2135 When updating from an older version the update should be performed one
2136 major release at a time, including running `make delete-old` at each
2139 When upgrading a live system, having a root shell around before
2140 installing anything can help undo problems. Not having a root shell
2141 around can lead to problems if pam has changed too much from your
2142 starting point to allow continued authentication after the upgrade.
2144 This file should be read as a log of events. When a later event changes
2145 information of a prior event, the prior event should not be deleted.
2146 Instead, a pointer to the entry with the new information should be
2147 placed in the old entry. Readers of this file should also sanity check
2148 older entries before relying on them blindly. Authors of new entries
2149 should write them with this in mind.
2153 When upgrading the boot ZFS pool to a new version, always follow
2156 1.) recompile and reinstall the ZFS boot loader and boot block
2157 (this is part of "make buildworld" and "make installworld")
2159 2.) update the ZFS boot block on your boot drive
2161 The following example updates the ZFS boot block on the first
2162 partition (freebsd-boot) of a GPT partitioned drive ada0:
2163 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
2165 Non-boot pools do not need these updates.
2169 If you are updating from a prior version of FreeBSD (even one just
2170 a few days old), you should follow this procedure. It is the most
2171 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2173 make kernel-toolchain
2174 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2175 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2177 To test a kernel once
2178 ---------------------
2179 If you just want to boot a kernel once (because you are not sure
2180 if it works, or if you want to boot a known bad kernel to provide
2181 debugging information) run
2182 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2183 nextboot -k testkernel
2185 To rebuild everything and install it on the current system.
2186 -----------------------------------------------------------
2187 # Note: sometimes if you are running current you gotta do more than
2188 # is listed here if you are upgrading from a really old current.
2190 <make sure you have good level 0 dumps>
2192 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2193 make installkernel KERNCONF=YOUR_KERNEL_HERE
2195 <reboot in single user> [3]
2202 To cross-install current onto a separate partition
2203 --------------------------------------------------
2204 # In this approach we use a separate partition to hold
2205 # current's root, 'usr', and 'var' directories. A partition
2206 # holding "/", "/usr" and "/var" should be about 2GB in
2209 <make sure you have good level 0 dumps>
2212 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2213 <maybe newfs current's root partition>
2214 <mount current's root partition on directory ${CURRENT_ROOT}>
2215 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
2216 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2217 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2218 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2219 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2220 <reboot into current>
2221 <do a "native" rebuild/install as described in the previous section>
2222 <maybe install compatibility libraries from ports/misc/compat*>
2226 To upgrade in-place from stable to current
2227 ----------------------------------------------
2228 <make sure you have good level 0 dumps>
2230 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
2231 make installkernel KERNCONF=YOUR_KERNEL_HERE
2233 <reboot in single user> [3]
2240 Make sure that you've read the UPDATING file to understand the
2241 tweaks to various things you need. At this point in the life
2242 cycle of current, things change often and you are on your own
2243 to cope. The defaults can also change, so please read ALL of
2244 the UPDATING entries.
2246 Also, if you are tracking -current, you must be subscribed to
2247 freebsd-current@freebsd.org. Make sure that before you update
2248 your sources that you have read and understood all the recent
2249 messages there. If in doubt, please track -stable which has
2250 much fewer pitfalls.
2252 [1] If you have third party modules, such as vmware, you
2253 should disable them at this point so they don't crash your
2256 [3] From the bootblocks, boot -s, and then do
2260 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed
2261 cd src # full path to source
2262 adjkerntz -i # if CMOS is wall time
2263 Also, when doing a major release upgrade, it is required that
2264 you boot into single user mode to do the installworld.
2266 [4] Note: This step is non-optional. Failure to do this step
2267 can result in a significant reduction in the functionality of the
2268 system. Attempting to do it by hand is not recommended and those
2269 that pursue this avenue should read this file carefully, as well
2270 as the archives of freebsd-current and freebsd-hackers mailing lists
2271 for potential gotchas. The -U option is also useful to consider.
2272 See mergemaster(8) for more information.
2274 [5] Usually this step is a no-op. However, from time to time
2275 you may need to do this if you get unknown user in the following
2276 step. It never hurts to do it all the time. You may need to
2277 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2278 install) after the buildworld before this step if you last updated
2279 from current before 20130425 or from -stable before 20130430.
2281 [6] This only deletes old files and directories. Old libraries
2282 can be deleted by "make delete-old-libs", but you have to make
2283 sure that no program is using those libraries anymore.
2285 [8] The new kernel must be able to run existing binaries used by an
2286 installworld. When upgrading across major versions, the new kernel's
2287 configuration must include the correct COMPAT_FREEBSD<n> option for
2288 existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure
2289 to do so may leave you with a system that is hard to boot to recover. A
2290 GENERIC kernel will include suitable compatibility options to run
2291 binaries from older branches. Note that the ability to run binaries
2292 from unsupported branches is not guaranteed.
2294 Make sure that you merge any new devices from GENERIC since the
2295 last time you updated your kernel config file. Options also
2296 change over time, so you may need to adjust your custom kernels
2299 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2300 "?=" instead of the "=" assignment operator, so that buildworld can
2301 override the CPUTYPE if it needs to.
2303 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2304 not on the command line, or in /etc/make.conf. buildworld will
2305 warn if it is improperly defined.
2308 This file contains a list, in reverse chronological order, of major
2309 breakages in tracking -current. It is not guaranteed to be a complete
2310 list of such breakages, and only contains entries since September 23, 2011.
2311 If you need to see UPDATING entries from before that date, you will need
2312 to fetch an UPDATING file from an older FreeBSD release.
2314 Copyright information:
2316 Copyright 1998-2009 M. Warner Losh <imp@FreeBSD.org>
2318 Redistribution, publication, translation and use, with or without
2319 modification, in full or in part, in any form or format of this
2320 document are permitted without further permission from the author.
2322 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2323 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2324 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2325 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2326 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2327 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2328 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2329 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2330 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2331 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2332 POSSIBILITY OF SUCH DAMAGE.
2334 Contact Warner Losh if you have any questions about your use of