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