1 Updating Information for FreeBSD current users.
3 This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>.
4 See end of file for further details. For commonly done items, please see the
5 COMMON ITEMS: section later in the file. These instructions assume that you
6 basically know what you are doing. If not, then please consult the FreeBSD
9 https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
11 Items affecting the ports and packages system can be found in
12 /usr/ports/UPDATING. Please read that file before running portupgrade.
14 NOTE TO PEOPLE WHO THINK THAT FreeBSD 13.x IS SLOW:
15 FreeBSD 13.x has many debugging features turned on, in both the kernel
16 and userland. These features attempt to detect incorrect use of
17 system primitives, and encourage loud failure through extra sanity
18 checking and fail stop semantics. They also substantially impact
19 system performance. If you want to do performance measurement,
20 benchmarking, and optimization, you'll want to turn them off. This
21 includes various WITNESS- related kernel options, INVARIANTS, malloc
22 debugging flags in userland, and various verbose features in the
23 kernel. Many developers choose to disable these features on build
24 machines to maximize performance. (To completely disable malloc
25 debugging, define WITH_MALLOC_PRODUCTION in /etc/src.conf and rebuild
26 world, or to merely disable the most expensive debugging functionality
27 at runtime, run "ln -s 'abort:false,junk:false' /etc/malloc.conf".)
30 All the data files for the calendar(1) program, except calendar.freebsd,
31 have been moved to the deskutils/calendar-data port, much like the
32 jewish calendar entries were moved to deskutils/hebcal years ago. After
33 make delete-old-files, you need to install it to retain full
34 functionality. calendar(1) will issue a reminder for files it can't
38 LINT files are no longer generated. We now include the relevant NOTES
39 files. Note: This may cause conflicts with updating in some cases.
40 find sys -name LINT\* -delete
41 is suggested across this commit to remove the generated LINT files.
43 If you have tried to update with generated files there, the svn
44 command you want to un-auger the tree is
47 and then do the above find from the top level. Substitute 'amd64'
48 above with where the error message indicates a conflict.
51 OpenZFS support has been integrated. Do not upgrade root pools until
52 the loader is updated to support zstd. Furthermore, we caution against
53 'zpool upgrade' for the next few weeks. The change should be transparent
54 unless you want to use new features.
56 Not all "NO_CLEAN" build scenarios work across these changes. Many
57 scenarios have been tested and fixed, but rebuilding kernels without
58 rebuilding world may fail.
60 The ZFS cache file has moved from /boot to /etc to match the OpenZFS
61 upstream default. A fallback to /boot has been added for mountroot.
63 Pool auto import behavior at boot has been moved from the kernel module
64 to an explicit "zpool import -a" in one of the rc scripts enabled by
65 zfs_enable=YES. This means your non-root zpools won't auto import until
66 you upgrade your /etc/rc.d files.
69 The resume code now notifies devd with the 'kernel' system
70 rather than the old 'kern' subsystem to be consistent with
71 other use. The old notification will be created as well, but
72 will be removed prior to FreeBSD 14.0.
75 r362275 changed the internal API between the kernel RPC and the
76 NFS modules. As such, all the modules must be recompiled from
80 r364330 modified the internal API used between the NFS modules.
81 As such, all the NFS modules must be re-compiled from sources.
84 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
85 been upgraded to 11.0.0. Please see the 20141231 entry below for
86 information about prerequisites and upgrading, if you are not already
87 using clang 3.5.0 or higher.
90 r364092 modified the internal ABI used between the kernel NFS
91 modules. As such, all of these modules need to be rebuilt
92 from sources, so a version bump was done.
95 Makefile.inc has been updated to work around the issue documented in
96 20200729. It was a case where the optimization of using symbolic links
97 to point to binaries created a situation where we'd run new binaries
98 with old libraries starting midway through the installworld process.
101 r363679 has redefined some undefined behavior in regcomp(3); notably,
102 extraneous escapes of most ordinary characters will no longer be
103 accepted. An exp-run has identified all of the problems with this in
104 ports, but other non-ports software may need extra escapes removed to
105 continue to function.
107 Because of this change, installworld may encounter the following error
108 from rtld: Undefined symbol "regcomp@FBSD_1.6" -- It is imperative that
109 you do not halt installworld. Instead, let it run to completion (whether
110 successful or not) and run installworld once more.
113 A new implementation of bc and dc has been imported in r362681. This
114 implementation corrects non-conformant behavior of the previous bc
115 and adds GNU bc compatible options. It offers a number of extensions,
116 is much faster on large values, and has support for message catalogs
117 (a number of languages are already supported, contributions of further
118 languages welcome). The option WITHOUT_GH_BC can be used to build the
119 world with the previous versions of bc and dc.
122 r362639 changed the internal API used between the NFS kernel modules.
123 As such, they all need to be rebuilt from sources.
126 r362158 changed the arguments for VFS_CHECKEXP(). As such, any
127 out of tree file systems need to be modified and rebuilt.
128 Also, any file systems that are modules must be rebuilt.
131 read(2) of a directory fd is now rejected by default. root may
132 re-enable it for system root only on non-ZFS filesystems with the
133 security.bsd.allow_read_dir sysctl(8) MIB if
134 security.bsd.suser_enabled=1.
136 It may be advised to setup aliases for grep to default to `-d skip` if
137 commonly non-recursively grepping a list that includes directories and
138 the potential for the resulting stderr output is not tolerable. Example
139 aliases are now installed, commented out, in /root/.cshrc and
143 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
144 been upgraded to 10.0.1. Please see the 20141231 entry below for
145 information about prerequisites and upgrading, if you are not already
146 using clang 3.5.0 or higher.
149 Support for obsolete compilers has been removed from the build system.
150 Clang 6 and GCC 6.4 are the minimum supported versions.
153 closefrom(2) has been moved under COMPAT12, and replaced in libc with a
154 stub that calls close_range(2). If using a custom kernel configuration,
155 you may want to ensure that the COMPAT_FREEBSD12 option is included, as
156 a slightly older -CURRENT userland and older FreeBSD userlands may not
157 be functional without closefrom(2).
160 Upstream DTS from Linux 5.6 was merged and they now have the SID
161 and THS (Secure ID controller and THermal Sensor) node present.
162 The DTB overlays have now been removed from the tree for the H3/H5 and
163 A64 SoCs and the aw_sid and aw_thermal driver have been updated to
164 deal with upstream DTS. If you are using those overlays you need to
165 remove them from loader.conf and update the DTBs on the FAT partition.
168 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
169 been upgraded to 10.0.0. Please see the 20141231 entry below for
170 information about prerequisites and upgrading, if you are not already
171 using clang 3.5.0 or higher.
174 The amd(8) automount daemon has been removed from the source tree.
175 As of FreeBSD 10.1 autofs(5) is the preferred tool for automounting.
176 amd is still available in the sysutils/am-utils port.
179 Removed brooktree driver (bktr.4) from the tree.
182 The WITH_GPL_DTC option has been removed. The BSD-licenced device tree
183 compiler in usr.bin/dtc is used on all architectures which use dtc, and
184 the GPL dtc is available (if needed) from the sysutils/dtc port.
187 The WITHOUT_LLVM_LIBUNWIND option has been removed. LLVM's libunwind
188 is used by all supported CPU architectures.
191 GCC 4.2.1 has been removed from the tree. The WITH_GCC,
192 WITH_GCC_BOOTSTRAP, and WITH_GNUCXX options are no longer available.
193 Users who wish to build FreeBSD with GCC must use the external toolchain
197 ncurses has been updated to a newer version (6.2-20200215). Given the ABI
198 has changed, users will have to rebuild all the ports that are linked to
202 The size of struct vnet and the magic cookie have changed.
203 Users need to recompile libkvm and all modules using VIMAGE
204 together with their new kernel.
207 Defining the long deprecated NO_CTF, NO_DEBUG_FILES, NO_INSTALLLIB,
208 NO_MAN, NO_PROFILE, and NO_WARNS variables is now an error. Update
209 your Makefiles and scripts to define MK_<var>=no instead as required.
211 One exception to this is that program or library Makefiles should
212 define MAN to empty rather than setting MK_MAN=no.
215 Clang/LLVM is now the default compiler and LLD the default
219 make universe no longer uses GCC 4.2.1 on any architectures.
220 Architectures not supported by in-tree Clang/LLVM require an
221 external toolchain package.
224 GCC 4.2.1 is now not built by default, as part of the GCC 4.2.1
225 retirement plan. Specifically, the GCC, GCC_BOOTSTRAP, and GNUCXX
226 options default to off for all supported CPU architectures. As a
227 short-term transition aid they may be enabled via WITH_* options.
228 GCC 4.2.1 is expected to be removed from the tree on 2020-03-31.
231 Support for armv5 has been disconnected and is being removed. The
232 machine combination MACHINE=arm MACHINE_ARCH=arm is no longer valid.
233 You must now use a MACHINE_ARCH of armv6 or armv7. The default
234 MACHINE_ARCH for MACHINE=arm is now armv7.
237 Clang/LLVM is now the default compiler for all powerpc architectures.
238 LLD is now the default linker for powerpc64. The change for powerpc64
239 also includes a change to the ELFv2 ABI, incompatible with the existing
243 Kernel-loadable random(4) modules are no longer unloadable.
246 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
247 been upgraded to 9.0.1. Please see the 20141231 entry below for
248 information about prerequisites and upgrading, if you are not already
249 using clang 3.5.0 or higher.
252 r355677 has modified the internal interface used between the
253 NFS modules in the kernel. As such, they must all be upgraded
254 simultaneously. I will do a version bump for this.
257 The root certificates of the Mozilla CA Certificate Store have been
258 imported into the base system and can be managed with the certctl(8)
259 utility. If you have installed the security/ca_root_nss port or package
260 with the ETCSYMLINK option (the default), be advised that there may be
261 differences between those included in the port and those included in
262 base due to differences in nss branch used as well as general update
263 frequency. Note also that certctl(8) cannot manage certs in the
264 format used by the security/ca_root_nss port.
267 The amd(8) automount daemon has been disabled by default, and will be
268 removed in the future. As of FreeBSD 10.1 the autofs(5) is available
272 The nctgpio and wbwd drivers have been moved to the superio bus.
273 If you have one of these drivers in a kernel configuration, then
274 you should add device superio to it. If you use one of these drivers
275 as a module and you compile a custom set of modules, then you should
276 add superio to the set.
279 KPIs for network drivers to access interface addresses have changed.
280 Users need to recompile NIC driver modules together with kernel.
283 The net.link.tap.user_open sysctl no longer prevents user opening of
284 already created /dev/tapNN devices. Access is still controlled by
285 node permissions, just like tun devices. The net.link.tap.user_open
286 sysctl is now used only to allow users to perform devfs cloning of
287 tap devices, and the subsequent open may not succeed if the user is not
288 in the appropriate group. This sysctl may be deprecated/removed
289 completely in the future.
292 mips, powerpc, and sparc64 are no longer built as part of
293 universe / tinderbox unless MAKE_OBSOLETE_GCC is defined. If
294 not defined, mips, powerpc, and sparc64 builds will look for
295 the xtoolchain binaries and if installed use them for universe
296 builds. As llvm 9.0 becomes vetted for these architectures, they
297 will be removed from the list.
300 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
301 been upgraded to 9.0.0. Please see the 20141231 entry below for
302 information about prerequisites and upgrading, if you are not already
303 using clang 3.5.0 or higher.
306 The hpt27xx, hptmv, hptnr, and hptrr drivers have been removed from
307 GENERIC. They are available as modules and can be loaded by adding
308 to /boot/loader.conf hpt27xx_load="YES", hptmv_load="YES",
309 hptnr_load="YES", or hptrr_load="YES", respectively.
312 ntpd no longer by default locks its pages in memory, allowing them
313 to be paged out by the kernel. Use rlimit memlock to restore
314 historic BSD behaviour. For example, add "rlimit memlock 32"
315 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
318 Several of ping6's options have been renamed for better consistency
319 with ping. If you use any of -ARWXaghmrtwx, you must update your
320 scripts. See ping6(8) for details.
323 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
324 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
325 been removed from mount_fusefs(8). You can safely remove them from
326 your scripts, because they had no effect.
328 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
329 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
330 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
331 sysctls have been removed. If you felt the need to set any of them to
332 a non-default value, please tell asomers@FreeBSD.org why.
335 Default permissions on the /var/account/acct file (and copies of it
336 rotated by periodic daily scripts) are changed from 0644 to 0640
337 because the file contains sensitive information that should not be
338 world-readable. If the /var/account directory must be created by
339 rc.d/accounting, the mode used is now 0750. Admins who use the
340 accounting feature are encouraged to change the mode of an existing
341 /var/account directory to 0750 or 0700.
344 Entropy collection and the /dev/random device are no longer optional
345 components. The "device random" option has been removed.
346 Implementations of distilling algorithms can still be made loadable
347 with "options RANDOM_LOADABLE" (e.g., random_fortuna.ko).
350 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
351 been upgraded to 8.0.1. Please see the 20141231 entry below for
352 information about prerequisites and upgrading, if you are not already
353 using clang 3.5.0 or higher.
356 A fix was applied to i386 kernel modules to avoid panics with
357 dpcpu or vnet. Users need to recompile i386 kernel modules
358 having pcpu or vnet sections or they will refuse to load.
361 User-wired pages now have their own counter,
362 vm.stats.vm.v_user_wire_count. The vm.max_wired sysctl was renamed
363 to vm.max_user_wired and changed from an unsigned int to an unsigned
364 long. bhyve VMs wired with the -S are now subject to the user
365 wiring limit; the vm.max_user_wired sysctl may need to be tuned to
366 avoid running into the limit.
369 The IPSEC option has been removed from GENERIC. Users requiring
370 ipsec(4) must now load the ipsec(4) kernel module.
373 The tap(4) driver has been folded into tun(4), and the module has been
374 renamed to tuntap. You should update any kld_list="if_tap" or
375 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
376 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
377 module instead, and "device tap" or "device tun" entries in kernel
378 config files to select the tuntap device instead.
381 The following knobs have been added related to tradeoffs between
382 safe use of the random device and availability in the absence of
385 kern.random.initial_seeding.bypass_before_seeding: tunable; set
386 non-zero to bypass the random device prior to seeding, or zero to
387 block random requests until the random device is initially seeded.
388 For now, set to 1 (unsafe) by default to restore pre-r346250 boot
389 availability properties.
391 kern.random.initial_seeding.read_random_bypassed_before_seeding:
392 read-only diagnostic sysctl that is set when bypass is enabled and
393 read_random(9) is bypassed, to enable programmatic handling of this
394 initial condition, if desired.
396 kern.random.initial_seeding.arc4random_bypassed_before_seeding:
397 Similar to the above, but for for arc4random(9) initial seeding.
399 kern.random.initial_seeding.disable_bypass_warnings: tunable; set
400 non-zero to disable warnings in dmesg when the same conditions are
401 met as for the diagnostic sysctls above. Defaults to zero, i.e.,
402 produce warnings in dmesg when the conditions are met.
405 The loadable random module KPI has changed; the random_infra_init()
406 routine now requires a 3rd function pointer for a bool (*)(void)
407 method that returns true if the random device is seeded (and
408 therefore unblocked).
411 r345895 reverts r320698. This implies that an nfsuserd(8) daemon
412 built from head sources between r320757 (July 6, 2017) and
413 r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
414 is added to the command line.
415 nfsuserd daemons built from head sources that are post-r338192 are
416 not affected and should continue to work.
419 The fuse(4) module has been renamed to fusefs(4) for consistency with
420 other filesystems. You should update any kld_load="fuse" entries in
421 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
422 "options FUSE" entries in kernel config files.
425 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
426 8.0.0. Please see the 20141231 entry below for information about
427 prerequisites and upgrading, if you are not already using clang 3.5.0
431 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
432 compiled into your custom kernel, add 'device xz' statement to the
436 drm and drm2 have been removed from the tree. Please see
437 https://wiki.freebsd.org/Graphics for the latest information on
438 migrating to the drm ports.
441 Iflib is no longer unconditionally compiled into the kernel. Drivers
442 using iflib and statically compiled into the kernel, now require
443 the 'device iflib' config option. For the same drivers loaded as
444 modules on kernels not having 'device iflib', the iflib.ko module
445 is loaded automatically.
448 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
449 options no longer exist since r343219 and r343427 respectively;
450 nothing uses them, so they should be just removed from custom
454 r342635 changes the way efibootmgr(8) works by requiring users to add
455 the -b (bootnum) parameter for commands where the bootnum was previously
456 specified with each option. For example 'efibootmgr -B 0001' is now
457 'efibootmgr -B -b 0001'.
460 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
461 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
462 servers that have vfs.nfsd.nfs_privport set will only allow mounts
463 from clients using a reserved port#. Since both the FreeBSD and Linux
464 NFSv4 clients use reserved port#s by default, this should not affect
468 The XLP config has been removed. We can't support 64-bit atomics in this
469 kernel because it is running in 32-bit mode. XLP users must transition
470 to running a 64-bit kernel (XLP64 or XLPN32).
472 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
473 the preferred emulator today and we don't need two different ones.
475 The old sibyte / swarm / Broadcom BCM1250 support has been
476 removed from the mips port.
479 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
480 7.0.1. Please see the 20141231 entry below for information about
481 prerequisites and upgrading, if you are not already using clang 3.5.0
485 Remove the timed and netdate programs from the base tree. Setting
486 the time with these daemons has been obsolete for over a decade.
489 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
490 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
491 it produces broken binaries when ifuncs are in use. Users needing
492 GNU ld should install the binutils port or package.
495 The BSD crtbegin and crtend code has been enabled by default. It has
496 had extensive testing on amd64, arm64, and i386. It can be disabled
497 by building a world with -DWITHOUT_BSD_CRTBEGIN.
500 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
501 has been converted to a port (misc/ctm) and will be removed from
502 FreeBSD-13. It is available as a package (ctm) for all supported
506 The default newsyslog.conf(5) file has been changed to only include
507 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
508 the filenames end in '.conf' and do not begin with a '.'.
510 You should check the configuration files in these two directories match
511 this naming convention. You can verify which configuration files are
512 being included using the command:
516 Ports for the DRM modules have been simplified. Now, amd64 users should
517 just install the drm-kmod port. All others should install
520 Graphics hardware that's newer than about 2010 usually works with
521 drm-kmod. For hardware older than 2013, however, some users will need
522 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
523 than 2008 usually only works in drm-legacy-kmod. The graphics team can
524 only commit to hardware made since 2013 due to the complexity of the
525 market and difficulty to test all the older cards effectively. If you
526 have hardware supported by drm-kmod, you are strongly encouraged to use
527 that as you will get better support.
529 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
530 elsewhere, the drm and drm2 modules will be eliminated from the src base
531 soon (with a limited exception for arm). Please update to the package
532 asap and report any issues to x11@freebsd.org.
534 Generally, anybody using the drm*-kmod packages should add
535 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
536 cross-threading surprises, especially with automatic driver
537 loading from X11 startup. These will become the defaults in 13-current
541 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
542 custom kernel and module loading configuration files must be updated
543 accordingly. Moreover, interfaces previous presented as ixlvN to the
544 system are now exposed as iavfN and network configuration files must
545 be adjusted as necessary.
548 OpenSSL has been updated to version 1.1.1. This update included
549 additional various API changes throughout the base system. It is
550 important to rebuild third-party software after upgrading. The value
551 of __FreeBSD_version has been bumped accordingly.
554 The legacy DRM modules and drivers have now been added to the loader's
555 module blacklist, in favor of loading them with kld_list in rc.conf(5).
556 The module blacklist may be overridden with the loader.conf(5)
557 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
561 The cam(4) based nda(4) driver will be used over nvd(4) by default on
562 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
563 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
564 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
568 Reproducible build mode is now on by default, in preparation for
569 FreeBSD 12.0. This eliminates build metadata such as the user,
570 host, and time from the kernel (and uname), unless the working tree
571 corresponds to a modified checkout from a version control system.
572 The previous behavior can be obtained by setting the /etc/src.conf
573 knob WITHOUT_REPRODUCIBLE_BUILD.
576 The Yarrow CSPRNG has been removed from the kernel as it has not been
577 supported by its designers since at least 2003. Fortuna has been the
578 default since FreeBSD-11.
581 devctl freeze/thaw have gone into the tree, the rc scripts have been
582 updated to use them and devmatch has been changed. You should update
583 kernel, userland and rc scripts all at the same time.
586 The default interpreter has been switched from 4th to Lua.
587 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
588 interpreter. If you have custom FORTH code you will need to set
589 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
590 src.conf for the build. This will create default hard links between
591 loader and loader_4th instead of loader and loader_lua, the new default.
592 If you are using UEFI it will create the proper hard link to loader.efi.
594 bhyve uses userboot.so. It remains 4th-only until some issues are solved
595 regarding coexisting with multiple versions of FreeBSD are resolved.
598 ls(1) now respects the COLORTERM environment variable used in other
599 systems and software to indicate that a colored terminal is both
600 supported and desired. If ls(1) is suddenly emitting colors, they may
601 be disabled again by either removing the unwanted COLORTERM from your
602 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
603 may not be observed in a future release.
606 The default pager for most commands has been changed to "less". To
607 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
611 The jedec_ts(4) driver has been removed. A superset of its functionality
612 is available in the jedec_dimm(4) driver, and the manpage for that
613 driver includes migration instructions. If you have "device jedec_ts"
614 in your kernel configuration file, it must be removed.
617 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
618 This should have no effect if the kernel is booted via BIOS/legacy boot.
619 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
620 has a buggy firmware that prevents a successful boot due to use of
624 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
625 support has been removed from the tree. These ports were
626 obsolete and/or known to be broken for many years.
629 loader.efi has been augmented to participate more fully in the
630 UEFI boot manager protocol. loader.efi will now look at the
631 BootXXXX environment variable to determine if a specific kernel
632 or root partition was specified. XXXX is derived from BootCurrent.
633 efibootmgr(8) manages these standard UEFI variables.
636 zfsloader's functionality has now been folded into loader.
637 zfsloader is no longer necessary once you've updated your
638 boot blocks. For a transition period, we will install a
639 hardlink for zfsloader to loader to allow a smooth transition
640 until the boot blocks can be updated (hard link because old
641 zfs boot blocks don't understand symlinks).
644 ARM64 now have efifb support, if you want to have serial console
645 on your arm64 board when an screen is connected and the bootloader
646 setup a frame buffer for us to use, just add :
650 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
651 an screen connected as the firmware will setup a frame buffer are that
652 u-boot will expose as an EFI frame buffer.
655 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
656 or take steps to update /etc/passwd before doing installworld on
657 existing systems. Do not skip the "mergemaster -Fp" step before
658 installworld, as described in the update procedures near the bottom
659 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
660 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
661 the ntp config file contain options that change file/dir locations.
662 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
663 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
664 taking steps to ensure that all required files/dirs are accessible
668 Big endian arm support has been removed.
671 The static environment setup in kernel configs is no longer mutually
672 exclusive with the loader(8) environment by default. In order to
673 restore the previous default behavior of disabling the loader(8)
674 environment if a static environment is present, you must specify
675 loader_env.disabled=1 in the static environment.
678 The ABI of syscalls used by management tools like sockstat and
679 netstat has been broken to allow 32-bit binaries to work on
680 64-bit kernels without modification. These programs will need
681 to match the kernel in order to function. External programs may
682 require minor modifications to accommodate a change of type in
683 structures from pointers to 64-bit virtual addresses.
686 On i386 and amd64 atomics are now inlined. Out of tree modules using
687 atomics will need to be rebuilt.
690 The '%I' format in the kern.corefile sysctl limits the number of
691 core files that a process can generate to the number stored in the
692 debug.ncores sysctl. The '%I' format is replaced by the single digit
693 index. Previously, if all indexes were taken the kernel would overwrite
694 only a core file with the highest index in a filename.
695 Currently the system will create a new core file if there is a free
696 index or if all slots are taken it will overwrite the oldest one.
699 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
700 6.0.1. Please see the 20141231 entry below for information about
701 prerequisites and upgrading, if you are not already using clang 3.5.0
705 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
706 needed to be changed to work with it. This change was made with r335763
707 and requires a mergemaster / etcupdate / etc to update the installed
711 r334930 changed the interface between the NFS modules, so they all
712 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
715 As of r334391 lld is the default amd64 system linker; it is installed
716 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
720 The kernel / userland interface for devinfo changed, so you'll
721 need a new kernel and userland as a pair for it to work (rebuilding
722 lib/libdevinfo is all that's required). devinfo and devmatch will
723 not work, but everything else will when there's a mismatch.
726 The on-disk format for hwpmc callchain records has changed to include
727 threadid corresponding to a given record. This changes the field offsets
728 and thus requires that libpmcstat be rebuilt before using a kernel
732 The vxge(4) driver has been removed. This driver was introduced into
733 HEAD one week before the Exar left the Ethernet market and is not
734 known to be used. If you have device vxge in your kernel config file
738 The amd64 kernel now requires a ld that supports ifunc to produce a
739 working kernel, either lld or a newer binutils. lld is built by default
740 on amd64, and the 'buildkernel' target uses it automatically. However,
741 it is not the default linker, so building the kernel the traditional
742 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
743 binutils port/package). lld will soon be default, and this requirement
746 NOTE: As of r334391 lld is the default system linker on amd64, and no
747 workaround is necessary.
750 The nxge(4) driver has been removed. This driver was for PCI-X 10g
751 cards made by s2io/Neterion. The company was acquired by Exar and
752 no longer sells or supports Ethernet products. If you have device
753 nxge in your kernel config file it must be removed.
756 The tz database (tzdb) has been updated to 2018e. This version more
757 correctly models time stamps in time zones with negative DST such as
758 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
759 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
760 time zone abbreviations and the tm_isdst flag.
763 The ixgb(4) driver has been removed. This driver was for an early and
764 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
765 quickly shifted to the long lived ixgbe family. If you have device
766 ixgb in your kernel config file it must be removed.
769 The lmc(4) driver has been removed. This was a WAN interface
770 card that was already reportedly rare in 2003, and had an ambiguous
771 license. If you have device lmc in your kernel config file it must
775 Support for Arcnet networks has been removed. If you have device
776 arcnet or device cm in your kernel config file they must be
780 Support for FDDI networks has been removed. If you have device
781 fddi or device fpa in your kernel config file they must be
785 In addition to supporting RFC 3164 formatted messages, the
786 syslogd(8) service is now capable of parsing RFC 5424 formatted
787 log messages. The main benefit of using RFC 5424 is that clients
788 may now send log messages with timestamps containing year numbers,
789 microseconds and time zone offsets.
791 Similarly, the syslog(3) C library function has been altered to
792 send RFC 5424 formatted messages to the local system logging
793 daemon. On systems using syslogd(8), this change should have no
794 negative impact, as long as syslogd(8) and the C library are
795 updated at the same time. On systems using a different system
796 logging daemon, it may be necessary to make configuration
797 adjustments, depending on the software used.
799 When using syslog-ng, add the 'syslog-protocol' flag to local
800 input sources to enable parsing of RFC 5424 formatted messages:
803 unix-dgram("/var/run/log" flags(syslog-protocol));
806 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
807 of the 'imuxsock' module to let messages be processed by the
808 regular RFC 3164/5424 parsing pipeline:
810 module(load="imuxsock" SysSock.UseSpecialParser="off")
812 Do note that these changes only affect communication between local
813 applications and syslogd(8). The format that syslogd(8) uses to
814 store messages on disk or forward messages to other systems
815 remains unchanged. syslogd(8) still uses RFC 3164 for these
816 purposes. Options to customize this behaviour will be added in the
817 future. Utilities that process log files stored in /var/log are
818 thus expected to continue to function as before.
820 __FreeBSD_version has been incremented to 1200061 to denote this
824 Support for token ring networks has been removed. If you
825 have "device token" in your kernel config you should remove
826 it. No device drivers supported token ring.
829 makefs was modified to be able to tag ISO9660 El Torito boot catalog
830 entries as EFI instead of overloading the i386 tag as done previously.
831 The amd64 mkisoimages.sh script used to build amd64 ISO images for
832 release was updated to use this. This may mean that makefs must be
833 updated before "make cdrom" can be run in the release directory. This
834 should be as simple as:
836 $ cd $SRCDIR/usr.sbin/makefs
837 $ make depend all install
840 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
841 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
842 Co-existence for the transition period will come shortly. Booting is a
843 complex environment and test coverage for Lua-enabled loaders has been
844 thin, so it would be prudent to assume it might not work and make
845 provisions for backup boot methods.
848 devmatch functionality has been turned on in devd. It will automatically
849 load drivers for unattached devices. This may cause unexpected drivers
850 to be loaded. Please report any problems to current@ and
854 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
855 6.0.0. Please see the 20141231 entry below for information about
856 prerequisites and upgrading, if you are not already using clang 3.5.0
860 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
861 This means it is used to link the kernel and userland libraries and
862 executables, but is not yet installed as /usr/bin/ld by default.
864 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
865 WITHOUT_LLD_BOOTSTRAP=yes
868 On i386, pmtimer has been removed. Its functionality has been folded
869 into apm. It was a no-op on ACPI in current for a while now (but was
870 still needed on i386 in FreeBSD 11 and earlier). Users may need to
871 remove it from kernel config files.
874 The use of RSS hash from the network card aka flowid has been
875 disabled by default for lagg(4) as it's currently incompatible with
876 the lacp and loadbalance protocols.
878 This can be re-enabled by setting the following in loader.conf:
879 net.link.lagg.default_use_flowid="1"
882 The SW_WATCHDOG option is no longer necessary to enable the
883 hardclock-based software watchdog if no hardware watchdog is
884 configured. As before, SW_WATCHDOG will cause the software
885 watchdog to be enabled even if a hardware watchdog is configured.
888 r326887 fixes the issue described in the 20171214 UPDATING entry.
889 r326888 flips the switch back to building GELI support always.
892 r362593 broke ZFS + GELI support for reasons unknown. However,
893 it also broke ZFS support generally, so GELI has been turned off
894 by default as the lesser evil in r326857. If you boot off ZFS and/or
895 GELI, it might not be a good time to update.
898 PowerPC users must update loader(8) by rebuilding world before
899 installing a new kernel, as the protocol connecting them has
900 changed. Without the update, loader metadata will not be passed
901 successfully to the kernel and users will have to enter their
902 root partition at the kernel mountroot prompt to continue booting.
903 Newer versions of loader can boot old kernels without issue.
906 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
907 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
908 to WITH/OUT_LOADER_GELI.
911 The naive and non-compliant support of posix_fallocate(2) in ZFS
912 has been removed as of r325320. The system call now returns EINVAL
913 when used on a ZFS file. Although the new behavior complies with the
914 standard, some consumers are not prepared to cope with it.
915 One known victim is lld prior to r325420.
918 Building in a FreeBSD src checkout will automatically create object
919 directories now rather than store files in the current directory if
920 'make obj' was not ran. Calling 'make obj' is no longer necessary.
921 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
922 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
926 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
927 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
928 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
929 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
930 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
931 The UNIFIED_OBJDIR option is a transitional feature that will be
932 removed for 12.0 release; please migrate to the new format for any
933 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
934 than hardcoding paths.
937 The native-xtools target no longer installs the files by default to the
938 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
939 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
942 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
943 options are changing from controlling the build if defined / undefined
944 to controlling the build with explicit 'yes' or 'no' values. They will
945 shift to WITH/WITHOUT options to match other options in the system.
948 libstand has turned into a private library for sys/boot use only.
949 It is no longer supported as a public interface outside of sys/boot.
952 The arm port has split armv6 into armv6 and armv7. armv7 is now
953 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
954 and are running a kernel from before r324363, you will need to add
955 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
958 When building multiple kernels using KERNCONF, non-existent KERNCONF
959 files will produce an error and buildkernel will fail. Previously
960 missing KERNCONF files silently failed giving no indication as to
961 why, only to subsequently discover during installkernel that the
962 desired kernel was never built in the first place.
965 The default serial number format for CTL LUNs has changed. This will
966 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
967 or iSCSI clients care about their LUNs' serial numbers. Users who
968 require serial number stability should hardcode serial numbers in
972 For 32-bit arm compiled for hard-float support, soft-floating point
973 binaries now always get their shared libraries from
974 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
975 /usr/libsoft also existed). Only users with a hard-float ld.so, but
976 soft-float everything else should be affected.
979 The geli password typed at boot is now hidden. To restore the previous
980 behavior, see geli(8) for configuration options.
983 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
984 sysctl values. Minor nit, but requires a rebuild of both world/kernel
988 "make check" behavior (made in ^/head@r295380) has been changed to
989 execute from a limited sandbox, as opposed to executing from
993 - The "beforecheck" and "aftercheck" targets are now specified.
994 - ${CHECKDIR} (added in commit noted above) has been removed.
995 - Legacy behavior can be enabled by setting
996 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
998 If the limited sandbox mode is enabled, "make check" will execute
999 "make distribution", then install, execute the tests, and clean up the
1000 sandbox if successful.
1002 The "make distribution" and "make install" targets are typically run as
1003 root to set appropriate permissions and ownership at installation time.
1004 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
1005 environment if executing "make check" with limited sandbox mode using
1006 an unprivileged user.
1009 Since the switch to GPT disk labels, fsck for UFS/FFS has been
1010 unable to automatically find alternate superblocks. As of r322297,
1011 the information needed to find alternate superblocks has been
1012 moved to the end of the area reserved for the boot block.
1013 Filesystems created with a newfs of this vintage or later
1014 will create the recovery information. If you have a filesystem
1015 created prior to this change and wish to have a recovery block
1016 created for your filesystem, you can do so by running fsck in
1017 foreground mode (i.e., do not use the -p or -y options). As it
1018 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
1019 to which you should answer yes.
1022 As of r321665, an NFSv4 server configuration that services
1023 Kerberos mounts or clients that do not support the uid/gid in
1024 owner/owner_group string capability, must explicitly enable
1025 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
1026 machine's /etc/rc.conf file.
1029 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
1030 Please see the 20141231 entry below for information about prerequisites
1031 and upgrading, if you are not already using clang 3.5.0 or higher.
1034 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
1035 r-commands (rlogin, rsh, etc.) to be built with the base system.
1038 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
1039 a very major ABI incompatible change, so users of FreeBSD/powerpc must
1040 be careful when performing source upgrades. It is best to run
1041 'make installworld' from an alternate root system, either a live
1042 CD/memory stick, or a temporary root partition. Additionally, all ports
1043 must be recompiled. powerpc64 is largely unaffected, except in the case
1044 of 32-bit compatibility. All 32-bit binaries will be affected.
1047 Forward compatibility for the "ino64" project have been committed. This
1048 will allow most new binaries to run on older kernels in a limited
1049 fashion. This prevents many of the common foot-shooting actions in the
1050 upgrade as well as the limited ability to roll back the kernel across
1051 the ino64 upgrade. Complicated use cases may not work properly, though
1052 enough simpler ones work to allow recovery in most situations.
1055 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
1056 if you require the GPL compiler.
1059 The internal ABI used for communication between the NFS kernel modules
1060 was changed by r320085, so __FreeBSD_version was bumped to
1061 ensure all the NFS related modules are updated together.
1064 The ABI of struct event was changed by extending the data
1065 member to 64bit and adding ext fields. For upgrade, same
1066 precautions as for the entry 20170523 "ino64" must be
1070 The GNU roff toolchain has been removed from base. To render manpages
1071 which are not supported by mandoc(1), man(1) can fallback on GNU roff
1072 from ports (and recommends to install it).
1073 To render roff(7) documents, consider using GNU roff from ports or the
1074 heirloom doctools roff toolchain from ports via pkg install groff or
1075 via pkg install heirloom-doctools.
1078 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
1079 smaller runtime footprint builds. This is useful for embedded systems
1080 which only require one chipset support.
1082 If you load it as a module, make sure this is in /boot/loader.conf:
1086 This will load the HAL, all chip/RF backends and if_ath_pci.
1087 If you have if_ath_pci in /boot/loader.conf, ensure it is after
1088 if_ath or it will not load any HAL chipset support.
1090 If you want to selectively load things (eg on ye cheape ARM/MIPS
1091 platforms where RAM is at a premium) you should:
1094 * load the chip modules in question
1095 * load ath_rate, ath_dfs
1097 * load if_ath_pci and/or if_ath_ahb depending upon your particular
1098 bus bind type - this is where probe/attach is done.
1100 For further comments/feedback, poke adrian@ .
1103 The "ino64" 64-bit inode project has been committed, which extends
1104 a number of types to 64 bits. Upgrading in place requires care and
1105 adherence to the documented upgrade procedure.
1107 If using a custom kernel configuration ensure that the
1108 COMPAT_FREEBSD11 option is included (as during the upgrade the
1109 system will be running the ino64 kernel with the existing world).
1111 For the safest in-place upgrade begin by removing previous build
1112 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full
1113 procedure documented below under the heading "To rebuild everything and
1114 install it on the current system." Specifically, a reboot is required
1115 after installing the new kernel before installing world. While an
1116 installworld normally works by accident from multiuser after rebooting
1117 the proper kernel, there are many cases where this will fail across this
1118 upgrade and installworld from single user is required.
1121 The NATM framework including the en(4), fatm(4), hatm(4), and
1122 patm(4) devices has been removed. Consumers should plan a
1123 migration before the end-of-life date for FreeBSD 11.
1126 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
1127 diff has not been implemented, if those are needed a newer version of
1128 GNU diff is available via the diffutils package under the gdiff name.
1131 As of r316810 for ipfilter, keep frags is no longer assumed when
1132 keep state is specified in a rule. r316810 aligns ipfilter with
1133 documentation in man pages separating keep frags from keep state.
1134 This allows keep state to be specified without forcing keep frags
1135 and allows keep frags to be specified independently of keep state.
1136 To maintain previous behaviour, also specify keep frags with
1137 keep state (as documented in ipf.conf.5).
1140 arm64 builds now use the base system LLD 4.0.0 linker by default,
1141 instead of requiring that the aarch64-binutils port or package be
1142 installed. To continue using aarch64-binutils, set
1143 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
1146 The UDP optimization in entry 20160818 that added the sysctl
1147 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
1148 packets will no longer be treated as L3 broadcast packets.
1151 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
1152 use any explicitly assigned loopback address available in the jail
1153 instead of using the first assigned address of the jail.
1156 The ctl.ko module no longer implements the iSCSI target frontend:
1157 cfiscsi.ko does instead.
1159 If building cfiscsi.ko as a kernel module, the module can be loaded
1160 via one of the following methods:
1161 - `cfiscsi_load="YES"` in loader.conf(5).
1162 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
1163 - ctladm(8)/ctld(8), when compiled with iSCSI support
1164 (`WITH_ISCSI=yes` in src.conf(5))
1166 Please see cfiscsi(4) for more details.
1169 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
1170 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
1171 same source (previously, the dependency of mmcsd.ko on mmc.ko was
1172 missing, but mmcsd.ko now will refuse to load if it is incompatible
1176 The syntax of ipfw(8) named states was changed to avoid ambiguity.
1177 If you have used named states in the firewall rules, you need to modify
1178 them after installworld and before rebooting. Now named states must
1179 be prefixed with colon.
1182 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
1183 removed as the userland we provide cannot use them. The KMS version
1184 (sys/dev/drm2) supports the same hardware.
1187 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
1188 Please see the 20141231 entry below for information about prerequisites
1189 and upgrading, if you are not already using clang 3.5.0 or higher.
1192 The code that provides support for ZFS .zfs/ directory functionality
1193 has been reimplemented. It's not possible now to create a snapshot
1194 by mkdir under .zfs/snapshot/. That should be the only user visible
1198 EISA bus support has been removed. The WITH_EISA option is no longer
1202 MCA bus support has been removed.
1205 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
1206 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
1209 The EM_MULTIQUEUE kernel configuration option is deprecated now that
1210 the em(4) driver conforms to iflib specifications.
1213 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
1214 IFLIB. If you have a custom kernel configuration that excludes em(4)
1215 but you use igb(4), you need to re-add em(4) to your custom
1219 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
1220 Please see the 20141231 entry below for information about prerequisites
1221 and upgrading, if you are not already using clang 3.5.0 or higher.
1224 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
1225 Please see the 20141231 entry below for information about prerequisites
1226 and upgrading, if you are not already using clang 3.5.0 or higher.
1229 The layout of the pmap structure has changed for powerpc to put the pmap
1230 statistics at the front for all CPU variations. libkvm(3) and all tools
1231 that link against it need to be recompiled.
1234 isl(4) and cyapa(4) drivers now require a new driver,
1235 chromebook_platform(4), to work properly on Chromebook-class hardware.
1236 On other types of hardware the drivers may need to be configured using
1237 device hints. Please see the corresponding manual pages for details.
1240 The urtwn(4) driver was merged into rtwn(4) and now consists of
1241 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
1243 Also, firmware for RTL8188CE was renamed due to possible name
1244 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
1247 GNU rcs has been removed from base. It is available as packages:
1248 - rcs: Latest GPLv3 GNU rcs version.
1249 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
1253 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
1254 modules now requires that the kernel configuration contain the
1255 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
1258 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
1259 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
1262 Relocatable object files with the extension of .So have been renamed
1263 to use an extension of .pico instead. The purpose of this change is
1264 to avoid a name clash with shared libraries on case-insensitive file
1265 systems. On those file systems, foo.So is the same file as foo.so.
1268 GNU rcs has been turned off by default. It can (temporarily) be built
1269 again by adding WITH_RCS knob in src.conf.
1270 Otherwise, GNU rcs is available from packages:
1271 - rcs: Latest GPLv3 GNU rcs version.
1272 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
1275 The backup_uses_rcs functionality has been removed from rc.subr.
1278 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
1279 two separate components, QUEUE_MACRO_DEBUG_TRACE and
1280 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
1281 QUEUE_MACRO_DEBUG behavior.
1284 r304787 changed some ioctl interfaces between the iSCSI userspace
1285 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1286 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1290 The UDP receive code has been updated to only treat incoming UDP
1291 packets that were addressed to an L2 broadcast address as L3
1292 broadcast packets. It is not expected that this will affect any
1293 standards-conforming UDP application. The new behaviour can be
1294 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1298 Remove the openbsd_poll system call.
1299 __FreeBSD_version has been bumped because of this.
1302 The stable/11 branch has been created from head@r302406.
1305 The libc stub for the pipe(2) system call has been replaced with
1306 a wrapper that calls the pipe2(2) system call and the pipe(2)
1307 system call is now only implemented by the kernels that include
1308 "options COMPAT_FREEBSD10" in their config file (this is the
1309 default). Users should ensure that this option is enabled in
1310 their kernel or upgrade userspace to r302092 before upgrading their
1314 CAM will now strip leading spaces from SCSI disks' serial numbers.
1315 This will affect users who create UFS filesystems on SCSI disks using
1316 those disk's diskid device nodes. For example, if /etc/fstab
1317 previously contained a line like
1318 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
1319 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
1320 transforms like gmirror may also be affected. ZFS users should
1324 The bitstring(3) API has been updated with new functionality and
1325 improved performance. But it is binary-incompatible with the old API.
1326 Objects built with the new headers may not be linked against objects
1327 built with the old headers.
1330 The brk and sbrk functions have been removed from libc on arm64.
1331 Binutils from ports has been updated to not link to these
1332 functions and should be updated to the latest version before
1333 installing a new libc.
1336 The armv6 port now defaults to hard float ABI. Limited support
1337 for running both hardfloat and soft float on the same system
1338 is available using the libraries installed with -DWITH_LIBSOFT.
1339 This has only been tested as an upgrade path for installworld
1340 and packages may fail or need manual intervention to run. New
1341 packages will be needed.
1343 To update an existing self-hosted armv6hf system, you must add
1344 TARGET_ARCH=armv6 on the make command line for both the build
1345 and the install steps.
1348 Kernel modules compiled outside of a kernel build now default to
1349 installing to /boot/modules instead of /boot/kernel. Many kernel
1350 modules built this way (such as those in ports) already overrode
1351 KMODDIR explicitly to install into /boot/modules. However,
1352 manually building and installing a module from /sys/modules will
1353 now install to /boot/modules instead of /boot/kernel.
1356 The CAM I/O scheduler has been committed to the kernel. There should be
1357 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1358 list of known rogues that claim support for this but actually corrupt
1359 data is believed to be complete, be on the lookout for data
1360 corruption. The known rogue list is believed to be complete:
1362 o Crucial MX100, M550 drives with MU01 firmware.
1363 o Micron M510 and M550 drives with MU01 firmware.
1364 o Micron M500 prior to MU07 firmware
1365 o Samsung 830, 840, and 850 all firmwares
1366 o FCCT M500 all firmwares
1368 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1369 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1370 updated firmware. Black listed drives will work correctly because these
1371 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1372 this list is the same as found in Linux, it's believed there are no
1373 other rogues in the market place. All other models from the above
1376 To be safe, if you are at all concerned, you can quirk each of your
1377 drives to prevent NCQ from being sent by setting:
1378 kern.cam.ada.X.quirks="0x2"
1379 in loader.conf. If the drive requires the 4k sector quirk, set the
1380 quirks entry to 0x3.
1383 The FAST_DEPEND build option has been removed and its functionality is
1384 now the one true way. The old mkdep(1) style of 'make depend' has
1385 been removed. See 20160311 for further details.
1388 Resource range types have grown from unsigned long to uintmax_t. All
1389 drivers, and anything using libdevinfo, need to be recompiled.
1392 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1393 builds. It no longer runs mkdep(1) during 'make depend', and the
1394 'make depend' stage can safely be skipped now as it is auto ran
1395 when building 'make all' and will generate all SRCS and DPSRCS before
1396 building anything else. Dependencies are gathered at compile time with
1397 -MF flags kept in separate .depend files per object file. Users should
1398 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1399 stale .depend files.
1402 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1403 kernel modules. Therefore, if you load any kernel modules at boot time,
1404 please install the boot loaders after you install the kernel, but before
1408 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1409 make installkernel KERNCONF=YOUR_KERNEL_HERE
1410 make -C sys/boot install
1411 <reboot in single user>
1413 Then follow the usual steps, described in the General Notes section,
1417 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1418 see the 20141231 entry below for information about prerequisites and
1419 upgrading, if you are not already using clang 3.5.0 or higher.
1422 The AIO subsystem is now a standard part of the kernel. The
1423 VFS_AIO kernel option and aio.ko kernel module have been removed.
1424 Due to stability concerns, asynchronous I/O requests are only
1425 permitted on sockets and raw disks by default. To enable
1426 asynchronous I/O requests on all file types, set the
1427 vfs.aio.enable_unsafe sysctl to a non-zero value.
1430 The ELF object manipulation tool objcopy is now provided by the
1431 ELF Tool Chain project rather than by GNU binutils. It should be a
1432 drop-in replacement, with the addition of arm64 support. The
1433 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1434 to obtain the GNU version if necessary.
1437 Building ZFS pools on top of zvols is prohibited by default. That
1438 feature has never worked safely; it's always been prone to deadlocks.
1439 Using a zvol as the backing store for a VM guest's virtual disk will
1440 still work, even if the guest is using ZFS. Legacy behavior can be
1441 restored by setting vfs.zfs.vol.recursive=1.
1444 The NONE and HPN patches has been removed from OpenSSH. They are
1445 still available in the security/openssh-portable port.
1448 With the addition of ypldap(8), a new _ypldap user is now required
1449 during installworld. "mergemaster -p" can be used to add the user
1450 prior to installworld, as documented in the handbook.
1453 The tftp loader (pxeboot) now uses the option root-path directive. As a
1454 consequence it no longer looks for a pxeboot.4th file on the tftp
1455 server. Instead it uses the regular /boot infrastructure as with the
1459 The code to start recording plug and play data into the modules has
1460 been committed. While the old tools will properly build a new kernel,
1461 a number of warnings about "unknown metadata record 4" will be produced
1462 for an older kldxref. To avoid such warnings, make sure to rebuild
1463 the kernel toolchain (or world). Make sure that you have r292078 or
1464 later when trying to build 292077 or later before rebuilding.
1467 Debug data files are now built by default with 'make buildworld' and
1468 installed with 'make installworld'. This facilitates debugging but
1469 requires more disk space both during the build and for the installed
1470 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1474 r291527 changed the internal interface between the nfsd.ko and
1475 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1476 __FreeBSD_version has been bumped because of this.
1479 Add support for unicode collation strings leads to a change of
1480 order of files listed by ls(1) for example. To get back to the old
1481 behaviour, set LC_COLLATE environment variable to "C".
1483 Databases administrators will need to reindex their databases given
1484 collation results will be different.
1486 Due to a bug in install(1) it is recommended to remove the ancient
1487 locales before running make installworld.
1489 rm -rf /usr/share/locale/*
1492 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1493 libcrypto.so.7 or libssl.so.7 must be recompiled.
1496 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1497 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1498 should be replaced with isp_2400 and isp_2500 modules respectively.
1501 The build previously allowed using 'make -n' to not recurse into
1502 sub-directories while showing what commands would be executed, and
1503 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1504 and 'make -N' will not.
1507 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1508 and etcupdate will now use this file. A custom sendmail.cf is now
1509 updated via this mechanism rather than via installworld. If you had
1510 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1511 want to remove the exclusion or change it to "always install".
1512 /etc/mail/sendmail.cf is now managed the same way regardless of
1513 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1514 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1517 Compatibility shims for legacy ATA device names have been removed.
1518 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1519 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1520 environment variables, /dev/ad* and /dev/ar* symbolic links.
1523 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1524 Please see the 20141231 entry below for information about prerequisites
1525 and upgrading, if you are not already using clang 3.5.0 or higher.
1528 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1529 and renamed from .symbols to .debug. This reduces the size requirements
1530 on the boot partition or file system and provides consistency with
1531 userland debug files.
1533 When using the supported kernel installation method the
1534 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1535 as is done with /boot/kernel.
1537 Developers wishing to maintain the historical behavior of installing
1538 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1541 The wireless drivers had undergone changes that remove the 'parent
1542 interface' from the ifconfig -l output. The rc.d network scripts
1543 used to check presence of a parent interface in the list, so old
1544 scripts would fail to start wireless networking. Thus, etcupdate(3)
1545 or mergemaster(8) run is required after kernel update, to update your
1546 rc.d scripts in /etc.
1549 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1550 These configurations are now automatically interpreted as
1551 'scrub fragment reassemble'.
1554 Kernel-loadable modules for the random(4) device are back. To use
1555 them, the kernel must have
1558 options RANDOM_LOADABLE
1560 kldload(8) can then be used to load random_fortuna.ko
1561 or random_yarrow.ko. Please note that due to the indirect
1562 function calls that the loadable modules need to provide,
1563 the build-in variants will be slightly more efficient.
1565 The random(4) kernel option RANDOM_DUMMY has been retired due to
1566 unpopularity. It was not all that useful anyway.
1569 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1570 Control over building the ELF Tool Chain tools is now provided by
1571 the WITHOUT_TOOLCHAIN knob.
1574 The polarity of Pulse Per Second (PPS) capture events with the
1575 uart(4) driver has been corrected. Prior to this change the PPS
1576 "assert" event corresponded to the trailing edge of a positive PPS
1577 pulse and the "clear" event was the leading edge of the next pulse.
1579 As the width of a PPS pulse in a typical GPS receiver is on the
1580 order of 1 millisecond, most users will not notice any significant
1581 difference with this change.
1583 Anyone who has compensated for the historical polarity reversal by
1584 configuring a negative offset equal to the pulse width will need to
1585 remove that workaround.
1588 The default group assigned to /dev/dri entries has been changed
1589 from 'wheel' to 'video' with the id of '44'. If you want to have
1590 access to the dri devices please add yourself to the video group
1593 # pw groupmod video -m $USER
1596 The menu.rc and loader.rc files will now be replaced during
1597 upgrades. Please migrate local changes to menu.rc.local and
1598 loader.rc.local instead.
1601 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1602 strings and strip have been removed. The src.conf(5) knob
1603 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1606 As ZFS requires more kernel stack pages than is the default on some
1607 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1608 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1610 Please consider using 'options KSTACK_PAGES=X' where X is greater
1611 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1614 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1615 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1616 default, i.e., they will not contain "::". For example, instead
1617 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1618 to have a more specific match, such as different map entries for
1619 IPv6:0:0 vs IPv6:0. This change requires that configuration
1620 data (including maps, files, classes, custom ruleset, etc.) must
1621 use the same format, so make certain such configuration data is
1622 upgrading. As a very simple check search for patterns like
1623 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1624 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1625 the cf option UseCompressedIPv6Addresses.
1628 The default kernel entropy-processing algorithm is now
1629 Fortuna, replacing Yarrow.
1631 Assuming you have 'device random' in your kernel config
1632 file, the configurations allow a kernel option to override
1633 this default. You may choose *ONE* of:
1635 options RANDOM_YARROW # Legacy /dev/random algorithm.
1636 options RANDOM_DUMMY # Blocking-only driver.
1638 If you have neither, you get Fortuna. For most people,
1639 read no further, Fortuna will give a /dev/random that works
1640 like it always used to, and the difference will be irrelevant.
1642 If you remove 'device random', you get *NO* kernel-processed
1643 entropy at all. This may be acceptable to folks building
1644 embedded systems, but has complications. Carry on reading,
1645 and it is assumed you know what you need.
1647 *PLEASE* read random(4) and random(9) if you are in the
1648 habit of tweaking kernel configs, and/or if you are a member
1649 of the embedded community, wanting specific and not-usual
1650 behaviour from your security subsystems.
1652 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1653 random', you will NOT have a functioning /dev/random, and
1654 many cryptographic features will not work, including SSH.
1655 You may also find strange behaviour from the random(3) set
1656 of library functions, in particular sranddev(3), srandomdev(3)
1657 and arc4random(3). The reason for this is that the KERN_ARND
1658 sysctl only returns entropy if it thinks it has some to
1659 share, and with RANDOM_DUMMY or no 'device random' this
1663 An additional fix for the issue described in the 20150614 sendmail
1664 entry below has been committed in revision 284717.
1667 FreeBSD's old make (fmake) has been removed from the system. It is
1668 available as the devel/fmake port or via pkg install fmake.
1671 The fix for the issue described in the 20150614 sendmail entry
1672 below has been committed in revision 284436. The work
1673 around described in that entry is no longer needed unless the
1674 default setting is overridden by a confDH_PARAMETERS configuration
1675 setting of '5' or pointing to a 512 bit DH parameter file.
1678 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1679 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1680 and devel/kyua to version 0.20+ and adjust any calling code to work
1681 with Kyuafile and kyua.
1684 The import of openssl to address the FreeBSD-SA-15:10.openssl
1685 security advisory includes a change which rejects handshakes
1686 with DH parameters below 768 bits. sendmail releases prior
1687 to 8.15.2 (not yet released), defaulted to a 512 bit
1688 DH parameter setting for client connections. To work around
1689 this interoperability, sendmail can be configured to use a
1690 2048 bit DH parameter by:
1692 1. Edit /etc/mail/`hostname`.mc
1693 2. If a setting for confDH_PARAMETERS does not exist or
1694 exists and is set to a string beginning with '5',
1695 replace it with '2'.
1696 3. If a setting for confDH_PARAMETERS exists and is set to
1697 a file path, create a new file with:
1698 openssl dhparam -out /path/to/file 2048
1699 4. Rebuild the .cf file:
1700 cd /etc/mail/; make; make install
1701 5. Restart sendmail:
1702 cd /etc/mail/; make restart
1704 A sendmail patch is coming, at which time this file will be
1708 Generation of legacy formatted entries have been disabled by default
1709 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1710 entries were converted to use the new format by default when the new,
1711 machine independent format have been added and supported since FreeBSD
1714 Please see the pwd_mkdb(8) manual page for further details.
1717 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1718 20141231 entry below for information about prerequisites and upgrading,
1719 if you are not already using 3.5.0 or higher.
1722 TI platform code switched to using vendor DTS files and this update
1723 may break existing systems running on Beaglebone, Beaglebone Black,
1726 - dtb files should be regenerated/reinstalled. Filenames are the
1727 same but content is different now
1728 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1729 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1730 addressing scheme is now pin 25 on /dev/gpioc3.
1731 - Pandaboard: /etc/ttys should be updated, serial console device is
1732 now /dev/ttyu2, not /dev/ttyu0
1735 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1736 If you need the GNU extension from groff soelim(1), install groff
1737 from package: pkg install groff, or via ports: textproc/groff.
1740 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1741 defined in symlink(7); previously symlinks were silently ignored.
1744 The const qualifier has been removed from iconv(3) to comply with
1745 POSIX. The ports tree is aware of this from r384038 onwards.
1748 Libraries specified by LIBADD in Makefiles must have a corresponding
1749 DPADD_<lib> variable to ensure correct dependencies. This is now
1750 enforced in src.libnames.mk.
1753 From legacy ata(4) driver was removed support for SATA controllers
1754 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1755 Kernel modules ataahci and ataadaptec were removed completely,
1756 replaced by ahci and mvs modules respectively.
1759 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1760 the 20141231 entry below for information about prerequisites and
1761 upgrading, if you are not already using 3.5.0 or higher.
1764 The 32-bit PowerPC kernel has been changed to a position-independent
1765 executable. This can only be booted with a version of loader(8)
1766 newer than January 31, 2015, so make sure to update both world and
1767 kernel before rebooting.
1770 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1771 but before r278950, the RNG was not seeded properly. Immediately
1772 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1773 ssh keys or openssl keys) that were generated w/ a kernel from that
1774 range. This does not affect programs that directly used /dev/random
1775 or /dev/urandom. All userland uses of arc4random(3) are affected.
1778 The autofs(4) ABI was changed in order to restore binary compatibility
1779 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1780 with the new kernel.
1783 The powerpc64 kernel has been changed to a position-independent
1784 executable. This can only be booted with a new version of loader(8),
1785 so make sure to update both world and kernel before rebooting.
1788 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1789 only release, no new features have been added. Please see the 20141231
1790 entry below for information about prerequisites and upgrading, if you
1791 are not already using 3.5.0.
1794 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1795 taken from the ELF Tool Chain project rather than GNU binutils. They
1796 should be drop-in replacements, with the addition of arm64 support.
1797 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1798 binutils tools, if necessary. See 20150805 for updated information.
1801 The default Unbound configuration now enables remote control
1802 using a local socket. Users who have already enabled the
1803 local_unbound service should regenerate their configuration
1804 by running "service local_unbound setup" as root.
1807 The GNU texinfo and GNU info pages have been removed.
1808 To be able to view GNU info pages please install texinfo from ports.
1811 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1813 As of this release, a prerequisite for building clang, llvm and lldb is
1814 a C++11 capable compiler and C++11 standard library. This means that to
1815 be able to successfully build the cross-tools stage of buildworld, with
1816 clang as the bootstrap compiler, your system compiler or cross compiler
1817 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1818 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1821 On any standard FreeBSD 10.x or 11.x installation, where clang and
1822 libc++ are on by default (that is, on x86 or arm), this should work out
1825 On 9.x installations where clang is enabled by default, e.g. on x86 and
1826 powerpc, libc++ will not be enabled by default, so libc++ should be
1827 built (with clang) and installed first. If both clang and libc++ are
1828 missing, build clang first, then use it to build libc++.
1830 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1831 the instructions for 9.x above.
1833 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1834 default, and do not build clang.
1836 Many embedded systems are resource constrained, and will not be able to
1837 build clang in a reasonable time, or in some cases at all. In those
1838 cases, cross building bootable systems on amd64 is a workaround.
1840 This new version of clang introduces a number of new warnings, of which
1841 the following are most likely to appear:
1845 This warns in two cases, for both C and C++:
1846 * When the code is trying to take the absolute value of an unsigned
1847 quantity, which is effectively a no-op, and almost never what was
1848 intended. The code should be fixed, if at all possible. If you are
1849 sure that the unsigned quantity can be safely cast to signed, without
1850 loss of information or undefined behavior, you can add an explicit
1851 cast, or disable the warning.
1853 * When the code is trying to take an absolute value, but the called
1854 abs() variant is for the wrong type, which can lead to truncation.
1855 If you want to disable the warning instead of fixing the code, please
1856 make sure that truncation will not occur, or it might lead to unwanted
1859 -Wtautological-undefined-compare and
1860 -Wundefined-bool-conversion
1862 These warn when C++ code is trying to compare 'this' against NULL, while
1863 'this' should never be NULL in well-defined C++ code. However, there is
1864 some legacy (pre C++11) code out there, which actively abuses this
1865 feature, which was less strictly defined in previous C++ versions.
1867 Squid and openjdk do this, for example. The warning can be turned off
1868 for C++98 and earlier, but compiling the code in C++11 mode might result
1869 in unexpected behavior; for example, the parts of the program that are
1870 unreachable could be optimized away.
1873 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1874 kernel sources have been removed. The .h files remain, since some
1875 utilities include them. This will need to be fixed later.
1876 If "mount -t oldnfs ..." is attempted, it will fail.
1877 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1878 the utilities will report errors.
1881 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1882 directories to top level SUBDIR variable when their parent
1883 directory is included in LOCAL_DIRS. Users with build systems with
1884 such hierarchies and without SUBDIR entries in the parent
1885 directory Makefiles should add them or add the directories to
1889 faith(4) and faithd(8) have been removed from the base system. Faith
1890 has been obsolete for a very long time.
1893 vt(4), the new console driver, is enabled by default. It brings
1894 support for Unicode and double-width characters, as well as
1895 support for UEFI and integration with the KMS kernel video
1898 You may need to update your console settings in /etc/rc.conf,
1899 most probably the keymap. During boot, /etc/rc.d/syscons will
1900 indicate what you need to do.
1902 vt(4) still has issues and lacks some features compared to
1903 syscons(4). See the wiki for up-to-date information:
1904 https://wiki.freebsd.org/Newcons
1906 If you want to keep using syscons(4), you can do so by adding
1907 the following line to /boot/loader.conf:
1911 pjdfstest has been integrated into kyua as an opt-in test suite.
1912 Please see share/doc/pjdfstest/README for more details on how to
1916 gperf has been removed from the base system for architectures
1917 that use clang. Ports that require gperf will obtain it from the
1921 pjdfstest has been moved from tools/regression/pjdfstest to
1925 At svn r271982, The default linux compat kernel ABI has been adjusted
1926 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1927 update. If you wish to continue using the linux-f10 compat ports,
1928 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1929 encouraged to update their linux-compat packages to linux-c6 during
1930 their next update cycle.
1933 The ofwfb driver, used to provide a graphics console on PowerPC when
1934 using vt(4), no longer allows mmap() of all physical memory. This
1935 will prevent Xorg on PowerPC with some ATI graphics cards from
1936 initializing properly unless x11-servers/xorg-server is updated to
1940 The xdev targets have been converted to using TARGET and
1941 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1944 The default unbound configuration has been modified to address
1945 issues with reverse lookups on networks that use private
1946 address ranges. If you use the local_unbound service, run
1947 "service local_unbound setup" as root to regenerate your
1948 configuration, then "service local_unbound reload" to load the
1952 The GNU texinfo and GNU info pages are not built and installed
1953 anymore, WITH_INFO knob has been added to allow to built and install
1955 UPDATE: see 20150102 entry on texinfo's removal
1958 The GNU readline library is now an INTERNALLIB - that is, it is
1959 statically linked into consumers (GDB and variants) in the base
1960 system, and the shared library is no longer installed. The
1961 devel/readline port is available for third party software that
1965 The Itanium architecture (ia64) has been removed from the list of
1966 known architectures. This is the first step in the removal of the
1970 Commit r268115 has added NFSv4.1 server support, merged from
1971 projects/nfsv4.1-server. Since this includes changes to the
1972 internal interfaces between the NFS related modules, a full
1973 build of the kernel and modules will be necessary.
1974 __FreeBSD_version has been bumped.
1977 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1978 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1979 which differs from the behaviour controlled by this knob.)
1982 Maximal length of the serial number in CTL was increased from 16 to
1983 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1984 and ctld, need to be rebuilt to work with a new kernel.
1987 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1988 1 respectively to match the upstream numbers. They were out of
1989 sync because, when they were originally added to FreeBSD, the
1990 upstream versions were not respected. These libraries are private
1991 and not yet built by default, so renumbering them should be a
1992 non-issue. However, unclean source trees will yield broken test
1993 programs once the operator executes "make delete-old-libs" after a
1994 "make installworld".
1996 Additionally, the atf-sh binary was made private by moving it into
1997 /usr/libexec/. Already-built shell test programs will keep the
1998 path to the old binary so they will break after "make delete-old"
2001 If you are using WITH_TESTS=yes (not the default), wipe the object
2002 tree and rebuild from scratch to prevent spurious test failures.
2003 This is only needed once: the misnumbered libraries and misplaced
2004 binaries have been added to OptionalObsoleteFiles.inc so they will
2005 be removed during a clean upgrade.
2008 Clang and llvm have been upgraded to 3.4.1 release.
2011 We bogusly installed src.opts.mk in /usr/share/mk. This file should
2012 be removed to avoid issues in the future (and has been added to
2016 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
2017 past, it affected all builds that used the bsd.*.mk files. The old
2018 behavior was a bug, but people may have relied upon it. To get this
2019 behavior back, you can .include /etc/src.conf from /etc/make.conf
2020 (which is still global and isn't changed). This also changes the
2021 behavior of incremental builds inside the tree of individual
2022 directories. Set MAKESYSPATH to ".../share/mk" to do that.
2023 Although this has survived make universe and some upgrade scenarios,
2024 other upgrade scenarios may have broken. At least one form of
2025 temporary breakage was fixed with MAKESYSPATH settings for buildworld
2026 as well... In cases where MAKESYSPATH isn't working with this
2027 setting, you'll need to set it to the full path to your tree.
2029 One side effect of all this cleaning up is that bsd.compiler.mk
2030 is no longer implicitly included by bsd.own.mk. If you wish to
2031 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
2035 The lindev device has been removed since /dev/full has been made a
2036 standard device. __FreeBSD_version has been bumped.
2039 The knob WITHOUT_VI was added to the base system, which controls
2040 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
2041 in order to reorder files share/termcap and didn't build ex(1) as a
2042 build tool, so building/installing with WITH_VI is highly advised for
2043 build hosts for older releases.
2045 This issue has been fixed in stable/9 and stable/10 in r277022 and
2046 r276991, respectively.
2049 The YES_HESIOD knob has been removed. It has been obsolete for
2050 a decade. Please move to using WITH_HESIOD instead or your builds
2051 will silently lack HESIOD.
2054 The uart(4) driver has been changed with respect to its handling
2055 of the low-level console. Previously the uart(4) driver prevented
2056 any process from changing the baudrate or the CLOCAL and HUPCL
2057 control flags. By removing the restrictions, operators can make
2058 changes to the serial console port without having to reboot.
2059 However, when getty(8) is started on the serial device that is
2060 associated with the low-level console, a misconfigured terminal
2061 line in /etc/ttys will now have a real impact.
2062 Before upgrading the kernel, make sure that /etc/ttys has the
2063 serial console device configured as 3wire without baudrate to
2064 preserve the previous behaviour. E.g:
2065 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
2068 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
2069 to improve performance. To re-enable it, if needed, run rpcbind
2070 with command line option -W.
2073 Switched back to the GPL dtc compiler due to updates in the upstream
2074 dts files not being supported by the BSDL dtc compiler. You will need
2075 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
2076 may result while building dtb files during a kernel build if you fail
2077 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
2080 Clang and llvm have been upgraded to 3.4 release.
2083 The nve(4) driver has been removed. Please use the nfe(4) driver
2084 for NVIDIA nForce MCP Ethernet adapters instead.
2087 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
2088 This could cause certain C++ applications using shared libraries built
2089 against the previous version of libc++ to crash. The incompatibility
2090 has now been fixed, but any C++ applications or shared libraries built
2091 between r261283 and r261801 should be recompiled.
2094 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
2095 capability mode support. Please note that enabling the feature in
2096 kernel is still highly recommended.
2099 OpenSSH is now built with sandbox support, and will use sandbox as
2100 the default privilege separation method. This requires Capsicum
2101 capability mode support in kernel.
2104 The libelf and libdwarf libraries have been updated to newer
2105 versions from upstream. Shared library version numbers for
2106 these two libraries were bumped. Any ports or binaries
2107 requiring these two libraries should be recompiled.
2108 __FreeBSD_version is bumped to 1100006.
2111 If a Makefile in a tests/ directory was auto-generating a Kyuafile
2112 instead of providing an explicit one, this would prevent such
2113 Makefile from providing its own Kyuafile in the future during
2114 NO_CLEAN builds. This has been fixed in the Makefiles but manual
2115 intervention is needed to clean an objdir if you use NO_CLEAN:
2116 # find /usr/obj -name Kyuafile | xargs rm -f
2119 The behavior of gss_pseudo_random() for the krb5 mechanism
2120 has changed, for applications requesting a longer random string
2121 than produced by the underlying enctype's pseudo-random() function.
2122 In particular, the random string produced from a session key of
2123 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
2124 be different at the 17th octet and later, after this change.
2125 The counter used in the PRF+ construction is now encoded as a
2126 big-endian integer in accordance with RFC 4402.
2127 __FreeBSD_version is bumped to 1100004.
2130 The WITHOUT_ATF build knob has been removed and its functionality
2131 has been subsumed into the more generic WITHOUT_TESTS. If you were
2132 using the former to disable the build of the ATF libraries, you
2133 should change your settings to use the latter.
2136 The default version of mtree is nmtree which is obtained from
2137 NetBSD. The output is generally the same, but may vary
2138 slightly. If you found you need identical output adding
2139 "-F freebsd9" to the command line should do the trick. For the
2140 time being, the old mtree is available as fmtree.
2143 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
2144 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
2145 1.1.4_8 and verify bsdyml not linked in, before running "make
2147 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
2149 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
2152 The stable/10 branch has been created in subversion from head
2159 Sometimes, obscure build problems are the result of environment
2160 poisoning. This can happen because the make utility reads its
2161 environment when searching for values for global variables. To run
2162 your build attempts in an "environmental clean room", prefix all make
2163 commands with 'env -i '. See the env(1) manual page for more details.
2164 Occasionally a build failure will occur with "make -j" due to a race
2165 condition. If this happens try building again without -j, and please
2166 report a bug if it happens consistently.
2168 When upgrading from one major version to another it is generally best to
2169 upgrade to the latest code in the currently installed branch first, then
2170 do an upgrade to the new branch. This is the best-tested upgrade path,
2171 and has the highest probability of being successful. Please try this
2172 approach if you encounter problems with a major version upgrade. Since
2173 the stable 4.x branch point, one has generally been able to upgrade from
2174 anywhere in the most recent stable branch to head / current (or even the
2175 last couple of stable branches). See the top of this file when there's
2178 The update process will emit an error on an attempt to perform a build
2179 or install from a FreeBSD version below the earliest supported version.
2180 When updating from an older version the update should be performed one
2181 major release at a time, including running `make delete-old` at each
2184 When upgrading a live system, having a root shell around before
2185 installing anything can help undo problems. Not having a root shell
2186 around can lead to problems if pam has changed too much from your
2187 starting point to allow continued authentication after the upgrade.
2189 This file should be read as a log of events. When a later event changes
2190 information of a prior event, the prior event should not be deleted.
2191 Instead, a pointer to the entry with the new information should be
2192 placed in the old entry. Readers of this file should also sanity check
2193 older entries before relying on them blindly. Authors of new entries
2194 should write them with this in mind.
2198 When upgrading the boot ZFS pool to a new version, always follow
2201 1.) recompile and reinstall the ZFS boot loader and boot block
2202 (this is part of "make buildworld" and "make installworld")
2204 2.) update the ZFS boot block on your boot drive
2206 The following example updates the ZFS boot block on the first
2207 partition (freebsd-boot) of a GPT partitioned drive ada0:
2208 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
2210 Non-boot pools do not need these updates.
2214 If you are updating from a prior version of FreeBSD (even one just
2215 a few days old), you should follow this procedure. It is the most
2216 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2218 make kernel-toolchain
2219 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2220 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2222 To test a kernel once
2223 ---------------------
2224 If you just want to boot a kernel once (because you are not sure
2225 if it works, or if you want to boot a known bad kernel to provide
2226 debugging information) run
2227 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2228 nextboot -k testkernel
2230 To rebuild everything and install it on the current system.
2231 -----------------------------------------------------------
2232 # Note: sometimes if you are running current you gotta do more than
2233 # is listed here if you are upgrading from a really old current.
2235 <make sure you have good level 0 dumps>
2237 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2238 make installkernel KERNCONF=YOUR_KERNEL_HERE
2240 <reboot in single user> [3]
2247 To cross-install current onto a separate partition
2248 --------------------------------------------------
2249 # In this approach we use a separate partition to hold
2250 # current's root, 'usr', and 'var' directories. A partition
2251 # holding "/", "/usr" and "/var" should be about 2GB in
2254 <make sure you have good level 0 dumps>
2257 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2258 <maybe newfs current's root partition>
2259 <mount current's root partition on directory ${CURRENT_ROOT}>
2260 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
2261 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2262 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2263 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2264 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2265 <reboot into current>
2266 <do a "native" rebuild/install as described in the previous section>
2267 <maybe install compatibility libraries from ports/misc/compat*>
2271 To upgrade in-place from stable to current
2272 ----------------------------------------------
2273 <make sure you have good level 0 dumps>
2275 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
2276 make installkernel KERNCONF=YOUR_KERNEL_HERE
2278 <reboot in single user> [3]
2285 Make sure that you've read the UPDATING file to understand the
2286 tweaks to various things you need. At this point in the life
2287 cycle of current, things change often and you are on your own
2288 to cope. The defaults can also change, so please read ALL of
2289 the UPDATING entries.
2291 Also, if you are tracking -current, you must be subscribed to
2292 freebsd-current@freebsd.org. Make sure that before you update
2293 your sources that you have read and understood all the recent
2294 messages there. If in doubt, please track -stable which has
2295 much fewer pitfalls.
2297 [1] If you have third party modules, such as vmware, you
2298 should disable them at this point so they don't crash your
2301 [3] From the bootblocks, boot -s, and then do
2305 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed
2306 cd src # full path to source
2307 adjkerntz -i # if CMOS is wall time
2308 Also, when doing a major release upgrade, it is required that
2309 you boot into single user mode to do the installworld.
2311 [4] Note: This step is non-optional. Failure to do this step
2312 can result in a significant reduction in the functionality of the
2313 system. Attempting to do it by hand is not recommended and those
2314 that pursue this avenue should read this file carefully, as well
2315 as the archives of freebsd-current and freebsd-hackers mailing lists
2316 for potential gotchas. The -U option is also useful to consider.
2317 See mergemaster(8) for more information.
2319 [5] Usually this step is a no-op. However, from time to time
2320 you may need to do this if you get unknown user in the following
2321 step. It never hurts to do it all the time. You may need to
2322 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2323 install) after the buildworld before this step if you last updated
2324 from current before 20130425 or from -stable before 20130430.
2326 [6] This only deletes old files and directories. Old libraries
2327 can be deleted by "make delete-old-libs", but you have to make
2328 sure that no program is using those libraries anymore.
2330 [8] The new kernel must be able to run existing binaries used by an
2331 installworld. When upgrading across major versions, the new kernel's
2332 configuration must include the correct COMPAT_FREEBSD<n> option for
2333 existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure
2334 to do so may leave you with a system that is hard to boot to recover. A
2335 GENERIC kernel will include suitable compatibility options to run
2336 binaries from older branches. Note that the ability to run binaries
2337 from unsupported branches is not guaranteed.
2339 Make sure that you merge any new devices from GENERIC since the
2340 last time you updated your kernel config file. Options also
2341 change over time, so you may need to adjust your custom kernels
2344 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2345 "?=" instead of the "=" assignment operator, so that buildworld can
2346 override the CPUTYPE if it needs to.
2348 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2349 not on the command line, or in /etc/make.conf. buildworld will
2350 warn if it is improperly defined.
2353 This file contains a list, in reverse chronological order, of major
2354 breakages in tracking -current. It is not guaranteed to be a complete
2355 list of such breakages, and only contains entries since September 23, 2011.
2356 If you need to see UPDATING entries from before that date, you will need
2357 to fetch an UPDATING file from an older FreeBSD release.
2359 Copyright information:
2361 Copyright 1998-2009 M. Warner Losh <imp@FreeBSD.org>
2363 Redistribution, publication, translation and use, with or without
2364 modification, in full or in part, in any form or format of this
2365 document are permitted without further permission from the author.
2367 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2368 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2369 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2370 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2371 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2372 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2373 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2374 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2375 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2376 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2377 POSSIBILITY OF SUCH DAMAGE.
2379 Contact Warner Losh if you have any questions about your use of