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 r364092 modified the internal ABI used between the kernel NFS
31 modules. As such, all of these modules need to be rebuilt
32 from sources, so a version bump was done.
35 Makefile.inc has been updated to work around the issue documented in
36 20200729. It was a case where the optimization of using symbolic links
37 to point to binaries created a situation where we'd run new binaries
38 with old libraries starting midway through the installworld process.
41 r363679 has redefined some undefined behavior in regcomp(3); notably,
42 extraneous escapes of most ordinary characters will no longer be
43 accepted. An exp-run has identified all of the problems with this in
44 ports, but other non-ports software may need extra escapes removed to
47 Because of this change, installworld may encounter the following error
48 from rtld: Undefined symbol "regcomp@FBSD_1.6" -- It is imperative that
49 you do not halt installworld. Instead, let it run to completion (whether
50 successful or not) and run installworld once more.
53 A new implementation of bc and dc has been imorted in r362681. This
54 implementation corrects non-conformant behavior of the previous bc
55 and adds GNU bc compatible options. It offers a number of extensions,
56 is much faster on large values, and has support for message catalogs
57 (a number of languages are already supported, contributions of further
58 languages welcome). The option WITHOUT_GH_BC can be used to build the
59 world with the previous versions of bc and dc.
62 r362639 changed the internal API used between the NFS kernel modules.
63 As such, they all need to be rebuilt from sources.
66 r362158 changed the arguments for VFS_CHECKEXP(). As such, any
67 out of tree file systems need to be modified and rebuilt.
68 Also, any file systems that are modules must be rebuilt.
71 read(2) of a directory fd is now rejected by default. root may
72 re-enable it for system root only on non-ZFS filesystems with the
73 security.bsd.allow_read_dir sysctl(8) MIB if
74 security.bsd.suser_enabled=1.
76 It may be advised to setup aliases for grep to default to `-d skip` if
77 commonly non-recursively grepping a list that includes directories and
78 the potential for the resulting stderr output is not tolerable. Example
79 aliases are now installed, commented out, in /root/.cshrc and
83 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
84 been upgraded to 10.0.1. Please see the 20141231 entry below for
85 information about prerequisites and upgrading, if you are not already
86 using clang 3.5.0 or higher.
89 Support for obsolete compilers has been removed from the build system.
90 Clang 6 and GCC 6.4 are the minimum supported versions.
93 closefrom(2) has been moved under COMPAT12, and replaced in libc with a
94 stub that calls close_range(2). If using a custom kernel configuration,
95 you may want to ensure that the COMPAT_FREEBSD12 option is included, as
96 a slightly older -CURRENT userland and older FreeBSD userlands may not
97 be functional without closefrom(2).
100 Upstream DTS from Linux 5.6 was merged and they now have the SID
101 and THS (Secure ID controller and THermal Sensor) node present.
102 The DTB overlays have now been removed from the tree for the H3/H5 and
103 A64 SoCs and the aw_sid and aw_thermal driver have been updated to
104 deal with upstream DTS. If you are using those overlays you need to
105 remove them from loader.conf and update the DTBs on the FAT partition.
108 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
109 been upgraded to 10.0.0. Please see the 20141231 entry below for
110 information about prerequisites and upgrading, if you are not already
111 using clang 3.5.0 or higher.
114 The amd(8) automount daemon has been removed from the source tree.
115 As of FreeBSD 10.1 autofs(5) is the preferred tool for automounting.
116 amd is still available in the sysutils/am-utils port.
119 Removed brooktree driver (bktr.4) from the tree.
122 The WITH_GPL_DTC option has been removed. The BSD-licenced device tree
123 compiler in usr.bin/dtc is used on all architectures which use dtc, and
124 the GPL dtc is available (if needed) from the sysutils/dtc port.
127 The WITHOUT_LLVM_LIBUNWIND option has been removed. LLVM's libunwind
128 is used by all supported CPU architectures.
131 GCC 4.2.1 has been removed from the tree. The WITH_GCC,
132 WITH_GCC_BOOTSTRAP, and WITH_GNUCXX options are no longer available.
133 Users who wish to build FreeBSD with GCC must use the external toolchain
137 ncurses has been updated to a newer version (6.2-20200215). Given the ABI
138 has changed, users will have to rebuild all the ports that are linked to
142 The size of struct vnet and the magic cookie have changed.
143 Users need to recompile libkvm and all modules using VIMAGE
144 together with their new kernel.
147 Defining the long deprecated NO_CTF, NO_DEBUG_FILES, NO_INSTALLLIB,
148 NO_MAN, NO_PROFILE, and NO_WARNS variables is now an error. Update
149 your Makefiles and scripts to define MK_<var>=no instead as required.
151 One exception to this is that program or library Makefiles should
152 define MAN to empty rather than setting MK_MAN=no.
155 Clang/LLVM is now the default compiler and LLD the default
159 make universe no longer uses GCC 4.2.1 on any architectures.
160 Architectures not supported by in-tree Clang/LLVM require an
161 external toolchain package.
164 GCC 4.2.1 is now not built by default, as part of the GCC 4.2.1
165 retirement plan. Specifically, the GCC, GCC_BOOTSTRAP, and GNUCXX
166 options default to off for all supported CPU architectures. As a
167 short-term transition aid they may be enabled via WITH_* options.
168 GCC 4.2.1 is expected to be removed from the tree on 2020-03-31.
171 Support for armv5 has been disconnected and is being removed. The
172 machine combination MACHINE=arm MACHINE_ARCH=arm is no longer valid.
173 You must now use a MACHINE_ARCH of armv6 or armv7. The default
174 MACHINE_ARCH for MACHINE=arm is now armv7.
177 Clang/LLVM is now the default compiler for all powerpc architectures.
178 LLD is now the default linker for powerpc64. The change for powerpc64
179 also includes a change to the ELFv2 ABI, incompatible with the existing
183 Kernel-loadable random(4) modules are no longer unloadable.
186 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
187 been upgraded to 9.0.1. Please see the 20141231 entry below for
188 information about prerequisites and upgrading, if you are not already
189 using clang 3.5.0 or higher.
192 r355677 has modified the internal interface used between the
193 NFS modules in the kernel. As such, they must all be upgraded
194 simultaneously. I will do a version bump for this.
197 The root certificates of the Mozilla CA Certificate Store have been
198 imported into the base system and can be managed with the certctl(8)
199 utility. If you have installed the security/ca_root_nss port or package
200 with the ETCSYMLINK option (the default), be advised that there may be
201 differences between those included in the port and those included in
202 base due to differences in nss branch used as well as general update
203 frequency. Note also that certctl(8) cannot manage certs in the
204 format used by the security/ca_root_nss port.
207 The amd(8) automount daemon has been disabled by default, and will be
208 removed in the future. As of FreeBSD 10.1 the autofs(5) is available
212 The nctgpio and wbwd drivers have been moved to the superio bus.
213 If you have one of these drivers in a kernel configuration, then
214 you should add device superio to it. If you use one of these drivers
215 as a module and you compile a custom set of modules, then you should
216 add superio to the set.
219 KPIs for network drivers to access interface addresses have changed.
220 Users need to recompile NIC driver modules together with kernel.
223 The net.link.tap.user_open sysctl no longer prevents user opening of
224 already created /dev/tapNN devices. Access is still controlled by
225 node permissions, just like tun devices. The net.link.tap.user_open
226 sysctl is now used only to allow users to perform devfs cloning of
227 tap devices, and the subsequent open may not succeed if the user is not
228 in the appropriate group. This sysctl may be deprecated/removed
229 completely in the future.
232 mips, powerpc, and sparc64 are no longer built as part of
233 universe / tinderbox unless MAKE_OBSOLETE_GCC is defined. If
234 not defined, mips, powerpc, and sparc64 builds will look for
235 the xtoolchain binaries and if installed use them for universe
236 builds. As llvm 9.0 becomes vetted for these architectures, they
237 will be removed from the list.
240 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
241 been upgraded to 9.0.0. Please see the 20141231 entry below for
242 information about prerequisites and upgrading, if you are not already
243 using clang 3.5.0 or higher.
246 The hpt27xx, hptmv, hptnr, and hptrr drivers have been removed from
247 GENERIC. They are available as modules and can be loaded by adding
248 to /boot/loader.conf hpt27xx_load="YES", hptmv_load="YES",
249 hptnr_load="YES", or hptrr_load="YES", respectively.
252 ntpd no longer by default locks its pages in memory, allowing them
253 to be paged out by the kernel. Use rlimit memlock to restore
254 historic BSD behaviour. For example, add "rlimit memlock 32"
255 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
258 Several of ping6's options have been renamed for better consistency
259 with ping. If you use any of -ARWXaghmrtwx, you must update your
260 scripts. See ping6(8) for details.
263 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
264 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
265 been removed from mount_fusefs(8). You can safely remove them from
266 your scripts, because they had no effect.
268 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
269 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
270 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
271 sysctls have been removed. If you felt the need to set any of them to
272 a non-default value, please tell asomers@FreeBSD.org why.
275 Default permissions on the /var/account/acct file (and copies of it
276 rotated by periodic daily scripts) are changed from 0644 to 0640
277 because the file contains sensitive information that should not be
278 world-readable. If the /var/account directory must be created by
279 rc.d/accounting, the mode used is now 0750. Admins who use the
280 accounting feature are encouraged to change the mode of an existing
281 /var/account directory to 0750 or 0700.
284 Entropy collection and the /dev/random device are no longer optional
285 components. The "device random" option has been removed.
286 Implementations of distilling algorithms can still be made loadable
287 with "options RANDOM_LOADABLE" (e.g., random_fortuna.ko).
290 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
291 been upgraded to 8.0.1. Please see the 20141231 entry below for
292 information about prerequisites and upgrading, if you are not already
293 using clang 3.5.0 or higher.
296 A fix was applied to i386 kernel modules to avoid panics with
297 dpcpu or vnet. Users need to recompile i386 kernel modules
298 having pcpu or vnet sections or they will refuse to load.
301 User-wired pages now have their own counter,
302 vm.stats.vm.v_user_wire_count. The vm.max_wired sysctl was renamed
303 to vm.max_user_wired and changed from an unsigned int to an unsigned
304 long. bhyve VMs wired with the -S are now subject to the user
305 wiring limit; the vm.max_user_wired sysctl may need to be tuned to
306 avoid running into the limit.
309 The IPSEC option has been removed from GENERIC. Users requiring
310 ipsec(4) must now load the ipsec(4) kernel module.
313 The tap(4) driver has been folded into tun(4), and the module has been
314 renamed to tuntap. You should update any kld_list="if_tap" or
315 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
316 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
317 module instead, and "device tap" or "device tun" entries in kernel
318 config files to select the tuntap device instead.
321 The following knobs have been added related to tradeoffs between
322 safe use of the random device and availability in the absence of
325 kern.random.initial_seeding.bypass_before_seeding: tunable; set
326 non-zero to bypass the random device prior to seeding, or zero to
327 block random requests until the random device is initially seeded.
328 For now, set to 1 (unsafe) by default to restore pre-r346250 boot
329 availability properties.
331 kern.random.initial_seeding.read_random_bypassed_before_seeding:
332 read-only diagnostic sysctl that is set when bypass is enabled and
333 read_random(9) is bypassed, to enable programmatic handling of this
334 initial condition, if desired.
336 kern.random.initial_seeding.arc4random_bypassed_before_seeding:
337 Similar to the above, but for for arc4random(9) initial seeding.
339 kern.random.initial_seeding.disable_bypass_warnings: tunable; set
340 non-zero to disable warnings in dmesg when the same conditions are
341 met as for the diagnostic sysctls above. Defaults to zero, i.e.,
342 produce warnings in dmesg when the conditions are met.
345 The loadable random module KPI has changed; the random_infra_init()
346 routine now requires a 3rd function pointer for a bool (*)(void)
347 method that returns true if the random device is seeded (and
348 therefore unblocked).
351 r345895 reverts r320698. This implies that an nfsuserd(8) daemon
352 built from head sources between r320757 (July 6, 2017) and
353 r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
354 is added to the command line.
355 nfsuserd daemons built from head sources that are post-r338192 are
356 not affected and should continue to work.
359 The fuse(4) module has been renamed to fusefs(4) for consistency with
360 other filesystems. You should update any kld_load="fuse" entries in
361 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
362 "options FUSE" entries in kernel config files.
365 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
366 8.0.0. Please see the 20141231 entry below for information about
367 prerequisites and upgrading, if you are not already using clang 3.5.0
371 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
372 compiled into your custom kernel, add 'device xz' statement to the
376 drm and drm2 have been removed from the tree. Please see
377 https://wiki.freebsd.org/Graphics for the latest information on
378 migrating to the drm ports.
381 Iflib is no longer unconditionally compiled into the kernel. Drivers
382 using iflib and statically compiled into the kernel, now require
383 the 'device iflib' config option. For the same drivers loaded as
384 modules on kernels not having 'device iflib', the iflib.ko module
385 is loaded automatically.
388 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
389 options no longer exist since r343219 and r343427 respectively;
390 nothing uses them, so they should be just removed from custom
394 r342635 changes the way efibootmgr(8) works by requiring users to add
395 the -b (bootnum) parameter for commands where the bootnum was previously
396 specified with each option. For example 'efibootmgr -B 0001' is now
397 'efibootmgr -B -b 0001'.
400 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
401 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
402 servers that have vfs.nfsd.nfs_privport set will only allow mounts
403 from clients using a reserved port#. Since both the FreeBSD and Linux
404 NFSv4 clients use reserved port#s by default, this should not affect
408 The XLP config has been removed. We can't support 64-bit atomics in this
409 kernel because it is running in 32-bit mode. XLP users must transition
410 to running a 64-bit kernel (XLP64 or XLPN32).
412 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
413 the preferred emulator today and we don't need two different ones.
415 The old sibyte / swarm / Broadcom BCM1250 support has been
416 removed from the mips port.
419 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
420 7.0.1. Please see the 20141231 entry below for information about
421 prerequisites and upgrading, if you are not already using clang 3.5.0
425 Remove the timed and netdate programs from the base tree. Setting
426 the time with these daemons has been obsolete for over a decade.
429 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
430 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
431 it produces broken binaries when ifuncs are in use. Users needing
432 GNU ld should install the binutils port or package.
435 The BSD crtbegin and crtend code has been enabled by default. It has
436 had extensive testing on amd64, arm64, and i386. It can be disabled
437 by building a world with -DWITHOUT_BSD_CRTBEGIN.
440 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
441 has been converted to a port (misc/ctm) and will be removed from
442 FreeBSD-13. It is available as a package (ctm) for all supported
446 The default newsyslog.conf(5) file has been changed to only include
447 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
448 the filenames end in '.conf' and do not begin with a '.'.
450 You should check the configuration files in these two directories match
451 this naming convention. You can verify which configuration files are
452 being included using the command:
456 Ports for the DRM modules have been simplified. Now, amd64 users should
457 just install the drm-kmod port. All others should install
460 Graphics hardware that's newer than about 2010 usually works with
461 drm-kmod. For hardware older than 2013, however, some users will need
462 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
463 than 2008 usually only works in drm-legacy-kmod. The graphics team can
464 only commit to hardware made since 2013 due to the complexity of the
465 market and difficulty to test all the older cards effectively. If you
466 have hardware supported by drm-kmod, you are strongly encouraged to use
467 that as you will get better support.
469 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
470 elsewhere, the drm and drm2 modules will be eliminated from the src base
471 soon (with a limited exception for arm). Please update to the package
472 asap and report any issues to x11@freebsd.org.
474 Generally, anybody using the drm*-kmod packages should add
475 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
476 cross-threading surprises, especially with automatic driver
477 loading from X11 startup. These will become the defaults in 13-current
481 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
482 custom kernel and module loading configuration files must be updated
483 accordingly. Moreover, interfaces previous presented as ixlvN to the
484 system are now exposed as iavfN and network configuration files must
485 be adjusted as necessary.
488 OpenSSL has been updated to version 1.1.1. This update included
489 additional various API changes throughout the base system. It is
490 important to rebuild third-party software after upgrading. The value
491 of __FreeBSD_version has been bumped accordingly.
494 The legacy DRM modules and drivers have now been added to the loader's
495 module blacklist, in favor of loading them with kld_list in rc.conf(5).
496 The module blacklist may be overridden with the loader.conf(5)
497 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
501 The cam(4) based nda(4) driver will be used over nvd(4) by default on
502 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
503 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
504 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
508 Reproducible build mode is now on by default, in preparation for
509 FreeBSD 12.0. This eliminates build metadata such as the user,
510 host, and time from the kernel (and uname), unless the working tree
511 corresponds to a modified checkout from a version control system.
512 The previous behavior can be obtained by setting the /etc/src.conf
513 knob WITHOUT_REPRODUCIBLE_BUILD.
516 The Yarrow CSPRNG has been removed from the kernel as it has not been
517 supported by its designers since at least 2003. Fortuna has been the
518 default since FreeBSD-11.
521 devctl freeze/thaw have gone into the tree, the rc scripts have been
522 updated to use them and devmatch has been changed. You should update
523 kernel, userland and rc scripts all at the same time.
526 The default interpreter has been switched from 4th to Lua.
527 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
528 interpreter. If you have custom FORTH code you will need to set
529 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
530 src.conf for the build. This will create default hard links between
531 loader and loader_4th instead of loader and loader_lua, the new default.
532 If you are using UEFI it will create the proper hard link to loader.efi.
534 bhyve uses userboot.so. It remains 4th-only until some issues are solved
535 regarding coexisting with multiple versions of FreeBSD are resolved.
538 ls(1) now respects the COLORTERM environment variable used in other
539 systems and software to indicate that a colored terminal is both
540 supported and desired. If ls(1) is suddenly emitting colors, they may
541 be disabled again by either removing the unwanted COLORTERM from your
542 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
543 may not be observed in a future release.
546 The default pager for most commands has been changed to "less". To
547 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
551 The jedec_ts(4) driver has been removed. A superset of its functionality
552 is available in the jedec_dimm(4) driver, and the manpage for that
553 driver includes migration instructions. If you have "device jedec_ts"
554 in your kernel configuration file, it must be removed.
557 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
558 This should have no effect if the kernel is booted via BIOS/legacy boot.
559 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
560 has a buggy firmware that prevents a successful boot due to use of
564 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
565 support has been removed from the tree. These ports were
566 obsolete and/or known to be broken for many years.
569 loader.efi has been augmented to participate more fully in the
570 UEFI boot manager protocol. loader.efi will now look at the
571 BootXXXX environment variable to determine if a specific kernel
572 or root partition was specified. XXXX is derived from BootCurrent.
573 efibootmgr(8) manages these standard UEFI variables.
576 zfsloader's functionality has now been folded into loader.
577 zfsloader is no longer necessary once you've updated your
578 boot blocks. For a transition period, we will install a
579 hardlink for zfsloader to loader to allow a smooth transition
580 until the boot blocks can be updated (hard link because old
581 zfs boot blocks don't understand symlinks).
584 ARM64 now have efifb support, if you want to have serial console
585 on your arm64 board when an screen is connected and the bootloader
586 setup a frame buffer for us to use, just add :
590 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
591 an screen connected as the firmware will setup a frame buffer are that
592 u-boot will expose as an EFI frame buffer.
595 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
596 or take steps to update /etc/passwd before doing installworld on
597 existing systems. Do not skip the "mergemaster -Fp" step before
598 installworld, as described in the update procedures near the bottom
599 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
600 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
601 the ntp config file contain options that change file/dir locations.
602 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
603 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
604 taking steps to ensure that all required files/dirs are accessible
608 Big endian arm support has been removed.
611 The static environment setup in kernel configs is no longer mutually
612 exclusive with the loader(8) environment by default. In order to
613 restore the previous default behavior of disabling the loader(8)
614 environment if a static environment is present, you must specify
615 loader_env.disabled=1 in the static environment.
618 The ABI of syscalls used by management tools like sockstat and
619 netstat has been broken to allow 32-bit binaries to work on
620 64-bit kernels without modification. These programs will need
621 to match the kernel in order to function. External programs may
622 require minor modifications to accommodate a change of type in
623 structures from pointers to 64-bit virtual addresses.
626 On i386 and amd64 atomics are now inlined. Out of tree modules using
627 atomics will need to be rebuilt.
630 The '%I' format in the kern.corefile sysctl limits the number of
631 core files that a process can generate to the number stored in the
632 debug.ncores sysctl. The '%I' format is replaced by the single digit
633 index. Previously, if all indexes were taken the kernel would overwrite
634 only a core file with the highest index in a filename.
635 Currently the system will create a new core file if there is a free
636 index or if all slots are taken it will overwrite the oldest one.
639 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
640 6.0.1. Please see the 20141231 entry below for information about
641 prerequisites and upgrading, if you are not already using clang 3.5.0
645 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
646 needed to be changed to work with it. This change was made with r335763
647 and requires a mergemaster / etcupdate / etc to update the installed
651 r334930 changed the interface between the NFS modules, so they all
652 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
655 As of r334391 lld is the default amd64 system linker; it is installed
656 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
660 The kernel / userland interface for devinfo changed, so you'll
661 need a new kernel and userland as a pair for it to work (rebuilding
662 lib/libdevinfo is all that's required). devinfo and devmatch will
663 not work, but everything else will when there's a mismatch.
666 The on-disk format for hwpmc callchain records has changed to include
667 threadid corresponding to a given record. This changes the field offsets
668 and thus requires that libpmcstat be rebuilt before using a kernel
672 The vxge(4) driver has been removed. This driver was introduced into
673 HEAD one week before the Exar left the Ethernet market and is not
674 known to be used. If you have device vxge in your kernel config file
678 The amd64 kernel now requires a ld that supports ifunc to produce a
679 working kernel, either lld or a newer binutils. lld is built by default
680 on amd64, and the 'buildkernel' target uses it automatically. However,
681 it is not the default linker, so building the kernel the traditional
682 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
683 binutils port/package). lld will soon be default, and this requirement
686 NOTE: As of r334391 lld is the default system linker on amd64, and no
687 workaround is necessary.
690 The nxge(4) driver has been removed. This driver was for PCI-X 10g
691 cards made by s2io/Neterion. The company was acquired by Exar and
692 no longer sells or supports Ethernet products. If you have device
693 nxge in your kernel config file it must be removed.
696 The tz database (tzdb) has been updated to 2018e. This version more
697 correctly models time stamps in time zones with negative DST such as
698 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
699 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
700 time zone abbreviations and the tm_isdst flag.
703 The ixgb(4) driver has been removed. This driver was for an early and
704 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
705 quickly shifted to the long lived ixgbe family. If you have device
706 ixgb in your kernel config file it must be removed.
709 The lmc(4) driver has been removed. This was a WAN interface
710 card that was already reportedly rare in 2003, and had an ambiguous
711 license. If you have device lmc in your kernel config file it must
715 Support for Arcnet networks has been removed. If you have device
716 arcnet or device cm in your kernel config file they must be
720 Support for FDDI networks has been removed. If you have device
721 fddi or device fpa in your kernel config file they must be
725 In addition to supporting RFC 3164 formatted messages, the
726 syslogd(8) service is now capable of parsing RFC 5424 formatted
727 log messages. The main benefit of using RFC 5424 is that clients
728 may now send log messages with timestamps containing year numbers,
729 microseconds and time zone offsets.
731 Similarly, the syslog(3) C library function has been altered to
732 send RFC 5424 formatted messages to the local system logging
733 daemon. On systems using syslogd(8), this change should have no
734 negative impact, as long as syslogd(8) and the C library are
735 updated at the same time. On systems using a different system
736 logging daemon, it may be necessary to make configuration
737 adjustments, depending on the software used.
739 When using syslog-ng, add the 'syslog-protocol' flag to local
740 input sources to enable parsing of RFC 5424 formatted messages:
743 unix-dgram("/var/run/log" flags(syslog-protocol));
746 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
747 of the 'imuxsock' module to let messages be processed by the
748 regular RFC 3164/5424 parsing pipeline:
750 module(load="imuxsock" SysSock.UseSpecialParser="off")
752 Do note that these changes only affect communication between local
753 applications and syslogd(8). The format that syslogd(8) uses to
754 store messages on disk or forward messages to other systems
755 remains unchanged. syslogd(8) still uses RFC 3164 for these
756 purposes. Options to customize this behaviour will be added in the
757 future. Utilities that process log files stored in /var/log are
758 thus expected to continue to function as before.
760 __FreeBSD_version has been incremented to 1200061 to denote this
764 Support for token ring networks has been removed. If you
765 have "device token" in your kernel config you should remove
766 it. No device drivers supported token ring.
769 makefs was modified to be able to tag ISO9660 El Torito boot catalog
770 entries as EFI instead of overloading the i386 tag as done previously.
771 The amd64 mkisoimages.sh script used to build amd64 ISO images for
772 release was updated to use this. This may mean that makefs must be
773 updated before "make cdrom" can be run in the release directory. This
774 should be as simple as:
776 $ cd $SRCDIR/usr.sbin/makefs
777 $ make depend all install
780 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
781 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
782 Co-existence for the transition period will come shortly. Booting is a
783 complex environment and test coverage for Lua-enabled loaders has been
784 thin, so it would be prudent to assume it might not work and make
785 provisions for backup boot methods.
788 devmatch functionality has been turned on in devd. It will automatically
789 load drivers for unattached devices. This may cause unexpected drivers
790 to be loaded. Please report any problems to current@ and
794 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
795 6.0.0. Please see the 20141231 entry below for information about
796 prerequisites and upgrading, if you are not already using clang 3.5.0
800 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
801 This means it is used to link the kernel and userland libraries and
802 executables, but is not yet installed as /usr/bin/ld by default.
804 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
805 WITHOUT_LLD_BOOTSTRAP=yes
808 On i386, pmtimer has been removed. Its functionality has been folded
809 into apm. It was a no-op on ACPI in current for a while now (but was
810 still needed on i386 in FreeBSD 11 and earlier). Users may need to
811 remove it from kernel config files.
814 The use of RSS hash from the network card aka flowid has been
815 disabled by default for lagg(4) as it's currently incompatible with
816 the lacp and loadbalance protocols.
818 This can be re-enabled by setting the following in loader.conf:
819 net.link.lagg.default_use_flowid="1"
822 The SW_WATCHDOG option is no longer necessary to enable the
823 hardclock-based software watchdog if no hardware watchdog is
824 configured. As before, SW_WATCHDOG will cause the software
825 watchdog to be enabled even if a hardware watchdog is configured.
828 r326887 fixes the issue described in the 20171214 UPDATING entry.
829 r326888 flips the switch back to building GELI support always.
832 r362593 broke ZFS + GELI support for reasons unknown. However,
833 it also broke ZFS support generally, so GELI has been turned off
834 by default as the lesser evil in r326857. If you boot off ZFS and/or
835 GELI, it might not be a good time to update.
838 PowerPC users must update loader(8) by rebuilding world before
839 installing a new kernel, as the protocol connecting them has
840 changed. Without the update, loader metadata will not be passed
841 successfully to the kernel and users will have to enter their
842 root partition at the kernel mountroot prompt to continue booting.
843 Newer versions of loader can boot old kernels without issue.
846 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
847 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
848 to WITH/OUT_LOADER_GELI.
851 The naive and non-compliant support of posix_fallocate(2) in ZFS
852 has been removed as of r325320. The system call now returns EINVAL
853 when used on a ZFS file. Although the new behavior complies with the
854 standard, some consumers are not prepared to cope with it.
855 One known victim is lld prior to r325420.
858 Building in a FreeBSD src checkout will automatically create object
859 directories now rather than store files in the current directory if
860 'make obj' was not ran. Calling 'make obj' is no longer necessary.
861 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
862 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
866 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
867 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
868 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
869 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
870 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
871 The UNIFIED_OBJDIR option is a transitional feature that will be
872 removed for 12.0 release; please migrate to the new format for any
873 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
874 than hardcoding paths.
877 The native-xtools target no longer installs the files by default to the
878 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
879 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
882 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
883 options are changing from controlling the build if defined / undefined
884 to controlling the build with explicit 'yes' or 'no' values. They will
885 shift to WITH/WITHOUT options to match other options in the system.
888 libstand has turned into a private library for sys/boot use only.
889 It is no longer supported as a public interface outside of sys/boot.
892 The arm port has split armv6 into armv6 and armv7. armv7 is now
893 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
894 and are running a kernel from before r324363, you will need to add
895 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
898 When building multiple kernels using KERNCONF, non-existent KERNCONF
899 files will produce an error and buildkernel will fail. Previously
900 missing KERNCONF files silently failed giving no indication as to
901 why, only to subsequently discover during installkernel that the
902 desired kernel was never built in the first place.
905 The default serial number format for CTL LUNs has changed. This will
906 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
907 or iSCSI clients care about their LUNs' serial numbers. Users who
908 require serial number stability should hardcode serial numbers in
912 For 32-bit arm compiled for hard-float support, soft-floating point
913 binaries now always get their shared libraries from
914 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
915 /usr/libsoft also existed). Only users with a hard-float ld.so, but
916 soft-float everything else should be affected.
919 The geli password typed at boot is now hidden. To restore the previous
920 behavior, see geli(8) for configuration options.
923 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
924 sysctl values. Minor nit, but requires a rebuild of both world/kernel
928 "make check" behavior (made in ^/head@r295380) has been changed to
929 execute from a limited sandbox, as opposed to executing from
933 - The "beforecheck" and "aftercheck" targets are now specified.
934 - ${CHECKDIR} (added in commit noted above) has been removed.
935 - Legacy behavior can be enabled by setting
936 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
938 If the limited sandbox mode is enabled, "make check" will execute
939 "make distribution", then install, execute the tests, and clean up the
940 sandbox if successful.
942 The "make distribution" and "make install" targets are typically run as
943 root to set appropriate permissions and ownership at installation time.
944 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
945 environment if executing "make check" with limited sandbox mode using
946 an unprivileged user.
949 Since the switch to GPT disk labels, fsck for UFS/FFS has been
950 unable to automatically find alternate superblocks. As of r322297,
951 the information needed to find alternate superblocks has been
952 moved to the end of the area reserved for the boot block.
953 Filesystems created with a newfs of this vintage or later
954 will create the recovery information. If you have a filesystem
955 created prior to this change and wish to have a recovery block
956 created for your filesystem, you can do so by running fsck in
957 foreground mode (i.e., do not use the -p or -y options). As it
958 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
959 to which you should answer yes.
962 As of r321665, an NFSv4 server configuration that services
963 Kerberos mounts or clients that do not support the uid/gid in
964 owner/owner_group string capability, must explicitly enable
965 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
966 machine's /etc/rc.conf file.
969 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
970 Please see the 20141231 entry below for information about prerequisites
971 and upgrading, if you are not already using clang 3.5.0 or higher.
974 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
975 r-commands (rlogin, rsh, etc.) to be built with the base system.
978 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
979 a very major ABI incompatible change, so users of FreeBSD/powerpc must
980 be careful when performing source upgrades. It is best to run
981 'make installworld' from an alternate root system, either a live
982 CD/memory stick, or a temporary root partition. Additionally, all ports
983 must be recompiled. powerpc64 is largely unaffected, except in the case
984 of 32-bit compatibility. All 32-bit binaries will be affected.
987 Forward compatibility for the "ino64" project have been committed. This
988 will allow most new binaries to run on older kernels in a limited
989 fashion. This prevents many of the common foot-shooting actions in the
990 upgrade as well as the limited ability to roll back the kernel across
991 the ino64 upgrade. Complicated use cases may not work properly, though
992 enough simpler ones work to allow recovery in most situations.
995 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
996 if you require the GPL compiler.
999 The internal ABI used for communication between the NFS kernel modules
1000 was changed by r320085, so __FreeBSD_version was bumped to
1001 ensure all the NFS related modules are updated together.
1004 The ABI of struct event was changed by extending the data
1005 member to 64bit and adding ext fields. For upgrade, same
1006 precautions as for the entry 20170523 "ino64" must be
1010 The GNU roff toolchain has been removed from base. To render manpages
1011 which are not supported by mandoc(1), man(1) can fallback on GNU roff
1012 from ports (and recommends to install it).
1013 To render roff(7) documents, consider using GNU roff from ports or the
1014 heirloom doctools roff toolchain from ports via pkg install groff or
1015 via pkg install heirloom-doctools.
1018 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
1019 smaller runtime footprint builds. This is useful for embedded systems
1020 which only require one chipset support.
1022 If you load it as a module, make sure this is in /boot/loader.conf:
1026 This will load the HAL, all chip/RF backends and if_ath_pci.
1027 If you have if_ath_pci in /boot/loader.conf, ensure it is after
1028 if_ath or it will not load any HAL chipset support.
1030 If you want to selectively load things (eg on ye cheape ARM/MIPS
1031 platforms where RAM is at a premium) you should:
1034 * load the chip modules in question
1035 * load ath_rate, ath_dfs
1037 * load if_ath_pci and/or if_ath_ahb depending upon your particular
1038 bus bind type - this is where probe/attach is done.
1040 For further comments/feedback, poke adrian@ .
1043 The "ino64" 64-bit inode project has been committed, which extends
1044 a number of types to 64 bits. Upgrading in place requires care and
1045 adherence to the documented upgrade procedure.
1047 If using a custom kernel configuration ensure that the
1048 COMPAT_FREEBSD11 option is included (as during the upgrade the
1049 system will be running the ino64 kernel with the existing world).
1051 For the safest in-place upgrade begin by removing previous build
1052 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full
1053 procedure documented below under the heading "To rebuild everything and
1054 install it on the current system." Specifically, a reboot is required
1055 after installing the new kernel before installing world. While an
1056 installworld normally works by accident from multiuser after rebooting
1057 the proper kernel, there are many cases where this will fail across this
1058 upgrade and installworld from single user is required.
1061 The NATM framework including the en(4), fatm(4), hatm(4), and
1062 patm(4) devices has been removed. Consumers should plan a
1063 migration before the end-of-life date for FreeBSD 11.
1066 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
1067 diff has not been implemented, if those are needed a newer version of
1068 GNU diff is available via the diffutils package under the gdiff name.
1071 As of r316810 for ipfilter, keep frags is no longer assumed when
1072 keep state is specified in a rule. r316810 aligns ipfilter with
1073 documentation in man pages separating keep frags from keep state.
1074 This allows keep state to be specified without forcing keep frags
1075 and allows keep frags to be specified independently of keep state.
1076 To maintain previous behaviour, also specify keep frags with
1077 keep state (as documented in ipf.conf.5).
1080 arm64 builds now use the base system LLD 4.0.0 linker by default,
1081 instead of requiring that the aarch64-binutils port or package be
1082 installed. To continue using aarch64-binutils, set
1083 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
1086 The UDP optimization in entry 20160818 that added the sysctl
1087 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
1088 packets will no longer be treated as L3 broadcast packets.
1091 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
1092 use any explicitly assigned loopback address available in the jail
1093 instead of using the first assigned address of the jail.
1096 The ctl.ko module no longer implements the iSCSI target frontend:
1097 cfiscsi.ko does instead.
1099 If building cfiscsi.ko as a kernel module, the module can be loaded
1100 via one of the following methods:
1101 - `cfiscsi_load="YES"` in loader.conf(5).
1102 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
1103 - ctladm(8)/ctld(8), when compiled with iSCSI support
1104 (`WITH_ISCSI=yes` in src.conf(5))
1106 Please see cfiscsi(4) for more details.
1109 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
1110 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
1111 same source (previously, the dependency of mmcsd.ko on mmc.ko was
1112 missing, but mmcsd.ko now will refuse to load if it is incompatible
1116 The syntax of ipfw(8) named states was changed to avoid ambiguity.
1117 If you have used named states in the firewall rules, you need to modify
1118 them after installworld and before rebooting. Now named states must
1119 be prefixed with colon.
1122 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
1123 removed as the userland we provide cannot use them. The KMS version
1124 (sys/dev/drm2) supports the same hardware.
1127 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
1128 Please see the 20141231 entry below for information about prerequisites
1129 and upgrading, if you are not already using clang 3.5.0 or higher.
1132 The code that provides support for ZFS .zfs/ directory functionality
1133 has been reimplemented. It's not possible now to create a snapshot
1134 by mkdir under .zfs/snapshot/. That should be the only user visible
1138 EISA bus support has been removed. The WITH_EISA option is no longer
1142 MCA bus support has been removed.
1145 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
1146 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
1149 The EM_MULTIQUEUE kernel configuration option is deprecated now that
1150 the em(4) driver conforms to iflib specifications.
1153 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
1154 IFLIB. If you have a custom kernel configuration that excludes em(4)
1155 but you use igb(4), you need to re-add em(4) to your custom
1159 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
1160 Please see the 20141231 entry below for information about prerequisites
1161 and upgrading, if you are not already using clang 3.5.0 or higher.
1164 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
1165 Please see the 20141231 entry below for information about prerequisites
1166 and upgrading, if you are not already using clang 3.5.0 or higher.
1169 The layout of the pmap structure has changed for powerpc to put the pmap
1170 statistics at the front for all CPU variations. libkvm(3) and all tools
1171 that link against it need to be recompiled.
1174 isl(4) and cyapa(4) drivers now require a new driver,
1175 chromebook_platform(4), to work properly on Chromebook-class hardware.
1176 On other types of hardware the drivers may need to be configured using
1177 device hints. Please see the corresponding manual pages for details.
1180 The urtwn(4) driver was merged into rtwn(4) and now consists of
1181 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
1183 Also, firmware for RTL8188CE was renamed due to possible name
1184 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
1187 GNU rcs has been removed from base. It is available as packages:
1188 - rcs: Latest GPLv3 GNU rcs version.
1189 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
1193 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
1194 modules now requires that the kernel configuration contain the
1195 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
1198 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
1199 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
1202 Relocatable object files with the extension of .So have been renamed
1203 to use an extension of .pico instead. The purpose of this change is
1204 to avoid a name clash with shared libraries on case-insensitive file
1205 systems. On those file systems, foo.So is the same file as foo.so.
1208 GNU rcs has been turned off by default. It can (temporarily) be built
1209 again by adding WITH_RCS knob in src.conf.
1210 Otherwise, GNU rcs is available from packages:
1211 - rcs: Latest GPLv3 GNU rcs version.
1212 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
1215 The backup_uses_rcs functionality has been removed from rc.subr.
1218 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
1219 two separate components, QUEUE_MACRO_DEBUG_TRACE and
1220 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
1221 QUEUE_MACRO_DEBUG behavior.
1224 r304787 changed some ioctl interfaces between the iSCSI userspace
1225 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1226 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1230 The UDP receive code has been updated to only treat incoming UDP
1231 packets that were addressed to an L2 broadcast address as L3
1232 broadcast packets. It is not expected that this will affect any
1233 standards-conforming UDP application. The new behaviour can be
1234 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1238 Remove the openbsd_poll system call.
1239 __FreeBSD_version has been bumped because of this.
1242 The stable/11 branch has been created from head@r302406.
1245 The libc stub for the pipe(2) system call has been replaced with
1246 a wrapper that calls the pipe2(2) system call and the pipe(2)
1247 system call is now only implemented by the kernels that include
1248 "options COMPAT_FREEBSD10" in their config file (this is the
1249 default). Users should ensure that this option is enabled in
1250 their kernel or upgrade userspace to r302092 before upgrading their
1254 CAM will now strip leading spaces from SCSI disks' serial numbers.
1255 This will affect users who create UFS filesystems on SCSI disks using
1256 those disk's diskid device nodes. For example, if /etc/fstab
1257 previously contained a line like
1258 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
1259 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
1260 transforms like gmirror may also be affected. ZFS users should
1264 The bitstring(3) API has been updated with new functionality and
1265 improved performance. But it is binary-incompatible with the old API.
1266 Objects built with the new headers may not be linked against objects
1267 built with the old headers.
1270 The brk and sbrk functions have been removed from libc on arm64.
1271 Binutils from ports has been updated to not link to these
1272 functions and should be updated to the latest version before
1273 installing a new libc.
1276 The armv6 port now defaults to hard float ABI. Limited support
1277 for running both hardfloat and soft float on the same system
1278 is available using the libraries installed with -DWITH_LIBSOFT.
1279 This has only been tested as an upgrade path for installworld
1280 and packages may fail or need manual intervention to run. New
1281 packages will be needed.
1283 To update an existing self-hosted armv6hf system, you must add
1284 TARGET_ARCH=armv6 on the make command line for both the build
1285 and the install steps.
1288 Kernel modules compiled outside of a kernel build now default to
1289 installing to /boot/modules instead of /boot/kernel. Many kernel
1290 modules built this way (such as those in ports) already overrode
1291 KMODDIR explicitly to install into /boot/modules. However,
1292 manually building and installing a module from /sys/modules will
1293 now install to /boot/modules instead of /boot/kernel.
1296 The CAM I/O scheduler has been committed to the kernel. There should be
1297 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1298 list of known rogues that claim support for this but actually corrupt
1299 data is believed to be complete, be on the lookout for data
1300 corruption. The known rogue list is believed to be complete:
1302 o Crucial MX100, M550 drives with MU01 firmware.
1303 o Micron M510 and M550 drives with MU01 firmware.
1304 o Micron M500 prior to MU07 firmware
1305 o Samsung 830, 840, and 850 all firmwares
1306 o FCCT M500 all firmwares
1308 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1309 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1310 updated firmware. Black listed drives will work correctly because these
1311 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1312 this list is the same as found in Linux, it's believed there are no
1313 other rogues in the market place. All other models from the above
1316 To be safe, if you are at all concerned, you can quirk each of your
1317 drives to prevent NCQ from being sent by setting:
1318 kern.cam.ada.X.quirks="0x2"
1319 in loader.conf. If the drive requires the 4k sector quirk, set the
1320 quirks entry to 0x3.
1323 The FAST_DEPEND build option has been removed and its functionality is
1324 now the one true way. The old mkdep(1) style of 'make depend' has
1325 been removed. See 20160311 for further details.
1328 Resource range types have grown from unsigned long to uintmax_t. All
1329 drivers, and anything using libdevinfo, need to be recompiled.
1332 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1333 builds. It no longer runs mkdep(1) during 'make depend', and the
1334 'make depend' stage can safely be skipped now as it is auto ran
1335 when building 'make all' and will generate all SRCS and DPSRCS before
1336 building anything else. Dependencies are gathered at compile time with
1337 -MF flags kept in separate .depend files per object file. Users should
1338 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1339 stale .depend files.
1342 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1343 kernel modules. Therefore, if you load any kernel modules at boot time,
1344 please install the boot loaders after you install the kernel, but before
1348 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1349 make installkernel KERNCONF=YOUR_KERNEL_HERE
1350 make -C sys/boot install
1351 <reboot in single user>
1353 Then follow the usual steps, described in the General Notes section,
1357 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1358 see the 20141231 entry below for information about prerequisites and
1359 upgrading, if you are not already using clang 3.5.0 or higher.
1362 The AIO subsystem is now a standard part of the kernel. The
1363 VFS_AIO kernel option and aio.ko kernel module have been removed.
1364 Due to stability concerns, asynchronous I/O requests are only
1365 permitted on sockets and raw disks by default. To enable
1366 asynchronous I/O requests on all file types, set the
1367 vfs.aio.enable_unsafe sysctl to a non-zero value.
1370 The ELF object manipulation tool objcopy is now provided by the
1371 ELF Tool Chain project rather than by GNU binutils. It should be a
1372 drop-in replacement, with the addition of arm64 support. The
1373 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1374 to obtain the GNU version if necessary.
1377 Building ZFS pools on top of zvols is prohibited by default. That
1378 feature has never worked safely; it's always been prone to deadlocks.
1379 Using a zvol as the backing store for a VM guest's virtual disk will
1380 still work, even if the guest is using ZFS. Legacy behavior can be
1381 restored by setting vfs.zfs.vol.recursive=1.
1384 The NONE and HPN patches has been removed from OpenSSH. They are
1385 still available in the security/openssh-portable port.
1388 With the addition of ypldap(8), a new _ypldap user is now required
1389 during installworld. "mergemaster -p" can be used to add the user
1390 prior to installworld, as documented in the handbook.
1393 The tftp loader (pxeboot) now uses the option root-path directive. As a
1394 consequence it no longer looks for a pxeboot.4th file on the tftp
1395 server. Instead it uses the regular /boot infrastructure as with the
1399 The code to start recording plug and play data into the modules has
1400 been committed. While the old tools will properly build a new kernel,
1401 a number of warnings about "unknown metadata record 4" will be produced
1402 for an older kldxref. To avoid such warnings, make sure to rebuild
1403 the kernel toolchain (or world). Make sure that you have r292078 or
1404 later when trying to build 292077 or later before rebuilding.
1407 Debug data files are now built by default with 'make buildworld' and
1408 installed with 'make installworld'. This facilitates debugging but
1409 requires more disk space both during the build and for the installed
1410 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1414 r291527 changed the internal interface between the nfsd.ko and
1415 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1416 __FreeBSD_version has been bumped because of this.
1419 Add support for unicode collation strings leads to a change of
1420 order of files listed by ls(1) for example. To get back to the old
1421 behaviour, set LC_COLLATE environment variable to "C".
1423 Databases administrators will need to reindex their databases given
1424 collation results will be different.
1426 Due to a bug in install(1) it is recommended to remove the ancient
1427 locales before running make installworld.
1429 rm -rf /usr/share/locale/*
1432 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1433 libcrypto.so.7 or libssl.so.7 must be recompiled.
1436 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1437 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1438 should be replaced with isp_2400 and isp_2500 modules respectively.
1441 The build previously allowed using 'make -n' to not recurse into
1442 sub-directories while showing what commands would be executed, and
1443 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1444 and 'make -N' will not.
1447 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1448 and etcupdate will now use this file. A custom sendmail.cf is now
1449 updated via this mechanism rather than via installworld. If you had
1450 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1451 want to remove the exclusion or change it to "always install".
1452 /etc/mail/sendmail.cf is now managed the same way regardless of
1453 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1454 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1457 Compatibility shims for legacy ATA device names have been removed.
1458 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1459 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1460 environment variables, /dev/ad* and /dev/ar* symbolic links.
1463 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1464 Please see the 20141231 entry below for information about prerequisites
1465 and upgrading, if you are not already using clang 3.5.0 or higher.
1468 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1469 and renamed from .symbols to .debug. This reduces the size requirements
1470 on the boot partition or file system and provides consistency with
1471 userland debug files.
1473 When using the supported kernel installation method the
1474 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1475 as is done with /boot/kernel.
1477 Developers wishing to maintain the historical behavior of installing
1478 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1481 The wireless drivers had undergone changes that remove the 'parent
1482 interface' from the ifconfig -l output. The rc.d network scripts
1483 used to check presence of a parent interface in the list, so old
1484 scripts would fail to start wireless networking. Thus, etcupdate(3)
1485 or mergemaster(8) run is required after kernel update, to update your
1486 rc.d scripts in /etc.
1489 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1490 These configurations are now automatically interpreted as
1491 'scrub fragment reassemble'.
1494 Kernel-loadable modules for the random(4) device are back. To use
1495 them, the kernel must have
1498 options RANDOM_LOADABLE
1500 kldload(8) can then be used to load random_fortuna.ko
1501 or random_yarrow.ko. Please note that due to the indirect
1502 function calls that the loadable modules need to provide,
1503 the build-in variants will be slightly more efficient.
1505 The random(4) kernel option RANDOM_DUMMY has been retired due to
1506 unpopularity. It was not all that useful anyway.
1509 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1510 Control over building the ELF Tool Chain tools is now provided by
1511 the WITHOUT_TOOLCHAIN knob.
1514 The polarity of Pulse Per Second (PPS) capture events with the
1515 uart(4) driver has been corrected. Prior to this change the PPS
1516 "assert" event corresponded to the trailing edge of a positive PPS
1517 pulse and the "clear" event was the leading edge of the next pulse.
1519 As the width of a PPS pulse in a typical GPS receiver is on the
1520 order of 1 millisecond, most users will not notice any significant
1521 difference with this change.
1523 Anyone who has compensated for the historical polarity reversal by
1524 configuring a negative offset equal to the pulse width will need to
1525 remove that workaround.
1528 The default group assigned to /dev/dri entries has been changed
1529 from 'wheel' to 'video' with the id of '44'. If you want to have
1530 access to the dri devices please add yourself to the video group
1533 # pw groupmod video -m $USER
1536 The menu.rc and loader.rc files will now be replaced during
1537 upgrades. Please migrate local changes to menu.rc.local and
1538 loader.rc.local instead.
1541 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1542 strings and strip have been removed. The src.conf(5) knob
1543 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1546 As ZFS requires more kernel stack pages than is the default on some
1547 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1548 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1550 Please consider using 'options KSTACK_PAGES=X' where X is greater
1551 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1554 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1555 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1556 default, i.e., they will not contain "::". For example, instead
1557 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1558 to have a more specific match, such as different map entries for
1559 IPv6:0:0 vs IPv6:0. This change requires that configuration
1560 data (including maps, files, classes, custom ruleset, etc.) must
1561 use the same format, so make certain such configuration data is
1562 upgrading. As a very simple check search for patterns like
1563 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1564 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1565 the cf option UseCompressedIPv6Addresses.
1568 The default kernel entropy-processing algorithm is now
1569 Fortuna, replacing Yarrow.
1571 Assuming you have 'device random' in your kernel config
1572 file, the configurations allow a kernel option to override
1573 this default. You may choose *ONE* of:
1575 options RANDOM_YARROW # Legacy /dev/random algorithm.
1576 options RANDOM_DUMMY # Blocking-only driver.
1578 If you have neither, you get Fortuna. For most people,
1579 read no further, Fortuna will give a /dev/random that works
1580 like it always used to, and the difference will be irrelevant.
1582 If you remove 'device random', you get *NO* kernel-processed
1583 entropy at all. This may be acceptable to folks building
1584 embedded systems, but has complications. Carry on reading,
1585 and it is assumed you know what you need.
1587 *PLEASE* read random(4) and random(9) if you are in the
1588 habit of tweaking kernel configs, and/or if you are a member
1589 of the embedded community, wanting specific and not-usual
1590 behaviour from your security subsystems.
1592 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1593 random', you will NOT have a functioning /dev/random, and
1594 many cryptographic features will not work, including SSH.
1595 You may also find strange behaviour from the random(3) set
1596 of library functions, in particular sranddev(3), srandomdev(3)
1597 and arc4random(3). The reason for this is that the KERN_ARND
1598 sysctl only returns entropy if it thinks it has some to
1599 share, and with RANDOM_DUMMY or no 'device random' this
1603 An additional fix for the issue described in the 20150614 sendmail
1604 entry below has been committed in revision 284717.
1607 FreeBSD's old make (fmake) has been removed from the system. It is
1608 available as the devel/fmake port or via pkg install fmake.
1611 The fix for the issue described in the 20150614 sendmail entry
1612 below has been committed in revision 284436. The work
1613 around described in that entry is no longer needed unless the
1614 default setting is overridden by a confDH_PARAMETERS configuration
1615 setting of '5' or pointing to a 512 bit DH parameter file.
1618 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1619 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1620 and devel/kyua to version 0.20+ and adjust any calling code to work
1621 with Kyuafile and kyua.
1624 The import of openssl to address the FreeBSD-SA-15:10.openssl
1625 security advisory includes a change which rejects handshakes
1626 with DH parameters below 768 bits. sendmail releases prior
1627 to 8.15.2 (not yet released), defaulted to a 512 bit
1628 DH parameter setting for client connections. To work around
1629 this interoperability, sendmail can be configured to use a
1630 2048 bit DH parameter by:
1632 1. Edit /etc/mail/`hostname`.mc
1633 2. If a setting for confDH_PARAMETERS does not exist or
1634 exists and is set to a string beginning with '5',
1635 replace it with '2'.
1636 3. If a setting for confDH_PARAMETERS exists and is set to
1637 a file path, create a new file with:
1638 openssl dhparam -out /path/to/file 2048
1639 4. Rebuild the .cf file:
1640 cd /etc/mail/; make; make install
1641 5. Restart sendmail:
1642 cd /etc/mail/; make restart
1644 A sendmail patch is coming, at which time this file will be
1648 Generation of legacy formatted entries have been disabled by default
1649 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1650 entries were converted to use the new format by default when the new,
1651 machine independent format have been added and supported since FreeBSD
1654 Please see the pwd_mkdb(8) manual page for further details.
1657 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1658 20141231 entry below for information about prerequisites and upgrading,
1659 if you are not already using 3.5.0 or higher.
1662 TI platform code switched to using vendor DTS files and this update
1663 may break existing systems running on Beaglebone, Beaglebone Black,
1666 - dtb files should be regenerated/reinstalled. Filenames are the
1667 same but content is different now
1668 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1669 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1670 addressing scheme is now pin 25 on /dev/gpioc3.
1671 - Pandaboard: /etc/ttys should be updated, serial console device is
1672 now /dev/ttyu2, not /dev/ttyu0
1675 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1676 If you need the GNU extension from groff soelim(1), install groff
1677 from package: pkg install groff, or via ports: textproc/groff.
1680 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1681 defined in symlink(7); previously symlinks were silently ignored.
1684 The const qualifier has been removed from iconv(3) to comply with
1685 POSIX. The ports tree is aware of this from r384038 onwards.
1688 Libraries specified by LIBADD in Makefiles must have a corresponding
1689 DPADD_<lib> variable to ensure correct dependencies. This is now
1690 enforced in src.libnames.mk.
1693 From legacy ata(4) driver was removed support for SATA controllers
1694 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1695 Kernel modules ataahci and ataadaptec were removed completely,
1696 replaced by ahci and mvs modules respectively.
1699 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1700 the 20141231 entry below for information about prerequisites and
1701 upgrading, if you are not already using 3.5.0 or higher.
1704 The 32-bit PowerPC kernel has been changed to a position-independent
1705 executable. This can only be booted with a version of loader(8)
1706 newer than January 31, 2015, so make sure to update both world and
1707 kernel before rebooting.
1710 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1711 but before r278950, the RNG was not seeded properly. Immediately
1712 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1713 ssh keys or openssl keys) that were generated w/ a kernel from that
1714 range. This does not affect programs that directly used /dev/random
1715 or /dev/urandom. All userland uses of arc4random(3) are affected.
1718 The autofs(4) ABI was changed in order to restore binary compatibility
1719 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1720 with the new kernel.
1723 The powerpc64 kernel has been changed to a position-independent
1724 executable. This can only be booted with a new version of loader(8),
1725 so make sure to update both world and kernel before rebooting.
1728 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1729 only release, no new features have been added. Please see the 20141231
1730 entry below for information about prerequisites and upgrading, if you
1731 are not already using 3.5.0.
1734 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1735 taken from the ELF Tool Chain project rather than GNU binutils. They
1736 should be drop-in replacements, with the addition of arm64 support.
1737 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1738 binutils tools, if necessary. See 20150805 for updated information.
1741 The default Unbound configuration now enables remote control
1742 using a local socket. Users who have already enabled the
1743 local_unbound service should regenerate their configuration
1744 by running "service local_unbound setup" as root.
1747 The GNU texinfo and GNU info pages have been removed.
1748 To be able to view GNU info pages please install texinfo from ports.
1751 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1753 As of this release, a prerequisite for building clang, llvm and lldb is
1754 a C++11 capable compiler and C++11 standard library. This means that to
1755 be able to successfully build the cross-tools stage of buildworld, with
1756 clang as the bootstrap compiler, your system compiler or cross compiler
1757 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1758 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1761 On any standard FreeBSD 10.x or 11.x installation, where clang and
1762 libc++ are on by default (that is, on x86 or arm), this should work out
1765 On 9.x installations where clang is enabled by default, e.g. on x86 and
1766 powerpc, libc++ will not be enabled by default, so libc++ should be
1767 built (with clang) and installed first. If both clang and libc++ are
1768 missing, build clang first, then use it to build libc++.
1770 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1771 the instructions for 9.x above.
1773 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1774 default, and do not build clang.
1776 Many embedded systems are resource constrained, and will not be able to
1777 build clang in a reasonable time, or in some cases at all. In those
1778 cases, cross building bootable systems on amd64 is a workaround.
1780 This new version of clang introduces a number of new warnings, of which
1781 the following are most likely to appear:
1785 This warns in two cases, for both C and C++:
1786 * When the code is trying to take the absolute value of an unsigned
1787 quantity, which is effectively a no-op, and almost never what was
1788 intended. The code should be fixed, if at all possible. If you are
1789 sure that the unsigned quantity can be safely cast to signed, without
1790 loss of information or undefined behavior, you can add an explicit
1791 cast, or disable the warning.
1793 * When the code is trying to take an absolute value, but the called
1794 abs() variant is for the wrong type, which can lead to truncation.
1795 If you want to disable the warning instead of fixing the code, please
1796 make sure that truncation will not occur, or it might lead to unwanted
1799 -Wtautological-undefined-compare and
1800 -Wundefined-bool-conversion
1802 These warn when C++ code is trying to compare 'this' against NULL, while
1803 'this' should never be NULL in well-defined C++ code. However, there is
1804 some legacy (pre C++11) code out there, which actively abuses this
1805 feature, which was less strictly defined in previous C++ versions.
1807 Squid and openjdk do this, for example. The warning can be turned off
1808 for C++98 and earlier, but compiling the code in C++11 mode might result
1809 in unexpected behavior; for example, the parts of the program that are
1810 unreachable could be optimized away.
1813 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1814 kernel sources have been removed. The .h files remain, since some
1815 utilities include them. This will need to be fixed later.
1816 If "mount -t oldnfs ..." is attempted, it will fail.
1817 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1818 the utilities will report errors.
1821 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1822 directories to top level SUBDIR variable when their parent
1823 directory is included in LOCAL_DIRS. Users with build systems with
1824 such hierarchies and without SUBDIR entries in the parent
1825 directory Makefiles should add them or add the directories to
1829 faith(4) and faithd(8) have been removed from the base system. Faith
1830 has been obsolete for a very long time.
1833 vt(4), the new console driver, is enabled by default. It brings
1834 support for Unicode and double-width characters, as well as
1835 support for UEFI and integration with the KMS kernel video
1838 You may need to update your console settings in /etc/rc.conf,
1839 most probably the keymap. During boot, /etc/rc.d/syscons will
1840 indicate what you need to do.
1842 vt(4) still has issues and lacks some features compared to
1843 syscons(4). See the wiki for up-to-date information:
1844 https://wiki.freebsd.org/Newcons
1846 If you want to keep using syscons(4), you can do so by adding
1847 the following line to /boot/loader.conf:
1851 pjdfstest has been integrated into kyua as an opt-in test suite.
1852 Please see share/doc/pjdfstest/README for more details on how to
1856 gperf has been removed from the base system for architectures
1857 that use clang. Ports that require gperf will obtain it from the
1861 pjdfstest has been moved from tools/regression/pjdfstest to
1865 At svn r271982, The default linux compat kernel ABI has been adjusted
1866 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1867 update. If you wish to continue using the linux-f10 compat ports,
1868 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1869 encouraged to update their linux-compat packages to linux-c6 during
1870 their next update cycle.
1873 The ofwfb driver, used to provide a graphics console on PowerPC when
1874 using vt(4), no longer allows mmap() of all physical memory. This
1875 will prevent Xorg on PowerPC with some ATI graphics cards from
1876 initializing properly unless x11-servers/xorg-server is updated to
1880 The xdev targets have been converted to using TARGET and
1881 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1884 The default unbound configuration has been modified to address
1885 issues with reverse lookups on networks that use private
1886 address ranges. If you use the local_unbound service, run
1887 "service local_unbound setup" as root to regenerate your
1888 configuration, then "service local_unbound reload" to load the
1892 The GNU texinfo and GNU info pages are not built and installed
1893 anymore, WITH_INFO knob has been added to allow to built and install
1895 UPDATE: see 20150102 entry on texinfo's removal
1898 The GNU readline library is now an INTERNALLIB - that is, it is
1899 statically linked into consumers (GDB and variants) in the base
1900 system, and the shared library is no longer installed. The
1901 devel/readline port is available for third party software that
1905 The Itanium architecture (ia64) has been removed from the list of
1906 known architectures. This is the first step in the removal of the
1910 Commit r268115 has added NFSv4.1 server support, merged from
1911 projects/nfsv4.1-server. Since this includes changes to the
1912 internal interfaces between the NFS related modules, a full
1913 build of the kernel and modules will be necessary.
1914 __FreeBSD_version has been bumped.
1917 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1918 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1919 which differs from the behaviour controlled by this knob.)
1922 Maximal length of the serial number in CTL was increased from 16 to
1923 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1924 and ctld, need to be rebuilt to work with a new kernel.
1927 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1928 1 respectively to match the upstream numbers. They were out of
1929 sync because, when they were originally added to FreeBSD, the
1930 upstream versions were not respected. These libraries are private
1931 and not yet built by default, so renumbering them should be a
1932 non-issue. However, unclean source trees will yield broken test
1933 programs once the operator executes "make delete-old-libs" after a
1934 "make installworld".
1936 Additionally, the atf-sh binary was made private by moving it into
1937 /usr/libexec/. Already-built shell test programs will keep the
1938 path to the old binary so they will break after "make delete-old"
1941 If you are using WITH_TESTS=yes (not the default), wipe the object
1942 tree and rebuild from scratch to prevent spurious test failures.
1943 This is only needed once: the misnumbered libraries and misplaced
1944 binaries have been added to OptionalObsoleteFiles.inc so they will
1945 be removed during a clean upgrade.
1948 Clang and llvm have been upgraded to 3.4.1 release.
1951 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1952 be removed to avoid issues in the future (and has been added to
1956 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1957 past, it affected all builds that used the bsd.*.mk files. The old
1958 behavior was a bug, but people may have relied upon it. To get this
1959 behavior back, you can .include /etc/src.conf from /etc/make.conf
1960 (which is still global and isn't changed). This also changes the
1961 behavior of incremental builds inside the tree of individual
1962 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1963 Although this has survived make universe and some upgrade scenarios,
1964 other upgrade scenarios may have broken. At least one form of
1965 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1966 as well... In cases where MAKESYSPATH isn't working with this
1967 setting, you'll need to set it to the full path to your tree.
1969 One side effect of all this cleaning up is that bsd.compiler.mk
1970 is no longer implicitly included by bsd.own.mk. If you wish to
1971 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1975 The lindev device has been removed since /dev/full has been made a
1976 standard device. __FreeBSD_version has been bumped.
1979 The knob WITHOUT_VI was added to the base system, which controls
1980 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1981 in order to reorder files share/termcap and didn't build ex(1) as a
1982 build tool, so building/installing with WITH_VI is highly advised for
1983 build hosts for older releases.
1985 This issue has been fixed in stable/9 and stable/10 in r277022 and
1986 r276991, respectively.
1989 The YES_HESIOD knob has been removed. It has been obsolete for
1990 a decade. Please move to using WITH_HESIOD instead or your builds
1991 will silently lack HESIOD.
1994 The uart(4) driver has been changed with respect to its handling
1995 of the low-level console. Previously the uart(4) driver prevented
1996 any process from changing the baudrate or the CLOCAL and HUPCL
1997 control flags. By removing the restrictions, operators can make
1998 changes to the serial console port without having to reboot.
1999 However, when getty(8) is started on the serial device that is
2000 associated with the low-level console, a misconfigured terminal
2001 line in /etc/ttys will now have a real impact.
2002 Before upgrading the kernel, make sure that /etc/ttys has the
2003 serial console device configured as 3wire without baudrate to
2004 preserve the previous behaviour. E.g:
2005 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
2008 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
2009 to improve performance. To re-enable it, if needed, run rpcbind
2010 with command line option -W.
2013 Switched back to the GPL dtc compiler due to updates in the upstream
2014 dts files not being supported by the BSDL dtc compiler. You will need
2015 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
2016 may result while building dtb files during a kernel build if you fail
2017 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
2020 Clang and llvm have been upgraded to 3.4 release.
2023 The nve(4) driver has been removed. Please use the nfe(4) driver
2024 for NVIDIA nForce MCP Ethernet adapters instead.
2027 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
2028 This could cause certain C++ applications using shared libraries built
2029 against the previous version of libc++ to crash. The incompatibility
2030 has now been fixed, but any C++ applications or shared libraries built
2031 between r261283 and r261801 should be recompiled.
2034 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
2035 capability mode support. Please note that enabling the feature in
2036 kernel is still highly recommended.
2039 OpenSSH is now built with sandbox support, and will use sandbox as
2040 the default privilege separation method. This requires Capsicum
2041 capability mode support in kernel.
2044 The libelf and libdwarf libraries have been updated to newer
2045 versions from upstream. Shared library version numbers for
2046 these two libraries were bumped. Any ports or binaries
2047 requiring these two libraries should be recompiled.
2048 __FreeBSD_version is bumped to 1100006.
2051 If a Makefile in a tests/ directory was auto-generating a Kyuafile
2052 instead of providing an explicit one, this would prevent such
2053 Makefile from providing its own Kyuafile in the future during
2054 NO_CLEAN builds. This has been fixed in the Makefiles but manual
2055 intervention is needed to clean an objdir if you use NO_CLEAN:
2056 # find /usr/obj -name Kyuafile | xargs rm -f
2059 The behavior of gss_pseudo_random() for the krb5 mechanism
2060 has changed, for applications requesting a longer random string
2061 than produced by the underlying enctype's pseudo-random() function.
2062 In particular, the random string produced from a session key of
2063 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
2064 be different at the 17th octet and later, after this change.
2065 The counter used in the PRF+ construction is now encoded as a
2066 big-endian integer in accordance with RFC 4402.
2067 __FreeBSD_version is bumped to 1100004.
2070 The WITHOUT_ATF build knob has been removed and its functionality
2071 has been subsumed into the more generic WITHOUT_TESTS. If you were
2072 using the former to disable the build of the ATF libraries, you
2073 should change your settings to use the latter.
2076 The default version of mtree is nmtree which is obtained from
2077 NetBSD. The output is generally the same, but may vary
2078 slightly. If you found you need identical output adding
2079 "-F freebsd9" to the command line should do the trick. For the
2080 time being, the old mtree is available as fmtree.
2083 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
2084 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
2085 1.1.4_8 and verify bsdyml not linked in, before running "make
2087 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
2089 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
2092 The stable/10 branch has been created in subversion from head
2099 Sometimes, obscure build problems are the result of environment
2100 poisoning. This can happen because the make utility reads its
2101 environment when searching for values for global variables. To run
2102 your build attempts in an "environmental clean room", prefix all make
2103 commands with 'env -i '. See the env(1) manual page for more details.
2104 Occasionally a build failure will occur with "make -j" due to a race
2105 condition. If this happens try building again without -j, and please
2106 report a bug if it happens consistently.
2108 When upgrading from one major version to another it is generally best to
2109 upgrade to the latest code in the currently installed branch first, then
2110 do an upgrade to the new branch. This is the best-tested upgrade path,
2111 and has the highest probability of being successful. Please try this
2112 approach if you encounter problems with a major version upgrade. Since
2113 the stable 4.x branch point, one has generally been able to upgrade from
2114 anywhere in the most recent stable branch to head / current (or even the
2115 last couple of stable branches). See the top of this file when there's
2118 The update process will emit an error on an attempt to perform a build
2119 or install from a FreeBSD version below the earliest supported version.
2120 When updating from an older version the update should be performed one
2121 major release at a time, including running `make delete-old` at each
2124 When upgrading a live system, having a root shell around before
2125 installing anything can help undo problems. Not having a root shell
2126 around can lead to problems if pam has changed too much from your
2127 starting point to allow continued authentication after the upgrade.
2129 This file should be read as a log of events. When a later event changes
2130 information of a prior event, the prior event should not be deleted.
2131 Instead, a pointer to the entry with the new information should be
2132 placed in the old entry. Readers of this file should also sanity check
2133 older entries before relying on them blindly. Authors of new entries
2134 should write them with this in mind.
2138 When upgrading the boot ZFS pool to a new version, always follow
2141 1.) recompile and reinstall the ZFS boot loader and boot block
2142 (this is part of "make buildworld" and "make installworld")
2144 2.) update the ZFS boot block on your boot drive
2146 The following example updates the ZFS boot block on the first
2147 partition (freebsd-boot) of a GPT partitioned drive ada0:
2148 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
2150 Non-boot pools do not need these updates.
2154 If you are updating from a prior version of FreeBSD (even one just
2155 a few days old), you should follow this procedure. It is the most
2156 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2158 make kernel-toolchain
2159 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2160 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2162 To test a kernel once
2163 ---------------------
2164 If you just want to boot a kernel once (because you are not sure
2165 if it works, or if you want to boot a known bad kernel to provide
2166 debugging information) run
2167 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2168 nextboot -k testkernel
2170 To rebuild everything and install it on the current system.
2171 -----------------------------------------------------------
2172 # Note: sometimes if you are running current you gotta do more than
2173 # is listed here if you are upgrading from a really old current.
2175 <make sure you have good level 0 dumps>
2177 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2178 make installkernel KERNCONF=YOUR_KERNEL_HERE
2180 <reboot in single user> [3]
2187 To cross-install current onto a separate partition
2188 --------------------------------------------------
2189 # In this approach we use a separate partition to hold
2190 # current's root, 'usr', and 'var' directories. A partition
2191 # holding "/", "/usr" and "/var" should be about 2GB in
2194 <make sure you have good level 0 dumps>
2197 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2198 <maybe newfs current's root partition>
2199 <mount current's root partition on directory ${CURRENT_ROOT}>
2200 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
2201 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2202 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2203 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2204 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2205 <reboot into current>
2206 <do a "native" rebuild/install as described in the previous section>
2207 <maybe install compatibility libraries from ports/misc/compat*>
2211 To upgrade in-place from stable to current
2212 ----------------------------------------------
2213 <make sure you have good level 0 dumps>
2215 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
2216 make installkernel KERNCONF=YOUR_KERNEL_HERE
2218 <reboot in single user> [3]
2225 Make sure that you've read the UPDATING file to understand the
2226 tweaks to various things you need. At this point in the life
2227 cycle of current, things change often and you are on your own
2228 to cope. The defaults can also change, so please read ALL of
2229 the UPDATING entries.
2231 Also, if you are tracking -current, you must be subscribed to
2232 freebsd-current@freebsd.org. Make sure that before you update
2233 your sources that you have read and understood all the recent
2234 messages there. If in doubt, please track -stable which has
2235 much fewer pitfalls.
2237 [1] If you have third party modules, such as vmware, you
2238 should disable them at this point so they don't crash your
2241 [3] From the bootblocks, boot -s, and then do
2245 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed
2246 cd src # full path to source
2247 adjkerntz -i # if CMOS is wall time
2248 Also, when doing a major release upgrade, it is required that
2249 you boot into single user mode to do the installworld.
2251 [4] Note: This step is non-optional. Failure to do this step
2252 can result in a significant reduction in the functionality of the
2253 system. Attempting to do it by hand is not recommended and those
2254 that pursue this avenue should read this file carefully, as well
2255 as the archives of freebsd-current and freebsd-hackers mailing lists
2256 for potential gotchas. The -U option is also useful to consider.
2257 See mergemaster(8) for more information.
2259 [5] Usually this step is a no-op. However, from time to time
2260 you may need to do this if you get unknown user in the following
2261 step. It never hurts to do it all the time. You may need to
2262 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2263 install) after the buildworld before this step if you last updated
2264 from current before 20130425 or from -stable before 20130430.
2266 [6] This only deletes old files and directories. Old libraries
2267 can be deleted by "make delete-old-libs", but you have to make
2268 sure that no program is using those libraries anymore.
2270 [8] The new kernel must be able to run existing binaries used by an
2271 installworld. When upgrading across major versions, the new kernel's
2272 configuration must include the correct COMPAT_FREEBSD<n> option for
2273 existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure
2274 to do so may leave you with a system that is hard to boot to recover. A
2275 GENERIC kernel will include suitable compatibility options to run
2276 binaries from older branches. Note that the ability to run binaries
2277 from unsupported branches is not guaranteed.
2279 Make sure that you merge any new devices from GENERIC since the
2280 last time you updated your kernel config file. Options also
2281 change over time, so you may need to adjust your custom kernels
2284 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2285 "?=" instead of the "=" assignment operator, so that buildworld can
2286 override the CPUTYPE if it needs to.
2288 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2289 not on the command line, or in /etc/make.conf. buildworld will
2290 warn if it is improperly defined.
2293 This file contains a list, in reverse chronological order, of major
2294 breakages in tracking -current. It is not guaranteed to be a complete
2295 list of such breakages, and only contains entries since September 23, 2011.
2296 If you need to see UPDATING entries from before that date, you will need
2297 to fetch an UPDATING file from an older FreeBSD release.
2299 Copyright information:
2301 Copyright 1998-2009 M. Warner Losh <imp@FreeBSD.org>
2303 Redistribution, publication, translation and use, with or without
2304 modification, in full or in part, in any form or format of this
2305 document are permitted without further permission from the author.
2307 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2308 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2309 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2310 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2311 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2312 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2313 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2314 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2315 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2316 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2317 POSSIBILITY OF SUCH DAMAGE.
2319 Contact Warner Losh if you have any questions about your use of