1 Updating Information for FreeBSD current users.
3 This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>.
4 See end of file for further details. For commonly done items, please see the
5 COMMON ITEMS: section later in the file. These instructions assume that you
6 basically know what you are doing. If not, then please consult the FreeBSD
9 https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
11 Items affecting the ports and packages system can be found in
12 /usr/ports/UPDATING. Please read that file before running portupgrade.
14 NOTE TO PEOPLE WHO THINK THAT FreeBSD 13.x IS SLOW:
15 FreeBSD 13.x has many debugging features turned on, in both the kernel
16 and userland. These features attempt to detect incorrect use of
17 system primitives, and encourage loud failure through extra sanity
18 checking and fail stop semantics. They also substantially impact
19 system performance. If you want to do performance measurement,
20 benchmarking, and optimization, you'll want to turn them off. This
21 includes various WITNESS- related kernel options, INVARIANTS, malloc
22 debugging flags in userland, and various verbose features in the
23 kernel. Many developers choose to disable these features on build
24 machines to maximize performance. (To completely disable malloc
25 debugging, define MALLOC_PRODUCTION in /etc/make.conf, or to merely
26 disable the most expensive debugging functionality run
27 "ln -s 'abort:false,junk:false' /etc/malloc.conf".)
30 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
31 been upgraded to 10.0.0. Please see the 20141231 entry below for
32 information about prerequisites and upgrading, if you are not already
33 using clang 3.5.0 or higher.
36 The size of struct vnet and the magic cookie have changed.
37 Users need to recompile libkvm and all modules using VIMAGE
38 together with their new kernel.
41 Defining the long deprecated NO_CTF, NO_DEBUG_FILES, NO_INSTALLLIB,
42 NO_MAN, NO_PROFILE, and NO_WARNS variables is now an error. Update
43 your Makefiles and scripts to define MK_<var>=no instead as required.
45 One exception to this is that program or library Makefiles should
46 define MAN to empty rather than setting MK_MAN=no.
49 Clang/LLVM is now the default compiler and LLD the default
53 make universe no longer uses GCC 4.2.1 on any architectures.
54 Architectures not supported by in-tree Clang/LLVM require an
55 external toolchain package.
58 GCC 4.2.1 is now not built by default, as part of the GCC 4.2.1
59 retirement plan. Specifically, the GCC, GCC_BOOTSTRAP, and GNUCXX
60 options default to off for all supported CPU architectures. As a
61 short-term transition aid they may be enabled via WITH_* options.
62 GCC 4.2.1 is expected to be removed from the tree on 2020-03-31.
65 Support for armv5 has been disconnected and is being removed. The
66 machine combination MACHINE=arm MACHINE_ARCH=arm is no longer valid.
67 You must now use a MACHINE_ARCH of armv6 or armv7. The default
68 MACHINE_ARCH for MACHINE=arm is now armv7.
71 Clang/LLVM is now the default compiler for all powerpc architectures.
72 LLD is now the default linker for powerpc64. The change for powerpc64
73 also includes a change to the ELFv2 ABI, incompatible with the existing
77 Kernel-loadable random(4) modules are no longer unloadable.
80 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
81 been upgraded to 9.0.1. Please see the 20141231 entry below for
82 information about prerequisites and upgrading, if you are not already
83 using clang 3.5.0 or higher.
86 r355677 has modified the internal interface used between the
87 NFS modules in the kernel. As such, they must all be upgraded
88 simultaneously. I will do a version bump for this.
91 The root certificates of the Mozilla CA Certificate Store have been
92 imported into the base system and can be managed with the certctl(8)
93 utility. If you have installed the security/ca_root_nss port or package
94 with the ETCSYMLINK option (the default), be advised that there may be
95 differences between those included in the port and those included in
96 base due to differences in nss branch used as well as general update
97 frequency. Note also that certctl(8) cannot manage certs in the
98 format used by the security/ca_root_nss port.
101 The amd(8) automount daemon has been disabled by default, and will be
102 removed in the future. As of FreeBSD 10.1 the autofs(5) is available
106 The nctgpio and wbwd drivers have been moved to the superio bus.
107 If you have one of these drivers in a kernel configuration, then
108 you should add device superio to it. If you use one of these drivers
109 as a module and you compile a custom set of modules, then you should
110 add superio to the set.
113 KPIs for network drivers to access interface addresses have changed.
114 Users need to recompile NIC driver modules together with kernel.
117 The net.link.tap.user_open sysctl no longer prevents user opening of
118 already created /dev/tapNN devices. Access is still controlled by
119 node permissions, just like tun devices. The net.link.tap.user_open
120 sysctl is now used only to allow users to perform devfs cloning of
121 tap devices, and the subsequent open may not succeed if the user is not
122 in the appropriate group. This sysctl may be deprecated/removed
123 completely in the future.
126 mips, powerpc, and sparc64 are no longer built as part of
127 universe / tinderbox unless MAKE_OBSOLETE_GCC is defined. If
128 not defined, mips, powerpc, and sparc64 builds will look for
129 the xtoolchain binaries and if installed use them for universe
130 builds. As llvm 9.0 becomes vetted for these architectures, they
131 will be removed from the list.
134 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
135 been upgraded to 9.0.0. Please see the 20141231 entry below for
136 information about prerequisites and upgrading, if you are not already
137 using clang 3.5.0 or higher.
140 The hpt27xx, hptmv, hptnr, and hptrr drivers have been removed from
141 GENERIC. They are available as modules and can be loaded by adding
142 to /boot/loader.conf hpt27xx_load="YES", hptmv_load="YES",
143 hptnr_load="YES", or hptrr_load="YES", respectively.
146 ntpd no longer by default locks its pages in memory, allowing them
147 to be paged out by the kernel. Use rlimit memlock to restore
148 historic BSD behaviour. For example, add "rlimit memlock 32"
149 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
152 Several of ping6's options have been renamed for better consistency
153 with ping. If you use any of -ARWXaghmrtwx, you must update your
154 scripts. See ping6(8) for details.
157 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
158 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
159 been removed from mount_fusefs(8). You can safely remove them from
160 your scripts, because they had no effect.
162 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
163 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
164 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
165 sysctls have been removed. If you felt the need to set any of them to
166 a non-default value, please tell asomers@FreeBSD.org why.
169 Default permissions on the /var/account/acct file (and copies of it
170 rotated by periodic daily scripts) are changed from 0644 to 0640
171 because the file contains sensitive information that should not be
172 world-readable. If the /var/account directory must be created by
173 rc.d/accounting, the mode used is now 0750. Admins who use the
174 accounting feature are encouraged to change the mode of an existing
175 /var/account directory to 0750 or 0700.
178 Entropy collection and the /dev/random device are no longer optional
179 components. The "device random" option has been removed.
180 Implementations of distilling algorithms can still be made loadable
181 with "options RANDOM_LOADABLE" (e.g., random_fortuna.ko).
184 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
185 been upgraded to 8.0.1. Please see the 20141231 entry below for
186 information about prerequisites and upgrading, if you are not already
187 using clang 3.5.0 or higher.
190 A fix was applied to i386 kernel modules to avoid panics with
191 dpcpu or vnet. Users need to recompile i386 kernel modules
192 having pcpu or vnet sections or they will refuse to load.
195 User-wired pages now have their own counter,
196 vm.stats.vm.v_user_wire_count. The vm.max_wired sysctl was renamed
197 to vm.max_user_wired and changed from an unsigned int to an unsigned
198 long. bhyve VMs wired with the -S are now subject to the user
199 wiring limit; the vm.max_user_wired sysctl may need to be tuned to
200 avoid running into the limit.
203 The IPSEC option has been removed from GENERIC. Users requiring
204 ipsec(4) must now load the ipsec(4) kernel module.
207 The tap(4) driver has been folded into tun(4), and the module has been
208 renamed to tuntap. You should update any kld_list="if_tap" or
209 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
210 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
211 module instead, and "device tap" or "device tun" entries in kernel
212 config files to select the tuntap device instead.
215 The following knobs have been added related to tradeoffs between
216 safe use of the random device and availability in the absence of
219 kern.random.initial_seeding.bypass_before_seeding: tunable; set
220 non-zero to bypass the random device prior to seeding, or zero to
221 block random requests until the random device is initially seeded.
222 For now, set to 1 (unsafe) by default to restore pre-r346250 boot
223 availability properties.
225 kern.random.initial_seeding.read_random_bypassed_before_seeding:
226 read-only diagnostic sysctl that is set when bypass is enabled and
227 read_random(9) is bypassed, to enable programmatic handling of this
228 initial condition, if desired.
230 kern.random.initial_seeding.arc4random_bypassed_before_seeding:
231 Similar to the above, but for for arc4random(9) initial seeding.
233 kern.random.initial_seeding.disable_bypass_warnings: tunable; set
234 non-zero to disable warnings in dmesg when the same conditions are
235 met as for the diagnostic sysctls above. Defaults to zero, i.e.,
236 produce warnings in dmesg when the conditions are met.
239 The loadable random module KPI has changed; the random_infra_init()
240 routine now requires a 3rd function pointer for a bool (*)(void)
241 method that returns true if the random device is seeded (and
242 therefore unblocked).
245 r345895 reverts r320698. This implies that an nfsuserd(8) daemon
246 built from head sources between r320757 (July 6, 2017) and
247 r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
248 is added to the command line.
249 nfsuserd daemons built from head sources that are post-r338192 are
250 not affected and should continue to work.
253 The fuse(4) module has been renamed to fusefs(4) for consistency with
254 other filesystems. You should update any kld_load="fuse" entries in
255 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
256 "options FUSE" entries in kernel config files.
259 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
260 8.0.0. Please see the 20141231 entry below for information about
261 prerequisites and upgrading, if you are not already using clang 3.5.0
265 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
266 compiled into your custom kernel, add 'device xz' statement to the
270 drm and drm2 have been removed from the tree. Please see
271 https://wiki.freebsd.org/Graphics for the latest information on
272 migrating to the drm ports.
275 Iflib is no longer unconditionally compiled into the kernel. Drivers
276 using iflib and statically compiled into the kernel, now require
277 the 'device iflib' config option. For the same drivers loaded as
278 modules on kernels not having 'device iflib', the iflib.ko module
279 is loaded automatically.
282 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
283 options no longer exist since r343219 and r343427 respectively;
284 nothing uses them, so they should be just removed from custom
288 r342635 changes the way efibootmgr(8) works by requiring users to add
289 the -b (bootnum) parameter for commands where the bootnum was previously
290 specified with each option. For example 'efibootmgr -B 0001' is now
291 'efibootmgr -B -b 0001'.
294 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
295 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
296 servers that have vfs.nfsd.nfs_privport set will only allow mounts
297 from clients using a reserved port#. Since both the FreeBSD and Linux
298 NFSv4 clients use reserved port#s by default, this should not affect
302 The XLP config has been removed. We can't support 64-bit atomics in this
303 kernel because it is running in 32-bit mode. XLP users must transition
304 to running a 64-bit kernel (XLP64 or XLPN32).
306 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
307 the preferred emulator today and we don't need two different ones.
309 The old sibyte / swarm / Broadcom BCM1250 support has been
310 removed from the mips port.
313 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
314 7.0.1. Please see the 20141231 entry below for information about
315 prerequisites and upgrading, if you are not already using clang 3.5.0
319 Remove the timed and netdate programs from the base tree. Setting
320 the time with these daemons has been obsolete for over a decade.
323 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
324 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
325 it produces broken binaries when ifuncs are in use. Users needing
326 GNU ld should install the binutils port or package.
329 The BSD crtbegin and crtend code has been enabled by default. It has
330 had extensive testing on amd64, arm64, and i386. It can be disabled
331 by building a world with -DWITHOUT_BSD_CRTBEGIN.
334 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
335 has been converted to a port (misc/ctm) and will be removed from
336 FreeBSD-13. It is available as a package (ctm) for all supported
340 The default newsyslog.conf(5) file has been changed to only include
341 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
342 the filenames end in '.conf' and do not begin with a '.'.
344 You should check the configuration files in these two directories match
345 this naming convention. You can verify which configuration files are
346 being included using the command:
350 Ports for the DRM modules have been simplified. Now, amd64 users should
351 just install the drm-kmod port. All others should install
354 Graphics hardware that's newer than about 2010 usually works with
355 drm-kmod. For hardware older than 2013, however, some users will need
356 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
357 than 2008 usually only works in drm-legacy-kmod. The graphics team can
358 only commit to hardware made since 2013 due to the complexity of the
359 market and difficulty to test all the older cards effectively. If you
360 have hardware supported by drm-kmod, you are strongly encouraged to use
361 that as you will get better support.
363 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
364 elsewhere, the drm and drm2 modules will be eliminated from the src base
365 soon (with a limited exception for arm). Please update to the package
366 asap and report any issues to x11@freebsd.org.
368 Generally, anybody using the drm*-kmod packages should add
369 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
370 cross-threading surprises, especially with automatic driver
371 loading from X11 startup. These will become the defaults in 13-current
375 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
376 custom kernel and module loading configuration files must be updated
377 accordingly. Moreover, interfaces previous presented as ixlvN to the
378 system are now exposed as iavfN and network configuration files must
379 be adjusted as necessary.
382 OpenSSL has been updated to version 1.1.1. This update included
383 additional various API changes throughout the base system. It is
384 important to rebuild third-party software after upgrading. The value
385 of __FreeBSD_version has been bumped accordingly.
388 The legacy DRM modules and drivers have now been added to the loader's
389 module blacklist, in favor of loading them with kld_list in rc.conf(5).
390 The module blacklist may be overridden with the loader.conf(5)
391 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
395 The cam(4) based nda(4) driver will be used over nvd(4) by default on
396 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
397 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
398 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
402 Reproducible build mode is now on by default, in preparation for
403 FreeBSD 12.0. This eliminates build metadata such as the user,
404 host, and time from the kernel (and uname), unless the working tree
405 corresponds to a modified checkout from a version control system.
406 The previous behavior can be obtained by setting the /etc/src.conf
407 knob WITHOUT_REPRODUCIBLE_BUILD.
410 The Yarrow CSPRNG has been removed from the kernel as it has not been
411 supported by its designers since at least 2003. Fortuna has been the
412 default since FreeBSD-11.
415 devctl freeze/thaw have gone into the tree, the rc scripts have been
416 updated to use them and devmatch has been changed. You should update
417 kernel, userland and rc scripts all at the same time.
420 The default interpreter has been switched from 4th to Lua.
421 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
422 interpreter. If you have custom FORTH code you will need to set
423 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
424 src.conf for the build. This will create default hard links between
425 loader and loader_4th instead of loader and loader_lua, the new default.
426 If you are using UEFI it will create the proper hard link to loader.efi.
428 bhyve uses userboot.so. It remains 4th-only until some issues are solved
429 regarding coexisting with multiple versions of FreeBSD are resolved.
432 ls(1) now respects the COLORTERM environment variable used in other
433 systems and software to indicate that a colored terminal is both
434 supported and desired. If ls(1) is suddenly emitting colors, they may
435 be disabled again by either removing the unwanted COLORTERM from your
436 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
437 may not be observed in a future release.
440 The default pager for most commands has been changed to "less". To
441 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
445 The jedec_ts(4) driver has been removed. A superset of its functionality
446 is available in the jedec_dimm(4) driver, and the manpage for that
447 driver includes migration instructions. If you have "device jedec_ts"
448 in your kernel configuration file, it must be removed.
451 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
452 This should have no effect if the kernel is booted via BIOS/legacy boot.
453 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
454 has a buggy firmware that prevents a successful boot due to use of
458 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
459 support has been removed from the tree. These ports were
460 obsolete and/or known to be broken for many years.
463 loader.efi has been augmented to participate more fully in the
464 UEFI boot manager protocol. loader.efi will now look at the
465 BootXXXX environment variable to determine if a specific kernel
466 or root partition was specified. XXXX is derived from BootCurrent.
467 efibootmgr(8) manages these standard UEFI variables.
470 zfsloader's functionality has now been folded into loader.
471 zfsloader is no longer necessary once you've updated your
472 boot blocks. For a transition period, we will install a
473 hardlink for zfsloader to loader to allow a smooth transition
474 until the boot blocks can be updated (hard link because old
475 zfs boot blocks don't understand symlinks).
478 ARM64 now have efifb support, if you want to have serial console
479 on your arm64 board when an screen is connected and the bootloader
480 setup a frame buffer for us to use, just add :
484 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
485 an screen connected as the firmware will setup a frame buffer are that
486 u-boot will expose as an EFI frame buffer.
489 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
490 or take steps to update /etc/passwd before doing installworld on
491 existing systems. Do not skip the "mergemaster -Fp" step before
492 installworld, as described in the update procedures near the bottom
493 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
494 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
495 the ntp config file contain options that change file/dir locations.
496 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
497 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
498 taking steps to ensure that all required files/dirs are accessible
502 Big endian arm support has been removed.
505 The static environment setup in kernel configs is no longer mutually
506 exclusive with the loader(8) environment by default. In order to
507 restore the previous default behavior of disabling the loader(8)
508 environment if a static environment is present, you must specify
509 loader_env.disabled=1 in the static environment.
512 The ABI of syscalls used by management tools like sockstat and
513 netstat has been broken to allow 32-bit binaries to work on
514 64-bit kernels without modification. These programs will need
515 to match the kernel in order to function. External programs may
516 require minor modifications to accommodate a change of type in
517 structures from pointers to 64-bit virtual addresses.
520 On i386 and amd64 atomics are now inlined. Out of tree modules using
521 atomics will need to be rebuilt.
524 The '%I' format in the kern.corefile sysctl limits the number of
525 core files that a process can generate to the number stored in the
526 debug.ncores sysctl. The '%I' format is replaced by the single digit
527 index. Previously, if all indexes were taken the kernel would overwrite
528 only a core file with the highest index in a filename.
529 Currently the system will create a new core file if there is a free
530 index or if all slots are taken it will overwrite the oldest one.
533 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
534 6.0.1. Please see the 20141231 entry below for information about
535 prerequisites and upgrading, if you are not already using clang 3.5.0
539 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
540 needed to be changed to work with it. This change was made with r335763
541 and requires a mergemaster / etcupdate / etc to update the installed
545 r334930 changed the interface between the NFS modules, so they all
546 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
549 As of r334391 lld is the default amd64 system linker; it is installed
550 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
554 The kernel / userland interface for devinfo changed, so you'll
555 need a new kernel and userland as a pair for it to work (rebuilding
556 lib/libdevinfo is all that's required). devinfo and devmatch will
557 not work, but everything else will when there's a mismatch.
560 The on-disk format for hwpmc callchain records has changed to include
561 threadid corresponding to a given record. This changes the field offsets
562 and thus requires that libpmcstat be rebuilt before using a kernel
566 The vxge(4) driver has been removed. This driver was introduced into
567 HEAD one week before the Exar left the Ethernet market and is not
568 known to be used. If you have device vxge in your kernel config file
572 The amd64 kernel now requires a ld that supports ifunc to produce a
573 working kernel, either lld or a newer binutils. lld is built by default
574 on amd64, and the 'buildkernel' target uses it automatically. However,
575 it is not the default linker, so building the kernel the traditional
576 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
577 binutils port/package). lld will soon be default, and this requirement
580 NOTE: As of r334391 lld is the default system linker on amd64, and no
581 workaround is necessary.
584 The nxge(4) driver has been removed. This driver was for PCI-X 10g
585 cards made by s2io/Neterion. The company was acquired by Exar and
586 no longer sells or supports Ethernet products. If you have device
587 nxge in your kernel config file it must be removed.
590 The tz database (tzdb) has been updated to 2018e. This version more
591 correctly models time stamps in time zones with negative DST such as
592 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
593 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
594 time zone abbreviations and the tm_isdst flag.
597 The ixgb(4) driver has been removed. This driver was for an early and
598 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
599 quickly shifted to the long lived ixgbe family. If you have device
600 ixgb in your kernel config file it must be removed.
603 The lmc(4) driver has been removed. This was a WAN interface
604 card that was already reportedly rare in 2003, and had an ambiguous
605 license. If you have device lmc in your kernel config file it must
609 Support for Arcnet networks has been removed. If you have device
610 arcnet or device cm in your kernel config file they must be
614 Support for FDDI networks has been removed. If you have device
615 fddi or device fpa in your kernel config file they must be
619 In addition to supporting RFC 3164 formatted messages, the
620 syslogd(8) service is now capable of parsing RFC 5424 formatted
621 log messages. The main benefit of using RFC 5424 is that clients
622 may now send log messages with timestamps containing year numbers,
623 microseconds and time zone offsets.
625 Similarly, the syslog(3) C library function has been altered to
626 send RFC 5424 formatted messages to the local system logging
627 daemon. On systems using syslogd(8), this change should have no
628 negative impact, as long as syslogd(8) and the C library are
629 updated at the same time. On systems using a different system
630 logging daemon, it may be necessary to make configuration
631 adjustments, depending on the software used.
633 When using syslog-ng, add the 'syslog-protocol' flag to local
634 input sources to enable parsing of RFC 5424 formatted messages:
637 unix-dgram("/var/run/log" flags(syslog-protocol));
640 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
641 of the 'imuxsock' module to let messages be processed by the
642 regular RFC 3164/5424 parsing pipeline:
644 module(load="imuxsock" SysSock.UseSpecialParser="off")
646 Do note that these changes only affect communication between local
647 applications and syslogd(8). The format that syslogd(8) uses to
648 store messages on disk or forward messages to other systems
649 remains unchanged. syslogd(8) still uses RFC 3164 for these
650 purposes. Options to customize this behaviour will be added in the
651 future. Utilities that process log files stored in /var/log are
652 thus expected to continue to function as before.
654 __FreeBSD_version has been incremented to 1200061 to denote this
658 Support for token ring networks has been removed. If you
659 have "device token" in your kernel config you should remove
660 it. No device drivers supported token ring.
663 makefs was modified to be able to tag ISO9660 El Torito boot catalog
664 entries as EFI instead of overloading the i386 tag as done previously.
665 The amd64 mkisoimages.sh script used to build amd64 ISO images for
666 release was updated to use this. This may mean that makefs must be
667 updated before "make cdrom" can be run in the release directory. This
668 should be as simple as:
670 $ cd $SRCDIR/usr.sbin/makefs
671 $ make depend all install
674 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
675 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
676 Co-existence for the transition period will come shortly. Booting is a
677 complex environment and test coverage for Lua-enabled loaders has been
678 thin, so it would be prudent to assume it might not work and make
679 provisions for backup boot methods.
682 devmatch functionality has been turned on in devd. It will automatically
683 load drivers for unattached devices. This may cause unexpected drivers
684 to be loaded. Please report any problems to current@ and
688 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
689 6.0.0. Please see the 20141231 entry below for information about
690 prerequisites and upgrading, if you are not already using clang 3.5.0
694 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
695 This means it is used to link the kernel and userland libraries and
696 executables, but is not yet installed as /usr/bin/ld by default.
698 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
699 WITHOUT_LLD_BOOTSTRAP=yes
702 On i386, pmtimer has been removed. Its functionality has been folded
703 into apm. It was a no-op on ACPI in current for a while now (but was
704 still needed on i386 in FreeBSD 11 and earlier). Users may need to
705 remove it from kernel config files.
708 The use of RSS hash from the network card aka flowid has been
709 disabled by default for lagg(4) as it's currently incompatible with
710 the lacp and loadbalance protocols.
712 This can be re-enabled by setting the following in loader.conf:
713 net.link.lagg.default_use_flowid="1"
716 The SW_WATCHDOG option is no longer necessary to enable the
717 hardclock-based software watchdog if no hardware watchdog is
718 configured. As before, SW_WATCHDOG will cause the software
719 watchdog to be enabled even if a hardware watchdog is configured.
722 r326887 fixes the issue described in the 20171214 UPDATING entry.
723 r326888 flips the switch back to building GELI support always.
726 r362593 broke ZFS + GELI support for reasons unknown. However,
727 it also broke ZFS support generally, so GELI has been turned off
728 by default as the lesser evil in r326857. If you boot off ZFS and/or
729 GELI, it might not be a good time to update.
732 PowerPC users must update loader(8) by rebuilding world before
733 installing a new kernel, as the protocol connecting them has
734 changed. Without the update, loader metadata will not be passed
735 successfully to the kernel and users will have to enter their
736 root partition at the kernel mountroot prompt to continue booting.
737 Newer versions of loader can boot old kernels without issue.
740 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
741 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
742 to WITH/OUT_LOADER_GELI.
745 The naive and non-compliant support of posix_fallocate(2) in ZFS
746 has been removed as of r325320. The system call now returns EINVAL
747 when used on a ZFS file. Although the new behavior complies with the
748 standard, some consumers are not prepared to cope with it.
749 One known victim is lld prior to r325420.
752 Building in a FreeBSD src checkout will automatically create object
753 directories now rather than store files in the current directory if
754 'make obj' was not ran. Calling 'make obj' is no longer necessary.
755 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
756 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
760 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
761 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
762 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
763 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
764 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
765 The UNIFIED_OBJDIR option is a transitional feature that will be
766 removed for 12.0 release; please migrate to the new format for any
767 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
768 than hardcoding paths.
771 The native-xtools target no longer installs the files by default to the
772 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
773 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
776 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
777 options are changing from controlling the build if defined / undefined
778 to controlling the build with explicit 'yes' or 'no' values. They will
779 shift to WITH/WITHOUT options to match other options in the system.
782 libstand has turned into a private library for sys/boot use only.
783 It is no longer supported as a public interface outside of sys/boot.
786 The arm port has split armv6 into armv6 and armv7. armv7 is now
787 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
788 and are running a kernel from before r324363, you will need to add
789 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
792 When building multiple kernels using KERNCONF, non-existent KERNCONF
793 files will produce an error and buildkernel will fail. Previously
794 missing KERNCONF files silently failed giving no indication as to
795 why, only to subsequently discover during installkernel that the
796 desired kernel was never built in the first place.
799 The default serial number format for CTL LUNs has changed. This will
800 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
801 or iSCSI clients care about their LUNs' serial numbers. Users who
802 require serial number stability should hardcode serial numbers in
806 For 32-bit arm compiled for hard-float support, soft-floating point
807 binaries now always get their shared libraries from
808 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
809 /usr/libsoft also existed). Only users with a hard-float ld.so, but
810 soft-float everything else should be affected.
813 The geli password typed at boot is now hidden. To restore the previous
814 behavior, see geli(8) for configuration options.
817 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
818 sysctl values. Minor nit, but requires a rebuild of both world/kernel
822 "make check" behavior (made in ^/head@r295380) has been changed to
823 execute from a limited sandbox, as opposed to executing from
827 - The "beforecheck" and "aftercheck" targets are now specified.
828 - ${CHECKDIR} (added in commit noted above) has been removed.
829 - Legacy behavior can be enabled by setting
830 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
832 If the limited sandbox mode is enabled, "make check" will execute
833 "make distribution", then install, execute the tests, and clean up the
834 sandbox if successful.
836 The "make distribution" and "make install" targets are typically run as
837 root to set appropriate permissions and ownership at installation time.
838 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
839 environment if executing "make check" with limited sandbox mode using
840 an unprivileged user.
843 Since the switch to GPT disk labels, fsck for UFS/FFS has been
844 unable to automatically find alternate superblocks. As of r322297,
845 the information needed to find alternate superblocks has been
846 moved to the end of the area reserved for the boot block.
847 Filesystems created with a newfs of this vintage or later
848 will create the recovery information. If you have a filesystem
849 created prior to this change and wish to have a recovery block
850 created for your filesystem, you can do so by running fsck in
851 foreground mode (i.e., do not use the -p or -y options). As it
852 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
853 to which you should answer yes.
856 As of r321665, an NFSv4 server configuration that services
857 Kerberos mounts or clients that do not support the uid/gid in
858 owner/owner_group string capability, must explicitly enable
859 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
860 machine's /etc/rc.conf file.
863 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
864 Please see the 20141231 entry below for information about prerequisites
865 and upgrading, if you are not already using clang 3.5.0 or higher.
868 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
869 r-commands (rlogin, rsh, etc.) to be built with the base system.
872 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
873 a very major ABI incompatible change, so users of FreeBSD/powerpc must
874 be careful when performing source upgrades. It is best to run
875 'make installworld' from an alternate root system, either a live
876 CD/memory stick, or a temporary root partition. Additionally, all ports
877 must be recompiled. powerpc64 is largely unaffected, except in the case
878 of 32-bit compatibility. All 32-bit binaries will be affected.
881 Forward compatibility for the "ino64" project have been committed. This
882 will allow most new binaries to run on older kernels in a limited
883 fashion. This prevents many of the common foot-shooting actions in the
884 upgrade as well as the limited ability to roll back the kernel across
885 the ino64 upgrade. Complicated use cases may not work properly, though
886 enough simpler ones work to allow recovery in most situations.
889 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
890 if you require the GPL compiler.
893 The internal ABI used for communication between the NFS kernel modules
894 was changed by r320085, so __FreeBSD_version was bumped to
895 ensure all the NFS related modules are updated together.
898 The ABI of struct event was changed by extending the data
899 member to 64bit and adding ext fields. For upgrade, same
900 precautions as for the entry 20170523 "ino64" must be
904 The GNU roff toolchain has been removed from base. To render manpages
905 which are not supported by mandoc(1), man(1) can fallback on GNU roff
906 from ports (and recommends to install it).
907 To render roff(7) documents, consider using GNU roff from ports or the
908 heirloom doctools roff toolchain from ports via pkg install groff or
909 via pkg install heirloom-doctools.
912 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
913 smaller runtime footprint builds. This is useful for embedded systems
914 which only require one chipset support.
916 If you load it as a module, make sure this is in /boot/loader.conf:
920 This will load the HAL, all chip/RF backends and if_ath_pci.
921 If you have if_ath_pci in /boot/loader.conf, ensure it is after
922 if_ath or it will not load any HAL chipset support.
924 If you want to selectively load things (eg on ye cheape ARM/MIPS
925 platforms where RAM is at a premium) you should:
928 * load the chip modules in question
929 * load ath_rate, ath_dfs
931 * load if_ath_pci and/or if_ath_ahb depending upon your particular
932 bus bind type - this is where probe/attach is done.
934 For further comments/feedback, poke adrian@ .
937 The "ino64" 64-bit inode project has been committed, which extends
938 a number of types to 64 bits. Upgrading in place requires care and
939 adherence to the documented upgrade procedure.
941 If using a custom kernel configuration ensure that the
942 COMPAT_FREEBSD11 option is included (as during the upgrade the
943 system will be running the ino64 kernel with the existing world).
945 For the safest in-place upgrade begin by removing previous build
946 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full
947 procedure documented below under the heading "To rebuild everything and
948 install it on the current system." Specifically, a reboot is required
949 after installing the new kernel before installing world. While an
950 installworld normally works by accident from multiuser after rebooting
951 the proper kernel, there are many cases where this will fail across this
952 upgrade and installworld from single user is required.
955 The NATM framework including the en(4), fatm(4), hatm(4), and
956 patm(4) devices has been removed. Consumers should plan a
957 migration before the end-of-life date for FreeBSD 11.
960 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
961 diff has not been implemented, if those are needed a newer version of
962 GNU diff is available via the diffutils package under the gdiff name.
965 As of r316810 for ipfilter, keep frags is no longer assumed when
966 keep state is specified in a rule. r316810 aligns ipfilter with
967 documentation in man pages separating keep frags from keep state.
968 This allows keep state to be specified without forcing keep frags
969 and allows keep frags to be specified independently of keep state.
970 To maintain previous behaviour, also specify keep frags with
971 keep state (as documented in ipf.conf.5).
974 arm64 builds now use the base system LLD 4.0.0 linker by default,
975 instead of requiring that the aarch64-binutils port or package be
976 installed. To continue using aarch64-binutils, set
977 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
980 The UDP optimization in entry 20160818 that added the sysctl
981 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
982 packets will no longer be treated as L3 broadcast packets.
985 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
986 use any explicitly assigned loopback address available in the jail
987 instead of using the first assigned address of the jail.
990 The ctl.ko module no longer implements the iSCSI target frontend:
991 cfiscsi.ko does instead.
993 If building cfiscsi.ko as a kernel module, the module can be loaded
994 via one of the following methods:
995 - `cfiscsi_load="YES"` in loader.conf(5).
996 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
997 - ctladm(8)/ctld(8), when compiled with iSCSI support
998 (`WITH_ISCSI=yes` in src.conf(5))
1000 Please see cfiscsi(4) for more details.
1003 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
1004 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
1005 same source (previously, the dependency of mmcsd.ko on mmc.ko was
1006 missing, but mmcsd.ko now will refuse to load if it is incompatible
1010 The syntax of ipfw(8) named states was changed to avoid ambiguity.
1011 If you have used named states in the firewall rules, you need to modify
1012 them after installworld and before rebooting. Now named states must
1013 be prefixed with colon.
1016 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
1017 removed as the userland we provide cannot use them. The KMS version
1018 (sys/dev/drm2) supports the same hardware.
1021 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
1022 Please see the 20141231 entry below for information about prerequisites
1023 and upgrading, if you are not already using clang 3.5.0 or higher.
1026 The code that provides support for ZFS .zfs/ directory functionality
1027 has been reimplemented. It's not possible now to create a snapshot
1028 by mkdir under .zfs/snapshot/. That should be the only user visible
1032 EISA bus support has been removed. The WITH_EISA option is no longer
1036 MCA bus support has been removed.
1039 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
1040 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
1043 The EM_MULTIQUEUE kernel configuration option is deprecated now that
1044 the em(4) driver conforms to iflib specifications.
1047 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
1048 IFLIB. If you have a custom kernel configuration that excludes em(4)
1049 but you use igb(4), you need to re-add em(4) to your custom
1053 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
1054 Please see the 20141231 entry below for information about prerequisites
1055 and upgrading, if you are not already using clang 3.5.0 or higher.
1058 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
1059 Please see the 20141231 entry below for information about prerequisites
1060 and upgrading, if you are not already using clang 3.5.0 or higher.
1063 The layout of the pmap structure has changed for powerpc to put the pmap
1064 statistics at the front for all CPU variations. libkvm(3) and all tools
1065 that link against it need to be recompiled.
1068 isl(4) and cyapa(4) drivers now require a new driver,
1069 chromebook_platform(4), to work properly on Chromebook-class hardware.
1070 On other types of hardware the drivers may need to be configured using
1071 device hints. Please see the corresponding manual pages for details.
1074 The urtwn(4) driver was merged into rtwn(4) and now consists of
1075 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
1077 Also, firmware for RTL8188CE was renamed due to possible name
1078 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
1081 GNU rcs has been removed from base. It is available as packages:
1082 - rcs: Latest GPLv3 GNU rcs version.
1083 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
1087 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
1088 modules now requires that the kernel configuration contain the
1089 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
1092 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
1093 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
1096 Relocatable object files with the extension of .So have been renamed
1097 to use an extension of .pico instead. The purpose of this change is
1098 to avoid a name clash with shared libraries on case-insensitive file
1099 systems. On those file systems, foo.So is the same file as foo.so.
1102 GNU rcs has been turned off by default. It can (temporarily) be built
1103 again by adding WITH_RCS knob in src.conf.
1104 Otherwise, GNU rcs is available from packages:
1105 - rcs: Latest GPLv3 GNU rcs version.
1106 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
1109 The backup_uses_rcs functionality has been removed from rc.subr.
1112 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
1113 two separate components, QUEUE_MACRO_DEBUG_TRACE and
1114 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
1115 QUEUE_MACRO_DEBUG behavior.
1118 r304787 changed some ioctl interfaces between the iSCSI userspace
1119 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1120 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1124 The UDP receive code has been updated to only treat incoming UDP
1125 packets that were addressed to an L2 broadcast address as L3
1126 broadcast packets. It is not expected that this will affect any
1127 standards-conforming UDP application. The new behaviour can be
1128 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1132 Remove the openbsd_poll system call.
1133 __FreeBSD_version has been bumped because of this.
1136 The stable/11 branch has been created from head@r302406.
1139 The libc stub for the pipe(2) system call has been replaced with
1140 a wrapper that calls the pipe2(2) system call and the pipe(2)
1141 system call is now only implemented by the kernels that include
1142 "options COMPAT_FREEBSD10" in their config file (this is the
1143 default). Users should ensure that this option is enabled in
1144 their kernel or upgrade userspace to r302092 before upgrading their
1148 CAM will now strip leading spaces from SCSI disks' serial numbers.
1149 This will affect users who create UFS filesystems on SCSI disks using
1150 those disk's diskid device nodes. For example, if /etc/fstab
1151 previously contained a line like
1152 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
1153 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
1154 transforms like gmirror may also be affected. ZFS users should
1158 The bitstring(3) API has been updated with new functionality and
1159 improved performance. But it is binary-incompatible with the old API.
1160 Objects built with the new headers may not be linked against objects
1161 built with the old headers.
1164 The brk and sbrk functions have been removed from libc on arm64.
1165 Binutils from ports has been updated to not link to these
1166 functions and should be updated to the latest version before
1167 installing a new libc.
1170 The armv6 port now defaults to hard float ABI. Limited support
1171 for running both hardfloat and soft float on the same system
1172 is available using the libraries installed with -DWITH_LIBSOFT.
1173 This has only been tested as an upgrade path for installworld
1174 and packages may fail or need manual intervention to run. New
1175 packages will be needed.
1177 To update an existing self-hosted armv6hf system, you must add
1178 TARGET_ARCH=armv6 on the make command line for both the build
1179 and the install steps.
1182 Kernel modules compiled outside of a kernel build now default to
1183 installing to /boot/modules instead of /boot/kernel. Many kernel
1184 modules built this way (such as those in ports) already overrode
1185 KMODDIR explicitly to install into /boot/modules. However,
1186 manually building and installing a module from /sys/modules will
1187 now install to /boot/modules instead of /boot/kernel.
1190 The CAM I/O scheduler has been committed to the kernel. There should be
1191 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1192 list of known rogues that claim support for this but actually corrupt
1193 data is believed to be complete, be on the lookout for data
1194 corruption. The known rogue list is believed to be complete:
1196 o Crucial MX100, M550 drives with MU01 firmware.
1197 o Micron M510 and M550 drives with MU01 firmware.
1198 o Micron M500 prior to MU07 firmware
1199 o Samsung 830, 840, and 850 all firmwares
1200 o FCCT M500 all firmwares
1202 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1203 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1204 updated firmware. Black listed drives will work correctly because these
1205 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1206 this list is the same as found in Linux, it's believed there are no
1207 other rogues in the market place. All other models from the above
1210 To be safe, if you are at all concerned, you can quirk each of your
1211 drives to prevent NCQ from being sent by setting:
1212 kern.cam.ada.X.quirks="0x2"
1213 in loader.conf. If the drive requires the 4k sector quirk, set the
1214 quirks entry to 0x3.
1217 The FAST_DEPEND build option has been removed and its functionality is
1218 now the one true way. The old mkdep(1) style of 'make depend' has
1219 been removed. See 20160311 for further details.
1222 Resource range types have grown from unsigned long to uintmax_t. All
1223 drivers, and anything using libdevinfo, need to be recompiled.
1226 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1227 builds. It no longer runs mkdep(1) during 'make depend', and the
1228 'make depend' stage can safely be skipped now as it is auto ran
1229 when building 'make all' and will generate all SRCS and DPSRCS before
1230 building anything else. Dependencies are gathered at compile time with
1231 -MF flags kept in separate .depend files per object file. Users should
1232 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1233 stale .depend files.
1236 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1237 kernel modules. Therefore, if you load any kernel modules at boot time,
1238 please install the boot loaders after you install the kernel, but before
1242 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1243 make installkernel KERNCONF=YOUR_KERNEL_HERE
1244 make -C sys/boot install
1245 <reboot in single user>
1247 Then follow the usual steps, described in the General Notes section,
1251 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1252 see the 20141231 entry below for information about prerequisites and
1253 upgrading, if you are not already using clang 3.5.0 or higher.
1256 The AIO subsystem is now a standard part of the kernel. The
1257 VFS_AIO kernel option and aio.ko kernel module have been removed.
1258 Due to stability concerns, asynchronous I/O requests are only
1259 permitted on sockets and raw disks by default. To enable
1260 asynchronous I/O requests on all file types, set the
1261 vfs.aio.enable_unsafe sysctl to a non-zero value.
1264 The ELF object manipulation tool objcopy is now provided by the
1265 ELF Tool Chain project rather than by GNU binutils. It should be a
1266 drop-in replacement, with the addition of arm64 support. The
1267 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1268 to obtain the GNU version if necessary.
1271 Building ZFS pools on top of zvols is prohibited by default. That
1272 feature has never worked safely; it's always been prone to deadlocks.
1273 Using a zvol as the backing store for a VM guest's virtual disk will
1274 still work, even if the guest is using ZFS. Legacy behavior can be
1275 restored by setting vfs.zfs.vol.recursive=1.
1278 The NONE and HPN patches has been removed from OpenSSH. They are
1279 still available in the security/openssh-portable port.
1282 With the addition of ypldap(8), a new _ypldap user is now required
1283 during installworld. "mergemaster -p" can be used to add the user
1284 prior to installworld, as documented in the handbook.
1287 The tftp loader (pxeboot) now uses the option root-path directive. As a
1288 consequence it no longer looks for a pxeboot.4th file on the tftp
1289 server. Instead it uses the regular /boot infrastructure as with the
1293 The code to start recording plug and play data into the modules has
1294 been committed. While the old tools will properly build a new kernel,
1295 a number of warnings about "unknown metadata record 4" will be produced
1296 for an older kldxref. To avoid such warnings, make sure to rebuild
1297 the kernel toolchain (or world). Make sure that you have r292078 or
1298 later when trying to build 292077 or later before rebuilding.
1301 Debug data files are now built by default with 'make buildworld' and
1302 installed with 'make installworld'. This facilitates debugging but
1303 requires more disk space both during the build and for the installed
1304 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1308 r291527 changed the internal interface between the nfsd.ko and
1309 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1310 __FreeBSD_version has been bumped because of this.
1313 Add support for unicode collation strings leads to a change of
1314 order of files listed by ls(1) for example. To get back to the old
1315 behaviour, set LC_COLLATE environment variable to "C".
1317 Databases administrators will need to reindex their databases given
1318 collation results will be different.
1320 Due to a bug in install(1) it is recommended to remove the ancient
1321 locales before running make installworld.
1323 rm -rf /usr/share/locale/*
1326 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1327 libcrypto.so.7 or libssl.so.7 must be recompiled.
1330 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1331 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1332 should be replaced with isp_2400 and isp_2500 modules respectively.
1335 The build previously allowed using 'make -n' to not recurse into
1336 sub-directories while showing what commands would be executed, and
1337 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1338 and 'make -N' will not.
1341 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1342 and etcupdate will now use this file. A custom sendmail.cf is now
1343 updated via this mechanism rather than via installworld. If you had
1344 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1345 want to remove the exclusion or change it to "always install".
1346 /etc/mail/sendmail.cf is now managed the same way regardless of
1347 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1348 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1351 Compatibility shims for legacy ATA device names have been removed.
1352 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1353 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1354 environment variables, /dev/ad* and /dev/ar* symbolic links.
1357 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1358 Please see the 20141231 entry below for information about prerequisites
1359 and upgrading, if you are not already using clang 3.5.0 or higher.
1362 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1363 and renamed from .symbols to .debug. This reduces the size requirements
1364 on the boot partition or file system and provides consistency with
1365 userland debug files.
1367 When using the supported kernel installation method the
1368 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1369 as is done with /boot/kernel.
1371 Developers wishing to maintain the historical behavior of installing
1372 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1375 The wireless drivers had undergone changes that remove the 'parent
1376 interface' from the ifconfig -l output. The rc.d network scripts
1377 used to check presence of a parent interface in the list, so old
1378 scripts would fail to start wireless networking. Thus, etcupdate(3)
1379 or mergemaster(8) run is required after kernel update, to update your
1380 rc.d scripts in /etc.
1383 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1384 These configurations are now automatically interpreted as
1385 'scrub fragment reassemble'.
1388 Kernel-loadable modules for the random(4) device are back. To use
1389 them, the kernel must have
1392 options RANDOM_LOADABLE
1394 kldload(8) can then be used to load random_fortuna.ko
1395 or random_yarrow.ko. Please note that due to the indirect
1396 function calls that the loadable modules need to provide,
1397 the build-in variants will be slightly more efficient.
1399 The random(4) kernel option RANDOM_DUMMY has been retired due to
1400 unpopularity. It was not all that useful anyway.
1403 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1404 Control over building the ELF Tool Chain tools is now provided by
1405 the WITHOUT_TOOLCHAIN knob.
1408 The polarity of Pulse Per Second (PPS) capture events with the
1409 uart(4) driver has been corrected. Prior to this change the PPS
1410 "assert" event corresponded to the trailing edge of a positive PPS
1411 pulse and the "clear" event was the leading edge of the next pulse.
1413 As the width of a PPS pulse in a typical GPS receiver is on the
1414 order of 1 millisecond, most users will not notice any significant
1415 difference with this change.
1417 Anyone who has compensated for the historical polarity reversal by
1418 configuring a negative offset equal to the pulse width will need to
1419 remove that workaround.
1422 The default group assigned to /dev/dri entries has been changed
1423 from 'wheel' to 'video' with the id of '44'. If you want to have
1424 access to the dri devices please add yourself to the video group
1427 # pw groupmod video -m $USER
1430 The menu.rc and loader.rc files will now be replaced during
1431 upgrades. Please migrate local changes to menu.rc.local and
1432 loader.rc.local instead.
1435 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1436 strings and strip have been removed. The src.conf(5) knob
1437 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1440 As ZFS requires more kernel stack pages than is the default on some
1441 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1442 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1444 Please consider using 'options KSTACK_PAGES=X' where X is greater
1445 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1448 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1449 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1450 default, i.e., they will not contain "::". For example, instead
1451 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1452 to have a more specific match, such as different map entries for
1453 IPv6:0:0 vs IPv6:0. This change requires that configuration
1454 data (including maps, files, classes, custom ruleset, etc.) must
1455 use the same format, so make certain such configuration data is
1456 upgrading. As a very simple check search for patterns like
1457 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1458 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1459 the cf option UseCompressedIPv6Addresses.
1462 The default kernel entropy-processing algorithm is now
1463 Fortuna, replacing Yarrow.
1465 Assuming you have 'device random' in your kernel config
1466 file, the configurations allow a kernel option to override
1467 this default. You may choose *ONE* of:
1469 options RANDOM_YARROW # Legacy /dev/random algorithm.
1470 options RANDOM_DUMMY # Blocking-only driver.
1472 If you have neither, you get Fortuna. For most people,
1473 read no further, Fortuna will give a /dev/random that works
1474 like it always used to, and the difference will be irrelevant.
1476 If you remove 'device random', you get *NO* kernel-processed
1477 entropy at all. This may be acceptable to folks building
1478 embedded systems, but has complications. Carry on reading,
1479 and it is assumed you know what you need.
1481 *PLEASE* read random(4) and random(9) if you are in the
1482 habit of tweaking kernel configs, and/or if you are a member
1483 of the embedded community, wanting specific and not-usual
1484 behaviour from your security subsystems.
1486 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1487 random', you will NOT have a functioning /dev/random, and
1488 many cryptographic features will not work, including SSH.
1489 You may also find strange behaviour from the random(3) set
1490 of library functions, in particular sranddev(3), srandomdev(3)
1491 and arc4random(3). The reason for this is that the KERN_ARND
1492 sysctl only returns entropy if it thinks it has some to
1493 share, and with RANDOM_DUMMY or no 'device random' this
1497 An additional fix for the issue described in the 20150614 sendmail
1498 entry below has been committed in revision 284717.
1501 FreeBSD's old make (fmake) has been removed from the system. It is
1502 available as the devel/fmake port or via pkg install fmake.
1505 The fix for the issue described in the 20150614 sendmail entry
1506 below has been committed in revision 284436. The work
1507 around described in that entry is no longer needed unless the
1508 default setting is overridden by a confDH_PARAMETERS configuration
1509 setting of '5' or pointing to a 512 bit DH parameter file.
1512 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1513 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1514 and devel/kyua to version 0.20+ and adjust any calling code to work
1515 with Kyuafile and kyua.
1518 The import of openssl to address the FreeBSD-SA-15:10.openssl
1519 security advisory includes a change which rejects handshakes
1520 with DH parameters below 768 bits. sendmail releases prior
1521 to 8.15.2 (not yet released), defaulted to a 512 bit
1522 DH parameter setting for client connections. To work around
1523 this interoperability, sendmail can be configured to use a
1524 2048 bit DH parameter by:
1526 1. Edit /etc/mail/`hostname`.mc
1527 2. If a setting for confDH_PARAMETERS does not exist or
1528 exists and is set to a string beginning with '5',
1529 replace it with '2'.
1530 3. If a setting for confDH_PARAMETERS exists and is set to
1531 a file path, create a new file with:
1532 openssl dhparam -out /path/to/file 2048
1533 4. Rebuild the .cf file:
1534 cd /etc/mail/; make; make install
1535 5. Restart sendmail:
1536 cd /etc/mail/; make restart
1538 A sendmail patch is coming, at which time this file will be
1542 Generation of legacy formatted entries have been disabled by default
1543 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1544 entries were converted to use the new format by default when the new,
1545 machine independent format have been added and supported since FreeBSD
1548 Please see the pwd_mkdb(8) manual page for further details.
1551 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1552 20141231 entry below for information about prerequisites and upgrading,
1553 if you are not already using 3.5.0 or higher.
1556 TI platform code switched to using vendor DTS files and this update
1557 may break existing systems running on Beaglebone, Beaglebone Black,
1560 - dtb files should be regenerated/reinstalled. Filenames are the
1561 same but content is different now
1562 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1563 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1564 addressing scheme is now pin 25 on /dev/gpioc3.
1565 - Pandaboard: /etc/ttys should be updated, serial console device is
1566 now /dev/ttyu2, not /dev/ttyu0
1569 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1570 If you need the GNU extension from groff soelim(1), install groff
1571 from package: pkg install groff, or via ports: textproc/groff.
1574 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1575 defined in symlink(7); previously symlinks were silently ignored.
1578 The const qualifier has been removed from iconv(3) to comply with
1579 POSIX. The ports tree is aware of this from r384038 onwards.
1582 Libraries specified by LIBADD in Makefiles must have a corresponding
1583 DPADD_<lib> variable to ensure correct dependencies. This is now
1584 enforced in src.libnames.mk.
1587 From legacy ata(4) driver was removed support for SATA controllers
1588 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1589 Kernel modules ataahci and ataadaptec were removed completely,
1590 replaced by ahci and mvs modules respectively.
1593 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1594 the 20141231 entry below for information about prerequisites and
1595 upgrading, if you are not already using 3.5.0 or higher.
1598 The 32-bit PowerPC kernel has been changed to a position-independent
1599 executable. This can only be booted with a version of loader(8)
1600 newer than January 31, 2015, so make sure to update both world and
1601 kernel before rebooting.
1604 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1605 but before r278950, the RNG was not seeded properly. Immediately
1606 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1607 ssh keys or openssl keys) that were generated w/ a kernel from that
1608 range. This does not affect programs that directly used /dev/random
1609 or /dev/urandom. All userland uses of arc4random(3) are affected.
1612 The autofs(4) ABI was changed in order to restore binary compatibility
1613 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1614 with the new kernel.
1617 The powerpc64 kernel has been changed to a position-independent
1618 executable. This can only be booted with a new version of loader(8),
1619 so make sure to update both world and kernel before rebooting.
1622 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1623 only release, no new features have been added. Please see the 20141231
1624 entry below for information about prerequisites and upgrading, if you
1625 are not already using 3.5.0.
1628 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1629 taken from the ELF Tool Chain project rather than GNU binutils. They
1630 should be drop-in replacements, with the addition of arm64 support.
1631 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1632 binutils tools, if necessary. See 20150805 for updated information.
1635 The default Unbound configuration now enables remote control
1636 using a local socket. Users who have already enabled the
1637 local_unbound service should regenerate their configuration
1638 by running "service local_unbound setup" as root.
1641 The GNU texinfo and GNU info pages have been removed.
1642 To be able to view GNU info pages please install texinfo from ports.
1645 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1647 As of this release, a prerequisite for building clang, llvm and lldb is
1648 a C++11 capable compiler and C++11 standard library. This means that to
1649 be able to successfully build the cross-tools stage of buildworld, with
1650 clang as the bootstrap compiler, your system compiler or cross compiler
1651 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1652 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1655 On any standard FreeBSD 10.x or 11.x installation, where clang and
1656 libc++ are on by default (that is, on x86 or arm), this should work out
1659 On 9.x installations where clang is enabled by default, e.g. on x86 and
1660 powerpc, libc++ will not be enabled by default, so libc++ should be
1661 built (with clang) and installed first. If both clang and libc++ are
1662 missing, build clang first, then use it to build libc++.
1664 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1665 the instructions for 9.x above.
1667 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1668 default, and do not build clang.
1670 Many embedded systems are resource constrained, and will not be able to
1671 build clang in a reasonable time, or in some cases at all. In those
1672 cases, cross building bootable systems on amd64 is a workaround.
1674 This new version of clang introduces a number of new warnings, of which
1675 the following are most likely to appear:
1679 This warns in two cases, for both C and C++:
1680 * When the code is trying to take the absolute value of an unsigned
1681 quantity, which is effectively a no-op, and almost never what was
1682 intended. The code should be fixed, if at all possible. If you are
1683 sure that the unsigned quantity can be safely cast to signed, without
1684 loss of information or undefined behavior, you can add an explicit
1685 cast, or disable the warning.
1687 * When the code is trying to take an absolute value, but the called
1688 abs() variant is for the wrong type, which can lead to truncation.
1689 If you want to disable the warning instead of fixing the code, please
1690 make sure that truncation will not occur, or it might lead to unwanted
1693 -Wtautological-undefined-compare and
1694 -Wundefined-bool-conversion
1696 These warn when C++ code is trying to compare 'this' against NULL, while
1697 'this' should never be NULL in well-defined C++ code. However, there is
1698 some legacy (pre C++11) code out there, which actively abuses this
1699 feature, which was less strictly defined in previous C++ versions.
1701 Squid and openjdk do this, for example. The warning can be turned off
1702 for C++98 and earlier, but compiling the code in C++11 mode might result
1703 in unexpected behavior; for example, the parts of the program that are
1704 unreachable could be optimized away.
1707 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1708 kernel sources have been removed. The .h files remain, since some
1709 utilities include them. This will need to be fixed later.
1710 If "mount -t oldnfs ..." is attempted, it will fail.
1711 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1712 the utilities will report errors.
1715 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1716 directories to top level SUBDIR variable when their parent
1717 directory is included in LOCAL_DIRS. Users with build systems with
1718 such hierarchies and without SUBDIR entries in the parent
1719 directory Makefiles should add them or add the directories to
1723 faith(4) and faithd(8) have been removed from the base system. Faith
1724 has been obsolete for a very long time.
1727 vt(4), the new console driver, is enabled by default. It brings
1728 support for Unicode and double-width characters, as well as
1729 support for UEFI and integration with the KMS kernel video
1732 You may need to update your console settings in /etc/rc.conf,
1733 most probably the keymap. During boot, /etc/rc.d/syscons will
1734 indicate what you need to do.
1736 vt(4) still has issues and lacks some features compared to
1737 syscons(4). See the wiki for up-to-date information:
1738 https://wiki.freebsd.org/Newcons
1740 If you want to keep using syscons(4), you can do so by adding
1741 the following line to /boot/loader.conf:
1745 pjdfstest has been integrated into kyua as an opt-in test suite.
1746 Please see share/doc/pjdfstest/README for more details on how to
1750 gperf has been removed from the base system for architectures
1751 that use clang. Ports that require gperf will obtain it from the
1755 pjdfstest has been moved from tools/regression/pjdfstest to
1759 At svn r271982, The default linux compat kernel ABI has been adjusted
1760 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1761 update. If you wish to continue using the linux-f10 compat ports,
1762 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1763 encouraged to update their linux-compat packages to linux-c6 during
1764 their next update cycle.
1767 The ofwfb driver, used to provide a graphics console on PowerPC when
1768 using vt(4), no longer allows mmap() of all physical memory. This
1769 will prevent Xorg on PowerPC with some ATI graphics cards from
1770 initializing properly unless x11-servers/xorg-server is updated to
1774 The xdev targets have been converted to using TARGET and
1775 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1778 The default unbound configuration has been modified to address
1779 issues with reverse lookups on networks that use private
1780 address ranges. If you use the local_unbound service, run
1781 "service local_unbound setup" as root to regenerate your
1782 configuration, then "service local_unbound reload" to load the
1786 The GNU texinfo and GNU info pages are not built and installed
1787 anymore, WITH_INFO knob has been added to allow to built and install
1789 UPDATE: see 20150102 entry on texinfo's removal
1792 The GNU readline library is now an INTERNALLIB - that is, it is
1793 statically linked into consumers (GDB and variants) in the base
1794 system, and the shared library is no longer installed. The
1795 devel/readline port is available for third party software that
1799 The Itanium architecture (ia64) has been removed from the list of
1800 known architectures. This is the first step in the removal of the
1804 Commit r268115 has added NFSv4.1 server support, merged from
1805 projects/nfsv4.1-server. Since this includes changes to the
1806 internal interfaces between the NFS related modules, a full
1807 build of the kernel and modules will be necessary.
1808 __FreeBSD_version has been bumped.
1811 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1812 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1813 which differs from the behaviour controlled by this knob.)
1816 Maximal length of the serial number in CTL was increased from 16 to
1817 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1818 and ctld, need to be rebuilt to work with a new kernel.
1821 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1822 1 respectively to match the upstream numbers. They were out of
1823 sync because, when they were originally added to FreeBSD, the
1824 upstream versions were not respected. These libraries are private
1825 and not yet built by default, so renumbering them should be a
1826 non-issue. However, unclean source trees will yield broken test
1827 programs once the operator executes "make delete-old-libs" after a
1828 "make installworld".
1830 Additionally, the atf-sh binary was made private by moving it into
1831 /usr/libexec/. Already-built shell test programs will keep the
1832 path to the old binary so they will break after "make delete-old"
1835 If you are using WITH_TESTS=yes (not the default), wipe the object
1836 tree and rebuild from scratch to prevent spurious test failures.
1837 This is only needed once: the misnumbered libraries and misplaced
1838 binaries have been added to OptionalObsoleteFiles.inc so they will
1839 be removed during a clean upgrade.
1842 Clang and llvm have been upgraded to 3.4.1 release.
1845 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1846 be removed to avoid issues in the future (and has been added to
1850 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1851 past, it affected all builds that used the bsd.*.mk files. The old
1852 behavior was a bug, but people may have relied upon it. To get this
1853 behavior back, you can .include /etc/src.conf from /etc/make.conf
1854 (which is still global and isn't changed). This also changes the
1855 behavior of incremental builds inside the tree of individual
1856 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1857 Although this has survived make universe and some upgrade scenarios,
1858 other upgrade scenarios may have broken. At least one form of
1859 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1860 as well... In cases where MAKESYSPATH isn't working with this
1861 setting, you'll need to set it to the full path to your tree.
1863 One side effect of all this cleaning up is that bsd.compiler.mk
1864 is no longer implicitly included by bsd.own.mk. If you wish to
1865 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1869 The lindev device has been removed since /dev/full has been made a
1870 standard device. __FreeBSD_version has been bumped.
1873 The knob WITHOUT_VI was added to the base system, which controls
1874 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1875 in order to reorder files share/termcap and didn't build ex(1) as a
1876 build tool, so building/installing with WITH_VI is highly advised for
1877 build hosts for older releases.
1879 This issue has been fixed in stable/9 and stable/10 in r277022 and
1880 r276991, respectively.
1883 The YES_HESIOD knob has been removed. It has been obsolete for
1884 a decade. Please move to using WITH_HESIOD instead or your builds
1885 will silently lack HESIOD.
1888 The uart(4) driver has been changed with respect to its handling
1889 of the low-level console. Previously the uart(4) driver prevented
1890 any process from changing the baudrate or the CLOCAL and HUPCL
1891 control flags. By removing the restrictions, operators can make
1892 changes to the serial console port without having to reboot.
1893 However, when getty(8) is started on the serial device that is
1894 associated with the low-level console, a misconfigured terminal
1895 line in /etc/ttys will now have a real impact.
1896 Before upgrading the kernel, make sure that /etc/ttys has the
1897 serial console device configured as 3wire without baudrate to
1898 preserve the previous behaviour. E.g:
1899 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1902 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1903 to improve performance. To re-enable it, if needed, run rpcbind
1904 with command line option -W.
1907 Switched back to the GPL dtc compiler due to updates in the upstream
1908 dts files not being supported by the BSDL dtc compiler. You will need
1909 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1910 may result while building dtb files during a kernel build if you fail
1911 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1914 Clang and llvm have been upgraded to 3.4 release.
1917 The nve(4) driver has been removed. Please use the nfe(4) driver
1918 for NVIDIA nForce MCP Ethernet adapters instead.
1921 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1922 This could cause certain C++ applications using shared libraries built
1923 against the previous version of libc++ to crash. The incompatibility
1924 has now been fixed, but any C++ applications or shared libraries built
1925 between r261283 and r261801 should be recompiled.
1928 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1929 capability mode support. Please note that enabling the feature in
1930 kernel is still highly recommended.
1933 OpenSSH is now built with sandbox support, and will use sandbox as
1934 the default privilege separation method. This requires Capsicum
1935 capability mode support in kernel.
1938 The libelf and libdwarf libraries have been updated to newer
1939 versions from upstream. Shared library version numbers for
1940 these two libraries were bumped. Any ports or binaries
1941 requiring these two libraries should be recompiled.
1942 __FreeBSD_version is bumped to 1100006.
1945 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1946 instead of providing an explicit one, this would prevent such
1947 Makefile from providing its own Kyuafile in the future during
1948 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1949 intervention is needed to clean an objdir if you use NO_CLEAN:
1950 # find /usr/obj -name Kyuafile | xargs rm -f
1953 The behavior of gss_pseudo_random() for the krb5 mechanism
1954 has changed, for applications requesting a longer random string
1955 than produced by the underlying enctype's pseudo-random() function.
1956 In particular, the random string produced from a session key of
1957 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1958 be different at the 17th octet and later, after this change.
1959 The counter used in the PRF+ construction is now encoded as a
1960 big-endian integer in accordance with RFC 4402.
1961 __FreeBSD_version is bumped to 1100004.
1964 The WITHOUT_ATF build knob has been removed and its functionality
1965 has been subsumed into the more generic WITHOUT_TESTS. If you were
1966 using the former to disable the build of the ATF libraries, you
1967 should change your settings to use the latter.
1970 The default version of mtree is nmtree which is obtained from
1971 NetBSD. The output is generally the same, but may vary
1972 slightly. If you found you need identical output adding
1973 "-F freebsd9" to the command line should do the trick. For the
1974 time being, the old mtree is available as fmtree.
1977 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1978 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1979 1.1.4_8 and verify bsdyml not linked in, before running "make
1981 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1983 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1986 The stable/10 branch has been created in subversion from head
1993 Sometimes, obscure build problems are the result of environment
1994 poisoning. This can happen because the make utility reads its
1995 environment when searching for values for global variables. To run
1996 your build attempts in an "environmental clean room", prefix all make
1997 commands with 'env -i '. See the env(1) manual page for more details.
1998 Occasionally a build failure will occur with "make -j" due to a race
1999 condition. If this happens try building again without -j, and please
2000 report a bug if it happens consistently.
2002 When upgrading from one major version to another it is generally best to
2003 upgrade to the latest code in the currently installed branch first, then
2004 do an upgrade to the new branch. This is the best-tested upgrade path,
2005 and has the highest probability of being successful. Please try this
2006 approach if you encounter problems with a major version upgrade. Since
2007 the stable 4.x branch point, one has generally been able to upgrade from
2008 anywhere in the most recent stable branch to head / current (or even the
2009 last couple of stable branches). See the top of this file when there's
2012 When upgrading a live system, having a root shell around before
2013 installing anything can help undo problems. Not having a root shell
2014 around can lead to problems if pam has changed too much from your
2015 starting point to allow continued authentication after the upgrade.
2017 This file should be read as a log of events. When a later event changes
2018 information of a prior event, the prior event should not be deleted.
2019 Instead, a pointer to the entry with the new information should be
2020 placed in the old entry. Readers of this file should also sanity check
2021 older entries before relying on them blindly. Authors of new entries
2022 should write them with this in mind.
2026 When upgrading the boot ZFS pool to a new version, always follow
2029 1.) recompile and reinstall the ZFS boot loader and boot block
2030 (this is part of "make buildworld" and "make installworld")
2032 2.) update the ZFS boot block on your boot drive
2034 The following example updates the ZFS boot block on the first
2035 partition (freebsd-boot) of a GPT partitioned drive ada0:
2036 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
2038 Non-boot pools do not need these updates.
2042 If you are updating from a prior version of FreeBSD (even one just
2043 a few days old), you should follow this procedure. It is the most
2044 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2046 make kernel-toolchain
2047 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2048 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2050 To test a kernel once
2051 ---------------------
2052 If you just want to boot a kernel once (because you are not sure
2053 if it works, or if you want to boot a known bad kernel to provide
2054 debugging information) run
2055 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2056 nextboot -k testkernel
2058 To rebuild everything and install it on the current system.
2059 -----------------------------------------------------------
2060 # Note: sometimes if you are running current you gotta do more than
2061 # is listed here if you are upgrading from a really old current.
2063 <make sure you have good level 0 dumps>
2065 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2066 make installkernel KERNCONF=YOUR_KERNEL_HERE
2068 <reboot in single user> [3]
2075 To cross-install current onto a separate partition
2076 --------------------------------------------------
2077 # In this approach we use a separate partition to hold
2078 # current's root, 'usr', and 'var' directories. A partition
2079 # holding "/", "/usr" and "/var" should be about 2GB in
2082 <make sure you have good level 0 dumps>
2085 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2086 <maybe newfs current's root partition>
2087 <mount current's root partition on directory ${CURRENT_ROOT}>
2088 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
2089 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2090 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2091 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2092 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2093 <reboot into current>
2094 <do a "native" rebuild/install as described in the previous section>
2095 <maybe install compatibility libraries from ports/misc/compat*>
2099 To upgrade in-place from stable to current
2100 ----------------------------------------------
2101 <make sure you have good level 0 dumps>
2103 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
2104 make installkernel KERNCONF=YOUR_KERNEL_HERE
2106 <reboot in single user> [3]
2113 Make sure that you've read the UPDATING file to understand the
2114 tweaks to various things you need. At this point in the life
2115 cycle of current, things change often and you are on your own
2116 to cope. The defaults can also change, so please read ALL of
2117 the UPDATING entries.
2119 Also, if you are tracking -current, you must be subscribed to
2120 freebsd-current@freebsd.org. Make sure that before you update
2121 your sources that you have read and understood all the recent
2122 messages there. If in doubt, please track -stable which has
2123 much fewer pitfalls.
2125 [1] If you have third party modules, such as vmware, you
2126 should disable them at this point so they don't crash your
2129 [3] From the bootblocks, boot -s, and then do
2133 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed
2134 cd src # full path to source
2135 adjkerntz -i # if CMOS is wall time
2136 Also, when doing a major release upgrade, it is required that
2137 you boot into single user mode to do the installworld.
2139 [4] Note: This step is non-optional. Failure to do this step
2140 can result in a significant reduction in the functionality of the
2141 system. Attempting to do it by hand is not recommended and those
2142 that pursue this avenue should read this file carefully, as well
2143 as the archives of freebsd-current and freebsd-hackers mailing lists
2144 for potential gotchas. The -U option is also useful to consider.
2145 See mergemaster(8) for more information.
2147 [5] Usually this step is a no-op. However, from time to time
2148 you may need to do this if you get unknown user in the following
2149 step. It never hurts to do it all the time. You may need to
2150 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2151 install) after the buildworld before this step if you last updated
2152 from current before 20130425 or from -stable before 20130430.
2154 [6] This only deletes old files and directories. Old libraries
2155 can be deleted by "make delete-old-libs", but you have to make
2156 sure that no program is using those libraries anymore.
2158 [8] The new kernel must be able to run existing binaries used by an
2159 installworld. When upgrading across major versions, the new kernel's
2160 configuration must include the correct COMPAT_FREEBSD<n> option for
2161 existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure
2162 to do so may leave you with a system that is hard to boot to recover. A
2163 GENERIC kernel will include suitable compatibility options to run
2164 binaries from older branches. Note that the ability to run binaries
2165 from unsupported branches is not guaranteed.
2167 Make sure that you merge any new devices from GENERIC since the
2168 last time you updated your kernel config file. Options also
2169 change over time, so you may need to adjust your custom kernels
2172 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2173 "?=" instead of the "=" assignment operator, so that buildworld can
2174 override the CPUTYPE if it needs to.
2176 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2177 not on the command line, or in /etc/make.conf. buildworld will
2178 warn if it is improperly defined.
2181 This file contains a list, in reverse chronological order, of major
2182 breakages in tracking -current. It is not guaranteed to be a complete
2183 list of such breakages, and only contains entries since September 23, 2011.
2184 If you need to see UPDATING entries from before that date, you will need
2185 to fetch an UPDATING file from an older FreeBSD release.
2187 Copyright information:
2189 Copyright 1998-2009 M. Warner Losh <imp@FreeBSD.org>
2191 Redistribution, publication, translation and use, with or without
2192 modification, in full or in part, in any form or format of this
2193 document are permitted without further permission from the author.
2195 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2196 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2197 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2198 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2199 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2200 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2201 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2202 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2203 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2204 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2205 POSSIBILITY OF SUCH DAMAGE.
2207 Contact Warner Losh if you have any questions about your use of