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 LINT files are no longer generated. We now include the relevant NOTES
31 files. Note: This may cause conflicts with updating in some cases.
32 find sys -name LINT\* -delete
33 is suggested across this commit to remove the generated LINT files.
35 If you have tried to update with generated files there, the svn
36 command you want to un-auger the tree is
39 and then do the above find from the top level. Substitute 'amd64'
40 above with where the error message indicates a conflict.
43 OpenZFS support has been integrated. Do not upgrade root pools until
44 the loader is updated to support zstd. Furthermore, we caution against
45 'zpool upgrade' for the next few weeks. The change should be transparent
46 unless you want to use new features.
48 Not all "NO_CLEAN" build scenarios work across these changes. Many
49 scenarios have been tested and fixed, but rebuilding kernels without
50 rebuilding world may fail.
52 The ZFS cache file has moved from /boot to /etc to match the OpenZFS
53 upstream default. A fallback to /boot has been added for mountroot.
55 Pool auto import behavior at boot has been moved from the kernel module
56 to an explicit "zpool import -a" in one of the rc scripts enabled by
57 zfs_enable=YES. This means your non-root zpools won't auto import until
58 you upgrade your /etc/rc.d files.
61 The resume code now notifies devd with the 'kernel' system
62 rather than the old 'kern' subsystem to be consistent with
63 other use. The old notification will be created as well, but
64 will be removed prior to FreeBSD 14.0.
67 r362275 changed the internal API between the kernel RPC and the
68 NFS modules. As such, all the modules must be recompiled from
72 r364330 modified the internal API used between the NFS modules.
73 As such, all the NFS modules must be re-compiled from sources.
76 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
77 been upgraded to 11.0.0. Please see the 20141231 entry below for
78 information about prerequisites and upgrading, if you are not already
79 using clang 3.5.0 or higher.
82 r364092 modified the internal ABI used between the kernel NFS
83 modules. As such, all of these modules need to be rebuilt
84 from sources, so a version bump was done.
87 Makefile.inc has been updated to work around the issue documented in
88 20200729. It was a case where the optimization of using symbolic links
89 to point to binaries created a situation where we'd run new binaries
90 with old libraries starting midway through the installworld process.
93 r363679 has redefined some undefined behavior in regcomp(3); notably,
94 extraneous escapes of most ordinary characters will no longer be
95 accepted. An exp-run has identified all of the problems with this in
96 ports, but other non-ports software may need extra escapes removed to
99 Because of this change, installworld may encounter the following error
100 from rtld: Undefined symbol "regcomp@FBSD_1.6" -- It is imperative that
101 you do not halt installworld. Instead, let it run to completion (whether
102 successful or not) and run installworld once more.
105 A new implementation of bc and dc has been imported in r362681. This
106 implementation corrects non-conformant behavior of the previous bc
107 and adds GNU bc compatible options. It offers a number of extensions,
108 is much faster on large values, and has support for message catalogs
109 (a number of languages are already supported, contributions of further
110 languages welcome). The option WITHOUT_GH_BC can be used to build the
111 world with the previous versions of bc and dc.
114 r362639 changed the internal API used between the NFS kernel modules.
115 As such, they all need to be rebuilt from sources.
118 r362158 changed the arguments for VFS_CHECKEXP(). As such, any
119 out of tree file systems need to be modified and rebuilt.
120 Also, any file systems that are modules must be rebuilt.
123 read(2) of a directory fd is now rejected by default. root may
124 re-enable it for system root only on non-ZFS filesystems with the
125 security.bsd.allow_read_dir sysctl(8) MIB if
126 security.bsd.suser_enabled=1.
128 It may be advised to setup aliases for grep to default to `-d skip` if
129 commonly non-recursively grepping a list that includes directories and
130 the potential for the resulting stderr output is not tolerable. Example
131 aliases are now installed, commented out, in /root/.cshrc and
135 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
136 been upgraded to 10.0.1. Please see the 20141231 entry below for
137 information about prerequisites and upgrading, if you are not already
138 using clang 3.5.0 or higher.
141 Support for obsolete compilers has been removed from the build system.
142 Clang 6 and GCC 6.4 are the minimum supported versions.
145 closefrom(2) has been moved under COMPAT12, and replaced in libc with a
146 stub that calls close_range(2). If using a custom kernel configuration,
147 you may want to ensure that the COMPAT_FREEBSD12 option is included, as
148 a slightly older -CURRENT userland and older FreeBSD userlands may not
149 be functional without closefrom(2).
152 Upstream DTS from Linux 5.6 was merged and they now have the SID
153 and THS (Secure ID controller and THermal Sensor) node present.
154 The DTB overlays have now been removed from the tree for the H3/H5 and
155 A64 SoCs and the aw_sid and aw_thermal driver have been updated to
156 deal with upstream DTS. If you are using those overlays you need to
157 remove them from loader.conf and update the DTBs on the FAT partition.
160 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
161 been upgraded to 10.0.0. Please see the 20141231 entry below for
162 information about prerequisites and upgrading, if you are not already
163 using clang 3.5.0 or higher.
166 The amd(8) automount daemon has been removed from the source tree.
167 As of FreeBSD 10.1 autofs(5) is the preferred tool for automounting.
168 amd is still available in the sysutils/am-utils port.
171 Removed brooktree driver (bktr.4) from the tree.
174 The WITH_GPL_DTC option has been removed. The BSD-licenced device tree
175 compiler in usr.bin/dtc is used on all architectures which use dtc, and
176 the GPL dtc is available (if needed) from the sysutils/dtc port.
179 The WITHOUT_LLVM_LIBUNWIND option has been removed. LLVM's libunwind
180 is used by all supported CPU architectures.
183 GCC 4.2.1 has been removed from the tree. The WITH_GCC,
184 WITH_GCC_BOOTSTRAP, and WITH_GNUCXX options are no longer available.
185 Users who wish to build FreeBSD with GCC must use the external toolchain
189 ncurses has been updated to a newer version (6.2-20200215). Given the ABI
190 has changed, users will have to rebuild all the ports that are linked to
194 The size of struct vnet and the magic cookie have changed.
195 Users need to recompile libkvm and all modules using VIMAGE
196 together with their new kernel.
199 Defining the long deprecated NO_CTF, NO_DEBUG_FILES, NO_INSTALLLIB,
200 NO_MAN, NO_PROFILE, and NO_WARNS variables is now an error. Update
201 your Makefiles and scripts to define MK_<var>=no instead as required.
203 One exception to this is that program or library Makefiles should
204 define MAN to empty rather than setting MK_MAN=no.
207 Clang/LLVM is now the default compiler and LLD the default
211 make universe no longer uses GCC 4.2.1 on any architectures.
212 Architectures not supported by in-tree Clang/LLVM require an
213 external toolchain package.
216 GCC 4.2.1 is now not built by default, as part of the GCC 4.2.1
217 retirement plan. Specifically, the GCC, GCC_BOOTSTRAP, and GNUCXX
218 options default to off for all supported CPU architectures. As a
219 short-term transition aid they may be enabled via WITH_* options.
220 GCC 4.2.1 is expected to be removed from the tree on 2020-03-31.
223 Support for armv5 has been disconnected and is being removed. The
224 machine combination MACHINE=arm MACHINE_ARCH=arm is no longer valid.
225 You must now use a MACHINE_ARCH of armv6 or armv7. The default
226 MACHINE_ARCH for MACHINE=arm is now armv7.
229 Clang/LLVM is now the default compiler for all powerpc architectures.
230 LLD is now the default linker for powerpc64. The change for powerpc64
231 also includes a change to the ELFv2 ABI, incompatible with the existing
235 Kernel-loadable random(4) modules are no longer unloadable.
238 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
239 been upgraded to 9.0.1. Please see the 20141231 entry below for
240 information about prerequisites and upgrading, if you are not already
241 using clang 3.5.0 or higher.
244 r355677 has modified the internal interface used between the
245 NFS modules in the kernel. As such, they must all be upgraded
246 simultaneously. I will do a version bump for this.
249 The root certificates of the Mozilla CA Certificate Store have been
250 imported into the base system and can be managed with the certctl(8)
251 utility. If you have installed the security/ca_root_nss port or package
252 with the ETCSYMLINK option (the default), be advised that there may be
253 differences between those included in the port and those included in
254 base due to differences in nss branch used as well as general update
255 frequency. Note also that certctl(8) cannot manage certs in the
256 format used by the security/ca_root_nss port.
259 The amd(8) automount daemon has been disabled by default, and will be
260 removed in the future. As of FreeBSD 10.1 the autofs(5) is available
264 The nctgpio and wbwd drivers have been moved to the superio bus.
265 If you have one of these drivers in a kernel configuration, then
266 you should add device superio to it. If you use one of these drivers
267 as a module and you compile a custom set of modules, then you should
268 add superio to the set.
271 KPIs for network drivers to access interface addresses have changed.
272 Users need to recompile NIC driver modules together with kernel.
275 The net.link.tap.user_open sysctl no longer prevents user opening of
276 already created /dev/tapNN devices. Access is still controlled by
277 node permissions, just like tun devices. The net.link.tap.user_open
278 sysctl is now used only to allow users to perform devfs cloning of
279 tap devices, and the subsequent open may not succeed if the user is not
280 in the appropriate group. This sysctl may be deprecated/removed
281 completely in the future.
284 mips, powerpc, and sparc64 are no longer built as part of
285 universe / tinderbox unless MAKE_OBSOLETE_GCC is defined. If
286 not defined, mips, powerpc, and sparc64 builds will look for
287 the xtoolchain binaries and if installed use them for universe
288 builds. As llvm 9.0 becomes vetted for these architectures, they
289 will be removed from the list.
292 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
293 been upgraded to 9.0.0. Please see the 20141231 entry below for
294 information about prerequisites and upgrading, if you are not already
295 using clang 3.5.0 or higher.
298 The hpt27xx, hptmv, hptnr, and hptrr drivers have been removed from
299 GENERIC. They are available as modules and can be loaded by adding
300 to /boot/loader.conf hpt27xx_load="YES", hptmv_load="YES",
301 hptnr_load="YES", or hptrr_load="YES", respectively.
304 ntpd no longer by default locks its pages in memory, allowing them
305 to be paged out by the kernel. Use rlimit memlock to restore
306 historic BSD behaviour. For example, add "rlimit memlock 32"
307 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
310 Several of ping6's options have been renamed for better consistency
311 with ping. If you use any of -ARWXaghmrtwx, you must update your
312 scripts. See ping6(8) for details.
315 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
316 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
317 been removed from mount_fusefs(8). You can safely remove them from
318 your scripts, because they had no effect.
320 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
321 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
322 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
323 sysctls have been removed. If you felt the need to set any of them to
324 a non-default value, please tell asomers@FreeBSD.org why.
327 Default permissions on the /var/account/acct file (and copies of it
328 rotated by periodic daily scripts) are changed from 0644 to 0640
329 because the file contains sensitive information that should not be
330 world-readable. If the /var/account directory must be created by
331 rc.d/accounting, the mode used is now 0750. Admins who use the
332 accounting feature are encouraged to change the mode of an existing
333 /var/account directory to 0750 or 0700.
336 Entropy collection and the /dev/random device are no longer optional
337 components. The "device random" option has been removed.
338 Implementations of distilling algorithms can still be made loadable
339 with "options RANDOM_LOADABLE" (e.g., random_fortuna.ko).
342 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
343 been upgraded to 8.0.1. Please see the 20141231 entry below for
344 information about prerequisites and upgrading, if you are not already
345 using clang 3.5.0 or higher.
348 A fix was applied to i386 kernel modules to avoid panics with
349 dpcpu or vnet. Users need to recompile i386 kernel modules
350 having pcpu or vnet sections or they will refuse to load.
353 User-wired pages now have their own counter,
354 vm.stats.vm.v_user_wire_count. The vm.max_wired sysctl was renamed
355 to vm.max_user_wired and changed from an unsigned int to an unsigned
356 long. bhyve VMs wired with the -S are now subject to the user
357 wiring limit; the vm.max_user_wired sysctl may need to be tuned to
358 avoid running into the limit.
361 The IPSEC option has been removed from GENERIC. Users requiring
362 ipsec(4) must now load the ipsec(4) kernel module.
365 The tap(4) driver has been folded into tun(4), and the module has been
366 renamed to tuntap. You should update any kld_list="if_tap" or
367 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
368 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
369 module instead, and "device tap" or "device tun" entries in kernel
370 config files to select the tuntap device instead.
373 The following knobs have been added related to tradeoffs between
374 safe use of the random device and availability in the absence of
377 kern.random.initial_seeding.bypass_before_seeding: tunable; set
378 non-zero to bypass the random device prior to seeding, or zero to
379 block random requests until the random device is initially seeded.
380 For now, set to 1 (unsafe) by default to restore pre-r346250 boot
381 availability properties.
383 kern.random.initial_seeding.read_random_bypassed_before_seeding:
384 read-only diagnostic sysctl that is set when bypass is enabled and
385 read_random(9) is bypassed, to enable programmatic handling of this
386 initial condition, if desired.
388 kern.random.initial_seeding.arc4random_bypassed_before_seeding:
389 Similar to the above, but for for arc4random(9) initial seeding.
391 kern.random.initial_seeding.disable_bypass_warnings: tunable; set
392 non-zero to disable warnings in dmesg when the same conditions are
393 met as for the diagnostic sysctls above. Defaults to zero, i.e.,
394 produce warnings in dmesg when the conditions are met.
397 The loadable random module KPI has changed; the random_infra_init()
398 routine now requires a 3rd function pointer for a bool (*)(void)
399 method that returns true if the random device is seeded (and
400 therefore unblocked).
403 r345895 reverts r320698. This implies that an nfsuserd(8) daemon
404 built from head sources between r320757 (July 6, 2017) and
405 r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
406 is added to the command line.
407 nfsuserd daemons built from head sources that are post-r338192 are
408 not affected and should continue to work.
411 The fuse(4) module has been renamed to fusefs(4) for consistency with
412 other filesystems. You should update any kld_load="fuse" entries in
413 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
414 "options FUSE" entries in kernel config files.
417 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
418 8.0.0. Please see the 20141231 entry below for information about
419 prerequisites and upgrading, if you are not already using clang 3.5.0
423 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
424 compiled into your custom kernel, add 'device xz' statement to the
428 drm and drm2 have been removed from the tree. Please see
429 https://wiki.freebsd.org/Graphics for the latest information on
430 migrating to the drm ports.
433 Iflib is no longer unconditionally compiled into the kernel. Drivers
434 using iflib and statically compiled into the kernel, now require
435 the 'device iflib' config option. For the same drivers loaded as
436 modules on kernels not having 'device iflib', the iflib.ko module
437 is loaded automatically.
440 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
441 options no longer exist since r343219 and r343427 respectively;
442 nothing uses them, so they should be just removed from custom
446 r342635 changes the way efibootmgr(8) works by requiring users to add
447 the -b (bootnum) parameter for commands where the bootnum was previously
448 specified with each option. For example 'efibootmgr -B 0001' is now
449 'efibootmgr -B -b 0001'.
452 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
453 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
454 servers that have vfs.nfsd.nfs_privport set will only allow mounts
455 from clients using a reserved port#. Since both the FreeBSD and Linux
456 NFSv4 clients use reserved port#s by default, this should not affect
460 The XLP config has been removed. We can't support 64-bit atomics in this
461 kernel because it is running in 32-bit mode. XLP users must transition
462 to running a 64-bit kernel (XLP64 or XLPN32).
464 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
465 the preferred emulator today and we don't need two different ones.
467 The old sibyte / swarm / Broadcom BCM1250 support has been
468 removed from the mips port.
471 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
472 7.0.1. Please see the 20141231 entry below for information about
473 prerequisites and upgrading, if you are not already using clang 3.5.0
477 Remove the timed and netdate programs from the base tree. Setting
478 the time with these daemons has been obsolete for over a decade.
481 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
482 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
483 it produces broken binaries when ifuncs are in use. Users needing
484 GNU ld should install the binutils port or package.
487 The BSD crtbegin and crtend code has been enabled by default. It has
488 had extensive testing on amd64, arm64, and i386. It can be disabled
489 by building a world with -DWITHOUT_BSD_CRTBEGIN.
492 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
493 has been converted to a port (misc/ctm) and will be removed from
494 FreeBSD-13. It is available as a package (ctm) for all supported
498 The default newsyslog.conf(5) file has been changed to only include
499 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
500 the filenames end in '.conf' and do not begin with a '.'.
502 You should check the configuration files in these two directories match
503 this naming convention. You can verify which configuration files are
504 being included using the command:
508 Ports for the DRM modules have been simplified. Now, amd64 users should
509 just install the drm-kmod port. All others should install
512 Graphics hardware that's newer than about 2010 usually works with
513 drm-kmod. For hardware older than 2013, however, some users will need
514 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
515 than 2008 usually only works in drm-legacy-kmod. The graphics team can
516 only commit to hardware made since 2013 due to the complexity of the
517 market and difficulty to test all the older cards effectively. If you
518 have hardware supported by drm-kmod, you are strongly encouraged to use
519 that as you will get better support.
521 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
522 elsewhere, the drm and drm2 modules will be eliminated from the src base
523 soon (with a limited exception for arm). Please update to the package
524 asap and report any issues to x11@freebsd.org.
526 Generally, anybody using the drm*-kmod packages should add
527 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
528 cross-threading surprises, especially with automatic driver
529 loading from X11 startup. These will become the defaults in 13-current
533 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
534 custom kernel and module loading configuration files must be updated
535 accordingly. Moreover, interfaces previous presented as ixlvN to the
536 system are now exposed as iavfN and network configuration files must
537 be adjusted as necessary.
540 OpenSSL has been updated to version 1.1.1. This update included
541 additional various API changes throughout the base system. It is
542 important to rebuild third-party software after upgrading. The value
543 of __FreeBSD_version has been bumped accordingly.
546 The legacy DRM modules and drivers have now been added to the loader's
547 module blacklist, in favor of loading them with kld_list in rc.conf(5).
548 The module blacklist may be overridden with the loader.conf(5)
549 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
553 The cam(4) based nda(4) driver will be used over nvd(4) by default on
554 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
555 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
556 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
560 Reproducible build mode is now on by default, in preparation for
561 FreeBSD 12.0. This eliminates build metadata such as the user,
562 host, and time from the kernel (and uname), unless the working tree
563 corresponds to a modified checkout from a version control system.
564 The previous behavior can be obtained by setting the /etc/src.conf
565 knob WITHOUT_REPRODUCIBLE_BUILD.
568 The Yarrow CSPRNG has been removed from the kernel as it has not been
569 supported by its designers since at least 2003. Fortuna has been the
570 default since FreeBSD-11.
573 devctl freeze/thaw have gone into the tree, the rc scripts have been
574 updated to use them and devmatch has been changed. You should update
575 kernel, userland and rc scripts all at the same time.
578 The default interpreter has been switched from 4th to Lua.
579 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
580 interpreter. If you have custom FORTH code you will need to set
581 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
582 src.conf for the build. This will create default hard links between
583 loader and loader_4th instead of loader and loader_lua, the new default.
584 If you are using UEFI it will create the proper hard link to loader.efi.
586 bhyve uses userboot.so. It remains 4th-only until some issues are solved
587 regarding coexisting with multiple versions of FreeBSD are resolved.
590 ls(1) now respects the COLORTERM environment variable used in other
591 systems and software to indicate that a colored terminal is both
592 supported and desired. If ls(1) is suddenly emitting colors, they may
593 be disabled again by either removing the unwanted COLORTERM from your
594 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
595 may not be observed in a future release.
598 The default pager for most commands has been changed to "less". To
599 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
603 The jedec_ts(4) driver has been removed. A superset of its functionality
604 is available in the jedec_dimm(4) driver, and the manpage for that
605 driver includes migration instructions. If you have "device jedec_ts"
606 in your kernel configuration file, it must be removed.
609 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
610 This should have no effect if the kernel is booted via BIOS/legacy boot.
611 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
612 has a buggy firmware that prevents a successful boot due to use of
616 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
617 support has been removed from the tree. These ports were
618 obsolete and/or known to be broken for many years.
621 loader.efi has been augmented to participate more fully in the
622 UEFI boot manager protocol. loader.efi will now look at the
623 BootXXXX environment variable to determine if a specific kernel
624 or root partition was specified. XXXX is derived from BootCurrent.
625 efibootmgr(8) manages these standard UEFI variables.
628 zfsloader's functionality has now been folded into loader.
629 zfsloader is no longer necessary once you've updated your
630 boot blocks. For a transition period, we will install a
631 hardlink for zfsloader to loader to allow a smooth transition
632 until the boot blocks can be updated (hard link because old
633 zfs boot blocks don't understand symlinks).
636 ARM64 now have efifb support, if you want to have serial console
637 on your arm64 board when an screen is connected and the bootloader
638 setup a frame buffer for us to use, just add :
642 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
643 an screen connected as the firmware will setup a frame buffer are that
644 u-boot will expose as an EFI frame buffer.
647 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
648 or take steps to update /etc/passwd before doing installworld on
649 existing systems. Do not skip the "mergemaster -Fp" step before
650 installworld, as described in the update procedures near the bottom
651 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
652 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
653 the ntp config file contain options that change file/dir locations.
654 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
655 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
656 taking steps to ensure that all required files/dirs are accessible
660 Big endian arm support has been removed.
663 The static environment setup in kernel configs is no longer mutually
664 exclusive with the loader(8) environment by default. In order to
665 restore the previous default behavior of disabling the loader(8)
666 environment if a static environment is present, you must specify
667 loader_env.disabled=1 in the static environment.
670 The ABI of syscalls used by management tools like sockstat and
671 netstat has been broken to allow 32-bit binaries to work on
672 64-bit kernels without modification. These programs will need
673 to match the kernel in order to function. External programs may
674 require minor modifications to accommodate a change of type in
675 structures from pointers to 64-bit virtual addresses.
678 On i386 and amd64 atomics are now inlined. Out of tree modules using
679 atomics will need to be rebuilt.
682 The '%I' format in the kern.corefile sysctl limits the number of
683 core files that a process can generate to the number stored in the
684 debug.ncores sysctl. The '%I' format is replaced by the single digit
685 index. Previously, if all indexes were taken the kernel would overwrite
686 only a core file with the highest index in a filename.
687 Currently the system will create a new core file if there is a free
688 index or if all slots are taken it will overwrite the oldest one.
691 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
692 6.0.1. Please see the 20141231 entry below for information about
693 prerequisites and upgrading, if you are not already using clang 3.5.0
697 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
698 needed to be changed to work with it. This change was made with r335763
699 and requires a mergemaster / etcupdate / etc to update the installed
703 r334930 changed the interface between the NFS modules, so they all
704 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
707 As of r334391 lld is the default amd64 system linker; it is installed
708 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
712 The kernel / userland interface for devinfo changed, so you'll
713 need a new kernel and userland as a pair for it to work (rebuilding
714 lib/libdevinfo is all that's required). devinfo and devmatch will
715 not work, but everything else will when there's a mismatch.
718 The on-disk format for hwpmc callchain records has changed to include
719 threadid corresponding to a given record. This changes the field offsets
720 and thus requires that libpmcstat be rebuilt before using a kernel
724 The vxge(4) driver has been removed. This driver was introduced into
725 HEAD one week before the Exar left the Ethernet market and is not
726 known to be used. If you have device vxge in your kernel config file
730 The amd64 kernel now requires a ld that supports ifunc to produce a
731 working kernel, either lld or a newer binutils. lld is built by default
732 on amd64, and the 'buildkernel' target uses it automatically. However,
733 it is not the default linker, so building the kernel the traditional
734 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
735 binutils port/package). lld will soon be default, and this requirement
738 NOTE: As of r334391 lld is the default system linker on amd64, and no
739 workaround is necessary.
742 The nxge(4) driver has been removed. This driver was for PCI-X 10g
743 cards made by s2io/Neterion. The company was acquired by Exar and
744 no longer sells or supports Ethernet products. If you have device
745 nxge in your kernel config file it must be removed.
748 The tz database (tzdb) has been updated to 2018e. This version more
749 correctly models time stamps in time zones with negative DST such as
750 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
751 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
752 time zone abbreviations and the tm_isdst flag.
755 The ixgb(4) driver has been removed. This driver was for an early and
756 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
757 quickly shifted to the long lived ixgbe family. If you have device
758 ixgb in your kernel config file it must be removed.
761 The lmc(4) driver has been removed. This was a WAN interface
762 card that was already reportedly rare in 2003, and had an ambiguous
763 license. If you have device lmc in your kernel config file it must
767 Support for Arcnet networks has been removed. If you have device
768 arcnet or device cm in your kernel config file they must be
772 Support for FDDI networks has been removed. If you have device
773 fddi or device fpa in your kernel config file they must be
777 In addition to supporting RFC 3164 formatted messages, the
778 syslogd(8) service is now capable of parsing RFC 5424 formatted
779 log messages. The main benefit of using RFC 5424 is that clients
780 may now send log messages with timestamps containing year numbers,
781 microseconds and time zone offsets.
783 Similarly, the syslog(3) C library function has been altered to
784 send RFC 5424 formatted messages to the local system logging
785 daemon. On systems using syslogd(8), this change should have no
786 negative impact, as long as syslogd(8) and the C library are
787 updated at the same time. On systems using a different system
788 logging daemon, it may be necessary to make configuration
789 adjustments, depending on the software used.
791 When using syslog-ng, add the 'syslog-protocol' flag to local
792 input sources to enable parsing of RFC 5424 formatted messages:
795 unix-dgram("/var/run/log" flags(syslog-protocol));
798 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
799 of the 'imuxsock' module to let messages be processed by the
800 regular RFC 3164/5424 parsing pipeline:
802 module(load="imuxsock" SysSock.UseSpecialParser="off")
804 Do note that these changes only affect communication between local
805 applications and syslogd(8). The format that syslogd(8) uses to
806 store messages on disk or forward messages to other systems
807 remains unchanged. syslogd(8) still uses RFC 3164 for these
808 purposes. Options to customize this behaviour will be added in the
809 future. Utilities that process log files stored in /var/log are
810 thus expected to continue to function as before.
812 __FreeBSD_version has been incremented to 1200061 to denote this
816 Support for token ring networks has been removed. If you
817 have "device token" in your kernel config you should remove
818 it. No device drivers supported token ring.
821 makefs was modified to be able to tag ISO9660 El Torito boot catalog
822 entries as EFI instead of overloading the i386 tag as done previously.
823 The amd64 mkisoimages.sh script used to build amd64 ISO images for
824 release was updated to use this. This may mean that makefs must be
825 updated before "make cdrom" can be run in the release directory. This
826 should be as simple as:
828 $ cd $SRCDIR/usr.sbin/makefs
829 $ make depend all install
832 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
833 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
834 Co-existence for the transition period will come shortly. Booting is a
835 complex environment and test coverage for Lua-enabled loaders has been
836 thin, so it would be prudent to assume it might not work and make
837 provisions for backup boot methods.
840 devmatch functionality has been turned on in devd. It will automatically
841 load drivers for unattached devices. This may cause unexpected drivers
842 to be loaded. Please report any problems to current@ and
846 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
847 6.0.0. Please see the 20141231 entry below for information about
848 prerequisites and upgrading, if you are not already using clang 3.5.0
852 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
853 This means it is used to link the kernel and userland libraries and
854 executables, but is not yet installed as /usr/bin/ld by default.
856 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
857 WITHOUT_LLD_BOOTSTRAP=yes
860 On i386, pmtimer has been removed. Its functionality has been folded
861 into apm. It was a no-op on ACPI in current for a while now (but was
862 still needed on i386 in FreeBSD 11 and earlier). Users may need to
863 remove it from kernel config files.
866 The use of RSS hash from the network card aka flowid has been
867 disabled by default for lagg(4) as it's currently incompatible with
868 the lacp and loadbalance protocols.
870 This can be re-enabled by setting the following in loader.conf:
871 net.link.lagg.default_use_flowid="1"
874 The SW_WATCHDOG option is no longer necessary to enable the
875 hardclock-based software watchdog if no hardware watchdog is
876 configured. As before, SW_WATCHDOG will cause the software
877 watchdog to be enabled even if a hardware watchdog is configured.
880 r326887 fixes the issue described in the 20171214 UPDATING entry.
881 r326888 flips the switch back to building GELI support always.
884 r362593 broke ZFS + GELI support for reasons unknown. However,
885 it also broke ZFS support generally, so GELI has been turned off
886 by default as the lesser evil in r326857. If you boot off ZFS and/or
887 GELI, it might not be a good time to update.
890 PowerPC users must update loader(8) by rebuilding world before
891 installing a new kernel, as the protocol connecting them has
892 changed. Without the update, loader metadata will not be passed
893 successfully to the kernel and users will have to enter their
894 root partition at the kernel mountroot prompt to continue booting.
895 Newer versions of loader can boot old kernels without issue.
898 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
899 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
900 to WITH/OUT_LOADER_GELI.
903 The naive and non-compliant support of posix_fallocate(2) in ZFS
904 has been removed as of r325320. The system call now returns EINVAL
905 when used on a ZFS file. Although the new behavior complies with the
906 standard, some consumers are not prepared to cope with it.
907 One known victim is lld prior to r325420.
910 Building in a FreeBSD src checkout will automatically create object
911 directories now rather than store files in the current directory if
912 'make obj' was not ran. Calling 'make obj' is no longer necessary.
913 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
914 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
918 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
919 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
920 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
921 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
922 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
923 The UNIFIED_OBJDIR option is a transitional feature that will be
924 removed for 12.0 release; please migrate to the new format for any
925 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
926 than hardcoding paths.
929 The native-xtools target no longer installs the files by default to the
930 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
931 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
934 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
935 options are changing from controlling the build if defined / undefined
936 to controlling the build with explicit 'yes' or 'no' values. They will
937 shift to WITH/WITHOUT options to match other options in the system.
940 libstand has turned into a private library for sys/boot use only.
941 It is no longer supported as a public interface outside of sys/boot.
944 The arm port has split armv6 into armv6 and armv7. armv7 is now
945 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
946 and are running a kernel from before r324363, you will need to add
947 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
950 When building multiple kernels using KERNCONF, non-existent KERNCONF
951 files will produce an error and buildkernel will fail. Previously
952 missing KERNCONF files silently failed giving no indication as to
953 why, only to subsequently discover during installkernel that the
954 desired kernel was never built in the first place.
957 The default serial number format for CTL LUNs has changed. This will
958 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
959 or iSCSI clients care about their LUNs' serial numbers. Users who
960 require serial number stability should hardcode serial numbers in
964 For 32-bit arm compiled for hard-float support, soft-floating point
965 binaries now always get their shared libraries from
966 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
967 /usr/libsoft also existed). Only users with a hard-float ld.so, but
968 soft-float everything else should be affected.
971 The geli password typed at boot is now hidden. To restore the previous
972 behavior, see geli(8) for configuration options.
975 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
976 sysctl values. Minor nit, but requires a rebuild of both world/kernel
980 "make check" behavior (made in ^/head@r295380) has been changed to
981 execute from a limited sandbox, as opposed to executing from
985 - The "beforecheck" and "aftercheck" targets are now specified.
986 - ${CHECKDIR} (added in commit noted above) has been removed.
987 - Legacy behavior can be enabled by setting
988 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
990 If the limited sandbox mode is enabled, "make check" will execute
991 "make distribution", then install, execute the tests, and clean up the
992 sandbox if successful.
994 The "make distribution" and "make install" targets are typically run as
995 root to set appropriate permissions and ownership at installation time.
996 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
997 environment if executing "make check" with limited sandbox mode using
998 an unprivileged user.
1001 Since the switch to GPT disk labels, fsck for UFS/FFS has been
1002 unable to automatically find alternate superblocks. As of r322297,
1003 the information needed to find alternate superblocks has been
1004 moved to the end of the area reserved for the boot block.
1005 Filesystems created with a newfs of this vintage or later
1006 will create the recovery information. If you have a filesystem
1007 created prior to this change and wish to have a recovery block
1008 created for your filesystem, you can do so by running fsck in
1009 foreground mode (i.e., do not use the -p or -y options). As it
1010 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
1011 to which you should answer yes.
1014 As of r321665, an NFSv4 server configuration that services
1015 Kerberos mounts or clients that do not support the uid/gid in
1016 owner/owner_group string capability, must explicitly enable
1017 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
1018 machine's /etc/rc.conf file.
1021 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
1022 Please see the 20141231 entry below for information about prerequisites
1023 and upgrading, if you are not already using clang 3.5.0 or higher.
1026 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
1027 r-commands (rlogin, rsh, etc.) to be built with the base system.
1030 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
1031 a very major ABI incompatible change, so users of FreeBSD/powerpc must
1032 be careful when performing source upgrades. It is best to run
1033 'make installworld' from an alternate root system, either a live
1034 CD/memory stick, or a temporary root partition. Additionally, all ports
1035 must be recompiled. powerpc64 is largely unaffected, except in the case
1036 of 32-bit compatibility. All 32-bit binaries will be affected.
1039 Forward compatibility for the "ino64" project have been committed. This
1040 will allow most new binaries to run on older kernels in a limited
1041 fashion. This prevents many of the common foot-shooting actions in the
1042 upgrade as well as the limited ability to roll back the kernel across
1043 the ino64 upgrade. Complicated use cases may not work properly, though
1044 enough simpler ones work to allow recovery in most situations.
1047 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
1048 if you require the GPL compiler.
1051 The internal ABI used for communication between the NFS kernel modules
1052 was changed by r320085, so __FreeBSD_version was bumped to
1053 ensure all the NFS related modules are updated together.
1056 The ABI of struct event was changed by extending the data
1057 member to 64bit and adding ext fields. For upgrade, same
1058 precautions as for the entry 20170523 "ino64" must be
1062 The GNU roff toolchain has been removed from base. To render manpages
1063 which are not supported by mandoc(1), man(1) can fallback on GNU roff
1064 from ports (and recommends to install it).
1065 To render roff(7) documents, consider using GNU roff from ports or the
1066 heirloom doctools roff toolchain from ports via pkg install groff or
1067 via pkg install heirloom-doctools.
1070 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
1071 smaller runtime footprint builds. This is useful for embedded systems
1072 which only require one chipset support.
1074 If you load it as a module, make sure this is in /boot/loader.conf:
1078 This will load the HAL, all chip/RF backends and if_ath_pci.
1079 If you have if_ath_pci in /boot/loader.conf, ensure it is after
1080 if_ath or it will not load any HAL chipset support.
1082 If you want to selectively load things (eg on ye cheape ARM/MIPS
1083 platforms where RAM is at a premium) you should:
1086 * load the chip modules in question
1087 * load ath_rate, ath_dfs
1089 * load if_ath_pci and/or if_ath_ahb depending upon your particular
1090 bus bind type - this is where probe/attach is done.
1092 For further comments/feedback, poke adrian@ .
1095 The "ino64" 64-bit inode project has been committed, which extends
1096 a number of types to 64 bits. Upgrading in place requires care and
1097 adherence to the documented upgrade procedure.
1099 If using a custom kernel configuration ensure that the
1100 COMPAT_FREEBSD11 option is included (as during the upgrade the
1101 system will be running the ino64 kernel with the existing world).
1103 For the safest in-place upgrade begin by removing previous build
1104 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full
1105 procedure documented below under the heading "To rebuild everything and
1106 install it on the current system." Specifically, a reboot is required
1107 after installing the new kernel before installing world. While an
1108 installworld normally works by accident from multiuser after rebooting
1109 the proper kernel, there are many cases where this will fail across this
1110 upgrade and installworld from single user is required.
1113 The NATM framework including the en(4), fatm(4), hatm(4), and
1114 patm(4) devices has been removed. Consumers should plan a
1115 migration before the end-of-life date for FreeBSD 11.
1118 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
1119 diff has not been implemented, if those are needed a newer version of
1120 GNU diff is available via the diffutils package under the gdiff name.
1123 As of r316810 for ipfilter, keep frags is no longer assumed when
1124 keep state is specified in a rule. r316810 aligns ipfilter with
1125 documentation in man pages separating keep frags from keep state.
1126 This allows keep state to be specified without forcing keep frags
1127 and allows keep frags to be specified independently of keep state.
1128 To maintain previous behaviour, also specify keep frags with
1129 keep state (as documented in ipf.conf.5).
1132 arm64 builds now use the base system LLD 4.0.0 linker by default,
1133 instead of requiring that the aarch64-binutils port or package be
1134 installed. To continue using aarch64-binutils, set
1135 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
1138 The UDP optimization in entry 20160818 that added the sysctl
1139 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
1140 packets will no longer be treated as L3 broadcast packets.
1143 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
1144 use any explicitly assigned loopback address available in the jail
1145 instead of using the first assigned address of the jail.
1148 The ctl.ko module no longer implements the iSCSI target frontend:
1149 cfiscsi.ko does instead.
1151 If building cfiscsi.ko as a kernel module, the module can be loaded
1152 via one of the following methods:
1153 - `cfiscsi_load="YES"` in loader.conf(5).
1154 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
1155 - ctladm(8)/ctld(8), when compiled with iSCSI support
1156 (`WITH_ISCSI=yes` in src.conf(5))
1158 Please see cfiscsi(4) for more details.
1161 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
1162 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
1163 same source (previously, the dependency of mmcsd.ko on mmc.ko was
1164 missing, but mmcsd.ko now will refuse to load if it is incompatible
1168 The syntax of ipfw(8) named states was changed to avoid ambiguity.
1169 If you have used named states in the firewall rules, you need to modify
1170 them after installworld and before rebooting. Now named states must
1171 be prefixed with colon.
1174 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
1175 removed as the userland we provide cannot use them. The KMS version
1176 (sys/dev/drm2) supports the same hardware.
1179 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
1180 Please see the 20141231 entry below for information about prerequisites
1181 and upgrading, if you are not already using clang 3.5.0 or higher.
1184 The code that provides support for ZFS .zfs/ directory functionality
1185 has been reimplemented. It's not possible now to create a snapshot
1186 by mkdir under .zfs/snapshot/. That should be the only user visible
1190 EISA bus support has been removed. The WITH_EISA option is no longer
1194 MCA bus support has been removed.
1197 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
1198 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
1201 The EM_MULTIQUEUE kernel configuration option is deprecated now that
1202 the em(4) driver conforms to iflib specifications.
1205 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
1206 IFLIB. If you have a custom kernel configuration that excludes em(4)
1207 but you use igb(4), you need to re-add em(4) to your custom
1211 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
1212 Please see the 20141231 entry below for information about prerequisites
1213 and upgrading, if you are not already using clang 3.5.0 or higher.
1216 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
1217 Please see the 20141231 entry below for information about prerequisites
1218 and upgrading, if you are not already using clang 3.5.0 or higher.
1221 The layout of the pmap structure has changed for powerpc to put the pmap
1222 statistics at the front for all CPU variations. libkvm(3) and all tools
1223 that link against it need to be recompiled.
1226 isl(4) and cyapa(4) drivers now require a new driver,
1227 chromebook_platform(4), to work properly on Chromebook-class hardware.
1228 On other types of hardware the drivers may need to be configured using
1229 device hints. Please see the corresponding manual pages for details.
1232 The urtwn(4) driver was merged into rtwn(4) and now consists of
1233 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
1235 Also, firmware for RTL8188CE was renamed due to possible name
1236 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
1239 GNU rcs has been removed from base. It is available as packages:
1240 - rcs: Latest GPLv3 GNU rcs version.
1241 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
1245 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
1246 modules now requires that the kernel configuration contain the
1247 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
1250 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
1251 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
1254 Relocatable object files with the extension of .So have been renamed
1255 to use an extension of .pico instead. The purpose of this change is
1256 to avoid a name clash with shared libraries on case-insensitive file
1257 systems. On those file systems, foo.So is the same file as foo.so.
1260 GNU rcs has been turned off by default. It can (temporarily) be built
1261 again by adding WITH_RCS knob in src.conf.
1262 Otherwise, GNU rcs is available from packages:
1263 - rcs: Latest GPLv3 GNU rcs version.
1264 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
1267 The backup_uses_rcs functionality has been removed from rc.subr.
1270 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
1271 two separate components, QUEUE_MACRO_DEBUG_TRACE and
1272 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
1273 QUEUE_MACRO_DEBUG behavior.
1276 r304787 changed some ioctl interfaces between the iSCSI userspace
1277 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1278 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1282 The UDP receive code has been updated to only treat incoming UDP
1283 packets that were addressed to an L2 broadcast address as L3
1284 broadcast packets. It is not expected that this will affect any
1285 standards-conforming UDP application. The new behaviour can be
1286 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1290 Remove the openbsd_poll system call.
1291 __FreeBSD_version has been bumped because of this.
1294 The stable/11 branch has been created from head@r302406.
1297 The libc stub for the pipe(2) system call has been replaced with
1298 a wrapper that calls the pipe2(2) system call and the pipe(2)
1299 system call is now only implemented by the kernels that include
1300 "options COMPAT_FREEBSD10" in their config file (this is the
1301 default). Users should ensure that this option is enabled in
1302 their kernel or upgrade userspace to r302092 before upgrading their
1306 CAM will now strip leading spaces from SCSI disks' serial numbers.
1307 This will affect users who create UFS filesystems on SCSI disks using
1308 those disk's diskid device nodes. For example, if /etc/fstab
1309 previously contained a line like
1310 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
1311 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
1312 transforms like gmirror may also be affected. ZFS users should
1316 The bitstring(3) API has been updated with new functionality and
1317 improved performance. But it is binary-incompatible with the old API.
1318 Objects built with the new headers may not be linked against objects
1319 built with the old headers.
1322 The brk and sbrk functions have been removed from libc on arm64.
1323 Binutils from ports has been updated to not link to these
1324 functions and should be updated to the latest version before
1325 installing a new libc.
1328 The armv6 port now defaults to hard float ABI. Limited support
1329 for running both hardfloat and soft float on the same system
1330 is available using the libraries installed with -DWITH_LIBSOFT.
1331 This has only been tested as an upgrade path for installworld
1332 and packages may fail or need manual intervention to run. New
1333 packages will be needed.
1335 To update an existing self-hosted armv6hf system, you must add
1336 TARGET_ARCH=armv6 on the make command line for both the build
1337 and the install steps.
1340 Kernel modules compiled outside of a kernel build now default to
1341 installing to /boot/modules instead of /boot/kernel. Many kernel
1342 modules built this way (such as those in ports) already overrode
1343 KMODDIR explicitly to install into /boot/modules. However,
1344 manually building and installing a module from /sys/modules will
1345 now install to /boot/modules instead of /boot/kernel.
1348 The CAM I/O scheduler has been committed to the kernel. There should be
1349 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1350 list of known rogues that claim support for this but actually corrupt
1351 data is believed to be complete, be on the lookout for data
1352 corruption. The known rogue list is believed to be complete:
1354 o Crucial MX100, M550 drives with MU01 firmware.
1355 o Micron M510 and M550 drives with MU01 firmware.
1356 o Micron M500 prior to MU07 firmware
1357 o Samsung 830, 840, and 850 all firmwares
1358 o FCCT M500 all firmwares
1360 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1361 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1362 updated firmware. Black listed drives will work correctly because these
1363 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1364 this list is the same as found in Linux, it's believed there are no
1365 other rogues in the market place. All other models from the above
1368 To be safe, if you are at all concerned, you can quirk each of your
1369 drives to prevent NCQ from being sent by setting:
1370 kern.cam.ada.X.quirks="0x2"
1371 in loader.conf. If the drive requires the 4k sector quirk, set the
1372 quirks entry to 0x3.
1375 The FAST_DEPEND build option has been removed and its functionality is
1376 now the one true way. The old mkdep(1) style of 'make depend' has
1377 been removed. See 20160311 for further details.
1380 Resource range types have grown from unsigned long to uintmax_t. All
1381 drivers, and anything using libdevinfo, need to be recompiled.
1384 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1385 builds. It no longer runs mkdep(1) during 'make depend', and the
1386 'make depend' stage can safely be skipped now as it is auto ran
1387 when building 'make all' and will generate all SRCS and DPSRCS before
1388 building anything else. Dependencies are gathered at compile time with
1389 -MF flags kept in separate .depend files per object file. Users should
1390 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1391 stale .depend files.
1394 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1395 kernel modules. Therefore, if you load any kernel modules at boot time,
1396 please install the boot loaders after you install the kernel, but before
1400 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1401 make installkernel KERNCONF=YOUR_KERNEL_HERE
1402 make -C sys/boot install
1403 <reboot in single user>
1405 Then follow the usual steps, described in the General Notes section,
1409 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1410 see the 20141231 entry below for information about prerequisites and
1411 upgrading, if you are not already using clang 3.5.0 or higher.
1414 The AIO subsystem is now a standard part of the kernel. The
1415 VFS_AIO kernel option and aio.ko kernel module have been removed.
1416 Due to stability concerns, asynchronous I/O requests are only
1417 permitted on sockets and raw disks by default. To enable
1418 asynchronous I/O requests on all file types, set the
1419 vfs.aio.enable_unsafe sysctl to a non-zero value.
1422 The ELF object manipulation tool objcopy is now provided by the
1423 ELF Tool Chain project rather than by GNU binutils. It should be a
1424 drop-in replacement, with the addition of arm64 support. The
1425 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1426 to obtain the GNU version if necessary.
1429 Building ZFS pools on top of zvols is prohibited by default. That
1430 feature has never worked safely; it's always been prone to deadlocks.
1431 Using a zvol as the backing store for a VM guest's virtual disk will
1432 still work, even if the guest is using ZFS. Legacy behavior can be
1433 restored by setting vfs.zfs.vol.recursive=1.
1436 The NONE and HPN patches has been removed from OpenSSH. They are
1437 still available in the security/openssh-portable port.
1440 With the addition of ypldap(8), a new _ypldap user is now required
1441 during installworld. "mergemaster -p" can be used to add the user
1442 prior to installworld, as documented in the handbook.
1445 The tftp loader (pxeboot) now uses the option root-path directive. As a
1446 consequence it no longer looks for a pxeboot.4th file on the tftp
1447 server. Instead it uses the regular /boot infrastructure as with the
1451 The code to start recording plug and play data into the modules has
1452 been committed. While the old tools will properly build a new kernel,
1453 a number of warnings about "unknown metadata record 4" will be produced
1454 for an older kldxref. To avoid such warnings, make sure to rebuild
1455 the kernel toolchain (or world). Make sure that you have r292078 or
1456 later when trying to build 292077 or later before rebuilding.
1459 Debug data files are now built by default with 'make buildworld' and
1460 installed with 'make installworld'. This facilitates debugging but
1461 requires more disk space both during the build and for the installed
1462 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1466 r291527 changed the internal interface between the nfsd.ko and
1467 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1468 __FreeBSD_version has been bumped because of this.
1471 Add support for unicode collation strings leads to a change of
1472 order of files listed by ls(1) for example. To get back to the old
1473 behaviour, set LC_COLLATE environment variable to "C".
1475 Databases administrators will need to reindex their databases given
1476 collation results will be different.
1478 Due to a bug in install(1) it is recommended to remove the ancient
1479 locales before running make installworld.
1481 rm -rf /usr/share/locale/*
1484 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1485 libcrypto.so.7 or libssl.so.7 must be recompiled.
1488 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1489 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1490 should be replaced with isp_2400 and isp_2500 modules respectively.
1493 The build previously allowed using 'make -n' to not recurse into
1494 sub-directories while showing what commands would be executed, and
1495 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1496 and 'make -N' will not.
1499 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1500 and etcupdate will now use this file. A custom sendmail.cf is now
1501 updated via this mechanism rather than via installworld. If you had
1502 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1503 want to remove the exclusion or change it to "always install".
1504 /etc/mail/sendmail.cf is now managed the same way regardless of
1505 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1506 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1509 Compatibility shims for legacy ATA device names have been removed.
1510 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1511 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1512 environment variables, /dev/ad* and /dev/ar* symbolic links.
1515 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1516 Please see the 20141231 entry below for information about prerequisites
1517 and upgrading, if you are not already using clang 3.5.0 or higher.
1520 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1521 and renamed from .symbols to .debug. This reduces the size requirements
1522 on the boot partition or file system and provides consistency with
1523 userland debug files.
1525 When using the supported kernel installation method the
1526 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1527 as is done with /boot/kernel.
1529 Developers wishing to maintain the historical behavior of installing
1530 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1533 The wireless drivers had undergone changes that remove the 'parent
1534 interface' from the ifconfig -l output. The rc.d network scripts
1535 used to check presence of a parent interface in the list, so old
1536 scripts would fail to start wireless networking. Thus, etcupdate(3)
1537 or mergemaster(8) run is required after kernel update, to update your
1538 rc.d scripts in /etc.
1541 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1542 These configurations are now automatically interpreted as
1543 'scrub fragment reassemble'.
1546 Kernel-loadable modules for the random(4) device are back. To use
1547 them, the kernel must have
1550 options RANDOM_LOADABLE
1552 kldload(8) can then be used to load random_fortuna.ko
1553 or random_yarrow.ko. Please note that due to the indirect
1554 function calls that the loadable modules need to provide,
1555 the build-in variants will be slightly more efficient.
1557 The random(4) kernel option RANDOM_DUMMY has been retired due to
1558 unpopularity. It was not all that useful anyway.
1561 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1562 Control over building the ELF Tool Chain tools is now provided by
1563 the WITHOUT_TOOLCHAIN knob.
1566 The polarity of Pulse Per Second (PPS) capture events with the
1567 uart(4) driver has been corrected. Prior to this change the PPS
1568 "assert" event corresponded to the trailing edge of a positive PPS
1569 pulse and the "clear" event was the leading edge of the next pulse.
1571 As the width of a PPS pulse in a typical GPS receiver is on the
1572 order of 1 millisecond, most users will not notice any significant
1573 difference with this change.
1575 Anyone who has compensated for the historical polarity reversal by
1576 configuring a negative offset equal to the pulse width will need to
1577 remove that workaround.
1580 The default group assigned to /dev/dri entries has been changed
1581 from 'wheel' to 'video' with the id of '44'. If you want to have
1582 access to the dri devices please add yourself to the video group
1585 # pw groupmod video -m $USER
1588 The menu.rc and loader.rc files will now be replaced during
1589 upgrades. Please migrate local changes to menu.rc.local and
1590 loader.rc.local instead.
1593 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1594 strings and strip have been removed. The src.conf(5) knob
1595 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1598 As ZFS requires more kernel stack pages than is the default on some
1599 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1600 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1602 Please consider using 'options KSTACK_PAGES=X' where X is greater
1603 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1606 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1607 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1608 default, i.e., they will not contain "::". For example, instead
1609 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1610 to have a more specific match, such as different map entries for
1611 IPv6:0:0 vs IPv6:0. This change requires that configuration
1612 data (including maps, files, classes, custom ruleset, etc.) must
1613 use the same format, so make certain such configuration data is
1614 upgrading. As a very simple check search for patterns like
1615 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1616 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1617 the cf option UseCompressedIPv6Addresses.
1620 The default kernel entropy-processing algorithm is now
1621 Fortuna, replacing Yarrow.
1623 Assuming you have 'device random' in your kernel config
1624 file, the configurations allow a kernel option to override
1625 this default. You may choose *ONE* of:
1627 options RANDOM_YARROW # Legacy /dev/random algorithm.
1628 options RANDOM_DUMMY # Blocking-only driver.
1630 If you have neither, you get Fortuna. For most people,
1631 read no further, Fortuna will give a /dev/random that works
1632 like it always used to, and the difference will be irrelevant.
1634 If you remove 'device random', you get *NO* kernel-processed
1635 entropy at all. This may be acceptable to folks building
1636 embedded systems, but has complications. Carry on reading,
1637 and it is assumed you know what you need.
1639 *PLEASE* read random(4) and random(9) if you are in the
1640 habit of tweaking kernel configs, and/or if you are a member
1641 of the embedded community, wanting specific and not-usual
1642 behaviour from your security subsystems.
1644 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1645 random', you will NOT have a functioning /dev/random, and
1646 many cryptographic features will not work, including SSH.
1647 You may also find strange behaviour from the random(3) set
1648 of library functions, in particular sranddev(3), srandomdev(3)
1649 and arc4random(3). The reason for this is that the KERN_ARND
1650 sysctl only returns entropy if it thinks it has some to
1651 share, and with RANDOM_DUMMY or no 'device random' this
1655 An additional fix for the issue described in the 20150614 sendmail
1656 entry below has been committed in revision 284717.
1659 FreeBSD's old make (fmake) has been removed from the system. It is
1660 available as the devel/fmake port or via pkg install fmake.
1663 The fix for the issue described in the 20150614 sendmail entry
1664 below has been committed in revision 284436. The work
1665 around described in that entry is no longer needed unless the
1666 default setting is overridden by a confDH_PARAMETERS configuration
1667 setting of '5' or pointing to a 512 bit DH parameter file.
1670 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1671 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1672 and devel/kyua to version 0.20+ and adjust any calling code to work
1673 with Kyuafile and kyua.
1676 The import of openssl to address the FreeBSD-SA-15:10.openssl
1677 security advisory includes a change which rejects handshakes
1678 with DH parameters below 768 bits. sendmail releases prior
1679 to 8.15.2 (not yet released), defaulted to a 512 bit
1680 DH parameter setting for client connections. To work around
1681 this interoperability, sendmail can be configured to use a
1682 2048 bit DH parameter by:
1684 1. Edit /etc/mail/`hostname`.mc
1685 2. If a setting for confDH_PARAMETERS does not exist or
1686 exists and is set to a string beginning with '5',
1687 replace it with '2'.
1688 3. If a setting for confDH_PARAMETERS exists and is set to
1689 a file path, create a new file with:
1690 openssl dhparam -out /path/to/file 2048
1691 4. Rebuild the .cf file:
1692 cd /etc/mail/; make; make install
1693 5. Restart sendmail:
1694 cd /etc/mail/; make restart
1696 A sendmail patch is coming, at which time this file will be
1700 Generation of legacy formatted entries have been disabled by default
1701 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1702 entries were converted to use the new format by default when the new,
1703 machine independent format have been added and supported since FreeBSD
1706 Please see the pwd_mkdb(8) manual page for further details.
1709 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1710 20141231 entry below for information about prerequisites and upgrading,
1711 if you are not already using 3.5.0 or higher.
1714 TI platform code switched to using vendor DTS files and this update
1715 may break existing systems running on Beaglebone, Beaglebone Black,
1718 - dtb files should be regenerated/reinstalled. Filenames are the
1719 same but content is different now
1720 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1721 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1722 addressing scheme is now pin 25 on /dev/gpioc3.
1723 - Pandaboard: /etc/ttys should be updated, serial console device is
1724 now /dev/ttyu2, not /dev/ttyu0
1727 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1728 If you need the GNU extension from groff soelim(1), install groff
1729 from package: pkg install groff, or via ports: textproc/groff.
1732 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1733 defined in symlink(7); previously symlinks were silently ignored.
1736 The const qualifier has been removed from iconv(3) to comply with
1737 POSIX. The ports tree is aware of this from r384038 onwards.
1740 Libraries specified by LIBADD in Makefiles must have a corresponding
1741 DPADD_<lib> variable to ensure correct dependencies. This is now
1742 enforced in src.libnames.mk.
1745 From legacy ata(4) driver was removed support for SATA controllers
1746 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1747 Kernel modules ataahci and ataadaptec were removed completely,
1748 replaced by ahci and mvs modules respectively.
1751 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1752 the 20141231 entry below for information about prerequisites and
1753 upgrading, if you are not already using 3.5.0 or higher.
1756 The 32-bit PowerPC kernel has been changed to a position-independent
1757 executable. This can only be booted with a version of loader(8)
1758 newer than January 31, 2015, so make sure to update both world and
1759 kernel before rebooting.
1762 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1763 but before r278950, the RNG was not seeded properly. Immediately
1764 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1765 ssh keys or openssl keys) that were generated w/ a kernel from that
1766 range. This does not affect programs that directly used /dev/random
1767 or /dev/urandom. All userland uses of arc4random(3) are affected.
1770 The autofs(4) ABI was changed in order to restore binary compatibility
1771 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1772 with the new kernel.
1775 The powerpc64 kernel has been changed to a position-independent
1776 executable. This can only be booted with a new version of loader(8),
1777 so make sure to update both world and kernel before rebooting.
1780 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1781 only release, no new features have been added. Please see the 20141231
1782 entry below for information about prerequisites and upgrading, if you
1783 are not already using 3.5.0.
1786 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1787 taken from the ELF Tool Chain project rather than GNU binutils. They
1788 should be drop-in replacements, with the addition of arm64 support.
1789 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1790 binutils tools, if necessary. See 20150805 for updated information.
1793 The default Unbound configuration now enables remote control
1794 using a local socket. Users who have already enabled the
1795 local_unbound service should regenerate their configuration
1796 by running "service local_unbound setup" as root.
1799 The GNU texinfo and GNU info pages have been removed.
1800 To be able to view GNU info pages please install texinfo from ports.
1803 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1805 As of this release, a prerequisite for building clang, llvm and lldb is
1806 a C++11 capable compiler and C++11 standard library. This means that to
1807 be able to successfully build the cross-tools stage of buildworld, with
1808 clang as the bootstrap compiler, your system compiler or cross compiler
1809 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1810 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1813 On any standard FreeBSD 10.x or 11.x installation, where clang and
1814 libc++ are on by default (that is, on x86 or arm), this should work out
1817 On 9.x installations where clang is enabled by default, e.g. on x86 and
1818 powerpc, libc++ will not be enabled by default, so libc++ should be
1819 built (with clang) and installed first. If both clang and libc++ are
1820 missing, build clang first, then use it to build libc++.
1822 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1823 the instructions for 9.x above.
1825 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1826 default, and do not build clang.
1828 Many embedded systems are resource constrained, and will not be able to
1829 build clang in a reasonable time, or in some cases at all. In those
1830 cases, cross building bootable systems on amd64 is a workaround.
1832 This new version of clang introduces a number of new warnings, of which
1833 the following are most likely to appear:
1837 This warns in two cases, for both C and C++:
1838 * When the code is trying to take the absolute value of an unsigned
1839 quantity, which is effectively a no-op, and almost never what was
1840 intended. The code should be fixed, if at all possible. If you are
1841 sure that the unsigned quantity can be safely cast to signed, without
1842 loss of information or undefined behavior, you can add an explicit
1843 cast, or disable the warning.
1845 * When the code is trying to take an absolute value, but the called
1846 abs() variant is for the wrong type, which can lead to truncation.
1847 If you want to disable the warning instead of fixing the code, please
1848 make sure that truncation will not occur, or it might lead to unwanted
1851 -Wtautological-undefined-compare and
1852 -Wundefined-bool-conversion
1854 These warn when C++ code is trying to compare 'this' against NULL, while
1855 'this' should never be NULL in well-defined C++ code. However, there is
1856 some legacy (pre C++11) code out there, which actively abuses this
1857 feature, which was less strictly defined in previous C++ versions.
1859 Squid and openjdk do this, for example. The warning can be turned off
1860 for C++98 and earlier, but compiling the code in C++11 mode might result
1861 in unexpected behavior; for example, the parts of the program that are
1862 unreachable could be optimized away.
1865 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1866 kernel sources have been removed. The .h files remain, since some
1867 utilities include them. This will need to be fixed later.
1868 If "mount -t oldnfs ..." is attempted, it will fail.
1869 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1870 the utilities will report errors.
1873 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1874 directories to top level SUBDIR variable when their parent
1875 directory is included in LOCAL_DIRS. Users with build systems with
1876 such hierarchies and without SUBDIR entries in the parent
1877 directory Makefiles should add them or add the directories to
1881 faith(4) and faithd(8) have been removed from the base system. Faith
1882 has been obsolete for a very long time.
1885 vt(4), the new console driver, is enabled by default. It brings
1886 support for Unicode and double-width characters, as well as
1887 support for UEFI and integration with the KMS kernel video
1890 You may need to update your console settings in /etc/rc.conf,
1891 most probably the keymap. During boot, /etc/rc.d/syscons will
1892 indicate what you need to do.
1894 vt(4) still has issues and lacks some features compared to
1895 syscons(4). See the wiki for up-to-date information:
1896 https://wiki.freebsd.org/Newcons
1898 If you want to keep using syscons(4), you can do so by adding
1899 the following line to /boot/loader.conf:
1903 pjdfstest has been integrated into kyua as an opt-in test suite.
1904 Please see share/doc/pjdfstest/README for more details on how to
1908 gperf has been removed from the base system for architectures
1909 that use clang. Ports that require gperf will obtain it from the
1913 pjdfstest has been moved from tools/regression/pjdfstest to
1917 At svn r271982, The default linux compat kernel ABI has been adjusted
1918 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1919 update. If you wish to continue using the linux-f10 compat ports,
1920 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1921 encouraged to update their linux-compat packages to linux-c6 during
1922 their next update cycle.
1925 The ofwfb driver, used to provide a graphics console on PowerPC when
1926 using vt(4), no longer allows mmap() of all physical memory. This
1927 will prevent Xorg on PowerPC with some ATI graphics cards from
1928 initializing properly unless x11-servers/xorg-server is updated to
1932 The xdev targets have been converted to using TARGET and
1933 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1936 The default unbound configuration has been modified to address
1937 issues with reverse lookups on networks that use private
1938 address ranges. If you use the local_unbound service, run
1939 "service local_unbound setup" as root to regenerate your
1940 configuration, then "service local_unbound reload" to load the
1944 The GNU texinfo and GNU info pages are not built and installed
1945 anymore, WITH_INFO knob has been added to allow to built and install
1947 UPDATE: see 20150102 entry on texinfo's removal
1950 The GNU readline library is now an INTERNALLIB - that is, it is
1951 statically linked into consumers (GDB and variants) in the base
1952 system, and the shared library is no longer installed. The
1953 devel/readline port is available for third party software that
1957 The Itanium architecture (ia64) has been removed from the list of
1958 known architectures. This is the first step in the removal of the
1962 Commit r268115 has added NFSv4.1 server support, merged from
1963 projects/nfsv4.1-server. Since this includes changes to the
1964 internal interfaces between the NFS related modules, a full
1965 build of the kernel and modules will be necessary.
1966 __FreeBSD_version has been bumped.
1969 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1970 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1971 which differs from the behaviour controlled by this knob.)
1974 Maximal length of the serial number in CTL was increased from 16 to
1975 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1976 and ctld, need to be rebuilt to work with a new kernel.
1979 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1980 1 respectively to match the upstream numbers. They were out of
1981 sync because, when they were originally added to FreeBSD, the
1982 upstream versions were not respected. These libraries are private
1983 and not yet built by default, so renumbering them should be a
1984 non-issue. However, unclean source trees will yield broken test
1985 programs once the operator executes "make delete-old-libs" after a
1986 "make installworld".
1988 Additionally, the atf-sh binary was made private by moving it into
1989 /usr/libexec/. Already-built shell test programs will keep the
1990 path to the old binary so they will break after "make delete-old"
1993 If you are using WITH_TESTS=yes (not the default), wipe the object
1994 tree and rebuild from scratch to prevent spurious test failures.
1995 This is only needed once: the misnumbered libraries and misplaced
1996 binaries have been added to OptionalObsoleteFiles.inc so they will
1997 be removed during a clean upgrade.
2000 Clang and llvm have been upgraded to 3.4.1 release.
2003 We bogusly installed src.opts.mk in /usr/share/mk. This file should
2004 be removed to avoid issues in the future (and has been added to
2008 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
2009 past, it affected all builds that used the bsd.*.mk files. The old
2010 behavior was a bug, but people may have relied upon it. To get this
2011 behavior back, you can .include /etc/src.conf from /etc/make.conf
2012 (which is still global and isn't changed). This also changes the
2013 behavior of incremental builds inside the tree of individual
2014 directories. Set MAKESYSPATH to ".../share/mk" to do that.
2015 Although this has survived make universe and some upgrade scenarios,
2016 other upgrade scenarios may have broken. At least one form of
2017 temporary breakage was fixed with MAKESYSPATH settings for buildworld
2018 as well... In cases where MAKESYSPATH isn't working with this
2019 setting, you'll need to set it to the full path to your tree.
2021 One side effect of all this cleaning up is that bsd.compiler.mk
2022 is no longer implicitly included by bsd.own.mk. If you wish to
2023 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
2027 The lindev device has been removed since /dev/full has been made a
2028 standard device. __FreeBSD_version has been bumped.
2031 The knob WITHOUT_VI was added to the base system, which controls
2032 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
2033 in order to reorder files share/termcap and didn't build ex(1) as a
2034 build tool, so building/installing with WITH_VI is highly advised for
2035 build hosts for older releases.
2037 This issue has been fixed in stable/9 and stable/10 in r277022 and
2038 r276991, respectively.
2041 The YES_HESIOD knob has been removed. It has been obsolete for
2042 a decade. Please move to using WITH_HESIOD instead or your builds
2043 will silently lack HESIOD.
2046 The uart(4) driver has been changed with respect to its handling
2047 of the low-level console. Previously the uart(4) driver prevented
2048 any process from changing the baudrate or the CLOCAL and HUPCL
2049 control flags. By removing the restrictions, operators can make
2050 changes to the serial console port without having to reboot.
2051 However, when getty(8) is started on the serial device that is
2052 associated with the low-level console, a misconfigured terminal
2053 line in /etc/ttys will now have a real impact.
2054 Before upgrading the kernel, make sure that /etc/ttys has the
2055 serial console device configured as 3wire without baudrate to
2056 preserve the previous behaviour. E.g:
2057 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
2060 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
2061 to improve performance. To re-enable it, if needed, run rpcbind
2062 with command line option -W.
2065 Switched back to the GPL dtc compiler due to updates in the upstream
2066 dts files not being supported by the BSDL dtc compiler. You will need
2067 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
2068 may result while building dtb files during a kernel build if you fail
2069 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
2072 Clang and llvm have been upgraded to 3.4 release.
2075 The nve(4) driver has been removed. Please use the nfe(4) driver
2076 for NVIDIA nForce MCP Ethernet adapters instead.
2079 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
2080 This could cause certain C++ applications using shared libraries built
2081 against the previous version of libc++ to crash. The incompatibility
2082 has now been fixed, but any C++ applications or shared libraries built
2083 between r261283 and r261801 should be recompiled.
2086 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
2087 capability mode support. Please note that enabling the feature in
2088 kernel is still highly recommended.
2091 OpenSSH is now built with sandbox support, and will use sandbox as
2092 the default privilege separation method. This requires Capsicum
2093 capability mode support in kernel.
2096 The libelf and libdwarf libraries have been updated to newer
2097 versions from upstream. Shared library version numbers for
2098 these two libraries were bumped. Any ports or binaries
2099 requiring these two libraries should be recompiled.
2100 __FreeBSD_version is bumped to 1100006.
2103 If a Makefile in a tests/ directory was auto-generating a Kyuafile
2104 instead of providing an explicit one, this would prevent such
2105 Makefile from providing its own Kyuafile in the future during
2106 NO_CLEAN builds. This has been fixed in the Makefiles but manual
2107 intervention is needed to clean an objdir if you use NO_CLEAN:
2108 # find /usr/obj -name Kyuafile | xargs rm -f
2111 The behavior of gss_pseudo_random() for the krb5 mechanism
2112 has changed, for applications requesting a longer random string
2113 than produced by the underlying enctype's pseudo-random() function.
2114 In particular, the random string produced from a session key of
2115 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
2116 be different at the 17th octet and later, after this change.
2117 The counter used in the PRF+ construction is now encoded as a
2118 big-endian integer in accordance with RFC 4402.
2119 __FreeBSD_version is bumped to 1100004.
2122 The WITHOUT_ATF build knob has been removed and its functionality
2123 has been subsumed into the more generic WITHOUT_TESTS. If you were
2124 using the former to disable the build of the ATF libraries, you
2125 should change your settings to use the latter.
2128 The default version of mtree is nmtree which is obtained from
2129 NetBSD. The output is generally the same, but may vary
2130 slightly. If you found you need identical output adding
2131 "-F freebsd9" to the command line should do the trick. For the
2132 time being, the old mtree is available as fmtree.
2135 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
2136 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
2137 1.1.4_8 and verify bsdyml not linked in, before running "make
2139 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
2141 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
2144 The stable/10 branch has been created in subversion from head
2151 Sometimes, obscure build problems are the result of environment
2152 poisoning. This can happen because the make utility reads its
2153 environment when searching for values for global variables. To run
2154 your build attempts in an "environmental clean room", prefix all make
2155 commands with 'env -i '. See the env(1) manual page for more details.
2156 Occasionally a build failure will occur with "make -j" due to a race
2157 condition. If this happens try building again without -j, and please
2158 report a bug if it happens consistently.
2160 When upgrading from one major version to another it is generally best to
2161 upgrade to the latest code in the currently installed branch first, then
2162 do an upgrade to the new branch. This is the best-tested upgrade path,
2163 and has the highest probability of being successful. Please try this
2164 approach if you encounter problems with a major version upgrade. Since
2165 the stable 4.x branch point, one has generally been able to upgrade from
2166 anywhere in the most recent stable branch to head / current (or even the
2167 last couple of stable branches). See the top of this file when there's
2170 The update process will emit an error on an attempt to perform a build
2171 or install from a FreeBSD version below the earliest supported version.
2172 When updating from an older version the update should be performed one
2173 major release at a time, including running `make delete-old` at each
2176 When upgrading a live system, having a root shell around before
2177 installing anything can help undo problems. Not having a root shell
2178 around can lead to problems if pam has changed too much from your
2179 starting point to allow continued authentication after the upgrade.
2181 This file should be read as a log of events. When a later event changes
2182 information of a prior event, the prior event should not be deleted.
2183 Instead, a pointer to the entry with the new information should be
2184 placed in the old entry. Readers of this file should also sanity check
2185 older entries before relying on them blindly. Authors of new entries
2186 should write them with this in mind.
2190 When upgrading the boot ZFS pool to a new version, always follow
2193 1.) recompile and reinstall the ZFS boot loader and boot block
2194 (this is part of "make buildworld" and "make installworld")
2196 2.) update the ZFS boot block on your boot drive
2198 The following example updates the ZFS boot block on the first
2199 partition (freebsd-boot) of a GPT partitioned drive ada0:
2200 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
2202 Non-boot pools do not need these updates.
2206 If you are updating from a prior version of FreeBSD (even one just
2207 a few days old), you should follow this procedure. It is the most
2208 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2210 make kernel-toolchain
2211 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2212 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2214 To test a kernel once
2215 ---------------------
2216 If you just want to boot a kernel once (because you are not sure
2217 if it works, or if you want to boot a known bad kernel to provide
2218 debugging information) run
2219 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2220 nextboot -k testkernel
2222 To rebuild everything and install it on the current system.
2223 -----------------------------------------------------------
2224 # Note: sometimes if you are running current you gotta do more than
2225 # is listed here if you are upgrading from a really old current.
2227 <make sure you have good level 0 dumps>
2229 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2230 make installkernel KERNCONF=YOUR_KERNEL_HERE
2232 <reboot in single user> [3]
2239 To cross-install current onto a separate partition
2240 --------------------------------------------------
2241 # In this approach we use a separate partition to hold
2242 # current's root, 'usr', and 'var' directories. A partition
2243 # holding "/", "/usr" and "/var" should be about 2GB in
2246 <make sure you have good level 0 dumps>
2249 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2250 <maybe newfs current's root partition>
2251 <mount current's root partition on directory ${CURRENT_ROOT}>
2252 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
2253 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2254 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2255 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2256 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2257 <reboot into current>
2258 <do a "native" rebuild/install as described in the previous section>
2259 <maybe install compatibility libraries from ports/misc/compat*>
2263 To upgrade in-place from stable to current
2264 ----------------------------------------------
2265 <make sure you have good level 0 dumps>
2267 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
2268 make installkernel KERNCONF=YOUR_KERNEL_HERE
2270 <reboot in single user> [3]
2277 Make sure that you've read the UPDATING file to understand the
2278 tweaks to various things you need. At this point in the life
2279 cycle of current, things change often and you are on your own
2280 to cope. The defaults can also change, so please read ALL of
2281 the UPDATING entries.
2283 Also, if you are tracking -current, you must be subscribed to
2284 freebsd-current@freebsd.org. Make sure that before you update
2285 your sources that you have read and understood all the recent
2286 messages there. If in doubt, please track -stable which has
2287 much fewer pitfalls.
2289 [1] If you have third party modules, such as vmware, you
2290 should disable them at this point so they don't crash your
2293 [3] From the bootblocks, boot -s, and then do
2297 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed
2298 cd src # full path to source
2299 adjkerntz -i # if CMOS is wall time
2300 Also, when doing a major release upgrade, it is required that
2301 you boot into single user mode to do the installworld.
2303 [4] Note: This step is non-optional. Failure to do this step
2304 can result in a significant reduction in the functionality of the
2305 system. Attempting to do it by hand is not recommended and those
2306 that pursue this avenue should read this file carefully, as well
2307 as the archives of freebsd-current and freebsd-hackers mailing lists
2308 for potential gotchas. The -U option is also useful to consider.
2309 See mergemaster(8) for more information.
2311 [5] Usually this step is a no-op. However, from time to time
2312 you may need to do this if you get unknown user in the following
2313 step. It never hurts to do it all the time. You may need to
2314 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2315 install) after the buildworld before this step if you last updated
2316 from current before 20130425 or from -stable before 20130430.
2318 [6] This only deletes old files and directories. Old libraries
2319 can be deleted by "make delete-old-libs", but you have to make
2320 sure that no program is using those libraries anymore.
2322 [8] The new kernel must be able to run existing binaries used by an
2323 installworld. When upgrading across major versions, the new kernel's
2324 configuration must include the correct COMPAT_FREEBSD<n> option for
2325 existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure
2326 to do so may leave you with a system that is hard to boot to recover. A
2327 GENERIC kernel will include suitable compatibility options to run
2328 binaries from older branches. Note that the ability to run binaries
2329 from unsupported branches is not guaranteed.
2331 Make sure that you merge any new devices from GENERIC since the
2332 last time you updated your kernel config file. Options also
2333 change over time, so you may need to adjust your custom kernels
2336 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2337 "?=" instead of the "=" assignment operator, so that buildworld can
2338 override the CPUTYPE if it needs to.
2340 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2341 not on the command line, or in /etc/make.conf. buildworld will
2342 warn if it is improperly defined.
2345 This file contains a list, in reverse chronological order, of major
2346 breakages in tracking -current. It is not guaranteed to be a complete
2347 list of such breakages, and only contains entries since September 23, 2011.
2348 If you need to see UPDATING entries from before that date, you will need
2349 to fetch an UPDATING file from an older FreeBSD release.
2351 Copyright information:
2353 Copyright 1998-2009 M. Warner Losh <imp@FreeBSD.org>
2355 Redistribution, publication, translation and use, with or without
2356 modification, in full or in part, in any form or format of this
2357 document are permitted without further permission from the author.
2359 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2360 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2361 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2362 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2363 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2364 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2365 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2366 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2367 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2368 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2369 POSSIBILITY OF SUCH DAMAGE.
2371 Contact Warner Losh if you have any questions about your use of