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