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 loader.efi has been augmented to participate more fully in the
36 UEFI boot manager protocol.
39 zfsloader's functionality has now been folded into loader.
40 zfsloader is no longer necesasary once you've updated your
41 boot blocks. For a transition period, we will install a
42 hardlink for zfsloader to loader to allow a smooth transition
43 until the boot blocks can be updated (hard link because old
44 zfs boot blocks don't understand symlinks).
47 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
48 or take steps to update /etc/passwd before doing installworld on
49 existing systems. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
50 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
51 the ntp config file contain options that change file/dir locations.
52 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
53 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
54 taking steps to ensure that all required files/dirs are accessible
58 Big endian arm support has been removed.
61 The static environment setup in kernel configs is no longer mutually
62 exclusive with the loader(8) environment by default. In order to
63 restore the previous default behavior of disabling the loader(8)
64 environment if a static environment is present, you must specify
65 loader_env.disabled=1 in the static environment.
68 The ABI of syscalls used by management tools like sockstat and
69 netstat has been broken to allow 32-bit binaries to work on
70 64-bit kernels without modification. These programs will need
71 to match the kernel in order to function. External programs may
72 require minor modifications to accommodate a change of type in
73 structures from pointers to 64-bit virtual addresses.
76 On i386 and amd64 atomics are now inlined. Out of tree modules using
77 atomics will need to be rebuilt.
80 The '%I' format in the kern.corefile sysctl limits the number of
81 core files that a process can generate to the number stored in the
82 debug.ncores sysctl. The '%I' format is replaced by the single digit
83 index. Previously, if all indexes were taken the kernel would overwrite
84 only a core file with the highest index in a filename.
85 Currently the system will create a new core file if there is a free
86 index or if all slots are taken it will overwrite the oldest one.
89 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
90 6.0.1. Please see the 20141231 entry below for information about
91 prerequisites and upgrading, if you are not already using clang 3.5.0
95 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
96 needed to be changed to work with it. This change was made with r335763
97 and requires a mergemaster / etcupdate / etc to update the installed file.
100 r334930 changed the interface between the NFS modules, so they all
101 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
104 The kernel / userland interface for devinfo changed, so you'll
105 need a new kernel and userland as a pair for it to work (rebuilding
106 lib/libdevinfo is all that's required). devinfo and devmatch will
107 not work, but everything else will when there's a mismatch.
110 The on-disk format for hwpmc callchain records has changed to include
111 threadid corresponding to a given record. This changes the field offsets
112 and thus requires that libpmcstat be rebuilt before using a kernel
116 The vxge(4) driver has been removed. This driver was introduced into
117 HEAD one week before the Exar left the Ethernet market and is not
118 known to be used. If you have device vxge in your kernel config file
122 The amd64 kernel now requires a ld that supports ifunc to produce a
123 working kernel, either lld or a newer binutils. lld is built by default
124 on amd64, and the 'buildkernel' target uses it automatically. However,
125 it is not the default linker, so building the kernel the traditional
126 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
127 binutils port/package). lld will soon be default, and this requirement
131 The nxge(4) driver has been removed. This driver was for PCI-X 10g
132 cards made by s2io/Neterion. The company was aquired by Exar and
133 no longer sells or supports Ethernet products. If you have device
134 nxge in your kernel config file it must be removed.
137 The tz database (tzdb) has been updated to 2018e. This version more
138 correctly models time stamps in time zones with negative DST such as
139 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
140 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
141 time zone abbreviations and the tm_isdst flag.
144 The ixgb(4) driver has been removed. This driver was for an early and
145 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
146 quickly shifted to the long lived ixgbe family. If you have device
147 ixgb in your kernel config file it must be removed.
150 The lmc(4) driver has been removed. This was a WAN interface
151 card that was already reportedly rare in 2003, and had an ambiguous
152 license. If you have device lmc in your kernel config file it must
156 Support for Arcnet networks has been removed. If you have device
157 arcnet or device cm in your kernel config file they must be
161 Support for FDDI networks has been removed. If you have device
162 fddi or device fpa in your kernel config file they must be
166 In addition to supporting RFC 3164 formatted messages, the
167 syslogd(8) service is now capable of parsing RFC 5424 formatted
168 log messages. The main benefit of using RFC 5424 is that clients
169 may now send log messages with timestamps containing year numbers,
170 microseconds and time zone offsets.
172 Similarly, the syslog(3) C library function has been altered to
173 send RFC 5424 formatted messages to the local system logging
174 daemon. On systems using syslogd(8), this change should have no
175 negative impact, as long as syslogd(8) and the C library are
176 updated at the same time. On systems using a different system
177 logging daemon, it may be necessary to make configuration
178 adjustments, depending on the software used.
180 When using syslog-ng, add the 'syslog-protocol' flag to local
181 input sources to enable parsing of RFC 5424 formatted messages:
184 unix-dgram("/var/run/log" flags(syslog-protocol));
187 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
188 of the 'imuxsock' module to let messages be processed by the
189 regular RFC 3164/5424 parsing pipeline:
191 module(load="imuxsock" SysSock.UseSpecialParser="off")
193 Do note that these changes only affect communication between local
194 applications and syslogd(8). The format that syslogd(8) uses to
195 store messages on disk or forward messages to other systems
196 remains unchanged. syslogd(8) still uses RFC 3164 for these
197 purposes. Options to customize this behaviour will be added in the
198 future. Utilities that process log files stored in /var/log are
199 thus expected to continue to function as before.
201 __FreeBSD_version has been incremented to 1200061 to denote this
205 Support for token ring networks has been removed. If you
206 have "device token" in your kernel config you should remove
207 it. No device drivers supported token ring.
210 makefs was modified to be able to tag ISO9660 El Torito boot catalog
211 entries as EFI instead of overloading the i386 tag as done previously.
212 The amd64 mkisoimages.sh script used to build amd64 ISO images for
213 release was updated to use this. This may mean that makefs must be
214 updated before "make cdrom" can be run in the release directory. This
215 should be as simple as:
217 $ cd $SRCDIR/usr.sbin/makefs
218 $ make depend all install
221 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
222 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
223 Co-existance for the transition period will come shortly. Booting is a
224 complex environment and test coverage for Lua-enabled loaders has been
225 thin, so it would be prudent to assume it might not work and make
226 provisions for backup boot methods.
229 devmatch functionality has been turned on in devd. It will automatically
230 load drivers for unattached devices. This may cause unexpected drivers to
231 be loaded. Please report any problems to current@ and imp@freebsd.org.
234 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
235 6.0.0. Please see the 20141231 entry below for information about
236 prerequisites and upgrading, if you are not already using clang 3.5.0
240 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
241 This means it is used to link the kernel and userland libraries and
242 executables, but is not yet installed as /usr/bin/ld by default.
244 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
245 WITHOUT_LLD_BOOTSTRAP=yes
248 On i386, pmtimer has been removed. Its functionality has been folded
249 into apm. It was a no-op on ACPI in current for a while now (but was still
250 needed on i386 in FreeBSD 11 and earlier). Users may need to remove it
251 from kernel config files.
254 The use of RSS hash from the network card aka flowid has been
255 disabled by default for lagg(4) as it's currently incompatible with
256 the lacp and loadbalance protocols.
258 This can be re-enabled by setting the following in loader.conf:
259 net.link.lagg.default_use_flowid="1"
262 The SW_WATCHDOG option is no longer necessary to enable the
263 hardclock-based software watchdog if no hardware watchdog is
264 configured. As before, SW_WATCHDOG will cause the software
265 watchdog to be enabled even if a hardware watchdog is configured.
268 r326887 fixes the issue described in the 20171214 UPDATING entry.
269 r326888 flips the switch back to building GELI support always.
272 r362593 broke ZFS + GELI support for reasons unknown. However,
273 it also broke ZFS support generally, so GELI has been turned off
274 by default as the lesser evil in r326857. If you boot off ZFS and/or
275 GELI, it might not be a good time to update.
278 PowerPC users must update loader(8) by rebuilding world before
279 installing a new kernel, as the protocol connecting them has
280 changed. Without the update, loader metadata will not be passed
281 successfully to the kernel and users will have to enter their
282 root partition at the kernel mountroot prompt to continue booting.
283 Newer versions of loader can boot old kernels without issue.
286 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
287 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
288 to WITH/OUT_LOADER_GELI.
291 The naive and non-compliant support of posix_fallocate(2) in ZFS
292 has been removed as of r325320. The system call now returns EINVAL
293 when used on a ZFS file. Although the new behavior complies with the
294 standard, some consumers are not prepared to cope with it.
295 One known victim is lld prior to r325420.
298 Building in a FreeBSD src checkout will automatically create object
299 directories now rather than store files in the current directory if
300 'make obj' was not ran. Calling 'make obj' is no longer necessary.
301 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
302 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
306 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
307 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
308 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
309 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
310 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
311 The UNIFIED_OBJDIR option is a transitional feature that will be
312 removed for 12.0 release; please migrate to the new format for any
313 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
314 than hardcoding paths.
317 The native-xtools target no longer installs the files by default to the
318 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
319 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
322 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
323 options are changing from controlling the build if defined / undefined
324 to controlling the build with explicit 'yes' or 'no' values. They will
325 shift to WITH/WITHOUT options to match other options in the system.
328 libstand has turned into a private library for sys/boot use only.
329 It is no longer supported as a public interface outside of sys/boot.
332 The arm port has split armv6 into armv6 and armv7. armv7 is now
333 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
334 and are running a kernel from before r324363, you will need to add
335 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
338 When building multiple kernels using KERNCONF, non-existent KERNCONF
339 files will produce an error and buildkernel will fail. Previously
340 missing KERNCONF files silently failed giving no indication as to
341 why, only to subsequently discover during installkernel that the
342 desired kernel was never built in the first place.
345 The default serial number format for CTL LUNs has changed. This will
346 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
347 or iSCSI clients care about their LUNs' serial numbers. Users who
348 require serial number stability should hardcode serial numbers in
352 For 32-bit arm compiled for hard-float support, soft-floating point
353 binaries now always get their shared libraries from
354 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
355 /usr/libsoft also existed). Only users with a hard-float ld.so, but
356 soft-float everything else should be affected.
359 The geli password typed at boot is now hidden. To restore the previous
360 behavior, see geli(8) for configuration options.
363 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
364 sysctl values. Minor nit, but requires a rebuild of both world/kernel
368 "make check" behavior (made in ^/head@r295380) has been changed to
369 execute from a limited sandbox, as opposed to executing from
373 - The "beforecheck" and "aftercheck" targets are now specified.
374 - ${CHECKDIR} (added in commit noted above) has been removed.
375 - Legacy behavior can be enabled by setting
376 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
378 If the limited sandbox mode is enabled, "make check" will execute
379 "make distribution", then install, execute the tests, and clean up the
380 sandbox if successful.
382 The "make distribution" and "make install" targets are typically run as
383 root to set appropriate permissions and ownership at installation time.
384 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
385 environment if executing "make check" with limited sandbox mode using
386 an unprivileged user.
389 Since the switch to GPT disk labels, fsck for UFS/FFS has been
390 unable to automatically find alternate superblocks. As of r322297,
391 the information needed to find alternate superblocks has been
392 moved to the end of the area reserved for the boot block.
393 Filesystems created with a newfs of this vintage or later
394 will create the recovery information. If you have a filesystem
395 created prior to this change and wish to have a recovery block
396 created for your filesystem, you can do so by running fsck in
397 foreground mode (i.e., do not use the -p or -y options). As it
398 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
399 to which you should answer yes.
402 As of r321665, an NFSv4 server configuration that services
403 Kerberos mounts or clients that do not support the uid/gid in
404 owner/owner_group string capability, must explicitly enable
405 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
406 machine's /etc/rc.conf file.
409 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
410 Please see the 20141231 entry below for information about prerequisites
411 and upgrading, if you are not already using clang 3.5.0 or higher.
414 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
415 r-commands (rlogin, rsh, etc.) to be built with the base system.
418 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
419 a very major ABI incompatible change, so users of FreeBSD/powerpc must
420 be careful when performing source upgrades. It is best to run
421 'make installworld' from an alternate root system, either a live
422 CD/memory stick, or a temporary root partition. Additionally, all ports
423 must be recompiled. powerpc64 is largely unaffected, except in the case
424 of 32-bit compatibility. All 32-bit binaries will be affected.
427 Forward compatibility for the "ino64" project have been committed. This
428 will allow most new binaries to run on older kernels in a limited
429 fashion. This prevents many of the common foot-shooting actions in the
430 upgrade as well as the limited ability to roll back the kernel across
431 the ino64 upgrade. Complicated use cases may not work properly, though
432 enough simpler ones work to allow recovery in most situations.
435 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
436 if you require the GPL compiler.
439 The internal ABI used for communication between the NFS kernel modules
440 was changed by r320085, so __FreeBSD_version was bumped to
441 ensure all the NFS related modules are updated together.
444 The ABI of struct event was changed by extending the data
445 member to 64bit and adding ext fields. For upgrade, same
446 precautions as for the entry 20170523 "ino64" must be
450 The GNU roff toolchain has been removed from base. To render manpages
451 which are not supported by mandoc(1), man(1) can fallback on GNU roff
452 from ports (and recommends to install it).
453 To render roff(7) documents, consider using GNU roff from ports or the
454 heirloom doctools roff toolchain from ports via pkg install groff or
455 via pkg install heirloom-doctools.
458 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
459 smaller runtime footprint builds. This is useful for embedded systems
460 which only require one chipset support.
462 If you load it as a module, make sure this is in /boot/loader.conf:
466 This will load the HAL, all chip/RF backends and if_ath_pci.
467 If you have if_ath_pci in /boot/loader.conf, ensure it is after
468 if_ath or it will not load any HAL chipset support.
470 If you want to selectively load things (eg on ye cheape ARM/MIPS
471 platforms where RAM is at a premium) you should:
474 * load the chip modules in question
475 * load ath_rate, ath_dfs
477 * load if_ath_pci and/or if_ath_ahb depending upon your particular
478 bus bind type - this is where probe/attach is done.
480 For further comments/feedback, poke adrian@ .
483 The "ino64" 64-bit inode project has been committed, which extends
484 a number of types to 64 bits. Upgrading in place requires care and
485 adherence to the documented upgrade procedure.
487 If using a custom kernel configuration ensure that the
488 COMPAT_FREEBSD11 option is included (as during the upgrade the
489 system will be running the ino64 kernel with the existing world).
491 For the safest in-place upgrade begin by removing previous build
492 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
493 full procedure documented below under the heading "To rebuild
494 everything and install it on the current system." Specifically,
495 a reboot is required after installing the new kernel before
499 The NATM framework including the en(4), fatm(4), hatm(4), and
500 patm(4) devices has been removed. Consumers should plan a
501 migration before the end-of-life date for FreeBSD 11.
504 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
505 diff has not been implemented, if those are needed a newer version of
506 GNU diff is available via the diffutils package under the gdiff name.
509 As of r316810 for ipfilter, keep frags is no longer assumed when
510 keep state is specified in a rule. r316810 aligns ipfilter with
511 documentation in man pages separating keep frags from keep state.
512 This allows keep state to be specified without forcing keep frags
513 and allows keep frags to be specified independently of keep state.
514 To maintain previous behaviour, also specify keep frags with
515 keep state (as documented in ipf.conf.5).
518 arm64 builds now use the base system LLD 4.0.0 linker by default,
519 instead of requiring that the aarch64-binutils port or package be
520 installed. To continue using aarch64-binutils, set
521 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
524 The UDP optimization in entry 20160818 that added the sysctl
525 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
526 packets will no longer be treated as L3 broadcast packets.
529 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
530 use any explicitly assigned loopback address available in the jail
531 instead of using the first assigned address of the jail.
534 The ctl.ko module no longer implements the iSCSI target frontend:
535 cfiscsi.ko does instead.
537 If building cfiscsi.ko as a kernel module, the module can be loaded
538 via one of the following methods:
539 - `cfiscsi_load="YES"` in loader.conf(5).
540 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
541 - ctladm(8)/ctld(8), when compiled with iSCSI support
542 (`WITH_ISCSI=yes` in src.conf(5))
544 Please see cfiscsi(4) for more details.
547 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
548 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
549 same source (previously, the dependency of mmcsd.ko on mmc.ko was
550 missing, but mmcsd.ko now will refuse to load if it is incompatible
554 The syntax of ipfw(8) named states was changed to avoid ambiguity.
555 If you have used named states in the firewall rules, you need to modify
556 them after installworld and before rebooting. Now named states must
557 be prefixed with colon.
560 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
561 removed as the userland we provide cannot use them. The KMS version
562 (sys/dev/drm2) supports the same hardware.
565 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
566 Please see the 20141231 entry below for information about prerequisites
567 and upgrading, if you are not already using clang 3.5.0 or higher.
570 The code that provides support for ZFS .zfs/ directory functionality
571 has been reimplemented. It's not possible now to create a snapshot
572 by mkdir under .zfs/snapshot/. That should be the only user visible
576 EISA bus support has been removed. The WITH_EISA option is no longer
580 MCA bus support has been removed.
583 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
584 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
587 The EM_MULTIQUEUE kernel configuration option is deprecated now that
588 the em(4) driver conforms to iflib specifications.
591 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
592 IFLIB. If you have a custom kernel configuration that excludes em(4)
593 but you use igb(4), you need to re-add em(4) to your custom configuration.
596 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
597 Please see the 20141231 entry below for information about prerequisites
598 and upgrading, if you are not already using clang 3.5.0 or higher.
601 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
602 Please see the 20141231 entry below for information about prerequisites
603 and upgrading, if you are not already using clang 3.5.0 or higher.
606 The layout of the pmap structure has changed for powerpc to put the pmap
607 statistics at the front for all CPU variations. libkvm(3) and all tools
608 that link against it need to be recompiled.
611 isl(4) and cyapa(4) drivers now require a new driver,
612 chromebook_platform(4), to work properly on Chromebook-class hardware.
613 On other types of hardware the drivers may need to be configured using
614 device hints. Please see the corresponding manual pages for details.
617 The urtwn(4) driver was merged into rtwn(4) and now consists of
618 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
620 Also, firmware for RTL8188CE was renamed due to possible name
621 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
624 GNU rcs has been removed from base. It is available as packages:
625 - rcs: Latest GPLv3 GNU rcs version.
626 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
630 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
631 modules now requires that the kernel configuration contain the
632 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
635 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
636 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
639 Relocatable object files with the extension of .So have been renamed
640 to use an extension of .pico instead. The purpose of this change is
641 to avoid a name clash with shared libraries on case-insensitive file
642 systems. On those file systems, foo.So is the same file as foo.so.
645 GNU rcs has been turned off by default. It can (temporarily) be built
646 again by adding WITH_RCS knob in src.conf.
647 Otherwise, GNU rcs is available from packages:
648 - rcs: Latest GPLv3 GNU rcs version.
649 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
652 The backup_uses_rcs functionality has been removed from rc.subr.
655 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
656 two separate components, QUEUE_MACRO_DEBUG_TRACE and
657 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
658 QUEUE_MACRO_DEBUG behavior.
661 r304787 changed some ioctl interfaces between the iSCSI userspace
662 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
663 rebuilt to work with new kernels. __FreeBSD_version has been bumped
667 The UDP receive code has been updated to only treat incoming UDP
668 packets that were addressed to an L2 broadcast address as L3
669 broadcast packets. It is not expected that this will affect any
670 standards-conforming UDP application. The new behaviour can be
671 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
675 Remove the openbsd_poll system call.
676 __FreeBSD_version has been bumped because of this.
679 The stable/11 branch has been created from head@r302406.
682 The libc stub for the pipe(2) system call has been replaced with
683 a wrapper that calls the pipe2(2) system call and the pipe(2)
684 system call is now only implemented by the kernels that include
685 "options COMPAT_FREEBSD10" in their config file (this is the
686 default). Users should ensure that this option is enabled in
687 their kernel or upgrade userspace to r302092 before upgrading their
691 CAM will now strip leading spaces from SCSI disks' serial numbers.
692 This will affect users who create UFS filesystems on SCSI disks using
693 those disk's diskid device nodes. For example, if /etc/fstab
694 previously contained a line like
695 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
696 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
697 transforms like gmirror may also be affected. ZFS users should
701 The bitstring(3) API has been updated with new functionality and
702 improved performance. But it is binary-incompatible with the old API.
703 Objects built with the new headers may not be linked against objects
704 built with the old headers.
707 The brk and sbrk functions have been removed from libc on arm64.
708 Binutils from ports has been updated to not link to these
709 functions and should be updated to the latest version before
710 installing a new libc.
713 The armv6 port now defaults to hard float ABI. Limited support
714 for running both hardfloat and soft float on the same system
715 is available using the libraries installed with -DWITH_LIBSOFT.
716 This has only been tested as an upgrade path for installworld
717 and packages may fail or need manual intervention to run. New
718 packages will be needed.
720 To update an existing self-hosted armv6hf system, you must add
721 TARGET_ARCH=armv6 on the make command line for both the build
722 and the install steps.
725 Kernel modules compiled outside of a kernel build now default to
726 installing to /boot/modules instead of /boot/kernel. Many kernel
727 modules built this way (such as those in ports) already overrode
728 KMODDIR explicitly to install into /boot/modules. However,
729 manually building and installing a module from /sys/modules will
730 now install to /boot/modules instead of /boot/kernel.
733 The CAM I/O scheduler has been committed to the kernel. There should be
734 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
735 list of known rogues that claim support for this but actually corrupt
736 data is believed to be complete, be on the lookout for data
737 corruption. The known rogue list is believed to be complete:
739 o Crucial MX100, M550 drives with MU01 firmware.
740 o Micron M510 and M550 drives with MU01 firmware.
741 o Micron M500 prior to MU07 firmware
742 o Samsung 830, 840, and 850 all firmwares
743 o FCCT M500 all firmwares
745 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
746 with working NCQ TRIM. For Micron branded drives, see your sales rep for
747 updated firmware. Black listed drives will work correctly because these
748 drives work correctly so long as no NCQ TRIMs are sent to them. Given
749 this list is the same as found in Linux, it's believed there are no
750 other rogues in the market place. All other models from the above
753 To be safe, if you are at all concerned, you can quirk each of your
754 drives to prevent NCQ from being sent by setting:
755 kern.cam.ada.X.quirks="0x2"
756 in loader.conf. If the drive requires the 4k sector quirk, set the
760 The FAST_DEPEND build option has been removed and its functionality is
761 now the one true way. The old mkdep(1) style of 'make depend' has
762 been removed. See 20160311 for further details.
765 Resource range types have grown from unsigned long to uintmax_t. All
766 drivers, and anything using libdevinfo, need to be recompiled.
769 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
770 builds. It no longer runs mkdep(1) during 'make depend', and the
771 'make depend' stage can safely be skipped now as it is auto ran
772 when building 'make all' and will generate all SRCS and DPSRCS before
773 building anything else. Dependencies are gathered at compile time with
774 -MF flags kept in separate .depend files per object file. Users should
775 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
779 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
780 kernel modules. Therefore, if you load any kernel modules at boot time,
781 please install the boot loaders after you install the kernel, but before
785 make buildkernel KERNCONF=YOUR_KERNEL_HERE
786 make installkernel KERNCONF=YOUR_KERNEL_HERE
787 make -C sys/boot install
788 <reboot in single user>
790 Then follow the usual steps, described in the General Notes section,
794 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
795 see the 20141231 entry below for information about prerequisites and
796 upgrading, if you are not already using clang 3.5.0 or higher.
799 The AIO subsystem is now a standard part of the kernel. The
800 VFS_AIO kernel option and aio.ko kernel module have been removed.
801 Due to stability concerns, asynchronous I/O requests are only
802 permitted on sockets and raw disks by default. To enable
803 asynchronous I/O requests on all file types, set the
804 vfs.aio.enable_unsafe sysctl to a non-zero value.
807 The ELF object manipulation tool objcopy is now provided by the
808 ELF Tool Chain project rather than by GNU binutils. It should be a
809 drop-in replacement, with the addition of arm64 support. The
810 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
811 to obtain the GNU version if necessary.
814 Building ZFS pools on top of zvols is prohibited by default. That
815 feature has never worked safely; it's always been prone to deadlocks.
816 Using a zvol as the backing store for a VM guest's virtual disk will
817 still work, even if the guest is using ZFS. Legacy behavior can be
818 restored by setting vfs.zfs.vol.recursive=1.
821 The NONE and HPN patches has been removed from OpenSSH. They are
822 still available in the security/openssh-portable port.
825 With the addition of ypldap(8), a new _ypldap user is now required
826 during installworld. "mergemaster -p" can be used to add the user
827 prior to installworld, as documented in the handbook.
830 The tftp loader (pxeboot) now uses the option root-path directive. As a
831 consequence it no longer looks for a pxeboot.4th file on the tftp
832 server. Instead it uses the regular /boot infrastructure as with the
836 The code to start recording plug and play data into the modules has
837 been committed. While the old tools will properly build a new kernel,
838 a number of warnings about "unknown metadata record 4" will be produced
839 for an older kldxref. To avoid such warnings, make sure to rebuild
840 the kernel toolchain (or world). Make sure that you have r292078 or
841 later when trying to build 292077 or later before rebuilding.
844 Debug data files are now built by default with 'make buildworld' and
845 installed with 'make installworld'. This facilitates debugging but
846 requires more disk space both during the build and for the installed
847 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
851 r291527 changed the internal interface between the nfsd.ko and
852 nfscommon.ko modules. As such, they must both be upgraded to-gether.
853 __FreeBSD_version has been bumped because of this.
856 Add support for unicode collation strings leads to a change of
857 order of files listed by ls(1) for example. To get back to the old
858 behaviour, set LC_COLLATE environment variable to "C".
860 Databases administrators will need to reindex their databases given
861 collation results will be different.
863 Due to a bug in install(1) it is recommended to remove the ancient
864 locales before running make installworld.
866 rm -rf /usr/share/locale/*
869 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
870 libcrypto.so.7 or libssl.so.7 must be recompiled.
873 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
874 Kernel modules isp_2400_multi and isp_2500_multi were removed and
875 should be replaced with isp_2400 and isp_2500 modules respectively.
878 The build previously allowed using 'make -n' to not recurse into
879 sub-directories while showing what commands would be executed, and
880 'make -n -n' to recursively show commands. Now 'make -n' will recurse
881 and 'make -N' will not.
884 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
885 and etcupdate will now use this file. A custom sendmail.cf is now
886 updated via this mechanism rather than via installworld. If you had
887 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
888 want to remove the exclusion or change it to "always install".
889 /etc/mail/sendmail.cf is now managed the same way regardless of
890 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
891 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
894 Compatibility shims for legacy ATA device names have been removed.
895 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
896 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
897 environment variables, /dev/ad* and /dev/ar* symbolic links.
900 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
901 Please see the 20141231 entry below for information about prerequisites
902 and upgrading, if you are not already using clang 3.5.0 or higher.
905 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
906 and renamed from .symbols to .debug. This reduces the size requirements
907 on the boot partition or file system and provides consistency with
908 userland debug files.
910 When using the supported kernel installation method the
911 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
912 as is done with /boot/kernel.
914 Developers wishing to maintain the historical behavior of installing
915 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
918 The wireless drivers had undergone changes that remove the 'parent
919 interface' from the ifconfig -l output. The rc.d network scripts
920 used to check presence of a parent interface in the list, so old
921 scripts would fail to start wireless networking. Thus, etcupdate(3)
922 or mergemaster(8) run is required after kernel update, to update your
923 rc.d scripts in /etc.
926 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
927 These configurations are now automatically interpreted as
928 'scrub fragment reassemble'.
931 Kernel-loadable modules for the random(4) device are back. To use
932 them, the kernel must have
935 options RANDOM_LOADABLE
937 kldload(8) can then be used to load random_fortuna.ko
938 or random_yarrow.ko. Please note that due to the indirect
939 function calls that the loadable modules need to provide,
940 the build-in variants will be slightly more efficient.
942 The random(4) kernel option RANDOM_DUMMY has been retired due to
943 unpopularity. It was not all that useful anyway.
946 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
947 Control over building the ELF Tool Chain tools is now provided by
948 the WITHOUT_TOOLCHAIN knob.
951 The polarity of Pulse Per Second (PPS) capture events with the
952 uart(4) driver has been corrected. Prior to this change the PPS
953 "assert" event corresponded to the trailing edge of a positive PPS
954 pulse and the "clear" event was the leading edge of the next pulse.
956 As the width of a PPS pulse in a typical GPS receiver is on the
957 order of 1 millisecond, most users will not notice any significant
958 difference with this change.
960 Anyone who has compensated for the historical polarity reversal by
961 configuring a negative offset equal to the pulse width will need to
962 remove that workaround.
965 The default group assigned to /dev/dri entries has been changed
966 from 'wheel' to 'video' with the id of '44'. If you want to have
967 access to the dri devices please add yourself to the video group
970 # pw groupmod video -m $USER
973 The menu.rc and loader.rc files will now be replaced during
974 upgrades. Please migrate local changes to menu.rc.local and
975 loader.rc.local instead.
978 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
979 strings and strip have been removed. The src.conf(5) knob
980 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
983 As ZFS requires more kernel stack pages than is the default on some
984 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
985 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
987 Please consider using 'options KSTACK_PAGES=X' where X is greater
988 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
991 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
992 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
993 default, i.e., they will not contain "::". For example, instead
994 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
995 to have a more specific match, such as different map entries for
996 IPv6:0:0 vs IPv6:0. This change requires that configuration
997 data (including maps, files, classes, custom ruleset, etc.) must
998 use the same format, so make certain such configuration data is
999 upgrading. As a very simple check search for patterns like
1000 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1001 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1002 the cf option UseCompressedIPv6Addresses.
1005 The default kernel entropy-processing algorithm is now
1006 Fortuna, replacing Yarrow.
1008 Assuming you have 'device random' in your kernel config
1009 file, the configurations allow a kernel option to override
1010 this default. You may choose *ONE* of:
1012 options RANDOM_YARROW # Legacy /dev/random algorithm.
1013 options RANDOM_DUMMY # Blocking-only driver.
1015 If you have neither, you get Fortuna. For most people,
1016 read no further, Fortuna will give a /dev/random that works
1017 like it always used to, and the difference will be irrelevant.
1019 If you remove 'device random', you get *NO* kernel-processed
1020 entropy at all. This may be acceptable to folks building
1021 embedded systems, but has complications. Carry on reading,
1022 and it is assumed you know what you need.
1024 *PLEASE* read random(4) and random(9) if you are in the
1025 habit of tweaking kernel configs, and/or if you are a member
1026 of the embedded community, wanting specific and not-usual
1027 behaviour from your security subsystems.
1029 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1030 random', you will NOT have a functioning /dev/random, and
1031 many cryptographic features will not work, including SSH.
1032 You may also find strange behaviour from the random(3) set
1033 of library functions, in particular sranddev(3), srandomdev(3)
1034 and arc4random(3). The reason for this is that the KERN_ARND
1035 sysctl only returns entropy if it thinks it has some to
1036 share, and with RANDOM_DUMMY or no 'device random' this
1040 An additional fix for the issue described in the 20150614 sendmail
1041 entry below has been committed in revision 284717.
1044 FreeBSD's old make (fmake) has been removed from the system. It is
1045 available as the devel/fmake port or via pkg install fmake.
1048 The fix for the issue described in the 20150614 sendmail entry
1049 below has been committed in revision 284436. The work
1050 around described in that entry is no longer needed unless the
1051 default setting is overridden by a confDH_PARAMETERS configuration
1052 setting of '5' or pointing to a 512 bit DH parameter file.
1055 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1056 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1057 and devel/kyua to version 0.20+ and adjust any calling code to work
1058 with Kyuafile and kyua.
1061 The import of openssl to address the FreeBSD-SA-15:10.openssl
1062 security advisory includes a change which rejects handshakes
1063 with DH parameters below 768 bits. sendmail releases prior
1064 to 8.15.2 (not yet released), defaulted to a 512 bit
1065 DH parameter setting for client connections. To work around
1066 this interoperability, sendmail can be configured to use a
1067 2048 bit DH parameter by:
1069 1. Edit /etc/mail/`hostname`.mc
1070 2. If a setting for confDH_PARAMETERS does not exist or
1071 exists and is set to a string beginning with '5',
1072 replace it with '2'.
1073 3. If a setting for confDH_PARAMETERS exists and is set to
1074 a file path, create a new file with:
1075 openssl dhparam -out /path/to/file 2048
1076 4. Rebuild the .cf file:
1077 cd /etc/mail/; make; make install
1078 5. Restart sendmail:
1079 cd /etc/mail/; make restart
1081 A sendmail patch is coming, at which time this file will be
1085 Generation of legacy formatted entries have been disabled by default
1086 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1087 entries were converted to use the new format by default when the new,
1088 machine independent format have been added and supported since FreeBSD
1091 Please see the pwd_mkdb(8) manual page for further details.
1094 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1095 20141231 entry below for information about prerequisites and upgrading,
1096 if you are not already using 3.5.0 or higher.
1099 TI platform code switched to using vendor DTS files and this update
1100 may break existing systems running on Beaglebone, Beaglebone Black,
1103 - dtb files should be regenerated/reinstalled. Filenames are the
1104 same but content is different now
1105 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1106 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1107 addressing scheme is now pin 25 on /dev/gpioc3.
1108 - Pandaboard: /etc/ttys should be updated, serial console device is
1109 now /dev/ttyu2, not /dev/ttyu0
1112 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1113 If you need the GNU extension from groff soelim(1), install groff
1114 from package: pkg install groff, or via ports: textproc/groff.
1117 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1118 defined in symlink(7); previously symlinks were silently ignored.
1121 The const qualifier has been removed from iconv(3) to comply with
1122 POSIX. The ports tree is aware of this from r384038 onwards.
1125 Libraries specified by LIBADD in Makefiles must have a corresponding
1126 DPADD_<lib> variable to ensure correct dependencies. This is now
1127 enforced in src.libnames.mk.
1130 From legacy ata(4) driver was removed support for SATA controllers
1131 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1132 Kernel modules ataahci and ataadaptec were removed completely,
1133 replaced by ahci and mvs modules respectively.
1136 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1137 the 20141231 entry below for information about prerequisites and
1138 upgrading, if you are not already using 3.5.0 or higher.
1141 The 32-bit PowerPC kernel has been changed to a position-independent
1142 executable. This can only be booted with a version of loader(8)
1143 newer than January 31, 2015, so make sure to update both world and
1144 kernel before rebooting.
1147 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1148 but before r278950, the RNG was not seeded properly. Immediately
1149 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1150 ssh keys or openssl keys) that were generated w/ a kernel from that
1151 range. This does not affect programs that directly used /dev/random
1152 or /dev/urandom. All userland uses of arc4random(3) are affected.
1155 The autofs(4) ABI was changed in order to restore binary compatibility
1156 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1157 with the new kernel.
1160 The powerpc64 kernel has been changed to a position-independent
1161 executable. This can only be booted with a new version of loader(8),
1162 so make sure to update both world and kernel before rebooting.
1165 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1166 only release, no new features have been added. Please see the 20141231
1167 entry below for information about prerequisites and upgrading, if you
1168 are not already using 3.5.0.
1171 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1172 taken from the ELF Tool Chain project rather than GNU binutils. They
1173 should be drop-in replacements, with the addition of arm64 support.
1174 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1175 binutils tools, if necessary. See 20150805 for updated information.
1178 The default Unbound configuration now enables remote control
1179 using a local socket. Users who have already enabled the
1180 local_unbound service should regenerate their configuration
1181 by running "service local_unbound setup" as root.
1184 The GNU texinfo and GNU info pages have been removed.
1185 To be able to view GNU info pages please install texinfo from ports.
1188 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1190 As of this release, a prerequisite for building clang, llvm and lldb is
1191 a C++11 capable compiler and C++11 standard library. This means that to
1192 be able to successfully build the cross-tools stage of buildworld, with
1193 clang as the bootstrap compiler, your system compiler or cross compiler
1194 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1195 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1198 On any standard FreeBSD 10.x or 11.x installation, where clang and
1199 libc++ are on by default (that is, on x86 or arm), this should work out
1202 On 9.x installations where clang is enabled by default, e.g. on x86 and
1203 powerpc, libc++ will not be enabled by default, so libc++ should be
1204 built (with clang) and installed first. If both clang and libc++ are
1205 missing, build clang first, then use it to build libc++.
1207 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1208 the instructions for 9.x above.
1210 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1211 default, and do not build clang.
1213 Many embedded systems are resource constrained, and will not be able to
1214 build clang in a reasonable time, or in some cases at all. In those
1215 cases, cross building bootable systems on amd64 is a workaround.
1217 This new version of clang introduces a number of new warnings, of which
1218 the following are most likely to appear:
1222 This warns in two cases, for both C and C++:
1223 * When the code is trying to take the absolute value of an unsigned
1224 quantity, which is effectively a no-op, and almost never what was
1225 intended. The code should be fixed, if at all possible. If you are
1226 sure that the unsigned quantity can be safely cast to signed, without
1227 loss of information or undefined behavior, you can add an explicit
1228 cast, or disable the warning.
1230 * When the code is trying to take an absolute value, but the called
1231 abs() variant is for the wrong type, which can lead to truncation.
1232 If you want to disable the warning instead of fixing the code, please
1233 make sure that truncation will not occur, or it might lead to unwanted
1236 -Wtautological-undefined-compare and
1237 -Wundefined-bool-conversion
1239 These warn when C++ code is trying to compare 'this' against NULL, while
1240 'this' should never be NULL in well-defined C++ code. However, there is
1241 some legacy (pre C++11) code out there, which actively abuses this
1242 feature, which was less strictly defined in previous C++ versions.
1244 Squid and openjdk do this, for example. The warning can be turned off
1245 for C++98 and earlier, but compiling the code in C++11 mode might result
1246 in unexpected behavior; for example, the parts of the program that are
1247 unreachable could be optimized away.
1250 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1251 kernel sources have been removed. The .h files remain, since some
1252 utilities include them. This will need to be fixed later.
1253 If "mount -t oldnfs ..." is attempted, it will fail.
1254 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1255 the utilities will report errors.
1258 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1259 directories to top level SUBDIR variable when their parent
1260 directory is included in LOCAL_DIRS. Users with build systems with
1261 such hierarchies and without SUBDIR entries in the parent
1262 directory Makefiles should add them or add the directories to
1266 faith(4) and faithd(8) have been removed from the base system. Faith
1267 has been obsolete for a very long time.
1270 vt(4), the new console driver, is enabled by default. It brings
1271 support for Unicode and double-width characters, as well as
1272 support for UEFI and integration with the KMS kernel video
1275 You may need to update your console settings in /etc/rc.conf,
1276 most probably the keymap. During boot, /etc/rc.d/syscons will
1277 indicate what you need to do.
1279 vt(4) still has issues and lacks some features compared to
1280 syscons(4). See the wiki for up-to-date information:
1281 https://wiki.freebsd.org/Newcons
1283 If you want to keep using syscons(4), you can do so by adding
1284 the following line to /boot/loader.conf:
1288 pjdfstest has been integrated into kyua as an opt-in test suite.
1289 Please see share/doc/pjdfstest/README for more details on how to
1293 gperf has been removed from the base system for architectures
1294 that use clang. Ports that require gperf will obtain it from the
1298 pjdfstest has been moved from tools/regression/pjdfstest to
1302 At svn r271982, The default linux compat kernel ABI has been adjusted
1303 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1304 update. If you wish to continue using the linux-f10 compat ports,
1305 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1306 encouraged to update their linux-compat packages to linux-c6 during
1307 their next update cycle.
1310 The ofwfb driver, used to provide a graphics console on PowerPC when
1311 using vt(4), no longer allows mmap() of all physical memory. This
1312 will prevent Xorg on PowerPC with some ATI graphics cards from
1313 initializing properly unless x11-servers/xorg-server is updated to
1317 The xdev targets have been converted to using TARGET and
1318 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1321 The default unbound configuration has been modified to address
1322 issues with reverse lookups on networks that use private
1323 address ranges. If you use the local_unbound service, run
1324 "service local_unbound setup" as root to regenerate your
1325 configuration, then "service local_unbound reload" to load the
1329 The GNU texinfo and GNU info pages are not built and installed
1330 anymore, WITH_INFO knob has been added to allow to built and install
1332 UPDATE: see 20150102 entry on texinfo's removal
1335 The GNU readline library is now an INTERNALLIB - that is, it is
1336 statically linked into consumers (GDB and variants) in the base
1337 system, and the shared library is no longer installed. The
1338 devel/readline port is available for third party software that
1342 The Itanium architecture (ia64) has been removed from the list of
1343 known architectures. This is the first step in the removal of the
1347 Commit r268115 has added NFSv4.1 server support, merged from
1348 projects/nfsv4.1-server. Since this includes changes to the
1349 internal interfaces between the NFS related modules, a full
1350 build of the kernel and modules will be necessary.
1351 __FreeBSD_version has been bumped.
1354 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1355 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1356 which differs from the behaviour controlled by this knob.)
1359 Maximal length of the serial number in CTL was increased from 16 to
1360 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1361 and ctld, need to be rebuilt to work with a new kernel.
1364 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1365 1 respectively to match the upstream numbers. They were out of
1366 sync because, when they were originally added to FreeBSD, the
1367 upstream versions were not respected. These libraries are private
1368 and not yet built by default, so renumbering them should be a
1369 non-issue. However, unclean source trees will yield broken test
1370 programs once the operator executes "make delete-old-libs" after a
1371 "make installworld".
1373 Additionally, the atf-sh binary was made private by moving it into
1374 /usr/libexec/. Already-built shell test programs will keep the
1375 path to the old binary so they will break after "make delete-old"
1378 If you are using WITH_TESTS=yes (not the default), wipe the object
1379 tree and rebuild from scratch to prevent spurious test failures.
1380 This is only needed once: the misnumbered libraries and misplaced
1381 binaries have been added to OptionalObsoleteFiles.inc so they will
1382 be removed during a clean upgrade.
1385 Clang and llvm have been upgraded to 3.4.1 release.
1388 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1389 be removed to avoid issues in the future (and has been added to
1393 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1394 past, it affected all builds that used the bsd.*.mk files. The old
1395 behavior was a bug, but people may have relied upon it. To get this
1396 behavior back, you can .include /etc/src.conf from /etc/make.conf
1397 (which is still global and isn't changed). This also changes the
1398 behavior of incremental builds inside the tree of individual
1399 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1400 Although this has survived make universe and some upgrade scenarios,
1401 other upgrade scenarios may have broken. At least one form of
1402 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1403 as well... In cases where MAKESYSPATH isn't working with this
1404 setting, you'll need to set it to the full path to your tree.
1406 One side effect of all this cleaning up is that bsd.compiler.mk
1407 is no longer implicitly included by bsd.own.mk. If you wish to
1408 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1412 The lindev device has been removed since /dev/full has been made a
1413 standard device. __FreeBSD_version has been bumped.
1416 The knob WITHOUT_VI was added to the base system, which controls
1417 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1418 in order to reorder files share/termcap and didn't build ex(1) as a
1419 build tool, so building/installing with WITH_VI is highly advised for
1420 build hosts for older releases.
1422 This issue has been fixed in stable/9 and stable/10 in r277022 and
1423 r276991, respectively.
1426 The YES_HESIOD knob has been removed. It has been obsolete for
1427 a decade. Please move to using WITH_HESIOD instead or your builds
1428 will silently lack HESIOD.
1431 The uart(4) driver has been changed with respect to its handling
1432 of the low-level console. Previously the uart(4) driver prevented
1433 any process from changing the baudrate or the CLOCAL and HUPCL
1434 control flags. By removing the restrictions, operators can make
1435 changes to the serial console port without having to reboot.
1436 However, when getty(8) is started on the serial device that is
1437 associated with the low-level console, a misconfigured terminal
1438 line in /etc/ttys will now have a real impact.
1439 Before upgrading the kernel, make sure that /etc/ttys has the
1440 serial console device configured as 3wire without baudrate to
1441 preserve the previous behaviour. E.g:
1442 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1445 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1446 to improve performance. To re-enable it, if needed, run rpcbind
1447 with command line option -W.
1450 Switched back to the GPL dtc compiler due to updates in the upstream
1451 dts files not being supported by the BSDL dtc compiler. You will need
1452 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1453 may result while building dtb files during a kernel build if you fail
1454 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1457 Clang and llvm have been upgraded to 3.4 release.
1460 The nve(4) driver has been removed. Please use the nfe(4) driver
1461 for NVIDIA nForce MCP Ethernet adapters instead.
1464 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1465 This could cause certain C++ applications using shared libraries built
1466 against the previous version of libc++ to crash. The incompatibility
1467 has now been fixed, but any C++ applications or shared libraries built
1468 between r261283 and r261801 should be recompiled.
1471 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1472 capability mode support. Please note that enabling the feature in
1473 kernel is still highly recommended.
1476 OpenSSH is now built with sandbox support, and will use sandbox as
1477 the default privilege separation method. This requires Capsicum
1478 capability mode support in kernel.
1481 The libelf and libdwarf libraries have been updated to newer
1482 versions from upstream. Shared library version numbers for
1483 these two libraries were bumped. Any ports or binaries
1484 requiring these two libraries should be recompiled.
1485 __FreeBSD_version is bumped to 1100006.
1488 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1489 instead of providing an explicit one, this would prevent such
1490 Makefile from providing its own Kyuafile in the future during
1491 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1492 intervention is needed to clean an objdir if you use NO_CLEAN:
1493 # find /usr/obj -name Kyuafile | xargs rm -f
1496 The behavior of gss_pseudo_random() for the krb5 mechanism
1497 has changed, for applications requesting a longer random string
1498 than produced by the underlying enctype's pseudo-random() function.
1499 In particular, the random string produced from a session key of
1500 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1501 be different at the 17th octet and later, after this change.
1502 The counter used in the PRF+ construction is now encoded as a
1503 big-endian integer in accordance with RFC 4402.
1504 __FreeBSD_version is bumped to 1100004.
1507 The WITHOUT_ATF build knob has been removed and its functionality
1508 has been subsumed into the more generic WITHOUT_TESTS. If you were
1509 using the former to disable the build of the ATF libraries, you
1510 should change your settings to use the latter.
1513 The default version of mtree is nmtree which is obtained from
1514 NetBSD. The output is generally the same, but may vary
1515 slightly. If you found you need identical output adding
1516 "-F freebsd9" to the command line should do the trick. For the
1517 time being, the old mtree is available as fmtree.
1520 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1521 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1522 1.1.4_8 and verify bsdyml not linked in, before running "make
1524 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1526 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1529 The stable/10 branch has been created in subversion from head
1536 Avoid using make -j when upgrading. While generally safe, there are
1537 sometimes problems using -j to upgrade. If your upgrade fails with
1538 -j, please try again without -j. From time to time in the past there
1539 have been problems using -j with buildworld and/or installworld. This
1540 is especially true when upgrading between "distant" versions (eg one
1541 that cross a major release boundary or several minor releases, or when
1542 several months have passed on the -current branch).
1544 Sometimes, obscure build problems are the result of environment
1545 poisoning. This can happen because the make utility reads its
1546 environment when searching for values for global variables. To run
1547 your build attempts in an "environmental clean room", prefix all make
1548 commands with 'env -i '. See the env(1) manual page for more details.
1550 When upgrading from one major version to another it is generally best to
1551 upgrade to the latest code in the currently installed branch first, then
1552 do an upgrade to the new branch. This is the best-tested upgrade path,
1553 and has the highest probability of being successful. Please try this
1554 approach if you encounter problems with a major version upgrade. Since
1555 the stable 4.x branch point, one has generally been able to upgrade from
1556 anywhere in the most recent stable branch to head / current (or even the
1557 last couple of stable branches). See the top of this file when there's
1560 When upgrading a live system, having a root shell around before
1561 installing anything can help undo problems. Not having a root shell
1562 around can lead to problems if pam has changed too much from your
1563 starting point to allow continued authentication after the upgrade.
1565 This file should be read as a log of events. When a later event changes
1566 information of a prior event, the prior event should not be deleted.
1567 Instead, a pointer to the entry with the new information should be
1568 placed in the old entry. Readers of this file should also sanity check
1569 older entries before relying on them blindly. Authors of new entries
1570 should write them with this in mind.
1574 When upgrading the boot ZFS pool to a new version, always follow
1577 1.) recompile and reinstall the ZFS boot loader and boot block
1578 (this is part of "make buildworld" and "make installworld")
1580 2.) update the ZFS boot block on your boot drive
1582 The following example updates the ZFS boot block on the first
1583 partition (freebsd-boot) of a GPT partitioned drive ada0:
1584 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1586 Non-boot pools do not need these updates.
1590 If you are updating from a prior version of FreeBSD (even one just
1591 a few days old), you should follow this procedure. It is the most
1592 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1594 make kernel-toolchain
1595 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1596 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1598 To test a kernel once
1599 ---------------------
1600 If you just want to boot a kernel once (because you are not sure
1601 if it works, or if you want to boot a known bad kernel to provide
1602 debugging information) run
1603 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1604 nextboot -k testkernel
1606 To rebuild everything and install it on the current system.
1607 -----------------------------------------------------------
1608 # Note: sometimes if you are running current you gotta do more than
1609 # is listed here if you are upgrading from a really old current.
1611 <make sure you have good level 0 dumps>
1613 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1614 make installkernel KERNCONF=YOUR_KERNEL_HERE
1616 <reboot in single user> [3]
1623 To cross-install current onto a separate partition
1624 --------------------------------------------------
1625 # In this approach we use a separate partition to hold
1626 # current's root, 'usr', and 'var' directories. A partition
1627 # holding "/", "/usr" and "/var" should be about 2GB in
1630 <make sure you have good level 0 dumps>
1633 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1634 <maybe newfs current's root partition>
1635 <mount current's root partition on directory ${CURRENT_ROOT}>
1636 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1637 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1638 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1639 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1640 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1641 <reboot into current>
1642 <do a "native" rebuild/install as described in the previous section>
1643 <maybe install compatibility libraries from ports/misc/compat*>
1647 To upgrade in-place from stable to current
1648 ----------------------------------------------
1649 <make sure you have good level 0 dumps>
1651 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1652 make installkernel KERNCONF=YOUR_KERNEL_HERE
1654 <reboot in single user> [3]
1661 Make sure that you've read the UPDATING file to understand the
1662 tweaks to various things you need. At this point in the life
1663 cycle of current, things change often and you are on your own
1664 to cope. The defaults can also change, so please read ALL of
1665 the UPDATING entries.
1667 Also, if you are tracking -current, you must be subscribed to
1668 freebsd-current@freebsd.org. Make sure that before you update
1669 your sources that you have read and understood all the recent
1670 messages there. If in doubt, please track -stable which has
1671 much fewer pitfalls.
1673 [1] If you have third party modules, such as vmware, you
1674 should disable them at this point so they don't crash your
1677 [3] From the bootblocks, boot -s, and then do
1682 adjkerntz -i # if CMOS is wall time
1683 Also, when doing a major release upgrade, it is required that
1684 you boot into single user mode to do the installworld.
1686 [4] Note: This step is non-optional. Failure to do this step
1687 can result in a significant reduction in the functionality of the
1688 system. Attempting to do it by hand is not recommended and those
1689 that pursue this avenue should read this file carefully, as well
1690 as the archives of freebsd-current and freebsd-hackers mailing lists
1691 for potential gotchas. The -U option is also useful to consider.
1692 See mergemaster(8) for more information.
1694 [5] Usually this step is a no-op. However, from time to time
1695 you may need to do this if you get unknown user in the following
1696 step. It never hurts to do it all the time. You may need to
1697 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1698 install) after the buildworld before this step if you last updated
1699 from current before 20130425 or from -stable before 20130430.
1701 [6] This only deletes old files and directories. Old libraries
1702 can be deleted by "make delete-old-libs", but you have to make
1703 sure that no program is using those libraries anymore.
1705 [8] In order to have a kernel that can run the 4.x binaries needed to
1706 do an installworld, you must include the COMPAT_FREEBSD4 option in
1707 your kernel. Failure to do so may leave you with a system that is
1708 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1709 required to run the 5.x binaries on more recent kernels. And so on
1710 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1712 Make sure that you merge any new devices from GENERIC since the
1713 last time you updated your kernel config file.
1715 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1716 "?=" instead of the "=" assignment operator, so that buildworld can
1717 override the CPUTYPE if it needs to.
1719 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1720 not on the command line, or in /etc/make.conf. buildworld will
1721 warn if it is improperly defined.
1724 This file contains a list, in reverse chronological order, of major
1725 breakages in tracking -current. It is not guaranteed to be a complete
1726 list of such breakages, and only contains entries since September 23, 2011.
1727 If you need to see UPDATING entries from before that date, you will need
1728 to fetch an UPDATING file from an older FreeBSD release.
1730 Copyright information:
1732 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1734 Redistribution, publication, translation and use, with or without
1735 modification, in full or in part, in any form or format of this
1736 document are permitted without further permission from the author.
1738 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1739 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1740 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1741 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1742 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1743 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1744 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1745 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1746 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1747 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1748 POSSIBILITY OF SUCH DAMAGE.
1750 Contact Warner Losh if you have any questions about your use of