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 MALLOC_PRODUCTION in /etc/make.conf, or to merely
26 disable the most expensive debugging functionality run
27 "ln -s 'abort:false,junk:false' /etc/malloc.conf".)
30 Clang/LLVM is now the default compiler and LLD the default
34 make universe no longer uses GCC 4.2.1 on any architectures.
35 Architectures not supported by in-tree Clang/LLVM require an
36 external toolchain package.
39 GCC 4.2.1 is now not built by default, as part of the GCC 4.2.1
40 retirement plan. Specifically, the GCC, GCC_BOOTSTRAP, and GNUCXX
41 options default to off for all supported CPU architectures. As a
42 short-term transition aid they may be enabled via WITH_* options.
43 GCC 4.2.1 is expected to be removed from the tree on 2020-03-31.
46 Support for armv5 has been disconnected and is being removed. The
47 machine combination MACHINE=arm MACHINE_ARCH=arm is no longer valid.
48 You must now use a MACHINE_ARCH of armv6 or armv7. The default
49 MACHINE_ARCH for MACHINE=arm is now armv7.
52 Clang/LLVM is now the default compiler for all powerpc architectures.
53 LLD is now the default linker for powerpc64. The change for powerpc64
54 also includes a change to the ELFv2 ABI, incompatible with the existing
58 Kernel-loadable random(4) modules are no longer unloadable.
61 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
62 been upgraded to 9.0.1. Please see the 20141231 entry below for
63 information about prerequisites and upgrading, if you are not already
64 using clang 3.5.0 or higher.
67 r355677 has modified the internal interface used between the
68 NFS modules in the kernel. As such, they must all be upgraded
69 simultaneously. I will do a version bump for this.
72 The root certificates of the Mozilla CA Certificate Store have been
73 imported into the base system and can be managed with the certctl(8)
74 utility. If you have installed the security/ca_root_nss port or package
75 with the ETCSYMLINK option (the default), be advised that there may be
76 differences between those included in the port and those included in
77 base due to differences in nss branch used as well as general update
78 frequency. Note also that certctl(8) cannot manage certs in the
79 format used by the security/ca_root_nss port.
82 The amd(8) automount daemon has been disabled by default, and will be
83 removed in the future. As of FreeBSD 10.1 the autofs(5) is available
87 The nctgpio and wbwd drivers have been moved to the superio bus.
88 If you have one of these drivers in a kernel configuration, then
89 you should add device superio to it. If you use one of these drivers
90 as a module and you compile a custom set of modules, then you should
91 add superio to the set.
94 KPIs for network drivers to access interface addresses have changed.
95 Users need to recompile NIC driver modules together with kernel.
98 The net.link.tap.user_open sysctl no longer prevents user opening of
99 already created /dev/tapNN devices. Access is still controlled by
100 node permissions, just like tun devices. The net.link.tap.user_open
101 sysctl is now used only to allow users to perform devfs cloning of
102 tap devices, and the subsequent open may not succeed if the user is not
103 in the appropriate group. This sysctl may be deprecated/removed
104 completely in the future.
107 mips, powerpc, and sparc64 are no longer built as part of
108 universe / tinderbox unless MAKE_OBSOLETE_GCC is defined. If
109 not defined, mips, powerpc, and sparc64 builds will look for
110 the xtoolchain binaries and if installed use them for universe
111 builds. As llvm 9.0 becomes vetted for these architectures, they
112 will be removed from the list.
115 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
116 been upgraded to 9.0.0. Please see the 20141231 entry below for
117 information about prerequisites and upgrading, if you are not already
118 using clang 3.5.0 or higher.
121 The hpt27xx, hptmv, hptnr, and hptrr drivers have been removed from
122 GENERIC. They are available as modules and can be loaded by adding
123 to /boot/loader.conf hpt27xx_load="YES", hptmv_load="YES",
124 hptnr_load="YES", or hptrr_load="YES", respectively.
127 ntpd no longer by default locks its pages in memory, allowing them
128 to be paged out by the kernel. Use rlimit memlock to restore
129 historic BSD behaviour. For example, add "rlimit memlock 32"
130 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
133 Several of ping6's options have been renamed for better consistency
134 with ping. If you use any of -ARWXaghmrtwx, you must update your
135 scripts. See ping6(8) for details.
138 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
139 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
140 been removed from mount_fusefs(8). You can safely remove them from
141 your scripts, because they had no effect.
143 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
144 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
145 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
146 sysctls have been removed. If you felt the need to set any of them to
147 a non-default value, please tell asomers@FreeBSD.org why.
150 Default permissions on the /var/account/acct file (and copies of it
151 rotated by periodic daily scripts) are changed from 0644 to 0640
152 because the file contains sensitive information that should not be
153 world-readable. If the /var/account directory must be created by
154 rc.d/accounting, the mode used is now 0750. Admins who use the
155 accounting feature are encouraged to change the mode of an existing
156 /var/account directory to 0750 or 0700.
159 Entropy collection and the /dev/random device are no longer optional
160 components. The "device random" option has been removed.
161 Implementations of distilling algorithms can still be made loadable
162 with "options RANDOM_LOADABLE" (e.g., random_fortuna.ko).
165 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
166 been upgraded to 8.0.1. Please see the 20141231 entry below for
167 information about prerequisites and upgrading, if you are not already
168 using clang 3.5.0 or higher.
171 A fix was applied to i386 kernel modules to avoid panics with
172 dpcpu or vnet. Users need to recompile i386 kernel modules
173 having pcpu or vnet sections or they will refuse to load.
176 User-wired pages now have their own counter,
177 vm.stats.vm.v_user_wire_count. The vm.max_wired sysctl was renamed
178 to vm.max_user_wired and changed from an unsigned int to an unsigned
179 long. bhyve VMs wired with the -S are now subject to the user
180 wiring limit; the vm.max_user_wired sysctl may need to be tuned to
181 avoid running into the limit.
184 The IPSEC option has been removed from GENERIC. Users requiring
185 ipsec(4) must now load the ipsec(4) kernel module.
188 The tap(4) driver has been folded into tun(4), and the module has been
189 renamed to tuntap. You should update any kld_list="if_tap" or
190 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
191 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
192 module instead, and "device tap" or "device tun" entries in kernel
193 config files to select the tuntap device instead.
196 The following knobs have been added related to tradeoffs between
197 safe use of the random device and availability in the absence of
200 kern.random.initial_seeding.bypass_before_seeding: tunable; set
201 non-zero to bypass the random device prior to seeding, or zero to
202 block random requests until the random device is initially seeded.
203 For now, set to 1 (unsafe) by default to restore pre-r346250 boot
204 availability properties.
206 kern.random.initial_seeding.read_random_bypassed_before_seeding:
207 read-only diagnostic sysctl that is set when bypass is enabled and
208 read_random(9) is bypassed, to enable programmatic handling of this
209 initial condition, if desired.
211 kern.random.initial_seeding.arc4random_bypassed_before_seeding:
212 Similar to the above, but for for arc4random(9) initial seeding.
214 kern.random.initial_seeding.disable_bypass_warnings: tunable; set
215 non-zero to disable warnings in dmesg when the same conditions are
216 met as for the diagnostic sysctls above. Defaults to zero, i.e.,
217 produce warnings in dmesg when the conditions are met.
220 The loadable random module KPI has changed; the random_infra_init()
221 routine now requires a 3rd function pointer for a bool (*)(void)
222 method that returns true if the random device is seeded (and
223 therefore unblocked).
226 r345895 reverts r320698. This implies that an nfsuserd(8) daemon
227 built from head sources between r320757 (July 6, 2017) and
228 r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
229 is added to the command line.
230 nfsuserd daemons built from head sources that are post-r338192 are
231 not affected and should continue to work.
234 The fuse(4) module has been renamed to fusefs(4) for consistency with
235 other filesystems. You should update any kld_load="fuse" entries in
236 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
237 "options FUSE" entries in kernel config files.
240 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
241 8.0.0. Please see the 20141231 entry below for information about
242 prerequisites and upgrading, if you are not already using clang 3.5.0
246 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
247 compiled into your custom kernel, add 'device xz' statement to the
251 drm and drm2 have been removed from the tree. Please see
252 https://wiki.freebsd.org/Graphics for the latest information on
253 migrating to the drm ports.
256 Iflib is no longer unconditionally compiled into the kernel. Drivers
257 using iflib and statically compiled into the kernel, now require
258 the 'device iflib' config option. For the same drivers loaded as
259 modules on kernels not having 'device iflib', the iflib.ko module
260 is loaded automatically.
263 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
264 options no longer exist since r343219 and r343427 respectively;
265 nothing uses them, so they should be just removed from custom
269 r342635 changes the way efibootmgr(8) works by requiring users to add
270 the -b (bootnum) parameter for commands where the bootnum was previously
271 specified with each option. For example 'efibootmgr -B 0001' is now
272 'efibootmgr -B -b 0001'.
275 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
276 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
277 servers that have vfs.nfsd.nfs_privport set will only allow mounts
278 from clients using a reserved port#. Since both the FreeBSD and Linux
279 NFSv4 clients use reserved port#s by default, this should not affect
283 The XLP config has been removed. We can't support 64-bit atomics in this
284 kernel because it is running in 32-bit mode. XLP users must transition
285 to running a 64-bit kernel (XLP64 or XLPN32).
287 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
288 the preferred emulator today and we don't need two different ones.
290 The old sibyte / swarm / Broadcom BCM1250 support has been
291 removed from the mips port.
294 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
295 7.0.1. Please see the 20141231 entry below for information about
296 prerequisites and upgrading, if you are not already using clang 3.5.0
300 Remove the timed and netdate programs from the base tree. Setting
301 the time with these daemons has been obsolete for over a decade.
304 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
305 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
306 it produces broken binaries when ifuncs are in use. Users needing
307 GNU ld should install the binutils port or package.
310 The BSD crtbegin and crtend code has been enabled by default. It has
311 had extensive testing on amd64, arm64, and i386. It can be disabled
312 by building a world with -DWITHOUT_BSD_CRTBEGIN.
315 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
316 has been converted to a port (misc/ctm) and will be removed from
317 FreeBSD-13. It is available as a package (ctm) for all supported
321 The default newsyslog.conf(5) file has been changed to only include
322 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
323 the filenames end in '.conf' and do not begin with a '.'.
325 You should check the configuration files in these two directories match
326 this naming convention. You can verify which configuration files are
327 being included using the command:
331 Ports for the DRM modules have been simplified. Now, amd64 users should
332 just install the drm-kmod port. All others should install
335 Graphics hardware that's newer than about 2010 usually works with
336 drm-kmod. For hardware older than 2013, however, some users will need
337 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
338 than 2008 usually only works in drm-legacy-kmod. The graphics team can
339 only commit to hardware made since 2013 due to the complexity of the
340 market and difficulty to test all the older cards effectively. If you
341 have hardware supported by drm-kmod, you are strongly encouraged to use
342 that as you will get better support.
344 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
345 elsewhere, the drm and drm2 modules will be eliminated from the src base
346 soon (with a limited exception for arm). Please update to the package
347 asap and report any issues to x11@freebsd.org.
349 Generally, anybody using the drm*-kmod packages should add
350 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
351 cross-threading surprises, especially with automatic driver
352 loading from X11 startup. These will become the defaults in 13-current
356 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
357 custom kernel and module loading configuration files must be updated
358 accordingly. Moreover, interfaces previous presented as ixlvN to the
359 system are now exposed as iavfN and network configuration files must
360 be adjusted as necessary.
363 OpenSSL has been updated to version 1.1.1. This update included
364 additional various API changes throughout the base system. It is
365 important to rebuild third-party software after upgrading. The value
366 of __FreeBSD_version has been bumped accordingly.
369 The legacy DRM modules and drivers have now been added to the loader's
370 module blacklist, in favor of loading them with kld_list in rc.conf(5).
371 The module blacklist may be overridden with the loader.conf(5)
372 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
376 The cam(4) based nda(4) driver will be used over nvd(4) by default on
377 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
378 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
379 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
383 Reproducible build mode is now on by default, in preparation for
384 FreeBSD 12.0. This eliminates build metadata such as the user,
385 host, and time from the kernel (and uname), unless the working tree
386 corresponds to a modified checkout from a version control system.
387 The previous behavior can be obtained by setting the /etc/src.conf
388 knob WITHOUT_REPRODUCIBLE_BUILD.
391 The Yarrow CSPRNG has been removed from the kernel as it has not been
392 supported by its designers since at least 2003. Fortuna has been the
393 default since FreeBSD-11.
396 devctl freeze/thaw have gone into the tree, the rc scripts have been
397 updated to use them and devmatch has been changed. You should update
398 kernel, userland and rc scripts all at the same time.
401 The default interpreter has been switched from 4th to Lua.
402 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
403 interpreter. If you have custom FORTH code you will need to set
404 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
405 src.conf for the build. This will create default hard links between
406 loader and loader_4th instead of loader and loader_lua, the new default.
407 If you are using UEFI it will create the proper hard link to loader.efi.
409 bhyve uses userboot.so. It remains 4th-only until some issues are solved
410 regarding coexisting with multiple versions of FreeBSD are resolved.
413 ls(1) now respects the COLORTERM environment variable used in other
414 systems and software to indicate that a colored terminal is both
415 supported and desired. If ls(1) is suddenly emitting colors, they may
416 be disabled again by either removing the unwanted COLORTERM from your
417 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
418 may not be observed in a future release.
421 The default pager for most commands has been changed to "less". To
422 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
426 The jedec_ts(4) driver has been removed. A superset of its functionality
427 is available in the jedec_dimm(4) driver, and the manpage for that
428 driver includes migration instructions. If you have "device jedec_ts"
429 in your kernel configuration file, it must be removed.
432 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
433 This should have no effect if the kernel is booted via BIOS/legacy boot.
434 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
435 has a buggy firmware that prevents a successful boot due to use of
439 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
440 support has been removed from the tree. These ports were
441 obsolete and/or known to be broken for many years.
444 loader.efi has been augmented to participate more fully in the
445 UEFI boot manager protocol. loader.efi will now look at the
446 BootXXXX environment variable to determine if a specific kernel
447 or root partition was specified. XXXX is derived from BootCurrent.
448 efibootmgr(8) manages these standard UEFI variables.
451 zfsloader's functionality has now been folded into loader.
452 zfsloader is no longer necessary once you've updated your
453 boot blocks. For a transition period, we will install a
454 hardlink for zfsloader to loader to allow a smooth transition
455 until the boot blocks can be updated (hard link because old
456 zfs boot blocks don't understand symlinks).
459 ARM64 now have efifb support, if you want to have serial console
460 on your arm64 board when an screen is connected and the bootloader
461 setup a frame buffer for us to use, just add :
465 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
466 an screen connected as the firmware will setup a frame buffer are that
467 u-boot will expose as an EFI frame buffer.
470 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
471 or take steps to update /etc/passwd before doing installworld on
472 existing systems. Do not skip the "mergemaster -Fp" step before
473 installworld, as described in the update procedures near the bottom
474 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
475 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
476 the ntp config file contain options that change file/dir locations.
477 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
478 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
479 taking steps to ensure that all required files/dirs are accessible
483 Big endian arm support has been removed.
486 The static environment setup in kernel configs is no longer mutually
487 exclusive with the loader(8) environment by default. In order to
488 restore the previous default behavior of disabling the loader(8)
489 environment if a static environment is present, you must specify
490 loader_env.disabled=1 in the static environment.
493 The ABI of syscalls used by management tools like sockstat and
494 netstat has been broken to allow 32-bit binaries to work on
495 64-bit kernels without modification. These programs will need
496 to match the kernel in order to function. External programs may
497 require minor modifications to accommodate a change of type in
498 structures from pointers to 64-bit virtual addresses.
501 On i386 and amd64 atomics are now inlined. Out of tree modules using
502 atomics will need to be rebuilt.
505 The '%I' format in the kern.corefile sysctl limits the number of
506 core files that a process can generate to the number stored in the
507 debug.ncores sysctl. The '%I' format is replaced by the single digit
508 index. Previously, if all indexes were taken the kernel would overwrite
509 only a core file with the highest index in a filename.
510 Currently the system will create a new core file if there is a free
511 index or if all slots are taken it will overwrite the oldest one.
514 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
515 6.0.1. Please see the 20141231 entry below for information about
516 prerequisites and upgrading, if you are not already using clang 3.5.0
520 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
521 needed to be changed to work with it. This change was made with r335763
522 and requires a mergemaster / etcupdate / etc to update the installed
526 r334930 changed the interface between the NFS modules, so they all
527 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
530 As of r334391 lld is the default amd64 system linker; it is installed
531 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
535 The kernel / userland interface for devinfo changed, so you'll
536 need a new kernel and userland as a pair for it to work (rebuilding
537 lib/libdevinfo is all that's required). devinfo and devmatch will
538 not work, but everything else will when there's a mismatch.
541 The on-disk format for hwpmc callchain records has changed to include
542 threadid corresponding to a given record. This changes the field offsets
543 and thus requires that libpmcstat be rebuilt before using a kernel
547 The vxge(4) driver has been removed. This driver was introduced into
548 HEAD one week before the Exar left the Ethernet market and is not
549 known to be used. If you have device vxge in your kernel config file
553 The amd64 kernel now requires a ld that supports ifunc to produce a
554 working kernel, either lld or a newer binutils. lld is built by default
555 on amd64, and the 'buildkernel' target uses it automatically. However,
556 it is not the default linker, so building the kernel the traditional
557 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
558 binutils port/package). lld will soon be default, and this requirement
561 NOTE: As of r334391 lld is the default system linker on amd64, and no
562 workaround is necessary.
565 The nxge(4) driver has been removed. This driver was for PCI-X 10g
566 cards made by s2io/Neterion. The company was acquired by Exar and
567 no longer sells or supports Ethernet products. If you have device
568 nxge in your kernel config file it must be removed.
571 The tz database (tzdb) has been updated to 2018e. This version more
572 correctly models time stamps in time zones with negative DST such as
573 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
574 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
575 time zone abbreviations and the tm_isdst flag.
578 The ixgb(4) driver has been removed. This driver was for an early and
579 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
580 quickly shifted to the long lived ixgbe family. If you have device
581 ixgb in your kernel config file it must be removed.
584 The lmc(4) driver has been removed. This was a WAN interface
585 card that was already reportedly rare in 2003, and had an ambiguous
586 license. If you have device lmc in your kernel config file it must
590 Support for Arcnet networks has been removed. If you have device
591 arcnet or device cm in your kernel config file they must be
595 Support for FDDI networks has been removed. If you have device
596 fddi or device fpa in your kernel config file they must be
600 In addition to supporting RFC 3164 formatted messages, the
601 syslogd(8) service is now capable of parsing RFC 5424 formatted
602 log messages. The main benefit of using RFC 5424 is that clients
603 may now send log messages with timestamps containing year numbers,
604 microseconds and time zone offsets.
606 Similarly, the syslog(3) C library function has been altered to
607 send RFC 5424 formatted messages to the local system logging
608 daemon. On systems using syslogd(8), this change should have no
609 negative impact, as long as syslogd(8) and the C library are
610 updated at the same time. On systems using a different system
611 logging daemon, it may be necessary to make configuration
612 adjustments, depending on the software used.
614 When using syslog-ng, add the 'syslog-protocol' flag to local
615 input sources to enable parsing of RFC 5424 formatted messages:
618 unix-dgram("/var/run/log" flags(syslog-protocol));
621 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
622 of the 'imuxsock' module to let messages be processed by the
623 regular RFC 3164/5424 parsing pipeline:
625 module(load="imuxsock" SysSock.UseSpecialParser="off")
627 Do note that these changes only affect communication between local
628 applications and syslogd(8). The format that syslogd(8) uses to
629 store messages on disk or forward messages to other systems
630 remains unchanged. syslogd(8) still uses RFC 3164 for these
631 purposes. Options to customize this behaviour will be added in the
632 future. Utilities that process log files stored in /var/log are
633 thus expected to continue to function as before.
635 __FreeBSD_version has been incremented to 1200061 to denote this
639 Support for token ring networks has been removed. If you
640 have "device token" in your kernel config you should remove
641 it. No device drivers supported token ring.
644 makefs was modified to be able to tag ISO9660 El Torito boot catalog
645 entries as EFI instead of overloading the i386 tag as done previously.
646 The amd64 mkisoimages.sh script used to build amd64 ISO images for
647 release was updated to use this. This may mean that makefs must be
648 updated before "make cdrom" can be run in the release directory. This
649 should be as simple as:
651 $ cd $SRCDIR/usr.sbin/makefs
652 $ make depend all install
655 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
656 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
657 Co-existence for the transition period will come shortly. Booting is a
658 complex environment and test coverage for Lua-enabled loaders has been
659 thin, so it would be prudent to assume it might not work and make
660 provisions for backup boot methods.
663 devmatch functionality has been turned on in devd. It will automatically
664 load drivers for unattached devices. This may cause unexpected drivers
665 to be loaded. Please report any problems to current@ and
669 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
670 6.0.0. Please see the 20141231 entry below for information about
671 prerequisites and upgrading, if you are not already using clang 3.5.0
675 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
676 This means it is used to link the kernel and userland libraries and
677 executables, but is not yet installed as /usr/bin/ld by default.
679 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
680 WITHOUT_LLD_BOOTSTRAP=yes
683 On i386, pmtimer has been removed. Its functionality has been folded
684 into apm. It was a no-op on ACPI in current for a while now (but was
685 still needed on i386 in FreeBSD 11 and earlier). Users may need to
686 remove it from kernel config files.
689 The use of RSS hash from the network card aka flowid has been
690 disabled by default for lagg(4) as it's currently incompatible with
691 the lacp and loadbalance protocols.
693 This can be re-enabled by setting the following in loader.conf:
694 net.link.lagg.default_use_flowid="1"
697 The SW_WATCHDOG option is no longer necessary to enable the
698 hardclock-based software watchdog if no hardware watchdog is
699 configured. As before, SW_WATCHDOG will cause the software
700 watchdog to be enabled even if a hardware watchdog is configured.
703 r326887 fixes the issue described in the 20171214 UPDATING entry.
704 r326888 flips the switch back to building GELI support always.
707 r362593 broke ZFS + GELI support for reasons unknown. However,
708 it also broke ZFS support generally, so GELI has been turned off
709 by default as the lesser evil in r326857. If you boot off ZFS and/or
710 GELI, it might not be a good time to update.
713 PowerPC users must update loader(8) by rebuilding world before
714 installing a new kernel, as the protocol connecting them has
715 changed. Without the update, loader metadata will not be passed
716 successfully to the kernel and users will have to enter their
717 root partition at the kernel mountroot prompt to continue booting.
718 Newer versions of loader can boot old kernels without issue.
721 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
722 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
723 to WITH/OUT_LOADER_GELI.
726 The naive and non-compliant support of posix_fallocate(2) in ZFS
727 has been removed as of r325320. The system call now returns EINVAL
728 when used on a ZFS file. Although the new behavior complies with the
729 standard, some consumers are not prepared to cope with it.
730 One known victim is lld prior to r325420.
733 Building in a FreeBSD src checkout will automatically create object
734 directories now rather than store files in the current directory if
735 'make obj' was not ran. Calling 'make obj' is no longer necessary.
736 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
737 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
741 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
742 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
743 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
744 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
745 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
746 The UNIFIED_OBJDIR option is a transitional feature that will be
747 removed for 12.0 release; please migrate to the new format for any
748 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
749 than hardcoding paths.
752 The native-xtools target no longer installs the files by default to the
753 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
754 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
757 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
758 options are changing from controlling the build if defined / undefined
759 to controlling the build with explicit 'yes' or 'no' values. They will
760 shift to WITH/WITHOUT options to match other options in the system.
763 libstand has turned into a private library for sys/boot use only.
764 It is no longer supported as a public interface outside of sys/boot.
767 The arm port has split armv6 into armv6 and armv7. armv7 is now
768 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
769 and are running a kernel from before r324363, you will need to add
770 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
773 When building multiple kernels using KERNCONF, non-existent KERNCONF
774 files will produce an error and buildkernel will fail. Previously
775 missing KERNCONF files silently failed giving no indication as to
776 why, only to subsequently discover during installkernel that the
777 desired kernel was never built in the first place.
780 The default serial number format for CTL LUNs has changed. This will
781 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
782 or iSCSI clients care about their LUNs' serial numbers. Users who
783 require serial number stability should hardcode serial numbers in
787 For 32-bit arm compiled for hard-float support, soft-floating point
788 binaries now always get their shared libraries from
789 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
790 /usr/libsoft also existed). Only users with a hard-float ld.so, but
791 soft-float everything else should be affected.
794 The geli password typed at boot is now hidden. To restore the previous
795 behavior, see geli(8) for configuration options.
798 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
799 sysctl values. Minor nit, but requires a rebuild of both world/kernel
803 "make check" behavior (made in ^/head@r295380) has been changed to
804 execute from a limited sandbox, as opposed to executing from
808 - The "beforecheck" and "aftercheck" targets are now specified.
809 - ${CHECKDIR} (added in commit noted above) has been removed.
810 - Legacy behavior can be enabled by setting
811 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
813 If the limited sandbox mode is enabled, "make check" will execute
814 "make distribution", then install, execute the tests, and clean up the
815 sandbox if successful.
817 The "make distribution" and "make install" targets are typically run as
818 root to set appropriate permissions and ownership at installation time.
819 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
820 environment if executing "make check" with limited sandbox mode using
821 an unprivileged user.
824 Since the switch to GPT disk labels, fsck for UFS/FFS has been
825 unable to automatically find alternate superblocks. As of r322297,
826 the information needed to find alternate superblocks has been
827 moved to the end of the area reserved for the boot block.
828 Filesystems created with a newfs of this vintage or later
829 will create the recovery information. If you have a filesystem
830 created prior to this change and wish to have a recovery block
831 created for your filesystem, you can do so by running fsck in
832 foreground mode (i.e., do not use the -p or -y options). As it
833 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
834 to which you should answer yes.
837 As of r321665, an NFSv4 server configuration that services
838 Kerberos mounts or clients that do not support the uid/gid in
839 owner/owner_group string capability, must explicitly enable
840 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
841 machine's /etc/rc.conf file.
844 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
845 Please see the 20141231 entry below for information about prerequisites
846 and upgrading, if you are not already using clang 3.5.0 or higher.
849 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
850 r-commands (rlogin, rsh, etc.) to be built with the base system.
853 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
854 a very major ABI incompatible change, so users of FreeBSD/powerpc must
855 be careful when performing source upgrades. It is best to run
856 'make installworld' from an alternate root system, either a live
857 CD/memory stick, or a temporary root partition. Additionally, all ports
858 must be recompiled. powerpc64 is largely unaffected, except in the case
859 of 32-bit compatibility. All 32-bit binaries will be affected.
862 Forward compatibility for the "ino64" project have been committed. This
863 will allow most new binaries to run on older kernels in a limited
864 fashion. This prevents many of the common foot-shooting actions in the
865 upgrade as well as the limited ability to roll back the kernel across
866 the ino64 upgrade. Complicated use cases may not work properly, though
867 enough simpler ones work to allow recovery in most situations.
870 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
871 if you require the GPL compiler.
874 The internal ABI used for communication between the NFS kernel modules
875 was changed by r320085, so __FreeBSD_version was bumped to
876 ensure all the NFS related modules are updated together.
879 The ABI of struct event was changed by extending the data
880 member to 64bit and adding ext fields. For upgrade, same
881 precautions as for the entry 20170523 "ino64" must be
885 The GNU roff toolchain has been removed from base. To render manpages
886 which are not supported by mandoc(1), man(1) can fallback on GNU roff
887 from ports (and recommends to install it).
888 To render roff(7) documents, consider using GNU roff from ports or the
889 heirloom doctools roff toolchain from ports via pkg install groff or
890 via pkg install heirloom-doctools.
893 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
894 smaller runtime footprint builds. This is useful for embedded systems
895 which only require one chipset support.
897 If you load it as a module, make sure this is in /boot/loader.conf:
901 This will load the HAL, all chip/RF backends and if_ath_pci.
902 If you have if_ath_pci in /boot/loader.conf, ensure it is after
903 if_ath or it will not load any HAL chipset support.
905 If you want to selectively load things (eg on ye cheape ARM/MIPS
906 platforms where RAM is at a premium) you should:
909 * load the chip modules in question
910 * load ath_rate, ath_dfs
912 * load if_ath_pci and/or if_ath_ahb depending upon your particular
913 bus bind type - this is where probe/attach is done.
915 For further comments/feedback, poke adrian@ .
918 The "ino64" 64-bit inode project has been committed, which extends
919 a number of types to 64 bits. Upgrading in place requires care and
920 adherence to the documented upgrade procedure.
922 If using a custom kernel configuration ensure that the
923 COMPAT_FREEBSD11 option is included (as during the upgrade the
924 system will be running the ino64 kernel with the existing world).
926 For the safest in-place upgrade begin by removing previous build
927 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full
928 procedure documented below under the heading "To rebuild everything and
929 install it on the current system." Specifically, a reboot is required
930 after installing the new kernel before installing world. While an
931 installworld normally works by accident from multiuser after rebooting
932 the proper kernel, there are many cases where this will fail across this
933 upgrade and installworld from single user is required.
936 The NATM framework including the en(4), fatm(4), hatm(4), and
937 patm(4) devices has been removed. Consumers should plan a
938 migration before the end-of-life date for FreeBSD 11.
941 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
942 diff has not been implemented, if those are needed a newer version of
943 GNU diff is available via the diffutils package under the gdiff name.
946 As of r316810 for ipfilter, keep frags is no longer assumed when
947 keep state is specified in a rule. r316810 aligns ipfilter with
948 documentation in man pages separating keep frags from keep state.
949 This allows keep state to be specified without forcing keep frags
950 and allows keep frags to be specified independently of keep state.
951 To maintain previous behaviour, also specify keep frags with
952 keep state (as documented in ipf.conf.5).
955 arm64 builds now use the base system LLD 4.0.0 linker by default,
956 instead of requiring that the aarch64-binutils port or package be
957 installed. To continue using aarch64-binutils, set
958 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
961 The UDP optimization in entry 20160818 that added the sysctl
962 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
963 packets will no longer be treated as L3 broadcast packets.
966 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
967 use any explicitly assigned loopback address available in the jail
968 instead of using the first assigned address of the jail.
971 The ctl.ko module no longer implements the iSCSI target frontend:
972 cfiscsi.ko does instead.
974 If building cfiscsi.ko as a kernel module, the module can be loaded
975 via one of the following methods:
976 - `cfiscsi_load="YES"` in loader.conf(5).
977 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
978 - ctladm(8)/ctld(8), when compiled with iSCSI support
979 (`WITH_ISCSI=yes` in src.conf(5))
981 Please see cfiscsi(4) for more details.
984 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
985 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
986 same source (previously, the dependency of mmcsd.ko on mmc.ko was
987 missing, but mmcsd.ko now will refuse to load if it is incompatible
991 The syntax of ipfw(8) named states was changed to avoid ambiguity.
992 If you have used named states in the firewall rules, you need to modify
993 them after installworld and before rebooting. Now named states must
994 be prefixed with colon.
997 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
998 removed as the userland we provide cannot use them. The KMS version
999 (sys/dev/drm2) supports the same hardware.
1002 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
1003 Please see the 20141231 entry below for information about prerequisites
1004 and upgrading, if you are not already using clang 3.5.0 or higher.
1007 The code that provides support for ZFS .zfs/ directory functionality
1008 has been reimplemented. It's not possible now to create a snapshot
1009 by mkdir under .zfs/snapshot/. That should be the only user visible
1013 EISA bus support has been removed. The WITH_EISA option is no longer
1017 MCA bus support has been removed.
1020 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
1021 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
1024 The EM_MULTIQUEUE kernel configuration option is deprecated now that
1025 the em(4) driver conforms to iflib specifications.
1028 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
1029 IFLIB. If you have a custom kernel configuration that excludes em(4)
1030 but you use igb(4), you need to re-add em(4) to your custom
1034 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
1035 Please see the 20141231 entry below for information about prerequisites
1036 and upgrading, if you are not already using clang 3.5.0 or higher.
1039 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
1040 Please see the 20141231 entry below for information about prerequisites
1041 and upgrading, if you are not already using clang 3.5.0 or higher.
1044 The layout of the pmap structure has changed for powerpc to put the pmap
1045 statistics at the front for all CPU variations. libkvm(3) and all tools
1046 that link against it need to be recompiled.
1049 isl(4) and cyapa(4) drivers now require a new driver,
1050 chromebook_platform(4), to work properly on Chromebook-class hardware.
1051 On other types of hardware the drivers may need to be configured using
1052 device hints. Please see the corresponding manual pages for details.
1055 The urtwn(4) driver was merged into rtwn(4) and now consists of
1056 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
1058 Also, firmware for RTL8188CE was renamed due to possible name
1059 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
1062 GNU rcs has been removed from base. It is available as packages:
1063 - rcs: Latest GPLv3 GNU rcs version.
1064 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
1068 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
1069 modules now requires that the kernel configuration contain the
1070 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
1073 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
1074 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
1077 Relocatable object files with the extension of .So have been renamed
1078 to use an extension of .pico instead. The purpose of this change is
1079 to avoid a name clash with shared libraries on case-insensitive file
1080 systems. On those file systems, foo.So is the same file as foo.so.
1083 GNU rcs has been turned off by default. It can (temporarily) be built
1084 again by adding WITH_RCS knob in src.conf.
1085 Otherwise, GNU rcs is available from packages:
1086 - rcs: Latest GPLv3 GNU rcs version.
1087 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
1090 The backup_uses_rcs functionality has been removed from rc.subr.
1093 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
1094 two separate components, QUEUE_MACRO_DEBUG_TRACE and
1095 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
1096 QUEUE_MACRO_DEBUG behavior.
1099 r304787 changed some ioctl interfaces between the iSCSI userspace
1100 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1101 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1105 The UDP receive code has been updated to only treat incoming UDP
1106 packets that were addressed to an L2 broadcast address as L3
1107 broadcast packets. It is not expected that this will affect any
1108 standards-conforming UDP application. The new behaviour can be
1109 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1113 Remove the openbsd_poll system call.
1114 __FreeBSD_version has been bumped because of this.
1117 The stable/11 branch has been created from head@r302406.
1120 The libc stub for the pipe(2) system call has been replaced with
1121 a wrapper that calls the pipe2(2) system call and the pipe(2)
1122 system call is now only implemented by the kernels that include
1123 "options COMPAT_FREEBSD10" in their config file (this is the
1124 default). Users should ensure that this option is enabled in
1125 their kernel or upgrade userspace to r302092 before upgrading their
1129 CAM will now strip leading spaces from SCSI disks' serial numbers.
1130 This will affect users who create UFS filesystems on SCSI disks using
1131 those disk's diskid device nodes. For example, if /etc/fstab
1132 previously contained a line like
1133 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
1134 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
1135 transforms like gmirror may also be affected. ZFS users should
1139 The bitstring(3) API has been updated with new functionality and
1140 improved performance. But it is binary-incompatible with the old API.
1141 Objects built with the new headers may not be linked against objects
1142 built with the old headers.
1145 The brk and sbrk functions have been removed from libc on arm64.
1146 Binutils from ports has been updated to not link to these
1147 functions and should be updated to the latest version before
1148 installing a new libc.
1151 The armv6 port now defaults to hard float ABI. Limited support
1152 for running both hardfloat and soft float on the same system
1153 is available using the libraries installed with -DWITH_LIBSOFT.
1154 This has only been tested as an upgrade path for installworld
1155 and packages may fail or need manual intervention to run. New
1156 packages will be needed.
1158 To update an existing self-hosted armv6hf system, you must add
1159 TARGET_ARCH=armv6 on the make command line for both the build
1160 and the install steps.
1163 Kernel modules compiled outside of a kernel build now default to
1164 installing to /boot/modules instead of /boot/kernel. Many kernel
1165 modules built this way (such as those in ports) already overrode
1166 KMODDIR explicitly to install into /boot/modules. However,
1167 manually building and installing a module from /sys/modules will
1168 now install to /boot/modules instead of /boot/kernel.
1171 The CAM I/O scheduler has been committed to the kernel. There should be
1172 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1173 list of known rogues that claim support for this but actually corrupt
1174 data is believed to be complete, be on the lookout for data
1175 corruption. The known rogue list is believed to be complete:
1177 o Crucial MX100, M550 drives with MU01 firmware.
1178 o Micron M510 and M550 drives with MU01 firmware.
1179 o Micron M500 prior to MU07 firmware
1180 o Samsung 830, 840, and 850 all firmwares
1181 o FCCT M500 all firmwares
1183 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1184 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1185 updated firmware. Black listed drives will work correctly because these
1186 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1187 this list is the same as found in Linux, it's believed there are no
1188 other rogues in the market place. All other models from the above
1191 To be safe, if you are at all concerned, you can quirk each of your
1192 drives to prevent NCQ from being sent by setting:
1193 kern.cam.ada.X.quirks="0x2"
1194 in loader.conf. If the drive requires the 4k sector quirk, set the
1195 quirks entry to 0x3.
1198 The FAST_DEPEND build option has been removed and its functionality is
1199 now the one true way. The old mkdep(1) style of 'make depend' has
1200 been removed. See 20160311 for further details.
1203 Resource range types have grown from unsigned long to uintmax_t. All
1204 drivers, and anything using libdevinfo, need to be recompiled.
1207 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1208 builds. It no longer runs mkdep(1) during 'make depend', and the
1209 'make depend' stage can safely be skipped now as it is auto ran
1210 when building 'make all' and will generate all SRCS and DPSRCS before
1211 building anything else. Dependencies are gathered at compile time with
1212 -MF flags kept in separate .depend files per object file. Users should
1213 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1214 stale .depend files.
1217 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1218 kernel modules. Therefore, if you load any kernel modules at boot time,
1219 please install the boot loaders after you install the kernel, but before
1223 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1224 make installkernel KERNCONF=YOUR_KERNEL_HERE
1225 make -C sys/boot install
1226 <reboot in single user>
1228 Then follow the usual steps, described in the General Notes section,
1232 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1233 see the 20141231 entry below for information about prerequisites and
1234 upgrading, if you are not already using clang 3.5.0 or higher.
1237 The AIO subsystem is now a standard part of the kernel. The
1238 VFS_AIO kernel option and aio.ko kernel module have been removed.
1239 Due to stability concerns, asynchronous I/O requests are only
1240 permitted on sockets and raw disks by default. To enable
1241 asynchronous I/O requests on all file types, set the
1242 vfs.aio.enable_unsafe sysctl to a non-zero value.
1245 The ELF object manipulation tool objcopy is now provided by the
1246 ELF Tool Chain project rather than by GNU binutils. It should be a
1247 drop-in replacement, with the addition of arm64 support. The
1248 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1249 to obtain the GNU version if necessary.
1252 Building ZFS pools on top of zvols is prohibited by default. That
1253 feature has never worked safely; it's always been prone to deadlocks.
1254 Using a zvol as the backing store for a VM guest's virtual disk will
1255 still work, even if the guest is using ZFS. Legacy behavior can be
1256 restored by setting vfs.zfs.vol.recursive=1.
1259 The NONE and HPN patches has been removed from OpenSSH. They are
1260 still available in the security/openssh-portable port.
1263 With the addition of ypldap(8), a new _ypldap user is now required
1264 during installworld. "mergemaster -p" can be used to add the user
1265 prior to installworld, as documented in the handbook.
1268 The tftp loader (pxeboot) now uses the option root-path directive. As a
1269 consequence it no longer looks for a pxeboot.4th file on the tftp
1270 server. Instead it uses the regular /boot infrastructure as with the
1274 The code to start recording plug and play data into the modules has
1275 been committed. While the old tools will properly build a new kernel,
1276 a number of warnings about "unknown metadata record 4" will be produced
1277 for an older kldxref. To avoid such warnings, make sure to rebuild
1278 the kernel toolchain (or world). Make sure that you have r292078 or
1279 later when trying to build 292077 or later before rebuilding.
1282 Debug data files are now built by default with 'make buildworld' and
1283 installed with 'make installworld'. This facilitates debugging but
1284 requires more disk space both during the build and for the installed
1285 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1289 r291527 changed the internal interface between the nfsd.ko and
1290 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1291 __FreeBSD_version has been bumped because of this.
1294 Add support for unicode collation strings leads to a change of
1295 order of files listed by ls(1) for example. To get back to the old
1296 behaviour, set LC_COLLATE environment variable to "C".
1298 Databases administrators will need to reindex their databases given
1299 collation results will be different.
1301 Due to a bug in install(1) it is recommended to remove the ancient
1302 locales before running make installworld.
1304 rm -rf /usr/share/locale/*
1307 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1308 libcrypto.so.7 or libssl.so.7 must be recompiled.
1311 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1312 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1313 should be replaced with isp_2400 and isp_2500 modules respectively.
1316 The build previously allowed using 'make -n' to not recurse into
1317 sub-directories while showing what commands would be executed, and
1318 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1319 and 'make -N' will not.
1322 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1323 and etcupdate will now use this file. A custom sendmail.cf is now
1324 updated via this mechanism rather than via installworld. If you had
1325 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1326 want to remove the exclusion or change it to "always install".
1327 /etc/mail/sendmail.cf is now managed the same way regardless of
1328 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1329 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1332 Compatibility shims for legacy ATA device names have been removed.
1333 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1334 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1335 environment variables, /dev/ad* and /dev/ar* symbolic links.
1338 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1339 Please see the 20141231 entry below for information about prerequisites
1340 and upgrading, if you are not already using clang 3.5.0 or higher.
1343 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1344 and renamed from .symbols to .debug. This reduces the size requirements
1345 on the boot partition or file system and provides consistency with
1346 userland debug files.
1348 When using the supported kernel installation method the
1349 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1350 as is done with /boot/kernel.
1352 Developers wishing to maintain the historical behavior of installing
1353 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1356 The wireless drivers had undergone changes that remove the 'parent
1357 interface' from the ifconfig -l output. The rc.d network scripts
1358 used to check presence of a parent interface in the list, so old
1359 scripts would fail to start wireless networking. Thus, etcupdate(3)
1360 or mergemaster(8) run is required after kernel update, to update your
1361 rc.d scripts in /etc.
1364 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1365 These configurations are now automatically interpreted as
1366 'scrub fragment reassemble'.
1369 Kernel-loadable modules for the random(4) device are back. To use
1370 them, the kernel must have
1373 options RANDOM_LOADABLE
1375 kldload(8) can then be used to load random_fortuna.ko
1376 or random_yarrow.ko. Please note that due to the indirect
1377 function calls that the loadable modules need to provide,
1378 the build-in variants will be slightly more efficient.
1380 The random(4) kernel option RANDOM_DUMMY has been retired due to
1381 unpopularity. It was not all that useful anyway.
1384 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1385 Control over building the ELF Tool Chain tools is now provided by
1386 the WITHOUT_TOOLCHAIN knob.
1389 The polarity of Pulse Per Second (PPS) capture events with the
1390 uart(4) driver has been corrected. Prior to this change the PPS
1391 "assert" event corresponded to the trailing edge of a positive PPS
1392 pulse and the "clear" event was the leading edge of the next pulse.
1394 As the width of a PPS pulse in a typical GPS receiver is on the
1395 order of 1 millisecond, most users will not notice any significant
1396 difference with this change.
1398 Anyone who has compensated for the historical polarity reversal by
1399 configuring a negative offset equal to the pulse width will need to
1400 remove that workaround.
1403 The default group assigned to /dev/dri entries has been changed
1404 from 'wheel' to 'video' with the id of '44'. If you want to have
1405 access to the dri devices please add yourself to the video group
1408 # pw groupmod video -m $USER
1411 The menu.rc and loader.rc files will now be replaced during
1412 upgrades. Please migrate local changes to menu.rc.local and
1413 loader.rc.local instead.
1416 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1417 strings and strip have been removed. The src.conf(5) knob
1418 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1421 As ZFS requires more kernel stack pages than is the default on some
1422 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1423 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1425 Please consider using 'options KSTACK_PAGES=X' where X is greater
1426 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1429 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1430 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1431 default, i.e., they will not contain "::". For example, instead
1432 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1433 to have a more specific match, such as different map entries for
1434 IPv6:0:0 vs IPv6:0. This change requires that configuration
1435 data (including maps, files, classes, custom ruleset, etc.) must
1436 use the same format, so make certain such configuration data is
1437 upgrading. As a very simple check search for patterns like
1438 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1439 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1440 the cf option UseCompressedIPv6Addresses.
1443 The default kernel entropy-processing algorithm is now
1444 Fortuna, replacing Yarrow.
1446 Assuming you have 'device random' in your kernel config
1447 file, the configurations allow a kernel option to override
1448 this default. You may choose *ONE* of:
1450 options RANDOM_YARROW # Legacy /dev/random algorithm.
1451 options RANDOM_DUMMY # Blocking-only driver.
1453 If you have neither, you get Fortuna. For most people,
1454 read no further, Fortuna will give a /dev/random that works
1455 like it always used to, and the difference will be irrelevant.
1457 If you remove 'device random', you get *NO* kernel-processed
1458 entropy at all. This may be acceptable to folks building
1459 embedded systems, but has complications. Carry on reading,
1460 and it is assumed you know what you need.
1462 *PLEASE* read random(4) and random(9) if you are in the
1463 habit of tweaking kernel configs, and/or if you are a member
1464 of the embedded community, wanting specific and not-usual
1465 behaviour from your security subsystems.
1467 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1468 random', you will NOT have a functioning /dev/random, and
1469 many cryptographic features will not work, including SSH.
1470 You may also find strange behaviour from the random(3) set
1471 of library functions, in particular sranddev(3), srandomdev(3)
1472 and arc4random(3). The reason for this is that the KERN_ARND
1473 sysctl only returns entropy if it thinks it has some to
1474 share, and with RANDOM_DUMMY or no 'device random' this
1478 An additional fix for the issue described in the 20150614 sendmail
1479 entry below has been committed in revision 284717.
1482 FreeBSD's old make (fmake) has been removed from the system. It is
1483 available as the devel/fmake port or via pkg install fmake.
1486 The fix for the issue described in the 20150614 sendmail entry
1487 below has been committed in revision 284436. The work
1488 around described in that entry is no longer needed unless the
1489 default setting is overridden by a confDH_PARAMETERS configuration
1490 setting of '5' or pointing to a 512 bit DH parameter file.
1493 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1494 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1495 and devel/kyua to version 0.20+ and adjust any calling code to work
1496 with Kyuafile and kyua.
1499 The import of openssl to address the FreeBSD-SA-15:10.openssl
1500 security advisory includes a change which rejects handshakes
1501 with DH parameters below 768 bits. sendmail releases prior
1502 to 8.15.2 (not yet released), defaulted to a 512 bit
1503 DH parameter setting for client connections. To work around
1504 this interoperability, sendmail can be configured to use a
1505 2048 bit DH parameter by:
1507 1. Edit /etc/mail/`hostname`.mc
1508 2. If a setting for confDH_PARAMETERS does not exist or
1509 exists and is set to a string beginning with '5',
1510 replace it with '2'.
1511 3. If a setting for confDH_PARAMETERS exists and is set to
1512 a file path, create a new file with:
1513 openssl dhparam -out /path/to/file 2048
1514 4. Rebuild the .cf file:
1515 cd /etc/mail/; make; make install
1516 5. Restart sendmail:
1517 cd /etc/mail/; make restart
1519 A sendmail patch is coming, at which time this file will be
1523 Generation of legacy formatted entries have been disabled by default
1524 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1525 entries were converted to use the new format by default when the new,
1526 machine independent format have been added and supported since FreeBSD
1529 Please see the pwd_mkdb(8) manual page for further details.
1532 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1533 20141231 entry below for information about prerequisites and upgrading,
1534 if you are not already using 3.5.0 or higher.
1537 TI platform code switched to using vendor DTS files and this update
1538 may break existing systems running on Beaglebone, Beaglebone Black,
1541 - dtb files should be regenerated/reinstalled. Filenames are the
1542 same but content is different now
1543 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1544 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1545 addressing scheme is now pin 25 on /dev/gpioc3.
1546 - Pandaboard: /etc/ttys should be updated, serial console device is
1547 now /dev/ttyu2, not /dev/ttyu0
1550 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1551 If you need the GNU extension from groff soelim(1), install groff
1552 from package: pkg install groff, or via ports: textproc/groff.
1555 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1556 defined in symlink(7); previously symlinks were silently ignored.
1559 The const qualifier has been removed from iconv(3) to comply with
1560 POSIX. The ports tree is aware of this from r384038 onwards.
1563 Libraries specified by LIBADD in Makefiles must have a corresponding
1564 DPADD_<lib> variable to ensure correct dependencies. This is now
1565 enforced in src.libnames.mk.
1568 From legacy ata(4) driver was removed support for SATA controllers
1569 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1570 Kernel modules ataahci and ataadaptec were removed completely,
1571 replaced by ahci and mvs modules respectively.
1574 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1575 the 20141231 entry below for information about prerequisites and
1576 upgrading, if you are not already using 3.5.0 or higher.
1579 The 32-bit PowerPC kernel has been changed to a position-independent
1580 executable. This can only be booted with a version of loader(8)
1581 newer than January 31, 2015, so make sure to update both world and
1582 kernel before rebooting.
1585 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1586 but before r278950, the RNG was not seeded properly. Immediately
1587 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1588 ssh keys or openssl keys) that were generated w/ a kernel from that
1589 range. This does not affect programs that directly used /dev/random
1590 or /dev/urandom. All userland uses of arc4random(3) are affected.
1593 The autofs(4) ABI was changed in order to restore binary compatibility
1594 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1595 with the new kernel.
1598 The powerpc64 kernel has been changed to a position-independent
1599 executable. This can only be booted with a new version of loader(8),
1600 so make sure to update both world and kernel before rebooting.
1603 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1604 only release, no new features have been added. Please see the 20141231
1605 entry below for information about prerequisites and upgrading, if you
1606 are not already using 3.5.0.
1609 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1610 taken from the ELF Tool Chain project rather than GNU binutils. They
1611 should be drop-in replacements, with the addition of arm64 support.
1612 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1613 binutils tools, if necessary. See 20150805 for updated information.
1616 The default Unbound configuration now enables remote control
1617 using a local socket. Users who have already enabled the
1618 local_unbound service should regenerate their configuration
1619 by running "service local_unbound setup" as root.
1622 The GNU texinfo and GNU info pages have been removed.
1623 To be able to view GNU info pages please install texinfo from ports.
1626 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1628 As of this release, a prerequisite for building clang, llvm and lldb is
1629 a C++11 capable compiler and C++11 standard library. This means that to
1630 be able to successfully build the cross-tools stage of buildworld, with
1631 clang as the bootstrap compiler, your system compiler or cross compiler
1632 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1633 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1636 On any standard FreeBSD 10.x or 11.x installation, where clang and
1637 libc++ are on by default (that is, on x86 or arm), this should work out
1640 On 9.x installations where clang is enabled by default, e.g. on x86 and
1641 powerpc, libc++ will not be enabled by default, so libc++ should be
1642 built (with clang) and installed first. If both clang and libc++ are
1643 missing, build clang first, then use it to build libc++.
1645 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1646 the instructions for 9.x above.
1648 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1649 default, and do not build clang.
1651 Many embedded systems are resource constrained, and will not be able to
1652 build clang in a reasonable time, or in some cases at all. In those
1653 cases, cross building bootable systems on amd64 is a workaround.
1655 This new version of clang introduces a number of new warnings, of which
1656 the following are most likely to appear:
1660 This warns in two cases, for both C and C++:
1661 * When the code is trying to take the absolute value of an unsigned
1662 quantity, which is effectively a no-op, and almost never what was
1663 intended. The code should be fixed, if at all possible. If you are
1664 sure that the unsigned quantity can be safely cast to signed, without
1665 loss of information or undefined behavior, you can add an explicit
1666 cast, or disable the warning.
1668 * When the code is trying to take an absolute value, but the called
1669 abs() variant is for the wrong type, which can lead to truncation.
1670 If you want to disable the warning instead of fixing the code, please
1671 make sure that truncation will not occur, or it might lead to unwanted
1674 -Wtautological-undefined-compare and
1675 -Wundefined-bool-conversion
1677 These warn when C++ code is trying to compare 'this' against NULL, while
1678 'this' should never be NULL in well-defined C++ code. However, there is
1679 some legacy (pre C++11) code out there, which actively abuses this
1680 feature, which was less strictly defined in previous C++ versions.
1682 Squid and openjdk do this, for example. The warning can be turned off
1683 for C++98 and earlier, but compiling the code in C++11 mode might result
1684 in unexpected behavior; for example, the parts of the program that are
1685 unreachable could be optimized away.
1688 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1689 kernel sources have been removed. The .h files remain, since some
1690 utilities include them. This will need to be fixed later.
1691 If "mount -t oldnfs ..." is attempted, it will fail.
1692 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1693 the utilities will report errors.
1696 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1697 directories to top level SUBDIR variable when their parent
1698 directory is included in LOCAL_DIRS. Users with build systems with
1699 such hierarchies and without SUBDIR entries in the parent
1700 directory Makefiles should add them or add the directories to
1704 faith(4) and faithd(8) have been removed from the base system. Faith
1705 has been obsolete for a very long time.
1708 vt(4), the new console driver, is enabled by default. It brings
1709 support for Unicode and double-width characters, as well as
1710 support for UEFI and integration with the KMS kernel video
1713 You may need to update your console settings in /etc/rc.conf,
1714 most probably the keymap. During boot, /etc/rc.d/syscons will
1715 indicate what you need to do.
1717 vt(4) still has issues and lacks some features compared to
1718 syscons(4). See the wiki for up-to-date information:
1719 https://wiki.freebsd.org/Newcons
1721 If you want to keep using syscons(4), you can do so by adding
1722 the following line to /boot/loader.conf:
1726 pjdfstest has been integrated into kyua as an opt-in test suite.
1727 Please see share/doc/pjdfstest/README for more details on how to
1731 gperf has been removed from the base system for architectures
1732 that use clang. Ports that require gperf will obtain it from the
1736 pjdfstest has been moved from tools/regression/pjdfstest to
1740 At svn r271982, The default linux compat kernel ABI has been adjusted
1741 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1742 update. If you wish to continue using the linux-f10 compat ports,
1743 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1744 encouraged to update their linux-compat packages to linux-c6 during
1745 their next update cycle.
1748 The ofwfb driver, used to provide a graphics console on PowerPC when
1749 using vt(4), no longer allows mmap() of all physical memory. This
1750 will prevent Xorg on PowerPC with some ATI graphics cards from
1751 initializing properly unless x11-servers/xorg-server is updated to
1755 The xdev targets have been converted to using TARGET and
1756 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1759 The default unbound configuration has been modified to address
1760 issues with reverse lookups on networks that use private
1761 address ranges. If you use the local_unbound service, run
1762 "service local_unbound setup" as root to regenerate your
1763 configuration, then "service local_unbound reload" to load the
1767 The GNU texinfo and GNU info pages are not built and installed
1768 anymore, WITH_INFO knob has been added to allow to built and install
1770 UPDATE: see 20150102 entry on texinfo's removal
1773 The GNU readline library is now an INTERNALLIB - that is, it is
1774 statically linked into consumers (GDB and variants) in the base
1775 system, and the shared library is no longer installed. The
1776 devel/readline port is available for third party software that
1780 The Itanium architecture (ia64) has been removed from the list of
1781 known architectures. This is the first step in the removal of the
1785 Commit r268115 has added NFSv4.1 server support, merged from
1786 projects/nfsv4.1-server. Since this includes changes to the
1787 internal interfaces between the NFS related modules, a full
1788 build of the kernel and modules will be necessary.
1789 __FreeBSD_version has been bumped.
1792 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1793 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1794 which differs from the behaviour controlled by this knob.)
1797 Maximal length of the serial number in CTL was increased from 16 to
1798 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1799 and ctld, need to be rebuilt to work with a new kernel.
1802 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1803 1 respectively to match the upstream numbers. They were out of
1804 sync because, when they were originally added to FreeBSD, the
1805 upstream versions were not respected. These libraries are private
1806 and not yet built by default, so renumbering them should be a
1807 non-issue. However, unclean source trees will yield broken test
1808 programs once the operator executes "make delete-old-libs" after a
1809 "make installworld".
1811 Additionally, the atf-sh binary was made private by moving it into
1812 /usr/libexec/. Already-built shell test programs will keep the
1813 path to the old binary so they will break after "make delete-old"
1816 If you are using WITH_TESTS=yes (not the default), wipe the object
1817 tree and rebuild from scratch to prevent spurious test failures.
1818 This is only needed once: the misnumbered libraries and misplaced
1819 binaries have been added to OptionalObsoleteFiles.inc so they will
1820 be removed during a clean upgrade.
1823 Clang and llvm have been upgraded to 3.4.1 release.
1826 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1827 be removed to avoid issues in the future (and has been added to
1831 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1832 past, it affected all builds that used the bsd.*.mk files. The old
1833 behavior was a bug, but people may have relied upon it. To get this
1834 behavior back, you can .include /etc/src.conf from /etc/make.conf
1835 (which is still global and isn't changed). This also changes the
1836 behavior of incremental builds inside the tree of individual
1837 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1838 Although this has survived make universe and some upgrade scenarios,
1839 other upgrade scenarios may have broken. At least one form of
1840 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1841 as well... In cases where MAKESYSPATH isn't working with this
1842 setting, you'll need to set it to the full path to your tree.
1844 One side effect of all this cleaning up is that bsd.compiler.mk
1845 is no longer implicitly included by bsd.own.mk. If you wish to
1846 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1850 The lindev device has been removed since /dev/full has been made a
1851 standard device. __FreeBSD_version has been bumped.
1854 The knob WITHOUT_VI was added to the base system, which controls
1855 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1856 in order to reorder files share/termcap and didn't build ex(1) as a
1857 build tool, so building/installing with WITH_VI is highly advised for
1858 build hosts for older releases.
1860 This issue has been fixed in stable/9 and stable/10 in r277022 and
1861 r276991, respectively.
1864 The YES_HESIOD knob has been removed. It has been obsolete for
1865 a decade. Please move to using WITH_HESIOD instead or your builds
1866 will silently lack HESIOD.
1869 The uart(4) driver has been changed with respect to its handling
1870 of the low-level console. Previously the uart(4) driver prevented
1871 any process from changing the baudrate or the CLOCAL and HUPCL
1872 control flags. By removing the restrictions, operators can make
1873 changes to the serial console port without having to reboot.
1874 However, when getty(8) is started on the serial device that is
1875 associated with the low-level console, a misconfigured terminal
1876 line in /etc/ttys will now have a real impact.
1877 Before upgrading the kernel, make sure that /etc/ttys has the
1878 serial console device configured as 3wire without baudrate to
1879 preserve the previous behaviour. E.g:
1880 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1883 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1884 to improve performance. To re-enable it, if needed, run rpcbind
1885 with command line option -W.
1888 Switched back to the GPL dtc compiler due to updates in the upstream
1889 dts files not being supported by the BSDL dtc compiler. You will need
1890 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1891 may result while building dtb files during a kernel build if you fail
1892 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1895 Clang and llvm have been upgraded to 3.4 release.
1898 The nve(4) driver has been removed. Please use the nfe(4) driver
1899 for NVIDIA nForce MCP Ethernet adapters instead.
1902 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1903 This could cause certain C++ applications using shared libraries built
1904 against the previous version of libc++ to crash. The incompatibility
1905 has now been fixed, but any C++ applications or shared libraries built
1906 between r261283 and r261801 should be recompiled.
1909 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1910 capability mode support. Please note that enabling the feature in
1911 kernel is still highly recommended.
1914 OpenSSH is now built with sandbox support, and will use sandbox as
1915 the default privilege separation method. This requires Capsicum
1916 capability mode support in kernel.
1919 The libelf and libdwarf libraries have been updated to newer
1920 versions from upstream. Shared library version numbers for
1921 these two libraries were bumped. Any ports or binaries
1922 requiring these two libraries should be recompiled.
1923 __FreeBSD_version is bumped to 1100006.
1926 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1927 instead of providing an explicit one, this would prevent such
1928 Makefile from providing its own Kyuafile in the future during
1929 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1930 intervention is needed to clean an objdir if you use NO_CLEAN:
1931 # find /usr/obj -name Kyuafile | xargs rm -f
1934 The behavior of gss_pseudo_random() for the krb5 mechanism
1935 has changed, for applications requesting a longer random string
1936 than produced by the underlying enctype's pseudo-random() function.
1937 In particular, the random string produced from a session key of
1938 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1939 be different at the 17th octet and later, after this change.
1940 The counter used in the PRF+ construction is now encoded as a
1941 big-endian integer in accordance with RFC 4402.
1942 __FreeBSD_version is bumped to 1100004.
1945 The WITHOUT_ATF build knob has been removed and its functionality
1946 has been subsumed into the more generic WITHOUT_TESTS. If you were
1947 using the former to disable the build of the ATF libraries, you
1948 should change your settings to use the latter.
1951 The default version of mtree is nmtree which is obtained from
1952 NetBSD. The output is generally the same, but may vary
1953 slightly. If you found you need identical output adding
1954 "-F freebsd9" to the command line should do the trick. For the
1955 time being, the old mtree is available as fmtree.
1958 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1959 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1960 1.1.4_8 and verify bsdyml not linked in, before running "make
1962 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1964 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1967 The stable/10 branch has been created in subversion from head
1974 Sometimes, obscure build problems are the result of environment
1975 poisoning. This can happen because the make utility reads its
1976 environment when searching for values for global variables. To run
1977 your build attempts in an "environmental clean room", prefix all make
1978 commands with 'env -i '. See the env(1) manual page for more details.
1979 Occasionally a build failure will occur with "make -j" due to a race
1980 condition. If this happens try building again without -j, and please
1981 report a bug if it happens consistently.
1983 When upgrading from one major version to another it is generally best to
1984 upgrade to the latest code in the currently installed branch first, then
1985 do an upgrade to the new branch. This is the best-tested upgrade path,
1986 and has the highest probability of being successful. Please try this
1987 approach if you encounter problems with a major version upgrade. Since
1988 the stable 4.x branch point, one has generally been able to upgrade from
1989 anywhere in the most recent stable branch to head / current (or even the
1990 last couple of stable branches). See the top of this file when there's
1993 When upgrading a live system, having a root shell around before
1994 installing anything can help undo problems. Not having a root shell
1995 around can lead to problems if pam has changed too much from your
1996 starting point to allow continued authentication after the upgrade.
1998 This file should be read as a log of events. When a later event changes
1999 information of a prior event, the prior event should not be deleted.
2000 Instead, a pointer to the entry with the new information should be
2001 placed in the old entry. Readers of this file should also sanity check
2002 older entries before relying on them blindly. Authors of new entries
2003 should write them with this in mind.
2007 When upgrading the boot ZFS pool to a new version, always follow
2010 1.) recompile and reinstall the ZFS boot loader and boot block
2011 (this is part of "make buildworld" and "make installworld")
2013 2.) update the ZFS boot block on your boot drive
2015 The following example updates the ZFS boot block on the first
2016 partition (freebsd-boot) of a GPT partitioned drive ada0:
2017 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
2019 Non-boot pools do not need these updates.
2023 If you are updating from a prior version of FreeBSD (even one just
2024 a few days old), you should follow this procedure. It is the most
2025 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2027 make kernel-toolchain
2028 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2029 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2031 To test a kernel once
2032 ---------------------
2033 If you just want to boot a kernel once (because you are not sure
2034 if it works, or if you want to boot a known bad kernel to provide
2035 debugging information) run
2036 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2037 nextboot -k testkernel
2039 To rebuild everything and install it on the current system.
2040 -----------------------------------------------------------
2041 # Note: sometimes if you are running current you gotta do more than
2042 # is listed here if you are upgrading from a really old current.
2044 <make sure you have good level 0 dumps>
2046 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2047 make installkernel KERNCONF=YOUR_KERNEL_HERE
2049 <reboot in single user> [3]
2056 To cross-install current onto a separate partition
2057 --------------------------------------------------
2058 # In this approach we use a separate partition to hold
2059 # current's root, 'usr', and 'var' directories. A partition
2060 # holding "/", "/usr" and "/var" should be about 2GB in
2063 <make sure you have good level 0 dumps>
2066 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2067 <maybe newfs current's root partition>
2068 <mount current's root partition on directory ${CURRENT_ROOT}>
2069 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
2070 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2071 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2072 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2073 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2074 <reboot into current>
2075 <do a "native" rebuild/install as described in the previous section>
2076 <maybe install compatibility libraries from ports/misc/compat*>
2080 To upgrade in-place from stable to current
2081 ----------------------------------------------
2082 <make sure you have good level 0 dumps>
2084 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
2085 make installkernel KERNCONF=YOUR_KERNEL_HERE
2087 <reboot in single user> [3]
2094 Make sure that you've read the UPDATING file to understand the
2095 tweaks to various things you need. At this point in the life
2096 cycle of current, things change often and you are on your own
2097 to cope. The defaults can also change, so please read ALL of
2098 the UPDATING entries.
2100 Also, if you are tracking -current, you must be subscribed to
2101 freebsd-current@freebsd.org. Make sure that before you update
2102 your sources that you have read and understood all the recent
2103 messages there. If in doubt, please track -stable which has
2104 much fewer pitfalls.
2106 [1] If you have third party modules, such as vmware, you
2107 should disable them at this point so they don't crash your
2110 [3] From the bootblocks, boot -s, and then do
2114 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed
2115 cd src # full path to source
2116 adjkerntz -i # if CMOS is wall time
2117 Also, when doing a major release upgrade, it is required that
2118 you boot into single user mode to do the installworld.
2120 [4] Note: This step is non-optional. Failure to do this step
2121 can result in a significant reduction in the functionality of the
2122 system. Attempting to do it by hand is not recommended and those
2123 that pursue this avenue should read this file carefully, as well
2124 as the archives of freebsd-current and freebsd-hackers mailing lists
2125 for potential gotchas. The -U option is also useful to consider.
2126 See mergemaster(8) for more information.
2128 [5] Usually this step is a no-op. However, from time to time
2129 you may need to do this if you get unknown user in the following
2130 step. It never hurts to do it all the time. You may need to
2131 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2132 install) after the buildworld before this step if you last updated
2133 from current before 20130425 or from -stable before 20130430.
2135 [6] This only deletes old files and directories. Old libraries
2136 can be deleted by "make delete-old-libs", but you have to make
2137 sure that no program is using those libraries anymore.
2139 [8] The new kernel must be able to run existing binaries used by an
2140 installworld. When upgrading across major versions, the new kernel's
2141 configuration must include the correct COMPAT_FREEBSD<n> option for
2142 existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure
2143 to do so may leave you with a system that is hard to boot to recover. A
2144 GENERIC kernel will include suitable compatibility options to run
2145 binaries from older branches. Note that the ability to run binaries
2146 from unsupported branches is not guaranteed.
2148 Make sure that you merge any new devices from GENERIC since the
2149 last time you updated your kernel config file. Options also
2150 change over time, so you may need to adjust your custom kernels
2153 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2154 "?=" instead of the "=" assignment operator, so that buildworld can
2155 override the CPUTYPE if it needs to.
2157 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2158 not on the command line, or in /etc/make.conf. buildworld will
2159 warn if it is improperly defined.
2162 This file contains a list, in reverse chronological order, of major
2163 breakages in tracking -current. It is not guaranteed to be a complete
2164 list of such breakages, and only contains entries since September 23, 2011.
2165 If you need to see UPDATING entries from before that date, you will need
2166 to fetch an UPDATING file from an older FreeBSD release.
2168 Copyright information:
2170 Copyright 1998-2009 M. Warner Losh <imp@FreeBSD.org>
2172 Redistribution, publication, translation and use, with or without
2173 modification, in full or in part, in any form or format of this
2174 document are permitted without further permission from the author.
2176 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2177 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2178 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2179 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2180 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2181 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2182 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2183 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2184 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2185 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2186 POSSIBILITY OF SUCH DAMAGE.
2188 Contact Warner Losh if you have any questions about your use of