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