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 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
31 been upgraded to 10.0.1. Please see the 20141231 entry below for
32 information about prerequisites and upgrading, if you are not already
33 using clang 3.5.0 or higher.
36 closefrom(2) has been moved under COMPAT12, and replaced in libc with a
37 stub that calls close_range(2). If using a custom kernel configuration,
38 you may want to ensure that the COMPAT_FREEBSD12 option is included, as
39 a slightly older -CURRENT userland and older FreeBSD userlands may not
40 be functional without closefrom(2).
43 Upstream DTS from Linux 5.6 was merged and they now have the SID
44 and THS (Secure ID controller and THermal Sensor) node present.
45 The DTB overlays have now been removed from the tree for the H3/H5 and
46 A64 SoCs and the aw_sid and aw_thermal driver have been updated to
47 deal with upstream DTS. If you are using those overlays you need to
48 remove them from loader.conf and update the DTBs on the FAT partition.
51 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
52 been upgraded to 10.0.0. Please see the 20141231 entry below for
53 information about prerequisites and upgrading, if you are not already
54 using clang 3.5.0 or higher.
57 The amd(8) automount daemon has been removed from the source tree.
58 As of FreeBSD 10.1 autofs(5) is the preferred tool for automounting.
59 amd is still available in the sysutils/am-utils port.
62 Removed brooktree driver (bktr.4) from the tree.
65 The WITH_GPL_DTC option has been removed. The BSD-licenced device tree
66 compiler in usr.bin/dtc is used on all architectures which use dtc, and
67 the GPL dtc is available (if needed) from the sysutils/dtc port.
70 The WITHOUT_LLVM_LIBUNWIND option has been removed. LLVM's libunwind
71 is used by all supported CPU architectures.
74 GCC 4.2.1 has been removed from the tree. The WITH_GCC,
75 WITH_GCC_BOOTSTRAP, and WITH_GNUCXX options are no longer available.
76 Users who wish to build FreeBSD with GCC must use the external toolchain
80 ncurses has been updated to a newer version (6.2-20200215). Given the ABI
81 has changed, users will have to rebuild all the ports that are linked to
85 The size of struct vnet and the magic cookie have changed.
86 Users need to recompile libkvm and all modules using VIMAGE
87 together with their new kernel.
90 Defining the long deprecated NO_CTF, NO_DEBUG_FILES, NO_INSTALLLIB,
91 NO_MAN, NO_PROFILE, and NO_WARNS variables is now an error. Update
92 your Makefiles and scripts to define MK_<var>=no instead as required.
94 One exception to this is that program or library Makefiles should
95 define MAN to empty rather than setting MK_MAN=no.
98 Clang/LLVM is now the default compiler and LLD the default
102 make universe no longer uses GCC 4.2.1 on any architectures.
103 Architectures not supported by in-tree Clang/LLVM require an
104 external toolchain package.
107 GCC 4.2.1 is now not built by default, as part of the GCC 4.2.1
108 retirement plan. Specifically, the GCC, GCC_BOOTSTRAP, and GNUCXX
109 options default to off for all supported CPU architectures. As a
110 short-term transition aid they may be enabled via WITH_* options.
111 GCC 4.2.1 is expected to be removed from the tree on 2020-03-31.
114 Support for armv5 has been disconnected and is being removed. The
115 machine combination MACHINE=arm MACHINE_ARCH=arm is no longer valid.
116 You must now use a MACHINE_ARCH of armv6 or armv7. The default
117 MACHINE_ARCH for MACHINE=arm is now armv7.
120 Clang/LLVM is now the default compiler for all powerpc architectures.
121 LLD is now the default linker for powerpc64. The change for powerpc64
122 also includes a change to the ELFv2 ABI, incompatible with the existing
126 Kernel-loadable random(4) modules are no longer unloadable.
129 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
130 been upgraded to 9.0.1. Please see the 20141231 entry below for
131 information about prerequisites and upgrading, if you are not already
132 using clang 3.5.0 or higher.
135 r355677 has modified the internal interface used between the
136 NFS modules in the kernel. As such, they must all be upgraded
137 simultaneously. I will do a version bump for this.
140 The root certificates of the Mozilla CA Certificate Store have been
141 imported into the base system and can be managed with the certctl(8)
142 utility. If you have installed the security/ca_root_nss port or package
143 with the ETCSYMLINK option (the default), be advised that there may be
144 differences between those included in the port and those included in
145 base due to differences in nss branch used as well as general update
146 frequency. Note also that certctl(8) cannot manage certs in the
147 format used by the security/ca_root_nss port.
150 The amd(8) automount daemon has been disabled by default, and will be
151 removed in the future. As of FreeBSD 10.1 the autofs(5) is available
155 The nctgpio and wbwd drivers have been moved to the superio bus.
156 If you have one of these drivers in a kernel configuration, then
157 you should add device superio to it. If you use one of these drivers
158 as a module and you compile a custom set of modules, then you should
159 add superio to the set.
162 KPIs for network drivers to access interface addresses have changed.
163 Users need to recompile NIC driver modules together with kernel.
166 The net.link.tap.user_open sysctl no longer prevents user opening of
167 already created /dev/tapNN devices. Access is still controlled by
168 node permissions, just like tun devices. The net.link.tap.user_open
169 sysctl is now used only to allow users to perform devfs cloning of
170 tap devices, and the subsequent open may not succeed if the user is not
171 in the appropriate group. This sysctl may be deprecated/removed
172 completely in the future.
175 mips, powerpc, and sparc64 are no longer built as part of
176 universe / tinderbox unless MAKE_OBSOLETE_GCC is defined. If
177 not defined, mips, powerpc, and sparc64 builds will look for
178 the xtoolchain binaries and if installed use them for universe
179 builds. As llvm 9.0 becomes vetted for these architectures, they
180 will be removed from the list.
183 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
184 been upgraded to 9.0.0. Please see the 20141231 entry below for
185 information about prerequisites and upgrading, if you are not already
186 using clang 3.5.0 or higher.
189 The hpt27xx, hptmv, hptnr, and hptrr drivers have been removed from
190 GENERIC. They are available as modules and can be loaded by adding
191 to /boot/loader.conf hpt27xx_load="YES", hptmv_load="YES",
192 hptnr_load="YES", or hptrr_load="YES", respectively.
195 ntpd no longer by default locks its pages in memory, allowing them
196 to be paged out by the kernel. Use rlimit memlock to restore
197 historic BSD behaviour. For example, add "rlimit memlock 32"
198 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
201 Several of ping6's options have been renamed for better consistency
202 with ping. If you use any of -ARWXaghmrtwx, you must update your
203 scripts. See ping6(8) for details.
206 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
207 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
208 been removed from mount_fusefs(8). You can safely remove them from
209 your scripts, because they had no effect.
211 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
212 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
213 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
214 sysctls have been removed. If you felt the need to set any of them to
215 a non-default value, please tell asomers@FreeBSD.org why.
218 Default permissions on the /var/account/acct file (and copies of it
219 rotated by periodic daily scripts) are changed from 0644 to 0640
220 because the file contains sensitive information that should not be
221 world-readable. If the /var/account directory must be created by
222 rc.d/accounting, the mode used is now 0750. Admins who use the
223 accounting feature are encouraged to change the mode of an existing
224 /var/account directory to 0750 or 0700.
227 Entropy collection and the /dev/random device are no longer optional
228 components. The "device random" option has been removed.
229 Implementations of distilling algorithms can still be made loadable
230 with "options RANDOM_LOADABLE" (e.g., random_fortuna.ko).
233 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
234 been upgraded to 8.0.1. Please see the 20141231 entry below for
235 information about prerequisites and upgrading, if you are not already
236 using clang 3.5.0 or higher.
239 A fix was applied to i386 kernel modules to avoid panics with
240 dpcpu or vnet. Users need to recompile i386 kernel modules
241 having pcpu or vnet sections or they will refuse to load.
244 User-wired pages now have their own counter,
245 vm.stats.vm.v_user_wire_count. The vm.max_wired sysctl was renamed
246 to vm.max_user_wired and changed from an unsigned int to an unsigned
247 long. bhyve VMs wired with the -S are now subject to the user
248 wiring limit; the vm.max_user_wired sysctl may need to be tuned to
249 avoid running into the limit.
252 The IPSEC option has been removed from GENERIC. Users requiring
253 ipsec(4) must now load the ipsec(4) kernel module.
256 The tap(4) driver has been folded into tun(4), and the module has been
257 renamed to tuntap. You should update any kld_list="if_tap" or
258 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
259 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
260 module instead, and "device tap" or "device tun" entries in kernel
261 config files to select the tuntap device instead.
264 The following knobs have been added related to tradeoffs between
265 safe use of the random device and availability in the absence of
268 kern.random.initial_seeding.bypass_before_seeding: tunable; set
269 non-zero to bypass the random device prior to seeding, or zero to
270 block random requests until the random device is initially seeded.
271 For now, set to 1 (unsafe) by default to restore pre-r346250 boot
272 availability properties.
274 kern.random.initial_seeding.read_random_bypassed_before_seeding:
275 read-only diagnostic sysctl that is set when bypass is enabled and
276 read_random(9) is bypassed, to enable programmatic handling of this
277 initial condition, if desired.
279 kern.random.initial_seeding.arc4random_bypassed_before_seeding:
280 Similar to the above, but for for arc4random(9) initial seeding.
282 kern.random.initial_seeding.disable_bypass_warnings: tunable; set
283 non-zero to disable warnings in dmesg when the same conditions are
284 met as for the diagnostic sysctls above. Defaults to zero, i.e.,
285 produce warnings in dmesg when the conditions are met.
288 The loadable random module KPI has changed; the random_infra_init()
289 routine now requires a 3rd function pointer for a bool (*)(void)
290 method that returns true if the random device is seeded (and
291 therefore unblocked).
294 r345895 reverts r320698. This implies that an nfsuserd(8) daemon
295 built from head sources between r320757 (July 6, 2017) and
296 r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
297 is added to the command line.
298 nfsuserd daemons built from head sources that are post-r338192 are
299 not affected and should continue to work.
302 The fuse(4) module has been renamed to fusefs(4) for consistency with
303 other filesystems. You should update any kld_load="fuse" entries in
304 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
305 "options FUSE" entries in kernel config files.
308 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
309 8.0.0. Please see the 20141231 entry below for information about
310 prerequisites and upgrading, if you are not already using clang 3.5.0
314 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
315 compiled into your custom kernel, add 'device xz' statement to the
319 drm and drm2 have been removed from the tree. Please see
320 https://wiki.freebsd.org/Graphics for the latest information on
321 migrating to the drm ports.
324 Iflib is no longer unconditionally compiled into the kernel. Drivers
325 using iflib and statically compiled into the kernel, now require
326 the 'device iflib' config option. For the same drivers loaded as
327 modules on kernels not having 'device iflib', the iflib.ko module
328 is loaded automatically.
331 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
332 options no longer exist since r343219 and r343427 respectively;
333 nothing uses them, so they should be just removed from custom
337 r342635 changes the way efibootmgr(8) works by requiring users to add
338 the -b (bootnum) parameter for commands where the bootnum was previously
339 specified with each option. For example 'efibootmgr -B 0001' is now
340 'efibootmgr -B -b 0001'.
343 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
344 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
345 servers that have vfs.nfsd.nfs_privport set will only allow mounts
346 from clients using a reserved port#. Since both the FreeBSD and Linux
347 NFSv4 clients use reserved port#s by default, this should not affect
351 The XLP config has been removed. We can't support 64-bit atomics in this
352 kernel because it is running in 32-bit mode. XLP users must transition
353 to running a 64-bit kernel (XLP64 or XLPN32).
355 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
356 the preferred emulator today and we don't need two different ones.
358 The old sibyte / swarm / Broadcom BCM1250 support has been
359 removed from the mips port.
362 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
363 7.0.1. Please see the 20141231 entry below for information about
364 prerequisites and upgrading, if you are not already using clang 3.5.0
368 Remove the timed and netdate programs from the base tree. Setting
369 the time with these daemons has been obsolete for over a decade.
372 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
373 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
374 it produces broken binaries when ifuncs are in use. Users needing
375 GNU ld should install the binutils port or package.
378 The BSD crtbegin and crtend code has been enabled by default. It has
379 had extensive testing on amd64, arm64, and i386. It can be disabled
380 by building a world with -DWITHOUT_BSD_CRTBEGIN.
383 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
384 has been converted to a port (misc/ctm) and will be removed from
385 FreeBSD-13. It is available as a package (ctm) for all supported
389 The default newsyslog.conf(5) file has been changed to only include
390 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
391 the filenames end in '.conf' and do not begin with a '.'.
393 You should check the configuration files in these two directories match
394 this naming convention. You can verify which configuration files are
395 being included using the command:
399 Ports for the DRM modules have been simplified. Now, amd64 users should
400 just install the drm-kmod port. All others should install
403 Graphics hardware that's newer than about 2010 usually works with
404 drm-kmod. For hardware older than 2013, however, some users will need
405 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
406 than 2008 usually only works in drm-legacy-kmod. The graphics team can
407 only commit to hardware made since 2013 due to the complexity of the
408 market and difficulty to test all the older cards effectively. If you
409 have hardware supported by drm-kmod, you are strongly encouraged to use
410 that as you will get better support.
412 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
413 elsewhere, the drm and drm2 modules will be eliminated from the src base
414 soon (with a limited exception for arm). Please update to the package
415 asap and report any issues to x11@freebsd.org.
417 Generally, anybody using the drm*-kmod packages should add
418 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
419 cross-threading surprises, especially with automatic driver
420 loading from X11 startup. These will become the defaults in 13-current
424 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
425 custom kernel and module loading configuration files must be updated
426 accordingly. Moreover, interfaces previous presented as ixlvN to the
427 system are now exposed as iavfN and network configuration files must
428 be adjusted as necessary.
431 OpenSSL has been updated to version 1.1.1. This update included
432 additional various API changes throughout the base system. It is
433 important to rebuild third-party software after upgrading. The value
434 of __FreeBSD_version has been bumped accordingly.
437 The legacy DRM modules and drivers have now been added to the loader's
438 module blacklist, in favor of loading them with kld_list in rc.conf(5).
439 The module blacklist may be overridden with the loader.conf(5)
440 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
444 The cam(4) based nda(4) driver will be used over nvd(4) by default on
445 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
446 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
447 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
451 Reproducible build mode is now on by default, in preparation for
452 FreeBSD 12.0. This eliminates build metadata such as the user,
453 host, and time from the kernel (and uname), unless the working tree
454 corresponds to a modified checkout from a version control system.
455 The previous behavior can be obtained by setting the /etc/src.conf
456 knob WITHOUT_REPRODUCIBLE_BUILD.
459 The Yarrow CSPRNG has been removed from the kernel as it has not been
460 supported by its designers since at least 2003. Fortuna has been the
461 default since FreeBSD-11.
464 devctl freeze/thaw have gone into the tree, the rc scripts have been
465 updated to use them and devmatch has been changed. You should update
466 kernel, userland and rc scripts all at the same time.
469 The default interpreter has been switched from 4th to Lua.
470 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
471 interpreter. If you have custom FORTH code you will need to set
472 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
473 src.conf for the build. This will create default hard links between
474 loader and loader_4th instead of loader and loader_lua, the new default.
475 If you are using UEFI it will create the proper hard link to loader.efi.
477 bhyve uses userboot.so. It remains 4th-only until some issues are solved
478 regarding coexisting with multiple versions of FreeBSD are resolved.
481 ls(1) now respects the COLORTERM environment variable used in other
482 systems and software to indicate that a colored terminal is both
483 supported and desired. If ls(1) is suddenly emitting colors, they may
484 be disabled again by either removing the unwanted COLORTERM from your
485 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
486 may not be observed in a future release.
489 The default pager for most commands has been changed to "less". To
490 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
494 The jedec_ts(4) driver has been removed. A superset of its functionality
495 is available in the jedec_dimm(4) driver, and the manpage for that
496 driver includes migration instructions. If you have "device jedec_ts"
497 in your kernel configuration file, it must be removed.
500 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
501 This should have no effect if the kernel is booted via BIOS/legacy boot.
502 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
503 has a buggy firmware that prevents a successful boot due to use of
507 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
508 support has been removed from the tree. These ports were
509 obsolete and/or known to be broken for many years.
512 loader.efi has been augmented to participate more fully in the
513 UEFI boot manager protocol. loader.efi will now look at the
514 BootXXXX environment variable to determine if a specific kernel
515 or root partition was specified. XXXX is derived from BootCurrent.
516 efibootmgr(8) manages these standard UEFI variables.
519 zfsloader's functionality has now been folded into loader.
520 zfsloader is no longer necessary once you've updated your
521 boot blocks. For a transition period, we will install a
522 hardlink for zfsloader to loader to allow a smooth transition
523 until the boot blocks can be updated (hard link because old
524 zfs boot blocks don't understand symlinks).
527 ARM64 now have efifb support, if you want to have serial console
528 on your arm64 board when an screen is connected and the bootloader
529 setup a frame buffer for us to use, just add :
533 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
534 an screen connected as the firmware will setup a frame buffer are that
535 u-boot will expose as an EFI frame buffer.
538 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
539 or take steps to update /etc/passwd before doing installworld on
540 existing systems. Do not skip the "mergemaster -Fp" step before
541 installworld, as described in the update procedures near the bottom
542 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
543 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
544 the ntp config file contain options that change file/dir locations.
545 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
546 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
547 taking steps to ensure that all required files/dirs are accessible
551 Big endian arm support has been removed.
554 The static environment setup in kernel configs is no longer mutually
555 exclusive with the loader(8) environment by default. In order to
556 restore the previous default behavior of disabling the loader(8)
557 environment if a static environment is present, you must specify
558 loader_env.disabled=1 in the static environment.
561 The ABI of syscalls used by management tools like sockstat and
562 netstat has been broken to allow 32-bit binaries to work on
563 64-bit kernels without modification. These programs will need
564 to match the kernel in order to function. External programs may
565 require minor modifications to accommodate a change of type in
566 structures from pointers to 64-bit virtual addresses.
569 On i386 and amd64 atomics are now inlined. Out of tree modules using
570 atomics will need to be rebuilt.
573 The '%I' format in the kern.corefile sysctl limits the number of
574 core files that a process can generate to the number stored in the
575 debug.ncores sysctl. The '%I' format is replaced by the single digit
576 index. Previously, if all indexes were taken the kernel would overwrite
577 only a core file with the highest index in a filename.
578 Currently the system will create a new core file if there is a free
579 index or if all slots are taken it will overwrite the oldest one.
582 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
583 6.0.1. Please see the 20141231 entry below for information about
584 prerequisites and upgrading, if you are not already using clang 3.5.0
588 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
589 needed to be changed to work with it. This change was made with r335763
590 and requires a mergemaster / etcupdate / etc to update the installed
594 r334930 changed the interface between the NFS modules, so they all
595 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
598 As of r334391 lld is the default amd64 system linker; it is installed
599 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
603 The kernel / userland interface for devinfo changed, so you'll
604 need a new kernel and userland as a pair for it to work (rebuilding
605 lib/libdevinfo is all that's required). devinfo and devmatch will
606 not work, but everything else will when there's a mismatch.
609 The on-disk format for hwpmc callchain records has changed to include
610 threadid corresponding to a given record. This changes the field offsets
611 and thus requires that libpmcstat be rebuilt before using a kernel
615 The vxge(4) driver has been removed. This driver was introduced into
616 HEAD one week before the Exar left the Ethernet market and is not
617 known to be used. If you have device vxge in your kernel config file
621 The amd64 kernel now requires a ld that supports ifunc to produce a
622 working kernel, either lld or a newer binutils. lld is built by default
623 on amd64, and the 'buildkernel' target uses it automatically. However,
624 it is not the default linker, so building the kernel the traditional
625 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
626 binutils port/package). lld will soon be default, and this requirement
629 NOTE: As of r334391 lld is the default system linker on amd64, and no
630 workaround is necessary.
633 The nxge(4) driver has been removed. This driver was for PCI-X 10g
634 cards made by s2io/Neterion. The company was acquired by Exar and
635 no longer sells or supports Ethernet products. If you have device
636 nxge in your kernel config file it must be removed.
639 The tz database (tzdb) has been updated to 2018e. This version more
640 correctly models time stamps in time zones with negative DST such as
641 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
642 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
643 time zone abbreviations and the tm_isdst flag.
646 The ixgb(4) driver has been removed. This driver was for an early and
647 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
648 quickly shifted to the long lived ixgbe family. If you have device
649 ixgb in your kernel config file it must be removed.
652 The lmc(4) driver has been removed. This was a WAN interface
653 card that was already reportedly rare in 2003, and had an ambiguous
654 license. If you have device lmc in your kernel config file it must
658 Support for Arcnet networks has been removed. If you have device
659 arcnet or device cm in your kernel config file they must be
663 Support for FDDI networks has been removed. If you have device
664 fddi or device fpa in your kernel config file they must be
668 In addition to supporting RFC 3164 formatted messages, the
669 syslogd(8) service is now capable of parsing RFC 5424 formatted
670 log messages. The main benefit of using RFC 5424 is that clients
671 may now send log messages with timestamps containing year numbers,
672 microseconds and time zone offsets.
674 Similarly, the syslog(3) C library function has been altered to
675 send RFC 5424 formatted messages to the local system logging
676 daemon. On systems using syslogd(8), this change should have no
677 negative impact, as long as syslogd(8) and the C library are
678 updated at the same time. On systems using a different system
679 logging daemon, it may be necessary to make configuration
680 adjustments, depending on the software used.
682 When using syslog-ng, add the 'syslog-protocol' flag to local
683 input sources to enable parsing of RFC 5424 formatted messages:
686 unix-dgram("/var/run/log" flags(syslog-protocol));
689 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
690 of the 'imuxsock' module to let messages be processed by the
691 regular RFC 3164/5424 parsing pipeline:
693 module(load="imuxsock" SysSock.UseSpecialParser="off")
695 Do note that these changes only affect communication between local
696 applications and syslogd(8). The format that syslogd(8) uses to
697 store messages on disk or forward messages to other systems
698 remains unchanged. syslogd(8) still uses RFC 3164 for these
699 purposes. Options to customize this behaviour will be added in the
700 future. Utilities that process log files stored in /var/log are
701 thus expected to continue to function as before.
703 __FreeBSD_version has been incremented to 1200061 to denote this
707 Support for token ring networks has been removed. If you
708 have "device token" in your kernel config you should remove
709 it. No device drivers supported token ring.
712 makefs was modified to be able to tag ISO9660 El Torito boot catalog
713 entries as EFI instead of overloading the i386 tag as done previously.
714 The amd64 mkisoimages.sh script used to build amd64 ISO images for
715 release was updated to use this. This may mean that makefs must be
716 updated before "make cdrom" can be run in the release directory. This
717 should be as simple as:
719 $ cd $SRCDIR/usr.sbin/makefs
720 $ make depend all install
723 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
724 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
725 Co-existence for the transition period will come shortly. Booting is a
726 complex environment and test coverage for Lua-enabled loaders has been
727 thin, so it would be prudent to assume it might not work and make
728 provisions for backup boot methods.
731 devmatch functionality has been turned on in devd. It will automatically
732 load drivers for unattached devices. This may cause unexpected drivers
733 to be loaded. Please report any problems to current@ and
737 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
738 6.0.0. Please see the 20141231 entry below for information about
739 prerequisites and upgrading, if you are not already using clang 3.5.0
743 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
744 This means it is used to link the kernel and userland libraries and
745 executables, but is not yet installed as /usr/bin/ld by default.
747 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
748 WITHOUT_LLD_BOOTSTRAP=yes
751 On i386, pmtimer has been removed. Its functionality has been folded
752 into apm. It was a no-op on ACPI in current for a while now (but was
753 still needed on i386 in FreeBSD 11 and earlier). Users may need to
754 remove it from kernel config files.
757 The use of RSS hash from the network card aka flowid has been
758 disabled by default for lagg(4) as it's currently incompatible with
759 the lacp and loadbalance protocols.
761 This can be re-enabled by setting the following in loader.conf:
762 net.link.lagg.default_use_flowid="1"
765 The SW_WATCHDOG option is no longer necessary to enable the
766 hardclock-based software watchdog if no hardware watchdog is
767 configured. As before, SW_WATCHDOG will cause the software
768 watchdog to be enabled even if a hardware watchdog is configured.
771 r326887 fixes the issue described in the 20171214 UPDATING entry.
772 r326888 flips the switch back to building GELI support always.
775 r362593 broke ZFS + GELI support for reasons unknown. However,
776 it also broke ZFS support generally, so GELI has been turned off
777 by default as the lesser evil in r326857. If you boot off ZFS and/or
778 GELI, it might not be a good time to update.
781 PowerPC users must update loader(8) by rebuilding world before
782 installing a new kernel, as the protocol connecting them has
783 changed. Without the update, loader metadata will not be passed
784 successfully to the kernel and users will have to enter their
785 root partition at the kernel mountroot prompt to continue booting.
786 Newer versions of loader can boot old kernels without issue.
789 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
790 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
791 to WITH/OUT_LOADER_GELI.
794 The naive and non-compliant support of posix_fallocate(2) in ZFS
795 has been removed as of r325320. The system call now returns EINVAL
796 when used on a ZFS file. Although the new behavior complies with the
797 standard, some consumers are not prepared to cope with it.
798 One known victim is lld prior to r325420.
801 Building in a FreeBSD src checkout will automatically create object
802 directories now rather than store files in the current directory if
803 'make obj' was not ran. Calling 'make obj' is no longer necessary.
804 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
805 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
809 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
810 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
811 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
812 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
813 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
814 The UNIFIED_OBJDIR option is a transitional feature that will be
815 removed for 12.0 release; please migrate to the new format for any
816 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
817 than hardcoding paths.
820 The native-xtools target no longer installs the files by default to the
821 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
822 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
825 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
826 options are changing from controlling the build if defined / undefined
827 to controlling the build with explicit 'yes' or 'no' values. They will
828 shift to WITH/WITHOUT options to match other options in the system.
831 libstand has turned into a private library for sys/boot use only.
832 It is no longer supported as a public interface outside of sys/boot.
835 The arm port has split armv6 into armv6 and armv7. armv7 is now
836 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
837 and are running a kernel from before r324363, you will need to add
838 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
841 When building multiple kernels using KERNCONF, non-existent KERNCONF
842 files will produce an error and buildkernel will fail. Previously
843 missing KERNCONF files silently failed giving no indication as to
844 why, only to subsequently discover during installkernel that the
845 desired kernel was never built in the first place.
848 The default serial number format for CTL LUNs has changed. This will
849 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
850 or iSCSI clients care about their LUNs' serial numbers. Users who
851 require serial number stability should hardcode serial numbers in
855 For 32-bit arm compiled for hard-float support, soft-floating point
856 binaries now always get their shared libraries from
857 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
858 /usr/libsoft also existed). Only users with a hard-float ld.so, but
859 soft-float everything else should be affected.
862 The geli password typed at boot is now hidden. To restore the previous
863 behavior, see geli(8) for configuration options.
866 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
867 sysctl values. Minor nit, but requires a rebuild of both world/kernel
871 "make check" behavior (made in ^/head@r295380) has been changed to
872 execute from a limited sandbox, as opposed to executing from
876 - The "beforecheck" and "aftercheck" targets are now specified.
877 - ${CHECKDIR} (added in commit noted above) has been removed.
878 - Legacy behavior can be enabled by setting
879 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
881 If the limited sandbox mode is enabled, "make check" will execute
882 "make distribution", then install, execute the tests, and clean up the
883 sandbox if successful.
885 The "make distribution" and "make install" targets are typically run as
886 root to set appropriate permissions and ownership at installation time.
887 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
888 environment if executing "make check" with limited sandbox mode using
889 an unprivileged user.
892 Since the switch to GPT disk labels, fsck for UFS/FFS has been
893 unable to automatically find alternate superblocks. As of r322297,
894 the information needed to find alternate superblocks has been
895 moved to the end of the area reserved for the boot block.
896 Filesystems created with a newfs of this vintage or later
897 will create the recovery information. If you have a filesystem
898 created prior to this change and wish to have a recovery block
899 created for your filesystem, you can do so by running fsck in
900 foreground mode (i.e., do not use the -p or -y options). As it
901 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
902 to which you should answer yes.
905 As of r321665, an NFSv4 server configuration that services
906 Kerberos mounts or clients that do not support the uid/gid in
907 owner/owner_group string capability, must explicitly enable
908 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
909 machine's /etc/rc.conf file.
912 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
913 Please see the 20141231 entry below for information about prerequisites
914 and upgrading, if you are not already using clang 3.5.0 or higher.
917 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
918 r-commands (rlogin, rsh, etc.) to be built with the base system.
921 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
922 a very major ABI incompatible change, so users of FreeBSD/powerpc must
923 be careful when performing source upgrades. It is best to run
924 'make installworld' from an alternate root system, either a live
925 CD/memory stick, or a temporary root partition. Additionally, all ports
926 must be recompiled. powerpc64 is largely unaffected, except in the case
927 of 32-bit compatibility. All 32-bit binaries will be affected.
930 Forward compatibility for the "ino64" project have been committed. This
931 will allow most new binaries to run on older kernels in a limited
932 fashion. This prevents many of the common foot-shooting actions in the
933 upgrade as well as the limited ability to roll back the kernel across
934 the ino64 upgrade. Complicated use cases may not work properly, though
935 enough simpler ones work to allow recovery in most situations.
938 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
939 if you require the GPL compiler.
942 The internal ABI used for communication between the NFS kernel modules
943 was changed by r320085, so __FreeBSD_version was bumped to
944 ensure all the NFS related modules are updated together.
947 The ABI of struct event was changed by extending the data
948 member to 64bit and adding ext fields. For upgrade, same
949 precautions as for the entry 20170523 "ino64" must be
953 The GNU roff toolchain has been removed from base. To render manpages
954 which are not supported by mandoc(1), man(1) can fallback on GNU roff
955 from ports (and recommends to install it).
956 To render roff(7) documents, consider using GNU roff from ports or the
957 heirloom doctools roff toolchain from ports via pkg install groff or
958 via pkg install heirloom-doctools.
961 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
962 smaller runtime footprint builds. This is useful for embedded systems
963 which only require one chipset support.
965 If you load it as a module, make sure this is in /boot/loader.conf:
969 This will load the HAL, all chip/RF backends and if_ath_pci.
970 If you have if_ath_pci in /boot/loader.conf, ensure it is after
971 if_ath or it will not load any HAL chipset support.
973 If you want to selectively load things (eg on ye cheape ARM/MIPS
974 platforms where RAM is at a premium) you should:
977 * load the chip modules in question
978 * load ath_rate, ath_dfs
980 * load if_ath_pci and/or if_ath_ahb depending upon your particular
981 bus bind type - this is where probe/attach is done.
983 For further comments/feedback, poke adrian@ .
986 The "ino64" 64-bit inode project has been committed, which extends
987 a number of types to 64 bits. Upgrading in place requires care and
988 adherence to the documented upgrade procedure.
990 If using a custom kernel configuration ensure that the
991 COMPAT_FREEBSD11 option is included (as during the upgrade the
992 system will be running the ino64 kernel with the existing world).
994 For the safest in-place upgrade begin by removing previous build
995 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full
996 procedure documented below under the heading "To rebuild everything and
997 install it on the current system." Specifically, a reboot is required
998 after installing the new kernel before installing world. While an
999 installworld normally works by accident from multiuser after rebooting
1000 the proper kernel, there are many cases where this will fail across this
1001 upgrade and installworld from single user is required.
1004 The NATM framework including the en(4), fatm(4), hatm(4), and
1005 patm(4) devices has been removed. Consumers should plan a
1006 migration before the end-of-life date for FreeBSD 11.
1009 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
1010 diff has not been implemented, if those are needed a newer version of
1011 GNU diff is available via the diffutils package under the gdiff name.
1014 As of r316810 for ipfilter, keep frags is no longer assumed when
1015 keep state is specified in a rule. r316810 aligns ipfilter with
1016 documentation in man pages separating keep frags from keep state.
1017 This allows keep state to be specified without forcing keep frags
1018 and allows keep frags to be specified independently of keep state.
1019 To maintain previous behaviour, also specify keep frags with
1020 keep state (as documented in ipf.conf.5).
1023 arm64 builds now use the base system LLD 4.0.0 linker by default,
1024 instead of requiring that the aarch64-binutils port or package be
1025 installed. To continue using aarch64-binutils, set
1026 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
1029 The UDP optimization in entry 20160818 that added the sysctl
1030 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
1031 packets will no longer be treated as L3 broadcast packets.
1034 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
1035 use any explicitly assigned loopback address available in the jail
1036 instead of using the first assigned address of the jail.
1039 The ctl.ko module no longer implements the iSCSI target frontend:
1040 cfiscsi.ko does instead.
1042 If building cfiscsi.ko as a kernel module, the module can be loaded
1043 via one of the following methods:
1044 - `cfiscsi_load="YES"` in loader.conf(5).
1045 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
1046 - ctladm(8)/ctld(8), when compiled with iSCSI support
1047 (`WITH_ISCSI=yes` in src.conf(5))
1049 Please see cfiscsi(4) for more details.
1052 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
1053 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
1054 same source (previously, the dependency of mmcsd.ko on mmc.ko was
1055 missing, but mmcsd.ko now will refuse to load if it is incompatible
1059 The syntax of ipfw(8) named states was changed to avoid ambiguity.
1060 If you have used named states in the firewall rules, you need to modify
1061 them after installworld and before rebooting. Now named states must
1062 be prefixed with colon.
1065 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
1066 removed as the userland we provide cannot use them. The KMS version
1067 (sys/dev/drm2) supports the same hardware.
1070 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
1071 Please see the 20141231 entry below for information about prerequisites
1072 and upgrading, if you are not already using clang 3.5.0 or higher.
1075 The code that provides support for ZFS .zfs/ directory functionality
1076 has been reimplemented. It's not possible now to create a snapshot
1077 by mkdir under .zfs/snapshot/. That should be the only user visible
1081 EISA bus support has been removed. The WITH_EISA option is no longer
1085 MCA bus support has been removed.
1088 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
1089 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
1092 The EM_MULTIQUEUE kernel configuration option is deprecated now that
1093 the em(4) driver conforms to iflib specifications.
1096 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
1097 IFLIB. If you have a custom kernel configuration that excludes em(4)
1098 but you use igb(4), you need to re-add em(4) to your custom
1102 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
1103 Please see the 20141231 entry below for information about prerequisites
1104 and upgrading, if you are not already using clang 3.5.0 or higher.
1107 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
1108 Please see the 20141231 entry below for information about prerequisites
1109 and upgrading, if you are not already using clang 3.5.0 or higher.
1112 The layout of the pmap structure has changed for powerpc to put the pmap
1113 statistics at the front for all CPU variations. libkvm(3) and all tools
1114 that link against it need to be recompiled.
1117 isl(4) and cyapa(4) drivers now require a new driver,
1118 chromebook_platform(4), to work properly on Chromebook-class hardware.
1119 On other types of hardware the drivers may need to be configured using
1120 device hints. Please see the corresponding manual pages for details.
1123 The urtwn(4) driver was merged into rtwn(4) and now consists of
1124 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
1126 Also, firmware for RTL8188CE was renamed due to possible name
1127 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
1130 GNU rcs has been removed from base. It is available as packages:
1131 - rcs: Latest GPLv3 GNU rcs version.
1132 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
1136 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
1137 modules now requires that the kernel configuration contain the
1138 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
1141 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
1142 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
1145 Relocatable object files with the extension of .So have been renamed
1146 to use an extension of .pico instead. The purpose of this change is
1147 to avoid a name clash with shared libraries on case-insensitive file
1148 systems. On those file systems, foo.So is the same file as foo.so.
1151 GNU rcs has been turned off by default. It can (temporarily) be built
1152 again by adding WITH_RCS knob in src.conf.
1153 Otherwise, GNU rcs is available from packages:
1154 - rcs: Latest GPLv3 GNU rcs version.
1155 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
1158 The backup_uses_rcs functionality has been removed from rc.subr.
1161 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
1162 two separate components, QUEUE_MACRO_DEBUG_TRACE and
1163 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
1164 QUEUE_MACRO_DEBUG behavior.
1167 r304787 changed some ioctl interfaces between the iSCSI userspace
1168 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1169 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1173 The UDP receive code has been updated to only treat incoming UDP
1174 packets that were addressed to an L2 broadcast address as L3
1175 broadcast packets. It is not expected that this will affect any
1176 standards-conforming UDP application. The new behaviour can be
1177 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1181 Remove the openbsd_poll system call.
1182 __FreeBSD_version has been bumped because of this.
1185 The stable/11 branch has been created from head@r302406.
1188 The libc stub for the pipe(2) system call has been replaced with
1189 a wrapper that calls the pipe2(2) system call and the pipe(2)
1190 system call is now only implemented by the kernels that include
1191 "options COMPAT_FREEBSD10" in their config file (this is the
1192 default). Users should ensure that this option is enabled in
1193 their kernel or upgrade userspace to r302092 before upgrading their
1197 CAM will now strip leading spaces from SCSI disks' serial numbers.
1198 This will affect users who create UFS filesystems on SCSI disks using
1199 those disk's diskid device nodes. For example, if /etc/fstab
1200 previously contained a line like
1201 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
1202 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
1203 transforms like gmirror may also be affected. ZFS users should
1207 The bitstring(3) API has been updated with new functionality and
1208 improved performance. But it is binary-incompatible with the old API.
1209 Objects built with the new headers may not be linked against objects
1210 built with the old headers.
1213 The brk and sbrk functions have been removed from libc on arm64.
1214 Binutils from ports has been updated to not link to these
1215 functions and should be updated to the latest version before
1216 installing a new libc.
1219 The armv6 port now defaults to hard float ABI. Limited support
1220 for running both hardfloat and soft float on the same system
1221 is available using the libraries installed with -DWITH_LIBSOFT.
1222 This has only been tested as an upgrade path for installworld
1223 and packages may fail or need manual intervention to run. New
1224 packages will be needed.
1226 To update an existing self-hosted armv6hf system, you must add
1227 TARGET_ARCH=armv6 on the make command line for both the build
1228 and the install steps.
1231 Kernel modules compiled outside of a kernel build now default to
1232 installing to /boot/modules instead of /boot/kernel. Many kernel
1233 modules built this way (such as those in ports) already overrode
1234 KMODDIR explicitly to install into /boot/modules. However,
1235 manually building and installing a module from /sys/modules will
1236 now install to /boot/modules instead of /boot/kernel.
1239 The CAM I/O scheduler has been committed to the kernel. There should be
1240 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1241 list of known rogues that claim support for this but actually corrupt
1242 data is believed to be complete, be on the lookout for data
1243 corruption. The known rogue list is believed to be complete:
1245 o Crucial MX100, M550 drives with MU01 firmware.
1246 o Micron M510 and M550 drives with MU01 firmware.
1247 o Micron M500 prior to MU07 firmware
1248 o Samsung 830, 840, and 850 all firmwares
1249 o FCCT M500 all firmwares
1251 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1252 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1253 updated firmware. Black listed drives will work correctly because these
1254 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1255 this list is the same as found in Linux, it's believed there are no
1256 other rogues in the market place. All other models from the above
1259 To be safe, if you are at all concerned, you can quirk each of your
1260 drives to prevent NCQ from being sent by setting:
1261 kern.cam.ada.X.quirks="0x2"
1262 in loader.conf. If the drive requires the 4k sector quirk, set the
1263 quirks entry to 0x3.
1266 The FAST_DEPEND build option has been removed and its functionality is
1267 now the one true way. The old mkdep(1) style of 'make depend' has
1268 been removed. See 20160311 for further details.
1271 Resource range types have grown from unsigned long to uintmax_t. All
1272 drivers, and anything using libdevinfo, need to be recompiled.
1275 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1276 builds. It no longer runs mkdep(1) during 'make depend', and the
1277 'make depend' stage can safely be skipped now as it is auto ran
1278 when building 'make all' and will generate all SRCS and DPSRCS before
1279 building anything else. Dependencies are gathered at compile time with
1280 -MF flags kept in separate .depend files per object file. Users should
1281 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1282 stale .depend files.
1285 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1286 kernel modules. Therefore, if you load any kernel modules at boot time,
1287 please install the boot loaders after you install the kernel, but before
1291 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1292 make installkernel KERNCONF=YOUR_KERNEL_HERE
1293 make -C sys/boot install
1294 <reboot in single user>
1296 Then follow the usual steps, described in the General Notes section,
1300 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1301 see the 20141231 entry below for information about prerequisites and
1302 upgrading, if you are not already using clang 3.5.0 or higher.
1305 The AIO subsystem is now a standard part of the kernel. The
1306 VFS_AIO kernel option and aio.ko kernel module have been removed.
1307 Due to stability concerns, asynchronous I/O requests are only
1308 permitted on sockets and raw disks by default. To enable
1309 asynchronous I/O requests on all file types, set the
1310 vfs.aio.enable_unsafe sysctl to a non-zero value.
1313 The ELF object manipulation tool objcopy is now provided by the
1314 ELF Tool Chain project rather than by GNU binutils. It should be a
1315 drop-in replacement, with the addition of arm64 support. The
1316 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1317 to obtain the GNU version if necessary.
1320 Building ZFS pools on top of zvols is prohibited by default. That
1321 feature has never worked safely; it's always been prone to deadlocks.
1322 Using a zvol as the backing store for a VM guest's virtual disk will
1323 still work, even if the guest is using ZFS. Legacy behavior can be
1324 restored by setting vfs.zfs.vol.recursive=1.
1327 The NONE and HPN patches has been removed from OpenSSH. They are
1328 still available in the security/openssh-portable port.
1331 With the addition of ypldap(8), a new _ypldap user is now required
1332 during installworld. "mergemaster -p" can be used to add the user
1333 prior to installworld, as documented in the handbook.
1336 The tftp loader (pxeboot) now uses the option root-path directive. As a
1337 consequence it no longer looks for a pxeboot.4th file on the tftp
1338 server. Instead it uses the regular /boot infrastructure as with the
1342 The code to start recording plug and play data into the modules has
1343 been committed. While the old tools will properly build a new kernel,
1344 a number of warnings about "unknown metadata record 4" will be produced
1345 for an older kldxref. To avoid such warnings, make sure to rebuild
1346 the kernel toolchain (or world). Make sure that you have r292078 or
1347 later when trying to build 292077 or later before rebuilding.
1350 Debug data files are now built by default with 'make buildworld' and
1351 installed with 'make installworld'. This facilitates debugging but
1352 requires more disk space both during the build and for the installed
1353 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1357 r291527 changed the internal interface between the nfsd.ko and
1358 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1359 __FreeBSD_version has been bumped because of this.
1362 Add support for unicode collation strings leads to a change of
1363 order of files listed by ls(1) for example. To get back to the old
1364 behaviour, set LC_COLLATE environment variable to "C".
1366 Databases administrators will need to reindex their databases given
1367 collation results will be different.
1369 Due to a bug in install(1) it is recommended to remove the ancient
1370 locales before running make installworld.
1372 rm -rf /usr/share/locale/*
1375 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1376 libcrypto.so.7 or libssl.so.7 must be recompiled.
1379 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1380 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1381 should be replaced with isp_2400 and isp_2500 modules respectively.
1384 The build previously allowed using 'make -n' to not recurse into
1385 sub-directories while showing what commands would be executed, and
1386 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1387 and 'make -N' will not.
1390 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1391 and etcupdate will now use this file. A custom sendmail.cf is now
1392 updated via this mechanism rather than via installworld. If you had
1393 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1394 want to remove the exclusion or change it to "always install".
1395 /etc/mail/sendmail.cf is now managed the same way regardless of
1396 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1397 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1400 Compatibility shims for legacy ATA device names have been removed.
1401 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1402 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1403 environment variables, /dev/ad* and /dev/ar* symbolic links.
1406 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1407 Please see the 20141231 entry below for information about prerequisites
1408 and upgrading, if you are not already using clang 3.5.0 or higher.
1411 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1412 and renamed from .symbols to .debug. This reduces the size requirements
1413 on the boot partition or file system and provides consistency with
1414 userland debug files.
1416 When using the supported kernel installation method the
1417 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1418 as is done with /boot/kernel.
1420 Developers wishing to maintain the historical behavior of installing
1421 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1424 The wireless drivers had undergone changes that remove the 'parent
1425 interface' from the ifconfig -l output. The rc.d network scripts
1426 used to check presence of a parent interface in the list, so old
1427 scripts would fail to start wireless networking. Thus, etcupdate(3)
1428 or mergemaster(8) run is required after kernel update, to update your
1429 rc.d scripts in /etc.
1432 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1433 These configurations are now automatically interpreted as
1434 'scrub fragment reassemble'.
1437 Kernel-loadable modules for the random(4) device are back. To use
1438 them, the kernel must have
1441 options RANDOM_LOADABLE
1443 kldload(8) can then be used to load random_fortuna.ko
1444 or random_yarrow.ko. Please note that due to the indirect
1445 function calls that the loadable modules need to provide,
1446 the build-in variants will be slightly more efficient.
1448 The random(4) kernel option RANDOM_DUMMY has been retired due to
1449 unpopularity. It was not all that useful anyway.
1452 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1453 Control over building the ELF Tool Chain tools is now provided by
1454 the WITHOUT_TOOLCHAIN knob.
1457 The polarity of Pulse Per Second (PPS) capture events with the
1458 uart(4) driver has been corrected. Prior to this change the PPS
1459 "assert" event corresponded to the trailing edge of a positive PPS
1460 pulse and the "clear" event was the leading edge of the next pulse.
1462 As the width of a PPS pulse in a typical GPS receiver is on the
1463 order of 1 millisecond, most users will not notice any significant
1464 difference with this change.
1466 Anyone who has compensated for the historical polarity reversal by
1467 configuring a negative offset equal to the pulse width will need to
1468 remove that workaround.
1471 The default group assigned to /dev/dri entries has been changed
1472 from 'wheel' to 'video' with the id of '44'. If you want to have
1473 access to the dri devices please add yourself to the video group
1476 # pw groupmod video -m $USER
1479 The menu.rc and loader.rc files will now be replaced during
1480 upgrades. Please migrate local changes to menu.rc.local and
1481 loader.rc.local instead.
1484 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1485 strings and strip have been removed. The src.conf(5) knob
1486 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1489 As ZFS requires more kernel stack pages than is the default on some
1490 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1491 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1493 Please consider using 'options KSTACK_PAGES=X' where X is greater
1494 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1497 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1498 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1499 default, i.e., they will not contain "::". For example, instead
1500 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1501 to have a more specific match, such as different map entries for
1502 IPv6:0:0 vs IPv6:0. This change requires that configuration
1503 data (including maps, files, classes, custom ruleset, etc.) must
1504 use the same format, so make certain such configuration data is
1505 upgrading. As a very simple check search for patterns like
1506 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1507 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1508 the cf option UseCompressedIPv6Addresses.
1511 The default kernel entropy-processing algorithm is now
1512 Fortuna, replacing Yarrow.
1514 Assuming you have 'device random' in your kernel config
1515 file, the configurations allow a kernel option to override
1516 this default. You may choose *ONE* of:
1518 options RANDOM_YARROW # Legacy /dev/random algorithm.
1519 options RANDOM_DUMMY # Blocking-only driver.
1521 If you have neither, you get Fortuna. For most people,
1522 read no further, Fortuna will give a /dev/random that works
1523 like it always used to, and the difference will be irrelevant.
1525 If you remove 'device random', you get *NO* kernel-processed
1526 entropy at all. This may be acceptable to folks building
1527 embedded systems, but has complications. Carry on reading,
1528 and it is assumed you know what you need.
1530 *PLEASE* read random(4) and random(9) if you are in the
1531 habit of tweaking kernel configs, and/or if you are a member
1532 of the embedded community, wanting specific and not-usual
1533 behaviour from your security subsystems.
1535 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1536 random', you will NOT have a functioning /dev/random, and
1537 many cryptographic features will not work, including SSH.
1538 You may also find strange behaviour from the random(3) set
1539 of library functions, in particular sranddev(3), srandomdev(3)
1540 and arc4random(3). The reason for this is that the KERN_ARND
1541 sysctl only returns entropy if it thinks it has some to
1542 share, and with RANDOM_DUMMY or no 'device random' this
1546 An additional fix for the issue described in the 20150614 sendmail
1547 entry below has been committed in revision 284717.
1550 FreeBSD's old make (fmake) has been removed from the system. It is
1551 available as the devel/fmake port or via pkg install fmake.
1554 The fix for the issue described in the 20150614 sendmail entry
1555 below has been committed in revision 284436. The work
1556 around described in that entry is no longer needed unless the
1557 default setting is overridden by a confDH_PARAMETERS configuration
1558 setting of '5' or pointing to a 512 bit DH parameter file.
1561 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1562 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1563 and devel/kyua to version 0.20+ and adjust any calling code to work
1564 with Kyuafile and kyua.
1567 The import of openssl to address the FreeBSD-SA-15:10.openssl
1568 security advisory includes a change which rejects handshakes
1569 with DH parameters below 768 bits. sendmail releases prior
1570 to 8.15.2 (not yet released), defaulted to a 512 bit
1571 DH parameter setting for client connections. To work around
1572 this interoperability, sendmail can be configured to use a
1573 2048 bit DH parameter by:
1575 1. Edit /etc/mail/`hostname`.mc
1576 2. If a setting for confDH_PARAMETERS does not exist or
1577 exists and is set to a string beginning with '5',
1578 replace it with '2'.
1579 3. If a setting for confDH_PARAMETERS exists and is set to
1580 a file path, create a new file with:
1581 openssl dhparam -out /path/to/file 2048
1582 4. Rebuild the .cf file:
1583 cd /etc/mail/; make; make install
1584 5. Restart sendmail:
1585 cd /etc/mail/; make restart
1587 A sendmail patch is coming, at which time this file will be
1591 Generation of legacy formatted entries have been disabled by default
1592 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1593 entries were converted to use the new format by default when the new,
1594 machine independent format have been added and supported since FreeBSD
1597 Please see the pwd_mkdb(8) manual page for further details.
1600 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1601 20141231 entry below for information about prerequisites and upgrading,
1602 if you are not already using 3.5.0 or higher.
1605 TI platform code switched to using vendor DTS files and this update
1606 may break existing systems running on Beaglebone, Beaglebone Black,
1609 - dtb files should be regenerated/reinstalled. Filenames are the
1610 same but content is different now
1611 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1612 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1613 addressing scheme is now pin 25 on /dev/gpioc3.
1614 - Pandaboard: /etc/ttys should be updated, serial console device is
1615 now /dev/ttyu2, not /dev/ttyu0
1618 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1619 If you need the GNU extension from groff soelim(1), install groff
1620 from package: pkg install groff, or via ports: textproc/groff.
1623 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1624 defined in symlink(7); previously symlinks were silently ignored.
1627 The const qualifier has been removed from iconv(3) to comply with
1628 POSIX. The ports tree is aware of this from r384038 onwards.
1631 Libraries specified by LIBADD in Makefiles must have a corresponding
1632 DPADD_<lib> variable to ensure correct dependencies. This is now
1633 enforced in src.libnames.mk.
1636 From legacy ata(4) driver was removed support for SATA controllers
1637 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1638 Kernel modules ataahci and ataadaptec were removed completely,
1639 replaced by ahci and mvs modules respectively.
1642 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1643 the 20141231 entry below for information about prerequisites and
1644 upgrading, if you are not already using 3.5.0 or higher.
1647 The 32-bit PowerPC kernel has been changed to a position-independent
1648 executable. This can only be booted with a version of loader(8)
1649 newer than January 31, 2015, so make sure to update both world and
1650 kernel before rebooting.
1653 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1654 but before r278950, the RNG was not seeded properly. Immediately
1655 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1656 ssh keys or openssl keys) that were generated w/ a kernel from that
1657 range. This does not affect programs that directly used /dev/random
1658 or /dev/urandom. All userland uses of arc4random(3) are affected.
1661 The autofs(4) ABI was changed in order to restore binary compatibility
1662 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1663 with the new kernel.
1666 The powerpc64 kernel has been changed to a position-independent
1667 executable. This can only be booted with a new version of loader(8),
1668 so make sure to update both world and kernel before rebooting.
1671 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1672 only release, no new features have been added. Please see the 20141231
1673 entry below for information about prerequisites and upgrading, if you
1674 are not already using 3.5.0.
1677 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1678 taken from the ELF Tool Chain project rather than GNU binutils. They
1679 should be drop-in replacements, with the addition of arm64 support.
1680 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1681 binutils tools, if necessary. See 20150805 for updated information.
1684 The default Unbound configuration now enables remote control
1685 using a local socket. Users who have already enabled the
1686 local_unbound service should regenerate their configuration
1687 by running "service local_unbound setup" as root.
1690 The GNU texinfo and GNU info pages have been removed.
1691 To be able to view GNU info pages please install texinfo from ports.
1694 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1696 As of this release, a prerequisite for building clang, llvm and lldb is
1697 a C++11 capable compiler and C++11 standard library. This means that to
1698 be able to successfully build the cross-tools stage of buildworld, with
1699 clang as the bootstrap compiler, your system compiler or cross compiler
1700 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1701 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1704 On any standard FreeBSD 10.x or 11.x installation, where clang and
1705 libc++ are on by default (that is, on x86 or arm), this should work out
1708 On 9.x installations where clang is enabled by default, e.g. on x86 and
1709 powerpc, libc++ will not be enabled by default, so libc++ should be
1710 built (with clang) and installed first. If both clang and libc++ are
1711 missing, build clang first, then use it to build libc++.
1713 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1714 the instructions for 9.x above.
1716 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1717 default, and do not build clang.
1719 Many embedded systems are resource constrained, and will not be able to
1720 build clang in a reasonable time, or in some cases at all. In those
1721 cases, cross building bootable systems on amd64 is a workaround.
1723 This new version of clang introduces a number of new warnings, of which
1724 the following are most likely to appear:
1728 This warns in two cases, for both C and C++:
1729 * When the code is trying to take the absolute value of an unsigned
1730 quantity, which is effectively a no-op, and almost never what was
1731 intended. The code should be fixed, if at all possible. If you are
1732 sure that the unsigned quantity can be safely cast to signed, without
1733 loss of information or undefined behavior, you can add an explicit
1734 cast, or disable the warning.
1736 * When the code is trying to take an absolute value, but the called
1737 abs() variant is for the wrong type, which can lead to truncation.
1738 If you want to disable the warning instead of fixing the code, please
1739 make sure that truncation will not occur, or it might lead to unwanted
1742 -Wtautological-undefined-compare and
1743 -Wundefined-bool-conversion
1745 These warn when C++ code is trying to compare 'this' against NULL, while
1746 'this' should never be NULL in well-defined C++ code. However, there is
1747 some legacy (pre C++11) code out there, which actively abuses this
1748 feature, which was less strictly defined in previous C++ versions.
1750 Squid and openjdk do this, for example. The warning can be turned off
1751 for C++98 and earlier, but compiling the code in C++11 mode might result
1752 in unexpected behavior; for example, the parts of the program that are
1753 unreachable could be optimized away.
1756 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1757 kernel sources have been removed. The .h files remain, since some
1758 utilities include them. This will need to be fixed later.
1759 If "mount -t oldnfs ..." is attempted, it will fail.
1760 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1761 the utilities will report errors.
1764 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1765 directories to top level SUBDIR variable when their parent
1766 directory is included in LOCAL_DIRS. Users with build systems with
1767 such hierarchies and without SUBDIR entries in the parent
1768 directory Makefiles should add them or add the directories to
1772 faith(4) and faithd(8) have been removed from the base system. Faith
1773 has been obsolete for a very long time.
1776 vt(4), the new console driver, is enabled by default. It brings
1777 support for Unicode and double-width characters, as well as
1778 support for UEFI and integration with the KMS kernel video
1781 You may need to update your console settings in /etc/rc.conf,
1782 most probably the keymap. During boot, /etc/rc.d/syscons will
1783 indicate what you need to do.
1785 vt(4) still has issues and lacks some features compared to
1786 syscons(4). See the wiki for up-to-date information:
1787 https://wiki.freebsd.org/Newcons
1789 If you want to keep using syscons(4), you can do so by adding
1790 the following line to /boot/loader.conf:
1794 pjdfstest has been integrated into kyua as an opt-in test suite.
1795 Please see share/doc/pjdfstest/README for more details on how to
1799 gperf has been removed from the base system for architectures
1800 that use clang. Ports that require gperf will obtain it from the
1804 pjdfstest has been moved from tools/regression/pjdfstest to
1808 At svn r271982, The default linux compat kernel ABI has been adjusted
1809 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1810 update. If you wish to continue using the linux-f10 compat ports,
1811 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1812 encouraged to update their linux-compat packages to linux-c6 during
1813 their next update cycle.
1816 The ofwfb driver, used to provide a graphics console on PowerPC when
1817 using vt(4), no longer allows mmap() of all physical memory. This
1818 will prevent Xorg on PowerPC with some ATI graphics cards from
1819 initializing properly unless x11-servers/xorg-server is updated to
1823 The xdev targets have been converted to using TARGET and
1824 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1827 The default unbound configuration has been modified to address
1828 issues with reverse lookups on networks that use private
1829 address ranges. If you use the local_unbound service, run
1830 "service local_unbound setup" as root to regenerate your
1831 configuration, then "service local_unbound reload" to load the
1835 The GNU texinfo and GNU info pages are not built and installed
1836 anymore, WITH_INFO knob has been added to allow to built and install
1838 UPDATE: see 20150102 entry on texinfo's removal
1841 The GNU readline library is now an INTERNALLIB - that is, it is
1842 statically linked into consumers (GDB and variants) in the base
1843 system, and the shared library is no longer installed. The
1844 devel/readline port is available for third party software that
1848 The Itanium architecture (ia64) has been removed from the list of
1849 known architectures. This is the first step in the removal of the
1853 Commit r268115 has added NFSv4.1 server support, merged from
1854 projects/nfsv4.1-server. Since this includes changes to the
1855 internal interfaces between the NFS related modules, a full
1856 build of the kernel and modules will be necessary.
1857 __FreeBSD_version has been bumped.
1860 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1861 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1862 which differs from the behaviour controlled by this knob.)
1865 Maximal length of the serial number in CTL was increased from 16 to
1866 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1867 and ctld, need to be rebuilt to work with a new kernel.
1870 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1871 1 respectively to match the upstream numbers. They were out of
1872 sync because, when they were originally added to FreeBSD, the
1873 upstream versions were not respected. These libraries are private
1874 and not yet built by default, so renumbering them should be a
1875 non-issue. However, unclean source trees will yield broken test
1876 programs once the operator executes "make delete-old-libs" after a
1877 "make installworld".
1879 Additionally, the atf-sh binary was made private by moving it into
1880 /usr/libexec/. Already-built shell test programs will keep the
1881 path to the old binary so they will break after "make delete-old"
1884 If you are using WITH_TESTS=yes (not the default), wipe the object
1885 tree and rebuild from scratch to prevent spurious test failures.
1886 This is only needed once: the misnumbered libraries and misplaced
1887 binaries have been added to OptionalObsoleteFiles.inc so they will
1888 be removed during a clean upgrade.
1891 Clang and llvm have been upgraded to 3.4.1 release.
1894 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1895 be removed to avoid issues in the future (and has been added to
1899 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1900 past, it affected all builds that used the bsd.*.mk files. The old
1901 behavior was a bug, but people may have relied upon it. To get this
1902 behavior back, you can .include /etc/src.conf from /etc/make.conf
1903 (which is still global and isn't changed). This also changes the
1904 behavior of incremental builds inside the tree of individual
1905 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1906 Although this has survived make universe and some upgrade scenarios,
1907 other upgrade scenarios may have broken. At least one form of
1908 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1909 as well... In cases where MAKESYSPATH isn't working with this
1910 setting, you'll need to set it to the full path to your tree.
1912 One side effect of all this cleaning up is that bsd.compiler.mk
1913 is no longer implicitly included by bsd.own.mk. If you wish to
1914 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1918 The lindev device has been removed since /dev/full has been made a
1919 standard device. __FreeBSD_version has been bumped.
1922 The knob WITHOUT_VI was added to the base system, which controls
1923 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1924 in order to reorder files share/termcap and didn't build ex(1) as a
1925 build tool, so building/installing with WITH_VI is highly advised for
1926 build hosts for older releases.
1928 This issue has been fixed in stable/9 and stable/10 in r277022 and
1929 r276991, respectively.
1932 The YES_HESIOD knob has been removed. It has been obsolete for
1933 a decade. Please move to using WITH_HESIOD instead or your builds
1934 will silently lack HESIOD.
1937 The uart(4) driver has been changed with respect to its handling
1938 of the low-level console. Previously the uart(4) driver prevented
1939 any process from changing the baudrate or the CLOCAL and HUPCL
1940 control flags. By removing the restrictions, operators can make
1941 changes to the serial console port without having to reboot.
1942 However, when getty(8) is started on the serial device that is
1943 associated with the low-level console, a misconfigured terminal
1944 line in /etc/ttys will now have a real impact.
1945 Before upgrading the kernel, make sure that /etc/ttys has the
1946 serial console device configured as 3wire without baudrate to
1947 preserve the previous behaviour. E.g:
1948 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1951 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1952 to improve performance. To re-enable it, if needed, run rpcbind
1953 with command line option -W.
1956 Switched back to the GPL dtc compiler due to updates in the upstream
1957 dts files not being supported by the BSDL dtc compiler. You will need
1958 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1959 may result while building dtb files during a kernel build if you fail
1960 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1963 Clang and llvm have been upgraded to 3.4 release.
1966 The nve(4) driver has been removed. Please use the nfe(4) driver
1967 for NVIDIA nForce MCP Ethernet adapters instead.
1970 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1971 This could cause certain C++ applications using shared libraries built
1972 against the previous version of libc++ to crash. The incompatibility
1973 has now been fixed, but any C++ applications or shared libraries built
1974 between r261283 and r261801 should be recompiled.
1977 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1978 capability mode support. Please note that enabling the feature in
1979 kernel is still highly recommended.
1982 OpenSSH is now built with sandbox support, and will use sandbox as
1983 the default privilege separation method. This requires Capsicum
1984 capability mode support in kernel.
1987 The libelf and libdwarf libraries have been updated to newer
1988 versions from upstream. Shared library version numbers for
1989 these two libraries were bumped. Any ports or binaries
1990 requiring these two libraries should be recompiled.
1991 __FreeBSD_version is bumped to 1100006.
1994 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1995 instead of providing an explicit one, this would prevent such
1996 Makefile from providing its own Kyuafile in the future during
1997 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1998 intervention is needed to clean an objdir if you use NO_CLEAN:
1999 # find /usr/obj -name Kyuafile | xargs rm -f
2002 The behavior of gss_pseudo_random() for the krb5 mechanism
2003 has changed, for applications requesting a longer random string
2004 than produced by the underlying enctype's pseudo-random() function.
2005 In particular, the random string produced from a session key of
2006 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
2007 be different at the 17th octet and later, after this change.
2008 The counter used in the PRF+ construction is now encoded as a
2009 big-endian integer in accordance with RFC 4402.
2010 __FreeBSD_version is bumped to 1100004.
2013 The WITHOUT_ATF build knob has been removed and its functionality
2014 has been subsumed into the more generic WITHOUT_TESTS. If you were
2015 using the former to disable the build of the ATF libraries, you
2016 should change your settings to use the latter.
2019 The default version of mtree is nmtree which is obtained from
2020 NetBSD. The output is generally the same, but may vary
2021 slightly. If you found you need identical output adding
2022 "-F freebsd9" to the command line should do the trick. For the
2023 time being, the old mtree is available as fmtree.
2026 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
2027 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
2028 1.1.4_8 and verify bsdyml not linked in, before running "make
2030 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
2032 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
2035 The stable/10 branch has been created in subversion from head
2042 Sometimes, obscure build problems are the result of environment
2043 poisoning. This can happen because the make utility reads its
2044 environment when searching for values for global variables. To run
2045 your build attempts in an "environmental clean room", prefix all make
2046 commands with 'env -i '. See the env(1) manual page for more details.
2047 Occasionally a build failure will occur with "make -j" due to a race
2048 condition. If this happens try building again without -j, and please
2049 report a bug if it happens consistently.
2051 When upgrading from one major version to another it is generally best to
2052 upgrade to the latest code in the currently installed branch first, then
2053 do an upgrade to the new branch. This is the best-tested upgrade path,
2054 and has the highest probability of being successful. Please try this
2055 approach if you encounter problems with a major version upgrade. Since
2056 the stable 4.x branch point, one has generally been able to upgrade from
2057 anywhere in the most recent stable branch to head / current (or even the
2058 last couple of stable branches). See the top of this file when there's
2061 The update process will emit an error on an attempt to perform a build
2062 or install from a FreeBSD version below the earliest supported version.
2063 When updating from an older version the update should be performed one
2064 major release at a time, including running `make delete-old` at each
2067 When upgrading a live system, having a root shell around before
2068 installing anything can help undo problems. Not having a root shell
2069 around can lead to problems if pam has changed too much from your
2070 starting point to allow continued authentication after the upgrade.
2072 This file should be read as a log of events. When a later event changes
2073 information of a prior event, the prior event should not be deleted.
2074 Instead, a pointer to the entry with the new information should be
2075 placed in the old entry. Readers of this file should also sanity check
2076 older entries before relying on them blindly. Authors of new entries
2077 should write them with this in mind.
2081 When upgrading the boot ZFS pool to a new version, always follow
2084 1.) recompile and reinstall the ZFS boot loader and boot block
2085 (this is part of "make buildworld" and "make installworld")
2087 2.) update the ZFS boot block on your boot drive
2089 The following example updates the ZFS boot block on the first
2090 partition (freebsd-boot) of a GPT partitioned drive ada0:
2091 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
2093 Non-boot pools do not need these updates.
2097 If you are updating from a prior version of FreeBSD (even one just
2098 a few days old), you should follow this procedure. It is the most
2099 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2101 make kernel-toolchain
2102 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2103 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2105 To test a kernel once
2106 ---------------------
2107 If you just want to boot a kernel once (because you are not sure
2108 if it works, or if you want to boot a known bad kernel to provide
2109 debugging information) run
2110 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2111 nextboot -k testkernel
2113 To rebuild everything and install it on the current system.
2114 -----------------------------------------------------------
2115 # Note: sometimes if you are running current you gotta do more than
2116 # is listed here if you are upgrading from a really old current.
2118 <make sure you have good level 0 dumps>
2120 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2121 make installkernel KERNCONF=YOUR_KERNEL_HERE
2123 <reboot in single user> [3]
2130 To cross-install current onto a separate partition
2131 --------------------------------------------------
2132 # In this approach we use a separate partition to hold
2133 # current's root, 'usr', and 'var' directories. A partition
2134 # holding "/", "/usr" and "/var" should be about 2GB in
2137 <make sure you have good level 0 dumps>
2140 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2141 <maybe newfs current's root partition>
2142 <mount current's root partition on directory ${CURRENT_ROOT}>
2143 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
2144 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2145 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2146 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2147 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2148 <reboot into current>
2149 <do a "native" rebuild/install as described in the previous section>
2150 <maybe install compatibility libraries from ports/misc/compat*>
2154 To upgrade in-place from stable to current
2155 ----------------------------------------------
2156 <make sure you have good level 0 dumps>
2158 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
2159 make installkernel KERNCONF=YOUR_KERNEL_HERE
2161 <reboot in single user> [3]
2168 Make sure that you've read the UPDATING file to understand the
2169 tweaks to various things you need. At this point in the life
2170 cycle of current, things change often and you are on your own
2171 to cope. The defaults can also change, so please read ALL of
2172 the UPDATING entries.
2174 Also, if you are tracking -current, you must be subscribed to
2175 freebsd-current@freebsd.org. Make sure that before you update
2176 your sources that you have read and understood all the recent
2177 messages there. If in doubt, please track -stable which has
2178 much fewer pitfalls.
2180 [1] If you have third party modules, such as vmware, you
2181 should disable them at this point so they don't crash your
2184 [3] From the bootblocks, boot -s, and then do
2188 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed
2189 cd src # full path to source
2190 adjkerntz -i # if CMOS is wall time
2191 Also, when doing a major release upgrade, it is required that
2192 you boot into single user mode to do the installworld.
2194 [4] Note: This step is non-optional. Failure to do this step
2195 can result in a significant reduction in the functionality of the
2196 system. Attempting to do it by hand is not recommended and those
2197 that pursue this avenue should read this file carefully, as well
2198 as the archives of freebsd-current and freebsd-hackers mailing lists
2199 for potential gotchas. The -U option is also useful to consider.
2200 See mergemaster(8) for more information.
2202 [5] Usually this step is a no-op. However, from time to time
2203 you may need to do this if you get unknown user in the following
2204 step. It never hurts to do it all the time. You may need to
2205 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2206 install) after the buildworld before this step if you last updated
2207 from current before 20130425 or from -stable before 20130430.
2209 [6] This only deletes old files and directories. Old libraries
2210 can be deleted by "make delete-old-libs", but you have to make
2211 sure that no program is using those libraries anymore.
2213 [8] The new kernel must be able to run existing binaries used by an
2214 installworld. When upgrading across major versions, the new kernel's
2215 configuration must include the correct COMPAT_FREEBSD<n> option for
2216 existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure
2217 to do so may leave you with a system that is hard to boot to recover. A
2218 GENERIC kernel will include suitable compatibility options to run
2219 binaries from older branches. Note that the ability to run binaries
2220 from unsupported branches is not guaranteed.
2222 Make sure that you merge any new devices from GENERIC since the
2223 last time you updated your kernel config file. Options also
2224 change over time, so you may need to adjust your custom kernels
2227 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2228 "?=" instead of the "=" assignment operator, so that buildworld can
2229 override the CPUTYPE if it needs to.
2231 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2232 not on the command line, or in /etc/make.conf. buildworld will
2233 warn if it is improperly defined.
2236 This file contains a list, in reverse chronological order, of major
2237 breakages in tracking -current. It is not guaranteed to be a complete
2238 list of such breakages, and only contains entries since September 23, 2011.
2239 If you need to see UPDATING entries from before that date, you will need
2240 to fetch an UPDATING file from an older FreeBSD release.
2242 Copyright information:
2244 Copyright 1998-2009 M. Warner Losh <imp@FreeBSD.org>
2246 Redistribution, publication, translation and use, with or without
2247 modification, in full or in part, in any form or format of this
2248 document are permitted without further permission from the author.
2250 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2251 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2252 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2253 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2254 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2255 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2256 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2257 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2258 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2259 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2260 POSSIBILITY OF SUCH DAMAGE.
2262 Contact Warner Losh if you have any questions about your use of