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: FreeBSD has switched from gcc to clang. If you have trouble bootstrapping
15 from older versions of FreeBSD, try WITHOUT_CLANG and WITH_GCC to bootstrap to
16 the tip of head, and then rebuild without this option. The bootstrap process
17 from older version of current across the gcc/clang cutover is a bit fragile.
19 NOTE TO PEOPLE WHO THINK THAT FreeBSD 12.x IS SLOW:
20 FreeBSD 12.x has many debugging features turned on, in both the kernel
21 and userland. These features attempt to detect incorrect use of
22 system primitives, and encourage loud failure through extra sanity
23 checking and fail stop semantics. They also substantially impact
24 system performance. If you want to do performance measurement,
25 benchmarking, and optimization, you'll want to turn them off. This
26 includes various WITNESS- related kernel options, INVARIANTS, malloc
27 debugging flags in userland, and various verbose features in the
28 kernel. Many developers choose to disable these features on build
29 machines to maximize performance. (To completely disable malloc
30 debugging, define MALLOC_PRODUCTION in /etc/make.conf, or to merely
31 disable the most expensive debugging functionality run
32 "ln -s 'abort:false,junk:false' /etc/malloc.conf".)
35 The Yarrow CSPRNG has been removed from the kernel as it has not been
36 supported by its designers since at least 2003. Fortuna has been the
37 default since FreeBSD-11.
40 devctl freeze/that have gone into the tree, the rc scripts have been
41 updated to use them and devmatch has been changed. You should update
42 kernel, userland and rc scripts all at the same time.
45 The default interpreter has been switched from 4th to Lua.
46 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
47 interpreter. If you have custom FORTH code you will need to set
48 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
49 src.conf for the build. This will create default hard links between
50 loader and loader_4th instead of loader and loader_lua, the new default.
51 If you are using UEFI it will create the proper hard link to loader.efi.
53 bhyve uses userboot.so. It remains 4th-only until some issues are solved
54 regarding coexisting with multiple versions of FreeBSD are resolved.
57 ls(1) now respects the COLORTERM environment variable used in other
58 systems and software to indicate that a colored terminal is both
59 supported and desired. If ls(1) is suddenly emitting colors, they may
60 be disabled again by either removing the unwanted COLORTERM from your
61 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
62 may not be observed in a future release.
65 The default pager for most commands has been changed to "less". To
66 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
70 The jedec_ts(4) driver has been removed. A superset of its functionality
71 is available in the jedec_dimm(4) driver, and the manpage for that
72 driver includes migration instructions. If you have "device jedec_ts"
73 in your kernel configuration file, it must be removed.
76 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
77 This should have no effect if the kernel is booted via BIOS/legacy boot.
78 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
79 has a buggy firmware that prevents a successful boot due to use of
83 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
84 support has been removed from the tree. These ports were
85 obsolete and/or known to be broken for many years.
88 loader.efi has been augmented to participate more fully in the
89 UEFI boot manager protocol. loader.efi will now look at the
90 BootXXXX environment variable to determine if a specific kernel
91 or root partition was specified. XXXX is derived from BootCurrent.
92 efibootmgr(8) manages these standard UEFI variables.
95 zfsloader's functionality has now been folded into loader.
96 zfsloader is no longer necessary once you've updated your
97 boot blocks. For a transition period, we will install a
98 hardlink for zfsloader to loader to allow a smooth transition
99 until the boot blocks can be updated (hard link because old
100 zfs boot blocks don't understand symlinks).
103 ARM64 now have efifb support, if you want to have serial console
104 on your arm64 board when an screen is connected and the bootloader
105 setup a frambuffer for us to use, just add :
109 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
110 an screen connected as the firmware will setup a framebuffer are that
111 u-boot will expose as an EFI framebuffer.
114 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
115 or take steps to update /etc/passwd before doing installworld on
116 existing systems. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
117 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
118 the ntp config file contain options that change file/dir locations.
119 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
120 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
121 taking steps to ensure that all required files/dirs are accessible
125 Big endian arm support has been removed.
128 The static environment setup in kernel configs is no longer mutually
129 exclusive with the loader(8) environment by default. In order to
130 restore the previous default behavior of disabling the loader(8)
131 environment if a static environment is present, you must specify
132 loader_env.disabled=1 in the static environment.
135 The ABI of syscalls used by management tools like sockstat and
136 netstat has been broken to allow 32-bit binaries to work on
137 64-bit kernels without modification. These programs will need
138 to match the kernel in order to function. External programs may
139 require minor modifications to accommodate a change of type in
140 structures from pointers to 64-bit virtual addresses.
143 On i386 and amd64 atomics are now inlined. Out of tree modules using
144 atomics will need to be rebuilt.
147 The '%I' format in the kern.corefile sysctl limits the number of
148 core files that a process can generate to the number stored in the
149 debug.ncores sysctl. The '%I' format is replaced by the single digit
150 index. Previously, if all indexes were taken the kernel would overwrite
151 only a core file with the highest index in a filename.
152 Currently the system will create a new core file if there is a free
153 index or if all slots are taken it will overwrite the oldest one.
156 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
157 6.0.1. Please see the 20141231 entry below for information about
158 prerequisites and upgrading, if you are not already using clang 3.5.0
162 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
163 needed to be changed to work with it. This change was made with r335763
164 and requires a mergemaster / etcupdate / etc to update the installed file.
167 r334930 changed the interface between the NFS modules, so they all
168 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
171 The kernel / userland interface for devinfo changed, so you'll
172 need a new kernel and userland as a pair for it to work (rebuilding
173 lib/libdevinfo is all that's required). devinfo and devmatch will
174 not work, but everything else will when there's a mismatch.
177 The on-disk format for hwpmc callchain records has changed to include
178 threadid corresponding to a given record. This changes the field offsets
179 and thus requires that libpmcstat be rebuilt before using a kernel
183 The vxge(4) driver has been removed. This driver was introduced into
184 HEAD one week before the Exar left the Ethernet market and is not
185 known to be used. If you have device vxge in your kernel config file
189 The amd64 kernel now requires a ld that supports ifunc to produce a
190 working kernel, either lld or a newer binutils. lld is built by default
191 on amd64, and the 'buildkernel' target uses it automatically. However,
192 it is not the default linker, so building the kernel the traditional
193 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
194 binutils port/package). lld will soon be default, and this requirement
198 The nxge(4) driver has been removed. This driver was for PCI-X 10g
199 cards made by s2io/Neterion. The company was aquired by Exar and
200 no longer sells or supports Ethernet products. If you have device
201 nxge in your kernel config file it must be removed.
204 The tz database (tzdb) has been updated to 2018e. This version more
205 correctly models time stamps in time zones with negative DST such as
206 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
207 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
208 time zone abbreviations and the tm_isdst flag.
211 The ixgb(4) driver has been removed. This driver was for an early and
212 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
213 quickly shifted to the long lived ixgbe family. If you have device
214 ixgb in your kernel config file it must be removed.
217 The lmc(4) driver has been removed. This was a WAN interface
218 card that was already reportedly rare in 2003, and had an ambiguous
219 license. If you have device lmc in your kernel config file it must
223 Support for Arcnet networks has been removed. If you have device
224 arcnet or device cm in your kernel config file they must be
228 Support for FDDI networks has been removed. If you have device
229 fddi or device fpa in your kernel config file they must be
233 In addition to supporting RFC 3164 formatted messages, the
234 syslogd(8) service is now capable of parsing RFC 5424 formatted
235 log messages. The main benefit of using RFC 5424 is that clients
236 may now send log messages with timestamps containing year numbers,
237 microseconds and time zone offsets.
239 Similarly, the syslog(3) C library function has been altered to
240 send RFC 5424 formatted messages to the local system logging
241 daemon. On systems using syslogd(8), this change should have no
242 negative impact, as long as syslogd(8) and the C library are
243 updated at the same time. On systems using a different system
244 logging daemon, it may be necessary to make configuration
245 adjustments, depending on the software used.
247 When using syslog-ng, add the 'syslog-protocol' flag to local
248 input sources to enable parsing of RFC 5424 formatted messages:
251 unix-dgram("/var/run/log" flags(syslog-protocol));
254 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
255 of the 'imuxsock' module to let messages be processed by the
256 regular RFC 3164/5424 parsing pipeline:
258 module(load="imuxsock" SysSock.UseSpecialParser="off")
260 Do note that these changes only affect communication between local
261 applications and syslogd(8). The format that syslogd(8) uses to
262 store messages on disk or forward messages to other systems
263 remains unchanged. syslogd(8) still uses RFC 3164 for these
264 purposes. Options to customize this behaviour will be added in the
265 future. Utilities that process log files stored in /var/log are
266 thus expected to continue to function as before.
268 __FreeBSD_version has been incremented to 1200061 to denote this
272 Support for token ring networks has been removed. If you
273 have "device token" in your kernel config you should remove
274 it. No device drivers supported token ring.
277 makefs was modified to be able to tag ISO9660 El Torito boot catalog
278 entries as EFI instead of overloading the i386 tag as done previously.
279 The amd64 mkisoimages.sh script used to build amd64 ISO images for
280 release was updated to use this. This may mean that makefs must be
281 updated before "make cdrom" can be run in the release directory. This
282 should be as simple as:
284 $ cd $SRCDIR/usr.sbin/makefs
285 $ make depend all install
288 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
289 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
290 Co-existance for the transition period will come shortly. Booting is a
291 complex environment and test coverage for Lua-enabled loaders has been
292 thin, so it would be prudent to assume it might not work and make
293 provisions for backup boot methods.
296 devmatch functionality has been turned on in devd. It will automatically
297 load drivers for unattached devices. This may cause unexpected drivers to
298 be loaded. Please report any problems to current@ and imp@freebsd.org.
301 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
302 6.0.0. Please see the 20141231 entry below for information about
303 prerequisites and upgrading, if you are not already using clang 3.5.0
307 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
308 This means it is used to link the kernel and userland libraries and
309 executables, but is not yet installed as /usr/bin/ld by default.
311 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
312 WITHOUT_LLD_BOOTSTRAP=yes
315 On i386, pmtimer has been removed. Its functionality has been folded
316 into apm. It was a no-op on ACPI in current for a while now (but was still
317 needed on i386 in FreeBSD 11 and earlier). Users may need to remove it
318 from kernel config files.
321 The use of RSS hash from the network card aka flowid has been
322 disabled by default for lagg(4) as it's currently incompatible with
323 the lacp and loadbalance protocols.
325 This can be re-enabled by setting the following in loader.conf:
326 net.link.lagg.default_use_flowid="1"
329 The SW_WATCHDOG option is no longer necessary to enable the
330 hardclock-based software watchdog if no hardware watchdog is
331 configured. As before, SW_WATCHDOG will cause the software
332 watchdog to be enabled even if a hardware watchdog is configured.
335 r326887 fixes the issue described in the 20171214 UPDATING entry.
336 r326888 flips the switch back to building GELI support always.
339 r362593 broke ZFS + GELI support for reasons unknown. However,
340 it also broke ZFS support generally, so GELI has been turned off
341 by default as the lesser evil in r326857. If you boot off ZFS and/or
342 GELI, it might not be a good time to update.
345 PowerPC users must update loader(8) by rebuilding world before
346 installing a new kernel, as the protocol connecting them has
347 changed. Without the update, loader metadata will not be passed
348 successfully to the kernel and users will have to enter their
349 root partition at the kernel mountroot prompt to continue booting.
350 Newer versions of loader can boot old kernels without issue.
353 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
354 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
355 to WITH/OUT_LOADER_GELI.
358 The naive and non-compliant support of posix_fallocate(2) in ZFS
359 has been removed as of r325320. The system call now returns EINVAL
360 when used on a ZFS file. Although the new behavior complies with the
361 standard, some consumers are not prepared to cope with it.
362 One known victim is lld prior to r325420.
365 Building in a FreeBSD src checkout will automatically create object
366 directories now rather than store files in the current directory if
367 'make obj' was not ran. Calling 'make obj' is no longer necessary.
368 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
369 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
373 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
374 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
375 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
376 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
377 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
378 The UNIFIED_OBJDIR option is a transitional feature that will be
379 removed for 12.0 release; please migrate to the new format for any
380 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
381 than hardcoding paths.
384 The native-xtools target no longer installs the files by default to the
385 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
386 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
389 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
390 options are changing from controlling the build if defined / undefined
391 to controlling the build with explicit 'yes' or 'no' values. They will
392 shift to WITH/WITHOUT options to match other options in the system.
395 libstand has turned into a private library for sys/boot use only.
396 It is no longer supported as a public interface outside of sys/boot.
399 The arm port has split armv6 into armv6 and armv7. armv7 is now
400 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
401 and are running a kernel from before r324363, you will need to add
402 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
405 When building multiple kernels using KERNCONF, non-existent KERNCONF
406 files will produce an error and buildkernel will fail. Previously
407 missing KERNCONF files silently failed giving no indication as to
408 why, only to subsequently discover during installkernel that the
409 desired kernel was never built in the first place.
412 The default serial number format for CTL LUNs has changed. This will
413 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
414 or iSCSI clients care about their LUNs' serial numbers. Users who
415 require serial number stability should hardcode serial numbers in
419 For 32-bit arm compiled for hard-float support, soft-floating point
420 binaries now always get their shared libraries from
421 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
422 /usr/libsoft also existed). Only users with a hard-float ld.so, but
423 soft-float everything else should be affected.
426 The geli password typed at boot is now hidden. To restore the previous
427 behavior, see geli(8) for configuration options.
430 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
431 sysctl values. Minor nit, but requires a rebuild of both world/kernel
435 "make check" behavior (made in ^/head@r295380) has been changed to
436 execute from a limited sandbox, as opposed to executing from
440 - The "beforecheck" and "aftercheck" targets are now specified.
441 - ${CHECKDIR} (added in commit noted above) has been removed.
442 - Legacy behavior can be enabled by setting
443 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
445 If the limited sandbox mode is enabled, "make check" will execute
446 "make distribution", then install, execute the tests, and clean up the
447 sandbox if successful.
449 The "make distribution" and "make install" targets are typically run as
450 root to set appropriate permissions and ownership at installation time.
451 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
452 environment if executing "make check" with limited sandbox mode using
453 an unprivileged user.
456 Since the switch to GPT disk labels, fsck for UFS/FFS has been
457 unable to automatically find alternate superblocks. As of r322297,
458 the information needed to find alternate superblocks has been
459 moved to the end of the area reserved for the boot block.
460 Filesystems created with a newfs of this vintage or later
461 will create the recovery information. If you have a filesystem
462 created prior to this change and wish to have a recovery block
463 created for your filesystem, you can do so by running fsck in
464 foreground mode (i.e., do not use the -p or -y options). As it
465 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
466 to which you should answer yes.
469 As of r321665, an NFSv4 server configuration that services
470 Kerberos mounts or clients that do not support the uid/gid in
471 owner/owner_group string capability, must explicitly enable
472 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
473 machine's /etc/rc.conf file.
476 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
477 Please see the 20141231 entry below for information about prerequisites
478 and upgrading, if you are not already using clang 3.5.0 or higher.
481 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
482 r-commands (rlogin, rsh, etc.) to be built with the base system.
485 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
486 a very major ABI incompatible change, so users of FreeBSD/powerpc must
487 be careful when performing source upgrades. It is best to run
488 'make installworld' from an alternate root system, either a live
489 CD/memory stick, or a temporary root partition. Additionally, all ports
490 must be recompiled. powerpc64 is largely unaffected, except in the case
491 of 32-bit compatibility. All 32-bit binaries will be affected.
494 Forward compatibility for the "ino64" project have been committed. This
495 will allow most new binaries to run on older kernels in a limited
496 fashion. This prevents many of the common foot-shooting actions in the
497 upgrade as well as the limited ability to roll back the kernel across
498 the ino64 upgrade. Complicated use cases may not work properly, though
499 enough simpler ones work to allow recovery in most situations.
502 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
503 if you require the GPL compiler.
506 The internal ABI used for communication between the NFS kernel modules
507 was changed by r320085, so __FreeBSD_version was bumped to
508 ensure all the NFS related modules are updated together.
511 The ABI of struct event was changed by extending the data
512 member to 64bit and adding ext fields. For upgrade, same
513 precautions as for the entry 20170523 "ino64" must be
517 The GNU roff toolchain has been removed from base. To render manpages
518 which are not supported by mandoc(1), man(1) can fallback on GNU roff
519 from ports (and recommends to install it).
520 To render roff(7) documents, consider using GNU roff from ports or the
521 heirloom doctools roff toolchain from ports via pkg install groff or
522 via pkg install heirloom-doctools.
525 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
526 smaller runtime footprint builds. This is useful for embedded systems
527 which only require one chipset support.
529 If you load it as a module, make sure this is in /boot/loader.conf:
533 This will load the HAL, all chip/RF backends and if_ath_pci.
534 If you have if_ath_pci in /boot/loader.conf, ensure it is after
535 if_ath or it will not load any HAL chipset support.
537 If you want to selectively load things (eg on ye cheape ARM/MIPS
538 platforms where RAM is at a premium) you should:
541 * load the chip modules in question
542 * load ath_rate, ath_dfs
544 * load if_ath_pci and/or if_ath_ahb depending upon your particular
545 bus bind type - this is where probe/attach is done.
547 For further comments/feedback, poke adrian@ .
550 The "ino64" 64-bit inode project has been committed, which extends
551 a number of types to 64 bits. Upgrading in place requires care and
552 adherence to the documented upgrade procedure.
554 If using a custom kernel configuration ensure that the
555 COMPAT_FREEBSD11 option is included (as during the upgrade the
556 system will be running the ino64 kernel with the existing world).
558 For the safest in-place upgrade begin by removing previous build
559 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
560 full procedure documented below under the heading "To rebuild
561 everything and install it on the current system." Specifically,
562 a reboot is required after installing the new kernel before
566 The NATM framework including the en(4), fatm(4), hatm(4), and
567 patm(4) devices has been removed. Consumers should plan a
568 migration before the end-of-life date for FreeBSD 11.
571 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
572 diff has not been implemented, if those are needed a newer version of
573 GNU diff is available via the diffutils package under the gdiff name.
576 As of r316810 for ipfilter, keep frags is no longer assumed when
577 keep state is specified in a rule. r316810 aligns ipfilter with
578 documentation in man pages separating keep frags from keep state.
579 This allows keep state to be specified without forcing keep frags
580 and allows keep frags to be specified independently of keep state.
581 To maintain previous behaviour, also specify keep frags with
582 keep state (as documented in ipf.conf.5).
585 arm64 builds now use the base system LLD 4.0.0 linker by default,
586 instead of requiring that the aarch64-binutils port or package be
587 installed. To continue using aarch64-binutils, set
588 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
591 The UDP optimization in entry 20160818 that added the sysctl
592 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
593 packets will no longer be treated as L3 broadcast packets.
596 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
597 use any explicitly assigned loopback address available in the jail
598 instead of using the first assigned address of the jail.
601 The ctl.ko module no longer implements the iSCSI target frontend:
602 cfiscsi.ko does instead.
604 If building cfiscsi.ko as a kernel module, the module can be loaded
605 via one of the following methods:
606 - `cfiscsi_load="YES"` in loader.conf(5).
607 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
608 - ctladm(8)/ctld(8), when compiled with iSCSI support
609 (`WITH_ISCSI=yes` in src.conf(5))
611 Please see cfiscsi(4) for more details.
614 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
615 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
616 same source (previously, the dependency of mmcsd.ko on mmc.ko was
617 missing, but mmcsd.ko now will refuse to load if it is incompatible
621 The syntax of ipfw(8) named states was changed to avoid ambiguity.
622 If you have used named states in the firewall rules, you need to modify
623 them after installworld and before rebooting. Now named states must
624 be prefixed with colon.
627 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
628 removed as the userland we provide cannot use them. The KMS version
629 (sys/dev/drm2) supports the same hardware.
632 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
633 Please see the 20141231 entry below for information about prerequisites
634 and upgrading, if you are not already using clang 3.5.0 or higher.
637 The code that provides support for ZFS .zfs/ directory functionality
638 has been reimplemented. It's not possible now to create a snapshot
639 by mkdir under .zfs/snapshot/. That should be the only user visible
643 EISA bus support has been removed. The WITH_EISA option is no longer
647 MCA bus support has been removed.
650 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
651 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
654 The EM_MULTIQUEUE kernel configuration option is deprecated now that
655 the em(4) driver conforms to iflib specifications.
658 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
659 IFLIB. If you have a custom kernel configuration that excludes em(4)
660 but you use igb(4), you need to re-add em(4) to your custom configuration.
663 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
664 Please see the 20141231 entry below for information about prerequisites
665 and upgrading, if you are not already using clang 3.5.0 or higher.
668 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
669 Please see the 20141231 entry below for information about prerequisites
670 and upgrading, if you are not already using clang 3.5.0 or higher.
673 The layout of the pmap structure has changed for powerpc to put the pmap
674 statistics at the front for all CPU variations. libkvm(3) and all tools
675 that link against it need to be recompiled.
678 isl(4) and cyapa(4) drivers now require a new driver,
679 chromebook_platform(4), to work properly on Chromebook-class hardware.
680 On other types of hardware the drivers may need to be configured using
681 device hints. Please see the corresponding manual pages for details.
684 The urtwn(4) driver was merged into rtwn(4) and now consists of
685 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
687 Also, firmware for RTL8188CE was renamed due to possible name
688 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
691 GNU rcs has been removed from base. It is available as packages:
692 - rcs: Latest GPLv3 GNU rcs version.
693 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
697 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
698 modules now requires that the kernel configuration contain the
699 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
702 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
703 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
706 Relocatable object files with the extension of .So have been renamed
707 to use an extension of .pico instead. The purpose of this change is
708 to avoid a name clash with shared libraries on case-insensitive file
709 systems. On those file systems, foo.So is the same file as foo.so.
712 GNU rcs has been turned off by default. It can (temporarily) be built
713 again by adding WITH_RCS knob in src.conf.
714 Otherwise, GNU rcs is available from packages:
715 - rcs: Latest GPLv3 GNU rcs version.
716 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
719 The backup_uses_rcs functionality has been removed from rc.subr.
722 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
723 two separate components, QUEUE_MACRO_DEBUG_TRACE and
724 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
725 QUEUE_MACRO_DEBUG behavior.
728 r304787 changed some ioctl interfaces between the iSCSI userspace
729 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
730 rebuilt to work with new kernels. __FreeBSD_version has been bumped
734 The UDP receive code has been updated to only treat incoming UDP
735 packets that were addressed to an L2 broadcast address as L3
736 broadcast packets. It is not expected that this will affect any
737 standards-conforming UDP application. The new behaviour can be
738 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
742 Remove the openbsd_poll system call.
743 __FreeBSD_version has been bumped because of this.
746 The stable/11 branch has been created from head@r302406.
749 The libc stub for the pipe(2) system call has been replaced with
750 a wrapper that calls the pipe2(2) system call and the pipe(2)
751 system call is now only implemented by the kernels that include
752 "options COMPAT_FREEBSD10" in their config file (this is the
753 default). Users should ensure that this option is enabled in
754 their kernel or upgrade userspace to r302092 before upgrading their
758 CAM will now strip leading spaces from SCSI disks' serial numbers.
759 This will affect users who create UFS filesystems on SCSI disks using
760 those disk's diskid device nodes. For example, if /etc/fstab
761 previously contained a line like
762 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
763 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
764 transforms like gmirror may also be affected. ZFS users should
768 The bitstring(3) API has been updated with new functionality and
769 improved performance. But it is binary-incompatible with the old API.
770 Objects built with the new headers may not be linked against objects
771 built with the old headers.
774 The brk and sbrk functions have been removed from libc on arm64.
775 Binutils from ports has been updated to not link to these
776 functions and should be updated to the latest version before
777 installing a new libc.
780 The armv6 port now defaults to hard float ABI. Limited support
781 for running both hardfloat and soft float on the same system
782 is available using the libraries installed with -DWITH_LIBSOFT.
783 This has only been tested as an upgrade path for installworld
784 and packages may fail or need manual intervention to run. New
785 packages will be needed.
787 To update an existing self-hosted armv6hf system, you must add
788 TARGET_ARCH=armv6 on the make command line for both the build
789 and the install steps.
792 Kernel modules compiled outside of a kernel build now default to
793 installing to /boot/modules instead of /boot/kernel. Many kernel
794 modules built this way (such as those in ports) already overrode
795 KMODDIR explicitly to install into /boot/modules. However,
796 manually building and installing a module from /sys/modules will
797 now install to /boot/modules instead of /boot/kernel.
800 The CAM I/O scheduler has been committed to the kernel. There should be
801 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
802 list of known rogues that claim support for this but actually corrupt
803 data is believed to be complete, be on the lookout for data
804 corruption. The known rogue list is believed to be complete:
806 o Crucial MX100, M550 drives with MU01 firmware.
807 o Micron M510 and M550 drives with MU01 firmware.
808 o Micron M500 prior to MU07 firmware
809 o Samsung 830, 840, and 850 all firmwares
810 o FCCT M500 all firmwares
812 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
813 with working NCQ TRIM. For Micron branded drives, see your sales rep for
814 updated firmware. Black listed drives will work correctly because these
815 drives work correctly so long as no NCQ TRIMs are sent to them. Given
816 this list is the same as found in Linux, it's believed there are no
817 other rogues in the market place. All other models from the above
820 To be safe, if you are at all concerned, you can quirk each of your
821 drives to prevent NCQ from being sent by setting:
822 kern.cam.ada.X.quirks="0x2"
823 in loader.conf. If the drive requires the 4k sector quirk, set the
827 The FAST_DEPEND build option has been removed and its functionality is
828 now the one true way. The old mkdep(1) style of 'make depend' has
829 been removed. See 20160311 for further details.
832 Resource range types have grown from unsigned long to uintmax_t. All
833 drivers, and anything using libdevinfo, need to be recompiled.
836 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
837 builds. It no longer runs mkdep(1) during 'make depend', and the
838 'make depend' stage can safely be skipped now as it is auto ran
839 when building 'make all' and will generate all SRCS and DPSRCS before
840 building anything else. Dependencies are gathered at compile time with
841 -MF flags kept in separate .depend files per object file. Users should
842 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
846 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
847 kernel modules. Therefore, if you load any kernel modules at boot time,
848 please install the boot loaders after you install the kernel, but before
852 make buildkernel KERNCONF=YOUR_KERNEL_HERE
853 make installkernel KERNCONF=YOUR_KERNEL_HERE
854 make -C sys/boot install
855 <reboot in single user>
857 Then follow the usual steps, described in the General Notes section,
861 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
862 see the 20141231 entry below for information about prerequisites and
863 upgrading, if you are not already using clang 3.5.0 or higher.
866 The AIO subsystem is now a standard part of the kernel. The
867 VFS_AIO kernel option and aio.ko kernel module have been removed.
868 Due to stability concerns, asynchronous I/O requests are only
869 permitted on sockets and raw disks by default. To enable
870 asynchronous I/O requests on all file types, set the
871 vfs.aio.enable_unsafe sysctl to a non-zero value.
874 The ELF object manipulation tool objcopy is now provided by the
875 ELF Tool Chain project rather than by GNU binutils. It should be a
876 drop-in replacement, with the addition of arm64 support. The
877 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
878 to obtain the GNU version if necessary.
881 Building ZFS pools on top of zvols is prohibited by default. That
882 feature has never worked safely; it's always been prone to deadlocks.
883 Using a zvol as the backing store for a VM guest's virtual disk will
884 still work, even if the guest is using ZFS. Legacy behavior can be
885 restored by setting vfs.zfs.vol.recursive=1.
888 The NONE and HPN patches has been removed from OpenSSH. They are
889 still available in the security/openssh-portable port.
892 With the addition of ypldap(8), a new _ypldap user is now required
893 during installworld. "mergemaster -p" can be used to add the user
894 prior to installworld, as documented in the handbook.
897 The tftp loader (pxeboot) now uses the option root-path directive. As a
898 consequence it no longer looks for a pxeboot.4th file on the tftp
899 server. Instead it uses the regular /boot infrastructure as with the
903 The code to start recording plug and play data into the modules has
904 been committed. While the old tools will properly build a new kernel,
905 a number of warnings about "unknown metadata record 4" will be produced
906 for an older kldxref. To avoid such warnings, make sure to rebuild
907 the kernel toolchain (or world). Make sure that you have r292078 or
908 later when trying to build 292077 or later before rebuilding.
911 Debug data files are now built by default with 'make buildworld' and
912 installed with 'make installworld'. This facilitates debugging but
913 requires more disk space both during the build and for the installed
914 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
918 r291527 changed the internal interface between the nfsd.ko and
919 nfscommon.ko modules. As such, they must both be upgraded to-gether.
920 __FreeBSD_version has been bumped because of this.
923 Add support for unicode collation strings leads to a change of
924 order of files listed by ls(1) for example. To get back to the old
925 behaviour, set LC_COLLATE environment variable to "C".
927 Databases administrators will need to reindex their databases given
928 collation results will be different.
930 Due to a bug in install(1) it is recommended to remove the ancient
931 locales before running make installworld.
933 rm -rf /usr/share/locale/*
936 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
937 libcrypto.so.7 or libssl.so.7 must be recompiled.
940 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
941 Kernel modules isp_2400_multi and isp_2500_multi were removed and
942 should be replaced with isp_2400 and isp_2500 modules respectively.
945 The build previously allowed using 'make -n' to not recurse into
946 sub-directories while showing what commands would be executed, and
947 'make -n -n' to recursively show commands. Now 'make -n' will recurse
948 and 'make -N' will not.
951 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
952 and etcupdate will now use this file. A custom sendmail.cf is now
953 updated via this mechanism rather than via installworld. If you had
954 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
955 want to remove the exclusion or change it to "always install".
956 /etc/mail/sendmail.cf is now managed the same way regardless of
957 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
958 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
961 Compatibility shims for legacy ATA device names have been removed.
962 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
963 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
964 environment variables, /dev/ad* and /dev/ar* symbolic links.
967 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
968 Please see the 20141231 entry below for information about prerequisites
969 and upgrading, if you are not already using clang 3.5.0 or higher.
972 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
973 and renamed from .symbols to .debug. This reduces the size requirements
974 on the boot partition or file system and provides consistency with
975 userland debug files.
977 When using the supported kernel installation method the
978 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
979 as is done with /boot/kernel.
981 Developers wishing to maintain the historical behavior of installing
982 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
985 The wireless drivers had undergone changes that remove the 'parent
986 interface' from the ifconfig -l output. The rc.d network scripts
987 used to check presence of a parent interface in the list, so old
988 scripts would fail to start wireless networking. Thus, etcupdate(3)
989 or mergemaster(8) run is required after kernel update, to update your
990 rc.d scripts in /etc.
993 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
994 These configurations are now automatically interpreted as
995 'scrub fragment reassemble'.
998 Kernel-loadable modules for the random(4) device are back. To use
999 them, the kernel must have
1002 options RANDOM_LOADABLE
1004 kldload(8) can then be used to load random_fortuna.ko
1005 or random_yarrow.ko. Please note that due to the indirect
1006 function calls that the loadable modules need to provide,
1007 the build-in variants will be slightly more efficient.
1009 The random(4) kernel option RANDOM_DUMMY has been retired due to
1010 unpopularity. It was not all that useful anyway.
1013 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1014 Control over building the ELF Tool Chain tools is now provided by
1015 the WITHOUT_TOOLCHAIN knob.
1018 The polarity of Pulse Per Second (PPS) capture events with the
1019 uart(4) driver has been corrected. Prior to this change the PPS
1020 "assert" event corresponded to the trailing edge of a positive PPS
1021 pulse and the "clear" event was the leading edge of the next pulse.
1023 As the width of a PPS pulse in a typical GPS receiver is on the
1024 order of 1 millisecond, most users will not notice any significant
1025 difference with this change.
1027 Anyone who has compensated for the historical polarity reversal by
1028 configuring a negative offset equal to the pulse width will need to
1029 remove that workaround.
1032 The default group assigned to /dev/dri entries has been changed
1033 from 'wheel' to 'video' with the id of '44'. If you want to have
1034 access to the dri devices please add yourself to the video group
1037 # pw groupmod video -m $USER
1040 The menu.rc and loader.rc files will now be replaced during
1041 upgrades. Please migrate local changes to menu.rc.local and
1042 loader.rc.local instead.
1045 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1046 strings and strip have been removed. The src.conf(5) knob
1047 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1050 As ZFS requires more kernel stack pages than is the default on some
1051 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1052 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1054 Please consider using 'options KSTACK_PAGES=X' where X is greater
1055 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1058 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1059 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1060 default, i.e., they will not contain "::". For example, instead
1061 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1062 to have a more specific match, such as different map entries for
1063 IPv6:0:0 vs IPv6:0. This change requires that configuration
1064 data (including maps, files, classes, custom ruleset, etc.) must
1065 use the same format, so make certain such configuration data is
1066 upgrading. As a very simple check search for patterns like
1067 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1068 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1069 the cf option UseCompressedIPv6Addresses.
1072 The default kernel entropy-processing algorithm is now
1073 Fortuna, replacing Yarrow.
1075 Assuming you have 'device random' in your kernel config
1076 file, the configurations allow a kernel option to override
1077 this default. You may choose *ONE* of:
1079 options RANDOM_YARROW # Legacy /dev/random algorithm.
1080 options RANDOM_DUMMY # Blocking-only driver.
1082 If you have neither, you get Fortuna. For most people,
1083 read no further, Fortuna will give a /dev/random that works
1084 like it always used to, and the difference will be irrelevant.
1086 If you remove 'device random', you get *NO* kernel-processed
1087 entropy at all. This may be acceptable to folks building
1088 embedded systems, but has complications. Carry on reading,
1089 and it is assumed you know what you need.
1091 *PLEASE* read random(4) and random(9) if you are in the
1092 habit of tweaking kernel configs, and/or if you are a member
1093 of the embedded community, wanting specific and not-usual
1094 behaviour from your security subsystems.
1096 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1097 random', you will NOT have a functioning /dev/random, and
1098 many cryptographic features will not work, including SSH.
1099 You may also find strange behaviour from the random(3) set
1100 of library functions, in particular sranddev(3), srandomdev(3)
1101 and arc4random(3). The reason for this is that the KERN_ARND
1102 sysctl only returns entropy if it thinks it has some to
1103 share, and with RANDOM_DUMMY or no 'device random' this
1107 An additional fix for the issue described in the 20150614 sendmail
1108 entry below has been committed in revision 284717.
1111 FreeBSD's old make (fmake) has been removed from the system. It is
1112 available as the devel/fmake port or via pkg install fmake.
1115 The fix for the issue described in the 20150614 sendmail entry
1116 below has been committed in revision 284436. The work
1117 around described in that entry is no longer needed unless the
1118 default setting is overridden by a confDH_PARAMETERS configuration
1119 setting of '5' or pointing to a 512 bit DH parameter file.
1122 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1123 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1124 and devel/kyua to version 0.20+ and adjust any calling code to work
1125 with Kyuafile and kyua.
1128 The import of openssl to address the FreeBSD-SA-15:10.openssl
1129 security advisory includes a change which rejects handshakes
1130 with DH parameters below 768 bits. sendmail releases prior
1131 to 8.15.2 (not yet released), defaulted to a 512 bit
1132 DH parameter setting for client connections. To work around
1133 this interoperability, sendmail can be configured to use a
1134 2048 bit DH parameter by:
1136 1. Edit /etc/mail/`hostname`.mc
1137 2. If a setting for confDH_PARAMETERS does not exist or
1138 exists and is set to a string beginning with '5',
1139 replace it with '2'.
1140 3. If a setting for confDH_PARAMETERS exists and is set to
1141 a file path, create a new file with:
1142 openssl dhparam -out /path/to/file 2048
1143 4. Rebuild the .cf file:
1144 cd /etc/mail/; make; make install
1145 5. Restart sendmail:
1146 cd /etc/mail/; make restart
1148 A sendmail patch is coming, at which time this file will be
1152 Generation of legacy formatted entries have been disabled by default
1153 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1154 entries were converted to use the new format by default when the new,
1155 machine independent format have been added and supported since FreeBSD
1158 Please see the pwd_mkdb(8) manual page for further details.
1161 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1162 20141231 entry below for information about prerequisites and upgrading,
1163 if you are not already using 3.5.0 or higher.
1166 TI platform code switched to using vendor DTS files and this update
1167 may break existing systems running on Beaglebone, Beaglebone Black,
1170 - dtb files should be regenerated/reinstalled. Filenames are the
1171 same but content is different now
1172 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1173 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1174 addressing scheme is now pin 25 on /dev/gpioc3.
1175 - Pandaboard: /etc/ttys should be updated, serial console device is
1176 now /dev/ttyu2, not /dev/ttyu0
1179 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1180 If you need the GNU extension from groff soelim(1), install groff
1181 from package: pkg install groff, or via ports: textproc/groff.
1184 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1185 defined in symlink(7); previously symlinks were silently ignored.
1188 The const qualifier has been removed from iconv(3) to comply with
1189 POSIX. The ports tree is aware of this from r384038 onwards.
1192 Libraries specified by LIBADD in Makefiles must have a corresponding
1193 DPADD_<lib> variable to ensure correct dependencies. This is now
1194 enforced in src.libnames.mk.
1197 From legacy ata(4) driver was removed support for SATA controllers
1198 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1199 Kernel modules ataahci and ataadaptec were removed completely,
1200 replaced by ahci and mvs modules respectively.
1203 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1204 the 20141231 entry below for information about prerequisites and
1205 upgrading, if you are not already using 3.5.0 or higher.
1208 The 32-bit PowerPC kernel has been changed to a position-independent
1209 executable. This can only be booted with a version of loader(8)
1210 newer than January 31, 2015, so make sure to update both world and
1211 kernel before rebooting.
1214 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1215 but before r278950, the RNG was not seeded properly. Immediately
1216 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1217 ssh keys or openssl keys) that were generated w/ a kernel from that
1218 range. This does not affect programs that directly used /dev/random
1219 or /dev/urandom. All userland uses of arc4random(3) are affected.
1222 The autofs(4) ABI was changed in order to restore binary compatibility
1223 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1224 with the new kernel.
1227 The powerpc64 kernel has been changed to a position-independent
1228 executable. This can only be booted with a new version of loader(8),
1229 so make sure to update both world and kernel before rebooting.
1232 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1233 only release, no new features have been added. Please see the 20141231
1234 entry below for information about prerequisites and upgrading, if you
1235 are not already using 3.5.0.
1238 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1239 taken from the ELF Tool Chain project rather than GNU binutils. They
1240 should be drop-in replacements, with the addition of arm64 support.
1241 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1242 binutils tools, if necessary. See 20150805 for updated information.
1245 The default Unbound configuration now enables remote control
1246 using a local socket. Users who have already enabled the
1247 local_unbound service should regenerate their configuration
1248 by running "service local_unbound setup" as root.
1251 The GNU texinfo and GNU info pages have been removed.
1252 To be able to view GNU info pages please install texinfo from ports.
1255 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1257 As of this release, a prerequisite for building clang, llvm and lldb is
1258 a C++11 capable compiler and C++11 standard library. This means that to
1259 be able to successfully build the cross-tools stage of buildworld, with
1260 clang as the bootstrap compiler, your system compiler or cross compiler
1261 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1262 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1265 On any standard FreeBSD 10.x or 11.x installation, where clang and
1266 libc++ are on by default (that is, on x86 or arm), this should work out
1269 On 9.x installations where clang is enabled by default, e.g. on x86 and
1270 powerpc, libc++ will not be enabled by default, so libc++ should be
1271 built (with clang) and installed first. If both clang and libc++ are
1272 missing, build clang first, then use it to build libc++.
1274 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1275 the instructions for 9.x above.
1277 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1278 default, and do not build clang.
1280 Many embedded systems are resource constrained, and will not be able to
1281 build clang in a reasonable time, or in some cases at all. In those
1282 cases, cross building bootable systems on amd64 is a workaround.
1284 This new version of clang introduces a number of new warnings, of which
1285 the following are most likely to appear:
1289 This warns in two cases, for both C and C++:
1290 * When the code is trying to take the absolute value of an unsigned
1291 quantity, which is effectively a no-op, and almost never what was
1292 intended. The code should be fixed, if at all possible. If you are
1293 sure that the unsigned quantity can be safely cast to signed, without
1294 loss of information or undefined behavior, you can add an explicit
1295 cast, or disable the warning.
1297 * When the code is trying to take an absolute value, but the called
1298 abs() variant is for the wrong type, which can lead to truncation.
1299 If you want to disable the warning instead of fixing the code, please
1300 make sure that truncation will not occur, or it might lead to unwanted
1303 -Wtautological-undefined-compare and
1304 -Wundefined-bool-conversion
1306 These warn when C++ code is trying to compare 'this' against NULL, while
1307 'this' should never be NULL in well-defined C++ code. However, there is
1308 some legacy (pre C++11) code out there, which actively abuses this
1309 feature, which was less strictly defined in previous C++ versions.
1311 Squid and openjdk do this, for example. The warning can be turned off
1312 for C++98 and earlier, but compiling the code in C++11 mode might result
1313 in unexpected behavior; for example, the parts of the program that are
1314 unreachable could be optimized away.
1317 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1318 kernel sources have been removed. The .h files remain, since some
1319 utilities include them. This will need to be fixed later.
1320 If "mount -t oldnfs ..." is attempted, it will fail.
1321 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1322 the utilities will report errors.
1325 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1326 directories to top level SUBDIR variable when their parent
1327 directory is included in LOCAL_DIRS. Users with build systems with
1328 such hierarchies and without SUBDIR entries in the parent
1329 directory Makefiles should add them or add the directories to
1333 faith(4) and faithd(8) have been removed from the base system. Faith
1334 has been obsolete for a very long time.
1337 vt(4), the new console driver, is enabled by default. It brings
1338 support for Unicode and double-width characters, as well as
1339 support for UEFI and integration with the KMS kernel video
1342 You may need to update your console settings in /etc/rc.conf,
1343 most probably the keymap. During boot, /etc/rc.d/syscons will
1344 indicate what you need to do.
1346 vt(4) still has issues and lacks some features compared to
1347 syscons(4). See the wiki for up-to-date information:
1348 https://wiki.freebsd.org/Newcons
1350 If you want to keep using syscons(4), you can do so by adding
1351 the following line to /boot/loader.conf:
1355 pjdfstest has been integrated into kyua as an opt-in test suite.
1356 Please see share/doc/pjdfstest/README for more details on how to
1360 gperf has been removed from the base system for architectures
1361 that use clang. Ports that require gperf will obtain it from the
1365 pjdfstest has been moved from tools/regression/pjdfstest to
1369 At svn r271982, The default linux compat kernel ABI has been adjusted
1370 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1371 update. If you wish to continue using the linux-f10 compat ports,
1372 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1373 encouraged to update their linux-compat packages to linux-c6 during
1374 their next update cycle.
1377 The ofwfb driver, used to provide a graphics console on PowerPC when
1378 using vt(4), no longer allows mmap() of all physical memory. This
1379 will prevent Xorg on PowerPC with some ATI graphics cards from
1380 initializing properly unless x11-servers/xorg-server is updated to
1384 The xdev targets have been converted to using TARGET and
1385 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1388 The default unbound configuration has been modified to address
1389 issues with reverse lookups on networks that use private
1390 address ranges. If you use the local_unbound service, run
1391 "service local_unbound setup" as root to regenerate your
1392 configuration, then "service local_unbound reload" to load the
1396 The GNU texinfo and GNU info pages are not built and installed
1397 anymore, WITH_INFO knob has been added to allow to built and install
1399 UPDATE: see 20150102 entry on texinfo's removal
1402 The GNU readline library is now an INTERNALLIB - that is, it is
1403 statically linked into consumers (GDB and variants) in the base
1404 system, and the shared library is no longer installed. The
1405 devel/readline port is available for third party software that
1409 The Itanium architecture (ia64) has been removed from the list of
1410 known architectures. This is the first step in the removal of the
1414 Commit r268115 has added NFSv4.1 server support, merged from
1415 projects/nfsv4.1-server. Since this includes changes to the
1416 internal interfaces between the NFS related modules, a full
1417 build of the kernel and modules will be necessary.
1418 __FreeBSD_version has been bumped.
1421 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1422 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1423 which differs from the behaviour controlled by this knob.)
1426 Maximal length of the serial number in CTL was increased from 16 to
1427 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1428 and ctld, need to be rebuilt to work with a new kernel.
1431 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1432 1 respectively to match the upstream numbers. They were out of
1433 sync because, when they were originally added to FreeBSD, the
1434 upstream versions were not respected. These libraries are private
1435 and not yet built by default, so renumbering them should be a
1436 non-issue. However, unclean source trees will yield broken test
1437 programs once the operator executes "make delete-old-libs" after a
1438 "make installworld".
1440 Additionally, the atf-sh binary was made private by moving it into
1441 /usr/libexec/. Already-built shell test programs will keep the
1442 path to the old binary so they will break after "make delete-old"
1445 If you are using WITH_TESTS=yes (not the default), wipe the object
1446 tree and rebuild from scratch to prevent spurious test failures.
1447 This is only needed once: the misnumbered libraries and misplaced
1448 binaries have been added to OptionalObsoleteFiles.inc so they will
1449 be removed during a clean upgrade.
1452 Clang and llvm have been upgraded to 3.4.1 release.
1455 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1456 be removed to avoid issues in the future (and has been added to
1460 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1461 past, it affected all builds that used the bsd.*.mk files. The old
1462 behavior was a bug, but people may have relied upon it. To get this
1463 behavior back, you can .include /etc/src.conf from /etc/make.conf
1464 (which is still global and isn't changed). This also changes the
1465 behavior of incremental builds inside the tree of individual
1466 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1467 Although this has survived make universe and some upgrade scenarios,
1468 other upgrade scenarios may have broken. At least one form of
1469 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1470 as well... In cases where MAKESYSPATH isn't working with this
1471 setting, you'll need to set it to the full path to your tree.
1473 One side effect of all this cleaning up is that bsd.compiler.mk
1474 is no longer implicitly included by bsd.own.mk. If you wish to
1475 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1479 The lindev device has been removed since /dev/full has been made a
1480 standard device. __FreeBSD_version has been bumped.
1483 The knob WITHOUT_VI was added to the base system, which controls
1484 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1485 in order to reorder files share/termcap and didn't build ex(1) as a
1486 build tool, so building/installing with WITH_VI is highly advised for
1487 build hosts for older releases.
1489 This issue has been fixed in stable/9 and stable/10 in r277022 and
1490 r276991, respectively.
1493 The YES_HESIOD knob has been removed. It has been obsolete for
1494 a decade. Please move to using WITH_HESIOD instead or your builds
1495 will silently lack HESIOD.
1498 The uart(4) driver has been changed with respect to its handling
1499 of the low-level console. Previously the uart(4) driver prevented
1500 any process from changing the baudrate or the CLOCAL and HUPCL
1501 control flags. By removing the restrictions, operators can make
1502 changes to the serial console port without having to reboot.
1503 However, when getty(8) is started on the serial device that is
1504 associated with the low-level console, a misconfigured terminal
1505 line in /etc/ttys will now have a real impact.
1506 Before upgrading the kernel, make sure that /etc/ttys has the
1507 serial console device configured as 3wire without baudrate to
1508 preserve the previous behaviour. E.g:
1509 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1512 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1513 to improve performance. To re-enable it, if needed, run rpcbind
1514 with command line option -W.
1517 Switched back to the GPL dtc compiler due to updates in the upstream
1518 dts files not being supported by the BSDL dtc compiler. You will need
1519 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1520 may result while building dtb files during a kernel build if you fail
1521 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1524 Clang and llvm have been upgraded to 3.4 release.
1527 The nve(4) driver has been removed. Please use the nfe(4) driver
1528 for NVIDIA nForce MCP Ethernet adapters instead.
1531 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1532 This could cause certain C++ applications using shared libraries built
1533 against the previous version of libc++ to crash. The incompatibility
1534 has now been fixed, but any C++ applications or shared libraries built
1535 between r261283 and r261801 should be recompiled.
1538 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1539 capability mode support. Please note that enabling the feature in
1540 kernel is still highly recommended.
1543 OpenSSH is now built with sandbox support, and will use sandbox as
1544 the default privilege separation method. This requires Capsicum
1545 capability mode support in kernel.
1548 The libelf and libdwarf libraries have been updated to newer
1549 versions from upstream. Shared library version numbers for
1550 these two libraries were bumped. Any ports or binaries
1551 requiring these two libraries should be recompiled.
1552 __FreeBSD_version is bumped to 1100006.
1555 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1556 instead of providing an explicit one, this would prevent such
1557 Makefile from providing its own Kyuafile in the future during
1558 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1559 intervention is needed to clean an objdir if you use NO_CLEAN:
1560 # find /usr/obj -name Kyuafile | xargs rm -f
1563 The behavior of gss_pseudo_random() for the krb5 mechanism
1564 has changed, for applications requesting a longer random string
1565 than produced by the underlying enctype's pseudo-random() function.
1566 In particular, the random string produced from a session key of
1567 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1568 be different at the 17th octet and later, after this change.
1569 The counter used in the PRF+ construction is now encoded as a
1570 big-endian integer in accordance with RFC 4402.
1571 __FreeBSD_version is bumped to 1100004.
1574 The WITHOUT_ATF build knob has been removed and its functionality
1575 has been subsumed into the more generic WITHOUT_TESTS. If you were
1576 using the former to disable the build of the ATF libraries, you
1577 should change your settings to use the latter.
1580 The default version of mtree is nmtree which is obtained from
1581 NetBSD. The output is generally the same, but may vary
1582 slightly. If you found you need identical output adding
1583 "-F freebsd9" to the command line should do the trick. For the
1584 time being, the old mtree is available as fmtree.
1587 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1588 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1589 1.1.4_8 and verify bsdyml not linked in, before running "make
1591 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1593 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1596 The stable/10 branch has been created in subversion from head
1603 Avoid using make -j when upgrading. While generally safe, there are
1604 sometimes problems using -j to upgrade. If your upgrade fails with
1605 -j, please try again without -j. From time to time in the past there
1606 have been problems using -j with buildworld and/or installworld. This
1607 is especially true when upgrading between "distant" versions (eg one
1608 that cross a major release boundary or several minor releases, or when
1609 several months have passed on the -current branch).
1611 Sometimes, obscure build problems are the result of environment
1612 poisoning. This can happen because the make utility reads its
1613 environment when searching for values for global variables. To run
1614 your build attempts in an "environmental clean room", prefix all make
1615 commands with 'env -i '. See the env(1) manual page for more details.
1617 When upgrading from one major version to another it is generally best to
1618 upgrade to the latest code in the currently installed branch first, then
1619 do an upgrade to the new branch. This is the best-tested upgrade path,
1620 and has the highest probability of being successful. Please try this
1621 approach if you encounter problems with a major version upgrade. Since
1622 the stable 4.x branch point, one has generally been able to upgrade from
1623 anywhere in the most recent stable branch to head / current (or even the
1624 last couple of stable branches). See the top of this file when there's
1627 When upgrading a live system, having a root shell around before
1628 installing anything can help undo problems. Not having a root shell
1629 around can lead to problems if pam has changed too much from your
1630 starting point to allow continued authentication after the upgrade.
1632 This file should be read as a log of events. When a later event changes
1633 information of a prior event, the prior event should not be deleted.
1634 Instead, a pointer to the entry with the new information should be
1635 placed in the old entry. Readers of this file should also sanity check
1636 older entries before relying on them blindly. Authors of new entries
1637 should write them with this in mind.
1641 When upgrading the boot ZFS pool to a new version, always follow
1644 1.) recompile and reinstall the ZFS boot loader and boot block
1645 (this is part of "make buildworld" and "make installworld")
1647 2.) update the ZFS boot block on your boot drive
1649 The following example updates the ZFS boot block on the first
1650 partition (freebsd-boot) of a GPT partitioned drive ada0:
1651 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1653 Non-boot pools do not need these updates.
1657 If you are updating from a prior version of FreeBSD (even one just
1658 a few days old), you should follow this procedure. It is the most
1659 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1661 make kernel-toolchain
1662 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1663 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1665 To test a kernel once
1666 ---------------------
1667 If you just want to boot a kernel once (because you are not sure
1668 if it works, or if you want to boot a known bad kernel to provide
1669 debugging information) run
1670 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1671 nextboot -k testkernel
1673 To rebuild everything and install it on the current system.
1674 -----------------------------------------------------------
1675 # Note: sometimes if you are running current you gotta do more than
1676 # is listed here if you are upgrading from a really old current.
1678 <make sure you have good level 0 dumps>
1680 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1681 make installkernel KERNCONF=YOUR_KERNEL_HERE
1683 <reboot in single user> [3]
1690 To cross-install current onto a separate partition
1691 --------------------------------------------------
1692 # In this approach we use a separate partition to hold
1693 # current's root, 'usr', and 'var' directories. A partition
1694 # holding "/", "/usr" and "/var" should be about 2GB in
1697 <make sure you have good level 0 dumps>
1700 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1701 <maybe newfs current's root partition>
1702 <mount current's root partition on directory ${CURRENT_ROOT}>
1703 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1704 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1705 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1706 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1707 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1708 <reboot into current>
1709 <do a "native" rebuild/install as described in the previous section>
1710 <maybe install compatibility libraries from ports/misc/compat*>
1714 To upgrade in-place from stable to current
1715 ----------------------------------------------
1716 <make sure you have good level 0 dumps>
1718 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1719 make installkernel KERNCONF=YOUR_KERNEL_HERE
1721 <reboot in single user> [3]
1728 Make sure that you've read the UPDATING file to understand the
1729 tweaks to various things you need. At this point in the life
1730 cycle of current, things change often and you are on your own
1731 to cope. The defaults can also change, so please read ALL of
1732 the UPDATING entries.
1734 Also, if you are tracking -current, you must be subscribed to
1735 freebsd-current@freebsd.org. Make sure that before you update
1736 your sources that you have read and understood all the recent
1737 messages there. If in doubt, please track -stable which has
1738 much fewer pitfalls.
1740 [1] If you have third party modules, such as vmware, you
1741 should disable them at this point so they don't crash your
1744 [3] From the bootblocks, boot -s, and then do
1749 adjkerntz -i # if CMOS is wall time
1750 Also, when doing a major release upgrade, it is required that
1751 you boot into single user mode to do the installworld.
1753 [4] Note: This step is non-optional. Failure to do this step
1754 can result in a significant reduction in the functionality of the
1755 system. Attempting to do it by hand is not recommended and those
1756 that pursue this avenue should read this file carefully, as well
1757 as the archives of freebsd-current and freebsd-hackers mailing lists
1758 for potential gotchas. The -U option is also useful to consider.
1759 See mergemaster(8) for more information.
1761 [5] Usually this step is a no-op. However, from time to time
1762 you may need to do this if you get unknown user in the following
1763 step. It never hurts to do it all the time. You may need to
1764 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1765 install) after the buildworld before this step if you last updated
1766 from current before 20130425 or from -stable before 20130430.
1768 [6] This only deletes old files and directories. Old libraries
1769 can be deleted by "make delete-old-libs", but you have to make
1770 sure that no program is using those libraries anymore.
1772 [8] In order to have a kernel that can run the 4.x binaries needed to
1773 do an installworld, you must include the COMPAT_FREEBSD4 option in
1774 your kernel. Failure to do so may leave you with a system that is
1775 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1776 required to run the 5.x binaries on more recent kernels. And so on
1777 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1779 Make sure that you merge any new devices from GENERIC since the
1780 last time you updated your kernel config file.
1782 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1783 "?=" instead of the "=" assignment operator, so that buildworld can
1784 override the CPUTYPE if it needs to.
1786 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1787 not on the command line, or in /etc/make.conf. buildworld will
1788 warn if it is improperly defined.
1791 This file contains a list, in reverse chronological order, of major
1792 breakages in tracking -current. It is not guaranteed to be a complete
1793 list of such breakages, and only contains entries since September 23, 2011.
1794 If you need to see UPDATING entries from before that date, you will need
1795 to fetch an UPDATING file from an older FreeBSD release.
1797 Copyright information:
1799 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1801 Redistribution, publication, translation and use, with or without
1802 modification, in full or in part, in any form or format of this
1803 document are permitted without further permission from the author.
1805 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1806 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1807 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1808 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1809 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1810 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1811 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1812 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1813 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1814 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1815 POSSIBILITY OF SUCH DAMAGE.
1817 Contact Warner Losh if you have any questions about your use of