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