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 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
31 been upgraded to 10.0.1. Please see the 20141231 entry below for
32 information about prerequisites and upgrading, if you are not already
33 using clang 3.5.0 or higher.
36 Support for obsolete compilers has been removed from the build system.
37 Clang 6 and GCC 6.4 are the minimum supported versions.
40 closefrom(2) has been moved under COMPAT12, and replaced in libc with a
41 stub that calls close_range(2). If using a custom kernel configuration,
42 you may want to ensure that the COMPAT_FREEBSD12 option is included, as
43 a slightly older -CURRENT userland and older FreeBSD userlands may not
44 be functional without closefrom(2).
47 Upstream DTS from Linux 5.6 was merged and they now have the SID
48 and THS (Secure ID controller and THermal Sensor) node present.
49 The DTB overlays have now been removed from the tree for the H3/H5 and
50 A64 SoCs and the aw_sid and aw_thermal driver have been updated to
51 deal with upstream DTS. If you are using those overlays you need to
52 remove them from loader.conf and update the DTBs on the FAT partition.
55 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
56 been upgraded to 10.0.0. Please see the 20141231 entry below for
57 information about prerequisites and upgrading, if you are not already
58 using clang 3.5.0 or higher.
61 The amd(8) automount daemon has been removed from the source tree.
62 As of FreeBSD 10.1 autofs(5) is the preferred tool for automounting.
63 amd is still available in the sysutils/am-utils port.
66 Removed brooktree driver (bktr.4) from the tree.
69 The WITH_GPL_DTC option has been removed. The BSD-licenced device tree
70 compiler in usr.bin/dtc is used on all architectures which use dtc, and
71 the GPL dtc is available (if needed) from the sysutils/dtc port.
74 The WITHOUT_LLVM_LIBUNWIND option has been removed. LLVM's libunwind
75 is used by all supported CPU architectures.
78 GCC 4.2.1 has been removed from the tree. The WITH_GCC,
79 WITH_GCC_BOOTSTRAP, and WITH_GNUCXX options are no longer available.
80 Users who wish to build FreeBSD with GCC must use the external toolchain
84 ncurses has been updated to a newer version (6.2-20200215). Given the ABI
85 has changed, users will have to rebuild all the ports that are linked to
89 The size of struct vnet and the magic cookie have changed.
90 Users need to recompile libkvm and all modules using VIMAGE
91 together with their new kernel.
94 Defining the long deprecated NO_CTF, NO_DEBUG_FILES, NO_INSTALLLIB,
95 NO_MAN, NO_PROFILE, and NO_WARNS variables is now an error. Update
96 your Makefiles and scripts to define MK_<var>=no instead as required.
98 One exception to this is that program or library Makefiles should
99 define MAN to empty rather than setting MK_MAN=no.
102 Clang/LLVM is now the default compiler and LLD the default
106 make universe no longer uses GCC 4.2.1 on any architectures.
107 Architectures not supported by in-tree Clang/LLVM require an
108 external toolchain package.
111 GCC 4.2.1 is now not built by default, as part of the GCC 4.2.1
112 retirement plan. Specifically, the GCC, GCC_BOOTSTRAP, and GNUCXX
113 options default to off for all supported CPU architectures. As a
114 short-term transition aid they may be enabled via WITH_* options.
115 GCC 4.2.1 is expected to be removed from the tree on 2020-03-31.
118 Support for armv5 has been disconnected and is being removed. The
119 machine combination MACHINE=arm MACHINE_ARCH=arm is no longer valid.
120 You must now use a MACHINE_ARCH of armv6 or armv7. The default
121 MACHINE_ARCH for MACHINE=arm is now armv7.
124 Clang/LLVM is now the default compiler for all powerpc architectures.
125 LLD is now the default linker for powerpc64. The change for powerpc64
126 also includes a change to the ELFv2 ABI, incompatible with the existing
130 Kernel-loadable random(4) modules are no longer unloadable.
133 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
134 been upgraded to 9.0.1. Please see the 20141231 entry below for
135 information about prerequisites and upgrading, if you are not already
136 using clang 3.5.0 or higher.
139 r355677 has modified the internal interface used between the
140 NFS modules in the kernel. As such, they must all be upgraded
141 simultaneously. I will do a version bump for this.
144 The root certificates of the Mozilla CA Certificate Store have been
145 imported into the base system and can be managed with the certctl(8)
146 utility. If you have installed the security/ca_root_nss port or package
147 with the ETCSYMLINK option (the default), be advised that there may be
148 differences between those included in the port and those included in
149 base due to differences in nss branch used as well as general update
150 frequency. Note also that certctl(8) cannot manage certs in the
151 format used by the security/ca_root_nss port.
154 The amd(8) automount daemon has been disabled by default, and will be
155 removed in the future. As of FreeBSD 10.1 the autofs(5) is available
159 The nctgpio and wbwd drivers have been moved to the superio bus.
160 If you have one of these drivers in a kernel configuration, then
161 you should add device superio to it. If you use one of these drivers
162 as a module and you compile a custom set of modules, then you should
163 add superio to the set.
166 KPIs for network drivers to access interface addresses have changed.
167 Users need to recompile NIC driver modules together with kernel.
170 The net.link.tap.user_open sysctl no longer prevents user opening of
171 already created /dev/tapNN devices. Access is still controlled by
172 node permissions, just like tun devices. The net.link.tap.user_open
173 sysctl is now used only to allow users to perform devfs cloning of
174 tap devices, and the subsequent open may not succeed if the user is not
175 in the appropriate group. This sysctl may be deprecated/removed
176 completely in the future.
179 mips, powerpc, and sparc64 are no longer built as part of
180 universe / tinderbox unless MAKE_OBSOLETE_GCC is defined. If
181 not defined, mips, powerpc, and sparc64 builds will look for
182 the xtoolchain binaries and if installed use them for universe
183 builds. As llvm 9.0 becomes vetted for these architectures, they
184 will be removed from the list.
187 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
188 been upgraded to 9.0.0. Please see the 20141231 entry below for
189 information about prerequisites and upgrading, if you are not already
190 using clang 3.5.0 or higher.
193 The hpt27xx, hptmv, hptnr, and hptrr drivers have been removed from
194 GENERIC. They are available as modules and can be loaded by adding
195 to /boot/loader.conf hpt27xx_load="YES", hptmv_load="YES",
196 hptnr_load="YES", or hptrr_load="YES", respectively.
199 ntpd no longer by default locks its pages in memory, allowing them
200 to be paged out by the kernel. Use rlimit memlock to restore
201 historic BSD behaviour. For example, add "rlimit memlock 32"
202 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
205 Several of ping6's options have been renamed for better consistency
206 with ping. If you use any of -ARWXaghmrtwx, you must update your
207 scripts. See ping6(8) for details.
210 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
211 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
212 been removed from mount_fusefs(8). You can safely remove them from
213 your scripts, because they had no effect.
215 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
216 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
217 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
218 sysctls have been removed. If you felt the need to set any of them to
219 a non-default value, please tell asomers@FreeBSD.org why.
222 Default permissions on the /var/account/acct file (and copies of it
223 rotated by periodic daily scripts) are changed from 0644 to 0640
224 because the file contains sensitive information that should not be
225 world-readable. If the /var/account directory must be created by
226 rc.d/accounting, the mode used is now 0750. Admins who use the
227 accounting feature are encouraged to change the mode of an existing
228 /var/account directory to 0750 or 0700.
231 Entropy collection and the /dev/random device are no longer optional
232 components. The "device random" option has been removed.
233 Implementations of distilling algorithms can still be made loadable
234 with "options RANDOM_LOADABLE" (e.g., random_fortuna.ko).
237 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
238 been upgraded to 8.0.1. Please see the 20141231 entry below for
239 information about prerequisites and upgrading, if you are not already
240 using clang 3.5.0 or higher.
243 A fix was applied to i386 kernel modules to avoid panics with
244 dpcpu or vnet. Users need to recompile i386 kernel modules
245 having pcpu or vnet sections or they will refuse to load.
248 User-wired pages now have their own counter,
249 vm.stats.vm.v_user_wire_count. The vm.max_wired sysctl was renamed
250 to vm.max_user_wired and changed from an unsigned int to an unsigned
251 long. bhyve VMs wired with the -S are now subject to the user
252 wiring limit; the vm.max_user_wired sysctl may need to be tuned to
253 avoid running into the limit.
256 The IPSEC option has been removed from GENERIC. Users requiring
257 ipsec(4) must now load the ipsec(4) kernel module.
260 The tap(4) driver has been folded into tun(4), and the module has been
261 renamed to tuntap. You should update any kld_list="if_tap" or
262 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
263 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
264 module instead, and "device tap" or "device tun" entries in kernel
265 config files to select the tuntap device instead.
268 The following knobs have been added related to tradeoffs between
269 safe use of the random device and availability in the absence of
272 kern.random.initial_seeding.bypass_before_seeding: tunable; set
273 non-zero to bypass the random device prior to seeding, or zero to
274 block random requests until the random device is initially seeded.
275 For now, set to 1 (unsafe) by default to restore pre-r346250 boot
276 availability properties.
278 kern.random.initial_seeding.read_random_bypassed_before_seeding:
279 read-only diagnostic sysctl that is set when bypass is enabled and
280 read_random(9) is bypassed, to enable programmatic handling of this
281 initial condition, if desired.
283 kern.random.initial_seeding.arc4random_bypassed_before_seeding:
284 Similar to the above, but for for arc4random(9) initial seeding.
286 kern.random.initial_seeding.disable_bypass_warnings: tunable; set
287 non-zero to disable warnings in dmesg when the same conditions are
288 met as for the diagnostic sysctls above. Defaults to zero, i.e.,
289 produce warnings in dmesg when the conditions are met.
292 The loadable random module KPI has changed; the random_infra_init()
293 routine now requires a 3rd function pointer for a bool (*)(void)
294 method that returns true if the random device is seeded (and
295 therefore unblocked).
298 r345895 reverts r320698. This implies that an nfsuserd(8) daemon
299 built from head sources between r320757 (July 6, 2017) and
300 r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
301 is added to the command line.
302 nfsuserd daemons built from head sources that are post-r338192 are
303 not affected and should continue to work.
306 The fuse(4) module has been renamed to fusefs(4) for consistency with
307 other filesystems. You should update any kld_load="fuse" entries in
308 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
309 "options FUSE" entries in kernel config files.
312 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
313 8.0.0. Please see the 20141231 entry below for information about
314 prerequisites and upgrading, if you are not already using clang 3.5.0
318 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
319 compiled into your custom kernel, add 'device xz' statement to the
323 drm and drm2 have been removed from the tree. Please see
324 https://wiki.freebsd.org/Graphics for the latest information on
325 migrating to the drm ports.
328 Iflib is no longer unconditionally compiled into the kernel. Drivers
329 using iflib and statically compiled into the kernel, now require
330 the 'device iflib' config option. For the same drivers loaded as
331 modules on kernels not having 'device iflib', the iflib.ko module
332 is loaded automatically.
335 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
336 options no longer exist since r343219 and r343427 respectively;
337 nothing uses them, so they should be just removed from custom
341 r342635 changes the way efibootmgr(8) works by requiring users to add
342 the -b (bootnum) parameter for commands where the bootnum was previously
343 specified with each option. For example 'efibootmgr -B 0001' is now
344 'efibootmgr -B -b 0001'.
347 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
348 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
349 servers that have vfs.nfsd.nfs_privport set will only allow mounts
350 from clients using a reserved port#. Since both the FreeBSD and Linux
351 NFSv4 clients use reserved port#s by default, this should not affect
355 The XLP config has been removed. We can't support 64-bit atomics in this
356 kernel because it is running in 32-bit mode. XLP users must transition
357 to running a 64-bit kernel (XLP64 or XLPN32).
359 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
360 the preferred emulator today and we don't need two different ones.
362 The old sibyte / swarm / Broadcom BCM1250 support has been
363 removed from the mips port.
366 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
367 7.0.1. Please see the 20141231 entry below for information about
368 prerequisites and upgrading, if you are not already using clang 3.5.0
372 Remove the timed and netdate programs from the base tree. Setting
373 the time with these daemons has been obsolete for over a decade.
376 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
377 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
378 it produces broken binaries when ifuncs are in use. Users needing
379 GNU ld should install the binutils port or package.
382 The BSD crtbegin and crtend code has been enabled by default. It has
383 had extensive testing on amd64, arm64, and i386. It can be disabled
384 by building a world with -DWITHOUT_BSD_CRTBEGIN.
387 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
388 has been converted to a port (misc/ctm) and will be removed from
389 FreeBSD-13. It is available as a package (ctm) for all supported
393 The default newsyslog.conf(5) file has been changed to only include
394 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
395 the filenames end in '.conf' and do not begin with a '.'.
397 You should check the configuration files in these two directories match
398 this naming convention. You can verify which configuration files are
399 being included using the command:
403 Ports for the DRM modules have been simplified. Now, amd64 users should
404 just install the drm-kmod port. All others should install
407 Graphics hardware that's newer than about 2010 usually works with
408 drm-kmod. For hardware older than 2013, however, some users will need
409 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
410 than 2008 usually only works in drm-legacy-kmod. The graphics team can
411 only commit to hardware made since 2013 due to the complexity of the
412 market and difficulty to test all the older cards effectively. If you
413 have hardware supported by drm-kmod, you are strongly encouraged to use
414 that as you will get better support.
416 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
417 elsewhere, the drm and drm2 modules will be eliminated from the src base
418 soon (with a limited exception for arm). Please update to the package
419 asap and report any issues to x11@freebsd.org.
421 Generally, anybody using the drm*-kmod packages should add
422 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
423 cross-threading surprises, especially with automatic driver
424 loading from X11 startup. These will become the defaults in 13-current
428 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
429 custom kernel and module loading configuration files must be updated
430 accordingly. Moreover, interfaces previous presented as ixlvN to the
431 system are now exposed as iavfN and network configuration files must
432 be adjusted as necessary.
435 OpenSSL has been updated to version 1.1.1. This update included
436 additional various API changes throughout the base system. It is
437 important to rebuild third-party software after upgrading. The value
438 of __FreeBSD_version has been bumped accordingly.
441 The legacy DRM modules and drivers have now been added to the loader's
442 module blacklist, in favor of loading them with kld_list in rc.conf(5).
443 The module blacklist may be overridden with the loader.conf(5)
444 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
448 The cam(4) based nda(4) driver will be used over nvd(4) by default on
449 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
450 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
451 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
455 Reproducible build mode is now on by default, in preparation for
456 FreeBSD 12.0. This eliminates build metadata such as the user,
457 host, and time from the kernel (and uname), unless the working tree
458 corresponds to a modified checkout from a version control system.
459 The previous behavior can be obtained by setting the /etc/src.conf
460 knob WITHOUT_REPRODUCIBLE_BUILD.
463 The Yarrow CSPRNG has been removed from the kernel as it has not been
464 supported by its designers since at least 2003. Fortuna has been the
465 default since FreeBSD-11.
468 devctl freeze/thaw have gone into the tree, the rc scripts have been
469 updated to use them and devmatch has been changed. You should update
470 kernel, userland and rc scripts all at the same time.
473 The default interpreter has been switched from 4th to Lua.
474 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
475 interpreter. If you have custom FORTH code you will need to set
476 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
477 src.conf for the build. This will create default hard links between
478 loader and loader_4th instead of loader and loader_lua, the new default.
479 If you are using UEFI it will create the proper hard link to loader.efi.
481 bhyve uses userboot.so. It remains 4th-only until some issues are solved
482 regarding coexisting with multiple versions of FreeBSD are resolved.
485 ls(1) now respects the COLORTERM environment variable used in other
486 systems and software to indicate that a colored terminal is both
487 supported and desired. If ls(1) is suddenly emitting colors, they may
488 be disabled again by either removing the unwanted COLORTERM from your
489 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
490 may not be observed in a future release.
493 The default pager for most commands has been changed to "less". To
494 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
498 The jedec_ts(4) driver has been removed. A superset of its functionality
499 is available in the jedec_dimm(4) driver, and the manpage for that
500 driver includes migration instructions. If you have "device jedec_ts"
501 in your kernel configuration file, it must be removed.
504 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
505 This should have no effect if the kernel is booted via BIOS/legacy boot.
506 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
507 has a buggy firmware that prevents a successful boot due to use of
511 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
512 support has been removed from the tree. These ports were
513 obsolete and/or known to be broken for many years.
516 loader.efi has been augmented to participate more fully in the
517 UEFI boot manager protocol. loader.efi will now look at the
518 BootXXXX environment variable to determine if a specific kernel
519 or root partition was specified. XXXX is derived from BootCurrent.
520 efibootmgr(8) manages these standard UEFI variables.
523 zfsloader's functionality has now been folded into loader.
524 zfsloader is no longer necessary once you've updated your
525 boot blocks. For a transition period, we will install a
526 hardlink for zfsloader to loader to allow a smooth transition
527 until the boot blocks can be updated (hard link because old
528 zfs boot blocks don't understand symlinks).
531 ARM64 now have efifb support, if you want to have serial console
532 on your arm64 board when an screen is connected and the bootloader
533 setup a frame buffer for us to use, just add :
537 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
538 an screen connected as the firmware will setup a frame buffer are that
539 u-boot will expose as an EFI frame buffer.
542 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
543 or take steps to update /etc/passwd before doing installworld on
544 existing systems. Do not skip the "mergemaster -Fp" step before
545 installworld, as described in the update procedures near the bottom
546 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
547 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
548 the ntp config file contain options that change file/dir locations.
549 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
550 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
551 taking steps to ensure that all required files/dirs are accessible
555 Big endian arm support has been removed.
558 The static environment setup in kernel configs is no longer mutually
559 exclusive with the loader(8) environment by default. In order to
560 restore the previous default behavior of disabling the loader(8)
561 environment if a static environment is present, you must specify
562 loader_env.disabled=1 in the static environment.
565 The ABI of syscalls used by management tools like sockstat and
566 netstat has been broken to allow 32-bit binaries to work on
567 64-bit kernels without modification. These programs will need
568 to match the kernel in order to function. External programs may
569 require minor modifications to accommodate a change of type in
570 structures from pointers to 64-bit virtual addresses.
573 On i386 and amd64 atomics are now inlined. Out of tree modules using
574 atomics will need to be rebuilt.
577 The '%I' format in the kern.corefile sysctl limits the number of
578 core files that a process can generate to the number stored in the
579 debug.ncores sysctl. The '%I' format is replaced by the single digit
580 index. Previously, if all indexes were taken the kernel would overwrite
581 only a core file with the highest index in a filename.
582 Currently the system will create a new core file if there is a free
583 index or if all slots are taken it will overwrite the oldest one.
586 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
587 6.0.1. Please see the 20141231 entry below for information about
588 prerequisites and upgrading, if you are not already using clang 3.5.0
592 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
593 needed to be changed to work with it. This change was made with r335763
594 and requires a mergemaster / etcupdate / etc to update the installed
598 r334930 changed the interface between the NFS modules, so they all
599 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
602 As of r334391 lld is the default amd64 system linker; it is installed
603 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
607 The kernel / userland interface for devinfo changed, so you'll
608 need a new kernel and userland as a pair for it to work (rebuilding
609 lib/libdevinfo is all that's required). devinfo and devmatch will
610 not work, but everything else will when there's a mismatch.
613 The on-disk format for hwpmc callchain records has changed to include
614 threadid corresponding to a given record. This changes the field offsets
615 and thus requires that libpmcstat be rebuilt before using a kernel
619 The vxge(4) driver has been removed. This driver was introduced into
620 HEAD one week before the Exar left the Ethernet market and is not
621 known to be used. If you have device vxge in your kernel config file
625 The amd64 kernel now requires a ld that supports ifunc to produce a
626 working kernel, either lld or a newer binutils. lld is built by default
627 on amd64, and the 'buildkernel' target uses it automatically. However,
628 it is not the default linker, so building the kernel the traditional
629 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
630 binutils port/package). lld will soon be default, and this requirement
633 NOTE: As of r334391 lld is the default system linker on amd64, and no
634 workaround is necessary.
637 The nxge(4) driver has been removed. This driver was for PCI-X 10g
638 cards made by s2io/Neterion. The company was acquired by Exar and
639 no longer sells or supports Ethernet products. If you have device
640 nxge in your kernel config file it must be removed.
643 The tz database (tzdb) has been updated to 2018e. This version more
644 correctly models time stamps in time zones with negative DST such as
645 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
646 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
647 time zone abbreviations and the tm_isdst flag.
650 The ixgb(4) driver has been removed. This driver was for an early and
651 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
652 quickly shifted to the long lived ixgbe family. If you have device
653 ixgb in your kernel config file it must be removed.
656 The lmc(4) driver has been removed. This was a WAN interface
657 card that was already reportedly rare in 2003, and had an ambiguous
658 license. If you have device lmc in your kernel config file it must
662 Support for Arcnet networks has been removed. If you have device
663 arcnet or device cm in your kernel config file they must be
667 Support for FDDI networks has been removed. If you have device
668 fddi or device fpa in your kernel config file they must be
672 In addition to supporting RFC 3164 formatted messages, the
673 syslogd(8) service is now capable of parsing RFC 5424 formatted
674 log messages. The main benefit of using RFC 5424 is that clients
675 may now send log messages with timestamps containing year numbers,
676 microseconds and time zone offsets.
678 Similarly, the syslog(3) C library function has been altered to
679 send RFC 5424 formatted messages to the local system logging
680 daemon. On systems using syslogd(8), this change should have no
681 negative impact, as long as syslogd(8) and the C library are
682 updated at the same time. On systems using a different system
683 logging daemon, it may be necessary to make configuration
684 adjustments, depending on the software used.
686 When using syslog-ng, add the 'syslog-protocol' flag to local
687 input sources to enable parsing of RFC 5424 formatted messages:
690 unix-dgram("/var/run/log" flags(syslog-protocol));
693 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
694 of the 'imuxsock' module to let messages be processed by the
695 regular RFC 3164/5424 parsing pipeline:
697 module(load="imuxsock" SysSock.UseSpecialParser="off")
699 Do note that these changes only affect communication between local
700 applications and syslogd(8). The format that syslogd(8) uses to
701 store messages on disk or forward messages to other systems
702 remains unchanged. syslogd(8) still uses RFC 3164 for these
703 purposes. Options to customize this behaviour will be added in the
704 future. Utilities that process log files stored in /var/log are
705 thus expected to continue to function as before.
707 __FreeBSD_version has been incremented to 1200061 to denote this
711 Support for token ring networks has been removed. If you
712 have "device token" in your kernel config you should remove
713 it. No device drivers supported token ring.
716 makefs was modified to be able to tag ISO9660 El Torito boot catalog
717 entries as EFI instead of overloading the i386 tag as done previously.
718 The amd64 mkisoimages.sh script used to build amd64 ISO images for
719 release was updated to use this. This may mean that makefs must be
720 updated before "make cdrom" can be run in the release directory. This
721 should be as simple as:
723 $ cd $SRCDIR/usr.sbin/makefs
724 $ make depend all install
727 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
728 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
729 Co-existence for the transition period will come shortly. Booting is a
730 complex environment and test coverage for Lua-enabled loaders has been
731 thin, so it would be prudent to assume it might not work and make
732 provisions for backup boot methods.
735 devmatch functionality has been turned on in devd. It will automatically
736 load drivers for unattached devices. This may cause unexpected drivers
737 to be loaded. Please report any problems to current@ and
741 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
742 6.0.0. Please see the 20141231 entry below for information about
743 prerequisites and upgrading, if you are not already using clang 3.5.0
747 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
748 This means it is used to link the kernel and userland libraries and
749 executables, but is not yet installed as /usr/bin/ld by default.
751 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
752 WITHOUT_LLD_BOOTSTRAP=yes
755 On i386, pmtimer has been removed. Its functionality has been folded
756 into apm. It was a no-op on ACPI in current for a while now (but was
757 still needed on i386 in FreeBSD 11 and earlier). Users may need to
758 remove it from kernel config files.
761 The use of RSS hash from the network card aka flowid has been
762 disabled by default for lagg(4) as it's currently incompatible with
763 the lacp and loadbalance protocols.
765 This can be re-enabled by setting the following in loader.conf:
766 net.link.lagg.default_use_flowid="1"
769 The SW_WATCHDOG option is no longer necessary to enable the
770 hardclock-based software watchdog if no hardware watchdog is
771 configured. As before, SW_WATCHDOG will cause the software
772 watchdog to be enabled even if a hardware watchdog is configured.
775 r326887 fixes the issue described in the 20171214 UPDATING entry.
776 r326888 flips the switch back to building GELI support always.
779 r362593 broke ZFS + GELI support for reasons unknown. However,
780 it also broke ZFS support generally, so GELI has been turned off
781 by default as the lesser evil in r326857. If you boot off ZFS and/or
782 GELI, it might not be a good time to update.
785 PowerPC users must update loader(8) by rebuilding world before
786 installing a new kernel, as the protocol connecting them has
787 changed. Without the update, loader metadata will not be passed
788 successfully to the kernel and users will have to enter their
789 root partition at the kernel mountroot prompt to continue booting.
790 Newer versions of loader can boot old kernels without issue.
793 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
794 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
795 to WITH/OUT_LOADER_GELI.
798 The naive and non-compliant support of posix_fallocate(2) in ZFS
799 has been removed as of r325320. The system call now returns EINVAL
800 when used on a ZFS file. Although the new behavior complies with the
801 standard, some consumers are not prepared to cope with it.
802 One known victim is lld prior to r325420.
805 Building in a FreeBSD src checkout will automatically create object
806 directories now rather than store files in the current directory if
807 'make obj' was not ran. Calling 'make obj' is no longer necessary.
808 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
809 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
813 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
814 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
815 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
816 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
817 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
818 The UNIFIED_OBJDIR option is a transitional feature that will be
819 removed for 12.0 release; please migrate to the new format for any
820 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
821 than hardcoding paths.
824 The native-xtools target no longer installs the files by default to the
825 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
826 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
829 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
830 options are changing from controlling the build if defined / undefined
831 to controlling the build with explicit 'yes' or 'no' values. They will
832 shift to WITH/WITHOUT options to match other options in the system.
835 libstand has turned into a private library for sys/boot use only.
836 It is no longer supported as a public interface outside of sys/boot.
839 The arm port has split armv6 into armv6 and armv7. armv7 is now
840 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
841 and are running a kernel from before r324363, you will need to add
842 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
845 When building multiple kernels using KERNCONF, non-existent KERNCONF
846 files will produce an error and buildkernel will fail. Previously
847 missing KERNCONF files silently failed giving no indication as to
848 why, only to subsequently discover during installkernel that the
849 desired kernel was never built in the first place.
852 The default serial number format for CTL LUNs has changed. This will
853 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
854 or iSCSI clients care about their LUNs' serial numbers. Users who
855 require serial number stability should hardcode serial numbers in
859 For 32-bit arm compiled for hard-float support, soft-floating point
860 binaries now always get their shared libraries from
861 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
862 /usr/libsoft also existed). Only users with a hard-float ld.so, but
863 soft-float everything else should be affected.
866 The geli password typed at boot is now hidden. To restore the previous
867 behavior, see geli(8) for configuration options.
870 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
871 sysctl values. Minor nit, but requires a rebuild of both world/kernel
875 "make check" behavior (made in ^/head@r295380) has been changed to
876 execute from a limited sandbox, as opposed to executing from
880 - The "beforecheck" and "aftercheck" targets are now specified.
881 - ${CHECKDIR} (added in commit noted above) has been removed.
882 - Legacy behavior can be enabled by setting
883 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
885 If the limited sandbox mode is enabled, "make check" will execute
886 "make distribution", then install, execute the tests, and clean up the
887 sandbox if successful.
889 The "make distribution" and "make install" targets are typically run as
890 root to set appropriate permissions and ownership at installation time.
891 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
892 environment if executing "make check" with limited sandbox mode using
893 an unprivileged user.
896 Since the switch to GPT disk labels, fsck for UFS/FFS has been
897 unable to automatically find alternate superblocks. As of r322297,
898 the information needed to find alternate superblocks has been
899 moved to the end of the area reserved for the boot block.
900 Filesystems created with a newfs of this vintage or later
901 will create the recovery information. If you have a filesystem
902 created prior to this change and wish to have a recovery block
903 created for your filesystem, you can do so by running fsck in
904 foreground mode (i.e., do not use the -p or -y options). As it
905 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
906 to which you should answer yes.
909 As of r321665, an NFSv4 server configuration that services
910 Kerberos mounts or clients that do not support the uid/gid in
911 owner/owner_group string capability, must explicitly enable
912 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
913 machine's /etc/rc.conf file.
916 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
917 Please see the 20141231 entry below for information about prerequisites
918 and upgrading, if you are not already using clang 3.5.0 or higher.
921 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
922 r-commands (rlogin, rsh, etc.) to be built with the base system.
925 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
926 a very major ABI incompatible change, so users of FreeBSD/powerpc must
927 be careful when performing source upgrades. It is best to run
928 'make installworld' from an alternate root system, either a live
929 CD/memory stick, or a temporary root partition. Additionally, all ports
930 must be recompiled. powerpc64 is largely unaffected, except in the case
931 of 32-bit compatibility. All 32-bit binaries will be affected.
934 Forward compatibility for the "ino64" project have been committed. This
935 will allow most new binaries to run on older kernels in a limited
936 fashion. This prevents many of the common foot-shooting actions in the
937 upgrade as well as the limited ability to roll back the kernel across
938 the ino64 upgrade. Complicated use cases may not work properly, though
939 enough simpler ones work to allow recovery in most situations.
942 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
943 if you require the GPL compiler.
946 The internal ABI used for communication between the NFS kernel modules
947 was changed by r320085, so __FreeBSD_version was bumped to
948 ensure all the NFS related modules are updated together.
951 The ABI of struct event was changed by extending the data
952 member to 64bit and adding ext fields. For upgrade, same
953 precautions as for the entry 20170523 "ino64" must be
957 The GNU roff toolchain has been removed from base. To render manpages
958 which are not supported by mandoc(1), man(1) can fallback on GNU roff
959 from ports (and recommends to install it).
960 To render roff(7) documents, consider using GNU roff from ports or the
961 heirloom doctools roff toolchain from ports via pkg install groff or
962 via pkg install heirloom-doctools.
965 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
966 smaller runtime footprint builds. This is useful for embedded systems
967 which only require one chipset support.
969 If you load it as a module, make sure this is in /boot/loader.conf:
973 This will load the HAL, all chip/RF backends and if_ath_pci.
974 If you have if_ath_pci in /boot/loader.conf, ensure it is after
975 if_ath or it will not load any HAL chipset support.
977 If you want to selectively load things (eg on ye cheape ARM/MIPS
978 platforms where RAM is at a premium) you should:
981 * load the chip modules in question
982 * load ath_rate, ath_dfs
984 * load if_ath_pci and/or if_ath_ahb depending upon your particular
985 bus bind type - this is where probe/attach is done.
987 For further comments/feedback, poke adrian@ .
990 The "ino64" 64-bit inode project has been committed, which extends
991 a number of types to 64 bits. Upgrading in place requires care and
992 adherence to the documented upgrade procedure.
994 If using a custom kernel configuration ensure that the
995 COMPAT_FREEBSD11 option is included (as during the upgrade the
996 system will be running the ino64 kernel with the existing world).
998 For the safest in-place upgrade begin by removing previous build
999 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full
1000 procedure documented below under the heading "To rebuild everything and
1001 install it on the current system." Specifically, a reboot is required
1002 after installing the new kernel before installing world. While an
1003 installworld normally works by accident from multiuser after rebooting
1004 the proper kernel, there are many cases where this will fail across this
1005 upgrade and installworld from single user is required.
1008 The NATM framework including the en(4), fatm(4), hatm(4), and
1009 patm(4) devices has been removed. Consumers should plan a
1010 migration before the end-of-life date for FreeBSD 11.
1013 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
1014 diff has not been implemented, if those are needed a newer version of
1015 GNU diff is available via the diffutils package under the gdiff name.
1018 As of r316810 for ipfilter, keep frags is no longer assumed when
1019 keep state is specified in a rule. r316810 aligns ipfilter with
1020 documentation in man pages separating keep frags from keep state.
1021 This allows keep state to be specified without forcing keep frags
1022 and allows keep frags to be specified independently of keep state.
1023 To maintain previous behaviour, also specify keep frags with
1024 keep state (as documented in ipf.conf.5).
1027 arm64 builds now use the base system LLD 4.0.0 linker by default,
1028 instead of requiring that the aarch64-binutils port or package be
1029 installed. To continue using aarch64-binutils, set
1030 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
1033 The UDP optimization in entry 20160818 that added the sysctl
1034 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
1035 packets will no longer be treated as L3 broadcast packets.
1038 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
1039 use any explicitly assigned loopback address available in the jail
1040 instead of using the first assigned address of the jail.
1043 The ctl.ko module no longer implements the iSCSI target frontend:
1044 cfiscsi.ko does instead.
1046 If building cfiscsi.ko as a kernel module, the module can be loaded
1047 via one of the following methods:
1048 - `cfiscsi_load="YES"` in loader.conf(5).
1049 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
1050 - ctladm(8)/ctld(8), when compiled with iSCSI support
1051 (`WITH_ISCSI=yes` in src.conf(5))
1053 Please see cfiscsi(4) for more details.
1056 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
1057 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
1058 same source (previously, the dependency of mmcsd.ko on mmc.ko was
1059 missing, but mmcsd.ko now will refuse to load if it is incompatible
1063 The syntax of ipfw(8) named states was changed to avoid ambiguity.
1064 If you have used named states in the firewall rules, you need to modify
1065 them after installworld and before rebooting. Now named states must
1066 be prefixed with colon.
1069 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
1070 removed as the userland we provide cannot use them. The KMS version
1071 (sys/dev/drm2) supports the same hardware.
1074 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
1075 Please see the 20141231 entry below for information about prerequisites
1076 and upgrading, if you are not already using clang 3.5.0 or higher.
1079 The code that provides support for ZFS .zfs/ directory functionality
1080 has been reimplemented. It's not possible now to create a snapshot
1081 by mkdir under .zfs/snapshot/. That should be the only user visible
1085 EISA bus support has been removed. The WITH_EISA option is no longer
1089 MCA bus support has been removed.
1092 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
1093 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
1096 The EM_MULTIQUEUE kernel configuration option is deprecated now that
1097 the em(4) driver conforms to iflib specifications.
1100 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
1101 IFLIB. If you have a custom kernel configuration that excludes em(4)
1102 but you use igb(4), you need to re-add em(4) to your custom
1106 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
1107 Please see the 20141231 entry below for information about prerequisites
1108 and upgrading, if you are not already using clang 3.5.0 or higher.
1111 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
1112 Please see the 20141231 entry below for information about prerequisites
1113 and upgrading, if you are not already using clang 3.5.0 or higher.
1116 The layout of the pmap structure has changed for powerpc to put the pmap
1117 statistics at the front for all CPU variations. libkvm(3) and all tools
1118 that link against it need to be recompiled.
1121 isl(4) and cyapa(4) drivers now require a new driver,
1122 chromebook_platform(4), to work properly on Chromebook-class hardware.
1123 On other types of hardware the drivers may need to be configured using
1124 device hints. Please see the corresponding manual pages for details.
1127 The urtwn(4) driver was merged into rtwn(4) and now consists of
1128 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
1130 Also, firmware for RTL8188CE was renamed due to possible name
1131 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
1134 GNU rcs has been removed from base. It is available as packages:
1135 - rcs: Latest GPLv3 GNU rcs version.
1136 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
1140 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
1141 modules now requires that the kernel configuration contain the
1142 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
1145 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
1146 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
1149 Relocatable object files with the extension of .So have been renamed
1150 to use an extension of .pico instead. The purpose of this change is
1151 to avoid a name clash with shared libraries on case-insensitive file
1152 systems. On those file systems, foo.So is the same file as foo.so.
1155 GNU rcs has been turned off by default. It can (temporarily) be built
1156 again by adding WITH_RCS knob in src.conf.
1157 Otherwise, GNU rcs is available from packages:
1158 - rcs: Latest GPLv3 GNU rcs version.
1159 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
1162 The backup_uses_rcs functionality has been removed from rc.subr.
1165 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
1166 two separate components, QUEUE_MACRO_DEBUG_TRACE and
1167 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
1168 QUEUE_MACRO_DEBUG behavior.
1171 r304787 changed some ioctl interfaces between the iSCSI userspace
1172 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1173 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1177 The UDP receive code has been updated to only treat incoming UDP
1178 packets that were addressed to an L2 broadcast address as L3
1179 broadcast packets. It is not expected that this will affect any
1180 standards-conforming UDP application. The new behaviour can be
1181 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1185 Remove the openbsd_poll system call.
1186 __FreeBSD_version has been bumped because of this.
1189 The stable/11 branch has been created from head@r302406.
1192 The libc stub for the pipe(2) system call has been replaced with
1193 a wrapper that calls the pipe2(2) system call and the pipe(2)
1194 system call is now only implemented by the kernels that include
1195 "options COMPAT_FREEBSD10" in their config file (this is the
1196 default). Users should ensure that this option is enabled in
1197 their kernel or upgrade userspace to r302092 before upgrading their
1201 CAM will now strip leading spaces from SCSI disks' serial numbers.
1202 This will affect users who create UFS filesystems on SCSI disks using
1203 those disk's diskid device nodes. For example, if /etc/fstab
1204 previously contained a line like
1205 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
1206 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
1207 transforms like gmirror may also be affected. ZFS users should
1211 The bitstring(3) API has been updated with new functionality and
1212 improved performance. But it is binary-incompatible with the old API.
1213 Objects built with the new headers may not be linked against objects
1214 built with the old headers.
1217 The brk and sbrk functions have been removed from libc on arm64.
1218 Binutils from ports has been updated to not link to these
1219 functions and should be updated to the latest version before
1220 installing a new libc.
1223 The armv6 port now defaults to hard float ABI. Limited support
1224 for running both hardfloat and soft float on the same system
1225 is available using the libraries installed with -DWITH_LIBSOFT.
1226 This has only been tested as an upgrade path for installworld
1227 and packages may fail or need manual intervention to run. New
1228 packages will be needed.
1230 To update an existing self-hosted armv6hf system, you must add
1231 TARGET_ARCH=armv6 on the make command line for both the build
1232 and the install steps.
1235 Kernel modules compiled outside of a kernel build now default to
1236 installing to /boot/modules instead of /boot/kernel. Many kernel
1237 modules built this way (such as those in ports) already overrode
1238 KMODDIR explicitly to install into /boot/modules. However,
1239 manually building and installing a module from /sys/modules will
1240 now install to /boot/modules instead of /boot/kernel.
1243 The CAM I/O scheduler has been committed to the kernel. There should be
1244 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1245 list of known rogues that claim support for this but actually corrupt
1246 data is believed to be complete, be on the lookout for data
1247 corruption. The known rogue list is believed to be complete:
1249 o Crucial MX100, M550 drives with MU01 firmware.
1250 o Micron M510 and M550 drives with MU01 firmware.
1251 o Micron M500 prior to MU07 firmware
1252 o Samsung 830, 840, and 850 all firmwares
1253 o FCCT M500 all firmwares
1255 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1256 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1257 updated firmware. Black listed drives will work correctly because these
1258 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1259 this list is the same as found in Linux, it's believed there are no
1260 other rogues in the market place. All other models from the above
1263 To be safe, if you are at all concerned, you can quirk each of your
1264 drives to prevent NCQ from being sent by setting:
1265 kern.cam.ada.X.quirks="0x2"
1266 in loader.conf. If the drive requires the 4k sector quirk, set the
1267 quirks entry to 0x3.
1270 The FAST_DEPEND build option has been removed and its functionality is
1271 now the one true way. The old mkdep(1) style of 'make depend' has
1272 been removed. See 20160311 for further details.
1275 Resource range types have grown from unsigned long to uintmax_t. All
1276 drivers, and anything using libdevinfo, need to be recompiled.
1279 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1280 builds. It no longer runs mkdep(1) during 'make depend', and the
1281 'make depend' stage can safely be skipped now as it is auto ran
1282 when building 'make all' and will generate all SRCS and DPSRCS before
1283 building anything else. Dependencies are gathered at compile time with
1284 -MF flags kept in separate .depend files per object file. Users should
1285 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1286 stale .depend files.
1289 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1290 kernel modules. Therefore, if you load any kernel modules at boot time,
1291 please install the boot loaders after you install the kernel, but before
1295 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1296 make installkernel KERNCONF=YOUR_KERNEL_HERE
1297 make -C sys/boot install
1298 <reboot in single user>
1300 Then follow the usual steps, described in the General Notes section,
1304 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1305 see the 20141231 entry below for information about prerequisites and
1306 upgrading, if you are not already using clang 3.5.0 or higher.
1309 The AIO subsystem is now a standard part of the kernel. The
1310 VFS_AIO kernel option and aio.ko kernel module have been removed.
1311 Due to stability concerns, asynchronous I/O requests are only
1312 permitted on sockets and raw disks by default. To enable
1313 asynchronous I/O requests on all file types, set the
1314 vfs.aio.enable_unsafe sysctl to a non-zero value.
1317 The ELF object manipulation tool objcopy is now provided by the
1318 ELF Tool Chain project rather than by GNU binutils. It should be a
1319 drop-in replacement, with the addition of arm64 support. The
1320 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1321 to obtain the GNU version if necessary.
1324 Building ZFS pools on top of zvols is prohibited by default. That
1325 feature has never worked safely; it's always been prone to deadlocks.
1326 Using a zvol as the backing store for a VM guest's virtual disk will
1327 still work, even if the guest is using ZFS. Legacy behavior can be
1328 restored by setting vfs.zfs.vol.recursive=1.
1331 The NONE and HPN patches has been removed from OpenSSH. They are
1332 still available in the security/openssh-portable port.
1335 With the addition of ypldap(8), a new _ypldap user is now required
1336 during installworld. "mergemaster -p" can be used to add the user
1337 prior to installworld, as documented in the handbook.
1340 The tftp loader (pxeboot) now uses the option root-path directive. As a
1341 consequence it no longer looks for a pxeboot.4th file on the tftp
1342 server. Instead it uses the regular /boot infrastructure as with the
1346 The code to start recording plug and play data into the modules has
1347 been committed. While the old tools will properly build a new kernel,
1348 a number of warnings about "unknown metadata record 4" will be produced
1349 for an older kldxref. To avoid such warnings, make sure to rebuild
1350 the kernel toolchain (or world). Make sure that you have r292078 or
1351 later when trying to build 292077 or later before rebuilding.
1354 Debug data files are now built by default with 'make buildworld' and
1355 installed with 'make installworld'. This facilitates debugging but
1356 requires more disk space both during the build and for the installed
1357 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1361 r291527 changed the internal interface between the nfsd.ko and
1362 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1363 __FreeBSD_version has been bumped because of this.
1366 Add support for unicode collation strings leads to a change of
1367 order of files listed by ls(1) for example. To get back to the old
1368 behaviour, set LC_COLLATE environment variable to "C".
1370 Databases administrators will need to reindex their databases given
1371 collation results will be different.
1373 Due to a bug in install(1) it is recommended to remove the ancient
1374 locales before running make installworld.
1376 rm -rf /usr/share/locale/*
1379 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1380 libcrypto.so.7 or libssl.so.7 must be recompiled.
1383 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1384 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1385 should be replaced with isp_2400 and isp_2500 modules respectively.
1388 The build previously allowed using 'make -n' to not recurse into
1389 sub-directories while showing what commands would be executed, and
1390 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1391 and 'make -N' will not.
1394 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1395 and etcupdate will now use this file. A custom sendmail.cf is now
1396 updated via this mechanism rather than via installworld. If you had
1397 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1398 want to remove the exclusion or change it to "always install".
1399 /etc/mail/sendmail.cf is now managed the same way regardless of
1400 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1401 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1404 Compatibility shims for legacy ATA device names have been removed.
1405 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1406 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1407 environment variables, /dev/ad* and /dev/ar* symbolic links.
1410 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1411 Please see the 20141231 entry below for information about prerequisites
1412 and upgrading, if you are not already using clang 3.5.0 or higher.
1415 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1416 and renamed from .symbols to .debug. This reduces the size requirements
1417 on the boot partition or file system and provides consistency with
1418 userland debug files.
1420 When using the supported kernel installation method the
1421 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1422 as is done with /boot/kernel.
1424 Developers wishing to maintain the historical behavior of installing
1425 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1428 The wireless drivers had undergone changes that remove the 'parent
1429 interface' from the ifconfig -l output. The rc.d network scripts
1430 used to check presence of a parent interface in the list, so old
1431 scripts would fail to start wireless networking. Thus, etcupdate(3)
1432 or mergemaster(8) run is required after kernel update, to update your
1433 rc.d scripts in /etc.
1436 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1437 These configurations are now automatically interpreted as
1438 'scrub fragment reassemble'.
1441 Kernel-loadable modules for the random(4) device are back. To use
1442 them, the kernel must have
1445 options RANDOM_LOADABLE
1447 kldload(8) can then be used to load random_fortuna.ko
1448 or random_yarrow.ko. Please note that due to the indirect
1449 function calls that the loadable modules need to provide,
1450 the build-in variants will be slightly more efficient.
1452 The random(4) kernel option RANDOM_DUMMY has been retired due to
1453 unpopularity. It was not all that useful anyway.
1456 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1457 Control over building the ELF Tool Chain tools is now provided by
1458 the WITHOUT_TOOLCHAIN knob.
1461 The polarity of Pulse Per Second (PPS) capture events with the
1462 uart(4) driver has been corrected. Prior to this change the PPS
1463 "assert" event corresponded to the trailing edge of a positive PPS
1464 pulse and the "clear" event was the leading edge of the next pulse.
1466 As the width of a PPS pulse in a typical GPS receiver is on the
1467 order of 1 millisecond, most users will not notice any significant
1468 difference with this change.
1470 Anyone who has compensated for the historical polarity reversal by
1471 configuring a negative offset equal to the pulse width will need to
1472 remove that workaround.
1475 The default group assigned to /dev/dri entries has been changed
1476 from 'wheel' to 'video' with the id of '44'. If you want to have
1477 access to the dri devices please add yourself to the video group
1480 # pw groupmod video -m $USER
1483 The menu.rc and loader.rc files will now be replaced during
1484 upgrades. Please migrate local changes to menu.rc.local and
1485 loader.rc.local instead.
1488 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1489 strings and strip have been removed. The src.conf(5) knob
1490 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1493 As ZFS requires more kernel stack pages than is the default on some
1494 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1495 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1497 Please consider using 'options KSTACK_PAGES=X' where X is greater
1498 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1501 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1502 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1503 default, i.e., they will not contain "::". For example, instead
1504 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1505 to have a more specific match, such as different map entries for
1506 IPv6:0:0 vs IPv6:0. This change requires that configuration
1507 data (including maps, files, classes, custom ruleset, etc.) must
1508 use the same format, so make certain such configuration data is
1509 upgrading. As a very simple check search for patterns like
1510 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1511 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1512 the cf option UseCompressedIPv6Addresses.
1515 The default kernel entropy-processing algorithm is now
1516 Fortuna, replacing Yarrow.
1518 Assuming you have 'device random' in your kernel config
1519 file, the configurations allow a kernel option to override
1520 this default. You may choose *ONE* of:
1522 options RANDOM_YARROW # Legacy /dev/random algorithm.
1523 options RANDOM_DUMMY # Blocking-only driver.
1525 If you have neither, you get Fortuna. For most people,
1526 read no further, Fortuna will give a /dev/random that works
1527 like it always used to, and the difference will be irrelevant.
1529 If you remove 'device random', you get *NO* kernel-processed
1530 entropy at all. This may be acceptable to folks building
1531 embedded systems, but has complications. Carry on reading,
1532 and it is assumed you know what you need.
1534 *PLEASE* read random(4) and random(9) if you are in the
1535 habit of tweaking kernel configs, and/or if you are a member
1536 of the embedded community, wanting specific and not-usual
1537 behaviour from your security subsystems.
1539 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1540 random', you will NOT have a functioning /dev/random, and
1541 many cryptographic features will not work, including SSH.
1542 You may also find strange behaviour from the random(3) set
1543 of library functions, in particular sranddev(3), srandomdev(3)
1544 and arc4random(3). The reason for this is that the KERN_ARND
1545 sysctl only returns entropy if it thinks it has some to
1546 share, and with RANDOM_DUMMY or no 'device random' this
1550 An additional fix for the issue described in the 20150614 sendmail
1551 entry below has been committed in revision 284717.
1554 FreeBSD's old make (fmake) has been removed from the system. It is
1555 available as the devel/fmake port or via pkg install fmake.
1558 The fix for the issue described in the 20150614 sendmail entry
1559 below has been committed in revision 284436. The work
1560 around described in that entry is no longer needed unless the
1561 default setting is overridden by a confDH_PARAMETERS configuration
1562 setting of '5' or pointing to a 512 bit DH parameter file.
1565 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1566 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1567 and devel/kyua to version 0.20+ and adjust any calling code to work
1568 with Kyuafile and kyua.
1571 The import of openssl to address the FreeBSD-SA-15:10.openssl
1572 security advisory includes a change which rejects handshakes
1573 with DH parameters below 768 bits. sendmail releases prior
1574 to 8.15.2 (not yet released), defaulted to a 512 bit
1575 DH parameter setting for client connections. To work around
1576 this interoperability, sendmail can be configured to use a
1577 2048 bit DH parameter by:
1579 1. Edit /etc/mail/`hostname`.mc
1580 2. If a setting for confDH_PARAMETERS does not exist or
1581 exists and is set to a string beginning with '5',
1582 replace it with '2'.
1583 3. If a setting for confDH_PARAMETERS exists and is set to
1584 a file path, create a new file with:
1585 openssl dhparam -out /path/to/file 2048
1586 4. Rebuild the .cf file:
1587 cd /etc/mail/; make; make install
1588 5. Restart sendmail:
1589 cd /etc/mail/; make restart
1591 A sendmail patch is coming, at which time this file will be
1595 Generation of legacy formatted entries have been disabled by default
1596 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1597 entries were converted to use the new format by default when the new,
1598 machine independent format have been added and supported since FreeBSD
1601 Please see the pwd_mkdb(8) manual page for further details.
1604 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1605 20141231 entry below for information about prerequisites and upgrading,
1606 if you are not already using 3.5.0 or higher.
1609 TI platform code switched to using vendor DTS files and this update
1610 may break existing systems running on Beaglebone, Beaglebone Black,
1613 - dtb files should be regenerated/reinstalled. Filenames are the
1614 same but content is different now
1615 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1616 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1617 addressing scheme is now pin 25 on /dev/gpioc3.
1618 - Pandaboard: /etc/ttys should be updated, serial console device is
1619 now /dev/ttyu2, not /dev/ttyu0
1622 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1623 If you need the GNU extension from groff soelim(1), install groff
1624 from package: pkg install groff, or via ports: textproc/groff.
1627 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1628 defined in symlink(7); previously symlinks were silently ignored.
1631 The const qualifier has been removed from iconv(3) to comply with
1632 POSIX. The ports tree is aware of this from r384038 onwards.
1635 Libraries specified by LIBADD in Makefiles must have a corresponding
1636 DPADD_<lib> variable to ensure correct dependencies. This is now
1637 enforced in src.libnames.mk.
1640 From legacy ata(4) driver was removed support for SATA controllers
1641 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1642 Kernel modules ataahci and ataadaptec were removed completely,
1643 replaced by ahci and mvs modules respectively.
1646 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1647 the 20141231 entry below for information about prerequisites and
1648 upgrading, if you are not already using 3.5.0 or higher.
1651 The 32-bit PowerPC kernel has been changed to a position-independent
1652 executable. This can only be booted with a version of loader(8)
1653 newer than January 31, 2015, so make sure to update both world and
1654 kernel before rebooting.
1657 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1658 but before r278950, the RNG was not seeded properly. Immediately
1659 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1660 ssh keys or openssl keys) that were generated w/ a kernel from that
1661 range. This does not affect programs that directly used /dev/random
1662 or /dev/urandom. All userland uses of arc4random(3) are affected.
1665 The autofs(4) ABI was changed in order to restore binary compatibility
1666 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1667 with the new kernel.
1670 The powerpc64 kernel has been changed to a position-independent
1671 executable. This can only be booted with a new version of loader(8),
1672 so make sure to update both world and kernel before rebooting.
1675 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1676 only release, no new features have been added. Please see the 20141231
1677 entry below for information about prerequisites and upgrading, if you
1678 are not already using 3.5.0.
1681 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1682 taken from the ELF Tool Chain project rather than GNU binutils. They
1683 should be drop-in replacements, with the addition of arm64 support.
1684 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1685 binutils tools, if necessary. See 20150805 for updated information.
1688 The default Unbound configuration now enables remote control
1689 using a local socket. Users who have already enabled the
1690 local_unbound service should regenerate their configuration
1691 by running "service local_unbound setup" as root.
1694 The GNU texinfo and GNU info pages have been removed.
1695 To be able to view GNU info pages please install texinfo from ports.
1698 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1700 As of this release, a prerequisite for building clang, llvm and lldb is
1701 a C++11 capable compiler and C++11 standard library. This means that to
1702 be able to successfully build the cross-tools stage of buildworld, with
1703 clang as the bootstrap compiler, your system compiler or cross compiler
1704 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1705 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1708 On any standard FreeBSD 10.x or 11.x installation, where clang and
1709 libc++ are on by default (that is, on x86 or arm), this should work out
1712 On 9.x installations where clang is enabled by default, e.g. on x86 and
1713 powerpc, libc++ will not be enabled by default, so libc++ should be
1714 built (with clang) and installed first. If both clang and libc++ are
1715 missing, build clang first, then use it to build libc++.
1717 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1718 the instructions for 9.x above.
1720 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1721 default, and do not build clang.
1723 Many embedded systems are resource constrained, and will not be able to
1724 build clang in a reasonable time, or in some cases at all. In those
1725 cases, cross building bootable systems on amd64 is a workaround.
1727 This new version of clang introduces a number of new warnings, of which
1728 the following are most likely to appear:
1732 This warns in two cases, for both C and C++:
1733 * When the code is trying to take the absolute value of an unsigned
1734 quantity, which is effectively a no-op, and almost never what was
1735 intended. The code should be fixed, if at all possible. If you are
1736 sure that the unsigned quantity can be safely cast to signed, without
1737 loss of information or undefined behavior, you can add an explicit
1738 cast, or disable the warning.
1740 * When the code is trying to take an absolute value, but the called
1741 abs() variant is for the wrong type, which can lead to truncation.
1742 If you want to disable the warning instead of fixing the code, please
1743 make sure that truncation will not occur, or it might lead to unwanted
1746 -Wtautological-undefined-compare and
1747 -Wundefined-bool-conversion
1749 These warn when C++ code is trying to compare 'this' against NULL, while
1750 'this' should never be NULL in well-defined C++ code. However, there is
1751 some legacy (pre C++11) code out there, which actively abuses this
1752 feature, which was less strictly defined in previous C++ versions.
1754 Squid and openjdk do this, for example. The warning can be turned off
1755 for C++98 and earlier, but compiling the code in C++11 mode might result
1756 in unexpected behavior; for example, the parts of the program that are
1757 unreachable could be optimized away.
1760 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1761 kernel sources have been removed. The .h files remain, since some
1762 utilities include them. This will need to be fixed later.
1763 If "mount -t oldnfs ..." is attempted, it will fail.
1764 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1765 the utilities will report errors.
1768 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1769 directories to top level SUBDIR variable when their parent
1770 directory is included in LOCAL_DIRS. Users with build systems with
1771 such hierarchies and without SUBDIR entries in the parent
1772 directory Makefiles should add them or add the directories to
1776 faith(4) and faithd(8) have been removed from the base system. Faith
1777 has been obsolete for a very long time.
1780 vt(4), the new console driver, is enabled by default. It brings
1781 support for Unicode and double-width characters, as well as
1782 support for UEFI and integration with the KMS kernel video
1785 You may need to update your console settings in /etc/rc.conf,
1786 most probably the keymap. During boot, /etc/rc.d/syscons will
1787 indicate what you need to do.
1789 vt(4) still has issues and lacks some features compared to
1790 syscons(4). See the wiki for up-to-date information:
1791 https://wiki.freebsd.org/Newcons
1793 If you want to keep using syscons(4), you can do so by adding
1794 the following line to /boot/loader.conf:
1798 pjdfstest has been integrated into kyua as an opt-in test suite.
1799 Please see share/doc/pjdfstest/README for more details on how to
1803 gperf has been removed from the base system for architectures
1804 that use clang. Ports that require gperf will obtain it from the
1808 pjdfstest has been moved from tools/regression/pjdfstest to
1812 At svn r271982, The default linux compat kernel ABI has been adjusted
1813 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1814 update. If you wish to continue using the linux-f10 compat ports,
1815 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1816 encouraged to update their linux-compat packages to linux-c6 during
1817 their next update cycle.
1820 The ofwfb driver, used to provide a graphics console on PowerPC when
1821 using vt(4), no longer allows mmap() of all physical memory. This
1822 will prevent Xorg on PowerPC with some ATI graphics cards from
1823 initializing properly unless x11-servers/xorg-server is updated to
1827 The xdev targets have been converted to using TARGET and
1828 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1831 The default unbound configuration has been modified to address
1832 issues with reverse lookups on networks that use private
1833 address ranges. If you use the local_unbound service, run
1834 "service local_unbound setup" as root to regenerate your
1835 configuration, then "service local_unbound reload" to load the
1839 The GNU texinfo and GNU info pages are not built and installed
1840 anymore, WITH_INFO knob has been added to allow to built and install
1842 UPDATE: see 20150102 entry on texinfo's removal
1845 The GNU readline library is now an INTERNALLIB - that is, it is
1846 statically linked into consumers (GDB and variants) in the base
1847 system, and the shared library is no longer installed. The
1848 devel/readline port is available for third party software that
1852 The Itanium architecture (ia64) has been removed from the list of
1853 known architectures. This is the first step in the removal of the
1857 Commit r268115 has added NFSv4.1 server support, merged from
1858 projects/nfsv4.1-server. Since this includes changes to the
1859 internal interfaces between the NFS related modules, a full
1860 build of the kernel and modules will be necessary.
1861 __FreeBSD_version has been bumped.
1864 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1865 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1866 which differs from the behaviour controlled by this knob.)
1869 Maximal length of the serial number in CTL was increased from 16 to
1870 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1871 and ctld, need to be rebuilt to work with a new kernel.
1874 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1875 1 respectively to match the upstream numbers. They were out of
1876 sync because, when they were originally added to FreeBSD, the
1877 upstream versions were not respected. These libraries are private
1878 and not yet built by default, so renumbering them should be a
1879 non-issue. However, unclean source trees will yield broken test
1880 programs once the operator executes "make delete-old-libs" after a
1881 "make installworld".
1883 Additionally, the atf-sh binary was made private by moving it into
1884 /usr/libexec/. Already-built shell test programs will keep the
1885 path to the old binary so they will break after "make delete-old"
1888 If you are using WITH_TESTS=yes (not the default), wipe the object
1889 tree and rebuild from scratch to prevent spurious test failures.
1890 This is only needed once: the misnumbered libraries and misplaced
1891 binaries have been added to OptionalObsoleteFiles.inc so they will
1892 be removed during a clean upgrade.
1895 Clang and llvm have been upgraded to 3.4.1 release.
1898 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1899 be removed to avoid issues in the future (and has been added to
1903 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1904 past, it affected all builds that used the bsd.*.mk files. The old
1905 behavior was a bug, but people may have relied upon it. To get this
1906 behavior back, you can .include /etc/src.conf from /etc/make.conf
1907 (which is still global and isn't changed). This also changes the
1908 behavior of incremental builds inside the tree of individual
1909 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1910 Although this has survived make universe and some upgrade scenarios,
1911 other upgrade scenarios may have broken. At least one form of
1912 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1913 as well... In cases where MAKESYSPATH isn't working with this
1914 setting, you'll need to set it to the full path to your tree.
1916 One side effect of all this cleaning up is that bsd.compiler.mk
1917 is no longer implicitly included by bsd.own.mk. If you wish to
1918 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1922 The lindev device has been removed since /dev/full has been made a
1923 standard device. __FreeBSD_version has been bumped.
1926 The knob WITHOUT_VI was added to the base system, which controls
1927 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1928 in order to reorder files share/termcap and didn't build ex(1) as a
1929 build tool, so building/installing with WITH_VI is highly advised for
1930 build hosts for older releases.
1932 This issue has been fixed in stable/9 and stable/10 in r277022 and
1933 r276991, respectively.
1936 The YES_HESIOD knob has been removed. It has been obsolete for
1937 a decade. Please move to using WITH_HESIOD instead or your builds
1938 will silently lack HESIOD.
1941 The uart(4) driver has been changed with respect to its handling
1942 of the low-level console. Previously the uart(4) driver prevented
1943 any process from changing the baudrate or the CLOCAL and HUPCL
1944 control flags. By removing the restrictions, operators can make
1945 changes to the serial console port without having to reboot.
1946 However, when getty(8) is started on the serial device that is
1947 associated with the low-level console, a misconfigured terminal
1948 line in /etc/ttys will now have a real impact.
1949 Before upgrading the kernel, make sure that /etc/ttys has the
1950 serial console device configured as 3wire without baudrate to
1951 preserve the previous behaviour. E.g:
1952 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1955 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1956 to improve performance. To re-enable it, if needed, run rpcbind
1957 with command line option -W.
1960 Switched back to the GPL dtc compiler due to updates in the upstream
1961 dts files not being supported by the BSDL dtc compiler. You will need
1962 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1963 may result while building dtb files during a kernel build if you fail
1964 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1967 Clang and llvm have been upgraded to 3.4 release.
1970 The nve(4) driver has been removed. Please use the nfe(4) driver
1971 for NVIDIA nForce MCP Ethernet adapters instead.
1974 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1975 This could cause certain C++ applications using shared libraries built
1976 against the previous version of libc++ to crash. The incompatibility
1977 has now been fixed, but any C++ applications or shared libraries built
1978 between r261283 and r261801 should be recompiled.
1981 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1982 capability mode support. Please note that enabling the feature in
1983 kernel is still highly recommended.
1986 OpenSSH is now built with sandbox support, and will use sandbox as
1987 the default privilege separation method. This requires Capsicum
1988 capability mode support in kernel.
1991 The libelf and libdwarf libraries have been updated to newer
1992 versions from upstream. Shared library version numbers for
1993 these two libraries were bumped. Any ports or binaries
1994 requiring these two libraries should be recompiled.
1995 __FreeBSD_version is bumped to 1100006.
1998 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1999 instead of providing an explicit one, this would prevent such
2000 Makefile from providing its own Kyuafile in the future during
2001 NO_CLEAN builds. This has been fixed in the Makefiles but manual
2002 intervention is needed to clean an objdir if you use NO_CLEAN:
2003 # find /usr/obj -name Kyuafile | xargs rm -f
2006 The behavior of gss_pseudo_random() for the krb5 mechanism
2007 has changed, for applications requesting a longer random string
2008 than produced by the underlying enctype's pseudo-random() function.
2009 In particular, the random string produced from a session key of
2010 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
2011 be different at the 17th octet and later, after this change.
2012 The counter used in the PRF+ construction is now encoded as a
2013 big-endian integer in accordance with RFC 4402.
2014 __FreeBSD_version is bumped to 1100004.
2017 The WITHOUT_ATF build knob has been removed and its functionality
2018 has been subsumed into the more generic WITHOUT_TESTS. If you were
2019 using the former to disable the build of the ATF libraries, you
2020 should change your settings to use the latter.
2023 The default version of mtree is nmtree which is obtained from
2024 NetBSD. The output is generally the same, but may vary
2025 slightly. If you found you need identical output adding
2026 "-F freebsd9" to the command line should do the trick. For the
2027 time being, the old mtree is available as fmtree.
2030 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
2031 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
2032 1.1.4_8 and verify bsdyml not linked in, before running "make
2034 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
2036 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
2039 The stable/10 branch has been created in subversion from head
2046 Sometimes, obscure build problems are the result of environment
2047 poisoning. This can happen because the make utility reads its
2048 environment when searching for values for global variables. To run
2049 your build attempts in an "environmental clean room", prefix all make
2050 commands with 'env -i '. See the env(1) manual page for more details.
2051 Occasionally a build failure will occur with "make -j" due to a race
2052 condition. If this happens try building again without -j, and please
2053 report a bug if it happens consistently.
2055 When upgrading from one major version to another it is generally best to
2056 upgrade to the latest code in the currently installed branch first, then
2057 do an upgrade to the new branch. This is the best-tested upgrade path,
2058 and has the highest probability of being successful. Please try this
2059 approach if you encounter problems with a major version upgrade. Since
2060 the stable 4.x branch point, one has generally been able to upgrade from
2061 anywhere in the most recent stable branch to head / current (or even the
2062 last couple of stable branches). See the top of this file when there's
2065 The update process will emit an error on an attempt to perform a build
2066 or install from a FreeBSD version below the earliest supported version.
2067 When updating from an older version the update should be performed one
2068 major release at a time, including running `make delete-old` at each
2071 When upgrading a live system, having a root shell around before
2072 installing anything can help undo problems. Not having a root shell
2073 around can lead to problems if pam has changed too much from your
2074 starting point to allow continued authentication after the upgrade.
2076 This file should be read as a log of events. When a later event changes
2077 information of a prior event, the prior event should not be deleted.
2078 Instead, a pointer to the entry with the new information should be
2079 placed in the old entry. Readers of this file should also sanity check
2080 older entries before relying on them blindly. Authors of new entries
2081 should write them with this in mind.
2085 When upgrading the boot ZFS pool to a new version, always follow
2088 1.) recompile and reinstall the ZFS boot loader and boot block
2089 (this is part of "make buildworld" and "make installworld")
2091 2.) update the ZFS boot block on your boot drive
2093 The following example updates the ZFS boot block on the first
2094 partition (freebsd-boot) of a GPT partitioned drive ada0:
2095 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
2097 Non-boot pools do not need these updates.
2101 If you are updating from a prior version of FreeBSD (even one just
2102 a few days old), you should follow this procedure. It is the most
2103 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2105 make kernel-toolchain
2106 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2107 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2109 To test a kernel once
2110 ---------------------
2111 If you just want to boot a kernel once (because you are not sure
2112 if it works, or if you want to boot a known bad kernel to provide
2113 debugging information) run
2114 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2115 nextboot -k testkernel
2117 To rebuild everything and install it on the current system.
2118 -----------------------------------------------------------
2119 # Note: sometimes if you are running current you gotta do more than
2120 # is listed here if you are upgrading from a really old current.
2122 <make sure you have good level 0 dumps>
2124 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2125 make installkernel KERNCONF=YOUR_KERNEL_HERE
2127 <reboot in single user> [3]
2134 To cross-install current onto a separate partition
2135 --------------------------------------------------
2136 # In this approach we use a separate partition to hold
2137 # current's root, 'usr', and 'var' directories. A partition
2138 # holding "/", "/usr" and "/var" should be about 2GB in
2141 <make sure you have good level 0 dumps>
2144 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2145 <maybe newfs current's root partition>
2146 <mount current's root partition on directory ${CURRENT_ROOT}>
2147 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
2148 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2149 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2150 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2151 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2152 <reboot into current>
2153 <do a "native" rebuild/install as described in the previous section>
2154 <maybe install compatibility libraries from ports/misc/compat*>
2158 To upgrade in-place from stable to current
2159 ----------------------------------------------
2160 <make sure you have good level 0 dumps>
2162 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
2163 make installkernel KERNCONF=YOUR_KERNEL_HERE
2165 <reboot in single user> [3]
2172 Make sure that you've read the UPDATING file to understand the
2173 tweaks to various things you need. At this point in the life
2174 cycle of current, things change often and you are on your own
2175 to cope. The defaults can also change, so please read ALL of
2176 the UPDATING entries.
2178 Also, if you are tracking -current, you must be subscribed to
2179 freebsd-current@freebsd.org. Make sure that before you update
2180 your sources that you have read and understood all the recent
2181 messages there. If in doubt, please track -stable which has
2182 much fewer pitfalls.
2184 [1] If you have third party modules, such as vmware, you
2185 should disable them at this point so they don't crash your
2188 [3] From the bootblocks, boot -s, and then do
2192 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed
2193 cd src # full path to source
2194 adjkerntz -i # if CMOS is wall time
2195 Also, when doing a major release upgrade, it is required that
2196 you boot into single user mode to do the installworld.
2198 [4] Note: This step is non-optional. Failure to do this step
2199 can result in a significant reduction in the functionality of the
2200 system. Attempting to do it by hand is not recommended and those
2201 that pursue this avenue should read this file carefully, as well
2202 as the archives of freebsd-current and freebsd-hackers mailing lists
2203 for potential gotchas. The -U option is also useful to consider.
2204 See mergemaster(8) for more information.
2206 [5] Usually this step is a no-op. However, from time to time
2207 you may need to do this if you get unknown user in the following
2208 step. It never hurts to do it all the time. You may need to
2209 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2210 install) after the buildworld before this step if you last updated
2211 from current before 20130425 or from -stable before 20130430.
2213 [6] This only deletes old files and directories. Old libraries
2214 can be deleted by "make delete-old-libs", but you have to make
2215 sure that no program is using those libraries anymore.
2217 [8] The new kernel must be able to run existing binaries used by an
2218 installworld. When upgrading across major versions, the new kernel's
2219 configuration must include the correct COMPAT_FREEBSD<n> option for
2220 existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure
2221 to do so may leave you with a system that is hard to boot to recover. A
2222 GENERIC kernel will include suitable compatibility options to run
2223 binaries from older branches. Note that the ability to run binaries
2224 from unsupported branches is not guaranteed.
2226 Make sure that you merge any new devices from GENERIC since the
2227 last time you updated your kernel config file. Options also
2228 change over time, so you may need to adjust your custom kernels
2231 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2232 "?=" instead of the "=" assignment operator, so that buildworld can
2233 override the CPUTYPE if it needs to.
2235 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2236 not on the command line, or in /etc/make.conf. buildworld will
2237 warn if it is improperly defined.
2240 This file contains a list, in reverse chronological order, of major
2241 breakages in tracking -current. It is not guaranteed to be a complete
2242 list of such breakages, and only contains entries since September 23, 2011.
2243 If you need to see UPDATING entries from before that date, you will need
2244 to fetch an UPDATING file from an older FreeBSD release.
2246 Copyright information:
2248 Copyright 1998-2009 M. Warner Losh <imp@FreeBSD.org>
2250 Redistribution, publication, translation and use, with or without
2251 modification, in full or in part, in any form or format of this
2252 document are permitted without further permission from the author.
2254 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2255 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2256 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2257 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2258 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2259 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2260 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2261 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2262 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2263 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2264 POSSIBILITY OF SUCH DAMAGE.
2266 Contact Warner Losh if you have any questions about your use of