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