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 updating system packages
15 NOTE TO PEOPLE WHO THINK THAT FreeBSD 14.x IS SLOW:
16 FreeBSD 14.x has many debugging features turned on, in both the kernel
17 and userland. These features attempt to detect incorrect use of
18 system primitives, and encourage loud failure through extra sanity
19 checking and fail stop semantics. They also substantially impact
20 system performance. If you want to do performance measurement,
21 benchmarking, and optimization, you'll want to turn them off. This
22 includes various WITNESS- related kernel options, INVARIANTS, malloc
23 debugging flags in userland, and various verbose features in the
24 kernel. Many developers choose to disable these features on build
25 machines to maximize performance. (To completely disable malloc
26 debugging, define WITH_MALLOC_PRODUCTION in /etc/src.conf and rebuild
27 world, or to merely disable the most expensive debugging functionality
28 at runtime, run "ln -s 'abort:false,junk:false' /etc/malloc.conf".)
31 Commit 7763814fc9c2 changed the internal KAPI between
32 the krpc and NFS. As such, the krpc, nfscommon and
33 nfscl modules must all be rebuilt from sources.
34 Without this patch, NFSv4.1/4.2 mounts should not
35 be done with the nfscbd(8) daemon running, to avoid
36 needing a working back channel for server->client RPCs.
39 Commit 01ae8969a9ee fixed the NFSv4.1/4.2 server so that it
40 handles binding of the back channel as required by RFC5661.
41 Until this patch is in your server, avoid use of the "nconnects"
42 mount option for Linux NFSv4.1/4.2 mounts.
45 For 64-bit architectures the base system is now built with Position
46 Independent Executable (PIE) support enabled by default. It may be
47 disabled using the WITHOUT_PIE knob. A clean build is required.
50 Various LinuxKPI functionality was added which conflicts with DRM.
51 Please update your drm-kmod port to after the __FreeBSD_verison 1400003
55 PC Card attachments for all devices have been removed. In the case of
56 wi and cmx, the entire drivers were removed because they were only
57 PC Card devices. FreeBSD_version 1300134 should be used for this
58 since it was bumped so recently.
61 Transport-independent parts of HID support have been split off the USB
62 code in to separate subsystem. Kernel configs which include one of
63 ums, ukbd, uhid, atp, wsp, wmt, uaudio, ugold or ucycom drivers should
64 be updated with adding of "device hid" line.
67 ncurses installation has been modified to only keep the widechar
68 enabled version. Incremental build is broken for that change, so it
69 requires a clean build.
72 The FreeBSD project has migrated from Subversion to Git. Temporary
73 instructions can be found at
74 https://github.com/bsdimp/freebsd-git-docs/blob/main/src-cvt.md
75 and other documents in that repo.
78 The services database has been updated to cover more of the basic
79 services expected in a modern system. The database is big enough
80 that it will cause issues in mergemaster in Releases previous to
81 12.2 and 11.3, or in very old current systems from before r358154.
84 Obsolete in-tree GDB 6.1.1 has been removed. GDB (including kgdb)
85 may be installed from ports or packages.
88 ping6 has been merged into ping. It can now be called as "ping -6".
89 See ping(8) for details.
92 Default value of net.add_addr_allfibs has been changed to 0.
93 If you have multi-fib configuration and rely on existence of all
94 interface routes in every fib, you need to set the above sysctl to 1.
97 The internal pre-processor in the calendar(1) program has been
98 extended to support more C pre-processor commands (e.g. #ifdef, #else,
99 and #undef) and to detect unbalanced conditional statements.
100 Error messages have been extended to include the filename and line
101 number if processing stops to help fixing malformed data files.
104 All the data files for the calendar(1) program, except calendar.freebsd,
105 have been moved to the deskutils/calendar-data port, much like the
106 jewish calendar entries were moved to deskutils/hebcal years ago. After
107 make delete-old-files, you need to install it to retain full
108 functionality. calendar(1) will issue a reminder for files it can't
112 LINT files are no longer generated. We now include the relevant NOTES
113 files. Note: This may cause conflicts with updating in some cases.
114 find sys -name LINT\* -delete
115 is suggested across this commit to remove the generated LINT files.
117 If you have tried to update with generated files there, the svn
118 command you want to un-auger the tree is
121 and then do the above find from the top level. Substitute 'amd64'
122 above with where the error message indicates a conflict.
125 OpenZFS support has been integrated. Do not upgrade root pools until
126 the loader is updated to support zstd. Furthermore, we caution against
127 'zpool upgrade' for the next few weeks. The change should be transparent
128 unless you want to use new features.
130 Not all "NO_CLEAN" build scenarios work across these changes. Many
131 scenarios have been tested and fixed, but rebuilding kernels without
132 rebuilding world may fail.
134 The ZFS cache file has moved from /boot to /etc to match the OpenZFS
135 upstream default. A fallback to /boot has been added for mountroot.
137 Pool auto import behavior at boot has been moved from the kernel module
138 to an explicit "zpool import -a" in one of the rc scripts enabled by
139 zfs_enable=YES. This means your non-root zpools won't auto import until
140 you upgrade your /etc/rc.d files.
143 The resume code now notifies devd with the 'kernel' system
144 rather than the old 'kern' subsystem to be consistent with
145 other use. The old notification will be created as well, but
146 will be removed prior to FreeBSD 14.0.
149 r362275 changed the internal API between the kernel RPC and the
150 NFS modules. As such, all the modules must be recompiled from
154 r364330 modified the internal API used between the NFS modules.
155 As such, all the NFS modules must be re-compiled from sources.
158 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
159 been upgraded to 11.0.0. Please see the 20141231 entry below for
160 information about prerequisites and upgrading, if you are not already
161 using clang 3.5.0 or higher.
164 r364092 modified the internal ABI used between the kernel NFS
165 modules. As such, all of these modules need to be rebuilt
166 from sources, so a version bump was done.
169 Makefile.inc has been updated to work around the issue documented in
170 20200729. It was a case where the optimization of using symbolic links
171 to point to binaries created a situation where we'd run new binaries
172 with old libraries starting midway through the installworld process.
175 r363679 has redefined some undefined behavior in regcomp(3); notably,
176 extraneous escapes of most ordinary characters will no longer be
177 accepted. An exp-run has identified all of the problems with this in
178 ports, but other non-ports software may need extra escapes removed to
179 continue to function.
181 Because of this change, installworld may encounter the following error
182 from rtld: Undefined symbol "regcomp@FBSD_1.6" -- It is imperative that
183 you do not halt installworld. Instead, let it run to completion (whether
184 successful or not) and run installworld once more.
187 A new implementation of bc and dc has been imported in r362681. This
188 implementation corrects non-conformant behavior of the previous bc
189 and adds GNU bc compatible options. It offers a number of extensions,
190 is much faster on large values, and has support for message catalogs
191 (a number of languages are already supported, contributions of further
192 languages welcome). The option WITHOUT_GH_BC can be used to build the
193 world with the previous versions of bc and dc.
196 r362639 changed the internal API used between the NFS kernel modules.
197 As such, they all need to be rebuilt from sources.
200 r362158 changed the arguments for VFS_CHECKEXP(). As such, any
201 out of tree file systems need to be modified and rebuilt.
202 Also, any file systems that are modules must be rebuilt.
205 read(2) of a directory fd is now rejected by default. root may
206 re-enable it for system root only on non-ZFS filesystems with the
207 security.bsd.allow_read_dir sysctl(8) MIB if
208 security.bsd.suser_enabled=1.
210 It may be advised to setup aliases for grep to default to `-d skip` if
211 commonly non-recursively grepping a list that includes directories and
212 the potential for the resulting stderr output is not tolerable. Example
213 aliases are now installed, commented out, in /root/.cshrc and
217 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
218 been upgraded to 10.0.1. Please see the 20141231 entry below for
219 information about prerequisites and upgrading, if you are not already
220 using clang 3.5.0 or higher.
223 Support for obsolete compilers has been removed from the build system.
224 Clang 6 and GCC 6.4 are the minimum supported versions.
227 closefrom(2) has been moved under COMPAT12, and replaced in libc with a
228 stub that calls close_range(2). If using a custom kernel configuration,
229 you may want to ensure that the COMPAT_FREEBSD12 option is included, as
230 a slightly older -CURRENT userland and older FreeBSD userlands may not
231 be functional without closefrom(2).
234 Upstream DTS from Linux 5.6 was merged and they now have the SID
235 and THS (Secure ID controller and THermal Sensor) node present.
236 The DTB overlays have now been removed from the tree for the H3/H5 and
237 A64 SoCs and the aw_sid and aw_thermal driver have been updated to
238 deal with upstream DTS. If you are using those overlays you need to
239 remove them from loader.conf and update the DTBs on the FAT partition.
242 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
243 been upgraded to 10.0.0. Please see the 20141231 entry below for
244 information about prerequisites and upgrading, if you are not already
245 using clang 3.5.0 or higher.
248 The amd(8) automount daemon has been removed from the source tree.
249 As of FreeBSD 10.1 autofs(5) is the preferred tool for automounting.
250 amd is still available in the sysutils/am-utils port.
253 Removed brooktree driver (bktr.4) from the tree.
256 The WITH_GPL_DTC option has been removed. The BSD-licenced device tree
257 compiler in usr.bin/dtc is used on all architectures which use dtc, and
258 the GPL dtc is available (if needed) from the sysutils/dtc port.
261 The WITHOUT_LLVM_LIBUNWIND option has been removed. LLVM's libunwind
262 is used by all supported CPU architectures.
265 GCC 4.2.1 has been removed from the tree. The WITH_GCC,
266 WITH_GCC_BOOTSTRAP, and WITH_GNUCXX options are no longer available.
267 Users who wish to build FreeBSD with GCC must use the external toolchain
271 ncurses has been updated to a newer version (6.2-20200215). Given the ABI
272 has changed, users will have to rebuild all the ports that are linked to
276 The size of struct vnet and the magic cookie have changed.
277 Users need to recompile libkvm and all modules using VIMAGE
278 together with their new kernel.
281 Defining the long deprecated NO_CTF, NO_DEBUG_FILES, NO_INSTALLLIB,
282 NO_MAN, NO_PROFILE, and NO_WARNS variables is now an error. Update
283 your Makefiles and scripts to define MK_<var>=no instead as required.
285 One exception to this is that program or library Makefiles should
286 define MAN to empty rather than setting MK_MAN=no.
289 Clang/LLVM is now the default compiler and LLD the default
293 make universe no longer uses GCC 4.2.1 on any architectures.
294 Architectures not supported by in-tree Clang/LLVM require an
295 external toolchain package.
298 GCC 4.2.1 is now not built by default, as part of the GCC 4.2.1
299 retirement plan. Specifically, the GCC, GCC_BOOTSTRAP, and GNUCXX
300 options default to off for all supported CPU architectures. As a
301 short-term transition aid they may be enabled via WITH_* options.
302 GCC 4.2.1 is expected to be removed from the tree on 2020-03-31.
305 Support for armv5 has been disconnected and is being removed. The
306 machine combination MACHINE=arm MACHINE_ARCH=arm is no longer valid.
307 You must now use a MACHINE_ARCH of armv6 or armv7. The default
308 MACHINE_ARCH for MACHINE=arm is now armv7.
311 Clang/LLVM is now the default compiler for all powerpc architectures.
312 LLD is now the default linker for powerpc64. The change for powerpc64
313 also includes a change to the ELFv2 ABI, incompatible with the existing
317 Kernel-loadable random(4) modules are no longer unloadable.
320 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
321 been upgraded to 9.0.1. Please see the 20141231 entry below for
322 information about prerequisites and upgrading, if you are not already
323 using clang 3.5.0 or higher.
326 r355677 has modified the internal interface used between the
327 NFS modules in the kernel. As such, they must all be upgraded
328 simultaneously. I will do a version bump for this.
331 The root certificates of the Mozilla CA Certificate Store have been
332 imported into the base system and can be managed with the certctl(8)
333 utility. If you have installed the security/ca_root_nss port or package
334 with the ETCSYMLINK option (the default), be advised that there may be
335 differences between those included in the port and those included in
336 base due to differences in nss branch used as well as general update
337 frequency. Note also that certctl(8) cannot manage certs in the
338 format used by the security/ca_root_nss port.
341 The amd(8) automount daemon has been disabled by default, and will be
342 removed in the future. As of FreeBSD 10.1 the autofs(5) is available
346 The nctgpio and wbwd drivers have been moved to the superio bus.
347 If you have one of these drivers in a kernel configuration, then
348 you should add device superio to it. If you use one of these drivers
349 as a module and you compile a custom set of modules, then you should
350 add superio to the set.
353 KPIs for network drivers to access interface addresses have changed.
354 Users need to recompile NIC driver modules together with kernel.
357 The net.link.tap.user_open sysctl no longer prevents user opening of
358 already created /dev/tapNN devices. Access is still controlled by
359 node permissions, just like tun devices. The net.link.tap.user_open
360 sysctl is now used only to allow users to perform devfs cloning of
361 tap devices, and the subsequent open may not succeed if the user is not
362 in the appropriate group. This sysctl may be deprecated/removed
363 completely in the future.
366 mips, powerpc, and sparc64 are no longer built as part of
367 universe / tinderbox unless MAKE_OBSOLETE_GCC is defined. If
368 not defined, mips, powerpc, and sparc64 builds will look for
369 the xtoolchain binaries and if installed use them for universe
370 builds. As llvm 9.0 becomes vetted for these architectures, they
371 will be removed from the list.
374 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
375 been upgraded to 9.0.0. Please see the 20141231 entry below for
376 information about prerequisites and upgrading, if you are not already
377 using clang 3.5.0 or higher.
380 The hpt27xx, hptmv, hptnr, and hptrr drivers have been removed from
381 GENERIC. They are available as modules and can be loaded by adding
382 to /boot/loader.conf hpt27xx_load="YES", hptmv_load="YES",
383 hptnr_load="YES", or hptrr_load="YES", respectively.
386 ntpd no longer by default locks its pages in memory, allowing them
387 to be paged out by the kernel. Use rlimit memlock to restore
388 historic BSD behaviour. For example, add "rlimit memlock 32"
389 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
392 Several of ping6's options have been renamed for better consistency
393 with ping. If you use any of -ARWXaghmrtwx, you must update your
394 scripts. See ping6(8) for details.
397 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
398 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
399 been removed from mount_fusefs(8). You can safely remove them from
400 your scripts, because they had no effect.
402 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
403 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
404 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
405 sysctls have been removed. If you felt the need to set any of them to
406 a non-default value, please tell asomers@FreeBSD.org why.
409 Default permissions on the /var/account/acct file (and copies of it
410 rotated by periodic daily scripts) are changed from 0644 to 0640
411 because the file contains sensitive information that should not be
412 world-readable. If the /var/account directory must be created by
413 rc.d/accounting, the mode used is now 0750. Admins who use the
414 accounting feature are encouraged to change the mode of an existing
415 /var/account directory to 0750 or 0700.
418 Entropy collection and the /dev/random device are no longer optional
419 components. The "device random" option has been removed.
420 Implementations of distilling algorithms can still be made loadable
421 with "options RANDOM_LOADABLE" (e.g., random_fortuna.ko).
424 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
425 been upgraded to 8.0.1. Please see the 20141231 entry below for
426 information about prerequisites and upgrading, if you are not already
427 using clang 3.5.0 or higher.
430 A fix was applied to i386 kernel modules to avoid panics with
431 dpcpu or vnet. Users need to recompile i386 kernel modules
432 having pcpu or vnet sections or they will refuse to load.
435 User-wired pages now have their own counter,
436 vm.stats.vm.v_user_wire_count. The vm.max_wired sysctl was renamed
437 to vm.max_user_wired and changed from an unsigned int to an unsigned
438 long. bhyve VMs wired with the -S are now subject to the user
439 wiring limit; the vm.max_user_wired sysctl may need to be tuned to
440 avoid running into the limit.
443 The IPSEC option has been removed from GENERIC. Users requiring
444 ipsec(4) must now load the ipsec(4) kernel module.
447 The tap(4) driver has been folded into tun(4), and the module has been
448 renamed to tuntap. You should update any kld_list="if_tap" or
449 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
450 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
451 module instead, and "device tap" or "device tun" entries in kernel
452 config files to select the tuntap device instead.
455 The following knobs have been added related to tradeoffs between
456 safe use of the random device and availability in the absence of
459 kern.random.initial_seeding.bypass_before_seeding: tunable; set
460 non-zero to bypass the random device prior to seeding, or zero to
461 block random requests until the random device is initially seeded.
462 For now, set to 1 (unsafe) by default to restore pre-r346250 boot
463 availability properties.
465 kern.random.initial_seeding.read_random_bypassed_before_seeding:
466 read-only diagnostic sysctl that is set when bypass is enabled and
467 read_random(9) is bypassed, to enable programmatic handling of this
468 initial condition, if desired.
470 kern.random.initial_seeding.arc4random_bypassed_before_seeding:
471 Similar to the above, but for for arc4random(9) initial seeding.
473 kern.random.initial_seeding.disable_bypass_warnings: tunable; set
474 non-zero to disable warnings in dmesg when the same conditions are
475 met as for the diagnostic sysctls above. Defaults to zero, i.e.,
476 produce warnings in dmesg when the conditions are met.
479 The loadable random module KPI has changed; the random_infra_init()
480 routine now requires a 3rd function pointer for a bool (*)(void)
481 method that returns true if the random device is seeded (and
482 therefore unblocked).
485 r345895 reverts r320698. This implies that an nfsuserd(8) daemon
486 built from head sources between r320757 (July 6, 2017) and
487 r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
488 is added to the command line.
489 nfsuserd daemons built from head sources that are post-r338192 are
490 not affected and should continue to work.
493 The fuse(4) module has been renamed to fusefs(4) for consistency with
494 other filesystems. You should update any kld_load="fuse" entries in
495 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
496 "options FUSE" entries in kernel config files.
499 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
500 8.0.0. Please see the 20141231 entry below for information about
501 prerequisites and upgrading, if you are not already using clang 3.5.0
505 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
506 compiled into your custom kernel, add 'device xz' statement to the
510 drm and drm2 have been removed from the tree. Please see
511 https://wiki.freebsd.org/Graphics for the latest information on
512 migrating to the drm ports.
515 Iflib is no longer unconditionally compiled into the kernel. Drivers
516 using iflib and statically compiled into the kernel, now require
517 the 'device iflib' config option. For the same drivers loaded as
518 modules on kernels not having 'device iflib', the iflib.ko module
519 is loaded automatically.
522 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
523 options no longer exist since r343219 and r343427 respectively;
524 nothing uses them, so they should be just removed from custom
528 r342635 changes the way efibootmgr(8) works by requiring users to add
529 the -b (bootnum) parameter for commands where the bootnum was previously
530 specified with each option. For example 'efibootmgr -B 0001' is now
531 'efibootmgr -B -b 0001'.
534 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
535 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
536 servers that have vfs.nfsd.nfs_privport set will only allow mounts
537 from clients using a reserved port#. Since both the FreeBSD and Linux
538 NFSv4 clients use reserved port#s by default, this should not affect
542 The XLP config has been removed. We can't support 64-bit atomics in this
543 kernel because it is running in 32-bit mode. XLP users must transition
544 to running a 64-bit kernel (XLP64 or XLPN32).
546 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
547 the preferred emulator today and we don't need two different ones.
549 The old sibyte / swarm / Broadcom BCM1250 support has been
550 removed from the mips port.
553 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
554 7.0.1. Please see the 20141231 entry below for information about
555 prerequisites and upgrading, if you are not already using clang 3.5.0
559 Remove the timed and netdate programs from the base tree. Setting
560 the time with these daemons has been obsolete for over a decade.
563 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
564 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
565 it produces broken binaries when ifuncs are in use. Users needing
566 GNU ld should install the binutils port or package.
569 The BSD crtbegin and crtend code has been enabled by default. It has
570 had extensive testing on amd64, arm64, and i386. It can be disabled
571 by building a world with -DWITHOUT_BSD_CRTBEGIN.
574 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
575 has been converted to a port (misc/ctm) and will be removed from
576 FreeBSD-13. It is available as a package (ctm) for all supported
580 The default newsyslog.conf(5) file has been changed to only include
581 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
582 the filenames end in '.conf' and do not begin with a '.'.
584 You should check the configuration files in these two directories match
585 this naming convention. You can verify which configuration files are
586 being included using the command:
590 Ports for the DRM modules have been simplified. Now, amd64 users should
591 just install the drm-kmod port. All others should install
594 Graphics hardware that's newer than about 2010 usually works with
595 drm-kmod. For hardware older than 2013, however, some users will need
596 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
597 than 2008 usually only works in drm-legacy-kmod. The graphics team can
598 only commit to hardware made since 2013 due to the complexity of the
599 market and difficulty to test all the older cards effectively. If you
600 have hardware supported by drm-kmod, you are strongly encouraged to use
601 that as you will get better support.
603 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
604 elsewhere, the drm and drm2 modules will be eliminated from the src base
605 soon (with a limited exception for arm). Please update to the package
606 asap and report any issues to x11@freebsd.org.
608 Generally, anybody using the drm*-kmod packages should add
609 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
610 cross-threading surprises, especially with automatic driver
611 loading from X11 startup. These will become the defaults in 13-current
615 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
616 custom kernel and module loading configuration files must be updated
617 accordingly. Moreover, interfaces previous presented as ixlvN to the
618 system are now exposed as iavfN and network configuration files must
619 be adjusted as necessary.
622 OpenSSL has been updated to version 1.1.1. This update included
623 additional various API changes throughout the base system. It is
624 important to rebuild third-party software after upgrading. The value
625 of __FreeBSD_version has been bumped accordingly.
628 The legacy DRM modules and drivers have now been added to the loader's
629 module blacklist, in favor of loading them with kld_list in rc.conf(5).
630 The module blacklist may be overridden with the loader.conf(5)
631 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
635 The cam(4) based nda(4) driver will be used over nvd(4) by default on
636 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
637 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
638 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
642 Reproducible build mode is now on by default, in preparation for
643 FreeBSD 12.0. This eliminates build metadata such as the user,
644 host, and time from the kernel (and uname), unless the working tree
645 corresponds to a modified checkout from a version control system.
646 The previous behavior can be obtained by setting the /etc/src.conf
647 knob WITHOUT_REPRODUCIBLE_BUILD.
650 The Yarrow CSPRNG has been removed from the kernel as it has not been
651 supported by its designers since at least 2003. Fortuna has been the
652 default since FreeBSD-11.
655 devctl freeze/thaw have gone into the tree, the rc scripts have been
656 updated to use them and devmatch has been changed. You should update
657 kernel, userland and rc scripts all at the same time.
660 The default interpreter has been switched from 4th to Lua.
661 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
662 interpreter. If you have custom FORTH code you will need to set
663 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
664 src.conf for the build. This will create default hard links between
665 loader and loader_4th instead of loader and loader_lua, the new default.
666 If you are using UEFI it will create the proper hard link to loader.efi.
668 bhyve uses userboot.so. It remains 4th-only until some issues are solved
669 regarding coexisting with multiple versions of FreeBSD are resolved.
672 ls(1) now respects the COLORTERM environment variable used in other
673 systems and software to indicate that a colored terminal is both
674 supported and desired. If ls(1) is suddenly emitting colors, they may
675 be disabled again by either removing the unwanted COLORTERM from your
676 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
677 may not be observed in a future release.
680 The default pager for most commands has been changed to "less". To
681 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
685 The jedec_ts(4) driver has been removed. A superset of its functionality
686 is available in the jedec_dimm(4) driver, and the manpage for that
687 driver includes migration instructions. If you have "device jedec_ts"
688 in your kernel configuration file, it must be removed.
691 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
692 This should have no effect if the kernel is booted via BIOS/legacy boot.
693 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
694 has a buggy firmware that prevents a successful boot due to use of
698 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
699 support has been removed from the tree. These ports were
700 obsolete and/or known to be broken for many years.
703 loader.efi has been augmented to participate more fully in the
704 UEFI boot manager protocol. loader.efi will now look at the
705 BootXXXX environment variable to determine if a specific kernel
706 or root partition was specified. XXXX is derived from BootCurrent.
707 efibootmgr(8) manages these standard UEFI variables.
710 zfsloader's functionality has now been folded into loader.
711 zfsloader is no longer necessary once you've updated your
712 boot blocks. For a transition period, we will install a
713 hardlink for zfsloader to loader to allow a smooth transition
714 until the boot blocks can be updated (hard link because old
715 zfs boot blocks don't understand symlinks).
718 ARM64 now have efifb support, if you want to have serial console
719 on your arm64 board when an screen is connected and the bootloader
720 setup a frame buffer for us to use, just add :
724 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
725 an screen connected as the firmware will setup a frame buffer are that
726 u-boot will expose as an EFI frame buffer.
729 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
730 or take steps to update /etc/passwd before doing installworld on
731 existing systems. Do not skip the "mergemaster -Fp" step before
732 installworld, as described in the update procedures near the bottom
733 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
734 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
735 the ntp config file contain options that change file/dir locations.
736 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
737 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
738 taking steps to ensure that all required files/dirs are accessible
742 Big endian arm support has been removed.
745 The static environment setup in kernel configs is no longer mutually
746 exclusive with the loader(8) environment by default. In order to
747 restore the previous default behavior of disabling the loader(8)
748 environment if a static environment is present, you must specify
749 loader_env.disabled=1 in the static environment.
752 The ABI of syscalls used by management tools like sockstat and
753 netstat has been broken to allow 32-bit binaries to work on
754 64-bit kernels without modification. These programs will need
755 to match the kernel in order to function. External programs may
756 require minor modifications to accommodate a change of type in
757 structures from pointers to 64-bit virtual addresses.
760 On i386 and amd64 atomics are now inlined. Out of tree modules using
761 atomics will need to be rebuilt.
764 The '%I' format in the kern.corefile sysctl limits the number of
765 core files that a process can generate to the number stored in the
766 debug.ncores sysctl. The '%I' format is replaced by the single digit
767 index. Previously, if all indexes were taken the kernel would overwrite
768 only a core file with the highest index in a filename.
769 Currently the system will create a new core file if there is a free
770 index or if all slots are taken it will overwrite the oldest one.
773 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
774 6.0.1. Please see the 20141231 entry below for information about
775 prerequisites and upgrading, if you are not already using clang 3.5.0
779 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
780 needed to be changed to work with it. This change was made with r335763
781 and requires a mergemaster / etcupdate / etc to update the installed
785 r334930 changed the interface between the NFS modules, so they all
786 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
789 As of r334391 lld is the default amd64 system linker; it is installed
790 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
794 The kernel / userland interface for devinfo changed, so you'll
795 need a new kernel and userland as a pair for it to work (rebuilding
796 lib/libdevinfo is all that's required). devinfo and devmatch will
797 not work, but everything else will when there's a mismatch.
800 The on-disk format for hwpmc callchain records has changed to include
801 threadid corresponding to a given record. This changes the field offsets
802 and thus requires that libpmcstat be rebuilt before using a kernel
806 The vxge(4) driver has been removed. This driver was introduced into
807 HEAD one week before the Exar left the Ethernet market and is not
808 known to be used. If you have device vxge in your kernel config file
812 The amd64 kernel now requires a ld that supports ifunc to produce a
813 working kernel, either lld or a newer binutils. lld is built by default
814 on amd64, and the 'buildkernel' target uses it automatically. However,
815 it is not the default linker, so building the kernel the traditional
816 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
817 binutils port/package). lld will soon be default, and this requirement
820 NOTE: As of r334391 lld is the default system linker on amd64, and no
821 workaround is necessary.
824 The nxge(4) driver has been removed. This driver was for PCI-X 10g
825 cards made by s2io/Neterion. The company was acquired by Exar and
826 no longer sells or supports Ethernet products. If you have device
827 nxge in your kernel config file it must be removed.
830 The tz database (tzdb) has been updated to 2018e. This version more
831 correctly models time stamps in time zones with negative DST such as
832 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
833 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
834 time zone abbreviations and the tm_isdst flag.
837 The ixgb(4) driver has been removed. This driver was for an early and
838 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
839 quickly shifted to the long lived ixgbe family. If you have device
840 ixgb in your kernel config file it must be removed.
843 The lmc(4) driver has been removed. This was a WAN interface
844 card that was already reportedly rare in 2003, and had an ambiguous
845 license. If you have device lmc in your kernel config file it must
849 Support for Arcnet networks has been removed. If you have device
850 arcnet or device cm in your kernel config file they must be
854 Support for FDDI networks has been removed. If you have device
855 fddi or device fpa in your kernel config file they must be
859 In addition to supporting RFC 3164 formatted messages, the
860 syslogd(8) service is now capable of parsing RFC 5424 formatted
861 log messages. The main benefit of using RFC 5424 is that clients
862 may now send log messages with timestamps containing year numbers,
863 microseconds and time zone offsets.
865 Similarly, the syslog(3) C library function has been altered to
866 send RFC 5424 formatted messages to the local system logging
867 daemon. On systems using syslogd(8), this change should have no
868 negative impact, as long as syslogd(8) and the C library are
869 updated at the same time. On systems using a different system
870 logging daemon, it may be necessary to make configuration
871 adjustments, depending on the software used.
873 When using syslog-ng, add the 'syslog-protocol' flag to local
874 input sources to enable parsing of RFC 5424 formatted messages:
877 unix-dgram("/var/run/log" flags(syslog-protocol));
880 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
881 of the 'imuxsock' module to let messages be processed by the
882 regular RFC 3164/5424 parsing pipeline:
884 module(load="imuxsock" SysSock.UseSpecialParser="off")
886 Do note that these changes only affect communication between local
887 applications and syslogd(8). The format that syslogd(8) uses to
888 store messages on disk or forward messages to other systems
889 remains unchanged. syslogd(8) still uses RFC 3164 for these
890 purposes. Options to customize this behaviour will be added in the
891 future. Utilities that process log files stored in /var/log are
892 thus expected to continue to function as before.
894 __FreeBSD_version has been incremented to 1200061 to denote this
898 Support for token ring networks has been removed. If you
899 have "device token" in your kernel config you should remove
900 it. No device drivers supported token ring.
903 makefs was modified to be able to tag ISO9660 El Torito boot catalog
904 entries as EFI instead of overloading the i386 tag as done previously.
905 The amd64 mkisoimages.sh script used to build amd64 ISO images for
906 release was updated to use this. This may mean that makefs must be
907 updated before "make cdrom" can be run in the release directory. This
908 should be as simple as:
910 $ cd $SRCDIR/usr.sbin/makefs
911 $ make depend all install
914 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
915 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
916 Co-existence for the transition period will come shortly. Booting is a
917 complex environment and test coverage for Lua-enabled loaders has been
918 thin, so it would be prudent to assume it might not work and make
919 provisions for backup boot methods.
922 devmatch functionality has been turned on in devd. It will automatically
923 load drivers for unattached devices. This may cause unexpected drivers
924 to be loaded. Please report any problems to current@ and
928 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
929 6.0.0. Please see the 20141231 entry below for information about
930 prerequisites and upgrading, if you are not already using clang 3.5.0
934 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
935 This means it is used to link the kernel and userland libraries and
936 executables, but is not yet installed as /usr/bin/ld by default.
938 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
939 WITHOUT_LLD_BOOTSTRAP=yes
942 On i386, pmtimer has been removed. Its functionality has been folded
943 into apm. It was a no-op on ACPI in current for a while now (but was
944 still needed on i386 in FreeBSD 11 and earlier). Users may need to
945 remove it from kernel config files.
948 The use of RSS hash from the network card aka flowid has been
949 disabled by default for lagg(4) as it's currently incompatible with
950 the lacp and loadbalance protocols.
952 This can be re-enabled by setting the following in loader.conf:
953 net.link.lagg.default_use_flowid="1"
956 The SW_WATCHDOG option is no longer necessary to enable the
957 hardclock-based software watchdog if no hardware watchdog is
958 configured. As before, SW_WATCHDOG will cause the software
959 watchdog to be enabled even if a hardware watchdog is configured.
962 r326887 fixes the issue described in the 20171214 UPDATING entry.
963 r326888 flips the switch back to building GELI support always.
966 r362593 broke ZFS + GELI support for reasons unknown. However,
967 it also broke ZFS support generally, so GELI has been turned off
968 by default as the lesser evil in r326857. If you boot off ZFS and/or
969 GELI, it might not be a good time to update.
972 PowerPC users must update loader(8) by rebuilding world before
973 installing a new kernel, as the protocol connecting them has
974 changed. Without the update, loader metadata will not be passed
975 successfully to the kernel and users will have to enter their
976 root partition at the kernel mountroot prompt to continue booting.
977 Newer versions of loader can boot old kernels without issue.
980 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
981 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
982 to WITH/OUT_LOADER_GELI.
985 The naive and non-compliant support of posix_fallocate(2) in ZFS
986 has been removed as of r325320. The system call now returns EINVAL
987 when used on a ZFS file. Although the new behavior complies with the
988 standard, some consumers are not prepared to cope with it.
989 One known victim is lld prior to r325420.
992 Building in a FreeBSD src checkout will automatically create object
993 directories now rather than store files in the current directory if
994 'make obj' was not ran. Calling 'make obj' is no longer necessary.
995 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
996 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
1000 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
1001 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
1002 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
1003 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
1004 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
1005 The UNIFIED_OBJDIR option is a transitional feature that will be
1006 removed for 12.0 release; please migrate to the new format for any
1007 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
1008 than hardcoding paths.
1011 The native-xtools target no longer installs the files by default to the
1012 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
1013 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
1016 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
1017 options are changing from controlling the build if defined / undefined
1018 to controlling the build with explicit 'yes' or 'no' values. They will
1019 shift to WITH/WITHOUT options to match other options in the system.
1022 libstand has turned into a private library for sys/boot use only.
1023 It is no longer supported as a public interface outside of sys/boot.
1026 The arm port has split armv6 into armv6 and armv7. armv7 is now
1027 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
1028 and are running a kernel from before r324363, you will need to add
1029 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
1032 When building multiple kernels using KERNCONF, non-existent KERNCONF
1033 files will produce an error and buildkernel will fail. Previously
1034 missing KERNCONF files silently failed giving no indication as to
1035 why, only to subsequently discover during installkernel that the
1036 desired kernel was never built in the first place.
1039 The default serial number format for CTL LUNs has changed. This will
1040 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
1041 or iSCSI clients care about their LUNs' serial numbers. Users who
1042 require serial number stability should hardcode serial numbers in
1046 For 32-bit arm compiled for hard-float support, soft-floating point
1047 binaries now always get their shared libraries from
1048 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
1049 /usr/libsoft also existed). Only users with a hard-float ld.so, but
1050 soft-float everything else should be affected.
1053 The geli password typed at boot is now hidden. To restore the previous
1054 behavior, see geli(8) for configuration options.
1057 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
1058 sysctl values. Minor nit, but requires a rebuild of both world/kernel
1062 "make check" behavior (made in ^/head@r295380) has been changed to
1063 execute from a limited sandbox, as opposed to executing from
1067 - The "beforecheck" and "aftercheck" targets are now specified.
1068 - ${CHECKDIR} (added in commit noted above) has been removed.
1069 - Legacy behavior can be enabled by setting
1070 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
1072 If the limited sandbox mode is enabled, "make check" will execute
1073 "make distribution", then install, execute the tests, and clean up the
1074 sandbox if successful.
1076 The "make distribution" and "make install" targets are typically run as
1077 root to set appropriate permissions and ownership at installation time.
1078 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
1079 environment if executing "make check" with limited sandbox mode using
1080 an unprivileged user.
1083 Since the switch to GPT disk labels, fsck for UFS/FFS has been
1084 unable to automatically find alternate superblocks. As of r322297,
1085 the information needed to find alternate superblocks has been
1086 moved to the end of the area reserved for the boot block.
1087 Filesystems created with a newfs of this vintage or later
1088 will create the recovery information. If you have a filesystem
1089 created prior to this change and wish to have a recovery block
1090 created for your filesystem, you can do so by running fsck in
1091 foreground mode (i.e., do not use the -p or -y options). As it
1092 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
1093 to which you should answer yes.
1096 As of r321665, an NFSv4 server configuration that services
1097 Kerberos mounts or clients that do not support the uid/gid in
1098 owner/owner_group string capability, must explicitly enable
1099 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
1100 machine's /etc/rc.conf file.
1103 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
1104 Please see the 20141231 entry below for information about prerequisites
1105 and upgrading, if you are not already using clang 3.5.0 or higher.
1108 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
1109 r-commands (rlogin, rsh, etc.) to be built with the base system.
1112 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
1113 a very major ABI incompatible change, so users of FreeBSD/powerpc must
1114 be careful when performing source upgrades. It is best to run
1115 'make installworld' from an alternate root system, either a live
1116 CD/memory stick, or a temporary root partition. Additionally, all ports
1117 must be recompiled. powerpc64 is largely unaffected, except in the case
1118 of 32-bit compatibility. All 32-bit binaries will be affected.
1121 Forward compatibility for the "ino64" project have been committed. This
1122 will allow most new binaries to run on older kernels in a limited
1123 fashion. This prevents many of the common foot-shooting actions in the
1124 upgrade as well as the limited ability to roll back the kernel across
1125 the ino64 upgrade. Complicated use cases may not work properly, though
1126 enough simpler ones work to allow recovery in most situations.
1129 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
1130 if you require the GPL compiler.
1133 The internal ABI used for communication between the NFS kernel modules
1134 was changed by r320085, so __FreeBSD_version was bumped to
1135 ensure all the NFS related modules are updated together.
1138 The ABI of struct event was changed by extending the data
1139 member to 64bit and adding ext fields. For upgrade, same
1140 precautions as for the entry 20170523 "ino64" must be
1144 The GNU roff toolchain has been removed from base. To render manpages
1145 which are not supported by mandoc(1), man(1) can fallback on GNU roff
1146 from ports (and recommends to install it).
1147 To render roff(7) documents, consider using GNU roff from ports or the
1148 heirloom doctools roff toolchain from ports via pkg install groff or
1149 via pkg install heirloom-doctools.
1152 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
1153 smaller runtime footprint builds. This is useful for embedded systems
1154 which only require one chipset support.
1156 If you load it as a module, make sure this is in /boot/loader.conf:
1160 This will load the HAL, all chip/RF backends and if_ath_pci.
1161 If you have if_ath_pci in /boot/loader.conf, ensure it is after
1162 if_ath or it will not load any HAL chipset support.
1164 If you want to selectively load things (eg on ye cheape ARM/MIPS
1165 platforms where RAM is at a premium) you should:
1168 * load the chip modules in question
1169 * load ath_rate, ath_dfs
1171 * load if_ath_pci and/or if_ath_ahb depending upon your particular
1172 bus bind type - this is where probe/attach is done.
1174 For further comments/feedback, poke adrian@ .
1177 The "ino64" 64-bit inode project has been committed, which extends
1178 a number of types to 64 bits. Upgrading in place requires care and
1179 adherence to the documented upgrade procedure.
1181 If using a custom kernel configuration ensure that the
1182 COMPAT_FREEBSD11 option is included (as during the upgrade the
1183 system will be running the ino64 kernel with the existing world).
1185 For the safest in-place upgrade begin by removing previous build
1186 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full
1187 procedure documented below under the heading "To rebuild everything and
1188 install it on the current system." Specifically, a reboot is required
1189 after installing the new kernel before installing world. While an
1190 installworld normally works by accident from multiuser after rebooting
1191 the proper kernel, there are many cases where this will fail across this
1192 upgrade and installworld from single user is required.
1195 The NATM framework including the en(4), fatm(4), hatm(4), and
1196 patm(4) devices has been removed. Consumers should plan a
1197 migration before the end-of-life date for FreeBSD 11.
1200 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
1201 diff has not been implemented, if those are needed a newer version of
1202 GNU diff is available via the diffutils package under the gdiff name.
1205 As of r316810 for ipfilter, keep frags is no longer assumed when
1206 keep state is specified in a rule. r316810 aligns ipfilter with
1207 documentation in man pages separating keep frags from keep state.
1208 This allows keep state to be specified without forcing keep frags
1209 and allows keep frags to be specified independently of keep state.
1210 To maintain previous behaviour, also specify keep frags with
1211 keep state (as documented in ipf.conf.5).
1214 arm64 builds now use the base system LLD 4.0.0 linker by default,
1215 instead of requiring that the aarch64-binutils port or package be
1216 installed. To continue using aarch64-binutils, set
1217 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
1220 The UDP optimization in entry 20160818 that added the sysctl
1221 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
1222 packets will no longer be treated as L3 broadcast packets.
1225 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
1226 use any explicitly assigned loopback address available in the jail
1227 instead of using the first assigned address of the jail.
1230 The ctl.ko module no longer implements the iSCSI target frontend:
1231 cfiscsi.ko does instead.
1233 If building cfiscsi.ko as a kernel module, the module can be loaded
1234 via one of the following methods:
1235 - `cfiscsi_load="YES"` in loader.conf(5).
1236 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
1237 - ctladm(8)/ctld(8), when compiled with iSCSI support
1238 (`WITH_ISCSI=yes` in src.conf(5))
1240 Please see cfiscsi(4) for more details.
1243 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
1244 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
1245 same source (previously, the dependency of mmcsd.ko on mmc.ko was
1246 missing, but mmcsd.ko now will refuse to load if it is incompatible
1250 The syntax of ipfw(8) named states was changed to avoid ambiguity.
1251 If you have used named states in the firewall rules, you need to modify
1252 them after installworld and before rebooting. Now named states must
1253 be prefixed with colon.
1256 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
1257 removed as the userland we provide cannot use them. The KMS version
1258 (sys/dev/drm2) supports the same hardware.
1261 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
1262 Please see the 20141231 entry below for information about prerequisites
1263 and upgrading, if you are not already using clang 3.5.0 or higher.
1266 The code that provides support for ZFS .zfs/ directory functionality
1267 has been reimplemented. It's not possible now to create a snapshot
1268 by mkdir under .zfs/snapshot/. That should be the only user visible
1272 EISA bus support has been removed. The WITH_EISA option is no longer
1276 MCA bus support has been removed.
1279 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
1280 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
1283 The EM_MULTIQUEUE kernel configuration option is deprecated now that
1284 the em(4) driver conforms to iflib specifications.
1287 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
1288 IFLIB. If you have a custom kernel configuration that excludes em(4)
1289 but you use igb(4), you need to re-add em(4) to your custom
1293 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
1294 Please see the 20141231 entry below for information about prerequisites
1295 and upgrading, if you are not already using clang 3.5.0 or higher.
1298 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
1299 Please see the 20141231 entry below for information about prerequisites
1300 and upgrading, if you are not already using clang 3.5.0 or higher.
1303 The layout of the pmap structure has changed for powerpc to put the pmap
1304 statistics at the front for all CPU variations. libkvm(3) and all tools
1305 that link against it need to be recompiled.
1308 isl(4) and cyapa(4) drivers now require a new driver,
1309 chromebook_platform(4), to work properly on Chromebook-class hardware.
1310 On other types of hardware the drivers may need to be configured using
1311 device hints. Please see the corresponding manual pages for details.
1314 The urtwn(4) driver was merged into rtwn(4) and now consists of
1315 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
1317 Also, firmware for RTL8188CE was renamed due to possible name
1318 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
1321 GNU rcs has been removed from base. It is available as packages:
1322 - rcs: Latest GPLv3 GNU rcs version.
1323 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
1327 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
1328 modules now requires that the kernel configuration contain the
1329 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
1332 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
1333 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
1336 Relocatable object files with the extension of .So have been renamed
1337 to use an extension of .pico instead. The purpose of this change is
1338 to avoid a name clash with shared libraries on case-insensitive file
1339 systems. On those file systems, foo.So is the same file as foo.so.
1342 GNU rcs has been turned off by default. It can (temporarily) be built
1343 again by adding WITH_RCS knob in src.conf.
1344 Otherwise, GNU rcs is available from packages:
1345 - rcs: Latest GPLv3 GNU rcs version.
1346 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
1349 The backup_uses_rcs functionality has been removed from rc.subr.
1352 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
1353 two separate components, QUEUE_MACRO_DEBUG_TRACE and
1354 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
1355 QUEUE_MACRO_DEBUG behavior.
1358 r304787 changed some ioctl interfaces between the iSCSI userspace
1359 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1360 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1364 The UDP receive code has been updated to only treat incoming UDP
1365 packets that were addressed to an L2 broadcast address as L3
1366 broadcast packets. It is not expected that this will affect any
1367 standards-conforming UDP application. The new behaviour can be
1368 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1372 Remove the openbsd_poll system call.
1373 __FreeBSD_version has been bumped because of this.
1376 The stable/11 branch has been created from head@r302406.
1379 The libc stub for the pipe(2) system call has been replaced with
1380 a wrapper that calls the pipe2(2) system call and the pipe(2)
1381 system call is now only implemented by the kernels that include
1382 "options COMPAT_FREEBSD10" in their config file (this is the
1383 default). Users should ensure that this option is enabled in
1384 their kernel or upgrade userspace to r302092 before upgrading their
1388 CAM will now strip leading spaces from SCSI disks' serial numbers.
1389 This will affect users who create UFS filesystems on SCSI disks using
1390 those disk's diskid device nodes. For example, if /etc/fstab
1391 previously contained a line like
1392 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
1393 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
1394 transforms like gmirror may also be affected. ZFS users should
1398 The bitstring(3) API has been updated with new functionality and
1399 improved performance. But it is binary-incompatible with the old API.
1400 Objects built with the new headers may not be linked against objects
1401 built with the old headers.
1404 The brk and sbrk functions have been removed from libc on arm64.
1405 Binutils from ports has been updated to not link to these
1406 functions and should be updated to the latest version before
1407 installing a new libc.
1410 The armv6 port now defaults to hard float ABI. Limited support
1411 for running both hardfloat and soft float on the same system
1412 is available using the libraries installed with -DWITH_LIBSOFT.
1413 This has only been tested as an upgrade path for installworld
1414 and packages may fail or need manual intervention to run. New
1415 packages will be needed.
1417 To update an existing self-hosted armv6hf system, you must add
1418 TARGET_ARCH=armv6 on the make command line for both the build
1419 and the install steps.
1422 Kernel modules compiled outside of a kernel build now default to
1423 installing to /boot/modules instead of /boot/kernel. Many kernel
1424 modules built this way (such as those in ports) already overrode
1425 KMODDIR explicitly to install into /boot/modules. However,
1426 manually building and installing a module from /sys/modules will
1427 now install to /boot/modules instead of /boot/kernel.
1430 The CAM I/O scheduler has been committed to the kernel. There should be
1431 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1432 list of known rogues that claim support for this but actually corrupt
1433 data is believed to be complete, be on the lookout for data
1434 corruption. The known rogue list is believed to be complete:
1436 o Crucial MX100, M550 drives with MU01 firmware.
1437 o Micron M510 and M550 drives with MU01 firmware.
1438 o Micron M500 prior to MU07 firmware
1439 o Samsung 830, 840, and 850 all firmwares
1440 o FCCT M500 all firmwares
1442 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1443 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1444 updated firmware. Black listed drives will work correctly because these
1445 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1446 this list is the same as found in Linux, it's believed there are no
1447 other rogues in the market place. All other models from the above
1450 To be safe, if you are at all concerned, you can quirk each of your
1451 drives to prevent NCQ from being sent by setting:
1452 kern.cam.ada.X.quirks="0x2"
1453 in loader.conf. If the drive requires the 4k sector quirk, set the
1454 quirks entry to 0x3.
1457 The FAST_DEPEND build option has been removed and its functionality is
1458 now the one true way. The old mkdep(1) style of 'make depend' has
1459 been removed. See 20160311 for further details.
1462 Resource range types have grown from unsigned long to uintmax_t. All
1463 drivers, and anything using libdevinfo, need to be recompiled.
1466 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1467 builds. It no longer runs mkdep(1) during 'make depend', and the
1468 'make depend' stage can safely be skipped now as it is auto ran
1469 when building 'make all' and will generate all SRCS and DPSRCS before
1470 building anything else. Dependencies are gathered at compile time with
1471 -MF flags kept in separate .depend files per object file. Users should
1472 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1473 stale .depend files.
1476 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1477 kernel modules. Therefore, if you load any kernel modules at boot time,
1478 please install the boot loaders after you install the kernel, but before
1482 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1483 make installkernel KERNCONF=YOUR_KERNEL_HERE
1484 make -C sys/boot install
1485 <reboot in single user>
1487 Then follow the usual steps, described in the General Notes section,
1491 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1492 see the 20141231 entry below for information about prerequisites and
1493 upgrading, if you are not already using clang 3.5.0 or higher.
1496 The AIO subsystem is now a standard part of the kernel. The
1497 VFS_AIO kernel option and aio.ko kernel module have been removed.
1498 Due to stability concerns, asynchronous I/O requests are only
1499 permitted on sockets and raw disks by default. To enable
1500 asynchronous I/O requests on all file types, set the
1501 vfs.aio.enable_unsafe sysctl to a non-zero value.
1504 The ELF object manipulation tool objcopy is now provided by the
1505 ELF Tool Chain project rather than by GNU binutils. It should be a
1506 drop-in replacement, with the addition of arm64 support. The
1507 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1508 to obtain the GNU version if necessary.
1511 Building ZFS pools on top of zvols is prohibited by default. That
1512 feature has never worked safely; it's always been prone to deadlocks.
1513 Using a zvol as the backing store for a VM guest's virtual disk will
1514 still work, even if the guest is using ZFS. Legacy behavior can be
1515 restored by setting vfs.zfs.vol.recursive=1.
1518 The NONE and HPN patches has been removed from OpenSSH. They are
1519 still available in the security/openssh-portable port.
1522 With the addition of ypldap(8), a new _ypldap user is now required
1523 during installworld. "mergemaster -p" can be used to add the user
1524 prior to installworld, as documented in the handbook.
1527 The tftp loader (pxeboot) now uses the option root-path directive. As a
1528 consequence it no longer looks for a pxeboot.4th file on the tftp
1529 server. Instead it uses the regular /boot infrastructure as with the
1533 The code to start recording plug and play data into the modules has
1534 been committed. While the old tools will properly build a new kernel,
1535 a number of warnings about "unknown metadata record 4" will be produced
1536 for an older kldxref. To avoid such warnings, make sure to rebuild
1537 the kernel toolchain (or world). Make sure that you have r292078 or
1538 later when trying to build 292077 or later before rebuilding.
1541 Debug data files are now built by default with 'make buildworld' and
1542 installed with 'make installworld'. This facilitates debugging but
1543 requires more disk space both during the build and for the installed
1544 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1548 r291527 changed the internal interface between the nfsd.ko and
1549 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1550 __FreeBSD_version has been bumped because of this.
1553 Add support for unicode collation strings leads to a change of
1554 order of files listed by ls(1) for example. To get back to the old
1555 behaviour, set LC_COLLATE environment variable to "C".
1557 Databases administrators will need to reindex their databases given
1558 collation results will be different.
1560 Due to a bug in install(1) it is recommended to remove the ancient
1561 locales before running make installworld.
1563 rm -rf /usr/share/locale/*
1566 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1567 libcrypto.so.7 or libssl.so.7 must be recompiled.
1570 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1571 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1572 should be replaced with isp_2400 and isp_2500 modules respectively.
1575 The build previously allowed using 'make -n' to not recurse into
1576 sub-directories while showing what commands would be executed, and
1577 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1578 and 'make -N' will not.
1581 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1582 and etcupdate will now use this file. A custom sendmail.cf is now
1583 updated via this mechanism rather than via installworld. If you had
1584 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1585 want to remove the exclusion or change it to "always install".
1586 /etc/mail/sendmail.cf is now managed the same way regardless of
1587 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1588 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1591 Compatibility shims for legacy ATA device names have been removed.
1592 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1593 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1594 environment variables, /dev/ad* and /dev/ar* symbolic links.
1597 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1598 Please see the 20141231 entry below for information about prerequisites
1599 and upgrading, if you are not already using clang 3.5.0 or higher.
1602 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1603 and renamed from .symbols to .debug. This reduces the size requirements
1604 on the boot partition or file system and provides consistency with
1605 userland debug files.
1607 When using the supported kernel installation method the
1608 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1609 as is done with /boot/kernel.
1611 Developers wishing to maintain the historical behavior of installing
1612 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1615 The wireless drivers had undergone changes that remove the 'parent
1616 interface' from the ifconfig -l output. The rc.d network scripts
1617 used to check presence of a parent interface in the list, so old
1618 scripts would fail to start wireless networking. Thus, etcupdate(3)
1619 or mergemaster(8) run is required after kernel update, to update your
1620 rc.d scripts in /etc.
1623 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1624 These configurations are now automatically interpreted as
1625 'scrub fragment reassemble'.
1628 Kernel-loadable modules for the random(4) device are back. To use
1629 them, the kernel must have
1632 options RANDOM_LOADABLE
1634 kldload(8) can then be used to load random_fortuna.ko
1635 or random_yarrow.ko. Please note that due to the indirect
1636 function calls that the loadable modules need to provide,
1637 the build-in variants will be slightly more efficient.
1639 The random(4) kernel option RANDOM_DUMMY has been retired due to
1640 unpopularity. It was not all that useful anyway.
1643 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1644 Control over building the ELF Tool Chain tools is now provided by
1645 the WITHOUT_TOOLCHAIN knob.
1648 The polarity of Pulse Per Second (PPS) capture events with the
1649 uart(4) driver has been corrected. Prior to this change the PPS
1650 "assert" event corresponded to the trailing edge of a positive PPS
1651 pulse and the "clear" event was the leading edge of the next pulse.
1653 As the width of a PPS pulse in a typical GPS receiver is on the
1654 order of 1 millisecond, most users will not notice any significant
1655 difference with this change.
1657 Anyone who has compensated for the historical polarity reversal by
1658 configuring a negative offset equal to the pulse width will need to
1659 remove that workaround.
1662 The default group assigned to /dev/dri entries has been changed
1663 from 'wheel' to 'video' with the id of '44'. If you want to have
1664 access to the dri devices please add yourself to the video group
1667 # pw groupmod video -m $USER
1670 The menu.rc and loader.rc files will now be replaced during
1671 upgrades. Please migrate local changes to menu.rc.local and
1672 loader.rc.local instead.
1675 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1676 strings and strip have been removed. The src.conf(5) knob
1677 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1680 As ZFS requires more kernel stack pages than is the default on some
1681 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1682 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1684 Please consider using 'options KSTACK_PAGES=X' where X is greater
1685 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1688 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1689 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1690 default, i.e., they will not contain "::". For example, instead
1691 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1692 to have a more specific match, such as different map entries for
1693 IPv6:0:0 vs IPv6:0. This change requires that configuration
1694 data (including maps, files, classes, custom ruleset, etc.) must
1695 use the same format, so make certain such configuration data is
1696 upgrading. As a very simple check search for patterns like
1697 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1698 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1699 the cf option UseCompressedIPv6Addresses.
1702 The default kernel entropy-processing algorithm is now
1703 Fortuna, replacing Yarrow.
1705 Assuming you have 'device random' in your kernel config
1706 file, the configurations allow a kernel option to override
1707 this default. You may choose *ONE* of:
1709 options RANDOM_YARROW # Legacy /dev/random algorithm.
1710 options RANDOM_DUMMY # Blocking-only driver.
1712 If you have neither, you get Fortuna. For most people,
1713 read no further, Fortuna will give a /dev/random that works
1714 like it always used to, and the difference will be irrelevant.
1716 If you remove 'device random', you get *NO* kernel-processed
1717 entropy at all. This may be acceptable to folks building
1718 embedded systems, but has complications. Carry on reading,
1719 and it is assumed you know what you need.
1721 *PLEASE* read random(4) and random(9) if you are in the
1722 habit of tweaking kernel configs, and/or if you are a member
1723 of the embedded community, wanting specific and not-usual
1724 behaviour from your security subsystems.
1726 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1727 random', you will NOT have a functioning /dev/random, and
1728 many cryptographic features will not work, including SSH.
1729 You may also find strange behaviour from the random(3) set
1730 of library functions, in particular sranddev(3), srandomdev(3)
1731 and arc4random(3). The reason for this is that the KERN_ARND
1732 sysctl only returns entropy if it thinks it has some to
1733 share, and with RANDOM_DUMMY or no 'device random' this
1737 An additional fix for the issue described in the 20150614 sendmail
1738 entry below has been committed in revision 284717.
1741 FreeBSD's old make (fmake) has been removed from the system. It is
1742 available as the devel/fmake port or via pkg install fmake.
1745 The fix for the issue described in the 20150614 sendmail entry
1746 below has been committed in revision 284436. The work
1747 around described in that entry is no longer needed unless the
1748 default setting is overridden by a confDH_PARAMETERS configuration
1749 setting of '5' or pointing to a 512 bit DH parameter file.
1752 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1753 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1754 and devel/kyua to version 0.20+ and adjust any calling code to work
1755 with Kyuafile and kyua.
1758 The import of openssl to address the FreeBSD-SA-15:10.openssl
1759 security advisory includes a change which rejects handshakes
1760 with DH parameters below 768 bits. sendmail releases prior
1761 to 8.15.2 (not yet released), defaulted to a 512 bit
1762 DH parameter setting for client connections. To work around
1763 this interoperability, sendmail can be configured to use a
1764 2048 bit DH parameter by:
1766 1. Edit /etc/mail/`hostname`.mc
1767 2. If a setting for confDH_PARAMETERS does not exist or
1768 exists and is set to a string beginning with '5',
1769 replace it with '2'.
1770 3. If a setting for confDH_PARAMETERS exists and is set to
1771 a file path, create a new file with:
1772 openssl dhparam -out /path/to/file 2048
1773 4. Rebuild the .cf file:
1774 cd /etc/mail/; make; make install
1775 5. Restart sendmail:
1776 cd /etc/mail/; make restart
1778 A sendmail patch is coming, at which time this file will be
1782 Generation of legacy formatted entries have been disabled by default
1783 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1784 entries were converted to use the new format by default when the new,
1785 machine independent format have been added and supported since FreeBSD
1788 Please see the pwd_mkdb(8) manual page for further details.
1791 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1792 20141231 entry below for information about prerequisites and upgrading,
1793 if you are not already using 3.5.0 or higher.
1796 TI platform code switched to using vendor DTS files and this update
1797 may break existing systems running on Beaglebone, Beaglebone Black,
1800 - dtb files should be regenerated/reinstalled. Filenames are the
1801 same but content is different now
1802 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1803 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1804 addressing scheme is now pin 25 on /dev/gpioc3.
1805 - Pandaboard: /etc/ttys should be updated, serial console device is
1806 now /dev/ttyu2, not /dev/ttyu0
1809 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1810 If you need the GNU extension from groff soelim(1), install groff
1811 from package: pkg install groff, or via ports: textproc/groff.
1814 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1815 defined in symlink(7); previously symlinks were silently ignored.
1818 The const qualifier has been removed from iconv(3) to comply with
1819 POSIX. The ports tree is aware of this from r384038 onwards.
1822 Libraries specified by LIBADD in Makefiles must have a corresponding
1823 DPADD_<lib> variable to ensure correct dependencies. This is now
1824 enforced in src.libnames.mk.
1827 From legacy ata(4) driver was removed support for SATA controllers
1828 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1829 Kernel modules ataahci and ataadaptec were removed completely,
1830 replaced by ahci and mvs modules respectively.
1833 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1834 the 20141231 entry below for information about prerequisites and
1835 upgrading, if you are not already using 3.5.0 or higher.
1838 The 32-bit PowerPC kernel has been changed to a position-independent
1839 executable. This can only be booted with a version of loader(8)
1840 newer than January 31, 2015, so make sure to update both world and
1841 kernel before rebooting.
1844 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1845 but before r278950, the RNG was not seeded properly. Immediately
1846 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1847 ssh keys or openssl keys) that were generated w/ a kernel from that
1848 range. This does not affect programs that directly used /dev/random
1849 or /dev/urandom. All userland uses of arc4random(3) are affected.
1852 The autofs(4) ABI was changed in order to restore binary compatibility
1853 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1854 with the new kernel.
1857 The powerpc64 kernel has been changed to a position-independent
1858 executable. This can only be booted with a new version of loader(8),
1859 so make sure to update both world and kernel before rebooting.
1862 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1863 only release, no new features have been added. Please see the 20141231
1864 entry below for information about prerequisites and upgrading, if you
1865 are not already using 3.5.0.
1868 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1869 taken from the ELF Tool Chain project rather than GNU binutils. They
1870 should be drop-in replacements, with the addition of arm64 support.
1871 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1872 binutils tools, if necessary. See 20150805 for updated information.
1875 The default Unbound configuration now enables remote control
1876 using a local socket. Users who have already enabled the
1877 local_unbound service should regenerate their configuration
1878 by running "service local_unbound setup" as root.
1881 The GNU texinfo and GNU info pages have been removed.
1882 To be able to view GNU info pages please install texinfo from ports.
1885 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1887 As of this release, a prerequisite for building clang, llvm and lldb is
1888 a C++11 capable compiler and C++11 standard library. This means that to
1889 be able to successfully build the cross-tools stage of buildworld, with
1890 clang as the bootstrap compiler, your system compiler or cross compiler
1891 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1892 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1895 On any standard FreeBSD 10.x or 11.x installation, where clang and
1896 libc++ are on by default (that is, on x86 or arm), this should work out
1899 On 9.x installations where clang is enabled by default, e.g. on x86 and
1900 powerpc, libc++ will not be enabled by default, so libc++ should be
1901 built (with clang) and installed first. If both clang and libc++ are
1902 missing, build clang first, then use it to build libc++.
1904 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1905 the instructions for 9.x above.
1907 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1908 default, and do not build clang.
1910 Many embedded systems are resource constrained, and will not be able to
1911 build clang in a reasonable time, or in some cases at all. In those
1912 cases, cross building bootable systems on amd64 is a workaround.
1914 This new version of clang introduces a number of new warnings, of which
1915 the following are most likely to appear:
1919 This warns in two cases, for both C and C++:
1920 * When the code is trying to take the absolute value of an unsigned
1921 quantity, which is effectively a no-op, and almost never what was
1922 intended. The code should be fixed, if at all possible. If you are
1923 sure that the unsigned quantity can be safely cast to signed, without
1924 loss of information or undefined behavior, you can add an explicit
1925 cast, or disable the warning.
1927 * When the code is trying to take an absolute value, but the called
1928 abs() variant is for the wrong type, which can lead to truncation.
1929 If you want to disable the warning instead of fixing the code, please
1930 make sure that truncation will not occur, or it might lead to unwanted
1933 -Wtautological-undefined-compare and
1934 -Wundefined-bool-conversion
1936 These warn when C++ code is trying to compare 'this' against NULL, while
1937 'this' should never be NULL in well-defined C++ code. However, there is
1938 some legacy (pre C++11) code out there, which actively abuses this
1939 feature, which was less strictly defined in previous C++ versions.
1941 Squid and openjdk do this, for example. The warning can be turned off
1942 for C++98 and earlier, but compiling the code in C++11 mode might result
1943 in unexpected behavior; for example, the parts of the program that are
1944 unreachable could be optimized away.
1947 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1948 kernel sources have been removed. The .h files remain, since some
1949 utilities include them. This will need to be fixed later.
1950 If "mount -t oldnfs ..." is attempted, it will fail.
1951 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1952 the utilities will report errors.
1955 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1956 directories to top level SUBDIR variable when their parent
1957 directory is included in LOCAL_DIRS. Users with build systems with
1958 such hierarchies and without SUBDIR entries in the parent
1959 directory Makefiles should add them or add the directories to
1963 faith(4) and faithd(8) have been removed from the base system. Faith
1964 has been obsolete for a very long time.
1967 vt(4), the new console driver, is enabled by default. It brings
1968 support for Unicode and double-width characters, as well as
1969 support for UEFI and integration with the KMS kernel video
1972 You may need to update your console settings in /etc/rc.conf,
1973 most probably the keymap. During boot, /etc/rc.d/syscons will
1974 indicate what you need to do.
1976 vt(4) still has issues and lacks some features compared to
1977 syscons(4). See the wiki for up-to-date information:
1978 https://wiki.freebsd.org/Newcons
1980 If you want to keep using syscons(4), you can do so by adding
1981 the following line to /boot/loader.conf:
1985 pjdfstest has been integrated into kyua as an opt-in test suite.
1986 Please see share/doc/pjdfstest/README for more details on how to
1990 gperf has been removed from the base system for architectures
1991 that use clang. Ports that require gperf will obtain it from the
1995 pjdfstest has been moved from tools/regression/pjdfstest to
1999 At svn r271982, The default linux compat kernel ABI has been adjusted
2000 to 2.6.18 in support of the linux-c6 compat ports infrastructure
2001 update. If you wish to continue using the linux-f10 compat ports,
2002 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
2003 encouraged to update their linux-compat packages to linux-c6 during
2004 their next update cycle.
2007 The ofwfb driver, used to provide a graphics console on PowerPC when
2008 using vt(4), no longer allows mmap() of all physical memory. This
2009 will prevent Xorg on PowerPC with some ATI graphics cards from
2010 initializing properly unless x11-servers/xorg-server is updated to
2014 The xdev targets have been converted to using TARGET and
2015 TARGET_ARCH instead of XDEV and XDEV_ARCH.
2018 The default unbound configuration has been modified to address
2019 issues with reverse lookups on networks that use private
2020 address ranges. If you use the local_unbound service, run
2021 "service local_unbound setup" as root to regenerate your
2022 configuration, then "service local_unbound reload" to load the
2026 The GNU texinfo and GNU info pages are not built and installed
2027 anymore, WITH_INFO knob has been added to allow to built and install
2029 UPDATE: see 20150102 entry on texinfo's removal
2032 The GNU readline library is now an INTERNALLIB - that is, it is
2033 statically linked into consumers (GDB and variants) in the base
2034 system, and the shared library is no longer installed. The
2035 devel/readline port is available for third party software that
2039 The Itanium architecture (ia64) has been removed from the list of
2040 known architectures. This is the first step in the removal of the
2044 Commit r268115 has added NFSv4.1 server support, merged from
2045 projects/nfsv4.1-server. Since this includes changes to the
2046 internal interfaces between the NFS related modules, a full
2047 build of the kernel and modules will be necessary.
2048 __FreeBSD_version has been bumped.
2051 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
2052 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
2053 which differs from the behaviour controlled by this knob.)
2056 Maximal length of the serial number in CTL was increased from 16 to
2057 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
2058 and ctld, need to be rebuilt to work with a new kernel.
2061 The libatf-c and libatf-c++ major versions were downgraded to 0 and
2062 1 respectively to match the upstream numbers. They were out of
2063 sync because, when they were originally added to FreeBSD, the
2064 upstream versions were not respected. These libraries are private
2065 and not yet built by default, so renumbering them should be a
2066 non-issue. However, unclean source trees will yield broken test
2067 programs once the operator executes "make delete-old-libs" after a
2068 "make installworld".
2070 Additionally, the atf-sh binary was made private by moving it into
2071 /usr/libexec/. Already-built shell test programs will keep the
2072 path to the old binary so they will break after "make delete-old"
2075 If you are using WITH_TESTS=yes (not the default), wipe the object
2076 tree and rebuild from scratch to prevent spurious test failures.
2077 This is only needed once: the misnumbered libraries and misplaced
2078 binaries have been added to OptionalObsoleteFiles.inc so they will
2079 be removed during a clean upgrade.
2082 Clang and llvm have been upgraded to 3.4.1 release.
2085 We bogusly installed src.opts.mk in /usr/share/mk. This file should
2086 be removed to avoid issues in the future (and has been added to
2090 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
2091 past, it affected all builds that used the bsd.*.mk files. The old
2092 behavior was a bug, but people may have relied upon it. To get this
2093 behavior back, you can .include /etc/src.conf from /etc/make.conf
2094 (which is still global and isn't changed). This also changes the
2095 behavior of incremental builds inside the tree of individual
2096 directories. Set MAKESYSPATH to ".../share/mk" to do that.
2097 Although this has survived make universe and some upgrade scenarios,
2098 other upgrade scenarios may have broken. At least one form of
2099 temporary breakage was fixed with MAKESYSPATH settings for buildworld
2100 as well... In cases where MAKESYSPATH isn't working with this
2101 setting, you'll need to set it to the full path to your tree.
2103 One side effect of all this cleaning up is that bsd.compiler.mk
2104 is no longer implicitly included by bsd.own.mk. If you wish to
2105 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
2109 The lindev device has been removed since /dev/full has been made a
2110 standard device. __FreeBSD_version has been bumped.
2113 The knob WITHOUT_VI was added to the base system, which controls
2114 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
2115 in order to reorder files share/termcap and didn't build ex(1) as a
2116 build tool, so building/installing with WITH_VI is highly advised for
2117 build hosts for older releases.
2119 This issue has been fixed in stable/9 and stable/10 in r277022 and
2120 r276991, respectively.
2123 The YES_HESIOD knob has been removed. It has been obsolete for
2124 a decade. Please move to using WITH_HESIOD instead or your builds
2125 will silently lack HESIOD.
2128 The uart(4) driver has been changed with respect to its handling
2129 of the low-level console. Previously the uart(4) driver prevented
2130 any process from changing the baudrate or the CLOCAL and HUPCL
2131 control flags. By removing the restrictions, operators can make
2132 changes to the serial console port without having to reboot.
2133 However, when getty(8) is started on the serial device that is
2134 associated with the low-level console, a misconfigured terminal
2135 line in /etc/ttys will now have a real impact.
2136 Before upgrading the kernel, make sure that /etc/ttys has the
2137 serial console device configured as 3wire without baudrate to
2138 preserve the previous behaviour. E.g:
2139 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
2142 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
2143 to improve performance. To re-enable it, if needed, run rpcbind
2144 with command line option -W.
2147 Switched back to the GPL dtc compiler due to updates in the upstream
2148 dts files not being supported by the BSDL dtc compiler. You will need
2149 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
2150 may result while building dtb files during a kernel build if you fail
2151 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
2154 Clang and llvm have been upgraded to 3.4 release.
2157 The nve(4) driver has been removed. Please use the nfe(4) driver
2158 for NVIDIA nForce MCP Ethernet adapters instead.
2161 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
2162 This could cause certain C++ applications using shared libraries built
2163 against the previous version of libc++ to crash. The incompatibility
2164 has now been fixed, but any C++ applications or shared libraries built
2165 between r261283 and r261801 should be recompiled.
2168 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
2169 capability mode support. Please note that enabling the feature in
2170 kernel is still highly recommended.
2173 OpenSSH is now built with sandbox support, and will use sandbox as
2174 the default privilege separation method. This requires Capsicum
2175 capability mode support in kernel.
2178 The libelf and libdwarf libraries have been updated to newer
2179 versions from upstream. Shared library version numbers for
2180 these two libraries were bumped. Any ports or binaries
2181 requiring these two libraries should be recompiled.
2182 __FreeBSD_version is bumped to 1100006.
2185 If a Makefile in a tests/ directory was auto-generating a Kyuafile
2186 instead of providing an explicit one, this would prevent such
2187 Makefile from providing its own Kyuafile in the future during
2188 NO_CLEAN builds. This has been fixed in the Makefiles but manual
2189 intervention is needed to clean an objdir if you use NO_CLEAN:
2190 # find /usr/obj -name Kyuafile | xargs rm -f
2193 The behavior of gss_pseudo_random() for the krb5 mechanism
2194 has changed, for applications requesting a longer random string
2195 than produced by the underlying enctype's pseudo-random() function.
2196 In particular, the random string produced from a session key of
2197 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
2198 be different at the 17th octet and later, after this change.
2199 The counter used in the PRF+ construction is now encoded as a
2200 big-endian integer in accordance with RFC 4402.
2201 __FreeBSD_version is bumped to 1100004.
2204 The WITHOUT_ATF build knob has been removed and its functionality
2205 has been subsumed into the more generic WITHOUT_TESTS. If you were
2206 using the former to disable the build of the ATF libraries, you
2207 should change your settings to use the latter.
2210 The default version of mtree is nmtree which is obtained from
2211 NetBSD. The output is generally the same, but may vary
2212 slightly. If you found you need identical output adding
2213 "-F freebsd9" to the command line should do the trick. For the
2214 time being, the old mtree is available as fmtree.
2217 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
2218 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
2219 1.1.4_8 and verify bsdyml not linked in, before running "make
2221 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
2223 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
2226 The stable/10 branch has been created in subversion from head
2233 Sometimes, obscure build problems are the result of environment
2234 poisoning. This can happen because the make utility reads its
2235 environment when searching for values for global variables. To run
2236 your build attempts in an "environmental clean room", prefix all make
2237 commands with 'env -i '. See the env(1) manual page for more details.
2238 Occasionally a build failure will occur with "make -j" due to a race
2239 condition. If this happens try building again without -j, and please
2240 report a bug if it happens consistently.
2242 When upgrading from one major version to another it is generally best to
2243 upgrade to the latest code in the currently installed branch first, then
2244 do an upgrade to the new branch. This is the best-tested upgrade path,
2245 and has the highest probability of being successful. Please try this
2246 approach if you encounter problems with a major version upgrade. Since
2247 the stable 4.x branch point, one has generally been able to upgrade from
2248 anywhere in the most recent stable branch to head / current (or even the
2249 last couple of stable branches). See the top of this file when there's
2252 The update process will emit an error on an attempt to perform a build
2253 or install from a FreeBSD version below the earliest supported version.
2254 When updating from an older version the update should be performed one
2255 major release at a time, including running `make delete-old` at each
2258 When upgrading a live system, having a root shell around before
2259 installing anything can help undo problems. Not having a root shell
2260 around can lead to problems if pam has changed too much from your
2261 starting point to allow continued authentication after the upgrade.
2263 This file should be read as a log of events. When a later event changes
2264 information of a prior event, the prior event should not be deleted.
2265 Instead, a pointer to the entry with the new information should be
2266 placed in the old entry. Readers of this file should also sanity check
2267 older entries before relying on them blindly. Authors of new entries
2268 should write them with this in mind.
2272 When upgrading the boot ZFS pool to a new version, always follow
2275 1.) recompile and reinstall the ZFS boot loader and boot block
2276 (this is part of "make buildworld" and "make installworld")
2278 2.) update the ZFS boot block on your boot drive
2280 The following example updates the ZFS boot block on the
2281 freebsd-boot partition of a GPT partitioned drive ada0:
2282 "gpart bootcode -p /boot/gptzfsboot -i $N ada0"
2283 The value $N will typically be 1 (if booting from BIOS) or 2 (if
2286 Non-boot pools do not need these updates.
2290 If you are updating from a prior version of FreeBSD (even one just
2291 a few days old), you should follow this procedure. It is the most
2292 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2294 make kernel-toolchain
2295 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2296 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2298 To test a kernel once
2299 ---------------------
2300 If you just want to boot a kernel once (because you are not sure
2301 if it works, or if you want to boot a known bad kernel to provide
2302 debugging information) run
2303 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2304 nextboot -k testkernel
2306 To rebuild everything and install it on the current system.
2307 -----------------------------------------------------------
2308 # Note: sometimes if you are running current you gotta do more than
2309 # is listed here if you are upgrading from a really old current.
2311 <make sure you have good level 0 dumps>
2313 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2314 make installkernel KERNCONF=YOUR_KERNEL_HERE
2316 <reboot in single user> [3]
2323 To cross-install current onto a separate partition
2324 --------------------------------------------------
2325 # In this approach we use a separate partition to hold
2326 # current's root, 'usr', and 'var' directories. A partition
2327 # holding "/", "/usr" and "/var" should be about 2GB in
2330 <make sure you have good level 0 dumps>
2333 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2334 <maybe newfs current's root partition>
2335 <mount current's root partition on directory ${CURRENT_ROOT}>
2336 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
2337 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2338 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2339 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2340 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2341 <reboot into current>
2342 <do a "native" rebuild/install as described in the previous section>
2343 <maybe install compatibility libraries from ports/misc/compat*>
2347 To upgrade in-place from stable to current
2348 ----------------------------------------------
2349 <make sure you have good level 0 dumps>
2351 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
2352 make installkernel KERNCONF=YOUR_KERNEL_HERE
2354 <reboot in single user> [3]
2361 Make sure that you've read the UPDATING file to understand the
2362 tweaks to various things you need. At this point in the life
2363 cycle of current, things change often and you are on your own
2364 to cope. The defaults can also change, so please read ALL of
2365 the UPDATING entries.
2367 Also, if you are tracking -current, you must be subscribed to
2368 freebsd-current@freebsd.org. Make sure that before you update
2369 your sources that you have read and understood all the recent
2370 messages there. If in doubt, please track -stable which has
2371 much fewer pitfalls.
2373 [1] If you have third party modules, such as vmware, you should disable
2374 them at this point so they don't crash your system on
2375 reboot. Alternatively, you should rebuild all the modules you have in
2376 your system and install them as well. If you are running -current, you
2377 should seriously consider placing all sources to all the modules for
2378 your system (or symlinks to them) in /usr/local/sys/modules so this
2379 happens automatically. If all your modules come from ports, then adding
2380 the port origin directories to PORTS_MODULES instead is also automatic
2382 PORTS_MODULES+=x11/nvidia-driver
2384 [3] From the bootblocks, boot -s, and then do
2388 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed
2389 cd src # full path to source
2390 adjkerntz -i # if CMOS is wall time
2391 Also, when doing a major release upgrade, it is required that you boot
2392 into single user mode to do the installworld.
2394 [4] Note: This step is non-optional. Failure to do this step
2395 can result in a significant reduction in the functionality of the
2396 system. Attempting to do it by hand is not recommended and those
2397 that pursue this avenue should read this file carefully, as well
2398 as the archives of freebsd-current and freebsd-hackers mailing lists
2399 for potential gotchas. The -U option is also useful to consider.
2400 See mergemaster(8) for more information.
2402 [5] Usually this step is a no-op. However, from time to time
2403 you may need to do this if you get unknown user in the following
2404 step. It never hurts to do it all the time. You may need to
2405 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2406 install) after the buildworld before this step if you last updated
2407 from current before 20130425 or from -stable before 20130430.
2409 [6] This only deletes old files and directories. Old libraries
2410 can be deleted by "make delete-old-libs", but you have to make
2411 sure that no program is using those libraries anymore.
2413 [8] The new kernel must be able to run existing binaries used by an
2414 installworld. When upgrading across major versions, the new kernel's
2415 configuration must include the correct COMPAT_FREEBSD<n> option for
2416 existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure
2417 to do so may leave you with a system that is hard to boot to recover. A
2418 GENERIC kernel will include suitable compatibility options to run
2419 binaries from older branches. Note that the ability to run binaries
2420 from unsupported branches is not guaranteed.
2422 Make sure that you merge any new devices from GENERIC since the
2423 last time you updated your kernel config file. Options also
2424 change over time, so you may need to adjust your custom kernels
2427 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2428 "?=" instead of the "=" assignment operator, so that buildworld can
2429 override the CPUTYPE if it needs to.
2431 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2432 not on the command line, or in /etc/make.conf. buildworld will
2433 warn if it is improperly defined.
2436 This file contains a list, in reverse chronological order, of major
2437 breakages in tracking -current. It is not guaranteed to be a complete
2438 list of such breakages, and only contains entries since September 23, 2011.
2439 If you need to see UPDATING entries from before that date, you will need
2440 to fetch an UPDATING file from an older FreeBSD release.
2442 Copyright information:
2444 Copyright 1998-2009 M. Warner Losh <imp@FreeBSD.org>
2446 Redistribution, publication, translation and use, with or without
2447 modification, in full or in part, in any form or format of this
2448 document are permitted without further permission from the author.
2450 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2451 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2452 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2453 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2454 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2455 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2456 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2457 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2458 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2459 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2460 POSSIBILITY OF SUCH DAMAGE.
2462 Contact Warner Losh if you have any questions about your use of