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 OpenZFS support has been integrated. Do not upgrade root pools until
31 the loader is updated to support zstd. Furthermore, we caution against
32 'zpool upgrade' for the next few weeks. The change should be transparent
33 unless you want to use new features.
35 Not all "NO_CLEAN" build scenarios work across these changes. Many
36 scenarios have been tested and fixed, but rebuilding kernels without
37 rebuilding world may fail.
40 The resume code now notifies devd with the 'kernel' system
41 rather than the old 'kern' subsystem to be consistent with
42 other use. The old notification will be created as well, but
43 will be removed prior to FreeBSD 14.0.
46 r362275 changed the internal API between the kernel RPC and the
47 NFS modules. As such, all the modules must be recompiled from
51 r364330 modified the internal API used between the NFS modules.
52 As such, all the NFS modules must be re-compiled from sources.
55 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
56 been upgraded to 11.0.0. Please see the 20141231 entry below for
57 information about prerequisites and upgrading, if you are not already
58 using clang 3.5.0 or higher.
61 r364092 modified the internal ABI used between the kernel NFS
62 modules. As such, all of these modules need to be rebuilt
63 from sources, so a version bump was done.
66 Makefile.inc has been updated to work around the issue documented in
67 20200729. It was a case where the optimization of using symbolic links
68 to point to binaries created a situation where we'd run new binaries
69 with old libraries starting midway through the installworld process.
72 r363679 has redefined some undefined behavior in regcomp(3); notably,
73 extraneous escapes of most ordinary characters will no longer be
74 accepted. An exp-run has identified all of the problems with this in
75 ports, but other non-ports software may need extra escapes removed to
78 Because of this change, installworld may encounter the following error
79 from rtld: Undefined symbol "regcomp@FBSD_1.6" -- It is imperative that
80 you do not halt installworld. Instead, let it run to completion (whether
81 successful or not) and run installworld once more.
84 A new implementation of bc and dc has been imorted in r362681. This
85 implementation corrects non-conformant behavior of the previous bc
86 and adds GNU bc compatible options. It offers a number of extensions,
87 is much faster on large values, and has support for message catalogs
88 (a number of languages are already supported, contributions of further
89 languages welcome). The option WITHOUT_GH_BC can be used to build the
90 world with the previous versions of bc and dc.
93 r362639 changed the internal API used between the NFS kernel modules.
94 As such, they all need to be rebuilt from sources.
97 r362158 changed the arguments for VFS_CHECKEXP(). As such, any
98 out of tree file systems need to be modified and rebuilt.
99 Also, any file systems that are modules must be rebuilt.
102 read(2) of a directory fd is now rejected by default. root may
103 re-enable it for system root only on non-ZFS filesystems with the
104 security.bsd.allow_read_dir sysctl(8) MIB if
105 security.bsd.suser_enabled=1.
107 It may be advised to setup aliases for grep to default to `-d skip` if
108 commonly non-recursively grepping a list that includes directories and
109 the potential for the resulting stderr output is not tolerable. Example
110 aliases are now installed, commented out, in /root/.cshrc and
114 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
115 been upgraded to 10.0.1. Please see the 20141231 entry below for
116 information about prerequisites and upgrading, if you are not already
117 using clang 3.5.0 or higher.
120 Support for obsolete compilers has been removed from the build system.
121 Clang 6 and GCC 6.4 are the minimum supported versions.
124 closefrom(2) has been moved under COMPAT12, and replaced in libc with a
125 stub that calls close_range(2). If using a custom kernel configuration,
126 you may want to ensure that the COMPAT_FREEBSD12 option is included, as
127 a slightly older -CURRENT userland and older FreeBSD userlands may not
128 be functional without closefrom(2).
131 Upstream DTS from Linux 5.6 was merged and they now have the SID
132 and THS (Secure ID controller and THermal Sensor) node present.
133 The DTB overlays have now been removed from the tree for the H3/H5 and
134 A64 SoCs and the aw_sid and aw_thermal driver have been updated to
135 deal with upstream DTS. If you are using those overlays you need to
136 remove them from loader.conf and update the DTBs on the FAT partition.
139 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
140 been upgraded to 10.0.0. Please see the 20141231 entry below for
141 information about prerequisites and upgrading, if you are not already
142 using clang 3.5.0 or higher.
145 The amd(8) automount daemon has been removed from the source tree.
146 As of FreeBSD 10.1 autofs(5) is the preferred tool for automounting.
147 amd is still available in the sysutils/am-utils port.
150 Removed brooktree driver (bktr.4) from the tree.
153 The WITH_GPL_DTC option has been removed. The BSD-licenced device tree
154 compiler in usr.bin/dtc is used on all architectures which use dtc, and
155 the GPL dtc is available (if needed) from the sysutils/dtc port.
158 The WITHOUT_LLVM_LIBUNWIND option has been removed. LLVM's libunwind
159 is used by all supported CPU architectures.
162 GCC 4.2.1 has been removed from the tree. The WITH_GCC,
163 WITH_GCC_BOOTSTRAP, and WITH_GNUCXX options are no longer available.
164 Users who wish to build FreeBSD with GCC must use the external toolchain
168 ncurses has been updated to a newer version (6.2-20200215). Given the ABI
169 has changed, users will have to rebuild all the ports that are linked to
173 The size of struct vnet and the magic cookie have changed.
174 Users need to recompile libkvm and all modules using VIMAGE
175 together with their new kernel.
178 Defining the long deprecated NO_CTF, NO_DEBUG_FILES, NO_INSTALLLIB,
179 NO_MAN, NO_PROFILE, and NO_WARNS variables is now an error. Update
180 your Makefiles and scripts to define MK_<var>=no instead as required.
182 One exception to this is that program or library Makefiles should
183 define MAN to empty rather than setting MK_MAN=no.
186 Clang/LLVM is now the default compiler and LLD the default
190 make universe no longer uses GCC 4.2.1 on any architectures.
191 Architectures not supported by in-tree Clang/LLVM require an
192 external toolchain package.
195 GCC 4.2.1 is now not built by default, as part of the GCC 4.2.1
196 retirement plan. Specifically, the GCC, GCC_BOOTSTRAP, and GNUCXX
197 options default to off for all supported CPU architectures. As a
198 short-term transition aid they may be enabled via WITH_* options.
199 GCC 4.2.1 is expected to be removed from the tree on 2020-03-31.
202 Support for armv5 has been disconnected and is being removed. The
203 machine combination MACHINE=arm MACHINE_ARCH=arm is no longer valid.
204 You must now use a MACHINE_ARCH of armv6 or armv7. The default
205 MACHINE_ARCH for MACHINE=arm is now armv7.
208 Clang/LLVM is now the default compiler for all powerpc architectures.
209 LLD is now the default linker for powerpc64. The change for powerpc64
210 also includes a change to the ELFv2 ABI, incompatible with the existing
214 Kernel-loadable random(4) modules are no longer unloadable.
217 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
218 been upgraded to 9.0.1. Please see the 20141231 entry below for
219 information about prerequisites and upgrading, if you are not already
220 using clang 3.5.0 or higher.
223 r355677 has modified the internal interface used between the
224 NFS modules in the kernel. As such, they must all be upgraded
225 simultaneously. I will do a version bump for this.
228 The root certificates of the Mozilla CA Certificate Store have been
229 imported into the base system and can be managed with the certctl(8)
230 utility. If you have installed the security/ca_root_nss port or package
231 with the ETCSYMLINK option (the default), be advised that there may be
232 differences between those included in the port and those included in
233 base due to differences in nss branch used as well as general update
234 frequency. Note also that certctl(8) cannot manage certs in the
235 format used by the security/ca_root_nss port.
238 The amd(8) automount daemon has been disabled by default, and will be
239 removed in the future. As of FreeBSD 10.1 the autofs(5) is available
243 The nctgpio and wbwd drivers have been moved to the superio bus.
244 If you have one of these drivers in a kernel configuration, then
245 you should add device superio to it. If you use one of these drivers
246 as a module and you compile a custom set of modules, then you should
247 add superio to the set.
250 KPIs for network drivers to access interface addresses have changed.
251 Users need to recompile NIC driver modules together with kernel.
254 The net.link.tap.user_open sysctl no longer prevents user opening of
255 already created /dev/tapNN devices. Access is still controlled by
256 node permissions, just like tun devices. The net.link.tap.user_open
257 sysctl is now used only to allow users to perform devfs cloning of
258 tap devices, and the subsequent open may not succeed if the user is not
259 in the appropriate group. This sysctl may be deprecated/removed
260 completely in the future.
263 mips, powerpc, and sparc64 are no longer built as part of
264 universe / tinderbox unless MAKE_OBSOLETE_GCC is defined. If
265 not defined, mips, powerpc, and sparc64 builds will look for
266 the xtoolchain binaries and if installed use them for universe
267 builds. As llvm 9.0 becomes vetted for these architectures, they
268 will be removed from the list.
271 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
272 been upgraded to 9.0.0. Please see the 20141231 entry below for
273 information about prerequisites and upgrading, if you are not already
274 using clang 3.5.0 or higher.
277 The hpt27xx, hptmv, hptnr, and hptrr drivers have been removed from
278 GENERIC. They are available as modules and can be loaded by adding
279 to /boot/loader.conf hpt27xx_load="YES", hptmv_load="YES",
280 hptnr_load="YES", or hptrr_load="YES", respectively.
283 ntpd no longer by default locks its pages in memory, allowing them
284 to be paged out by the kernel. Use rlimit memlock to restore
285 historic BSD behaviour. For example, add "rlimit memlock 32"
286 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
289 Several of ping6's options have been renamed for better consistency
290 with ping. If you use any of -ARWXaghmrtwx, you must update your
291 scripts. See ping6(8) for details.
294 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
295 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
296 been removed from mount_fusefs(8). You can safely remove them from
297 your scripts, because they had no effect.
299 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
300 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
301 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
302 sysctls have been removed. If you felt the need to set any of them to
303 a non-default value, please tell asomers@FreeBSD.org why.
306 Default permissions on the /var/account/acct file (and copies of it
307 rotated by periodic daily scripts) are changed from 0644 to 0640
308 because the file contains sensitive information that should not be
309 world-readable. If the /var/account directory must be created by
310 rc.d/accounting, the mode used is now 0750. Admins who use the
311 accounting feature are encouraged to change the mode of an existing
312 /var/account directory to 0750 or 0700.
315 Entropy collection and the /dev/random device are no longer optional
316 components. The "device random" option has been removed.
317 Implementations of distilling algorithms can still be made loadable
318 with "options RANDOM_LOADABLE" (e.g., random_fortuna.ko).
321 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
322 been upgraded to 8.0.1. Please see the 20141231 entry below for
323 information about prerequisites and upgrading, if you are not already
324 using clang 3.5.0 or higher.
327 A fix was applied to i386 kernel modules to avoid panics with
328 dpcpu or vnet. Users need to recompile i386 kernel modules
329 having pcpu or vnet sections or they will refuse to load.
332 User-wired pages now have their own counter,
333 vm.stats.vm.v_user_wire_count. The vm.max_wired sysctl was renamed
334 to vm.max_user_wired and changed from an unsigned int to an unsigned
335 long. bhyve VMs wired with the -S are now subject to the user
336 wiring limit; the vm.max_user_wired sysctl may need to be tuned to
337 avoid running into the limit.
340 The IPSEC option has been removed from GENERIC. Users requiring
341 ipsec(4) must now load the ipsec(4) kernel module.
344 The tap(4) driver has been folded into tun(4), and the module has been
345 renamed to tuntap. You should update any kld_list="if_tap" or
346 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
347 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
348 module instead, and "device tap" or "device tun" entries in kernel
349 config files to select the tuntap device instead.
352 The following knobs have been added related to tradeoffs between
353 safe use of the random device and availability in the absence of
356 kern.random.initial_seeding.bypass_before_seeding: tunable; set
357 non-zero to bypass the random device prior to seeding, or zero to
358 block random requests until the random device is initially seeded.
359 For now, set to 1 (unsafe) by default to restore pre-r346250 boot
360 availability properties.
362 kern.random.initial_seeding.read_random_bypassed_before_seeding:
363 read-only diagnostic sysctl that is set when bypass is enabled and
364 read_random(9) is bypassed, to enable programmatic handling of this
365 initial condition, if desired.
367 kern.random.initial_seeding.arc4random_bypassed_before_seeding:
368 Similar to the above, but for for arc4random(9) initial seeding.
370 kern.random.initial_seeding.disable_bypass_warnings: tunable; set
371 non-zero to disable warnings in dmesg when the same conditions are
372 met as for the diagnostic sysctls above. Defaults to zero, i.e.,
373 produce warnings in dmesg when the conditions are met.
376 The loadable random module KPI has changed; the random_infra_init()
377 routine now requires a 3rd function pointer for a bool (*)(void)
378 method that returns true if the random device is seeded (and
379 therefore unblocked).
382 r345895 reverts r320698. This implies that an nfsuserd(8) daemon
383 built from head sources between r320757 (July 6, 2017) and
384 r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
385 is added to the command line.
386 nfsuserd daemons built from head sources that are post-r338192 are
387 not affected and should continue to work.
390 The fuse(4) module has been renamed to fusefs(4) for consistency with
391 other filesystems. You should update any kld_load="fuse" entries in
392 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
393 "options FUSE" entries in kernel config files.
396 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
397 8.0.0. Please see the 20141231 entry below for information about
398 prerequisites and upgrading, if you are not already using clang 3.5.0
402 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
403 compiled into your custom kernel, add 'device xz' statement to the
407 drm and drm2 have been removed from the tree. Please see
408 https://wiki.freebsd.org/Graphics for the latest information on
409 migrating to the drm ports.
412 Iflib is no longer unconditionally compiled into the kernel. Drivers
413 using iflib and statically compiled into the kernel, now require
414 the 'device iflib' config option. For the same drivers loaded as
415 modules on kernels not having 'device iflib', the iflib.ko module
416 is loaded automatically.
419 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
420 options no longer exist since r343219 and r343427 respectively;
421 nothing uses them, so they should be just removed from custom
425 r342635 changes the way efibootmgr(8) works by requiring users to add
426 the -b (bootnum) parameter for commands where the bootnum was previously
427 specified with each option. For example 'efibootmgr -B 0001' is now
428 'efibootmgr -B -b 0001'.
431 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
432 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
433 servers that have vfs.nfsd.nfs_privport set will only allow mounts
434 from clients using a reserved port#. Since both the FreeBSD and Linux
435 NFSv4 clients use reserved port#s by default, this should not affect
439 The XLP config has been removed. We can't support 64-bit atomics in this
440 kernel because it is running in 32-bit mode. XLP users must transition
441 to running a 64-bit kernel (XLP64 or XLPN32).
443 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
444 the preferred emulator today and we don't need two different ones.
446 The old sibyte / swarm / Broadcom BCM1250 support has been
447 removed from the mips port.
450 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
451 7.0.1. Please see the 20141231 entry below for information about
452 prerequisites and upgrading, if you are not already using clang 3.5.0
456 Remove the timed and netdate programs from the base tree. Setting
457 the time with these daemons has been obsolete for over a decade.
460 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
461 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
462 it produces broken binaries when ifuncs are in use. Users needing
463 GNU ld should install the binutils port or package.
466 The BSD crtbegin and crtend code has been enabled by default. It has
467 had extensive testing on amd64, arm64, and i386. It can be disabled
468 by building a world with -DWITHOUT_BSD_CRTBEGIN.
471 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
472 has been converted to a port (misc/ctm) and will be removed from
473 FreeBSD-13. It is available as a package (ctm) for all supported
477 The default newsyslog.conf(5) file has been changed to only include
478 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
479 the filenames end in '.conf' and do not begin with a '.'.
481 You should check the configuration files in these two directories match
482 this naming convention. You can verify which configuration files are
483 being included using the command:
487 Ports for the DRM modules have been simplified. Now, amd64 users should
488 just install the drm-kmod port. All others should install
491 Graphics hardware that's newer than about 2010 usually works with
492 drm-kmod. For hardware older than 2013, however, some users will need
493 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
494 than 2008 usually only works in drm-legacy-kmod. The graphics team can
495 only commit to hardware made since 2013 due to the complexity of the
496 market and difficulty to test all the older cards effectively. If you
497 have hardware supported by drm-kmod, you are strongly encouraged to use
498 that as you will get better support.
500 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
501 elsewhere, the drm and drm2 modules will be eliminated from the src base
502 soon (with a limited exception for arm). Please update to the package
503 asap and report any issues to x11@freebsd.org.
505 Generally, anybody using the drm*-kmod packages should add
506 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
507 cross-threading surprises, especially with automatic driver
508 loading from X11 startup. These will become the defaults in 13-current
512 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
513 custom kernel and module loading configuration files must be updated
514 accordingly. Moreover, interfaces previous presented as ixlvN to the
515 system are now exposed as iavfN and network configuration files must
516 be adjusted as necessary.
519 OpenSSL has been updated to version 1.1.1. This update included
520 additional various API changes throughout the base system. It is
521 important to rebuild third-party software after upgrading. The value
522 of __FreeBSD_version has been bumped accordingly.
525 The legacy DRM modules and drivers have now been added to the loader's
526 module blacklist, in favor of loading them with kld_list in rc.conf(5).
527 The module blacklist may be overridden with the loader.conf(5)
528 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
532 The cam(4) based nda(4) driver will be used over nvd(4) by default on
533 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
534 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
535 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
539 Reproducible build mode is now on by default, in preparation for
540 FreeBSD 12.0. This eliminates build metadata such as the user,
541 host, and time from the kernel (and uname), unless the working tree
542 corresponds to a modified checkout from a version control system.
543 The previous behavior can be obtained by setting the /etc/src.conf
544 knob WITHOUT_REPRODUCIBLE_BUILD.
547 The Yarrow CSPRNG has been removed from the kernel as it has not been
548 supported by its designers since at least 2003. Fortuna has been the
549 default since FreeBSD-11.
552 devctl freeze/thaw have gone into the tree, the rc scripts have been
553 updated to use them and devmatch has been changed. You should update
554 kernel, userland and rc scripts all at the same time.
557 The default interpreter has been switched from 4th to Lua.
558 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
559 interpreter. If you have custom FORTH code you will need to set
560 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
561 src.conf for the build. This will create default hard links between
562 loader and loader_4th instead of loader and loader_lua, the new default.
563 If you are using UEFI it will create the proper hard link to loader.efi.
565 bhyve uses userboot.so. It remains 4th-only until some issues are solved
566 regarding coexisting with multiple versions of FreeBSD are resolved.
569 ls(1) now respects the COLORTERM environment variable used in other
570 systems and software to indicate that a colored terminal is both
571 supported and desired. If ls(1) is suddenly emitting colors, they may
572 be disabled again by either removing the unwanted COLORTERM from your
573 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
574 may not be observed in a future release.
577 The default pager for most commands has been changed to "less". To
578 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
582 The jedec_ts(4) driver has been removed. A superset of its functionality
583 is available in the jedec_dimm(4) driver, and the manpage for that
584 driver includes migration instructions. If you have "device jedec_ts"
585 in your kernel configuration file, it must be removed.
588 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
589 This should have no effect if the kernel is booted via BIOS/legacy boot.
590 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
591 has a buggy firmware that prevents a successful boot due to use of
595 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
596 support has been removed from the tree. These ports were
597 obsolete and/or known to be broken for many years.
600 loader.efi has been augmented to participate more fully in the
601 UEFI boot manager protocol. loader.efi will now look at the
602 BootXXXX environment variable to determine if a specific kernel
603 or root partition was specified. XXXX is derived from BootCurrent.
604 efibootmgr(8) manages these standard UEFI variables.
607 zfsloader's functionality has now been folded into loader.
608 zfsloader is no longer necessary once you've updated your
609 boot blocks. For a transition period, we will install a
610 hardlink for zfsloader to loader to allow a smooth transition
611 until the boot blocks can be updated (hard link because old
612 zfs boot blocks don't understand symlinks).
615 ARM64 now have efifb support, if you want to have serial console
616 on your arm64 board when an screen is connected and the bootloader
617 setup a frame buffer for us to use, just add :
621 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
622 an screen connected as the firmware will setup a frame buffer are that
623 u-boot will expose as an EFI frame buffer.
626 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
627 or take steps to update /etc/passwd before doing installworld on
628 existing systems. Do not skip the "mergemaster -Fp" step before
629 installworld, as described in the update procedures near the bottom
630 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
631 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
632 the ntp config file contain options that change file/dir locations.
633 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
634 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
635 taking steps to ensure that all required files/dirs are accessible
639 Big endian arm support has been removed.
642 The static environment setup in kernel configs is no longer mutually
643 exclusive with the loader(8) environment by default. In order to
644 restore the previous default behavior of disabling the loader(8)
645 environment if a static environment is present, you must specify
646 loader_env.disabled=1 in the static environment.
649 The ABI of syscalls used by management tools like sockstat and
650 netstat has been broken to allow 32-bit binaries to work on
651 64-bit kernels without modification. These programs will need
652 to match the kernel in order to function. External programs may
653 require minor modifications to accommodate a change of type in
654 structures from pointers to 64-bit virtual addresses.
657 On i386 and amd64 atomics are now inlined. Out of tree modules using
658 atomics will need to be rebuilt.
661 The '%I' format in the kern.corefile sysctl limits the number of
662 core files that a process can generate to the number stored in the
663 debug.ncores sysctl. The '%I' format is replaced by the single digit
664 index. Previously, if all indexes were taken the kernel would overwrite
665 only a core file with the highest index in a filename.
666 Currently the system will create a new core file if there is a free
667 index or if all slots are taken it will overwrite the oldest one.
670 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
671 6.0.1. Please see the 20141231 entry below for information about
672 prerequisites and upgrading, if you are not already using clang 3.5.0
676 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
677 needed to be changed to work with it. This change was made with r335763
678 and requires a mergemaster / etcupdate / etc to update the installed
682 r334930 changed the interface between the NFS modules, so they all
683 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
686 As of r334391 lld is the default amd64 system linker; it is installed
687 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
691 The kernel / userland interface for devinfo changed, so you'll
692 need a new kernel and userland as a pair for it to work (rebuilding
693 lib/libdevinfo is all that's required). devinfo and devmatch will
694 not work, but everything else will when there's a mismatch.
697 The on-disk format for hwpmc callchain records has changed to include
698 threadid corresponding to a given record. This changes the field offsets
699 and thus requires that libpmcstat be rebuilt before using a kernel
703 The vxge(4) driver has been removed. This driver was introduced into
704 HEAD one week before the Exar left the Ethernet market and is not
705 known to be used. If you have device vxge in your kernel config file
709 The amd64 kernel now requires a ld that supports ifunc to produce a
710 working kernel, either lld or a newer binutils. lld is built by default
711 on amd64, and the 'buildkernel' target uses it automatically. However,
712 it is not the default linker, so building the kernel the traditional
713 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
714 binutils port/package). lld will soon be default, and this requirement
717 NOTE: As of r334391 lld is the default system linker on amd64, and no
718 workaround is necessary.
721 The nxge(4) driver has been removed. This driver was for PCI-X 10g
722 cards made by s2io/Neterion. The company was acquired by Exar and
723 no longer sells or supports Ethernet products. If you have device
724 nxge in your kernel config file it must be removed.
727 The tz database (tzdb) has been updated to 2018e. This version more
728 correctly models time stamps in time zones with negative DST such as
729 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
730 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
731 time zone abbreviations and the tm_isdst flag.
734 The ixgb(4) driver has been removed. This driver was for an early and
735 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
736 quickly shifted to the long lived ixgbe family. If you have device
737 ixgb in your kernel config file it must be removed.
740 The lmc(4) driver has been removed. This was a WAN interface
741 card that was already reportedly rare in 2003, and had an ambiguous
742 license. If you have device lmc in your kernel config file it must
746 Support for Arcnet networks has been removed. If you have device
747 arcnet or device cm in your kernel config file they must be
751 Support for FDDI networks has been removed. If you have device
752 fddi or device fpa in your kernel config file they must be
756 In addition to supporting RFC 3164 formatted messages, the
757 syslogd(8) service is now capable of parsing RFC 5424 formatted
758 log messages. The main benefit of using RFC 5424 is that clients
759 may now send log messages with timestamps containing year numbers,
760 microseconds and time zone offsets.
762 Similarly, the syslog(3) C library function has been altered to
763 send RFC 5424 formatted messages to the local system logging
764 daemon. On systems using syslogd(8), this change should have no
765 negative impact, as long as syslogd(8) and the C library are
766 updated at the same time. On systems using a different system
767 logging daemon, it may be necessary to make configuration
768 adjustments, depending on the software used.
770 When using syslog-ng, add the 'syslog-protocol' flag to local
771 input sources to enable parsing of RFC 5424 formatted messages:
774 unix-dgram("/var/run/log" flags(syslog-protocol));
777 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
778 of the 'imuxsock' module to let messages be processed by the
779 regular RFC 3164/5424 parsing pipeline:
781 module(load="imuxsock" SysSock.UseSpecialParser="off")
783 Do note that these changes only affect communication between local
784 applications and syslogd(8). The format that syslogd(8) uses to
785 store messages on disk or forward messages to other systems
786 remains unchanged. syslogd(8) still uses RFC 3164 for these
787 purposes. Options to customize this behaviour will be added in the
788 future. Utilities that process log files stored in /var/log are
789 thus expected to continue to function as before.
791 __FreeBSD_version has been incremented to 1200061 to denote this
795 Support for token ring networks has been removed. If you
796 have "device token" in your kernel config you should remove
797 it. No device drivers supported token ring.
800 makefs was modified to be able to tag ISO9660 El Torito boot catalog
801 entries as EFI instead of overloading the i386 tag as done previously.
802 The amd64 mkisoimages.sh script used to build amd64 ISO images for
803 release was updated to use this. This may mean that makefs must be
804 updated before "make cdrom" can be run in the release directory. This
805 should be as simple as:
807 $ cd $SRCDIR/usr.sbin/makefs
808 $ make depend all install
811 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
812 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
813 Co-existence for the transition period will come shortly. Booting is a
814 complex environment and test coverage for Lua-enabled loaders has been
815 thin, so it would be prudent to assume it might not work and make
816 provisions for backup boot methods.
819 devmatch functionality has been turned on in devd. It will automatically
820 load drivers for unattached devices. This may cause unexpected drivers
821 to be loaded. Please report any problems to current@ and
825 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
826 6.0.0. Please see the 20141231 entry below for information about
827 prerequisites and upgrading, if you are not already using clang 3.5.0
831 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
832 This means it is used to link the kernel and userland libraries and
833 executables, but is not yet installed as /usr/bin/ld by default.
835 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
836 WITHOUT_LLD_BOOTSTRAP=yes
839 On i386, pmtimer has been removed. Its functionality has been folded
840 into apm. It was a no-op on ACPI in current for a while now (but was
841 still needed on i386 in FreeBSD 11 and earlier). Users may need to
842 remove it from kernel config files.
845 The use of RSS hash from the network card aka flowid has been
846 disabled by default for lagg(4) as it's currently incompatible with
847 the lacp and loadbalance protocols.
849 This can be re-enabled by setting the following in loader.conf:
850 net.link.lagg.default_use_flowid="1"
853 The SW_WATCHDOG option is no longer necessary to enable the
854 hardclock-based software watchdog if no hardware watchdog is
855 configured. As before, SW_WATCHDOG will cause the software
856 watchdog to be enabled even if a hardware watchdog is configured.
859 r326887 fixes the issue described in the 20171214 UPDATING entry.
860 r326888 flips the switch back to building GELI support always.
863 r362593 broke ZFS + GELI support for reasons unknown. However,
864 it also broke ZFS support generally, so GELI has been turned off
865 by default as the lesser evil in r326857. If you boot off ZFS and/or
866 GELI, it might not be a good time to update.
869 PowerPC users must update loader(8) by rebuilding world before
870 installing a new kernel, as the protocol connecting them has
871 changed. Without the update, loader metadata will not be passed
872 successfully to the kernel and users will have to enter their
873 root partition at the kernel mountroot prompt to continue booting.
874 Newer versions of loader can boot old kernels without issue.
877 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
878 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
879 to WITH/OUT_LOADER_GELI.
882 The naive and non-compliant support of posix_fallocate(2) in ZFS
883 has been removed as of r325320. The system call now returns EINVAL
884 when used on a ZFS file. Although the new behavior complies with the
885 standard, some consumers are not prepared to cope with it.
886 One known victim is lld prior to r325420.
889 Building in a FreeBSD src checkout will automatically create object
890 directories now rather than store files in the current directory if
891 'make obj' was not ran. Calling 'make obj' is no longer necessary.
892 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
893 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
897 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
898 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
899 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
900 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
901 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
902 The UNIFIED_OBJDIR option is a transitional feature that will be
903 removed for 12.0 release; please migrate to the new format for any
904 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
905 than hardcoding paths.
908 The native-xtools target no longer installs the files by default to the
909 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
910 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
913 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
914 options are changing from controlling the build if defined / undefined
915 to controlling the build with explicit 'yes' or 'no' values. They will
916 shift to WITH/WITHOUT options to match other options in the system.
919 libstand has turned into a private library for sys/boot use only.
920 It is no longer supported as a public interface outside of sys/boot.
923 The arm port has split armv6 into armv6 and armv7. armv7 is now
924 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
925 and are running a kernel from before r324363, you will need to add
926 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
929 When building multiple kernels using KERNCONF, non-existent KERNCONF
930 files will produce an error and buildkernel will fail. Previously
931 missing KERNCONF files silently failed giving no indication as to
932 why, only to subsequently discover during installkernel that the
933 desired kernel was never built in the first place.
936 The default serial number format for CTL LUNs has changed. This will
937 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
938 or iSCSI clients care about their LUNs' serial numbers. Users who
939 require serial number stability should hardcode serial numbers in
943 For 32-bit arm compiled for hard-float support, soft-floating point
944 binaries now always get their shared libraries from
945 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
946 /usr/libsoft also existed). Only users with a hard-float ld.so, but
947 soft-float everything else should be affected.
950 The geli password typed at boot is now hidden. To restore the previous
951 behavior, see geli(8) for configuration options.
954 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
955 sysctl values. Minor nit, but requires a rebuild of both world/kernel
959 "make check" behavior (made in ^/head@r295380) has been changed to
960 execute from a limited sandbox, as opposed to executing from
964 - The "beforecheck" and "aftercheck" targets are now specified.
965 - ${CHECKDIR} (added in commit noted above) has been removed.
966 - Legacy behavior can be enabled by setting
967 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
969 If the limited sandbox mode is enabled, "make check" will execute
970 "make distribution", then install, execute the tests, and clean up the
971 sandbox if successful.
973 The "make distribution" and "make install" targets are typically run as
974 root to set appropriate permissions and ownership at installation time.
975 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
976 environment if executing "make check" with limited sandbox mode using
977 an unprivileged user.
980 Since the switch to GPT disk labels, fsck for UFS/FFS has been
981 unable to automatically find alternate superblocks. As of r322297,
982 the information needed to find alternate superblocks has been
983 moved to the end of the area reserved for the boot block.
984 Filesystems created with a newfs of this vintage or later
985 will create the recovery information. If you have a filesystem
986 created prior to this change and wish to have a recovery block
987 created for your filesystem, you can do so by running fsck in
988 foreground mode (i.e., do not use the -p or -y options). As it
989 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
990 to which you should answer yes.
993 As of r321665, an NFSv4 server configuration that services
994 Kerberos mounts or clients that do not support the uid/gid in
995 owner/owner_group string capability, must explicitly enable
996 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
997 machine's /etc/rc.conf file.
1000 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
1001 Please see the 20141231 entry below for information about prerequisites
1002 and upgrading, if you are not already using clang 3.5.0 or higher.
1005 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
1006 r-commands (rlogin, rsh, etc.) to be built with the base system.
1009 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
1010 a very major ABI incompatible change, so users of FreeBSD/powerpc must
1011 be careful when performing source upgrades. It is best to run
1012 'make installworld' from an alternate root system, either a live
1013 CD/memory stick, or a temporary root partition. Additionally, all ports
1014 must be recompiled. powerpc64 is largely unaffected, except in the case
1015 of 32-bit compatibility. All 32-bit binaries will be affected.
1018 Forward compatibility for the "ino64" project have been committed. This
1019 will allow most new binaries to run on older kernels in a limited
1020 fashion. This prevents many of the common foot-shooting actions in the
1021 upgrade as well as the limited ability to roll back the kernel across
1022 the ino64 upgrade. Complicated use cases may not work properly, though
1023 enough simpler ones work to allow recovery in most situations.
1026 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
1027 if you require the GPL compiler.
1030 The internal ABI used for communication between the NFS kernel modules
1031 was changed by r320085, so __FreeBSD_version was bumped to
1032 ensure all the NFS related modules are updated together.
1035 The ABI of struct event was changed by extending the data
1036 member to 64bit and adding ext fields. For upgrade, same
1037 precautions as for the entry 20170523 "ino64" must be
1041 The GNU roff toolchain has been removed from base. To render manpages
1042 which are not supported by mandoc(1), man(1) can fallback on GNU roff
1043 from ports (and recommends to install it).
1044 To render roff(7) documents, consider using GNU roff from ports or the
1045 heirloom doctools roff toolchain from ports via pkg install groff or
1046 via pkg install heirloom-doctools.
1049 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
1050 smaller runtime footprint builds. This is useful for embedded systems
1051 which only require one chipset support.
1053 If you load it as a module, make sure this is in /boot/loader.conf:
1057 This will load the HAL, all chip/RF backends and if_ath_pci.
1058 If you have if_ath_pci in /boot/loader.conf, ensure it is after
1059 if_ath or it will not load any HAL chipset support.
1061 If you want to selectively load things (eg on ye cheape ARM/MIPS
1062 platforms where RAM is at a premium) you should:
1065 * load the chip modules in question
1066 * load ath_rate, ath_dfs
1068 * load if_ath_pci and/or if_ath_ahb depending upon your particular
1069 bus bind type - this is where probe/attach is done.
1071 For further comments/feedback, poke adrian@ .
1074 The "ino64" 64-bit inode project has been committed, which extends
1075 a number of types to 64 bits. Upgrading in place requires care and
1076 adherence to the documented upgrade procedure.
1078 If using a custom kernel configuration ensure that the
1079 COMPAT_FREEBSD11 option is included (as during the upgrade the
1080 system will be running the ino64 kernel with the existing world).
1082 For the safest in-place upgrade begin by removing previous build
1083 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full
1084 procedure documented below under the heading "To rebuild everything and
1085 install it on the current system." Specifically, a reboot is required
1086 after installing the new kernel before installing world. While an
1087 installworld normally works by accident from multiuser after rebooting
1088 the proper kernel, there are many cases where this will fail across this
1089 upgrade and installworld from single user is required.
1092 The NATM framework including the en(4), fatm(4), hatm(4), and
1093 patm(4) devices has been removed. Consumers should plan a
1094 migration before the end-of-life date for FreeBSD 11.
1097 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
1098 diff has not been implemented, if those are needed a newer version of
1099 GNU diff is available via the diffutils package under the gdiff name.
1102 As of r316810 for ipfilter, keep frags is no longer assumed when
1103 keep state is specified in a rule. r316810 aligns ipfilter with
1104 documentation in man pages separating keep frags from keep state.
1105 This allows keep state to be specified without forcing keep frags
1106 and allows keep frags to be specified independently of keep state.
1107 To maintain previous behaviour, also specify keep frags with
1108 keep state (as documented in ipf.conf.5).
1111 arm64 builds now use the base system LLD 4.0.0 linker by default,
1112 instead of requiring that the aarch64-binutils port or package be
1113 installed. To continue using aarch64-binutils, set
1114 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
1117 The UDP optimization in entry 20160818 that added the sysctl
1118 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
1119 packets will no longer be treated as L3 broadcast packets.
1122 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
1123 use any explicitly assigned loopback address available in the jail
1124 instead of using the first assigned address of the jail.
1127 The ctl.ko module no longer implements the iSCSI target frontend:
1128 cfiscsi.ko does instead.
1130 If building cfiscsi.ko as a kernel module, the module can be loaded
1131 via one of the following methods:
1132 - `cfiscsi_load="YES"` in loader.conf(5).
1133 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
1134 - ctladm(8)/ctld(8), when compiled with iSCSI support
1135 (`WITH_ISCSI=yes` in src.conf(5))
1137 Please see cfiscsi(4) for more details.
1140 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
1141 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
1142 same source (previously, the dependency of mmcsd.ko on mmc.ko was
1143 missing, but mmcsd.ko now will refuse to load if it is incompatible
1147 The syntax of ipfw(8) named states was changed to avoid ambiguity.
1148 If you have used named states in the firewall rules, you need to modify
1149 them after installworld and before rebooting. Now named states must
1150 be prefixed with colon.
1153 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
1154 removed as the userland we provide cannot use them. The KMS version
1155 (sys/dev/drm2) supports the same hardware.
1158 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
1159 Please see the 20141231 entry below for information about prerequisites
1160 and upgrading, if you are not already using clang 3.5.0 or higher.
1163 The code that provides support for ZFS .zfs/ directory functionality
1164 has been reimplemented. It's not possible now to create a snapshot
1165 by mkdir under .zfs/snapshot/. That should be the only user visible
1169 EISA bus support has been removed. The WITH_EISA option is no longer
1173 MCA bus support has been removed.
1176 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
1177 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
1180 The EM_MULTIQUEUE kernel configuration option is deprecated now that
1181 the em(4) driver conforms to iflib specifications.
1184 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
1185 IFLIB. If you have a custom kernel configuration that excludes em(4)
1186 but you use igb(4), you need to re-add em(4) to your custom
1190 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
1191 Please see the 20141231 entry below for information about prerequisites
1192 and upgrading, if you are not already using clang 3.5.0 or higher.
1195 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
1196 Please see the 20141231 entry below for information about prerequisites
1197 and upgrading, if you are not already using clang 3.5.0 or higher.
1200 The layout of the pmap structure has changed for powerpc to put the pmap
1201 statistics at the front for all CPU variations. libkvm(3) and all tools
1202 that link against it need to be recompiled.
1205 isl(4) and cyapa(4) drivers now require a new driver,
1206 chromebook_platform(4), to work properly on Chromebook-class hardware.
1207 On other types of hardware the drivers may need to be configured using
1208 device hints. Please see the corresponding manual pages for details.
1211 The urtwn(4) driver was merged into rtwn(4) and now consists of
1212 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
1214 Also, firmware for RTL8188CE was renamed due to possible name
1215 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
1218 GNU rcs has been removed from base. It is available as packages:
1219 - rcs: Latest GPLv3 GNU rcs version.
1220 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
1224 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
1225 modules now requires that the kernel configuration contain the
1226 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
1229 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
1230 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
1233 Relocatable object files with the extension of .So have been renamed
1234 to use an extension of .pico instead. The purpose of this change is
1235 to avoid a name clash with shared libraries on case-insensitive file
1236 systems. On those file systems, foo.So is the same file as foo.so.
1239 GNU rcs has been turned off by default. It can (temporarily) be built
1240 again by adding WITH_RCS knob in src.conf.
1241 Otherwise, GNU rcs is available from packages:
1242 - rcs: Latest GPLv3 GNU rcs version.
1243 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
1246 The backup_uses_rcs functionality has been removed from rc.subr.
1249 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
1250 two separate components, QUEUE_MACRO_DEBUG_TRACE and
1251 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
1252 QUEUE_MACRO_DEBUG behavior.
1255 r304787 changed some ioctl interfaces between the iSCSI userspace
1256 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1257 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1261 The UDP receive code has been updated to only treat incoming UDP
1262 packets that were addressed to an L2 broadcast address as L3
1263 broadcast packets. It is not expected that this will affect any
1264 standards-conforming UDP application. The new behaviour can be
1265 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1269 Remove the openbsd_poll system call.
1270 __FreeBSD_version has been bumped because of this.
1273 The stable/11 branch has been created from head@r302406.
1276 The libc stub for the pipe(2) system call has been replaced with
1277 a wrapper that calls the pipe2(2) system call and the pipe(2)
1278 system call is now only implemented by the kernels that include
1279 "options COMPAT_FREEBSD10" in their config file (this is the
1280 default). Users should ensure that this option is enabled in
1281 their kernel or upgrade userspace to r302092 before upgrading their
1285 CAM will now strip leading spaces from SCSI disks' serial numbers.
1286 This will affect users who create UFS filesystems on SCSI disks using
1287 those disk's diskid device nodes. For example, if /etc/fstab
1288 previously contained a line like
1289 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
1290 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
1291 transforms like gmirror may also be affected. ZFS users should
1295 The bitstring(3) API has been updated with new functionality and
1296 improved performance. But it is binary-incompatible with the old API.
1297 Objects built with the new headers may not be linked against objects
1298 built with the old headers.
1301 The brk and sbrk functions have been removed from libc on arm64.
1302 Binutils from ports has been updated to not link to these
1303 functions and should be updated to the latest version before
1304 installing a new libc.
1307 The armv6 port now defaults to hard float ABI. Limited support
1308 for running both hardfloat and soft float on the same system
1309 is available using the libraries installed with -DWITH_LIBSOFT.
1310 This has only been tested as an upgrade path for installworld
1311 and packages may fail or need manual intervention to run. New
1312 packages will be needed.
1314 To update an existing self-hosted armv6hf system, you must add
1315 TARGET_ARCH=armv6 on the make command line for both the build
1316 and the install steps.
1319 Kernel modules compiled outside of a kernel build now default to
1320 installing to /boot/modules instead of /boot/kernel. Many kernel
1321 modules built this way (such as those in ports) already overrode
1322 KMODDIR explicitly to install into /boot/modules. However,
1323 manually building and installing a module from /sys/modules will
1324 now install to /boot/modules instead of /boot/kernel.
1327 The CAM I/O scheduler has been committed to the kernel. There should be
1328 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1329 list of known rogues that claim support for this but actually corrupt
1330 data is believed to be complete, be on the lookout for data
1331 corruption. The known rogue list is believed to be complete:
1333 o Crucial MX100, M550 drives with MU01 firmware.
1334 o Micron M510 and M550 drives with MU01 firmware.
1335 o Micron M500 prior to MU07 firmware
1336 o Samsung 830, 840, and 850 all firmwares
1337 o FCCT M500 all firmwares
1339 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1340 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1341 updated firmware. Black listed drives will work correctly because these
1342 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1343 this list is the same as found in Linux, it's believed there are no
1344 other rogues in the market place. All other models from the above
1347 To be safe, if you are at all concerned, you can quirk each of your
1348 drives to prevent NCQ from being sent by setting:
1349 kern.cam.ada.X.quirks="0x2"
1350 in loader.conf. If the drive requires the 4k sector quirk, set the
1351 quirks entry to 0x3.
1354 The FAST_DEPEND build option has been removed and its functionality is
1355 now the one true way. The old mkdep(1) style of 'make depend' has
1356 been removed. See 20160311 for further details.
1359 Resource range types have grown from unsigned long to uintmax_t. All
1360 drivers, and anything using libdevinfo, need to be recompiled.
1363 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1364 builds. It no longer runs mkdep(1) during 'make depend', and the
1365 'make depend' stage can safely be skipped now as it is auto ran
1366 when building 'make all' and will generate all SRCS and DPSRCS before
1367 building anything else. Dependencies are gathered at compile time with
1368 -MF flags kept in separate .depend files per object file. Users should
1369 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1370 stale .depend files.
1373 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1374 kernel modules. Therefore, if you load any kernel modules at boot time,
1375 please install the boot loaders after you install the kernel, but before
1379 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1380 make installkernel KERNCONF=YOUR_KERNEL_HERE
1381 make -C sys/boot install
1382 <reboot in single user>
1384 Then follow the usual steps, described in the General Notes section,
1388 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1389 see the 20141231 entry below for information about prerequisites and
1390 upgrading, if you are not already using clang 3.5.0 or higher.
1393 The AIO subsystem is now a standard part of the kernel. The
1394 VFS_AIO kernel option and aio.ko kernel module have been removed.
1395 Due to stability concerns, asynchronous I/O requests are only
1396 permitted on sockets and raw disks by default. To enable
1397 asynchronous I/O requests on all file types, set the
1398 vfs.aio.enable_unsafe sysctl to a non-zero value.
1401 The ELF object manipulation tool objcopy is now provided by the
1402 ELF Tool Chain project rather than by GNU binutils. It should be a
1403 drop-in replacement, with the addition of arm64 support. The
1404 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1405 to obtain the GNU version if necessary.
1408 Building ZFS pools on top of zvols is prohibited by default. That
1409 feature has never worked safely; it's always been prone to deadlocks.
1410 Using a zvol as the backing store for a VM guest's virtual disk will
1411 still work, even if the guest is using ZFS. Legacy behavior can be
1412 restored by setting vfs.zfs.vol.recursive=1.
1415 The NONE and HPN patches has been removed from OpenSSH. They are
1416 still available in the security/openssh-portable port.
1419 With the addition of ypldap(8), a new _ypldap user is now required
1420 during installworld. "mergemaster -p" can be used to add the user
1421 prior to installworld, as documented in the handbook.
1424 The tftp loader (pxeboot) now uses the option root-path directive. As a
1425 consequence it no longer looks for a pxeboot.4th file on the tftp
1426 server. Instead it uses the regular /boot infrastructure as with the
1430 The code to start recording plug and play data into the modules has
1431 been committed. While the old tools will properly build a new kernel,
1432 a number of warnings about "unknown metadata record 4" will be produced
1433 for an older kldxref. To avoid such warnings, make sure to rebuild
1434 the kernel toolchain (or world). Make sure that you have r292078 or
1435 later when trying to build 292077 or later before rebuilding.
1438 Debug data files are now built by default with 'make buildworld' and
1439 installed with 'make installworld'. This facilitates debugging but
1440 requires more disk space both during the build and for the installed
1441 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1445 r291527 changed the internal interface between the nfsd.ko and
1446 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1447 __FreeBSD_version has been bumped because of this.
1450 Add support for unicode collation strings leads to a change of
1451 order of files listed by ls(1) for example. To get back to the old
1452 behaviour, set LC_COLLATE environment variable to "C".
1454 Databases administrators will need to reindex their databases given
1455 collation results will be different.
1457 Due to a bug in install(1) it is recommended to remove the ancient
1458 locales before running make installworld.
1460 rm -rf /usr/share/locale/*
1463 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1464 libcrypto.so.7 or libssl.so.7 must be recompiled.
1467 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1468 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1469 should be replaced with isp_2400 and isp_2500 modules respectively.
1472 The build previously allowed using 'make -n' to not recurse into
1473 sub-directories while showing what commands would be executed, and
1474 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1475 and 'make -N' will not.
1478 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1479 and etcupdate will now use this file. A custom sendmail.cf is now
1480 updated via this mechanism rather than via installworld. If you had
1481 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1482 want to remove the exclusion or change it to "always install".
1483 /etc/mail/sendmail.cf is now managed the same way regardless of
1484 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1485 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1488 Compatibility shims for legacy ATA device names have been removed.
1489 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1490 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1491 environment variables, /dev/ad* and /dev/ar* symbolic links.
1494 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1495 Please see the 20141231 entry below for information about prerequisites
1496 and upgrading, if you are not already using clang 3.5.0 or higher.
1499 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1500 and renamed from .symbols to .debug. This reduces the size requirements
1501 on the boot partition or file system and provides consistency with
1502 userland debug files.
1504 When using the supported kernel installation method the
1505 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1506 as is done with /boot/kernel.
1508 Developers wishing to maintain the historical behavior of installing
1509 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1512 The wireless drivers had undergone changes that remove the 'parent
1513 interface' from the ifconfig -l output. The rc.d network scripts
1514 used to check presence of a parent interface in the list, so old
1515 scripts would fail to start wireless networking. Thus, etcupdate(3)
1516 or mergemaster(8) run is required after kernel update, to update your
1517 rc.d scripts in /etc.
1520 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1521 These configurations are now automatically interpreted as
1522 'scrub fragment reassemble'.
1525 Kernel-loadable modules for the random(4) device are back. To use
1526 them, the kernel must have
1529 options RANDOM_LOADABLE
1531 kldload(8) can then be used to load random_fortuna.ko
1532 or random_yarrow.ko. Please note that due to the indirect
1533 function calls that the loadable modules need to provide,
1534 the build-in variants will be slightly more efficient.
1536 The random(4) kernel option RANDOM_DUMMY has been retired due to
1537 unpopularity. It was not all that useful anyway.
1540 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1541 Control over building the ELF Tool Chain tools is now provided by
1542 the WITHOUT_TOOLCHAIN knob.
1545 The polarity of Pulse Per Second (PPS) capture events with the
1546 uart(4) driver has been corrected. Prior to this change the PPS
1547 "assert" event corresponded to the trailing edge of a positive PPS
1548 pulse and the "clear" event was the leading edge of the next pulse.
1550 As the width of a PPS pulse in a typical GPS receiver is on the
1551 order of 1 millisecond, most users will not notice any significant
1552 difference with this change.
1554 Anyone who has compensated for the historical polarity reversal by
1555 configuring a negative offset equal to the pulse width will need to
1556 remove that workaround.
1559 The default group assigned to /dev/dri entries has been changed
1560 from 'wheel' to 'video' with the id of '44'. If you want to have
1561 access to the dri devices please add yourself to the video group
1564 # pw groupmod video -m $USER
1567 The menu.rc and loader.rc files will now be replaced during
1568 upgrades. Please migrate local changes to menu.rc.local and
1569 loader.rc.local instead.
1572 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1573 strings and strip have been removed. The src.conf(5) knob
1574 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1577 As ZFS requires more kernel stack pages than is the default on some
1578 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1579 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1581 Please consider using 'options KSTACK_PAGES=X' where X is greater
1582 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1585 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1586 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1587 default, i.e., they will not contain "::". For example, instead
1588 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1589 to have a more specific match, such as different map entries for
1590 IPv6:0:0 vs IPv6:0. This change requires that configuration
1591 data (including maps, files, classes, custom ruleset, etc.) must
1592 use the same format, so make certain such configuration data is
1593 upgrading. As a very simple check search for patterns like
1594 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1595 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1596 the cf option UseCompressedIPv6Addresses.
1599 The default kernel entropy-processing algorithm is now
1600 Fortuna, replacing Yarrow.
1602 Assuming you have 'device random' in your kernel config
1603 file, the configurations allow a kernel option to override
1604 this default. You may choose *ONE* of:
1606 options RANDOM_YARROW # Legacy /dev/random algorithm.
1607 options RANDOM_DUMMY # Blocking-only driver.
1609 If you have neither, you get Fortuna. For most people,
1610 read no further, Fortuna will give a /dev/random that works
1611 like it always used to, and the difference will be irrelevant.
1613 If you remove 'device random', you get *NO* kernel-processed
1614 entropy at all. This may be acceptable to folks building
1615 embedded systems, but has complications. Carry on reading,
1616 and it is assumed you know what you need.
1618 *PLEASE* read random(4) and random(9) if you are in the
1619 habit of tweaking kernel configs, and/or if you are a member
1620 of the embedded community, wanting specific and not-usual
1621 behaviour from your security subsystems.
1623 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1624 random', you will NOT have a functioning /dev/random, and
1625 many cryptographic features will not work, including SSH.
1626 You may also find strange behaviour from the random(3) set
1627 of library functions, in particular sranddev(3), srandomdev(3)
1628 and arc4random(3). The reason for this is that the KERN_ARND
1629 sysctl only returns entropy if it thinks it has some to
1630 share, and with RANDOM_DUMMY or no 'device random' this
1634 An additional fix for the issue described in the 20150614 sendmail
1635 entry below has been committed in revision 284717.
1638 FreeBSD's old make (fmake) has been removed from the system. It is
1639 available as the devel/fmake port or via pkg install fmake.
1642 The fix for the issue described in the 20150614 sendmail entry
1643 below has been committed in revision 284436. The work
1644 around described in that entry is no longer needed unless the
1645 default setting is overridden by a confDH_PARAMETERS configuration
1646 setting of '5' or pointing to a 512 bit DH parameter file.
1649 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1650 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1651 and devel/kyua to version 0.20+ and adjust any calling code to work
1652 with Kyuafile and kyua.
1655 The import of openssl to address the FreeBSD-SA-15:10.openssl
1656 security advisory includes a change which rejects handshakes
1657 with DH parameters below 768 bits. sendmail releases prior
1658 to 8.15.2 (not yet released), defaulted to a 512 bit
1659 DH parameter setting for client connections. To work around
1660 this interoperability, sendmail can be configured to use a
1661 2048 bit DH parameter by:
1663 1. Edit /etc/mail/`hostname`.mc
1664 2. If a setting for confDH_PARAMETERS does not exist or
1665 exists and is set to a string beginning with '5',
1666 replace it with '2'.
1667 3. If a setting for confDH_PARAMETERS exists and is set to
1668 a file path, create a new file with:
1669 openssl dhparam -out /path/to/file 2048
1670 4. Rebuild the .cf file:
1671 cd /etc/mail/; make; make install
1672 5. Restart sendmail:
1673 cd /etc/mail/; make restart
1675 A sendmail patch is coming, at which time this file will be
1679 Generation of legacy formatted entries have been disabled by default
1680 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1681 entries were converted to use the new format by default when the new,
1682 machine independent format have been added and supported since FreeBSD
1685 Please see the pwd_mkdb(8) manual page for further details.
1688 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1689 20141231 entry below for information about prerequisites and upgrading,
1690 if you are not already using 3.5.0 or higher.
1693 TI platform code switched to using vendor DTS files and this update
1694 may break existing systems running on Beaglebone, Beaglebone Black,
1697 - dtb files should be regenerated/reinstalled. Filenames are the
1698 same but content is different now
1699 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1700 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1701 addressing scheme is now pin 25 on /dev/gpioc3.
1702 - Pandaboard: /etc/ttys should be updated, serial console device is
1703 now /dev/ttyu2, not /dev/ttyu0
1706 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1707 If you need the GNU extension from groff soelim(1), install groff
1708 from package: pkg install groff, or via ports: textproc/groff.
1711 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1712 defined in symlink(7); previously symlinks were silently ignored.
1715 The const qualifier has been removed from iconv(3) to comply with
1716 POSIX. The ports tree is aware of this from r384038 onwards.
1719 Libraries specified by LIBADD in Makefiles must have a corresponding
1720 DPADD_<lib> variable to ensure correct dependencies. This is now
1721 enforced in src.libnames.mk.
1724 From legacy ata(4) driver was removed support for SATA controllers
1725 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1726 Kernel modules ataahci and ataadaptec were removed completely,
1727 replaced by ahci and mvs modules respectively.
1730 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1731 the 20141231 entry below for information about prerequisites and
1732 upgrading, if you are not already using 3.5.0 or higher.
1735 The 32-bit PowerPC kernel has been changed to a position-independent
1736 executable. This can only be booted with a version of loader(8)
1737 newer than January 31, 2015, so make sure to update both world and
1738 kernel before rebooting.
1741 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1742 but before r278950, the RNG was not seeded properly. Immediately
1743 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1744 ssh keys or openssl keys) that were generated w/ a kernel from that
1745 range. This does not affect programs that directly used /dev/random
1746 or /dev/urandom. All userland uses of arc4random(3) are affected.
1749 The autofs(4) ABI was changed in order to restore binary compatibility
1750 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1751 with the new kernel.
1754 The powerpc64 kernel has been changed to a position-independent
1755 executable. This can only be booted with a new version of loader(8),
1756 so make sure to update both world and kernel before rebooting.
1759 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1760 only release, no new features have been added. Please see the 20141231
1761 entry below for information about prerequisites and upgrading, if you
1762 are not already using 3.5.0.
1765 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1766 taken from the ELF Tool Chain project rather than GNU binutils. They
1767 should be drop-in replacements, with the addition of arm64 support.
1768 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1769 binutils tools, if necessary. See 20150805 for updated information.
1772 The default Unbound configuration now enables remote control
1773 using a local socket. Users who have already enabled the
1774 local_unbound service should regenerate their configuration
1775 by running "service local_unbound setup" as root.
1778 The GNU texinfo and GNU info pages have been removed.
1779 To be able to view GNU info pages please install texinfo from ports.
1782 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1784 As of this release, a prerequisite for building clang, llvm and lldb is
1785 a C++11 capable compiler and C++11 standard library. This means that to
1786 be able to successfully build the cross-tools stage of buildworld, with
1787 clang as the bootstrap compiler, your system compiler or cross compiler
1788 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1789 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1792 On any standard FreeBSD 10.x or 11.x installation, where clang and
1793 libc++ are on by default (that is, on x86 or arm), this should work out
1796 On 9.x installations where clang is enabled by default, e.g. on x86 and
1797 powerpc, libc++ will not be enabled by default, so libc++ should be
1798 built (with clang) and installed first. If both clang and libc++ are
1799 missing, build clang first, then use it to build libc++.
1801 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1802 the instructions for 9.x above.
1804 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1805 default, and do not build clang.
1807 Many embedded systems are resource constrained, and will not be able to
1808 build clang in a reasonable time, or in some cases at all. In those
1809 cases, cross building bootable systems on amd64 is a workaround.
1811 This new version of clang introduces a number of new warnings, of which
1812 the following are most likely to appear:
1816 This warns in two cases, for both C and C++:
1817 * When the code is trying to take the absolute value of an unsigned
1818 quantity, which is effectively a no-op, and almost never what was
1819 intended. The code should be fixed, if at all possible. If you are
1820 sure that the unsigned quantity can be safely cast to signed, without
1821 loss of information or undefined behavior, you can add an explicit
1822 cast, or disable the warning.
1824 * When the code is trying to take an absolute value, but the called
1825 abs() variant is for the wrong type, which can lead to truncation.
1826 If you want to disable the warning instead of fixing the code, please
1827 make sure that truncation will not occur, or it might lead to unwanted
1830 -Wtautological-undefined-compare and
1831 -Wundefined-bool-conversion
1833 These warn when C++ code is trying to compare 'this' against NULL, while
1834 'this' should never be NULL in well-defined C++ code. However, there is
1835 some legacy (pre C++11) code out there, which actively abuses this
1836 feature, which was less strictly defined in previous C++ versions.
1838 Squid and openjdk do this, for example. The warning can be turned off
1839 for C++98 and earlier, but compiling the code in C++11 mode might result
1840 in unexpected behavior; for example, the parts of the program that are
1841 unreachable could be optimized away.
1844 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1845 kernel sources have been removed. The .h files remain, since some
1846 utilities include them. This will need to be fixed later.
1847 If "mount -t oldnfs ..." is attempted, it will fail.
1848 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1849 the utilities will report errors.
1852 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1853 directories to top level SUBDIR variable when their parent
1854 directory is included in LOCAL_DIRS. Users with build systems with
1855 such hierarchies and without SUBDIR entries in the parent
1856 directory Makefiles should add them or add the directories to
1860 faith(4) and faithd(8) have been removed from the base system. Faith
1861 has been obsolete for a very long time.
1864 vt(4), the new console driver, is enabled by default. It brings
1865 support for Unicode and double-width characters, as well as
1866 support for UEFI and integration with the KMS kernel video
1869 You may need to update your console settings in /etc/rc.conf,
1870 most probably the keymap. During boot, /etc/rc.d/syscons will
1871 indicate what you need to do.
1873 vt(4) still has issues and lacks some features compared to
1874 syscons(4). See the wiki for up-to-date information:
1875 https://wiki.freebsd.org/Newcons
1877 If you want to keep using syscons(4), you can do so by adding
1878 the following line to /boot/loader.conf:
1882 pjdfstest has been integrated into kyua as an opt-in test suite.
1883 Please see share/doc/pjdfstest/README for more details on how to
1887 gperf has been removed from the base system for architectures
1888 that use clang. Ports that require gperf will obtain it from the
1892 pjdfstest has been moved from tools/regression/pjdfstest to
1896 At svn r271982, The default linux compat kernel ABI has been adjusted
1897 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1898 update. If you wish to continue using the linux-f10 compat ports,
1899 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1900 encouraged to update their linux-compat packages to linux-c6 during
1901 their next update cycle.
1904 The ofwfb driver, used to provide a graphics console on PowerPC when
1905 using vt(4), no longer allows mmap() of all physical memory. This
1906 will prevent Xorg on PowerPC with some ATI graphics cards from
1907 initializing properly unless x11-servers/xorg-server is updated to
1911 The xdev targets have been converted to using TARGET and
1912 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1915 The default unbound configuration has been modified to address
1916 issues with reverse lookups on networks that use private
1917 address ranges. If you use the local_unbound service, run
1918 "service local_unbound setup" as root to regenerate your
1919 configuration, then "service local_unbound reload" to load the
1923 The GNU texinfo and GNU info pages are not built and installed
1924 anymore, WITH_INFO knob has been added to allow to built and install
1926 UPDATE: see 20150102 entry on texinfo's removal
1929 The GNU readline library is now an INTERNALLIB - that is, it is
1930 statically linked into consumers (GDB and variants) in the base
1931 system, and the shared library is no longer installed. The
1932 devel/readline port is available for third party software that
1936 The Itanium architecture (ia64) has been removed from the list of
1937 known architectures. This is the first step in the removal of the
1941 Commit r268115 has added NFSv4.1 server support, merged from
1942 projects/nfsv4.1-server. Since this includes changes to the
1943 internal interfaces between the NFS related modules, a full
1944 build of the kernel and modules will be necessary.
1945 __FreeBSD_version has been bumped.
1948 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1949 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1950 which differs from the behaviour controlled by this knob.)
1953 Maximal length of the serial number in CTL was increased from 16 to
1954 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1955 and ctld, need to be rebuilt to work with a new kernel.
1958 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1959 1 respectively to match the upstream numbers. They were out of
1960 sync because, when they were originally added to FreeBSD, the
1961 upstream versions were not respected. These libraries are private
1962 and not yet built by default, so renumbering them should be a
1963 non-issue. However, unclean source trees will yield broken test
1964 programs once the operator executes "make delete-old-libs" after a
1965 "make installworld".
1967 Additionally, the atf-sh binary was made private by moving it into
1968 /usr/libexec/. Already-built shell test programs will keep the
1969 path to the old binary so they will break after "make delete-old"
1972 If you are using WITH_TESTS=yes (not the default), wipe the object
1973 tree and rebuild from scratch to prevent spurious test failures.
1974 This is only needed once: the misnumbered libraries and misplaced
1975 binaries have been added to OptionalObsoleteFiles.inc so they will
1976 be removed during a clean upgrade.
1979 Clang and llvm have been upgraded to 3.4.1 release.
1982 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1983 be removed to avoid issues in the future (and has been added to
1987 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1988 past, it affected all builds that used the bsd.*.mk files. The old
1989 behavior was a bug, but people may have relied upon it. To get this
1990 behavior back, you can .include /etc/src.conf from /etc/make.conf
1991 (which is still global and isn't changed). This also changes the
1992 behavior of incremental builds inside the tree of individual
1993 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1994 Although this has survived make universe and some upgrade scenarios,
1995 other upgrade scenarios may have broken. At least one form of
1996 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1997 as well... In cases where MAKESYSPATH isn't working with this
1998 setting, you'll need to set it to the full path to your tree.
2000 One side effect of all this cleaning up is that bsd.compiler.mk
2001 is no longer implicitly included by bsd.own.mk. If you wish to
2002 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
2006 The lindev device has been removed since /dev/full has been made a
2007 standard device. __FreeBSD_version has been bumped.
2010 The knob WITHOUT_VI was added to the base system, which controls
2011 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
2012 in order to reorder files share/termcap and didn't build ex(1) as a
2013 build tool, so building/installing with WITH_VI is highly advised for
2014 build hosts for older releases.
2016 This issue has been fixed in stable/9 and stable/10 in r277022 and
2017 r276991, respectively.
2020 The YES_HESIOD knob has been removed. It has been obsolete for
2021 a decade. Please move to using WITH_HESIOD instead or your builds
2022 will silently lack HESIOD.
2025 The uart(4) driver has been changed with respect to its handling
2026 of the low-level console. Previously the uart(4) driver prevented
2027 any process from changing the baudrate or the CLOCAL and HUPCL
2028 control flags. By removing the restrictions, operators can make
2029 changes to the serial console port without having to reboot.
2030 However, when getty(8) is started on the serial device that is
2031 associated with the low-level console, a misconfigured terminal
2032 line in /etc/ttys will now have a real impact.
2033 Before upgrading the kernel, make sure that /etc/ttys has the
2034 serial console device configured as 3wire without baudrate to
2035 preserve the previous behaviour. E.g:
2036 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
2039 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
2040 to improve performance. To re-enable it, if needed, run rpcbind
2041 with command line option -W.
2044 Switched back to the GPL dtc compiler due to updates in the upstream
2045 dts files not being supported by the BSDL dtc compiler. You will need
2046 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
2047 may result while building dtb files during a kernel build if you fail
2048 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
2051 Clang and llvm have been upgraded to 3.4 release.
2054 The nve(4) driver has been removed. Please use the nfe(4) driver
2055 for NVIDIA nForce MCP Ethernet adapters instead.
2058 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
2059 This could cause certain C++ applications using shared libraries built
2060 against the previous version of libc++ to crash. The incompatibility
2061 has now been fixed, but any C++ applications or shared libraries built
2062 between r261283 and r261801 should be recompiled.
2065 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
2066 capability mode support. Please note that enabling the feature in
2067 kernel is still highly recommended.
2070 OpenSSH is now built with sandbox support, and will use sandbox as
2071 the default privilege separation method. This requires Capsicum
2072 capability mode support in kernel.
2075 The libelf and libdwarf libraries have been updated to newer
2076 versions from upstream. Shared library version numbers for
2077 these two libraries were bumped. Any ports or binaries
2078 requiring these two libraries should be recompiled.
2079 __FreeBSD_version is bumped to 1100006.
2082 If a Makefile in a tests/ directory was auto-generating a Kyuafile
2083 instead of providing an explicit one, this would prevent such
2084 Makefile from providing its own Kyuafile in the future during
2085 NO_CLEAN builds. This has been fixed in the Makefiles but manual
2086 intervention is needed to clean an objdir if you use NO_CLEAN:
2087 # find /usr/obj -name Kyuafile | xargs rm -f
2090 The behavior of gss_pseudo_random() for the krb5 mechanism
2091 has changed, for applications requesting a longer random string
2092 than produced by the underlying enctype's pseudo-random() function.
2093 In particular, the random string produced from a session key of
2094 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
2095 be different at the 17th octet and later, after this change.
2096 The counter used in the PRF+ construction is now encoded as a
2097 big-endian integer in accordance with RFC 4402.
2098 __FreeBSD_version is bumped to 1100004.
2101 The WITHOUT_ATF build knob has been removed and its functionality
2102 has been subsumed into the more generic WITHOUT_TESTS. If you were
2103 using the former to disable the build of the ATF libraries, you
2104 should change your settings to use the latter.
2107 The default version of mtree is nmtree which is obtained from
2108 NetBSD. The output is generally the same, but may vary
2109 slightly. If you found you need identical output adding
2110 "-F freebsd9" to the command line should do the trick. For the
2111 time being, the old mtree is available as fmtree.
2114 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
2115 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
2116 1.1.4_8 and verify bsdyml not linked in, before running "make
2118 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
2120 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
2123 The stable/10 branch has been created in subversion from head
2130 Sometimes, obscure build problems are the result of environment
2131 poisoning. This can happen because the make utility reads its
2132 environment when searching for values for global variables. To run
2133 your build attempts in an "environmental clean room", prefix all make
2134 commands with 'env -i '. See the env(1) manual page for more details.
2135 Occasionally a build failure will occur with "make -j" due to a race
2136 condition. If this happens try building again without -j, and please
2137 report a bug if it happens consistently.
2139 When upgrading from one major version to another it is generally best to
2140 upgrade to the latest code in the currently installed branch first, then
2141 do an upgrade to the new branch. This is the best-tested upgrade path,
2142 and has the highest probability of being successful. Please try this
2143 approach if you encounter problems with a major version upgrade. Since
2144 the stable 4.x branch point, one has generally been able to upgrade from
2145 anywhere in the most recent stable branch to head / current (or even the
2146 last couple of stable branches). See the top of this file when there's
2149 The update process will emit an error on an attempt to perform a build
2150 or install from a FreeBSD version below the earliest supported version.
2151 When updating from an older version the update should be performed one
2152 major release at a time, including running `make delete-old` at each
2155 When upgrading a live system, having a root shell around before
2156 installing anything can help undo problems. Not having a root shell
2157 around can lead to problems if pam has changed too much from your
2158 starting point to allow continued authentication after the upgrade.
2160 This file should be read as a log of events. When a later event changes
2161 information of a prior event, the prior event should not be deleted.
2162 Instead, a pointer to the entry with the new information should be
2163 placed in the old entry. Readers of this file should also sanity check
2164 older entries before relying on them blindly. Authors of new entries
2165 should write them with this in mind.
2169 When upgrading the boot ZFS pool to a new version, always follow
2172 1.) recompile and reinstall the ZFS boot loader and boot block
2173 (this is part of "make buildworld" and "make installworld")
2175 2.) update the ZFS boot block on your boot drive
2177 The following example updates the ZFS boot block on the first
2178 partition (freebsd-boot) of a GPT partitioned drive ada0:
2179 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
2181 Non-boot pools do not need these updates.
2185 If you are updating from a prior version of FreeBSD (even one just
2186 a few days old), you should follow this procedure. It is the most
2187 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2189 make kernel-toolchain
2190 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2191 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2193 To test a kernel once
2194 ---------------------
2195 If you just want to boot a kernel once (because you are not sure
2196 if it works, or if you want to boot a known bad kernel to provide
2197 debugging information) run
2198 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2199 nextboot -k testkernel
2201 To rebuild everything and install it on the current system.
2202 -----------------------------------------------------------
2203 # Note: sometimes if you are running current you gotta do more than
2204 # is listed here if you are upgrading from a really old current.
2206 <make sure you have good level 0 dumps>
2208 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2209 make installkernel KERNCONF=YOUR_KERNEL_HERE
2211 <reboot in single user> [3]
2218 To cross-install current onto a separate partition
2219 --------------------------------------------------
2220 # In this approach we use a separate partition to hold
2221 # current's root, 'usr', and 'var' directories. A partition
2222 # holding "/", "/usr" and "/var" should be about 2GB in
2225 <make sure you have good level 0 dumps>
2228 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2229 <maybe newfs current's root partition>
2230 <mount current's root partition on directory ${CURRENT_ROOT}>
2231 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
2232 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2233 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2234 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2235 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2236 <reboot into current>
2237 <do a "native" rebuild/install as described in the previous section>
2238 <maybe install compatibility libraries from ports/misc/compat*>
2242 To upgrade in-place from stable to current
2243 ----------------------------------------------
2244 <make sure you have good level 0 dumps>
2246 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
2247 make installkernel KERNCONF=YOUR_KERNEL_HERE
2249 <reboot in single user> [3]
2256 Make sure that you've read the UPDATING file to understand the
2257 tweaks to various things you need. At this point in the life
2258 cycle of current, things change often and you are on your own
2259 to cope. The defaults can also change, so please read ALL of
2260 the UPDATING entries.
2262 Also, if you are tracking -current, you must be subscribed to
2263 freebsd-current@freebsd.org. Make sure that before you update
2264 your sources that you have read and understood all the recent
2265 messages there. If in doubt, please track -stable which has
2266 much fewer pitfalls.
2268 [1] If you have third party modules, such as vmware, you
2269 should disable them at this point so they don't crash your
2272 [3] From the bootblocks, boot -s, and then do
2276 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed
2277 cd src # full path to source
2278 adjkerntz -i # if CMOS is wall time
2279 Also, when doing a major release upgrade, it is required that
2280 you boot into single user mode to do the installworld.
2282 [4] Note: This step is non-optional. Failure to do this step
2283 can result in a significant reduction in the functionality of the
2284 system. Attempting to do it by hand is not recommended and those
2285 that pursue this avenue should read this file carefully, as well
2286 as the archives of freebsd-current and freebsd-hackers mailing lists
2287 for potential gotchas. The -U option is also useful to consider.
2288 See mergemaster(8) for more information.
2290 [5] Usually this step is a no-op. However, from time to time
2291 you may need to do this if you get unknown user in the following
2292 step. It never hurts to do it all the time. You may need to
2293 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2294 install) after the buildworld before this step if you last updated
2295 from current before 20130425 or from -stable before 20130430.
2297 [6] This only deletes old files and directories. Old libraries
2298 can be deleted by "make delete-old-libs", but you have to make
2299 sure that no program is using those libraries anymore.
2301 [8] The new kernel must be able to run existing binaries used by an
2302 installworld. When upgrading across major versions, the new kernel's
2303 configuration must include the correct COMPAT_FREEBSD<n> option for
2304 existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure
2305 to do so may leave you with a system that is hard to boot to recover. A
2306 GENERIC kernel will include suitable compatibility options to run
2307 binaries from older branches. Note that the ability to run binaries
2308 from unsupported branches is not guaranteed.
2310 Make sure that you merge any new devices from GENERIC since the
2311 last time you updated your kernel config file. Options also
2312 change over time, so you may need to adjust your custom kernels
2315 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2316 "?=" instead of the "=" assignment operator, so that buildworld can
2317 override the CPUTYPE if it needs to.
2319 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2320 not on the command line, or in /etc/make.conf. buildworld will
2321 warn if it is improperly defined.
2324 This file contains a list, in reverse chronological order, of major
2325 breakages in tracking -current. It is not guaranteed to be a complete
2326 list of such breakages, and only contains entries since September 23, 2011.
2327 If you need to see UPDATING entries from before that date, you will need
2328 to fetch an UPDATING file from an older FreeBSD release.
2330 Copyright information:
2332 Copyright 1998-2009 M. Warner Losh <imp@FreeBSD.org>
2334 Redistribution, publication, translation and use, with or without
2335 modification, in full or in part, in any form or format of this
2336 document are permitted without further permission from the author.
2338 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2339 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2340 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2341 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2342 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2343 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2344 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2345 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2346 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2347 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2348 POSSIBILITY OF SUCH DAMAGE.
2350 Contact Warner Losh if you have any questions about your use of