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 On i386 and amd64 atomics are now inlined. Out of tree modules using
36 atomics will need to be rebuilt.
39 The '%I' format in the kern.corefile sysctl limits the number of
40 core files that a process can generate to the number stored in the
41 debug.ncores sysctl. The '%I' format is replaced by the single digit
42 index. Previously, if all indexes were taken the kernel would overwrite
43 only a core file with the highest index in a filename.
44 Currently the system will create a new core file if there is a free
45 index or if all slots are taken it will overwrite the oldest one.
48 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
49 6.0.1. Please see the 20141231 entry below for information about
50 prerequisites and upgrading, if you are not already using clang 3.5.0
54 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
55 needed to be changed to work with it. This change was made with r335763
56 and requires a mergemaster / etcupdate / etc to update the installed file.
59 r334930 changed the interface between the NFS modules, so they all
60 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
63 The kernel / userland interface for devinfo changed, so you'll
64 need a new kernel and userland as a pair for it to work (rebuilding
65 lib/libdevinfo is all that's required). devinfo and devmatch will
66 not work, but everything else will when there's a mismatch.
69 The on-disk format for hwpmc callchain records has changed to include
70 threadid corresponding to a given record. This changes the field offsets
71 and thus requires that libpmcstat be rebuilt before using a kernel
75 The vxge(4) driver has been removed. This driver was introduced into
76 HEAD one week before the Exar left the Ethernet market and is not
77 known to be used. If you have device vxge in your kernel config file
81 The amd64 kernel now requires a ld that supports ifunc to produce a
82 working kernel, either lld or a newer binutils. lld is built by default
83 on amd64, and the 'buildkernel' target uses it automatically. However,
84 it is not the default linker, so building the kernel the traditional
85 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
86 binutils port/package). lld will soon be default, and this requirement
90 The nxge(4) driver has been removed. This driver was for PCI-X 10g
91 cards made by s2io/Neterion. The company was aquired by Exar and
92 no longer sells or supports Ethernet products. If you have device
93 nxge in your kernel config file it must be removed.
96 The tz database (tzdb) has been updated to 2018e. This version more
97 correctly models time stamps in time zones with negative DST such as
98 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
99 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
100 time zone abbreviations and the tm_isdst flag.
103 The ixgb(4) driver has been removed. This driver was for an early and
104 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
105 quickly shifted to the long lived ixgbe family. If you have device
106 ixgb in your kernel config file it must be removed.
109 The lmc(4) driver has been removed. This was a WAN interface
110 card that was already reportedly rare in 2003, and had an ambiguous
111 license. If you have device lmc in your kernel config file it must
115 Support for Arcnet networks has been removed. If you have device
116 arcnet or device cm in your kernel config file they must be
120 Support for FDDI networks has been removed. If you have device
121 fddi or device fpa in your kernel config file they must be
125 In addition to supporting RFC 3164 formatted messages, the
126 syslogd(8) service is now capable of parsing RFC 5424 formatted
127 log messages. The main benefit of using RFC 5424 is that clients
128 may now send log messages with timestamps containing year numbers,
129 microseconds and time zone offsets.
131 Similarly, the syslog(3) C library function has been altered to
132 send RFC 5424 formatted messages to the local system logging
133 daemon. On systems using syslogd(8), this change should have no
134 negative impact, as long as syslogd(8) and the C library are
135 updated at the same time. On systems using a different system
136 logging daemon, it may be necessary to make configuration
137 adjustments, depending on the software used.
139 When using syslog-ng, add the 'syslog-protocol' flag to local
140 input sources to enable parsing of RFC 5424 formatted messages:
143 unix-dgram("/var/run/log" flags(syslog-protocol));
146 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
147 of the 'imuxsock' module to let messages be processed by the
148 regular RFC 3164/5424 parsing pipeline:
150 module(load="imuxsock" SysSock.UseSpecialParser="off")
152 Do note that these changes only affect communication between local
153 applications and syslogd(8). The format that syslogd(8) uses to
154 store messages on disk or forward messages to other systems
155 remains unchanged. syslogd(8) still uses RFC 3164 for these
156 purposes. Options to customize this behaviour will be added in the
157 future. Utilities that process log files stored in /var/log are
158 thus expected to continue to function as before.
160 __FreeBSD_version has been incremented to 1200061 to denote this
164 Support for token ring networks has been removed. If you
165 have "device token" in your kernel config you should remove
166 it. No device drivers supported token ring.
169 makefs was modified to be able to tag ISO9660 El Torito boot catalog
170 entries as EFI instead of overloading the i386 tag as done previously.
171 The amd64 mkisoimages.sh script used to build amd64 ISO images for
172 release was updated to use this. This may mean that makefs must be
173 updated before "make cdrom" can be run in the release directory. This
174 should be as simple as:
176 $ cd $SRCDIR/usr.sbin/makefs
177 $ make depend all install
180 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
181 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
182 Co-existance for the transition period will come shortly. Booting is a
183 complex environment and test coverage for Lua-enabled loaders has been
184 thin, so it would be prudent to assume it might not work and make
185 provisions for backup boot methods.
188 devmatch functionality has been turned on in devd. It will automatically
189 load drivers for unattached devices. This may cause unexpected drivers to
190 be loaded. Please report any problems to current@ and imp@freebsd.org.
193 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
194 6.0.0. Please see the 20141231 entry below for information about
195 prerequisites and upgrading, if you are not already using clang 3.5.0
199 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
200 This means it is used to link the kernel and userland libraries and
201 executables, but is not yet installed as /usr/bin/ld by default.
203 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
204 WITHOUT_LLD_BOOTSTRAP=yes
207 On i386, pmtimer has been removed. Its functionality has been folded
208 into apm. It was a no-op on ACPI in current for a while now (but was still
209 needed on i386 in FreeBSD 11 and earlier). Users may need to remove it
210 from kernel config files.
213 The use of RSS hash from the network card aka flowid has been
214 disabled by default for lagg(4) as it's currently incompatible with
215 the lacp and loadbalance protocols.
217 This can be re-enabled by setting the following in loader.conf:
218 net.link.lagg.default_use_flowid="1"
221 The SW_WATCHDOG option is no longer necessary to enable the
222 hardclock-based software watchdog if no hardware watchdog is
223 configured. As before, SW_WATCHDOG will cause the software
224 watchdog to be enabled even if a hardware watchdog is configured.
227 r326887 fixes the issue described in the 20171214 UPDATING entry.
228 r326888 flips the switch back to building GELI support always.
231 r362593 broke ZFS + GELI support for reasons unknown. However,
232 it also broke ZFS support generally, so GELI has been turned off
233 by default as the lesser evil in r326857. If you boot off ZFS and/or
234 GELI, it might not be a good time to update.
237 PowerPC users must update loader(8) by rebuilding world before
238 installing a new kernel, as the protocol connecting them has
239 changed. Without the update, loader metadata will not be passed
240 successfully to the kernel and users will have to enter their
241 root partition at the kernel mountroot prompt to continue booting.
242 Newer versions of loader can boot old kernels without issue.
245 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
246 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
247 to WITH/OUT_LOADER_GELI.
250 The naive and non-compliant support of posix_fallocate(2) in ZFS
251 has been removed as of r325320. The system call now returns EINVAL
252 when used on a ZFS file. Although the new behavior complies with the
253 standard, some consumers are not prepared to cope with it.
254 One known victim is lld prior to r325420.
257 Building in a FreeBSD src checkout will automatically create object
258 directories now rather than store files in the current directory if
259 'make obj' was not ran. Calling 'make obj' is no longer necessary.
260 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
261 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
265 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
266 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
267 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
268 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
269 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
270 The UNIFIED_OBJDIR option is a transitional feature that will be
271 removed for 12.0 release; please migrate to the new format for any
272 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
273 than hardcoding paths.
276 The native-xtools target no longer installs the files by default to the
277 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
278 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
281 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
282 options are changing from controlling the build if defined / undefined
283 to controlling the build with explicit 'yes' or 'no' values. They will
284 shift to WITH/WITHOUT options to match other options in the system.
287 libstand has turned into a private library for sys/boot use only.
288 It is no longer supported as a public interface outside of sys/boot.
291 The arm port has split armv6 into armv6 and armv7. armv7 is now
292 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
293 and are running a kernel from before r324363, you will need to add
294 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
297 When building multiple kernels using KERNCONF, non-existent KERNCONF
298 files will produce an error and buildkernel will fail. Previously
299 missing KERNCONF files silently failed giving no indication as to
300 why, only to subsequently discover during installkernel that the
301 desired kernel was never built in the first place.
304 The default serial number format for CTL LUNs has changed. This will
305 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
306 or iSCSI clients care about their LUNs' serial numbers. Users who
307 require serial number stability should hardcode serial numbers in
311 For 32-bit arm compiled for hard-float support, soft-floating point
312 binaries now always get their shared libraries from
313 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
314 /usr/libsoft also existed). Only users with a hard-float ld.so, but
315 soft-float everything else should be affected.
318 The geli password typed at boot is now hidden. To restore the previous
319 behavior, see geli(8) for configuration options.
322 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
323 sysctl values. Minor nit, but requires a rebuild of both world/kernel
327 "make check" behavior (made in ^/head@r295380) has been changed to
328 execute from a limited sandbox, as opposed to executing from
332 - The "beforecheck" and "aftercheck" targets are now specified.
333 - ${CHECKDIR} (added in commit noted above) has been removed.
334 - Legacy behavior can be enabled by setting
335 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
337 If the limited sandbox mode is enabled, "make check" will execute
338 "make distribution", then install, execute the tests, and clean up the
339 sandbox if successful.
341 The "make distribution" and "make install" targets are typically run as
342 root to set appropriate permissions and ownership at installation time.
343 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
344 environment if executing "make check" with limited sandbox mode using
345 an unprivileged user.
348 Since the switch to GPT disk labels, fsck for UFS/FFS has been
349 unable to automatically find alternate superblocks. As of r322297,
350 the information needed to find alternate superblocks has been
351 moved to the end of the area reserved for the boot block.
352 Filesystems created with a newfs of this vintage or later
353 will create the recovery information. If you have a filesystem
354 created prior to this change and wish to have a recovery block
355 created for your filesystem, you can do so by running fsck in
356 foreground mode (i.e., do not use the -p or -y options). As it
357 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
358 to which you should answer yes.
361 As of r321665, an NFSv4 server configuration that services
362 Kerberos mounts or clients that do not support the uid/gid in
363 owner/owner_group string capability, must explicitly enable
364 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
365 machine's /etc/rc.conf file.
368 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
369 Please see the 20141231 entry below for information about prerequisites
370 and upgrading, if you are not already using clang 3.5.0 or higher.
373 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
374 r-commands (rlogin, rsh, etc.) to be built with the base system.
377 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
378 a very major ABI incompatible change, so users of FreeBSD/powerpc must
379 be careful when performing source upgrades. It is best to run
380 'make installworld' from an alternate root system, either a live
381 CD/memory stick, or a temporary root partition. Additionally, all ports
382 must be recompiled. powerpc64 is largely unaffected, except in the case
383 of 32-bit compatibility. All 32-bit binaries will be affected.
386 Forward compatibility for the "ino64" project have been committed. This
387 will allow most new binaries to run on older kernels in a limited
388 fashion. This prevents many of the common foot-shooting actions in the
389 upgrade as well as the limited ability to roll back the kernel across
390 the ino64 upgrade. Complicated use cases may not work properly, though
391 enough simpler ones work to allow recovery in most situations.
394 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
395 if you require the GPL compiler.
398 The internal ABI used for communication between the NFS kernel modules
399 was changed by r320085, so __FreeBSD_version was bumped to
400 ensure all the NFS related modules are updated together.
403 The ABI of struct event was changed by extending the data
404 member to 64bit and adding ext fields. For upgrade, same
405 precautions as for the entry 20170523 "ino64" must be
409 The GNU roff toolchain has been removed from base. To render manpages
410 which are not supported by mandoc(1), man(1) can fallback on GNU roff
411 from ports (and recommends to install it).
412 To render roff(7) documents, consider using GNU roff from ports or the
413 heirloom doctools roff toolchain from ports via pkg install groff or
414 via pkg install heirloom-doctools.
417 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
418 smaller runtime footprint builds. This is useful for embedded systems
419 which only require one chipset support.
421 If you load it as a module, make sure this is in /boot/loader.conf:
425 This will load the HAL, all chip/RF backends and if_ath_pci.
426 If you have if_ath_pci in /boot/loader.conf, ensure it is after
427 if_ath or it will not load any HAL chipset support.
429 If you want to selectively load things (eg on ye cheape ARM/MIPS
430 platforms where RAM is at a premium) you should:
433 * load the chip modules in question
434 * load ath_rate, ath_dfs
436 * load if_ath_pci and/or if_ath_ahb depending upon your particular
437 bus bind type - this is where probe/attach is done.
439 For further comments/feedback, poke adrian@ .
442 The "ino64" 64-bit inode project has been committed, which extends
443 a number of types to 64 bits. Upgrading in place requires care and
444 adherence to the documented upgrade procedure.
446 If using a custom kernel configuration ensure that the
447 COMPAT_FREEBSD11 option is included (as during the upgrade the
448 system will be running the ino64 kernel with the existing world).
450 For the safest in-place upgrade begin by removing previous build
451 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
452 full procedure documented below under the heading "To rebuild
453 everything and install it on the current system." Specifically,
454 a reboot is required after installing the new kernel before
458 The NATM framework including the en(4), fatm(4), hatm(4), and
459 patm(4) devices has been removed. Consumers should plan a
460 migration before the end-of-life date for FreeBSD 11.
463 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
464 diff has not been implemented, if those are needed a newer version of
465 GNU diff is available via the diffutils package under the gdiff name.
468 As of r316810 for ipfilter, keep frags is no longer assumed when
469 keep state is specified in a rule. r316810 aligns ipfilter with
470 documentation in man pages separating keep frags from keep state.
471 This allows keep state to be specified without forcing keep frags
472 and allows keep frags to be specified independently of keep state.
473 To maintain previous behaviour, also specify keep frags with
474 keep state (as documented in ipf.conf.5).
477 arm64 builds now use the base system LLD 4.0.0 linker by default,
478 instead of requiring that the aarch64-binutils port or package be
479 installed. To continue using aarch64-binutils, set
480 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
483 The UDP optimization in entry 20160818 that added the sysctl
484 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
485 packets will no longer be treated as L3 broadcast packets.
488 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
489 use any explicitly assigned loopback address available in the jail
490 instead of using the first assigned address of the jail.
493 The ctl.ko module no longer implements the iSCSI target frontend:
494 cfiscsi.ko does instead.
496 If building cfiscsi.ko as a kernel module, the module can be loaded
497 via one of the following methods:
498 - `cfiscsi_load="YES"` in loader.conf(5).
499 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
500 - ctladm(8)/ctld(8), when compiled with iSCSI support
501 (`WITH_ISCSI=yes` in src.conf(5))
503 Please see cfiscsi(4) for more details.
506 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
507 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
508 same source (previously, the dependency of mmcsd.ko on mmc.ko was
509 missing, but mmcsd.ko now will refuse to load if it is incompatible
513 The syntax of ipfw(8) named states was changed to avoid ambiguity.
514 If you have used named states in the firewall rules, you need to modify
515 them after installworld and before rebooting. Now named states must
516 be prefixed with colon.
519 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
520 removed as the userland we provide cannot use them. The KMS version
521 (sys/dev/drm2) supports the same hardware.
524 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
525 Please see the 20141231 entry below for information about prerequisites
526 and upgrading, if you are not already using clang 3.5.0 or higher.
529 The code that provides support for ZFS .zfs/ directory functionality
530 has been reimplemented. It's not possible now to create a snapshot
531 by mkdir under .zfs/snapshot/. That should be the only user visible
535 EISA bus support has been removed. The WITH_EISA option is no longer
539 MCA bus support has been removed.
542 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
543 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
546 The EM_MULTIQUEUE kernel configuration option is deprecated now that
547 the em(4) driver conforms to iflib specifications.
550 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
551 IFLIB. If you have a custom kernel configuration that excludes em(4)
552 but you use igb(4), you need to re-add em(4) to your custom configuration.
555 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
556 Please see the 20141231 entry below for information about prerequisites
557 and upgrading, if you are not already using clang 3.5.0 or higher.
560 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
561 Please see the 20141231 entry below for information about prerequisites
562 and upgrading, if you are not already using clang 3.5.0 or higher.
565 The layout of the pmap structure has changed for powerpc to put the pmap
566 statistics at the front for all CPU variations. libkvm(3) and all tools
567 that link against it need to be recompiled.
570 isl(4) and cyapa(4) drivers now require a new driver,
571 chromebook_platform(4), to work properly on Chromebook-class hardware.
572 On other types of hardware the drivers may need to be configured using
573 device hints. Please see the corresponding manual pages for details.
576 The urtwn(4) driver was merged into rtwn(4) and now consists of
577 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
579 Also, firmware for RTL8188CE was renamed due to possible name
580 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
583 GNU rcs has been removed from base. It is available as packages:
584 - rcs: Latest GPLv3 GNU rcs version.
585 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
589 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
590 modules now requires that the kernel configuration contain the
591 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
594 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
595 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
598 Relocatable object files with the extension of .So have been renamed
599 to use an extension of .pico instead. The purpose of this change is
600 to avoid a name clash with shared libraries on case-insensitive file
601 systems. On those file systems, foo.So is the same file as foo.so.
604 GNU rcs has been turned off by default. It can (temporarily) be built
605 again by adding WITH_RCS knob in src.conf.
606 Otherwise, GNU rcs is available from packages:
607 - rcs: Latest GPLv3 GNU rcs version.
608 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
611 The backup_uses_rcs functionality has been removed from rc.subr.
614 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
615 two separate components, QUEUE_MACRO_DEBUG_TRACE and
616 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
617 QUEUE_MACRO_DEBUG behavior.
620 r304787 changed some ioctl interfaces between the iSCSI userspace
621 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
622 rebuilt to work with new kernels. __FreeBSD_version has been bumped
626 The UDP receive code has been updated to only treat incoming UDP
627 packets that were addressed to an L2 broadcast address as L3
628 broadcast packets. It is not expected that this will affect any
629 standards-conforming UDP application. The new behaviour can be
630 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
634 Remove the openbsd_poll system call.
635 __FreeBSD_version has been bumped because of this.
638 The libc stub for the pipe(2) system call has been replaced with
639 a wrapper that calls the pipe2(2) system call and the pipe(2)
640 system call is now only implemented by the kernels that include
641 "options COMPAT_FREEBSD10" in their config file (this is the
642 default). Users should ensure that this option is enabled in
643 their kernel or upgrade userspace to r302092 before upgrading their
647 CAM will now strip leading spaces from SCSI disks' serial numbers.
648 This will affect users who create UFS filesystems on SCSI disks using
649 those disk's diskid device nodes. For example, if /etc/fstab
650 previously contained a line like
651 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
652 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
653 transforms like gmirror may also be affected. ZFS users should
657 The bitstring(3) API has been updated with new functionality and
658 improved performance. But it is binary-incompatible with the old API.
659 Objects built with the new headers may not be linked against objects
660 built with the old headers.
663 The brk and sbrk functions have been removed from libc on arm64.
664 Binutils from ports has been updated to not link to these
665 functions and should be updated to the latest version before
666 installing a new libc.
669 The armv6 port now defaults to hard float ABI. Limited support
670 for running both hardfloat and soft float on the same system
671 is available using the libraries installed with -DWITH_LIBSOFT.
672 This has only been tested as an upgrade path for installworld
673 and packages may fail or need manual intervention to run. New
674 packages will be needed.
676 To update an existing self-hosted armv6hf system, you must add
677 TARGET_ARCH=armv6 on the make command line for both the build
678 and the install steps.
681 Kernel modules compiled outside of a kernel build now default to
682 installing to /boot/modules instead of /boot/kernel. Many kernel
683 modules built this way (such as those in ports) already overrode
684 KMODDIR explicitly to install into /boot/modules. However,
685 manually building and installing a module from /sys/modules will
686 now install to /boot/modules instead of /boot/kernel.
689 The CAM I/O scheduler has been committed to the kernel. There should be
690 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
691 list of known rogues that claim support for this but actually corrupt
692 data is believed to be complete, be on the lookout for data
693 corruption. The known rogue list is believed to be complete:
695 o Crucial MX100, M550 drives with MU01 firmware.
696 o Micron M510 and M550 drives with MU01 firmware.
697 o Micron M500 prior to MU07 firmware
698 o Samsung 830, 840, and 850 all firmwares
699 o FCCT M500 all firmwares
701 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
702 with working NCQ TRIM. For Micron branded drives, see your sales rep for
703 updated firmware. Black listed drives will work correctly because these
704 drives work correctly so long as no NCQ TRIMs are sent to them. Given
705 this list is the same as found in Linux, it's believed there are no
706 other rogues in the market place. All other models from the above
709 To be safe, if you are at all concerned, you can quirk each of your
710 drives to prevent NCQ from being sent by setting:
711 kern.cam.ada.X.quirks="0x2"
712 in loader.conf. If the drive requires the 4k sector quirk, set the
716 The FAST_DEPEND build option has been removed and its functionality is
717 now the one true way. The old mkdep(1) style of 'make depend' has
718 been removed. See 20160311 for further details.
721 Resource range types have grown from unsigned long to uintmax_t. All
722 drivers, and anything using libdevinfo, need to be recompiled.
725 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
726 builds. It no longer runs mkdep(1) during 'make depend', and the
727 'make depend' stage can safely be skipped now as it is auto ran
728 when building 'make all' and will generate all SRCS and DPSRCS before
729 building anything else. Dependencies are gathered at compile time with
730 -MF flags kept in separate .depend files per object file. Users should
731 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
735 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
736 kernel modules. Therefore, if you load any kernel modules at boot time,
737 please install the boot loaders after you install the kernel, but before
741 make buildkernel KERNCONF=YOUR_KERNEL_HERE
742 make installkernel KERNCONF=YOUR_KERNEL_HERE
743 make -C sys/boot install
744 <reboot in single user>
746 Then follow the usual steps, described in the General Notes section,
750 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
751 see the 20141231 entry below for information about prerequisites and
752 upgrading, if you are not already using clang 3.5.0 or higher.
755 The AIO subsystem is now a standard part of the kernel. The
756 VFS_AIO kernel option and aio.ko kernel module have been removed.
757 Due to stability concerns, asynchronous I/O requests are only
758 permitted on sockets and raw disks by default. To enable
759 asynchronous I/O requests on all file types, set the
760 vfs.aio.enable_unsafe sysctl to a non-zero value.
763 The ELF object manipulation tool objcopy is now provided by the
764 ELF Tool Chain project rather than by GNU binutils. It should be a
765 drop-in replacement, with the addition of arm64 support. The
766 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
767 to obtain the GNU version if necessary.
770 Building ZFS pools on top of zvols is prohibited by default. That
771 feature has never worked safely; it's always been prone to deadlocks.
772 Using a zvol as the backing store for a VM guest's virtual disk will
773 still work, even if the guest is using ZFS. Legacy behavior can be
774 restored by setting vfs.zfs.vol.recursive=1.
777 The NONE and HPN patches has been removed from OpenSSH. They are
778 still available in the security/openssh-portable port.
781 With the addition of ypldap(8), a new _ypldap user is now required
782 during installworld. "mergemaster -p" can be used to add the user
783 prior to installworld, as documented in the handbook.
786 The tftp loader (pxeboot) now uses the option root-path directive. As a
787 consequence it no longer looks for a pxeboot.4th file on the tftp
788 server. Instead it uses the regular /boot infrastructure as with the
792 The code to start recording plug and play data into the modules has
793 been committed. While the old tools will properly build a new kernel,
794 a number of warnings about "unknown metadata record 4" will be produced
795 for an older kldxref. To avoid such warnings, make sure to rebuild
796 the kernel toolchain (or world). Make sure that you have r292078 or
797 later when trying to build 292077 or later before rebuilding.
800 Debug data files are now built by default with 'make buildworld' and
801 installed with 'make installworld'. This facilitates debugging but
802 requires more disk space both during the build and for the installed
803 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
807 r291527 changed the internal interface between the nfsd.ko and
808 nfscommon.ko modules. As such, they must both be upgraded to-gether.
809 __FreeBSD_version has been bumped because of this.
812 Add support for unicode collation strings leads to a change of
813 order of files listed by ls(1) for example. To get back to the old
814 behaviour, set LC_COLLATE environment variable to "C".
816 Databases administrators will need to reindex their databases given
817 collation results will be different.
819 Due to a bug in install(1) it is recommended to remove the ancient
820 locales before running make installworld.
822 rm -rf /usr/share/locale/*
825 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
826 libcrypto.so.7 or libssl.so.7 must be recompiled.
829 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
830 Kernel modules isp_2400_multi and isp_2500_multi were removed and
831 should be replaced with isp_2400 and isp_2500 modules respectively.
834 The build previously allowed using 'make -n' to not recurse into
835 sub-directories while showing what commands would be executed, and
836 'make -n -n' to recursively show commands. Now 'make -n' will recurse
837 and 'make -N' will not.
840 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
841 and etcupdate will now use this file. A custom sendmail.cf is now
842 updated via this mechanism rather than via installworld. If you had
843 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
844 want to remove the exclusion or change it to "always install".
845 /etc/mail/sendmail.cf is now managed the same way regardless of
846 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
847 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
850 Compatibility shims for legacy ATA device names have been removed.
851 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
852 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
853 environment variables, /dev/ad* and /dev/ar* symbolic links.
856 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
857 Please see the 20141231 entry below for information about prerequisites
858 and upgrading, if you are not already using clang 3.5.0 or higher.
861 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
862 and renamed from .symbols to .debug. This reduces the size requirements
863 on the boot partition or file system and provides consistency with
864 userland debug files.
866 When using the supported kernel installation method the
867 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
868 as is done with /boot/kernel.
870 Developers wishing to maintain the historical behavior of installing
871 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
874 The wireless drivers had undergone changes that remove the 'parent
875 interface' from the ifconfig -l output. The rc.d network scripts
876 used to check presence of a parent interface in the list, so old
877 scripts would fail to start wireless networking. Thus, etcupdate(3)
878 or mergemaster(8) run is required after kernel update, to update your
879 rc.d scripts in /etc.
882 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
883 These configurations are now automatically interpreted as
884 'scrub fragment reassemble'.
887 Kernel-loadable modules for the random(4) device are back. To use
888 them, the kernel must have
891 options RANDOM_LOADABLE
893 kldload(8) can then be used to load random_fortuna.ko
894 or random_yarrow.ko. Please note that due to the indirect
895 function calls that the loadable modules need to provide,
896 the build-in variants will be slightly more efficient.
898 The random(4) kernel option RANDOM_DUMMY has been retired due to
899 unpopularity. It was not all that useful anyway.
902 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
903 Control over building the ELF Tool Chain tools is now provided by
904 the WITHOUT_TOOLCHAIN knob.
907 The polarity of Pulse Per Second (PPS) capture events with the
908 uart(4) driver has been corrected. Prior to this change the PPS
909 "assert" event corresponded to the trailing edge of a positive PPS
910 pulse and the "clear" event was the leading edge of the next pulse.
912 As the width of a PPS pulse in a typical GPS receiver is on the
913 order of 1 millisecond, most users will not notice any significant
914 difference with this change.
916 Anyone who has compensated for the historical polarity reversal by
917 configuring a negative offset equal to the pulse width will need to
918 remove that workaround.
921 The default group assigned to /dev/dri entries has been changed
922 from 'wheel' to 'video' with the id of '44'. If you want to have
923 access to the dri devices please add yourself to the video group
926 # pw groupmod video -m $USER
929 The menu.rc and loader.rc files will now be replaced during
930 upgrades. Please migrate local changes to menu.rc.local and
931 loader.rc.local instead.
934 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
935 strings and strip have been removed. The src.conf(5) knob
936 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
939 As ZFS requires more kernel stack pages than is the default on some
940 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
941 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
943 Please consider using 'options KSTACK_PAGES=X' where X is greater
944 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
947 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
948 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
949 default, i.e., they will not contain "::". For example, instead
950 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
951 to have a more specific match, such as different map entries for
952 IPv6:0:0 vs IPv6:0. This change requires that configuration
953 data (including maps, files, classes, custom ruleset, etc.) must
954 use the same format, so make certain such configuration data is
955 upgrading. As a very simple check search for patterns like
956 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
957 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
958 the cf option UseCompressedIPv6Addresses.
961 The default kernel entropy-processing algorithm is now
962 Fortuna, replacing Yarrow.
964 Assuming you have 'device random' in your kernel config
965 file, the configurations allow a kernel option to override
966 this default. You may choose *ONE* of:
968 options RANDOM_YARROW # Legacy /dev/random algorithm.
969 options RANDOM_DUMMY # Blocking-only driver.
971 If you have neither, you get Fortuna. For most people,
972 read no further, Fortuna will give a /dev/random that works
973 like it always used to, and the difference will be irrelevant.
975 If you remove 'device random', you get *NO* kernel-processed
976 entropy at all. This may be acceptable to folks building
977 embedded systems, but has complications. Carry on reading,
978 and it is assumed you know what you need.
980 *PLEASE* read random(4) and random(9) if you are in the
981 habit of tweaking kernel configs, and/or if you are a member
982 of the embedded community, wanting specific and not-usual
983 behaviour from your security subsystems.
985 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
986 random', you will NOT have a functioning /dev/random, and
987 many cryptographic features will not work, including SSH.
988 You may also find strange behaviour from the random(3) set
989 of library functions, in particular sranddev(3), srandomdev(3)
990 and arc4random(3). The reason for this is that the KERN_ARND
991 sysctl only returns entropy if it thinks it has some to
992 share, and with RANDOM_DUMMY or no 'device random' this
996 An additional fix for the issue described in the 20150614 sendmail
997 entry below has been committed in revision 284717.
1000 FreeBSD's old make (fmake) has been removed from the system. It is
1001 available as the devel/fmake port or via pkg install fmake.
1004 The fix for the issue described in the 20150614 sendmail entry
1005 below has been committed in revision 284436. The work
1006 around described in that entry is no longer needed unless the
1007 default setting is overridden by a confDH_PARAMETERS configuration
1008 setting of '5' or pointing to a 512 bit DH parameter file.
1011 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1012 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1013 and devel/kyua to version 0.20+ and adjust any calling code to work
1014 with Kyuafile and kyua.
1017 The import of openssl to address the FreeBSD-SA-15:10.openssl
1018 security advisory includes a change which rejects handshakes
1019 with DH parameters below 768 bits. sendmail releases prior
1020 to 8.15.2 (not yet released), defaulted to a 512 bit
1021 DH parameter setting for client connections. To work around
1022 this interoperability, sendmail can be configured to use a
1023 2048 bit DH parameter by:
1025 1. Edit /etc/mail/`hostname`.mc
1026 2. If a setting for confDH_PARAMETERS does not exist or
1027 exists and is set to a string beginning with '5',
1028 replace it with '2'.
1029 3. If a setting for confDH_PARAMETERS exists and is set to
1030 a file path, create a new file with:
1031 openssl dhparam -out /path/to/file 2048
1032 4. Rebuild the .cf file:
1033 cd /etc/mail/; make; make install
1034 5. Restart sendmail:
1035 cd /etc/mail/; make restart
1037 A sendmail patch is coming, at which time this file will be
1041 Generation of legacy formatted entries have been disabled by default
1042 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1043 entries were converted to use the new format by default when the new,
1044 machine independent format have been added and supported since FreeBSD
1047 Please see the pwd_mkdb(8) manual page for further details.
1050 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1051 20141231 entry below for information about prerequisites and upgrading,
1052 if you are not already using 3.5.0 or higher.
1055 TI platform code switched to using vendor DTS files and this update
1056 may break existing systems running on Beaglebone, Beaglebone Black,
1059 - dtb files should be regenerated/reinstalled. Filenames are the
1060 same but content is different now
1061 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1062 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1063 addressing scheme is now pin 25 on /dev/gpioc3.
1064 - Pandaboard: /etc/ttys should be updated, serial console device is
1065 now /dev/ttyu2, not /dev/ttyu0
1068 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1069 If you need the GNU extension from groff soelim(1), install groff
1070 from package: pkg install groff, or via ports: textproc/groff.
1073 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1074 defined in symlink(7); previously symlinks were silently ignored.
1077 The const qualifier has been removed from iconv(3) to comply with
1078 POSIX. The ports tree is aware of this from r384038 onwards.
1081 Libraries specified by LIBADD in Makefiles must have a corresponding
1082 DPADD_<lib> variable to ensure correct dependencies. This is now
1083 enforced in src.libnames.mk.
1086 From legacy ata(4) driver was removed support for SATA controllers
1087 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1088 Kernel modules ataahci and ataadaptec were removed completely,
1089 replaced by ahci and mvs modules respectively.
1092 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1093 the 20141231 entry below for information about prerequisites and
1094 upgrading, if you are not already using 3.5.0 or higher.
1097 The 32-bit PowerPC kernel has been changed to a position-independent
1098 executable. This can only be booted with a version of loader(8)
1099 newer than January 31, 2015, so make sure to update both world and
1100 kernel before rebooting.
1103 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1104 but before r278950, the RNG was not seeded properly. Immediately
1105 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1106 ssh keys or openssl keys) that were generated w/ a kernel from that
1107 range. This does not affect programs that directly used /dev/random
1108 or /dev/urandom. All userland uses of arc4random(3) are affected.
1111 The autofs(4) ABI was changed in order to restore binary compatibility
1112 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1113 with the new kernel.
1116 The powerpc64 kernel has been changed to a position-independent
1117 executable. This can only be booted with a new version of loader(8),
1118 so make sure to update both world and kernel before rebooting.
1121 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1122 only release, no new features have been added. Please see the 20141231
1123 entry below for information about prerequisites and upgrading, if you
1124 are not already using 3.5.0.
1127 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1128 taken from the ELF Tool Chain project rather than GNU binutils. They
1129 should be drop-in replacements, with the addition of arm64 support.
1130 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1131 binutils tools, if necessary. See 20150805 for updated information.
1134 The default Unbound configuration now enables remote control
1135 using a local socket. Users who have already enabled the
1136 local_unbound service should regenerate their configuration
1137 by running "service local_unbound setup" as root.
1140 The GNU texinfo and GNU info pages have been removed.
1141 To be able to view GNU info pages please install texinfo from ports.
1144 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1146 As of this release, a prerequisite for building clang, llvm and lldb is
1147 a C++11 capable compiler and C++11 standard library. This means that to
1148 be able to successfully build the cross-tools stage of buildworld, with
1149 clang as the bootstrap compiler, your system compiler or cross compiler
1150 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1151 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1154 On any standard FreeBSD 10.x or 11.x installation, where clang and
1155 libc++ are on by default (that is, on x86 or arm), this should work out
1158 On 9.x installations where clang is enabled by default, e.g. on x86 and
1159 powerpc, libc++ will not be enabled by default, so libc++ should be
1160 built (with clang) and installed first. If both clang and libc++ are
1161 missing, build clang first, then use it to build libc++.
1163 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1164 the instructions for 9.x above.
1166 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1167 default, and do not build clang.
1169 Many embedded systems are resource constrained, and will not be able to
1170 build clang in a reasonable time, or in some cases at all. In those
1171 cases, cross building bootable systems on amd64 is a workaround.
1173 This new version of clang introduces a number of new warnings, of which
1174 the following are most likely to appear:
1178 This warns in two cases, for both C and C++:
1179 * When the code is trying to take the absolute value of an unsigned
1180 quantity, which is effectively a no-op, and almost never what was
1181 intended. The code should be fixed, if at all possible. If you are
1182 sure that the unsigned quantity can be safely cast to signed, without
1183 loss of information or undefined behavior, you can add an explicit
1184 cast, or disable the warning.
1186 * When the code is trying to take an absolute value, but the called
1187 abs() variant is for the wrong type, which can lead to truncation.
1188 If you want to disable the warning instead of fixing the code, please
1189 make sure that truncation will not occur, or it might lead to unwanted
1192 -Wtautological-undefined-compare and
1193 -Wundefined-bool-conversion
1195 These warn when C++ code is trying to compare 'this' against NULL, while
1196 'this' should never be NULL in well-defined C++ code. However, there is
1197 some legacy (pre C++11) code out there, which actively abuses this
1198 feature, which was less strictly defined in previous C++ versions.
1200 Squid and openjdk do this, for example. The warning can be turned off
1201 for C++98 and earlier, but compiling the code in C++11 mode might result
1202 in unexpected behavior; for example, the parts of the program that are
1203 unreachable could be optimized away.
1206 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1207 kernel sources have been removed. The .h files remain, since some
1208 utilities include them. This will need to be fixed later.
1209 If "mount -t oldnfs ..." is attempted, it will fail.
1210 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1211 the utilities will report errors.
1214 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1215 directories to top level SUBDIR variable when their parent
1216 directory is included in LOCAL_DIRS. Users with build systems with
1217 such hierarchies and without SUBDIR entries in the parent
1218 directory Makefiles should add them or add the directories to
1222 faith(4) and faithd(8) have been removed from the base system. Faith
1223 has been obsolete for a very long time.
1226 vt(4), the new console driver, is enabled by default. It brings
1227 support for Unicode and double-width characters, as well as
1228 support for UEFI and integration with the KMS kernel video
1231 You may need to update your console settings in /etc/rc.conf,
1232 most probably the keymap. During boot, /etc/rc.d/syscons will
1233 indicate what you need to do.
1235 vt(4) still has issues and lacks some features compared to
1236 syscons(4). See the wiki for up-to-date information:
1237 https://wiki.freebsd.org/Newcons
1239 If you want to keep using syscons(4), you can do so by adding
1240 the following line to /boot/loader.conf:
1244 pjdfstest has been integrated into kyua as an opt-in test suite.
1245 Please see share/doc/pjdfstest/README for more details on how to
1249 gperf has been removed from the base system for architectures
1250 that use clang. Ports that require gperf will obtain it from the
1254 pjdfstest has been moved from tools/regression/pjdfstest to
1258 At svn r271982, The default linux compat kernel ABI has been adjusted
1259 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1260 update. If you wish to continue using the linux-f10 compat ports,
1261 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1262 encouraged to update their linux-compat packages to linux-c6 during
1263 their next update cycle.
1266 The ofwfb driver, used to provide a graphics console on PowerPC when
1267 using vt(4), no longer allows mmap() of all physical memory. This
1268 will prevent Xorg on PowerPC with some ATI graphics cards from
1269 initializing properly unless x11-servers/xorg-server is updated to
1273 The xdev targets have been converted to using TARGET and
1274 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1277 The default unbound configuration has been modified to address
1278 issues with reverse lookups on networks that use private
1279 address ranges. If you use the local_unbound service, run
1280 "service local_unbound setup" as root to regenerate your
1281 configuration, then "service local_unbound reload" to load the
1285 The GNU texinfo and GNU info pages are not built and installed
1286 anymore, WITH_INFO knob has been added to allow to built and install
1288 UPDATE: see 20150102 entry on texinfo's removal
1291 The GNU readline library is now an INTERNALLIB - that is, it is
1292 statically linked into consumers (GDB and variants) in the base
1293 system, and the shared library is no longer installed. The
1294 devel/readline port is available for third party software that
1298 The Itanium architecture (ia64) has been removed from the list of
1299 known architectures. This is the first step in the removal of the
1303 Commit r268115 has added NFSv4.1 server support, merged from
1304 projects/nfsv4.1-server. Since this includes changes to the
1305 internal interfaces between the NFS related modules, a full
1306 build of the kernel and modules will be necessary.
1307 __FreeBSD_version has been bumped.
1310 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1311 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1312 which differs from the behaviour controlled by this knob.)
1315 Maximal length of the serial number in CTL was increased from 16 to
1316 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1317 and ctld, need to be rebuilt to work with a new kernel.
1320 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1321 1 respectively to match the upstream numbers. They were out of
1322 sync because, when they were originally added to FreeBSD, the
1323 upstream versions were not respected. These libraries are private
1324 and not yet built by default, so renumbering them should be a
1325 non-issue. However, unclean source trees will yield broken test
1326 programs once the operator executes "make delete-old-libs" after a
1327 "make installworld".
1329 Additionally, the atf-sh binary was made private by moving it into
1330 /usr/libexec/. Already-built shell test programs will keep the
1331 path to the old binary so they will break after "make delete-old"
1334 If you are using WITH_TESTS=yes (not the default), wipe the object
1335 tree and rebuild from scratch to prevent spurious test failures.
1336 This is only needed once: the misnumbered libraries and misplaced
1337 binaries have been added to OptionalObsoleteFiles.inc so they will
1338 be removed during a clean upgrade.
1341 Clang and llvm have been upgraded to 3.4.1 release.
1344 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1345 be removed to avoid issues in the future (and has been added to
1349 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1350 past, it affected all builds that used the bsd.*.mk files. The old
1351 behavior was a bug, but people may have relied upon it. To get this
1352 behavior back, you can .include /etc/src.conf from /etc/make.conf
1353 (which is still global and isn't changed). This also changes the
1354 behavior of incremental builds inside the tree of individual
1355 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1356 Although this has survived make universe and some upgrade scenarios,
1357 other upgrade scenarios may have broken. At least one form of
1358 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1359 as well... In cases where MAKESYSPATH isn't working with this
1360 setting, you'll need to set it to the full path to your tree.
1362 One side effect of all this cleaning up is that bsd.compiler.mk
1363 is no longer implicitly included by bsd.own.mk. If you wish to
1364 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1368 The lindev device has been removed since /dev/full has been made a
1369 standard device. __FreeBSD_version has been bumped.
1372 The knob WITHOUT_VI was added to the base system, which controls
1373 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1374 in order to reorder files share/termcap and didn't build ex(1) as a
1375 build tool, so building/installing with WITH_VI is highly advised for
1376 build hosts for older releases.
1378 This issue has been fixed in stable/9 and stable/10 in r277022 and
1379 r276991, respectively.
1382 The YES_HESIOD knob has been removed. It has been obsolete for
1383 a decade. Please move to using WITH_HESIOD instead or your builds
1384 will silently lack HESIOD.
1387 The uart(4) driver has been changed with respect to its handling
1388 of the low-level console. Previously the uart(4) driver prevented
1389 any process from changing the baudrate or the CLOCAL and HUPCL
1390 control flags. By removing the restrictions, operators can make
1391 changes to the serial console port without having to reboot.
1392 However, when getty(8) is started on the serial device that is
1393 associated with the low-level console, a misconfigured terminal
1394 line in /etc/ttys will now have a real impact.
1395 Before upgrading the kernel, make sure that /etc/ttys has the
1396 serial console device configured as 3wire without baudrate to
1397 preserve the previous behaviour. E.g:
1398 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1401 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1402 to improve performance. To re-enable it, if needed, run rpcbind
1403 with command line option -W.
1406 Switched back to the GPL dtc compiler due to updates in the upstream
1407 dts files not being supported by the BSDL dtc compiler. You will need
1408 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1409 may result while building dtb files during a kernel build if you fail
1410 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1413 Clang and llvm have been upgraded to 3.4 release.
1416 The nve(4) driver has been removed. Please use the nfe(4) driver
1417 for NVIDIA nForce MCP Ethernet adapters instead.
1420 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1421 This could cause certain C++ applications using shared libraries built
1422 against the previous version of libc++ to crash. The incompatibility
1423 has now been fixed, but any C++ applications or shared libraries built
1424 between r261283 and r261801 should be recompiled.
1427 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1428 capability mode support. Please note that enabling the feature in
1429 kernel is still highly recommended.
1432 OpenSSH is now built with sandbox support, and will use sandbox as
1433 the default privilege separation method. This requires Capsicum
1434 capability mode support in kernel.
1437 The libelf and libdwarf libraries have been updated to newer
1438 versions from upstream. Shared library version numbers for
1439 these two libraries were bumped. Any ports or binaries
1440 requiring these two libraries should be recompiled.
1441 __FreeBSD_version is bumped to 1100006.
1444 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1445 instead of providing an explicit one, this would prevent such
1446 Makefile from providing its own Kyuafile in the future during
1447 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1448 intervention is needed to clean an objdir if you use NO_CLEAN:
1449 # find /usr/obj -name Kyuafile | xargs rm -f
1452 The behavior of gss_pseudo_random() for the krb5 mechanism
1453 has changed, for applications requesting a longer random string
1454 than produced by the underlying enctype's pseudo-random() function.
1455 In particular, the random string produced from a session key of
1456 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1457 be different at the 17th octet and later, after this change.
1458 The counter used in the PRF+ construction is now encoded as a
1459 big-endian integer in accordance with RFC 4402.
1460 __FreeBSD_version is bumped to 1100004.
1463 The WITHOUT_ATF build knob has been removed and its functionality
1464 has been subsumed into the more generic WITHOUT_TESTS. If you were
1465 using the former to disable the build of the ATF libraries, you
1466 should change your settings to use the latter.
1469 The default version of mtree is nmtree which is obtained from
1470 NetBSD. The output is generally the same, but may vary
1471 slightly. If you found you need identical output adding
1472 "-F freebsd9" to the command line should do the trick. For the
1473 time being, the old mtree is available as fmtree.
1476 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1477 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1478 1.1.4_8 and verify bsdyml not linked in, before running "make
1480 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1482 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1485 The stable/10 branch has been created in subversion from head
1492 Avoid using make -j when upgrading. While generally safe, there are
1493 sometimes problems using -j to upgrade. If your upgrade fails with
1494 -j, please try again without -j. From time to time in the past there
1495 have been problems using -j with buildworld and/or installworld. This
1496 is especially true when upgrading between "distant" versions (eg one
1497 that cross a major release boundary or several minor releases, or when
1498 several months have passed on the -current branch).
1500 Sometimes, obscure build problems are the result of environment
1501 poisoning. This can happen because the make utility reads its
1502 environment when searching for values for global variables. To run
1503 your build attempts in an "environmental clean room", prefix all make
1504 commands with 'env -i '. See the env(1) manual page for more details.
1506 When upgrading from one major version to another it is generally best to
1507 upgrade to the latest code in the currently installed branch first, then
1508 do an upgrade to the new branch. This is the best-tested upgrade path,
1509 and has the highest probability of being successful. Please try this
1510 approach if you encounter problems with a major version upgrade. Since
1511 the stable 4.x branch point, one has generally been able to upgrade from
1512 anywhere in the most recent stable branch to head / current (or even the
1513 last couple of stable branches). See the top of this file when there's
1516 When upgrading a live system, having a root shell around before
1517 installing anything can help undo problems. Not having a root shell
1518 around can lead to problems if pam has changed too much from your
1519 starting point to allow continued authentication after the upgrade.
1521 This file should be read as a log of events. When a later event changes
1522 information of a prior event, the prior event should not be deleted.
1523 Instead, a pointer to the entry with the new information should be
1524 placed in the old entry. Readers of this file should also sanity check
1525 older entries before relying on them blindly. Authors of new entries
1526 should write them with this in mind.
1530 When upgrading the boot ZFS pool to a new version, always follow
1533 1.) recompile and reinstall the ZFS boot loader and boot block
1534 (this is part of "make buildworld" and "make installworld")
1536 2.) update the ZFS boot block on your boot drive
1538 The following example updates the ZFS boot block on the first
1539 partition (freebsd-boot) of a GPT partitioned drive ada0:
1540 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1542 Non-boot pools do not need these updates.
1546 If you are updating from a prior version of FreeBSD (even one just
1547 a few days old), you should follow this procedure. It is the most
1548 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1550 make kernel-toolchain
1551 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1552 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1554 To test a kernel once
1555 ---------------------
1556 If you just want to boot a kernel once (because you are not sure
1557 if it works, or if you want to boot a known bad kernel to provide
1558 debugging information) run
1559 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1560 nextboot -k testkernel
1562 To rebuild everything and install it on the current system.
1563 -----------------------------------------------------------
1564 # Note: sometimes if you are running current you gotta do more than
1565 # is listed here if you are upgrading from a really old current.
1567 <make sure you have good level 0 dumps>
1569 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1570 make installkernel KERNCONF=YOUR_KERNEL_HERE
1572 <reboot in single user> [3]
1579 To cross-install current onto a separate partition
1580 --------------------------------------------------
1581 # In this approach we use a separate partition to hold
1582 # current's root, 'usr', and 'var' directories. A partition
1583 # holding "/", "/usr" and "/var" should be about 2GB in
1586 <make sure you have good level 0 dumps>
1589 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1590 <maybe newfs current's root partition>
1591 <mount current's root partition on directory ${CURRENT_ROOT}>
1592 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1593 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1594 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1595 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1596 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1597 <reboot into current>
1598 <do a "native" rebuild/install as described in the previous section>
1599 <maybe install compatibility libraries from ports/misc/compat*>
1603 To upgrade in-place from stable to current
1604 ----------------------------------------------
1605 <make sure you have good level 0 dumps>
1607 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1608 make installkernel KERNCONF=YOUR_KERNEL_HERE
1610 <reboot in single user> [3]
1617 Make sure that you've read the UPDATING file to understand the
1618 tweaks to various things you need. At this point in the life
1619 cycle of current, things change often and you are on your own
1620 to cope. The defaults can also change, so please read ALL of
1621 the UPDATING entries.
1623 Also, if you are tracking -current, you must be subscribed to
1624 freebsd-current@freebsd.org. Make sure that before you update
1625 your sources that you have read and understood all the recent
1626 messages there. If in doubt, please track -stable which has
1627 much fewer pitfalls.
1629 [1] If you have third party modules, such as vmware, you
1630 should disable them at this point so they don't crash your
1633 [3] From the bootblocks, boot -s, and then do
1638 adjkerntz -i # if CMOS is wall time
1639 Also, when doing a major release upgrade, it is required that
1640 you boot into single user mode to do the installworld.
1642 [4] Note: This step is non-optional. Failure to do this step
1643 can result in a significant reduction in the functionality of the
1644 system. Attempting to do it by hand is not recommended and those
1645 that pursue this avenue should read this file carefully, as well
1646 as the archives of freebsd-current and freebsd-hackers mailing lists
1647 for potential gotchas. The -U option is also useful to consider.
1648 See mergemaster(8) for more information.
1650 [5] Usually this step is a no-op. However, from time to time
1651 you may need to do this if you get unknown user in the following
1652 step. It never hurts to do it all the time. You may need to
1653 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1654 install) after the buildworld before this step if you last updated
1655 from current before 20130425 or from -stable before 20130430.
1657 [6] This only deletes old files and directories. Old libraries
1658 can be deleted by "make delete-old-libs", but you have to make
1659 sure that no program is using those libraries anymore.
1661 [8] In order to have a kernel that can run the 4.x binaries needed to
1662 do an installworld, you must include the COMPAT_FREEBSD4 option in
1663 your kernel. Failure to do so may leave you with a system that is
1664 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1665 required to run the 5.x binaries on more recent kernels. And so on
1666 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1668 Make sure that you merge any new devices from GENERIC since the
1669 last time you updated your kernel config file.
1671 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1672 "?=" instead of the "=" assignment operator, so that buildworld can
1673 override the CPUTYPE if it needs to.
1675 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1676 not on the command line, or in /etc/make.conf. buildworld will
1677 warn if it is improperly defined.
1680 This file contains a list, in reverse chronological order, of major
1681 breakages in tracking -current. It is not guaranteed to be a complete
1682 list of such breakages, and only contains entries since September 23, 2011.
1683 If you need to see UPDATING entries from before that date, you will need
1684 to fetch an UPDATING file from an older FreeBSD release.
1686 Copyright information:
1688 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1690 Redistribution, publication, translation and use, with or without
1691 modification, in full or in part, in any form or format of this
1692 document are permitted without further permission from the author.
1694 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1695 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1696 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1697 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1698 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1699 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1700 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1701 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1702 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1703 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1704 POSSIBILITY OF SUCH DAMAGE.
1706 Contact Warner Losh if you have any questions about your use of