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 ixgb(4) driver has been removed. This driver was for an early and
56 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
57 quickly shifted to the long lived ixgbe family. If you have device
58 ixgb in your kernel config file it must be removed.
61 The lmc(4) driver has been removed. This was a WAN interface
62 card that was already reportedly rare in 2003, and had an ambiguous
63 license. If you have device lmc in your kernel config file it must
67 Support for Arcnet networks has been removed. If you have device
68 arcnet or device cm in your kernel config file they must be
72 Support for FDDI networks has been removed. If you have device
73 fddi or device fpa in your kernel config file they must be
77 In addition to supporting RFC 3164 formatted messages, the
78 syslogd(8) service is now capable of parsing RFC 5424 formatted
79 log messages. The main benefit of using RFC 5424 is that clients
80 may now send log messages with timestamps containing year numbers,
81 microseconds and time zone offsets.
83 Similarly, the syslog(3) C library function has been altered to
84 send RFC 5424 formatted messages to the local system logging
85 daemon. On systems using syslogd(8), this change should have no
86 negative impact, as long as syslogd(8) and the C library are
87 updated at the same time. On systems using a different system
88 logging daemon, it may be necessary to make configuration
89 adjustments, depending on the software used.
91 When using syslog-ng, add the 'syslog-protocol' flag to local
92 input sources to enable parsing of RFC 5424 formatted messages:
95 unix-dgram("/var/run/log" flags(syslog-protocol));
98 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
99 of the 'imuxsock' module to let messages be processed by the
100 regular RFC 3164/5424 parsing pipeline:
102 module(load="imuxsock" SysSock.UseSpecialParser="off")
104 Do note that these changes only affect communication between local
105 applications and syslogd(8). The format that syslogd(8) uses to
106 store messages on disk or forward messages to other systems
107 remains unchanged. syslogd(8) still uses RFC 3164 for these
108 purposes. Options to customize this behaviour will be added in the
109 future. Utilities that process log files stored in /var/log are
110 thus expected to continue to function as before.
112 __FreeBSD_version has been incremented to 1200061 to denote this
116 Support for token ring networks has been removed. If you
117 have "device token" in your kernel config you should remove
118 it. No device drivers supported token ring.
121 makefs was modified to be able to tag ISO9660 El Torito boot catalog
122 entries as EFI instead of overloading the i386 tag as done previously.
123 The amd64 mkisoimages.sh script used to build amd64 ISO images for
124 release was updated to use this. This may mean that makefs must be
125 updated before "make cdrom" can be run in the release directory. This
126 should be as simple as:
128 $ cd $SRCDIR/usr.sbin/makefs
129 $ make depend all install
132 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
133 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
134 Co-existance for the transition period will come shortly. Booting is a
135 complex environment and test coverage for Lua-enabled loaders has been
136 thin, so it would be prudent to assume it might not work and make
137 provisions for backup boot methods.
140 devmatch functionality has been turned on in devd. It will automatically
141 load drivers for unattached devices. This may cause unexpected drivers to
142 be loaded. Please report any problems to current@ and imp@freebsd.org.
145 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
146 6.0.0. Please see the 20141231 entry below for information about
147 prerequisites and upgrading, if you are not already using clang 3.5.0
151 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
152 This means it is used to link the kernel and userland libraries and
153 executables, but is not yet installed as /usr/bin/ld by default.
155 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
156 WITHOUT_LLD_BOOTSTRAP=yes
159 On i386, pmtimer has been removed. Its functionality has been folded
160 into apm. It was a no-op on ACPI in current for a while now (but was still
161 needed on i386 in FreeBSD 11 and earlier). Users may need to remove it
162 from kernel config files.
165 The use of RSS hash from the network card aka flowid has been
166 disabled by default for lagg(4) as it's currently incompatible with
167 the lacp and loadbalance protocols.
169 This can be re-enabled by setting the following in loader.conf:
170 net.link.lagg.default_use_flowid="1"
173 The SW_WATCHDOG option is no longer necessary to enable the
174 hardclock-based software watchdog if no hardware watchdog is
175 configured. As before, SW_WATCHDOG will cause the software
176 watchdog to be enabled even if a hardware watchdog is configured.
179 r326887 fixes the issue described in the 20171214 UPDATING entry.
180 r326888 flips the switch back to building GELI support always.
183 r362593 broke ZFS + GELI support for reasons unknown. However,
184 it also broke ZFS support generally, so GELI has been turned off
185 by default as the lesser evil in r326857. If you boot off ZFS and/or
186 GELI, it might not be a good time to update.
189 PowerPC users must update loader(8) by rebuilding world before
190 installing a new kernel, as the protocol connecting them has
191 changed. Without the update, loader metadata will not be passed
192 successfully to the kernel and users will have to enter their
193 root partition at the kernel mountroot prompt to continue booting.
194 Newer versions of loader can boot old kernels without issue.
197 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
198 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
199 to WITH/OUT_LOADER_GELI.
202 The naive and non-compliant support of posix_fallocate(2) in ZFS
203 has been removed as of r325320. The system call now returns EINVAL
204 when used on a ZFS file. Although the new behavior complies with the
205 standard, some consumers are not prepared to cope with it.
206 One known victim is lld prior to r325420.
209 Building in a FreeBSD src checkout will automatically create object
210 directories now rather than store files in the current directory if
211 'make obj' was not ran. Calling 'make obj' is no longer necessary.
212 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
213 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
217 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
218 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
219 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
220 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
221 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
222 The UNIFIED_OBJDIR option is a transitional feature that will be
223 removed for 12.0 release; please migrate to the new format for any
224 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
225 than hardcoding paths.
228 The native-xtools target no longer installs the files by default to the
229 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
230 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
233 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
234 options are changing from controlling the build if defined / undefined
235 to controlling the build with explicit 'yes' or 'no' values. They will
236 shift to WITH/WITHOUT options to match other options in the system.
239 libstand has turned into a private library for sys/boot use only.
240 It is no longer supported as a public interface outside of sys/boot.
243 The arm port has split armv6 into armv6 and armv7. armv7 is now
244 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
245 and are running a kernel from before r324363, you will need to add
246 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
249 When building multiple kernels using KERNCONF, non-existent KERNCONF
250 files will produce an error and buildkernel will fail. Previously
251 missing KERNCONF files silently failed giving no indication as to
252 why, only to subsequently discover during installkernel that the
253 desired kernel was never built in the first place.
256 The default serial number format for CTL LUNs has changed. This will
257 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
258 or iSCSI clients care about their LUNs' serial numbers. Users who
259 require serial number stability should hardcode serial numbers in
263 For 32-bit arm compiled for hard-float support, soft-floating point
264 binaries now always get their shared libraries from
265 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
266 /usr/libsoft also existed). Only users with a hard-float ld.so, but
267 soft-float everything else should be affected.
270 The geli password typed at boot is now hidden. To restore the previous
271 behavior, see geli(8) for configuration options.
274 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
275 sysctl values. Minor nit, but requires a rebuild of both world/kernel
279 "make check" behavior (made in ^/head@r295380) has been changed to
280 execute from a limited sandbox, as opposed to executing from
284 - The "beforecheck" and "aftercheck" targets are now specified.
285 - ${CHECKDIR} (added in commit noted above) has been removed.
286 - Legacy behavior can be enabled by setting
287 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
289 If the limited sandbox mode is enabled, "make check" will execute
290 "make distribution", then install, execute the tests, and clean up the
291 sandbox if successful.
293 The "make distribution" and "make install" targets are typically run as
294 root to set appropriate permissions and ownership at installation time.
295 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
296 environment if executing "make check" with limited sandbox mode using
297 an unprivileged user.
300 Since the switch to GPT disk labels, fsck for UFS/FFS has been
301 unable to automatically find alternate superblocks. As of r322297,
302 the information needed to find alternate superblocks has been
303 moved to the end of the area reserved for the boot block.
304 Filesystems created with a newfs of this vintage or later
305 will create the recovery information. If you have a filesystem
306 created prior to this change and wish to have a recovery block
307 created for your filesystem, you can do so by running fsck in
308 foreground mode (i.e., do not use the -p or -y options). As it
309 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
310 to which you should answer yes.
313 As of r321665, an NFSv4 server configuration that services
314 Kerberos mounts or clients that do not support the uid/gid in
315 owner/owner_group string capability, must explicitly enable
316 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
317 machine's /etc/rc.conf file.
320 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
321 Please see the 20141231 entry below for information about prerequisites
322 and upgrading, if you are not already using clang 3.5.0 or higher.
325 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
326 r-commands (rlogin, rsh, etc.) to be built with the base system.
329 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
330 a very major ABI incompatible change, so users of FreeBSD/powerpc must
331 be careful when performing source upgrades. It is best to run
332 'make installworld' from an alternate root system, either a live
333 CD/memory stick, or a temporary root partition. Additionally, all ports
334 must be recompiled. powerpc64 is largely unaffected, except in the case
335 of 32-bit compatibility. All 32-bit binaries will be affected.
338 Forward compatibility for the "ino64" project have been committed. This
339 will allow most new binaries to run on older kernels in a limited
340 fashion. This prevents many of the common foot-shooting actions in the
341 upgrade as well as the limited ability to roll back the kernel across
342 the ino64 upgrade. Complicated use cases may not work properly, though
343 enough simpler ones work to allow recovery in most situations.
346 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
347 if you require the GPL compiler.
350 The internal ABI used for communication between the NFS kernel modules
351 was changed by r320085, so __FreeBSD_version was bumped to
352 ensure all the NFS related modules are updated together.
355 The ABI of struct event was changed by extending the data
356 member to 64bit and adding ext fields. For upgrade, same
357 precautions as for the entry 20170523 "ino64" must be
361 The GNU roff toolchain has been removed from base. To render manpages
362 which are not supported by mandoc(1), man(1) can fallback on GNU roff
363 from ports (and recommends to install it).
364 To render roff(7) documents, consider using GNU roff from ports or the
365 heirloom doctools roff toolchain from ports via pkg install groff or
366 via pkg install heirloom-doctools.
369 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
370 smaller runtime footprint builds. This is useful for embedded systems
371 which only require one chipset support.
373 If you load it as a module, make sure this is in /boot/loader.conf:
377 This will load the HAL, all chip/RF backends and if_ath_pci.
378 If you have if_ath_pci in /boot/loader.conf, ensure it is after
379 if_ath or it will not load any HAL chipset support.
381 If you want to selectively load things (eg on ye cheape ARM/MIPS
382 platforms where RAM is at a premium) you should:
385 * load the chip modules in question
386 * load ath_rate, ath_dfs
388 * load if_ath_pci and/or if_ath_ahb depending upon your particular
389 bus bind type - this is where probe/attach is done.
391 For further comments/feedback, poke adrian@ .
394 The "ino64" 64-bit inode project has been committed, which extends
395 a number of types to 64 bits. Upgrading in place requires care and
396 adherence to the documented upgrade procedure.
398 If using a custom kernel configuration ensure that the
399 COMPAT_FREEBSD11 option is included (as during the upgrade the
400 system will be running the ino64 kernel with the existing world).
402 For the safest in-place upgrade begin by removing previous build
403 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
404 full procedure documented below under the heading "To rebuild
405 everything and install it on the current system." Specifically,
406 a reboot is required after installing the new kernel before
410 The NATM framework including the en(4), fatm(4), hatm(4), and
411 patm(4) devices has been removed. Consumers should plan a
412 migration before the end-of-life date for FreeBSD 11.
415 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
416 diff has not been implemented, if those are needed a newer version of
417 GNU diff is available via the diffutils package under the gdiff name.
420 As of r316810 for ipfilter, keep frags is no longer assumed when
421 keep state is specified in a rule. r316810 aligns ipfilter with
422 documentation in man pages separating keep frags from keep state.
423 This allows keep state to be specified without forcing keep frags
424 and allows keep frags to be specified independently of keep state.
425 To maintain previous behaviour, also specify keep frags with
426 keep state (as documented in ipf.conf.5).
429 arm64 builds now use the base system LLD 4.0.0 linker by default,
430 instead of requiring that the aarch64-binutils port or package be
431 installed. To continue using aarch64-binutils, set
432 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
435 The UDP optimization in entry 20160818 that added the sysctl
436 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
437 packets will no longer be treated as L3 broadcast packets.
440 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
441 use any explicitly assigned loopback address available in the jail
442 instead of using the first assigned address of the jail.
445 The ctl.ko module no longer implements the iSCSI target frontend:
446 cfiscsi.ko does instead.
448 If building cfiscsi.ko as a kernel module, the module can be loaded
449 via one of the following methods:
450 - `cfiscsi_load="YES"` in loader.conf(5).
451 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
452 - ctladm(8)/ctld(8), when compiled with iSCSI support
453 (`WITH_ISCSI=yes` in src.conf(5))
455 Please see cfiscsi(4) for more details.
458 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
459 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
460 same source (previously, the dependency of mmcsd.ko on mmc.ko was
461 missing, but mmcsd.ko now will refuse to load if it is incompatible
465 The syntax of ipfw(8) named states was changed to avoid ambiguity.
466 If you have used named states in the firewall rules, you need to modify
467 them after installworld and before rebooting. Now named states must
468 be prefixed with colon.
471 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
472 removed as the userland we provide cannot use them. The KMS version
473 (sys/dev/drm2) supports the same hardware.
476 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
477 Please see the 20141231 entry below for information about prerequisites
478 and upgrading, if you are not already using clang 3.5.0 or higher.
481 The code that provides support for ZFS .zfs/ directory functionality
482 has been reimplemented. It's not possible now to create a snapshot
483 by mkdir under .zfs/snapshot/. That should be the only user visible
487 EISA bus support has been removed. The WITH_EISA option is no longer
491 MCA bus support has been removed.
494 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
495 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
498 The EM_MULTIQUEUE kernel configuration option is deprecated now that
499 the em(4) driver conforms to iflib specifications.
502 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
503 IFLIB. If you have a custom kernel configuration that excludes em(4)
504 but you use igb(4), you need to re-add em(4) to your custom configuration.
507 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
508 Please see the 20141231 entry below for information about prerequisites
509 and upgrading, if you are not already using clang 3.5.0 or higher.
512 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
513 Please see the 20141231 entry below for information about prerequisites
514 and upgrading, if you are not already using clang 3.5.0 or higher.
517 The layout of the pmap structure has changed for powerpc to put the pmap
518 statistics at the front for all CPU variations. libkvm(3) and all tools
519 that link against it need to be recompiled.
522 isl(4) and cyapa(4) drivers now require a new driver,
523 chromebook_platform(4), to work properly on Chromebook-class hardware.
524 On other types of hardware the drivers may need to be configured using
525 device hints. Please see the corresponding manual pages for details.
528 The urtwn(4) driver was merged into rtwn(4) and now consists of
529 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
531 Also, firmware for RTL8188CE was renamed due to possible name
532 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
535 GNU rcs has been removed from base. It is available as packages:
536 - rcs: Latest GPLv3 GNU rcs version.
537 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
541 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
542 modules now requires that the kernel configuration contain the
543 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
546 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
547 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
550 Relocatable object files with the extension of .So have been renamed
551 to use an extension of .pico instead. The purpose of this change is
552 to avoid a name clash with shared libraries on case-insensitive file
553 systems. On those file systems, foo.So is the same file as foo.so.
556 GNU rcs has been turned off by default. It can (temporarily) be built
557 again by adding WITH_RCS knob in src.conf.
558 Otherwise, GNU rcs is available from packages:
559 - rcs: Latest GPLv3 GNU rcs version.
560 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
563 The backup_uses_rcs functionality has been removed from rc.subr.
566 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
567 two separate components, QUEUE_MACRO_DEBUG_TRACE and
568 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
569 QUEUE_MACRO_DEBUG behavior.
572 r304787 changed some ioctl interfaces between the iSCSI userspace
573 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
574 rebuilt to work with new kernels. __FreeBSD_version has been bumped
578 The UDP receive code has been updated to only treat incoming UDP
579 packets that were addressed to an L2 broadcast address as L3
580 broadcast packets. It is not expected that this will affect any
581 standards-conforming UDP application. The new behaviour can be
582 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
586 Remove the openbsd_poll system call.
587 __FreeBSD_version has been bumped because of this.
590 The libc stub for the pipe(2) system call has been replaced with
591 a wrapper that calls the pipe2(2) system call and the pipe(2)
592 system call is now only implemented by the kernels that include
593 "options COMPAT_FREEBSD10" in their config file (this is the
594 default). Users should ensure that this option is enabled in
595 their kernel or upgrade userspace to r302092 before upgrading their
599 CAM will now strip leading spaces from SCSI disks' serial numbers.
600 This will affect users who create UFS filesystems on SCSI disks using
601 those disk's diskid device nodes. For example, if /etc/fstab
602 previously contained a line like
603 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
604 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
605 transforms like gmirror may also be affected. ZFS users should
609 The bitstring(3) API has been updated with new functionality and
610 improved performance. But it is binary-incompatible with the old API.
611 Objects built with the new headers may not be linked against objects
612 built with the old headers.
615 The brk and sbrk functions have been removed from libc on arm64.
616 Binutils from ports has been updated to not link to these
617 functions and should be updated to the latest version before
618 installing a new libc.
621 The armv6 port now defaults to hard float ABI. Limited support
622 for running both hardfloat and soft float on the same system
623 is available using the libraries installed with -DWITH_LIBSOFT.
624 This has only been tested as an upgrade path for installworld
625 and packages may fail or need manual intervention to run. New
626 packages will be needed.
628 To update an existing self-hosted armv6hf system, you must add
629 TARGET_ARCH=armv6 on the make command line for both the build
630 and the install steps.
633 Kernel modules compiled outside of a kernel build now default to
634 installing to /boot/modules instead of /boot/kernel. Many kernel
635 modules built this way (such as those in ports) already overrode
636 KMODDIR explicitly to install into /boot/modules. However,
637 manually building and installing a module from /sys/modules will
638 now install to /boot/modules instead of /boot/kernel.
641 The CAM I/O scheduler has been committed to the kernel. There should be
642 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
643 list of known rogues that claim support for this but actually corrupt
644 data is believed to be complete, be on the lookout for data
645 corruption. The known rogue list is believed to be complete:
647 o Crucial MX100, M550 drives with MU01 firmware.
648 o Micron M510 and M550 drives with MU01 firmware.
649 o Micron M500 prior to MU07 firmware
650 o Samsung 830, 840, and 850 all firmwares
651 o FCCT M500 all firmwares
653 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
654 with working NCQ TRIM. For Micron branded drives, see your sales rep for
655 updated firmware. Black listed drives will work correctly because these
656 drives work correctly so long as no NCQ TRIMs are sent to them. Given
657 this list is the same as found in Linux, it's believed there are no
658 other rogues in the market place. All other models from the above
661 To be safe, if you are at all concerned, you can quirk each of your
662 drives to prevent NCQ from being sent by setting:
663 kern.cam.ada.X.quirks="0x2"
664 in loader.conf. If the drive requires the 4k sector quirk, set the
668 The FAST_DEPEND build option has been removed and its functionality is
669 now the one true way. The old mkdep(1) style of 'make depend' has
670 been removed. See 20160311 for further details.
673 Resource range types have grown from unsigned long to uintmax_t. All
674 drivers, and anything using libdevinfo, need to be recompiled.
677 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
678 builds. It no longer runs mkdep(1) during 'make depend', and the
679 'make depend' stage can safely be skipped now as it is auto ran
680 when building 'make all' and will generate all SRCS and DPSRCS before
681 building anything else. Dependencies are gathered at compile time with
682 -MF flags kept in separate .depend files per object file. Users should
683 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
687 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
688 kernel modules. Therefore, if you load any kernel modules at boot time,
689 please install the boot loaders after you install the kernel, but before
693 make buildkernel KERNCONF=YOUR_KERNEL_HERE
694 make installkernel KERNCONF=YOUR_KERNEL_HERE
695 make -C sys/boot install
696 <reboot in single user>
698 Then follow the usual steps, described in the General Notes section,
702 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
703 see the 20141231 entry below for information about prerequisites and
704 upgrading, if you are not already using clang 3.5.0 or higher.
707 The AIO subsystem is now a standard part of the kernel. The
708 VFS_AIO kernel option and aio.ko kernel module have been removed.
709 Due to stability concerns, asynchronous I/O requests are only
710 permitted on sockets and raw disks by default. To enable
711 asynchronous I/O requests on all file types, set the
712 vfs.aio.enable_unsafe sysctl to a non-zero value.
715 The ELF object manipulation tool objcopy is now provided by the
716 ELF Tool Chain project rather than by GNU binutils. It should be a
717 drop-in replacement, with the addition of arm64 support. The
718 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
719 to obtain the GNU version if necessary.
722 Building ZFS pools on top of zvols is prohibited by default. That
723 feature has never worked safely; it's always been prone to deadlocks.
724 Using a zvol as the backing store for a VM guest's virtual disk will
725 still work, even if the guest is using ZFS. Legacy behavior can be
726 restored by setting vfs.zfs.vol.recursive=1.
729 The NONE and HPN patches has been removed from OpenSSH. They are
730 still available in the security/openssh-portable port.
733 With the addition of ypldap(8), a new _ypldap user is now required
734 during installworld. "mergemaster -p" can be used to add the user
735 prior to installworld, as documented in the handbook.
738 The tftp loader (pxeboot) now uses the option root-path directive. As a
739 consequence it no longer looks for a pxeboot.4th file on the tftp
740 server. Instead it uses the regular /boot infrastructure as with the
744 The code to start recording plug and play data into the modules has
745 been committed. While the old tools will properly build a new kernel,
746 a number of warnings about "unknown metadata record 4" will be produced
747 for an older kldxref. To avoid such warnings, make sure to rebuild
748 the kernel toolchain (or world). Make sure that you have r292078 or
749 later when trying to build 292077 or later before rebuilding.
752 Debug data files are now built by default with 'make buildworld' and
753 installed with 'make installworld'. This facilitates debugging but
754 requires more disk space both during the build and for the installed
755 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
759 r291527 changed the internal interface between the nfsd.ko and
760 nfscommon.ko modules. As such, they must both be upgraded to-gether.
761 __FreeBSD_version has been bumped because of this.
764 Add support for unicode collation strings leads to a change of
765 order of files listed by ls(1) for example. To get back to the old
766 behaviour, set LC_COLLATE environment variable to "C".
768 Databases administrators will need to reindex their databases given
769 collation results will be different.
771 Due to a bug in install(1) it is recommended to remove the ancient
772 locales before running make installworld.
774 rm -rf /usr/share/locale/*
777 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
778 libcrypto.so.7 or libssl.so.7 must be recompiled.
781 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
782 Kernel modules isp_2400_multi and isp_2500_multi were removed and
783 should be replaced with isp_2400 and isp_2500 modules respectively.
786 The build previously allowed using 'make -n' to not recurse into
787 sub-directories while showing what commands would be executed, and
788 'make -n -n' to recursively show commands. Now 'make -n' will recurse
789 and 'make -N' will not.
792 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
793 and etcupdate will now use this file. A custom sendmail.cf is now
794 updated via this mechanism rather than via installworld. If you had
795 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
796 want to remove the exclusion or change it to "always install".
797 /etc/mail/sendmail.cf is now managed the same way regardless of
798 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
799 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
802 Compatibility shims for legacy ATA device names have been removed.
803 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
804 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
805 environment variables, /dev/ad* and /dev/ar* symbolic links.
808 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
809 Please see the 20141231 entry below for information about prerequisites
810 and upgrading, if you are not already using clang 3.5.0 or higher.
813 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
814 and renamed from .symbols to .debug. This reduces the size requirements
815 on the boot partition or file system and provides consistency with
816 userland debug files.
818 When using the supported kernel installation method the
819 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
820 as is done with /boot/kernel.
822 Developers wishing to maintain the historical behavior of installing
823 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
826 The wireless drivers had undergone changes that remove the 'parent
827 interface' from the ifconfig -l output. The rc.d network scripts
828 used to check presence of a parent interface in the list, so old
829 scripts would fail to start wireless networking. Thus, etcupdate(3)
830 or mergemaster(8) run is required after kernel update, to update your
831 rc.d scripts in /etc.
834 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
835 These configurations are now automatically interpreted as
836 'scrub fragment reassemble'.
839 Kernel-loadable modules for the random(4) device are back. To use
840 them, the kernel must have
843 options RANDOM_LOADABLE
845 kldload(8) can then be used to load random_fortuna.ko
846 or random_yarrow.ko. Please note that due to the indirect
847 function calls that the loadable modules need to provide,
848 the build-in variants will be slightly more efficient.
850 The random(4) kernel option RANDOM_DUMMY has been retired due to
851 unpopularity. It was not all that useful anyway.
854 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
855 Control over building the ELF Tool Chain tools is now provided by
856 the WITHOUT_TOOLCHAIN knob.
859 The polarity of Pulse Per Second (PPS) capture events with the
860 uart(4) driver has been corrected. Prior to this change the PPS
861 "assert" event corresponded to the trailing edge of a positive PPS
862 pulse and the "clear" event was the leading edge of the next pulse.
864 As the width of a PPS pulse in a typical GPS receiver is on the
865 order of 1 millisecond, most users will not notice any significant
866 difference with this change.
868 Anyone who has compensated for the historical polarity reversal by
869 configuring a negative offset equal to the pulse width will need to
870 remove that workaround.
873 The default group assigned to /dev/dri entries has been changed
874 from 'wheel' to 'video' with the id of '44'. If you want to have
875 access to the dri devices please add yourself to the video group
878 # pw groupmod video -m $USER
881 The menu.rc and loader.rc files will now be replaced during
882 upgrades. Please migrate local changes to menu.rc.local and
883 loader.rc.local instead.
886 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
887 strings and strip have been removed. The src.conf(5) knob
888 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
891 As ZFS requires more kernel stack pages than is the default on some
892 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
893 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
895 Please consider using 'options KSTACK_PAGES=X' where X is greater
896 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
899 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
900 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
901 default, i.e., they will not contain "::". For example, instead
902 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
903 to have a more specific match, such as different map entries for
904 IPv6:0:0 vs IPv6:0. This change requires that configuration
905 data (including maps, files, classes, custom ruleset, etc.) must
906 use the same format, so make certain such configuration data is
907 upgrading. As a very simple check search for patterns like
908 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
909 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
910 the cf option UseCompressedIPv6Addresses.
913 The default kernel entropy-processing algorithm is now
914 Fortuna, replacing Yarrow.
916 Assuming you have 'device random' in your kernel config
917 file, the configurations allow a kernel option to override
918 this default. You may choose *ONE* of:
920 options RANDOM_YARROW # Legacy /dev/random algorithm.
921 options RANDOM_DUMMY # Blocking-only driver.
923 If you have neither, you get Fortuna. For most people,
924 read no further, Fortuna will give a /dev/random that works
925 like it always used to, and the difference will be irrelevant.
927 If you remove 'device random', you get *NO* kernel-processed
928 entropy at all. This may be acceptable to folks building
929 embedded systems, but has complications. Carry on reading,
930 and it is assumed you know what you need.
932 *PLEASE* read random(4) and random(9) if you are in the
933 habit of tweaking kernel configs, and/or if you are a member
934 of the embedded community, wanting specific and not-usual
935 behaviour from your security subsystems.
937 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
938 random', you will NOT have a functioning /dev/random, and
939 many cryptographic features will not work, including SSH.
940 You may also find strange behaviour from the random(3) set
941 of library functions, in particular sranddev(3), srandomdev(3)
942 and arc4random(3). The reason for this is that the KERN_ARND
943 sysctl only returns entropy if it thinks it has some to
944 share, and with RANDOM_DUMMY or no 'device random' this
948 An additional fix for the issue described in the 20150614 sendmail
949 entry below has been committed in revision 284717.
952 FreeBSD's old make (fmake) has been removed from the system. It is
953 available as the devel/fmake port or via pkg install fmake.
956 The fix for the issue described in the 20150614 sendmail entry
957 below has been committed in revision 284436. The work
958 around described in that entry is no longer needed unless the
959 default setting is overridden by a confDH_PARAMETERS configuration
960 setting of '5' or pointing to a 512 bit DH parameter file.
963 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
964 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
965 and devel/kyua to version 0.20+ and adjust any calling code to work
966 with Kyuafile and kyua.
969 The import of openssl to address the FreeBSD-SA-15:10.openssl
970 security advisory includes a change which rejects handshakes
971 with DH parameters below 768 bits. sendmail releases prior
972 to 8.15.2 (not yet released), defaulted to a 512 bit
973 DH parameter setting for client connections. To work around
974 this interoperability, sendmail can be configured to use a
975 2048 bit DH parameter by:
977 1. Edit /etc/mail/`hostname`.mc
978 2. If a setting for confDH_PARAMETERS does not exist or
979 exists and is set to a string beginning with '5',
981 3. If a setting for confDH_PARAMETERS exists and is set to
982 a file path, create a new file with:
983 openssl dhparam -out /path/to/file 2048
984 4. Rebuild the .cf file:
985 cd /etc/mail/; make; make install
987 cd /etc/mail/; make restart
989 A sendmail patch is coming, at which time this file will be
993 Generation of legacy formatted entries have been disabled by default
994 in pwd_mkdb(8), as all base system consumers of the legacy formatted
995 entries were converted to use the new format by default when the new,
996 machine independent format have been added and supported since FreeBSD
999 Please see the pwd_mkdb(8) manual page for further details.
1002 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1003 20141231 entry below for information about prerequisites and upgrading,
1004 if you are not already using 3.5.0 or higher.
1007 TI platform code switched to using vendor DTS files and this update
1008 may break existing systems running on Beaglebone, Beaglebone Black,
1011 - dtb files should be regenerated/reinstalled. Filenames are the
1012 same but content is different now
1013 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1014 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1015 addressing scheme is now pin 25 on /dev/gpioc3.
1016 - Pandaboard: /etc/ttys should be updated, serial console device is
1017 now /dev/ttyu2, not /dev/ttyu0
1020 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1021 If you need the GNU extension from groff soelim(1), install groff
1022 from package: pkg install groff, or via ports: textproc/groff.
1025 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1026 defined in symlink(7); previously symlinks were silently ignored.
1029 The const qualifier has been removed from iconv(3) to comply with
1030 POSIX. The ports tree is aware of this from r384038 onwards.
1033 Libraries specified by LIBADD in Makefiles must have a corresponding
1034 DPADD_<lib> variable to ensure correct dependencies. This is now
1035 enforced in src.libnames.mk.
1038 From legacy ata(4) driver was removed support for SATA controllers
1039 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1040 Kernel modules ataahci and ataadaptec were removed completely,
1041 replaced by ahci and mvs modules respectively.
1044 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1045 the 20141231 entry below for information about prerequisites and
1046 upgrading, if you are not already using 3.5.0 or higher.
1049 The 32-bit PowerPC kernel has been changed to a position-independent
1050 executable. This can only be booted with a version of loader(8)
1051 newer than January 31, 2015, so make sure to update both world and
1052 kernel before rebooting.
1055 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1056 but before r278950, the RNG was not seeded properly. Immediately
1057 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1058 ssh keys or openssl keys) that were generated w/ a kernel from that
1059 range. This does not affect programs that directly used /dev/random
1060 or /dev/urandom. All userland uses of arc4random(3) are affected.
1063 The autofs(4) ABI was changed in order to restore binary compatibility
1064 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1065 with the new kernel.
1068 The powerpc64 kernel has been changed to a position-independent
1069 executable. This can only be booted with a new version of loader(8),
1070 so make sure to update both world and kernel before rebooting.
1073 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1074 only release, no new features have been added. Please see the 20141231
1075 entry below for information about prerequisites and upgrading, if you
1076 are not already using 3.5.0.
1079 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1080 taken from the ELF Tool Chain project rather than GNU binutils. They
1081 should be drop-in replacements, with the addition of arm64 support.
1082 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1083 binutils tools, if necessary. See 20150805 for updated information.
1086 The default Unbound configuration now enables remote control
1087 using a local socket. Users who have already enabled the
1088 local_unbound service should regenerate their configuration
1089 by running "service local_unbound setup" as root.
1092 The GNU texinfo and GNU info pages have been removed.
1093 To be able to view GNU info pages please install texinfo from ports.
1096 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1098 As of this release, a prerequisite for building clang, llvm and lldb is
1099 a C++11 capable compiler and C++11 standard library. This means that to
1100 be able to successfully build the cross-tools stage of buildworld, with
1101 clang as the bootstrap compiler, your system compiler or cross compiler
1102 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1103 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1106 On any standard FreeBSD 10.x or 11.x installation, where clang and
1107 libc++ are on by default (that is, on x86 or arm), this should work out
1110 On 9.x installations where clang is enabled by default, e.g. on x86 and
1111 powerpc, libc++ will not be enabled by default, so libc++ should be
1112 built (with clang) and installed first. If both clang and libc++ are
1113 missing, build clang first, then use it to build libc++.
1115 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1116 the instructions for 9.x above.
1118 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1119 default, and do not build clang.
1121 Many embedded systems are resource constrained, and will not be able to
1122 build clang in a reasonable time, or in some cases at all. In those
1123 cases, cross building bootable systems on amd64 is a workaround.
1125 This new version of clang introduces a number of new warnings, of which
1126 the following are most likely to appear:
1130 This warns in two cases, for both C and C++:
1131 * When the code is trying to take the absolute value of an unsigned
1132 quantity, which is effectively a no-op, and almost never what was
1133 intended. The code should be fixed, if at all possible. If you are
1134 sure that the unsigned quantity can be safely cast to signed, without
1135 loss of information or undefined behavior, you can add an explicit
1136 cast, or disable the warning.
1138 * When the code is trying to take an absolute value, but the called
1139 abs() variant is for the wrong type, which can lead to truncation.
1140 If you want to disable the warning instead of fixing the code, please
1141 make sure that truncation will not occur, or it might lead to unwanted
1144 -Wtautological-undefined-compare and
1145 -Wundefined-bool-conversion
1147 These warn when C++ code is trying to compare 'this' against NULL, while
1148 'this' should never be NULL in well-defined C++ code. However, there is
1149 some legacy (pre C++11) code out there, which actively abuses this
1150 feature, which was less strictly defined in previous C++ versions.
1152 Squid and openjdk do this, for example. The warning can be turned off
1153 for C++98 and earlier, but compiling the code in C++11 mode might result
1154 in unexpected behavior; for example, the parts of the program that are
1155 unreachable could be optimized away.
1158 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1159 kernel sources have been removed. The .h files remain, since some
1160 utilities include them. This will need to be fixed later.
1161 If "mount -t oldnfs ..." is attempted, it will fail.
1162 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1163 the utilities will report errors.
1166 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1167 directories to top level SUBDIR variable when their parent
1168 directory is included in LOCAL_DIRS. Users with build systems with
1169 such hierarchies and without SUBDIR entries in the parent
1170 directory Makefiles should add them or add the directories to
1174 faith(4) and faithd(8) have been removed from the base system. Faith
1175 has been obsolete for a very long time.
1178 vt(4), the new console driver, is enabled by default. It brings
1179 support for Unicode and double-width characters, as well as
1180 support for UEFI and integration with the KMS kernel video
1183 You may need to update your console settings in /etc/rc.conf,
1184 most probably the keymap. During boot, /etc/rc.d/syscons will
1185 indicate what you need to do.
1187 vt(4) still has issues and lacks some features compared to
1188 syscons(4). See the wiki for up-to-date information:
1189 https://wiki.freebsd.org/Newcons
1191 If you want to keep using syscons(4), you can do so by adding
1192 the following line to /boot/loader.conf:
1196 pjdfstest has been integrated into kyua as an opt-in test suite.
1197 Please see share/doc/pjdfstest/README for more details on how to
1201 gperf has been removed from the base system for architectures
1202 that use clang. Ports that require gperf will obtain it from the
1206 pjdfstest has been moved from tools/regression/pjdfstest to
1210 At svn r271982, The default linux compat kernel ABI has been adjusted
1211 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1212 update. If you wish to continue using the linux-f10 compat ports,
1213 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1214 encouraged to update their linux-compat packages to linux-c6 during
1215 their next update cycle.
1218 The ofwfb driver, used to provide a graphics console on PowerPC when
1219 using vt(4), no longer allows mmap() of all physical memory. This
1220 will prevent Xorg on PowerPC with some ATI graphics cards from
1221 initializing properly unless x11-servers/xorg-server is updated to
1225 The xdev targets have been converted to using TARGET and
1226 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1229 The default unbound configuration has been modified to address
1230 issues with reverse lookups on networks that use private
1231 address ranges. If you use the local_unbound service, run
1232 "service local_unbound setup" as root to regenerate your
1233 configuration, then "service local_unbound reload" to load the
1237 The GNU texinfo and GNU info pages are not built and installed
1238 anymore, WITH_INFO knob has been added to allow to built and install
1240 UPDATE: see 20150102 entry on texinfo's removal
1243 The GNU readline library is now an INTERNALLIB - that is, it is
1244 statically linked into consumers (GDB and variants) in the base
1245 system, and the shared library is no longer installed. The
1246 devel/readline port is available for third party software that
1250 The Itanium architecture (ia64) has been removed from the list of
1251 known architectures. This is the first step in the removal of the
1255 Commit r268115 has added NFSv4.1 server support, merged from
1256 projects/nfsv4.1-server. Since this includes changes to the
1257 internal interfaces between the NFS related modules, a full
1258 build of the kernel and modules will be necessary.
1259 __FreeBSD_version has been bumped.
1262 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1263 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1264 which differs from the behaviour controlled by this knob.)
1267 Maximal length of the serial number in CTL was increased from 16 to
1268 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1269 and ctld, need to be rebuilt to work with a new kernel.
1272 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1273 1 respectively to match the upstream numbers. They were out of
1274 sync because, when they were originally added to FreeBSD, the
1275 upstream versions were not respected. These libraries are private
1276 and not yet built by default, so renumbering them should be a
1277 non-issue. However, unclean source trees will yield broken test
1278 programs once the operator executes "make delete-old-libs" after a
1279 "make installworld".
1281 Additionally, the atf-sh binary was made private by moving it into
1282 /usr/libexec/. Already-built shell test programs will keep the
1283 path to the old binary so they will break after "make delete-old"
1286 If you are using WITH_TESTS=yes (not the default), wipe the object
1287 tree and rebuild from scratch to prevent spurious test failures.
1288 This is only needed once: the misnumbered libraries and misplaced
1289 binaries have been added to OptionalObsoleteFiles.inc so they will
1290 be removed during a clean upgrade.
1293 Clang and llvm have been upgraded to 3.4.1 release.
1296 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1297 be removed to avoid issues in the future (and has been added to
1301 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1302 past, it affected all builds that used the bsd.*.mk files. The old
1303 behavior was a bug, but people may have relied upon it. To get this
1304 behavior back, you can .include /etc/src.conf from /etc/make.conf
1305 (which is still global and isn't changed). This also changes the
1306 behavior of incremental builds inside the tree of individual
1307 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1308 Although this has survived make universe and some upgrade scenarios,
1309 other upgrade scenarios may have broken. At least one form of
1310 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1311 as well... In cases where MAKESYSPATH isn't working with this
1312 setting, you'll need to set it to the full path to your tree.
1314 One side effect of all this cleaning up is that bsd.compiler.mk
1315 is no longer implicitly included by bsd.own.mk. If you wish to
1316 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1320 The lindev device has been removed since /dev/full has been made a
1321 standard device. __FreeBSD_version has been bumped.
1324 The knob WITHOUT_VI was added to the base system, which controls
1325 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1326 in order to reorder files share/termcap and didn't build ex(1) as a
1327 build tool, so building/installing with WITH_VI is highly advised for
1328 build hosts for older releases.
1330 This issue has been fixed in stable/9 and stable/10 in r277022 and
1331 r276991, respectively.
1334 The YES_HESIOD knob has been removed. It has been obsolete for
1335 a decade. Please move to using WITH_HESIOD instead or your builds
1336 will silently lack HESIOD.
1339 The uart(4) driver has been changed with respect to its handling
1340 of the low-level console. Previously the uart(4) driver prevented
1341 any process from changing the baudrate or the CLOCAL and HUPCL
1342 control flags. By removing the restrictions, operators can make
1343 changes to the serial console port without having to reboot.
1344 However, when getty(8) is started on the serial device that is
1345 associated with the low-level console, a misconfigured terminal
1346 line in /etc/ttys will now have a real impact.
1347 Before upgrading the kernel, make sure that /etc/ttys has the
1348 serial console device configured as 3wire without baudrate to
1349 preserve the previous behaviour. E.g:
1350 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1353 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1354 to improve performance. To re-enable it, if needed, run rpcbind
1355 with command line option -W.
1358 Switched back to the GPL dtc compiler due to updates in the upstream
1359 dts files not being supported by the BSDL dtc compiler. You will need
1360 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1361 may result while building dtb files during a kernel build if you fail
1362 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1365 Clang and llvm have been upgraded to 3.4 release.
1368 The nve(4) driver has been removed. Please use the nfe(4) driver
1369 for NVIDIA nForce MCP Ethernet adapters instead.
1372 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1373 This could cause certain C++ applications using shared libraries built
1374 against the previous version of libc++ to crash. The incompatibility
1375 has now been fixed, but any C++ applications or shared libraries built
1376 between r261283 and r261801 should be recompiled.
1379 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1380 capability mode support. Please note that enabling the feature in
1381 kernel is still highly recommended.
1384 OpenSSH is now built with sandbox support, and will use sandbox as
1385 the default privilege separation method. This requires Capsicum
1386 capability mode support in kernel.
1389 The libelf and libdwarf libraries have been updated to newer
1390 versions from upstream. Shared library version numbers for
1391 these two libraries were bumped. Any ports or binaries
1392 requiring these two libraries should be recompiled.
1393 __FreeBSD_version is bumped to 1100006.
1396 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1397 instead of providing an explicit one, this would prevent such
1398 Makefile from providing its own Kyuafile in the future during
1399 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1400 intervention is needed to clean an objdir if you use NO_CLEAN:
1401 # find /usr/obj -name Kyuafile | xargs rm -f
1404 The behavior of gss_pseudo_random() for the krb5 mechanism
1405 has changed, for applications requesting a longer random string
1406 than produced by the underlying enctype's pseudo-random() function.
1407 In particular, the random string produced from a session key of
1408 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1409 be different at the 17th octet and later, after this change.
1410 The counter used in the PRF+ construction is now encoded as a
1411 big-endian integer in accordance with RFC 4402.
1412 __FreeBSD_version is bumped to 1100004.
1415 The WITHOUT_ATF build knob has been removed and its functionality
1416 has been subsumed into the more generic WITHOUT_TESTS. If you were
1417 using the former to disable the build of the ATF libraries, you
1418 should change your settings to use the latter.
1421 The default version of mtree is nmtree which is obtained from
1422 NetBSD. The output is generally the same, but may vary
1423 slightly. If you found you need identical output adding
1424 "-F freebsd9" to the command line should do the trick. For the
1425 time being, the old mtree is available as fmtree.
1428 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1429 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1430 1.1.4_8 and verify bsdyml not linked in, before running "make
1432 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1434 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1437 The stable/10 branch has been created in subversion from head
1444 Avoid using make -j when upgrading. While generally safe, there are
1445 sometimes problems using -j to upgrade. If your upgrade fails with
1446 -j, please try again without -j. From time to time in the past there
1447 have been problems using -j with buildworld and/or installworld. This
1448 is especially true when upgrading between "distant" versions (eg one
1449 that cross a major release boundary or several minor releases, or when
1450 several months have passed on the -current branch).
1452 Sometimes, obscure build problems are the result of environment
1453 poisoning. This can happen because the make utility reads its
1454 environment when searching for values for global variables. To run
1455 your build attempts in an "environmental clean room", prefix all make
1456 commands with 'env -i '. See the env(1) manual page for more details.
1458 When upgrading from one major version to another it is generally best to
1459 upgrade to the latest code in the currently installed branch first, then
1460 do an upgrade to the new branch. This is the best-tested upgrade path,
1461 and has the highest probability of being successful. Please try this
1462 approach if you encounter problems with a major version upgrade. Since
1463 the stable 4.x branch point, one has generally been able to upgrade from
1464 anywhere in the most recent stable branch to head / current (or even the
1465 last couple of stable branches). See the top of this file when there's
1468 When upgrading a live system, having a root shell around before
1469 installing anything can help undo problems. Not having a root shell
1470 around can lead to problems if pam has changed too much from your
1471 starting point to allow continued authentication after the upgrade.
1473 This file should be read as a log of events. When a later event changes
1474 information of a prior event, the prior event should not be deleted.
1475 Instead, a pointer to the entry with the new information should be
1476 placed in the old entry. Readers of this file should also sanity check
1477 older entries before relying on them blindly. Authors of new entries
1478 should write them with this in mind.
1482 When upgrading the boot ZFS pool to a new version, always follow
1485 1.) recompile and reinstall the ZFS boot loader and boot block
1486 (this is part of "make buildworld" and "make installworld")
1488 2.) update the ZFS boot block on your boot drive
1490 The following example updates the ZFS boot block on the first
1491 partition (freebsd-boot) of a GPT partitioned drive ada0:
1492 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1494 Non-boot pools do not need these updates.
1498 If you are updating from a prior version of FreeBSD (even one just
1499 a few days old), you should follow this procedure. It is the most
1500 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1502 make kernel-toolchain
1503 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1504 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1506 To test a kernel once
1507 ---------------------
1508 If you just want to boot a kernel once (because you are not sure
1509 if it works, or if you want to boot a known bad kernel to provide
1510 debugging information) run
1511 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1512 nextboot -k testkernel
1514 To rebuild everything and install it on the current system.
1515 -----------------------------------------------------------
1516 # Note: sometimes if you are running current you gotta do more than
1517 # is listed here if you are upgrading from a really old current.
1519 <make sure you have good level 0 dumps>
1521 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1522 make installkernel KERNCONF=YOUR_KERNEL_HERE
1524 <reboot in single user> [3]
1531 To cross-install current onto a separate partition
1532 --------------------------------------------------
1533 # In this approach we use a separate partition to hold
1534 # current's root, 'usr', and 'var' directories. A partition
1535 # holding "/", "/usr" and "/var" should be about 2GB in
1538 <make sure you have good level 0 dumps>
1541 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1542 <maybe newfs current's root partition>
1543 <mount current's root partition on directory ${CURRENT_ROOT}>
1544 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1545 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1546 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1547 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1548 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1549 <reboot into current>
1550 <do a "native" rebuild/install as described in the previous section>
1551 <maybe install compatibility libraries from ports/misc/compat*>
1555 To upgrade in-place from stable to current
1556 ----------------------------------------------
1557 <make sure you have good level 0 dumps>
1559 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1560 make installkernel KERNCONF=YOUR_KERNEL_HERE
1562 <reboot in single user> [3]
1569 Make sure that you've read the UPDATING file to understand the
1570 tweaks to various things you need. At this point in the life
1571 cycle of current, things change often and you are on your own
1572 to cope. The defaults can also change, so please read ALL of
1573 the UPDATING entries.
1575 Also, if you are tracking -current, you must be subscribed to
1576 freebsd-current@freebsd.org. Make sure that before you update
1577 your sources that you have read and understood all the recent
1578 messages there. If in doubt, please track -stable which has
1579 much fewer pitfalls.
1581 [1] If you have third party modules, such as vmware, you
1582 should disable them at this point so they don't crash your
1585 [3] From the bootblocks, boot -s, and then do
1590 adjkerntz -i # if CMOS is wall time
1591 Also, when doing a major release upgrade, it is required that
1592 you boot into single user mode to do the installworld.
1594 [4] Note: This step is non-optional. Failure to do this step
1595 can result in a significant reduction in the functionality of the
1596 system. Attempting to do it by hand is not recommended and those
1597 that pursue this avenue should read this file carefully, as well
1598 as the archives of freebsd-current and freebsd-hackers mailing lists
1599 for potential gotchas. The -U option is also useful to consider.
1600 See mergemaster(8) for more information.
1602 [5] Usually this step is a no-op. However, from time to time
1603 you may need to do this if you get unknown user in the following
1604 step. It never hurts to do it all the time. You may need to
1605 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1606 install) after the buildworld before this step if you last updated
1607 from current before 20130425 or from -stable before 20130430.
1609 [6] This only deletes old files and directories. Old libraries
1610 can be deleted by "make delete-old-libs", but you have to make
1611 sure that no program is using those libraries anymore.
1613 [8] In order to have a kernel that can run the 4.x binaries needed to
1614 do an installworld, you must include the COMPAT_FREEBSD4 option in
1615 your kernel. Failure to do so may leave you with a system that is
1616 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1617 required to run the 5.x binaries on more recent kernels. And so on
1618 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1620 Make sure that you merge any new devices from GENERIC since the
1621 last time you updated your kernel config file.
1623 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1624 "?=" instead of the "=" assignment operator, so that buildworld can
1625 override the CPUTYPE if it needs to.
1627 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1628 not on the command line, or in /etc/make.conf. buildworld will
1629 warn if it is improperly defined.
1632 This file contains a list, in reverse chronological order, of major
1633 breakages in tracking -current. It is not guaranteed to be a complete
1634 list of such breakages, and only contains entries since September 23, 2011.
1635 If you need to see UPDATING entries from before that date, you will need
1636 to fetch an UPDATING file from an older FreeBSD release.
1638 Copyright information:
1640 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1642 Redistribution, publication, translation and use, with or without
1643 modification, in full or in part, in any form or format of this
1644 document are permitted without further permission from the author.
1646 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1647 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1648 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1649 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1650 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1651 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1652 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1653 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1654 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1655 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1656 POSSIBILITY OF SUCH DAMAGE.
1658 Contact Warner Losh if you have any questions about your use of