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