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/makeworld.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 The ABI of syscalls used by management tools like sockstat and
36 netstat has been broken to allow 32-bit binaries to work on
37 64-bit kernels without modification. These programs will need
38 to match the kernel in order to function. External programs may
39 require minor modifications to accommodate a change of type in
40 structures from pointers to 64-bit virtual addresses.
43 On i386 and amd64 atomics are now inlined. Out of tree modules using
44 atomics will need to be rebuilt.
47 The '%I' format in the kern.corefile sysctl limits the number of
48 core files that a process can generate to the number stored in the
49 debug.ncores sysctl. The '%I' format is replaced by the single digit
50 index. Previously, if all indexes were taken the kernel would overwrite
51 only a core file with the highest index in a filename.
52 Currently the system will create a new core file if there is a free
53 index or if all slots are taken it will overwrite the oldest one.
56 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
57 6.0.1. Please see the 20141231 entry below for information about
58 prerequisites and upgrading, if you are not already using clang 3.5.0
62 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
63 needed to be changed to work with it. This change was made with r335763
64 and requires a mergemaster / etcupdate / etc to update the installed file.
67 r334930 changed the interface between the NFS modules, so they all
68 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
71 The kernel / userland interface for devinfo changed, so you'll
72 need a new kernel and userland as a pair for it to work (rebuilding
73 lib/libdevinfo is all that's required). devinfo and devmatch will
74 not work, but everything else will when there's a mismatch.
77 The on-disk format for hwpmc callchain records has changed to include
78 threadid corresponding to a given record. This changes the field offsets
79 and thus requires that libpmcstat be rebuilt before using a kernel
83 The vxge(4) driver has been removed. This driver was introduced into
84 HEAD one week before the Exar left the Ethernet market and is not
85 known to be used. If you have device vxge in your kernel config file
89 The amd64 kernel now requires a ld that supports ifunc to produce a
90 working kernel, either lld or a newer binutils. lld is built by default
91 on amd64, and the 'buildkernel' target uses it automatically. However,
92 it is not the default linker, so building the kernel the traditional
93 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
94 binutils port/package). lld will soon be default, and this requirement
98 The nxge(4) driver has been removed. This driver was for PCI-X 10g
99 cards made by s2io/Neterion. The company was aquired by Exar and
100 no longer sells or supports Ethernet products. If you have device
101 nxge in your kernel config file it must be removed.
104 The tz database (tzdb) has been updated to 2018e. This version more
105 correctly models time stamps in time zones with negative DST such as
106 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
107 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
108 time zone abbreviations and the tm_isdst flag.
111 The ixgb(4) driver has been removed. This driver was for an early and
112 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
113 quickly shifted to the long lived ixgbe family. If you have device
114 ixgb in your kernel config file it must be removed.
117 The lmc(4) driver has been removed. This was a WAN interface
118 card that was already reportedly rare in 2003, and had an ambiguous
119 license. If you have device lmc in your kernel config file it must
123 Support for Arcnet networks has been removed. If you have device
124 arcnet or device cm in your kernel config file they must be
128 Support for FDDI networks has been removed. If you have device
129 fddi or device fpa in your kernel config file they must be
133 In addition to supporting RFC 3164 formatted messages, the
134 syslogd(8) service is now capable of parsing RFC 5424 formatted
135 log messages. The main benefit of using RFC 5424 is that clients
136 may now send log messages with timestamps containing year numbers,
137 microseconds and time zone offsets.
139 Similarly, the syslog(3) C library function has been altered to
140 send RFC 5424 formatted messages to the local system logging
141 daemon. On systems using syslogd(8), this change should have no
142 negative impact, as long as syslogd(8) and the C library are
143 updated at the same time. On systems using a different system
144 logging daemon, it may be necessary to make configuration
145 adjustments, depending on the software used.
147 When using syslog-ng, add the 'syslog-protocol' flag to local
148 input sources to enable parsing of RFC 5424 formatted messages:
151 unix-dgram("/var/run/log" flags(syslog-protocol));
154 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
155 of the 'imuxsock' module to let messages be processed by the
156 regular RFC 3164/5424 parsing pipeline:
158 module(load="imuxsock" SysSock.UseSpecialParser="off")
160 Do note that these changes only affect communication between local
161 applications and syslogd(8). The format that syslogd(8) uses to
162 store messages on disk or forward messages to other systems
163 remains unchanged. syslogd(8) still uses RFC 3164 for these
164 purposes. Options to customize this behaviour will be added in the
165 future. Utilities that process log files stored in /var/log are
166 thus expected to continue to function as before.
168 __FreeBSD_version has been incremented to 1200061 to denote this
172 Support for token ring networks has been removed. If you
173 have "device token" in your kernel config you should remove
174 it. No device drivers supported token ring.
177 makefs was modified to be able to tag ISO9660 El Torito boot catalog
178 entries as EFI instead of overloading the i386 tag as done previously.
179 The amd64 mkisoimages.sh script used to build amd64 ISO images for
180 release was updated to use this. This may mean that makefs must be
181 updated before "make cdrom" can be run in the release directory. This
182 should be as simple as:
184 $ cd $SRCDIR/usr.sbin/makefs
185 $ make depend all install
188 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
189 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
190 Co-existance for the transition period will come shortly. Booting is a
191 complex environment and test coverage for Lua-enabled loaders has been
192 thin, so it would be prudent to assume it might not work and make
193 provisions for backup boot methods.
196 devmatch functionality has been turned on in devd. It will automatically
197 load drivers for unattached devices. This may cause unexpected drivers to
198 be loaded. Please report any problems to current@ and imp@freebsd.org.
201 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
202 6.0.0. Please see the 20141231 entry below for information about
203 prerequisites and upgrading, if you are not already using clang 3.5.0
207 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
208 This means it is used to link the kernel and userland libraries and
209 executables, but is not yet installed as /usr/bin/ld by default.
211 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
212 WITHOUT_LLD_BOOTSTRAP=yes
215 On i386, pmtimer has been removed. Its functionality has been folded
216 into apm. It was a no-op on ACPI in current for a while now (but was still
217 needed on i386 in FreeBSD 11 and earlier). Users may need to remove it
218 from kernel config files.
221 The use of RSS hash from the network card aka flowid has been
222 disabled by default for lagg(4) as it's currently incompatible with
223 the lacp and loadbalance protocols.
225 This can be re-enabled by setting the following in loader.conf:
226 net.link.lagg.default_use_flowid="1"
229 The SW_WATCHDOG option is no longer necessary to enable the
230 hardclock-based software watchdog if no hardware watchdog is
231 configured. As before, SW_WATCHDOG will cause the software
232 watchdog to be enabled even if a hardware watchdog is configured.
235 r326887 fixes the issue described in the 20171214 UPDATING entry.
236 r326888 flips the switch back to building GELI support always.
239 r362593 broke ZFS + GELI support for reasons unknown. However,
240 it also broke ZFS support generally, so GELI has been turned off
241 by default as the lesser evil in r326857. If you boot off ZFS and/or
242 GELI, it might not be a good time to update.
245 PowerPC users must update loader(8) by rebuilding world before
246 installing a new kernel, as the protocol connecting them has
247 changed. Without the update, loader metadata will not be passed
248 successfully to the kernel and users will have to enter their
249 root partition at the kernel mountroot prompt to continue booting.
250 Newer versions of loader can boot old kernels without issue.
253 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
254 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
255 to WITH/OUT_LOADER_GELI.
258 The naive and non-compliant support of posix_fallocate(2) in ZFS
259 has been removed as of r325320. The system call now returns EINVAL
260 when used on a ZFS file. Although the new behavior complies with the
261 standard, some consumers are not prepared to cope with it.
262 One known victim is lld prior to r325420.
265 Building in a FreeBSD src checkout will automatically create object
266 directories now rather than store files in the current directory if
267 'make obj' was not ran. Calling 'make obj' is no longer necessary.
268 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
269 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
273 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
274 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
275 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
276 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
277 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
278 The UNIFIED_OBJDIR option is a transitional feature that will be
279 removed for 12.0 release; please migrate to the new format for any
280 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
281 than hardcoding paths.
284 The native-xtools target no longer installs the files by default to the
285 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
286 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
289 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
290 options are changing from controlling the build if defined / undefined
291 to controlling the build with explicit 'yes' or 'no' values. They will
292 shift to WITH/WITHOUT options to match other options in the system.
295 libstand has turned into a private library for sys/boot use only.
296 It is no longer supported as a public interface outside of sys/boot.
299 The arm port has split armv6 into armv6 and armv7. armv7 is now
300 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
301 and are running a kernel from before r324363, you will need to add
302 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
305 When building multiple kernels using KERNCONF, non-existent KERNCONF
306 files will produce an error and buildkernel will fail. Previously
307 missing KERNCONF files silently failed giving no indication as to
308 why, only to subsequently discover during installkernel that the
309 desired kernel was never built in the first place.
312 The default serial number format for CTL LUNs has changed. This will
313 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
314 or iSCSI clients care about their LUNs' serial numbers. Users who
315 require serial number stability should hardcode serial numbers in
319 For 32-bit arm compiled for hard-float support, soft-floating point
320 binaries now always get their shared libraries from
321 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
322 /usr/libsoft also existed). Only users with a hard-float ld.so, but
323 soft-float everything else should be affected.
326 The geli password typed at boot is now hidden. To restore the previous
327 behavior, see geli(8) for configuration options.
330 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
331 sysctl values. Minor nit, but requires a rebuild of both world/kernel
335 "make check" behavior (made in ^/head@r295380) has been changed to
336 execute from a limited sandbox, as opposed to executing from
340 - The "beforecheck" and "aftercheck" targets are now specified.
341 - ${CHECKDIR} (added in commit noted above) has been removed.
342 - Legacy behavior can be enabled by setting
343 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
345 If the limited sandbox mode is enabled, "make check" will execute
346 "make distribution", then install, execute the tests, and clean up the
347 sandbox if successful.
349 The "make distribution" and "make install" targets are typically run as
350 root to set appropriate permissions and ownership at installation time.
351 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
352 environment if executing "make check" with limited sandbox mode using
353 an unprivileged user.
356 Since the switch to GPT disk labels, fsck for UFS/FFS has been
357 unable to automatically find alternate superblocks. As of r322297,
358 the information needed to find alternate superblocks has been
359 moved to the end of the area reserved for the boot block.
360 Filesystems created with a newfs of this vintage or later
361 will create the recovery information. If you have a filesystem
362 created prior to this change and wish to have a recovery block
363 created for your filesystem, you can do so by running fsck in
364 foreground mode (i.e., do not use the -p or -y options). As it
365 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
366 to which you should answer yes.
369 As of r321665, an NFSv4 server configuration that services
370 Kerberos mounts or clients that do not support the uid/gid in
371 owner/owner_group string capability, must explicitly enable
372 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
373 machine's /etc/rc.conf file.
376 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
377 Please see the 20141231 entry below for information about prerequisites
378 and upgrading, if you are not already using clang 3.5.0 or higher.
381 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
382 r-commands (rlogin, rsh, etc.) to be built with the base system.
385 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
386 a very major ABI incompatible change, so users of FreeBSD/powerpc must
387 be careful when performing source upgrades. It is best to run
388 'make installworld' from an alternate root system, either a live
389 CD/memory stick, or a temporary root partition. Additionally, all ports
390 must be recompiled. powerpc64 is largely unaffected, except in the case
391 of 32-bit compatibility. All 32-bit binaries will be affected.
394 Forward compatibility for the "ino64" project have been committed. This
395 will allow most new binaries to run on older kernels in a limited
396 fashion. This prevents many of the common foot-shooting actions in the
397 upgrade as well as the limited ability to roll back the kernel across
398 the ino64 upgrade. Complicated use cases may not work properly, though
399 enough simpler ones work to allow recovery in most situations.
402 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
403 if you require the GPL compiler.
406 The internal ABI used for communication between the NFS kernel modules
407 was changed by r320085, so __FreeBSD_version was bumped to
408 ensure all the NFS related modules are updated together.
411 The ABI of struct event was changed by extending the data
412 member to 64bit and adding ext fields. For upgrade, same
413 precautions as for the entry 20170523 "ino64" must be
417 The GNU roff toolchain has been removed from base. To render manpages
418 which are not supported by mandoc(1), man(1) can fallback on GNU roff
419 from ports (and recommends to install it).
420 To render roff(7) documents, consider using GNU roff from ports or the
421 heirloom doctools roff toolchain from ports via pkg install groff or
422 via pkg install heirloom-doctools.
425 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
426 smaller runtime footprint builds. This is useful for embedded systems
427 which only require one chipset support.
429 If you load it as a module, make sure this is in /boot/loader.conf:
433 This will load the HAL, all chip/RF backends and if_ath_pci.
434 If you have if_ath_pci in /boot/loader.conf, ensure it is after
435 if_ath or it will not load any HAL chipset support.
437 If you want to selectively load things (eg on ye cheape ARM/MIPS
438 platforms where RAM is at a premium) you should:
441 * load the chip modules in question
442 * load ath_rate, ath_dfs
444 * load if_ath_pci and/or if_ath_ahb depending upon your particular
445 bus bind type - this is where probe/attach is done.
447 For further comments/feedback, poke adrian@ .
450 The "ino64" 64-bit inode project has been committed, which extends
451 a number of types to 64 bits. Upgrading in place requires care and
452 adherence to the documented upgrade procedure.
454 If using a custom kernel configuration ensure that the
455 COMPAT_FREEBSD11 option is included (as during the upgrade the
456 system will be running the ino64 kernel with the existing world).
458 For the safest in-place upgrade begin by removing previous build
459 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
460 full procedure documented below under the heading "To rebuild
461 everything and install it on the current system." Specifically,
462 a reboot is required after installing the new kernel before
466 The NATM framework including the en(4), fatm(4), hatm(4), and
467 patm(4) devices has been removed. Consumers should plan a
468 migration before the end-of-life date for FreeBSD 11.
471 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
472 diff has not been implemented, if those are needed a newer version of
473 GNU diff is available via the diffutils package under the gdiff name.
476 As of r316810 for ipfilter, keep frags is no longer assumed when
477 keep state is specified in a rule. r316810 aligns ipfilter with
478 documentation in man pages separating keep frags from keep state.
479 This allows keep state to be specified without forcing keep frags
480 and allows keep frags to be specified independently of keep state.
481 To maintain previous behaviour, also specify keep frags with
482 keep state (as documented in ipf.conf.5).
485 arm64 builds now use the base system LLD 4.0.0 linker by default,
486 instead of requiring that the aarch64-binutils port or package be
487 installed. To continue using aarch64-binutils, set
488 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
491 The UDP optimization in entry 20160818 that added the sysctl
492 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
493 packets will no longer be treated as L3 broadcast packets.
496 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
497 use any explicitly assigned loopback address available in the jail
498 instead of using the first assigned address of the jail.
501 The ctl.ko module no longer implements the iSCSI target frontend:
502 cfiscsi.ko does instead.
504 If building cfiscsi.ko as a kernel module, the module can be loaded
505 via one of the following methods:
506 - `cfiscsi_load="YES"` in loader.conf(5).
507 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
508 - ctladm(8)/ctld(8), when compiled with iSCSI support
509 (`WITH_ISCSI=yes` in src.conf(5))
511 Please see cfiscsi(4) for more details.
514 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
515 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
516 same source (previously, the dependency of mmcsd.ko on mmc.ko was
517 missing, but mmcsd.ko now will refuse to load if it is incompatible
521 The syntax of ipfw(8) named states was changed to avoid ambiguity.
522 If you have used named states in the firewall rules, you need to modify
523 them after installworld and before rebooting. Now named states must
524 be prefixed with colon.
527 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
528 removed as the userland we provide cannot use them. The KMS version
529 (sys/dev/drm2) supports the same hardware.
532 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
533 Please see the 20141231 entry below for information about prerequisites
534 and upgrading, if you are not already using clang 3.5.0 or higher.
537 The code that provides support for ZFS .zfs/ directory functionality
538 has been reimplemented. It's not possible now to create a snapshot
539 by mkdir under .zfs/snapshot/. That should be the only user visible
543 EISA bus support has been removed. The WITH_EISA option is no longer
547 MCA bus support has been removed.
550 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
551 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
554 The EM_MULTIQUEUE kernel configuration option is deprecated now that
555 the em(4) driver conforms to iflib specifications.
558 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
559 IFLIB. If you have a custom kernel configuration that excludes em(4)
560 but you use igb(4), you need to re-add em(4) to your custom configuration.
563 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
564 Please see the 20141231 entry below for information about prerequisites
565 and upgrading, if you are not already using clang 3.5.0 or higher.
568 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
569 Please see the 20141231 entry below for information about prerequisites
570 and upgrading, if you are not already using clang 3.5.0 or higher.
573 The layout of the pmap structure has changed for powerpc to put the pmap
574 statistics at the front for all CPU variations. libkvm(3) and all tools
575 that link against it need to be recompiled.
578 isl(4) and cyapa(4) drivers now require a new driver,
579 chromebook_platform(4), to work properly on Chromebook-class hardware.
580 On other types of hardware the drivers may need to be configured using
581 device hints. Please see the corresponding manual pages for details.
584 The urtwn(4) driver was merged into rtwn(4) and now consists of
585 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
587 Also, firmware for RTL8188CE was renamed due to possible name
588 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
591 GNU rcs has been removed from base. It is available as packages:
592 - rcs: Latest GPLv3 GNU rcs version.
593 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
597 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
598 modules now requires that the kernel configuration contain the
599 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
602 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
603 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
606 Relocatable object files with the extension of .So have been renamed
607 to use an extension of .pico instead. The purpose of this change is
608 to avoid a name clash with shared libraries on case-insensitive file
609 systems. On those file systems, foo.So is the same file as foo.so.
612 GNU rcs has been turned off by default. It can (temporarily) be built
613 again by adding WITH_RCS knob in src.conf.
614 Otherwise, GNU rcs is available from packages:
615 - rcs: Latest GPLv3 GNU rcs version.
616 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
619 The backup_uses_rcs functionality has been removed from rc.subr.
622 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
623 two separate components, QUEUE_MACRO_DEBUG_TRACE and
624 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
625 QUEUE_MACRO_DEBUG behavior.
628 r304787 changed some ioctl interfaces between the iSCSI userspace
629 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
630 rebuilt to work with new kernels. __FreeBSD_version has been bumped
634 The UDP receive code has been updated to only treat incoming UDP
635 packets that were addressed to an L2 broadcast address as L3
636 broadcast packets. It is not expected that this will affect any
637 standards-conforming UDP application. The new behaviour can be
638 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
642 Remove the openbsd_poll system call.
643 __FreeBSD_version has been bumped because of this.
646 The libc stub for the pipe(2) system call has been replaced with
647 a wrapper that calls the pipe2(2) system call and the pipe(2)
648 system call is now only implemented by the kernels that include
649 "options COMPAT_FREEBSD10" in their config file (this is the
650 default). Users should ensure that this option is enabled in
651 their kernel or upgrade userspace to r302092 before upgrading their
655 CAM will now strip leading spaces from SCSI disks' serial numbers.
656 This will affect users who create UFS filesystems on SCSI disks using
657 those disk's diskid device nodes. For example, if /etc/fstab
658 previously contained a line like
659 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
660 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
661 transforms like gmirror may also be affected. ZFS users should
665 The bitstring(3) API has been updated with new functionality and
666 improved performance. But it is binary-incompatible with the old API.
667 Objects built with the new headers may not be linked against objects
668 built with the old headers.
671 The brk and sbrk functions have been removed from libc on arm64.
672 Binutils from ports has been updated to not link to these
673 functions and should be updated to the latest version before
674 installing a new libc.
677 The armv6 port now defaults to hard float ABI. Limited support
678 for running both hardfloat and soft float on the same system
679 is available using the libraries installed with -DWITH_LIBSOFT.
680 This has only been tested as an upgrade path for installworld
681 and packages may fail or need manual intervention to run. New
682 packages will be needed.
684 To update an existing self-hosted armv6hf system, you must add
685 TARGET_ARCH=armv6 on the make command line for both the build
686 and the install steps.
689 Kernel modules compiled outside of a kernel build now default to
690 installing to /boot/modules instead of /boot/kernel. Many kernel
691 modules built this way (such as those in ports) already overrode
692 KMODDIR explicitly to install into /boot/modules. However,
693 manually building and installing a module from /sys/modules will
694 now install to /boot/modules instead of /boot/kernel.
697 The CAM I/O scheduler has been committed to the kernel. There should be
698 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
699 list of known rogues that claim support for this but actually corrupt
700 data is believed to be complete, be on the lookout for data
701 corruption. The known rogue list is believed to be complete:
703 o Crucial MX100, M550 drives with MU01 firmware.
704 o Micron M510 and M550 drives with MU01 firmware.
705 o Micron M500 prior to MU07 firmware
706 o Samsung 830, 840, and 850 all firmwares
707 o FCCT M500 all firmwares
709 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
710 with working NCQ TRIM. For Micron branded drives, see your sales rep for
711 updated firmware. Black listed drives will work correctly because these
712 drives work correctly so long as no NCQ TRIMs are sent to them. Given
713 this list is the same as found in Linux, it's believed there are no
714 other rogues in the market place. All other models from the above
717 To be safe, if you are at all concerned, you can quirk each of your
718 drives to prevent NCQ from being sent by setting:
719 kern.cam.ada.X.quirks="0x2"
720 in loader.conf. If the drive requires the 4k sector quirk, set the
724 The FAST_DEPEND build option has been removed and its functionality is
725 now the one true way. The old mkdep(1) style of 'make depend' has
726 been removed. See 20160311 for further details.
729 Resource range types have grown from unsigned long to uintmax_t. All
730 drivers, and anything using libdevinfo, need to be recompiled.
733 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
734 builds. It no longer runs mkdep(1) during 'make depend', and the
735 'make depend' stage can safely be skipped now as it is auto ran
736 when building 'make all' and will generate all SRCS and DPSRCS before
737 building anything else. Dependencies are gathered at compile time with
738 -MF flags kept in separate .depend files per object file. Users should
739 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
743 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
744 kernel modules. Therefore, if you load any kernel modules at boot time,
745 please install the boot loaders after you install the kernel, but before
749 make buildkernel KERNCONF=YOUR_KERNEL_HERE
750 make installkernel KERNCONF=YOUR_KERNEL_HERE
751 make -C sys/boot install
752 <reboot in single user>
754 Then follow the usual steps, described in the General Notes section,
758 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
759 see the 20141231 entry below for information about prerequisites and
760 upgrading, if you are not already using clang 3.5.0 or higher.
763 The AIO subsystem is now a standard part of the kernel. The
764 VFS_AIO kernel option and aio.ko kernel module have been removed.
765 Due to stability concerns, asynchronous I/O requests are only
766 permitted on sockets and raw disks by default. To enable
767 asynchronous I/O requests on all file types, set the
768 vfs.aio.enable_unsafe sysctl to a non-zero value.
771 The ELF object manipulation tool objcopy is now provided by the
772 ELF Tool Chain project rather than by GNU binutils. It should be a
773 drop-in replacement, with the addition of arm64 support. The
774 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
775 to obtain the GNU version if necessary.
778 Building ZFS pools on top of zvols is prohibited by default. That
779 feature has never worked safely; it's always been prone to deadlocks.
780 Using a zvol as the backing store for a VM guest's virtual disk will
781 still work, even if the guest is using ZFS. Legacy behavior can be
782 restored by setting vfs.zfs.vol.recursive=1.
785 The NONE and HPN patches has been removed from OpenSSH. They are
786 still available in the security/openssh-portable port.
789 With the addition of ypldap(8), a new _ypldap user is now required
790 during installworld. "mergemaster -p" can be used to add the user
791 prior to installworld, as documented in the handbook.
794 The tftp loader (pxeboot) now uses the option root-path directive. As a
795 consequence it no longer looks for a pxeboot.4th file on the tftp
796 server. Instead it uses the regular /boot infrastructure as with the
800 The code to start recording plug and play data into the modules has
801 been committed. While the old tools will properly build a new kernel,
802 a number of warnings about "unknown metadata record 4" will be produced
803 for an older kldxref. To avoid such warnings, make sure to rebuild
804 the kernel toolchain (or world). Make sure that you have r292078 or
805 later when trying to build 292077 or later before rebuilding.
808 Debug data files are now built by default with 'make buildworld' and
809 installed with 'make installworld'. This facilitates debugging but
810 requires more disk space both during the build and for the installed
811 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
815 r291527 changed the internal interface between the nfsd.ko and
816 nfscommon.ko modules. As such, they must both be upgraded to-gether.
817 __FreeBSD_version has been bumped because of this.
820 Add support for unicode collation strings leads to a change of
821 order of files listed by ls(1) for example. To get back to the old
822 behaviour, set LC_COLLATE environment variable to "C".
824 Databases administrators will need to reindex their databases given
825 collation results will be different.
827 Due to a bug in install(1) it is recommended to remove the ancient
828 locales before running make installworld.
830 rm -rf /usr/share/locale/*
833 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
834 libcrypto.so.7 or libssl.so.7 must be recompiled.
837 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
838 Kernel modules isp_2400_multi and isp_2500_multi were removed and
839 should be replaced with isp_2400 and isp_2500 modules respectively.
842 The build previously allowed using 'make -n' to not recurse into
843 sub-directories while showing what commands would be executed, and
844 'make -n -n' to recursively show commands. Now 'make -n' will recurse
845 and 'make -N' will not.
848 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
849 and etcupdate will now use this file. A custom sendmail.cf is now
850 updated via this mechanism rather than via installworld. If you had
851 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
852 want to remove the exclusion or change it to "always install".
853 /etc/mail/sendmail.cf is now managed the same way regardless of
854 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
855 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
858 Compatibility shims for legacy ATA device names have been removed.
859 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
860 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
861 environment variables, /dev/ad* and /dev/ar* symbolic links.
864 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
865 Please see the 20141231 entry below for information about prerequisites
866 and upgrading, if you are not already using clang 3.5.0 or higher.
869 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
870 and renamed from .symbols to .debug. This reduces the size requirements
871 on the boot partition or file system and provides consistency with
872 userland debug files.
874 When using the supported kernel installation method the
875 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
876 as is done with /boot/kernel.
878 Developers wishing to maintain the historical behavior of installing
879 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
882 The wireless drivers had undergone changes that remove the 'parent
883 interface' from the ifconfig -l output. The rc.d network scripts
884 used to check presence of a parent interface in the list, so old
885 scripts would fail to start wireless networking. Thus, etcupdate(3)
886 or mergemaster(8) run is required after kernel update, to update your
887 rc.d scripts in /etc.
890 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
891 These configurations are now automatically interpreted as
892 'scrub fragment reassemble'.
895 Kernel-loadable modules for the random(4) device are back. To use
896 them, the kernel must have
899 options RANDOM_LOADABLE
901 kldload(8) can then be used to load random_fortuna.ko
902 or random_yarrow.ko. Please note that due to the indirect
903 function calls that the loadable modules need to provide,
904 the build-in variants will be slightly more efficient.
906 The random(4) kernel option RANDOM_DUMMY has been retired due to
907 unpopularity. It was not all that useful anyway.
910 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
911 Control over building the ELF Tool Chain tools is now provided by
912 the WITHOUT_TOOLCHAIN knob.
915 The polarity of Pulse Per Second (PPS) capture events with the
916 uart(4) driver has been corrected. Prior to this change the PPS
917 "assert" event corresponded to the trailing edge of a positive PPS
918 pulse and the "clear" event was the leading edge of the next pulse.
920 As the width of a PPS pulse in a typical GPS receiver is on the
921 order of 1 millisecond, most users will not notice any significant
922 difference with this change.
924 Anyone who has compensated for the historical polarity reversal by
925 configuring a negative offset equal to the pulse width will need to
926 remove that workaround.
929 The default group assigned to /dev/dri entries has been changed
930 from 'wheel' to 'video' with the id of '44'. If you want to have
931 access to the dri devices please add yourself to the video group
934 # pw groupmod video -m $USER
937 The menu.rc and loader.rc files will now be replaced during
938 upgrades. Please migrate local changes to menu.rc.local and
939 loader.rc.local instead.
942 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
943 strings and strip have been removed. The src.conf(5) knob
944 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
947 As ZFS requires more kernel stack pages than is the default on some
948 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
949 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
951 Please consider using 'options KSTACK_PAGES=X' where X is greater
952 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
955 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
956 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
957 default, i.e., they will not contain "::". For example, instead
958 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
959 to have a more specific match, such as different map entries for
960 IPv6:0:0 vs IPv6:0. This change requires that configuration
961 data (including maps, files, classes, custom ruleset, etc.) must
962 use the same format, so make certain such configuration data is
963 upgrading. As a very simple check search for patterns like
964 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
965 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
966 the cf option UseCompressedIPv6Addresses.
969 The default kernel entropy-processing algorithm is now
970 Fortuna, replacing Yarrow.
972 Assuming you have 'device random' in your kernel config
973 file, the configurations allow a kernel option to override
974 this default. You may choose *ONE* of:
976 options RANDOM_YARROW # Legacy /dev/random algorithm.
977 options RANDOM_DUMMY # Blocking-only driver.
979 If you have neither, you get Fortuna. For most people,
980 read no further, Fortuna will give a /dev/random that works
981 like it always used to, and the difference will be irrelevant.
983 If you remove 'device random', you get *NO* kernel-processed
984 entropy at all. This may be acceptable to folks building
985 embedded systems, but has complications. Carry on reading,
986 and it is assumed you know what you need.
988 *PLEASE* read random(4) and random(9) if you are in the
989 habit of tweaking kernel configs, and/or if you are a member
990 of the embedded community, wanting specific and not-usual
991 behaviour from your security subsystems.
993 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
994 random', you will NOT have a functioning /dev/random, and
995 many cryptographic features will not work, including SSH.
996 You may also find strange behaviour from the random(3) set
997 of library functions, in particular sranddev(3), srandomdev(3)
998 and arc4random(3). The reason for this is that the KERN_ARND
999 sysctl only returns entropy if it thinks it has some to
1000 share, and with RANDOM_DUMMY or no 'device random' this
1004 An additional fix for the issue described in the 20150614 sendmail
1005 entry below has been committed in revision 284717.
1008 FreeBSD's old make (fmake) has been removed from the system. It is
1009 available as the devel/fmake port or via pkg install fmake.
1012 The fix for the issue described in the 20150614 sendmail entry
1013 below has been committed in revision 284436. The work
1014 around described in that entry is no longer needed unless the
1015 default setting is overridden by a confDH_PARAMETERS configuration
1016 setting of '5' or pointing to a 512 bit DH parameter file.
1019 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1020 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1021 and devel/kyua to version 0.20+ and adjust any calling code to work
1022 with Kyuafile and kyua.
1025 The import of openssl to address the FreeBSD-SA-15:10.openssl
1026 security advisory includes a change which rejects handshakes
1027 with DH parameters below 768 bits. sendmail releases prior
1028 to 8.15.2 (not yet released), defaulted to a 512 bit
1029 DH parameter setting for client connections. To work around
1030 this interoperability, sendmail can be configured to use a
1031 2048 bit DH parameter by:
1033 1. Edit /etc/mail/`hostname`.mc
1034 2. If a setting for confDH_PARAMETERS does not exist or
1035 exists and is set to a string beginning with '5',
1036 replace it with '2'.
1037 3. If a setting for confDH_PARAMETERS exists and is set to
1038 a file path, create a new file with:
1039 openssl dhparam -out /path/to/file 2048
1040 4. Rebuild the .cf file:
1041 cd /etc/mail/; make; make install
1042 5. Restart sendmail:
1043 cd /etc/mail/; make restart
1045 A sendmail patch is coming, at which time this file will be
1049 Generation of legacy formatted entries have been disabled by default
1050 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1051 entries were converted to use the new format by default when the new,
1052 machine independent format have been added and supported since FreeBSD
1055 Please see the pwd_mkdb(8) manual page for further details.
1058 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1059 20141231 entry below for information about prerequisites and upgrading,
1060 if you are not already using 3.5.0 or higher.
1063 TI platform code switched to using vendor DTS files and this update
1064 may break existing systems running on Beaglebone, Beaglebone Black,
1067 - dtb files should be regenerated/reinstalled. Filenames are the
1068 same but content is different now
1069 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1070 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1071 addressing scheme is now pin 25 on /dev/gpioc3.
1072 - Pandaboard: /etc/ttys should be updated, serial console device is
1073 now /dev/ttyu2, not /dev/ttyu0
1076 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1077 If you need the GNU extension from groff soelim(1), install groff
1078 from package: pkg install groff, or via ports: textproc/groff.
1081 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1082 defined in symlink(7); previously symlinks were silently ignored.
1085 The const qualifier has been removed from iconv(3) to comply with
1086 POSIX. The ports tree is aware of this from r384038 onwards.
1089 Libraries specified by LIBADD in Makefiles must have a corresponding
1090 DPADD_<lib> variable to ensure correct dependencies. This is now
1091 enforced in src.libnames.mk.
1094 From legacy ata(4) driver was removed support for SATA controllers
1095 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1096 Kernel modules ataahci and ataadaptec were removed completely,
1097 replaced by ahci and mvs modules respectively.
1100 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1101 the 20141231 entry below for information about prerequisites and
1102 upgrading, if you are not already using 3.5.0 or higher.
1105 The 32-bit PowerPC kernel has been changed to a position-independent
1106 executable. This can only be booted with a version of loader(8)
1107 newer than January 31, 2015, so make sure to update both world and
1108 kernel before rebooting.
1111 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1112 but before r278950, the RNG was not seeded properly. Immediately
1113 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1114 ssh keys or openssl keys) that were generated w/ a kernel from that
1115 range. This does not affect programs that directly used /dev/random
1116 or /dev/urandom. All userland uses of arc4random(3) are affected.
1119 The autofs(4) ABI was changed in order to restore binary compatibility
1120 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1121 with the new kernel.
1124 The powerpc64 kernel has been changed to a position-independent
1125 executable. This can only be booted with a new version of loader(8),
1126 so make sure to update both world and kernel before rebooting.
1129 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1130 only release, no new features have been added. Please see the 20141231
1131 entry below for information about prerequisites and upgrading, if you
1132 are not already using 3.5.0.
1135 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1136 taken from the ELF Tool Chain project rather than GNU binutils. They
1137 should be drop-in replacements, with the addition of arm64 support.
1138 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1139 binutils tools, if necessary. See 20150805 for updated information.
1142 The default Unbound configuration now enables remote control
1143 using a local socket. Users who have already enabled the
1144 local_unbound service should regenerate their configuration
1145 by running "service local_unbound setup" as root.
1148 The GNU texinfo and GNU info pages have been removed.
1149 To be able to view GNU info pages please install texinfo from ports.
1152 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1154 As of this release, a prerequisite for building clang, llvm and lldb is
1155 a C++11 capable compiler and C++11 standard library. This means that to
1156 be able to successfully build the cross-tools stage of buildworld, with
1157 clang as the bootstrap compiler, your system compiler or cross compiler
1158 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1159 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1162 On any standard FreeBSD 10.x or 11.x installation, where clang and
1163 libc++ are on by default (that is, on x86 or arm), this should work out
1166 On 9.x installations where clang is enabled by default, e.g. on x86 and
1167 powerpc, libc++ will not be enabled by default, so libc++ should be
1168 built (with clang) and installed first. If both clang and libc++ are
1169 missing, build clang first, then use it to build libc++.
1171 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1172 the instructions for 9.x above.
1174 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1175 default, and do not build clang.
1177 Many embedded systems are resource constrained, and will not be able to
1178 build clang in a reasonable time, or in some cases at all. In those
1179 cases, cross building bootable systems on amd64 is a workaround.
1181 This new version of clang introduces a number of new warnings, of which
1182 the following are most likely to appear:
1186 This warns in two cases, for both C and C++:
1187 * When the code is trying to take the absolute value of an unsigned
1188 quantity, which is effectively a no-op, and almost never what was
1189 intended. The code should be fixed, if at all possible. If you are
1190 sure that the unsigned quantity can be safely cast to signed, without
1191 loss of information or undefined behavior, you can add an explicit
1192 cast, or disable the warning.
1194 * When the code is trying to take an absolute value, but the called
1195 abs() variant is for the wrong type, which can lead to truncation.
1196 If you want to disable the warning instead of fixing the code, please
1197 make sure that truncation will not occur, or it might lead to unwanted
1200 -Wtautological-undefined-compare and
1201 -Wundefined-bool-conversion
1203 These warn when C++ code is trying to compare 'this' against NULL, while
1204 'this' should never be NULL in well-defined C++ code. However, there is
1205 some legacy (pre C++11) code out there, which actively abuses this
1206 feature, which was less strictly defined in previous C++ versions.
1208 Squid and openjdk do this, for example. The warning can be turned off
1209 for C++98 and earlier, but compiling the code in C++11 mode might result
1210 in unexpected behavior; for example, the parts of the program that are
1211 unreachable could be optimized away.
1214 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1215 kernel sources have been removed. The .h files remain, since some
1216 utilities include them. This will need to be fixed later.
1217 If "mount -t oldnfs ..." is attempted, it will fail.
1218 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1219 the utilities will report errors.
1222 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1223 directories to top level SUBDIR variable when their parent
1224 directory is included in LOCAL_DIRS. Users with build systems with
1225 such hierarchies and without SUBDIR entries in the parent
1226 directory Makefiles should add them or add the directories to
1230 faith(4) and faithd(8) have been removed from the base system. Faith
1231 has been obsolete for a very long time.
1234 vt(4), the new console driver, is enabled by default. It brings
1235 support for Unicode and double-width characters, as well as
1236 support for UEFI and integration with the KMS kernel video
1239 You may need to update your console settings in /etc/rc.conf,
1240 most probably the keymap. During boot, /etc/rc.d/syscons will
1241 indicate what you need to do.
1243 vt(4) still has issues and lacks some features compared to
1244 syscons(4). See the wiki for up-to-date information:
1245 https://wiki.freebsd.org/Newcons
1247 If you want to keep using syscons(4), you can do so by adding
1248 the following line to /boot/loader.conf:
1252 pjdfstest has been integrated into kyua as an opt-in test suite.
1253 Please see share/doc/pjdfstest/README for more details on how to
1257 gperf has been removed from the base system for architectures
1258 that use clang. Ports that require gperf will obtain it from the
1262 pjdfstest has been moved from tools/regression/pjdfstest to
1266 At svn r271982, The default linux compat kernel ABI has been adjusted
1267 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1268 update. If you wish to continue using the linux-f10 compat ports,
1269 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1270 encouraged to update their linux-compat packages to linux-c6 during
1271 their next update cycle.
1274 The ofwfb driver, used to provide a graphics console on PowerPC when
1275 using vt(4), no longer allows mmap() of all physical memory. This
1276 will prevent Xorg on PowerPC with some ATI graphics cards from
1277 initializing properly unless x11-servers/xorg-server is updated to
1281 The xdev targets have been converted to using TARGET and
1282 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1285 The default unbound configuration has been modified to address
1286 issues with reverse lookups on networks that use private
1287 address ranges. If you use the local_unbound service, run
1288 "service local_unbound setup" as root to regenerate your
1289 configuration, then "service local_unbound reload" to load the
1293 The GNU texinfo and GNU info pages are not built and installed
1294 anymore, WITH_INFO knob has been added to allow to built and install
1296 UPDATE: see 20150102 entry on texinfo's removal
1299 The GNU readline library is now an INTERNALLIB - that is, it is
1300 statically linked into consumers (GDB and variants) in the base
1301 system, and the shared library is no longer installed. The
1302 devel/readline port is available for third party software that
1306 The Itanium architecture (ia64) has been removed from the list of
1307 known architectures. This is the first step in the removal of the
1311 Commit r268115 has added NFSv4.1 server support, merged from
1312 projects/nfsv4.1-server. Since this includes changes to the
1313 internal interfaces between the NFS related modules, a full
1314 build of the kernel and modules will be necessary.
1315 __FreeBSD_version has been bumped.
1318 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1319 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1320 which differs from the behaviour controlled by this knob.)
1323 Maximal length of the serial number in CTL was increased from 16 to
1324 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1325 and ctld, need to be rebuilt to work with a new kernel.
1328 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1329 1 respectively to match the upstream numbers. They were out of
1330 sync because, when they were originally added to FreeBSD, the
1331 upstream versions were not respected. These libraries are private
1332 and not yet built by default, so renumbering them should be a
1333 non-issue. However, unclean source trees will yield broken test
1334 programs once the operator executes "make delete-old-libs" after a
1335 "make installworld".
1337 Additionally, the atf-sh binary was made private by moving it into
1338 /usr/libexec/. Already-built shell test programs will keep the
1339 path to the old binary so they will break after "make delete-old"
1342 If you are using WITH_TESTS=yes (not the default), wipe the object
1343 tree and rebuild from scratch to prevent spurious test failures.
1344 This is only needed once: the misnumbered libraries and misplaced
1345 binaries have been added to OptionalObsoleteFiles.inc so they will
1346 be removed during a clean upgrade.
1349 Clang and llvm have been upgraded to 3.4.1 release.
1352 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1353 be removed to avoid issues in the future (and has been added to
1357 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1358 past, it affected all builds that used the bsd.*.mk files. The old
1359 behavior was a bug, but people may have relied upon it. To get this
1360 behavior back, you can .include /etc/src.conf from /etc/make.conf
1361 (which is still global and isn't changed). This also changes the
1362 behavior of incremental builds inside the tree of individual
1363 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1364 Although this has survived make universe and some upgrade scenarios,
1365 other upgrade scenarios may have broken. At least one form of
1366 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1367 as well... In cases where MAKESYSPATH isn't working with this
1368 setting, you'll need to set it to the full path to your tree.
1370 One side effect of all this cleaning up is that bsd.compiler.mk
1371 is no longer implicitly included by bsd.own.mk. If you wish to
1372 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1376 The lindev device has been removed since /dev/full has been made a
1377 standard device. __FreeBSD_version has been bumped.
1380 The knob WITHOUT_VI was added to the base system, which controls
1381 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1382 in order to reorder files share/termcap and didn't build ex(1) as a
1383 build tool, so building/installing with WITH_VI is highly advised for
1384 build hosts for older releases.
1386 This issue has been fixed in stable/9 and stable/10 in r277022 and
1387 r276991, respectively.
1390 The YES_HESIOD knob has been removed. It has been obsolete for
1391 a decade. Please move to using WITH_HESIOD instead or your builds
1392 will silently lack HESIOD.
1395 The uart(4) driver has been changed with respect to its handling
1396 of the low-level console. Previously the uart(4) driver prevented
1397 any process from changing the baudrate or the CLOCAL and HUPCL
1398 control flags. By removing the restrictions, operators can make
1399 changes to the serial console port without having to reboot.
1400 However, when getty(8) is started on the serial device that is
1401 associated with the low-level console, a misconfigured terminal
1402 line in /etc/ttys will now have a real impact.
1403 Before upgrading the kernel, make sure that /etc/ttys has the
1404 serial console device configured as 3wire without baudrate to
1405 preserve the previous behaviour. E.g:
1406 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1409 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1410 to improve performance. To re-enable it, if needed, run rpcbind
1411 with command line option -W.
1414 Switched back to the GPL dtc compiler due to updates in the upstream
1415 dts files not being supported by the BSDL dtc compiler. You will need
1416 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1417 may result while building dtb files during a kernel build if you fail
1418 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1421 Clang and llvm have been upgraded to 3.4 release.
1424 The nve(4) driver has been removed. Please use the nfe(4) driver
1425 for NVIDIA nForce MCP Ethernet adapters instead.
1428 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1429 This could cause certain C++ applications using shared libraries built
1430 against the previous version of libc++ to crash. The incompatibility
1431 has now been fixed, but any C++ applications or shared libraries built
1432 between r261283 and r261801 should be recompiled.
1435 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1436 capability mode support. Please note that enabling the feature in
1437 kernel is still highly recommended.
1440 OpenSSH is now built with sandbox support, and will use sandbox as
1441 the default privilege separation method. This requires Capsicum
1442 capability mode support in kernel.
1445 The libelf and libdwarf libraries have been updated to newer
1446 versions from upstream. Shared library version numbers for
1447 these two libraries were bumped. Any ports or binaries
1448 requiring these two libraries should be recompiled.
1449 __FreeBSD_version is bumped to 1100006.
1452 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1453 instead of providing an explicit one, this would prevent such
1454 Makefile from providing its own Kyuafile in the future during
1455 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1456 intervention is needed to clean an objdir if you use NO_CLEAN:
1457 # find /usr/obj -name Kyuafile | xargs rm -f
1460 The behavior of gss_pseudo_random() for the krb5 mechanism
1461 has changed, for applications requesting a longer random string
1462 than produced by the underlying enctype's pseudo-random() function.
1463 In particular, the random string produced from a session key of
1464 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1465 be different at the 17th octet and later, after this change.
1466 The counter used in the PRF+ construction is now encoded as a
1467 big-endian integer in accordance with RFC 4402.
1468 __FreeBSD_version is bumped to 1100004.
1471 The WITHOUT_ATF build knob has been removed and its functionality
1472 has been subsumed into the more generic WITHOUT_TESTS. If you were
1473 using the former to disable the build of the ATF libraries, you
1474 should change your settings to use the latter.
1477 The default version of mtree is nmtree which is obtained from
1478 NetBSD. The output is generally the same, but may vary
1479 slightly. If you found you need identical output adding
1480 "-F freebsd9" to the command line should do the trick. For the
1481 time being, the old mtree is available as fmtree.
1484 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1485 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1486 1.1.4_8 and verify bsdyml not linked in, before running "make
1488 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1490 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1493 The stable/10 branch has been created in subversion from head
1500 Avoid using make -j when upgrading. While generally safe, there are
1501 sometimes problems using -j to upgrade. If your upgrade fails with
1502 -j, please try again without -j. From time to time in the past there
1503 have been problems using -j with buildworld and/or installworld. This
1504 is especially true when upgrading between "distant" versions (eg one
1505 that cross a major release boundary or several minor releases, or when
1506 several months have passed on the -current branch).
1508 Sometimes, obscure build problems are the result of environment
1509 poisoning. This can happen because the make utility reads its
1510 environment when searching for values for global variables. To run
1511 your build attempts in an "environmental clean room", prefix all make
1512 commands with 'env -i '. See the env(1) manual page for more details.
1514 When upgrading from one major version to another it is generally best to
1515 upgrade to the latest code in the currently installed branch first, then
1516 do an upgrade to the new branch. This is the best-tested upgrade path,
1517 and has the highest probability of being successful. Please try this
1518 approach if you encounter problems with a major version upgrade. Since
1519 the stable 4.x branch point, one has generally been able to upgrade from
1520 anywhere in the most recent stable branch to head / current (or even the
1521 last couple of stable branches). See the top of this file when there's
1524 When upgrading a live system, having a root shell around before
1525 installing anything can help undo problems. Not having a root shell
1526 around can lead to problems if pam has changed too much from your
1527 starting point to allow continued authentication after the upgrade.
1529 This file should be read as a log of events. When a later event changes
1530 information of a prior event, the prior event should not be deleted.
1531 Instead, a pointer to the entry with the new information should be
1532 placed in the old entry. Readers of this file should also sanity check
1533 older entries before relying on them blindly. Authors of new entries
1534 should write them with this in mind.
1538 When upgrading the boot ZFS pool to a new version, always follow
1541 1.) recompile and reinstall the ZFS boot loader and boot block
1542 (this is part of "make buildworld" and "make installworld")
1544 2.) update the ZFS boot block on your boot drive
1546 The following example updates the ZFS boot block on the first
1547 partition (freebsd-boot) of a GPT partitioned drive ada0:
1548 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1550 Non-boot pools do not need these updates.
1554 If you are updating from a prior version of FreeBSD (even one just
1555 a few days old), you should follow this procedure. It is the most
1556 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1558 make kernel-toolchain
1559 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1560 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1562 To test a kernel once
1563 ---------------------
1564 If you just want to boot a kernel once (because you are not sure
1565 if it works, or if you want to boot a known bad kernel to provide
1566 debugging information) run
1567 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1568 nextboot -k testkernel
1570 To rebuild everything and install it on the current system.
1571 -----------------------------------------------------------
1572 # Note: sometimes if you are running current you gotta do more than
1573 # is listed here if you are upgrading from a really old current.
1575 <make sure you have good level 0 dumps>
1577 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1578 make installkernel KERNCONF=YOUR_KERNEL_HERE
1580 <reboot in single user> [3]
1587 To cross-install current onto a separate partition
1588 --------------------------------------------------
1589 # In this approach we use a separate partition to hold
1590 # current's root, 'usr', and 'var' directories. A partition
1591 # holding "/", "/usr" and "/var" should be about 2GB in
1594 <make sure you have good level 0 dumps>
1597 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1598 <maybe newfs current's root partition>
1599 <mount current's root partition on directory ${CURRENT_ROOT}>
1600 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1601 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1602 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1603 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1604 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1605 <reboot into current>
1606 <do a "native" rebuild/install as described in the previous section>
1607 <maybe install compatibility libraries from ports/misc/compat*>
1611 To upgrade in-place from stable to current
1612 ----------------------------------------------
1613 <make sure you have good level 0 dumps>
1615 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1616 make installkernel KERNCONF=YOUR_KERNEL_HERE
1618 <reboot in single user> [3]
1625 Make sure that you've read the UPDATING file to understand the
1626 tweaks to various things you need. At this point in the life
1627 cycle of current, things change often and you are on your own
1628 to cope. The defaults can also change, so please read ALL of
1629 the UPDATING entries.
1631 Also, if you are tracking -current, you must be subscribed to
1632 freebsd-current@freebsd.org. Make sure that before you update
1633 your sources that you have read and understood all the recent
1634 messages there. If in doubt, please track -stable which has
1635 much fewer pitfalls.
1637 [1] If you have third party modules, such as vmware, you
1638 should disable them at this point so they don't crash your
1641 [3] From the bootblocks, boot -s, and then do
1646 adjkerntz -i # if CMOS is wall time
1647 Also, when doing a major release upgrade, it is required that
1648 you boot into single user mode to do the installworld.
1650 [4] Note: This step is non-optional. Failure to do this step
1651 can result in a significant reduction in the functionality of the
1652 system. Attempting to do it by hand is not recommended and those
1653 that pursue this avenue should read this file carefully, as well
1654 as the archives of freebsd-current and freebsd-hackers mailing lists
1655 for potential gotchas. The -U option is also useful to consider.
1656 See mergemaster(8) for more information.
1658 [5] Usually this step is a no-op. However, from time to time
1659 you may need to do this if you get unknown user in the following
1660 step. It never hurts to do it all the time. You may need to
1661 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1662 install) after the buildworld before this step if you last updated
1663 from current before 20130425 or from -stable before 20130430.
1665 [6] This only deletes old files and directories. Old libraries
1666 can be deleted by "make delete-old-libs", but you have to make
1667 sure that no program is using those libraries anymore.
1669 [8] In order to have a kernel that can run the 4.x binaries needed to
1670 do an installworld, you must include the COMPAT_FREEBSD4 option in
1671 your kernel. Failure to do so may leave you with a system that is
1672 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1673 required to run the 5.x binaries on more recent kernels. And so on
1674 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1676 Make sure that you merge any new devices from GENERIC since the
1677 last time you updated your kernel config file.
1679 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1680 "?=" instead of the "=" assignment operator, so that buildworld can
1681 override the CPUTYPE if it needs to.
1683 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1684 not on the command line, or in /etc/make.conf. buildworld will
1685 warn if it is improperly defined.
1688 This file contains a list, in reverse chronological order, of major
1689 breakages in tracking -current. It is not guaranteed to be a complete
1690 list of such breakages, and only contains entries since September 23, 2011.
1691 If you need to see UPDATING entries from before that date, you will need
1692 to fetch an UPDATING file from an older FreeBSD release.
1694 Copyright information:
1696 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1698 Redistribution, publication, translation and use, with or without
1699 modification, in full or in part, in any form or format of this
1700 document are permitted without further permission from the author.
1702 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1703 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1704 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1705 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1706 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1707 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1708 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1709 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1710 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1711 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1712 POSSIBILITY OF SUCH DAMAGE.
1714 Contact Warner Losh if you have any questions about your use of