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