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 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
36 This should have no effect if the kernel is booted via BIOS/legacy boot.
37 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
38 has a buggy firmware that prevents a successful boot due to use of
42 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
43 support has been removed from the tree. These ports were
44 obsolete and/or known to be broken for many years.
47 loader.efi has been augmented to participate more fully in the
48 UEFI boot manager protocol. loader.efi will now look at the
49 BootXXXX environment variable to determine if a specific kernel
50 or root partition was specified. XXXX is derived from BootCurrent.
51 efibootmgr(8) manages these standard UEFI variables.
54 zfsloader's functionality has now been folded into loader.
55 zfsloader is no longer necessary once you've updated your
56 boot blocks. For a transition period, we will install a
57 hardlink for zfsloader to loader to allow a smooth transition
58 until the boot blocks can be updated (hard link because old
59 zfs boot blocks don't understand symlinks).
62 ARM64 now have efifb support, if you want to have serial console
63 on your arm64 board when an screen is connected and the bootloader
64 setup a frambuffer for us to use, just add :
68 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
69 an screen connected as the firmware will setup a framebuffer are that
70 u-boot will expose as an EFI framebuffer.
73 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
74 or take steps to update /etc/passwd before doing installworld on
75 existing systems. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
76 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
77 the ntp config file contain options that change file/dir locations.
78 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
79 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
80 taking steps to ensure that all required files/dirs are accessible
84 Big endian arm support has been removed.
87 The static environment setup in kernel configs is no longer mutually
88 exclusive with the loader(8) environment by default. In order to
89 restore the previous default behavior of disabling the loader(8)
90 environment if a static environment is present, you must specify
91 loader_env.disabled=1 in the static environment.
94 The ABI of syscalls used by management tools like sockstat and
95 netstat has been broken to allow 32-bit binaries to work on
96 64-bit kernels without modification. These programs will need
97 to match the kernel in order to function. External programs may
98 require minor modifications to accommodate a change of type in
99 structures from pointers to 64-bit virtual addresses.
102 On i386 and amd64 atomics are now inlined. Out of tree modules using
103 atomics will need to be rebuilt.
106 The '%I' format in the kern.corefile sysctl limits the number of
107 core files that a process can generate to the number stored in the
108 debug.ncores sysctl. The '%I' format is replaced by the single digit
109 index. Previously, if all indexes were taken the kernel would overwrite
110 only a core file with the highest index in a filename.
111 Currently the system will create a new core file if there is a free
112 index or if all slots are taken it will overwrite the oldest one.
115 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
116 6.0.1. Please see the 20141231 entry below for information about
117 prerequisites and upgrading, if you are not already using clang 3.5.0
121 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
122 needed to be changed to work with it. This change was made with r335763
123 and requires a mergemaster / etcupdate / etc to update the installed file.
126 r334930 changed the interface between the NFS modules, so they all
127 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
130 The kernel / userland interface for devinfo changed, so you'll
131 need a new kernel and userland as a pair for it to work (rebuilding
132 lib/libdevinfo is all that's required). devinfo and devmatch will
133 not work, but everything else will when there's a mismatch.
136 The on-disk format for hwpmc callchain records has changed to include
137 threadid corresponding to a given record. This changes the field offsets
138 and thus requires that libpmcstat be rebuilt before using a kernel
142 The vxge(4) driver has been removed. This driver was introduced into
143 HEAD one week before the Exar left the Ethernet market and is not
144 known to be used. If you have device vxge in your kernel config file
148 The amd64 kernel now requires a ld that supports ifunc to produce a
149 working kernel, either lld or a newer binutils. lld is built by default
150 on amd64, and the 'buildkernel' target uses it automatically. However,
151 it is not the default linker, so building the kernel the traditional
152 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
153 binutils port/package). lld will soon be default, and this requirement
157 The nxge(4) driver has been removed. This driver was for PCI-X 10g
158 cards made by s2io/Neterion. The company was aquired by Exar and
159 no longer sells or supports Ethernet products. If you have device
160 nxge in your kernel config file it must be removed.
163 The tz database (tzdb) has been updated to 2018e. This version more
164 correctly models time stamps in time zones with negative DST such as
165 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
166 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
167 time zone abbreviations and the tm_isdst flag.
170 The ixgb(4) driver has been removed. This driver was for an early and
171 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
172 quickly shifted to the long lived ixgbe family. If you have device
173 ixgb in your kernel config file it must be removed.
176 The lmc(4) driver has been removed. This was a WAN interface
177 card that was already reportedly rare in 2003, and had an ambiguous
178 license. If you have device lmc in your kernel config file it must
182 Support for Arcnet networks has been removed. If you have device
183 arcnet or device cm in your kernel config file they must be
187 Support for FDDI networks has been removed. If you have device
188 fddi or device fpa in your kernel config file they must be
192 In addition to supporting RFC 3164 formatted messages, the
193 syslogd(8) service is now capable of parsing RFC 5424 formatted
194 log messages. The main benefit of using RFC 5424 is that clients
195 may now send log messages with timestamps containing year numbers,
196 microseconds and time zone offsets.
198 Similarly, the syslog(3) C library function has been altered to
199 send RFC 5424 formatted messages to the local system logging
200 daemon. On systems using syslogd(8), this change should have no
201 negative impact, as long as syslogd(8) and the C library are
202 updated at the same time. On systems using a different system
203 logging daemon, it may be necessary to make configuration
204 adjustments, depending on the software used.
206 When using syslog-ng, add the 'syslog-protocol' flag to local
207 input sources to enable parsing of RFC 5424 formatted messages:
210 unix-dgram("/var/run/log" flags(syslog-protocol));
213 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
214 of the 'imuxsock' module to let messages be processed by the
215 regular RFC 3164/5424 parsing pipeline:
217 module(load="imuxsock" SysSock.UseSpecialParser="off")
219 Do note that these changes only affect communication between local
220 applications and syslogd(8). The format that syslogd(8) uses to
221 store messages on disk or forward messages to other systems
222 remains unchanged. syslogd(8) still uses RFC 3164 for these
223 purposes. Options to customize this behaviour will be added in the
224 future. Utilities that process log files stored in /var/log are
225 thus expected to continue to function as before.
227 __FreeBSD_version has been incremented to 1200061 to denote this
231 Support for token ring networks has been removed. If you
232 have "device token" in your kernel config you should remove
233 it. No device drivers supported token ring.
236 makefs was modified to be able to tag ISO9660 El Torito boot catalog
237 entries as EFI instead of overloading the i386 tag as done previously.
238 The amd64 mkisoimages.sh script used to build amd64 ISO images for
239 release was updated to use this. This may mean that makefs must be
240 updated before "make cdrom" can be run in the release directory. This
241 should be as simple as:
243 $ cd $SRCDIR/usr.sbin/makefs
244 $ make depend all install
247 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
248 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
249 Co-existance for the transition period will come shortly. Booting is a
250 complex environment and test coverage for Lua-enabled loaders has been
251 thin, so it would be prudent to assume it might not work and make
252 provisions for backup boot methods.
255 devmatch functionality has been turned on in devd. It will automatically
256 load drivers for unattached devices. This may cause unexpected drivers to
257 be loaded. Please report any problems to current@ and imp@freebsd.org.
260 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
261 6.0.0. Please see the 20141231 entry below for information about
262 prerequisites and upgrading, if you are not already using clang 3.5.0
266 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
267 This means it is used to link the kernel and userland libraries and
268 executables, but is not yet installed as /usr/bin/ld by default.
270 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
271 WITHOUT_LLD_BOOTSTRAP=yes
274 On i386, pmtimer has been removed. Its functionality has been folded
275 into apm. It was a no-op on ACPI in current for a while now (but was still
276 needed on i386 in FreeBSD 11 and earlier). Users may need to remove it
277 from kernel config files.
280 The use of RSS hash from the network card aka flowid has been
281 disabled by default for lagg(4) as it's currently incompatible with
282 the lacp and loadbalance protocols.
284 This can be re-enabled by setting the following in loader.conf:
285 net.link.lagg.default_use_flowid="1"
288 The SW_WATCHDOG option is no longer necessary to enable the
289 hardclock-based software watchdog if no hardware watchdog is
290 configured. As before, SW_WATCHDOG will cause the software
291 watchdog to be enabled even if a hardware watchdog is configured.
294 r326887 fixes the issue described in the 20171214 UPDATING entry.
295 r326888 flips the switch back to building GELI support always.
298 r362593 broke ZFS + GELI support for reasons unknown. However,
299 it also broke ZFS support generally, so GELI has been turned off
300 by default as the lesser evil in r326857. If you boot off ZFS and/or
301 GELI, it might not be a good time to update.
304 PowerPC users must update loader(8) by rebuilding world before
305 installing a new kernel, as the protocol connecting them has
306 changed. Without the update, loader metadata will not be passed
307 successfully to the kernel and users will have to enter their
308 root partition at the kernel mountroot prompt to continue booting.
309 Newer versions of loader can boot old kernels without issue.
312 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
313 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
314 to WITH/OUT_LOADER_GELI.
317 The naive and non-compliant support of posix_fallocate(2) in ZFS
318 has been removed as of r325320. The system call now returns EINVAL
319 when used on a ZFS file. Although the new behavior complies with the
320 standard, some consumers are not prepared to cope with it.
321 One known victim is lld prior to r325420.
324 Building in a FreeBSD src checkout will automatically create object
325 directories now rather than store files in the current directory if
326 'make obj' was not ran. Calling 'make obj' is no longer necessary.
327 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
328 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
332 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
333 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
334 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
335 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
336 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
337 The UNIFIED_OBJDIR option is a transitional feature that will be
338 removed for 12.0 release; please migrate to the new format for any
339 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
340 than hardcoding paths.
343 The native-xtools target no longer installs the files by default to the
344 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
345 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
348 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
349 options are changing from controlling the build if defined / undefined
350 to controlling the build with explicit 'yes' or 'no' values. They will
351 shift to WITH/WITHOUT options to match other options in the system.
354 libstand has turned into a private library for sys/boot use only.
355 It is no longer supported as a public interface outside of sys/boot.
358 The arm port has split armv6 into armv6 and armv7. armv7 is now
359 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
360 and are running a kernel from before r324363, you will need to add
361 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
364 When building multiple kernels using KERNCONF, non-existent KERNCONF
365 files will produce an error and buildkernel will fail. Previously
366 missing KERNCONF files silently failed giving no indication as to
367 why, only to subsequently discover during installkernel that the
368 desired kernel was never built in the first place.
371 The default serial number format for CTL LUNs has changed. This will
372 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
373 or iSCSI clients care about their LUNs' serial numbers. Users who
374 require serial number stability should hardcode serial numbers in
378 For 32-bit arm compiled for hard-float support, soft-floating point
379 binaries now always get their shared libraries from
380 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
381 /usr/libsoft also existed). Only users with a hard-float ld.so, but
382 soft-float everything else should be affected.
385 The geli password typed at boot is now hidden. To restore the previous
386 behavior, see geli(8) for configuration options.
389 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
390 sysctl values. Minor nit, but requires a rebuild of both world/kernel
394 "make check" behavior (made in ^/head@r295380) has been changed to
395 execute from a limited sandbox, as opposed to executing from
399 - The "beforecheck" and "aftercheck" targets are now specified.
400 - ${CHECKDIR} (added in commit noted above) has been removed.
401 - Legacy behavior can be enabled by setting
402 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
404 If the limited sandbox mode is enabled, "make check" will execute
405 "make distribution", then install, execute the tests, and clean up the
406 sandbox if successful.
408 The "make distribution" and "make install" targets are typically run as
409 root to set appropriate permissions and ownership at installation time.
410 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
411 environment if executing "make check" with limited sandbox mode using
412 an unprivileged user.
415 Since the switch to GPT disk labels, fsck for UFS/FFS has been
416 unable to automatically find alternate superblocks. As of r322297,
417 the information needed to find alternate superblocks has been
418 moved to the end of the area reserved for the boot block.
419 Filesystems created with a newfs of this vintage or later
420 will create the recovery information. If you have a filesystem
421 created prior to this change and wish to have a recovery block
422 created for your filesystem, you can do so by running fsck in
423 foreground mode (i.e., do not use the -p or -y options). As it
424 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
425 to which you should answer yes.
428 As of r321665, an NFSv4 server configuration that services
429 Kerberos mounts or clients that do not support the uid/gid in
430 owner/owner_group string capability, must explicitly enable
431 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
432 machine's /etc/rc.conf file.
435 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
436 Please see the 20141231 entry below for information about prerequisites
437 and upgrading, if you are not already using clang 3.5.0 or higher.
440 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
441 r-commands (rlogin, rsh, etc.) to be built with the base system.
444 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
445 a very major ABI incompatible change, so users of FreeBSD/powerpc must
446 be careful when performing source upgrades. It is best to run
447 'make installworld' from an alternate root system, either a live
448 CD/memory stick, or a temporary root partition. Additionally, all ports
449 must be recompiled. powerpc64 is largely unaffected, except in the case
450 of 32-bit compatibility. All 32-bit binaries will be affected.
453 Forward compatibility for the "ino64" project have been committed. This
454 will allow most new binaries to run on older kernels in a limited
455 fashion. This prevents many of the common foot-shooting actions in the
456 upgrade as well as the limited ability to roll back the kernel across
457 the ino64 upgrade. Complicated use cases may not work properly, though
458 enough simpler ones work to allow recovery in most situations.
461 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
462 if you require the GPL compiler.
465 The internal ABI used for communication between the NFS kernel modules
466 was changed by r320085, so __FreeBSD_version was bumped to
467 ensure all the NFS related modules are updated together.
470 The ABI of struct event was changed by extending the data
471 member to 64bit and adding ext fields. For upgrade, same
472 precautions as for the entry 20170523 "ino64" must be
476 The GNU roff toolchain has been removed from base. To render manpages
477 which are not supported by mandoc(1), man(1) can fallback on GNU roff
478 from ports (and recommends to install it).
479 To render roff(7) documents, consider using GNU roff from ports or the
480 heirloom doctools roff toolchain from ports via pkg install groff or
481 via pkg install heirloom-doctools.
484 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
485 smaller runtime footprint builds. This is useful for embedded systems
486 which only require one chipset support.
488 If you load it as a module, make sure this is in /boot/loader.conf:
492 This will load the HAL, all chip/RF backends and if_ath_pci.
493 If you have if_ath_pci in /boot/loader.conf, ensure it is after
494 if_ath or it will not load any HAL chipset support.
496 If you want to selectively load things (eg on ye cheape ARM/MIPS
497 platforms where RAM is at a premium) you should:
500 * load the chip modules in question
501 * load ath_rate, ath_dfs
503 * load if_ath_pci and/or if_ath_ahb depending upon your particular
504 bus bind type - this is where probe/attach is done.
506 For further comments/feedback, poke adrian@ .
509 The "ino64" 64-bit inode project has been committed, which extends
510 a number of types to 64 bits. Upgrading in place requires care and
511 adherence to the documented upgrade procedure.
513 If using a custom kernel configuration ensure that the
514 COMPAT_FREEBSD11 option is included (as during the upgrade the
515 system will be running the ino64 kernel with the existing world).
517 For the safest in-place upgrade begin by removing previous build
518 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
519 full procedure documented below under the heading "To rebuild
520 everything and install it on the current system." Specifically,
521 a reboot is required after installing the new kernel before
525 The NATM framework including the en(4), fatm(4), hatm(4), and
526 patm(4) devices has been removed. Consumers should plan a
527 migration before the end-of-life date for FreeBSD 11.
530 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
531 diff has not been implemented, if those are needed a newer version of
532 GNU diff is available via the diffutils package under the gdiff name.
535 As of r316810 for ipfilter, keep frags is no longer assumed when
536 keep state is specified in a rule. r316810 aligns ipfilter with
537 documentation in man pages separating keep frags from keep state.
538 This allows keep state to be specified without forcing keep frags
539 and allows keep frags to be specified independently of keep state.
540 To maintain previous behaviour, also specify keep frags with
541 keep state (as documented in ipf.conf.5).
544 arm64 builds now use the base system LLD 4.0.0 linker by default,
545 instead of requiring that the aarch64-binutils port or package be
546 installed. To continue using aarch64-binutils, set
547 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
550 The UDP optimization in entry 20160818 that added the sysctl
551 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
552 packets will no longer be treated as L3 broadcast packets.
555 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
556 use any explicitly assigned loopback address available in the jail
557 instead of using the first assigned address of the jail.
560 The ctl.ko module no longer implements the iSCSI target frontend:
561 cfiscsi.ko does instead.
563 If building cfiscsi.ko as a kernel module, the module can be loaded
564 via one of the following methods:
565 - `cfiscsi_load="YES"` in loader.conf(5).
566 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
567 - ctladm(8)/ctld(8), when compiled with iSCSI support
568 (`WITH_ISCSI=yes` in src.conf(5))
570 Please see cfiscsi(4) for more details.
573 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
574 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
575 same source (previously, the dependency of mmcsd.ko on mmc.ko was
576 missing, but mmcsd.ko now will refuse to load if it is incompatible
580 The syntax of ipfw(8) named states was changed to avoid ambiguity.
581 If you have used named states in the firewall rules, you need to modify
582 them after installworld and before rebooting. Now named states must
583 be prefixed with colon.
586 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
587 removed as the userland we provide cannot use them. The KMS version
588 (sys/dev/drm2) supports the same hardware.
591 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
592 Please see the 20141231 entry below for information about prerequisites
593 and upgrading, if you are not already using clang 3.5.0 or higher.
596 The code that provides support for ZFS .zfs/ directory functionality
597 has been reimplemented. It's not possible now to create a snapshot
598 by mkdir under .zfs/snapshot/. That should be the only user visible
602 EISA bus support has been removed. The WITH_EISA option is no longer
606 MCA bus support has been removed.
609 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
610 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
613 The EM_MULTIQUEUE kernel configuration option is deprecated now that
614 the em(4) driver conforms to iflib specifications.
617 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
618 IFLIB. If you have a custom kernel configuration that excludes em(4)
619 but you use igb(4), you need to re-add em(4) to your custom configuration.
622 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
623 Please see the 20141231 entry below for information about prerequisites
624 and upgrading, if you are not already using clang 3.5.0 or higher.
627 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
628 Please see the 20141231 entry below for information about prerequisites
629 and upgrading, if you are not already using clang 3.5.0 or higher.
632 The layout of the pmap structure has changed for powerpc to put the pmap
633 statistics at the front for all CPU variations. libkvm(3) and all tools
634 that link against it need to be recompiled.
637 isl(4) and cyapa(4) drivers now require a new driver,
638 chromebook_platform(4), to work properly on Chromebook-class hardware.
639 On other types of hardware the drivers may need to be configured using
640 device hints. Please see the corresponding manual pages for details.
643 The urtwn(4) driver was merged into rtwn(4) and now consists of
644 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
646 Also, firmware for RTL8188CE was renamed due to possible name
647 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
650 GNU rcs has been removed from base. It is available as packages:
651 - rcs: Latest GPLv3 GNU rcs version.
652 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
656 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
657 modules now requires that the kernel configuration contain the
658 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
661 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
662 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
665 Relocatable object files with the extension of .So have been renamed
666 to use an extension of .pico instead. The purpose of this change is
667 to avoid a name clash with shared libraries on case-insensitive file
668 systems. On those file systems, foo.So is the same file as foo.so.
671 GNU rcs has been turned off by default. It can (temporarily) be built
672 again by adding WITH_RCS knob in src.conf.
673 Otherwise, GNU rcs is available from packages:
674 - rcs: Latest GPLv3 GNU rcs version.
675 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
678 The backup_uses_rcs functionality has been removed from rc.subr.
681 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
682 two separate components, QUEUE_MACRO_DEBUG_TRACE and
683 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
684 QUEUE_MACRO_DEBUG behavior.
687 r304787 changed some ioctl interfaces between the iSCSI userspace
688 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
689 rebuilt to work with new kernels. __FreeBSD_version has been bumped
693 The UDP receive code has been updated to only treat incoming UDP
694 packets that were addressed to an L2 broadcast address as L3
695 broadcast packets. It is not expected that this will affect any
696 standards-conforming UDP application. The new behaviour can be
697 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
701 Remove the openbsd_poll system call.
702 __FreeBSD_version has been bumped because of this.
705 The stable/11 branch has been created from head@r302406.
708 The libc stub for the pipe(2) system call has been replaced with
709 a wrapper that calls the pipe2(2) system call and the pipe(2)
710 system call is now only implemented by the kernels that include
711 "options COMPAT_FREEBSD10" in their config file (this is the
712 default). Users should ensure that this option is enabled in
713 their kernel or upgrade userspace to r302092 before upgrading their
717 CAM will now strip leading spaces from SCSI disks' serial numbers.
718 This will affect users who create UFS filesystems on SCSI disks using
719 those disk's diskid device nodes. For example, if /etc/fstab
720 previously contained a line like
721 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
722 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
723 transforms like gmirror may also be affected. ZFS users should
727 The bitstring(3) API has been updated with new functionality and
728 improved performance. But it is binary-incompatible with the old API.
729 Objects built with the new headers may not be linked against objects
730 built with the old headers.
733 The brk and sbrk functions have been removed from libc on arm64.
734 Binutils from ports has been updated to not link to these
735 functions and should be updated to the latest version before
736 installing a new libc.
739 The armv6 port now defaults to hard float ABI. Limited support
740 for running both hardfloat and soft float on the same system
741 is available using the libraries installed with -DWITH_LIBSOFT.
742 This has only been tested as an upgrade path for installworld
743 and packages may fail or need manual intervention to run. New
744 packages will be needed.
746 To update an existing self-hosted armv6hf system, you must add
747 TARGET_ARCH=armv6 on the make command line for both the build
748 and the install steps.
751 Kernel modules compiled outside of a kernel build now default to
752 installing to /boot/modules instead of /boot/kernel. Many kernel
753 modules built this way (such as those in ports) already overrode
754 KMODDIR explicitly to install into /boot/modules. However,
755 manually building and installing a module from /sys/modules will
756 now install to /boot/modules instead of /boot/kernel.
759 The CAM I/O scheduler has been committed to the kernel. There should be
760 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
761 list of known rogues that claim support for this but actually corrupt
762 data is believed to be complete, be on the lookout for data
763 corruption. The known rogue list is believed to be complete:
765 o Crucial MX100, M550 drives with MU01 firmware.
766 o Micron M510 and M550 drives with MU01 firmware.
767 o Micron M500 prior to MU07 firmware
768 o Samsung 830, 840, and 850 all firmwares
769 o FCCT M500 all firmwares
771 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
772 with working NCQ TRIM. For Micron branded drives, see your sales rep for
773 updated firmware. Black listed drives will work correctly because these
774 drives work correctly so long as no NCQ TRIMs are sent to them. Given
775 this list is the same as found in Linux, it's believed there are no
776 other rogues in the market place. All other models from the above
779 To be safe, if you are at all concerned, you can quirk each of your
780 drives to prevent NCQ from being sent by setting:
781 kern.cam.ada.X.quirks="0x2"
782 in loader.conf. If the drive requires the 4k sector quirk, set the
786 The FAST_DEPEND build option has been removed and its functionality is
787 now the one true way. The old mkdep(1) style of 'make depend' has
788 been removed. See 20160311 for further details.
791 Resource range types have grown from unsigned long to uintmax_t. All
792 drivers, and anything using libdevinfo, need to be recompiled.
795 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
796 builds. It no longer runs mkdep(1) during 'make depend', and the
797 'make depend' stage can safely be skipped now as it is auto ran
798 when building 'make all' and will generate all SRCS and DPSRCS before
799 building anything else. Dependencies are gathered at compile time with
800 -MF flags kept in separate .depend files per object file. Users should
801 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
805 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
806 kernel modules. Therefore, if you load any kernel modules at boot time,
807 please install the boot loaders after you install the kernel, but before
811 make buildkernel KERNCONF=YOUR_KERNEL_HERE
812 make installkernel KERNCONF=YOUR_KERNEL_HERE
813 make -C sys/boot install
814 <reboot in single user>
816 Then follow the usual steps, described in the General Notes section,
820 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
821 see the 20141231 entry below for information about prerequisites and
822 upgrading, if you are not already using clang 3.5.0 or higher.
825 The AIO subsystem is now a standard part of the kernel. The
826 VFS_AIO kernel option and aio.ko kernel module have been removed.
827 Due to stability concerns, asynchronous I/O requests are only
828 permitted on sockets and raw disks by default. To enable
829 asynchronous I/O requests on all file types, set the
830 vfs.aio.enable_unsafe sysctl to a non-zero value.
833 The ELF object manipulation tool objcopy is now provided by the
834 ELF Tool Chain project rather than by GNU binutils. It should be a
835 drop-in replacement, with the addition of arm64 support. The
836 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
837 to obtain the GNU version if necessary.
840 Building ZFS pools on top of zvols is prohibited by default. That
841 feature has never worked safely; it's always been prone to deadlocks.
842 Using a zvol as the backing store for a VM guest's virtual disk will
843 still work, even if the guest is using ZFS. Legacy behavior can be
844 restored by setting vfs.zfs.vol.recursive=1.
847 The NONE and HPN patches has been removed from OpenSSH. They are
848 still available in the security/openssh-portable port.
851 With the addition of ypldap(8), a new _ypldap user is now required
852 during installworld. "mergemaster -p" can be used to add the user
853 prior to installworld, as documented in the handbook.
856 The tftp loader (pxeboot) now uses the option root-path directive. As a
857 consequence it no longer looks for a pxeboot.4th file on the tftp
858 server. Instead it uses the regular /boot infrastructure as with the
862 The code to start recording plug and play data into the modules has
863 been committed. While the old tools will properly build a new kernel,
864 a number of warnings about "unknown metadata record 4" will be produced
865 for an older kldxref. To avoid such warnings, make sure to rebuild
866 the kernel toolchain (or world). Make sure that you have r292078 or
867 later when trying to build 292077 or later before rebuilding.
870 Debug data files are now built by default with 'make buildworld' and
871 installed with 'make installworld'. This facilitates debugging but
872 requires more disk space both during the build and for the installed
873 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
877 r291527 changed the internal interface between the nfsd.ko and
878 nfscommon.ko modules. As such, they must both be upgraded to-gether.
879 __FreeBSD_version has been bumped because of this.
882 Add support for unicode collation strings leads to a change of
883 order of files listed by ls(1) for example. To get back to the old
884 behaviour, set LC_COLLATE environment variable to "C".
886 Databases administrators will need to reindex their databases given
887 collation results will be different.
889 Due to a bug in install(1) it is recommended to remove the ancient
890 locales before running make installworld.
892 rm -rf /usr/share/locale/*
895 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
896 libcrypto.so.7 or libssl.so.7 must be recompiled.
899 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
900 Kernel modules isp_2400_multi and isp_2500_multi were removed and
901 should be replaced with isp_2400 and isp_2500 modules respectively.
904 The build previously allowed using 'make -n' to not recurse into
905 sub-directories while showing what commands would be executed, and
906 'make -n -n' to recursively show commands. Now 'make -n' will recurse
907 and 'make -N' will not.
910 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
911 and etcupdate will now use this file. A custom sendmail.cf is now
912 updated via this mechanism rather than via installworld. If you had
913 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
914 want to remove the exclusion or change it to "always install".
915 /etc/mail/sendmail.cf is now managed the same way regardless of
916 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
917 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
920 Compatibility shims for legacy ATA device names have been removed.
921 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
922 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
923 environment variables, /dev/ad* and /dev/ar* symbolic links.
926 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
927 Please see the 20141231 entry below for information about prerequisites
928 and upgrading, if you are not already using clang 3.5.0 or higher.
931 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
932 and renamed from .symbols to .debug. This reduces the size requirements
933 on the boot partition or file system and provides consistency with
934 userland debug files.
936 When using the supported kernel installation method the
937 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
938 as is done with /boot/kernel.
940 Developers wishing to maintain the historical behavior of installing
941 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
944 The wireless drivers had undergone changes that remove the 'parent
945 interface' from the ifconfig -l output. The rc.d network scripts
946 used to check presence of a parent interface in the list, so old
947 scripts would fail to start wireless networking. Thus, etcupdate(3)
948 or mergemaster(8) run is required after kernel update, to update your
949 rc.d scripts in /etc.
952 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
953 These configurations are now automatically interpreted as
954 'scrub fragment reassemble'.
957 Kernel-loadable modules for the random(4) device are back. To use
958 them, the kernel must have
961 options RANDOM_LOADABLE
963 kldload(8) can then be used to load random_fortuna.ko
964 or random_yarrow.ko. Please note that due to the indirect
965 function calls that the loadable modules need to provide,
966 the build-in variants will be slightly more efficient.
968 The random(4) kernel option RANDOM_DUMMY has been retired due to
969 unpopularity. It was not all that useful anyway.
972 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
973 Control over building the ELF Tool Chain tools is now provided by
974 the WITHOUT_TOOLCHAIN knob.
977 The polarity of Pulse Per Second (PPS) capture events with the
978 uart(4) driver has been corrected. Prior to this change the PPS
979 "assert" event corresponded to the trailing edge of a positive PPS
980 pulse and the "clear" event was the leading edge of the next pulse.
982 As the width of a PPS pulse in a typical GPS receiver is on the
983 order of 1 millisecond, most users will not notice any significant
984 difference with this change.
986 Anyone who has compensated for the historical polarity reversal by
987 configuring a negative offset equal to the pulse width will need to
988 remove that workaround.
991 The default group assigned to /dev/dri entries has been changed
992 from 'wheel' to 'video' with the id of '44'. If you want to have
993 access to the dri devices please add yourself to the video group
996 # pw groupmod video -m $USER
999 The menu.rc and loader.rc files will now be replaced during
1000 upgrades. Please migrate local changes to menu.rc.local and
1001 loader.rc.local instead.
1004 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1005 strings and strip have been removed. The src.conf(5) knob
1006 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1009 As ZFS requires more kernel stack pages than is the default on some
1010 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1011 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1013 Please consider using 'options KSTACK_PAGES=X' where X is greater
1014 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1017 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1018 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1019 default, i.e., they will not contain "::". For example, instead
1020 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1021 to have a more specific match, such as different map entries for
1022 IPv6:0:0 vs IPv6:0. This change requires that configuration
1023 data (including maps, files, classes, custom ruleset, etc.) must
1024 use the same format, so make certain such configuration data is
1025 upgrading. As a very simple check search for patterns like
1026 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1027 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1028 the cf option UseCompressedIPv6Addresses.
1031 The default kernel entropy-processing algorithm is now
1032 Fortuna, replacing Yarrow.
1034 Assuming you have 'device random' in your kernel config
1035 file, the configurations allow a kernel option to override
1036 this default. You may choose *ONE* of:
1038 options RANDOM_YARROW # Legacy /dev/random algorithm.
1039 options RANDOM_DUMMY # Blocking-only driver.
1041 If you have neither, you get Fortuna. For most people,
1042 read no further, Fortuna will give a /dev/random that works
1043 like it always used to, and the difference will be irrelevant.
1045 If you remove 'device random', you get *NO* kernel-processed
1046 entropy at all. This may be acceptable to folks building
1047 embedded systems, but has complications. Carry on reading,
1048 and it is assumed you know what you need.
1050 *PLEASE* read random(4) and random(9) if you are in the
1051 habit of tweaking kernel configs, and/or if you are a member
1052 of the embedded community, wanting specific and not-usual
1053 behaviour from your security subsystems.
1055 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1056 random', you will NOT have a functioning /dev/random, and
1057 many cryptographic features will not work, including SSH.
1058 You may also find strange behaviour from the random(3) set
1059 of library functions, in particular sranddev(3), srandomdev(3)
1060 and arc4random(3). The reason for this is that the KERN_ARND
1061 sysctl only returns entropy if it thinks it has some to
1062 share, and with RANDOM_DUMMY or no 'device random' this
1066 An additional fix for the issue described in the 20150614 sendmail
1067 entry below has been committed in revision 284717.
1070 FreeBSD's old make (fmake) has been removed from the system. It is
1071 available as the devel/fmake port or via pkg install fmake.
1074 The fix for the issue described in the 20150614 sendmail entry
1075 below has been committed in revision 284436. The work
1076 around described in that entry is no longer needed unless the
1077 default setting is overridden by a confDH_PARAMETERS configuration
1078 setting of '5' or pointing to a 512 bit DH parameter file.
1081 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1082 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1083 and devel/kyua to version 0.20+ and adjust any calling code to work
1084 with Kyuafile and kyua.
1087 The import of openssl to address the FreeBSD-SA-15:10.openssl
1088 security advisory includes a change which rejects handshakes
1089 with DH parameters below 768 bits. sendmail releases prior
1090 to 8.15.2 (not yet released), defaulted to a 512 bit
1091 DH parameter setting for client connections. To work around
1092 this interoperability, sendmail can be configured to use a
1093 2048 bit DH parameter by:
1095 1. Edit /etc/mail/`hostname`.mc
1096 2. If a setting for confDH_PARAMETERS does not exist or
1097 exists and is set to a string beginning with '5',
1098 replace it with '2'.
1099 3. If a setting for confDH_PARAMETERS exists and is set to
1100 a file path, create a new file with:
1101 openssl dhparam -out /path/to/file 2048
1102 4. Rebuild the .cf file:
1103 cd /etc/mail/; make; make install
1104 5. Restart sendmail:
1105 cd /etc/mail/; make restart
1107 A sendmail patch is coming, at which time this file will be
1111 Generation of legacy formatted entries have been disabled by default
1112 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1113 entries were converted to use the new format by default when the new,
1114 machine independent format have been added and supported since FreeBSD
1117 Please see the pwd_mkdb(8) manual page for further details.
1120 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1121 20141231 entry below for information about prerequisites and upgrading,
1122 if you are not already using 3.5.0 or higher.
1125 TI platform code switched to using vendor DTS files and this update
1126 may break existing systems running on Beaglebone, Beaglebone Black,
1129 - dtb files should be regenerated/reinstalled. Filenames are the
1130 same but content is different now
1131 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1132 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1133 addressing scheme is now pin 25 on /dev/gpioc3.
1134 - Pandaboard: /etc/ttys should be updated, serial console device is
1135 now /dev/ttyu2, not /dev/ttyu0
1138 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1139 If you need the GNU extension from groff soelim(1), install groff
1140 from package: pkg install groff, or via ports: textproc/groff.
1143 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1144 defined in symlink(7); previously symlinks were silently ignored.
1147 The const qualifier has been removed from iconv(3) to comply with
1148 POSIX. The ports tree is aware of this from r384038 onwards.
1151 Libraries specified by LIBADD in Makefiles must have a corresponding
1152 DPADD_<lib> variable to ensure correct dependencies. This is now
1153 enforced in src.libnames.mk.
1156 From legacy ata(4) driver was removed support for SATA controllers
1157 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1158 Kernel modules ataahci and ataadaptec were removed completely,
1159 replaced by ahci and mvs modules respectively.
1162 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1163 the 20141231 entry below for information about prerequisites and
1164 upgrading, if you are not already using 3.5.0 or higher.
1167 The 32-bit PowerPC kernel has been changed to a position-independent
1168 executable. This can only be booted with a version of loader(8)
1169 newer than January 31, 2015, so make sure to update both world and
1170 kernel before rebooting.
1173 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1174 but before r278950, the RNG was not seeded properly. Immediately
1175 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1176 ssh keys or openssl keys) that were generated w/ a kernel from that
1177 range. This does not affect programs that directly used /dev/random
1178 or /dev/urandom. All userland uses of arc4random(3) are affected.
1181 The autofs(4) ABI was changed in order to restore binary compatibility
1182 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1183 with the new kernel.
1186 The powerpc64 kernel has been changed to a position-independent
1187 executable. This can only be booted with a new version of loader(8),
1188 so make sure to update both world and kernel before rebooting.
1191 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1192 only release, no new features have been added. Please see the 20141231
1193 entry below for information about prerequisites and upgrading, if you
1194 are not already using 3.5.0.
1197 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1198 taken from the ELF Tool Chain project rather than GNU binutils. They
1199 should be drop-in replacements, with the addition of arm64 support.
1200 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1201 binutils tools, if necessary. See 20150805 for updated information.
1204 The default Unbound configuration now enables remote control
1205 using a local socket. Users who have already enabled the
1206 local_unbound service should regenerate their configuration
1207 by running "service local_unbound setup" as root.
1210 The GNU texinfo and GNU info pages have been removed.
1211 To be able to view GNU info pages please install texinfo from ports.
1214 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1216 As of this release, a prerequisite for building clang, llvm and lldb is
1217 a C++11 capable compiler and C++11 standard library. This means that to
1218 be able to successfully build the cross-tools stage of buildworld, with
1219 clang as the bootstrap compiler, your system compiler or cross compiler
1220 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1221 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1224 On any standard FreeBSD 10.x or 11.x installation, where clang and
1225 libc++ are on by default (that is, on x86 or arm), this should work out
1228 On 9.x installations where clang is enabled by default, e.g. on x86 and
1229 powerpc, libc++ will not be enabled by default, so libc++ should be
1230 built (with clang) and installed first. If both clang and libc++ are
1231 missing, build clang first, then use it to build libc++.
1233 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1234 the instructions for 9.x above.
1236 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1237 default, and do not build clang.
1239 Many embedded systems are resource constrained, and will not be able to
1240 build clang in a reasonable time, or in some cases at all. In those
1241 cases, cross building bootable systems on amd64 is a workaround.
1243 This new version of clang introduces a number of new warnings, of which
1244 the following are most likely to appear:
1248 This warns in two cases, for both C and C++:
1249 * When the code is trying to take the absolute value of an unsigned
1250 quantity, which is effectively a no-op, and almost never what was
1251 intended. The code should be fixed, if at all possible. If you are
1252 sure that the unsigned quantity can be safely cast to signed, without
1253 loss of information or undefined behavior, you can add an explicit
1254 cast, or disable the warning.
1256 * When the code is trying to take an absolute value, but the called
1257 abs() variant is for the wrong type, which can lead to truncation.
1258 If you want to disable the warning instead of fixing the code, please
1259 make sure that truncation will not occur, or it might lead to unwanted
1262 -Wtautological-undefined-compare and
1263 -Wundefined-bool-conversion
1265 These warn when C++ code is trying to compare 'this' against NULL, while
1266 'this' should never be NULL in well-defined C++ code. However, there is
1267 some legacy (pre C++11) code out there, which actively abuses this
1268 feature, which was less strictly defined in previous C++ versions.
1270 Squid and openjdk do this, for example. The warning can be turned off
1271 for C++98 and earlier, but compiling the code in C++11 mode might result
1272 in unexpected behavior; for example, the parts of the program that are
1273 unreachable could be optimized away.
1276 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1277 kernel sources have been removed. The .h files remain, since some
1278 utilities include them. This will need to be fixed later.
1279 If "mount -t oldnfs ..." is attempted, it will fail.
1280 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1281 the utilities will report errors.
1284 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1285 directories to top level SUBDIR variable when their parent
1286 directory is included in LOCAL_DIRS. Users with build systems with
1287 such hierarchies and without SUBDIR entries in the parent
1288 directory Makefiles should add them or add the directories to
1292 faith(4) and faithd(8) have been removed from the base system. Faith
1293 has been obsolete for a very long time.
1296 vt(4), the new console driver, is enabled by default. It brings
1297 support for Unicode and double-width characters, as well as
1298 support for UEFI and integration with the KMS kernel video
1301 You may need to update your console settings in /etc/rc.conf,
1302 most probably the keymap. During boot, /etc/rc.d/syscons will
1303 indicate what you need to do.
1305 vt(4) still has issues and lacks some features compared to
1306 syscons(4). See the wiki for up-to-date information:
1307 https://wiki.freebsd.org/Newcons
1309 If you want to keep using syscons(4), you can do so by adding
1310 the following line to /boot/loader.conf:
1314 pjdfstest has been integrated into kyua as an opt-in test suite.
1315 Please see share/doc/pjdfstest/README for more details on how to
1319 gperf has been removed from the base system for architectures
1320 that use clang. Ports that require gperf will obtain it from the
1324 pjdfstest has been moved from tools/regression/pjdfstest to
1328 At svn r271982, The default linux compat kernel ABI has been adjusted
1329 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1330 update. If you wish to continue using the linux-f10 compat ports,
1331 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1332 encouraged to update their linux-compat packages to linux-c6 during
1333 their next update cycle.
1336 The ofwfb driver, used to provide a graphics console on PowerPC when
1337 using vt(4), no longer allows mmap() of all physical memory. This
1338 will prevent Xorg on PowerPC with some ATI graphics cards from
1339 initializing properly unless x11-servers/xorg-server is updated to
1343 The xdev targets have been converted to using TARGET and
1344 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1347 The default unbound configuration has been modified to address
1348 issues with reverse lookups on networks that use private
1349 address ranges. If you use the local_unbound service, run
1350 "service local_unbound setup" as root to regenerate your
1351 configuration, then "service local_unbound reload" to load the
1355 The GNU texinfo and GNU info pages are not built and installed
1356 anymore, WITH_INFO knob has been added to allow to built and install
1358 UPDATE: see 20150102 entry on texinfo's removal
1361 The GNU readline library is now an INTERNALLIB - that is, it is
1362 statically linked into consumers (GDB and variants) in the base
1363 system, and the shared library is no longer installed. The
1364 devel/readline port is available for third party software that
1368 The Itanium architecture (ia64) has been removed from the list of
1369 known architectures. This is the first step in the removal of the
1373 Commit r268115 has added NFSv4.1 server support, merged from
1374 projects/nfsv4.1-server. Since this includes changes to the
1375 internal interfaces between the NFS related modules, a full
1376 build of the kernel and modules will be necessary.
1377 __FreeBSD_version has been bumped.
1380 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1381 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1382 which differs from the behaviour controlled by this knob.)
1385 Maximal length of the serial number in CTL was increased from 16 to
1386 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1387 and ctld, need to be rebuilt to work with a new kernel.
1390 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1391 1 respectively to match the upstream numbers. They were out of
1392 sync because, when they were originally added to FreeBSD, the
1393 upstream versions were not respected. These libraries are private
1394 and not yet built by default, so renumbering them should be a
1395 non-issue. However, unclean source trees will yield broken test
1396 programs once the operator executes "make delete-old-libs" after a
1397 "make installworld".
1399 Additionally, the atf-sh binary was made private by moving it into
1400 /usr/libexec/. Already-built shell test programs will keep the
1401 path to the old binary so they will break after "make delete-old"
1404 If you are using WITH_TESTS=yes (not the default), wipe the object
1405 tree and rebuild from scratch to prevent spurious test failures.
1406 This is only needed once: the misnumbered libraries and misplaced
1407 binaries have been added to OptionalObsoleteFiles.inc so they will
1408 be removed during a clean upgrade.
1411 Clang and llvm have been upgraded to 3.4.1 release.
1414 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1415 be removed to avoid issues in the future (and has been added to
1419 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1420 past, it affected all builds that used the bsd.*.mk files. The old
1421 behavior was a bug, but people may have relied upon it. To get this
1422 behavior back, you can .include /etc/src.conf from /etc/make.conf
1423 (which is still global and isn't changed). This also changes the
1424 behavior of incremental builds inside the tree of individual
1425 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1426 Although this has survived make universe and some upgrade scenarios,
1427 other upgrade scenarios may have broken. At least one form of
1428 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1429 as well... In cases where MAKESYSPATH isn't working with this
1430 setting, you'll need to set it to the full path to your tree.
1432 One side effect of all this cleaning up is that bsd.compiler.mk
1433 is no longer implicitly included by bsd.own.mk. If you wish to
1434 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1438 The lindev device has been removed since /dev/full has been made a
1439 standard device. __FreeBSD_version has been bumped.
1442 The knob WITHOUT_VI was added to the base system, which controls
1443 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1444 in order to reorder files share/termcap and didn't build ex(1) as a
1445 build tool, so building/installing with WITH_VI is highly advised for
1446 build hosts for older releases.
1448 This issue has been fixed in stable/9 and stable/10 in r277022 and
1449 r276991, respectively.
1452 The YES_HESIOD knob has been removed. It has been obsolete for
1453 a decade. Please move to using WITH_HESIOD instead or your builds
1454 will silently lack HESIOD.
1457 The uart(4) driver has been changed with respect to its handling
1458 of the low-level console. Previously the uart(4) driver prevented
1459 any process from changing the baudrate or the CLOCAL and HUPCL
1460 control flags. By removing the restrictions, operators can make
1461 changes to the serial console port without having to reboot.
1462 However, when getty(8) is started on the serial device that is
1463 associated with the low-level console, a misconfigured terminal
1464 line in /etc/ttys will now have a real impact.
1465 Before upgrading the kernel, make sure that /etc/ttys has the
1466 serial console device configured as 3wire without baudrate to
1467 preserve the previous behaviour. E.g:
1468 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1471 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1472 to improve performance. To re-enable it, if needed, run rpcbind
1473 with command line option -W.
1476 Switched back to the GPL dtc compiler due to updates in the upstream
1477 dts files not being supported by the BSDL dtc compiler. You will need
1478 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1479 may result while building dtb files during a kernel build if you fail
1480 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1483 Clang and llvm have been upgraded to 3.4 release.
1486 The nve(4) driver has been removed. Please use the nfe(4) driver
1487 for NVIDIA nForce MCP Ethernet adapters instead.
1490 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1491 This could cause certain C++ applications using shared libraries built
1492 against the previous version of libc++ to crash. The incompatibility
1493 has now been fixed, but any C++ applications or shared libraries built
1494 between r261283 and r261801 should be recompiled.
1497 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1498 capability mode support. Please note that enabling the feature in
1499 kernel is still highly recommended.
1502 OpenSSH is now built with sandbox support, and will use sandbox as
1503 the default privilege separation method. This requires Capsicum
1504 capability mode support in kernel.
1507 The libelf and libdwarf libraries have been updated to newer
1508 versions from upstream. Shared library version numbers for
1509 these two libraries were bumped. Any ports or binaries
1510 requiring these two libraries should be recompiled.
1511 __FreeBSD_version is bumped to 1100006.
1514 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1515 instead of providing an explicit one, this would prevent such
1516 Makefile from providing its own Kyuafile in the future during
1517 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1518 intervention is needed to clean an objdir if you use NO_CLEAN:
1519 # find /usr/obj -name Kyuafile | xargs rm -f
1522 The behavior of gss_pseudo_random() for the krb5 mechanism
1523 has changed, for applications requesting a longer random string
1524 than produced by the underlying enctype's pseudo-random() function.
1525 In particular, the random string produced from a session key of
1526 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1527 be different at the 17th octet and later, after this change.
1528 The counter used in the PRF+ construction is now encoded as a
1529 big-endian integer in accordance with RFC 4402.
1530 __FreeBSD_version is bumped to 1100004.
1533 The WITHOUT_ATF build knob has been removed and its functionality
1534 has been subsumed into the more generic WITHOUT_TESTS. If you were
1535 using the former to disable the build of the ATF libraries, you
1536 should change your settings to use the latter.
1539 The default version of mtree is nmtree which is obtained from
1540 NetBSD. The output is generally the same, but may vary
1541 slightly. If you found you need identical output adding
1542 "-F freebsd9" to the command line should do the trick. For the
1543 time being, the old mtree is available as fmtree.
1546 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1547 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1548 1.1.4_8 and verify bsdyml not linked in, before running "make
1550 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1552 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1555 The stable/10 branch has been created in subversion from head
1562 Avoid using make -j when upgrading. While generally safe, there are
1563 sometimes problems using -j to upgrade. If your upgrade fails with
1564 -j, please try again without -j. From time to time in the past there
1565 have been problems using -j with buildworld and/or installworld. This
1566 is especially true when upgrading between "distant" versions (eg one
1567 that cross a major release boundary or several minor releases, or when
1568 several months have passed on the -current branch).
1570 Sometimes, obscure build problems are the result of environment
1571 poisoning. This can happen because the make utility reads its
1572 environment when searching for values for global variables. To run
1573 your build attempts in an "environmental clean room", prefix all make
1574 commands with 'env -i '. See the env(1) manual page for more details.
1576 When upgrading from one major version to another it is generally best to
1577 upgrade to the latest code in the currently installed branch first, then
1578 do an upgrade to the new branch. This is the best-tested upgrade path,
1579 and has the highest probability of being successful. Please try this
1580 approach if you encounter problems with a major version upgrade. Since
1581 the stable 4.x branch point, one has generally been able to upgrade from
1582 anywhere in the most recent stable branch to head / current (or even the
1583 last couple of stable branches). See the top of this file when there's
1586 When upgrading a live system, having a root shell around before
1587 installing anything can help undo problems. Not having a root shell
1588 around can lead to problems if pam has changed too much from your
1589 starting point to allow continued authentication after the upgrade.
1591 This file should be read as a log of events. When a later event changes
1592 information of a prior event, the prior event should not be deleted.
1593 Instead, a pointer to the entry with the new information should be
1594 placed in the old entry. Readers of this file should also sanity check
1595 older entries before relying on them blindly. Authors of new entries
1596 should write them with this in mind.
1600 When upgrading the boot ZFS pool to a new version, always follow
1603 1.) recompile and reinstall the ZFS boot loader and boot block
1604 (this is part of "make buildworld" and "make installworld")
1606 2.) update the ZFS boot block on your boot drive
1608 The following example updates the ZFS boot block on the first
1609 partition (freebsd-boot) of a GPT partitioned drive ada0:
1610 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1612 Non-boot pools do not need these updates.
1616 If you are updating from a prior version of FreeBSD (even one just
1617 a few days old), you should follow this procedure. It is the most
1618 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1620 make kernel-toolchain
1621 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1622 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1624 To test a kernel once
1625 ---------------------
1626 If you just want to boot a kernel once (because you are not sure
1627 if it works, or if you want to boot a known bad kernel to provide
1628 debugging information) run
1629 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1630 nextboot -k testkernel
1632 To rebuild everything and install it on the current system.
1633 -----------------------------------------------------------
1634 # Note: sometimes if you are running current you gotta do more than
1635 # is listed here if you are upgrading from a really old current.
1637 <make sure you have good level 0 dumps>
1639 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1640 make installkernel KERNCONF=YOUR_KERNEL_HERE
1642 <reboot in single user> [3]
1649 To cross-install current onto a separate partition
1650 --------------------------------------------------
1651 # In this approach we use a separate partition to hold
1652 # current's root, 'usr', and 'var' directories. A partition
1653 # holding "/", "/usr" and "/var" should be about 2GB in
1656 <make sure you have good level 0 dumps>
1659 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1660 <maybe newfs current's root partition>
1661 <mount current's root partition on directory ${CURRENT_ROOT}>
1662 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1663 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1664 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1665 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1666 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1667 <reboot into current>
1668 <do a "native" rebuild/install as described in the previous section>
1669 <maybe install compatibility libraries from ports/misc/compat*>
1673 To upgrade in-place from stable to current
1674 ----------------------------------------------
1675 <make sure you have good level 0 dumps>
1677 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1678 make installkernel KERNCONF=YOUR_KERNEL_HERE
1680 <reboot in single user> [3]
1687 Make sure that you've read the UPDATING file to understand the
1688 tweaks to various things you need. At this point in the life
1689 cycle of current, things change often and you are on your own
1690 to cope. The defaults can also change, so please read ALL of
1691 the UPDATING entries.
1693 Also, if you are tracking -current, you must be subscribed to
1694 freebsd-current@freebsd.org. Make sure that before you update
1695 your sources that you have read and understood all the recent
1696 messages there. If in doubt, please track -stable which has
1697 much fewer pitfalls.
1699 [1] If you have third party modules, such as vmware, you
1700 should disable them at this point so they don't crash your
1703 [3] From the bootblocks, boot -s, and then do
1708 adjkerntz -i # if CMOS is wall time
1709 Also, when doing a major release upgrade, it is required that
1710 you boot into single user mode to do the installworld.
1712 [4] Note: This step is non-optional. Failure to do this step
1713 can result in a significant reduction in the functionality of the
1714 system. Attempting to do it by hand is not recommended and those
1715 that pursue this avenue should read this file carefully, as well
1716 as the archives of freebsd-current and freebsd-hackers mailing lists
1717 for potential gotchas. The -U option is also useful to consider.
1718 See mergemaster(8) for more information.
1720 [5] Usually this step is a no-op. However, from time to time
1721 you may need to do this if you get unknown user in the following
1722 step. It never hurts to do it all the time. You may need to
1723 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1724 install) after the buildworld before this step if you last updated
1725 from current before 20130425 or from -stable before 20130430.
1727 [6] This only deletes old files and directories. Old libraries
1728 can be deleted by "make delete-old-libs", but you have to make
1729 sure that no program is using those libraries anymore.
1731 [8] In order to have a kernel that can run the 4.x binaries needed to
1732 do an installworld, you must include the COMPAT_FREEBSD4 option in
1733 your kernel. Failure to do so may leave you with a system that is
1734 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1735 required to run the 5.x binaries on more recent kernels. And so on
1736 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1738 Make sure that you merge any new devices from GENERIC since the
1739 last time you updated your kernel config file.
1741 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1742 "?=" instead of the "=" assignment operator, so that buildworld can
1743 override the CPUTYPE if it needs to.
1745 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1746 not on the command line, or in /etc/make.conf. buildworld will
1747 warn if it is improperly defined.
1750 This file contains a list, in reverse chronological order, of major
1751 breakages in tracking -current. It is not guaranteed to be a complete
1752 list of such breakages, and only contains entries since September 23, 2011.
1753 If you need to see UPDATING entries from before that date, you will need
1754 to fetch an UPDATING file from an older FreeBSD release.
1756 Copyright information:
1758 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1760 Redistribution, publication, translation and use, with or without
1761 modification, in full or in part, in any form or format of this
1762 document are permitted without further permission from the author.
1764 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1765 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1766 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1767 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1768 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1769 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1770 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1771 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1772 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1773 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1774 POSSIBILITY OF SUCH DAMAGE.
1776 Contact Warner Losh if you have any questions about your use of