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