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 Support for armv5 has been disconnected and is being removed. The
31 machine combination MACHINE=arm MACHINE_ARCH=arm is no longer valid.
32 You must now use a MACHINE_ARCH of armv6 or armv7. The default
33 MACHINE_ARCH for MACHINE=arm is now armv7.
36 Clang/LLVM is now the default compiler for all powerpc architectures.
37 LLD is now the default linker for powerpc64. The change for powerpc64
38 also includes a change to the ELFv2 ABI, incompatible with the existing
42 Kernel-loadable random(4) modules are no longer unloadable.
45 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
46 been upgraded to 9.0.1. Please see the 20141231 entry below for
47 information about prerequisites and upgrading, if you are not already
48 using clang 3.5.0 or higher.
51 r355677 has modified the internal interface used between the
52 NFS modules in the kernel. As such, they must all be upgraded
53 simultaneously. I will do a version bump for this.
56 The root certificates of the Mozilla CA Certificate Store have been
57 imported into the base system and can be managed with the certctl(8)
58 utility. If you have installed the security/ca_root_nss port or package
59 with the ETCSYMLINK option (the default), be advised that there may be
60 differences between those included in the port and those included in
61 base due to differences in nss branch used as well as general update
62 frequency. Note also that certctl(8) cannot manage certs in the
63 format used by the security/ca_root_nss port.
66 The amd(8) automount daemon has been disabled by default, and will be
67 removed in the future. As of FreeBSD 10.1 the autofs(5) is available
71 The nctgpio and wbwd drivers have been moved to the superio bus.
72 If you have one of these drivers in a kernel configuration, then
73 you should add device superio to it. If you use one of these drivers
74 as a module and you compile a custom set of modules, then you should
75 add superio to the set.
78 KPIs for network drivers to access interface addresses have changed.
79 Users need to recompile NIC driver modules together with kernel.
82 The net.link.tap.user_open sysctl no longer prevents user opening of
83 already created /dev/tapNN devices. Access is still controlled by
84 node permissions, just like tun devices. The net.link.tap.user_open
85 sysctl is now used only to allow users to perform devfs cloning of
86 tap devices, and the subsequent open may not succeed if the user is not
87 in the appropriate group. This sysctl may be deprecated/removed
88 completely in the future.
91 mips, powerpc, and sparc64 are no longer built as part of
92 universe / tinderbox unless MAKE_OBSOLETE_GCC is defined. If
93 not defined, mips, powerpc, and sparc64 builds will look for
94 the xtoolchain binaries and if installed use them for universe
95 builds. As llvm 9.0 becomes vetted for these architectures, they
96 will be removed from the list.
99 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
100 been upgraded to 9.0.0. Please see the 20141231 entry below for
101 information about prerequisites and upgrading, if you are not already
102 using clang 3.5.0 or higher.
105 The hpt27xx, hptmv, hptnr, and hptrr drivers have been removed from
106 GENERIC. They are available as modules and can be loaded by adding
107 to /boot/loader.conf hpt27xx_load="YES", hptmv_load="YES",
108 hptnr_load="YES", or hptrr_load="YES", respectively.
111 ntpd no longer by default locks its pages in memory, allowing them
112 to be paged out by the kernel. Use rlimit memlock to restore
113 historic BSD behaviour. For example, add "rlimit memlock 32"
114 to ntp.conf to lock up to 32 MB of ntpd address space in memory.
117 Several of ping6's options have been renamed for better consistency
118 with ping. If you use any of -ARWXaghmrtwx, you must update your
119 scripts. See ping6(8) for details.
122 The vfs.fusefs.sync_unmount and vfs.fusefs.init_backgrounded sysctls
123 and the "-o sync_unmount" and "-o init_backgrounded" mount options have
124 been removed from mount_fusefs(8). You can safely remove them from
125 your scripts, because they had no effect.
127 The vfs.fusefs.fix_broken_io, vfs.fusefs.sync_resize,
128 vfs.fusefs.refresh_size, vfs.fusefs.mmap_enable,
129 vfs.fusefs.reclaim_revoked, and vfs.fusefs.data_cache_invalidate
130 sysctls have been removed. If you felt the need to set any of them to
131 a non-default value, please tell asomers@FreeBSD.org why.
134 Default permissions on the /var/account/acct file (and copies of it
135 rotated by periodic daily scripts) are changed from 0644 to 0640
136 because the file contains sensitive information that should not be
137 world-readable. If the /var/account directory must be created by
138 rc.d/accounting, the mode used is now 0750. Admins who use the
139 accounting feature are encouraged to change the mode of an existing
140 /var/account directory to 0750 or 0700.
143 Entropy collection and the /dev/random device are no longer optional
144 components. The "device random" option has been removed.
145 Implementations of distilling algorithms can still be made loadable
146 with "options RANDOM_LOADABLE" (e.g., random_fortuna.ko).
149 Clang, llvm, lld, lldb, compiler-rt, libc++, libunwind and openmp have
150 been upgraded to 8.0.1. Please see the 20141231 entry below for
151 information about prerequisites and upgrading, if you are not already
152 using clang 3.5.0 or higher.
155 A fix was applied to i386 kernel modules to avoid panics with
156 dpcpu or vnet. Users need to recompile i386 kernel modules
157 having pcpu or vnet sections or they will refuse to load.
160 User-wired pages now have their own counter,
161 vm.stats.vm.v_user_wire_count. The vm.max_wired sysctl was renamed
162 to vm.max_user_wired and changed from an unsigned int to an unsigned
163 long. bhyve VMs wired with the -S are now subject to the user
164 wiring limit; the vm.max_user_wired sysctl may need to be tuned to
165 avoid running into the limit.
168 The IPSEC option has been removed from GENERIC. Users requiring
169 ipsec(4) must now load the ipsec(4) kernel module.
172 The tap(4) driver has been folded into tun(4), and the module has been
173 renamed to tuntap. You should update any kld_list="if_tap" or
174 kld_list="if_tun" entries in /etc/rc.conf, if_tap_load="YES" or
175 if_tun_load="YES" entries in /boot/loader.conf to load the if_tuntap
176 module instead, and "device tap" or "device tun" entries in kernel
177 config files to select the tuntap device instead.
180 The following knobs have been added related to tradeoffs between
181 safe use of the random device and availability in the absence of
184 kern.random.initial_seeding.bypass_before_seeding: tunable; set
185 non-zero to bypass the random device prior to seeding, or zero to
186 block random requests until the random device is initially seeded.
187 For now, set to 1 (unsafe) by default to restore pre-r346250 boot
188 availability properties.
190 kern.random.initial_seeding.read_random_bypassed_before_seeding:
191 read-only diagnostic sysctl that is set when bypass is enabled and
192 read_random(9) is bypassed, to enable programmatic handling of this
193 initial condition, if desired.
195 kern.random.initial_seeding.arc4random_bypassed_before_seeding:
196 Similar to the above, but for for arc4random(9) initial seeding.
198 kern.random.initial_seeding.disable_bypass_warnings: tunable; set
199 non-zero to disable warnings in dmesg when the same conditions are
200 met as for the diagnostic sysctls above. Defaults to zero, i.e.,
201 produce warnings in dmesg when the conditions are met.
204 The loadable random module KPI has changed; the random_infra_init()
205 routine now requires a 3rd function pointer for a bool (*)(void)
206 method that returns true if the random device is seeded (and
207 therefore unblocked).
210 r345895 reverts r320698. This implies that an nfsuserd(8) daemon
211 built from head sources between r320757 (July 6, 2017) and
212 r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
213 is added to the command line.
214 nfsuserd daemons built from head sources that are post-r338192 are
215 not affected and should continue to work.
218 The fuse(4) module has been renamed to fusefs(4) for consistency with
219 other filesystems. You should update any kld_load="fuse" entries in
220 /etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
221 "options FUSE" entries in kernel config files.
224 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
225 8.0.0. Please see the 20141231 entry below for information about
226 prerequisites and upgrading, if you are not already using clang 3.5.0
230 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
231 compiled into your custom kernel, add 'device xz' statement to the
235 drm and drm2 have been removed from the tree. Please see
236 https://wiki.freebsd.org/Graphics for the latest information on
237 migrating to the drm ports.
240 Iflib is no longer unconditionally compiled into the kernel. Drivers
241 using iflib and statically compiled into the kernel, now require
242 the 'device iflib' config option. For the same drivers loaded as
243 modules on kernels not having 'device iflib', the iflib.ko module
244 is loaded automatically.
247 The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
248 options no longer exist since r343219 and r343427 respectively;
249 nothing uses them, so they should be just removed from custom
253 r342635 changes the way efibootmgr(8) works by requiring users to add
254 the -b (bootnum) parameter for commands where the bootnum was previously
255 specified with each option. For example 'efibootmgr -B 0001' is now
256 'efibootmgr -B -b 0001'.
259 r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
260 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
261 servers that have vfs.nfsd.nfs_privport set will only allow mounts
262 from clients using a reserved port#. Since both the FreeBSD and Linux
263 NFSv4 clients use reserved port#s by default, this should not affect
267 The XLP config has been removed. We can't support 64-bit atomics in this
268 kernel because it is running in 32-bit mode. XLP users must transition
269 to running a 64-bit kernel (XLP64 or XLPN32).
271 The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
272 the preferred emulator today and we don't need two different ones.
274 The old sibyte / swarm / Broadcom BCM1250 support has been
275 removed from the mips port.
278 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
279 7.0.1. Please see the 20141231 entry below for information about
280 prerequisites and upgrading, if you are not already using clang 3.5.0
284 Remove the timed and netdate programs from the base tree. Setting
285 the time with these daemons has been obsolete for over a decade.
288 On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
289 linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
290 it produces broken binaries when ifuncs are in use. Users needing
291 GNU ld should install the binutils port or package.
294 The BSD crtbegin and crtend code has been enabled by default. It has
295 had extensive testing on amd64, arm64, and i386. It can be disabled
296 by building a world with -DWITHOUT_BSD_CRTBEGIN.
299 The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
300 has been converted to a port (misc/ctm) and will be removed from
301 FreeBSD-13. It is available as a package (ctm) for all supported
305 The default newsyslog.conf(5) file has been changed to only include
306 files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
307 the filenames end in '.conf' and do not begin with a '.'.
309 You should check the configuration files in these two directories match
310 this naming convention. You can verify which configuration files are
311 being included using the command:
315 Ports for the DRM modules have been simplified. Now, amd64 users should
316 just install the drm-kmod port. All others should install
319 Graphics hardware that's newer than about 2010 usually works with
320 drm-kmod. For hardware older than 2013, however, some users will need
321 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
322 than 2008 usually only works in drm-legacy-kmod. The graphics team can
323 only commit to hardware made since 2013 due to the complexity of the
324 market and difficulty to test all the older cards effectively. If you
325 have hardware supported by drm-kmod, you are strongly encouraged to use
326 that as you will get better support.
328 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
329 elsewhere, the drm and drm2 modules will be eliminated from the src base
330 soon (with a limited exception for arm). Please update to the package
331 asap and report any issues to x11@freebsd.org.
333 Generally, anybody using the drm*-kmod packages should add
334 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
335 cross-threading surprises, especially with automatic driver
336 loading from X11 startup. These will become the defaults in 13-current
340 The ixlv(4) driver has been renamed to iavf(4). As a consequence,
341 custom kernel and module loading configuration files must be updated
342 accordingly. Moreover, interfaces previous presented as ixlvN to the
343 system are now exposed as iavfN and network configuration files must
344 be adjusted as necessary.
347 OpenSSL has been updated to version 1.1.1. This update included
348 additional various API changes throughout the base system. It is
349 important to rebuild third-party software after upgrading. The value
350 of __FreeBSD_version has been bumped accordingly.
353 The legacy DRM modules and drivers have now been added to the loader's
354 module blacklist, in favor of loading them with kld_list in rc.conf(5).
355 The module blacklist may be overridden with the loader.conf(5)
356 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
360 The cam(4) based nda(4) driver will be used over nvd(4) by default on
361 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
362 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
363 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
367 Reproducible build mode is now on by default, in preparation for
368 FreeBSD 12.0. This eliminates build metadata such as the user,
369 host, and time from the kernel (and uname), unless the working tree
370 corresponds to a modified checkout from a version control system.
371 The previous behavior can be obtained by setting the /etc/src.conf
372 knob WITHOUT_REPRODUCIBLE_BUILD.
375 The Yarrow CSPRNG has been removed from the kernel as it has not been
376 supported by its designers since at least 2003. Fortuna has been the
377 default since FreeBSD-11.
380 devctl freeze/thaw have gone into the tree, the rc scripts have been
381 updated to use them and devmatch has been changed. You should update
382 kernel, userland and rc scripts all at the same time.
385 The default interpreter has been switched from 4th to Lua.
386 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
387 interpreter. If you have custom FORTH code you will need to set
388 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
389 src.conf for the build. This will create default hard links between
390 loader and loader_4th instead of loader and loader_lua, the new default.
391 If you are using UEFI it will create the proper hard link to loader.efi.
393 bhyve uses userboot.so. It remains 4th-only until some issues are solved
394 regarding coexisting with multiple versions of FreeBSD are resolved.
397 ls(1) now respects the COLORTERM environment variable used in other
398 systems and software to indicate that a colored terminal is both
399 supported and desired. If ls(1) is suddenly emitting colors, they may
400 be disabled again by either removing the unwanted COLORTERM from your
401 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
402 may not be observed in a future release.
405 The default pager for most commands has been changed to "less". To
406 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
410 The jedec_ts(4) driver has been removed. A superset of its functionality
411 is available in the jedec_dimm(4) driver, and the manpage for that
412 driver includes migration instructions. If you have "device jedec_ts"
413 in your kernel configuration file, it must be removed.
416 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
417 This should have no effect if the kernel is booted via BIOS/legacy boot.
418 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
419 has a buggy firmware that prevents a successful boot due to use of
423 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
424 support has been removed from the tree. These ports were
425 obsolete and/or known to be broken for many years.
428 loader.efi has been augmented to participate more fully in the
429 UEFI boot manager protocol. loader.efi will now look at the
430 BootXXXX environment variable to determine if a specific kernel
431 or root partition was specified. XXXX is derived from BootCurrent.
432 efibootmgr(8) manages these standard UEFI variables.
435 zfsloader's functionality has now been folded into loader.
436 zfsloader is no longer necessary once you've updated your
437 boot blocks. For a transition period, we will install a
438 hardlink for zfsloader to loader to allow a smooth transition
439 until the boot blocks can be updated (hard link because old
440 zfs boot blocks don't understand symlinks).
443 ARM64 now have efifb support, if you want to have serial console
444 on your arm64 board when an screen is connected and the bootloader
445 setup a frame buffer for us to use, just add :
449 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
450 an screen connected as the firmware will setup a frame buffer are that
451 u-boot will expose as an EFI frame buffer.
454 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
455 or take steps to update /etc/passwd before doing installworld on
456 existing systems. Do not skip the "mergemaster -Fp" step before
457 installworld, as described in the update procedures near the bottom
458 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
459 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
460 the ntp config file contain options that change file/dir locations.
461 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
462 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
463 taking steps to ensure that all required files/dirs are accessible
467 Big endian arm support has been removed.
470 The static environment setup in kernel configs is no longer mutually
471 exclusive with the loader(8) environment by default. In order to
472 restore the previous default behavior of disabling the loader(8)
473 environment if a static environment is present, you must specify
474 loader_env.disabled=1 in the static environment.
477 The ABI of syscalls used by management tools like sockstat and
478 netstat has been broken to allow 32-bit binaries to work on
479 64-bit kernels without modification. These programs will need
480 to match the kernel in order to function. External programs may
481 require minor modifications to accommodate a change of type in
482 structures from pointers to 64-bit virtual addresses.
485 On i386 and amd64 atomics are now inlined. Out of tree modules using
486 atomics will need to be rebuilt.
489 The '%I' format in the kern.corefile sysctl limits the number of
490 core files that a process can generate to the number stored in the
491 debug.ncores sysctl. The '%I' format is replaced by the single digit
492 index. Previously, if all indexes were taken the kernel would overwrite
493 only a core file with the highest index in a filename.
494 Currently the system will create a new core file if there is a free
495 index or if all slots are taken it will overwrite the oldest one.
498 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
499 6.0.1. Please see the 20141231 entry below for information about
500 prerequisites and upgrading, if you are not already using clang 3.5.0
504 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
505 needed to be changed to work with it. This change was made with r335763
506 and requires a mergemaster / etcupdate / etc to update the installed
510 r334930 changed the interface between the NFS modules, so they all
511 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
514 As of r334391 lld is the default amd64 system linker; it is installed
515 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
519 The kernel / userland interface for devinfo changed, so you'll
520 need a new kernel and userland as a pair for it to work (rebuilding
521 lib/libdevinfo is all that's required). devinfo and devmatch will
522 not work, but everything else will when there's a mismatch.
525 The on-disk format for hwpmc callchain records has changed to include
526 threadid corresponding to a given record. This changes the field offsets
527 and thus requires that libpmcstat be rebuilt before using a kernel
531 The vxge(4) driver has been removed. This driver was introduced into
532 HEAD one week before the Exar left the Ethernet market and is not
533 known to be used. If you have device vxge in your kernel config file
537 The amd64 kernel now requires a ld that supports ifunc to produce a
538 working kernel, either lld or a newer binutils. lld is built by default
539 on amd64, and the 'buildkernel' target uses it automatically. However,
540 it is not the default linker, so building the kernel the traditional
541 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
542 binutils port/package). lld will soon be default, and this requirement
545 NOTE: As of r334391 lld is the default system linker on amd64, and no
546 workaround is necessary.
549 The nxge(4) driver has been removed. This driver was for PCI-X 10g
550 cards made by s2io/Neterion. The company was acquired by Exar and
551 no longer sells or supports Ethernet products. If you have device
552 nxge in your kernel config file it must be removed.
555 The tz database (tzdb) has been updated to 2018e. This version more
556 correctly models time stamps in time zones with negative DST such as
557 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
558 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
559 time zone abbreviations and the tm_isdst flag.
562 The ixgb(4) driver has been removed. This driver was for an early and
563 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
564 quickly shifted to the long lived ixgbe family. If you have device
565 ixgb in your kernel config file it must be removed.
568 The lmc(4) driver has been removed. This was a WAN interface
569 card that was already reportedly rare in 2003, and had an ambiguous
570 license. If you have device lmc in your kernel config file it must
574 Support for Arcnet networks has been removed. If you have device
575 arcnet or device cm in your kernel config file they must be
579 Support for FDDI networks has been removed. If you have device
580 fddi or device fpa in your kernel config file they must be
584 In addition to supporting RFC 3164 formatted messages, the
585 syslogd(8) service is now capable of parsing RFC 5424 formatted
586 log messages. The main benefit of using RFC 5424 is that clients
587 may now send log messages with timestamps containing year numbers,
588 microseconds and time zone offsets.
590 Similarly, the syslog(3) C library function has been altered to
591 send RFC 5424 formatted messages to the local system logging
592 daemon. On systems using syslogd(8), this change should have no
593 negative impact, as long as syslogd(8) and the C library are
594 updated at the same time. On systems using a different system
595 logging daemon, it may be necessary to make configuration
596 adjustments, depending on the software used.
598 When using syslog-ng, add the 'syslog-protocol' flag to local
599 input sources to enable parsing of RFC 5424 formatted messages:
602 unix-dgram("/var/run/log" flags(syslog-protocol));
605 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
606 of the 'imuxsock' module to let messages be processed by the
607 regular RFC 3164/5424 parsing pipeline:
609 module(load="imuxsock" SysSock.UseSpecialParser="off")
611 Do note that these changes only affect communication between local
612 applications and syslogd(8). The format that syslogd(8) uses to
613 store messages on disk or forward messages to other systems
614 remains unchanged. syslogd(8) still uses RFC 3164 for these
615 purposes. Options to customize this behaviour will be added in the
616 future. Utilities that process log files stored in /var/log are
617 thus expected to continue to function as before.
619 __FreeBSD_version has been incremented to 1200061 to denote this
623 Support for token ring networks has been removed. If you
624 have "device token" in your kernel config you should remove
625 it. No device drivers supported token ring.
628 makefs was modified to be able to tag ISO9660 El Torito boot catalog
629 entries as EFI instead of overloading the i386 tag as done previously.
630 The amd64 mkisoimages.sh script used to build amd64 ISO images for
631 release was updated to use this. This may mean that makefs must be
632 updated before "make cdrom" can be run in the release directory. This
633 should be as simple as:
635 $ cd $SRCDIR/usr.sbin/makefs
636 $ make depend all install
639 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
640 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
641 Co-existence for the transition period will come shortly. Booting is a
642 complex environment and test coverage for Lua-enabled loaders has been
643 thin, so it would be prudent to assume it might not work and make
644 provisions for backup boot methods.
647 devmatch functionality has been turned on in devd. It will automatically
648 load drivers for unattached devices. This may cause unexpected drivers
649 to be loaded. Please report any problems to current@ and
653 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
654 6.0.0. Please see the 20141231 entry below for information about
655 prerequisites and upgrading, if you are not already using clang 3.5.0
659 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
660 This means it is used to link the kernel and userland libraries and
661 executables, but is not yet installed as /usr/bin/ld by default.
663 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
664 WITHOUT_LLD_BOOTSTRAP=yes
667 On i386, pmtimer has been removed. Its functionality has been folded
668 into apm. It was a no-op on ACPI in current for a while now (but was
669 still needed on i386 in FreeBSD 11 and earlier). Users may need to
670 remove it from kernel config files.
673 The use of RSS hash from the network card aka flowid has been
674 disabled by default for lagg(4) as it's currently incompatible with
675 the lacp and loadbalance protocols.
677 This can be re-enabled by setting the following in loader.conf:
678 net.link.lagg.default_use_flowid="1"
681 The SW_WATCHDOG option is no longer necessary to enable the
682 hardclock-based software watchdog if no hardware watchdog is
683 configured. As before, SW_WATCHDOG will cause the software
684 watchdog to be enabled even if a hardware watchdog is configured.
687 r326887 fixes the issue described in the 20171214 UPDATING entry.
688 r326888 flips the switch back to building GELI support always.
691 r362593 broke ZFS + GELI support for reasons unknown. However,
692 it also broke ZFS support generally, so GELI has been turned off
693 by default as the lesser evil in r326857. If you boot off ZFS and/or
694 GELI, it might not be a good time to update.
697 PowerPC users must update loader(8) by rebuilding world before
698 installing a new kernel, as the protocol connecting them has
699 changed. Without the update, loader metadata will not be passed
700 successfully to the kernel and users will have to enter their
701 root partition at the kernel mountroot prompt to continue booting.
702 Newer versions of loader can boot old kernels without issue.
705 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
706 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
707 to WITH/OUT_LOADER_GELI.
710 The naive and non-compliant support of posix_fallocate(2) in ZFS
711 has been removed as of r325320. The system call now returns EINVAL
712 when used on a ZFS file. Although the new behavior complies with the
713 standard, some consumers are not prepared to cope with it.
714 One known victim is lld prior to r325420.
717 Building in a FreeBSD src checkout will automatically create object
718 directories now rather than store files in the current directory if
719 'make obj' was not ran. Calling 'make obj' is no longer necessary.
720 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
721 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
725 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
726 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
727 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
728 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
729 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
730 The UNIFIED_OBJDIR option is a transitional feature that will be
731 removed for 12.0 release; please migrate to the new format for any
732 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
733 than hardcoding paths.
736 The native-xtools target no longer installs the files by default to the
737 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
738 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
741 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
742 options are changing from controlling the build if defined / undefined
743 to controlling the build with explicit 'yes' or 'no' values. They will
744 shift to WITH/WITHOUT options to match other options in the system.
747 libstand has turned into a private library for sys/boot use only.
748 It is no longer supported as a public interface outside of sys/boot.
751 The arm port has split armv6 into armv6 and armv7. armv7 is now
752 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
753 and are running a kernel from before r324363, you will need to add
754 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
757 When building multiple kernels using KERNCONF, non-existent KERNCONF
758 files will produce an error and buildkernel will fail. Previously
759 missing KERNCONF files silently failed giving no indication as to
760 why, only to subsequently discover during installkernel that the
761 desired kernel was never built in the first place.
764 The default serial number format for CTL LUNs has changed. This will
765 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
766 or iSCSI clients care about their LUNs' serial numbers. Users who
767 require serial number stability should hardcode serial numbers in
771 For 32-bit arm compiled for hard-float support, soft-floating point
772 binaries now always get their shared libraries from
773 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
774 /usr/libsoft also existed). Only users with a hard-float ld.so, but
775 soft-float everything else should be affected.
778 The geli password typed at boot is now hidden. To restore the previous
779 behavior, see geli(8) for configuration options.
782 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
783 sysctl values. Minor nit, but requires a rebuild of both world/kernel
787 "make check" behavior (made in ^/head@r295380) has been changed to
788 execute from a limited sandbox, as opposed to executing from
792 - The "beforecheck" and "aftercheck" targets are now specified.
793 - ${CHECKDIR} (added in commit noted above) has been removed.
794 - Legacy behavior can be enabled by setting
795 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
797 If the limited sandbox mode is enabled, "make check" will execute
798 "make distribution", then install, execute the tests, and clean up the
799 sandbox if successful.
801 The "make distribution" and "make install" targets are typically run as
802 root to set appropriate permissions and ownership at installation time.
803 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
804 environment if executing "make check" with limited sandbox mode using
805 an unprivileged user.
808 Since the switch to GPT disk labels, fsck for UFS/FFS has been
809 unable to automatically find alternate superblocks. As of r322297,
810 the information needed to find alternate superblocks has been
811 moved to the end of the area reserved for the boot block.
812 Filesystems created with a newfs of this vintage or later
813 will create the recovery information. If you have a filesystem
814 created prior to this change and wish to have a recovery block
815 created for your filesystem, you can do so by running fsck in
816 foreground mode (i.e., do not use the -p or -y options). As it
817 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
818 to which you should answer yes.
821 As of r321665, an NFSv4 server configuration that services
822 Kerberos mounts or clients that do not support the uid/gid in
823 owner/owner_group string capability, must explicitly enable
824 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
825 machine's /etc/rc.conf file.
828 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
829 Please see the 20141231 entry below for information about prerequisites
830 and upgrading, if you are not already using clang 3.5.0 or higher.
833 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
834 r-commands (rlogin, rsh, etc.) to be built with the base system.
837 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
838 a very major ABI incompatible change, so users of FreeBSD/powerpc must
839 be careful when performing source upgrades. It is best to run
840 'make installworld' from an alternate root system, either a live
841 CD/memory stick, or a temporary root partition. Additionally, all ports
842 must be recompiled. powerpc64 is largely unaffected, except in the case
843 of 32-bit compatibility. All 32-bit binaries will be affected.
846 Forward compatibility for the "ino64" project have been committed. This
847 will allow most new binaries to run on older kernels in a limited
848 fashion. This prevents many of the common foot-shooting actions in the
849 upgrade as well as the limited ability to roll back the kernel across
850 the ino64 upgrade. Complicated use cases may not work properly, though
851 enough simpler ones work to allow recovery in most situations.
854 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
855 if you require the GPL compiler.
858 The internal ABI used for communication between the NFS kernel modules
859 was changed by r320085, so __FreeBSD_version was bumped to
860 ensure all the NFS related modules are updated together.
863 The ABI of struct event was changed by extending the data
864 member to 64bit and adding ext fields. For upgrade, same
865 precautions as for the entry 20170523 "ino64" must be
869 The GNU roff toolchain has been removed from base. To render manpages
870 which are not supported by mandoc(1), man(1) can fallback on GNU roff
871 from ports (and recommends to install it).
872 To render roff(7) documents, consider using GNU roff from ports or the
873 heirloom doctools roff toolchain from ports via pkg install groff or
874 via pkg install heirloom-doctools.
877 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
878 smaller runtime footprint builds. This is useful for embedded systems
879 which only require one chipset support.
881 If you load it as a module, make sure this is in /boot/loader.conf:
885 This will load the HAL, all chip/RF backends and if_ath_pci.
886 If you have if_ath_pci in /boot/loader.conf, ensure it is after
887 if_ath or it will not load any HAL chipset support.
889 If you want to selectively load things (eg on ye cheape ARM/MIPS
890 platforms where RAM is at a premium) you should:
893 * load the chip modules in question
894 * load ath_rate, ath_dfs
896 * load if_ath_pci and/or if_ath_ahb depending upon your particular
897 bus bind type - this is where probe/attach is done.
899 For further comments/feedback, poke adrian@ .
902 The "ino64" 64-bit inode project has been committed, which extends
903 a number of types to 64 bits. Upgrading in place requires care and
904 adherence to the documented upgrade procedure.
906 If using a custom kernel configuration ensure that the
907 COMPAT_FREEBSD11 option is included (as during the upgrade the
908 system will be running the ino64 kernel with the existing world).
910 For the safest in-place upgrade begin by removing previous build
911 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full
912 procedure documented below under the heading "To rebuild everything and
913 install it on the current system." Specifically, a reboot is required
914 after installing the new kernel before installing world. While an
915 installworld normally works by accident from multiuser after rebooting
916 the proper kernel, there are many cases where this will fail across this
917 upgrade and installworld from single user is required.
920 The NATM framework including the en(4), fatm(4), hatm(4), and
921 patm(4) devices has been removed. Consumers should plan a
922 migration before the end-of-life date for FreeBSD 11.
925 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
926 diff has not been implemented, if those are needed a newer version of
927 GNU diff is available via the diffutils package under the gdiff name.
930 As of r316810 for ipfilter, keep frags is no longer assumed when
931 keep state is specified in a rule. r316810 aligns ipfilter with
932 documentation in man pages separating keep frags from keep state.
933 This allows keep state to be specified without forcing keep frags
934 and allows keep frags to be specified independently of keep state.
935 To maintain previous behaviour, also specify keep frags with
936 keep state (as documented in ipf.conf.5).
939 arm64 builds now use the base system LLD 4.0.0 linker by default,
940 instead of requiring that the aarch64-binutils port or package be
941 installed. To continue using aarch64-binutils, set
942 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
945 The UDP optimization in entry 20160818 that added the sysctl
946 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
947 packets will no longer be treated as L3 broadcast packets.
950 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
951 use any explicitly assigned loopback address available in the jail
952 instead of using the first assigned address of the jail.
955 The ctl.ko module no longer implements the iSCSI target frontend:
956 cfiscsi.ko does instead.
958 If building cfiscsi.ko as a kernel module, the module can be loaded
959 via one of the following methods:
960 - `cfiscsi_load="YES"` in loader.conf(5).
961 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
962 - ctladm(8)/ctld(8), when compiled with iSCSI support
963 (`WITH_ISCSI=yes` in src.conf(5))
965 Please see cfiscsi(4) for more details.
968 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
969 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
970 same source (previously, the dependency of mmcsd.ko on mmc.ko was
971 missing, but mmcsd.ko now will refuse to load if it is incompatible
975 The syntax of ipfw(8) named states was changed to avoid ambiguity.
976 If you have used named states in the firewall rules, you need to modify
977 them after installworld and before rebooting. Now named states must
978 be prefixed with colon.
981 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
982 removed as the userland we provide cannot use them. The KMS version
983 (sys/dev/drm2) supports the same hardware.
986 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
987 Please see the 20141231 entry below for information about prerequisites
988 and upgrading, if you are not already using clang 3.5.0 or higher.
991 The code that provides support for ZFS .zfs/ directory functionality
992 has been reimplemented. It's not possible now to create a snapshot
993 by mkdir under .zfs/snapshot/. That should be the only user visible
997 EISA bus support has been removed. The WITH_EISA option is no longer
1001 MCA bus support has been removed.
1004 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
1005 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
1008 The EM_MULTIQUEUE kernel configuration option is deprecated now that
1009 the em(4) driver conforms to iflib specifications.
1012 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
1013 IFLIB. If you have a custom kernel configuration that excludes em(4)
1014 but you use igb(4), you need to re-add em(4) to your custom
1018 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
1019 Please see the 20141231 entry below for information about prerequisites
1020 and upgrading, if you are not already using clang 3.5.0 or higher.
1023 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
1024 Please see the 20141231 entry below for information about prerequisites
1025 and upgrading, if you are not already using clang 3.5.0 or higher.
1028 The layout of the pmap structure has changed for powerpc to put the pmap
1029 statistics at the front for all CPU variations. libkvm(3) and all tools
1030 that link against it need to be recompiled.
1033 isl(4) and cyapa(4) drivers now require a new driver,
1034 chromebook_platform(4), to work properly on Chromebook-class hardware.
1035 On other types of hardware the drivers may need to be configured using
1036 device hints. Please see the corresponding manual pages for details.
1039 The urtwn(4) driver was merged into rtwn(4) and now consists of
1040 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
1042 Also, firmware for RTL8188CE was renamed due to possible name
1043 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
1046 GNU rcs has been removed from base. It is available as packages:
1047 - rcs: Latest GPLv3 GNU rcs version.
1048 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
1052 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
1053 modules now requires that the kernel configuration contain the
1054 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
1057 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
1058 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
1061 Relocatable object files with the extension of .So have been renamed
1062 to use an extension of .pico instead. The purpose of this change is
1063 to avoid a name clash with shared libraries on case-insensitive file
1064 systems. On those file systems, foo.So is the same file as foo.so.
1067 GNU rcs has been turned off by default. It can (temporarily) be built
1068 again by adding WITH_RCS knob in src.conf.
1069 Otherwise, GNU rcs is available from packages:
1070 - rcs: Latest GPLv3 GNU rcs version.
1071 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
1074 The backup_uses_rcs functionality has been removed from rc.subr.
1077 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
1078 two separate components, QUEUE_MACRO_DEBUG_TRACE and
1079 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
1080 QUEUE_MACRO_DEBUG behavior.
1083 r304787 changed some ioctl interfaces between the iSCSI userspace
1084 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
1085 rebuilt to work with new kernels. __FreeBSD_version has been bumped
1089 The UDP receive code has been updated to only treat incoming UDP
1090 packets that were addressed to an L2 broadcast address as L3
1091 broadcast packets. It is not expected that this will affect any
1092 standards-conforming UDP application. The new behaviour can be
1093 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
1097 Remove the openbsd_poll system call.
1098 __FreeBSD_version has been bumped because of this.
1101 The stable/11 branch has been created from head@r302406.
1104 The libc stub for the pipe(2) system call has been replaced with
1105 a wrapper that calls the pipe2(2) system call and the pipe(2)
1106 system call is now only implemented by the kernels that include
1107 "options COMPAT_FREEBSD10" in their config file (this is the
1108 default). Users should ensure that this option is enabled in
1109 their kernel or upgrade userspace to r302092 before upgrading their
1113 CAM will now strip leading spaces from SCSI disks' serial numbers.
1114 This will affect users who create UFS filesystems on SCSI disks using
1115 those disk's diskid device nodes. For example, if /etc/fstab
1116 previously contained a line like
1117 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
1118 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
1119 transforms like gmirror may also be affected. ZFS users should
1123 The bitstring(3) API has been updated with new functionality and
1124 improved performance. But it is binary-incompatible with the old API.
1125 Objects built with the new headers may not be linked against objects
1126 built with the old headers.
1129 The brk and sbrk functions have been removed from libc on arm64.
1130 Binutils from ports has been updated to not link to these
1131 functions and should be updated to the latest version before
1132 installing a new libc.
1135 The armv6 port now defaults to hard float ABI. Limited support
1136 for running both hardfloat and soft float on the same system
1137 is available using the libraries installed with -DWITH_LIBSOFT.
1138 This has only been tested as an upgrade path for installworld
1139 and packages may fail or need manual intervention to run. New
1140 packages will be needed.
1142 To update an existing self-hosted armv6hf system, you must add
1143 TARGET_ARCH=armv6 on the make command line for both the build
1144 and the install steps.
1147 Kernel modules compiled outside of a kernel build now default to
1148 installing to /boot/modules instead of /boot/kernel. Many kernel
1149 modules built this way (such as those in ports) already overrode
1150 KMODDIR explicitly to install into /boot/modules. However,
1151 manually building and installing a module from /sys/modules will
1152 now install to /boot/modules instead of /boot/kernel.
1155 The CAM I/O scheduler has been committed to the kernel. There should be
1156 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
1157 list of known rogues that claim support for this but actually corrupt
1158 data is believed to be complete, be on the lookout for data
1159 corruption. The known rogue list is believed to be complete:
1161 o Crucial MX100, M550 drives with MU01 firmware.
1162 o Micron M510 and M550 drives with MU01 firmware.
1163 o Micron M500 prior to MU07 firmware
1164 o Samsung 830, 840, and 850 all firmwares
1165 o FCCT M500 all firmwares
1167 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
1168 with working NCQ TRIM. For Micron branded drives, see your sales rep for
1169 updated firmware. Black listed drives will work correctly because these
1170 drives work correctly so long as no NCQ TRIMs are sent to them. Given
1171 this list is the same as found in Linux, it's believed there are no
1172 other rogues in the market place. All other models from the above
1175 To be safe, if you are at all concerned, you can quirk each of your
1176 drives to prevent NCQ from being sent by setting:
1177 kern.cam.ada.X.quirks="0x2"
1178 in loader.conf. If the drive requires the 4k sector quirk, set the
1179 quirks entry to 0x3.
1182 The FAST_DEPEND build option has been removed and its functionality is
1183 now the one true way. The old mkdep(1) style of 'make depend' has
1184 been removed. See 20160311 for further details.
1187 Resource range types have grown from unsigned long to uintmax_t. All
1188 drivers, and anything using libdevinfo, need to be recompiled.
1191 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1192 builds. It no longer runs mkdep(1) during 'make depend', and the
1193 'make depend' stage can safely be skipped now as it is auto ran
1194 when building 'make all' and will generate all SRCS and DPSRCS before
1195 building anything else. Dependencies are gathered at compile time with
1196 -MF flags kept in separate .depend files per object file. Users should
1197 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1198 stale .depend files.
1201 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1202 kernel modules. Therefore, if you load any kernel modules at boot time,
1203 please install the boot loaders after you install the kernel, but before
1207 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1208 make installkernel KERNCONF=YOUR_KERNEL_HERE
1209 make -C sys/boot install
1210 <reboot in single user>
1212 Then follow the usual steps, described in the General Notes section,
1216 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
1217 see the 20141231 entry below for information about prerequisites and
1218 upgrading, if you are not already using clang 3.5.0 or higher.
1221 The AIO subsystem is now a standard part of the kernel. The
1222 VFS_AIO kernel option and aio.ko kernel module have been removed.
1223 Due to stability concerns, asynchronous I/O requests are only
1224 permitted on sockets and raw disks by default. To enable
1225 asynchronous I/O requests on all file types, set the
1226 vfs.aio.enable_unsafe sysctl to a non-zero value.
1229 The ELF object manipulation tool objcopy is now provided by the
1230 ELF Tool Chain project rather than by GNU binutils. It should be a
1231 drop-in replacement, with the addition of arm64 support. The
1232 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1233 to obtain the GNU version if necessary.
1236 Building ZFS pools on top of zvols is prohibited by default. That
1237 feature has never worked safely; it's always been prone to deadlocks.
1238 Using a zvol as the backing store for a VM guest's virtual disk will
1239 still work, even if the guest is using ZFS. Legacy behavior can be
1240 restored by setting vfs.zfs.vol.recursive=1.
1243 The NONE and HPN patches has been removed from OpenSSH. They are
1244 still available in the security/openssh-portable port.
1247 With the addition of ypldap(8), a new _ypldap user is now required
1248 during installworld. "mergemaster -p" can be used to add the user
1249 prior to installworld, as documented in the handbook.
1252 The tftp loader (pxeboot) now uses the option root-path directive. As a
1253 consequence it no longer looks for a pxeboot.4th file on the tftp
1254 server. Instead it uses the regular /boot infrastructure as with the
1258 The code to start recording plug and play data into the modules has
1259 been committed. While the old tools will properly build a new kernel,
1260 a number of warnings about "unknown metadata record 4" will be produced
1261 for an older kldxref. To avoid such warnings, make sure to rebuild
1262 the kernel toolchain (or world). Make sure that you have r292078 or
1263 later when trying to build 292077 or later before rebuilding.
1266 Debug data files are now built by default with 'make buildworld' and
1267 installed with 'make installworld'. This facilitates debugging but
1268 requires more disk space both during the build and for the installed
1269 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1273 r291527 changed the internal interface between the nfsd.ko and
1274 nfscommon.ko modules. As such, they must both be upgraded to-gether.
1275 __FreeBSD_version has been bumped because of this.
1278 Add support for unicode collation strings leads to a change of
1279 order of files listed by ls(1) for example. To get back to the old
1280 behaviour, set LC_COLLATE environment variable to "C".
1282 Databases administrators will need to reindex their databases given
1283 collation results will be different.
1285 Due to a bug in install(1) it is recommended to remove the ancient
1286 locales before running make installworld.
1288 rm -rf /usr/share/locale/*
1291 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
1292 libcrypto.so.7 or libssl.so.7 must be recompiled.
1295 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1296 Kernel modules isp_2400_multi and isp_2500_multi were removed and
1297 should be replaced with isp_2400 and isp_2500 modules respectively.
1300 The build previously allowed using 'make -n' to not recurse into
1301 sub-directories while showing what commands would be executed, and
1302 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1303 and 'make -N' will not.
1306 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1307 and etcupdate will now use this file. A custom sendmail.cf is now
1308 updated via this mechanism rather than via installworld. If you had
1309 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1310 want to remove the exclusion or change it to "always install".
1311 /etc/mail/sendmail.cf is now managed the same way regardless of
1312 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1313 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1316 Compatibility shims for legacy ATA device names have been removed.
1317 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1318 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1319 environment variables, /dev/ad* and /dev/ar* symbolic links.
1322 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1323 Please see the 20141231 entry below for information about prerequisites
1324 and upgrading, if you are not already using clang 3.5.0 or higher.
1327 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1328 and renamed from .symbols to .debug. This reduces the size requirements
1329 on the boot partition or file system and provides consistency with
1330 userland debug files.
1332 When using the supported kernel installation method the
1333 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1334 as is done with /boot/kernel.
1336 Developers wishing to maintain the historical behavior of installing
1337 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1340 The wireless drivers had undergone changes that remove the 'parent
1341 interface' from the ifconfig -l output. The rc.d network scripts
1342 used to check presence of a parent interface in the list, so old
1343 scripts would fail to start wireless networking. Thus, etcupdate(3)
1344 or mergemaster(8) run is required after kernel update, to update your
1345 rc.d scripts in /etc.
1348 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1349 These configurations are now automatically interpreted as
1350 'scrub fragment reassemble'.
1353 Kernel-loadable modules for the random(4) device are back. To use
1354 them, the kernel must have
1357 options RANDOM_LOADABLE
1359 kldload(8) can then be used to load random_fortuna.ko
1360 or random_yarrow.ko. Please note that due to the indirect
1361 function calls that the loadable modules need to provide,
1362 the build-in variants will be slightly more efficient.
1364 The random(4) kernel option RANDOM_DUMMY has been retired due to
1365 unpopularity. It was not all that useful anyway.
1368 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1369 Control over building the ELF Tool Chain tools is now provided by
1370 the WITHOUT_TOOLCHAIN knob.
1373 The polarity of Pulse Per Second (PPS) capture events with the
1374 uart(4) driver has been corrected. Prior to this change the PPS
1375 "assert" event corresponded to the trailing edge of a positive PPS
1376 pulse and the "clear" event was the leading edge of the next pulse.
1378 As the width of a PPS pulse in a typical GPS receiver is on the
1379 order of 1 millisecond, most users will not notice any significant
1380 difference with this change.
1382 Anyone who has compensated for the historical polarity reversal by
1383 configuring a negative offset equal to the pulse width will need to
1384 remove that workaround.
1387 The default group assigned to /dev/dri entries has been changed
1388 from 'wheel' to 'video' with the id of '44'. If you want to have
1389 access to the dri devices please add yourself to the video group
1392 # pw groupmod video -m $USER
1395 The menu.rc and loader.rc files will now be replaced during
1396 upgrades. Please migrate local changes to menu.rc.local and
1397 loader.rc.local instead.
1400 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1401 strings and strip have been removed. The src.conf(5) knob
1402 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1405 As ZFS requires more kernel stack pages than is the default on some
1406 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1407 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1409 Please consider using 'options KSTACK_PAGES=X' where X is greater
1410 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1413 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1414 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1415 default, i.e., they will not contain "::". For example, instead
1416 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1417 to have a more specific match, such as different map entries for
1418 IPv6:0:0 vs IPv6:0. This change requires that configuration
1419 data (including maps, files, classes, custom ruleset, etc.) must
1420 use the same format, so make certain such configuration data is
1421 upgrading. As a very simple check search for patterns like
1422 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1423 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1424 the cf option UseCompressedIPv6Addresses.
1427 The default kernel entropy-processing algorithm is now
1428 Fortuna, replacing Yarrow.
1430 Assuming you have 'device random' in your kernel config
1431 file, the configurations allow a kernel option to override
1432 this default. You may choose *ONE* of:
1434 options RANDOM_YARROW # Legacy /dev/random algorithm.
1435 options RANDOM_DUMMY # Blocking-only driver.
1437 If you have neither, you get Fortuna. For most people,
1438 read no further, Fortuna will give a /dev/random that works
1439 like it always used to, and the difference will be irrelevant.
1441 If you remove 'device random', you get *NO* kernel-processed
1442 entropy at all. This may be acceptable to folks building
1443 embedded systems, but has complications. Carry on reading,
1444 and it is assumed you know what you need.
1446 *PLEASE* read random(4) and random(9) if you are in the
1447 habit of tweaking kernel configs, and/or if you are a member
1448 of the embedded community, wanting specific and not-usual
1449 behaviour from your security subsystems.
1451 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1452 random', you will NOT have a functioning /dev/random, and
1453 many cryptographic features will not work, including SSH.
1454 You may also find strange behaviour from the random(3) set
1455 of library functions, in particular sranddev(3), srandomdev(3)
1456 and arc4random(3). The reason for this is that the KERN_ARND
1457 sysctl only returns entropy if it thinks it has some to
1458 share, and with RANDOM_DUMMY or no 'device random' this
1462 An additional fix for the issue described in the 20150614 sendmail
1463 entry below has been committed in revision 284717.
1466 FreeBSD's old make (fmake) has been removed from the system. It is
1467 available as the devel/fmake port or via pkg install fmake.
1470 The fix for the issue described in the 20150614 sendmail entry
1471 below has been committed in revision 284436. The work
1472 around described in that entry is no longer needed unless the
1473 default setting is overridden by a confDH_PARAMETERS configuration
1474 setting of '5' or pointing to a 512 bit DH parameter file.
1477 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1478 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1479 and devel/kyua to version 0.20+ and adjust any calling code to work
1480 with Kyuafile and kyua.
1483 The import of openssl to address the FreeBSD-SA-15:10.openssl
1484 security advisory includes a change which rejects handshakes
1485 with DH parameters below 768 bits. sendmail releases prior
1486 to 8.15.2 (not yet released), defaulted to a 512 bit
1487 DH parameter setting for client connections. To work around
1488 this interoperability, sendmail can be configured to use a
1489 2048 bit DH parameter by:
1491 1. Edit /etc/mail/`hostname`.mc
1492 2. If a setting for confDH_PARAMETERS does not exist or
1493 exists and is set to a string beginning with '5',
1494 replace it with '2'.
1495 3. If a setting for confDH_PARAMETERS exists and is set to
1496 a file path, create a new file with:
1497 openssl dhparam -out /path/to/file 2048
1498 4. Rebuild the .cf file:
1499 cd /etc/mail/; make; make install
1500 5. Restart sendmail:
1501 cd /etc/mail/; make restart
1503 A sendmail patch is coming, at which time this file will be
1507 Generation of legacy formatted entries have been disabled by default
1508 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1509 entries were converted to use the new format by default when the new,
1510 machine independent format have been added and supported since FreeBSD
1513 Please see the pwd_mkdb(8) manual page for further details.
1516 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1517 20141231 entry below for information about prerequisites and upgrading,
1518 if you are not already using 3.5.0 or higher.
1521 TI platform code switched to using vendor DTS files and this update
1522 may break existing systems running on Beaglebone, Beaglebone Black,
1525 - dtb files should be regenerated/reinstalled. Filenames are the
1526 same but content is different now
1527 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1528 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1529 addressing scheme is now pin 25 on /dev/gpioc3.
1530 - Pandaboard: /etc/ttys should be updated, serial console device is
1531 now /dev/ttyu2, not /dev/ttyu0
1534 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1535 If you need the GNU extension from groff soelim(1), install groff
1536 from package: pkg install groff, or via ports: textproc/groff.
1539 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1540 defined in symlink(7); previously symlinks were silently ignored.
1543 The const qualifier has been removed from iconv(3) to comply with
1544 POSIX. The ports tree is aware of this from r384038 onwards.
1547 Libraries specified by LIBADD in Makefiles must have a corresponding
1548 DPADD_<lib> variable to ensure correct dependencies. This is now
1549 enforced in src.libnames.mk.
1552 From legacy ata(4) driver was removed support for SATA controllers
1553 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1554 Kernel modules ataahci and ataadaptec were removed completely,
1555 replaced by ahci and mvs modules respectively.
1558 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1559 the 20141231 entry below for information about prerequisites and
1560 upgrading, if you are not already using 3.5.0 or higher.
1563 The 32-bit PowerPC kernel has been changed to a position-independent
1564 executable. This can only be booted with a version of loader(8)
1565 newer than January 31, 2015, so make sure to update both world and
1566 kernel before rebooting.
1569 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1570 but before r278950, the RNG was not seeded properly. Immediately
1571 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1572 ssh keys or openssl keys) that were generated w/ a kernel from that
1573 range. This does not affect programs that directly used /dev/random
1574 or /dev/urandom. All userland uses of arc4random(3) are affected.
1577 The autofs(4) ABI was changed in order to restore binary compatibility
1578 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1579 with the new kernel.
1582 The powerpc64 kernel has been changed to a position-independent
1583 executable. This can only be booted with a new version of loader(8),
1584 so make sure to update both world and kernel before rebooting.
1587 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1588 only release, no new features have been added. Please see the 20141231
1589 entry below for information about prerequisites and upgrading, if you
1590 are not already using 3.5.0.
1593 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1594 taken from the ELF Tool Chain project rather than GNU binutils. They
1595 should be drop-in replacements, with the addition of arm64 support.
1596 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1597 binutils tools, if necessary. See 20150805 for updated information.
1600 The default Unbound configuration now enables remote control
1601 using a local socket. Users who have already enabled the
1602 local_unbound service should regenerate their configuration
1603 by running "service local_unbound setup" as root.
1606 The GNU texinfo and GNU info pages have been removed.
1607 To be able to view GNU info pages please install texinfo from ports.
1610 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1612 As of this release, a prerequisite for building clang, llvm and lldb is
1613 a C++11 capable compiler and C++11 standard library. This means that to
1614 be able to successfully build the cross-tools stage of buildworld, with
1615 clang as the bootstrap compiler, your system compiler or cross compiler
1616 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1617 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1620 On any standard FreeBSD 10.x or 11.x installation, where clang and
1621 libc++ are on by default (that is, on x86 or arm), this should work out
1624 On 9.x installations where clang is enabled by default, e.g. on x86 and
1625 powerpc, libc++ will not be enabled by default, so libc++ should be
1626 built (with clang) and installed first. If both clang and libc++ are
1627 missing, build clang first, then use it to build libc++.
1629 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1630 the instructions for 9.x above.
1632 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1633 default, and do not build clang.
1635 Many embedded systems are resource constrained, and will not be able to
1636 build clang in a reasonable time, or in some cases at all. In those
1637 cases, cross building bootable systems on amd64 is a workaround.
1639 This new version of clang introduces a number of new warnings, of which
1640 the following are most likely to appear:
1644 This warns in two cases, for both C and C++:
1645 * When the code is trying to take the absolute value of an unsigned
1646 quantity, which is effectively a no-op, and almost never what was
1647 intended. The code should be fixed, if at all possible. If you are
1648 sure that the unsigned quantity can be safely cast to signed, without
1649 loss of information or undefined behavior, you can add an explicit
1650 cast, or disable the warning.
1652 * When the code is trying to take an absolute value, but the called
1653 abs() variant is for the wrong type, which can lead to truncation.
1654 If you want to disable the warning instead of fixing the code, please
1655 make sure that truncation will not occur, or it might lead to unwanted
1658 -Wtautological-undefined-compare and
1659 -Wundefined-bool-conversion
1661 These warn when C++ code is trying to compare 'this' against NULL, while
1662 'this' should never be NULL in well-defined C++ code. However, there is
1663 some legacy (pre C++11) code out there, which actively abuses this
1664 feature, which was less strictly defined in previous C++ versions.
1666 Squid and openjdk do this, for example. The warning can be turned off
1667 for C++98 and earlier, but compiling the code in C++11 mode might result
1668 in unexpected behavior; for example, the parts of the program that are
1669 unreachable could be optimized away.
1672 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1673 kernel sources have been removed. The .h files remain, since some
1674 utilities include them. This will need to be fixed later.
1675 If "mount -t oldnfs ..." is attempted, it will fail.
1676 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1677 the utilities will report errors.
1680 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1681 directories to top level SUBDIR variable when their parent
1682 directory is included in LOCAL_DIRS. Users with build systems with
1683 such hierarchies and without SUBDIR entries in the parent
1684 directory Makefiles should add them or add the directories to
1688 faith(4) and faithd(8) have been removed from the base system. Faith
1689 has been obsolete for a very long time.
1692 vt(4), the new console driver, is enabled by default. It brings
1693 support for Unicode and double-width characters, as well as
1694 support for UEFI and integration with the KMS kernel video
1697 You may need to update your console settings in /etc/rc.conf,
1698 most probably the keymap. During boot, /etc/rc.d/syscons will
1699 indicate what you need to do.
1701 vt(4) still has issues and lacks some features compared to
1702 syscons(4). See the wiki for up-to-date information:
1703 https://wiki.freebsd.org/Newcons
1705 If you want to keep using syscons(4), you can do so by adding
1706 the following line to /boot/loader.conf:
1710 pjdfstest has been integrated into kyua as an opt-in test suite.
1711 Please see share/doc/pjdfstest/README for more details on how to
1715 gperf has been removed from the base system for architectures
1716 that use clang. Ports that require gperf will obtain it from the
1720 pjdfstest has been moved from tools/regression/pjdfstest to
1724 At svn r271982, The default linux compat kernel ABI has been adjusted
1725 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1726 update. If you wish to continue using the linux-f10 compat ports,
1727 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1728 encouraged to update their linux-compat packages to linux-c6 during
1729 their next update cycle.
1732 The ofwfb driver, used to provide a graphics console on PowerPC when
1733 using vt(4), no longer allows mmap() of all physical memory. This
1734 will prevent Xorg on PowerPC with some ATI graphics cards from
1735 initializing properly unless x11-servers/xorg-server is updated to
1739 The xdev targets have been converted to using TARGET and
1740 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1743 The default unbound configuration has been modified to address
1744 issues with reverse lookups on networks that use private
1745 address ranges. If you use the local_unbound service, run
1746 "service local_unbound setup" as root to regenerate your
1747 configuration, then "service local_unbound reload" to load the
1751 The GNU texinfo and GNU info pages are not built and installed
1752 anymore, WITH_INFO knob has been added to allow to built and install
1754 UPDATE: see 20150102 entry on texinfo's removal
1757 The GNU readline library is now an INTERNALLIB - that is, it is
1758 statically linked into consumers (GDB and variants) in the base
1759 system, and the shared library is no longer installed. The
1760 devel/readline port is available for third party software that
1764 The Itanium architecture (ia64) has been removed from the list of
1765 known architectures. This is the first step in the removal of the
1769 Commit r268115 has added NFSv4.1 server support, merged from
1770 projects/nfsv4.1-server. Since this includes changes to the
1771 internal interfaces between the NFS related modules, a full
1772 build of the kernel and modules will be necessary.
1773 __FreeBSD_version has been bumped.
1776 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1777 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1778 which differs from the behaviour controlled by this knob.)
1781 Maximal length of the serial number in CTL was increased from 16 to
1782 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1783 and ctld, need to be rebuilt to work with a new kernel.
1786 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1787 1 respectively to match the upstream numbers. They were out of
1788 sync because, when they were originally added to FreeBSD, the
1789 upstream versions were not respected. These libraries are private
1790 and not yet built by default, so renumbering them should be a
1791 non-issue. However, unclean source trees will yield broken test
1792 programs once the operator executes "make delete-old-libs" after a
1793 "make installworld".
1795 Additionally, the atf-sh binary was made private by moving it into
1796 /usr/libexec/. Already-built shell test programs will keep the
1797 path to the old binary so they will break after "make delete-old"
1800 If you are using WITH_TESTS=yes (not the default), wipe the object
1801 tree and rebuild from scratch to prevent spurious test failures.
1802 This is only needed once: the misnumbered libraries and misplaced
1803 binaries have been added to OptionalObsoleteFiles.inc so they will
1804 be removed during a clean upgrade.
1807 Clang and llvm have been upgraded to 3.4.1 release.
1810 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1811 be removed to avoid issues in the future (and has been added to
1815 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1816 past, it affected all builds that used the bsd.*.mk files. The old
1817 behavior was a bug, but people may have relied upon it. To get this
1818 behavior back, you can .include /etc/src.conf from /etc/make.conf
1819 (which is still global and isn't changed). This also changes the
1820 behavior of incremental builds inside the tree of individual
1821 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1822 Although this has survived make universe and some upgrade scenarios,
1823 other upgrade scenarios may have broken. At least one form of
1824 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1825 as well... In cases where MAKESYSPATH isn't working with this
1826 setting, you'll need to set it to the full path to your tree.
1828 One side effect of all this cleaning up is that bsd.compiler.mk
1829 is no longer implicitly included by bsd.own.mk. If you wish to
1830 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1834 The lindev device has been removed since /dev/full has been made a
1835 standard device. __FreeBSD_version has been bumped.
1838 The knob WITHOUT_VI was added to the base system, which controls
1839 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1840 in order to reorder files share/termcap and didn't build ex(1) as a
1841 build tool, so building/installing with WITH_VI is highly advised for
1842 build hosts for older releases.
1844 This issue has been fixed in stable/9 and stable/10 in r277022 and
1845 r276991, respectively.
1848 The YES_HESIOD knob has been removed. It has been obsolete for
1849 a decade. Please move to using WITH_HESIOD instead or your builds
1850 will silently lack HESIOD.
1853 The uart(4) driver has been changed with respect to its handling
1854 of the low-level console. Previously the uart(4) driver prevented
1855 any process from changing the baudrate or the CLOCAL and HUPCL
1856 control flags. By removing the restrictions, operators can make
1857 changes to the serial console port without having to reboot.
1858 However, when getty(8) is started on the serial device that is
1859 associated with the low-level console, a misconfigured terminal
1860 line in /etc/ttys will now have a real impact.
1861 Before upgrading the kernel, make sure that /etc/ttys has the
1862 serial console device configured as 3wire without baudrate to
1863 preserve the previous behaviour. E.g:
1864 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1867 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1868 to improve performance. To re-enable it, if needed, run rpcbind
1869 with command line option -W.
1872 Switched back to the GPL dtc compiler due to updates in the upstream
1873 dts files not being supported by the BSDL dtc compiler. You will need
1874 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1875 may result while building dtb files during a kernel build if you fail
1876 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1879 Clang and llvm have been upgraded to 3.4 release.
1882 The nve(4) driver has been removed. Please use the nfe(4) driver
1883 for NVIDIA nForce MCP Ethernet adapters instead.
1886 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1887 This could cause certain C++ applications using shared libraries built
1888 against the previous version of libc++ to crash. The incompatibility
1889 has now been fixed, but any C++ applications or shared libraries built
1890 between r261283 and r261801 should be recompiled.
1893 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1894 capability mode support. Please note that enabling the feature in
1895 kernel is still highly recommended.
1898 OpenSSH is now built with sandbox support, and will use sandbox as
1899 the default privilege separation method. This requires Capsicum
1900 capability mode support in kernel.
1903 The libelf and libdwarf libraries have been updated to newer
1904 versions from upstream. Shared library version numbers for
1905 these two libraries were bumped. Any ports or binaries
1906 requiring these two libraries should be recompiled.
1907 __FreeBSD_version is bumped to 1100006.
1910 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1911 instead of providing an explicit one, this would prevent such
1912 Makefile from providing its own Kyuafile in the future during
1913 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1914 intervention is needed to clean an objdir if you use NO_CLEAN:
1915 # find /usr/obj -name Kyuafile | xargs rm -f
1918 The behavior of gss_pseudo_random() for the krb5 mechanism
1919 has changed, for applications requesting a longer random string
1920 than produced by the underlying enctype's pseudo-random() function.
1921 In particular, the random string produced from a session key of
1922 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1923 be different at the 17th octet and later, after this change.
1924 The counter used in the PRF+ construction is now encoded as a
1925 big-endian integer in accordance with RFC 4402.
1926 __FreeBSD_version is bumped to 1100004.
1929 The WITHOUT_ATF build knob has been removed and its functionality
1930 has been subsumed into the more generic WITHOUT_TESTS. If you were
1931 using the former to disable the build of the ATF libraries, you
1932 should change your settings to use the latter.
1935 The default version of mtree is nmtree which is obtained from
1936 NetBSD. The output is generally the same, but may vary
1937 slightly. If you found you need identical output adding
1938 "-F freebsd9" to the command line should do the trick. For the
1939 time being, the old mtree is available as fmtree.
1942 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1943 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1944 1.1.4_8 and verify bsdyml not linked in, before running "make
1946 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1948 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1951 The stable/10 branch has been created in subversion from head
1958 Sometimes, obscure build problems are the result of environment
1959 poisoning. This can happen because the make utility reads its
1960 environment when searching for values for global variables. To run
1961 your build attempts in an "environmental clean room", prefix all make
1962 commands with 'env -i '. See the env(1) manual page for more details.
1963 Occasionally a build failure will occur with "make -j" due to a race
1964 condition. If this happens try building again without -j, and please
1965 report a bug if it happens consistently.
1967 When upgrading from one major version to another it is generally best to
1968 upgrade to the latest code in the currently installed branch first, then
1969 do an upgrade to the new branch. This is the best-tested upgrade path,
1970 and has the highest probability of being successful. Please try this
1971 approach if you encounter problems with a major version upgrade. Since
1972 the stable 4.x branch point, one has generally been able to upgrade from
1973 anywhere in the most recent stable branch to head / current (or even the
1974 last couple of stable branches). See the top of this file when there's
1977 When upgrading a live system, having a root shell around before
1978 installing anything can help undo problems. Not having a root shell
1979 around can lead to problems if pam has changed too much from your
1980 starting point to allow continued authentication after the upgrade.
1982 This file should be read as a log of events. When a later event changes
1983 information of a prior event, the prior event should not be deleted.
1984 Instead, a pointer to the entry with the new information should be
1985 placed in the old entry. Readers of this file should also sanity check
1986 older entries before relying on them blindly. Authors of new entries
1987 should write them with this in mind.
1991 When upgrading the boot ZFS pool to a new version, always follow
1994 1.) recompile and reinstall the ZFS boot loader and boot block
1995 (this is part of "make buildworld" and "make installworld")
1997 2.) update the ZFS boot block on your boot drive
1999 The following example updates the ZFS boot block on the first
2000 partition (freebsd-boot) of a GPT partitioned drive ada0:
2001 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
2003 Non-boot pools do not need these updates.
2007 If you are updating from a prior version of FreeBSD (even one just
2008 a few days old), you should follow this procedure. It is the most
2009 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2011 make kernel-toolchain
2012 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2013 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2015 To test a kernel once
2016 ---------------------
2017 If you just want to boot a kernel once (because you are not sure
2018 if it works, or if you want to boot a known bad kernel to provide
2019 debugging information) run
2020 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2021 nextboot -k testkernel
2023 To rebuild everything and install it on the current system.
2024 -----------------------------------------------------------
2025 # Note: sometimes if you are running current you gotta do more than
2026 # is listed here if you are upgrading from a really old current.
2028 <make sure you have good level 0 dumps>
2030 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2031 make installkernel KERNCONF=YOUR_KERNEL_HERE
2033 <reboot in single user> [3]
2040 To cross-install current onto a separate partition
2041 --------------------------------------------------
2042 # In this approach we use a separate partition to hold
2043 # current's root, 'usr', and 'var' directories. A partition
2044 # holding "/", "/usr" and "/var" should be about 2GB in
2047 <make sure you have good level 0 dumps>
2050 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2051 <maybe newfs current's root partition>
2052 <mount current's root partition on directory ${CURRENT_ROOT}>
2053 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
2054 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2055 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2056 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2057 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2058 <reboot into current>
2059 <do a "native" rebuild/install as described in the previous section>
2060 <maybe install compatibility libraries from ports/misc/compat*>
2064 To upgrade in-place from stable to current
2065 ----------------------------------------------
2066 <make sure you have good level 0 dumps>
2068 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
2069 make installkernel KERNCONF=YOUR_KERNEL_HERE
2071 <reboot in single user> [3]
2078 Make sure that you've read the UPDATING file to understand the
2079 tweaks to various things you need. At this point in the life
2080 cycle of current, things change often and you are on your own
2081 to cope. The defaults can also change, so please read ALL of
2082 the UPDATING entries.
2084 Also, if you are tracking -current, you must be subscribed to
2085 freebsd-current@freebsd.org. Make sure that before you update
2086 your sources that you have read and understood all the recent
2087 messages there. If in doubt, please track -stable which has
2088 much fewer pitfalls.
2090 [1] If you have third party modules, such as vmware, you
2091 should disable them at this point so they don't crash your
2094 [3] From the bootblocks, boot -s, and then do
2098 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed
2099 cd src # full path to source
2100 adjkerntz -i # if CMOS is wall time
2101 Also, when doing a major release upgrade, it is required that
2102 you boot into single user mode to do the installworld.
2104 [4] Note: This step is non-optional. Failure to do this step
2105 can result in a significant reduction in the functionality of the
2106 system. Attempting to do it by hand is not recommended and those
2107 that pursue this avenue should read this file carefully, as well
2108 as the archives of freebsd-current and freebsd-hackers mailing lists
2109 for potential gotchas. The -U option is also useful to consider.
2110 See mergemaster(8) for more information.
2112 [5] Usually this step is a no-op. However, from time to time
2113 you may need to do this if you get unknown user in the following
2114 step. It never hurts to do it all the time. You may need to
2115 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2116 install) after the buildworld before this step if you last updated
2117 from current before 20130425 or from -stable before 20130430.
2119 [6] This only deletes old files and directories. Old libraries
2120 can be deleted by "make delete-old-libs", but you have to make
2121 sure that no program is using those libraries anymore.
2123 [8] The new kernel must be able to run existing binaries used by an
2124 installworld. When upgrading across major versions, the new kernel's
2125 configuration must include the correct COMPAT_FREEBSD<n> option for
2126 existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure
2127 to do so may leave you with a system that is hard to boot to recover. A
2128 GENERIC kernel will include suitable compatibility options to run
2129 binaries from older branches. Note that the ability to run binaries
2130 from unsupported branches is not guaranteed.
2132 Make sure that you merge any new devices from GENERIC since the
2133 last time you updated your kernel config file. Options also
2134 change over time, so you may need to adjust your custom kernels
2137 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2138 "?=" instead of the "=" assignment operator, so that buildworld can
2139 override the CPUTYPE if it needs to.
2141 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2142 not on the command line, or in /etc/make.conf. buildworld will
2143 warn if it is improperly defined.
2146 This file contains a list, in reverse chronological order, of major
2147 breakages in tracking -current. It is not guaranteed to be a complete
2148 list of such breakages, and only contains entries since September 23, 2011.
2149 If you need to see UPDATING entries from before that date, you will need
2150 to fetch an UPDATING file from an older FreeBSD release.
2152 Copyright information:
2154 Copyright 1998-2009 M. Warner Losh <imp@FreeBSD.org>
2156 Redistribution, publication, translation and use, with or without
2157 modification, in full or in part, in any form or format of this
2158 document are permitted without further permission from the author.
2160 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2161 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2162 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2163 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2164 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2165 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2166 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2167 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2168 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2169 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2170 POSSIBILITY OF SUCH DAMAGE.
2172 Contact Warner Losh if you have any questions about your use of