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 r362158 changed the arguments for VFS_CHECKEXP(). As such, any
31 out of tree file systems need to be modified and rebuilt.
32 Also, any file systems that are modules must be rebuilt.
35 read(2) of a directory fd is now rejected by default. root may
36 re-enable it for system root only on non-ZFS filesystems with the
37 security.bsd.allow_read_dir sysctl(8) MIB if
38 security.bsd.suser_enabled=1.
40 It may be advised to setup aliases for grep to default to `-d skip` if
41 commonly non-recursively grepping a list that includes directories and
42 the potential for the resulting stderr output is not tolerable. Example
43 aliases are now installed, commented out, in /root/.cshrc and
47 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
48 been upgraded to 10.0.1. Please see the 20141231 entry below for
49 information about prerequisites and upgrading, if you are not already
50 using clang 3.5.0 or higher.
53 Support for obsolete compilers has been removed from the build system.
54 Clang 6 and GCC 6.4 are the minimum supported versions.
57 closefrom(2) has been moved under COMPAT12, and replaced in libc with a
58 stub that calls close_range(2). If using a custom kernel configuration,
59 you may want to ensure that the COMPAT_FREEBSD12 option is included, as
60 a slightly older -CURRENT userland and older FreeBSD userlands may not
61 be functional without closefrom(2).
64 Upstream DTS from Linux 5.6 was merged and they now have the SID
65 and THS (Secure ID controller and THermal Sensor) node present.
66 The DTB overlays have now been removed from the tree for the H3/H5 and
67 A64 SoCs and the aw_sid and aw_thermal driver have been updated to
68 deal with upstream DTS. If you are using those overlays you need to
69 remove them from loader.conf and update the DTBs on the FAT partition.
72 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
73 been upgraded to 10.0.0. Please see the 20141231 entry below for
74 information about prerequisites and upgrading, if you are not already
75 using clang 3.5.0 or higher.
78 The amd(8) automount daemon has been removed from the source tree.
79 As of FreeBSD 10.1 autofs(5) is the preferred tool for automounting.
80 amd is still available in the sysutils/am-utils port.
83 Removed brooktree driver (bktr.4) from the tree.
86 The WITH_GPL_DTC option has been removed. The BSD-licenced device tree
87 compiler in usr.bin/dtc is used on all architectures which use dtc, and
88 the GPL dtc is available (if needed) from the sysutils/dtc port.
91 The WITHOUT_LLVM_LIBUNWIND option has been removed. LLVM's libunwind
92 is used by all supported CPU architectures.
95 GCC 4.2.1 has been removed from the tree. The WITH_GCC,
96 WITH_GCC_BOOTSTRAP, and WITH_GNUCXX options are no longer available.
97 Users who wish to build FreeBSD with GCC must use the external toolchain
101 ncurses has been updated to a newer version (6.2-20200215). Given the ABI
102 has changed, users will have to rebuild all the ports that are linked to
106 The size of struct vnet and the magic cookie have changed.
107 Users need to recompile libkvm and all modules using VIMAGE
108 together with their new kernel.
111 Defining the long deprecated NO_CTF, NO_DEBUG_FILES, NO_INSTALLLIB,
112 NO_MAN, NO_PROFILE, and NO_WARNS variables is now an error. Update
113 your Makefiles and scripts to define MK_<var>=no instead as required.
115 One exception to this is that program or library Makefiles should
116 define MAN to empty rather than setting MK_MAN=no.
119 Clang/LLVM is now the default compiler and LLD the default
123 make universe no longer uses GCC 4.2.1 on any architectures.
124 Architectures not supported by in-tree Clang/LLVM require an
125 external toolchain package.
128 GCC 4.2.1 is now not built by default, as part of the GCC 4.2.1
129 retirement plan. Specifically, the GCC, GCC_BOOTSTRAP, and GNUCXX
130 options default to off for all supported CPU architectures. As a
131 short-term transition aid they may be enabled via WITH_* options.
132 GCC 4.2.1 is expected to be removed from the tree on 2020-03-31.
135 Support for armv5 has been disconnected and is being removed. The
136 machine combination MACHINE=arm MACHINE_ARCH=arm is no longer valid.
137 You must now use a MACHINE_ARCH of armv6 or armv7. The default
138 MACHINE_ARCH for MACHINE=arm is now armv7.
141 Clang/LLVM is now the default compiler for all powerpc architectures.
142 LLD is now the default linker for powerpc64. The change for powerpc64
143 also includes a change to the ELFv2 ABI, incompatible with the existing
147 Kernel-loadable random(4) modules are no longer unloadable.
150 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
151 been upgraded to 9.0.1. Please see the 20141231 entry below for
152 information about prerequisites and upgrading, if you are not already
153 using clang 3.5.0 or higher.
156 r355677 has modified the internal interface used between the
157 NFS modules in the kernel. As such, they must all be upgraded
158 simultaneously. I will do a version bump for this.
161 The root certificates of the Mozilla CA Certificate Store have been
162 imported into the base system and can be managed with the certctl(8)
163 utility. If you have installed the security/ca_root_nss port or package
164 with the ETCSYMLINK option (the default), be advised that there may be
165 differences between those included in the port and those included in
166 base due to differences in nss branch used as well as general update
167 frequency. Note also that certctl(8) cannot manage certs in the
168 format used by the security/ca_root_nss port.
171 The amd(8) automount daemon has been disabled by default, and will be
172 removed in the future. As of FreeBSD 10.1 the autofs(5) is available
176 The nctgpio and wbwd drivers have been moved to the superio bus.
177 If you have one of these drivers in a kernel configuration, then
178 you should add device superio to it. If you use one of these drivers
179 as a module and you compile a custom set of modules, then you should
180 add superio to the set.
183 KPIs for network drivers to access interface addresses have changed.
184 Users need to recompile NIC driver modules together with kernel.
187 The net.link.tap.user_open sysctl no longer prevents user opening of
188 already created /dev/tapNN devices. Access is still controlled by
189 node permissions, just like tun devices. The net.link.tap.user_open
190 sysctl is now used only to allow users to perform devfs cloning of
191 tap devices, and the subsequent open may not succeed if the user is not
192 in the appropriate group. This sysctl may be deprecated/removed
193 completely in the future.
196 mips, powerpc, and sparc64 are no longer built as part of
197 universe / tinderbox unless MAKE_OBSOLETE_GCC is defined. If
198 not defined, mips, powerpc, and sparc64 builds will look for
199 the xtoolchain binaries and if installed use them for universe
200 builds. As llvm 9.0 becomes vetted for these architectures, they
201 will be removed from the list.
204 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
205 been upgraded to 9.0.0. Please see the 20141231 entry below for
206 information about prerequisites and upgrading, if you are not already
207 using clang 3.5.0 or higher.
210 The hpt27xx, hptmv, hptnr, and hptrr drivers have been removed from
211 GENERIC. They are available as modules and can be loaded by adding
212 to /boot/loader.conf hpt27xx_load="YES", hptmv_load="YES",
213 hptnr_load="YES", or hptrr_load="YES", respectively.
216 ntpd no longer by default locks its pages in memory, allowing them
217 to be paged out by the kernel. Use rlimit memlock to restore
218 historic BSD behaviour. For example, add "rlimit memlock 32"
219 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
222 Several of ping6's options have been renamed for better consistency
223 with ping. If you use any of -ARWXaghmrtwx, you must update your
224 scripts. See ping6(8) for details.
227 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
228 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
229 been removed from mount_fusefs(8). You can safely remove them from
230 your scripts, because they had no effect.
232 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
233 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
234 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
235 sysctls have been removed. If you felt the need to set any of them to
236 a non-default value, please tell asomers@FreeBSD.org why.
239 Default permissions on the /var/account/acct file (and copies of it
240 rotated by periodic daily scripts) are changed from 0644 to 0640
241 because the file contains sensitive information that should not be
242 world-readable. If the /var/account directory must be created by
243 rc.d/accounting, the mode used is now 0750. Admins who use the
244 accounting feature are encouraged to change the mode of an existing
245 /var/account directory to 0750 or 0700.
248 Entropy collection and the /dev/random device are no longer optional
249 components. The "device random" option has been removed.
250 Implementations of distilling algorithms can still be made loadable
251 with "options RANDOM_LOADABLE" (e.g., random_fortuna.ko).
254 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
255 been upgraded to 8.0.1. Please see the 20141231 entry below for
256 information about prerequisites and upgrading, if you are not already
257 using clang 3.5.0 or higher.
260 A fix was applied to i386 kernel modules to avoid panics with
261 dpcpu or vnet. Users need to recompile i386 kernel modules
262 having pcpu or vnet sections or they will refuse to load.
265 User-wired pages now have their own counter,
266 vm.stats.vm.v_user_wire_count. The vm.max_wired sysctl was renamed
267 to vm.max_user_wired and changed from an unsigned int to an unsigned
268 long. bhyve VMs wired with the -S are now subject to the user
269 wiring limit; the vm.max_user_wired sysctl may need to be tuned to
270 avoid running into the limit.
273 The IPSEC option has been removed from GENERIC. Users requiring
274 ipsec(4) must now load the ipsec(4) kernel module.
277 The tap(4) driver has been folded into tun(4), and the module has been
278 renamed to tuntap. You should update any kld_list="if_tap" or
279 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
280 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
281 module instead, and "device tap" or "device tun" entries in kernel
282 config files to select the tuntap device instead.
285 The following knobs have been added related to tradeoffs between
286 safe use of the random device and availability in the absence of
289 kern.random.initial_seeding.bypass_before_seeding: tunable; set
290 non-zero to bypass the random device prior to seeding, or zero to
291 block random requests until the random device is initially seeded.
292 For now, set to 1 (unsafe) by default to restore pre-r346250 boot
293 availability properties.
295 kern.random.initial_seeding.read_random_bypassed_before_seeding:
296 read-only diagnostic sysctl that is set when bypass is enabled and
297 read_random(9) is bypassed, to enable programmatic handling of this
298 initial condition, if desired.
300 kern.random.initial_seeding.arc4random_bypassed_before_seeding:
301 Similar to the above, but for for arc4random(9) initial seeding.
303 kern.random.initial_seeding.disable_bypass_warnings: tunable; set
304 non-zero to disable warnings in dmesg when the same conditions are
305 met as for the diagnostic sysctls above. Defaults to zero, i.e.,
306 produce warnings in dmesg when the conditions are met.
309 The loadable random module KPI has changed; the random_infra_init()
310 routine now requires a 3rd function pointer for a bool (*)(void)
311 method that returns true if the random device is seeded (and
312 therefore unblocked).
315 r345895 reverts r320698. This implies that an nfsuserd(8) daemon
316 built from head sources between r320757 (July 6, 2017) and
317 r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
318 is added to the command line.
319 nfsuserd daemons built from head sources that are post-r338192 are
320 not affected and should continue to work.
323 The fuse(4) module has been renamed to fusefs(4) for consistency with
324 other filesystems. You should update any kld_load="fuse" entries in
325 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
326 "options FUSE" entries in kernel config files.
329 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
330 8.0.0. Please see the 20141231 entry below for information about
331 prerequisites and upgrading, if you are not already using clang 3.5.0
335 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
336 compiled into your custom kernel, add 'device xz' statement to the
340 drm and drm2 have been removed from the tree. Please see
341 https://wiki.freebsd.org/Graphics for the latest information on
342 migrating to the drm ports.
345 Iflib is no longer unconditionally compiled into the kernel. Drivers
346 using iflib and statically compiled into the kernel, now require
347 the 'device iflib' config option. For the same drivers loaded as
348 modules on kernels not having 'device iflib', the iflib.ko module
349 is loaded automatically.
352 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
353 options no longer exist since r343219 and r343427 respectively;
354 nothing uses them, so they should be just removed from custom
358 r342635 changes the way efibootmgr(8) works by requiring users to add
359 the -b (bootnum) parameter for commands where the bootnum was previously
360 specified with each option. For example 'efibootmgr -B 0001' is now
361 'efibootmgr -B -b 0001'.
364 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
365 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
366 servers that have vfs.nfsd.nfs_privport set will only allow mounts
367 from clients using a reserved port#. Since both the FreeBSD and Linux
368 NFSv4 clients use reserved port#s by default, this should not affect
372 The XLP config has been removed. We can't support 64-bit atomics in this
373 kernel because it is running in 32-bit mode. XLP users must transition
374 to running a 64-bit kernel (XLP64 or XLPN32).
376 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
377 the preferred emulator today and we don't need two different ones.
379 The old sibyte / swarm / Broadcom BCM1250 support has been
380 removed from the mips port.
383 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
384 7.0.1. Please see the 20141231 entry below for information about
385 prerequisites and upgrading, if you are not already using clang 3.5.0
389 Remove the timed and netdate programs from the base tree. Setting
390 the time with these daemons has been obsolete for over a decade.
393 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
394 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
395 it produces broken binaries when ifuncs are in use. Users needing
396 GNU ld should install the binutils port or package.
399 The BSD crtbegin and crtend code has been enabled by default. It has
400 had extensive testing on amd64, arm64, and i386. It can be disabled
401 by building a world with -DWITHOUT_BSD_CRTBEGIN.
404 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
405 has been converted to a port (misc/ctm) and will be removed from
406 FreeBSD-13. It is available as a package (ctm) for all supported
410 The default newsyslog.conf(5) file has been changed to only include
411 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
412 the filenames end in '.conf' and do not begin with a '.'.
414 You should check the configuration files in these two directories match
415 this naming convention. You can verify which configuration files are
416 being included using the command:
420 Ports for the DRM modules have been simplified. Now, amd64 users should
421 just install the drm-kmod port. All others should install
424 Graphics hardware that's newer than about 2010 usually works with
425 drm-kmod. For hardware older than 2013, however, some users will need
426 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
427 than 2008 usually only works in drm-legacy-kmod. The graphics team can
428 only commit to hardware made since 2013 due to the complexity of the
429 market and difficulty to test all the older cards effectively. If you
430 have hardware supported by drm-kmod, you are strongly encouraged to use
431 that as you will get better support.
433 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
434 elsewhere, the drm and drm2 modules will be eliminated from the src base
435 soon (with a limited exception for arm). Please update to the package
436 asap and report any issues to x11@freebsd.org.
438 Generally, anybody using the drm*-kmod packages should add
439 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
440 cross-threading surprises, especially with automatic driver
441 loading from X11 startup. These will become the defaults in 13-current
445 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
446 custom kernel and module loading configuration files must be updated
447 accordingly. Moreover, interfaces previous presented as ixlvN to the
448 system are now exposed as iavfN and network configuration files must
449 be adjusted as necessary.
452 OpenSSL has been updated to version 1.1.1. This update included
453 additional various API changes throughout the base system. It is
454 important to rebuild third-party software after upgrading. The value
455 of __FreeBSD_version has been bumped accordingly.
458 The legacy DRM modules and drivers have now been added to the loader's
459 module blacklist, in favor of loading them with kld_list in rc.conf(5).
460 The module blacklist may be overridden with the loader.conf(5)
461 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
465 The cam(4) based nda(4) driver will be used over nvd(4) by default on
466 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
467 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
468 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
472 Reproducible build mode is now on by default, in preparation for
473 FreeBSD 12.0. This eliminates build metadata such as the user,
474 host, and time from the kernel (and uname), unless the working tree
475 corresponds to a modified checkout from a version control system.
476 The previous behavior can be obtained by setting the /etc/src.conf
477 knob WITHOUT_REPRODUCIBLE_BUILD.
480 The Yarrow CSPRNG has been removed from the kernel as it has not been
481 supported by its designers since at least 2003. Fortuna has been the
482 default since FreeBSD-11.
485 devctl freeze/thaw have gone into the tree, the rc scripts have been
486 updated to use them and devmatch has been changed. You should update
487 kernel, userland and rc scripts all at the same time.
490 The default interpreter has been switched from 4th to Lua.
491 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
492 interpreter. If you have custom FORTH code you will need to set
493 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
494 src.conf for the build. This will create default hard links between
495 loader and loader_4th instead of loader and loader_lua, the new default.
496 If you are using UEFI it will create the proper hard link to loader.efi.
498 bhyve uses userboot.so. It remains 4th-only until some issues are solved
499 regarding coexisting with multiple versions of FreeBSD are resolved.
502 ls(1) now respects the COLORTERM environment variable used in other
503 systems and software to indicate that a colored terminal is both
504 supported and desired. If ls(1) is suddenly emitting colors, they may
505 be disabled again by either removing the unwanted COLORTERM from your
506 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
507 may not be observed in a future release.
510 The default pager for most commands has been changed to "less". To
511 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
515 The jedec_ts(4) driver has been removed. A superset of its functionality
516 is available in the jedec_dimm(4) driver, and the manpage for that
517 driver includes migration instructions. If you have "device jedec_ts"
518 in your kernel configuration file, it must be removed.
521 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
522 This should have no effect if the kernel is booted via BIOS/legacy boot.
523 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
524 has a buggy firmware that prevents a successful boot due to use of
528 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
529 support has been removed from the tree. These ports were
530 obsolete and/or known to be broken for many years.
533 loader.efi has been augmented to participate more fully in the
534 UEFI boot manager protocol. loader.efi will now look at the
535 BootXXXX environment variable to determine if a specific kernel
536 or root partition was specified. XXXX is derived from BootCurrent.
537 efibootmgr(8) manages these standard UEFI variables.
540 zfsloader's functionality has now been folded into loader.
541 zfsloader is no longer necessary once you've updated your
542 boot blocks. For a transition period, we will install a
543 hardlink for zfsloader to loader to allow a smooth transition
544 until the boot blocks can be updated (hard link because old
545 zfs boot blocks don't understand symlinks).
548 ARM64 now have efifb support, if you want to have serial console
549 on your arm64 board when an screen is connected and the bootloader
550 setup a frame buffer for us to use, just add :
554 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
555 an screen connected as the firmware will setup a frame buffer are that
556 u-boot will expose as an EFI frame buffer.
559 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
560 or take steps to update /etc/passwd before doing installworld on
561 existing systems. Do not skip the "mergemaster -Fp" step before
562 installworld, as described in the update procedures near the bottom
563 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
564 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
565 the ntp config file contain options that change file/dir locations.
566 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
567 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
568 taking steps to ensure that all required files/dirs are accessible
572 Big endian arm support has been removed.
575 The static environment setup in kernel configs is no longer mutually
576 exclusive with the loader(8) environment by default. In order to
577 restore the previous default behavior of disabling the loader(8)
578 environment if a static environment is present, you must specify
579 loader_env.disabled=1 in the static environment.
582 The ABI of syscalls used by management tools like sockstat and
583 netstat has been broken to allow 32-bit binaries to work on
584 64-bit kernels without modification. These programs will need
585 to match the kernel in order to function. External programs may
586 require minor modifications to accommodate a change of type in
587 structures from pointers to 64-bit virtual addresses.
590 On i386 and amd64 atomics are now inlined. Out of tree modules using
591 atomics will need to be rebuilt.
594 The '%I' format in the kern.corefile sysctl limits the number of
595 core files that a process can generate to the number stored in the
596 debug.ncores sysctl. The '%I' format is replaced by the single digit
597 index. Previously, if all indexes were taken the kernel would overwrite
598 only a core file with the highest index in a filename.
599 Currently the system will create a new core file if there is a free
600 index or if all slots are taken it will overwrite the oldest one.
603 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
604 6.0.1. Please see the 20141231 entry below for information about
605 prerequisites and upgrading, if you are not already using clang 3.5.0
609 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
610 needed to be changed to work with it. This change was made with r335763
611 and requires a mergemaster / etcupdate / etc to update the installed
615 r334930 changed the interface between the NFS modules, so they all
616 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
619 As of r334391 lld is the default amd64 system linker; it is installed
620 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
624 The kernel / userland interface for devinfo changed, so you'll
625 need a new kernel and userland as a pair for it to work (rebuilding
626 lib/libdevinfo is all that's required). devinfo and devmatch will
627 not work, but everything else will when there's a mismatch.
630 The on-disk format for hwpmc callchain records has changed to include
631 threadid corresponding to a given record. This changes the field offsets
632 and thus requires that libpmcstat be rebuilt before using a kernel
636 The vxge(4) driver has been removed. This driver was introduced into
637 HEAD one week before the Exar left the Ethernet market and is not
638 known to be used. If you have device vxge in your kernel config file
642 The amd64 kernel now requires a ld that supports ifunc to produce a
643 working kernel, either lld or a newer binutils. lld is built by default
644 on amd64, and the 'buildkernel' target uses it automatically. However,
645 it is not the default linker, so building the kernel the traditional
646 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
647 binutils port/package). lld will soon be default, and this requirement
650 NOTE: As of r334391 lld is the default system linker on amd64, and no
651 workaround is necessary.
654 The nxge(4) driver has been removed. This driver was for PCI-X 10g
655 cards made by s2io/Neterion. The company was acquired by Exar and
656 no longer sells or supports Ethernet products. If you have device
657 nxge in your kernel config file it must be removed.
660 The tz database (tzdb) has been updated to 2018e. This version more
661 correctly models time stamps in time zones with negative DST such as
662 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
663 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
664 time zone abbreviations and the tm_isdst flag.
667 The ixgb(4) driver has been removed. This driver was for an early and
668 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
669 quickly shifted to the long lived ixgbe family. If you have device
670 ixgb in your kernel config file it must be removed.
673 The lmc(4) driver has been removed. This was a WAN interface
674 card that was already reportedly rare in 2003, and had an ambiguous
675 license. If you have device lmc in your kernel config file it must
679 Support for Arcnet networks has been removed. If you have device
680 arcnet or device cm in your kernel config file they must be
684 Support for FDDI networks has been removed. If you have device
685 fddi or device fpa in your kernel config file they must be
689 In addition to supporting RFC 3164 formatted messages, the
690 syslogd(8) service is now capable of parsing RFC 5424 formatted
691 log messages. The main benefit of using RFC 5424 is that clients
692 may now send log messages with timestamps containing year numbers,
693 microseconds and time zone offsets.
695 Similarly, the syslog(3) C library function has been altered to
696 send RFC 5424 formatted messages to the local system logging
697 daemon. On systems using syslogd(8), this change should have no
698 negative impact, as long as syslogd(8) and the C library are
699 updated at the same time. On systems using a different system
700 logging daemon, it may be necessary to make configuration
701 adjustments, depending on the software used.
703 When using syslog-ng, add the 'syslog-protocol' flag to local
704 input sources to enable parsing of RFC 5424 formatted messages:
707 unix-dgram("/var/run/log" flags(syslog-protocol));
710 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
711 of the 'imuxsock' module to let messages be processed by the
712 regular RFC 3164/5424 parsing pipeline:
714 module(load="imuxsock" SysSock.UseSpecialParser="off")
716 Do note that these changes only affect communication between local
717 applications and syslogd(8). The format that syslogd(8) uses to
718 store messages on disk or forward messages to other systems
719 remains unchanged. syslogd(8) still uses RFC 3164 for these
720 purposes. Options to customize this behaviour will be added in the
721 future. Utilities that process log files stored in /var/log are
722 thus expected to continue to function as before.
724 __FreeBSD_version has been incremented to 1200061 to denote this
728 Support for token ring networks has been removed. If you
729 have "device token" in your kernel config you should remove
730 it. No device drivers supported token ring.
733 makefs was modified to be able to tag ISO9660 El Torito boot catalog
734 entries as EFI instead of overloading the i386 tag as done previously.
735 The amd64 mkisoimages.sh script used to build amd64 ISO images for
736 release was updated to use this. This may mean that makefs must be
737 updated before "make cdrom" can be run in the release directory. This
738 should be as simple as:
740 $ cd $SRCDIR/usr.sbin/makefs
741 $ make depend all install
744 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
745 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
746 Co-existence for the transition period will come shortly. Booting is a
747 complex environment and test coverage for Lua-enabled loaders has been
748 thin, so it would be prudent to assume it might not work and make
749 provisions for backup boot methods.
752 devmatch functionality has been turned on in devd. It will automatically
753 load drivers for unattached devices. This may cause unexpected drivers
754 to be loaded. Please report any problems to current@ and
758 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
759 6.0.0. Please see the 20141231 entry below for information about
760 prerequisites and upgrading, if you are not already using clang 3.5.0
764 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
765 This means it is used to link the kernel and userland libraries and
766 executables, but is not yet installed as /usr/bin/ld by default.
768 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
769 WITHOUT_LLD_BOOTSTRAP=yes
772 On i386, pmtimer has been removed. Its functionality has been folded
773 into apm. It was a no-op on ACPI in current for a while now (but was
774 still needed on i386 in FreeBSD 11 and earlier). Users may need to
775 remove it from kernel config files.
778 The use of RSS hash from the network card aka flowid has been
779 disabled by default for lagg(4) as it's currently incompatible with
780 the lacp and loadbalance protocols.
782 This can be re-enabled by setting the following in loader.conf:
783 net.link.lagg.default_use_flowid="1"
786 The SW_WATCHDOG option is no longer necessary to enable the
787 hardclock-based software watchdog if no hardware watchdog is
788 configured. As before, SW_WATCHDOG will cause the software
789 watchdog to be enabled even if a hardware watchdog is configured.
792 r326887 fixes the issue described in the 20171214 UPDATING entry.
793 r326888 flips the switch back to building GELI support always.
796 r362593 broke ZFS + GELI support for reasons unknown. However,
797 it also broke ZFS support generally, so GELI has been turned off
798 by default as the lesser evil in r326857. If you boot off ZFS and/or
799 GELI, it might not be a good time to update.
802 PowerPC users must update loader(8) by rebuilding world before
803 installing a new kernel, as the protocol connecting them has
804 changed. Without the update, loader metadata will not be passed
805 successfully to the kernel and users will have to enter their
806 root partition at the kernel mountroot prompt to continue booting.
807 Newer versions of loader can boot old kernels without issue.
810 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
811 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
812 to WITH/OUT_LOADER_GELI.
815 The naive and non-compliant support of posix_fallocate(2) in ZFS
816 has been removed as of r325320. The system call now returns EINVAL
817 when used on a ZFS file. Although the new behavior complies with the
818 standard, some consumers are not prepared to cope with it.
819 One known victim is lld prior to r325420.
822 Building in a FreeBSD src checkout will automatically create object
823 directories now rather than store files in the current directory if
824 'make obj' was not ran. Calling 'make obj' is no longer necessary.
825 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
826 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
830 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
831 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
832 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
833 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
834 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
835 The UNIFIED_OBJDIR option is a transitional feature that will be
836 removed for 12.0 release; please migrate to the new format for any
837 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
838 than hardcoding paths.
841 The native-xtools target no longer installs the files by default to the
842 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
843 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
846 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
847 options are changing from controlling the build if defined / undefined
848 to controlling the build with explicit 'yes' or 'no' values. They will
849 shift to WITH/WITHOUT options to match other options in the system.
852 libstand has turned into a private library for sys/boot use only.
853 It is no longer supported as a public interface outside of sys/boot.
856 The arm port has split armv6 into armv6 and armv7. armv7 is now
857 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
858 and are running a kernel from before r324363, you will need to add
859 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
862 When building multiple kernels using KERNCONF, non-existent KERNCONF
863 files will produce an error and buildkernel will fail. Previously
864 missing KERNCONF files silently failed giving no indication as to
865 why, only to subsequently discover during installkernel that the
866 desired kernel was never built in the first place.
869 The default serial number format for CTL LUNs has changed. This will
870 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
871 or iSCSI clients care about their LUNs' serial numbers. Users who
872 require serial number stability should hardcode serial numbers in
876 For 32-bit arm compiled for hard-float support, soft-floating point
877 binaries now always get their shared libraries from
878 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
879 /usr/libsoft also existed). Only users with a hard-float ld.so, but
880 soft-float everything else should be affected.
883 The geli password typed at boot is now hidden. To restore the previous
884 behavior, see geli(8) for configuration options.
887 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
888 sysctl values. Minor nit, but requires a rebuild of both world/kernel
892 "make check" behavior (made in ^/head@r295380) has been changed to
893 execute from a limited sandbox, as opposed to executing from
897 - The "beforecheck" and "aftercheck" targets are now specified.
898 - ${CHECKDIR} (added in commit noted above) has been removed.
899 - Legacy behavior can be enabled by setting
900 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
902 If the limited sandbox mode is enabled, "make check" will execute
903 "make distribution", then install, execute the tests, and clean up the
904 sandbox if successful.
906 The "make distribution" and "make install" targets are typically run as
907 root to set appropriate permissions and ownership at installation time.
908 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
909 environment if executing "make check" with limited sandbox mode using
910 an unprivileged user.
913 Since the switch to GPT disk labels, fsck for UFS/FFS has been
914 unable to automatically find alternate superblocks. As of r322297,
915 the information needed to find alternate superblocks has been
916 moved to the end of the area reserved for the boot block.
917 Filesystems created with a newfs of this vintage or later
918 will create the recovery information. If you have a filesystem
919 created prior to this change and wish to have a recovery block
920 created for your filesystem, you can do so by running fsck in
921 foreground mode (i.e., do not use the -p or -y options). As it
922 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
923 to which you should answer yes.
926 As of r321665, an NFSv4 server configuration that services
927 Kerberos mounts or clients that do not support the uid/gid in
928 owner/owner_group string capability, must explicitly enable
929 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
930 machine's /etc/rc.conf file.
933 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
934 Please see the 20141231 entry below for information about prerequisites
935 and upgrading, if you are not already using clang 3.5.0 or higher.
938 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
939 r-commands (rlogin, rsh, etc.) to be built with the base system.
942 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
943 a very major ABI incompatible change, so users of FreeBSD/powerpc must
944 be careful when performing source upgrades. It is best to run
945 'make installworld' from an alternate root system, either a live
946 CD/memory stick, or a temporary root partition. Additionally, all ports
947 must be recompiled. powerpc64 is largely unaffected, except in the case
948 of 32-bit compatibility. All 32-bit binaries will be affected.
951 Forward compatibility for the "ino64" project have been committed. This
952 will allow most new binaries to run on older kernels in a limited
953 fashion. This prevents many of the common foot-shooting actions in the
954 upgrade as well as the limited ability to roll back the kernel across
955 the ino64 upgrade. Complicated use cases may not work properly, though
956 enough simpler ones work to allow recovery in most situations.
959 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
960 if you require the GPL compiler.
963 The internal ABI used for communication between the NFS kernel modules
964 was changed by r320085, so __FreeBSD_version was bumped to
965 ensure all the NFS related modules are updated together.
968 The ABI of struct event was changed by extending the data
969 member to 64bit and adding ext fields. For upgrade, same
970 precautions as for the entry 20170523 "ino64" must be
974 The GNU roff toolchain has been removed from base. To render manpages
975 which are not supported by mandoc(1), man(1) can fallback on GNU roff
976 from ports (and recommends to install it).
977 To render roff(7) documents, consider using GNU roff from ports or the
978 heirloom doctools roff toolchain from ports via pkg install groff or
979 via pkg install heirloom-doctools.
982 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
983 smaller runtime footprint builds. This is useful for embedded systems
984 which only require one chipset support.
986 If you load it as a module, make sure this is in /boot/loader.conf:
990 This will load the HAL, all chip/RF backends and if_ath_pci.
991 If you have if_ath_pci in /boot/loader.conf, ensure it is after
992 if_ath or it will not load any HAL chipset support.
994 If you want to selectively load things (eg on ye cheape ARM/MIPS
995 platforms where RAM is at a premium) you should:
998 * load the chip modules in question
999 * load ath_rate, ath_dfs
1001 * load if_ath_pci and/or if_ath_ahb depending upon your particular
1002 bus bind type - this is where probe/attach is done.
1004 For further comments/feedback, poke adrian@ .
1007 The "ino64" 64-bit inode project has been committed, which extends
1008 a number of types to 64 bits. Upgrading in place requires care and
1009 adherence to the documented upgrade procedure.
1011 If using a custom kernel configuration ensure that the
1012 COMPAT_FREEBSD11 option is included (as during the upgrade the
1013 system will be running the ino64 kernel with the existing world).
1015 For the safest in-place upgrade begin by removing previous build
1016 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full
1017 procedure documented below under the heading "To rebuild everything and
1018 install it on the current system." Specifically, a reboot is required
1019 after installing the new kernel before installing world. While an
1020 installworld normally works by accident from multiuser after rebooting
1021 the proper kernel, there are many cases where this will fail across this
1022 upgrade and installworld from single user is required.
1025 The NATM framework including the en(4), fatm(4), hatm(4), and
1026 patm(4) devices has been removed. Consumers should plan a
1027 migration before the end-of-life date for FreeBSD 11.
1030 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
1031 diff has not been implemented, if those are needed a newer version of
1032 GNU diff is available via the diffutils package under the gdiff name.
1035 As of r316810 for ipfilter, keep frags is no longer assumed when
1036 keep state is specified in a rule. r316810 aligns ipfilter with
1037 documentation in man pages separating keep frags from keep state.
1038 This allows keep state to be specified without forcing keep frags
1039 and allows keep frags to be specified independently of keep state.
1040 To maintain previous behaviour, also specify keep frags with
1041 keep state (as documented in ipf.conf.5).
1044 arm64 builds now use the base system LLD 4.0.0 linker by default,
1045 instead of requiring that the aarch64-binutils port or package be
1046 installed. To continue using aarch64-binutils, set
1047 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
1050 The UDP optimization in entry 20160818 that added the sysctl
1051 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
1052 packets will no longer be treated as L3 broadcast packets.
1055 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
1056 use any explicitly assigned loopback address available in the jail
1057 instead of using the first assigned address of the jail.
1060 The ctl.ko module no longer implements the iSCSI target frontend:
1061 cfiscsi.ko does instead.
1063 If building cfiscsi.ko as a kernel module, the module can be loaded
1064 via one of the following methods:
1065 - `cfiscsi_load="YES"` in loader.conf(5).
1066 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
1067 - ctladm(8)/ctld(8), when compiled with iSCSI support
1068 (`WITH_ISCSI=yes` in src.conf(5))
1070 Please see cfiscsi(4) for more details.
1073 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
1074 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
1075 same source (previously, the dependency of mmcsd.ko on mmc.ko was
1076 missing, but mmcsd.ko now will refuse to load if it is incompatible
1080 The syntax of ipfw(8) named states was changed to avoid ambiguity.
1081 If you have used named states in the firewall rules, you need to modify
1082 them after installworld and before rebooting. Now named states must
1083 be prefixed with colon.
1086 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
1087 removed as the userland we provide cannot use them. The KMS version
1088 (sys/dev/drm2) supports the same hardware.
1091 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
1092 Please see the 20141231 entry below for information about prerequisites
1093 and upgrading, if you are not already using clang 3.5.0 or higher.
1096 The code that provides support for ZFS .zfs/ directory functionality
1097 has been reimplemented. It's not possible now to create a snapshot
1098 by mkdir under .zfs/snapshot/. That should be the only user visible
1102 EISA bus support has been removed. The WITH_EISA option is no longer
1106 MCA bus support has been removed.
1109 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
1110 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
1113 The EM_MULTIQUEUE kernel configuration option is deprecated now that
1114 the em(4) driver conforms to iflib specifications.
1117 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
1118 IFLIB. If you have a custom kernel configuration that excludes em(4)
1119 but you use igb(4), you need to re-add em(4) to your custom
1123 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
1124 Please see the 20141231 entry below for information about prerequisites
1125 and upgrading, if you are not already using clang 3.5.0 or higher.
1128 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
1129 Please see the 20141231 entry below for information about prerequisites
1130 and upgrading, if you are not already using clang 3.5.0 or higher.
1133 The layout of the pmap structure has changed for powerpc to put the pmap
1134 statistics at the front for all CPU variations. libkvm(3) and all tools
1135 that link against it need to be recompiled.
1138 isl(4) and cyapa(4) drivers now require a new driver,
1139 chromebook_platform(4), to work properly on Chromebook-class hardware.
1140 On other types of hardware the drivers may need to be configured using
1141 device hints. Please see the corresponding manual pages for details.
1144 The urtwn(4) driver was merged into rtwn(4) and now consists of
1145 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
1147 Also, firmware for RTL8188CE was renamed due to possible name
1148 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
1151 GNU rcs has been removed from base. It is available as packages:
1152 - rcs: Latest GPLv3 GNU rcs version.
1153 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
1157 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
1158 modules now requires that the kernel configuration contain the
1159 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
1162 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
1163 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
1166 Relocatable object files with the extension of .So have been renamed
1167 to use an extension of .pico instead. The purpose of this change is
1168 to avoid a name clash with shared libraries on case-insensitive file
1169 systems. On those file systems, foo.So is the same file as foo.so.
1172 GNU rcs has been turned off by default. It can (temporarily) be built
1173 again by adding WITH_RCS knob in src.conf.
1174 Otherwise, GNU rcs is available from packages:
1175 - rcs: Latest GPLv3 GNU rcs version.
1176 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
1179 The backup_uses_rcs functionality has been removed from rc.subr.
1182 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
1183 two separate components, QUEUE_MACRO_DEBUG_TRACE and
1184 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
1185 QUEUE_MACRO_DEBUG behavior.
1188 r304787 changed some ioctl interfaces between the iSCSI userspace
1189 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1190 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1194 The UDP receive code has been updated to only treat incoming UDP
1195 packets that were addressed to an L2 broadcast address as L3
1196 broadcast packets. It is not expected that this will affect any
1197 standards-conforming UDP application. The new behaviour can be
1198 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1202 Remove the openbsd_poll system call.
1203 __FreeBSD_version has been bumped because of this.
1206 The stable/11 branch has been created from head@r302406.
1209 The libc stub for the pipe(2) system call has been replaced with
1210 a wrapper that calls the pipe2(2) system call and the pipe(2)
1211 system call is now only implemented by the kernels that include
1212 "options COMPAT_FREEBSD10" in their config file (this is the
1213 default). Users should ensure that this option is enabled in
1214 their kernel or upgrade userspace to r302092 before upgrading their
1218 CAM will now strip leading spaces from SCSI disks' serial numbers.
1219 This will affect users who create UFS filesystems on SCSI disks using
1220 those disk's diskid device nodes. For example, if /etc/fstab
1221 previously contained a line like
1222 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
1223 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
1224 transforms like gmirror may also be affected. ZFS users should
1228 The bitstring(3) API has been updated with new functionality and
1229 improved performance. But it is binary-incompatible with the old API.
1230 Objects built with the new headers may not be linked against objects
1231 built with the old headers.
1234 The brk and sbrk functions have been removed from libc on arm64.
1235 Binutils from ports has been updated to not link to these
1236 functions and should be updated to the latest version before
1237 installing a new libc.
1240 The armv6 port now defaults to hard float ABI. Limited support
1241 for running both hardfloat and soft float on the same system
1242 is available using the libraries installed with -DWITH_LIBSOFT.
1243 This has only been tested as an upgrade path for installworld
1244 and packages may fail or need manual intervention to run. New
1245 packages will be needed.
1247 To update an existing self-hosted armv6hf system, you must add
1248 TARGET_ARCH=armv6 on the make command line for both the build
1249 and the install steps.
1252 Kernel modules compiled outside of a kernel build now default to
1253 installing to /boot/modules instead of /boot/kernel. Many kernel
1254 modules built this way (such as those in ports) already overrode
1255 KMODDIR explicitly to install into /boot/modules. However,
1256 manually building and installing a module from /sys/modules will
1257 now install to /boot/modules instead of /boot/kernel.
1260 The CAM I/O scheduler has been committed to the kernel. There should be
1261 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1262 list of known rogues that claim support for this but actually corrupt
1263 data is believed to be complete, be on the lookout for data
1264 corruption. The known rogue list is believed to be complete:
1266 o Crucial MX100, M550 drives with MU01 firmware.
1267 o Micron M510 and M550 drives with MU01 firmware.
1268 o Micron M500 prior to MU07 firmware
1269 o Samsung 830, 840, and 850 all firmwares
1270 o FCCT M500 all firmwares
1272 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1273 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1274 updated firmware. Black listed drives will work correctly because these
1275 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1276 this list is the same as found in Linux, it's believed there are no
1277 other rogues in the market place. All other models from the above
1280 To be safe, if you are at all concerned, you can quirk each of your
1281 drives to prevent NCQ from being sent by setting:
1282 kern.cam.ada.X.quirks="0x2"
1283 in loader.conf. If the drive requires the 4k sector quirk, set the
1284 quirks entry to 0x3.
1287 The FAST_DEPEND build option has been removed and its functionality is
1288 now the one true way. The old mkdep(1) style of 'make depend' has
1289 been removed. See 20160311 for further details.
1292 Resource range types have grown from unsigned long to uintmax_t. All
1293 drivers, and anything using libdevinfo, need to be recompiled.
1296 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1297 builds. It no longer runs mkdep(1) during 'make depend', and the
1298 'make depend' stage can safely be skipped now as it is auto ran
1299 when building 'make all' and will generate all SRCS and DPSRCS before
1300 building anything else. Dependencies are gathered at compile time with
1301 -MF flags kept in separate .depend files per object file. Users should
1302 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1303 stale .depend files.
1306 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1307 kernel modules. Therefore, if you load any kernel modules at boot time,
1308 please install the boot loaders after you install the kernel, but before
1312 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1313 make installkernel KERNCONF=YOUR_KERNEL_HERE
1314 make -C sys/boot install
1315 <reboot in single user>
1317 Then follow the usual steps, described in the General Notes section,
1321 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1322 see the 20141231 entry below for information about prerequisites and
1323 upgrading, if you are not already using clang 3.5.0 or higher.
1326 The AIO subsystem is now a standard part of the kernel. The
1327 VFS_AIO kernel option and aio.ko kernel module have been removed.
1328 Due to stability concerns, asynchronous I/O requests are only
1329 permitted on sockets and raw disks by default. To enable
1330 asynchronous I/O requests on all file types, set the
1331 vfs.aio.enable_unsafe sysctl to a non-zero value.
1334 The ELF object manipulation tool objcopy is now provided by the
1335 ELF Tool Chain project rather than by GNU binutils. It should be a
1336 drop-in replacement, with the addition of arm64 support. The
1337 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1338 to obtain the GNU version if necessary.
1341 Building ZFS pools on top of zvols is prohibited by default. That
1342 feature has never worked safely; it's always been prone to deadlocks.
1343 Using a zvol as the backing store for a VM guest's virtual disk will
1344 still work, even if the guest is using ZFS. Legacy behavior can be
1345 restored by setting vfs.zfs.vol.recursive=1.
1348 The NONE and HPN patches has been removed from OpenSSH. They are
1349 still available in the security/openssh-portable port.
1352 With the addition of ypldap(8), a new _ypldap user is now required
1353 during installworld. "mergemaster -p" can be used to add the user
1354 prior to installworld, as documented in the handbook.
1357 The tftp loader (pxeboot) now uses the option root-path directive. As a
1358 consequence it no longer looks for a pxeboot.4th file on the tftp
1359 server. Instead it uses the regular /boot infrastructure as with the
1363 The code to start recording plug and play data into the modules has
1364 been committed. While the old tools will properly build a new kernel,
1365 a number of warnings about "unknown metadata record 4" will be produced
1366 for an older kldxref. To avoid such warnings, make sure to rebuild
1367 the kernel toolchain (or world). Make sure that you have r292078 or
1368 later when trying to build 292077 or later before rebuilding.
1371 Debug data files are now built by default with 'make buildworld' and
1372 installed with 'make installworld'. This facilitates debugging but
1373 requires more disk space both during the build and for the installed
1374 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1378 r291527 changed the internal interface between the nfsd.ko and
1379 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1380 __FreeBSD_version has been bumped because of this.
1383 Add support for unicode collation strings leads to a change of
1384 order of files listed by ls(1) for example. To get back to the old
1385 behaviour, set LC_COLLATE environment variable to "C".
1387 Databases administrators will need to reindex their databases given
1388 collation results will be different.
1390 Due to a bug in install(1) it is recommended to remove the ancient
1391 locales before running make installworld.
1393 rm -rf /usr/share/locale/*
1396 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1397 libcrypto.so.7 or libssl.so.7 must be recompiled.
1400 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1401 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1402 should be replaced with isp_2400 and isp_2500 modules respectively.
1405 The build previously allowed using 'make -n' to not recurse into
1406 sub-directories while showing what commands would be executed, and
1407 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1408 and 'make -N' will not.
1411 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1412 and etcupdate will now use this file. A custom sendmail.cf is now
1413 updated via this mechanism rather than via installworld. If you had
1414 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1415 want to remove the exclusion or change it to "always install".
1416 /etc/mail/sendmail.cf is now managed the same way regardless of
1417 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1418 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1421 Compatibility shims for legacy ATA device names have been removed.
1422 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1423 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1424 environment variables, /dev/ad* and /dev/ar* symbolic links.
1427 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1428 Please see the 20141231 entry below for information about prerequisites
1429 and upgrading, if you are not already using clang 3.5.0 or higher.
1432 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1433 and renamed from .symbols to .debug. This reduces the size requirements
1434 on the boot partition or file system and provides consistency with
1435 userland debug files.
1437 When using the supported kernel installation method the
1438 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1439 as is done with /boot/kernel.
1441 Developers wishing to maintain the historical behavior of installing
1442 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1445 The wireless drivers had undergone changes that remove the 'parent
1446 interface' from the ifconfig -l output. The rc.d network scripts
1447 used to check presence of a parent interface in the list, so old
1448 scripts would fail to start wireless networking. Thus, etcupdate(3)
1449 or mergemaster(8) run is required after kernel update, to update your
1450 rc.d scripts in /etc.
1453 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1454 These configurations are now automatically interpreted as
1455 'scrub fragment reassemble'.
1458 Kernel-loadable modules for the random(4) device are back. To use
1459 them, the kernel must have
1462 options RANDOM_LOADABLE
1464 kldload(8) can then be used to load random_fortuna.ko
1465 or random_yarrow.ko. Please note that due to the indirect
1466 function calls that the loadable modules need to provide,
1467 the build-in variants will be slightly more efficient.
1469 The random(4) kernel option RANDOM_DUMMY has been retired due to
1470 unpopularity. It was not all that useful anyway.
1473 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1474 Control over building the ELF Tool Chain tools is now provided by
1475 the WITHOUT_TOOLCHAIN knob.
1478 The polarity of Pulse Per Second (PPS) capture events with the
1479 uart(4) driver has been corrected. Prior to this change the PPS
1480 "assert" event corresponded to the trailing edge of a positive PPS
1481 pulse and the "clear" event was the leading edge of the next pulse.
1483 As the width of a PPS pulse in a typical GPS receiver is on the
1484 order of 1 millisecond, most users will not notice any significant
1485 difference with this change.
1487 Anyone who has compensated for the historical polarity reversal by
1488 configuring a negative offset equal to the pulse width will need to
1489 remove that workaround.
1492 The default group assigned to /dev/dri entries has been changed
1493 from 'wheel' to 'video' with the id of '44'. If you want to have
1494 access to the dri devices please add yourself to the video group
1497 # pw groupmod video -m $USER
1500 The menu.rc and loader.rc files will now be replaced during
1501 upgrades. Please migrate local changes to menu.rc.local and
1502 loader.rc.local instead.
1505 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1506 strings and strip have been removed. The src.conf(5) knob
1507 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1510 As ZFS requires more kernel stack pages than is the default on some
1511 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1512 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1514 Please consider using 'options KSTACK_PAGES=X' where X is greater
1515 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1518 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1519 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1520 default, i.e., they will not contain "::". For example, instead
1521 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1522 to have a more specific match, such as different map entries for
1523 IPv6:0:0 vs IPv6:0. This change requires that configuration
1524 data (including maps, files, classes, custom ruleset, etc.) must
1525 use the same format, so make certain such configuration data is
1526 upgrading. As a very simple check search for patterns like
1527 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1528 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1529 the cf option UseCompressedIPv6Addresses.
1532 The default kernel entropy-processing algorithm is now
1533 Fortuna, replacing Yarrow.
1535 Assuming you have 'device random' in your kernel config
1536 file, the configurations allow a kernel option to override
1537 this default. You may choose *ONE* of:
1539 options RANDOM_YARROW # Legacy /dev/random algorithm.
1540 options RANDOM_DUMMY # Blocking-only driver.
1542 If you have neither, you get Fortuna. For most people,
1543 read no further, Fortuna will give a /dev/random that works
1544 like it always used to, and the difference will be irrelevant.
1546 If you remove 'device random', you get *NO* kernel-processed
1547 entropy at all. This may be acceptable to folks building
1548 embedded systems, but has complications. Carry on reading,
1549 and it is assumed you know what you need.
1551 *PLEASE* read random(4) and random(9) if you are in the
1552 habit of tweaking kernel configs, and/or if you are a member
1553 of the embedded community, wanting specific and not-usual
1554 behaviour from your security subsystems.
1556 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1557 random', you will NOT have a functioning /dev/random, and
1558 many cryptographic features will not work, including SSH.
1559 You may also find strange behaviour from the random(3) set
1560 of library functions, in particular sranddev(3), srandomdev(3)
1561 and arc4random(3). The reason for this is that the KERN_ARND
1562 sysctl only returns entropy if it thinks it has some to
1563 share, and with RANDOM_DUMMY or no 'device random' this
1567 An additional fix for the issue described in the 20150614 sendmail
1568 entry below has been committed in revision 284717.
1571 FreeBSD's old make (fmake) has been removed from the system. It is
1572 available as the devel/fmake port or via pkg install fmake.
1575 The fix for the issue described in the 20150614 sendmail entry
1576 below has been committed in revision 284436. The work
1577 around described in that entry is no longer needed unless the
1578 default setting is overridden by a confDH_PARAMETERS configuration
1579 setting of '5' or pointing to a 512 bit DH parameter file.
1582 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1583 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1584 and devel/kyua to version 0.20+ and adjust any calling code to work
1585 with Kyuafile and kyua.
1588 The import of openssl to address the FreeBSD-SA-15:10.openssl
1589 security advisory includes a change which rejects handshakes
1590 with DH parameters below 768 bits. sendmail releases prior
1591 to 8.15.2 (not yet released), defaulted to a 512 bit
1592 DH parameter setting for client connections. To work around
1593 this interoperability, sendmail can be configured to use a
1594 2048 bit DH parameter by:
1596 1. Edit /etc/mail/`hostname`.mc
1597 2. If a setting for confDH_PARAMETERS does not exist or
1598 exists and is set to a string beginning with '5',
1599 replace it with '2'.
1600 3. If a setting for confDH_PARAMETERS exists and is set to
1601 a file path, create a new file with:
1602 openssl dhparam -out /path/to/file 2048
1603 4. Rebuild the .cf file:
1604 cd /etc/mail/; make; make install
1605 5. Restart sendmail:
1606 cd /etc/mail/; make restart
1608 A sendmail patch is coming, at which time this file will be
1612 Generation of legacy formatted entries have been disabled by default
1613 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1614 entries were converted to use the new format by default when the new,
1615 machine independent format have been added and supported since FreeBSD
1618 Please see the pwd_mkdb(8) manual page for further details.
1621 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1622 20141231 entry below for information about prerequisites and upgrading,
1623 if you are not already using 3.5.0 or higher.
1626 TI platform code switched to using vendor DTS files and this update
1627 may break existing systems running on Beaglebone, Beaglebone Black,
1630 - dtb files should be regenerated/reinstalled. Filenames are the
1631 same but content is different now
1632 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1633 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1634 addressing scheme is now pin 25 on /dev/gpioc3.
1635 - Pandaboard: /etc/ttys should be updated, serial console device is
1636 now /dev/ttyu2, not /dev/ttyu0
1639 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1640 If you need the GNU extension from groff soelim(1), install groff
1641 from package: pkg install groff, or via ports: textproc/groff.
1644 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1645 defined in symlink(7); previously symlinks were silently ignored.
1648 The const qualifier has been removed from iconv(3) to comply with
1649 POSIX. The ports tree is aware of this from r384038 onwards.
1652 Libraries specified by LIBADD in Makefiles must have a corresponding
1653 DPADD_<lib> variable to ensure correct dependencies. This is now
1654 enforced in src.libnames.mk.
1657 From legacy ata(4) driver was removed support for SATA controllers
1658 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1659 Kernel modules ataahci and ataadaptec were removed completely,
1660 replaced by ahci and mvs modules respectively.
1663 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1664 the 20141231 entry below for information about prerequisites and
1665 upgrading, if you are not already using 3.5.0 or higher.
1668 The 32-bit PowerPC kernel has been changed to a position-independent
1669 executable. This can only be booted with a version of loader(8)
1670 newer than January 31, 2015, so make sure to update both world and
1671 kernel before rebooting.
1674 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1675 but before r278950, the RNG was not seeded properly. Immediately
1676 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1677 ssh keys or openssl keys) that were generated w/ a kernel from that
1678 range. This does not affect programs that directly used /dev/random
1679 or /dev/urandom. All userland uses of arc4random(3) are affected.
1682 The autofs(4) ABI was changed in order to restore binary compatibility
1683 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1684 with the new kernel.
1687 The powerpc64 kernel has been changed to a position-independent
1688 executable. This can only be booted with a new version of loader(8),
1689 so make sure to update both world and kernel before rebooting.
1692 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1693 only release, no new features have been added. Please see the 20141231
1694 entry below for information about prerequisites and upgrading, if you
1695 are not already using 3.5.0.
1698 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1699 taken from the ELF Tool Chain project rather than GNU binutils. They
1700 should be drop-in replacements, with the addition of arm64 support.
1701 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1702 binutils tools, if necessary. See 20150805 for updated information.
1705 The default Unbound configuration now enables remote control
1706 using a local socket. Users who have already enabled the
1707 local_unbound service should regenerate their configuration
1708 by running "service local_unbound setup" as root.
1711 The GNU texinfo and GNU info pages have been removed.
1712 To be able to view GNU info pages please install texinfo from ports.
1715 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1717 As of this release, a prerequisite for building clang, llvm and lldb is
1718 a C++11 capable compiler and C++11 standard library. This means that to
1719 be able to successfully build the cross-tools stage of buildworld, with
1720 clang as the bootstrap compiler, your system compiler or cross compiler
1721 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1722 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1725 On any standard FreeBSD 10.x or 11.x installation, where clang and
1726 libc++ are on by default (that is, on x86 or arm), this should work out
1729 On 9.x installations where clang is enabled by default, e.g. on x86 and
1730 powerpc, libc++ will not be enabled by default, so libc++ should be
1731 built (with clang) and installed first. If both clang and libc++ are
1732 missing, build clang first, then use it to build libc++.
1734 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1735 the instructions for 9.x above.
1737 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1738 default, and do not build clang.
1740 Many embedded systems are resource constrained, and will not be able to
1741 build clang in a reasonable time, or in some cases at all. In those
1742 cases, cross building bootable systems on amd64 is a workaround.
1744 This new version of clang introduces a number of new warnings, of which
1745 the following are most likely to appear:
1749 This warns in two cases, for both C and C++:
1750 * When the code is trying to take the absolute value of an unsigned
1751 quantity, which is effectively a no-op, and almost never what was
1752 intended. The code should be fixed, if at all possible. If you are
1753 sure that the unsigned quantity can be safely cast to signed, without
1754 loss of information or undefined behavior, you can add an explicit
1755 cast, or disable the warning.
1757 * When the code is trying to take an absolute value, but the called
1758 abs() variant is for the wrong type, which can lead to truncation.
1759 If you want to disable the warning instead of fixing the code, please
1760 make sure that truncation will not occur, or it might lead to unwanted
1763 -Wtautological-undefined-compare and
1764 -Wundefined-bool-conversion
1766 These warn when C++ code is trying to compare 'this' against NULL, while
1767 'this' should never be NULL in well-defined C++ code. However, there is
1768 some legacy (pre C++11) code out there, which actively abuses this
1769 feature, which was less strictly defined in previous C++ versions.
1771 Squid and openjdk do this, for example. The warning can be turned off
1772 for C++98 and earlier, but compiling the code in C++11 mode might result
1773 in unexpected behavior; for example, the parts of the program that are
1774 unreachable could be optimized away.
1777 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1778 kernel sources have been removed. The .h files remain, since some
1779 utilities include them. This will need to be fixed later.
1780 If "mount -t oldnfs ..." is attempted, it will fail.
1781 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1782 the utilities will report errors.
1785 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1786 directories to top level SUBDIR variable when their parent
1787 directory is included in LOCAL_DIRS. Users with build systems with
1788 such hierarchies and without SUBDIR entries in the parent
1789 directory Makefiles should add them or add the directories to
1793 faith(4) and faithd(8) have been removed from the base system. Faith
1794 has been obsolete for a very long time.
1797 vt(4), the new console driver, is enabled by default. It brings
1798 support for Unicode and double-width characters, as well as
1799 support for UEFI and integration with the KMS kernel video
1802 You may need to update your console settings in /etc/rc.conf,
1803 most probably the keymap. During boot, /etc/rc.d/syscons will
1804 indicate what you need to do.
1806 vt(4) still has issues and lacks some features compared to
1807 syscons(4). See the wiki for up-to-date information:
1808 https://wiki.freebsd.org/Newcons
1810 If you want to keep using syscons(4), you can do so by adding
1811 the following line to /boot/loader.conf:
1815 pjdfstest has been integrated into kyua as an opt-in test suite.
1816 Please see share/doc/pjdfstest/README for more details on how to
1820 gperf has been removed from the base system for architectures
1821 that use clang. Ports that require gperf will obtain it from the
1825 pjdfstest has been moved from tools/regression/pjdfstest to
1829 At svn r271982, The default linux compat kernel ABI has been adjusted
1830 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1831 update. If you wish to continue using the linux-f10 compat ports,
1832 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1833 encouraged to update their linux-compat packages to linux-c6 during
1834 their next update cycle.
1837 The ofwfb driver, used to provide a graphics console on PowerPC when
1838 using vt(4), no longer allows mmap() of all physical memory. This
1839 will prevent Xorg on PowerPC with some ATI graphics cards from
1840 initializing properly unless x11-servers/xorg-server is updated to
1844 The xdev targets have been converted to using TARGET and
1845 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1848 The default unbound configuration has been modified to address
1849 issues with reverse lookups on networks that use private
1850 address ranges. If you use the local_unbound service, run
1851 "service local_unbound setup" as root to regenerate your
1852 configuration, then "service local_unbound reload" to load the
1856 The GNU texinfo and GNU info pages are not built and installed
1857 anymore, WITH_INFO knob has been added to allow to built and install
1859 UPDATE: see 20150102 entry on texinfo's removal
1862 The GNU readline library is now an INTERNALLIB - that is, it is
1863 statically linked into consumers (GDB and variants) in the base
1864 system, and the shared library is no longer installed. The
1865 devel/readline port is available for third party software that
1869 The Itanium architecture (ia64) has been removed from the list of
1870 known architectures. This is the first step in the removal of the
1874 Commit r268115 has added NFSv4.1 server support, merged from
1875 projects/nfsv4.1-server. Since this includes changes to the
1876 internal interfaces between the NFS related modules, a full
1877 build of the kernel and modules will be necessary.
1878 __FreeBSD_version has been bumped.
1881 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1882 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1883 which differs from the behaviour controlled by this knob.)
1886 Maximal length of the serial number in CTL was increased from 16 to
1887 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1888 and ctld, need to be rebuilt to work with a new kernel.
1891 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1892 1 respectively to match the upstream numbers. They were out of
1893 sync because, when they were originally added to FreeBSD, the
1894 upstream versions were not respected. These libraries are private
1895 and not yet built by default, so renumbering them should be a
1896 non-issue. However, unclean source trees will yield broken test
1897 programs once the operator executes "make delete-old-libs" after a
1898 "make installworld".
1900 Additionally, the atf-sh binary was made private by moving it into
1901 /usr/libexec/. Already-built shell test programs will keep the
1902 path to the old binary so they will break after "make delete-old"
1905 If you are using WITH_TESTS=yes (not the default), wipe the object
1906 tree and rebuild from scratch to prevent spurious test failures.
1907 This is only needed once: the misnumbered libraries and misplaced
1908 binaries have been added to OptionalObsoleteFiles.inc so they will
1909 be removed during a clean upgrade.
1912 Clang and llvm have been upgraded to 3.4.1 release.
1915 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1916 be removed to avoid issues in the future (and has been added to
1920 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1921 past, it affected all builds that used the bsd.*.mk files. The old
1922 behavior was a bug, but people may have relied upon it. To get this
1923 behavior back, you can .include /etc/src.conf from /etc/make.conf
1924 (which is still global and isn't changed). This also changes the
1925 behavior of incremental builds inside the tree of individual
1926 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1927 Although this has survived make universe and some upgrade scenarios,
1928 other upgrade scenarios may have broken. At least one form of
1929 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1930 as well... In cases where MAKESYSPATH isn't working with this
1931 setting, you'll need to set it to the full path to your tree.
1933 One side effect of all this cleaning up is that bsd.compiler.mk
1934 is no longer implicitly included by bsd.own.mk. If you wish to
1935 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1939 The lindev device has been removed since /dev/full has been made a
1940 standard device. __FreeBSD_version has been bumped.
1943 The knob WITHOUT_VI was added to the base system, which controls
1944 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1945 in order to reorder files share/termcap and didn't build ex(1) as a
1946 build tool, so building/installing with WITH_VI is highly advised for
1947 build hosts for older releases.
1949 This issue has been fixed in stable/9 and stable/10 in r277022 and
1950 r276991, respectively.
1953 The YES_HESIOD knob has been removed. It has been obsolete for
1954 a decade. Please move to using WITH_HESIOD instead or your builds
1955 will silently lack HESIOD.
1958 The uart(4) driver has been changed with respect to its handling
1959 of the low-level console. Previously the uart(4) driver prevented
1960 any process from changing the baudrate or the CLOCAL and HUPCL
1961 control flags. By removing the restrictions, operators can make
1962 changes to the serial console port without having to reboot.
1963 However, when getty(8) is started on the serial device that is
1964 associated with the low-level console, a misconfigured terminal
1965 line in /etc/ttys will now have a real impact.
1966 Before upgrading the kernel, make sure that /etc/ttys has the
1967 serial console device configured as 3wire without baudrate to
1968 preserve the previous behaviour. E.g:
1969 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1972 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1973 to improve performance. To re-enable it, if needed, run rpcbind
1974 with command line option -W.
1977 Switched back to the GPL dtc compiler due to updates in the upstream
1978 dts files not being supported by the BSDL dtc compiler. You will need
1979 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1980 may result while building dtb files during a kernel build if you fail
1981 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1984 Clang and llvm have been upgraded to 3.4 release.
1987 The nve(4) driver has been removed. Please use the nfe(4) driver
1988 for NVIDIA nForce MCP Ethernet adapters instead.
1991 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1992 This could cause certain C++ applications using shared libraries built
1993 against the previous version of libc++ to crash. The incompatibility
1994 has now been fixed, but any C++ applications or shared libraries built
1995 between r261283 and r261801 should be recompiled.
1998 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1999 capability mode support. Please note that enabling the feature in
2000 kernel is still highly recommended.
2003 OpenSSH is now built with sandbox support, and will use sandbox as
2004 the default privilege separation method. This requires Capsicum
2005 capability mode support in kernel.
2008 The libelf and libdwarf libraries have been updated to newer
2009 versions from upstream. Shared library version numbers for
2010 these two libraries were bumped. Any ports or binaries
2011 requiring these two libraries should be recompiled.
2012 __FreeBSD_version is bumped to 1100006.
2015 If a Makefile in a tests/ directory was auto-generating a Kyuafile
2016 instead of providing an explicit one, this would prevent such
2017 Makefile from providing its own Kyuafile in the future during
2018 NO_CLEAN builds. This has been fixed in the Makefiles but manual
2019 intervention is needed to clean an objdir if you use NO_CLEAN:
2020 # find /usr/obj -name Kyuafile | xargs rm -f
2023 The behavior of gss_pseudo_random() for the krb5 mechanism
2024 has changed, for applications requesting a longer random string
2025 than produced by the underlying enctype's pseudo-random() function.
2026 In particular, the random string produced from a session key of
2027 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
2028 be different at the 17th octet and later, after this change.
2029 The counter used in the PRF+ construction is now encoded as a
2030 big-endian integer in accordance with RFC 4402.
2031 __FreeBSD_version is bumped to 1100004.
2034 The WITHOUT_ATF build knob has been removed and its functionality
2035 has been subsumed into the more generic WITHOUT_TESTS. If you were
2036 using the former to disable the build of the ATF libraries, you
2037 should change your settings to use the latter.
2040 The default version of mtree is nmtree which is obtained from
2041 NetBSD. The output is generally the same, but may vary
2042 slightly. If you found you need identical output adding
2043 "-F freebsd9" to the command line should do the trick. For the
2044 time being, the old mtree is available as fmtree.
2047 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
2048 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
2049 1.1.4_8 and verify bsdyml not linked in, before running "make
2051 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
2053 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
2056 The stable/10 branch has been created in subversion from head
2063 Sometimes, obscure build problems are the result of environment
2064 poisoning. This can happen because the make utility reads its
2065 environment when searching for values for global variables. To run
2066 your build attempts in an "environmental clean room", prefix all make
2067 commands with 'env -i '. See the env(1) manual page for more details.
2068 Occasionally a build failure will occur with "make -j" due to a race
2069 condition. If this happens try building again without -j, and please
2070 report a bug if it happens consistently.
2072 When upgrading from one major version to another it is generally best to
2073 upgrade to the latest code in the currently installed branch first, then
2074 do an upgrade to the new branch. This is the best-tested upgrade path,
2075 and has the highest probability of being successful. Please try this
2076 approach if you encounter problems with a major version upgrade. Since
2077 the stable 4.x branch point, one has generally been able to upgrade from
2078 anywhere in the most recent stable branch to head / current (or even the
2079 last couple of stable branches). See the top of this file when there's
2082 The update process will emit an error on an attempt to perform a build
2083 or install from a FreeBSD version below the earliest supported version.
2084 When updating from an older version the update should be performed one
2085 major release at a time, including running `make delete-old` at each
2088 When upgrading a live system, having a root shell around before
2089 installing anything can help undo problems. Not having a root shell
2090 around can lead to problems if pam has changed too much from your
2091 starting point to allow continued authentication after the upgrade.
2093 This file should be read as a log of events. When a later event changes
2094 information of a prior event, the prior event should not be deleted.
2095 Instead, a pointer to the entry with the new information should be
2096 placed in the old entry. Readers of this file should also sanity check
2097 older entries before relying on them blindly. Authors of new entries
2098 should write them with this in mind.
2102 When upgrading the boot ZFS pool to a new version, always follow
2105 1.) recompile and reinstall the ZFS boot loader and boot block
2106 (this is part of "make buildworld" and "make installworld")
2108 2.) update the ZFS boot block on your boot drive
2110 The following example updates the ZFS boot block on the first
2111 partition (freebsd-boot) of a GPT partitioned drive ada0:
2112 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
2114 Non-boot pools do not need these updates.
2118 If you are updating from a prior version of FreeBSD (even one just
2119 a few days old), you should follow this procedure. It is the most
2120 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2122 make kernel-toolchain
2123 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2124 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2126 To test a kernel once
2127 ---------------------
2128 If you just want to boot a kernel once (because you are not sure
2129 if it works, or if you want to boot a known bad kernel to provide
2130 debugging information) run
2131 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2132 nextboot -k testkernel
2134 To rebuild everything and install it on the current system.
2135 -----------------------------------------------------------
2136 # Note: sometimes if you are running current you gotta do more than
2137 # is listed here if you are upgrading from a really old current.
2139 <make sure you have good level 0 dumps>
2141 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2142 make installkernel KERNCONF=YOUR_KERNEL_HERE
2144 <reboot in single user> [3]
2151 To cross-install current onto a separate partition
2152 --------------------------------------------------
2153 # In this approach we use a separate partition to hold
2154 # current's root, 'usr', and 'var' directories. A partition
2155 # holding "/", "/usr" and "/var" should be about 2GB in
2158 <make sure you have good level 0 dumps>
2161 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2162 <maybe newfs current's root partition>
2163 <mount current's root partition on directory ${CURRENT_ROOT}>
2164 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
2165 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2166 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2167 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2168 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2169 <reboot into current>
2170 <do a "native" rebuild/install as described in the previous section>
2171 <maybe install compatibility libraries from ports/misc/compat*>
2175 To upgrade in-place from stable to current
2176 ----------------------------------------------
2177 <make sure you have good level 0 dumps>
2179 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
2180 make installkernel KERNCONF=YOUR_KERNEL_HERE
2182 <reboot in single user> [3]
2189 Make sure that you've read the UPDATING file to understand the
2190 tweaks to various things you need. At this point in the life
2191 cycle of current, things change often and you are on your own
2192 to cope. The defaults can also change, so please read ALL of
2193 the UPDATING entries.
2195 Also, if you are tracking -current, you must be subscribed to
2196 freebsd-current@freebsd.org. Make sure that before you update
2197 your sources that you have read and understood all the recent
2198 messages there. If in doubt, please track -stable which has
2199 much fewer pitfalls.
2201 [1] If you have third party modules, such as vmware, you
2202 should disable them at this point so they don't crash your
2205 [3] From the bootblocks, boot -s, and then do
2209 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed
2210 cd src # full path to source
2211 adjkerntz -i # if CMOS is wall time
2212 Also, when doing a major release upgrade, it is required that
2213 you boot into single user mode to do the installworld.
2215 [4] Note: This step is non-optional. Failure to do this step
2216 can result in a significant reduction in the functionality of the
2217 system. Attempting to do it by hand is not recommended and those
2218 that pursue this avenue should read this file carefully, as well
2219 as the archives of freebsd-current and freebsd-hackers mailing lists
2220 for potential gotchas. The -U option is also useful to consider.
2221 See mergemaster(8) for more information.
2223 [5] Usually this step is a no-op. However, from time to time
2224 you may need to do this if you get unknown user in the following
2225 step. It never hurts to do it all the time. You may need to
2226 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2227 install) after the buildworld before this step if you last updated
2228 from current before 20130425 or from -stable before 20130430.
2230 [6] This only deletes old files and directories. Old libraries
2231 can be deleted by "make delete-old-libs", but you have to make
2232 sure that no program is using those libraries anymore.
2234 [8] The new kernel must be able to run existing binaries used by an
2235 installworld. When upgrading across major versions, the new kernel's
2236 configuration must include the correct COMPAT_FREEBSD<n> option for
2237 existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure
2238 to do so may leave you with a system that is hard to boot to recover. A
2239 GENERIC kernel will include suitable compatibility options to run
2240 binaries from older branches. Note that the ability to run binaries
2241 from unsupported branches is not guaranteed.
2243 Make sure that you merge any new devices from GENERIC since the
2244 last time you updated your kernel config file. Options also
2245 change over time, so you may need to adjust your custom kernels
2248 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2249 "?=" instead of the "=" assignment operator, so that buildworld can
2250 override the CPUTYPE if it needs to.
2252 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2253 not on the command line, or in /etc/make.conf. buildworld will
2254 warn if it is improperly defined.
2257 This file contains a list, in reverse chronological order, of major
2258 breakages in tracking -current. It is not guaranteed to be a complete
2259 list of such breakages, and only contains entries since September 23, 2011.
2260 If you need to see UPDATING entries from before that date, you will need
2261 to fetch an UPDATING file from an older FreeBSD release.
2263 Copyright information:
2265 Copyright 1998-2009 M. Warner Losh <imp@FreeBSD.org>
2267 Redistribution, publication, translation and use, with or without
2268 modification, in full or in part, in any form or format of this
2269 document are permitted without further permission from the author.
2271 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2272 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2273 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2274 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2275 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2276 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2277 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2278 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2279 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2280 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2281 POSSIBILITY OF SUCH DAMAGE.
2283 Contact Warner Losh if you have any questions about your use of