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.
36 Commit 01ae8969a9ee fixed the NFSv4.1/4.2 server so that it
37 handles binding of the back channel as required by RFC5661.
38 Until this patch is in your server, avoid use of the "nconnects"
39 mount option for Linux NFSv4.1/4.2 mounts.
42 For 64-bit architectures the base system is now built with Position
43 Independent Executable (PIE) support enabled by default. It may be
44 disabled using the WITHOUT_PIE knob. A clean build is required.
47 Various LinuxKPI functionality was added which conflicts with DRM.
48 Please update your drm-kmod port to after the __FreeBSD_verison 1400003
52 PC Card attachments for all devices have been removed. In the case of
53 wi and cmx, the entire drivers were removed because they were only
54 PC Card devices. FreeBSD_version 1300134 should be used for this
55 since it was bumped so recently.
58 Transport-independent parts of HID support have been split off the USB
59 code in to separate subsystem. Kernel configs which include one of
60 ums, ukbd, uhid, atp, wsp, wmt, uaudio, ugold or ucycom drivers should
61 be updated with adding of "device hid" line.
64 ncurses installation has been modified to only keep the widechar
65 enabled version. Incremental build is broken for that change, so it
66 requires a clean build.
69 The FreeBSD project has migrated from Subversion to Git. Temporary
70 instructions can be found at
71 https://github.com/bsdimp/freebsd-git-docs/blob/main/src-cvt.md
72 and other documents in that repo.
75 The services database has been updated to cover more of the basic
76 services expected in a modern system. The database is big enough
77 that it will cause issues in mergemaster in Releases previous to
78 12.2 and 11.3, or in very old current systems from before r358154.
81 Obsolete in-tree GDB 6.1.1 has been removed. GDB (including kgdb)
82 may be installed from ports or packages.
85 ping6 has been merged into ping. It can now be called as "ping -6".
86 See ping(8) for details.
89 Default value of net.add_addr_allfibs has been changed to 0.
90 If you have multi-fib configuration and rely on existence of all
91 interface routes in every fib, you need to set the above sysctl to 1.
94 The internal pre-processor in the calendar(1) program has been
95 extended to support more C pre-processor commands (e.g. #ifdef, #else,
96 and #undef) and to detect unbalanced conditional statements.
97 Error messages have been extended to include the filename and line
98 number if processing stops to help fixing malformed data files.
101 All the data files for the calendar(1) program, except calendar.freebsd,
102 have been moved to the deskutils/calendar-data port, much like the
103 jewish calendar entries were moved to deskutils/hebcal years ago. After
104 make delete-old-files, you need to install it to retain full
105 functionality. calendar(1) will issue a reminder for files it can't
109 LINT files are no longer generated. We now include the relevant NOTES
110 files. Note: This may cause conflicts with updating in some cases.
111 find sys -name LINT\* -delete
112 is suggested across this commit to remove the generated LINT files.
114 If you have tried to update with generated files there, the svn
115 command you want to un-auger the tree is
118 and then do the above find from the top level. Substitute 'amd64'
119 above with where the error message indicates a conflict.
122 OpenZFS support has been integrated. Do not upgrade root pools until
123 the loader is updated to support zstd. Furthermore, we caution against
124 'zpool upgrade' for the next few weeks. The change should be transparent
125 unless you want to use new features.
127 Not all "NO_CLEAN" build scenarios work across these changes. Many
128 scenarios have been tested and fixed, but rebuilding kernels without
129 rebuilding world may fail.
131 The ZFS cache file has moved from /boot to /etc to match the OpenZFS
132 upstream default. A fallback to /boot has been added for mountroot.
134 Pool auto import behavior at boot has been moved from the kernel module
135 to an explicit "zpool import -a" in one of the rc scripts enabled by
136 zfs_enable=YES. This means your non-root zpools won't auto import until
137 you upgrade your /etc/rc.d files.
140 The resume code now notifies devd with the 'kernel' system
141 rather than the old 'kern' subsystem to be consistent with
142 other use. The old notification will be created as well, but
143 will be removed prior to FreeBSD 14.0.
146 r362275 changed the internal API between the kernel RPC and the
147 NFS modules. As such, all the modules must be recompiled from
151 r364330 modified the internal API used between the NFS modules.
152 As such, all the NFS modules must be re-compiled from sources.
155 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
156 been upgraded to 11.0.0. Please see the 20141231 entry below for
157 information about prerequisites and upgrading, if you are not already
158 using clang 3.5.0 or higher.
161 r364092 modified the internal ABI used between the kernel NFS
162 modules. As such, all of these modules need to be rebuilt
163 from sources, so a version bump was done.
166 Makefile.inc has been updated to work around the issue documented in
167 20200729. It was a case where the optimization of using symbolic links
168 to point to binaries created a situation where we'd run new binaries
169 with old libraries starting midway through the installworld process.
172 r363679 has redefined some undefined behavior in regcomp(3); notably,
173 extraneous escapes of most ordinary characters will no longer be
174 accepted. An exp-run has identified all of the problems with this in
175 ports, but other non-ports software may need extra escapes removed to
176 continue to function.
178 Because of this change, installworld may encounter the following error
179 from rtld: Undefined symbol "regcomp@FBSD_1.6" -- It is imperative that
180 you do not halt installworld. Instead, let it run to completion (whether
181 successful or not) and run installworld once more.
184 A new implementation of bc and dc has been imported in r362681. This
185 implementation corrects non-conformant behavior of the previous bc
186 and adds GNU bc compatible options. It offers a number of extensions,
187 is much faster on large values, and has support for message catalogs
188 (a number of languages are already supported, contributions of further
189 languages welcome). The option WITHOUT_GH_BC can be used to build the
190 world with the previous versions of bc and dc.
193 r362639 changed the internal API used between the NFS kernel modules.
194 As such, they all need to be rebuilt from sources.
197 r362158 changed the arguments for VFS_CHECKEXP(). As such, any
198 out of tree file systems need to be modified and rebuilt.
199 Also, any file systems that are modules must be rebuilt.
202 read(2) of a directory fd is now rejected by default. root may
203 re-enable it for system root only on non-ZFS filesystems with the
204 security.bsd.allow_read_dir sysctl(8) MIB if
205 security.bsd.suser_enabled=1.
207 It may be advised to setup aliases for grep to default to `-d skip` if
208 commonly non-recursively grepping a list that includes directories and
209 the potential for the resulting stderr output is not tolerable. Example
210 aliases are now installed, commented out, in /root/.cshrc and
214 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
215 been upgraded to 10.0.1. Please see the 20141231 entry below for
216 information about prerequisites and upgrading, if you are not already
217 using clang 3.5.0 or higher.
220 Support for obsolete compilers has been removed from the build system.
221 Clang 6 and GCC 6.4 are the minimum supported versions.
224 closefrom(2) has been moved under COMPAT12, and replaced in libc with a
225 stub that calls close_range(2). If using a custom kernel configuration,
226 you may want to ensure that the COMPAT_FREEBSD12 option is included, as
227 a slightly older -CURRENT userland and older FreeBSD userlands may not
228 be functional without closefrom(2).
231 Upstream DTS from Linux 5.6 was merged and they now have the SID
232 and THS (Secure ID controller and THermal Sensor) node present.
233 The DTB overlays have now been removed from the tree for the H3/H5 and
234 A64 SoCs and the aw_sid and aw_thermal driver have been updated to
235 deal with upstream DTS. If you are using those overlays you need to
236 remove them from loader.conf and update the DTBs on the FAT partition.
239 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
240 been upgraded to 10.0.0. Please see the 20141231 entry below for
241 information about prerequisites and upgrading, if you are not already
242 using clang 3.5.0 or higher.
245 The amd(8) automount daemon has been removed from the source tree.
246 As of FreeBSD 10.1 autofs(5) is the preferred tool for automounting.
247 amd is still available in the sysutils/am-utils port.
250 Removed brooktree driver (bktr.4) from the tree.
253 The WITH_GPL_DTC option has been removed. The BSD-licenced device tree
254 compiler in usr.bin/dtc is used on all architectures which use dtc, and
255 the GPL dtc is available (if needed) from the sysutils/dtc port.
258 The WITHOUT_LLVM_LIBUNWIND option has been removed. LLVM's libunwind
259 is used by all supported CPU architectures.
262 GCC 4.2.1 has been removed from the tree. The WITH_GCC,
263 WITH_GCC_BOOTSTRAP, and WITH_GNUCXX options are no longer available.
264 Users who wish to build FreeBSD with GCC must use the external toolchain
268 ncurses has been updated to a newer version (6.2-20200215). Given the ABI
269 has changed, users will have to rebuild all the ports that are linked to
273 The size of struct vnet and the magic cookie have changed.
274 Users need to recompile libkvm and all modules using VIMAGE
275 together with their new kernel.
278 Defining the long deprecated NO_CTF, NO_DEBUG_FILES, NO_INSTALLLIB,
279 NO_MAN, NO_PROFILE, and NO_WARNS variables is now an error. Update
280 your Makefiles and scripts to define MK_<var>=no instead as required.
282 One exception to this is that program or library Makefiles should
283 define MAN to empty rather than setting MK_MAN=no.
286 Clang/LLVM is now the default compiler and LLD the default
290 make universe no longer uses GCC 4.2.1 on any architectures.
291 Architectures not supported by in-tree Clang/LLVM require an
292 external toolchain package.
295 GCC 4.2.1 is now not built by default, as part of the GCC 4.2.1
296 retirement plan. Specifically, the GCC, GCC_BOOTSTRAP, and GNUCXX
297 options default to off for all supported CPU architectures. As a
298 short-term transition aid they may be enabled via WITH_* options.
299 GCC 4.2.1 is expected to be removed from the tree on 2020-03-31.
302 Support for armv5 has been disconnected and is being removed. The
303 machine combination MACHINE=arm MACHINE_ARCH=arm is no longer valid.
304 You must now use a MACHINE_ARCH of armv6 or armv7. The default
305 MACHINE_ARCH for MACHINE=arm is now armv7.
308 Clang/LLVM is now the default compiler for all powerpc architectures.
309 LLD is now the default linker for powerpc64. The change for powerpc64
310 also includes a change to the ELFv2 ABI, incompatible with the existing
314 Kernel-loadable random(4) modules are no longer unloadable.
317 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
318 been upgraded to 9.0.1. Please see the 20141231 entry below for
319 information about prerequisites and upgrading, if you are not already
320 using clang 3.5.0 or higher.
323 r355677 has modified the internal interface used between the
324 NFS modules in the kernel. As such, they must all be upgraded
325 simultaneously. I will do a version bump for this.
328 The root certificates of the Mozilla CA Certificate Store have been
329 imported into the base system and can be managed with the certctl(8)
330 utility. If you have installed the security/ca_root_nss port or package
331 with the ETCSYMLINK option (the default), be advised that there may be
332 differences between those included in the port and those included in
333 base due to differences in nss branch used as well as general update
334 frequency. Note also that certctl(8) cannot manage certs in the
335 format used by the security/ca_root_nss port.
338 The amd(8) automount daemon has been disabled by default, and will be
339 removed in the future. As of FreeBSD 10.1 the autofs(5) is available
343 The nctgpio and wbwd drivers have been moved to the superio bus.
344 If you have one of these drivers in a kernel configuration, then
345 you should add device superio to it. If you use one of these drivers
346 as a module and you compile a custom set of modules, then you should
347 add superio to the set.
350 KPIs for network drivers to access interface addresses have changed.
351 Users need to recompile NIC driver modules together with kernel.
354 The net.link.tap.user_open sysctl no longer prevents user opening of
355 already created /dev/tapNN devices. Access is still controlled by
356 node permissions, just like tun devices. The net.link.tap.user_open
357 sysctl is now used only to allow users to perform devfs cloning of
358 tap devices, and the subsequent open may not succeed if the user is not
359 in the appropriate group. This sysctl may be deprecated/removed
360 completely in the future.
363 mips, powerpc, and sparc64 are no longer built as part of
364 universe / tinderbox unless MAKE_OBSOLETE_GCC is defined. If
365 not defined, mips, powerpc, and sparc64 builds will look for
366 the xtoolchain binaries and if installed use them for universe
367 builds. As llvm 9.0 becomes vetted for these architectures, they
368 will be removed from the list.
371 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
372 been upgraded to 9.0.0. Please see the 20141231 entry below for
373 information about prerequisites and upgrading, if you are not already
374 using clang 3.5.0 or higher.
377 The hpt27xx, hptmv, hptnr, and hptrr drivers have been removed from
378 GENERIC. They are available as modules and can be loaded by adding
379 to /boot/loader.conf hpt27xx_load="YES", hptmv_load="YES",
380 hptnr_load="YES", or hptrr_load="YES", respectively.
383 ntpd no longer by default locks its pages in memory, allowing them
384 to be paged out by the kernel. Use rlimit memlock to restore
385 historic BSD behaviour. For example, add "rlimit memlock 32"
386 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
389 Several of ping6's options have been renamed for better consistency
390 with ping. If you use any of -ARWXaghmrtwx, you must update your
391 scripts. See ping6(8) for details.
394 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
395 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
396 been removed from mount_fusefs(8). You can safely remove them from
397 your scripts, because they had no effect.
399 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
400 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
401 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
402 sysctls have been removed. If you felt the need to set any of them to
403 a non-default value, please tell asomers@FreeBSD.org why.
406 Default permissions on the /var/account/acct file (and copies of it
407 rotated by periodic daily scripts) are changed from 0644 to 0640
408 because the file contains sensitive information that should not be
409 world-readable. If the /var/account directory must be created by
410 rc.d/accounting, the mode used is now 0750. Admins who use the
411 accounting feature are encouraged to change the mode of an existing
412 /var/account directory to 0750 or 0700.
415 Entropy collection and the /dev/random device are no longer optional
416 components. The "device random" option has been removed.
417 Implementations of distilling algorithms can still be made loadable
418 with "options RANDOM_LOADABLE" (e.g., random_fortuna.ko).
421 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
422 been upgraded to 8.0.1. Please see the 20141231 entry below for
423 information about prerequisites and upgrading, if you are not already
424 using clang 3.5.0 or higher.
427 A fix was applied to i386 kernel modules to avoid panics with
428 dpcpu or vnet. Users need to recompile i386 kernel modules
429 having pcpu or vnet sections or they will refuse to load.
432 User-wired pages now have their own counter,
433 vm.stats.vm.v_user_wire_count. The vm.max_wired sysctl was renamed
434 to vm.max_user_wired and changed from an unsigned int to an unsigned
435 long. bhyve VMs wired with the -S are now subject to the user
436 wiring limit; the vm.max_user_wired sysctl may need to be tuned to
437 avoid running into the limit.
440 The IPSEC option has been removed from GENERIC. Users requiring
441 ipsec(4) must now load the ipsec(4) kernel module.
444 The tap(4) driver has been folded into tun(4), and the module has been
445 renamed to tuntap. You should update any kld_list="if_tap" or
446 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
447 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
448 module instead, and "device tap" or "device tun" entries in kernel
449 config files to select the tuntap device instead.
452 The following knobs have been added related to tradeoffs between
453 safe use of the random device and availability in the absence of
456 kern.random.initial_seeding.bypass_before_seeding: tunable; set
457 non-zero to bypass the random device prior to seeding, or zero to
458 block random requests until the random device is initially seeded.
459 For now, set to 1 (unsafe) by default to restore pre-r346250 boot
460 availability properties.
462 kern.random.initial_seeding.read_random_bypassed_before_seeding:
463 read-only diagnostic sysctl that is set when bypass is enabled and
464 read_random(9) is bypassed, to enable programmatic handling of this
465 initial condition, if desired.
467 kern.random.initial_seeding.arc4random_bypassed_before_seeding:
468 Similar to the above, but for for arc4random(9) initial seeding.
470 kern.random.initial_seeding.disable_bypass_warnings: tunable; set
471 non-zero to disable warnings in dmesg when the same conditions are
472 met as for the diagnostic sysctls above. Defaults to zero, i.e.,
473 produce warnings in dmesg when the conditions are met.
476 The loadable random module KPI has changed; the random_infra_init()
477 routine now requires a 3rd function pointer for a bool (*)(void)
478 method that returns true if the random device is seeded (and
479 therefore unblocked).
482 r345895 reverts r320698. This implies that an nfsuserd(8) daemon
483 built from head sources between r320757 (July 6, 2017) and
484 r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
485 is added to the command line.
486 nfsuserd daemons built from head sources that are post-r338192 are
487 not affected and should continue to work.
490 The fuse(4) module has been renamed to fusefs(4) for consistency with
491 other filesystems. You should update any kld_load="fuse" entries in
492 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
493 "options FUSE" entries in kernel config files.
496 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
497 8.0.0. Please see the 20141231 entry below for information about
498 prerequisites and upgrading, if you are not already using clang 3.5.0
502 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
503 compiled into your custom kernel, add 'device xz' statement to the
507 drm and drm2 have been removed from the tree. Please see
508 https://wiki.freebsd.org/Graphics for the latest information on
509 migrating to the drm ports.
512 Iflib is no longer unconditionally compiled into the kernel. Drivers
513 using iflib and statically compiled into the kernel, now require
514 the 'device iflib' config option. For the same drivers loaded as
515 modules on kernels not having 'device iflib', the iflib.ko module
516 is loaded automatically.
519 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
520 options no longer exist since r343219 and r343427 respectively;
521 nothing uses them, so they should be just removed from custom
525 r342635 changes the way efibootmgr(8) works by requiring users to add
526 the -b (bootnum) parameter for commands where the bootnum was previously
527 specified with each option. For example 'efibootmgr -B 0001' is now
528 'efibootmgr -B -b 0001'.
531 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
532 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
533 servers that have vfs.nfsd.nfs_privport set will only allow mounts
534 from clients using a reserved port#. Since both the FreeBSD and Linux
535 NFSv4 clients use reserved port#s by default, this should not affect
539 The XLP config has been removed. We can't support 64-bit atomics in this
540 kernel because it is running in 32-bit mode. XLP users must transition
541 to running a 64-bit kernel (XLP64 or XLPN32).
543 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
544 the preferred emulator today and we don't need two different ones.
546 The old sibyte / swarm / Broadcom BCM1250 support has been
547 removed from the mips port.
550 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
551 7.0.1. Please see the 20141231 entry below for information about
552 prerequisites and upgrading, if you are not already using clang 3.5.0
556 Remove the timed and netdate programs from the base tree. Setting
557 the time with these daemons has been obsolete for over a decade.
560 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
561 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
562 it produces broken binaries when ifuncs are in use. Users needing
563 GNU ld should install the binutils port or package.
566 The BSD crtbegin and crtend code has been enabled by default. It has
567 had extensive testing on amd64, arm64, and i386. It can be disabled
568 by building a world with -DWITHOUT_BSD_CRTBEGIN.
571 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
572 has been converted to a port (misc/ctm) and will be removed from
573 FreeBSD-13. It is available as a package (ctm) for all supported
577 The default newsyslog.conf(5) file has been changed to only include
578 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
579 the filenames end in '.conf' and do not begin with a '.'.
581 You should check the configuration files in these two directories match
582 this naming convention. You can verify which configuration files are
583 being included using the command:
587 Ports for the DRM modules have been simplified. Now, amd64 users should
588 just install the drm-kmod port. All others should install
591 Graphics hardware that's newer than about 2010 usually works with
592 drm-kmod. For hardware older than 2013, however, some users will need
593 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
594 than 2008 usually only works in drm-legacy-kmod. The graphics team can
595 only commit to hardware made since 2013 due to the complexity of the
596 market and difficulty to test all the older cards effectively. If you
597 have hardware supported by drm-kmod, you are strongly encouraged to use
598 that as you will get better support.
600 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
601 elsewhere, the drm and drm2 modules will be eliminated from the src base
602 soon (with a limited exception for arm). Please update to the package
603 asap and report any issues to x11@freebsd.org.
605 Generally, anybody using the drm*-kmod packages should add
606 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
607 cross-threading surprises, especially with automatic driver
608 loading from X11 startup. These will become the defaults in 13-current
612 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
613 custom kernel and module loading configuration files must be updated
614 accordingly. Moreover, interfaces previous presented as ixlvN to the
615 system are now exposed as iavfN and network configuration files must
616 be adjusted as necessary.
619 OpenSSL has been updated to version 1.1.1. This update included
620 additional various API changes throughout the base system. It is
621 important to rebuild third-party software after upgrading. The value
622 of __FreeBSD_version has been bumped accordingly.
625 The legacy DRM modules and drivers have now been added to the loader's
626 module blacklist, in favor of loading them with kld_list in rc.conf(5).
627 The module blacklist may be overridden with the loader.conf(5)
628 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
632 The cam(4) based nda(4) driver will be used over nvd(4) by default on
633 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
634 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
635 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
639 Reproducible build mode is now on by default, in preparation for
640 FreeBSD 12.0. This eliminates build metadata such as the user,
641 host, and time from the kernel (and uname), unless the working tree
642 corresponds to a modified checkout from a version control system.
643 The previous behavior can be obtained by setting the /etc/src.conf
644 knob WITHOUT_REPRODUCIBLE_BUILD.
647 The Yarrow CSPRNG has been removed from the kernel as it has not been
648 supported by its designers since at least 2003. Fortuna has been the
649 default since FreeBSD-11.
652 devctl freeze/thaw have gone into the tree, the rc scripts have been
653 updated to use them and devmatch has been changed. You should update
654 kernel, userland and rc scripts all at the same time.
657 The default interpreter has been switched from 4th to Lua.
658 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
659 interpreter. If you have custom FORTH code you will need to set
660 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
661 src.conf for the build. This will create default hard links between
662 loader and loader_4th instead of loader and loader_lua, the new default.
663 If you are using UEFI it will create the proper hard link to loader.efi.
665 bhyve uses userboot.so. It remains 4th-only until some issues are solved
666 regarding coexisting with multiple versions of FreeBSD are resolved.
669 ls(1) now respects the COLORTERM environment variable used in other
670 systems and software to indicate that a colored terminal is both
671 supported and desired. If ls(1) is suddenly emitting colors, they may
672 be disabled again by either removing the unwanted COLORTERM from your
673 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
674 may not be observed in a future release.
677 The default pager for most commands has been changed to "less". To
678 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
682 The jedec_ts(4) driver has been removed. A superset of its functionality
683 is available in the jedec_dimm(4) driver, and the manpage for that
684 driver includes migration instructions. If you have "device jedec_ts"
685 in your kernel configuration file, it must be removed.
688 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
689 This should have no effect if the kernel is booted via BIOS/legacy boot.
690 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
691 has a buggy firmware that prevents a successful boot due to use of
695 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
696 support has been removed from the tree. These ports were
697 obsolete and/or known to be broken for many years.
700 loader.efi has been augmented to participate more fully in the
701 UEFI boot manager protocol. loader.efi will now look at the
702 BootXXXX environment variable to determine if a specific kernel
703 or root partition was specified. XXXX is derived from BootCurrent.
704 efibootmgr(8) manages these standard UEFI variables.
707 zfsloader's functionality has now been folded into loader.
708 zfsloader is no longer necessary once you've updated your
709 boot blocks. For a transition period, we will install a
710 hardlink for zfsloader to loader to allow a smooth transition
711 until the boot blocks can be updated (hard link because old
712 zfs boot blocks don't understand symlinks).
715 ARM64 now have efifb support, if you want to have serial console
716 on your arm64 board when an screen is connected and the bootloader
717 setup a frame buffer for us to use, just add :
721 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
722 an screen connected as the firmware will setup a frame buffer are that
723 u-boot will expose as an EFI frame buffer.
726 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
727 or take steps to update /etc/passwd before doing installworld on
728 existing systems. Do not skip the "mergemaster -Fp" step before
729 installworld, as described in the update procedures near the bottom
730 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
731 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
732 the ntp config file contain options that change file/dir locations.
733 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
734 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
735 taking steps to ensure that all required files/dirs are accessible
739 Big endian arm support has been removed.
742 The static environment setup in kernel configs is no longer mutually
743 exclusive with the loader(8) environment by default. In order to
744 restore the previous default behavior of disabling the loader(8)
745 environment if a static environment is present, you must specify
746 loader_env.disabled=1 in the static environment.
749 The ABI of syscalls used by management tools like sockstat and
750 netstat has been broken to allow 32-bit binaries to work on
751 64-bit kernels without modification. These programs will need
752 to match the kernel in order to function. External programs may
753 require minor modifications to accommodate a change of type in
754 structures from pointers to 64-bit virtual addresses.
757 On i386 and amd64 atomics are now inlined. Out of tree modules using
758 atomics will need to be rebuilt.
761 The '%I' format in the kern.corefile sysctl limits the number of
762 core files that a process can generate to the number stored in the
763 debug.ncores sysctl. The '%I' format is replaced by the single digit
764 index. Previously, if all indexes were taken the kernel would overwrite
765 only a core file with the highest index in a filename.
766 Currently the system will create a new core file if there is a free
767 index or if all slots are taken it will overwrite the oldest one.
770 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
771 6.0.1. Please see the 20141231 entry below for information about
772 prerequisites and upgrading, if you are not already using clang 3.5.0
776 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
777 needed to be changed to work with it. This change was made with r335763
778 and requires a mergemaster / etcupdate / etc to update the installed
782 r334930 changed the interface between the NFS modules, so they all
783 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
786 As of r334391 lld is the default amd64 system linker; it is installed
787 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
791 The kernel / userland interface for devinfo changed, so you'll
792 need a new kernel and userland as a pair for it to work (rebuilding
793 lib/libdevinfo is all that's required). devinfo and devmatch will
794 not work, but everything else will when there's a mismatch.
797 The on-disk format for hwpmc callchain records has changed to include
798 threadid corresponding to a given record. This changes the field offsets
799 and thus requires that libpmcstat be rebuilt before using a kernel
803 The vxge(4) driver has been removed. This driver was introduced into
804 HEAD one week before the Exar left the Ethernet market and is not
805 known to be used. If you have device vxge in your kernel config file
809 The amd64 kernel now requires a ld that supports ifunc to produce a
810 working kernel, either lld or a newer binutils. lld is built by default
811 on amd64, and the 'buildkernel' target uses it automatically. However,
812 it is not the default linker, so building the kernel the traditional
813 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
814 binutils port/package). lld will soon be default, and this requirement
817 NOTE: As of r334391 lld is the default system linker on amd64, and no
818 workaround is necessary.
821 The nxge(4) driver has been removed. This driver was for PCI-X 10g
822 cards made by s2io/Neterion. The company was acquired by Exar and
823 no longer sells or supports Ethernet products. If you have device
824 nxge in your kernel config file it must be removed.
827 The tz database (tzdb) has been updated to 2018e. This version more
828 correctly models time stamps in time zones with negative DST such as
829 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
830 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
831 time zone abbreviations and the tm_isdst flag.
834 The ixgb(4) driver has been removed. This driver was for an early and
835 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
836 quickly shifted to the long lived ixgbe family. If you have device
837 ixgb in your kernel config file it must be removed.
840 The lmc(4) driver has been removed. This was a WAN interface
841 card that was already reportedly rare in 2003, and had an ambiguous
842 license. If you have device lmc in your kernel config file it must
846 Support for Arcnet networks has been removed. If you have device
847 arcnet or device cm in your kernel config file they must be
851 Support for FDDI networks has been removed. If you have device
852 fddi or device fpa in your kernel config file they must be
856 In addition to supporting RFC 3164 formatted messages, the
857 syslogd(8) service is now capable of parsing RFC 5424 formatted
858 log messages. The main benefit of using RFC 5424 is that clients
859 may now send log messages with timestamps containing year numbers,
860 microseconds and time zone offsets.
862 Similarly, the syslog(3) C library function has been altered to
863 send RFC 5424 formatted messages to the local system logging
864 daemon. On systems using syslogd(8), this change should have no
865 negative impact, as long as syslogd(8) and the C library are
866 updated at the same time. On systems using a different system
867 logging daemon, it may be necessary to make configuration
868 adjustments, depending on the software used.
870 When using syslog-ng, add the 'syslog-protocol' flag to local
871 input sources to enable parsing of RFC 5424 formatted messages:
874 unix-dgram("/var/run/log" flags(syslog-protocol));
877 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
878 of the 'imuxsock' module to let messages be processed by the
879 regular RFC 3164/5424 parsing pipeline:
881 module(load="imuxsock" SysSock.UseSpecialParser="off")
883 Do note that these changes only affect communication between local
884 applications and syslogd(8). The format that syslogd(8) uses to
885 store messages on disk or forward messages to other systems
886 remains unchanged. syslogd(8) still uses RFC 3164 for these
887 purposes. Options to customize this behaviour will be added in the
888 future. Utilities that process log files stored in /var/log are
889 thus expected to continue to function as before.
891 __FreeBSD_version has been incremented to 1200061 to denote this
895 Support for token ring networks has been removed. If you
896 have "device token" in your kernel config you should remove
897 it. No device drivers supported token ring.
900 makefs was modified to be able to tag ISO9660 El Torito boot catalog
901 entries as EFI instead of overloading the i386 tag as done previously.
902 The amd64 mkisoimages.sh script used to build amd64 ISO images for
903 release was updated to use this. This may mean that makefs must be
904 updated before "make cdrom" can be run in the release directory. This
905 should be as simple as:
907 $ cd $SRCDIR/usr.sbin/makefs
908 $ make depend all install
911 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
912 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
913 Co-existence for the transition period will come shortly. Booting is a
914 complex environment and test coverage for Lua-enabled loaders has been
915 thin, so it would be prudent to assume it might not work and make
916 provisions for backup boot methods.
919 devmatch functionality has been turned on in devd. It will automatically
920 load drivers for unattached devices. This may cause unexpected drivers
921 to be loaded. Please report any problems to current@ and
925 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
926 6.0.0. Please see the 20141231 entry below for information about
927 prerequisites and upgrading, if you are not already using clang 3.5.0
931 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
932 This means it is used to link the kernel and userland libraries and
933 executables, but is not yet installed as /usr/bin/ld by default.
935 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
936 WITHOUT_LLD_BOOTSTRAP=yes
939 On i386, pmtimer has been removed. Its functionality has been folded
940 into apm. It was a no-op on ACPI in current for a while now (but was
941 still needed on i386 in FreeBSD 11 and earlier). Users may need to
942 remove it from kernel config files.
945 The use of RSS hash from the network card aka flowid has been
946 disabled by default for lagg(4) as it's currently incompatible with
947 the lacp and loadbalance protocols.
949 This can be re-enabled by setting the following in loader.conf:
950 net.link.lagg.default_use_flowid="1"
953 The SW_WATCHDOG option is no longer necessary to enable the
954 hardclock-based software watchdog if no hardware watchdog is
955 configured. As before, SW_WATCHDOG will cause the software
956 watchdog to be enabled even if a hardware watchdog is configured.
959 r326887 fixes the issue described in the 20171214 UPDATING entry.
960 r326888 flips the switch back to building GELI support always.
963 r362593 broke ZFS + GELI support for reasons unknown. However,
964 it also broke ZFS support generally, so GELI has been turned off
965 by default as the lesser evil in r326857. If you boot off ZFS and/or
966 GELI, it might not be a good time to update.
969 PowerPC users must update loader(8) by rebuilding world before
970 installing a new kernel, as the protocol connecting them has
971 changed. Without the update, loader metadata will not be passed
972 successfully to the kernel and users will have to enter their
973 root partition at the kernel mountroot prompt to continue booting.
974 Newer versions of loader can boot old kernels without issue.
977 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
978 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
979 to WITH/OUT_LOADER_GELI.
982 The naive and non-compliant support of posix_fallocate(2) in ZFS
983 has been removed as of r325320. The system call now returns EINVAL
984 when used on a ZFS file. Although the new behavior complies with the
985 standard, some consumers are not prepared to cope with it.
986 One known victim is lld prior to r325420.
989 Building in a FreeBSD src checkout will automatically create object
990 directories now rather than store files in the current directory if
991 'make obj' was not ran. Calling 'make obj' is no longer necessary.
992 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
993 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
997 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
998 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
999 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
1000 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
1001 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
1002 The UNIFIED_OBJDIR option is a transitional feature that will be
1003 removed for 12.0 release; please migrate to the new format for any
1004 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
1005 than hardcoding paths.
1008 The native-xtools target no longer installs the files by default to the
1009 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
1010 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
1013 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
1014 options are changing from controlling the build if defined / undefined
1015 to controlling the build with explicit 'yes' or 'no' values. They will
1016 shift to WITH/WITHOUT options to match other options in the system.
1019 libstand has turned into a private library for sys/boot use only.
1020 It is no longer supported as a public interface outside of sys/boot.
1023 The arm port has split armv6 into armv6 and armv7. armv7 is now
1024 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
1025 and are running a kernel from before r324363, you will need to add
1026 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
1029 When building multiple kernels using KERNCONF, non-existent KERNCONF
1030 files will produce an error and buildkernel will fail. Previously
1031 missing KERNCONF files silently failed giving no indication as to
1032 why, only to subsequently discover during installkernel that the
1033 desired kernel was never built in the first place.
1036 The default serial number format for CTL LUNs has changed. This will
1037 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
1038 or iSCSI clients care about their LUNs' serial numbers. Users who
1039 require serial number stability should hardcode serial numbers in
1043 For 32-bit arm compiled for hard-float support, soft-floating point
1044 binaries now always get their shared libraries from
1045 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
1046 /usr/libsoft also existed). Only users with a hard-float ld.so, but
1047 soft-float everything else should be affected.
1050 The geli password typed at boot is now hidden. To restore the previous
1051 behavior, see geli(8) for configuration options.
1054 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
1055 sysctl values. Minor nit, but requires a rebuild of both world/kernel
1059 "make check" behavior (made in ^/head@r295380) has been changed to
1060 execute from a limited sandbox, as opposed to executing from
1064 - The "beforecheck" and "aftercheck" targets are now specified.
1065 - ${CHECKDIR} (added in commit noted above) has been removed.
1066 - Legacy behavior can be enabled by setting
1067 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
1069 If the limited sandbox mode is enabled, "make check" will execute
1070 "make distribution", then install, execute the tests, and clean up the
1071 sandbox if successful.
1073 The "make distribution" and "make install" targets are typically run as
1074 root to set appropriate permissions and ownership at installation time.
1075 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
1076 environment if executing "make check" with limited sandbox mode using
1077 an unprivileged user.
1080 Since the switch to GPT disk labels, fsck for UFS/FFS has been
1081 unable to automatically find alternate superblocks. As of r322297,
1082 the information needed to find alternate superblocks has been
1083 moved to the end of the area reserved for the boot block.
1084 Filesystems created with a newfs of this vintage or later
1085 will create the recovery information. If you have a filesystem
1086 created prior to this change and wish to have a recovery block
1087 created for your filesystem, you can do so by running fsck in
1088 foreground mode (i.e., do not use the -p or -y options). As it
1089 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
1090 to which you should answer yes.
1093 As of r321665, an NFSv4 server configuration that services
1094 Kerberos mounts or clients that do not support the uid/gid in
1095 owner/owner_group string capability, must explicitly enable
1096 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
1097 machine's /etc/rc.conf file.
1100 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
1101 Please see the 20141231 entry below for information about prerequisites
1102 and upgrading, if you are not already using clang 3.5.0 or higher.
1105 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
1106 r-commands (rlogin, rsh, etc.) to be built with the base system.
1109 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
1110 a very major ABI incompatible change, so users of FreeBSD/powerpc must
1111 be careful when performing source upgrades. It is best to run
1112 'make installworld' from an alternate root system, either a live
1113 CD/memory stick, or a temporary root partition. Additionally, all ports
1114 must be recompiled. powerpc64 is largely unaffected, except in the case
1115 of 32-bit compatibility. All 32-bit binaries will be affected.
1118 Forward compatibility for the "ino64" project have been committed. This
1119 will allow most new binaries to run on older kernels in a limited
1120 fashion. This prevents many of the common foot-shooting actions in the
1121 upgrade as well as the limited ability to roll back the kernel across
1122 the ino64 upgrade. Complicated use cases may not work properly, though
1123 enough simpler ones work to allow recovery in most situations.
1126 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
1127 if you require the GPL compiler.
1130 The internal ABI used for communication between the NFS kernel modules
1131 was changed by r320085, so __FreeBSD_version was bumped to
1132 ensure all the NFS related modules are updated together.
1135 The ABI of struct event was changed by extending the data
1136 member to 64bit and adding ext fields. For upgrade, same
1137 precautions as for the entry 20170523 "ino64" must be
1141 The GNU roff toolchain has been removed from base. To render manpages
1142 which are not supported by mandoc(1), man(1) can fallback on GNU roff
1143 from ports (and recommends to install it).
1144 To render roff(7) documents, consider using GNU roff from ports or the
1145 heirloom doctools roff toolchain from ports via pkg install groff or
1146 via pkg install heirloom-doctools.
1149 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
1150 smaller runtime footprint builds. This is useful for embedded systems
1151 which only require one chipset support.
1153 If you load it as a module, make sure this is in /boot/loader.conf:
1157 This will load the HAL, all chip/RF backends and if_ath_pci.
1158 If you have if_ath_pci in /boot/loader.conf, ensure it is after
1159 if_ath or it will not load any HAL chipset support.
1161 If you want to selectively load things (eg on ye cheape ARM/MIPS
1162 platforms where RAM is at a premium) you should:
1165 * load the chip modules in question
1166 * load ath_rate, ath_dfs
1168 * load if_ath_pci and/or if_ath_ahb depending upon your particular
1169 bus bind type - this is where probe/attach is done.
1171 For further comments/feedback, poke adrian@ .
1174 The "ino64" 64-bit inode project has been committed, which extends
1175 a number of types to 64 bits. Upgrading in place requires care and
1176 adherence to the documented upgrade procedure.
1178 If using a custom kernel configuration ensure that the
1179 COMPAT_FREEBSD11 option is included (as during the upgrade the
1180 system will be running the ino64 kernel with the existing world).
1182 For the safest in-place upgrade begin by removing previous build
1183 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full
1184 procedure documented below under the heading "To rebuild everything and
1185 install it on the current system." Specifically, a reboot is required
1186 after installing the new kernel before installing world. While an
1187 installworld normally works by accident from multiuser after rebooting
1188 the proper kernel, there are many cases where this will fail across this
1189 upgrade and installworld from single user is required.
1192 The NATM framework including the en(4), fatm(4), hatm(4), and
1193 patm(4) devices has been removed. Consumers should plan a
1194 migration before the end-of-life date for FreeBSD 11.
1197 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
1198 diff has not been implemented, if those are needed a newer version of
1199 GNU diff is available via the diffutils package under the gdiff name.
1202 As of r316810 for ipfilter, keep frags is no longer assumed when
1203 keep state is specified in a rule. r316810 aligns ipfilter with
1204 documentation in man pages separating keep frags from keep state.
1205 This allows keep state to be specified without forcing keep frags
1206 and allows keep frags to be specified independently of keep state.
1207 To maintain previous behaviour, also specify keep frags with
1208 keep state (as documented in ipf.conf.5).
1211 arm64 builds now use the base system LLD 4.0.0 linker by default,
1212 instead of requiring that the aarch64-binutils port or package be
1213 installed. To continue using aarch64-binutils, set
1214 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
1217 The UDP optimization in entry 20160818 that added the sysctl
1218 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
1219 packets will no longer be treated as L3 broadcast packets.
1222 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
1223 use any explicitly assigned loopback address available in the jail
1224 instead of using the first assigned address of the jail.
1227 The ctl.ko module no longer implements the iSCSI target frontend:
1228 cfiscsi.ko does instead.
1230 If building cfiscsi.ko as a kernel module, the module can be loaded
1231 via one of the following methods:
1232 - `cfiscsi_load="YES"` in loader.conf(5).
1233 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
1234 - ctladm(8)/ctld(8), when compiled with iSCSI support
1235 (`WITH_ISCSI=yes` in src.conf(5))
1237 Please see cfiscsi(4) for more details.
1240 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
1241 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
1242 same source (previously, the dependency of mmcsd.ko on mmc.ko was
1243 missing, but mmcsd.ko now will refuse to load if it is incompatible
1247 The syntax of ipfw(8) named states was changed to avoid ambiguity.
1248 If you have used named states in the firewall rules, you need to modify
1249 them after installworld and before rebooting. Now named states must
1250 be prefixed with colon.
1253 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
1254 removed as the userland we provide cannot use them. The KMS version
1255 (sys/dev/drm2) supports the same hardware.
1258 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
1259 Please see the 20141231 entry below for information about prerequisites
1260 and upgrading, if you are not already using clang 3.5.0 or higher.
1263 The code that provides support for ZFS .zfs/ directory functionality
1264 has been reimplemented. It's not possible now to create a snapshot
1265 by mkdir under .zfs/snapshot/. That should be the only user visible
1269 EISA bus support has been removed. The WITH_EISA option is no longer
1273 MCA bus support has been removed.
1276 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
1277 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
1280 The EM_MULTIQUEUE kernel configuration option is deprecated now that
1281 the em(4) driver conforms to iflib specifications.
1284 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
1285 IFLIB. If you have a custom kernel configuration that excludes em(4)
1286 but you use igb(4), you need to re-add em(4) to your custom
1290 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
1291 Please see the 20141231 entry below for information about prerequisites
1292 and upgrading, if you are not already using clang 3.5.0 or higher.
1295 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
1296 Please see the 20141231 entry below for information about prerequisites
1297 and upgrading, if you are not already using clang 3.5.0 or higher.
1300 The layout of the pmap structure has changed for powerpc to put the pmap
1301 statistics at the front for all CPU variations. libkvm(3) and all tools
1302 that link against it need to be recompiled.
1305 isl(4) and cyapa(4) drivers now require a new driver,
1306 chromebook_platform(4), to work properly on Chromebook-class hardware.
1307 On other types of hardware the drivers may need to be configured using
1308 device hints. Please see the corresponding manual pages for details.
1311 The urtwn(4) driver was merged into rtwn(4) and now consists of
1312 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
1314 Also, firmware for RTL8188CE was renamed due to possible name
1315 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
1318 GNU rcs has been removed from base. It is available as packages:
1319 - rcs: Latest GPLv3 GNU rcs version.
1320 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
1324 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
1325 modules now requires that the kernel configuration contain the
1326 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
1329 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
1330 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
1333 Relocatable object files with the extension of .So have been renamed
1334 to use an extension of .pico instead. The purpose of this change is
1335 to avoid a name clash with shared libraries on case-insensitive file
1336 systems. On those file systems, foo.So is the same file as foo.so.
1339 GNU rcs has been turned off by default. It can (temporarily) be built
1340 again by adding WITH_RCS knob in src.conf.
1341 Otherwise, GNU rcs is available from packages:
1342 - rcs: Latest GPLv3 GNU rcs version.
1343 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
1346 The backup_uses_rcs functionality has been removed from rc.subr.
1349 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
1350 two separate components, QUEUE_MACRO_DEBUG_TRACE and
1351 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
1352 QUEUE_MACRO_DEBUG behavior.
1355 r304787 changed some ioctl interfaces between the iSCSI userspace
1356 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1357 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1361 The UDP receive code has been updated to only treat incoming UDP
1362 packets that were addressed to an L2 broadcast address as L3
1363 broadcast packets. It is not expected that this will affect any
1364 standards-conforming UDP application. The new behaviour can be
1365 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1369 Remove the openbsd_poll system call.
1370 __FreeBSD_version has been bumped because of this.
1373 The stable/11 branch has been created from head@r302406.
1376 The libc stub for the pipe(2) system call has been replaced with
1377 a wrapper that calls the pipe2(2) system call and the pipe(2)
1378 system call is now only implemented by the kernels that include
1379 "options COMPAT_FREEBSD10" in their config file (this is the
1380 default). Users should ensure that this option is enabled in
1381 their kernel or upgrade userspace to r302092 before upgrading their
1385 CAM will now strip leading spaces from SCSI disks' serial numbers.
1386 This will affect users who create UFS filesystems on SCSI disks using
1387 those disk's diskid device nodes. For example, if /etc/fstab
1388 previously contained a line like
1389 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
1390 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
1391 transforms like gmirror may also be affected. ZFS users should
1395 The bitstring(3) API has been updated with new functionality and
1396 improved performance. But it is binary-incompatible with the old API.
1397 Objects built with the new headers may not be linked against objects
1398 built with the old headers.
1401 The brk and sbrk functions have been removed from libc on arm64.
1402 Binutils from ports has been updated to not link to these
1403 functions and should be updated to the latest version before
1404 installing a new libc.
1407 The armv6 port now defaults to hard float ABI. Limited support
1408 for running both hardfloat and soft float on the same system
1409 is available using the libraries installed with -DWITH_LIBSOFT.
1410 This has only been tested as an upgrade path for installworld
1411 and packages may fail or need manual intervention to run. New
1412 packages will be needed.
1414 To update an existing self-hosted armv6hf system, you must add
1415 TARGET_ARCH=armv6 on the make command line for both the build
1416 and the install steps.
1419 Kernel modules compiled outside of a kernel build now default to
1420 installing to /boot/modules instead of /boot/kernel. Many kernel
1421 modules built this way (such as those in ports) already overrode
1422 KMODDIR explicitly to install into /boot/modules. However,
1423 manually building and installing a module from /sys/modules will
1424 now install to /boot/modules instead of /boot/kernel.
1427 The CAM I/O scheduler has been committed to the kernel. There should be
1428 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1429 list of known rogues that claim support for this but actually corrupt
1430 data is believed to be complete, be on the lookout for data
1431 corruption. The known rogue list is believed to be complete:
1433 o Crucial MX100, M550 drives with MU01 firmware.
1434 o Micron M510 and M550 drives with MU01 firmware.
1435 o Micron M500 prior to MU07 firmware
1436 o Samsung 830, 840, and 850 all firmwares
1437 o FCCT M500 all firmwares
1439 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1440 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1441 updated firmware. Black listed drives will work correctly because these
1442 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1443 this list is the same as found in Linux, it's believed there are no
1444 other rogues in the market place. All other models from the above
1447 To be safe, if you are at all concerned, you can quirk each of your
1448 drives to prevent NCQ from being sent by setting:
1449 kern.cam.ada.X.quirks="0x2"
1450 in loader.conf. If the drive requires the 4k sector quirk, set the
1451 quirks entry to 0x3.
1454 The FAST_DEPEND build option has been removed and its functionality is
1455 now the one true way. The old mkdep(1) style of 'make depend' has
1456 been removed. See 20160311 for further details.
1459 Resource range types have grown from unsigned long to uintmax_t. All
1460 drivers, and anything using libdevinfo, need to be recompiled.
1463 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1464 builds. It no longer runs mkdep(1) during 'make depend', and the
1465 'make depend' stage can safely be skipped now as it is auto ran
1466 when building 'make all' and will generate all SRCS and DPSRCS before
1467 building anything else. Dependencies are gathered at compile time with
1468 -MF flags kept in separate .depend files per object file. Users should
1469 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1470 stale .depend files.
1473 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1474 kernel modules. Therefore, if you load any kernel modules at boot time,
1475 please install the boot loaders after you install the kernel, but before
1479 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1480 make installkernel KERNCONF=YOUR_KERNEL_HERE
1481 make -C sys/boot install
1482 <reboot in single user>
1484 Then follow the usual steps, described in the General Notes section,
1488 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1489 see the 20141231 entry below for information about prerequisites and
1490 upgrading, if you are not already using clang 3.5.0 or higher.
1493 The AIO subsystem is now a standard part of the kernel. The
1494 VFS_AIO kernel option and aio.ko kernel module have been removed.
1495 Due to stability concerns, asynchronous I/O requests are only
1496 permitted on sockets and raw disks by default. To enable
1497 asynchronous I/O requests on all file types, set the
1498 vfs.aio.enable_unsafe sysctl to a non-zero value.
1501 The ELF object manipulation tool objcopy is now provided by the
1502 ELF Tool Chain project rather than by GNU binutils. It should be a
1503 drop-in replacement, with the addition of arm64 support. The
1504 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1505 to obtain the GNU version if necessary.
1508 Building ZFS pools on top of zvols is prohibited by default. That
1509 feature has never worked safely; it's always been prone to deadlocks.
1510 Using a zvol as the backing store for a VM guest's virtual disk will
1511 still work, even if the guest is using ZFS. Legacy behavior can be
1512 restored by setting vfs.zfs.vol.recursive=1.
1515 The NONE and HPN patches has been removed from OpenSSH. They are
1516 still available in the security/openssh-portable port.
1519 With the addition of ypldap(8), a new _ypldap user is now required
1520 during installworld. "mergemaster -p" can be used to add the user
1521 prior to installworld, as documented in the handbook.
1524 The tftp loader (pxeboot) now uses the option root-path directive. As a
1525 consequence it no longer looks for a pxeboot.4th file on the tftp
1526 server. Instead it uses the regular /boot infrastructure as with the
1530 The code to start recording plug and play data into the modules has
1531 been committed. While the old tools will properly build a new kernel,
1532 a number of warnings about "unknown metadata record 4" will be produced
1533 for an older kldxref. To avoid such warnings, make sure to rebuild
1534 the kernel toolchain (or world). Make sure that you have r292078 or
1535 later when trying to build 292077 or later before rebuilding.
1538 Debug data files are now built by default with 'make buildworld' and
1539 installed with 'make installworld'. This facilitates debugging but
1540 requires more disk space both during the build and for the installed
1541 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1545 r291527 changed the internal interface between the nfsd.ko and
1546 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1547 __FreeBSD_version has been bumped because of this.
1550 Add support for unicode collation strings leads to a change of
1551 order of files listed by ls(1) for example. To get back to the old
1552 behaviour, set LC_COLLATE environment variable to "C".
1554 Databases administrators will need to reindex their databases given
1555 collation results will be different.
1557 Due to a bug in install(1) it is recommended to remove the ancient
1558 locales before running make installworld.
1560 rm -rf /usr/share/locale/*
1563 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1564 libcrypto.so.7 or libssl.so.7 must be recompiled.
1567 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1568 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1569 should be replaced with isp_2400 and isp_2500 modules respectively.
1572 The build previously allowed using 'make -n' to not recurse into
1573 sub-directories while showing what commands would be executed, and
1574 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1575 and 'make -N' will not.
1578 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1579 and etcupdate will now use this file. A custom sendmail.cf is now
1580 updated via this mechanism rather than via installworld. If you had
1581 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1582 want to remove the exclusion or change it to "always install".
1583 /etc/mail/sendmail.cf is now managed the same way regardless of
1584 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1585 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1588 Compatibility shims for legacy ATA device names have been removed.
1589 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1590 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1591 environment variables, /dev/ad* and /dev/ar* symbolic links.
1594 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1595 Please see the 20141231 entry below for information about prerequisites
1596 and upgrading, if you are not already using clang 3.5.0 or higher.
1599 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1600 and renamed from .symbols to .debug. This reduces the size requirements
1601 on the boot partition or file system and provides consistency with
1602 userland debug files.
1604 When using the supported kernel installation method the
1605 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1606 as is done with /boot/kernel.
1608 Developers wishing to maintain the historical behavior of installing
1609 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1612 The wireless drivers had undergone changes that remove the 'parent
1613 interface' from the ifconfig -l output. The rc.d network scripts
1614 used to check presence of a parent interface in the list, so old
1615 scripts would fail to start wireless networking. Thus, etcupdate(3)
1616 or mergemaster(8) run is required after kernel update, to update your
1617 rc.d scripts in /etc.
1620 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1621 These configurations are now automatically interpreted as
1622 'scrub fragment reassemble'.
1625 Kernel-loadable modules for the random(4) device are back. To use
1626 them, the kernel must have
1629 options RANDOM_LOADABLE
1631 kldload(8) can then be used to load random_fortuna.ko
1632 or random_yarrow.ko. Please note that due to the indirect
1633 function calls that the loadable modules need to provide,
1634 the build-in variants will be slightly more efficient.
1636 The random(4) kernel option RANDOM_DUMMY has been retired due to
1637 unpopularity. It was not all that useful anyway.
1640 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1641 Control over building the ELF Tool Chain tools is now provided by
1642 the WITHOUT_TOOLCHAIN knob.
1645 The polarity of Pulse Per Second (PPS) capture events with the
1646 uart(4) driver has been corrected. Prior to this change the PPS
1647 "assert" event corresponded to the trailing edge of a positive PPS
1648 pulse and the "clear" event was the leading edge of the next pulse.
1650 As the width of a PPS pulse in a typical GPS receiver is on the
1651 order of 1 millisecond, most users will not notice any significant
1652 difference with this change.
1654 Anyone who has compensated for the historical polarity reversal by
1655 configuring a negative offset equal to the pulse width will need to
1656 remove that workaround.
1659 The default group assigned to /dev/dri entries has been changed
1660 from 'wheel' to 'video' with the id of '44'. If you want to have
1661 access to the dri devices please add yourself to the video group
1664 # pw groupmod video -m $USER
1667 The menu.rc and loader.rc files will now be replaced during
1668 upgrades. Please migrate local changes to menu.rc.local and
1669 loader.rc.local instead.
1672 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1673 strings and strip have been removed. The src.conf(5) knob
1674 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1677 As ZFS requires more kernel stack pages than is the default on some
1678 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1679 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1681 Please consider using 'options KSTACK_PAGES=X' where X is greater
1682 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1685 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1686 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1687 default, i.e., they will not contain "::". For example, instead
1688 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1689 to have a more specific match, such as different map entries for
1690 IPv6:0:0 vs IPv6:0. This change requires that configuration
1691 data (including maps, files, classes, custom ruleset, etc.) must
1692 use the same format, so make certain such configuration data is
1693 upgrading. As a very simple check search for patterns like
1694 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1695 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1696 the cf option UseCompressedIPv6Addresses.
1699 The default kernel entropy-processing algorithm is now
1700 Fortuna, replacing Yarrow.
1702 Assuming you have 'device random' in your kernel config
1703 file, the configurations allow a kernel option to override
1704 this default. You may choose *ONE* of:
1706 options RANDOM_YARROW # Legacy /dev/random algorithm.
1707 options RANDOM_DUMMY # Blocking-only driver.
1709 If you have neither, you get Fortuna. For most people,
1710 read no further, Fortuna will give a /dev/random that works
1711 like it always used to, and the difference will be irrelevant.
1713 If you remove 'device random', you get *NO* kernel-processed
1714 entropy at all. This may be acceptable to folks building
1715 embedded systems, but has complications. Carry on reading,
1716 and it is assumed you know what you need.
1718 *PLEASE* read random(4) and random(9) if you are in the
1719 habit of tweaking kernel configs, and/or if you are a member
1720 of the embedded community, wanting specific and not-usual
1721 behaviour from your security subsystems.
1723 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1724 random', you will NOT have a functioning /dev/random, and
1725 many cryptographic features will not work, including SSH.
1726 You may also find strange behaviour from the random(3) set
1727 of library functions, in particular sranddev(3), srandomdev(3)
1728 and arc4random(3). The reason for this is that the KERN_ARND
1729 sysctl only returns entropy if it thinks it has some to
1730 share, and with RANDOM_DUMMY or no 'device random' this
1734 An additional fix for the issue described in the 20150614 sendmail
1735 entry below has been committed in revision 284717.
1738 FreeBSD's old make (fmake) has been removed from the system. It is
1739 available as the devel/fmake port or via pkg install fmake.
1742 The fix for the issue described in the 20150614 sendmail entry
1743 below has been committed in revision 284436. The work
1744 around described in that entry is no longer needed unless the
1745 default setting is overridden by a confDH_PARAMETERS configuration
1746 setting of '5' or pointing to a 512 bit DH parameter file.
1749 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1750 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1751 and devel/kyua to version 0.20+ and adjust any calling code to work
1752 with Kyuafile and kyua.
1755 The import of openssl to address the FreeBSD-SA-15:10.openssl
1756 security advisory includes a change which rejects handshakes
1757 with DH parameters below 768 bits. sendmail releases prior
1758 to 8.15.2 (not yet released), defaulted to a 512 bit
1759 DH parameter setting for client connections. To work around
1760 this interoperability, sendmail can be configured to use a
1761 2048 bit DH parameter by:
1763 1. Edit /etc/mail/`hostname`.mc
1764 2. If a setting for confDH_PARAMETERS does not exist or
1765 exists and is set to a string beginning with '5',
1766 replace it with '2'.
1767 3. If a setting for confDH_PARAMETERS exists and is set to
1768 a file path, create a new file with:
1769 openssl dhparam -out /path/to/file 2048
1770 4. Rebuild the .cf file:
1771 cd /etc/mail/; make; make install
1772 5. Restart sendmail:
1773 cd /etc/mail/; make restart
1775 A sendmail patch is coming, at which time this file will be
1779 Generation of legacy formatted entries have been disabled by default
1780 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1781 entries were converted to use the new format by default when the new,
1782 machine independent format have been added and supported since FreeBSD
1785 Please see the pwd_mkdb(8) manual page for further details.
1788 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1789 20141231 entry below for information about prerequisites and upgrading,
1790 if you are not already using 3.5.0 or higher.
1793 TI platform code switched to using vendor DTS files and this update
1794 may break existing systems running on Beaglebone, Beaglebone Black,
1797 - dtb files should be regenerated/reinstalled. Filenames are the
1798 same but content is different now
1799 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1800 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1801 addressing scheme is now pin 25 on /dev/gpioc3.
1802 - Pandaboard: /etc/ttys should be updated, serial console device is
1803 now /dev/ttyu2, not /dev/ttyu0
1806 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1807 If you need the GNU extension from groff soelim(1), install groff
1808 from package: pkg install groff, or via ports: textproc/groff.
1811 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1812 defined in symlink(7); previously symlinks were silently ignored.
1815 The const qualifier has been removed from iconv(3) to comply with
1816 POSIX. The ports tree is aware of this from r384038 onwards.
1819 Libraries specified by LIBADD in Makefiles must have a corresponding
1820 DPADD_<lib> variable to ensure correct dependencies. This is now
1821 enforced in src.libnames.mk.
1824 From legacy ata(4) driver was removed support for SATA controllers
1825 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1826 Kernel modules ataahci and ataadaptec were removed completely,
1827 replaced by ahci and mvs modules respectively.
1830 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1831 the 20141231 entry below for information about prerequisites and
1832 upgrading, if you are not already using 3.5.0 or higher.
1835 The 32-bit PowerPC kernel has been changed to a position-independent
1836 executable. This can only be booted with a version of loader(8)
1837 newer than January 31, 2015, so make sure to update both world and
1838 kernel before rebooting.
1841 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1842 but before r278950, the RNG was not seeded properly. Immediately
1843 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1844 ssh keys or openssl keys) that were generated w/ a kernel from that
1845 range. This does not affect programs that directly used /dev/random
1846 or /dev/urandom. All userland uses of arc4random(3) are affected.
1849 The autofs(4) ABI was changed in order to restore binary compatibility
1850 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1851 with the new kernel.
1854 The powerpc64 kernel has been changed to a position-independent
1855 executable. This can only be booted with a new version of loader(8),
1856 so make sure to update both world and kernel before rebooting.
1859 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1860 only release, no new features have been added. Please see the 20141231
1861 entry below for information about prerequisites and upgrading, if you
1862 are not already using 3.5.0.
1865 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1866 taken from the ELF Tool Chain project rather than GNU binutils. They
1867 should be drop-in replacements, with the addition of arm64 support.
1868 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1869 binutils tools, if necessary. See 20150805 for updated information.
1872 The default Unbound configuration now enables remote control
1873 using a local socket. Users who have already enabled the
1874 local_unbound service should regenerate their configuration
1875 by running "service local_unbound setup" as root.
1878 The GNU texinfo and GNU info pages have been removed.
1879 To be able to view GNU info pages please install texinfo from ports.
1882 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1884 As of this release, a prerequisite for building clang, llvm and lldb is
1885 a C++11 capable compiler and C++11 standard library. This means that to
1886 be able to successfully build the cross-tools stage of buildworld, with
1887 clang as the bootstrap compiler, your system compiler or cross compiler
1888 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1889 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1892 On any standard FreeBSD 10.x or 11.x installation, where clang and
1893 libc++ are on by default (that is, on x86 or arm), this should work out
1896 On 9.x installations where clang is enabled by default, e.g. on x86 and
1897 powerpc, libc++ will not be enabled by default, so libc++ should be
1898 built (with clang) and installed first. If both clang and libc++ are
1899 missing, build clang first, then use it to build libc++.
1901 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1902 the instructions for 9.x above.
1904 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1905 default, and do not build clang.
1907 Many embedded systems are resource constrained, and will not be able to
1908 build clang in a reasonable time, or in some cases at all. In those
1909 cases, cross building bootable systems on amd64 is a workaround.
1911 This new version of clang introduces a number of new warnings, of which
1912 the following are most likely to appear:
1916 This warns in two cases, for both C and C++:
1917 * When the code is trying to take the absolute value of an unsigned
1918 quantity, which is effectively a no-op, and almost never what was
1919 intended. The code should be fixed, if at all possible. If you are
1920 sure that the unsigned quantity can be safely cast to signed, without
1921 loss of information or undefined behavior, you can add an explicit
1922 cast, or disable the warning.
1924 * When the code is trying to take an absolute value, but the called
1925 abs() variant is for the wrong type, which can lead to truncation.
1926 If you want to disable the warning instead of fixing the code, please
1927 make sure that truncation will not occur, or it might lead to unwanted
1930 -Wtautological-undefined-compare and
1931 -Wundefined-bool-conversion
1933 These warn when C++ code is trying to compare 'this' against NULL, while
1934 'this' should never be NULL in well-defined C++ code. However, there is
1935 some legacy (pre C++11) code out there, which actively abuses this
1936 feature, which was less strictly defined in previous C++ versions.
1938 Squid and openjdk do this, for example. The warning can be turned off
1939 for C++98 and earlier, but compiling the code in C++11 mode might result
1940 in unexpected behavior; for example, the parts of the program that are
1941 unreachable could be optimized away.
1944 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1945 kernel sources have been removed. The .h files remain, since some
1946 utilities include them. This will need to be fixed later.
1947 If "mount -t oldnfs ..." is attempted, it will fail.
1948 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1949 the utilities will report errors.
1952 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1953 directories to top level SUBDIR variable when their parent
1954 directory is included in LOCAL_DIRS. Users with build systems with
1955 such hierarchies and without SUBDIR entries in the parent
1956 directory Makefiles should add them or add the directories to
1960 faith(4) and faithd(8) have been removed from the base system. Faith
1961 has been obsolete for a very long time.
1964 vt(4), the new console driver, is enabled by default. It brings
1965 support for Unicode and double-width characters, as well as
1966 support for UEFI and integration with the KMS kernel video
1969 You may need to update your console settings in /etc/rc.conf,
1970 most probably the keymap. During boot, /etc/rc.d/syscons will
1971 indicate what you need to do.
1973 vt(4) still has issues and lacks some features compared to
1974 syscons(4). See the wiki for up-to-date information:
1975 https://wiki.freebsd.org/Newcons
1977 If you want to keep using syscons(4), you can do so by adding
1978 the following line to /boot/loader.conf:
1982 pjdfstest has been integrated into kyua as an opt-in test suite.
1983 Please see share/doc/pjdfstest/README for more details on how to
1987 gperf has been removed from the base system for architectures
1988 that use clang. Ports that require gperf will obtain it from the
1992 pjdfstest has been moved from tools/regression/pjdfstest to
1996 At svn r271982, The default linux compat kernel ABI has been adjusted
1997 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1998 update. If you wish to continue using the linux-f10 compat ports,
1999 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
2000 encouraged to update their linux-compat packages to linux-c6 during
2001 their next update cycle.
2004 The ofwfb driver, used to provide a graphics console on PowerPC when
2005 using vt(4), no longer allows mmap() of all physical memory. This
2006 will prevent Xorg on PowerPC with some ATI graphics cards from
2007 initializing properly unless x11-servers/xorg-server is updated to
2011 The xdev targets have been converted to using TARGET and
2012 TARGET_ARCH instead of XDEV and XDEV_ARCH.
2015 The default unbound configuration has been modified to address
2016 issues with reverse lookups on networks that use private
2017 address ranges. If you use the local_unbound service, run
2018 "service local_unbound setup" as root to regenerate your
2019 configuration, then "service local_unbound reload" to load the
2023 The GNU texinfo and GNU info pages are not built and installed
2024 anymore, WITH_INFO knob has been added to allow to built and install
2026 UPDATE: see 20150102 entry on texinfo's removal
2029 The GNU readline library is now an INTERNALLIB - that is, it is
2030 statically linked into consumers (GDB and variants) in the base
2031 system, and the shared library is no longer installed. The
2032 devel/readline port is available for third party software that
2036 The Itanium architecture (ia64) has been removed from the list of
2037 known architectures. This is the first step in the removal of the
2041 Commit r268115 has added NFSv4.1 server support, merged from
2042 projects/nfsv4.1-server. Since this includes changes to the
2043 internal interfaces between the NFS related modules, a full
2044 build of the kernel and modules will be necessary.
2045 __FreeBSD_version has been bumped.
2048 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
2049 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
2050 which differs from the behaviour controlled by this knob.)
2053 Maximal length of the serial number in CTL was increased from 16 to
2054 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
2055 and ctld, need to be rebuilt to work with a new kernel.
2058 The libatf-c and libatf-c++ major versions were downgraded to 0 and
2059 1 respectively to match the upstream numbers. They were out of
2060 sync because, when they were originally added to FreeBSD, the
2061 upstream versions were not respected. These libraries are private
2062 and not yet built by default, so renumbering them should be a
2063 non-issue. However, unclean source trees will yield broken test
2064 programs once the operator executes "make delete-old-libs" after a
2065 "make installworld".
2067 Additionally, the atf-sh binary was made private by moving it into
2068 /usr/libexec/. Already-built shell test programs will keep the
2069 path to the old binary so they will break after "make delete-old"
2072 If you are using WITH_TESTS=yes (not the default), wipe the object
2073 tree and rebuild from scratch to prevent spurious test failures.
2074 This is only needed once: the misnumbered libraries and misplaced
2075 binaries have been added to OptionalObsoleteFiles.inc so they will
2076 be removed during a clean upgrade.
2079 Clang and llvm have been upgraded to 3.4.1 release.
2082 We bogusly installed src.opts.mk in /usr/share/mk. This file should
2083 be removed to avoid issues in the future (and has been added to
2087 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
2088 past, it affected all builds that used the bsd.*.mk files. The old
2089 behavior was a bug, but people may have relied upon it. To get this
2090 behavior back, you can .include /etc/src.conf from /etc/make.conf
2091 (which is still global and isn't changed). This also changes the
2092 behavior of incremental builds inside the tree of individual
2093 directories. Set MAKESYSPATH to ".../share/mk" to do that.
2094 Although this has survived make universe and some upgrade scenarios,
2095 other upgrade scenarios may have broken. At least one form of
2096 temporary breakage was fixed with MAKESYSPATH settings for buildworld
2097 as well... In cases where MAKESYSPATH isn't working with this
2098 setting, you'll need to set it to the full path to your tree.
2100 One side effect of all this cleaning up is that bsd.compiler.mk
2101 is no longer implicitly included by bsd.own.mk. If you wish to
2102 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
2106 The lindev device has been removed since /dev/full has been made a
2107 standard device. __FreeBSD_version has been bumped.
2110 The knob WITHOUT_VI was added to the base system, which controls
2111 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
2112 in order to reorder files share/termcap and didn't build ex(1) as a
2113 build tool, so building/installing with WITH_VI is highly advised for
2114 build hosts for older releases.
2116 This issue has been fixed in stable/9 and stable/10 in r277022 and
2117 r276991, respectively.
2120 The YES_HESIOD knob has been removed. It has been obsolete for
2121 a decade. Please move to using WITH_HESIOD instead or your builds
2122 will silently lack HESIOD.
2125 The uart(4) driver has been changed with respect to its handling
2126 of the low-level console. Previously the uart(4) driver prevented
2127 any process from changing the baudrate or the CLOCAL and HUPCL
2128 control flags. By removing the restrictions, operators can make
2129 changes to the serial console port without having to reboot.
2130 However, when getty(8) is started on the serial device that is
2131 associated with the low-level console, a misconfigured terminal
2132 line in /etc/ttys will now have a real impact.
2133 Before upgrading the kernel, make sure that /etc/ttys has the
2134 serial console device configured as 3wire without baudrate to
2135 preserve the previous behaviour. E.g:
2136 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
2139 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
2140 to improve performance. To re-enable it, if needed, run rpcbind
2141 with command line option -W.
2144 Switched back to the GPL dtc compiler due to updates in the upstream
2145 dts files not being supported by the BSDL dtc compiler. You will need
2146 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
2147 may result while building dtb files during a kernel build if you fail
2148 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
2151 Clang and llvm have been upgraded to 3.4 release.
2154 The nve(4) driver has been removed. Please use the nfe(4) driver
2155 for NVIDIA nForce MCP Ethernet adapters instead.
2158 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
2159 This could cause certain C++ applications using shared libraries built
2160 against the previous version of libc++ to crash. The incompatibility
2161 has now been fixed, but any C++ applications or shared libraries built
2162 between r261283 and r261801 should be recompiled.
2165 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
2166 capability mode support. Please note that enabling the feature in
2167 kernel is still highly recommended.
2170 OpenSSH is now built with sandbox support, and will use sandbox as
2171 the default privilege separation method. This requires Capsicum
2172 capability mode support in kernel.
2175 The libelf and libdwarf libraries have been updated to newer
2176 versions from upstream. Shared library version numbers for
2177 these two libraries were bumped. Any ports or binaries
2178 requiring these two libraries should be recompiled.
2179 __FreeBSD_version is bumped to 1100006.
2182 If a Makefile in a tests/ directory was auto-generating a Kyuafile
2183 instead of providing an explicit one, this would prevent such
2184 Makefile from providing its own Kyuafile in the future during
2185 NO_CLEAN builds. This has been fixed in the Makefiles but manual
2186 intervention is needed to clean an objdir if you use NO_CLEAN:
2187 # find /usr/obj -name Kyuafile | xargs rm -f
2190 The behavior of gss_pseudo_random() for the krb5 mechanism
2191 has changed, for applications requesting a longer random string
2192 than produced by the underlying enctype's pseudo-random() function.
2193 In particular, the random string produced from a session key of
2194 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
2195 be different at the 17th octet and later, after this change.
2196 The counter used in the PRF+ construction is now encoded as a
2197 big-endian integer in accordance with RFC 4402.
2198 __FreeBSD_version is bumped to 1100004.
2201 The WITHOUT_ATF build knob has been removed and its functionality
2202 has been subsumed into the more generic WITHOUT_TESTS. If you were
2203 using the former to disable the build of the ATF libraries, you
2204 should change your settings to use the latter.
2207 The default version of mtree is nmtree which is obtained from
2208 NetBSD. The output is generally the same, but may vary
2209 slightly. If you found you need identical output adding
2210 "-F freebsd9" to the command line should do the trick. For the
2211 time being, the old mtree is available as fmtree.
2214 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
2215 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
2216 1.1.4_8 and verify bsdyml not linked in, before running "make
2218 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
2220 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
2223 The stable/10 branch has been created in subversion from head
2230 Sometimes, obscure build problems are the result of environment
2231 poisoning. This can happen because the make utility reads its
2232 environment when searching for values for global variables. To run
2233 your build attempts in an "environmental clean room", prefix all make
2234 commands with 'env -i '. See the env(1) manual page for more details.
2235 Occasionally a build failure will occur with "make -j" due to a race
2236 condition. If this happens try building again without -j, and please
2237 report a bug if it happens consistently.
2239 When upgrading from one major version to another it is generally best to
2240 upgrade to the latest code in the currently installed branch first, then
2241 do an upgrade to the new branch. This is the best-tested upgrade path,
2242 and has the highest probability of being successful. Please try this
2243 approach if you encounter problems with a major version upgrade. Since
2244 the stable 4.x branch point, one has generally been able to upgrade from
2245 anywhere in the most recent stable branch to head / current (or even the
2246 last couple of stable branches). See the top of this file when there's
2249 The update process will emit an error on an attempt to perform a build
2250 or install from a FreeBSD version below the earliest supported version.
2251 When updating from an older version the update should be performed one
2252 major release at a time, including running `make delete-old` at each
2255 When upgrading a live system, having a root shell around before
2256 installing anything can help undo problems. Not having a root shell
2257 around can lead to problems if pam has changed too much from your
2258 starting point to allow continued authentication after the upgrade.
2260 This file should be read as a log of events. When a later event changes
2261 information of a prior event, the prior event should not be deleted.
2262 Instead, a pointer to the entry with the new information should be
2263 placed in the old entry. Readers of this file should also sanity check
2264 older entries before relying on them blindly. Authors of new entries
2265 should write them with this in mind.
2269 When upgrading the boot ZFS pool to a new version, always follow
2272 1.) recompile and reinstall the ZFS boot loader and boot block
2273 (this is part of "make buildworld" and "make installworld")
2275 2.) update the ZFS boot block on your boot drive
2277 The following example updates the ZFS boot block on the
2278 freebsd-boot partition of a GPT partitioned drive ada0:
2279 "gpart bootcode -p /boot/gptzfsboot -i $N ada0"
2280 The value $N will typically be 1 (if booting from BIOS) or 2 (if
2283 Non-boot pools do not need these updates.
2287 If you are updating from a prior version of FreeBSD (even one just
2288 a few days old), you should follow this procedure. It is the most
2289 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2291 make kernel-toolchain
2292 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2293 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2295 To test a kernel once
2296 ---------------------
2297 If you just want to boot a kernel once (because you are not sure
2298 if it works, or if you want to boot a known bad kernel to provide
2299 debugging information) run
2300 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2301 nextboot -k testkernel
2303 To rebuild everything and install it on the current system.
2304 -----------------------------------------------------------
2305 # Note: sometimes if you are running current you gotta do more than
2306 # is listed here if you are upgrading from a really old current.
2308 <make sure you have good level 0 dumps>
2310 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2311 make installkernel KERNCONF=YOUR_KERNEL_HERE
2313 <reboot in single user> [3]
2320 To cross-install current onto a separate partition
2321 --------------------------------------------------
2322 # In this approach we use a separate partition to hold
2323 # current's root, 'usr', and 'var' directories. A partition
2324 # holding "/", "/usr" and "/var" should be about 2GB in
2327 <make sure you have good level 0 dumps>
2330 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2331 <maybe newfs current's root partition>
2332 <mount current's root partition on directory ${CURRENT_ROOT}>
2333 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
2334 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2335 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2336 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2337 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2338 <reboot into current>
2339 <do a "native" rebuild/install as described in the previous section>
2340 <maybe install compatibility libraries from ports/misc/compat*>
2344 To upgrade in-place from stable to current
2345 ----------------------------------------------
2346 <make sure you have good level 0 dumps>
2348 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
2349 make installkernel KERNCONF=YOUR_KERNEL_HERE
2351 <reboot in single user> [3]
2358 Make sure that you've read the UPDATING file to understand the
2359 tweaks to various things you need. At this point in the life
2360 cycle of current, things change often and you are on your own
2361 to cope. The defaults can also change, so please read ALL of
2362 the UPDATING entries.
2364 Also, if you are tracking -current, you must be subscribed to
2365 freebsd-current@freebsd.org. Make sure that before you update
2366 your sources that you have read and understood all the recent
2367 messages there. If in doubt, please track -stable which has
2368 much fewer pitfalls.
2370 [1] If you have third party modules, such as vmware, you should disable
2371 them at this point so they don't crash your system on
2372 reboot. Alternatively, you should rebuild all the modules you have in
2373 your system and install them as well. If you are running -current, you
2374 should seriously consider placing all sources to all the modules for
2375 your system (or symlinks to them) in /usr/local/sys/modules so this
2376 happens automatically. If all your modules come from ports, then adding
2377 the port origin directories to PORTS_MODULES instead is also automatic
2379 PORTS_MODULES+=x11/nvidia-driver
2381 [3] From the bootblocks, boot -s, and then do
2385 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed
2386 cd src # full path to source
2387 adjkerntz -i # if CMOS is wall time
2388 Also, when doing a major release upgrade, it is required that you boot
2389 into single user mode to do the installworld.
2391 [4] Note: This step is non-optional. Failure to do this step
2392 can result in a significant reduction in the functionality of the
2393 system. Attempting to do it by hand is not recommended and those
2394 that pursue this avenue should read this file carefully, as well
2395 as the archives of freebsd-current and freebsd-hackers mailing lists
2396 for potential gotchas. The -U option is also useful to consider.
2397 See mergemaster(8) for more information.
2399 [5] Usually this step is a no-op. However, from time to time
2400 you may need to do this if you get unknown user in the following
2401 step. It never hurts to do it all the time. You may need to
2402 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2403 install) after the buildworld before this step if you last updated
2404 from current before 20130425 or from -stable before 20130430.
2406 [6] This only deletes old files and directories. Old libraries
2407 can be deleted by "make delete-old-libs", but you have to make
2408 sure that no program is using those libraries anymore.
2410 [8] The new kernel must be able to run existing binaries used by an
2411 installworld. When upgrading across major versions, the new kernel's
2412 configuration must include the correct COMPAT_FREEBSD<n> option for
2413 existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure
2414 to do so may leave you with a system that is hard to boot to recover. A
2415 GENERIC kernel will include suitable compatibility options to run
2416 binaries from older branches. Note that the ability to run binaries
2417 from unsupported branches is not guaranteed.
2419 Make sure that you merge any new devices from GENERIC since the
2420 last time you updated your kernel config file. Options also
2421 change over time, so you may need to adjust your custom kernels
2424 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2425 "?=" instead of the "=" assignment operator, so that buildworld can
2426 override the CPUTYPE if it needs to.
2428 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2429 not on the command line, or in /etc/make.conf. buildworld will
2430 warn if it is improperly defined.
2433 This file contains a list, in reverse chronological order, of major
2434 breakages in tracking -current. It is not guaranteed to be a complete
2435 list of such breakages, and only contains entries since September 23, 2011.
2436 If you need to see UPDATING entries from before that date, you will need
2437 to fetch an UPDATING file from an older FreeBSD release.
2439 Copyright information:
2441 Copyright 1998-2009 M. Warner Losh <imp@FreeBSD.org>
2443 Redistribution, publication, translation and use, with or without
2444 modification, in full or in part, in any form or format of this
2445 document are permitted without further permission from the author.
2447 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2448 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2449 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2450 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2451 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2452 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2453 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2454 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2455 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2456 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2457 POSSIBILITY OF SUCH DAMAGE.
2459 Contact Warner Losh if you have any questions about your use of