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