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