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.
20 The stable/12 branch has been created in subversion from head
24 Ports for the DRM modules have been simplified. Now, amd64 users should
25 just install the drm-kmod port. All others should install
28 Graphics hardware that's newer than about 2010 usually works with
29 drm-kmod. For hardware older than 2013, however, some users will need
30 to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
31 than 2008 usually only works in drm-legacy-kmod. The graphics team can
32 only commit to hardware made since 2013 due to the complexity of the
33 market and difficulty to test all the older cards effectively. If you
34 have hardware supported by drm-kmod, you are strongly encouraged to use
35 that as you will get better support.
37 Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
38 elsewhere, the drm and drm2 modules will be eliminated from the src base
39 soon (with a limited exception for arm). Please update to the package asap
40 and report any issues to x11@freebsd.org.
42 Generally, anybody using the drm*-kmod packages should add
43 WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
44 cross-threading surprises, especially with automatic driver
45 loading from X11 startup. These will become the defaults in 13-current
49 OpenSSL has been updated to version 1.1.1. This update included
50 additional various API changes througout the base system. It is
51 important to rebuild third-party software after upgrading. The value
52 of __FreeBSD_version has been bumped accordingly.
55 The legacy DRM modules and drivers have now been added to the loader's
56 module blacklist, in favor of loading them with kld_list in rc.conf(5).
57 The module blacklist may be overridden with the loader.conf(5)
58 'module_blacklist' variable, but loading them via rc.conf(5) is strongly
62 The cam(4) based nda(4) driver will be used over nvd(4) by default on
63 powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
64 loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
65 driver. Make sure to edit /boot/etc/kboot.conf and fstab to use the
69 Reproducible build mode is now on by default, in preparation for
70 FreeBSD 12.0. This eliminates build metadata such as the user,
71 host, and time from the kernel (and uname), unless the working tree
72 corresponds to a modified checkout from a version control system.
73 The previous behavior can be obtained by setting the /etc/src.conf
74 knob WITHOUT_REPRODUCIBLE_BUILD.
77 The Yarrow CSPRNG has been removed from the kernel as it has not been
78 supported by its designers since at least 2003. Fortuna has been the
79 default since FreeBSD-11.
82 devctl freeze/thaw have gone into the tree, the rc scripts have been
83 updated to use them and devmatch has been changed. You should update
84 kernel, userland and rc scripts all at the same time.
87 The default interpreter has been switched from 4th to Lua.
88 LOADER_DEFAULT_INTERP, documented in build(7), will override the default
89 interpreter. If you have custom FORTH code you will need to set
90 LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
91 src.conf for the build. This will create default hard links between
92 loader and loader_4th instead of loader and loader_lua, the new default.
93 If you are using UEFI it will create the proper hard link to loader.efi.
95 bhyve uses userboot.so. It remains 4th-only until some issues are solved
96 regarding coexisting with multiple versions of FreeBSD are resolved.
99 ls(1) now respects the COLORTERM environment variable used in other
100 systems and software to indicate that a colored terminal is both
101 supported and desired. If ls(1) is suddenly emitting colors, they may
102 be disabled again by either removing the unwanted COLORTERM from your
103 environment, or using `ls --color=never`. The ls(1) specific CLICOLOR
104 may not be observed in a future release.
107 The default pager for most commands has been changed to "less". To
108 restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
112 The jedec_ts(4) driver has been removed. A superset of its functionality
113 is available in the jedec_dimm(4) driver, and the manpage for that
114 driver includes migration instructions. If you have "device jedec_ts"
115 in your kernel configuration file, it must be removed.
118 amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
119 This should have no effect if the kernel is booted via BIOS/legacy boot.
120 EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
121 has a buggy firmware that prevents a successful boot due to use of
125 Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
126 support has been removed from the tree. These ports were
127 obsolete and/or known to be broken for many years.
130 loader.efi has been augmented to participate more fully in the
131 UEFI boot manager protocol. loader.efi will now look at the
132 BootXXXX environment variable to determine if a specific kernel
133 or root partition was specified. XXXX is derived from BootCurrent.
134 efibootmgr(8) manages these standard UEFI variables.
137 zfsloader's functionality has now been folded into loader.
138 zfsloader is no longer necessary once you've updated your
139 boot blocks. For a transition period, we will install a
140 hardlink for zfsloader to loader to allow a smooth transition
141 until the boot blocks can be updated (hard link because old
142 zfs boot blocks don't understand symlinks).
145 ARM64 now have efifb support, if you want to have serial console
146 on your arm64 board when an screen is connected and the bootloader
147 setup a frambuffer for us to use, just add :
151 For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
152 an screen connected as the firmware will setup a framebuffer are that
153 u-boot will expose as an EFI framebuffer.
156 New uid:gid added, ntpd:ntpd (123:123). Be sure to run mergemaster
157 or take steps to update /etc/passwd before doing installworld on
158 existing systems. Do not skip the "mergemaster -Fp" step before
159 installworld, as described in the update procedures near the bottom
160 of this document. Also, rc.d/ntpd now starts ntpd(8) as user ntpd
161 if the new mac_ntpd(4) policy is available, unless ntpd_flags or
162 the ntp config file contain options that change file/dir locations.
163 When such options (e.g., "statsdir" or "crypto") are used, ntpd can
164 still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
165 taking steps to ensure that all required files/dirs are accessible
169 Big endian arm support has been removed.
172 The static environment setup in kernel configs is no longer mutually
173 exclusive with the loader(8) environment by default. In order to
174 restore the previous default behavior of disabling the loader(8)
175 environment if a static environment is present, you must specify
176 loader_env.disabled=1 in the static environment.
179 The ABI of syscalls used by management tools like sockstat and
180 netstat has been broken to allow 32-bit binaries to work on
181 64-bit kernels without modification. These programs will need
182 to match the kernel in order to function. External programs may
183 require minor modifications to accommodate a change of type in
184 structures from pointers to 64-bit virtual addresses.
187 On i386 and amd64 atomics are now inlined. Out of tree modules using
188 atomics will need to be rebuilt.
191 The '%I' format in the kern.corefile sysctl limits the number of
192 core files that a process can generate to the number stored in the
193 debug.ncores sysctl. The '%I' format is replaced by the single digit
194 index. Previously, if all indexes were taken the kernel would overwrite
195 only a core file with the highest index in a filename.
196 Currently the system will create a new core file if there is a free
197 index or if all slots are taken it will overwrite the oldest one.
200 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
201 6.0.1. Please see the 20141231 entry below for information about
202 prerequisites and upgrading, if you are not already using clang 3.5.0
206 r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
207 needed to be changed to work with it. This change was made with r335763
208 and requires a mergemaster / etcupdate / etc to update the installed file.
211 r334930 changed the interface between the NFS modules, so they all
212 need to be rebuilt. r335018 did a __FreeBSD_version bump for this.
215 As of r334391 lld is the default amd64 system linker; it is installed
216 as /usr/bin/ld. Kernel build workarounds (see 20180510 entry) are no
220 The kernel / userland interface for devinfo changed, so you'll
221 need a new kernel and userland as a pair for it to work (rebuilding
222 lib/libdevinfo is all that's required). devinfo and devmatch will
223 not work, but everything else will when there's a mismatch.
226 The on-disk format for hwpmc callchain records has changed to include
227 threadid corresponding to a given record. This changes the field offsets
228 and thus requires that libpmcstat be rebuilt before using a kernel
232 The vxge(4) driver has been removed. This driver was introduced into
233 HEAD one week before the Exar left the Ethernet market and is not
234 known to be used. If you have device vxge in your kernel config file
238 The amd64 kernel now requires a ld that supports ifunc to produce a
239 working kernel, either lld or a newer binutils. lld is built by default
240 on amd64, and the 'buildkernel' target uses it automatically. However,
241 it is not the default linker, so building the kernel the traditional
242 way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
243 binutils port/package). lld will soon be default, and this requirement
246 NOTE: As of r334391 lld is the default system linker on amd64, and no
247 workaround is necessary.
250 The nxge(4) driver has been removed. This driver was for PCI-X 10g
251 cards made by s2io/Neterion. The company was aquired by Exar and
252 no longer sells or supports Ethernet products. If you have device
253 nxge in your kernel config file it must be removed.
256 The tz database (tzdb) has been updated to 2018e. This version more
257 correctly models time stamps in time zones with negative DST such as
258 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
259 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
260 time zone abbreviations and the tm_isdst flag.
263 The ixgb(4) driver has been removed. This driver was for an early and
264 uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
265 quickly shifted to the long lived ixgbe family. If you have device
266 ixgb in your kernel config file it must be removed.
269 The lmc(4) driver has been removed. This was a WAN interface
270 card that was already reportedly rare in 2003, and had an ambiguous
271 license. If you have device lmc in your kernel config file it must
275 Support for Arcnet networks has been removed. If you have device
276 arcnet or device cm in your kernel config file they must be
280 Support for FDDI networks has been removed. If you have device
281 fddi or device fpa in your kernel config file they must be
285 In addition to supporting RFC 3164 formatted messages, the
286 syslogd(8) service is now capable of parsing RFC 5424 formatted
287 log messages. The main benefit of using RFC 5424 is that clients
288 may now send log messages with timestamps containing year numbers,
289 microseconds and time zone offsets.
291 Similarly, the syslog(3) C library function has been altered to
292 send RFC 5424 formatted messages to the local system logging
293 daemon. On systems using syslogd(8), this change should have no
294 negative impact, as long as syslogd(8) and the C library are
295 updated at the same time. On systems using a different system
296 logging daemon, it may be necessary to make configuration
297 adjustments, depending on the software used.
299 When using syslog-ng, add the 'syslog-protocol' flag to local
300 input sources to enable parsing of RFC 5424 formatted messages:
303 unix-dgram("/var/run/log" flags(syslog-protocol));
306 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
307 of the 'imuxsock' module to let messages be processed by the
308 regular RFC 3164/5424 parsing pipeline:
310 module(load="imuxsock" SysSock.UseSpecialParser="off")
312 Do note that these changes only affect communication between local
313 applications and syslogd(8). The format that syslogd(8) uses to
314 store messages on disk or forward messages to other systems
315 remains unchanged. syslogd(8) still uses RFC 3164 for these
316 purposes. Options to customize this behaviour will be added in the
317 future. Utilities that process log files stored in /var/log are
318 thus expected to continue to function as before.
320 __FreeBSD_version has been incremented to 1200061 to denote this
324 Support for token ring networks has been removed. If you
325 have "device token" in your kernel config you should remove
326 it. No device drivers supported token ring.
329 makefs was modified to be able to tag ISO9660 El Torito boot catalog
330 entries as EFI instead of overloading the i386 tag as done previously.
331 The amd64 mkisoimages.sh script used to build amd64 ISO images for
332 release was updated to use this. This may mean that makefs must be
333 updated before "make cdrom" can be run in the release directory. This
334 should be as simple as:
336 $ cd $SRCDIR/usr.sbin/makefs
337 $ make depend all install
340 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
341 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
342 Co-existance for the transition period will come shortly. Booting is a
343 complex environment and test coverage for Lua-enabled loaders has been
344 thin, so it would be prudent to assume it might not work and make
345 provisions for backup boot methods.
348 devmatch functionality has been turned on in devd. It will automatically
349 load drivers for unattached devices. This may cause unexpected drivers to
350 be loaded. Please report any problems to current@ and imp@freebsd.org.
353 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
354 6.0.0. Please see the 20141231 entry below for information about
355 prerequisites and upgrading, if you are not already using clang 3.5.0
359 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
360 This means it is used to link the kernel and userland libraries and
361 executables, but is not yet installed as /usr/bin/ld by default.
363 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
364 WITHOUT_LLD_BOOTSTRAP=yes
367 On i386, pmtimer has been removed. Its functionality has been folded
368 into apm. It was a no-op on ACPI in current for a while now (but was still
369 needed on i386 in FreeBSD 11 and earlier). Users may need to remove it
370 from kernel config files.
373 The use of RSS hash from the network card aka flowid has been
374 disabled by default for lagg(4) as it's currently incompatible with
375 the lacp and loadbalance protocols.
377 This can be re-enabled by setting the following in loader.conf:
378 net.link.lagg.default_use_flowid="1"
381 The SW_WATCHDOG option is no longer necessary to enable the
382 hardclock-based software watchdog if no hardware watchdog is
383 configured. As before, SW_WATCHDOG will cause the software
384 watchdog to be enabled even if a hardware watchdog is configured.
387 r326887 fixes the issue described in the 20171214 UPDATING entry.
388 r326888 flips the switch back to building GELI support always.
391 r362593 broke ZFS + GELI support for reasons unknown. However,
392 it also broke ZFS support generally, so GELI has been turned off
393 by default as the lesser evil in r326857. If you boot off ZFS and/or
394 GELI, it might not be a good time to update.
397 PowerPC users must update loader(8) by rebuilding world before
398 installing a new kernel, as the protocol connecting them has
399 changed. Without the update, loader metadata will not be passed
400 successfully to the kernel and users will have to enter their
401 root partition at the kernel mountroot prompt to continue booting.
402 Newer versions of loader can boot old kernels without issue.
405 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
406 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
407 to WITH/OUT_LOADER_GELI.
410 The naive and non-compliant support of posix_fallocate(2) in ZFS
411 has been removed as of r325320. The system call now returns EINVAL
412 when used on a ZFS file. Although the new behavior complies with the
413 standard, some consumers are not prepared to cope with it.
414 One known victim is lld prior to r325420.
417 Building in a FreeBSD src checkout will automatically create object
418 directories now rather than store files in the current directory if
419 'make obj' was not ran. Calling 'make obj' is no longer necessary.
420 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
421 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
425 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
426 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
427 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
428 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
429 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
430 The UNIFIED_OBJDIR option is a transitional feature that will be
431 removed for 12.0 release; please migrate to the new format for any
432 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
433 than hardcoding paths.
436 The native-xtools target no longer installs the files by default to the
437 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
438 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
441 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
442 options are changing from controlling the build if defined / undefined
443 to controlling the build with explicit 'yes' or 'no' values. They will
444 shift to WITH/WITHOUT options to match other options in the system.
447 libstand has turned into a private library for sys/boot use only.
448 It is no longer supported as a public interface outside of sys/boot.
451 The arm port has split armv6 into armv6 and armv7. armv7 is now
452 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
453 and are running a kernel from before r324363, you will need to add
454 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
457 When building multiple kernels using KERNCONF, non-existent KERNCONF
458 files will produce an error and buildkernel will fail. Previously
459 missing KERNCONF files silently failed giving no indication as to
460 why, only to subsequently discover during installkernel that the
461 desired kernel was never built in the first place.
464 The default serial number format for CTL LUNs has changed. This will
465 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
466 or iSCSI clients care about their LUNs' serial numbers. Users who
467 require serial number stability should hardcode serial numbers in
471 For 32-bit arm compiled for hard-float support, soft-floating point
472 binaries now always get their shared libraries from
473 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
474 /usr/libsoft also existed). Only users with a hard-float ld.so, but
475 soft-float everything else should be affected.
478 The geli password typed at boot is now hidden. To restore the previous
479 behavior, see geli(8) for configuration options.
482 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
483 sysctl values. Minor nit, but requires a rebuild of both world/kernel
487 "make check" behavior (made in ^/head@r295380) has been changed to
488 execute from a limited sandbox, as opposed to executing from
492 - The "beforecheck" and "aftercheck" targets are now specified.
493 - ${CHECKDIR} (added in commit noted above) has been removed.
494 - Legacy behavior can be enabled by setting
495 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
497 If the limited sandbox mode is enabled, "make check" will execute
498 "make distribution", then install, execute the tests, and clean up the
499 sandbox if successful.
501 The "make distribution" and "make install" targets are typically run as
502 root to set appropriate permissions and ownership at installation time.
503 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
504 environment if executing "make check" with limited sandbox mode using
505 an unprivileged user.
508 Since the switch to GPT disk labels, fsck for UFS/FFS has been
509 unable to automatically find alternate superblocks. As of r322297,
510 the information needed to find alternate superblocks has been
511 moved to the end of the area reserved for the boot block.
512 Filesystems created with a newfs of this vintage or later
513 will create the recovery information. If you have a filesystem
514 created prior to this change and wish to have a recovery block
515 created for your filesystem, you can do so by running fsck in
516 foreground mode (i.e., do not use the -p or -y options). As it
517 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
518 to which you should answer yes.
521 As of r321665, an NFSv4 server configuration that services
522 Kerberos mounts or clients that do not support the uid/gid in
523 owner/owner_group string capability, must explicitly enable
524 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
525 machine's /etc/rc.conf file.
528 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
529 Please see the 20141231 entry below for information about prerequisites
530 and upgrading, if you are not already using clang 3.5.0 or higher.
533 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
534 r-commands (rlogin, rsh, etc.) to be built with the base system.
537 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
538 a very major ABI incompatible change, so users of FreeBSD/powerpc must
539 be careful when performing source upgrades. It is best to run
540 'make installworld' from an alternate root system, either a live
541 CD/memory stick, or a temporary root partition. Additionally, all ports
542 must be recompiled. powerpc64 is largely unaffected, except in the case
543 of 32-bit compatibility. All 32-bit binaries will be affected.
546 Forward compatibility for the "ino64" project have been committed. This
547 will allow most new binaries to run on older kernels in a limited
548 fashion. This prevents many of the common foot-shooting actions in the
549 upgrade as well as the limited ability to roll back the kernel across
550 the ino64 upgrade. Complicated use cases may not work properly, though
551 enough simpler ones work to allow recovery in most situations.
554 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
555 if you require the GPL compiler.
558 The internal ABI used for communication between the NFS kernel modules
559 was changed by r320085, so __FreeBSD_version was bumped to
560 ensure all the NFS related modules are updated together.
563 The ABI of struct event was changed by extending the data
564 member to 64bit and adding ext fields. For upgrade, same
565 precautions as for the entry 20170523 "ino64" must be
569 The GNU roff toolchain has been removed from base. To render manpages
570 which are not supported by mandoc(1), man(1) can fallback on GNU roff
571 from ports (and recommends to install it).
572 To render roff(7) documents, consider using GNU roff from ports or the
573 heirloom doctools roff toolchain from ports via pkg install groff or
574 via pkg install heirloom-doctools.
577 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
578 smaller runtime footprint builds. This is useful for embedded systems
579 which only require one chipset support.
581 If you load it as a module, make sure this is in /boot/loader.conf:
585 This will load the HAL, all chip/RF backends and if_ath_pci.
586 If you have if_ath_pci in /boot/loader.conf, ensure it is after
587 if_ath or it will not load any HAL chipset support.
589 If you want to selectively load things (eg on ye cheape ARM/MIPS
590 platforms where RAM is at a premium) you should:
593 * load the chip modules in question
594 * load ath_rate, ath_dfs
596 * load if_ath_pci and/or if_ath_ahb depending upon your particular
597 bus bind type - this is where probe/attach is done.
599 For further comments/feedback, poke adrian@ .
602 The "ino64" 64-bit inode project has been committed, which extends
603 a number of types to 64 bits. Upgrading in place requires care and
604 adherence to the documented upgrade procedure.
606 If using a custom kernel configuration ensure that the
607 COMPAT_FREEBSD11 option is included (as during the upgrade the
608 system will be running the ino64 kernel with the existing world).
610 For the safest in-place upgrade begin by removing previous build
611 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
612 full procedure documented below under the heading "To rebuild
613 everything and install it on the current system." Specifically,
614 a reboot is required after installing the new kernel before
618 The NATM framework including the en(4), fatm(4), hatm(4), and
619 patm(4) devices has been removed. Consumers should plan a
620 migration before the end-of-life date for FreeBSD 11.
623 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
624 diff has not been implemented, if those are needed a newer version of
625 GNU diff is available via the diffutils package under the gdiff name.
628 As of r316810 for ipfilter, keep frags is no longer assumed when
629 keep state is specified in a rule. r316810 aligns ipfilter with
630 documentation in man pages separating keep frags from keep state.
631 This allows keep state to be specified without forcing keep frags
632 and allows keep frags to be specified independently of keep state.
633 To maintain previous behaviour, also specify keep frags with
634 keep state (as documented in ipf.conf.5).
637 arm64 builds now use the base system LLD 4.0.0 linker by default,
638 instead of requiring that the aarch64-binutils port or package be
639 installed. To continue using aarch64-binutils, set
640 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
643 The UDP optimization in entry 20160818 that added the sysctl
644 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
645 packets will no longer be treated as L3 broadcast packets.
648 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
649 use any explicitly assigned loopback address available in the jail
650 instead of using the first assigned address of the jail.
653 The ctl.ko module no longer implements the iSCSI target frontend:
654 cfiscsi.ko does instead.
656 If building cfiscsi.ko as a kernel module, the module can be loaded
657 via one of the following methods:
658 - `cfiscsi_load="YES"` in loader.conf(5).
659 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
660 - ctladm(8)/ctld(8), when compiled with iSCSI support
661 (`WITH_ISCSI=yes` in src.conf(5))
663 Please see cfiscsi(4) for more details.
666 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
667 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
668 same source (previously, the dependency of mmcsd.ko on mmc.ko was
669 missing, but mmcsd.ko now will refuse to load if it is incompatible
673 The syntax of ipfw(8) named states was changed to avoid ambiguity.
674 If you have used named states in the firewall rules, you need to modify
675 them after installworld and before rebooting. Now named states must
676 be prefixed with colon.
679 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
680 removed as the userland we provide cannot use them. The KMS version
681 (sys/dev/drm2) supports the same hardware.
684 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
685 Please see the 20141231 entry below for information about prerequisites
686 and upgrading, if you are not already using clang 3.5.0 or higher.
689 The code that provides support for ZFS .zfs/ directory functionality
690 has been reimplemented. It's not possible now to create a snapshot
691 by mkdir under .zfs/snapshot/. That should be the only user visible
695 EISA bus support has been removed. The WITH_EISA option is no longer
699 MCA bus support has been removed.
702 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
703 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
706 The EM_MULTIQUEUE kernel configuration option is deprecated now that
707 the em(4) driver conforms to iflib specifications.
710 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
711 IFLIB. If you have a custom kernel configuration that excludes em(4)
712 but you use igb(4), you need to re-add em(4) to your custom configuration.
715 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
716 Please see the 20141231 entry below for information about prerequisites
717 and upgrading, if you are not already using clang 3.5.0 or higher.
720 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
721 Please see the 20141231 entry below for information about prerequisites
722 and upgrading, if you are not already using clang 3.5.0 or higher.
725 The layout of the pmap structure has changed for powerpc to put the pmap
726 statistics at the front for all CPU variations. libkvm(3) and all tools
727 that link against it need to be recompiled.
730 isl(4) and cyapa(4) drivers now require a new driver,
731 chromebook_platform(4), to work properly on Chromebook-class hardware.
732 On other types of hardware the drivers may need to be configured using
733 device hints. Please see the corresponding manual pages for details.
736 The urtwn(4) driver was merged into rtwn(4) and now consists of
737 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
739 Also, firmware for RTL8188CE was renamed due to possible name
740 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
743 GNU rcs has been removed from base. It is available as packages:
744 - rcs: Latest GPLv3 GNU rcs version.
745 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
749 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
750 modules now requires that the kernel configuration contain the
751 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
754 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
755 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
758 Relocatable object files with the extension of .So have been renamed
759 to use an extension of .pico instead. The purpose of this change is
760 to avoid a name clash with shared libraries on case-insensitive file
761 systems. On those file systems, foo.So is the same file as foo.so.
764 GNU rcs has been turned off by default. It can (temporarily) be built
765 again by adding WITH_RCS knob in src.conf.
766 Otherwise, GNU rcs is available from packages:
767 - rcs: Latest GPLv3 GNU rcs version.
768 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
771 The backup_uses_rcs functionality has been removed from rc.subr.
774 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
775 two separate components, QUEUE_MACRO_DEBUG_TRACE and
776 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
777 QUEUE_MACRO_DEBUG behavior.
780 r304787 changed some ioctl interfaces between the iSCSI userspace
781 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
782 rebuilt to work with new kernels. __FreeBSD_version has been bumped
786 The UDP receive code has been updated to only treat incoming UDP
787 packets that were addressed to an L2 broadcast address as L3
788 broadcast packets. It is not expected that this will affect any
789 standards-conforming UDP application. The new behaviour can be
790 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
794 Remove the openbsd_poll system call.
795 __FreeBSD_version has been bumped because of this.
798 The stable/11 branch has been created from head@r302406.
801 The libc stub for the pipe(2) system call has been replaced with
802 a wrapper that calls the pipe2(2) system call and the pipe(2)
803 system call is now only implemented by the kernels that include
804 "options COMPAT_FREEBSD10" in their config file (this is the
805 default). Users should ensure that this option is enabled in
806 their kernel or upgrade userspace to r302092 before upgrading their
810 CAM will now strip leading spaces from SCSI disks' serial numbers.
811 This will affect users who create UFS filesystems on SCSI disks using
812 those disk's diskid device nodes. For example, if /etc/fstab
813 previously contained a line like
814 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
815 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
816 transforms like gmirror may also be affected. ZFS users should
820 The bitstring(3) API has been updated with new functionality and
821 improved performance. But it is binary-incompatible with the old API.
822 Objects built with the new headers may not be linked against objects
823 built with the old headers.
826 The brk and sbrk functions have been removed from libc on arm64.
827 Binutils from ports has been updated to not link to these
828 functions and should be updated to the latest version before
829 installing a new libc.
832 The armv6 port now defaults to hard float ABI. Limited support
833 for running both hardfloat and soft float on the same system
834 is available using the libraries installed with -DWITH_LIBSOFT.
835 This has only been tested as an upgrade path for installworld
836 and packages may fail or need manual intervention to run. New
837 packages will be needed.
839 To update an existing self-hosted armv6hf system, you must add
840 TARGET_ARCH=armv6 on the make command line for both the build
841 and the install steps.
844 Kernel modules compiled outside of a kernel build now default to
845 installing to /boot/modules instead of /boot/kernel. Many kernel
846 modules built this way (such as those in ports) already overrode
847 KMODDIR explicitly to install into /boot/modules. However,
848 manually building and installing a module from /sys/modules will
849 now install to /boot/modules instead of /boot/kernel.
852 The CAM I/O scheduler has been committed to the kernel. There should be
853 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
854 list of known rogues that claim support for this but actually corrupt
855 data is believed to be complete, be on the lookout for data
856 corruption. The known rogue list is believed to be complete:
858 o Crucial MX100, M550 drives with MU01 firmware.
859 o Micron M510 and M550 drives with MU01 firmware.
860 o Micron M500 prior to MU07 firmware
861 o Samsung 830, 840, and 850 all firmwares
862 o FCCT M500 all firmwares
864 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
865 with working NCQ TRIM. For Micron branded drives, see your sales rep for
866 updated firmware. Black listed drives will work correctly because these
867 drives work correctly so long as no NCQ TRIMs are sent to them. Given
868 this list is the same as found in Linux, it's believed there are no
869 other rogues in the market place. All other models from the above
872 To be safe, if you are at all concerned, you can quirk each of your
873 drives to prevent NCQ from being sent by setting:
874 kern.cam.ada.X.quirks="0x2"
875 in loader.conf. If the drive requires the 4k sector quirk, set the
879 The FAST_DEPEND build option has been removed and its functionality is
880 now the one true way. The old mkdep(1) style of 'make depend' has
881 been removed. See 20160311 for further details.
884 Resource range types have grown from unsigned long to uintmax_t. All
885 drivers, and anything using libdevinfo, need to be recompiled.
888 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
889 builds. It no longer runs mkdep(1) during 'make depend', and the
890 'make depend' stage can safely be skipped now as it is auto ran
891 when building 'make all' and will generate all SRCS and DPSRCS before
892 building anything else. Dependencies are gathered at compile time with
893 -MF flags kept in separate .depend files per object file. Users should
894 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
898 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
899 kernel modules. Therefore, if you load any kernel modules at boot time,
900 please install the boot loaders after you install the kernel, but before
904 make buildkernel KERNCONF=YOUR_KERNEL_HERE
905 make installkernel KERNCONF=YOUR_KERNEL_HERE
906 make -C sys/boot install
907 <reboot in single user>
909 Then follow the usual steps, described in the General Notes section,
913 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
914 see the 20141231 entry below for information about prerequisites and
915 upgrading, if you are not already using clang 3.5.0 or higher.
918 The AIO subsystem is now a standard part of the kernel. The
919 VFS_AIO kernel option and aio.ko kernel module have been removed.
920 Due to stability concerns, asynchronous I/O requests are only
921 permitted on sockets and raw disks by default. To enable
922 asynchronous I/O requests on all file types, set the
923 vfs.aio.enable_unsafe sysctl to a non-zero value.
926 The ELF object manipulation tool objcopy is now provided by the
927 ELF Tool Chain project rather than by GNU binutils. It should be a
928 drop-in replacement, with the addition of arm64 support. The
929 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
930 to obtain the GNU version if necessary.
933 Building ZFS pools on top of zvols is prohibited by default. That
934 feature has never worked safely; it's always been prone to deadlocks.
935 Using a zvol as the backing store for a VM guest's virtual disk will
936 still work, even if the guest is using ZFS. Legacy behavior can be
937 restored by setting vfs.zfs.vol.recursive=1.
940 The NONE and HPN patches has been removed from OpenSSH. They are
941 still available in the security/openssh-portable port.
944 With the addition of ypldap(8), a new _ypldap user is now required
945 during installworld. "mergemaster -p" can be used to add the user
946 prior to installworld, as documented in the handbook.
949 The tftp loader (pxeboot) now uses the option root-path directive. As a
950 consequence it no longer looks for a pxeboot.4th file on the tftp
951 server. Instead it uses the regular /boot infrastructure as with the
955 The code to start recording plug and play data into the modules has
956 been committed. While the old tools will properly build a new kernel,
957 a number of warnings about "unknown metadata record 4" will be produced
958 for an older kldxref. To avoid such warnings, make sure to rebuild
959 the kernel toolchain (or world). Make sure that you have r292078 or
960 later when trying to build 292077 or later before rebuilding.
963 Debug data files are now built by default with 'make buildworld' and
964 installed with 'make installworld'. This facilitates debugging but
965 requires more disk space both during the build and for the installed
966 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
970 r291527 changed the internal interface between the nfsd.ko and
971 nfscommon.ko modules. As such, they must both be upgraded to-gether.
972 __FreeBSD_version has been bumped because of this.
975 Add support for unicode collation strings leads to a change of
976 order of files listed by ls(1) for example. To get back to the old
977 behaviour, set LC_COLLATE environment variable to "C".
979 Databases administrators will need to reindex their databases given
980 collation results will be different.
982 Due to a bug in install(1) it is recommended to remove the ancient
983 locales before running make installworld.
985 rm -rf /usr/share/locale/*
988 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
989 libcrypto.so.7 or libssl.so.7 must be recompiled.
992 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
993 Kernel modules isp_2400_multi and isp_2500_multi were removed and
994 should be replaced with isp_2400 and isp_2500 modules respectively.
997 The build previously allowed using 'make -n' to not recurse into
998 sub-directories while showing what commands would be executed, and
999 'make -n -n' to recursively show commands. Now 'make -n' will recurse
1000 and 'make -N' will not.
1003 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1004 and etcupdate will now use this file. A custom sendmail.cf is now
1005 updated via this mechanism rather than via installworld. If you had
1006 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1007 want to remove the exclusion or change it to "always install".
1008 /etc/mail/sendmail.cf is now managed the same way regardless of
1009 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
1010 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1013 Compatibility shims for legacy ATA device names have been removed.
1014 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1015 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1016 environment variables, /dev/ad* and /dev/ar* symbolic links.
1019 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1020 Please see the 20141231 entry below for information about prerequisites
1021 and upgrading, if you are not already using clang 3.5.0 or higher.
1024 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1025 and renamed from .symbols to .debug. This reduces the size requirements
1026 on the boot partition or file system and provides consistency with
1027 userland debug files.
1029 When using the supported kernel installation method the
1030 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1031 as is done with /boot/kernel.
1033 Developers wishing to maintain the historical behavior of installing
1034 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1037 The wireless drivers had undergone changes that remove the 'parent
1038 interface' from the ifconfig -l output. The rc.d network scripts
1039 used to check presence of a parent interface in the list, so old
1040 scripts would fail to start wireless networking. Thus, etcupdate(3)
1041 or mergemaster(8) run is required after kernel update, to update your
1042 rc.d scripts in /etc.
1045 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1046 These configurations are now automatically interpreted as
1047 'scrub fragment reassemble'.
1050 Kernel-loadable modules for the random(4) device are back. To use
1051 them, the kernel must have
1054 options RANDOM_LOADABLE
1056 kldload(8) can then be used to load random_fortuna.ko
1057 or random_yarrow.ko. Please note that due to the indirect
1058 function calls that the loadable modules need to provide,
1059 the build-in variants will be slightly more efficient.
1061 The random(4) kernel option RANDOM_DUMMY has been retired due to
1062 unpopularity. It was not all that useful anyway.
1065 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1066 Control over building the ELF Tool Chain tools is now provided by
1067 the WITHOUT_TOOLCHAIN knob.
1070 The polarity of Pulse Per Second (PPS) capture events with the
1071 uart(4) driver has been corrected. Prior to this change the PPS
1072 "assert" event corresponded to the trailing edge of a positive PPS
1073 pulse and the "clear" event was the leading edge of the next pulse.
1075 As the width of a PPS pulse in a typical GPS receiver is on the
1076 order of 1 millisecond, most users will not notice any significant
1077 difference with this change.
1079 Anyone who has compensated for the historical polarity reversal by
1080 configuring a negative offset equal to the pulse width will need to
1081 remove that workaround.
1084 The default group assigned to /dev/dri entries has been changed
1085 from 'wheel' to 'video' with the id of '44'. If you want to have
1086 access to the dri devices please add yourself to the video group
1089 # pw groupmod video -m $USER
1092 The menu.rc and loader.rc files will now be replaced during
1093 upgrades. Please migrate local changes to menu.rc.local and
1094 loader.rc.local instead.
1097 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1098 strings and strip have been removed. The src.conf(5) knob
1099 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1102 As ZFS requires more kernel stack pages than is the default on some
1103 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1104 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1106 Please consider using 'options KSTACK_PAGES=X' where X is greater
1107 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1110 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
1111 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1112 default, i.e., they will not contain "::". For example, instead
1113 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
1114 to have a more specific match, such as different map entries for
1115 IPv6:0:0 vs IPv6:0. This change requires that configuration
1116 data (including maps, files, classes, custom ruleset, etc.) must
1117 use the same format, so make certain such configuration data is
1118 upgrading. As a very simple check search for patterns like
1119 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
1120 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1121 the cf option UseCompressedIPv6Addresses.
1124 The default kernel entropy-processing algorithm is now
1125 Fortuna, replacing Yarrow.
1127 Assuming you have 'device random' in your kernel config
1128 file, the configurations allow a kernel option to override
1129 this default. You may choose *ONE* of:
1131 options RANDOM_YARROW # Legacy /dev/random algorithm.
1132 options RANDOM_DUMMY # Blocking-only driver.
1134 If you have neither, you get Fortuna. For most people,
1135 read no further, Fortuna will give a /dev/random that works
1136 like it always used to, and the difference will be irrelevant.
1138 If you remove 'device random', you get *NO* kernel-processed
1139 entropy at all. This may be acceptable to folks building
1140 embedded systems, but has complications. Carry on reading,
1141 and it is assumed you know what you need.
1143 *PLEASE* read random(4) and random(9) if you are in the
1144 habit of tweaking kernel configs, and/or if you are a member
1145 of the embedded community, wanting specific and not-usual
1146 behaviour from your security subsystems.
1148 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1149 random', you will NOT have a functioning /dev/random, and
1150 many cryptographic features will not work, including SSH.
1151 You may also find strange behaviour from the random(3) set
1152 of library functions, in particular sranddev(3), srandomdev(3)
1153 and arc4random(3). The reason for this is that the KERN_ARND
1154 sysctl only returns entropy if it thinks it has some to
1155 share, and with RANDOM_DUMMY or no 'device random' this
1159 An additional fix for the issue described in the 20150614 sendmail
1160 entry below has been committed in revision 284717.
1163 FreeBSD's old make (fmake) has been removed from the system. It is
1164 available as the devel/fmake port or via pkg install fmake.
1167 The fix for the issue described in the 20150614 sendmail entry
1168 below has been committed in revision 284436. The work
1169 around described in that entry is no longer needed unless the
1170 default setting is overridden by a confDH_PARAMETERS configuration
1171 setting of '5' or pointing to a 512 bit DH parameter file.
1174 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1175 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1176 and devel/kyua to version 0.20+ and adjust any calling code to work
1177 with Kyuafile and kyua.
1180 The import of openssl to address the FreeBSD-SA-15:10.openssl
1181 security advisory includes a change which rejects handshakes
1182 with DH parameters below 768 bits. sendmail releases prior
1183 to 8.15.2 (not yet released), defaulted to a 512 bit
1184 DH parameter setting for client connections. To work around
1185 this interoperability, sendmail can be configured to use a
1186 2048 bit DH parameter by:
1188 1. Edit /etc/mail/`hostname`.mc
1189 2. If a setting for confDH_PARAMETERS does not exist or
1190 exists and is set to a string beginning with '5',
1191 replace it with '2'.
1192 3. If a setting for confDH_PARAMETERS exists and is set to
1193 a file path, create a new file with:
1194 openssl dhparam -out /path/to/file 2048
1195 4. Rebuild the .cf file:
1196 cd /etc/mail/; make; make install
1197 5. Restart sendmail:
1198 cd /etc/mail/; make restart
1200 A sendmail patch is coming, at which time this file will be
1204 Generation of legacy formatted entries have been disabled by default
1205 in pwd_mkdb(8), as all base system consumers of the legacy formatted
1206 entries were converted to use the new format by default when the new,
1207 machine independent format have been added and supported since FreeBSD
1210 Please see the pwd_mkdb(8) manual page for further details.
1213 Clang and llvm have been upgraded to 3.6.1 release. Please see the
1214 20141231 entry below for information about prerequisites and upgrading,
1215 if you are not already using 3.5.0 or higher.
1218 TI platform code switched to using vendor DTS files and this update
1219 may break existing systems running on Beaglebone, Beaglebone Black,
1222 - dtb files should be regenerated/reinstalled. Filenames are the
1223 same but content is different now
1224 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1225 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1226 addressing scheme is now pin 25 on /dev/gpioc3.
1227 - Pandaboard: /etc/ttys should be updated, serial console device is
1228 now /dev/ttyu2, not /dev/ttyu0
1231 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1232 If you need the GNU extension from groff soelim(1), install groff
1233 from package: pkg install groff, or via ports: textproc/groff.
1236 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1237 defined in symlink(7); previously symlinks were silently ignored.
1240 The const qualifier has been removed from iconv(3) to comply with
1241 POSIX. The ports tree is aware of this from r384038 onwards.
1244 Libraries specified by LIBADD in Makefiles must have a corresponding
1245 DPADD_<lib> variable to ensure correct dependencies. This is now
1246 enforced in src.libnames.mk.
1249 From legacy ata(4) driver was removed support for SATA controllers
1250 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1251 Kernel modules ataahci and ataadaptec were removed completely,
1252 replaced by ahci and mvs modules respectively.
1255 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1256 the 20141231 entry below for information about prerequisites and
1257 upgrading, if you are not already using 3.5.0 or higher.
1260 The 32-bit PowerPC kernel has been changed to a position-independent
1261 executable. This can only be booted with a version of loader(8)
1262 newer than January 31, 2015, so make sure to update both world and
1263 kernel before rebooting.
1266 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1267 but before r278950, the RNG was not seeded properly. Immediately
1268 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1269 ssh keys or openssl keys) that were generated w/ a kernel from that
1270 range. This does not affect programs that directly used /dev/random
1271 or /dev/urandom. All userland uses of arc4random(3) are affected.
1274 The autofs(4) ABI was changed in order to restore binary compatibility
1275 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1276 with the new kernel.
1279 The powerpc64 kernel has been changed to a position-independent
1280 executable. This can only be booted with a new version of loader(8),
1281 so make sure to update both world and kernel before rebooting.
1284 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1285 only release, no new features have been added. Please see the 20141231
1286 entry below for information about prerequisites and upgrading, if you
1287 are not already using 3.5.0.
1290 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1291 taken from the ELF Tool Chain project rather than GNU binutils. They
1292 should be drop-in replacements, with the addition of arm64 support.
1293 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1294 binutils tools, if necessary. See 20150805 for updated information.
1297 The default Unbound configuration now enables remote control
1298 using a local socket. Users who have already enabled the
1299 local_unbound service should regenerate their configuration
1300 by running "service local_unbound setup" as root.
1303 The GNU texinfo and GNU info pages have been removed.
1304 To be able to view GNU info pages please install texinfo from ports.
1307 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1309 As of this release, a prerequisite for building clang, llvm and lldb is
1310 a C++11 capable compiler and C++11 standard library. This means that to
1311 be able to successfully build the cross-tools stage of buildworld, with
1312 clang as the bootstrap compiler, your system compiler or cross compiler
1313 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1314 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1317 On any standard FreeBSD 10.x or 11.x installation, where clang and
1318 libc++ are on by default (that is, on x86 or arm), this should work out
1321 On 9.x installations where clang is enabled by default, e.g. on x86 and
1322 powerpc, libc++ will not be enabled by default, so libc++ should be
1323 built (with clang) and installed first. If both clang and libc++ are
1324 missing, build clang first, then use it to build libc++.
1326 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1327 the instructions for 9.x above.
1329 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1330 default, and do not build clang.
1332 Many embedded systems are resource constrained, and will not be able to
1333 build clang in a reasonable time, or in some cases at all. In those
1334 cases, cross building bootable systems on amd64 is a workaround.
1336 This new version of clang introduces a number of new warnings, of which
1337 the following are most likely to appear:
1341 This warns in two cases, for both C and C++:
1342 * When the code is trying to take the absolute value of an unsigned
1343 quantity, which is effectively a no-op, and almost never what was
1344 intended. The code should be fixed, if at all possible. If you are
1345 sure that the unsigned quantity can be safely cast to signed, without
1346 loss of information or undefined behavior, you can add an explicit
1347 cast, or disable the warning.
1349 * When the code is trying to take an absolute value, but the called
1350 abs() variant is for the wrong type, which can lead to truncation.
1351 If you want to disable the warning instead of fixing the code, please
1352 make sure that truncation will not occur, or it might lead to unwanted
1355 -Wtautological-undefined-compare and
1356 -Wundefined-bool-conversion
1358 These warn when C++ code is trying to compare 'this' against NULL, while
1359 'this' should never be NULL in well-defined C++ code. However, there is
1360 some legacy (pre C++11) code out there, which actively abuses this
1361 feature, which was less strictly defined in previous C++ versions.
1363 Squid and openjdk do this, for example. The warning can be turned off
1364 for C++98 and earlier, but compiling the code in C++11 mode might result
1365 in unexpected behavior; for example, the parts of the program that are
1366 unreachable could be optimized away.
1369 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1370 kernel sources have been removed. The .h files remain, since some
1371 utilities include them. This will need to be fixed later.
1372 If "mount -t oldnfs ..." is attempted, it will fail.
1373 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1374 the utilities will report errors.
1377 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1378 directories to top level SUBDIR variable when their parent
1379 directory is included in LOCAL_DIRS. Users with build systems with
1380 such hierarchies and without SUBDIR entries in the parent
1381 directory Makefiles should add them or add the directories to
1385 faith(4) and faithd(8) have been removed from the base system. Faith
1386 has been obsolete for a very long time.
1389 vt(4), the new console driver, is enabled by default. It brings
1390 support for Unicode and double-width characters, as well as
1391 support for UEFI and integration with the KMS kernel video
1394 You may need to update your console settings in /etc/rc.conf,
1395 most probably the keymap. During boot, /etc/rc.d/syscons will
1396 indicate what you need to do.
1398 vt(4) still has issues and lacks some features compared to
1399 syscons(4). See the wiki for up-to-date information:
1400 https://wiki.freebsd.org/Newcons
1402 If you want to keep using syscons(4), you can do so by adding
1403 the following line to /boot/loader.conf:
1407 pjdfstest has been integrated into kyua as an opt-in test suite.
1408 Please see share/doc/pjdfstest/README for more details on how to
1412 gperf has been removed from the base system for architectures
1413 that use clang. Ports that require gperf will obtain it from the
1417 pjdfstest has been moved from tools/regression/pjdfstest to
1421 At svn r271982, The default linux compat kernel ABI has been adjusted
1422 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1423 update. If you wish to continue using the linux-f10 compat ports,
1424 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1425 encouraged to update their linux-compat packages to linux-c6 during
1426 their next update cycle.
1429 The ofwfb driver, used to provide a graphics console on PowerPC when
1430 using vt(4), no longer allows mmap() of all physical memory. This
1431 will prevent Xorg on PowerPC with some ATI graphics cards from
1432 initializing properly unless x11-servers/xorg-server is updated to
1436 The xdev targets have been converted to using TARGET and
1437 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1440 The default unbound configuration has been modified to address
1441 issues with reverse lookups on networks that use private
1442 address ranges. If you use the local_unbound service, run
1443 "service local_unbound setup" as root to regenerate your
1444 configuration, then "service local_unbound reload" to load the
1448 The GNU texinfo and GNU info pages are not built and installed
1449 anymore, WITH_INFO knob has been added to allow to built and install
1451 UPDATE: see 20150102 entry on texinfo's removal
1454 The GNU readline library is now an INTERNALLIB - that is, it is
1455 statically linked into consumers (GDB and variants) in the base
1456 system, and the shared library is no longer installed. The
1457 devel/readline port is available for third party software that
1461 The Itanium architecture (ia64) has been removed from the list of
1462 known architectures. This is the first step in the removal of the
1466 Commit r268115 has added NFSv4.1 server support, merged from
1467 projects/nfsv4.1-server. Since this includes changes to the
1468 internal interfaces between the NFS related modules, a full
1469 build of the kernel and modules will be necessary.
1470 __FreeBSD_version has been bumped.
1473 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1474 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1475 which differs from the behaviour controlled by this knob.)
1478 Maximal length of the serial number in CTL was increased from 16 to
1479 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1480 and ctld, need to be rebuilt to work with a new kernel.
1483 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1484 1 respectively to match the upstream numbers. They were out of
1485 sync because, when they were originally added to FreeBSD, the
1486 upstream versions were not respected. These libraries are private
1487 and not yet built by default, so renumbering them should be a
1488 non-issue. However, unclean source trees will yield broken test
1489 programs once the operator executes "make delete-old-libs" after a
1490 "make installworld".
1492 Additionally, the atf-sh binary was made private by moving it into
1493 /usr/libexec/. Already-built shell test programs will keep the
1494 path to the old binary so they will break after "make delete-old"
1497 If you are using WITH_TESTS=yes (not the default), wipe the object
1498 tree and rebuild from scratch to prevent spurious test failures.
1499 This is only needed once: the misnumbered libraries and misplaced
1500 binaries have been added to OptionalObsoleteFiles.inc so they will
1501 be removed during a clean upgrade.
1504 Clang and llvm have been upgraded to 3.4.1 release.
1507 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1508 be removed to avoid issues in the future (and has been added to
1512 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1513 past, it affected all builds that used the bsd.*.mk files. The old
1514 behavior was a bug, but people may have relied upon it. To get this
1515 behavior back, you can .include /etc/src.conf from /etc/make.conf
1516 (which is still global and isn't changed). This also changes the
1517 behavior of incremental builds inside the tree of individual
1518 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1519 Although this has survived make universe and some upgrade scenarios,
1520 other upgrade scenarios may have broken. At least one form of
1521 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1522 as well... In cases where MAKESYSPATH isn't working with this
1523 setting, you'll need to set it to the full path to your tree.
1525 One side effect of all this cleaning up is that bsd.compiler.mk
1526 is no longer implicitly included by bsd.own.mk. If you wish to
1527 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1531 The lindev device has been removed since /dev/full has been made a
1532 standard device. __FreeBSD_version has been bumped.
1535 The knob WITHOUT_VI was added to the base system, which controls
1536 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1537 in order to reorder files share/termcap and didn't build ex(1) as a
1538 build tool, so building/installing with WITH_VI is highly advised for
1539 build hosts for older releases.
1541 This issue has been fixed in stable/9 and stable/10 in r277022 and
1542 r276991, respectively.
1545 The YES_HESIOD knob has been removed. It has been obsolete for
1546 a decade. Please move to using WITH_HESIOD instead or your builds
1547 will silently lack HESIOD.
1550 The uart(4) driver has been changed with respect to its handling
1551 of the low-level console. Previously the uart(4) driver prevented
1552 any process from changing the baudrate or the CLOCAL and HUPCL
1553 control flags. By removing the restrictions, operators can make
1554 changes to the serial console port without having to reboot.
1555 However, when getty(8) is started on the serial device that is
1556 associated with the low-level console, a misconfigured terminal
1557 line in /etc/ttys will now have a real impact.
1558 Before upgrading the kernel, make sure that /etc/ttys has the
1559 serial console device configured as 3wire without baudrate to
1560 preserve the previous behaviour. E.g:
1561 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1564 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1565 to improve performance. To re-enable it, if needed, run rpcbind
1566 with command line option -W.
1569 Switched back to the GPL dtc compiler due to updates in the upstream
1570 dts files not being supported by the BSDL dtc compiler. You will need
1571 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1572 may result while building dtb files during a kernel build if you fail
1573 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1576 Clang and llvm have been upgraded to 3.4 release.
1579 The nve(4) driver has been removed. Please use the nfe(4) driver
1580 for NVIDIA nForce MCP Ethernet adapters instead.
1583 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1584 This could cause certain C++ applications using shared libraries built
1585 against the previous version of libc++ to crash. The incompatibility
1586 has now been fixed, but any C++ applications or shared libraries built
1587 between r261283 and r261801 should be recompiled.
1590 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1591 capability mode support. Please note that enabling the feature in
1592 kernel is still highly recommended.
1595 OpenSSH is now built with sandbox support, and will use sandbox as
1596 the default privilege separation method. This requires Capsicum
1597 capability mode support in kernel.
1600 The libelf and libdwarf libraries have been updated to newer
1601 versions from upstream. Shared library version numbers for
1602 these two libraries were bumped. Any ports or binaries
1603 requiring these two libraries should be recompiled.
1604 __FreeBSD_version is bumped to 1100006.
1607 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1608 instead of providing an explicit one, this would prevent such
1609 Makefile from providing its own Kyuafile in the future during
1610 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1611 intervention is needed to clean an objdir if you use NO_CLEAN:
1612 # find /usr/obj -name Kyuafile | xargs rm -f
1615 The behavior of gss_pseudo_random() for the krb5 mechanism
1616 has changed, for applications requesting a longer random string
1617 than produced by the underlying enctype's pseudo-random() function.
1618 In particular, the random string produced from a session key of
1619 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1620 be different at the 17th octet and later, after this change.
1621 The counter used in the PRF+ construction is now encoded as a
1622 big-endian integer in accordance with RFC 4402.
1623 __FreeBSD_version is bumped to 1100004.
1626 The WITHOUT_ATF build knob has been removed and its functionality
1627 has been subsumed into the more generic WITHOUT_TESTS. If you were
1628 using the former to disable the build of the ATF libraries, you
1629 should change your settings to use the latter.
1632 The default version of mtree is nmtree which is obtained from
1633 NetBSD. The output is generally the same, but may vary
1634 slightly. If you found you need identical output adding
1635 "-F freebsd9" to the command line should do the trick. For the
1636 time being, the old mtree is available as fmtree.
1639 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1640 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1641 1.1.4_8 and verify bsdyml not linked in, before running "make
1643 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1645 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1648 The stable/10 branch has been created in subversion from head
1655 Avoid using make -j when upgrading. While generally safe, there are
1656 sometimes problems using -j to upgrade. If your upgrade fails with
1657 -j, please try again without -j. From time to time in the past there
1658 have been problems using -j with buildworld and/or installworld. This
1659 is especially true when upgrading between "distant" versions (eg one
1660 that cross a major release boundary or several minor releases, or when
1661 several months have passed on the -current branch).
1663 Sometimes, obscure build problems are the result of environment
1664 poisoning. This can happen because the make utility reads its
1665 environment when searching for values for global variables. To run
1666 your build attempts in an "environmental clean room", prefix all make
1667 commands with 'env -i '. See the env(1) manual page for more details.
1669 When upgrading from one major version to another it is generally best to
1670 upgrade to the latest code in the currently installed branch first, then
1671 do an upgrade to the new branch. This is the best-tested upgrade path,
1672 and has the highest probability of being successful. Please try this
1673 approach if you encounter problems with a major version upgrade. Since
1674 the stable 4.x branch point, one has generally been able to upgrade from
1675 anywhere in the most recent stable branch to head / current (or even the
1676 last couple of stable branches). See the top of this file when there's
1679 When upgrading a live system, having a root shell around before
1680 installing anything can help undo problems. Not having a root shell
1681 around can lead to problems if pam has changed too much from your
1682 starting point to allow continued authentication after the upgrade.
1684 This file should be read as a log of events. When a later event changes
1685 information of a prior event, the prior event should not be deleted.
1686 Instead, a pointer to the entry with the new information should be
1687 placed in the old entry. Readers of this file should also sanity check
1688 older entries before relying on them blindly. Authors of new entries
1689 should write them with this in mind.
1693 When upgrading the boot ZFS pool to a new version, always follow
1696 1.) recompile and reinstall the ZFS boot loader and boot block
1697 (this is part of "make buildworld" and "make installworld")
1699 2.) update the ZFS boot block on your boot drive
1701 The following example updates the ZFS boot block on the first
1702 partition (freebsd-boot) of a GPT partitioned drive ada0:
1703 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1705 Non-boot pools do not need these updates.
1709 If you are updating from a prior version of FreeBSD (even one just
1710 a few days old), you should follow this procedure. It is the most
1711 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1713 make kernel-toolchain
1714 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1715 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1717 To test a kernel once
1718 ---------------------
1719 If you just want to boot a kernel once (because you are not sure
1720 if it works, or if you want to boot a known bad kernel to provide
1721 debugging information) run
1722 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1723 nextboot -k testkernel
1725 To rebuild everything and install it on the current system.
1726 -----------------------------------------------------------
1727 # Note: sometimes if you are running current you gotta do more than
1728 # is listed here if you are upgrading from a really old current.
1730 <make sure you have good level 0 dumps>
1732 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1733 make installkernel KERNCONF=YOUR_KERNEL_HERE
1735 <reboot in single user> [3]
1742 To cross-install current onto a separate partition
1743 --------------------------------------------------
1744 # In this approach we use a separate partition to hold
1745 # current's root, 'usr', and 'var' directories. A partition
1746 # holding "/", "/usr" and "/var" should be about 2GB in
1749 <make sure you have good level 0 dumps>
1752 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1753 <maybe newfs current's root partition>
1754 <mount current's root partition on directory ${CURRENT_ROOT}>
1755 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1756 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1757 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1758 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1759 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1760 <reboot into current>
1761 <do a "native" rebuild/install as described in the previous section>
1762 <maybe install compatibility libraries from ports/misc/compat*>
1766 To upgrade in-place from stable to current
1767 ----------------------------------------------
1768 <make sure you have good level 0 dumps>
1770 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1771 make installkernel KERNCONF=YOUR_KERNEL_HERE
1773 <reboot in single user> [3]
1780 Make sure that you've read the UPDATING file to understand the
1781 tweaks to various things you need. At this point in the life
1782 cycle of current, things change often and you are on your own
1783 to cope. The defaults can also change, so please read ALL of
1784 the UPDATING entries.
1786 Also, if you are tracking -current, you must be subscribed to
1787 freebsd-current@freebsd.org. Make sure that before you update
1788 your sources that you have read and understood all the recent
1789 messages there. If in doubt, please track -stable which has
1790 much fewer pitfalls.
1792 [1] If you have third party modules, such as vmware, you
1793 should disable them at this point so they don't crash your
1796 [3] From the bootblocks, boot -s, and then do
1801 adjkerntz -i # if CMOS is wall time
1802 Also, when doing a major release upgrade, it is required that
1803 you boot into single user mode to do the installworld.
1805 [4] Note: This step is non-optional. Failure to do this step
1806 can result in a significant reduction in the functionality of the
1807 system. Attempting to do it by hand is not recommended and those
1808 that pursue this avenue should read this file carefully, as well
1809 as the archives of freebsd-current and freebsd-hackers mailing lists
1810 for potential gotchas. The -U option is also useful to consider.
1811 See mergemaster(8) for more information.
1813 [5] Usually this step is a no-op. However, from time to time
1814 you may need to do this if you get unknown user in the following
1815 step. It never hurts to do it all the time. You may need to
1816 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1817 install) after the buildworld before this step if you last updated
1818 from current before 20130425 or from -stable before 20130430.
1820 [6] This only deletes old files and directories. Old libraries
1821 can be deleted by "make delete-old-libs", but you have to make
1822 sure that no program is using those libraries anymore.
1824 [8] In order to have a kernel that can run the 4.x binaries needed to
1825 do an installworld, you must include the COMPAT_FREEBSD4 option in
1826 your kernel. Failure to do so may leave you with a system that is
1827 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1828 required to run the 5.x binaries on more recent kernels. And so on
1829 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1831 Make sure that you merge any new devices from GENERIC since the
1832 last time you updated your kernel config file.
1834 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1835 "?=" instead of the "=" assignment operator, so that buildworld can
1836 override the CPUTYPE if it needs to.
1838 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1839 not on the command line, or in /etc/make.conf. buildworld will
1840 warn if it is improperly defined.
1843 This file contains a list, in reverse chronological order, of major
1844 breakages in tracking -current. It is not guaranteed to be a complete
1845 list of such breakages, and only contains entries since September 23, 2011.
1846 If you need to see UPDATING entries from before that date, you will need
1847 to fetch an UPDATING file from an older FreeBSD release.
1849 Copyright information:
1851 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1853 Redistribution, publication, translation and use, with or without
1854 modification, in full or in part, in any form or format of this
1855 document are permitted without further permission from the author.
1857 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1858 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1859 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1860 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1861 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1862 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1863 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1864 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1865 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1866 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1867 POSSIBILITY OF SUCH DAMAGE.
1869 Contact Warner Losh if you have any questions about your use of