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 default interpreter has been switched from 4th to Lua.
36 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
37 interpreter. If you have custom FORTH code you will need to set
38 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
39 src.conf for the build. This will create default hard links between
40 loader and loader_4th instead of loader and loader_lua, the new default.
41 If you are using UEFI it will create the proper hard link to loader.efi.
44 ls(1) now respects the COLORTERM environment variable used in other
45 systems and software to indicate that a colored terminal is both
46 supported and desired. If ls(1) is suddenly emitting colors, they may
47 be disabled again by either removing the unwanted COLORTERM from your
48 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
49 may not be observed in a future release.
52 The default pager for most commands has been changed to "less". To
53 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
57 The jedec_ts(4) driver has been removed. A superset of its functionality
58 is available in the jedec_dimm(4) driver, and the manpage for that
59 driver includes migration instructions. If you have "device jedec_ts"
60 in your kernel configuration file, it must be removed.
63 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
64 This should have no effect if the kernel is booted via BIOS/legacy boot.
65 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
66 has a buggy firmware that prevents a successful boot due to use of
70 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
71 support has been removed from the tree. These ports were
72 obsolete and/or known to be broken for many years.
75 loader.efi has been augmented to participate more fully in the
76 UEFI boot manager protocol. loader.efi will now look at the
77 BootXXXX environment variable to determine if a specific kernel
78 or root partition was specified. XXXX is derived from BootCurrent.
79 efibootmgr(8) manages these standard UEFI variables.
82 zfsloader's functionality has now been folded into loader.
83 zfsloader is no longer necessary once you've updated your
84 boot blocks. For a transition period, we will install a
85 hardlink for zfsloader to loader to allow a smooth transition
86 until the boot blocks can be updated (hard link because old
87 zfs boot blocks don't understand symlinks).
90 ARM64 now have efifb support, if you want to have serial console
91 on your arm64 board when an screen is connected and the bootloader
92 setup a frambuffer for us to use, just add :
96 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
97 an screen connected as the firmware will setup a framebuffer are that
98 u-boot will expose as an EFI framebuffer.
101 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
102 or take steps to update /etc/passwd before doing installworld on
103 existing systems. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
104 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
105 the ntp config file contain options that change file/dir locations.
106 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
107 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
108 taking steps to ensure that all required files/dirs are accessible
112 Big endian arm support has been removed.
115 The static environment setup in kernel configs is no longer mutually
116 exclusive with the loader(8) environment by default. In order to
117 restore the previous default behavior of disabling the loader(8)
118 environment if a static environment is present, you must specify
119 loader_env.disabled=1 in the static environment.
122 The ABI of syscalls used by management tools like sockstat and
123 netstat has been broken to allow 32-bit binaries to work on
124 64-bit kernels without modification. These programs will need
125 to match the kernel in order to function. External programs may
126 require minor modifications to accommodate a change of type in
127 structures from pointers to 64-bit virtual addresses.
130 On i386 and amd64 atomics are now inlined. Out of tree modules using
131 atomics will need to be rebuilt.
134 The '%I' format in the kern.corefile sysctl limits the number of
135 core files that a process can generate to the number stored in the
136 debug.ncores sysctl. The '%I' format is replaced by the single digit
137 index. Previously, if all indexes were taken the kernel would overwrite
138 only a core file with the highest index in a filename.
139 Currently the system will create a new core file if there is a free
140 index or if all slots are taken it will overwrite the oldest one.
143 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
144 6.0.1. Please see the 20141231 entry below for information about
145 prerequisites and upgrading, if you are not already using clang 3.5.0
149 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
150 needed to be changed to work with it. This change was made with r335763
151 and requires a mergemaster / etcupdate / etc to update the installed file.
154 r334930 changed the interface between the NFS modules, so they all
155 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
158 The kernel / userland interface for devinfo changed, so you'll
159 need a new kernel and userland as a pair for it to work (rebuilding
160 lib/libdevinfo is all that's required). devinfo and devmatch will
161 not work, but everything else will when there's a mismatch.
164 The on-disk format for hwpmc callchain records has changed to include
165 threadid corresponding to a given record. This changes the field offsets
166 and thus requires that libpmcstat be rebuilt before using a kernel
170 The vxge(4) driver has been removed. This driver was introduced into
171 HEAD one week before the Exar left the Ethernet market and is not
172 known to be used. If you have device vxge in your kernel config file
176 The amd64 kernel now requires a ld that supports ifunc to produce a
177 working kernel, either lld or a newer binutils. lld is built by default
178 on amd64, and the 'buildkernel' target uses it automatically. However,
179 it is not the default linker, so building the kernel the traditional
180 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
181 binutils port/package). lld will soon be default, and this requirement
185 The nxge(4) driver has been removed. This driver was for PCI-X 10g
186 cards made by s2io/Neterion. The company was aquired by Exar and
187 no longer sells or supports Ethernet products. If you have device
188 nxge in your kernel config file it must be removed.
191 The tz database (tzdb) has been updated to 2018e. This version more
192 correctly models time stamps in time zones with negative DST such as
193 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
194 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
195 time zone abbreviations and the tm_isdst flag.
198 The ixgb(4) driver has been removed. This driver was for an early and
199 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
200 quickly shifted to the long lived ixgbe family. If you have device
201 ixgb in your kernel config file it must be removed.
204 The lmc(4) driver has been removed. This was a WAN interface
205 card that was already reportedly rare in 2003, and had an ambiguous
206 license. If you have device lmc in your kernel config file it must
210 Support for Arcnet networks has been removed. If you have device
211 arcnet or device cm in your kernel config file they must be
215 Support for FDDI networks has been removed. If you have device
216 fddi or device fpa in your kernel config file they must be
220 In addition to supporting RFC 3164 formatted messages, the
221 syslogd(8) service is now capable of parsing RFC 5424 formatted
222 log messages. The main benefit of using RFC 5424 is that clients
223 may now send log messages with timestamps containing year numbers,
224 microseconds and time zone offsets.
226 Similarly, the syslog(3) C library function has been altered to
227 send RFC 5424 formatted messages to the local system logging
228 daemon. On systems using syslogd(8), this change should have no
229 negative impact, as long as syslogd(8) and the C library are
230 updated at the same time. On systems using a different system
231 logging daemon, it may be necessary to make configuration
232 adjustments, depending on the software used.
234 When using syslog-ng, add the 'syslog-protocol' flag to local
235 input sources to enable parsing of RFC 5424 formatted messages:
238 unix-dgram("/var/run/log" flags(syslog-protocol));
241 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
242 of the 'imuxsock' module to let messages be processed by the
243 regular RFC 3164/5424 parsing pipeline:
245 module(load="imuxsock" SysSock.UseSpecialParser="off")
247 Do note that these changes only affect communication between local
248 applications and syslogd(8). The format that syslogd(8) uses to
249 store messages on disk or forward messages to other systems
250 remains unchanged. syslogd(8) still uses RFC 3164 for these
251 purposes. Options to customize this behaviour will be added in the
252 future. Utilities that process log files stored in /var/log are
253 thus expected to continue to function as before.
255 __FreeBSD_version has been incremented to 1200061 to denote this
259 Support for token ring networks has been removed. If you
260 have "device token" in your kernel config you should remove
261 it. No device drivers supported token ring.
264 makefs was modified to be able to tag ISO9660 El Torito boot catalog
265 entries as EFI instead of overloading the i386 tag as done previously.
266 The amd64 mkisoimages.sh script used to build amd64 ISO images for
267 release was updated to use this. This may mean that makefs must be
268 updated before "make cdrom" can be run in the release directory. This
269 should be as simple as:
271 $ cd $SRCDIR/usr.sbin/makefs
272 $ make depend all install
275 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
276 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
277 Co-existance for the transition period will come shortly. Booting is a
278 complex environment and test coverage for Lua-enabled loaders has been
279 thin, so it would be prudent to assume it might not work and make
280 provisions for backup boot methods.
283 devmatch functionality has been turned on in devd. It will automatically
284 load drivers for unattached devices. This may cause unexpected drivers to
285 be loaded. Please report any problems to current@ and imp@freebsd.org.
288 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
289 6.0.0. Please see the 20141231 entry below for information about
290 prerequisites and upgrading, if you are not already using clang 3.5.0
294 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
295 This means it is used to link the kernel and userland libraries and
296 executables, but is not yet installed as /usr/bin/ld by default.
298 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
299 WITHOUT_LLD_BOOTSTRAP=yes
302 On i386, pmtimer has been removed. Its functionality has been folded
303 into apm. It was a no-op on ACPI in current for a while now (but was still
304 needed on i386 in FreeBSD 11 and earlier). Users may need to remove it
305 from kernel config files.
308 The use of RSS hash from the network card aka flowid has been
309 disabled by default for lagg(4) as it's currently incompatible with
310 the lacp and loadbalance protocols.
312 This can be re-enabled by setting the following in loader.conf:
313 net.link.lagg.default_use_flowid="1"
316 The SW_WATCHDOG option is no longer necessary to enable the
317 hardclock-based software watchdog if no hardware watchdog is
318 configured. As before, SW_WATCHDOG will cause the software
319 watchdog to be enabled even if a hardware watchdog is configured.
322 r326887 fixes the issue described in the 20171214 UPDATING entry.
323 r326888 flips the switch back to building GELI support always.
326 r362593 broke ZFS + GELI support for reasons unknown. However,
327 it also broke ZFS support generally, so GELI has been turned off
328 by default as the lesser evil in r326857. If you boot off ZFS and/or
329 GELI, it might not be a good time to update.
332 PowerPC users must update loader(8) by rebuilding world before
333 installing a new kernel, as the protocol connecting them has
334 changed. Without the update, loader metadata will not be passed
335 successfully to the kernel and users will have to enter their
336 root partition at the kernel mountroot prompt to continue booting.
337 Newer versions of loader can boot old kernels without issue.
340 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
341 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
342 to WITH/OUT_LOADER_GELI.
345 The naive and non-compliant support of posix_fallocate(2) in ZFS
346 has been removed as of r325320. The system call now returns EINVAL
347 when used on a ZFS file. Although the new behavior complies with the
348 standard, some consumers are not prepared to cope with it.
349 One known victim is lld prior to r325420.
352 Building in a FreeBSD src checkout will automatically create object
353 directories now rather than store files in the current directory if
354 'make obj' was not ran. Calling 'make obj' is no longer necessary.
355 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
356 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
360 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
361 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
362 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
363 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
364 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
365 The UNIFIED_OBJDIR option is a transitional feature that will be
366 removed for 12.0 release; please migrate to the new format for any
367 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
368 than hardcoding paths.
371 The native-xtools target no longer installs the files by default to the
372 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
373 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
376 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
377 options are changing from controlling the build if defined / undefined
378 to controlling the build with explicit 'yes' or 'no' values. They will
379 shift to WITH/WITHOUT options to match other options in the system.
382 libstand has turned into a private library for sys/boot use only.
383 It is no longer supported as a public interface outside of sys/boot.
386 The arm port has split armv6 into armv6 and armv7. armv7 is now
387 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
388 and are running a kernel from before r324363, you will need to add
389 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
392 When building multiple kernels using KERNCONF, non-existent KERNCONF
393 files will produce an error and buildkernel will fail. Previously
394 missing KERNCONF files silently failed giving no indication as to
395 why, only to subsequently discover during installkernel that the
396 desired kernel was never built in the first place.
399 The default serial number format for CTL LUNs has changed. This will
400 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
401 or iSCSI clients care about their LUNs' serial numbers. Users who
402 require serial number stability should hardcode serial numbers in
406 For 32-bit arm compiled for hard-float support, soft-floating point
407 binaries now always get their shared libraries from
408 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
409 /usr/libsoft also existed). Only users with a hard-float ld.so, but
410 soft-float everything else should be affected.
413 The geli password typed at boot is now hidden. To restore the previous
414 behavior, see geli(8) for configuration options.
417 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
418 sysctl values. Minor nit, but requires a rebuild of both world/kernel
422 "make check" behavior (made in ^/head@r295380) has been changed to
423 execute from a limited sandbox, as opposed to executing from
427 - The "beforecheck" and "aftercheck" targets are now specified.
428 - ${CHECKDIR} (added in commit noted above) has been removed.
429 - Legacy behavior can be enabled by setting
430 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
432 If the limited sandbox mode is enabled, "make check" will execute
433 "make distribution", then install, execute the tests, and clean up the
434 sandbox if successful.
436 The "make distribution" and "make install" targets are typically run as
437 root to set appropriate permissions and ownership at installation time.
438 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
439 environment if executing "make check" with limited sandbox mode using
440 an unprivileged user.
443 Since the switch to GPT disk labels, fsck for UFS/FFS has been
444 unable to automatically find alternate superblocks. As of r322297,
445 the information needed to find alternate superblocks has been
446 moved to the end of the area reserved for the boot block.
447 Filesystems created with a newfs of this vintage or later
448 will create the recovery information. If you have a filesystem
449 created prior to this change and wish to have a recovery block
450 created for your filesystem, you can do so by running fsck in
451 foreground mode (i.e., do not use the -p or -y options). As it
452 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
453 to which you should answer yes.
456 As of r321665, an NFSv4 server configuration that services
457 Kerberos mounts or clients that do not support the uid/gid in
458 owner/owner_group string capability, must explicitly enable
459 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
460 machine's /etc/rc.conf file.
463 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
464 Please see the 20141231 entry below for information about prerequisites
465 and upgrading, if you are not already using clang 3.5.0 or higher.
468 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
469 r-commands (rlogin, rsh, etc.) to be built with the base system.
472 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
473 a very major ABI incompatible change, so users of FreeBSD/powerpc must
474 be careful when performing source upgrades. It is best to run
475 'make installworld' from an alternate root system, either a live
476 CD/memory stick, or a temporary root partition. Additionally, all ports
477 must be recompiled. powerpc64 is largely unaffected, except in the case
478 of 32-bit compatibility. All 32-bit binaries will be affected.
481 Forward compatibility for the "ino64" project have been committed. This
482 will allow most new binaries to run on older kernels in a limited
483 fashion. This prevents many of the common foot-shooting actions in the
484 upgrade as well as the limited ability to roll back the kernel across
485 the ino64 upgrade. Complicated use cases may not work properly, though
486 enough simpler ones work to allow recovery in most situations.
489 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
490 if you require the GPL compiler.
493 The internal ABI used for communication between the NFS kernel modules
494 was changed by r320085, so __FreeBSD_version was bumped to
495 ensure all the NFS related modules are updated together.
498 The ABI of struct event was changed by extending the data
499 member to 64bit and adding ext fields. For upgrade, same
500 precautions as for the entry 20170523 "ino64" must be
504 The GNU roff toolchain has been removed from base. To render manpages
505 which are not supported by mandoc(1), man(1) can fallback on GNU roff
506 from ports (and recommends to install it).
507 To render roff(7) documents, consider using GNU roff from ports or the
508 heirloom doctools roff toolchain from ports via pkg install groff or
509 via pkg install heirloom-doctools.
512 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
513 smaller runtime footprint builds. This is useful for embedded systems
514 which only require one chipset support.
516 If you load it as a module, make sure this is in /boot/loader.conf:
520 This will load the HAL, all chip/RF backends and if_ath_pci.
521 If you have if_ath_pci in /boot/loader.conf, ensure it is after
522 if_ath or it will not load any HAL chipset support.
524 If you want to selectively load things (eg on ye cheape ARM/MIPS
525 platforms where RAM is at a premium) you should:
528 * load the chip modules in question
529 * load ath_rate, ath_dfs
531 * load if_ath_pci and/or if_ath_ahb depending upon your particular
532 bus bind type - this is where probe/attach is done.
534 For further comments/feedback, poke adrian@ .
537 The "ino64" 64-bit inode project has been committed, which extends
538 a number of types to 64 bits. Upgrading in place requires care and
539 adherence to the documented upgrade procedure.
541 If using a custom kernel configuration ensure that the
542 COMPAT_FREEBSD11 option is included (as during the upgrade the
543 system will be running the ino64 kernel with the existing world).
545 For the safest in-place upgrade begin by removing previous build
546 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
547 full procedure documented below under the heading "To rebuild
548 everything and install it on the current system." Specifically,
549 a reboot is required after installing the new kernel before
553 The NATM framework including the en(4), fatm(4), hatm(4), and
554 patm(4) devices has been removed. Consumers should plan a
555 migration before the end-of-life date for FreeBSD 11.
558 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
559 diff has not been implemented, if those are needed a newer version of
560 GNU diff is available via the diffutils package under the gdiff name.
563 As of r316810 for ipfilter, keep frags is no longer assumed when
564 keep state is specified in a rule. r316810 aligns ipfilter with
565 documentation in man pages separating keep frags from keep state.
566 This allows keep state to be specified without forcing keep frags
567 and allows keep frags to be specified independently of keep state.
568 To maintain previous behaviour, also specify keep frags with
569 keep state (as documented in ipf.conf.5).
572 arm64 builds now use the base system LLD 4.0.0 linker by default,
573 instead of requiring that the aarch64-binutils port or package be
574 installed. To continue using aarch64-binutils, set
575 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
578 The UDP optimization in entry 20160818 that added the sysctl
579 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
580 packets will no longer be treated as L3 broadcast packets.
583 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
584 use any explicitly assigned loopback address available in the jail
585 instead of using the first assigned address of the jail.
588 The ctl.ko module no longer implements the iSCSI target frontend:
589 cfiscsi.ko does instead.
591 If building cfiscsi.ko as a kernel module, the module can be loaded
592 via one of the following methods:
593 - `cfiscsi_load="YES"` in loader.conf(5).
594 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
595 - ctladm(8)/ctld(8), when compiled with iSCSI support
596 (`WITH_ISCSI=yes` in src.conf(5))
598 Please see cfiscsi(4) for more details.
601 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
602 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
603 same source (previously, the dependency of mmcsd.ko on mmc.ko was
604 missing, but mmcsd.ko now will refuse to load if it is incompatible
608 The syntax of ipfw(8) named states was changed to avoid ambiguity.
609 If you have used named states in the firewall rules, you need to modify
610 them after installworld and before rebooting. Now named states must
611 be prefixed with colon.
614 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
615 removed as the userland we provide cannot use them. The KMS version
616 (sys/dev/drm2) supports the same hardware.
619 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
620 Please see the 20141231 entry below for information about prerequisites
621 and upgrading, if you are not already using clang 3.5.0 or higher.
624 The code that provides support for ZFS .zfs/ directory functionality
625 has been reimplemented. It's not possible now to create a snapshot
626 by mkdir under .zfs/snapshot/. That should be the only user visible
630 EISA bus support has been removed. The WITH_EISA option is no longer
634 MCA bus support has been removed.
637 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
638 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
641 The EM_MULTIQUEUE kernel configuration option is deprecated now that
642 the em(4) driver conforms to iflib specifications.
645 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
646 IFLIB. If you have a custom kernel configuration that excludes em(4)
647 but you use igb(4), you need to re-add em(4) to your custom configuration.
650 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
651 Please see the 20141231 entry below for information about prerequisites
652 and upgrading, if you are not already using clang 3.5.0 or higher.
655 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
656 Please see the 20141231 entry below for information about prerequisites
657 and upgrading, if you are not already using clang 3.5.0 or higher.
660 The layout of the pmap structure has changed for powerpc to put the pmap
661 statistics at the front for all CPU variations. libkvm(3) and all tools
662 that link against it need to be recompiled.
665 isl(4) and cyapa(4) drivers now require a new driver,
666 chromebook_platform(4), to work properly on Chromebook-class hardware.
667 On other types of hardware the drivers may need to be configured using
668 device hints. Please see the corresponding manual pages for details.
671 The urtwn(4) driver was merged into rtwn(4) and now consists of
672 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
674 Also, firmware for RTL8188CE was renamed due to possible name
675 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
678 GNU rcs has been removed from base. It is available as packages:
679 - rcs: Latest GPLv3 GNU rcs version.
680 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
684 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
685 modules now requires that the kernel configuration contain the
686 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
689 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
690 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
693 Relocatable object files with the extension of .So have been renamed
694 to use an extension of .pico instead. The purpose of this change is
695 to avoid a name clash with shared libraries on case-insensitive file
696 systems. On those file systems, foo.So is the same file as foo.so.
699 GNU rcs has been turned off by default. It can (temporarily) be built
700 again by adding WITH_RCS knob in src.conf.
701 Otherwise, GNU rcs is available from packages:
702 - rcs: Latest GPLv3 GNU rcs version.
703 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
706 The backup_uses_rcs functionality has been removed from rc.subr.
709 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
710 two separate components, QUEUE_MACRO_DEBUG_TRACE and
711 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
712 QUEUE_MACRO_DEBUG behavior.
715 r304787 changed some ioctl interfaces between the iSCSI userspace
716 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
717 rebuilt to work with new kernels. __FreeBSD_version has been bumped
721 The UDP receive code has been updated to only treat incoming UDP
722 packets that were addressed to an L2 broadcast address as L3
723 broadcast packets. It is not expected that this will affect any
724 standards-conforming UDP application. The new behaviour can be
725 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
729 Remove the openbsd_poll system call.
730 __FreeBSD_version has been bumped because of this.
733 The stable/11 branch has been created from head@r302406.
736 The libc stub for the pipe(2) system call has been replaced with
737 a wrapper that calls the pipe2(2) system call and the pipe(2)
738 system call is now only implemented by the kernels that include
739 "options COMPAT_FREEBSD10" in their config file (this is the
740 default). Users should ensure that this option is enabled in
741 their kernel or upgrade userspace to r302092 before upgrading their
745 CAM will now strip leading spaces from SCSI disks' serial numbers.
746 This will affect users who create UFS filesystems on SCSI disks using
747 those disk's diskid device nodes. For example, if /etc/fstab
748 previously contained a line like
749 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
750 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
751 transforms like gmirror may also be affected. ZFS users should
755 The bitstring(3) API has been updated with new functionality and
756 improved performance. But it is binary-incompatible with the old API.
757 Objects built with the new headers may not be linked against objects
758 built with the old headers.
761 The brk and sbrk functions have been removed from libc on arm64.
762 Binutils from ports has been updated to not link to these
763 functions and should be updated to the latest version before
764 installing a new libc.
767 The armv6 port now defaults to hard float ABI. Limited support
768 for running both hardfloat and soft float on the same system
769 is available using the libraries installed with -DWITH_LIBSOFT.
770 This has only been tested as an upgrade path for installworld
771 and packages may fail or need manual intervention to run. New
772 packages will be needed.
774 To update an existing self-hosted armv6hf system, you must add
775 TARGET_ARCH=armv6 on the make command line for both the build
776 and the install steps.
779 Kernel modules compiled outside of a kernel build now default to
780 installing to /boot/modules instead of /boot/kernel. Many kernel
781 modules built this way (such as those in ports) already overrode
782 KMODDIR explicitly to install into /boot/modules. However,
783 manually building and installing a module from /sys/modules will
784 now install to /boot/modules instead of /boot/kernel.
787 The CAM I/O scheduler has been committed to the kernel. There should be
788 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
789 list of known rogues that claim support for this but actually corrupt
790 data is believed to be complete, be on the lookout for data
791 corruption. The known rogue list is believed to be complete:
793 o Crucial MX100, M550 drives with MU01 firmware.
794 o Micron M510 and M550 drives with MU01 firmware.
795 o Micron M500 prior to MU07 firmware
796 o Samsung 830, 840, and 850 all firmwares
797 o FCCT M500 all firmwares
799 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
800 with working NCQ TRIM. For Micron branded drives, see your sales rep for
801 updated firmware. Black listed drives will work correctly because these
802 drives work correctly so long as no NCQ TRIMs are sent to them. Given
803 this list is the same as found in Linux, it's believed there are no
804 other rogues in the market place. All other models from the above
807 To be safe, if you are at all concerned, you can quirk each of your
808 drives to prevent NCQ from being sent by setting:
809 kern.cam.ada.X.quirks="0x2"
810 in loader.conf. If the drive requires the 4k sector quirk, set the
814 The FAST_DEPEND build option has been removed and its functionality is
815 now the one true way. The old mkdep(1) style of 'make depend' has
816 been removed. See 20160311 for further details.
819 Resource range types have grown from unsigned long to uintmax_t. All
820 drivers, and anything using libdevinfo, need to be recompiled.
823 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
824 builds. It no longer runs mkdep(1) during 'make depend', and the
825 'make depend' stage can safely be skipped now as it is auto ran
826 when building 'make all' and will generate all SRCS and DPSRCS before
827 building anything else. Dependencies are gathered at compile time with
828 -MF flags kept in separate .depend files per object file. Users should
829 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
833 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
834 kernel modules. Therefore, if you load any kernel modules at boot time,
835 please install the boot loaders after you install the kernel, but before
839 make buildkernel KERNCONF=YOUR_KERNEL_HERE
840 make installkernel KERNCONF=YOUR_KERNEL_HERE
841 make -C sys/boot install
842 <reboot in single user>
844 Then follow the usual steps, described in the General Notes section,
848 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
849 see the 20141231 entry below for information about prerequisites and
850 upgrading, if you are not already using clang 3.5.0 or higher.
853 The AIO subsystem is now a standard part of the kernel. The
854 VFS_AIO kernel option and aio.ko kernel module have been removed.
855 Due to stability concerns, asynchronous I/O requests are only
856 permitted on sockets and raw disks by default. To enable
857 asynchronous I/O requests on all file types, set the
858 vfs.aio.enable_unsafe sysctl to a non-zero value.
861 The ELF object manipulation tool objcopy is now provided by the
862 ELF Tool Chain project rather than by GNU binutils. It should be a
863 drop-in replacement, with the addition of arm64 support. The
864 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
865 to obtain the GNU version if necessary.
868 Building ZFS pools on top of zvols is prohibited by default. That
869 feature has never worked safely; it's always been prone to deadlocks.
870 Using a zvol as the backing store for a VM guest's virtual disk will
871 still work, even if the guest is using ZFS. Legacy behavior can be
872 restored by setting vfs.zfs.vol.recursive=1.
875 The NONE and HPN patches has been removed from OpenSSH. They are
876 still available in the security/openssh-portable port.
879 With the addition of ypldap(8), a new _ypldap user is now required
880 during installworld. "mergemaster -p" can be used to add the user
881 prior to installworld, as documented in the handbook.
884 The tftp loader (pxeboot) now uses the option root-path directive. As a
885 consequence it no longer looks for a pxeboot.4th file on the tftp
886 server. Instead it uses the regular /boot infrastructure as with the
890 The code to start recording plug and play data into the modules has
891 been committed. While the old tools will properly build a new kernel,
892 a number of warnings about "unknown metadata record 4" will be produced
893 for an older kldxref. To avoid such warnings, make sure to rebuild
894 the kernel toolchain (or world). Make sure that you have r292078 or
895 later when trying to build 292077 or later before rebuilding.
898 Debug data files are now built by default with 'make buildworld' and
899 installed with 'make installworld'. This facilitates debugging but
900 requires more disk space both during the build and for the installed
901 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
905 r291527 changed the internal interface between the nfsd.ko and
906 nfscommon.ko modules. As such, they must both be upgraded to-gether.
907 __FreeBSD_version has been bumped because of this.
910 Add support for unicode collation strings leads to a change of
911 order of files listed by ls(1) for example. To get back to the old
912 behaviour, set LC_COLLATE environment variable to "C".
914 Databases administrators will need to reindex their databases given
915 collation results will be different.
917 Due to a bug in install(1) it is recommended to remove the ancient
918 locales before running make installworld.
920 rm -rf /usr/share/locale/*
923 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
924 libcrypto.so.7 or libssl.so.7 must be recompiled.
927 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
928 Kernel modules isp_2400_multi and isp_2500_multi were removed and
929 should be replaced with isp_2400 and isp_2500 modules respectively.
932 The build previously allowed using 'make -n' to not recurse into
933 sub-directories while showing what commands would be executed, and
934 'make -n -n' to recursively show commands. Now 'make -n' will recurse
935 and 'make -N' will not.
938 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
939 and etcupdate will now use this file. A custom sendmail.cf is now
940 updated via this mechanism rather than via installworld. If you had
941 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
942 want to remove the exclusion or change it to "always install".
943 /etc/mail/sendmail.cf is now managed the same way regardless of
944 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
945 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
948 Compatibility shims for legacy ATA device names have been removed.
949 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
950 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
951 environment variables, /dev/ad* and /dev/ar* symbolic links.
954 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
955 Please see the 20141231 entry below for information about prerequisites
956 and upgrading, if you are not already using clang 3.5.0 or higher.
959 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
960 and renamed from .symbols to .debug. This reduces the size requirements
961 on the boot partition or file system and provides consistency with
962 userland debug files.
964 When using the supported kernel installation method the
965 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
966 as is done with /boot/kernel.
968 Developers wishing to maintain the historical behavior of installing
969 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
972 The wireless drivers had undergone changes that remove the 'parent
973 interface' from the ifconfig -l output. The rc.d network scripts
974 used to check presence of a parent interface in the list, so old
975 scripts would fail to start wireless networking. Thus, etcupdate(3)
976 or mergemaster(8) run is required after kernel update, to update your
977 rc.d scripts in /etc.
980 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
981 These configurations are now automatically interpreted as
982 'scrub fragment reassemble'.
985 Kernel-loadable modules for the random(4) device are back. To use
986 them, the kernel must have
989 options RANDOM_LOADABLE
991 kldload(8) can then be used to load random_fortuna.ko
992 or random_yarrow.ko. Please note that due to the indirect
993 function calls that the loadable modules need to provide,
994 the build-in variants will be slightly more efficient.
996 The random(4) kernel option RANDOM_DUMMY has been retired due to
997 unpopularity. It was not all that useful anyway.
1000 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1001 Control over building the ELF Tool Chain tools is now provided by
1002 the WITHOUT_TOOLCHAIN knob.
1005 The polarity of Pulse Per Second (PPS) capture events with the
1006 uart(4) driver has been corrected. Prior to this change the PPS
1007 "assert" event corresponded to the trailing edge of a positive PPS
1008 pulse and the "clear" event was the leading edge of the next pulse.
1010 As the width of a PPS pulse in a typical GPS receiver is on the
1011 order of 1 millisecond, most users will not notice any significant
1012 difference with this change.
1014 Anyone who has compensated for the historical polarity reversal by
1015 configuring a negative offset equal to the pulse width will need to
1016 remove that workaround.
1019 The default group assigned to /dev/dri entries has been changed
1020 from 'wheel' to 'video' with the id of '44'. If you want to have
1021 access to the dri devices please add yourself to the video group
1024 # pw groupmod video -m $USER
1027 The menu.rc and loader.rc files will now be replaced during
1028 upgrades. Please migrate local changes to menu.rc.local and
1029 loader.rc.local instead.
1032 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1033 strings and strip have been removed. The src.conf(5) knob
1034 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1037 As ZFS requires more kernel stack pages than is the default on some
1038 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1039 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1041 Please consider using 'options KSTACK_PAGES=X' where X is greater
1042 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1045 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1046 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1047 default, i.e., they will not contain "::". For example, instead
1048 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1049 to have a more specific match, such as different map entries for
1050 IPv6:0:0 vs IPv6:0. This change requires that configuration
1051 data (including maps, files, classes, custom ruleset, etc.) must
1052 use the same format, so make certain such configuration data is
1053 upgrading. As a very simple check search for patterns like
1054 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1055 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1056 the cf option UseCompressedIPv6Addresses.
1059 The default kernel entropy-processing algorithm is now
1060 Fortuna, replacing Yarrow.
1062 Assuming you have 'device random' in your kernel config
1063 file, the configurations allow a kernel option to override
1064 this default. You may choose *ONE* of:
1066 options RANDOM_YARROW # Legacy /dev/random algorithm.
1067 options RANDOM_DUMMY # Blocking-only driver.
1069 If you have neither, you get Fortuna. For most people,
1070 read no further, Fortuna will give a /dev/random that works
1071 like it always used to, and the difference will be irrelevant.
1073 If you remove 'device random', you get *NO* kernel-processed
1074 entropy at all. This may be acceptable to folks building
1075 embedded systems, but has complications. Carry on reading,
1076 and it is assumed you know what you need.
1078 *PLEASE* read random(4) and random(9) if you are in the
1079 habit of tweaking kernel configs, and/or if you are a member
1080 of the embedded community, wanting specific and not-usual
1081 behaviour from your security subsystems.
1083 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1084 random', you will NOT have a functioning /dev/random, and
1085 many cryptographic features will not work, including SSH.
1086 You may also find strange behaviour from the random(3) set
1087 of library functions, in particular sranddev(3), srandomdev(3)
1088 and arc4random(3). The reason for this is that the KERN_ARND
1089 sysctl only returns entropy if it thinks it has some to
1090 share, and with RANDOM_DUMMY or no 'device random' this
1094 An additional fix for the issue described in the 20150614 sendmail
1095 entry below has been committed in revision 284717.
1098 FreeBSD's old make (fmake) has been removed from the system. It is
1099 available as the devel/fmake port or via pkg install fmake.
1102 The fix for the issue described in the 20150614 sendmail entry
1103 below has been committed in revision 284436. The work
1104 around described in that entry is no longer needed unless the
1105 default setting is overridden by a confDH_PARAMETERS configuration
1106 setting of '5' or pointing to a 512 bit DH parameter file.
1109 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1110 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1111 and devel/kyua to version 0.20+ and adjust any calling code to work
1112 with Kyuafile and kyua.
1115 The import of openssl to address the FreeBSD-SA-15:10.openssl
1116 security advisory includes a change which rejects handshakes
1117 with DH parameters below 768 bits. sendmail releases prior
1118 to 8.15.2 (not yet released), defaulted to a 512 bit
1119 DH parameter setting for client connections. To work around
1120 this interoperability, sendmail can be configured to use a
1121 2048 bit DH parameter by:
1123 1. Edit /etc/mail/`hostname`.mc
1124 2. If a setting for confDH_PARAMETERS does not exist or
1125 exists and is set to a string beginning with '5',
1126 replace it with '2'.
1127 3. If a setting for confDH_PARAMETERS exists and is set to
1128 a file path, create a new file with:
1129 openssl dhparam -out /path/to/file 2048
1130 4. Rebuild the .cf file:
1131 cd /etc/mail/; make; make install
1132 5. Restart sendmail:
1133 cd /etc/mail/; make restart
1135 A sendmail patch is coming, at which time this file will be
1139 Generation of legacy formatted entries have been disabled by default
1140 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1141 entries were converted to use the new format by default when the new,
1142 machine independent format have been added and supported since FreeBSD
1145 Please see the pwd_mkdb(8) manual page for further details.
1148 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1149 20141231 entry below for information about prerequisites and upgrading,
1150 if you are not already using 3.5.0 or higher.
1153 TI platform code switched to using vendor DTS files and this update
1154 may break existing systems running on Beaglebone, Beaglebone Black,
1157 - dtb files should be regenerated/reinstalled. Filenames are the
1158 same but content is different now
1159 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1160 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1161 addressing scheme is now pin 25 on /dev/gpioc3.
1162 - Pandaboard: /etc/ttys should be updated, serial console device is
1163 now /dev/ttyu2, not /dev/ttyu0
1166 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1167 If you need the GNU extension from groff soelim(1), install groff
1168 from package: pkg install groff, or via ports: textproc/groff.
1171 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1172 defined in symlink(7); previously symlinks were silently ignored.
1175 The const qualifier has been removed from iconv(3) to comply with
1176 POSIX. The ports tree is aware of this from r384038 onwards.
1179 Libraries specified by LIBADD in Makefiles must have a corresponding
1180 DPADD_<lib> variable to ensure correct dependencies. This is now
1181 enforced in src.libnames.mk.
1184 From legacy ata(4) driver was removed support for SATA controllers
1185 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1186 Kernel modules ataahci and ataadaptec were removed completely,
1187 replaced by ahci and mvs modules respectively.
1190 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1191 the 20141231 entry below for information about prerequisites and
1192 upgrading, if you are not already using 3.5.0 or higher.
1195 The 32-bit PowerPC kernel has been changed to a position-independent
1196 executable. This can only be booted with a version of loader(8)
1197 newer than January 31, 2015, so make sure to update both world and
1198 kernel before rebooting.
1201 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1202 but before r278950, the RNG was not seeded properly. Immediately
1203 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1204 ssh keys or openssl keys) that were generated w/ a kernel from that
1205 range. This does not affect programs that directly used /dev/random
1206 or /dev/urandom. All userland uses of arc4random(3) are affected.
1209 The autofs(4) ABI was changed in order to restore binary compatibility
1210 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1211 with the new kernel.
1214 The powerpc64 kernel has been changed to a position-independent
1215 executable. This can only be booted with a new version of loader(8),
1216 so make sure to update both world and kernel before rebooting.
1219 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1220 only release, no new features have been added. Please see the 20141231
1221 entry below for information about prerequisites and upgrading, if you
1222 are not already using 3.5.0.
1225 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1226 taken from the ELF Tool Chain project rather than GNU binutils. They
1227 should be drop-in replacements, with the addition of arm64 support.
1228 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1229 binutils tools, if necessary. See 20150805 for updated information.
1232 The default Unbound configuration now enables remote control
1233 using a local socket. Users who have already enabled the
1234 local_unbound service should regenerate their configuration
1235 by running "service local_unbound setup" as root.
1238 The GNU texinfo and GNU info pages have been removed.
1239 To be able to view GNU info pages please install texinfo from ports.
1242 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1244 As of this release, a prerequisite for building clang, llvm and lldb is
1245 a C++11 capable compiler and C++11 standard library. This means that to
1246 be able to successfully build the cross-tools stage of buildworld, with
1247 clang as the bootstrap compiler, your system compiler or cross compiler
1248 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1249 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1252 On any standard FreeBSD 10.x or 11.x installation, where clang and
1253 libc++ are on by default (that is, on x86 or arm), this should work out
1256 On 9.x installations where clang is enabled by default, e.g. on x86 and
1257 powerpc, libc++ will not be enabled by default, so libc++ should be
1258 built (with clang) and installed first. If both clang and libc++ are
1259 missing, build clang first, then use it to build libc++.
1261 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1262 the instructions for 9.x above.
1264 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1265 default, and do not build clang.
1267 Many embedded systems are resource constrained, and will not be able to
1268 build clang in a reasonable time, or in some cases at all. In those
1269 cases, cross building bootable systems on amd64 is a workaround.
1271 This new version of clang introduces a number of new warnings, of which
1272 the following are most likely to appear:
1276 This warns in two cases, for both C and C++:
1277 * When the code is trying to take the absolute value of an unsigned
1278 quantity, which is effectively a no-op, and almost never what was
1279 intended. The code should be fixed, if at all possible. If you are
1280 sure that the unsigned quantity can be safely cast to signed, without
1281 loss of information or undefined behavior, you can add an explicit
1282 cast, or disable the warning.
1284 * When the code is trying to take an absolute value, but the called
1285 abs() variant is for the wrong type, which can lead to truncation.
1286 If you want to disable the warning instead of fixing the code, please
1287 make sure that truncation will not occur, or it might lead to unwanted
1290 -Wtautological-undefined-compare and
1291 -Wundefined-bool-conversion
1293 These warn when C++ code is trying to compare 'this' against NULL, while
1294 'this' should never be NULL in well-defined C++ code. However, there is
1295 some legacy (pre C++11) code out there, which actively abuses this
1296 feature, which was less strictly defined in previous C++ versions.
1298 Squid and openjdk do this, for example. The warning can be turned off
1299 for C++98 and earlier, but compiling the code in C++11 mode might result
1300 in unexpected behavior; for example, the parts of the program that are
1301 unreachable could be optimized away.
1304 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1305 kernel sources have been removed. The .h files remain, since some
1306 utilities include them. This will need to be fixed later.
1307 If "mount -t oldnfs ..." is attempted, it will fail.
1308 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1309 the utilities will report errors.
1312 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1313 directories to top level SUBDIR variable when their parent
1314 directory is included in LOCAL_DIRS. Users with build systems with
1315 such hierarchies and without SUBDIR entries in the parent
1316 directory Makefiles should add them or add the directories to
1320 faith(4) and faithd(8) have been removed from the base system. Faith
1321 has been obsolete for a very long time.
1324 vt(4), the new console driver, is enabled by default. It brings
1325 support for Unicode and double-width characters, as well as
1326 support for UEFI and integration with the KMS kernel video
1329 You may need to update your console settings in /etc/rc.conf,
1330 most probably the keymap. During boot, /etc/rc.d/syscons will
1331 indicate what you need to do.
1333 vt(4) still has issues and lacks some features compared to
1334 syscons(4). See the wiki for up-to-date information:
1335 https://wiki.freebsd.org/Newcons
1337 If you want to keep using syscons(4), you can do so by adding
1338 the following line to /boot/loader.conf:
1342 pjdfstest has been integrated into kyua as an opt-in test suite.
1343 Please see share/doc/pjdfstest/README for more details on how to
1347 gperf has been removed from the base system for architectures
1348 that use clang. Ports that require gperf will obtain it from the
1352 pjdfstest has been moved from tools/regression/pjdfstest to
1356 At svn r271982, The default linux compat kernel ABI has been adjusted
1357 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1358 update. If you wish to continue using the linux-f10 compat ports,
1359 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1360 encouraged to update their linux-compat packages to linux-c6 during
1361 their next update cycle.
1364 The ofwfb driver, used to provide a graphics console on PowerPC when
1365 using vt(4), no longer allows mmap() of all physical memory. This
1366 will prevent Xorg on PowerPC with some ATI graphics cards from
1367 initializing properly unless x11-servers/xorg-server is updated to
1371 The xdev targets have been converted to using TARGET and
1372 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1375 The default unbound configuration has been modified to address
1376 issues with reverse lookups on networks that use private
1377 address ranges. If you use the local_unbound service, run
1378 "service local_unbound setup" as root to regenerate your
1379 configuration, then "service local_unbound reload" to load the
1383 The GNU texinfo and GNU info pages are not built and installed
1384 anymore, WITH_INFO knob has been added to allow to built and install
1386 UPDATE: see 20150102 entry on texinfo's removal
1389 The GNU readline library is now an INTERNALLIB - that is, it is
1390 statically linked into consumers (GDB and variants) in the base
1391 system, and the shared library is no longer installed. The
1392 devel/readline port is available for third party software that
1396 The Itanium architecture (ia64) has been removed from the list of
1397 known architectures. This is the first step in the removal of the
1401 Commit r268115 has added NFSv4.1 server support, merged from
1402 projects/nfsv4.1-server. Since this includes changes to the
1403 internal interfaces between the NFS related modules, a full
1404 build of the kernel and modules will be necessary.
1405 __FreeBSD_version has been bumped.
1408 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1409 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1410 which differs from the behaviour controlled by this knob.)
1413 Maximal length of the serial number in CTL was increased from 16 to
1414 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1415 and ctld, need to be rebuilt to work with a new kernel.
1418 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1419 1 respectively to match the upstream numbers. They were out of
1420 sync because, when they were originally added to FreeBSD, the
1421 upstream versions were not respected. These libraries are private
1422 and not yet built by default, so renumbering them should be a
1423 non-issue. However, unclean source trees will yield broken test
1424 programs once the operator executes "make delete-old-libs" after a
1425 "make installworld".
1427 Additionally, the atf-sh binary was made private by moving it into
1428 /usr/libexec/. Already-built shell test programs will keep the
1429 path to the old binary so they will break after "make delete-old"
1432 If you are using WITH_TESTS=yes (not the default), wipe the object
1433 tree and rebuild from scratch to prevent spurious test failures.
1434 This is only needed once: the misnumbered libraries and misplaced
1435 binaries have been added to OptionalObsoleteFiles.inc so they will
1436 be removed during a clean upgrade.
1439 Clang and llvm have been upgraded to 3.4.1 release.
1442 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1443 be removed to avoid issues in the future (and has been added to
1447 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1448 past, it affected all builds that used the bsd.*.mk files. The old
1449 behavior was a bug, but people may have relied upon it. To get this
1450 behavior back, you can .include /etc/src.conf from /etc/make.conf
1451 (which is still global and isn't changed). This also changes the
1452 behavior of incremental builds inside the tree of individual
1453 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1454 Although this has survived make universe and some upgrade scenarios,
1455 other upgrade scenarios may have broken. At least one form of
1456 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1457 as well... In cases where MAKESYSPATH isn't working with this
1458 setting, you'll need to set it to the full path to your tree.
1460 One side effect of all this cleaning up is that bsd.compiler.mk
1461 is no longer implicitly included by bsd.own.mk. If you wish to
1462 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1466 The lindev device has been removed since /dev/full has been made a
1467 standard device. __FreeBSD_version has been bumped.
1470 The knob WITHOUT_VI was added to the base system, which controls
1471 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1472 in order to reorder files share/termcap and didn't build ex(1) as a
1473 build tool, so building/installing with WITH_VI is highly advised for
1474 build hosts for older releases.
1476 This issue has been fixed in stable/9 and stable/10 in r277022 and
1477 r276991, respectively.
1480 The YES_HESIOD knob has been removed. It has been obsolete for
1481 a decade. Please move to using WITH_HESIOD instead or your builds
1482 will silently lack HESIOD.
1485 The uart(4) driver has been changed with respect to its handling
1486 of the low-level console. Previously the uart(4) driver prevented
1487 any process from changing the baudrate or the CLOCAL and HUPCL
1488 control flags. By removing the restrictions, operators can make
1489 changes to the serial console port without having to reboot.
1490 However, when getty(8) is started on the serial device that is
1491 associated with the low-level console, a misconfigured terminal
1492 line in /etc/ttys will now have a real impact.
1493 Before upgrading the kernel, make sure that /etc/ttys has the
1494 serial console device configured as 3wire without baudrate to
1495 preserve the previous behaviour. E.g:
1496 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1499 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1500 to improve performance. To re-enable it, if needed, run rpcbind
1501 with command line option -W.
1504 Switched back to the GPL dtc compiler due to updates in the upstream
1505 dts files not being supported by the BSDL dtc compiler. You will need
1506 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1507 may result while building dtb files during a kernel build if you fail
1508 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1511 Clang and llvm have been upgraded to 3.4 release.
1514 The nve(4) driver has been removed. Please use the nfe(4) driver
1515 for NVIDIA nForce MCP Ethernet adapters instead.
1518 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1519 This could cause certain C++ applications using shared libraries built
1520 against the previous version of libc++ to crash. The incompatibility
1521 has now been fixed, but any C++ applications or shared libraries built
1522 between r261283 and r261801 should be recompiled.
1525 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1526 capability mode support. Please note that enabling the feature in
1527 kernel is still highly recommended.
1530 OpenSSH is now built with sandbox support, and will use sandbox as
1531 the default privilege separation method. This requires Capsicum
1532 capability mode support in kernel.
1535 The libelf and libdwarf libraries have been updated to newer
1536 versions from upstream. Shared library version numbers for
1537 these two libraries were bumped. Any ports or binaries
1538 requiring these two libraries should be recompiled.
1539 __FreeBSD_version is bumped to 1100006.
1542 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1543 instead of providing an explicit one, this would prevent such
1544 Makefile from providing its own Kyuafile in the future during
1545 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1546 intervention is needed to clean an objdir if you use NO_CLEAN:
1547 # find /usr/obj -name Kyuafile | xargs rm -f
1550 The behavior of gss_pseudo_random() for the krb5 mechanism
1551 has changed, for applications requesting a longer random string
1552 than produced by the underlying enctype's pseudo-random() function.
1553 In particular, the random string produced from a session key of
1554 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1555 be different at the 17th octet and later, after this change.
1556 The counter used in the PRF+ construction is now encoded as a
1557 big-endian integer in accordance with RFC 4402.
1558 __FreeBSD_version is bumped to 1100004.
1561 The WITHOUT_ATF build knob has been removed and its functionality
1562 has been subsumed into the more generic WITHOUT_TESTS. If you were
1563 using the former to disable the build of the ATF libraries, you
1564 should change your settings to use the latter.
1567 The default version of mtree is nmtree which is obtained from
1568 NetBSD. The output is generally the same, but may vary
1569 slightly. If you found you need identical output adding
1570 "-F freebsd9" to the command line should do the trick. For the
1571 time being, the old mtree is available as fmtree.
1574 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1575 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1576 1.1.4_8 and verify bsdyml not linked in, before running "make
1578 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1580 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1583 The stable/10 branch has been created in subversion from head
1590 Avoid using make -j when upgrading. While generally safe, there are
1591 sometimes problems using -j to upgrade. If your upgrade fails with
1592 -j, please try again without -j. From time to time in the past there
1593 have been problems using -j with buildworld and/or installworld. This
1594 is especially true when upgrading between "distant" versions (eg one
1595 that cross a major release boundary or several minor releases, or when
1596 several months have passed on the -current branch).
1598 Sometimes, obscure build problems are the result of environment
1599 poisoning. This can happen because the make utility reads its
1600 environment when searching for values for global variables. To run
1601 your build attempts in an "environmental clean room", prefix all make
1602 commands with 'env -i '. See the env(1) manual page for more details.
1604 When upgrading from one major version to another it is generally best to
1605 upgrade to the latest code in the currently installed branch first, then
1606 do an upgrade to the new branch. This is the best-tested upgrade path,
1607 and has the highest probability of being successful. Please try this
1608 approach if you encounter problems with a major version upgrade. Since
1609 the stable 4.x branch point, one has generally been able to upgrade from
1610 anywhere in the most recent stable branch to head / current (or even the
1611 last couple of stable branches). See the top of this file when there's
1614 When upgrading a live system, having a root shell around before
1615 installing anything can help undo problems. Not having a root shell
1616 around can lead to problems if pam has changed too much from your
1617 starting point to allow continued authentication after the upgrade.
1619 This file should be read as a log of events. When a later event changes
1620 information of a prior event, the prior event should not be deleted.
1621 Instead, a pointer to the entry with the new information should be
1622 placed in the old entry. Readers of this file should also sanity check
1623 older entries before relying on them blindly. Authors of new entries
1624 should write them with this in mind.
1628 When upgrading the boot ZFS pool to a new version, always follow
1631 1.) recompile and reinstall the ZFS boot loader and boot block
1632 (this is part of "make buildworld" and "make installworld")
1634 2.) update the ZFS boot block on your boot drive
1636 The following example updates the ZFS boot block on the first
1637 partition (freebsd-boot) of a GPT partitioned drive ada0:
1638 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1640 Non-boot pools do not need these updates.
1644 If you are updating from a prior version of FreeBSD (even one just
1645 a few days old), you should follow this procedure. It is the most
1646 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1648 make kernel-toolchain
1649 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1650 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1652 To test a kernel once
1653 ---------------------
1654 If you just want to boot a kernel once (because you are not sure
1655 if it works, or if you want to boot a known bad kernel to provide
1656 debugging information) run
1657 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1658 nextboot -k testkernel
1660 To rebuild everything and install it on the current system.
1661 -----------------------------------------------------------
1662 # Note: sometimes if you are running current you gotta do more than
1663 # is listed here if you are upgrading from a really old current.
1665 <make sure you have good level 0 dumps>
1667 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1668 make installkernel KERNCONF=YOUR_KERNEL_HERE
1670 <reboot in single user> [3]
1677 To cross-install current onto a separate partition
1678 --------------------------------------------------
1679 # In this approach we use a separate partition to hold
1680 # current's root, 'usr', and 'var' directories. A partition
1681 # holding "/", "/usr" and "/var" should be about 2GB in
1684 <make sure you have good level 0 dumps>
1687 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1688 <maybe newfs current's root partition>
1689 <mount current's root partition on directory ${CURRENT_ROOT}>
1690 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1691 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1692 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1693 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1694 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1695 <reboot into current>
1696 <do a "native" rebuild/install as described in the previous section>
1697 <maybe install compatibility libraries from ports/misc/compat*>
1701 To upgrade in-place from stable to current
1702 ----------------------------------------------
1703 <make sure you have good level 0 dumps>
1705 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1706 make installkernel KERNCONF=YOUR_KERNEL_HERE
1708 <reboot in single user> [3]
1715 Make sure that you've read the UPDATING file to understand the
1716 tweaks to various things you need. At this point in the life
1717 cycle of current, things change often and you are on your own
1718 to cope. The defaults can also change, so please read ALL of
1719 the UPDATING entries.
1721 Also, if you are tracking -current, you must be subscribed to
1722 freebsd-current@freebsd.org. Make sure that before you update
1723 your sources that you have read and understood all the recent
1724 messages there. If in doubt, please track -stable which has
1725 much fewer pitfalls.
1727 [1] If you have third party modules, such as vmware, you
1728 should disable them at this point so they don't crash your
1731 [3] From the bootblocks, boot -s, and then do
1736 adjkerntz -i # if CMOS is wall time
1737 Also, when doing a major release upgrade, it is required that
1738 you boot into single user mode to do the installworld.
1740 [4] Note: This step is non-optional. Failure to do this step
1741 can result in a significant reduction in the functionality of the
1742 system. Attempting to do it by hand is not recommended and those
1743 that pursue this avenue should read this file carefully, as well
1744 as the archives of freebsd-current and freebsd-hackers mailing lists
1745 for potential gotchas. The -U option is also useful to consider.
1746 See mergemaster(8) for more information.
1748 [5] Usually this step is a no-op. However, from time to time
1749 you may need to do this if you get unknown user in the following
1750 step. It never hurts to do it all the time. You may need to
1751 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1752 install) after the buildworld before this step if you last updated
1753 from current before 20130425 or from -stable before 20130430.
1755 [6] This only deletes old files and directories. Old libraries
1756 can be deleted by "make delete-old-libs", but you have to make
1757 sure that no program is using those libraries anymore.
1759 [8] In order to have a kernel that can run the 4.x binaries needed to
1760 do an installworld, you must include the COMPAT_FREEBSD4 option in
1761 your kernel. Failure to do so may leave you with a system that is
1762 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1763 required to run the 5.x binaries on more recent kernels. And so on
1764 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1766 Make sure that you merge any new devices from GENERIC since the
1767 last time you updated your kernel config file.
1769 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1770 "?=" instead of the "=" assignment operator, so that buildworld can
1771 override the CPUTYPE if it needs to.
1773 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1774 not on the command line, or in /etc/make.conf. buildworld will
1775 warn if it is improperly defined.
1778 This file contains a list, in reverse chronological order, of major
1779 breakages in tracking -current. It is not guaranteed to be a complete
1780 list of such breakages, and only contains entries since September 23, 2011.
1781 If you need to see UPDATING entries from before that date, you will need
1782 to fetch an UPDATING file from an older FreeBSD release.
1784 Copyright information:
1786 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1788 Redistribution, publication, translation and use, with or without
1789 modification, in full or in part, in any form or format of this
1790 document are permitted without further permission from the author.
1792 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1793 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1794 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1795 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1796 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1797 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1798 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1799 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1800 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1801 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1802 POSSIBILITY OF SUCH DAMAGE.
1804 Contact Warner Losh if you have any questions about your use of