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 WITH_MALLOC_PRODUCTION in /etc/src.conf and rebuild
26 world, or to merely disable the most expensive debugging functionality
27 at runtime, run "ln -s 'abort:false,junk:false' /etc/malloc.conf".)
30 Obsolete in-tree GDB 6.1.1 has been removed. GDB (including kgdb)
31 may be installed from ports or packages.
34 ping6 has been merged into ping. It can now be called as "ping -6".
35 See ping(8) for details.
38 Default value of net.add_addr_allfibs has been changed to 0.
39 If you have multi-fib configuration and rely on existence of all
40 interface routes in every fib, you need to set the above sysctl to 1.
42 The internal pre-processor in the calendar(1) program has been
43 extended to support more C pre-processor commands (e.g. #ifdef, #else,
44 and #undef) and to detect unbalanced conditional statements.
45 Error messages have been extended to include the filename and line
46 number if processing stops to help fixing malformed data files.
49 All the data files for the calendar(1) program, except calendar.freebsd,
50 have been moved to the deskutils/calendar-data port, much like the
51 jewish calendar entries were moved to deskutils/hebcal years ago. After
52 make delete-old-files, you need to install it to retain full
53 functionality. calendar(1) will issue a reminder for files it can't
57 LINT files are no longer generated. We now include the relevant NOTES
58 files. Note: This may cause conflicts with updating in some cases.
59 find sys -name LINT\* -delete
60 is suggested across this commit to remove the generated LINT files.
62 If you have tried to update with generated files there, the svn
63 command you want to un-auger the tree is
66 and then do the above find from the top level. Substitute 'amd64'
67 above with where the error message indicates a conflict.
70 OpenZFS support has been integrated. Do not upgrade root pools until
71 the loader is updated to support zstd. Furthermore, we caution against
72 'zpool upgrade' for the next few weeks. The change should be transparent
73 unless you want to use new features.
75 Not all "NO_CLEAN" build scenarios work across these changes. Many
76 scenarios have been tested and fixed, but rebuilding kernels without
77 rebuilding world may fail.
79 The ZFS cache file has moved from /boot to /etc to match the OpenZFS
80 upstream default. A fallback to /boot has been added for mountroot.
82 Pool auto import behavior at boot has been moved from the kernel module
83 to an explicit "zpool import -a" in one of the rc scripts enabled by
84 zfs_enable=YES. This means your non-root zpools won't auto import until
85 you upgrade your /etc/rc.d files.
88 The resume code now notifies devd with the 'kernel' system
89 rather than the old 'kern' subsystem to be consistent with
90 other use. The old notification will be created as well, but
91 will be removed prior to FreeBSD 14.0.
94 r362275 changed the internal API between the kernel RPC and the
95 NFS modules. As such, all the modules must be recompiled from
99 r364330 modified the internal API used between the NFS modules.
100 As such, all the NFS modules must be re-compiled from sources.
103 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
104 been upgraded to 11.0.0. Please see the 20141231 entry below for
105 information about prerequisites and upgrading, if you are not already
106 using clang 3.5.0 or higher.
109 r364092 modified the internal ABI used between the kernel NFS
110 modules. As such, all of these modules need to be rebuilt
111 from sources, so a version bump was done.
114 Makefile.inc has been updated to work around the issue documented in
115 20200729. It was a case where the optimization of using symbolic links
116 to point to binaries created a situation where we'd run new binaries
117 with old libraries starting midway through the installworld process.
120 r363679 has redefined some undefined behavior in regcomp(3); notably,
121 extraneous escapes of most ordinary characters will no longer be
122 accepted. An exp-run has identified all of the problems with this in
123 ports, but other non-ports software may need extra escapes removed to
124 continue to function.
126 Because of this change, installworld may encounter the following error
127 from rtld: Undefined symbol "regcomp@FBSD_1.6" -- It is imperative that
128 you do not halt installworld. Instead, let it run to completion (whether
129 successful or not) and run installworld once more.
132 A new implementation of bc and dc has been imported in r362681. This
133 implementation corrects non-conformant behavior of the previous bc
134 and adds GNU bc compatible options. It offers a number of extensions,
135 is much faster on large values, and has support for message catalogs
136 (a number of languages are already supported, contributions of further
137 languages welcome). The option WITHOUT_GH_BC can be used to build the
138 world with the previous versions of bc and dc.
141 r362639 changed the internal API used between the NFS kernel modules.
142 As such, they all need to be rebuilt from sources.
145 r362158 changed the arguments for VFS_CHECKEXP(). As such, any
146 out of tree file systems need to be modified and rebuilt.
147 Also, any file systems that are modules must be rebuilt.
150 read(2) of a directory fd is now rejected by default. root may
151 re-enable it for system root only on non-ZFS filesystems with the
152 security.bsd.allow_read_dir sysctl(8) MIB if
153 security.bsd.suser_enabled=1.
155 It may be advised to setup aliases for grep to default to `-d skip` if
156 commonly non-recursively grepping a list that includes directories and
157 the potential for the resulting stderr output is not tolerable. Example
158 aliases are now installed, commented out, in /root/.cshrc and
162 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
163 been upgraded to 10.0.1. Please see the 20141231 entry below for
164 information about prerequisites and upgrading, if you are not already
165 using clang 3.5.0 or higher.
168 Support for obsolete compilers has been removed from the build system.
169 Clang 6 and GCC 6.4 are the minimum supported versions.
172 closefrom(2) has been moved under COMPAT12, and replaced in libc with a
173 stub that calls close_range(2). If using a custom kernel configuration,
174 you may want to ensure that the COMPAT_FREEBSD12 option is included, as
175 a slightly older -CURRENT userland and older FreeBSD userlands may not
176 be functional without closefrom(2).
179 Upstream DTS from Linux 5.6 was merged and they now have the SID
180 and THS (Secure ID controller and THermal Sensor) node present.
181 The DTB overlays have now been removed from the tree for the H3/H5 and
182 A64 SoCs and the aw_sid and aw_thermal driver have been updated to
183 deal with upstream DTS. If you are using those overlays you need to
184 remove them from loader.conf and update the DTBs on the FAT partition.
187 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
188 been upgraded to 10.0.0. Please see the 20141231 entry below for
189 information about prerequisites and upgrading, if you are not already
190 using clang 3.5.0 or higher.
193 The amd(8) automount daemon has been removed from the source tree.
194 As of FreeBSD 10.1 autofs(5) is the preferred tool for automounting.
195 amd is still available in the sysutils/am-utils port.
198 Removed brooktree driver (bktr.4) from the tree.
201 The WITH_GPL_DTC option has been removed. The BSD-licenced device tree
202 compiler in usr.bin/dtc is used on all architectures which use dtc, and
203 the GPL dtc is available (if needed) from the sysutils/dtc port.
206 The WITHOUT_LLVM_LIBUNWIND option has been removed. LLVM's libunwind
207 is used by all supported CPU architectures.
210 GCC 4.2.1 has been removed from the tree. The WITH_GCC,
211 WITH_GCC_BOOTSTRAP, and WITH_GNUCXX options are no longer available.
212 Users who wish to build FreeBSD with GCC must use the external toolchain
216 ncurses has been updated to a newer version (6.2-20200215). Given the ABI
217 has changed, users will have to rebuild all the ports that are linked to
221 The size of struct vnet and the magic cookie have changed.
222 Users need to recompile libkvm and all modules using VIMAGE
223 together with their new kernel.
226 Defining the long deprecated NO_CTF, NO_DEBUG_FILES, NO_INSTALLLIB,
227 NO_MAN, NO_PROFILE, and NO_WARNS variables is now an error. Update
228 your Makefiles and scripts to define MK_<var>=no instead as required.
230 One exception to this is that program or library Makefiles should
231 define MAN to empty rather than setting MK_MAN=no.
234 Clang/LLVM is now the default compiler and LLD the default
238 make universe no longer uses GCC 4.2.1 on any architectures.
239 Architectures not supported by in-tree Clang/LLVM require an
240 external toolchain package.
243 GCC 4.2.1 is now not built by default, as part of the GCC 4.2.1
244 retirement plan. Specifically, the GCC, GCC_BOOTSTRAP, and GNUCXX
245 options default to off for all supported CPU architectures. As a
246 short-term transition aid they may be enabled via WITH_* options.
247 GCC 4.2.1 is expected to be removed from the tree on 2020-03-31.
250 Support for armv5 has been disconnected and is being removed. The
251 machine combination MACHINE=arm MACHINE_ARCH=arm is no longer valid.
252 You must now use a MACHINE_ARCH of armv6 or armv7. The default
253 MACHINE_ARCH for MACHINE=arm is now armv7.
256 Clang/LLVM is now the default compiler for all powerpc architectures.
257 LLD is now the default linker for powerpc64. The change for powerpc64
258 also includes a change to the ELFv2 ABI, incompatible with the existing
262 Kernel-loadable random(4) modules are no longer unloadable.
265 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
266 been upgraded to 9.0.1. Please see the 20141231 entry below for
267 information about prerequisites and upgrading, if you are not already
268 using clang 3.5.0 or higher.
271 r355677 has modified the internal interface used between the
272 NFS modules in the kernel. As such, they must all be upgraded
273 simultaneously. I will do a version bump for this.
276 The root certificates of the Mozilla CA Certificate Store have been
277 imported into the base system and can be managed with the certctl(8)
278 utility. If you have installed the security/ca_root_nss port or package
279 with the ETCSYMLINK option (the default), be advised that there may be
280 differences between those included in the port and those included in
281 base due to differences in nss branch used as well as general update
282 frequency. Note also that certctl(8) cannot manage certs in the
283 format used by the security/ca_root_nss port.
286 The amd(8) automount daemon has been disabled by default, and will be
287 removed in the future. As of FreeBSD 10.1 the autofs(5) is available
291 The nctgpio and wbwd drivers have been moved to the superio bus.
292 If you have one of these drivers in a kernel configuration, then
293 you should add device superio to it. If you use one of these drivers
294 as a module and you compile a custom set of modules, then you should
295 add superio to the set.
298 KPIs for network drivers to access interface addresses have changed.
299 Users need to recompile NIC driver modules together with kernel.
302 The net.link.tap.user_open sysctl no longer prevents user opening of
303 already created /dev/tapNN devices. Access is still controlled by
304 node permissions, just like tun devices. The net.link.tap.user_open
305 sysctl is now used only to allow users to perform devfs cloning of
306 tap devices, and the subsequent open may not succeed if the user is not
307 in the appropriate group. This sysctl may be deprecated/removed
308 completely in the future.
311 mips, powerpc, and sparc64 are no longer built as part of
312 universe / tinderbox unless MAKE_OBSOLETE_GCC is defined. If
313 not defined, mips, powerpc, and sparc64 builds will look for
314 the xtoolchain binaries and if installed use them for universe
315 builds. As llvm 9.0 becomes vetted for these architectures, they
316 will be removed from the list.
319 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
320 been upgraded to 9.0.0. Please see the 20141231 entry below for
321 information about prerequisites and upgrading, if you are not already
322 using clang 3.5.0 or higher.
325 The hpt27xx, hptmv, hptnr, and hptrr drivers have been removed from
326 GENERIC. They are available as modules and can be loaded by adding
327 to /boot/loader.conf hpt27xx_load="YES", hptmv_load="YES",
328 hptnr_load="YES", or hptrr_load="YES", respectively.
331 ntpd no longer by default locks its pages in memory, allowing them
332 to be paged out by the kernel. Use rlimit memlock to restore
333 historic BSD behaviour. For example, add "rlimit memlock 32"
334 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
337 Several of ping6's options have been renamed for better consistency
338 with ping. If you use any of -ARWXaghmrtwx, you must update your
339 scripts. See ping6(8) for details.
342 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
343 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
344 been removed from mount_fusefs(8). You can safely remove them from
345 your scripts, because they had no effect.
347 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
348 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
349 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
350 sysctls have been removed. If you felt the need to set any of them to
351 a non-default value, please tell asomers@FreeBSD.org why.
354 Default permissions on the /var/account/acct file (and copies of it
355 rotated by periodic daily scripts) are changed from 0644 to 0640
356 because the file contains sensitive information that should not be
357 world-readable. If the /var/account directory must be created by
358 rc.d/accounting, the mode used is now 0750. Admins who use the
359 accounting feature are encouraged to change the mode of an existing
360 /var/account directory to 0750 or 0700.
363 Entropy collection and the /dev/random device are no longer optional
364 components. The "device random" option has been removed.
365 Implementations of distilling algorithms can still be made loadable
366 with "options RANDOM_LOADABLE" (e.g., random_fortuna.ko).
369 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
370 been upgraded to 8.0.1. Please see the 20141231 entry below for
371 information about prerequisites and upgrading, if you are not already
372 using clang 3.5.0 or higher.
375 A fix was applied to i386 kernel modules to avoid panics with
376 dpcpu or vnet. Users need to recompile i386 kernel modules
377 having pcpu or vnet sections or they will refuse to load.
380 User-wired pages now have their own counter,
381 vm.stats.vm.v_user_wire_count. The vm.max_wired sysctl was renamed
382 to vm.max_user_wired and changed from an unsigned int to an unsigned
383 long. bhyve VMs wired with the -S are now subject to the user
384 wiring limit; the vm.max_user_wired sysctl may need to be tuned to
385 avoid running into the limit.
388 The IPSEC option has been removed from GENERIC. Users requiring
389 ipsec(4) must now load the ipsec(4) kernel module.
392 The tap(4) driver has been folded into tun(4), and the module has been
393 renamed to tuntap. You should update any kld_list="if_tap" or
394 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
395 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
396 module instead, and "device tap" or "device tun" entries in kernel
397 config files to select the tuntap device instead.
400 The following knobs have been added related to tradeoffs between
401 safe use of the random device and availability in the absence of
404 kern.random.initial_seeding.bypass_before_seeding: tunable; set
405 non-zero to bypass the random device prior to seeding, or zero to
406 block random requests until the random device is initially seeded.
407 For now, set to 1 (unsafe) by default to restore pre-r346250 boot
408 availability properties.
410 kern.random.initial_seeding.read_random_bypassed_before_seeding:
411 read-only diagnostic sysctl that is set when bypass is enabled and
412 read_random(9) is bypassed, to enable programmatic handling of this
413 initial condition, if desired.
415 kern.random.initial_seeding.arc4random_bypassed_before_seeding:
416 Similar to the above, but for for arc4random(9) initial seeding.
418 kern.random.initial_seeding.disable_bypass_warnings: tunable; set
419 non-zero to disable warnings in dmesg when the same conditions are
420 met as for the diagnostic sysctls above. Defaults to zero, i.e.,
421 produce warnings in dmesg when the conditions are met.
424 The loadable random module KPI has changed; the random_infra_init()
425 routine now requires a 3rd function pointer for a bool (*)(void)
426 method that returns true if the random device is seeded (and
427 therefore unblocked).
430 r345895 reverts r320698. This implies that an nfsuserd(8) daemon
431 built from head sources between r320757 (July 6, 2017) and
432 r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
433 is added to the command line.
434 nfsuserd daemons built from head sources that are post-r338192 are
435 not affected and should continue to work.
438 The fuse(4) module has been renamed to fusefs(4) for consistency with
439 other filesystems. You should update any kld_load="fuse" entries in
440 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
441 "options FUSE" entries in kernel config files.
444 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
445 8.0.0. Please see the 20141231 entry below for information about
446 prerequisites and upgrading, if you are not already using clang 3.5.0
450 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
451 compiled into your custom kernel, add 'device xz' statement to the
455 drm and drm2 have been removed from the tree. Please see
456 https://wiki.freebsd.org/Graphics for the latest information on
457 migrating to the drm ports.
460 Iflib is no longer unconditionally compiled into the kernel. Drivers
461 using iflib and statically compiled into the kernel, now require
462 the 'device iflib' config option. For the same drivers loaded as
463 modules on kernels not having 'device iflib', the iflib.ko module
464 is loaded automatically.
467 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
468 options no longer exist since r343219 and r343427 respectively;
469 nothing uses them, so they should be just removed from custom
473 r342635 changes the way efibootmgr(8) works by requiring users to add
474 the -b (bootnum) parameter for commands where the bootnum was previously
475 specified with each option. For example 'efibootmgr -B 0001' is now
476 'efibootmgr -B -b 0001'.
479 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
480 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
481 servers that have vfs.nfsd.nfs_privport set will only allow mounts
482 from clients using a reserved port#. Since both the FreeBSD and Linux
483 NFSv4 clients use reserved port#s by default, this should not affect
487 The XLP config has been removed. We can't support 64-bit atomics in this
488 kernel because it is running in 32-bit mode. XLP users must transition
489 to running a 64-bit kernel (XLP64 or XLPN32).
491 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
492 the preferred emulator today and we don't need two different ones.
494 The old sibyte / swarm / Broadcom BCM1250 support has been
495 removed from the mips port.
498 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
499 7.0.1. Please see the 20141231 entry below for information about
500 prerequisites and upgrading, if you are not already using clang 3.5.0
504 Remove the timed and netdate programs from the base tree. Setting
505 the time with these daemons has been obsolete for over a decade.
508 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
509 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
510 it produces broken binaries when ifuncs are in use. Users needing
511 GNU ld should install the binutils port or package.
514 The BSD crtbegin and crtend code has been enabled by default. It has
515 had extensive testing on amd64, arm64, and i386. It can be disabled
516 by building a world with -DWITHOUT_BSD_CRTBEGIN.
519 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
520 has been converted to a port (misc/ctm) and will be removed from
521 FreeBSD-13. It is available as a package (ctm) for all supported
525 The default newsyslog.conf(5) file has been changed to only include
526 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
527 the filenames end in '.conf' and do not begin with a '.'.
529 You should check the configuration files in these two directories match
530 this naming convention. You can verify which configuration files are
531 being included using the command:
535 Ports for the DRM modules have been simplified. Now, amd64 users should
536 just install the drm-kmod port. All others should install
539 Graphics hardware that's newer than about 2010 usually works with
540 drm-kmod. For hardware older than 2013, however, some users will need
541 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
542 than 2008 usually only works in drm-legacy-kmod. The graphics team can
543 only commit to hardware made since 2013 due to the complexity of the
544 market and difficulty to test all the older cards effectively. If you
545 have hardware supported by drm-kmod, you are strongly encouraged to use
546 that as you will get better support.
548 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
549 elsewhere, the drm and drm2 modules will be eliminated from the src base
550 soon (with a limited exception for arm). Please update to the package
551 asap and report any issues to x11@freebsd.org.
553 Generally, anybody using the drm*-kmod packages should add
554 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
555 cross-threading surprises, especially with automatic driver
556 loading from X11 startup. These will become the defaults in 13-current
560 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
561 custom kernel and module loading configuration files must be updated
562 accordingly. Moreover, interfaces previous presented as ixlvN to the
563 system are now exposed as iavfN and network configuration files must
564 be adjusted as necessary.
567 OpenSSL has been updated to version 1.1.1. This update included
568 additional various API changes throughout the base system. It is
569 important to rebuild third-party software after upgrading. The value
570 of __FreeBSD_version has been bumped accordingly.
573 The legacy DRM modules and drivers have now been added to the loader's
574 module blacklist, in favor of loading them with kld_list in rc.conf(5).
575 The module blacklist may be overridden with the loader.conf(5)
576 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
580 The cam(4) based nda(4) driver will be used over nvd(4) by default on
581 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
582 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
583 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
587 Reproducible build mode is now on by default, in preparation for
588 FreeBSD 12.0. This eliminates build metadata such as the user,
589 host, and time from the kernel (and uname), unless the working tree
590 corresponds to a modified checkout from a version control system.
591 The previous behavior can be obtained by setting the /etc/src.conf
592 knob WITHOUT_REPRODUCIBLE_BUILD.
595 The Yarrow CSPRNG has been removed from the kernel as it has not been
596 supported by its designers since at least 2003. Fortuna has been the
597 default since FreeBSD-11.
600 devctl freeze/thaw have gone into the tree, the rc scripts have been
601 updated to use them and devmatch has been changed. You should update
602 kernel, userland and rc scripts all at the same time.
605 The default interpreter has been switched from 4th to Lua.
606 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
607 interpreter. If you have custom FORTH code you will need to set
608 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
609 src.conf for the build. This will create default hard links between
610 loader and loader_4th instead of loader and loader_lua, the new default.
611 If you are using UEFI it will create the proper hard link to loader.efi.
613 bhyve uses userboot.so. It remains 4th-only until some issues are solved
614 regarding coexisting with multiple versions of FreeBSD are resolved.
617 ls(1) now respects the COLORTERM environment variable used in other
618 systems and software to indicate that a colored terminal is both
619 supported and desired. If ls(1) is suddenly emitting colors, they may
620 be disabled again by either removing the unwanted COLORTERM from your
621 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
622 may not be observed in a future release.
625 The default pager for most commands has been changed to "less". To
626 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
630 The jedec_ts(4) driver has been removed. A superset of its functionality
631 is available in the jedec_dimm(4) driver, and the manpage for that
632 driver includes migration instructions. If you have "device jedec_ts"
633 in your kernel configuration file, it must be removed.
636 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
637 This should have no effect if the kernel is booted via BIOS/legacy boot.
638 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
639 has a buggy firmware that prevents a successful boot due to use of
643 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
644 support has been removed from the tree. These ports were
645 obsolete and/or known to be broken for many years.
648 loader.efi has been augmented to participate more fully in the
649 UEFI boot manager protocol. loader.efi will now look at the
650 BootXXXX environment variable to determine if a specific kernel
651 or root partition was specified. XXXX is derived from BootCurrent.
652 efibootmgr(8) manages these standard UEFI variables.
655 zfsloader's functionality has now been folded into loader.
656 zfsloader is no longer necessary once you've updated your
657 boot blocks. For a transition period, we will install a
658 hardlink for zfsloader to loader to allow a smooth transition
659 until the boot blocks can be updated (hard link because old
660 zfs boot blocks don't understand symlinks).
663 ARM64 now have efifb support, if you want to have serial console
664 on your arm64 board when an screen is connected and the bootloader
665 setup a frame buffer for us to use, just add :
669 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
670 an screen connected as the firmware will setup a frame buffer are that
671 u-boot will expose as an EFI frame buffer.
674 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
675 or take steps to update /etc/passwd before doing installworld on
676 existing systems. Do not skip the "mergemaster -Fp" step before
677 installworld, as described in the update procedures near the bottom
678 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
679 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
680 the ntp config file contain options that change file/dir locations.
681 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
682 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
683 taking steps to ensure that all required files/dirs are accessible
687 Big endian arm support has been removed.
690 The static environment setup in kernel configs is no longer mutually
691 exclusive with the loader(8) environment by default. In order to
692 restore the previous default behavior of disabling the loader(8)
693 environment if a static environment is present, you must specify
694 loader_env.disabled=1 in the static environment.
697 The ABI of syscalls used by management tools like sockstat and
698 netstat has been broken to allow 32-bit binaries to work on
699 64-bit kernels without modification. These programs will need
700 to match the kernel in order to function. External programs may
701 require minor modifications to accommodate a change of type in
702 structures from pointers to 64-bit virtual addresses.
705 On i386 and amd64 atomics are now inlined. Out of tree modules using
706 atomics will need to be rebuilt.
709 The '%I' format in the kern.corefile sysctl limits the number of
710 core files that a process can generate to the number stored in the
711 debug.ncores sysctl. The '%I' format is replaced by the single digit
712 index. Previously, if all indexes were taken the kernel would overwrite
713 only a core file with the highest index in a filename.
714 Currently the system will create a new core file if there is a free
715 index or if all slots are taken it will overwrite the oldest one.
718 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
719 6.0.1. Please see the 20141231 entry below for information about
720 prerequisites and upgrading, if you are not already using clang 3.5.0
724 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
725 needed to be changed to work with it. This change was made with r335763
726 and requires a mergemaster / etcupdate / etc to update the installed
730 r334930 changed the interface between the NFS modules, so they all
731 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
734 As of r334391 lld is the default amd64 system linker; it is installed
735 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
739 The kernel / userland interface for devinfo changed, so you'll
740 need a new kernel and userland as a pair for it to work (rebuilding
741 lib/libdevinfo is all that's required). devinfo and devmatch will
742 not work, but everything else will when there's a mismatch.
745 The on-disk format for hwpmc callchain records has changed to include
746 threadid corresponding to a given record. This changes the field offsets
747 and thus requires that libpmcstat be rebuilt before using a kernel
751 The vxge(4) driver has been removed. This driver was introduced into
752 HEAD one week before the Exar left the Ethernet market and is not
753 known to be used. If you have device vxge in your kernel config file
757 The amd64 kernel now requires a ld that supports ifunc to produce a
758 working kernel, either lld or a newer binutils. lld is built by default
759 on amd64, and the 'buildkernel' target uses it automatically. However,
760 it is not the default linker, so building the kernel the traditional
761 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
762 binutils port/package). lld will soon be default, and this requirement
765 NOTE: As of r334391 lld is the default system linker on amd64, and no
766 workaround is necessary.
769 The nxge(4) driver has been removed. This driver was for PCI-X 10g
770 cards made by s2io/Neterion. The company was acquired by Exar and
771 no longer sells or supports Ethernet products. If you have device
772 nxge in your kernel config file it must be removed.
775 The tz database (tzdb) has been updated to 2018e. This version more
776 correctly models time stamps in time zones with negative DST such as
777 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
778 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
779 time zone abbreviations and the tm_isdst flag.
782 The ixgb(4) driver has been removed. This driver was for an early and
783 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
784 quickly shifted to the long lived ixgbe family. If you have device
785 ixgb in your kernel config file it must be removed.
788 The lmc(4) driver has been removed. This was a WAN interface
789 card that was already reportedly rare in 2003, and had an ambiguous
790 license. If you have device lmc in your kernel config file it must
794 Support for Arcnet networks has been removed. If you have device
795 arcnet or device cm in your kernel config file they must be
799 Support for FDDI networks has been removed. If you have device
800 fddi or device fpa in your kernel config file they must be
804 In addition to supporting RFC 3164 formatted messages, the
805 syslogd(8) service is now capable of parsing RFC 5424 formatted
806 log messages. The main benefit of using RFC 5424 is that clients
807 may now send log messages with timestamps containing year numbers,
808 microseconds and time zone offsets.
810 Similarly, the syslog(3) C library function has been altered to
811 send RFC 5424 formatted messages to the local system logging
812 daemon. On systems using syslogd(8), this change should have no
813 negative impact, as long as syslogd(8) and the C library are
814 updated at the same time. On systems using a different system
815 logging daemon, it may be necessary to make configuration
816 adjustments, depending on the software used.
818 When using syslog-ng, add the 'syslog-protocol' flag to local
819 input sources to enable parsing of RFC 5424 formatted messages:
822 unix-dgram("/var/run/log" flags(syslog-protocol));
825 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
826 of the 'imuxsock' module to let messages be processed by the
827 regular RFC 3164/5424 parsing pipeline:
829 module(load="imuxsock" SysSock.UseSpecialParser="off")
831 Do note that these changes only affect communication between local
832 applications and syslogd(8). The format that syslogd(8) uses to
833 store messages on disk or forward messages to other systems
834 remains unchanged. syslogd(8) still uses RFC 3164 for these
835 purposes. Options to customize this behaviour will be added in the
836 future. Utilities that process log files stored in /var/log are
837 thus expected to continue to function as before.
839 __FreeBSD_version has been incremented to 1200061 to denote this
843 Support for token ring networks has been removed. If you
844 have "device token" in your kernel config you should remove
845 it. No device drivers supported token ring.
848 makefs was modified to be able to tag ISO9660 El Torito boot catalog
849 entries as EFI instead of overloading the i386 tag as done previously.
850 The amd64 mkisoimages.sh script used to build amd64 ISO images for
851 release was updated to use this. This may mean that makefs must be
852 updated before "make cdrom" can be run in the release directory. This
853 should be as simple as:
855 $ cd $SRCDIR/usr.sbin/makefs
856 $ make depend all install
859 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
860 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
861 Co-existence for the transition period will come shortly. Booting is a
862 complex environment and test coverage for Lua-enabled loaders has been
863 thin, so it would be prudent to assume it might not work and make
864 provisions for backup boot methods.
867 devmatch functionality has been turned on in devd. It will automatically
868 load drivers for unattached devices. This may cause unexpected drivers
869 to be loaded. Please report any problems to current@ and
873 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
874 6.0.0. Please see the 20141231 entry below for information about
875 prerequisites and upgrading, if you are not already using clang 3.5.0
879 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
880 This means it is used to link the kernel and userland libraries and
881 executables, but is not yet installed as /usr/bin/ld by default.
883 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
884 WITHOUT_LLD_BOOTSTRAP=yes
887 On i386, pmtimer has been removed. Its functionality has been folded
888 into apm. It was a no-op on ACPI in current for a while now (but was
889 still needed on i386 in FreeBSD 11 and earlier). Users may need to
890 remove it from kernel config files.
893 The use of RSS hash from the network card aka flowid has been
894 disabled by default for lagg(4) as it's currently incompatible with
895 the lacp and loadbalance protocols.
897 This can be re-enabled by setting the following in loader.conf:
898 net.link.lagg.default_use_flowid="1"
901 The SW_WATCHDOG option is no longer necessary to enable the
902 hardclock-based software watchdog if no hardware watchdog is
903 configured. As before, SW_WATCHDOG will cause the software
904 watchdog to be enabled even if a hardware watchdog is configured.
907 r326887 fixes the issue described in the 20171214 UPDATING entry.
908 r326888 flips the switch back to building GELI support always.
911 r362593 broke ZFS + GELI support for reasons unknown. However,
912 it also broke ZFS support generally, so GELI has been turned off
913 by default as the lesser evil in r326857. If you boot off ZFS and/or
914 GELI, it might not be a good time to update.
917 PowerPC users must update loader(8) by rebuilding world before
918 installing a new kernel, as the protocol connecting them has
919 changed. Without the update, loader metadata will not be passed
920 successfully to the kernel and users will have to enter their
921 root partition at the kernel mountroot prompt to continue booting.
922 Newer versions of loader can boot old kernels without issue.
925 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
926 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
927 to WITH/OUT_LOADER_GELI.
930 The naive and non-compliant support of posix_fallocate(2) in ZFS
931 has been removed as of r325320. The system call now returns EINVAL
932 when used on a ZFS file. Although the new behavior complies with the
933 standard, some consumers are not prepared to cope with it.
934 One known victim is lld prior to r325420.
937 Building in a FreeBSD src checkout will automatically create object
938 directories now rather than store files in the current directory if
939 'make obj' was not ran. Calling 'make obj' is no longer necessary.
940 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
941 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
945 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
946 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
947 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
948 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
949 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
950 The UNIFIED_OBJDIR option is a transitional feature that will be
951 removed for 12.0 release; please migrate to the new format for any
952 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
953 than hardcoding paths.
956 The native-xtools target no longer installs the files by default to the
957 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
958 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
961 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
962 options are changing from controlling the build if defined / undefined
963 to controlling the build with explicit 'yes' or 'no' values. They will
964 shift to WITH/WITHOUT options to match other options in the system.
967 libstand has turned into a private library for sys/boot use only.
968 It is no longer supported as a public interface outside of sys/boot.
971 The arm port has split armv6 into armv6 and armv7. armv7 is now
972 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
973 and are running a kernel from before r324363, you will need to add
974 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
977 When building multiple kernels using KERNCONF, non-existent KERNCONF
978 files will produce an error and buildkernel will fail. Previously
979 missing KERNCONF files silently failed giving no indication as to
980 why, only to subsequently discover during installkernel that the
981 desired kernel was never built in the first place.
984 The default serial number format for CTL LUNs has changed. This will
985 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
986 or iSCSI clients care about their LUNs' serial numbers. Users who
987 require serial number stability should hardcode serial numbers in
991 For 32-bit arm compiled for hard-float support, soft-floating point
992 binaries now always get their shared libraries from
993 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
994 /usr/libsoft also existed). Only users with a hard-float ld.so, but
995 soft-float everything else should be affected.
998 The geli password typed at boot is now hidden. To restore the previous
999 behavior, see geli(8) for configuration options.
1002 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
1003 sysctl values. Minor nit, but requires a rebuild of both world/kernel
1007 "make check" behavior (made in ^/head@r295380) has been changed to
1008 execute from a limited sandbox, as opposed to executing from
1012 - The "beforecheck" and "aftercheck" targets are now specified.
1013 - ${CHECKDIR} (added in commit noted above) has been removed.
1014 - Legacy behavior can be enabled by setting
1015 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
1017 If the limited sandbox mode is enabled, "make check" will execute
1018 "make distribution", then install, execute the tests, and clean up the
1019 sandbox if successful.
1021 The "make distribution" and "make install" targets are typically run as
1022 root to set appropriate permissions and ownership at installation time.
1023 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
1024 environment if executing "make check" with limited sandbox mode using
1025 an unprivileged user.
1028 Since the switch to GPT disk labels, fsck for UFS/FFS has been
1029 unable to automatically find alternate superblocks. As of r322297,
1030 the information needed to find alternate superblocks has been
1031 moved to the end of the area reserved for the boot block.
1032 Filesystems created with a newfs of this vintage or later
1033 will create the recovery information. If you have a filesystem
1034 created prior to this change and wish to have a recovery block
1035 created for your filesystem, you can do so by running fsck in
1036 foreground mode (i.e., do not use the -p or -y options). As it
1037 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
1038 to which you should answer yes.
1041 As of r321665, an NFSv4 server configuration that services
1042 Kerberos mounts or clients that do not support the uid/gid in
1043 owner/owner_group string capability, must explicitly enable
1044 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
1045 machine's /etc/rc.conf file.
1048 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
1049 Please see the 20141231 entry below for information about prerequisites
1050 and upgrading, if you are not already using clang 3.5.0 or higher.
1053 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
1054 r-commands (rlogin, rsh, etc.) to be built with the base system.
1057 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
1058 a very major ABI incompatible change, so users of FreeBSD/powerpc must
1059 be careful when performing source upgrades. It is best to run
1060 'make installworld' from an alternate root system, either a live
1061 CD/memory stick, or a temporary root partition. Additionally, all ports
1062 must be recompiled. powerpc64 is largely unaffected, except in the case
1063 of 32-bit compatibility. All 32-bit binaries will be affected.
1066 Forward compatibility for the "ino64" project have been committed. This
1067 will allow most new binaries to run on older kernels in a limited
1068 fashion. This prevents many of the common foot-shooting actions in the
1069 upgrade as well as the limited ability to roll back the kernel across
1070 the ino64 upgrade. Complicated use cases may not work properly, though
1071 enough simpler ones work to allow recovery in most situations.
1074 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
1075 if you require the GPL compiler.
1078 The internal ABI used for communication between the NFS kernel modules
1079 was changed by r320085, so __FreeBSD_version was bumped to
1080 ensure all the NFS related modules are updated together.
1083 The ABI of struct event was changed by extending the data
1084 member to 64bit and adding ext fields. For upgrade, same
1085 precautions as for the entry 20170523 "ino64" must be
1089 The GNU roff toolchain has been removed from base. To render manpages
1090 which are not supported by mandoc(1), man(1) can fallback on GNU roff
1091 from ports (and recommends to install it).
1092 To render roff(7) documents, consider using GNU roff from ports or the
1093 heirloom doctools roff toolchain from ports via pkg install groff or
1094 via pkg install heirloom-doctools.
1097 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
1098 smaller runtime footprint builds. This is useful for embedded systems
1099 which only require one chipset support.
1101 If you load it as a module, make sure this is in /boot/loader.conf:
1105 This will load the HAL, all chip/RF backends and if_ath_pci.
1106 If you have if_ath_pci in /boot/loader.conf, ensure it is after
1107 if_ath or it will not load any HAL chipset support.
1109 If you want to selectively load things (eg on ye cheape ARM/MIPS
1110 platforms where RAM is at a premium) you should:
1113 * load the chip modules in question
1114 * load ath_rate, ath_dfs
1116 * load if_ath_pci and/or if_ath_ahb depending upon your particular
1117 bus bind type - this is where probe/attach is done.
1119 For further comments/feedback, poke adrian@ .
1122 The "ino64" 64-bit inode project has been committed, which extends
1123 a number of types to 64 bits. Upgrading in place requires care and
1124 adherence to the documented upgrade procedure.
1126 If using a custom kernel configuration ensure that the
1127 COMPAT_FREEBSD11 option is included (as during the upgrade the
1128 system will be running the ino64 kernel with the existing world).
1130 For the safest in-place upgrade begin by removing previous build
1131 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full
1132 procedure documented below under the heading "To rebuild everything and
1133 install it on the current system." Specifically, a reboot is required
1134 after installing the new kernel before installing world. While an
1135 installworld normally works by accident from multiuser after rebooting
1136 the proper kernel, there are many cases where this will fail across this
1137 upgrade and installworld from single user is required.
1140 The NATM framework including the en(4), fatm(4), hatm(4), and
1141 patm(4) devices has been removed. Consumers should plan a
1142 migration before the end-of-life date for FreeBSD 11.
1145 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
1146 diff has not been implemented, if those are needed a newer version of
1147 GNU diff is available via the diffutils package under the gdiff name.
1150 As of r316810 for ipfilter, keep frags is no longer assumed when
1151 keep state is specified in a rule. r316810 aligns ipfilter with
1152 documentation in man pages separating keep frags from keep state.
1153 This allows keep state to be specified without forcing keep frags
1154 and allows keep frags to be specified independently of keep state.
1155 To maintain previous behaviour, also specify keep frags with
1156 keep state (as documented in ipf.conf.5).
1159 arm64 builds now use the base system LLD 4.0.0 linker by default,
1160 instead of requiring that the aarch64-binutils port or package be
1161 installed. To continue using aarch64-binutils, set
1162 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
1165 The UDP optimization in entry 20160818 that added the sysctl
1166 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
1167 packets will no longer be treated as L3 broadcast packets.
1170 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
1171 use any explicitly assigned loopback address available in the jail
1172 instead of using the first assigned address of the jail.
1175 The ctl.ko module no longer implements the iSCSI target frontend:
1176 cfiscsi.ko does instead.
1178 If building cfiscsi.ko as a kernel module, the module can be loaded
1179 via one of the following methods:
1180 - `cfiscsi_load="YES"` in loader.conf(5).
1181 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
1182 - ctladm(8)/ctld(8), when compiled with iSCSI support
1183 (`WITH_ISCSI=yes` in src.conf(5))
1185 Please see cfiscsi(4) for more details.
1188 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
1189 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
1190 same source (previously, the dependency of mmcsd.ko on mmc.ko was
1191 missing, but mmcsd.ko now will refuse to load if it is incompatible
1195 The syntax of ipfw(8) named states was changed to avoid ambiguity.
1196 If you have used named states in the firewall rules, you need to modify
1197 them after installworld and before rebooting. Now named states must
1198 be prefixed with colon.
1201 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
1202 removed as the userland we provide cannot use them. The KMS version
1203 (sys/dev/drm2) supports the same hardware.
1206 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
1207 Please see the 20141231 entry below for information about prerequisites
1208 and upgrading, if you are not already using clang 3.5.0 or higher.
1211 The code that provides support for ZFS .zfs/ directory functionality
1212 has been reimplemented. It's not possible now to create a snapshot
1213 by mkdir under .zfs/snapshot/. That should be the only user visible
1217 EISA bus support has been removed. The WITH_EISA option is no longer
1221 MCA bus support has been removed.
1224 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
1225 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
1228 The EM_MULTIQUEUE kernel configuration option is deprecated now that
1229 the em(4) driver conforms to iflib specifications.
1232 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
1233 IFLIB. If you have a custom kernel configuration that excludes em(4)
1234 but you use igb(4), you need to re-add em(4) to your custom
1238 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
1239 Please see the 20141231 entry below for information about prerequisites
1240 and upgrading, if you are not already using clang 3.5.0 or higher.
1243 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
1244 Please see the 20141231 entry below for information about prerequisites
1245 and upgrading, if you are not already using clang 3.5.0 or higher.
1248 The layout of the pmap structure has changed for powerpc to put the pmap
1249 statistics at the front for all CPU variations. libkvm(3) and all tools
1250 that link against it need to be recompiled.
1253 isl(4) and cyapa(4) drivers now require a new driver,
1254 chromebook_platform(4), to work properly on Chromebook-class hardware.
1255 On other types of hardware the drivers may need to be configured using
1256 device hints. Please see the corresponding manual pages for details.
1259 The urtwn(4) driver was merged into rtwn(4) and now consists of
1260 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
1262 Also, firmware for RTL8188CE was renamed due to possible name
1263 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
1266 GNU rcs has been removed from base. It is available as packages:
1267 - rcs: Latest GPLv3 GNU rcs version.
1268 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
1272 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
1273 modules now requires that the kernel configuration contain the
1274 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
1277 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
1278 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
1281 Relocatable object files with the extension of .So have been renamed
1282 to use an extension of .pico instead. The purpose of this change is
1283 to avoid a name clash with shared libraries on case-insensitive file
1284 systems. On those file systems, foo.So is the same file as foo.so.
1287 GNU rcs has been turned off by default. It can (temporarily) be built
1288 again by adding WITH_RCS knob in src.conf.
1289 Otherwise, GNU rcs is available from packages:
1290 - rcs: Latest GPLv3 GNU rcs version.
1291 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
1294 The backup_uses_rcs functionality has been removed from rc.subr.
1297 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
1298 two separate components, QUEUE_MACRO_DEBUG_TRACE and
1299 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
1300 QUEUE_MACRO_DEBUG behavior.
1303 r304787 changed some ioctl interfaces between the iSCSI userspace
1304 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1305 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1309 The UDP receive code has been updated to only treat incoming UDP
1310 packets that were addressed to an L2 broadcast address as L3
1311 broadcast packets. It is not expected that this will affect any
1312 standards-conforming UDP application. The new behaviour can be
1313 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1317 Remove the openbsd_poll system call.
1318 __FreeBSD_version has been bumped because of this.
1321 The stable/11 branch has been created from head@r302406.
1324 The libc stub for the pipe(2) system call has been replaced with
1325 a wrapper that calls the pipe2(2) system call and the pipe(2)
1326 system call is now only implemented by the kernels that include
1327 "options COMPAT_FREEBSD10" in their config file (this is the
1328 default). Users should ensure that this option is enabled in
1329 their kernel or upgrade userspace to r302092 before upgrading their
1333 CAM will now strip leading spaces from SCSI disks' serial numbers.
1334 This will affect users who create UFS filesystems on SCSI disks using
1335 those disk's diskid device nodes. For example, if /etc/fstab
1336 previously contained a line like
1337 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
1338 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
1339 transforms like gmirror may also be affected. ZFS users should
1343 The bitstring(3) API has been updated with new functionality and
1344 improved performance. But it is binary-incompatible with the old API.
1345 Objects built with the new headers may not be linked against objects
1346 built with the old headers.
1349 The brk and sbrk functions have been removed from libc on arm64.
1350 Binutils from ports has been updated to not link to these
1351 functions and should be updated to the latest version before
1352 installing a new libc.
1355 The armv6 port now defaults to hard float ABI. Limited support
1356 for running both hardfloat and soft float on the same system
1357 is available using the libraries installed with -DWITH_LIBSOFT.
1358 This has only been tested as an upgrade path for installworld
1359 and packages may fail or need manual intervention to run. New
1360 packages will be needed.
1362 To update an existing self-hosted armv6hf system, you must add
1363 TARGET_ARCH=armv6 on the make command line for both the build
1364 and the install steps.
1367 Kernel modules compiled outside of a kernel build now default to
1368 installing to /boot/modules instead of /boot/kernel. Many kernel
1369 modules built this way (such as those in ports) already overrode
1370 KMODDIR explicitly to install into /boot/modules. However,
1371 manually building and installing a module from /sys/modules will
1372 now install to /boot/modules instead of /boot/kernel.
1375 The CAM I/O scheduler has been committed to the kernel. There should be
1376 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1377 list of known rogues that claim support for this but actually corrupt
1378 data is believed to be complete, be on the lookout for data
1379 corruption. The known rogue list is believed to be complete:
1381 o Crucial MX100, M550 drives with MU01 firmware.
1382 o Micron M510 and M550 drives with MU01 firmware.
1383 o Micron M500 prior to MU07 firmware
1384 o Samsung 830, 840, and 850 all firmwares
1385 o FCCT M500 all firmwares
1387 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1388 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1389 updated firmware. Black listed drives will work correctly because these
1390 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1391 this list is the same as found in Linux, it's believed there are no
1392 other rogues in the market place. All other models from the above
1395 To be safe, if you are at all concerned, you can quirk each of your
1396 drives to prevent NCQ from being sent by setting:
1397 kern.cam.ada.X.quirks="0x2"
1398 in loader.conf. If the drive requires the 4k sector quirk, set the
1399 quirks entry to 0x3.
1402 The FAST_DEPEND build option has been removed and its functionality is
1403 now the one true way. The old mkdep(1) style of 'make depend' has
1404 been removed. See 20160311 for further details.
1407 Resource range types have grown from unsigned long to uintmax_t. All
1408 drivers, and anything using libdevinfo, need to be recompiled.
1411 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1412 builds. It no longer runs mkdep(1) during 'make depend', and the
1413 'make depend' stage can safely be skipped now as it is auto ran
1414 when building 'make all' and will generate all SRCS and DPSRCS before
1415 building anything else. Dependencies are gathered at compile time with
1416 -MF flags kept in separate .depend files per object file. Users should
1417 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1418 stale .depend files.
1421 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1422 kernel modules. Therefore, if you load any kernel modules at boot time,
1423 please install the boot loaders after you install the kernel, but before
1427 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1428 make installkernel KERNCONF=YOUR_KERNEL_HERE
1429 make -C sys/boot install
1430 <reboot in single user>
1432 Then follow the usual steps, described in the General Notes section,
1436 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1437 see the 20141231 entry below for information about prerequisites and
1438 upgrading, if you are not already using clang 3.5.0 or higher.
1441 The AIO subsystem is now a standard part of the kernel. The
1442 VFS_AIO kernel option and aio.ko kernel module have been removed.
1443 Due to stability concerns, asynchronous I/O requests are only
1444 permitted on sockets and raw disks by default. To enable
1445 asynchronous I/O requests on all file types, set the
1446 vfs.aio.enable_unsafe sysctl to a non-zero value.
1449 The ELF object manipulation tool objcopy is now provided by the
1450 ELF Tool Chain project rather than by GNU binutils. It should be a
1451 drop-in replacement, with the addition of arm64 support. The
1452 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1453 to obtain the GNU version if necessary.
1456 Building ZFS pools on top of zvols is prohibited by default. That
1457 feature has never worked safely; it's always been prone to deadlocks.
1458 Using a zvol as the backing store for a VM guest's virtual disk will
1459 still work, even if the guest is using ZFS. Legacy behavior can be
1460 restored by setting vfs.zfs.vol.recursive=1.
1463 The NONE and HPN patches has been removed from OpenSSH. They are
1464 still available in the security/openssh-portable port.
1467 With the addition of ypldap(8), a new _ypldap user is now required
1468 during installworld. "mergemaster -p" can be used to add the user
1469 prior to installworld, as documented in the handbook.
1472 The tftp loader (pxeboot) now uses the option root-path directive. As a
1473 consequence it no longer looks for a pxeboot.4th file on the tftp
1474 server. Instead it uses the regular /boot infrastructure as with the
1478 The code to start recording plug and play data into the modules has
1479 been committed. While the old tools will properly build a new kernel,
1480 a number of warnings about "unknown metadata record 4" will be produced
1481 for an older kldxref. To avoid such warnings, make sure to rebuild
1482 the kernel toolchain (or world). Make sure that you have r292078 or
1483 later when trying to build 292077 or later before rebuilding.
1486 Debug data files are now built by default with 'make buildworld' and
1487 installed with 'make installworld'. This facilitates debugging but
1488 requires more disk space both during the build and for the installed
1489 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1493 r291527 changed the internal interface between the nfsd.ko and
1494 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1495 __FreeBSD_version has been bumped because of this.
1498 Add support for unicode collation strings leads to a change of
1499 order of files listed by ls(1) for example. To get back to the old
1500 behaviour, set LC_COLLATE environment variable to "C".
1502 Databases administrators will need to reindex their databases given
1503 collation results will be different.
1505 Due to a bug in install(1) it is recommended to remove the ancient
1506 locales before running make installworld.
1508 rm -rf /usr/share/locale/*
1511 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1512 libcrypto.so.7 or libssl.so.7 must be recompiled.
1515 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1516 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1517 should be replaced with isp_2400 and isp_2500 modules respectively.
1520 The build previously allowed using 'make -n' to not recurse into
1521 sub-directories while showing what commands would be executed, and
1522 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1523 and 'make -N' will not.
1526 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1527 and etcupdate will now use this file. A custom sendmail.cf is now
1528 updated via this mechanism rather than via installworld. If you had
1529 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1530 want to remove the exclusion or change it to "always install".
1531 /etc/mail/sendmail.cf is now managed the same way regardless of
1532 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1533 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1536 Compatibility shims for legacy ATA device names have been removed.
1537 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1538 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1539 environment variables, /dev/ad* and /dev/ar* symbolic links.
1542 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1543 Please see the 20141231 entry below for information about prerequisites
1544 and upgrading, if you are not already using clang 3.5.0 or higher.
1547 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1548 and renamed from .symbols to .debug. This reduces the size requirements
1549 on the boot partition or file system and provides consistency with
1550 userland debug files.
1552 When using the supported kernel installation method the
1553 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1554 as is done with /boot/kernel.
1556 Developers wishing to maintain the historical behavior of installing
1557 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1560 The wireless drivers had undergone changes that remove the 'parent
1561 interface' from the ifconfig -l output. The rc.d network scripts
1562 used to check presence of a parent interface in the list, so old
1563 scripts would fail to start wireless networking. Thus, etcupdate(3)
1564 or mergemaster(8) run is required after kernel update, to update your
1565 rc.d scripts in /etc.
1568 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1569 These configurations are now automatically interpreted as
1570 'scrub fragment reassemble'.
1573 Kernel-loadable modules for the random(4) device are back. To use
1574 them, the kernel must have
1577 options RANDOM_LOADABLE
1579 kldload(8) can then be used to load random_fortuna.ko
1580 or random_yarrow.ko. Please note that due to the indirect
1581 function calls that the loadable modules need to provide,
1582 the build-in variants will be slightly more efficient.
1584 The random(4) kernel option RANDOM_DUMMY has been retired due to
1585 unpopularity. It was not all that useful anyway.
1588 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1589 Control over building the ELF Tool Chain tools is now provided by
1590 the WITHOUT_TOOLCHAIN knob.
1593 The polarity of Pulse Per Second (PPS) capture events with the
1594 uart(4) driver has been corrected. Prior to this change the PPS
1595 "assert" event corresponded to the trailing edge of a positive PPS
1596 pulse and the "clear" event was the leading edge of the next pulse.
1598 As the width of a PPS pulse in a typical GPS receiver is on the
1599 order of 1 millisecond, most users will not notice any significant
1600 difference with this change.
1602 Anyone who has compensated for the historical polarity reversal by
1603 configuring a negative offset equal to the pulse width will need to
1604 remove that workaround.
1607 The default group assigned to /dev/dri entries has been changed
1608 from 'wheel' to 'video' with the id of '44'. If you want to have
1609 access to the dri devices please add yourself to the video group
1612 # pw groupmod video -m $USER
1615 The menu.rc and loader.rc files will now be replaced during
1616 upgrades. Please migrate local changes to menu.rc.local and
1617 loader.rc.local instead.
1620 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1621 strings and strip have been removed. The src.conf(5) knob
1622 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1625 As ZFS requires more kernel stack pages than is the default on some
1626 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1627 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1629 Please consider using 'options KSTACK_PAGES=X' where X is greater
1630 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1633 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1634 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1635 default, i.e., they will not contain "::". For example, instead
1636 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1637 to have a more specific match, such as different map entries for
1638 IPv6:0:0 vs IPv6:0. This change requires that configuration
1639 data (including maps, files, classes, custom ruleset, etc.) must
1640 use the same format, so make certain such configuration data is
1641 upgrading. As a very simple check search for patterns like
1642 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1643 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1644 the cf option UseCompressedIPv6Addresses.
1647 The default kernel entropy-processing algorithm is now
1648 Fortuna, replacing Yarrow.
1650 Assuming you have 'device random' in your kernel config
1651 file, the configurations allow a kernel option to override
1652 this default. You may choose *ONE* of:
1654 options RANDOM_YARROW # Legacy /dev/random algorithm.
1655 options RANDOM_DUMMY # Blocking-only driver.
1657 If you have neither, you get Fortuna. For most people,
1658 read no further, Fortuna will give a /dev/random that works
1659 like it always used to, and the difference will be irrelevant.
1661 If you remove 'device random', you get *NO* kernel-processed
1662 entropy at all. This may be acceptable to folks building
1663 embedded systems, but has complications. Carry on reading,
1664 and it is assumed you know what you need.
1666 *PLEASE* read random(4) and random(9) if you are in the
1667 habit of tweaking kernel configs, and/or if you are a member
1668 of the embedded community, wanting specific and not-usual
1669 behaviour from your security subsystems.
1671 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1672 random', you will NOT have a functioning /dev/random, and
1673 many cryptographic features will not work, including SSH.
1674 You may also find strange behaviour from the random(3) set
1675 of library functions, in particular sranddev(3), srandomdev(3)
1676 and arc4random(3). The reason for this is that the KERN_ARND
1677 sysctl only returns entropy if it thinks it has some to
1678 share, and with RANDOM_DUMMY or no 'device random' this
1682 An additional fix for the issue described in the 20150614 sendmail
1683 entry below has been committed in revision 284717.
1686 FreeBSD's old make (fmake) has been removed from the system. It is
1687 available as the devel/fmake port or via pkg install fmake.
1690 The fix for the issue described in the 20150614 sendmail entry
1691 below has been committed in revision 284436. The work
1692 around described in that entry is no longer needed unless the
1693 default setting is overridden by a confDH_PARAMETERS configuration
1694 setting of '5' or pointing to a 512 bit DH parameter file.
1697 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1698 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1699 and devel/kyua to version 0.20+ and adjust any calling code to work
1700 with Kyuafile and kyua.
1703 The import of openssl to address the FreeBSD-SA-15:10.openssl
1704 security advisory includes a change which rejects handshakes
1705 with DH parameters below 768 bits. sendmail releases prior
1706 to 8.15.2 (not yet released), defaulted to a 512 bit
1707 DH parameter setting for client connections. To work around
1708 this interoperability, sendmail can be configured to use a
1709 2048 bit DH parameter by:
1711 1. Edit /etc/mail/`hostname`.mc
1712 2. If a setting for confDH_PARAMETERS does not exist or
1713 exists and is set to a string beginning with '5',
1714 replace it with '2'.
1715 3. If a setting for confDH_PARAMETERS exists and is set to
1716 a file path, create a new file with:
1717 openssl dhparam -out /path/to/file 2048
1718 4. Rebuild the .cf file:
1719 cd /etc/mail/; make; make install
1720 5. Restart sendmail:
1721 cd /etc/mail/; make restart
1723 A sendmail patch is coming, at which time this file will be
1727 Generation of legacy formatted entries have been disabled by default
1728 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1729 entries were converted to use the new format by default when the new,
1730 machine independent format have been added and supported since FreeBSD
1733 Please see the pwd_mkdb(8) manual page for further details.
1736 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1737 20141231 entry below for information about prerequisites and upgrading,
1738 if you are not already using 3.5.0 or higher.
1741 TI platform code switched to using vendor DTS files and this update
1742 may break existing systems running on Beaglebone, Beaglebone Black,
1745 - dtb files should be regenerated/reinstalled. Filenames are the
1746 same but content is different now
1747 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1748 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1749 addressing scheme is now pin 25 on /dev/gpioc3.
1750 - Pandaboard: /etc/ttys should be updated, serial console device is
1751 now /dev/ttyu2, not /dev/ttyu0
1754 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1755 If you need the GNU extension from groff soelim(1), install groff
1756 from package: pkg install groff, or via ports: textproc/groff.
1759 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1760 defined in symlink(7); previously symlinks were silently ignored.
1763 The const qualifier has been removed from iconv(3) to comply with
1764 POSIX. The ports tree is aware of this from r384038 onwards.
1767 Libraries specified by LIBADD in Makefiles must have a corresponding
1768 DPADD_<lib> variable to ensure correct dependencies. This is now
1769 enforced in src.libnames.mk.
1772 From legacy ata(4) driver was removed support for SATA controllers
1773 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1774 Kernel modules ataahci and ataadaptec were removed completely,
1775 replaced by ahci and mvs modules respectively.
1778 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1779 the 20141231 entry below for information about prerequisites and
1780 upgrading, if you are not already using 3.5.0 or higher.
1783 The 32-bit PowerPC kernel has been changed to a position-independent
1784 executable. This can only be booted with a version of loader(8)
1785 newer than January 31, 2015, so make sure to update both world and
1786 kernel before rebooting.
1789 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1790 but before r278950, the RNG was not seeded properly. Immediately
1791 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1792 ssh keys or openssl keys) that were generated w/ a kernel from that
1793 range. This does not affect programs that directly used /dev/random
1794 or /dev/urandom. All userland uses of arc4random(3) are affected.
1797 The autofs(4) ABI was changed in order to restore binary compatibility
1798 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1799 with the new kernel.
1802 The powerpc64 kernel has been changed to a position-independent
1803 executable. This can only be booted with a new version of loader(8),
1804 so make sure to update both world and kernel before rebooting.
1807 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1808 only release, no new features have been added. Please see the 20141231
1809 entry below for information about prerequisites and upgrading, if you
1810 are not already using 3.5.0.
1813 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1814 taken from the ELF Tool Chain project rather than GNU binutils. They
1815 should be drop-in replacements, with the addition of arm64 support.
1816 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1817 binutils tools, if necessary. See 20150805 for updated information.
1820 The default Unbound configuration now enables remote control
1821 using a local socket. Users who have already enabled the
1822 local_unbound service should regenerate their configuration
1823 by running "service local_unbound setup" as root.
1826 The GNU texinfo and GNU info pages have been removed.
1827 To be able to view GNU info pages please install texinfo from ports.
1830 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1832 As of this release, a prerequisite for building clang, llvm and lldb is
1833 a C++11 capable compiler and C++11 standard library. This means that to
1834 be able to successfully build the cross-tools stage of buildworld, with
1835 clang as the bootstrap compiler, your system compiler or cross compiler
1836 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1837 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1840 On any standard FreeBSD 10.x or 11.x installation, where clang and
1841 libc++ are on by default (that is, on x86 or arm), this should work out
1844 On 9.x installations where clang is enabled by default, e.g. on x86 and
1845 powerpc, libc++ will not be enabled by default, so libc++ should be
1846 built (with clang) and installed first. If both clang and libc++ are
1847 missing, build clang first, then use it to build libc++.
1849 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1850 the instructions for 9.x above.
1852 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1853 default, and do not build clang.
1855 Many embedded systems are resource constrained, and will not be able to
1856 build clang in a reasonable time, or in some cases at all. In those
1857 cases, cross building bootable systems on amd64 is a workaround.
1859 This new version of clang introduces a number of new warnings, of which
1860 the following are most likely to appear:
1864 This warns in two cases, for both C and C++:
1865 * When the code is trying to take the absolute value of an unsigned
1866 quantity, which is effectively a no-op, and almost never what was
1867 intended. The code should be fixed, if at all possible. If you are
1868 sure that the unsigned quantity can be safely cast to signed, without
1869 loss of information or undefined behavior, you can add an explicit
1870 cast, or disable the warning.
1872 * When the code is trying to take an absolute value, but the called
1873 abs() variant is for the wrong type, which can lead to truncation.
1874 If you want to disable the warning instead of fixing the code, please
1875 make sure that truncation will not occur, or it might lead to unwanted
1878 -Wtautological-undefined-compare and
1879 -Wundefined-bool-conversion
1881 These warn when C++ code is trying to compare 'this' against NULL, while
1882 'this' should never be NULL in well-defined C++ code. However, there is
1883 some legacy (pre C++11) code out there, which actively abuses this
1884 feature, which was less strictly defined in previous C++ versions.
1886 Squid and openjdk do this, for example. The warning can be turned off
1887 for C++98 and earlier, but compiling the code in C++11 mode might result
1888 in unexpected behavior; for example, the parts of the program that are
1889 unreachable could be optimized away.
1892 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1893 kernel sources have been removed. The .h files remain, since some
1894 utilities include them. This will need to be fixed later.
1895 If "mount -t oldnfs ..." is attempted, it will fail.
1896 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1897 the utilities will report errors.
1900 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1901 directories to top level SUBDIR variable when their parent
1902 directory is included in LOCAL_DIRS. Users with build systems with
1903 such hierarchies and without SUBDIR entries in the parent
1904 directory Makefiles should add them or add the directories to
1908 faith(4) and faithd(8) have been removed from the base system. Faith
1909 has been obsolete for a very long time.
1912 vt(4), the new console driver, is enabled by default. It brings
1913 support for Unicode and double-width characters, as well as
1914 support for UEFI and integration with the KMS kernel video
1917 You may need to update your console settings in /etc/rc.conf,
1918 most probably the keymap. During boot, /etc/rc.d/syscons will
1919 indicate what you need to do.
1921 vt(4) still has issues and lacks some features compared to
1922 syscons(4). See the wiki for up-to-date information:
1923 https://wiki.freebsd.org/Newcons
1925 If you want to keep using syscons(4), you can do so by adding
1926 the following line to /boot/loader.conf:
1930 pjdfstest has been integrated into kyua as an opt-in test suite.
1931 Please see share/doc/pjdfstest/README for more details on how to
1935 gperf has been removed from the base system for architectures
1936 that use clang. Ports that require gperf will obtain it from the
1940 pjdfstest has been moved from tools/regression/pjdfstest to
1944 At svn r271982, The default linux compat kernel ABI has been adjusted
1945 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1946 update. If you wish to continue using the linux-f10 compat ports,
1947 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1948 encouraged to update their linux-compat packages to linux-c6 during
1949 their next update cycle.
1952 The ofwfb driver, used to provide a graphics console on PowerPC when
1953 using vt(4), no longer allows mmap() of all physical memory. This
1954 will prevent Xorg on PowerPC with some ATI graphics cards from
1955 initializing properly unless x11-servers/xorg-server is updated to
1959 The xdev targets have been converted to using TARGET and
1960 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1963 The default unbound configuration has been modified to address
1964 issues with reverse lookups on networks that use private
1965 address ranges. If you use the local_unbound service, run
1966 "service local_unbound setup" as root to regenerate your
1967 configuration, then "service local_unbound reload" to load the
1971 The GNU texinfo and GNU info pages are not built and installed
1972 anymore, WITH_INFO knob has been added to allow to built and install
1974 UPDATE: see 20150102 entry on texinfo's removal
1977 The GNU readline library is now an INTERNALLIB - that is, it is
1978 statically linked into consumers (GDB and variants) in the base
1979 system, and the shared library is no longer installed. The
1980 devel/readline port is available for third party software that
1984 The Itanium architecture (ia64) has been removed from the list of
1985 known architectures. This is the first step in the removal of the
1989 Commit r268115 has added NFSv4.1 server support, merged from
1990 projects/nfsv4.1-server. Since this includes changes to the
1991 internal interfaces between the NFS related modules, a full
1992 build of the kernel and modules will be necessary.
1993 __FreeBSD_version has been bumped.
1996 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1997 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1998 which differs from the behaviour controlled by this knob.)
2001 Maximal length of the serial number in CTL was increased from 16 to
2002 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
2003 and ctld, need to be rebuilt to work with a new kernel.
2006 The libatf-c and libatf-c++ major versions were downgraded to 0 and
2007 1 respectively to match the upstream numbers. They were out of
2008 sync because, when they were originally added to FreeBSD, the
2009 upstream versions were not respected. These libraries are private
2010 and not yet built by default, so renumbering them should be a
2011 non-issue. However, unclean source trees will yield broken test
2012 programs once the operator executes "make delete-old-libs" after a
2013 "make installworld".
2015 Additionally, the atf-sh binary was made private by moving it into
2016 /usr/libexec/. Already-built shell test programs will keep the
2017 path to the old binary so they will break after "make delete-old"
2020 If you are using WITH_TESTS=yes (not the default), wipe the object
2021 tree and rebuild from scratch to prevent spurious test failures.
2022 This is only needed once: the misnumbered libraries and misplaced
2023 binaries have been added to OptionalObsoleteFiles.inc so they will
2024 be removed during a clean upgrade.
2027 Clang and llvm have been upgraded to 3.4.1 release.
2030 We bogusly installed src.opts.mk in /usr/share/mk. This file should
2031 be removed to avoid issues in the future (and has been added to
2035 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
2036 past, it affected all builds that used the bsd.*.mk files. The old
2037 behavior was a bug, but people may have relied upon it. To get this
2038 behavior back, you can .include /etc/src.conf from /etc/make.conf
2039 (which is still global and isn't changed). This also changes the
2040 behavior of incremental builds inside the tree of individual
2041 directories. Set MAKESYSPATH to ".../share/mk" to do that.
2042 Although this has survived make universe and some upgrade scenarios,
2043 other upgrade scenarios may have broken. At least one form of
2044 temporary breakage was fixed with MAKESYSPATH settings for buildworld
2045 as well... In cases where MAKESYSPATH isn't working with this
2046 setting, you'll need to set it to the full path to your tree.
2048 One side effect of all this cleaning up is that bsd.compiler.mk
2049 is no longer implicitly included by bsd.own.mk. If you wish to
2050 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
2054 The lindev device has been removed since /dev/full has been made a
2055 standard device. __FreeBSD_version has been bumped.
2058 The knob WITHOUT_VI was added to the base system, which controls
2059 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
2060 in order to reorder files share/termcap and didn't build ex(1) as a
2061 build tool, so building/installing with WITH_VI is highly advised for
2062 build hosts for older releases.
2064 This issue has been fixed in stable/9 and stable/10 in r277022 and
2065 r276991, respectively.
2068 The YES_HESIOD knob has been removed. It has been obsolete for
2069 a decade. Please move to using WITH_HESIOD instead or your builds
2070 will silently lack HESIOD.
2073 The uart(4) driver has been changed with respect to its handling
2074 of the low-level console. Previously the uart(4) driver prevented
2075 any process from changing the baudrate or the CLOCAL and HUPCL
2076 control flags. By removing the restrictions, operators can make
2077 changes to the serial console port without having to reboot.
2078 However, when getty(8) is started on the serial device that is
2079 associated with the low-level console, a misconfigured terminal
2080 line in /etc/ttys will now have a real impact.
2081 Before upgrading the kernel, make sure that /etc/ttys has the
2082 serial console device configured as 3wire without baudrate to
2083 preserve the previous behaviour. E.g:
2084 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
2087 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
2088 to improve performance. To re-enable it, if needed, run rpcbind
2089 with command line option -W.
2092 Switched back to the GPL dtc compiler due to updates in the upstream
2093 dts files not being supported by the BSDL dtc compiler. You will need
2094 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
2095 may result while building dtb files during a kernel build if you fail
2096 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
2099 Clang and llvm have been upgraded to 3.4 release.
2102 The nve(4) driver has been removed. Please use the nfe(4) driver
2103 for NVIDIA nForce MCP Ethernet adapters instead.
2106 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
2107 This could cause certain C++ applications using shared libraries built
2108 against the previous version of libc++ to crash. The incompatibility
2109 has now been fixed, but any C++ applications or shared libraries built
2110 between r261283 and r261801 should be recompiled.
2113 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
2114 capability mode support. Please note that enabling the feature in
2115 kernel is still highly recommended.
2118 OpenSSH is now built with sandbox support, and will use sandbox as
2119 the default privilege separation method. This requires Capsicum
2120 capability mode support in kernel.
2123 The libelf and libdwarf libraries have been updated to newer
2124 versions from upstream. Shared library version numbers for
2125 these two libraries were bumped. Any ports or binaries
2126 requiring these two libraries should be recompiled.
2127 __FreeBSD_version is bumped to 1100006.
2130 If a Makefile in a tests/ directory was auto-generating a Kyuafile
2131 instead of providing an explicit one, this would prevent such
2132 Makefile from providing its own Kyuafile in the future during
2133 NO_CLEAN builds. This has been fixed in the Makefiles but manual
2134 intervention is needed to clean an objdir if you use NO_CLEAN:
2135 # find /usr/obj -name Kyuafile | xargs rm -f
2138 The behavior of gss_pseudo_random() for the krb5 mechanism
2139 has changed, for applications requesting a longer random string
2140 than produced by the underlying enctype's pseudo-random() function.
2141 In particular, the random string produced from a session key of
2142 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
2143 be different at the 17th octet and later, after this change.
2144 The counter used in the PRF+ construction is now encoded as a
2145 big-endian integer in accordance with RFC 4402.
2146 __FreeBSD_version is bumped to 1100004.
2149 The WITHOUT_ATF build knob has been removed and its functionality
2150 has been subsumed into the more generic WITHOUT_TESTS. If you were
2151 using the former to disable the build of the ATF libraries, you
2152 should change your settings to use the latter.
2155 The default version of mtree is nmtree which is obtained from
2156 NetBSD. The output is generally the same, but may vary
2157 slightly. If you found you need identical output adding
2158 "-F freebsd9" to the command line should do the trick. For the
2159 time being, the old mtree is available as fmtree.
2162 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
2163 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
2164 1.1.4_8 and verify bsdyml not linked in, before running "make
2166 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
2168 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
2171 The stable/10 branch has been created in subversion from head
2178 Sometimes, obscure build problems are the result of environment
2179 poisoning. This can happen because the make utility reads its
2180 environment when searching for values for global variables. To run
2181 your build attempts in an "environmental clean room", prefix all make
2182 commands with 'env -i '. See the env(1) manual page for more details.
2183 Occasionally a build failure will occur with "make -j" due to a race
2184 condition. If this happens try building again without -j, and please
2185 report a bug if it happens consistently.
2187 When upgrading from one major version to another it is generally best to
2188 upgrade to the latest code in the currently installed branch first, then
2189 do an upgrade to the new branch. This is the best-tested upgrade path,
2190 and has the highest probability of being successful. Please try this
2191 approach if you encounter problems with a major version upgrade. Since
2192 the stable 4.x branch point, one has generally been able to upgrade from
2193 anywhere in the most recent stable branch to head / current (or even the
2194 last couple of stable branches). See the top of this file when there's
2197 The update process will emit an error on an attempt to perform a build
2198 or install from a FreeBSD version below the earliest supported version.
2199 When updating from an older version the update should be performed one
2200 major release at a time, including running `make delete-old` at each
2203 When upgrading a live system, having a root shell around before
2204 installing anything can help undo problems. Not having a root shell
2205 around can lead to problems if pam has changed too much from your
2206 starting point to allow continued authentication after the upgrade.
2208 This file should be read as a log of events. When a later event changes
2209 information of a prior event, the prior event should not be deleted.
2210 Instead, a pointer to the entry with the new information should be
2211 placed in the old entry. Readers of this file should also sanity check
2212 older entries before relying on them blindly. Authors of new entries
2213 should write them with this in mind.
2217 When upgrading the boot ZFS pool to a new version, always follow
2220 1.) recompile and reinstall the ZFS boot loader and boot block
2221 (this is part of "make buildworld" and "make installworld")
2223 2.) update the ZFS boot block on your boot drive
2225 The following example updates the ZFS boot block on the
2226 freebsd-boot partition of a GPT partitioned drive ada0:
2227 "gpart bootcode -p /boot/gptzfsboot -i $N ada0"
2228 The value $N will typically be 1 (if booting from BIOS) or 2 (if
2231 Non-boot pools do not need these updates.
2235 If you are updating from a prior version of FreeBSD (even one just
2236 a few days old), you should follow this procedure. It is the most
2237 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2239 make kernel-toolchain
2240 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2241 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2243 To test a kernel once
2244 ---------------------
2245 If you just want to boot a kernel once (because you are not sure
2246 if it works, or if you want to boot a known bad kernel to provide
2247 debugging information) run
2248 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2249 nextboot -k testkernel
2251 To rebuild everything and install it on the current system.
2252 -----------------------------------------------------------
2253 # Note: sometimes if you are running current you gotta do more than
2254 # is listed here if you are upgrading from a really old current.
2256 <make sure you have good level 0 dumps>
2258 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2259 make installkernel KERNCONF=YOUR_KERNEL_HERE
2261 <reboot in single user> [3]
2268 To cross-install current onto a separate partition
2269 --------------------------------------------------
2270 # In this approach we use a separate partition to hold
2271 # current's root, 'usr', and 'var' directories. A partition
2272 # holding "/", "/usr" and "/var" should be about 2GB in
2275 <make sure you have good level 0 dumps>
2278 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2279 <maybe newfs current's root partition>
2280 <mount current's root partition on directory ${CURRENT_ROOT}>
2281 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
2282 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2283 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2284 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2285 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2286 <reboot into current>
2287 <do a "native" rebuild/install as described in the previous section>
2288 <maybe install compatibility libraries from ports/misc/compat*>
2292 To upgrade in-place from stable to current
2293 ----------------------------------------------
2294 <make sure you have good level 0 dumps>
2296 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
2297 make installkernel KERNCONF=YOUR_KERNEL_HERE
2299 <reboot in single user> [3]
2306 Make sure that you've read the UPDATING file to understand the
2307 tweaks to various things you need. At this point in the life
2308 cycle of current, things change often and you are on your own
2309 to cope. The defaults can also change, so please read ALL of
2310 the UPDATING entries.
2312 Also, if you are tracking -current, you must be subscribed to
2313 freebsd-current@freebsd.org. Make sure that before you update
2314 your sources that you have read and understood all the recent
2315 messages there. If in doubt, please track -stable which has
2316 much fewer pitfalls.
2318 [1] If you have third party modules, such as vmware, you should disable
2319 them at this point so they don't crash your system on
2320 reboot. Alternatively, you should rebuild all the modules you have in
2321 your system and install them as well. If you are running -current, you
2322 should seriously consider placing all sources to all the modules for
2323 your system (or symlinks to them) in /usr/local/sys/modules so this
2324 happens automatically. If all your modules come from ports, then adding
2325 the port origin directories to PORTS_MODULES instead is also automatic
2327 PORTS_MODULES+=x11/nvidia-driver
2329 [3] From the bootblocks, boot -s, and then do
2333 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed
2334 cd src # full path to source
2335 adjkerntz -i # if CMOS is wall time
2336 Also, when doing a major release upgrade, it is required that you boot
2337 into single user mode to do the installworld.
2339 [4] Note: This step is non-optional. Failure to do this step
2340 can result in a significant reduction in the functionality of the
2341 system. Attempting to do it by hand is not recommended and those
2342 that pursue this avenue should read this file carefully, as well
2343 as the archives of freebsd-current and freebsd-hackers mailing lists
2344 for potential gotchas. The -U option is also useful to consider.
2345 See mergemaster(8) for more information.
2347 [5] Usually this step is a no-op. However, from time to time
2348 you may need to do this if you get unknown user in the following
2349 step. It never hurts to do it all the time. You may need to
2350 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2351 install) after the buildworld before this step if you last updated
2352 from current before 20130425 or from -stable before 20130430.
2354 [6] This only deletes old files and directories. Old libraries
2355 can be deleted by "make delete-old-libs", but you have to make
2356 sure that no program is using those libraries anymore.
2358 [8] The new kernel must be able to run existing binaries used by an
2359 installworld. When upgrading across major versions, the new kernel's
2360 configuration must include the correct COMPAT_FREEBSD<n> option for
2361 existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure
2362 to do so may leave you with a system that is hard to boot to recover. A
2363 GENERIC kernel will include suitable compatibility options to run
2364 binaries from older branches. Note that the ability to run binaries
2365 from unsupported branches is not guaranteed.
2367 Make sure that you merge any new devices from GENERIC since the
2368 last time you updated your kernel config file. Options also
2369 change over time, so you may need to adjust your custom kernels
2372 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2373 "?=" instead of the "=" assignment operator, so that buildworld can
2374 override the CPUTYPE if it needs to.
2376 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2377 not on the command line, or in /etc/make.conf. buildworld will
2378 warn if it is improperly defined.
2381 This file contains a list, in reverse chronological order, of major
2382 breakages in tracking -current. It is not guaranteed to be a complete
2383 list of such breakages, and only contains entries since September 23, 2011.
2384 If you need to see UPDATING entries from before that date, you will need
2385 to fetch an UPDATING file from an older FreeBSD release.
2387 Copyright information:
2389 Copyright 1998-2009 M. Warner Losh <imp@FreeBSD.org>
2391 Redistribution, publication, translation and use, with or without
2392 modification, in full or in part, in any form or format of this
2393 document are permitted without further permission from the author.
2395 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2396 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2397 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2398 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2399 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2400 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2401 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2402 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2403 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2404 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2405 POSSIBILITY OF SUCH DAMAGE.
2407 Contact Warner Losh if you have any questions about your use of