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 Default value of net.add_addr_allfibs has been changed to 0.
31 If you have multi-fib configuration and rely on existence of all
32 interface routes in every fib, you need to set the above sysctl to 1.
34 The internal pre-processor in the calendar(1) program has been
35 extended to support more C pre-processor commands (e.g. #ifdef, #else,
36 and #undef) and to detect unbalanced conditional statements.
37 Error messages have been extended to include the filename and line
38 number if processing stops to help fixing malformed data files.
41 All the data files for the calendar(1) program, except calendar.freebsd,
42 have been moved to the deskutils/calendar-data port, much like the
43 jewish calendar entries were moved to deskutils/hebcal years ago. After
44 make delete-old-files, you need to install it to retain full
45 functionality. calendar(1) will issue a reminder for files it can't
49 LINT files are no longer generated. We now include the relevant NOTES
50 files. Note: This may cause conflicts with updating in some cases.
51 find sys -name LINT\* -delete
52 is suggested across this commit to remove the generated LINT files.
54 If you have tried to update with generated files there, the svn
55 command you want to un-auger the tree is
58 and then do the above find from the top level. Substitute 'amd64'
59 above with where the error message indicates a conflict.
62 OpenZFS support has been integrated. Do not upgrade root pools until
63 the loader is updated to support zstd. Furthermore, we caution against
64 'zpool upgrade' for the next few weeks. The change should be transparent
65 unless you want to use new features.
67 Not all "NO_CLEAN" build scenarios work across these changes. Many
68 scenarios have been tested and fixed, but rebuilding kernels without
69 rebuilding world may fail.
71 The ZFS cache file has moved from /boot to /etc to match the OpenZFS
72 upstream default. A fallback to /boot has been added for mountroot.
74 Pool auto import behavior at boot has been moved from the kernel module
75 to an explicit "zpool import -a" in one of the rc scripts enabled by
76 zfs_enable=YES. This means your non-root zpools won't auto import until
77 you upgrade your /etc/rc.d files.
80 The resume code now notifies devd with the 'kernel' system
81 rather than the old 'kern' subsystem to be consistent with
82 other use. The old notification will be created as well, but
83 will be removed prior to FreeBSD 14.0.
86 r362275 changed the internal API between the kernel RPC and the
87 NFS modules. As such, all the modules must be recompiled from
91 r364330 modified the internal API used between the NFS modules.
92 As such, all the NFS modules must be re-compiled from sources.
95 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
96 been upgraded to 11.0.0. Please see the 20141231 entry below for
97 information about prerequisites and upgrading, if you are not already
98 using clang 3.5.0 or higher.
101 r364092 modified the internal ABI used between the kernel NFS
102 modules. As such, all of these modules need to be rebuilt
103 from sources, so a version bump was done.
106 Makefile.inc has been updated to work around the issue documented in
107 20200729. It was a case where the optimization of using symbolic links
108 to point to binaries created a situation where we'd run new binaries
109 with old libraries starting midway through the installworld process.
112 r363679 has redefined some undefined behavior in regcomp(3); notably,
113 extraneous escapes of most ordinary characters will no longer be
114 accepted. An exp-run has identified all of the problems with this in
115 ports, but other non-ports software may need extra escapes removed to
116 continue to function.
118 Because of this change, installworld may encounter the following error
119 from rtld: Undefined symbol "regcomp@FBSD_1.6" -- It is imperative that
120 you do not halt installworld. Instead, let it run to completion (whether
121 successful or not) and run installworld once more.
124 A new implementation of bc and dc has been imported in r362681. This
125 implementation corrects non-conformant behavior of the previous bc
126 and adds GNU bc compatible options. It offers a number of extensions,
127 is much faster on large values, and has support for message catalogs
128 (a number of languages are already supported, contributions of further
129 languages welcome). The option WITHOUT_GH_BC can be used to build the
130 world with the previous versions of bc and dc.
133 r362639 changed the internal API used between the NFS kernel modules.
134 As such, they all need to be rebuilt from sources.
137 r362158 changed the arguments for VFS_CHECKEXP(). As such, any
138 out of tree file systems need to be modified and rebuilt.
139 Also, any file systems that are modules must be rebuilt.
142 read(2) of a directory fd is now rejected by default. root may
143 re-enable it for system root only on non-ZFS filesystems with the
144 security.bsd.allow_read_dir sysctl(8) MIB if
145 security.bsd.suser_enabled=1.
147 It may be advised to setup aliases for grep to default to `-d skip` if
148 commonly non-recursively grepping a list that includes directories and
149 the potential for the resulting stderr output is not tolerable. Example
150 aliases are now installed, commented out, in /root/.cshrc and
154 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
155 been upgraded to 10.0.1. Please see the 20141231 entry below for
156 information about prerequisites and upgrading, if you are not already
157 using clang 3.5.0 or higher.
160 Support for obsolete compilers has been removed from the build system.
161 Clang 6 and GCC 6.4 are the minimum supported versions.
164 closefrom(2) has been moved under COMPAT12, and replaced in libc with a
165 stub that calls close_range(2). If using a custom kernel configuration,
166 you may want to ensure that the COMPAT_FREEBSD12 option is included, as
167 a slightly older -CURRENT userland and older FreeBSD userlands may not
168 be functional without closefrom(2).
171 Upstream DTS from Linux 5.6 was merged and they now have the SID
172 and THS (Secure ID controller and THermal Sensor) node present.
173 The DTB overlays have now been removed from the tree for the H3/H5 and
174 A64 SoCs and the aw_sid and aw_thermal driver have been updated to
175 deal with upstream DTS. If you are using those overlays you need to
176 remove them from loader.conf and update the DTBs on the FAT partition.
179 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
180 been upgraded to 10.0.0. Please see the 20141231 entry below for
181 information about prerequisites and upgrading, if you are not already
182 using clang 3.5.0 or higher.
185 The amd(8) automount daemon has been removed from the source tree.
186 As of FreeBSD 10.1 autofs(5) is the preferred tool for automounting.
187 amd is still available in the sysutils/am-utils port.
190 Removed brooktree driver (bktr.4) from the tree.
193 The WITH_GPL_DTC option has been removed. The BSD-licenced device tree
194 compiler in usr.bin/dtc is used on all architectures which use dtc, and
195 the GPL dtc is available (if needed) from the sysutils/dtc port.
198 The WITHOUT_LLVM_LIBUNWIND option has been removed. LLVM's libunwind
199 is used by all supported CPU architectures.
202 GCC 4.2.1 has been removed from the tree. The WITH_GCC,
203 WITH_GCC_BOOTSTRAP, and WITH_GNUCXX options are no longer available.
204 Users who wish to build FreeBSD with GCC must use the external toolchain
208 ncurses has been updated to a newer version (6.2-20200215). Given the ABI
209 has changed, users will have to rebuild all the ports that are linked to
213 The size of struct vnet and the magic cookie have changed.
214 Users need to recompile libkvm and all modules using VIMAGE
215 together with their new kernel.
218 Defining the long deprecated NO_CTF, NO_DEBUG_FILES, NO_INSTALLLIB,
219 NO_MAN, NO_PROFILE, and NO_WARNS variables is now an error. Update
220 your Makefiles and scripts to define MK_<var>=no instead as required.
222 One exception to this is that program or library Makefiles should
223 define MAN to empty rather than setting MK_MAN=no.
226 Clang/LLVM is now the default compiler and LLD the default
230 make universe no longer uses GCC 4.2.1 on any architectures.
231 Architectures not supported by in-tree Clang/LLVM require an
232 external toolchain package.
235 GCC 4.2.1 is now not built by default, as part of the GCC 4.2.1
236 retirement plan. Specifically, the GCC, GCC_BOOTSTRAP, and GNUCXX
237 options default to off for all supported CPU architectures. As a
238 short-term transition aid they may be enabled via WITH_* options.
239 GCC 4.2.1 is expected to be removed from the tree on 2020-03-31.
242 Support for armv5 has been disconnected and is being removed. The
243 machine combination MACHINE=arm MACHINE_ARCH=arm is no longer valid.
244 You must now use a MACHINE_ARCH of armv6 or armv7. The default
245 MACHINE_ARCH for MACHINE=arm is now armv7.
248 Clang/LLVM is now the default compiler for all powerpc architectures.
249 LLD is now the default linker for powerpc64. The change for powerpc64
250 also includes a change to the ELFv2 ABI, incompatible with the existing
254 Kernel-loadable random(4) modules are no longer unloadable.
257 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
258 been upgraded to 9.0.1. Please see the 20141231 entry below for
259 information about prerequisites and upgrading, if you are not already
260 using clang 3.5.0 or higher.
263 r355677 has modified the internal interface used between the
264 NFS modules in the kernel. As such, they must all be upgraded
265 simultaneously. I will do a version bump for this.
268 The root certificates of the Mozilla CA Certificate Store have been
269 imported into the base system and can be managed with the certctl(8)
270 utility. If you have installed the security/ca_root_nss port or package
271 with the ETCSYMLINK option (the default), be advised that there may be
272 differences between those included in the port and those included in
273 base due to differences in nss branch used as well as general update
274 frequency. Note also that certctl(8) cannot manage certs in the
275 format used by the security/ca_root_nss port.
278 The amd(8) automount daemon has been disabled by default, and will be
279 removed in the future. As of FreeBSD 10.1 the autofs(5) is available
283 The nctgpio and wbwd drivers have been moved to the superio bus.
284 If you have one of these drivers in a kernel configuration, then
285 you should add device superio to it. If you use one of these drivers
286 as a module and you compile a custom set of modules, then you should
287 add superio to the set.
290 KPIs for network drivers to access interface addresses have changed.
291 Users need to recompile NIC driver modules together with kernel.
294 The net.link.tap.user_open sysctl no longer prevents user opening of
295 already created /dev/tapNN devices. Access is still controlled by
296 node permissions, just like tun devices. The net.link.tap.user_open
297 sysctl is now used only to allow users to perform devfs cloning of
298 tap devices, and the subsequent open may not succeed if the user is not
299 in the appropriate group. This sysctl may be deprecated/removed
300 completely in the future.
303 mips, powerpc, and sparc64 are no longer built as part of
304 universe / tinderbox unless MAKE_OBSOLETE_GCC is defined. If
305 not defined, mips, powerpc, and sparc64 builds will look for
306 the xtoolchain binaries and if installed use them for universe
307 builds. As llvm 9.0 becomes vetted for these architectures, they
308 will be removed from the list.
311 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
312 been upgraded to 9.0.0. Please see the 20141231 entry below for
313 information about prerequisites and upgrading, if you are not already
314 using clang 3.5.0 or higher.
317 The hpt27xx, hptmv, hptnr, and hptrr drivers have been removed from
318 GENERIC. They are available as modules and can be loaded by adding
319 to /boot/loader.conf hpt27xx_load="YES", hptmv_load="YES",
320 hptnr_load="YES", or hptrr_load="YES", respectively.
323 ntpd no longer by default locks its pages in memory, allowing them
324 to be paged out by the kernel. Use rlimit memlock to restore
325 historic BSD behaviour. For example, add "rlimit memlock 32"
326 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
329 Several of ping6's options have been renamed for better consistency
330 with ping. If you use any of -ARWXaghmrtwx, you must update your
331 scripts. See ping6(8) for details.
334 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
335 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
336 been removed from mount_fusefs(8). You can safely remove them from
337 your scripts, because they had no effect.
339 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
340 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
341 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
342 sysctls have been removed. If you felt the need to set any of them to
343 a non-default value, please tell asomers@FreeBSD.org why.
346 Default permissions on the /var/account/acct file (and copies of it
347 rotated by periodic daily scripts) are changed from 0644 to 0640
348 because the file contains sensitive information that should not be
349 world-readable. If the /var/account directory must be created by
350 rc.d/accounting, the mode used is now 0750. Admins who use the
351 accounting feature are encouraged to change the mode of an existing
352 /var/account directory to 0750 or 0700.
355 Entropy collection and the /dev/random device are no longer optional
356 components. The "device random" option has been removed.
357 Implementations of distilling algorithms can still be made loadable
358 with "options RANDOM_LOADABLE" (e.g., random_fortuna.ko).
361 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
362 been upgraded to 8.0.1. Please see the 20141231 entry below for
363 information about prerequisites and upgrading, if you are not already
364 using clang 3.5.0 or higher.
367 A fix was applied to i386 kernel modules to avoid panics with
368 dpcpu or vnet. Users need to recompile i386 kernel modules
369 having pcpu or vnet sections or they will refuse to load.
372 User-wired pages now have their own counter,
373 vm.stats.vm.v_user_wire_count. The vm.max_wired sysctl was renamed
374 to vm.max_user_wired and changed from an unsigned int to an unsigned
375 long. bhyve VMs wired with the -S are now subject to the user
376 wiring limit; the vm.max_user_wired sysctl may need to be tuned to
377 avoid running into the limit.
380 The IPSEC option has been removed from GENERIC. Users requiring
381 ipsec(4) must now load the ipsec(4) kernel module.
384 The tap(4) driver has been folded into tun(4), and the module has been
385 renamed to tuntap. You should update any kld_list="if_tap" or
386 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
387 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
388 module instead, and "device tap" or "device tun" entries in kernel
389 config files to select the tuntap device instead.
392 The following knobs have been added related to tradeoffs between
393 safe use of the random device and availability in the absence of
396 kern.random.initial_seeding.bypass_before_seeding: tunable; set
397 non-zero to bypass the random device prior to seeding, or zero to
398 block random requests until the random device is initially seeded.
399 For now, set to 1 (unsafe) by default to restore pre-r346250 boot
400 availability properties.
402 kern.random.initial_seeding.read_random_bypassed_before_seeding:
403 read-only diagnostic sysctl that is set when bypass is enabled and
404 read_random(9) is bypassed, to enable programmatic handling of this
405 initial condition, if desired.
407 kern.random.initial_seeding.arc4random_bypassed_before_seeding:
408 Similar to the above, but for for arc4random(9) initial seeding.
410 kern.random.initial_seeding.disable_bypass_warnings: tunable; set
411 non-zero to disable warnings in dmesg when the same conditions are
412 met as for the diagnostic sysctls above. Defaults to zero, i.e.,
413 produce warnings in dmesg when the conditions are met.
416 The loadable random module KPI has changed; the random_infra_init()
417 routine now requires a 3rd function pointer for a bool (*)(void)
418 method that returns true if the random device is seeded (and
419 therefore unblocked).
422 r345895 reverts r320698. This implies that an nfsuserd(8) daemon
423 built from head sources between r320757 (July 6, 2017) and
424 r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
425 is added to the command line.
426 nfsuserd daemons built from head sources that are post-r338192 are
427 not affected and should continue to work.
430 The fuse(4) module has been renamed to fusefs(4) for consistency with
431 other filesystems. You should update any kld_load="fuse" entries in
432 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
433 "options FUSE" entries in kernel config files.
436 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
437 8.0.0. Please see the 20141231 entry below for information about
438 prerequisites and upgrading, if you are not already using clang 3.5.0
442 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
443 compiled into your custom kernel, add 'device xz' statement to the
447 drm and drm2 have been removed from the tree. Please see
448 https://wiki.freebsd.org/Graphics for the latest information on
449 migrating to the drm ports.
452 Iflib is no longer unconditionally compiled into the kernel. Drivers
453 using iflib and statically compiled into the kernel, now require
454 the 'device iflib' config option. For the same drivers loaded as
455 modules on kernels not having 'device iflib', the iflib.ko module
456 is loaded automatically.
459 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
460 options no longer exist since r343219 and r343427 respectively;
461 nothing uses them, so they should be just removed from custom
465 r342635 changes the way efibootmgr(8) works by requiring users to add
466 the -b (bootnum) parameter for commands where the bootnum was previously
467 specified with each option. For example 'efibootmgr -B 0001' is now
468 'efibootmgr -B -b 0001'.
471 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
472 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
473 servers that have vfs.nfsd.nfs_privport set will only allow mounts
474 from clients using a reserved port#. Since both the FreeBSD and Linux
475 NFSv4 clients use reserved port#s by default, this should not affect
479 The XLP config has been removed. We can't support 64-bit atomics in this
480 kernel because it is running in 32-bit mode. XLP users must transition
481 to running a 64-bit kernel (XLP64 or XLPN32).
483 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
484 the preferred emulator today and we don't need two different ones.
486 The old sibyte / swarm / Broadcom BCM1250 support has been
487 removed from the mips port.
490 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
491 7.0.1. Please see the 20141231 entry below for information about
492 prerequisites and upgrading, if you are not already using clang 3.5.0
496 Remove the timed and netdate programs from the base tree. Setting
497 the time with these daemons has been obsolete for over a decade.
500 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
501 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
502 it produces broken binaries when ifuncs are in use. Users needing
503 GNU ld should install the binutils port or package.
506 The BSD crtbegin and crtend code has been enabled by default. It has
507 had extensive testing on amd64, arm64, and i386. It can be disabled
508 by building a world with -DWITHOUT_BSD_CRTBEGIN.
511 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
512 has been converted to a port (misc/ctm) and will be removed from
513 FreeBSD-13. It is available as a package (ctm) for all supported
517 The default newsyslog.conf(5) file has been changed to only include
518 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
519 the filenames end in '.conf' and do not begin with a '.'.
521 You should check the configuration files in these two directories match
522 this naming convention. You can verify which configuration files are
523 being included using the command:
527 Ports for the DRM modules have been simplified. Now, amd64 users should
528 just install the drm-kmod port. All others should install
531 Graphics hardware that's newer than about 2010 usually works with
532 drm-kmod. For hardware older than 2013, however, some users will need
533 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
534 than 2008 usually only works in drm-legacy-kmod. The graphics team can
535 only commit to hardware made since 2013 due to the complexity of the
536 market and difficulty to test all the older cards effectively. If you
537 have hardware supported by drm-kmod, you are strongly encouraged to use
538 that as you will get better support.
540 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
541 elsewhere, the drm and drm2 modules will be eliminated from the src base
542 soon (with a limited exception for arm). Please update to the package
543 asap and report any issues to x11@freebsd.org.
545 Generally, anybody using the drm*-kmod packages should add
546 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
547 cross-threading surprises, especially with automatic driver
548 loading from X11 startup. These will become the defaults in 13-current
552 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
553 custom kernel and module loading configuration files must be updated
554 accordingly. Moreover, interfaces previous presented as ixlvN to the
555 system are now exposed as iavfN and network configuration files must
556 be adjusted as necessary.
559 OpenSSL has been updated to version 1.1.1. This update included
560 additional various API changes throughout the base system. It is
561 important to rebuild third-party software after upgrading. The value
562 of __FreeBSD_version has been bumped accordingly.
565 The legacy DRM modules and drivers have now been added to the loader's
566 module blacklist, in favor of loading them with kld_list in rc.conf(5).
567 The module blacklist may be overridden with the loader.conf(5)
568 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
572 The cam(4) based nda(4) driver will be used over nvd(4) by default on
573 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
574 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
575 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
579 Reproducible build mode is now on by default, in preparation for
580 FreeBSD 12.0. This eliminates build metadata such as the user,
581 host, and time from the kernel (and uname), unless the working tree
582 corresponds to a modified checkout from a version control system.
583 The previous behavior can be obtained by setting the /etc/src.conf
584 knob WITHOUT_REPRODUCIBLE_BUILD.
587 The Yarrow CSPRNG has been removed from the kernel as it has not been
588 supported by its designers since at least 2003. Fortuna has been the
589 default since FreeBSD-11.
592 devctl freeze/thaw have gone into the tree, the rc scripts have been
593 updated to use them and devmatch has been changed. You should update
594 kernel, userland and rc scripts all at the same time.
597 The default interpreter has been switched from 4th to Lua.
598 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
599 interpreter. If you have custom FORTH code you will need to set
600 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
601 src.conf for the build. This will create default hard links between
602 loader and loader_4th instead of loader and loader_lua, the new default.
603 If you are using UEFI it will create the proper hard link to loader.efi.
605 bhyve uses userboot.so. It remains 4th-only until some issues are solved
606 regarding coexisting with multiple versions of FreeBSD are resolved.
609 ls(1) now respects the COLORTERM environment variable used in other
610 systems and software to indicate that a colored terminal is both
611 supported and desired. If ls(1) is suddenly emitting colors, they may
612 be disabled again by either removing the unwanted COLORTERM from your
613 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
614 may not be observed in a future release.
617 The default pager for most commands has been changed to "less". To
618 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
622 The jedec_ts(4) driver has been removed. A superset of its functionality
623 is available in the jedec_dimm(4) driver, and the manpage for that
624 driver includes migration instructions. If you have "device jedec_ts"
625 in your kernel configuration file, it must be removed.
628 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
629 This should have no effect if the kernel is booted via BIOS/legacy boot.
630 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
631 has a buggy firmware that prevents a successful boot due to use of
635 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
636 support has been removed from the tree. These ports were
637 obsolete and/or known to be broken for many years.
640 loader.efi has been augmented to participate more fully in the
641 UEFI boot manager protocol. loader.efi will now look at the
642 BootXXXX environment variable to determine if a specific kernel
643 or root partition was specified. XXXX is derived from BootCurrent.
644 efibootmgr(8) manages these standard UEFI variables.
647 zfsloader's functionality has now been folded into loader.
648 zfsloader is no longer necessary once you've updated your
649 boot blocks. For a transition period, we will install a
650 hardlink for zfsloader to loader to allow a smooth transition
651 until the boot blocks can be updated (hard link because old
652 zfs boot blocks don't understand symlinks).
655 ARM64 now have efifb support, if you want to have serial console
656 on your arm64 board when an screen is connected and the bootloader
657 setup a frame buffer for us to use, just add :
661 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
662 an screen connected as the firmware will setup a frame buffer are that
663 u-boot will expose as an EFI frame buffer.
666 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
667 or take steps to update /etc/passwd before doing installworld on
668 existing systems. Do not skip the "mergemaster -Fp" step before
669 installworld, as described in the update procedures near the bottom
670 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
671 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
672 the ntp config file contain options that change file/dir locations.
673 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
674 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
675 taking steps to ensure that all required files/dirs are accessible
679 Big endian arm support has been removed.
682 The static environment setup in kernel configs is no longer mutually
683 exclusive with the loader(8) environment by default. In order to
684 restore the previous default behavior of disabling the loader(8)
685 environment if a static environment is present, you must specify
686 loader_env.disabled=1 in the static environment.
689 The ABI of syscalls used by management tools like sockstat and
690 netstat has been broken to allow 32-bit binaries to work on
691 64-bit kernels without modification. These programs will need
692 to match the kernel in order to function. External programs may
693 require minor modifications to accommodate a change of type in
694 structures from pointers to 64-bit virtual addresses.
697 On i386 and amd64 atomics are now inlined. Out of tree modules using
698 atomics will need to be rebuilt.
701 The '%I' format in the kern.corefile sysctl limits the number of
702 core files that a process can generate to the number stored in the
703 debug.ncores sysctl. The '%I' format is replaced by the single digit
704 index. Previously, if all indexes were taken the kernel would overwrite
705 only a core file with the highest index in a filename.
706 Currently the system will create a new core file if there is a free
707 index or if all slots are taken it will overwrite the oldest one.
710 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
711 6.0.1. Please see the 20141231 entry below for information about
712 prerequisites and upgrading, if you are not already using clang 3.5.0
716 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
717 needed to be changed to work with it. This change was made with r335763
718 and requires a mergemaster / etcupdate / etc to update the installed
722 r334930 changed the interface between the NFS modules, so they all
723 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
726 As of r334391 lld is the default amd64 system linker; it is installed
727 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
731 The kernel / userland interface for devinfo changed, so you'll
732 need a new kernel and userland as a pair for it to work (rebuilding
733 lib/libdevinfo is all that's required). devinfo and devmatch will
734 not work, but everything else will when there's a mismatch.
737 The on-disk format for hwpmc callchain records has changed to include
738 threadid corresponding to a given record. This changes the field offsets
739 and thus requires that libpmcstat be rebuilt before using a kernel
743 The vxge(4) driver has been removed. This driver was introduced into
744 HEAD one week before the Exar left the Ethernet market and is not
745 known to be used. If you have device vxge in your kernel config file
749 The amd64 kernel now requires a ld that supports ifunc to produce a
750 working kernel, either lld or a newer binutils. lld is built by default
751 on amd64, and the 'buildkernel' target uses it automatically. However,
752 it is not the default linker, so building the kernel the traditional
753 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
754 binutils port/package). lld will soon be default, and this requirement
757 NOTE: As of r334391 lld is the default system linker on amd64, and no
758 workaround is necessary.
761 The nxge(4) driver has been removed. This driver was for PCI-X 10g
762 cards made by s2io/Neterion. The company was acquired by Exar and
763 no longer sells or supports Ethernet products. If you have device
764 nxge in your kernel config file it must be removed.
767 The tz database (tzdb) has been updated to 2018e. This version more
768 correctly models time stamps in time zones with negative DST such as
769 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
770 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
771 time zone abbreviations and the tm_isdst flag.
774 The ixgb(4) driver has been removed. This driver was for an early and
775 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
776 quickly shifted to the long lived ixgbe family. If you have device
777 ixgb in your kernel config file it must be removed.
780 The lmc(4) driver has been removed. This was a WAN interface
781 card that was already reportedly rare in 2003, and had an ambiguous
782 license. If you have device lmc in your kernel config file it must
786 Support for Arcnet networks has been removed. If you have device
787 arcnet or device cm in your kernel config file they must be
791 Support for FDDI networks has been removed. If you have device
792 fddi or device fpa in your kernel config file they must be
796 In addition to supporting RFC 3164 formatted messages, the
797 syslogd(8) service is now capable of parsing RFC 5424 formatted
798 log messages. The main benefit of using RFC 5424 is that clients
799 may now send log messages with timestamps containing year numbers,
800 microseconds and time zone offsets.
802 Similarly, the syslog(3) C library function has been altered to
803 send RFC 5424 formatted messages to the local system logging
804 daemon. On systems using syslogd(8), this change should have no
805 negative impact, as long as syslogd(8) and the C library are
806 updated at the same time. On systems using a different system
807 logging daemon, it may be necessary to make configuration
808 adjustments, depending on the software used.
810 When using syslog-ng, add the 'syslog-protocol' flag to local
811 input sources to enable parsing of RFC 5424 formatted messages:
814 unix-dgram("/var/run/log" flags(syslog-protocol));
817 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
818 of the 'imuxsock' module to let messages be processed by the
819 regular RFC 3164/5424 parsing pipeline:
821 module(load="imuxsock" SysSock.UseSpecialParser="off")
823 Do note that these changes only affect communication between local
824 applications and syslogd(8). The format that syslogd(8) uses to
825 store messages on disk or forward messages to other systems
826 remains unchanged. syslogd(8) still uses RFC 3164 for these
827 purposes. Options to customize this behaviour will be added in the
828 future. Utilities that process log files stored in /var/log are
829 thus expected to continue to function as before.
831 __FreeBSD_version has been incremented to 1200061 to denote this
835 Support for token ring networks has been removed. If you
836 have "device token" in your kernel config you should remove
837 it. No device drivers supported token ring.
840 makefs was modified to be able to tag ISO9660 El Torito boot catalog
841 entries as EFI instead of overloading the i386 tag as done previously.
842 The amd64 mkisoimages.sh script used to build amd64 ISO images for
843 release was updated to use this. This may mean that makefs must be
844 updated before "make cdrom" can be run in the release directory. This
845 should be as simple as:
847 $ cd $SRCDIR/usr.sbin/makefs
848 $ make depend all install
851 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
852 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
853 Co-existence for the transition period will come shortly. Booting is a
854 complex environment and test coverage for Lua-enabled loaders has been
855 thin, so it would be prudent to assume it might not work and make
856 provisions for backup boot methods.
859 devmatch functionality has been turned on in devd. It will automatically
860 load drivers for unattached devices. This may cause unexpected drivers
861 to be loaded. Please report any problems to current@ and
865 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
866 6.0.0. Please see the 20141231 entry below for information about
867 prerequisites and upgrading, if you are not already using clang 3.5.0
871 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
872 This means it is used to link the kernel and userland libraries and
873 executables, but is not yet installed as /usr/bin/ld by default.
875 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
876 WITHOUT_LLD_BOOTSTRAP=yes
879 On i386, pmtimer has been removed. Its functionality has been folded
880 into apm. It was a no-op on ACPI in current for a while now (but was
881 still needed on i386 in FreeBSD 11 and earlier). Users may need to
882 remove it from kernel config files.
885 The use of RSS hash from the network card aka flowid has been
886 disabled by default for lagg(4) as it's currently incompatible with
887 the lacp and loadbalance protocols.
889 This can be re-enabled by setting the following in loader.conf:
890 net.link.lagg.default_use_flowid="1"
893 The SW_WATCHDOG option is no longer necessary to enable the
894 hardclock-based software watchdog if no hardware watchdog is
895 configured. As before, SW_WATCHDOG will cause the software
896 watchdog to be enabled even if a hardware watchdog is configured.
899 r326887 fixes the issue described in the 20171214 UPDATING entry.
900 r326888 flips the switch back to building GELI support always.
903 r362593 broke ZFS + GELI support for reasons unknown. However,
904 it also broke ZFS support generally, so GELI has been turned off
905 by default as the lesser evil in r326857. If you boot off ZFS and/or
906 GELI, it might not be a good time to update.
909 PowerPC users must update loader(8) by rebuilding world before
910 installing a new kernel, as the protocol connecting them has
911 changed. Without the update, loader metadata will not be passed
912 successfully to the kernel and users will have to enter their
913 root partition at the kernel mountroot prompt to continue booting.
914 Newer versions of loader can boot old kernels without issue.
917 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
918 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
919 to WITH/OUT_LOADER_GELI.
922 The naive and non-compliant support of posix_fallocate(2) in ZFS
923 has been removed as of r325320. The system call now returns EINVAL
924 when used on a ZFS file. Although the new behavior complies with the
925 standard, some consumers are not prepared to cope with it.
926 One known victim is lld prior to r325420.
929 Building in a FreeBSD src checkout will automatically create object
930 directories now rather than store files in the current directory if
931 'make obj' was not ran. Calling 'make obj' is no longer necessary.
932 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
933 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
937 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
938 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
939 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
940 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
941 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
942 The UNIFIED_OBJDIR option is a transitional feature that will be
943 removed for 12.0 release; please migrate to the new format for any
944 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
945 than hardcoding paths.
948 The native-xtools target no longer installs the files by default to the
949 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
950 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
953 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
954 options are changing from controlling the build if defined / undefined
955 to controlling the build with explicit 'yes' or 'no' values. They will
956 shift to WITH/WITHOUT options to match other options in the system.
959 libstand has turned into a private library for sys/boot use only.
960 It is no longer supported as a public interface outside of sys/boot.
963 The arm port has split armv6 into armv6 and armv7. armv7 is now
964 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
965 and are running a kernel from before r324363, you will need to add
966 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
969 When building multiple kernels using KERNCONF, non-existent KERNCONF
970 files will produce an error and buildkernel will fail. Previously
971 missing KERNCONF files silently failed giving no indication as to
972 why, only to subsequently discover during installkernel that the
973 desired kernel was never built in the first place.
976 The default serial number format for CTL LUNs has changed. This will
977 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
978 or iSCSI clients care about their LUNs' serial numbers. Users who
979 require serial number stability should hardcode serial numbers in
983 For 32-bit arm compiled for hard-float support, soft-floating point
984 binaries now always get their shared libraries from
985 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
986 /usr/libsoft also existed). Only users with a hard-float ld.so, but
987 soft-float everything else should be affected.
990 The geli password typed at boot is now hidden. To restore the previous
991 behavior, see geli(8) for configuration options.
994 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
995 sysctl values. Minor nit, but requires a rebuild of both world/kernel
999 "make check" behavior (made in ^/head@r295380) has been changed to
1000 execute from a limited sandbox, as opposed to executing from
1004 - The "beforecheck" and "aftercheck" targets are now specified.
1005 - ${CHECKDIR} (added in commit noted above) has been removed.
1006 - Legacy behavior can be enabled by setting
1007 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
1009 If the limited sandbox mode is enabled, "make check" will execute
1010 "make distribution", then install, execute the tests, and clean up the
1011 sandbox if successful.
1013 The "make distribution" and "make install" targets are typically run as
1014 root to set appropriate permissions and ownership at installation time.
1015 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
1016 environment if executing "make check" with limited sandbox mode using
1017 an unprivileged user.
1020 Since the switch to GPT disk labels, fsck for UFS/FFS has been
1021 unable to automatically find alternate superblocks. As of r322297,
1022 the information needed to find alternate superblocks has been
1023 moved to the end of the area reserved for the boot block.
1024 Filesystems created with a newfs of this vintage or later
1025 will create the recovery information. If you have a filesystem
1026 created prior to this change and wish to have a recovery block
1027 created for your filesystem, you can do so by running fsck in
1028 foreground mode (i.e., do not use the -p or -y options). As it
1029 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
1030 to which you should answer yes.
1033 As of r321665, an NFSv4 server configuration that services
1034 Kerberos mounts or clients that do not support the uid/gid in
1035 owner/owner_group string capability, must explicitly enable
1036 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
1037 machine's /etc/rc.conf file.
1040 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
1041 Please see the 20141231 entry below for information about prerequisites
1042 and upgrading, if you are not already using clang 3.5.0 or higher.
1045 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
1046 r-commands (rlogin, rsh, etc.) to be built with the base system.
1049 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
1050 a very major ABI incompatible change, so users of FreeBSD/powerpc must
1051 be careful when performing source upgrades. It is best to run
1052 'make installworld' from an alternate root system, either a live
1053 CD/memory stick, or a temporary root partition. Additionally, all ports
1054 must be recompiled. powerpc64 is largely unaffected, except in the case
1055 of 32-bit compatibility. All 32-bit binaries will be affected.
1058 Forward compatibility for the "ino64" project have been committed. This
1059 will allow most new binaries to run on older kernels in a limited
1060 fashion. This prevents many of the common foot-shooting actions in the
1061 upgrade as well as the limited ability to roll back the kernel across
1062 the ino64 upgrade. Complicated use cases may not work properly, though
1063 enough simpler ones work to allow recovery in most situations.
1066 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
1067 if you require the GPL compiler.
1070 The internal ABI used for communication between the NFS kernel modules
1071 was changed by r320085, so __FreeBSD_version was bumped to
1072 ensure all the NFS related modules are updated together.
1075 The ABI of struct event was changed by extending the data
1076 member to 64bit and adding ext fields. For upgrade, same
1077 precautions as for the entry 20170523 "ino64" must be
1081 The GNU roff toolchain has been removed from base. To render manpages
1082 which are not supported by mandoc(1), man(1) can fallback on GNU roff
1083 from ports (and recommends to install it).
1084 To render roff(7) documents, consider using GNU roff from ports or the
1085 heirloom doctools roff toolchain from ports via pkg install groff or
1086 via pkg install heirloom-doctools.
1089 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
1090 smaller runtime footprint builds. This is useful for embedded systems
1091 which only require one chipset support.
1093 If you load it as a module, make sure this is in /boot/loader.conf:
1097 This will load the HAL, all chip/RF backends and if_ath_pci.
1098 If you have if_ath_pci in /boot/loader.conf, ensure it is after
1099 if_ath or it will not load any HAL chipset support.
1101 If you want to selectively load things (eg on ye cheape ARM/MIPS
1102 platforms where RAM is at a premium) you should:
1105 * load the chip modules in question
1106 * load ath_rate, ath_dfs
1108 * load if_ath_pci and/or if_ath_ahb depending upon your particular
1109 bus bind type - this is where probe/attach is done.
1111 For further comments/feedback, poke adrian@ .
1114 The "ino64" 64-bit inode project has been committed, which extends
1115 a number of types to 64 bits. Upgrading in place requires care and
1116 adherence to the documented upgrade procedure.
1118 If using a custom kernel configuration ensure that the
1119 COMPAT_FREEBSD11 option is included (as during the upgrade the
1120 system will be running the ino64 kernel with the existing world).
1122 For the safest in-place upgrade begin by removing previous build
1123 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full
1124 procedure documented below under the heading "To rebuild everything and
1125 install it on the current system." Specifically, a reboot is required
1126 after installing the new kernel before installing world. While an
1127 installworld normally works by accident from multiuser after rebooting
1128 the proper kernel, there are many cases where this will fail across this
1129 upgrade and installworld from single user is required.
1132 The NATM framework including the en(4), fatm(4), hatm(4), and
1133 patm(4) devices has been removed. Consumers should plan a
1134 migration before the end-of-life date for FreeBSD 11.
1137 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
1138 diff has not been implemented, if those are needed a newer version of
1139 GNU diff is available via the diffutils package under the gdiff name.
1142 As of r316810 for ipfilter, keep frags is no longer assumed when
1143 keep state is specified in a rule. r316810 aligns ipfilter with
1144 documentation in man pages separating keep frags from keep state.
1145 This allows keep state to be specified without forcing keep frags
1146 and allows keep frags to be specified independently of keep state.
1147 To maintain previous behaviour, also specify keep frags with
1148 keep state (as documented in ipf.conf.5).
1151 arm64 builds now use the base system LLD 4.0.0 linker by default,
1152 instead of requiring that the aarch64-binutils port or package be
1153 installed. To continue using aarch64-binutils, set
1154 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
1157 The UDP optimization in entry 20160818 that added the sysctl
1158 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
1159 packets will no longer be treated as L3 broadcast packets.
1162 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
1163 use any explicitly assigned loopback address available in the jail
1164 instead of using the first assigned address of the jail.
1167 The ctl.ko module no longer implements the iSCSI target frontend:
1168 cfiscsi.ko does instead.
1170 If building cfiscsi.ko as a kernel module, the module can be loaded
1171 via one of the following methods:
1172 - `cfiscsi_load="YES"` in loader.conf(5).
1173 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
1174 - ctladm(8)/ctld(8), when compiled with iSCSI support
1175 (`WITH_ISCSI=yes` in src.conf(5))
1177 Please see cfiscsi(4) for more details.
1180 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
1181 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
1182 same source (previously, the dependency of mmcsd.ko on mmc.ko was
1183 missing, but mmcsd.ko now will refuse to load if it is incompatible
1187 The syntax of ipfw(8) named states was changed to avoid ambiguity.
1188 If you have used named states in the firewall rules, you need to modify
1189 them after installworld and before rebooting. Now named states must
1190 be prefixed with colon.
1193 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
1194 removed as the userland we provide cannot use them. The KMS version
1195 (sys/dev/drm2) supports the same hardware.
1198 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
1199 Please see the 20141231 entry below for information about prerequisites
1200 and upgrading, if you are not already using clang 3.5.0 or higher.
1203 The code that provides support for ZFS .zfs/ directory functionality
1204 has been reimplemented. It's not possible now to create a snapshot
1205 by mkdir under .zfs/snapshot/. That should be the only user visible
1209 EISA bus support has been removed. The WITH_EISA option is no longer
1213 MCA bus support has been removed.
1216 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
1217 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
1220 The EM_MULTIQUEUE kernel configuration option is deprecated now that
1221 the em(4) driver conforms to iflib specifications.
1224 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
1225 IFLIB. If you have a custom kernel configuration that excludes em(4)
1226 but you use igb(4), you need to re-add em(4) to your custom
1230 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
1231 Please see the 20141231 entry below for information about prerequisites
1232 and upgrading, if you are not already using clang 3.5.0 or higher.
1235 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
1236 Please see the 20141231 entry below for information about prerequisites
1237 and upgrading, if you are not already using clang 3.5.0 or higher.
1240 The layout of the pmap structure has changed for powerpc to put the pmap
1241 statistics at the front for all CPU variations. libkvm(3) and all tools
1242 that link against it need to be recompiled.
1245 isl(4) and cyapa(4) drivers now require a new driver,
1246 chromebook_platform(4), to work properly on Chromebook-class hardware.
1247 On other types of hardware the drivers may need to be configured using
1248 device hints. Please see the corresponding manual pages for details.
1251 The urtwn(4) driver was merged into rtwn(4) and now consists of
1252 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
1254 Also, firmware for RTL8188CE was renamed due to possible name
1255 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
1258 GNU rcs has been removed from base. It is available as packages:
1259 - rcs: Latest GPLv3 GNU rcs version.
1260 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
1264 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
1265 modules now requires that the kernel configuration contain the
1266 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
1269 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
1270 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
1273 Relocatable object files with the extension of .So have been renamed
1274 to use an extension of .pico instead. The purpose of this change is
1275 to avoid a name clash with shared libraries on case-insensitive file
1276 systems. On those file systems, foo.So is the same file as foo.so.
1279 GNU rcs has been turned off by default. It can (temporarily) be built
1280 again by adding WITH_RCS knob in src.conf.
1281 Otherwise, GNU rcs is available from packages:
1282 - rcs: Latest GPLv3 GNU rcs version.
1283 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
1286 The backup_uses_rcs functionality has been removed from rc.subr.
1289 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
1290 two separate components, QUEUE_MACRO_DEBUG_TRACE and
1291 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
1292 QUEUE_MACRO_DEBUG behavior.
1295 r304787 changed some ioctl interfaces between the iSCSI userspace
1296 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1297 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1301 The UDP receive code has been updated to only treat incoming UDP
1302 packets that were addressed to an L2 broadcast address as L3
1303 broadcast packets. It is not expected that this will affect any
1304 standards-conforming UDP application. The new behaviour can be
1305 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1309 Remove the openbsd_poll system call.
1310 __FreeBSD_version has been bumped because of this.
1313 The stable/11 branch has been created from head@r302406.
1316 The libc stub for the pipe(2) system call has been replaced with
1317 a wrapper that calls the pipe2(2) system call and the pipe(2)
1318 system call is now only implemented by the kernels that include
1319 "options COMPAT_FREEBSD10" in their config file (this is the
1320 default). Users should ensure that this option is enabled in
1321 their kernel or upgrade userspace to r302092 before upgrading their
1325 CAM will now strip leading spaces from SCSI disks' serial numbers.
1326 This will affect users who create UFS filesystems on SCSI disks using
1327 those disk's diskid device nodes. For example, if /etc/fstab
1328 previously contained a line like
1329 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
1330 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
1331 transforms like gmirror may also be affected. ZFS users should
1335 The bitstring(3) API has been updated with new functionality and
1336 improved performance. But it is binary-incompatible with the old API.
1337 Objects built with the new headers may not be linked against objects
1338 built with the old headers.
1341 The brk and sbrk functions have been removed from libc on arm64.
1342 Binutils from ports has been updated to not link to these
1343 functions and should be updated to the latest version before
1344 installing a new libc.
1347 The armv6 port now defaults to hard float ABI. Limited support
1348 for running both hardfloat and soft float on the same system
1349 is available using the libraries installed with -DWITH_LIBSOFT.
1350 This has only been tested as an upgrade path for installworld
1351 and packages may fail or need manual intervention to run. New
1352 packages will be needed.
1354 To update an existing self-hosted armv6hf system, you must add
1355 TARGET_ARCH=armv6 on the make command line for both the build
1356 and the install steps.
1359 Kernel modules compiled outside of a kernel build now default to
1360 installing to /boot/modules instead of /boot/kernel. Many kernel
1361 modules built this way (such as those in ports) already overrode
1362 KMODDIR explicitly to install into /boot/modules. However,
1363 manually building and installing a module from /sys/modules will
1364 now install to /boot/modules instead of /boot/kernel.
1367 The CAM I/O scheduler has been committed to the kernel. There should be
1368 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1369 list of known rogues that claim support for this but actually corrupt
1370 data is believed to be complete, be on the lookout for data
1371 corruption. The known rogue list is believed to be complete:
1373 o Crucial MX100, M550 drives with MU01 firmware.
1374 o Micron M510 and M550 drives with MU01 firmware.
1375 o Micron M500 prior to MU07 firmware
1376 o Samsung 830, 840, and 850 all firmwares
1377 o FCCT M500 all firmwares
1379 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1380 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1381 updated firmware. Black listed drives will work correctly because these
1382 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1383 this list is the same as found in Linux, it's believed there are no
1384 other rogues in the market place. All other models from the above
1387 To be safe, if you are at all concerned, you can quirk each of your
1388 drives to prevent NCQ from being sent by setting:
1389 kern.cam.ada.X.quirks="0x2"
1390 in loader.conf. If the drive requires the 4k sector quirk, set the
1391 quirks entry to 0x3.
1394 The FAST_DEPEND build option has been removed and its functionality is
1395 now the one true way. The old mkdep(1) style of 'make depend' has
1396 been removed. See 20160311 for further details.
1399 Resource range types have grown from unsigned long to uintmax_t. All
1400 drivers, and anything using libdevinfo, need to be recompiled.
1403 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1404 builds. It no longer runs mkdep(1) during 'make depend', and the
1405 'make depend' stage can safely be skipped now as it is auto ran
1406 when building 'make all' and will generate all SRCS and DPSRCS before
1407 building anything else. Dependencies are gathered at compile time with
1408 -MF flags kept in separate .depend files per object file. Users should
1409 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1410 stale .depend files.
1413 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1414 kernel modules. Therefore, if you load any kernel modules at boot time,
1415 please install the boot loaders after you install the kernel, but before
1419 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1420 make installkernel KERNCONF=YOUR_KERNEL_HERE
1421 make -C sys/boot install
1422 <reboot in single user>
1424 Then follow the usual steps, described in the General Notes section,
1428 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1429 see the 20141231 entry below for information about prerequisites and
1430 upgrading, if you are not already using clang 3.5.0 or higher.
1433 The AIO subsystem is now a standard part of the kernel. The
1434 VFS_AIO kernel option and aio.ko kernel module have been removed.
1435 Due to stability concerns, asynchronous I/O requests are only
1436 permitted on sockets and raw disks by default. To enable
1437 asynchronous I/O requests on all file types, set the
1438 vfs.aio.enable_unsafe sysctl to a non-zero value.
1441 The ELF object manipulation tool objcopy is now provided by the
1442 ELF Tool Chain project rather than by GNU binutils. It should be a
1443 drop-in replacement, with the addition of arm64 support. The
1444 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1445 to obtain the GNU version if necessary.
1448 Building ZFS pools on top of zvols is prohibited by default. That
1449 feature has never worked safely; it's always been prone to deadlocks.
1450 Using a zvol as the backing store for a VM guest's virtual disk will
1451 still work, even if the guest is using ZFS. Legacy behavior can be
1452 restored by setting vfs.zfs.vol.recursive=1.
1455 The NONE and HPN patches has been removed from OpenSSH. They are
1456 still available in the security/openssh-portable port.
1459 With the addition of ypldap(8), a new _ypldap user is now required
1460 during installworld. "mergemaster -p" can be used to add the user
1461 prior to installworld, as documented in the handbook.
1464 The tftp loader (pxeboot) now uses the option root-path directive. As a
1465 consequence it no longer looks for a pxeboot.4th file on the tftp
1466 server. Instead it uses the regular /boot infrastructure as with the
1470 The code to start recording plug and play data into the modules has
1471 been committed. While the old tools will properly build a new kernel,
1472 a number of warnings about "unknown metadata record 4" will be produced
1473 for an older kldxref. To avoid such warnings, make sure to rebuild
1474 the kernel toolchain (or world). Make sure that you have r292078 or
1475 later when trying to build 292077 or later before rebuilding.
1478 Debug data files are now built by default with 'make buildworld' and
1479 installed with 'make installworld'. This facilitates debugging but
1480 requires more disk space both during the build and for the installed
1481 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1485 r291527 changed the internal interface between the nfsd.ko and
1486 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1487 __FreeBSD_version has been bumped because of this.
1490 Add support for unicode collation strings leads to a change of
1491 order of files listed by ls(1) for example. To get back to the old
1492 behaviour, set LC_COLLATE environment variable to "C".
1494 Databases administrators will need to reindex their databases given
1495 collation results will be different.
1497 Due to a bug in install(1) it is recommended to remove the ancient
1498 locales before running make installworld.
1500 rm -rf /usr/share/locale/*
1503 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1504 libcrypto.so.7 or libssl.so.7 must be recompiled.
1507 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1508 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1509 should be replaced with isp_2400 and isp_2500 modules respectively.
1512 The build previously allowed using 'make -n' to not recurse into
1513 sub-directories while showing what commands would be executed, and
1514 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1515 and 'make -N' will not.
1518 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1519 and etcupdate will now use this file. A custom sendmail.cf is now
1520 updated via this mechanism rather than via installworld. If you had
1521 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1522 want to remove the exclusion or change it to "always install".
1523 /etc/mail/sendmail.cf is now managed the same way regardless of
1524 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1525 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1528 Compatibility shims for legacy ATA device names have been removed.
1529 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1530 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1531 environment variables, /dev/ad* and /dev/ar* symbolic links.
1534 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1535 Please see the 20141231 entry below for information about prerequisites
1536 and upgrading, if you are not already using clang 3.5.0 or higher.
1539 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1540 and renamed from .symbols to .debug. This reduces the size requirements
1541 on the boot partition or file system and provides consistency with
1542 userland debug files.
1544 When using the supported kernel installation method the
1545 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1546 as is done with /boot/kernel.
1548 Developers wishing to maintain the historical behavior of installing
1549 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1552 The wireless drivers had undergone changes that remove the 'parent
1553 interface' from the ifconfig -l output. The rc.d network scripts
1554 used to check presence of a parent interface in the list, so old
1555 scripts would fail to start wireless networking. Thus, etcupdate(3)
1556 or mergemaster(8) run is required after kernel update, to update your
1557 rc.d scripts in /etc.
1560 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1561 These configurations are now automatically interpreted as
1562 'scrub fragment reassemble'.
1565 Kernel-loadable modules for the random(4) device are back. To use
1566 them, the kernel must have
1569 options RANDOM_LOADABLE
1571 kldload(8) can then be used to load random_fortuna.ko
1572 or random_yarrow.ko. Please note that due to the indirect
1573 function calls that the loadable modules need to provide,
1574 the build-in variants will be slightly more efficient.
1576 The random(4) kernel option RANDOM_DUMMY has been retired due to
1577 unpopularity. It was not all that useful anyway.
1580 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1581 Control over building the ELF Tool Chain tools is now provided by
1582 the WITHOUT_TOOLCHAIN knob.
1585 The polarity of Pulse Per Second (PPS) capture events with the
1586 uart(4) driver has been corrected. Prior to this change the PPS
1587 "assert" event corresponded to the trailing edge of a positive PPS
1588 pulse and the "clear" event was the leading edge of the next pulse.
1590 As the width of a PPS pulse in a typical GPS receiver is on the
1591 order of 1 millisecond, most users will not notice any significant
1592 difference with this change.
1594 Anyone who has compensated for the historical polarity reversal by
1595 configuring a negative offset equal to the pulse width will need to
1596 remove that workaround.
1599 The default group assigned to /dev/dri entries has been changed
1600 from 'wheel' to 'video' with the id of '44'. If you want to have
1601 access to the dri devices please add yourself to the video group
1604 # pw groupmod video -m $USER
1607 The menu.rc and loader.rc files will now be replaced during
1608 upgrades. Please migrate local changes to menu.rc.local and
1609 loader.rc.local instead.
1612 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1613 strings and strip have been removed. The src.conf(5) knob
1614 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1617 As ZFS requires more kernel stack pages than is the default on some
1618 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1619 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1621 Please consider using 'options KSTACK_PAGES=X' where X is greater
1622 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1625 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1626 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1627 default, i.e., they will not contain "::". For example, instead
1628 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1629 to have a more specific match, such as different map entries for
1630 IPv6:0:0 vs IPv6:0. This change requires that configuration
1631 data (including maps, files, classes, custom ruleset, etc.) must
1632 use the same format, so make certain such configuration data is
1633 upgrading. As a very simple check search for patterns like
1634 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1635 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1636 the cf option UseCompressedIPv6Addresses.
1639 The default kernel entropy-processing algorithm is now
1640 Fortuna, replacing Yarrow.
1642 Assuming you have 'device random' in your kernel config
1643 file, the configurations allow a kernel option to override
1644 this default. You may choose *ONE* of:
1646 options RANDOM_YARROW # Legacy /dev/random algorithm.
1647 options RANDOM_DUMMY # Blocking-only driver.
1649 If you have neither, you get Fortuna. For most people,
1650 read no further, Fortuna will give a /dev/random that works
1651 like it always used to, and the difference will be irrelevant.
1653 If you remove 'device random', you get *NO* kernel-processed
1654 entropy at all. This may be acceptable to folks building
1655 embedded systems, but has complications. Carry on reading,
1656 and it is assumed you know what you need.
1658 *PLEASE* read random(4) and random(9) if you are in the
1659 habit of tweaking kernel configs, and/or if you are a member
1660 of the embedded community, wanting specific and not-usual
1661 behaviour from your security subsystems.
1663 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1664 random', you will NOT have a functioning /dev/random, and
1665 many cryptographic features will not work, including SSH.
1666 You may also find strange behaviour from the random(3) set
1667 of library functions, in particular sranddev(3), srandomdev(3)
1668 and arc4random(3). The reason for this is that the KERN_ARND
1669 sysctl only returns entropy if it thinks it has some to
1670 share, and with RANDOM_DUMMY or no 'device random' this
1674 An additional fix for the issue described in the 20150614 sendmail
1675 entry below has been committed in revision 284717.
1678 FreeBSD's old make (fmake) has been removed from the system. It is
1679 available as the devel/fmake port or via pkg install fmake.
1682 The fix for the issue described in the 20150614 sendmail entry
1683 below has been committed in revision 284436. The work
1684 around described in that entry is no longer needed unless the
1685 default setting is overridden by a confDH_PARAMETERS configuration
1686 setting of '5' or pointing to a 512 bit DH parameter file.
1689 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1690 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1691 and devel/kyua to version 0.20+ and adjust any calling code to work
1692 with Kyuafile and kyua.
1695 The import of openssl to address the FreeBSD-SA-15:10.openssl
1696 security advisory includes a change which rejects handshakes
1697 with DH parameters below 768 bits. sendmail releases prior
1698 to 8.15.2 (not yet released), defaulted to a 512 bit
1699 DH parameter setting for client connections. To work around
1700 this interoperability, sendmail can be configured to use a
1701 2048 bit DH parameter by:
1703 1. Edit /etc/mail/`hostname`.mc
1704 2. If a setting for confDH_PARAMETERS does not exist or
1705 exists and is set to a string beginning with '5',
1706 replace it with '2'.
1707 3. If a setting for confDH_PARAMETERS exists and is set to
1708 a file path, create a new file with:
1709 openssl dhparam -out /path/to/file 2048
1710 4. Rebuild the .cf file:
1711 cd /etc/mail/; make; make install
1712 5. Restart sendmail:
1713 cd /etc/mail/; make restart
1715 A sendmail patch is coming, at which time this file will be
1719 Generation of legacy formatted entries have been disabled by default
1720 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1721 entries were converted to use the new format by default when the new,
1722 machine independent format have been added and supported since FreeBSD
1725 Please see the pwd_mkdb(8) manual page for further details.
1728 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1729 20141231 entry below for information about prerequisites and upgrading,
1730 if you are not already using 3.5.0 or higher.
1733 TI platform code switched to using vendor DTS files and this update
1734 may break existing systems running on Beaglebone, Beaglebone Black,
1737 - dtb files should be regenerated/reinstalled. Filenames are the
1738 same but content is different now
1739 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1740 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1741 addressing scheme is now pin 25 on /dev/gpioc3.
1742 - Pandaboard: /etc/ttys should be updated, serial console device is
1743 now /dev/ttyu2, not /dev/ttyu0
1746 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1747 If you need the GNU extension from groff soelim(1), install groff
1748 from package: pkg install groff, or via ports: textproc/groff.
1751 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1752 defined in symlink(7); previously symlinks were silently ignored.
1755 The const qualifier has been removed from iconv(3) to comply with
1756 POSIX. The ports tree is aware of this from r384038 onwards.
1759 Libraries specified by LIBADD in Makefiles must have a corresponding
1760 DPADD_<lib> variable to ensure correct dependencies. This is now
1761 enforced in src.libnames.mk.
1764 From legacy ata(4) driver was removed support for SATA controllers
1765 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1766 Kernel modules ataahci and ataadaptec were removed completely,
1767 replaced by ahci and mvs modules respectively.
1770 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1771 the 20141231 entry below for information about prerequisites and
1772 upgrading, if you are not already using 3.5.0 or higher.
1775 The 32-bit PowerPC kernel has been changed to a position-independent
1776 executable. This can only be booted with a version of loader(8)
1777 newer than January 31, 2015, so make sure to update both world and
1778 kernel before rebooting.
1781 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1782 but before r278950, the RNG was not seeded properly. Immediately
1783 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1784 ssh keys or openssl keys) that were generated w/ a kernel from that
1785 range. This does not affect programs that directly used /dev/random
1786 or /dev/urandom. All userland uses of arc4random(3) are affected.
1789 The autofs(4) ABI was changed in order to restore binary compatibility
1790 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1791 with the new kernel.
1794 The powerpc64 kernel has been changed to a position-independent
1795 executable. This can only be booted with a new version of loader(8),
1796 so make sure to update both world and kernel before rebooting.
1799 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1800 only release, no new features have been added. Please see the 20141231
1801 entry below for information about prerequisites and upgrading, if you
1802 are not already using 3.5.0.
1805 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1806 taken from the ELF Tool Chain project rather than GNU binutils. They
1807 should be drop-in replacements, with the addition of arm64 support.
1808 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1809 binutils tools, if necessary. See 20150805 for updated information.
1812 The default Unbound configuration now enables remote control
1813 using a local socket. Users who have already enabled the
1814 local_unbound service should regenerate their configuration
1815 by running "service local_unbound setup" as root.
1818 The GNU texinfo and GNU info pages have been removed.
1819 To be able to view GNU info pages please install texinfo from ports.
1822 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1824 As of this release, a prerequisite for building clang, llvm and lldb is
1825 a C++11 capable compiler and C++11 standard library. This means that to
1826 be able to successfully build the cross-tools stage of buildworld, with
1827 clang as the bootstrap compiler, your system compiler or cross compiler
1828 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1829 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1832 On any standard FreeBSD 10.x or 11.x installation, where clang and
1833 libc++ are on by default (that is, on x86 or arm), this should work out
1836 On 9.x installations where clang is enabled by default, e.g. on x86 and
1837 powerpc, libc++ will not be enabled by default, so libc++ should be
1838 built (with clang) and installed first. If both clang and libc++ are
1839 missing, build clang first, then use it to build libc++.
1841 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1842 the instructions for 9.x above.
1844 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1845 default, and do not build clang.
1847 Many embedded systems are resource constrained, and will not be able to
1848 build clang in a reasonable time, or in some cases at all. In those
1849 cases, cross building bootable systems on amd64 is a workaround.
1851 This new version of clang introduces a number of new warnings, of which
1852 the following are most likely to appear:
1856 This warns in two cases, for both C and C++:
1857 * When the code is trying to take the absolute value of an unsigned
1858 quantity, which is effectively a no-op, and almost never what was
1859 intended. The code should be fixed, if at all possible. If you are
1860 sure that the unsigned quantity can be safely cast to signed, without
1861 loss of information or undefined behavior, you can add an explicit
1862 cast, or disable the warning.
1864 * When the code is trying to take an absolute value, but the called
1865 abs() variant is for the wrong type, which can lead to truncation.
1866 If you want to disable the warning instead of fixing the code, please
1867 make sure that truncation will not occur, or it might lead to unwanted
1870 -Wtautological-undefined-compare and
1871 -Wundefined-bool-conversion
1873 These warn when C++ code is trying to compare 'this' against NULL, while
1874 'this' should never be NULL in well-defined C++ code. However, there is
1875 some legacy (pre C++11) code out there, which actively abuses this
1876 feature, which was less strictly defined in previous C++ versions.
1878 Squid and openjdk do this, for example. The warning can be turned off
1879 for C++98 and earlier, but compiling the code in C++11 mode might result
1880 in unexpected behavior; for example, the parts of the program that are
1881 unreachable could be optimized away.
1884 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1885 kernel sources have been removed. The .h files remain, since some
1886 utilities include them. This will need to be fixed later.
1887 If "mount -t oldnfs ..." is attempted, it will fail.
1888 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1889 the utilities will report errors.
1892 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1893 directories to top level SUBDIR variable when their parent
1894 directory is included in LOCAL_DIRS. Users with build systems with
1895 such hierarchies and without SUBDIR entries in the parent
1896 directory Makefiles should add them or add the directories to
1900 faith(4) and faithd(8) have been removed from the base system. Faith
1901 has been obsolete for a very long time.
1904 vt(4), the new console driver, is enabled by default. It brings
1905 support for Unicode and double-width characters, as well as
1906 support for UEFI and integration with the KMS kernel video
1909 You may need to update your console settings in /etc/rc.conf,
1910 most probably the keymap. During boot, /etc/rc.d/syscons will
1911 indicate what you need to do.
1913 vt(4) still has issues and lacks some features compared to
1914 syscons(4). See the wiki for up-to-date information:
1915 https://wiki.freebsd.org/Newcons
1917 If you want to keep using syscons(4), you can do so by adding
1918 the following line to /boot/loader.conf:
1922 pjdfstest has been integrated into kyua as an opt-in test suite.
1923 Please see share/doc/pjdfstest/README for more details on how to
1927 gperf has been removed from the base system for architectures
1928 that use clang. Ports that require gperf will obtain it from the
1932 pjdfstest has been moved from tools/regression/pjdfstest to
1936 At svn r271982, The default linux compat kernel ABI has been adjusted
1937 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1938 update. If you wish to continue using the linux-f10 compat ports,
1939 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1940 encouraged to update their linux-compat packages to linux-c6 during
1941 their next update cycle.
1944 The ofwfb driver, used to provide a graphics console on PowerPC when
1945 using vt(4), no longer allows mmap() of all physical memory. This
1946 will prevent Xorg on PowerPC with some ATI graphics cards from
1947 initializing properly unless x11-servers/xorg-server is updated to
1951 The xdev targets have been converted to using TARGET and
1952 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1955 The default unbound configuration has been modified to address
1956 issues with reverse lookups on networks that use private
1957 address ranges. If you use the local_unbound service, run
1958 "service local_unbound setup" as root to regenerate your
1959 configuration, then "service local_unbound reload" to load the
1963 The GNU texinfo and GNU info pages are not built and installed
1964 anymore, WITH_INFO knob has been added to allow to built and install
1966 UPDATE: see 20150102 entry on texinfo's removal
1969 The GNU readline library is now an INTERNALLIB - that is, it is
1970 statically linked into consumers (GDB and variants) in the base
1971 system, and the shared library is no longer installed. The
1972 devel/readline port is available for third party software that
1976 The Itanium architecture (ia64) has been removed from the list of
1977 known architectures. This is the first step in the removal of the
1981 Commit r268115 has added NFSv4.1 server support, merged from
1982 projects/nfsv4.1-server. Since this includes changes to the
1983 internal interfaces between the NFS related modules, a full
1984 build of the kernel and modules will be necessary.
1985 __FreeBSD_version has been bumped.
1988 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1989 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1990 which differs from the behaviour controlled by this knob.)
1993 Maximal length of the serial number in CTL was increased from 16 to
1994 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1995 and ctld, need to be rebuilt to work with a new kernel.
1998 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1999 1 respectively to match the upstream numbers. They were out of
2000 sync because, when they were originally added to FreeBSD, the
2001 upstream versions were not respected. These libraries are private
2002 and not yet built by default, so renumbering them should be a
2003 non-issue. However, unclean source trees will yield broken test
2004 programs once the operator executes "make delete-old-libs" after a
2005 "make installworld".
2007 Additionally, the atf-sh binary was made private by moving it into
2008 /usr/libexec/. Already-built shell test programs will keep the
2009 path to the old binary so they will break after "make delete-old"
2012 If you are using WITH_TESTS=yes (not the default), wipe the object
2013 tree and rebuild from scratch to prevent spurious test failures.
2014 This is only needed once: the misnumbered libraries and misplaced
2015 binaries have been added to OptionalObsoleteFiles.inc so they will
2016 be removed during a clean upgrade.
2019 Clang and llvm have been upgraded to 3.4.1 release.
2022 We bogusly installed src.opts.mk in /usr/share/mk. This file should
2023 be removed to avoid issues in the future (and has been added to
2027 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
2028 past, it affected all builds that used the bsd.*.mk files. The old
2029 behavior was a bug, but people may have relied upon it. To get this
2030 behavior back, you can .include /etc/src.conf from /etc/make.conf
2031 (which is still global and isn't changed). This also changes the
2032 behavior of incremental builds inside the tree of individual
2033 directories. Set MAKESYSPATH to ".../share/mk" to do that.
2034 Although this has survived make universe and some upgrade scenarios,
2035 other upgrade scenarios may have broken. At least one form of
2036 temporary breakage was fixed with MAKESYSPATH settings for buildworld
2037 as well... In cases where MAKESYSPATH isn't working with this
2038 setting, you'll need to set it to the full path to your tree.
2040 One side effect of all this cleaning up is that bsd.compiler.mk
2041 is no longer implicitly included by bsd.own.mk. If you wish to
2042 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
2046 The lindev device has been removed since /dev/full has been made a
2047 standard device. __FreeBSD_version has been bumped.
2050 The knob WITHOUT_VI was added to the base system, which controls
2051 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
2052 in order to reorder files share/termcap and didn't build ex(1) as a
2053 build tool, so building/installing with WITH_VI is highly advised for
2054 build hosts for older releases.
2056 This issue has been fixed in stable/9 and stable/10 in r277022 and
2057 r276991, respectively.
2060 The YES_HESIOD knob has been removed. It has been obsolete for
2061 a decade. Please move to using WITH_HESIOD instead or your builds
2062 will silently lack HESIOD.
2065 The uart(4) driver has been changed with respect to its handling
2066 of the low-level console. Previously the uart(4) driver prevented
2067 any process from changing the baudrate or the CLOCAL and HUPCL
2068 control flags. By removing the restrictions, operators can make
2069 changes to the serial console port without having to reboot.
2070 However, when getty(8) is started on the serial device that is
2071 associated with the low-level console, a misconfigured terminal
2072 line in /etc/ttys will now have a real impact.
2073 Before upgrading the kernel, make sure that /etc/ttys has the
2074 serial console device configured as 3wire without baudrate to
2075 preserve the previous behaviour. E.g:
2076 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
2079 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
2080 to improve performance. To re-enable it, if needed, run rpcbind
2081 with command line option -W.
2084 Switched back to the GPL dtc compiler due to updates in the upstream
2085 dts files not being supported by the BSDL dtc compiler. You will need
2086 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
2087 may result while building dtb files during a kernel build if you fail
2088 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
2091 Clang and llvm have been upgraded to 3.4 release.
2094 The nve(4) driver has been removed. Please use the nfe(4) driver
2095 for NVIDIA nForce MCP Ethernet adapters instead.
2098 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
2099 This could cause certain C++ applications using shared libraries built
2100 against the previous version of libc++ to crash. The incompatibility
2101 has now been fixed, but any C++ applications or shared libraries built
2102 between r261283 and r261801 should be recompiled.
2105 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
2106 capability mode support. Please note that enabling the feature in
2107 kernel is still highly recommended.
2110 OpenSSH is now built with sandbox support, and will use sandbox as
2111 the default privilege separation method. This requires Capsicum
2112 capability mode support in kernel.
2115 The libelf and libdwarf libraries have been updated to newer
2116 versions from upstream. Shared library version numbers for
2117 these two libraries were bumped. Any ports or binaries
2118 requiring these two libraries should be recompiled.
2119 __FreeBSD_version is bumped to 1100006.
2122 If a Makefile in a tests/ directory was auto-generating a Kyuafile
2123 instead of providing an explicit one, this would prevent such
2124 Makefile from providing its own Kyuafile in the future during
2125 NO_CLEAN builds. This has been fixed in the Makefiles but manual
2126 intervention is needed to clean an objdir if you use NO_CLEAN:
2127 # find /usr/obj -name Kyuafile | xargs rm -f
2130 The behavior of gss_pseudo_random() for the krb5 mechanism
2131 has changed, for applications requesting a longer random string
2132 than produced by the underlying enctype's pseudo-random() function.
2133 In particular, the random string produced from a session key of
2134 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
2135 be different at the 17th octet and later, after this change.
2136 The counter used in the PRF+ construction is now encoded as a
2137 big-endian integer in accordance with RFC 4402.
2138 __FreeBSD_version is bumped to 1100004.
2141 The WITHOUT_ATF build knob has been removed and its functionality
2142 has been subsumed into the more generic WITHOUT_TESTS. If you were
2143 using the former to disable the build of the ATF libraries, you
2144 should change your settings to use the latter.
2147 The default version of mtree is nmtree which is obtained from
2148 NetBSD. The output is generally the same, but may vary
2149 slightly. If you found you need identical output adding
2150 "-F freebsd9" to the command line should do the trick. For the
2151 time being, the old mtree is available as fmtree.
2154 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
2155 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
2156 1.1.4_8 and verify bsdyml not linked in, before running "make
2158 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
2160 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
2163 The stable/10 branch has been created in subversion from head
2170 Sometimes, obscure build problems are the result of environment
2171 poisoning. This can happen because the make utility reads its
2172 environment when searching for values for global variables. To run
2173 your build attempts in an "environmental clean room", prefix all make
2174 commands with 'env -i '. See the env(1) manual page for more details.
2175 Occasionally a build failure will occur with "make -j" due to a race
2176 condition. If this happens try building again without -j, and please
2177 report a bug if it happens consistently.
2179 When upgrading from one major version to another it is generally best to
2180 upgrade to the latest code in the currently installed branch first, then
2181 do an upgrade to the new branch. This is the best-tested upgrade path,
2182 and has the highest probability of being successful. Please try this
2183 approach if you encounter problems with a major version upgrade. Since
2184 the stable 4.x branch point, one has generally been able to upgrade from
2185 anywhere in the most recent stable branch to head / current (or even the
2186 last couple of stable branches). See the top of this file when there's
2189 The update process will emit an error on an attempt to perform a build
2190 or install from a FreeBSD version below the earliest supported version.
2191 When updating from an older version the update should be performed one
2192 major release at a time, including running `make delete-old` at each
2195 When upgrading a live system, having a root shell around before
2196 installing anything can help undo problems. Not having a root shell
2197 around can lead to problems if pam has changed too much from your
2198 starting point to allow continued authentication after the upgrade.
2200 This file should be read as a log of events. When a later event changes
2201 information of a prior event, the prior event should not be deleted.
2202 Instead, a pointer to the entry with the new information should be
2203 placed in the old entry. Readers of this file should also sanity check
2204 older entries before relying on them blindly. Authors of new entries
2205 should write them with this in mind.
2209 When upgrading the boot ZFS pool to a new version, always follow
2212 1.) recompile and reinstall the ZFS boot loader and boot block
2213 (this is part of "make buildworld" and "make installworld")
2215 2.) update the ZFS boot block on your boot drive
2217 The following example updates the ZFS boot block on the
2218 freebsd-boot partition of a GPT partitioned drive ada0:
2219 "gpart bootcode -p /boot/gptzfsboot -i $N ada0"
2220 The value $N will typically be 1 (if booting from BIOS) or 2 (if
2223 Non-boot pools do not need these updates.
2227 If you are updating from a prior version of FreeBSD (even one just
2228 a few days old), you should follow this procedure. It is the most
2229 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2231 make kernel-toolchain
2232 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2233 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2235 To test a kernel once
2236 ---------------------
2237 If you just want to boot a kernel once (because you are not sure
2238 if it works, or if you want to boot a known bad kernel to provide
2239 debugging information) run
2240 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2241 nextboot -k testkernel
2243 To rebuild everything and install it on the current system.
2244 -----------------------------------------------------------
2245 # Note: sometimes if you are running current you gotta do more than
2246 # is listed here if you are upgrading from a really old current.
2248 <make sure you have good level 0 dumps>
2250 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2251 make installkernel KERNCONF=YOUR_KERNEL_HERE
2253 <reboot in single user> [3]
2260 To cross-install current onto a separate partition
2261 --------------------------------------------------
2262 # In this approach we use a separate partition to hold
2263 # current's root, 'usr', and 'var' directories. A partition
2264 # holding "/", "/usr" and "/var" should be about 2GB in
2267 <make sure you have good level 0 dumps>
2270 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2271 <maybe newfs current's root partition>
2272 <mount current's root partition on directory ${CURRENT_ROOT}>
2273 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
2274 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2275 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2276 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2277 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2278 <reboot into current>
2279 <do a "native" rebuild/install as described in the previous section>
2280 <maybe install compatibility libraries from ports/misc/compat*>
2284 To upgrade in-place from stable to current
2285 ----------------------------------------------
2286 <make sure you have good level 0 dumps>
2288 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
2289 make installkernel KERNCONF=YOUR_KERNEL_HERE
2291 <reboot in single user> [3]
2298 Make sure that you've read the UPDATING file to understand the
2299 tweaks to various things you need. At this point in the life
2300 cycle of current, things change often and you are on your own
2301 to cope. The defaults can also change, so please read ALL of
2302 the UPDATING entries.
2304 Also, if you are tracking -current, you must be subscribed to
2305 freebsd-current@freebsd.org. Make sure that before you update
2306 your sources that you have read and understood all the recent
2307 messages there. If in doubt, please track -stable which has
2308 much fewer pitfalls.
2310 [1] If you have third party modules, such as vmware, you should disable
2311 them at this point so they don't crash your system on
2312 reboot. Alternatively, you should rebuild all the modules you have in
2313 your system and install them as well. If you are running -current, you
2314 should seriously consider placing all sources to all the modules for
2315 your system (or symlinks to them) in /usr/local/sys/modules so this
2316 happens automatically. If all your modules come from ports, then adding
2317 the port origin directories to PORTS_MODULES instead is also automatic
2319 PORTS_MODULES+=x11/nvidia-driver
2321 [3] From the bootblocks, boot -s, and then do
2325 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed
2326 cd src # full path to source
2327 adjkerntz -i # if CMOS is wall time
2328 Also, when doing a major release upgrade, it is required that you boot
2329 into single user mode to do the installworld.
2331 [4] Note: This step is non-optional. Failure to do this step
2332 can result in a significant reduction in the functionality of the
2333 system. Attempting to do it by hand is not recommended and those
2334 that pursue this avenue should read this file carefully, as well
2335 as the archives of freebsd-current and freebsd-hackers mailing lists
2336 for potential gotchas. The -U option is also useful to consider.
2337 See mergemaster(8) for more information.
2339 [5] Usually this step is a no-op. However, from time to time
2340 you may need to do this if you get unknown user in the following
2341 step. It never hurts to do it all the time. You may need to
2342 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2343 install) after the buildworld before this step if you last updated
2344 from current before 20130425 or from -stable before 20130430.
2346 [6] This only deletes old files and directories. Old libraries
2347 can be deleted by "make delete-old-libs", but you have to make
2348 sure that no program is using those libraries anymore.
2350 [8] The new kernel must be able to run existing binaries used by an
2351 installworld. When upgrading across major versions, the new kernel's
2352 configuration must include the correct COMPAT_FREEBSD<n> option for
2353 existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure
2354 to do so may leave you with a system that is hard to boot to recover. A
2355 GENERIC kernel will include suitable compatibility options to run
2356 binaries from older branches. Note that the ability to run binaries
2357 from unsupported branches is not guaranteed.
2359 Make sure that you merge any new devices from GENERIC since the
2360 last time you updated your kernel config file. Options also
2361 change over time, so you may need to adjust your custom kernels
2364 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2365 "?=" instead of the "=" assignment operator, so that buildworld can
2366 override the CPUTYPE if it needs to.
2368 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2369 not on the command line, or in /etc/make.conf. buildworld will
2370 warn if it is improperly defined.
2373 This file contains a list, in reverse chronological order, of major
2374 breakages in tracking -current. It is not guaranteed to be a complete
2375 list of such breakages, and only contains entries since September 23, 2011.
2376 If you need to see UPDATING entries from before that date, you will need
2377 to fetch an UPDATING file from an older FreeBSD release.
2379 Copyright information:
2381 Copyright 1998-2009 M. Warner Losh <imp@FreeBSD.org>
2383 Redistribution, publication, translation and use, with or without
2384 modification, in full or in part, in any form or format of this
2385 document are permitted without further permission from the author.
2387 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2388 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2389 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2390 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2391 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2392 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2393 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2394 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2395 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2396 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2397 POSSIBILITY OF SUCH DAMAGE.
2399 Contact Warner Losh if you have any questions about your use of