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