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