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".)
36 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
37 6.0.1. Please see the 20141231 entry below for information about
38 prerequisites and upgrading, if you are not already using clang 3.5.0
42 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
43 needed to be changed to work with it. This change was made with r335763
44 and requires a mergemaster / etcupdate / etc to update the installed file.
47 r334930 changed the interface between the NFS modules, so they all
48 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
51 The kernel / userland interface for devinfo changed, so you'll
52 need a new kernel and userland as a pair for it to work (rebuilding
53 lib/libdevinfo is all that's required). devinfo and devmatch will
54 not work, but everything else will when there's a mismatch.
57 The on-disk format for hwpmc callchain records has changed to include
58 threadid corresponding to a given record. This changes the field offsets
59 and thus requires that libpmcstat be rebuilt before using a kernel
63 The vxge(4) driver has been removed. This driver was introduced into
64 HEAD one week before the Exar left the Ethernet market and is not
65 known to be used. If you have device vxge in your kernel config file
69 The amd64 kernel now requires a ld that supports ifunc to produce a
70 working kernel, either lld or a newer binutils. lld is built by default
71 on amd64, and the 'buildkernel' target uses it automatically. However,
72 it is not the default linker, so building the kernel the traditional
73 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
74 binutils port/package). lld will soon be default, and this requirement
78 The nxge(4) driver has been removed. This driver was for PCI-X 10g
79 cards made by s2io/Neterion. The company was aquired by Exar and
80 no longer sells or supports Ethernet products. If you have device
81 nxge in your kernel config file it must be removed.
84 The tz database (tzdb) has been updated to 2018e. This version more
85 correctly models time stamps in time zones with negative DST such as
86 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
87 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
88 time zone abbreviations and the tm_isdst flag.
91 The ixgb(4) driver has been removed. This driver was for an early and
92 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
93 quickly shifted to the long lived ixgbe family. If you have device
94 ixgb in your kernel config file it must be removed.
97 The lmc(4) driver has been removed. This was a WAN interface
98 card that was already reportedly rare in 2003, and had an ambiguous
99 license. If you have device lmc in your kernel config file it must
103 Support for Arcnet networks has been removed. If you have device
104 arcnet or device cm in your kernel config file they must be
108 Support for FDDI networks has been removed. If you have device
109 fddi or device fpa in your kernel config file they must be
113 In addition to supporting RFC 3164 formatted messages, the
114 syslogd(8) service is now capable of parsing RFC 5424 formatted
115 log messages. The main benefit of using RFC 5424 is that clients
116 may now send log messages with timestamps containing year numbers,
117 microseconds and time zone offsets.
119 Similarly, the syslog(3) C library function has been altered to
120 send RFC 5424 formatted messages to the local system logging
121 daemon. On systems using syslogd(8), this change should have no
122 negative impact, as long as syslogd(8) and the C library are
123 updated at the same time. On systems using a different system
124 logging daemon, it may be necessary to make configuration
125 adjustments, depending on the software used.
127 When using syslog-ng, add the 'syslog-protocol' flag to local
128 input sources to enable parsing of RFC 5424 formatted messages:
131 unix-dgram("/var/run/log" flags(syslog-protocol));
134 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
135 of the 'imuxsock' module to let messages be processed by the
136 regular RFC 3164/5424 parsing pipeline:
138 module(load="imuxsock" SysSock.UseSpecialParser="off")
140 Do note that these changes only affect communication between local
141 applications and syslogd(8). The format that syslogd(8) uses to
142 store messages on disk or forward messages to other systems
143 remains unchanged. syslogd(8) still uses RFC 3164 for these
144 purposes. Options to customize this behaviour will be added in the
145 future. Utilities that process log files stored in /var/log are
146 thus expected to continue to function as before.
148 __FreeBSD_version has been incremented to 1200061 to denote this
152 Support for token ring networks has been removed. If you
153 have "device token" in your kernel config you should remove
154 it. No device drivers supported token ring.
157 makefs was modified to be able to tag ISO9660 El Torito boot catalog
158 entries as EFI instead of overloading the i386 tag as done previously.
159 The amd64 mkisoimages.sh script used to build amd64 ISO images for
160 release was updated to use this. This may mean that makefs must be
161 updated before "make cdrom" can be run in the release directory. This
162 should be as simple as:
164 $ cd $SRCDIR/usr.sbin/makefs
165 $ make depend all install
168 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
169 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
170 Co-existance for the transition period will come shortly. Booting is a
171 complex environment and test coverage for Lua-enabled loaders has been
172 thin, so it would be prudent to assume it might not work and make
173 provisions for backup boot methods.
176 devmatch functionality has been turned on in devd. It will automatically
177 load drivers for unattached devices. This may cause unexpected drivers to
178 be loaded. Please report any problems to current@ and imp@freebsd.org.
181 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
182 6.0.0. Please see the 20141231 entry below for information about
183 prerequisites and upgrading, if you are not already using clang 3.5.0
187 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
188 This means it is used to link the kernel and userland libraries and
189 executables, but is not yet installed as /usr/bin/ld by default.
191 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
192 WITHOUT_LLD_BOOTSTRAP=yes
195 On i386, pmtimer has been removed. Its functionality has been folded
196 into apm. It was a no-op on ACPI in current for a while now (but was still
197 needed on i386 in FreeBSD 11 and earlier). Users may need to remove it
198 from kernel config files.
201 The use of RSS hash from the network card aka flowid has been
202 disabled by default for lagg(4) as it's currently incompatible with
203 the lacp and loadbalance protocols.
205 This can be re-enabled by setting the following in loader.conf:
206 net.link.lagg.default_use_flowid="1"
209 The SW_WATCHDOG option is no longer necessary to enable the
210 hardclock-based software watchdog if no hardware watchdog is
211 configured. As before, SW_WATCHDOG will cause the software
212 watchdog to be enabled even if a hardware watchdog is configured.
215 r326887 fixes the issue described in the 20171214 UPDATING entry.
216 r326888 flips the switch back to building GELI support always.
219 r362593 broke ZFS + GELI support for reasons unknown. However,
220 it also broke ZFS support generally, so GELI has been turned off
221 by default as the lesser evil in r326857. If you boot off ZFS and/or
222 GELI, it might not be a good time to update.
225 PowerPC users must update loader(8) by rebuilding world before
226 installing a new kernel, as the protocol connecting them has
227 changed. Without the update, loader metadata will not be passed
228 successfully to the kernel and users will have to enter their
229 root partition at the kernel mountroot prompt to continue booting.
230 Newer versions of loader can boot old kernels without issue.
233 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
234 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
235 to WITH/OUT_LOADER_GELI.
238 The naive and non-compliant support of posix_fallocate(2) in ZFS
239 has been removed as of r325320. The system call now returns EINVAL
240 when used on a ZFS file. Although the new behavior complies with the
241 standard, some consumers are not prepared to cope with it.
242 One known victim is lld prior to r325420.
245 Building in a FreeBSD src checkout will automatically create object
246 directories now rather than store files in the current directory if
247 'make obj' was not ran. Calling 'make obj' is no longer necessary.
248 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
249 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
253 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
254 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
255 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
256 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
257 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
258 The UNIFIED_OBJDIR option is a transitional feature that will be
259 removed for 12.0 release; please migrate to the new format for any
260 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
261 than hardcoding paths.
264 The native-xtools target no longer installs the files by default to the
265 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
266 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
269 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
270 options are changing from controlling the build if defined / undefined
271 to controlling the build with explicit 'yes' or 'no' values. They will
272 shift to WITH/WITHOUT options to match other options in the system.
275 libstand has turned into a private library for sys/boot use only.
276 It is no longer supported as a public interface outside of sys/boot.
279 The arm port has split armv6 into armv6 and armv7. armv7 is now
280 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
281 and are running a kernel from before r324363, you will need to add
282 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
285 When building multiple kernels using KERNCONF, non-existent KERNCONF
286 files will produce an error and buildkernel will fail. Previously
287 missing KERNCONF files silently failed giving no indication as to
288 why, only to subsequently discover during installkernel that the
289 desired kernel was never built in the first place.
292 The default serial number format for CTL LUNs has changed. This will
293 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
294 or iSCSI clients care about their LUNs' serial numbers. Users who
295 require serial number stability should hardcode serial numbers in
299 For 32-bit arm compiled for hard-float support, soft-floating point
300 binaries now always get their shared libraries from
301 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
302 /usr/libsoft also existed). Only users with a hard-float ld.so, but
303 soft-float everything else should be affected.
306 The geli password typed at boot is now hidden. To restore the previous
307 behavior, see geli(8) for configuration options.
310 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
311 sysctl values. Minor nit, but requires a rebuild of both world/kernel
315 "make check" behavior (made in ^/head@r295380) has been changed to
316 execute from a limited sandbox, as opposed to executing from
320 - The "beforecheck" and "aftercheck" targets are now specified.
321 - ${CHECKDIR} (added in commit noted above) has been removed.
322 - Legacy behavior can be enabled by setting
323 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
325 If the limited sandbox mode is enabled, "make check" will execute
326 "make distribution", then install, execute the tests, and clean up the
327 sandbox if successful.
329 The "make distribution" and "make install" targets are typically run as
330 root to set appropriate permissions and ownership at installation time.
331 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
332 environment if executing "make check" with limited sandbox mode using
333 an unprivileged user.
336 Since the switch to GPT disk labels, fsck for UFS/FFS has been
337 unable to automatically find alternate superblocks. As of r322297,
338 the information needed to find alternate superblocks has been
339 moved to the end of the area reserved for the boot block.
340 Filesystems created with a newfs of this vintage or later
341 will create the recovery information. If you have a filesystem
342 created prior to this change and wish to have a recovery block
343 created for your filesystem, you can do so by running fsck in
344 foreground mode (i.e., do not use the -p or -y options). As it
345 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
346 to which you should answer yes.
349 As of r321665, an NFSv4 server configuration that services
350 Kerberos mounts or clients that do not support the uid/gid in
351 owner/owner_group string capability, must explicitly enable
352 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
353 machine's /etc/rc.conf file.
356 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
357 Please see the 20141231 entry below for information about prerequisites
358 and upgrading, if you are not already using clang 3.5.0 or higher.
361 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
362 r-commands (rlogin, rsh, etc.) to be built with the base system.
365 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
366 a very major ABI incompatible change, so users of FreeBSD/powerpc must
367 be careful when performing source upgrades. It is best to run
368 'make installworld' from an alternate root system, either a live
369 CD/memory stick, or a temporary root partition. Additionally, all ports
370 must be recompiled. powerpc64 is largely unaffected, except in the case
371 of 32-bit compatibility. All 32-bit binaries will be affected.
374 Forward compatibility for the "ino64" project have been committed. This
375 will allow most new binaries to run on older kernels in a limited
376 fashion. This prevents many of the common foot-shooting actions in the
377 upgrade as well as the limited ability to roll back the kernel across
378 the ino64 upgrade. Complicated use cases may not work properly, though
379 enough simpler ones work to allow recovery in most situations.
382 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
383 if you require the GPL compiler.
386 The internal ABI used for communication between the NFS kernel modules
387 was changed by r320085, so __FreeBSD_version was bumped to
388 ensure all the NFS related modules are updated together.
391 The ABI of struct event was changed by extending the data
392 member to 64bit and adding ext fields. For upgrade, same
393 precautions as for the entry 20170523 "ino64" must be
397 The GNU roff toolchain has been removed from base. To render manpages
398 which are not supported by mandoc(1), man(1) can fallback on GNU roff
399 from ports (and recommends to install it).
400 To render roff(7) documents, consider using GNU roff from ports or the
401 heirloom doctools roff toolchain from ports via pkg install groff or
402 via pkg install heirloom-doctools.
405 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
406 smaller runtime footprint builds. This is useful for embedded systems
407 which only require one chipset support.
409 If you load it as a module, make sure this is in /boot/loader.conf:
413 This will load the HAL, all chip/RF backends and if_ath_pci.
414 If you have if_ath_pci in /boot/loader.conf, ensure it is after
415 if_ath or it will not load any HAL chipset support.
417 If you want to selectively load things (eg on ye cheape ARM/MIPS
418 platforms where RAM is at a premium) you should:
421 * load the chip modules in question
422 * load ath_rate, ath_dfs
424 * load if_ath_pci and/or if_ath_ahb depending upon your particular
425 bus bind type - this is where probe/attach is done.
427 For further comments/feedback, poke adrian@ .
430 The "ino64" 64-bit inode project has been committed, which extends
431 a number of types to 64 bits. Upgrading in place requires care and
432 adherence to the documented upgrade procedure.
434 If using a custom kernel configuration ensure that the
435 COMPAT_FREEBSD11 option is included (as during the upgrade the
436 system will be running the ino64 kernel with the existing world).
438 For the safest in-place upgrade begin by removing previous build
439 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
440 full procedure documented below under the heading "To rebuild
441 everything and install it on the current system." Specifically,
442 a reboot is required after installing the new kernel before
446 The NATM framework including the en(4), fatm(4), hatm(4), and
447 patm(4) devices has been removed. Consumers should plan a
448 migration before the end-of-life date for FreeBSD 11.
451 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
452 diff has not been implemented, if those are needed a newer version of
453 GNU diff is available via the diffutils package under the gdiff name.
456 As of r316810 for ipfilter, keep frags is no longer assumed when
457 keep state is specified in a rule. r316810 aligns ipfilter with
458 documentation in man pages separating keep frags from keep state.
459 This allows keep state to be specified without forcing keep frags
460 and allows keep frags to be specified independently of keep state.
461 To maintain previous behaviour, also specify keep frags with
462 keep state (as documented in ipf.conf.5).
465 arm64 builds now use the base system LLD 4.0.0 linker by default,
466 instead of requiring that the aarch64-binutils port or package be
467 installed. To continue using aarch64-binutils, set
468 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
471 The UDP optimization in entry 20160818 that added the sysctl
472 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
473 packets will no longer be treated as L3 broadcast packets.
476 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
477 use any explicitly assigned loopback address available in the jail
478 instead of using the first assigned address of the jail.
481 The ctl.ko module no longer implements the iSCSI target frontend:
482 cfiscsi.ko does instead.
484 If building cfiscsi.ko as a kernel module, the module can be loaded
485 via one of the following methods:
486 - `cfiscsi_load="YES"` in loader.conf(5).
487 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
488 - ctladm(8)/ctld(8), when compiled with iSCSI support
489 (`WITH_ISCSI=yes` in src.conf(5))
491 Please see cfiscsi(4) for more details.
494 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
495 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
496 same source (previously, the dependency of mmcsd.ko on mmc.ko was
497 missing, but mmcsd.ko now will refuse to load if it is incompatible
501 The syntax of ipfw(8) named states was changed to avoid ambiguity.
502 If you have used named states in the firewall rules, you need to modify
503 them after installworld and before rebooting. Now named states must
504 be prefixed with colon.
507 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
508 removed as the userland we provide cannot use them. The KMS version
509 (sys/dev/drm2) supports the same hardware.
512 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
513 Please see the 20141231 entry below for information about prerequisites
514 and upgrading, if you are not already using clang 3.5.0 or higher.
517 The code that provides support for ZFS .zfs/ directory functionality
518 has been reimplemented. It's not possible now to create a snapshot
519 by mkdir under .zfs/snapshot/. That should be the only user visible
523 EISA bus support has been removed. The WITH_EISA option is no longer
527 MCA bus support has been removed.
530 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
531 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
534 The EM_MULTIQUEUE kernel configuration option is deprecated now that
535 the em(4) driver conforms to iflib specifications.
538 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
539 IFLIB. If you have a custom kernel configuration that excludes em(4)
540 but you use igb(4), you need to re-add em(4) to your custom configuration.
543 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
544 Please see the 20141231 entry below for information about prerequisites
545 and upgrading, if you are not already using clang 3.5.0 or higher.
548 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
549 Please see the 20141231 entry below for information about prerequisites
550 and upgrading, if you are not already using clang 3.5.0 or higher.
553 The layout of the pmap structure has changed for powerpc to put the pmap
554 statistics at the front for all CPU variations. libkvm(3) and all tools
555 that link against it need to be recompiled.
558 isl(4) and cyapa(4) drivers now require a new driver,
559 chromebook_platform(4), to work properly on Chromebook-class hardware.
560 On other types of hardware the drivers may need to be configured using
561 device hints. Please see the corresponding manual pages for details.
564 The urtwn(4) driver was merged into rtwn(4) and now consists of
565 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
567 Also, firmware for RTL8188CE was renamed due to possible name
568 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
571 GNU rcs has been removed from base. It is available as packages:
572 - rcs: Latest GPLv3 GNU rcs version.
573 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
577 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
578 modules now requires that the kernel configuration contain the
579 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
582 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
583 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
586 Relocatable object files with the extension of .So have been renamed
587 to use an extension of .pico instead. The purpose of this change is
588 to avoid a name clash with shared libraries on case-insensitive file
589 systems. On those file systems, foo.So is the same file as foo.so.
592 GNU rcs has been turned off by default. It can (temporarily) be built
593 again by adding WITH_RCS knob in src.conf.
594 Otherwise, GNU rcs is available from packages:
595 - rcs: Latest GPLv3 GNU rcs version.
596 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
599 The backup_uses_rcs functionality has been removed from rc.subr.
602 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
603 two separate components, QUEUE_MACRO_DEBUG_TRACE and
604 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
605 QUEUE_MACRO_DEBUG behavior.
608 r304787 changed some ioctl interfaces between the iSCSI userspace
609 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
610 rebuilt to work with new kernels. __FreeBSD_version has been bumped
614 The UDP receive code has been updated to only treat incoming UDP
615 packets that were addressed to an L2 broadcast address as L3
616 broadcast packets. It is not expected that this will affect any
617 standards-conforming UDP application. The new behaviour can be
618 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
622 Remove the openbsd_poll system call.
623 __FreeBSD_version has been bumped because of this.
626 The libc stub for the pipe(2) system call has been replaced with
627 a wrapper that calls the pipe2(2) system call and the pipe(2)
628 system call is now only implemented by the kernels that include
629 "options COMPAT_FREEBSD10" in their config file (this is the
630 default). Users should ensure that this option is enabled in
631 their kernel or upgrade userspace to r302092 before upgrading their
635 CAM will now strip leading spaces from SCSI disks' serial numbers.
636 This will affect users who create UFS filesystems on SCSI disks using
637 those disk's diskid device nodes. For example, if /etc/fstab
638 previously contained a line like
639 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
640 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
641 transforms like gmirror may also be affected. ZFS users should
645 The bitstring(3) API has been updated with new functionality and
646 improved performance. But it is binary-incompatible with the old API.
647 Objects built with the new headers may not be linked against objects
648 built with the old headers.
651 The brk and sbrk functions have been removed from libc on arm64.
652 Binutils from ports has been updated to not link to these
653 functions and should be updated to the latest version before
654 installing a new libc.
657 The armv6 port now defaults to hard float ABI. Limited support
658 for running both hardfloat and soft float on the same system
659 is available using the libraries installed with -DWITH_LIBSOFT.
660 This has only been tested as an upgrade path for installworld
661 and packages may fail or need manual intervention to run. New
662 packages will be needed.
664 To update an existing self-hosted armv6hf system, you must add
665 TARGET_ARCH=armv6 on the make command line for both the build
666 and the install steps.
669 Kernel modules compiled outside of a kernel build now default to
670 installing to /boot/modules instead of /boot/kernel. Many kernel
671 modules built this way (such as those in ports) already overrode
672 KMODDIR explicitly to install into /boot/modules. However,
673 manually building and installing a module from /sys/modules will
674 now install to /boot/modules instead of /boot/kernel.
677 The CAM I/O scheduler has been committed to the kernel. There should be
678 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
679 list of known rogues that claim support for this but actually corrupt
680 data is believed to be complete, be on the lookout for data
681 corruption. The known rogue list is believed to be complete:
683 o Crucial MX100, M550 drives with MU01 firmware.
684 o Micron M510 and M550 drives with MU01 firmware.
685 o Micron M500 prior to MU07 firmware
686 o Samsung 830, 840, and 850 all firmwares
687 o FCCT M500 all firmwares
689 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
690 with working NCQ TRIM. For Micron branded drives, see your sales rep for
691 updated firmware. Black listed drives will work correctly because these
692 drives work correctly so long as no NCQ TRIMs are sent to them. Given
693 this list is the same as found in Linux, it's believed there are no
694 other rogues in the market place. All other models from the above
697 To be safe, if you are at all concerned, you can quirk each of your
698 drives to prevent NCQ from being sent by setting:
699 kern.cam.ada.X.quirks="0x2"
700 in loader.conf. If the drive requires the 4k sector quirk, set the
704 The FAST_DEPEND build option has been removed and its functionality is
705 now the one true way. The old mkdep(1) style of 'make depend' has
706 been removed. See 20160311 for further details.
709 Resource range types have grown from unsigned long to uintmax_t. All
710 drivers, and anything using libdevinfo, need to be recompiled.
713 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
714 builds. It no longer runs mkdep(1) during 'make depend', and the
715 'make depend' stage can safely be skipped now as it is auto ran
716 when building 'make all' and will generate all SRCS and DPSRCS before
717 building anything else. Dependencies are gathered at compile time with
718 -MF flags kept in separate .depend files per object file. Users should
719 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
723 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
724 kernel modules. Therefore, if you load any kernel modules at boot time,
725 please install the boot loaders after you install the kernel, but before
729 make buildkernel KERNCONF=YOUR_KERNEL_HERE
730 make installkernel KERNCONF=YOUR_KERNEL_HERE
731 make -C sys/boot install
732 <reboot in single user>
734 Then follow the usual steps, described in the General Notes section,
738 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
739 see the 20141231 entry below for information about prerequisites and
740 upgrading, if you are not already using clang 3.5.0 or higher.
743 The AIO subsystem is now a standard part of the kernel. The
744 VFS_AIO kernel option and aio.ko kernel module have been removed.
745 Due to stability concerns, asynchronous I/O requests are only
746 permitted on sockets and raw disks by default. To enable
747 asynchronous I/O requests on all file types, set the
748 vfs.aio.enable_unsafe sysctl to a non-zero value.
751 The ELF object manipulation tool objcopy is now provided by the
752 ELF Tool Chain project rather than by GNU binutils. It should be a
753 drop-in replacement, with the addition of arm64 support. The
754 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
755 to obtain the GNU version if necessary.
758 Building ZFS pools on top of zvols is prohibited by default. That
759 feature has never worked safely; it's always been prone to deadlocks.
760 Using a zvol as the backing store for a VM guest's virtual disk will
761 still work, even if the guest is using ZFS. Legacy behavior can be
762 restored by setting vfs.zfs.vol.recursive=1.
765 The NONE and HPN patches has been removed from OpenSSH. They are
766 still available in the security/openssh-portable port.
769 With the addition of ypldap(8), a new _ypldap user is now required
770 during installworld. "mergemaster -p" can be used to add the user
771 prior to installworld, as documented in the handbook.
774 The tftp loader (pxeboot) now uses the option root-path directive. As a
775 consequence it no longer looks for a pxeboot.4th file on the tftp
776 server. Instead it uses the regular /boot infrastructure as with the
780 The code to start recording plug and play data into the modules has
781 been committed. While the old tools will properly build a new kernel,
782 a number of warnings about "unknown metadata record 4" will be produced
783 for an older kldxref. To avoid such warnings, make sure to rebuild
784 the kernel toolchain (or world). Make sure that you have r292078 or
785 later when trying to build 292077 or later before rebuilding.
788 Debug data files are now built by default with 'make buildworld' and
789 installed with 'make installworld'. This facilitates debugging but
790 requires more disk space both during the build and for the installed
791 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
795 r291527 changed the internal interface between the nfsd.ko and
796 nfscommon.ko modules. As such, they must both be upgraded to-gether.
797 __FreeBSD_version has been bumped because of this.
800 Add support for unicode collation strings leads to a change of
801 order of files listed by ls(1) for example. To get back to the old
802 behaviour, set LC_COLLATE environment variable to "C".
804 Databases administrators will need to reindex their databases given
805 collation results will be different.
807 Due to a bug in install(1) it is recommended to remove the ancient
808 locales before running make installworld.
810 rm -rf /usr/share/locale/*
813 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
814 libcrypto.so.7 or libssl.so.7 must be recompiled.
817 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
818 Kernel modules isp_2400_multi and isp_2500_multi were removed and
819 should be replaced with isp_2400 and isp_2500 modules respectively.
822 The build previously allowed using 'make -n' to not recurse into
823 sub-directories while showing what commands would be executed, and
824 'make -n -n' to recursively show commands. Now 'make -n' will recurse
825 and 'make -N' will not.
828 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
829 and etcupdate will now use this file. A custom sendmail.cf is now
830 updated via this mechanism rather than via installworld. If you had
831 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
832 want to remove the exclusion or change it to "always install".
833 /etc/mail/sendmail.cf is now managed the same way regardless of
834 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
835 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
838 Compatibility shims for legacy ATA device names have been removed.
839 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
840 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
841 environment variables, /dev/ad* and /dev/ar* symbolic links.
844 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
845 Please see the 20141231 entry below for information about prerequisites
846 and upgrading, if you are not already using clang 3.5.0 or higher.
849 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
850 and renamed from .symbols to .debug. This reduces the size requirements
851 on the boot partition or file system and provides consistency with
852 userland debug files.
854 When using the supported kernel installation method the
855 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
856 as is done with /boot/kernel.
858 Developers wishing to maintain the historical behavior of installing
859 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
862 The wireless drivers had undergone changes that remove the 'parent
863 interface' from the ifconfig -l output. The rc.d network scripts
864 used to check presence of a parent interface in the list, so old
865 scripts would fail to start wireless networking. Thus, etcupdate(3)
866 or mergemaster(8) run is required after kernel update, to update your
867 rc.d scripts in /etc.
870 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
871 These configurations are now automatically interpreted as
872 'scrub fragment reassemble'.
875 Kernel-loadable modules for the random(4) device are back. To use
876 them, the kernel must have
879 options RANDOM_LOADABLE
881 kldload(8) can then be used to load random_fortuna.ko
882 or random_yarrow.ko. Please note that due to the indirect
883 function calls that the loadable modules need to provide,
884 the build-in variants will be slightly more efficient.
886 The random(4) kernel option RANDOM_DUMMY has been retired due to
887 unpopularity. It was not all that useful anyway.
890 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
891 Control over building the ELF Tool Chain tools is now provided by
892 the WITHOUT_TOOLCHAIN knob.
895 The polarity of Pulse Per Second (PPS) capture events with the
896 uart(4) driver has been corrected. Prior to this change the PPS
897 "assert" event corresponded to the trailing edge of a positive PPS
898 pulse and the "clear" event was the leading edge of the next pulse.
900 As the width of a PPS pulse in a typical GPS receiver is on the
901 order of 1 millisecond, most users will not notice any significant
902 difference with this change.
904 Anyone who has compensated for the historical polarity reversal by
905 configuring a negative offset equal to the pulse width will need to
906 remove that workaround.
909 The default group assigned to /dev/dri entries has been changed
910 from 'wheel' to 'video' with the id of '44'. If you want to have
911 access to the dri devices please add yourself to the video group
914 # pw groupmod video -m $USER
917 The menu.rc and loader.rc files will now be replaced during
918 upgrades. Please migrate local changes to menu.rc.local and
919 loader.rc.local instead.
922 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
923 strings and strip have been removed. The src.conf(5) knob
924 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
927 As ZFS requires more kernel stack pages than is the default on some
928 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
929 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
931 Please consider using 'options KSTACK_PAGES=X' where X is greater
932 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
935 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
936 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
937 default, i.e., they will not contain "::". For example, instead
938 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
939 to have a more specific match, such as different map entries for
940 IPv6:0:0 vs IPv6:0. This change requires that configuration
941 data (including maps, files, classes, custom ruleset, etc.) must
942 use the same format, so make certain such configuration data is
943 upgrading. As a very simple check search for patterns like
944 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
945 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
946 the cf option UseCompressedIPv6Addresses.
949 The default kernel entropy-processing algorithm is now
950 Fortuna, replacing Yarrow.
952 Assuming you have 'device random' in your kernel config
953 file, the configurations allow a kernel option to override
954 this default. You may choose *ONE* of:
956 options RANDOM_YARROW # Legacy /dev/random algorithm.
957 options RANDOM_DUMMY # Blocking-only driver.
959 If you have neither, you get Fortuna. For most people,
960 read no further, Fortuna will give a /dev/random that works
961 like it always used to, and the difference will be irrelevant.
963 If you remove 'device random', you get *NO* kernel-processed
964 entropy at all. This may be acceptable to folks building
965 embedded systems, but has complications. Carry on reading,
966 and it is assumed you know what you need.
968 *PLEASE* read random(4) and random(9) if you are in the
969 habit of tweaking kernel configs, and/or if you are a member
970 of the embedded community, wanting specific and not-usual
971 behaviour from your security subsystems.
973 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
974 random', you will NOT have a functioning /dev/random, and
975 many cryptographic features will not work, including SSH.
976 You may also find strange behaviour from the random(3) set
977 of library functions, in particular sranddev(3), srandomdev(3)
978 and arc4random(3). The reason for this is that the KERN_ARND
979 sysctl only returns entropy if it thinks it has some to
980 share, and with RANDOM_DUMMY or no 'device random' this
984 An additional fix for the issue described in the 20150614 sendmail
985 entry below has been committed in revision 284717.
988 FreeBSD's old make (fmake) has been removed from the system. It is
989 available as the devel/fmake port or via pkg install fmake.
992 The fix for the issue described in the 20150614 sendmail entry
993 below has been committed in revision 284436. The work
994 around described in that entry is no longer needed unless the
995 default setting is overridden by a confDH_PARAMETERS configuration
996 setting of '5' or pointing to a 512 bit DH parameter file.
999 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1000 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1001 and devel/kyua to version 0.20+ and adjust any calling code to work
1002 with Kyuafile and kyua.
1005 The import of openssl to address the FreeBSD-SA-15:10.openssl
1006 security advisory includes a change which rejects handshakes
1007 with DH parameters below 768 bits. sendmail releases prior
1008 to 8.15.2 (not yet released), defaulted to a 512 bit
1009 DH parameter setting for client connections. To work around
1010 this interoperability, sendmail can be configured to use a
1011 2048 bit DH parameter by:
1013 1. Edit /etc/mail/`hostname`.mc
1014 2. If a setting for confDH_PARAMETERS does not exist or
1015 exists and is set to a string beginning with '5',
1016 replace it with '2'.
1017 3. If a setting for confDH_PARAMETERS exists and is set to
1018 a file path, create a new file with:
1019 openssl dhparam -out /path/to/file 2048
1020 4. Rebuild the .cf file:
1021 cd /etc/mail/; make; make install
1022 5. Restart sendmail:
1023 cd /etc/mail/; make restart
1025 A sendmail patch is coming, at which time this file will be
1029 Generation of legacy formatted entries have been disabled by default
1030 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1031 entries were converted to use the new format by default when the new,
1032 machine independent format have been added and supported since FreeBSD
1035 Please see the pwd_mkdb(8) manual page for further details.
1038 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1039 20141231 entry below for information about prerequisites and upgrading,
1040 if you are not already using 3.5.0 or higher.
1043 TI platform code switched to using vendor DTS files and this update
1044 may break existing systems running on Beaglebone, Beaglebone Black,
1047 - dtb files should be regenerated/reinstalled. Filenames are the
1048 same but content is different now
1049 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1050 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1051 addressing scheme is now pin 25 on /dev/gpioc3.
1052 - Pandaboard: /etc/ttys should be updated, serial console device is
1053 now /dev/ttyu2, not /dev/ttyu0
1056 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1057 If you need the GNU extension from groff soelim(1), install groff
1058 from package: pkg install groff, or via ports: textproc/groff.
1061 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1062 defined in symlink(7); previously symlinks were silently ignored.
1065 The const qualifier has been removed from iconv(3) to comply with
1066 POSIX. The ports tree is aware of this from r384038 onwards.
1069 Libraries specified by LIBADD in Makefiles must have a corresponding
1070 DPADD_<lib> variable to ensure correct dependencies. This is now
1071 enforced in src.libnames.mk.
1074 From legacy ata(4) driver was removed support for SATA controllers
1075 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1076 Kernel modules ataahci and ataadaptec were removed completely,
1077 replaced by ahci and mvs modules respectively.
1080 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1081 the 20141231 entry below for information about prerequisites and
1082 upgrading, if you are not already using 3.5.0 or higher.
1085 The 32-bit PowerPC kernel has been changed to a position-independent
1086 executable. This can only be booted with a version of loader(8)
1087 newer than January 31, 2015, so make sure to update both world and
1088 kernel before rebooting.
1091 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1092 but before r278950, the RNG was not seeded properly. Immediately
1093 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1094 ssh keys or openssl keys) that were generated w/ a kernel from that
1095 range. This does not affect programs that directly used /dev/random
1096 or /dev/urandom. All userland uses of arc4random(3) are affected.
1099 The autofs(4) ABI was changed in order to restore binary compatibility
1100 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1101 with the new kernel.
1104 The powerpc64 kernel has been changed to a position-independent
1105 executable. This can only be booted with a new version of loader(8),
1106 so make sure to update both world and kernel before rebooting.
1109 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1110 only release, no new features have been added. Please see the 20141231
1111 entry below for information about prerequisites and upgrading, if you
1112 are not already using 3.5.0.
1115 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1116 taken from the ELF Tool Chain project rather than GNU binutils. They
1117 should be drop-in replacements, with the addition of arm64 support.
1118 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1119 binutils tools, if necessary. See 20150805 for updated information.
1122 The default Unbound configuration now enables remote control
1123 using a local socket. Users who have already enabled the
1124 local_unbound service should regenerate their configuration
1125 by running "service local_unbound setup" as root.
1128 The GNU texinfo and GNU info pages have been removed.
1129 To be able to view GNU info pages please install texinfo from ports.
1132 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1134 As of this release, a prerequisite for building clang, llvm and lldb is
1135 a C++11 capable compiler and C++11 standard library. This means that to
1136 be able to successfully build the cross-tools stage of buildworld, with
1137 clang as the bootstrap compiler, your system compiler or cross compiler
1138 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1139 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1142 On any standard FreeBSD 10.x or 11.x installation, where clang and
1143 libc++ are on by default (that is, on x86 or arm), this should work out
1146 On 9.x installations where clang is enabled by default, e.g. on x86 and
1147 powerpc, libc++ will not be enabled by default, so libc++ should be
1148 built (with clang) and installed first. If both clang and libc++ are
1149 missing, build clang first, then use it to build libc++.
1151 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1152 the instructions for 9.x above.
1154 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1155 default, and do not build clang.
1157 Many embedded systems are resource constrained, and will not be able to
1158 build clang in a reasonable time, or in some cases at all. In those
1159 cases, cross building bootable systems on amd64 is a workaround.
1161 This new version of clang introduces a number of new warnings, of which
1162 the following are most likely to appear:
1166 This warns in two cases, for both C and C++:
1167 * When the code is trying to take the absolute value of an unsigned
1168 quantity, which is effectively a no-op, and almost never what was
1169 intended. The code should be fixed, if at all possible. If you are
1170 sure that the unsigned quantity can be safely cast to signed, without
1171 loss of information or undefined behavior, you can add an explicit
1172 cast, or disable the warning.
1174 * When the code is trying to take an absolute value, but the called
1175 abs() variant is for the wrong type, which can lead to truncation.
1176 If you want to disable the warning instead of fixing the code, please
1177 make sure that truncation will not occur, or it might lead to unwanted
1180 -Wtautological-undefined-compare and
1181 -Wundefined-bool-conversion
1183 These warn when C++ code is trying to compare 'this' against NULL, while
1184 'this' should never be NULL in well-defined C++ code. However, there is
1185 some legacy (pre C++11) code out there, which actively abuses this
1186 feature, which was less strictly defined in previous C++ versions.
1188 Squid and openjdk do this, for example. The warning can be turned off
1189 for C++98 and earlier, but compiling the code in C++11 mode might result
1190 in unexpected behavior; for example, the parts of the program that are
1191 unreachable could be optimized away.
1194 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1195 kernel sources have been removed. The .h files remain, since some
1196 utilities include them. This will need to be fixed later.
1197 If "mount -t oldnfs ..." is attempted, it will fail.
1198 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1199 the utilities will report errors.
1202 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1203 directories to top level SUBDIR variable when their parent
1204 directory is included in LOCAL_DIRS. Users with build systems with
1205 such hierarchies and without SUBDIR entries in the parent
1206 directory Makefiles should add them or add the directories to
1210 faith(4) and faithd(8) have been removed from the base system. Faith
1211 has been obsolete for a very long time.
1214 vt(4), the new console driver, is enabled by default. It brings
1215 support for Unicode and double-width characters, as well as
1216 support for UEFI and integration with the KMS kernel video
1219 You may need to update your console settings in /etc/rc.conf,
1220 most probably the keymap. During boot, /etc/rc.d/syscons will
1221 indicate what you need to do.
1223 vt(4) still has issues and lacks some features compared to
1224 syscons(4). See the wiki for up-to-date information:
1225 https://wiki.freebsd.org/Newcons
1227 If you want to keep using syscons(4), you can do so by adding
1228 the following line to /boot/loader.conf:
1232 pjdfstest has been integrated into kyua as an opt-in test suite.
1233 Please see share/doc/pjdfstest/README for more details on how to
1237 gperf has been removed from the base system for architectures
1238 that use clang. Ports that require gperf will obtain it from the
1242 pjdfstest has been moved from tools/regression/pjdfstest to
1246 At svn r271982, The default linux compat kernel ABI has been adjusted
1247 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1248 update. If you wish to continue using the linux-f10 compat ports,
1249 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1250 encouraged to update their linux-compat packages to linux-c6 during
1251 their next update cycle.
1254 The ofwfb driver, used to provide a graphics console on PowerPC when
1255 using vt(4), no longer allows mmap() of all physical memory. This
1256 will prevent Xorg on PowerPC with some ATI graphics cards from
1257 initializing properly unless x11-servers/xorg-server is updated to
1261 The xdev targets have been converted to using TARGET and
1262 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1265 The default unbound configuration has been modified to address
1266 issues with reverse lookups on networks that use private
1267 address ranges. If you use the local_unbound service, run
1268 "service local_unbound setup" as root to regenerate your
1269 configuration, then "service local_unbound reload" to load the
1273 The GNU texinfo and GNU info pages are not built and installed
1274 anymore, WITH_INFO knob has been added to allow to built and install
1276 UPDATE: see 20150102 entry on texinfo's removal
1279 The GNU readline library is now an INTERNALLIB - that is, it is
1280 statically linked into consumers (GDB and variants) in the base
1281 system, and the shared library is no longer installed. The
1282 devel/readline port is available for third party software that
1286 The Itanium architecture (ia64) has been removed from the list of
1287 known architectures. This is the first step in the removal of the
1291 Commit r268115 has added NFSv4.1 server support, merged from
1292 projects/nfsv4.1-server. Since this includes changes to the
1293 internal interfaces between the NFS related modules, a full
1294 build of the kernel and modules will be necessary.
1295 __FreeBSD_version has been bumped.
1298 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1299 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1300 which differs from the behaviour controlled by this knob.)
1303 Maximal length of the serial number in CTL was increased from 16 to
1304 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1305 and ctld, need to be rebuilt to work with a new kernel.
1308 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1309 1 respectively to match the upstream numbers. They were out of
1310 sync because, when they were originally added to FreeBSD, the
1311 upstream versions were not respected. These libraries are private
1312 and not yet built by default, so renumbering them should be a
1313 non-issue. However, unclean source trees will yield broken test
1314 programs once the operator executes "make delete-old-libs" after a
1315 "make installworld".
1317 Additionally, the atf-sh binary was made private by moving it into
1318 /usr/libexec/. Already-built shell test programs will keep the
1319 path to the old binary so they will break after "make delete-old"
1322 If you are using WITH_TESTS=yes (not the default), wipe the object
1323 tree and rebuild from scratch to prevent spurious test failures.
1324 This is only needed once: the misnumbered libraries and misplaced
1325 binaries have been added to OptionalObsoleteFiles.inc so they will
1326 be removed during a clean upgrade.
1329 Clang and llvm have been upgraded to 3.4.1 release.
1332 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1333 be removed to avoid issues in the future (and has been added to
1337 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1338 past, it affected all builds that used the bsd.*.mk files. The old
1339 behavior was a bug, but people may have relied upon it. To get this
1340 behavior back, you can .include /etc/src.conf from /etc/make.conf
1341 (which is still global and isn't changed). This also changes the
1342 behavior of incremental builds inside the tree of individual
1343 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1344 Although this has survived make universe and some upgrade scenarios,
1345 other upgrade scenarios may have broken. At least one form of
1346 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1347 as well... In cases where MAKESYSPATH isn't working with this
1348 setting, you'll need to set it to the full path to your tree.
1350 One side effect of all this cleaning up is that bsd.compiler.mk
1351 is no longer implicitly included by bsd.own.mk. If you wish to
1352 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1356 The lindev device has been removed since /dev/full has been made a
1357 standard device. __FreeBSD_version has been bumped.
1360 The knob WITHOUT_VI was added to the base system, which controls
1361 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1362 in order to reorder files share/termcap and didn't build ex(1) as a
1363 build tool, so building/installing with WITH_VI is highly advised for
1364 build hosts for older releases.
1366 This issue has been fixed in stable/9 and stable/10 in r277022 and
1367 r276991, respectively.
1370 The YES_HESIOD knob has been removed. It has been obsolete for
1371 a decade. Please move to using WITH_HESIOD instead or your builds
1372 will silently lack HESIOD.
1375 The uart(4) driver has been changed with respect to its handling
1376 of the low-level console. Previously the uart(4) driver prevented
1377 any process from changing the baudrate or the CLOCAL and HUPCL
1378 control flags. By removing the restrictions, operators can make
1379 changes to the serial console port without having to reboot.
1380 However, when getty(8) is started on the serial device that is
1381 associated with the low-level console, a misconfigured terminal
1382 line in /etc/ttys will now have a real impact.
1383 Before upgrading the kernel, make sure that /etc/ttys has the
1384 serial console device configured as 3wire without baudrate to
1385 preserve the previous behaviour. E.g:
1386 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1389 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1390 to improve performance. To re-enable it, if needed, run rpcbind
1391 with command line option -W.
1394 Switched back to the GPL dtc compiler due to updates in the upstream
1395 dts files not being supported by the BSDL dtc compiler. You will need
1396 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1397 may result while building dtb files during a kernel build if you fail
1398 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1401 Clang and llvm have been upgraded to 3.4 release.
1404 The nve(4) driver has been removed. Please use the nfe(4) driver
1405 for NVIDIA nForce MCP Ethernet adapters instead.
1408 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1409 This could cause certain C++ applications using shared libraries built
1410 against the previous version of libc++ to crash. The incompatibility
1411 has now been fixed, but any C++ applications or shared libraries built
1412 between r261283 and r261801 should be recompiled.
1415 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1416 capability mode support. Please note that enabling the feature in
1417 kernel is still highly recommended.
1420 OpenSSH is now built with sandbox support, and will use sandbox as
1421 the default privilege separation method. This requires Capsicum
1422 capability mode support in kernel.
1425 The libelf and libdwarf libraries have been updated to newer
1426 versions from upstream. Shared library version numbers for
1427 these two libraries were bumped. Any ports or binaries
1428 requiring these two libraries should be recompiled.
1429 __FreeBSD_version is bumped to 1100006.
1432 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1433 instead of providing an explicit one, this would prevent such
1434 Makefile from providing its own Kyuafile in the future during
1435 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1436 intervention is needed to clean an objdir if you use NO_CLEAN:
1437 # find /usr/obj -name Kyuafile | xargs rm -f
1440 The behavior of gss_pseudo_random() for the krb5 mechanism
1441 has changed, for applications requesting a longer random string
1442 than produced by the underlying enctype's pseudo-random() function.
1443 In particular, the random string produced from a session key of
1444 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1445 be different at the 17th octet and later, after this change.
1446 The counter used in the PRF+ construction is now encoded as a
1447 big-endian integer in accordance with RFC 4402.
1448 __FreeBSD_version is bumped to 1100004.
1451 The WITHOUT_ATF build knob has been removed and its functionality
1452 has been subsumed into the more generic WITHOUT_TESTS. If you were
1453 using the former to disable the build of the ATF libraries, you
1454 should change your settings to use the latter.
1457 The default version of mtree is nmtree which is obtained from
1458 NetBSD. The output is generally the same, but may vary
1459 slightly. If you found you need identical output adding
1460 "-F freebsd9" to the command line should do the trick. For the
1461 time being, the old mtree is available as fmtree.
1464 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1465 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1466 1.1.4_8 and verify bsdyml not linked in, before running "make
1468 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1470 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1473 The stable/10 branch has been created in subversion from head
1480 Avoid using make -j when upgrading. While generally safe, there are
1481 sometimes problems using -j to upgrade. If your upgrade fails with
1482 -j, please try again without -j. From time to time in the past there
1483 have been problems using -j with buildworld and/or installworld. This
1484 is especially true when upgrading between "distant" versions (eg one
1485 that cross a major release boundary or several minor releases, or when
1486 several months have passed on the -current branch).
1488 Sometimes, obscure build problems are the result of environment
1489 poisoning. This can happen because the make utility reads its
1490 environment when searching for values for global variables. To run
1491 your build attempts in an "environmental clean room", prefix all make
1492 commands with 'env -i '. See the env(1) manual page for more details.
1494 When upgrading from one major version to another it is generally best to
1495 upgrade to the latest code in the currently installed branch first, then
1496 do an upgrade to the new branch. This is the best-tested upgrade path,
1497 and has the highest probability of being successful. Please try this
1498 approach if you encounter problems with a major version upgrade. Since
1499 the stable 4.x branch point, one has generally been able to upgrade from
1500 anywhere in the most recent stable branch to head / current (or even the
1501 last couple of stable branches). See the top of this file when there's
1504 When upgrading a live system, having a root shell around before
1505 installing anything can help undo problems. Not having a root shell
1506 around can lead to problems if pam has changed too much from your
1507 starting point to allow continued authentication after the upgrade.
1509 This file should be read as a log of events. When a later event changes
1510 information of a prior event, the prior event should not be deleted.
1511 Instead, a pointer to the entry with the new information should be
1512 placed in the old entry. Readers of this file should also sanity check
1513 older entries before relying on them blindly. Authors of new entries
1514 should write them with this in mind.
1518 When upgrading the boot ZFS pool to a new version, always follow
1521 1.) recompile and reinstall the ZFS boot loader and boot block
1522 (this is part of "make buildworld" and "make installworld")
1524 2.) update the ZFS boot block on your boot drive
1526 The following example updates the ZFS boot block on the first
1527 partition (freebsd-boot) of a GPT partitioned drive ada0:
1528 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1530 Non-boot pools do not need these updates.
1534 If you are updating from a prior version of FreeBSD (even one just
1535 a few days old), you should follow this procedure. It is the most
1536 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1538 make kernel-toolchain
1539 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1540 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1542 To test a kernel once
1543 ---------------------
1544 If you just want to boot a kernel once (because you are not sure
1545 if it works, or if you want to boot a known bad kernel to provide
1546 debugging information) run
1547 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1548 nextboot -k testkernel
1550 To rebuild everything and install it on the current system.
1551 -----------------------------------------------------------
1552 # Note: sometimes if you are running current you gotta do more than
1553 # is listed here if you are upgrading from a really old current.
1555 <make sure you have good level 0 dumps>
1557 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1558 make installkernel KERNCONF=YOUR_KERNEL_HERE
1560 <reboot in single user> [3]
1567 To cross-install current onto a separate partition
1568 --------------------------------------------------
1569 # In this approach we use a separate partition to hold
1570 # current's root, 'usr', and 'var' directories. A partition
1571 # holding "/", "/usr" and "/var" should be about 2GB in
1574 <make sure you have good level 0 dumps>
1577 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1578 <maybe newfs current's root partition>
1579 <mount current's root partition on directory ${CURRENT_ROOT}>
1580 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1581 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1582 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1583 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1584 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1585 <reboot into current>
1586 <do a "native" rebuild/install as described in the previous section>
1587 <maybe install compatibility libraries from ports/misc/compat*>
1591 To upgrade in-place from stable to current
1592 ----------------------------------------------
1593 <make sure you have good level 0 dumps>
1595 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1596 make installkernel KERNCONF=YOUR_KERNEL_HERE
1598 <reboot in single user> [3]
1605 Make sure that you've read the UPDATING file to understand the
1606 tweaks to various things you need. At this point in the life
1607 cycle of current, things change often and you are on your own
1608 to cope. The defaults can also change, so please read ALL of
1609 the UPDATING entries.
1611 Also, if you are tracking -current, you must be subscribed to
1612 freebsd-current@freebsd.org. Make sure that before you update
1613 your sources that you have read and understood all the recent
1614 messages there. If in doubt, please track -stable which has
1615 much fewer pitfalls.
1617 [1] If you have third party modules, such as vmware, you
1618 should disable them at this point so they don't crash your
1621 [3] From the bootblocks, boot -s, and then do
1626 adjkerntz -i # if CMOS is wall time
1627 Also, when doing a major release upgrade, it is required that
1628 you boot into single user mode to do the installworld.
1630 [4] Note: This step is non-optional. Failure to do this step
1631 can result in a significant reduction in the functionality of the
1632 system. Attempting to do it by hand is not recommended and those
1633 that pursue this avenue should read this file carefully, as well
1634 as the archives of freebsd-current and freebsd-hackers mailing lists
1635 for potential gotchas. The -U option is also useful to consider.
1636 See mergemaster(8) for more information.
1638 [5] Usually this step is a no-op. However, from time to time
1639 you may need to do this if you get unknown user in the following
1640 step. It never hurts to do it all the time. You may need to
1641 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1642 install) after the buildworld before this step if you last updated
1643 from current before 20130425 or from -stable before 20130430.
1645 [6] This only deletes old files and directories. Old libraries
1646 can be deleted by "make delete-old-libs", but you have to make
1647 sure that no program is using those libraries anymore.
1649 [8] In order to have a kernel that can run the 4.x binaries needed to
1650 do an installworld, you must include the COMPAT_FREEBSD4 option in
1651 your kernel. Failure to do so may leave you with a system that is
1652 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1653 required to run the 5.x binaries on more recent kernels. And so on
1654 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1656 Make sure that you merge any new devices from GENERIC since the
1657 last time you updated your kernel config file.
1659 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1660 "?=" instead of the "=" assignment operator, so that buildworld can
1661 override the CPUTYPE if it needs to.
1663 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1664 not on the command line, or in /etc/make.conf. buildworld will
1665 warn if it is improperly defined.
1668 This file contains a list, in reverse chronological order, of major
1669 breakages in tracking -current. It is not guaranteed to be a complete
1670 list of such breakages, and only contains entries since September 23, 2011.
1671 If you need to see UPDATING entries from before that date, you will need
1672 to fetch an UPDATING file from an older FreeBSD release.
1674 Copyright information:
1676 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1678 Redistribution, publication, translation and use, with or without
1679 modification, in full or in part, in any form or format of this
1680 document are permitted without further permission from the author.
1682 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1683 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1684 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1685 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1686 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1687 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1688 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1689 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1690 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1691 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1692 POSSIBILITY OF SUCH DAMAGE.
1694 Contact Warner Losh if you have any questions about your use of