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 r363679 has redefined some undefined behavior in regcomp(3); notably,
31 extraneous escapes of most ordinary characters will no longer be
32 accepted. An exp-run has identified all of the problems with this in
33 ports, but other non-ports software may need extra escapes removed to
36 Because of this change, installworld may encounter the following error
37 from rtld: Undefined symbol "regcomp@FBSD_1.6" -- It is imperative that
38 you do not halt installworld. Instead, let it run to completion (whether
39 successful or not) and run installworld once more.
42 A new implementation of bc and dc has been imorted in r362681. This
43 implementation corrects non-conformant behavior of the previous bc
44 and adds GNU bc compatible options. It offers a number of extensions,
45 is much faster on large values, and has support for message catalogs
46 (a number of languages are already supported, contributions of further
47 languages welcome). The option WITHOUT_GH_BC can be used to build the
48 world with the previous versions of bc and dc.
51 r362639 changed the internal API used between the NFS kernel modules.
52 As such, they all need to be rebuilt from sources.
55 r362158 changed the arguments for VFS_CHECKEXP(). As such, any
56 out of tree file systems need to be modified and rebuilt.
57 Also, any file systems that are modules must be rebuilt.
60 read(2) of a directory fd is now rejected by default. root may
61 re-enable it for system root only on non-ZFS filesystems with the
62 security.bsd.allow_read_dir sysctl(8) MIB if
63 security.bsd.suser_enabled=1.
65 It may be advised to setup aliases for grep to default to `-d skip` if
66 commonly non-recursively grepping a list that includes directories and
67 the potential for the resulting stderr output is not tolerable. Example
68 aliases are now installed, commented out, in /root/.cshrc and
72 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
73 been upgraded to 10.0.1. Please see the 20141231 entry below for
74 information about prerequisites and upgrading, if you are not already
75 using clang 3.5.0 or higher.
78 Support for obsolete compilers has been removed from the build system.
79 Clang 6 and GCC 6.4 are the minimum supported versions.
82 closefrom(2) has been moved under COMPAT12, and replaced in libc with a
83 stub that calls close_range(2). If using a custom kernel configuration,
84 you may want to ensure that the COMPAT_FREEBSD12 option is included, as
85 a slightly older -CURRENT userland and older FreeBSD userlands may not
86 be functional without closefrom(2).
89 Upstream DTS from Linux 5.6 was merged and they now have the SID
90 and THS (Secure ID controller and THermal Sensor) node present.
91 The DTB overlays have now been removed from the tree for the H3/H5 and
92 A64 SoCs and the aw_sid and aw_thermal driver have been updated to
93 deal with upstream DTS. If you are using those overlays you need to
94 remove them from loader.conf and update the DTBs on the FAT partition.
97 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
98 been upgraded to 10.0.0. Please see the 20141231 entry below for
99 information about prerequisites and upgrading, if you are not already
100 using clang 3.5.0 or higher.
103 The amd(8) automount daemon has been removed from the source tree.
104 As of FreeBSD 10.1 autofs(5) is the preferred tool for automounting.
105 amd is still available in the sysutils/am-utils port.
108 Removed brooktree driver (bktr.4) from the tree.
111 The WITH_GPL_DTC option has been removed. The BSD-licenced device tree
112 compiler in usr.bin/dtc is used on all architectures which use dtc, and
113 the GPL dtc is available (if needed) from the sysutils/dtc port.
116 The WITHOUT_LLVM_LIBUNWIND option has been removed. LLVM's libunwind
117 is used by all supported CPU architectures.
120 GCC 4.2.1 has been removed from the tree. The WITH_GCC,
121 WITH_GCC_BOOTSTRAP, and WITH_GNUCXX options are no longer available.
122 Users who wish to build FreeBSD with GCC must use the external toolchain
126 ncurses has been updated to a newer version (6.2-20200215). Given the ABI
127 has changed, users will have to rebuild all the ports that are linked to
131 The size of struct vnet and the magic cookie have changed.
132 Users need to recompile libkvm and all modules using VIMAGE
133 together with their new kernel.
136 Defining the long deprecated NO_CTF, NO_DEBUG_FILES, NO_INSTALLLIB,
137 NO_MAN, NO_PROFILE, and NO_WARNS variables is now an error. Update
138 your Makefiles and scripts to define MK_<var>=no instead as required.
140 One exception to this is that program or library Makefiles should
141 define MAN to empty rather than setting MK_MAN=no.
144 Clang/LLVM is now the default compiler and LLD the default
148 make universe no longer uses GCC 4.2.1 on any architectures.
149 Architectures not supported by in-tree Clang/LLVM require an
150 external toolchain package.
153 GCC 4.2.1 is now not built by default, as part of the GCC 4.2.1
154 retirement plan. Specifically, the GCC, GCC_BOOTSTRAP, and GNUCXX
155 options default to off for all supported CPU architectures. As a
156 short-term transition aid they may be enabled via WITH_* options.
157 GCC 4.2.1 is expected to be removed from the tree on 2020-03-31.
160 Support for armv5 has been disconnected and is being removed. The
161 machine combination MACHINE=arm MACHINE_ARCH=arm is no longer valid.
162 You must now use a MACHINE_ARCH of armv6 or armv7. The default
163 MACHINE_ARCH for MACHINE=arm is now armv7.
166 Clang/LLVM is now the default compiler for all powerpc architectures.
167 LLD is now the default linker for powerpc64. The change for powerpc64
168 also includes a change to the ELFv2 ABI, incompatible with the existing
172 Kernel-loadable random(4) modules are no longer unloadable.
175 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
176 been upgraded to 9.0.1. Please see the 20141231 entry below for
177 information about prerequisites and upgrading, if you are not already
178 using clang 3.5.0 or higher.
181 r355677 has modified the internal interface used between the
182 NFS modules in the kernel. As such, they must all be upgraded
183 simultaneously. I will do a version bump for this.
186 The root certificates of the Mozilla CA Certificate Store have been
187 imported into the base system and can be managed with the certctl(8)
188 utility. If you have installed the security/ca_root_nss port or package
189 with the ETCSYMLINK option (the default), be advised that there may be
190 differences between those included in the port and those included in
191 base due to differences in nss branch used as well as general update
192 frequency. Note also that certctl(8) cannot manage certs in the
193 format used by the security/ca_root_nss port.
196 The amd(8) automount daemon has been disabled by default, and will be
197 removed in the future. As of FreeBSD 10.1 the autofs(5) is available
201 The nctgpio and wbwd drivers have been moved to the superio bus.
202 If you have one of these drivers in a kernel configuration, then
203 you should add device superio to it. If you use one of these drivers
204 as a module and you compile a custom set of modules, then you should
205 add superio to the set.
208 KPIs for network drivers to access interface addresses have changed.
209 Users need to recompile NIC driver modules together with kernel.
212 The net.link.tap.user_open sysctl no longer prevents user opening of
213 already created /dev/tapNN devices. Access is still controlled by
214 node permissions, just like tun devices. The net.link.tap.user_open
215 sysctl is now used only to allow users to perform devfs cloning of
216 tap devices, and the subsequent open may not succeed if the user is not
217 in the appropriate group. This sysctl may be deprecated/removed
218 completely in the future.
221 mips, powerpc, and sparc64 are no longer built as part of
222 universe / tinderbox unless MAKE_OBSOLETE_GCC is defined. If
223 not defined, mips, powerpc, and sparc64 builds will look for
224 the xtoolchain binaries and if installed use them for universe
225 builds. As llvm 9.0 becomes vetted for these architectures, they
226 will be removed from the list.
229 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
230 been upgraded to 9.0.0. Please see the 20141231 entry below for
231 information about prerequisites and upgrading, if you are not already
232 using clang 3.5.0 or higher.
235 The hpt27xx, hptmv, hptnr, and hptrr drivers have been removed from
236 GENERIC. They are available as modules and can be loaded by adding
237 to /boot/loader.conf hpt27xx_load="YES", hptmv_load="YES",
238 hptnr_load="YES", or hptrr_load="YES", respectively.
241 ntpd no longer by default locks its pages in memory, allowing them
242 to be paged out by the kernel. Use rlimit memlock to restore
243 historic BSD behaviour. For example, add "rlimit memlock 32"
244 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
247 Several of ping6's options have been renamed for better consistency
248 with ping. If you use any of -ARWXaghmrtwx, you must update your
249 scripts. See ping6(8) for details.
252 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
253 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
254 been removed from mount_fusefs(8). You can safely remove them from
255 your scripts, because they had no effect.
257 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
258 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
259 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
260 sysctls have been removed. If you felt the need to set any of them to
261 a non-default value, please tell asomers@FreeBSD.org why.
264 Default permissions on the /var/account/acct file (and copies of it
265 rotated by periodic daily scripts) are changed from 0644 to 0640
266 because the file contains sensitive information that should not be
267 world-readable. If the /var/account directory must be created by
268 rc.d/accounting, the mode used is now 0750. Admins who use the
269 accounting feature are encouraged to change the mode of an existing
270 /var/account directory to 0750 or 0700.
273 Entropy collection and the /dev/random device are no longer optional
274 components. The "device random" option has been removed.
275 Implementations of distilling algorithms can still be made loadable
276 with "options RANDOM_LOADABLE" (e.g., random_fortuna.ko).
279 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
280 been upgraded to 8.0.1. Please see the 20141231 entry below for
281 information about prerequisites and upgrading, if you are not already
282 using clang 3.5.0 or higher.
285 A fix was applied to i386 kernel modules to avoid panics with
286 dpcpu or vnet. Users need to recompile i386 kernel modules
287 having pcpu or vnet sections or they will refuse to load.
290 User-wired pages now have their own counter,
291 vm.stats.vm.v_user_wire_count. The vm.max_wired sysctl was renamed
292 to vm.max_user_wired and changed from an unsigned int to an unsigned
293 long. bhyve VMs wired with the -S are now subject to the user
294 wiring limit; the vm.max_user_wired sysctl may need to be tuned to
295 avoid running into the limit.
298 The IPSEC option has been removed from GENERIC. Users requiring
299 ipsec(4) must now load the ipsec(4) kernel module.
302 The tap(4) driver has been folded into tun(4), and the module has been
303 renamed to tuntap. You should update any kld_list="if_tap" or
304 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
305 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
306 module instead, and "device tap" or "device tun" entries in kernel
307 config files to select the tuntap device instead.
310 The following knobs have been added related to tradeoffs between
311 safe use of the random device and availability in the absence of
314 kern.random.initial_seeding.bypass_before_seeding: tunable; set
315 non-zero to bypass the random device prior to seeding, or zero to
316 block random requests until the random device is initially seeded.
317 For now, set to 1 (unsafe) by default to restore pre-r346250 boot
318 availability properties.
320 kern.random.initial_seeding.read_random_bypassed_before_seeding:
321 read-only diagnostic sysctl that is set when bypass is enabled and
322 read_random(9) is bypassed, to enable programmatic handling of this
323 initial condition, if desired.
325 kern.random.initial_seeding.arc4random_bypassed_before_seeding:
326 Similar to the above, but for for arc4random(9) initial seeding.
328 kern.random.initial_seeding.disable_bypass_warnings: tunable; set
329 non-zero to disable warnings in dmesg when the same conditions are
330 met as for the diagnostic sysctls above. Defaults to zero, i.e.,
331 produce warnings in dmesg when the conditions are met.
334 The loadable random module KPI has changed; the random_infra_init()
335 routine now requires a 3rd function pointer for a bool (*)(void)
336 method that returns true if the random device is seeded (and
337 therefore unblocked).
340 r345895 reverts r320698. This implies that an nfsuserd(8) daemon
341 built from head sources between r320757 (July 6, 2017) and
342 r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
343 is added to the command line.
344 nfsuserd daemons built from head sources that are post-r338192 are
345 not affected and should continue to work.
348 The fuse(4) module has been renamed to fusefs(4) for consistency with
349 other filesystems. You should update any kld_load="fuse" entries in
350 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
351 "options FUSE" entries in kernel config files.
354 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
355 8.0.0. Please see the 20141231 entry below for information about
356 prerequisites and upgrading, if you are not already using clang 3.5.0
360 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
361 compiled into your custom kernel, add 'device xz' statement to the
365 drm and drm2 have been removed from the tree. Please see
366 https://wiki.freebsd.org/Graphics for the latest information on
367 migrating to the drm ports.
370 Iflib is no longer unconditionally compiled into the kernel. Drivers
371 using iflib and statically compiled into the kernel, now require
372 the 'device iflib' config option. For the same drivers loaded as
373 modules on kernels not having 'device iflib', the iflib.ko module
374 is loaded automatically.
377 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
378 options no longer exist since r343219 and r343427 respectively;
379 nothing uses them, so they should be just removed from custom
383 r342635 changes the way efibootmgr(8) works by requiring users to add
384 the -b (bootnum) parameter for commands where the bootnum was previously
385 specified with each option. For example 'efibootmgr -B 0001' is now
386 'efibootmgr -B -b 0001'.
389 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
390 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
391 servers that have vfs.nfsd.nfs_privport set will only allow mounts
392 from clients using a reserved port#. Since both the FreeBSD and Linux
393 NFSv4 clients use reserved port#s by default, this should not affect
397 The XLP config has been removed. We can't support 64-bit atomics in this
398 kernel because it is running in 32-bit mode. XLP users must transition
399 to running a 64-bit kernel (XLP64 or XLPN32).
401 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
402 the preferred emulator today and we don't need two different ones.
404 The old sibyte / swarm / Broadcom BCM1250 support has been
405 removed from the mips port.
408 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
409 7.0.1. Please see the 20141231 entry below for information about
410 prerequisites and upgrading, if you are not already using clang 3.5.0
414 Remove the timed and netdate programs from the base tree. Setting
415 the time with these daemons has been obsolete for over a decade.
418 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
419 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
420 it produces broken binaries when ifuncs are in use. Users needing
421 GNU ld should install the binutils port or package.
424 The BSD crtbegin and crtend code has been enabled by default. It has
425 had extensive testing on amd64, arm64, and i386. It can be disabled
426 by building a world with -DWITHOUT_BSD_CRTBEGIN.
429 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
430 has been converted to a port (misc/ctm) and will be removed from
431 FreeBSD-13. It is available as a package (ctm) for all supported
435 The default newsyslog.conf(5) file has been changed to only include
436 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
437 the filenames end in '.conf' and do not begin with a '.'.
439 You should check the configuration files in these two directories match
440 this naming convention. You can verify which configuration files are
441 being included using the command:
445 Ports for the DRM modules have been simplified. Now, amd64 users should
446 just install the drm-kmod port. All others should install
449 Graphics hardware that's newer than about 2010 usually works with
450 drm-kmod. For hardware older than 2013, however, some users will need
451 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
452 than 2008 usually only works in drm-legacy-kmod. The graphics team can
453 only commit to hardware made since 2013 due to the complexity of the
454 market and difficulty to test all the older cards effectively. If you
455 have hardware supported by drm-kmod, you are strongly encouraged to use
456 that as you will get better support.
458 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
459 elsewhere, the drm and drm2 modules will be eliminated from the src base
460 soon (with a limited exception for arm). Please update to the package
461 asap and report any issues to x11@freebsd.org.
463 Generally, anybody using the drm*-kmod packages should add
464 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
465 cross-threading surprises, especially with automatic driver
466 loading from X11 startup. These will become the defaults in 13-current
470 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
471 custom kernel and module loading configuration files must be updated
472 accordingly. Moreover, interfaces previous presented as ixlvN to the
473 system are now exposed as iavfN and network configuration files must
474 be adjusted as necessary.
477 OpenSSL has been updated to version 1.1.1. This update included
478 additional various API changes throughout the base system. It is
479 important to rebuild third-party software after upgrading. The value
480 of __FreeBSD_version has been bumped accordingly.
483 The legacy DRM modules and drivers have now been added to the loader's
484 module blacklist, in favor of loading them with kld_list in rc.conf(5).
485 The module blacklist may be overridden with the loader.conf(5)
486 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
490 The cam(4) based nda(4) driver will be used over nvd(4) by default on
491 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
492 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
493 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
497 Reproducible build mode is now on by default, in preparation for
498 FreeBSD 12.0. This eliminates build metadata such as the user,
499 host, and time from the kernel (and uname), unless the working tree
500 corresponds to a modified checkout from a version control system.
501 The previous behavior can be obtained by setting the /etc/src.conf
502 knob WITHOUT_REPRODUCIBLE_BUILD.
505 The Yarrow CSPRNG has been removed from the kernel as it has not been
506 supported by its designers since at least 2003. Fortuna has been the
507 default since FreeBSD-11.
510 devctl freeze/thaw have gone into the tree, the rc scripts have been
511 updated to use them and devmatch has been changed. You should update
512 kernel, userland and rc scripts all at the same time.
515 The default interpreter has been switched from 4th to Lua.
516 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
517 interpreter. If you have custom FORTH code you will need to set
518 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
519 src.conf for the build. This will create default hard links between
520 loader and loader_4th instead of loader and loader_lua, the new default.
521 If you are using UEFI it will create the proper hard link to loader.efi.
523 bhyve uses userboot.so. It remains 4th-only until some issues are solved
524 regarding coexisting with multiple versions of FreeBSD are resolved.
527 ls(1) now respects the COLORTERM environment variable used in other
528 systems and software to indicate that a colored terminal is both
529 supported and desired. If ls(1) is suddenly emitting colors, they may
530 be disabled again by either removing the unwanted COLORTERM from your
531 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
532 may not be observed in a future release.
535 The default pager for most commands has been changed to "less". To
536 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
540 The jedec_ts(4) driver has been removed. A superset of its functionality
541 is available in the jedec_dimm(4) driver, and the manpage for that
542 driver includes migration instructions. If you have "device jedec_ts"
543 in your kernel configuration file, it must be removed.
546 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
547 This should have no effect if the kernel is booted via BIOS/legacy boot.
548 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
549 has a buggy firmware that prevents a successful boot due to use of
553 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
554 support has been removed from the tree. These ports were
555 obsolete and/or known to be broken for many years.
558 loader.efi has been augmented to participate more fully in the
559 UEFI boot manager protocol. loader.efi will now look at the
560 BootXXXX environment variable to determine if a specific kernel
561 or root partition was specified. XXXX is derived from BootCurrent.
562 efibootmgr(8) manages these standard UEFI variables.
565 zfsloader's functionality has now been folded into loader.
566 zfsloader is no longer necessary once you've updated your
567 boot blocks. For a transition period, we will install a
568 hardlink for zfsloader to loader to allow a smooth transition
569 until the boot blocks can be updated (hard link because old
570 zfs boot blocks don't understand symlinks).
573 ARM64 now have efifb support, if you want to have serial console
574 on your arm64 board when an screen is connected and the bootloader
575 setup a frame buffer for us to use, just add :
579 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
580 an screen connected as the firmware will setup a frame buffer are that
581 u-boot will expose as an EFI frame buffer.
584 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
585 or take steps to update /etc/passwd before doing installworld on
586 existing systems. Do not skip the "mergemaster -Fp" step before
587 installworld, as described in the update procedures near the bottom
588 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
589 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
590 the ntp config file contain options that change file/dir locations.
591 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
592 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
593 taking steps to ensure that all required files/dirs are accessible
597 Big endian arm support has been removed.
600 The static environment setup in kernel configs is no longer mutually
601 exclusive with the loader(8) environment by default. In order to
602 restore the previous default behavior of disabling the loader(8)
603 environment if a static environment is present, you must specify
604 loader_env.disabled=1 in the static environment.
607 The ABI of syscalls used by management tools like sockstat and
608 netstat has been broken to allow 32-bit binaries to work on
609 64-bit kernels without modification. These programs will need
610 to match the kernel in order to function. External programs may
611 require minor modifications to accommodate a change of type in
612 structures from pointers to 64-bit virtual addresses.
615 On i386 and amd64 atomics are now inlined. Out of tree modules using
616 atomics will need to be rebuilt.
619 The '%I' format in the kern.corefile sysctl limits the number of
620 core files that a process can generate to the number stored in the
621 debug.ncores sysctl. The '%I' format is replaced by the single digit
622 index. Previously, if all indexes were taken the kernel would overwrite
623 only a core file with the highest index in a filename.
624 Currently the system will create a new core file if there is a free
625 index or if all slots are taken it will overwrite the oldest one.
628 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
629 6.0.1. Please see the 20141231 entry below for information about
630 prerequisites and upgrading, if you are not already using clang 3.5.0
634 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
635 needed to be changed to work with it. This change was made with r335763
636 and requires a mergemaster / etcupdate / etc to update the installed
640 r334930 changed the interface between the NFS modules, so they all
641 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
644 As of r334391 lld is the default amd64 system linker; it is installed
645 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
649 The kernel / userland interface for devinfo changed, so you'll
650 need a new kernel and userland as a pair for it to work (rebuilding
651 lib/libdevinfo is all that's required). devinfo and devmatch will
652 not work, but everything else will when there's a mismatch.
655 The on-disk format for hwpmc callchain records has changed to include
656 threadid corresponding to a given record. This changes the field offsets
657 and thus requires that libpmcstat be rebuilt before using a kernel
661 The vxge(4) driver has been removed. This driver was introduced into
662 HEAD one week before the Exar left the Ethernet market and is not
663 known to be used. If you have device vxge in your kernel config file
667 The amd64 kernel now requires a ld that supports ifunc to produce a
668 working kernel, either lld or a newer binutils. lld is built by default
669 on amd64, and the 'buildkernel' target uses it automatically. However,
670 it is not the default linker, so building the kernel the traditional
671 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
672 binutils port/package). lld will soon be default, and this requirement
675 NOTE: As of r334391 lld is the default system linker on amd64, and no
676 workaround is necessary.
679 The nxge(4) driver has been removed. This driver was for PCI-X 10g
680 cards made by s2io/Neterion. The company was acquired by Exar and
681 no longer sells or supports Ethernet products. If you have device
682 nxge in your kernel config file it must be removed.
685 The tz database (tzdb) has been updated to 2018e. This version more
686 correctly models time stamps in time zones with negative DST such as
687 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
688 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
689 time zone abbreviations and the tm_isdst flag.
692 The ixgb(4) driver has been removed. This driver was for an early and
693 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
694 quickly shifted to the long lived ixgbe family. If you have device
695 ixgb in your kernel config file it must be removed.
698 The lmc(4) driver has been removed. This was a WAN interface
699 card that was already reportedly rare in 2003, and had an ambiguous
700 license. If you have device lmc in your kernel config file it must
704 Support for Arcnet networks has been removed. If you have device
705 arcnet or device cm in your kernel config file they must be
709 Support for FDDI networks has been removed. If you have device
710 fddi or device fpa in your kernel config file they must be
714 In addition to supporting RFC 3164 formatted messages, the
715 syslogd(8) service is now capable of parsing RFC 5424 formatted
716 log messages. The main benefit of using RFC 5424 is that clients
717 may now send log messages with timestamps containing year numbers,
718 microseconds and time zone offsets.
720 Similarly, the syslog(3) C library function has been altered to
721 send RFC 5424 formatted messages to the local system logging
722 daemon. On systems using syslogd(8), this change should have no
723 negative impact, as long as syslogd(8) and the C library are
724 updated at the same time. On systems using a different system
725 logging daemon, it may be necessary to make configuration
726 adjustments, depending on the software used.
728 When using syslog-ng, add the 'syslog-protocol' flag to local
729 input sources to enable parsing of RFC 5424 formatted messages:
732 unix-dgram("/var/run/log" flags(syslog-protocol));
735 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
736 of the 'imuxsock' module to let messages be processed by the
737 regular RFC 3164/5424 parsing pipeline:
739 module(load="imuxsock" SysSock.UseSpecialParser="off")
741 Do note that these changes only affect communication between local
742 applications and syslogd(8). The format that syslogd(8) uses to
743 store messages on disk or forward messages to other systems
744 remains unchanged. syslogd(8) still uses RFC 3164 for these
745 purposes. Options to customize this behaviour will be added in the
746 future. Utilities that process log files stored in /var/log are
747 thus expected to continue to function as before.
749 __FreeBSD_version has been incremented to 1200061 to denote this
753 Support for token ring networks has been removed. If you
754 have "device token" in your kernel config you should remove
755 it. No device drivers supported token ring.
758 makefs was modified to be able to tag ISO9660 El Torito boot catalog
759 entries as EFI instead of overloading the i386 tag as done previously.
760 The amd64 mkisoimages.sh script used to build amd64 ISO images for
761 release was updated to use this. This may mean that makefs must be
762 updated before "make cdrom" can be run in the release directory. This
763 should be as simple as:
765 $ cd $SRCDIR/usr.sbin/makefs
766 $ make depend all install
769 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
770 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
771 Co-existence for the transition period will come shortly. Booting is a
772 complex environment and test coverage for Lua-enabled loaders has been
773 thin, so it would be prudent to assume it might not work and make
774 provisions for backup boot methods.
777 devmatch functionality has been turned on in devd. It will automatically
778 load drivers for unattached devices. This may cause unexpected drivers
779 to be loaded. Please report any problems to current@ and
783 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
784 6.0.0. Please see the 20141231 entry below for information about
785 prerequisites and upgrading, if you are not already using clang 3.5.0
789 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
790 This means it is used to link the kernel and userland libraries and
791 executables, but is not yet installed as /usr/bin/ld by default.
793 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
794 WITHOUT_LLD_BOOTSTRAP=yes
797 On i386, pmtimer has been removed. Its functionality has been folded
798 into apm. It was a no-op on ACPI in current for a while now (but was
799 still needed on i386 in FreeBSD 11 and earlier). Users may need to
800 remove it from kernel config files.
803 The use of RSS hash from the network card aka flowid has been
804 disabled by default for lagg(4) as it's currently incompatible with
805 the lacp and loadbalance protocols.
807 This can be re-enabled by setting the following in loader.conf:
808 net.link.lagg.default_use_flowid="1"
811 The SW_WATCHDOG option is no longer necessary to enable the
812 hardclock-based software watchdog if no hardware watchdog is
813 configured. As before, SW_WATCHDOG will cause the software
814 watchdog to be enabled even if a hardware watchdog is configured.
817 r326887 fixes the issue described in the 20171214 UPDATING entry.
818 r326888 flips the switch back to building GELI support always.
821 r362593 broke ZFS + GELI support for reasons unknown. However,
822 it also broke ZFS support generally, so GELI has been turned off
823 by default as the lesser evil in r326857. If you boot off ZFS and/or
824 GELI, it might not be a good time to update.
827 PowerPC users must update loader(8) by rebuilding world before
828 installing a new kernel, as the protocol connecting them has
829 changed. Without the update, loader metadata will not be passed
830 successfully to the kernel and users will have to enter their
831 root partition at the kernel mountroot prompt to continue booting.
832 Newer versions of loader can boot old kernels without issue.
835 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
836 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
837 to WITH/OUT_LOADER_GELI.
840 The naive and non-compliant support of posix_fallocate(2) in ZFS
841 has been removed as of r325320. The system call now returns EINVAL
842 when used on a ZFS file. Although the new behavior complies with the
843 standard, some consumers are not prepared to cope with it.
844 One known victim is lld prior to r325420.
847 Building in a FreeBSD src checkout will automatically create object
848 directories now rather than store files in the current directory if
849 'make obj' was not ran. Calling 'make obj' is no longer necessary.
850 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
851 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
855 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
856 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
857 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
858 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
859 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
860 The UNIFIED_OBJDIR option is a transitional feature that will be
861 removed for 12.0 release; please migrate to the new format for any
862 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
863 than hardcoding paths.
866 The native-xtools target no longer installs the files by default to the
867 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
868 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
871 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
872 options are changing from controlling the build if defined / undefined
873 to controlling the build with explicit 'yes' or 'no' values. They will
874 shift to WITH/WITHOUT options to match other options in the system.
877 libstand has turned into a private library for sys/boot use only.
878 It is no longer supported as a public interface outside of sys/boot.
881 The arm port has split armv6 into armv6 and armv7. armv7 is now
882 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
883 and are running a kernel from before r324363, you will need to add
884 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
887 When building multiple kernels using KERNCONF, non-existent KERNCONF
888 files will produce an error and buildkernel will fail. Previously
889 missing KERNCONF files silently failed giving no indication as to
890 why, only to subsequently discover during installkernel that the
891 desired kernel was never built in the first place.
894 The default serial number format for CTL LUNs has changed. This will
895 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
896 or iSCSI clients care about their LUNs' serial numbers. Users who
897 require serial number stability should hardcode serial numbers in
901 For 32-bit arm compiled for hard-float support, soft-floating point
902 binaries now always get their shared libraries from
903 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
904 /usr/libsoft also existed). Only users with a hard-float ld.so, but
905 soft-float everything else should be affected.
908 The geli password typed at boot is now hidden. To restore the previous
909 behavior, see geli(8) for configuration options.
912 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
913 sysctl values. Minor nit, but requires a rebuild of both world/kernel
917 "make check" behavior (made in ^/head@r295380) has been changed to
918 execute from a limited sandbox, as opposed to executing from
922 - The "beforecheck" and "aftercheck" targets are now specified.
923 - ${CHECKDIR} (added in commit noted above) has been removed.
924 - Legacy behavior can be enabled by setting
925 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
927 If the limited sandbox mode is enabled, "make check" will execute
928 "make distribution", then install, execute the tests, and clean up the
929 sandbox if successful.
931 The "make distribution" and "make install" targets are typically run as
932 root to set appropriate permissions and ownership at installation time.
933 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
934 environment if executing "make check" with limited sandbox mode using
935 an unprivileged user.
938 Since the switch to GPT disk labels, fsck for UFS/FFS has been
939 unable to automatically find alternate superblocks. As of r322297,
940 the information needed to find alternate superblocks has been
941 moved to the end of the area reserved for the boot block.
942 Filesystems created with a newfs of this vintage or later
943 will create the recovery information. If you have a filesystem
944 created prior to this change and wish to have a recovery block
945 created for your filesystem, you can do so by running fsck in
946 foreground mode (i.e., do not use the -p or -y options). As it
947 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
948 to which you should answer yes.
951 As of r321665, an NFSv4 server configuration that services
952 Kerberos mounts or clients that do not support the uid/gid in
953 owner/owner_group string capability, must explicitly enable
954 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
955 machine's /etc/rc.conf file.
958 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
959 Please see the 20141231 entry below for information about prerequisites
960 and upgrading, if you are not already using clang 3.5.0 or higher.
963 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
964 r-commands (rlogin, rsh, etc.) to be built with the base system.
967 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
968 a very major ABI incompatible change, so users of FreeBSD/powerpc must
969 be careful when performing source upgrades. It is best to run
970 'make installworld' from an alternate root system, either a live
971 CD/memory stick, or a temporary root partition. Additionally, all ports
972 must be recompiled. powerpc64 is largely unaffected, except in the case
973 of 32-bit compatibility. All 32-bit binaries will be affected.
976 Forward compatibility for the "ino64" project have been committed. This
977 will allow most new binaries to run on older kernels in a limited
978 fashion. This prevents many of the common foot-shooting actions in the
979 upgrade as well as the limited ability to roll back the kernel across
980 the ino64 upgrade. Complicated use cases may not work properly, though
981 enough simpler ones work to allow recovery in most situations.
984 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
985 if you require the GPL compiler.
988 The internal ABI used for communication between the NFS kernel modules
989 was changed by r320085, so __FreeBSD_version was bumped to
990 ensure all the NFS related modules are updated together.
993 The ABI of struct event was changed by extending the data
994 member to 64bit and adding ext fields. For upgrade, same
995 precautions as for the entry 20170523 "ino64" must be
999 The GNU roff toolchain has been removed from base. To render manpages
1000 which are not supported by mandoc(1), man(1) can fallback on GNU roff
1001 from ports (and recommends to install it).
1002 To render roff(7) documents, consider using GNU roff from ports or the
1003 heirloom doctools roff toolchain from ports via pkg install groff or
1004 via pkg install heirloom-doctools.
1007 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
1008 smaller runtime footprint builds. This is useful for embedded systems
1009 which only require one chipset support.
1011 If you load it as a module, make sure this is in /boot/loader.conf:
1015 This will load the HAL, all chip/RF backends and if_ath_pci.
1016 If you have if_ath_pci in /boot/loader.conf, ensure it is after
1017 if_ath or it will not load any HAL chipset support.
1019 If you want to selectively load things (eg on ye cheape ARM/MIPS
1020 platforms where RAM is at a premium) you should:
1023 * load the chip modules in question
1024 * load ath_rate, ath_dfs
1026 * load if_ath_pci and/or if_ath_ahb depending upon your particular
1027 bus bind type - this is where probe/attach is done.
1029 For further comments/feedback, poke adrian@ .
1032 The "ino64" 64-bit inode project has been committed, which extends
1033 a number of types to 64 bits. Upgrading in place requires care and
1034 adherence to the documented upgrade procedure.
1036 If using a custom kernel configuration ensure that the
1037 COMPAT_FREEBSD11 option is included (as during the upgrade the
1038 system will be running the ino64 kernel with the existing world).
1040 For the safest in-place upgrade begin by removing previous build
1041 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full
1042 procedure documented below under the heading "To rebuild everything and
1043 install it on the current system." Specifically, a reboot is required
1044 after installing the new kernel before installing world. While an
1045 installworld normally works by accident from multiuser after rebooting
1046 the proper kernel, there are many cases where this will fail across this
1047 upgrade and installworld from single user is required.
1050 The NATM framework including the en(4), fatm(4), hatm(4), and
1051 patm(4) devices has been removed. Consumers should plan a
1052 migration before the end-of-life date for FreeBSD 11.
1055 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
1056 diff has not been implemented, if those are needed a newer version of
1057 GNU diff is available via the diffutils package under the gdiff name.
1060 As of r316810 for ipfilter, keep frags is no longer assumed when
1061 keep state is specified in a rule. r316810 aligns ipfilter with
1062 documentation in man pages separating keep frags from keep state.
1063 This allows keep state to be specified without forcing keep frags
1064 and allows keep frags to be specified independently of keep state.
1065 To maintain previous behaviour, also specify keep frags with
1066 keep state (as documented in ipf.conf.5).
1069 arm64 builds now use the base system LLD 4.0.0 linker by default,
1070 instead of requiring that the aarch64-binutils port or package be
1071 installed. To continue using aarch64-binutils, set
1072 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
1075 The UDP optimization in entry 20160818 that added the sysctl
1076 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
1077 packets will no longer be treated as L3 broadcast packets.
1080 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
1081 use any explicitly assigned loopback address available in the jail
1082 instead of using the first assigned address of the jail.
1085 The ctl.ko module no longer implements the iSCSI target frontend:
1086 cfiscsi.ko does instead.
1088 If building cfiscsi.ko as a kernel module, the module can be loaded
1089 via one of the following methods:
1090 - `cfiscsi_load="YES"` in loader.conf(5).
1091 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
1092 - ctladm(8)/ctld(8), when compiled with iSCSI support
1093 (`WITH_ISCSI=yes` in src.conf(5))
1095 Please see cfiscsi(4) for more details.
1098 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
1099 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
1100 same source (previously, the dependency of mmcsd.ko on mmc.ko was
1101 missing, but mmcsd.ko now will refuse to load if it is incompatible
1105 The syntax of ipfw(8) named states was changed to avoid ambiguity.
1106 If you have used named states in the firewall rules, you need to modify
1107 them after installworld and before rebooting. Now named states must
1108 be prefixed with colon.
1111 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
1112 removed as the userland we provide cannot use them. The KMS version
1113 (sys/dev/drm2) supports the same hardware.
1116 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
1117 Please see the 20141231 entry below for information about prerequisites
1118 and upgrading, if you are not already using clang 3.5.0 or higher.
1121 The code that provides support for ZFS .zfs/ directory functionality
1122 has been reimplemented. It's not possible now to create a snapshot
1123 by mkdir under .zfs/snapshot/. That should be the only user visible
1127 EISA bus support has been removed. The WITH_EISA option is no longer
1131 MCA bus support has been removed.
1134 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
1135 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
1138 The EM_MULTIQUEUE kernel configuration option is deprecated now that
1139 the em(4) driver conforms to iflib specifications.
1142 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
1143 IFLIB. If you have a custom kernel configuration that excludes em(4)
1144 but you use igb(4), you need to re-add em(4) to your custom
1148 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
1149 Please see the 20141231 entry below for information about prerequisites
1150 and upgrading, if you are not already using clang 3.5.0 or higher.
1153 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
1154 Please see the 20141231 entry below for information about prerequisites
1155 and upgrading, if you are not already using clang 3.5.0 or higher.
1158 The layout of the pmap structure has changed for powerpc to put the pmap
1159 statistics at the front for all CPU variations. libkvm(3) and all tools
1160 that link against it need to be recompiled.
1163 isl(4) and cyapa(4) drivers now require a new driver,
1164 chromebook_platform(4), to work properly on Chromebook-class hardware.
1165 On other types of hardware the drivers may need to be configured using
1166 device hints. Please see the corresponding manual pages for details.
1169 The urtwn(4) driver was merged into rtwn(4) and now consists of
1170 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
1172 Also, firmware for RTL8188CE was renamed due to possible name
1173 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
1176 GNU rcs has been removed from base. It is available as packages:
1177 - rcs: Latest GPLv3 GNU rcs version.
1178 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
1182 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
1183 modules now requires that the kernel configuration contain the
1184 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
1187 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
1188 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
1191 Relocatable object files with the extension of .So have been renamed
1192 to use an extension of .pico instead. The purpose of this change is
1193 to avoid a name clash with shared libraries on case-insensitive file
1194 systems. On those file systems, foo.So is the same file as foo.so.
1197 GNU rcs has been turned off by default. It can (temporarily) be built
1198 again by adding WITH_RCS knob in src.conf.
1199 Otherwise, GNU rcs is available from packages:
1200 - rcs: Latest GPLv3 GNU rcs version.
1201 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
1204 The backup_uses_rcs functionality has been removed from rc.subr.
1207 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
1208 two separate components, QUEUE_MACRO_DEBUG_TRACE and
1209 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
1210 QUEUE_MACRO_DEBUG behavior.
1213 r304787 changed some ioctl interfaces between the iSCSI userspace
1214 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1215 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1219 The UDP receive code has been updated to only treat incoming UDP
1220 packets that were addressed to an L2 broadcast address as L3
1221 broadcast packets. It is not expected that this will affect any
1222 standards-conforming UDP application. The new behaviour can be
1223 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1227 Remove the openbsd_poll system call.
1228 __FreeBSD_version has been bumped because of this.
1231 The stable/11 branch has been created from head@r302406.
1234 The libc stub for the pipe(2) system call has been replaced with
1235 a wrapper that calls the pipe2(2) system call and the pipe(2)
1236 system call is now only implemented by the kernels that include
1237 "options COMPAT_FREEBSD10" in their config file (this is the
1238 default). Users should ensure that this option is enabled in
1239 their kernel or upgrade userspace to r302092 before upgrading their
1243 CAM will now strip leading spaces from SCSI disks' serial numbers.
1244 This will affect users who create UFS filesystems on SCSI disks using
1245 those disk's diskid device nodes. For example, if /etc/fstab
1246 previously contained a line like
1247 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
1248 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
1249 transforms like gmirror may also be affected. ZFS users should
1253 The bitstring(3) API has been updated with new functionality and
1254 improved performance. But it is binary-incompatible with the old API.
1255 Objects built with the new headers may not be linked against objects
1256 built with the old headers.
1259 The brk and sbrk functions have been removed from libc on arm64.
1260 Binutils from ports has been updated to not link to these
1261 functions and should be updated to the latest version before
1262 installing a new libc.
1265 The armv6 port now defaults to hard float ABI. Limited support
1266 for running both hardfloat and soft float on the same system
1267 is available using the libraries installed with -DWITH_LIBSOFT.
1268 This has only been tested as an upgrade path for installworld
1269 and packages may fail or need manual intervention to run. New
1270 packages will be needed.
1272 To update an existing self-hosted armv6hf system, you must add
1273 TARGET_ARCH=armv6 on the make command line for both the build
1274 and the install steps.
1277 Kernel modules compiled outside of a kernel build now default to
1278 installing to /boot/modules instead of /boot/kernel. Many kernel
1279 modules built this way (such as those in ports) already overrode
1280 KMODDIR explicitly to install into /boot/modules. However,
1281 manually building and installing a module from /sys/modules will
1282 now install to /boot/modules instead of /boot/kernel.
1285 The CAM I/O scheduler has been committed to the kernel. There should be
1286 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1287 list of known rogues that claim support for this but actually corrupt
1288 data is believed to be complete, be on the lookout for data
1289 corruption. The known rogue list is believed to be complete:
1291 o Crucial MX100, M550 drives with MU01 firmware.
1292 o Micron M510 and M550 drives with MU01 firmware.
1293 o Micron M500 prior to MU07 firmware
1294 o Samsung 830, 840, and 850 all firmwares
1295 o FCCT M500 all firmwares
1297 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1298 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1299 updated firmware. Black listed drives will work correctly because these
1300 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1301 this list is the same as found in Linux, it's believed there are no
1302 other rogues in the market place. All other models from the above
1305 To be safe, if you are at all concerned, you can quirk each of your
1306 drives to prevent NCQ from being sent by setting:
1307 kern.cam.ada.X.quirks="0x2"
1308 in loader.conf. If the drive requires the 4k sector quirk, set the
1309 quirks entry to 0x3.
1312 The FAST_DEPEND build option has been removed and its functionality is
1313 now the one true way. The old mkdep(1) style of 'make depend' has
1314 been removed. See 20160311 for further details.
1317 Resource range types have grown from unsigned long to uintmax_t. All
1318 drivers, and anything using libdevinfo, need to be recompiled.
1321 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1322 builds. It no longer runs mkdep(1) during 'make depend', and the
1323 'make depend' stage can safely be skipped now as it is auto ran
1324 when building 'make all' and will generate all SRCS and DPSRCS before
1325 building anything else. Dependencies are gathered at compile time with
1326 -MF flags kept in separate .depend files per object file. Users should
1327 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1328 stale .depend files.
1331 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1332 kernel modules. Therefore, if you load any kernel modules at boot time,
1333 please install the boot loaders after you install the kernel, but before
1337 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1338 make installkernel KERNCONF=YOUR_KERNEL_HERE
1339 make -C sys/boot install
1340 <reboot in single user>
1342 Then follow the usual steps, described in the General Notes section,
1346 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1347 see the 20141231 entry below for information about prerequisites and
1348 upgrading, if you are not already using clang 3.5.0 or higher.
1351 The AIO subsystem is now a standard part of the kernel. The
1352 VFS_AIO kernel option and aio.ko kernel module have been removed.
1353 Due to stability concerns, asynchronous I/O requests are only
1354 permitted on sockets and raw disks by default. To enable
1355 asynchronous I/O requests on all file types, set the
1356 vfs.aio.enable_unsafe sysctl to a non-zero value.
1359 The ELF object manipulation tool objcopy is now provided by the
1360 ELF Tool Chain project rather than by GNU binutils. It should be a
1361 drop-in replacement, with the addition of arm64 support. The
1362 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1363 to obtain the GNU version if necessary.
1366 Building ZFS pools on top of zvols is prohibited by default. That
1367 feature has never worked safely; it's always been prone to deadlocks.
1368 Using a zvol as the backing store for a VM guest's virtual disk will
1369 still work, even if the guest is using ZFS. Legacy behavior can be
1370 restored by setting vfs.zfs.vol.recursive=1.
1373 The NONE and HPN patches has been removed from OpenSSH. They are
1374 still available in the security/openssh-portable port.
1377 With the addition of ypldap(8), a new _ypldap user is now required
1378 during installworld. "mergemaster -p" can be used to add the user
1379 prior to installworld, as documented in the handbook.
1382 The tftp loader (pxeboot) now uses the option root-path directive. As a
1383 consequence it no longer looks for a pxeboot.4th file on the tftp
1384 server. Instead it uses the regular /boot infrastructure as with the
1388 The code to start recording plug and play data into the modules has
1389 been committed. While the old tools will properly build a new kernel,
1390 a number of warnings about "unknown metadata record 4" will be produced
1391 for an older kldxref. To avoid such warnings, make sure to rebuild
1392 the kernel toolchain (or world). Make sure that you have r292078 or
1393 later when trying to build 292077 or later before rebuilding.
1396 Debug data files are now built by default with 'make buildworld' and
1397 installed with 'make installworld'. This facilitates debugging but
1398 requires more disk space both during the build and for the installed
1399 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1403 r291527 changed the internal interface between the nfsd.ko and
1404 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1405 __FreeBSD_version has been bumped because of this.
1408 Add support for unicode collation strings leads to a change of
1409 order of files listed by ls(1) for example. To get back to the old
1410 behaviour, set LC_COLLATE environment variable to "C".
1412 Databases administrators will need to reindex their databases given
1413 collation results will be different.
1415 Due to a bug in install(1) it is recommended to remove the ancient
1416 locales before running make installworld.
1418 rm -rf /usr/share/locale/*
1421 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1422 libcrypto.so.7 or libssl.so.7 must be recompiled.
1425 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1426 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1427 should be replaced with isp_2400 and isp_2500 modules respectively.
1430 The build previously allowed using 'make -n' to not recurse into
1431 sub-directories while showing what commands would be executed, and
1432 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1433 and 'make -N' will not.
1436 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1437 and etcupdate will now use this file. A custom sendmail.cf is now
1438 updated via this mechanism rather than via installworld. If you had
1439 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1440 want to remove the exclusion or change it to "always install".
1441 /etc/mail/sendmail.cf is now managed the same way regardless of
1442 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1443 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1446 Compatibility shims for legacy ATA device names have been removed.
1447 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1448 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1449 environment variables, /dev/ad* and /dev/ar* symbolic links.
1452 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1453 Please see the 20141231 entry below for information about prerequisites
1454 and upgrading, if you are not already using clang 3.5.0 or higher.
1457 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1458 and renamed from .symbols to .debug. This reduces the size requirements
1459 on the boot partition or file system and provides consistency with
1460 userland debug files.
1462 When using the supported kernel installation method the
1463 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1464 as is done with /boot/kernel.
1466 Developers wishing to maintain the historical behavior of installing
1467 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1470 The wireless drivers had undergone changes that remove the 'parent
1471 interface' from the ifconfig -l output. The rc.d network scripts
1472 used to check presence of a parent interface in the list, so old
1473 scripts would fail to start wireless networking. Thus, etcupdate(3)
1474 or mergemaster(8) run is required after kernel update, to update your
1475 rc.d scripts in /etc.
1478 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1479 These configurations are now automatically interpreted as
1480 'scrub fragment reassemble'.
1483 Kernel-loadable modules for the random(4) device are back. To use
1484 them, the kernel must have
1487 options RANDOM_LOADABLE
1489 kldload(8) can then be used to load random_fortuna.ko
1490 or random_yarrow.ko. Please note that due to the indirect
1491 function calls that the loadable modules need to provide,
1492 the build-in variants will be slightly more efficient.
1494 The random(4) kernel option RANDOM_DUMMY has been retired due to
1495 unpopularity. It was not all that useful anyway.
1498 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1499 Control over building the ELF Tool Chain tools is now provided by
1500 the WITHOUT_TOOLCHAIN knob.
1503 The polarity of Pulse Per Second (PPS) capture events with the
1504 uart(4) driver has been corrected. Prior to this change the PPS
1505 "assert" event corresponded to the trailing edge of a positive PPS
1506 pulse and the "clear" event was the leading edge of the next pulse.
1508 As the width of a PPS pulse in a typical GPS receiver is on the
1509 order of 1 millisecond, most users will not notice any significant
1510 difference with this change.
1512 Anyone who has compensated for the historical polarity reversal by
1513 configuring a negative offset equal to the pulse width will need to
1514 remove that workaround.
1517 The default group assigned to /dev/dri entries has been changed
1518 from 'wheel' to 'video' with the id of '44'. If you want to have
1519 access to the dri devices please add yourself to the video group
1522 # pw groupmod video -m $USER
1525 The menu.rc and loader.rc files will now be replaced during
1526 upgrades. Please migrate local changes to menu.rc.local and
1527 loader.rc.local instead.
1530 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1531 strings and strip have been removed. The src.conf(5) knob
1532 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1535 As ZFS requires more kernel stack pages than is the default on some
1536 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1537 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1539 Please consider using 'options KSTACK_PAGES=X' where X is greater
1540 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1543 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1544 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1545 default, i.e., they will not contain "::". For example, instead
1546 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1547 to have a more specific match, such as different map entries for
1548 IPv6:0:0 vs IPv6:0. This change requires that configuration
1549 data (including maps, files, classes, custom ruleset, etc.) must
1550 use the same format, so make certain such configuration data is
1551 upgrading. As a very simple check search for patterns like
1552 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1553 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1554 the cf option UseCompressedIPv6Addresses.
1557 The default kernel entropy-processing algorithm is now
1558 Fortuna, replacing Yarrow.
1560 Assuming you have 'device random' in your kernel config
1561 file, the configurations allow a kernel option to override
1562 this default. You may choose *ONE* of:
1564 options RANDOM_YARROW # Legacy /dev/random algorithm.
1565 options RANDOM_DUMMY # Blocking-only driver.
1567 If you have neither, you get Fortuna. For most people,
1568 read no further, Fortuna will give a /dev/random that works
1569 like it always used to, and the difference will be irrelevant.
1571 If you remove 'device random', you get *NO* kernel-processed
1572 entropy at all. This may be acceptable to folks building
1573 embedded systems, but has complications. Carry on reading,
1574 and it is assumed you know what you need.
1576 *PLEASE* read random(4) and random(9) if you are in the
1577 habit of tweaking kernel configs, and/or if you are a member
1578 of the embedded community, wanting specific and not-usual
1579 behaviour from your security subsystems.
1581 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1582 random', you will NOT have a functioning /dev/random, and
1583 many cryptographic features will not work, including SSH.
1584 You may also find strange behaviour from the random(3) set
1585 of library functions, in particular sranddev(3), srandomdev(3)
1586 and arc4random(3). The reason for this is that the KERN_ARND
1587 sysctl only returns entropy if it thinks it has some to
1588 share, and with RANDOM_DUMMY or no 'device random' this
1592 An additional fix for the issue described in the 20150614 sendmail
1593 entry below has been committed in revision 284717.
1596 FreeBSD's old make (fmake) has been removed from the system. It is
1597 available as the devel/fmake port or via pkg install fmake.
1600 The fix for the issue described in the 20150614 sendmail entry
1601 below has been committed in revision 284436. The work
1602 around described in that entry is no longer needed unless the
1603 default setting is overridden by a confDH_PARAMETERS configuration
1604 setting of '5' or pointing to a 512 bit DH parameter file.
1607 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1608 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1609 and devel/kyua to version 0.20+ and adjust any calling code to work
1610 with Kyuafile and kyua.
1613 The import of openssl to address the FreeBSD-SA-15:10.openssl
1614 security advisory includes a change which rejects handshakes
1615 with DH parameters below 768 bits. sendmail releases prior
1616 to 8.15.2 (not yet released), defaulted to a 512 bit
1617 DH parameter setting for client connections. To work around
1618 this interoperability, sendmail can be configured to use a
1619 2048 bit DH parameter by:
1621 1. Edit /etc/mail/`hostname`.mc
1622 2. If a setting for confDH_PARAMETERS does not exist or
1623 exists and is set to a string beginning with '5',
1624 replace it with '2'.
1625 3. If a setting for confDH_PARAMETERS exists and is set to
1626 a file path, create a new file with:
1627 openssl dhparam -out /path/to/file 2048
1628 4. Rebuild the .cf file:
1629 cd /etc/mail/; make; make install
1630 5. Restart sendmail:
1631 cd /etc/mail/; make restart
1633 A sendmail patch is coming, at which time this file will be
1637 Generation of legacy formatted entries have been disabled by default
1638 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1639 entries were converted to use the new format by default when the new,
1640 machine independent format have been added and supported since FreeBSD
1643 Please see the pwd_mkdb(8) manual page for further details.
1646 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1647 20141231 entry below for information about prerequisites and upgrading,
1648 if you are not already using 3.5.0 or higher.
1651 TI platform code switched to using vendor DTS files and this update
1652 may break existing systems running on Beaglebone, Beaglebone Black,
1655 - dtb files should be regenerated/reinstalled. Filenames are the
1656 same but content is different now
1657 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1658 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1659 addressing scheme is now pin 25 on /dev/gpioc3.
1660 - Pandaboard: /etc/ttys should be updated, serial console device is
1661 now /dev/ttyu2, not /dev/ttyu0
1664 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1665 If you need the GNU extension from groff soelim(1), install groff
1666 from package: pkg install groff, or via ports: textproc/groff.
1669 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1670 defined in symlink(7); previously symlinks were silently ignored.
1673 The const qualifier has been removed from iconv(3) to comply with
1674 POSIX. The ports tree is aware of this from r384038 onwards.
1677 Libraries specified by LIBADD in Makefiles must have a corresponding
1678 DPADD_<lib> variable to ensure correct dependencies. This is now
1679 enforced in src.libnames.mk.
1682 From legacy ata(4) driver was removed support for SATA controllers
1683 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1684 Kernel modules ataahci and ataadaptec were removed completely,
1685 replaced by ahci and mvs modules respectively.
1688 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1689 the 20141231 entry below for information about prerequisites and
1690 upgrading, if you are not already using 3.5.0 or higher.
1693 The 32-bit PowerPC kernel has been changed to a position-independent
1694 executable. This can only be booted with a version of loader(8)
1695 newer than January 31, 2015, so make sure to update both world and
1696 kernel before rebooting.
1699 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1700 but before r278950, the RNG was not seeded properly. Immediately
1701 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1702 ssh keys or openssl keys) that were generated w/ a kernel from that
1703 range. This does not affect programs that directly used /dev/random
1704 or /dev/urandom. All userland uses of arc4random(3) are affected.
1707 The autofs(4) ABI was changed in order to restore binary compatibility
1708 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1709 with the new kernel.
1712 The powerpc64 kernel has been changed to a position-independent
1713 executable. This can only be booted with a new version of loader(8),
1714 so make sure to update both world and kernel before rebooting.
1717 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1718 only release, no new features have been added. Please see the 20141231
1719 entry below for information about prerequisites and upgrading, if you
1720 are not already using 3.5.0.
1723 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1724 taken from the ELF Tool Chain project rather than GNU binutils. They
1725 should be drop-in replacements, with the addition of arm64 support.
1726 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1727 binutils tools, if necessary. See 20150805 for updated information.
1730 The default Unbound configuration now enables remote control
1731 using a local socket. Users who have already enabled the
1732 local_unbound service should regenerate their configuration
1733 by running "service local_unbound setup" as root.
1736 The GNU texinfo and GNU info pages have been removed.
1737 To be able to view GNU info pages please install texinfo from ports.
1740 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1742 As of this release, a prerequisite for building clang, llvm and lldb is
1743 a C++11 capable compiler and C++11 standard library. This means that to
1744 be able to successfully build the cross-tools stage of buildworld, with
1745 clang as the bootstrap compiler, your system compiler or cross compiler
1746 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1747 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1750 On any standard FreeBSD 10.x or 11.x installation, where clang and
1751 libc++ are on by default (that is, on x86 or arm), this should work out
1754 On 9.x installations where clang is enabled by default, e.g. on x86 and
1755 powerpc, libc++ will not be enabled by default, so libc++ should be
1756 built (with clang) and installed first. If both clang and libc++ are
1757 missing, build clang first, then use it to build libc++.
1759 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1760 the instructions for 9.x above.
1762 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1763 default, and do not build clang.
1765 Many embedded systems are resource constrained, and will not be able to
1766 build clang in a reasonable time, or in some cases at all. In those
1767 cases, cross building bootable systems on amd64 is a workaround.
1769 This new version of clang introduces a number of new warnings, of which
1770 the following are most likely to appear:
1774 This warns in two cases, for both C and C++:
1775 * When the code is trying to take the absolute value of an unsigned
1776 quantity, which is effectively a no-op, and almost never what was
1777 intended. The code should be fixed, if at all possible. If you are
1778 sure that the unsigned quantity can be safely cast to signed, without
1779 loss of information or undefined behavior, you can add an explicit
1780 cast, or disable the warning.
1782 * When the code is trying to take an absolute value, but the called
1783 abs() variant is for the wrong type, which can lead to truncation.
1784 If you want to disable the warning instead of fixing the code, please
1785 make sure that truncation will not occur, or it might lead to unwanted
1788 -Wtautological-undefined-compare and
1789 -Wundefined-bool-conversion
1791 These warn when C++ code is trying to compare 'this' against NULL, while
1792 'this' should never be NULL in well-defined C++ code. However, there is
1793 some legacy (pre C++11) code out there, which actively abuses this
1794 feature, which was less strictly defined in previous C++ versions.
1796 Squid and openjdk do this, for example. The warning can be turned off
1797 for C++98 and earlier, but compiling the code in C++11 mode might result
1798 in unexpected behavior; for example, the parts of the program that are
1799 unreachable could be optimized away.
1802 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1803 kernel sources have been removed. The .h files remain, since some
1804 utilities include them. This will need to be fixed later.
1805 If "mount -t oldnfs ..." is attempted, it will fail.
1806 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1807 the utilities will report errors.
1810 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1811 directories to top level SUBDIR variable when their parent
1812 directory is included in LOCAL_DIRS. Users with build systems with
1813 such hierarchies and without SUBDIR entries in the parent
1814 directory Makefiles should add them or add the directories to
1818 faith(4) and faithd(8) have been removed from the base system. Faith
1819 has been obsolete for a very long time.
1822 vt(4), the new console driver, is enabled by default. It brings
1823 support for Unicode and double-width characters, as well as
1824 support for UEFI and integration with the KMS kernel video
1827 You may need to update your console settings in /etc/rc.conf,
1828 most probably the keymap. During boot, /etc/rc.d/syscons will
1829 indicate what you need to do.
1831 vt(4) still has issues and lacks some features compared to
1832 syscons(4). See the wiki for up-to-date information:
1833 https://wiki.freebsd.org/Newcons
1835 If you want to keep using syscons(4), you can do so by adding
1836 the following line to /boot/loader.conf:
1840 pjdfstest has been integrated into kyua as an opt-in test suite.
1841 Please see share/doc/pjdfstest/README for more details on how to
1845 gperf has been removed from the base system for architectures
1846 that use clang. Ports that require gperf will obtain it from the
1850 pjdfstest has been moved from tools/regression/pjdfstest to
1854 At svn r271982, The default linux compat kernel ABI has been adjusted
1855 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1856 update. If you wish to continue using the linux-f10 compat ports,
1857 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1858 encouraged to update their linux-compat packages to linux-c6 during
1859 their next update cycle.
1862 The ofwfb driver, used to provide a graphics console on PowerPC when
1863 using vt(4), no longer allows mmap() of all physical memory. This
1864 will prevent Xorg on PowerPC with some ATI graphics cards from
1865 initializing properly unless x11-servers/xorg-server is updated to
1869 The xdev targets have been converted to using TARGET and
1870 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1873 The default unbound configuration has been modified to address
1874 issues with reverse lookups on networks that use private
1875 address ranges. If you use the local_unbound service, run
1876 "service local_unbound setup" as root to regenerate your
1877 configuration, then "service local_unbound reload" to load the
1881 The GNU texinfo and GNU info pages are not built and installed
1882 anymore, WITH_INFO knob has been added to allow to built and install
1884 UPDATE: see 20150102 entry on texinfo's removal
1887 The GNU readline library is now an INTERNALLIB - that is, it is
1888 statically linked into consumers (GDB and variants) in the base
1889 system, and the shared library is no longer installed. The
1890 devel/readline port is available for third party software that
1894 The Itanium architecture (ia64) has been removed from the list of
1895 known architectures. This is the first step in the removal of the
1899 Commit r268115 has added NFSv4.1 server support, merged from
1900 projects/nfsv4.1-server. Since this includes changes to the
1901 internal interfaces between the NFS related modules, a full
1902 build of the kernel and modules will be necessary.
1903 __FreeBSD_version has been bumped.
1906 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1907 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1908 which differs from the behaviour controlled by this knob.)
1911 Maximal length of the serial number in CTL was increased from 16 to
1912 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1913 and ctld, need to be rebuilt to work with a new kernel.
1916 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1917 1 respectively to match the upstream numbers. They were out of
1918 sync because, when they were originally added to FreeBSD, the
1919 upstream versions were not respected. These libraries are private
1920 and not yet built by default, so renumbering them should be a
1921 non-issue. However, unclean source trees will yield broken test
1922 programs once the operator executes "make delete-old-libs" after a
1923 "make installworld".
1925 Additionally, the atf-sh binary was made private by moving it into
1926 /usr/libexec/. Already-built shell test programs will keep the
1927 path to the old binary so they will break after "make delete-old"
1930 If you are using WITH_TESTS=yes (not the default), wipe the object
1931 tree and rebuild from scratch to prevent spurious test failures.
1932 This is only needed once: the misnumbered libraries and misplaced
1933 binaries have been added to OptionalObsoleteFiles.inc so they will
1934 be removed during a clean upgrade.
1937 Clang and llvm have been upgraded to 3.4.1 release.
1940 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1941 be removed to avoid issues in the future (and has been added to
1945 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1946 past, it affected all builds that used the bsd.*.mk files. The old
1947 behavior was a bug, but people may have relied upon it. To get this
1948 behavior back, you can .include /etc/src.conf from /etc/make.conf
1949 (which is still global and isn't changed). This also changes the
1950 behavior of incremental builds inside the tree of individual
1951 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1952 Although this has survived make universe and some upgrade scenarios,
1953 other upgrade scenarios may have broken. At least one form of
1954 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1955 as well... In cases where MAKESYSPATH isn't working with this
1956 setting, you'll need to set it to the full path to your tree.
1958 One side effect of all this cleaning up is that bsd.compiler.mk
1959 is no longer implicitly included by bsd.own.mk. If you wish to
1960 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1964 The lindev device has been removed since /dev/full has been made a
1965 standard device. __FreeBSD_version has been bumped.
1968 The knob WITHOUT_VI was added to the base system, which controls
1969 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1970 in order to reorder files share/termcap and didn't build ex(1) as a
1971 build tool, so building/installing with WITH_VI is highly advised for
1972 build hosts for older releases.
1974 This issue has been fixed in stable/9 and stable/10 in r277022 and
1975 r276991, respectively.
1978 The YES_HESIOD knob has been removed. It has been obsolete for
1979 a decade. Please move to using WITH_HESIOD instead or your builds
1980 will silently lack HESIOD.
1983 The uart(4) driver has been changed with respect to its handling
1984 of the low-level console. Previously the uart(4) driver prevented
1985 any process from changing the baudrate or the CLOCAL and HUPCL
1986 control flags. By removing the restrictions, operators can make
1987 changes to the serial console port without having to reboot.
1988 However, when getty(8) is started on the serial device that is
1989 associated with the low-level console, a misconfigured terminal
1990 line in /etc/ttys will now have a real impact.
1991 Before upgrading the kernel, make sure that /etc/ttys has the
1992 serial console device configured as 3wire without baudrate to
1993 preserve the previous behaviour. E.g:
1994 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1997 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1998 to improve performance. To re-enable it, if needed, run rpcbind
1999 with command line option -W.
2002 Switched back to the GPL dtc compiler due to updates in the upstream
2003 dts files not being supported by the BSDL dtc compiler. You will need
2004 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
2005 may result while building dtb files during a kernel build if you fail
2006 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
2009 Clang and llvm have been upgraded to 3.4 release.
2012 The nve(4) driver has been removed. Please use the nfe(4) driver
2013 for NVIDIA nForce MCP Ethernet adapters instead.
2016 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
2017 This could cause certain C++ applications using shared libraries built
2018 against the previous version of libc++ to crash. The incompatibility
2019 has now been fixed, but any C++ applications or shared libraries built
2020 between r261283 and r261801 should be recompiled.
2023 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
2024 capability mode support. Please note that enabling the feature in
2025 kernel is still highly recommended.
2028 OpenSSH is now built with sandbox support, and will use sandbox as
2029 the default privilege separation method. This requires Capsicum
2030 capability mode support in kernel.
2033 The libelf and libdwarf libraries have been updated to newer
2034 versions from upstream. Shared library version numbers for
2035 these two libraries were bumped. Any ports or binaries
2036 requiring these two libraries should be recompiled.
2037 __FreeBSD_version is bumped to 1100006.
2040 If a Makefile in a tests/ directory was auto-generating a Kyuafile
2041 instead of providing an explicit one, this would prevent such
2042 Makefile from providing its own Kyuafile in the future during
2043 NO_CLEAN builds. This has been fixed in the Makefiles but manual
2044 intervention is needed to clean an objdir if you use NO_CLEAN:
2045 # find /usr/obj -name Kyuafile | xargs rm -f
2048 The behavior of gss_pseudo_random() for the krb5 mechanism
2049 has changed, for applications requesting a longer random string
2050 than produced by the underlying enctype's pseudo-random() function.
2051 In particular, the random string produced from a session key of
2052 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
2053 be different at the 17th octet and later, after this change.
2054 The counter used in the PRF+ construction is now encoded as a
2055 big-endian integer in accordance with RFC 4402.
2056 __FreeBSD_version is bumped to 1100004.
2059 The WITHOUT_ATF build knob has been removed and its functionality
2060 has been subsumed into the more generic WITHOUT_TESTS. If you were
2061 using the former to disable the build of the ATF libraries, you
2062 should change your settings to use the latter.
2065 The default version of mtree is nmtree which is obtained from
2066 NetBSD. The output is generally the same, but may vary
2067 slightly. If you found you need identical output adding
2068 "-F freebsd9" to the command line should do the trick. For the
2069 time being, the old mtree is available as fmtree.
2072 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
2073 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
2074 1.1.4_8 and verify bsdyml not linked in, before running "make
2076 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
2078 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
2081 The stable/10 branch has been created in subversion from head
2088 Sometimes, obscure build problems are the result of environment
2089 poisoning. This can happen because the make utility reads its
2090 environment when searching for values for global variables. To run
2091 your build attempts in an "environmental clean room", prefix all make
2092 commands with 'env -i '. See the env(1) manual page for more details.
2093 Occasionally a build failure will occur with "make -j" due to a race
2094 condition. If this happens try building again without -j, and please
2095 report a bug if it happens consistently.
2097 When upgrading from one major version to another it is generally best to
2098 upgrade to the latest code in the currently installed branch first, then
2099 do an upgrade to the new branch. This is the best-tested upgrade path,
2100 and has the highest probability of being successful. Please try this
2101 approach if you encounter problems with a major version upgrade. Since
2102 the stable 4.x branch point, one has generally been able to upgrade from
2103 anywhere in the most recent stable branch to head / current (or even the
2104 last couple of stable branches). See the top of this file when there's
2107 The update process will emit an error on an attempt to perform a build
2108 or install from a FreeBSD version below the earliest supported version.
2109 When updating from an older version the update should be performed one
2110 major release at a time, including running `make delete-old` at each
2113 When upgrading a live system, having a root shell around before
2114 installing anything can help undo problems. Not having a root shell
2115 around can lead to problems if pam has changed too much from your
2116 starting point to allow continued authentication after the upgrade.
2118 This file should be read as a log of events. When a later event changes
2119 information of a prior event, the prior event should not be deleted.
2120 Instead, a pointer to the entry with the new information should be
2121 placed in the old entry. Readers of this file should also sanity check
2122 older entries before relying on them blindly. Authors of new entries
2123 should write them with this in mind.
2127 When upgrading the boot ZFS pool to a new version, always follow
2130 1.) recompile and reinstall the ZFS boot loader and boot block
2131 (this is part of "make buildworld" and "make installworld")
2133 2.) update the ZFS boot block on your boot drive
2135 The following example updates the ZFS boot block on the first
2136 partition (freebsd-boot) of a GPT partitioned drive ada0:
2137 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
2139 Non-boot pools do not need these updates.
2143 If you are updating from a prior version of FreeBSD (even one just
2144 a few days old), you should follow this procedure. It is the most
2145 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2147 make kernel-toolchain
2148 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2149 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2151 To test a kernel once
2152 ---------------------
2153 If you just want to boot a kernel once (because you are not sure
2154 if it works, or if you want to boot a known bad kernel to provide
2155 debugging information) run
2156 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2157 nextboot -k testkernel
2159 To rebuild everything and install it on the current system.
2160 -----------------------------------------------------------
2161 # Note: sometimes if you are running current you gotta do more than
2162 # is listed here if you are upgrading from a really old current.
2164 <make sure you have good level 0 dumps>
2166 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2167 make installkernel KERNCONF=YOUR_KERNEL_HERE
2169 <reboot in single user> [3]
2176 To cross-install current onto a separate partition
2177 --------------------------------------------------
2178 # In this approach we use a separate partition to hold
2179 # current's root, 'usr', and 'var' directories. A partition
2180 # holding "/", "/usr" and "/var" should be about 2GB in
2183 <make sure you have good level 0 dumps>
2186 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2187 <maybe newfs current's root partition>
2188 <mount current's root partition on directory ${CURRENT_ROOT}>
2189 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
2190 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2191 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2192 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2193 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2194 <reboot into current>
2195 <do a "native" rebuild/install as described in the previous section>
2196 <maybe install compatibility libraries from ports/misc/compat*>
2200 To upgrade in-place from stable to current
2201 ----------------------------------------------
2202 <make sure you have good level 0 dumps>
2204 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
2205 make installkernel KERNCONF=YOUR_KERNEL_HERE
2207 <reboot in single user> [3]
2214 Make sure that you've read the UPDATING file to understand the
2215 tweaks to various things you need. At this point in the life
2216 cycle of current, things change often and you are on your own
2217 to cope. The defaults can also change, so please read ALL of
2218 the UPDATING entries.
2220 Also, if you are tracking -current, you must be subscribed to
2221 freebsd-current@freebsd.org. Make sure that before you update
2222 your sources that you have read and understood all the recent
2223 messages there. If in doubt, please track -stable which has
2224 much fewer pitfalls.
2226 [1] If you have third party modules, such as vmware, you
2227 should disable them at this point so they don't crash your
2230 [3] From the bootblocks, boot -s, and then do
2234 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed
2235 cd src # full path to source
2236 adjkerntz -i # if CMOS is wall time
2237 Also, when doing a major release upgrade, it is required that
2238 you boot into single user mode to do the installworld.
2240 [4] Note: This step is non-optional. Failure to do this step
2241 can result in a significant reduction in the functionality of the
2242 system. Attempting to do it by hand is not recommended and those
2243 that pursue this avenue should read this file carefully, as well
2244 as the archives of freebsd-current and freebsd-hackers mailing lists
2245 for potential gotchas. The -U option is also useful to consider.
2246 See mergemaster(8) for more information.
2248 [5] Usually this step is a no-op. However, from time to time
2249 you may need to do this if you get unknown user in the following
2250 step. It never hurts to do it all the time. You may need to
2251 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2252 install) after the buildworld before this step if you last updated
2253 from current before 20130425 or from -stable before 20130430.
2255 [6] This only deletes old files and directories. Old libraries
2256 can be deleted by "make delete-old-libs", but you have to make
2257 sure that no program is using those libraries anymore.
2259 [8] The new kernel must be able to run existing binaries used by an
2260 installworld. When upgrading across major versions, the new kernel's
2261 configuration must include the correct COMPAT_FREEBSD<n> option for
2262 existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure
2263 to do so may leave you with a system that is hard to boot to recover. A
2264 GENERIC kernel will include suitable compatibility options to run
2265 binaries from older branches. Note that the ability to run binaries
2266 from unsupported branches is not guaranteed.
2268 Make sure that you merge any new devices from GENERIC since the
2269 last time you updated your kernel config file. Options also
2270 change over time, so you may need to adjust your custom kernels
2273 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2274 "?=" instead of the "=" assignment operator, so that buildworld can
2275 override the CPUTYPE if it needs to.
2277 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2278 not on the command line, or in /etc/make.conf. buildworld will
2279 warn if it is improperly defined.
2282 This file contains a list, in reverse chronological order, of major
2283 breakages in tracking -current. It is not guaranteed to be a complete
2284 list of such breakages, and only contains entries since September 23, 2011.
2285 If you need to see UPDATING entries from before that date, you will need
2286 to fetch an UPDATING file from an older FreeBSD release.
2288 Copyright information:
2290 Copyright 1998-2009 M. Warner Losh <imp@FreeBSD.org>
2292 Redistribution, publication, translation and use, with or without
2293 modification, in full or in part, in any form or format of this
2294 document are permitted without further permission from the author.
2296 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2297 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2298 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2299 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2300 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2301 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2302 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2303 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2304 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2305 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2306 POSSIBILITY OF SUCH DAMAGE.
2308 Contact Warner Losh if you have any questions about your use of