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