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