1 Updating Information for FreeBSD current users.
3 This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>.
4 See end of file for further details. For commonly done items, please see the
5 COMMON ITEMS: section later in the file. These instructions assume that you
6 basically know what you are doing. If not, then please consult the FreeBSD
9 https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/current-stable.html
11 Items affecting the ports and packages system can be found in
12 /usr/ports/UPDATING. Please read that file before running portupgrade.
14 NOTE: FreeBSD has switched from gcc to clang. If you have trouble bootstrapping
15 from older versions of FreeBSD, try WITHOUT_CLANG and WITH_GCC to bootstrap to
16 the tip of head, and then rebuild without this option. The bootstrap process
17 from older version of current across the gcc/clang cutover is a bit fragile.
19 NOTE TO PEOPLE WHO THINK THAT FreeBSD 12.x IS SLOW:
20 FreeBSD 12.x has many debugging features turned on, in both the kernel
21 and userland. These features attempt to detect incorrect use of
22 system primitives, and encourage loud failure through extra sanity
23 checking and fail stop semantics. They also substantially impact
24 system performance. If you want to do performance measurement,
25 benchmarking, and optimization, you'll want to turn them off. This
26 includes various WITNESS- related kernel options, INVARIANTS, malloc
27 debugging flags in userland, and various verbose features in the
28 kernel. Many developers choose to disable these features on build
29 machines to maximize performance. (To completely disable malloc
30 debugging, define MALLOC_PRODUCTION in /etc/make.conf, or to merely
31 disable the most expensive debugging functionality run
32 "ln -s 'abort:false,junk:false' /etc/malloc.conf".)
35 ****************************** SPECIAL WARNING: ******************************
37 Due to a bug in some versions of clang that's very hard to workaround in
38 the upgrade process, to upgrade to -current you must first upgrade
39 either stable/9 after r286035 or stable/10 after r286033 (including
40 10.3-RELEASE) or current after r286007 (including stable/11 and
41 11.0-RELEASE). These revisions post-date the 10.2 and 9.3 releases, so
42 you'll need to take the unusual step of upgrading to the tip of the
43 stable branch before moving to 11 or -current via a source upgrade.
44 stable/11 and 11.0-RELEASE have working newer compiler. This differs
45 from the historical situation where one could upgrade from anywhere on
46 the last couple of stable branches, so be careful.
48 If you're running a hybrid system on 9.x or 10.x with an updated clang
49 compiler or are using an supported external toolchain, the build system
50 will allow the upgrade. Otherwise it will print a reminder.
52 ****************************** SPECIAL WARNING: ******************************
55 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
56 6.0.0. Please see the 20141231 entry below for information about
57 prerequisites and upgrading, if you are not already using clang 3.5.0
61 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
62 This means it is used to link the kernel and userland libraries and
63 executables, but is not yet installed as /usr/bin/ld by default.
65 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
66 WITHOUT_LLD_BOOTSTRAP=yes
69 On i386, pmtimer has been removed. Its functionality has been folded
70 into apm. It was a no-op on ACPI in current for a while now (but was still
71 needed on i386 in FreeBSD 11 and earlier). Users may need to remove it
72 from kernel config files.
75 The use of RSS hash from the network card aka flowid has been
76 disabled by default for lagg(4) as it's currently incompatible with
77 the lacp and loadbalance protocols.
79 This can be re-enabled by setting the following in loader.conf:
80 net.link.lagg.default_use_flowid="1"
83 The SW_WATCHDOG option is no longer necessary to enable the
84 hardclock-based software watchdog if no hardware watchdog is
85 configured. As before, SW_WATCHDOG will cause the software
86 watchdog to be enabled even if a hardware watchdog is configured.
89 r326887 fixes the issue described in the 20171214 UPDATING entry.
90 r326888 flips the switch back to building GELI support always.
93 r362593 broke ZFS + GELI support for reasons unknown. However,
94 it also broke ZFS support generally, so GELI has been turned off
95 by default as the lesser evil in r326857. If you boot off ZFS and/or
96 GELI, it might not be a good time to update.
99 PowerPC users must update loader(8) by rebuilding world before
100 installing a new kernel, as the protocol connecting them has
101 changed. Without the update, loader metadata will not be passed
102 successfully to the kernel and users will have to enter their
103 root partition at the kernel mountroot prompt to continue booting.
104 Newer versions of loader can boot old kernels without issue.
107 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
108 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
109 to WITH/OUT_LOADER_GELI.
112 The naive and non-compliant support of posix_fallocate(2) in ZFS
113 has been removed as of r325320. The system call now returns EINVAL
114 when used on a ZFS file. Although the new behavior complies with the
115 standard, some consumers are not prepared to cope with it.
116 One known victim is lld prior to r325420.
119 Building in a FreeBSD src checkout will automatically create object
120 directories now rather than store files in the current directory if
121 'make obj' was not ran. Calling 'make obj' is no longer necessary.
122 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
123 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
127 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
128 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
129 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
130 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
131 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
132 The UNIFIED_OBJDIR option is a transitional feature that will be
133 removed for 12.0 release; please migrate to the new format for any
134 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
135 than hardcoding paths.
138 The native-xtools target no longer installs the files by default to the
139 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
140 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
143 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
144 options are changing from controlling the build if defined / undefined
145 to controlling the build with explicit 'yes' or 'no' values. They will
146 shift to WITH/WITHOUT options to match other options in the system.
149 libstand has turned into a private library for sys/boot use only.
150 It is no longer supported as a public interface outside of sys/boot.
153 The arm port has split armv6 into armv6 and armv7. armv7 is now
154 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
155 and are running a kernel from before r324363, you will need to add
156 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
159 When building multiple kernels using KERNCONF, non-existent KERNCONF
160 files will produce an error and buildkernel will fail. Previously
161 missing KERNCONF files silently failed giving no indication as to
162 why, only to subsequently discover during installkernel that the
163 desired kernel was never built in the first place.
166 The default serial number format for CTL LUNs has changed. This will
167 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
168 or iSCSI clients care about their LUNs' serial numbers. Users who
169 require serial number stability should hardcode serial numbers in
173 For 32-bit arm compiled for hard-float support, soft-floating point
174 binaries now always get their shared libraries from
175 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
176 /usr/libsoft also existed). Only users with a hard-float ld.so, but
177 soft-float everything else should be affected.
180 The geli password typed at boot is now hidden. To restore the previous
181 behavior, see geli(8) for configuration options.
184 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
185 sysctl values. Minor nit, but requires a rebuild of both world/kernel
189 "make check" behavior (made in ^/head@r295380) has been changed to
190 execute from a limited sandbox, as opposed to executing from
194 - The "beforecheck" and "aftercheck" targets are now specified.
195 - ${CHECKDIR} (added in commit noted above) has been removed.
196 - Legacy behavior can be enabled by setting
197 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
199 If the limited sandbox mode is enabled, "make check" will execute
200 "make distribution", then install, execute the tests, and clean up the
201 sandbox if successful.
203 The "make distribution" and "make install" targets are typically run as
204 root to set appropriate permissions and ownership at installation time.
205 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
206 environment if executing "make check" with limited sandbox mode using
207 an unprivileged user.
210 Since the switch to GPT disk labels, fsck for UFS/FFS has been
211 unable to automatically find alternate superblocks. As of r322297,
212 the information needed to find alternate superblocks has been
213 moved to the end of the area reserved for the boot block.
214 Filesystems created with a newfs of this vintage or later
215 will create the recovery information. If you have a filesystem
216 created prior to this change and wish to have a recovery block
217 created for your filesystem, you can do so by running fsck in
218 foreground mode (i.e., do not use the -p or -y options). As it
219 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
220 to which you should answer yes.
223 As of r321665, an NFSv4 server configuration that services
224 Kerberos mounts or clients that do not support the uid/gid in
225 owner/owner_group string capability, must explicitly enable
226 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
227 machine's /etc/rc.conf file.
230 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
231 Please see the 20141231 entry below for information about prerequisites
232 and upgrading, if you are not already using clang 3.5.0 or higher.
235 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
236 r-commands (rlogin, rsh, etc.) to be built with the base system.
239 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
240 a very major ABI incompatible change, so users of FreeBSD/powerpc must
241 be careful when performing source upgrades. It is best to run
242 'make installworld' from an alternate root system, either a live
243 CD/memory stick, or a temporary root partition. Additionally, all ports
244 must be recompiled. powerpc64 is largely unaffected, except in the case
245 of 32-bit compatibility. All 32-bit binaries will be affected.
248 Forward compatibility for the "ino64" project have been committed. This
249 will allow most new binaries to run on older kernels in a limited
250 fashion. This prevents many of the common foot-shooting actions in the
251 upgrade as well as the limited ability to roll back the kernel across
252 the ino64 upgrade. Complicated use cases may not work properly, though
253 enough simpler ones work to allow recovery in most situations.
256 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
257 if you require the GPL compiler.
260 The internal ABI used for communication between the NFS kernel modules
261 was changed by r320085, so __FreeBSD_version was bumped to
262 ensure all the NFS related modules are updated together.
265 The ABI of struct event was changed by extending the data
266 member to 64bit and adding ext fields. For upgrade, same
267 precautions as for the entry 20170523 "ino64" must be
271 The GNU roff toolchain has been removed from base. To render manpages
272 which are not supported by mandoc(1), man(1) can fallback on GNU roff
273 from ports (and recommends to install it).
274 To render roff(7) documents, consider using GNU roff from ports or the
275 heirloom doctools roff toolchain from ports via pkg install groff or
276 via pkg install heirloom-doctools.
279 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
280 smaller runtime footprint builds. This is useful for embedded systems
281 which only require one chipset support.
283 If you load it as a module, make sure this is in /boot/loader.conf:
287 This will load the HAL, all chip/RF backends and if_ath_pci.
288 If you have if_ath_pci in /boot/loader.conf, ensure it is after
289 if_ath or it will not load any HAL chipset support.
291 If you want to selectively load things (eg on ye cheape ARM/MIPS
292 platforms where RAM is at a premium) you should:
295 * load the chip modules in question
296 * load ath_rate, ath_dfs
298 * load if_ath_pci and/or if_ath_ahb depending upon your particular
299 bus bind type - this is where probe/attach is done.
301 For further comments/feedback, poke adrian@ .
304 The "ino64" 64-bit inode project has been committed, which extends
305 a number of types to 64 bits. Upgrading in place requires care and
306 adherence to the documented upgrade procedure.
308 If using a custom kernel configuration ensure that the
309 COMPAT_FREEBSD11 option is included (as during the upgrade the
310 system will be running the ino64 kernel with the existing world).
312 For the safest in-place upgrade begin by removing previous build
313 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
314 full procedure documented below under the heading "To rebuild
315 everything and install it on the current system." Specifically,
316 a reboot is required after installing the new kernel before
320 The NATM framework including the en(4), fatm(4), hatm(4), and
321 patm(4) devices has been removed. Consumers should plan a
322 migration before the end-of-life date for FreeBSD 11.
325 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
326 diff has not been implemented, if those are needed a newer version of
327 GNU diff is available via the diffutils package under the gdiff name.
330 As of r316810 for ipfilter, keep frags is no longer assumed when
331 keep state is specified in a rule. r316810 aligns ipfilter with
332 documentation in man pages separating keep frags from keep state.
333 This allows keep state to be specified without forcing keep frags
334 and allows keep frags to be specified independently of keep state.
335 To maintain previous behaviour, also specify keep frags with
336 keep state (as documented in ipf.conf.5).
339 arm64 builds now use the base system LLD 4.0.0 linker by default,
340 instead of requiring that the aarch64-binutils port or package be
341 installed. To continue using aarch64-binutils, set
342 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
345 The UDP optimization in entry 20160818 that added the sysctl
346 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
347 packets will no longer be treated as L3 broadcast packets.
350 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
351 use any explicitly assigned loopback address available in the jail
352 instead of using the first assigned address of the jail.
355 The ctl.ko module no longer implements the iSCSI target frontend:
356 cfiscsi.ko does instead.
358 If building cfiscsi.ko as a kernel module, the module can be loaded
359 via one of the following methods:
360 - `cfiscsi_load="YES"` in loader.conf(5).
361 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
362 - ctladm(8)/ctld(8), when compiled with iSCSI support
363 (`WITH_ISCSI=yes` in src.conf(5))
365 Please see cfiscsi(4) for more details.
368 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
369 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
370 same source (previously, the dependency of mmcsd.ko on mmc.ko was
371 missing, but mmcsd.ko now will refuse to load if it is incompatible
375 The syntax of ipfw(8) named states was changed to avoid ambiguity.
376 If you have used named states in the firewall rules, you need to modify
377 them after installworld and before rebooting. Now named states must
378 be prefixed with colon.
381 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
382 removed as the userland we provide cannot use them. The KMS version
383 (sys/dev/drm2) supports the same hardware.
386 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
387 Please see the 20141231 entry below for information about prerequisites
388 and upgrading, if you are not already using clang 3.5.0 or higher.
391 The code that provides support for ZFS .zfs/ directory functionality
392 has been reimplemented. It's not possible now to create a snapshot
393 by mkdir under .zfs/snapshot/. That should be the only user visible
397 EISA bus support has been removed. The WITH_EISA option is no longer
401 MCA bus support has been removed.
404 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
405 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
408 The EM_MULTIQUEUE kernel configuration option is deprecated now that
409 the em(4) driver conforms to iflib specifications.
412 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
413 IFLIB. If you have a custom kernel configuration that excludes em(4)
414 but you use igb(4), you need to re-add em(4) to your custom configuration.
417 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
418 Please see the 20141231 entry below for information about prerequisites
419 and upgrading, if you are not already using clang 3.5.0 or higher.
422 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
423 Please see the 20141231 entry below for information about prerequisites
424 and upgrading, if you are not already using clang 3.5.0 or higher.
427 The layout of the pmap structure has changed for powerpc to put the pmap
428 statistics at the front for all CPU variations. libkvm(3) and all tools
429 that link against it need to be recompiled.
432 isl(4) and cyapa(4) drivers now require a new driver,
433 chromebook_platform(4), to work properly on Chromebook-class hardware.
434 On other types of hardware the drivers may need to be configured using
435 device hints. Please see the corresponding manual pages for details.
438 The urtwn(4) driver was merged into rtwn(4) and now consists of
439 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
441 Also, firmware for RTL8188CE was renamed due to possible name
442 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
445 GNU rcs has been removed from base. It is available as packages:
446 - rcs: Latest GPLv3 GNU rcs version.
447 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
451 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
452 modules now requires that the kernel configuration contain the
453 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
456 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
457 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
460 Relocatable object files with the extension of .So have been renamed
461 to use an extension of .pico instead. The purpose of this change is
462 to avoid a name clash with shared libraries on case-insensitive file
463 systems. On those file systems, foo.So is the same file as foo.so.
466 GNU rcs has been turned off by default. It can (temporarily) be built
467 again by adding WITH_RCS knob in src.conf.
468 Otherwise, GNU rcs is available from packages:
469 - rcs: Latest GPLv3 GNU rcs version.
470 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
473 The backup_uses_rcs functionality has been removed from rc.subr.
476 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
477 two separate components, QUEUE_MACRO_DEBUG_TRACE and
478 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
479 QUEUE_MACRO_DEBUG behavior.
482 r304787 changed some ioctl interfaces between the iSCSI userspace
483 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
484 rebuilt to work with new kernels. __FreeBSD_version has been bumped
488 The UDP receive code has been updated to only treat incoming UDP
489 packets that were addressed to an L2 broadcast address as L3
490 broadcast packets. It is not expected that this will affect any
491 standards-conforming UDP application. The new behaviour can be
492 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
496 Remove the openbsd_poll system call.
497 __FreeBSD_version has been bumped because of this.
500 The libc stub for the pipe(2) system call has been replaced with
501 a wrapper that calls the pipe2(2) system call and the pipe(2)
502 system call is now only implemented by the kernels that include
503 "options COMPAT_FREEBSD10" in their config file (this is the
504 default). Users should ensure that this option is enabled in
505 their kernel or upgrade userspace to r302092 before upgrading their
509 CAM will now strip leading spaces from SCSI disks' serial numbers.
510 This will affect users who create UFS filesystems on SCSI disks using
511 those disk's diskid device nodes. For example, if /etc/fstab
512 previously contained a line like
513 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
514 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
515 transforms like gmirror may also be affected. ZFS users should
519 The bitstring(3) API has been updated with new functionality and
520 improved performance. But it is binary-incompatible with the old API.
521 Objects built with the new headers may not be linked against objects
522 built with the old headers.
525 The brk and sbrk functions have been removed from libc on arm64.
526 Binutils from ports has been updated to not link to these
527 functions and should be updated to the latest version before
528 installing a new libc.
531 The armv6 port now defaults to hard float ABI. Limited support
532 for running both hardfloat and soft float on the same system
533 is available using the libraries installed with -DWITH_LIBSOFT.
534 This has only been tested as an upgrade path for installworld
535 and packages may fail or need manual intervention to run. New
536 packages will be needed.
538 To update an existing self-hosted armv6hf system, you must add
539 TARGET_ARCH=armv6 on the make command line for both the build
540 and the install steps.
543 Kernel modules compiled outside of a kernel build now default to
544 installing to /boot/modules instead of /boot/kernel. Many kernel
545 modules built this way (such as those in ports) already overrode
546 KMODDIR explicitly to install into /boot/modules. However,
547 manually building and installing a module from /sys/modules will
548 now install to /boot/modules instead of /boot/kernel.
551 The CAM I/O scheduler has been committed to the kernel. There should be
552 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
553 list of known rogues that claim support for this but actually corrupt
554 data is believed to be complete, be on the lookout for data
555 corruption. The known rogue list is believed to be complete:
557 o Crucial MX100, M550 drives with MU01 firmware.
558 o Micron M510 and M550 drives with MU01 firmware.
559 o Micron M500 prior to MU07 firmware
560 o Samsung 830, 840, and 850 all firmwares
561 o FCCT M500 all firmwares
563 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
564 with working NCQ TRIM. For Micron branded drives, see your sales rep for
565 updated firmware. Black listed drives will work correctly because these
566 drives work correctly so long as no NCQ TRIMs are sent to them. Given
567 this list is the same as found in Linux, it's believed there are no
568 other rogues in the market place. All other models from the above
571 To be safe, if you are at all concerned, you can quirk each of your
572 drives to prevent NCQ from being sent by setting:
573 kern.cam.ada.X.quirks="0x2"
574 in loader.conf. If the drive requires the 4k sector quirk, set the
578 The FAST_DEPEND build option has been removed and its functionality is
579 now the one true way. The old mkdep(1) style of 'make depend' has
580 been removed. See 20160311 for further details.
583 Resource range types have grown from unsigned long to uintmax_t. All
584 drivers, and anything using libdevinfo, need to be recompiled.
587 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
588 builds. It no longer runs mkdep(1) during 'make depend', and the
589 'make depend' stage can safely be skipped now as it is auto ran
590 when building 'make all' and will generate all SRCS and DPSRCS before
591 building anything else. Dependencies are gathered at compile time with
592 -MF flags kept in separate .depend files per object file. Users should
593 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
597 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
598 kernel modules. Therefore, if you load any kernel modules at boot time,
599 please install the boot loaders after you install the kernel, but before
603 make kernel KERNCONF=YOUR_KERNEL_HERE
604 make -C sys/boot install
605 <reboot in single user>
607 Then follow the usual steps, described in the General Notes section,
611 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
612 see the 20141231 entry below for information about prerequisites and
613 upgrading, if you are not already using clang 3.5.0 or higher.
616 The AIO subsystem is now a standard part of the kernel. The
617 VFS_AIO kernel option and aio.ko kernel module have been removed.
618 Due to stability concerns, asynchronous I/O requests are only
619 permitted on sockets and raw disks by default. To enable
620 asynchronous I/O requests on all file types, set the
621 vfs.aio.enable_unsafe sysctl to a non-zero value.
624 The ELF object manipulation tool objcopy is now provided by the
625 ELF Tool Chain project rather than by GNU binutils. It should be a
626 drop-in replacement, with the addition of arm64 support. The
627 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
628 to obtain the GNU version if necessary.
631 Building ZFS pools on top of zvols is prohibited by default. That
632 feature has never worked safely; it's always been prone to deadlocks.
633 Using a zvol as the backing store for a VM guest's virtual disk will
634 still work, even if the guest is using ZFS. Legacy behavior can be
635 restored by setting vfs.zfs.vol.recursive=1.
638 The NONE and HPN patches has been removed from OpenSSH. They are
639 still available in the security/openssh-portable port.
642 With the addition of ypldap(8), a new _ypldap user is now required
643 during installworld. "mergemaster -p" can be used to add the user
644 prior to installworld, as documented in the handbook.
647 The tftp loader (pxeboot) now uses the option root-path directive. As a
648 consequence it no longer looks for a pxeboot.4th file on the tftp
649 server. Instead it uses the regular /boot infrastructure as with the
653 The code to start recording plug and play data into the modules has
654 been committed. While the old tools will properly build a new kernel,
655 a number of warnings about "unknown metadata record 4" will be produced
656 for an older kldxref. To avoid such warnings, make sure to rebuild
657 the kernel toolchain (or world). Make sure that you have r292078 or
658 later when trying to build 292077 or later before rebuilding.
661 Debug data files are now built by default with 'make buildworld' and
662 installed with 'make installworld'. This facilitates debugging but
663 requires more disk space both during the build and for the installed
664 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
668 r291527 changed the internal interface between the nfsd.ko and
669 nfscommon.ko modules. As such, they must both be upgraded to-gether.
670 __FreeBSD_version has been bumped because of this.
673 Add support for unicode collation strings leads to a change of
674 order of files listed by ls(1) for example. To get back to the old
675 behaviour, set LC_COLLATE environment variable to "C".
677 Databases administrators will need to reindex their databases given
678 collation results will be different.
680 Due to a bug in install(1) it is recommended to remove the ancient
681 locales before running make installworld.
683 rm -rf /usr/share/locale/*
686 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
687 libcrypto.so.7 or libssl.so.7 must be recompiled.
690 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
691 Kernel modules isp_2400_multi and isp_2500_multi were removed and
692 should be replaced with isp_2400 and isp_2500 modules respectively.
695 The build previously allowed using 'make -n' to not recurse into
696 sub-directories while showing what commands would be executed, and
697 'make -n -n' to recursively show commands. Now 'make -n' will recurse
698 and 'make -N' will not.
701 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
702 and etcupdate will now use this file. A custom sendmail.cf is now
703 updated via this mechanism rather than via installworld. If you had
704 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
705 want to remove the exclusion or change it to "always install".
706 /etc/mail/sendmail.cf is now managed the same way regardless of
707 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
708 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
711 Compatibility shims for legacy ATA device names have been removed.
712 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
713 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
714 environment variables, /dev/ad* and /dev/ar* symbolic links.
717 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
718 Please see the 20141231 entry below for information about prerequisites
719 and upgrading, if you are not already using clang 3.5.0 or higher.
722 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
723 and renamed from .symbols to .debug. This reduces the size requirements
724 on the boot partition or file system and provides consistency with
725 userland debug files.
727 When using the supported kernel installation method the
728 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
729 as is done with /boot/kernel.
731 Developers wishing to maintain the historical behavior of installing
732 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
735 The wireless drivers had undergone changes that remove the 'parent
736 interface' from the ifconfig -l output. The rc.d network scripts
737 used to check presence of a parent interface in the list, so old
738 scripts would fail to start wireless networking. Thus, etcupdate(3)
739 or mergemaster(8) run is required after kernel update, to update your
740 rc.d scripts in /etc.
743 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
744 These configurations are now automatically interpreted as
745 'scrub fragment reassemble'.
748 Kernel-loadable modules for the random(4) device are back. To use
749 them, the kernel must have
752 options RANDOM_LOADABLE
754 kldload(8) can then be used to load random_fortuna.ko
755 or random_yarrow.ko. Please note that due to the indirect
756 function calls that the loadable modules need to provide,
757 the build-in variants will be slightly more efficient.
759 The random(4) kernel option RANDOM_DUMMY has been retired due to
760 unpopularity. It was not all that useful anyway.
763 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
764 Control over building the ELF Tool Chain tools is now provided by
765 the WITHOUT_TOOLCHAIN knob.
768 The polarity of Pulse Per Second (PPS) capture events with the
769 uart(4) driver has been corrected. Prior to this change the PPS
770 "assert" event corresponded to the trailing edge of a positive PPS
771 pulse and the "clear" event was the leading edge of the next pulse.
773 As the width of a PPS pulse in a typical GPS receiver is on the
774 order of 1 millisecond, most users will not notice any significant
775 difference with this change.
777 Anyone who has compensated for the historical polarity reversal by
778 configuring a negative offset equal to the pulse width will need to
779 remove that workaround.
782 The default group assigned to /dev/dri entries has been changed
783 from 'wheel' to 'video' with the id of '44'. If you want to have
784 access to the dri devices please add yourself to the video group
787 # pw groupmod video -m $USER
790 The menu.rc and loader.rc files will now be replaced during
791 upgrades. Please migrate local changes to menu.rc.local and
792 loader.rc.local instead.
795 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
796 strings and strip have been removed. The src.conf(5) knob
797 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
800 As ZFS requires more kernel stack pages than is the default on some
801 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
802 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
804 Please consider using 'options KSTACK_PAGES=X' where X is greater
805 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
808 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
809 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
810 default, i.e., they will not contain "::". For example, instead
811 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
812 to have a more specific match, such as different map entries for
813 IPv6:0:0 vs IPv6:0. This change requires that configuration
814 data (including maps, files, classes, custom ruleset, etc.) must
815 use the same format, so make certain such configuration data is
816 upgrading. As a very simple check search for patterns like
817 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
818 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
819 the cf option UseCompressedIPv6Addresses.
822 The default kernel entropy-processing algorithm is now
823 Fortuna, replacing Yarrow.
825 Assuming you have 'device random' in your kernel config
826 file, the configurations allow a kernel option to override
827 this default. You may choose *ONE* of:
829 options RANDOM_YARROW # Legacy /dev/random algorithm.
830 options RANDOM_DUMMY # Blocking-only driver.
832 If you have neither, you get Fortuna. For most people,
833 read no further, Fortuna will give a /dev/random that works
834 like it always used to, and the difference will be irrelevant.
836 If you remove 'device random', you get *NO* kernel-processed
837 entropy at all. This may be acceptable to folks building
838 embedded systems, but has complications. Carry on reading,
839 and it is assumed you know what you need.
841 *PLEASE* read random(4) and random(9) if you are in the
842 habit of tweaking kernel configs, and/or if you are a member
843 of the embedded community, wanting specific and not-usual
844 behaviour from your security subsystems.
846 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
847 random', you will NOT have a functioning /dev/random, and
848 many cryptographic features will not work, including SSH.
849 You may also find strange behaviour from the random(3) set
850 of library functions, in particular sranddev(3), srandomdev(3)
851 and arc4random(3). The reason for this is that the KERN_ARND
852 sysctl only returns entropy if it thinks it has some to
853 share, and with RANDOM_DUMMY or no 'device random' this
857 An additional fix for the issue described in the 20150614 sendmail
858 entry below has been committed in revision 284717.
861 FreeBSD's old make (fmake) has been removed from the system. It is
862 available as the devel/fmake port or via pkg install fmake.
865 The fix for the issue described in the 20150614 sendmail entry
866 below has been committed in revision 284436. The work
867 around described in that entry is no longer needed unless the
868 default setting is overridden by a confDH_PARAMETERS configuration
869 setting of '5' or pointing to a 512 bit DH parameter file.
872 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
873 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
874 and devel/kyua to version 0.20+ and adjust any calling code to work
875 with Kyuafile and kyua.
878 The import of openssl to address the FreeBSD-SA-15:10.openssl
879 security advisory includes a change which rejects handshakes
880 with DH parameters below 768 bits. sendmail releases prior
881 to 8.15.2 (not yet released), defaulted to a 512 bit
882 DH parameter setting for client connections. To work around
883 this interoperability, sendmail can be configured to use a
884 2048 bit DH parameter by:
886 1. Edit /etc/mail/`hostname`.mc
887 2. If a setting for confDH_PARAMETERS does not exist or
888 exists and is set to a string beginning with '5',
890 3. If a setting for confDH_PARAMETERS exists and is set to
891 a file path, create a new file with:
892 openssl dhparam -out /path/to/file 2048
893 4. Rebuild the .cf file:
894 cd /etc/mail/; make; make install
896 cd /etc/mail/; make restart
898 A sendmail patch is coming, at which time this file will be
902 Generation of legacy formatted entries have been disabled by default
903 in pwd_mkdb(8), as all base system consumers of the legacy formatted
904 entries were converted to use the new format by default when the new,
905 machine independent format have been added and supported since FreeBSD
908 Please see the pwd_mkdb(8) manual page for further details.
911 Clang and llvm have been upgraded to 3.6.1 release. Please see the
912 20141231 entry below for information about prerequisites and upgrading,
913 if you are not already using 3.5.0 or higher.
916 TI platform code switched to using vendor DTS files and this update
917 may break existing systems running on Beaglebone, Beaglebone Black,
920 - dtb files should be regenerated/reinstalled. Filenames are the
921 same but content is different now
922 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
923 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
924 addressing scheme is now pin 25 on /dev/gpioc3.
925 - Pandaboard: /etc/ttys should be updated, serial console device is
926 now /dev/ttyu2, not /dev/ttyu0
929 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
930 If you need the GNU extension from groff soelim(1), install groff
931 from package: pkg install groff, or via ports: textproc/groff.
934 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
935 defined in symlink(7); previously symlinks were silently ignored.
938 The const qualifier has been removed from iconv(3) to comply with
939 POSIX. The ports tree is aware of this from r384038 onwards.
942 Libraries specified by LIBADD in Makefiles must have a corresponding
943 DPADD_<lib> variable to ensure correct dependencies. This is now
944 enforced in src.libnames.mk.
947 From legacy ata(4) driver was removed support for SATA controllers
948 supported by more functional drivers ahci(4), siis(4) and mvs(4).
949 Kernel modules ataahci and ataadaptec were removed completely,
950 replaced by ahci and mvs modules respectively.
953 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
954 the 20141231 entry below for information about prerequisites and
955 upgrading, if you are not already using 3.5.0 or higher.
958 The 32-bit PowerPC kernel has been changed to a position-independent
959 executable. This can only be booted with a version of loader(8)
960 newer than January 31, 2015, so make sure to update both world and
961 kernel before rebooting.
964 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
965 but before r278950, the RNG was not seeded properly. Immediately
966 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
967 ssh keys or openssl keys) that were generated w/ a kernel from that
968 range. This does not affect programs that directly used /dev/random
969 or /dev/urandom. All userland uses of arc4random(3) are affected.
972 The autofs(4) ABI was changed in order to restore binary compatibility
973 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
977 The powerpc64 kernel has been changed to a position-independent
978 executable. This can only be booted with a new version of loader(8),
979 so make sure to update both world and kernel before rebooting.
982 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
983 only release, no new features have been added. Please see the 20141231
984 entry below for information about prerequisites and upgrading, if you
985 are not already using 3.5.0.
988 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
989 taken from the ELF Tool Chain project rather than GNU binutils. They
990 should be drop-in replacements, with the addition of arm64 support.
991 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
992 binutils tools, if necessary. See 20150805 for updated information.
995 The default Unbound configuration now enables remote control
996 using a local socket. Users who have already enabled the
997 local_unbound service should regenerate their configuration
998 by running "service local_unbound setup" as root.
1001 The GNU texinfo and GNU info pages have been removed.
1002 To be able to view GNU info pages please install texinfo from ports.
1005 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1007 As of this release, a prerequisite for building clang, llvm and lldb is
1008 a C++11 capable compiler and C++11 standard library. This means that to
1009 be able to successfully build the cross-tools stage of buildworld, with
1010 clang as the bootstrap compiler, your system compiler or cross compiler
1011 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1012 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1015 On any standard FreeBSD 10.x or 11.x installation, where clang and
1016 libc++ are on by default (that is, on x86 or arm), this should work out
1019 On 9.x installations where clang is enabled by default, e.g. on x86 and
1020 powerpc, libc++ will not be enabled by default, so libc++ should be
1021 built (with clang) and installed first. If both clang and libc++ are
1022 missing, build clang first, then use it to build libc++.
1024 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1025 the instructions for 9.x above.
1027 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1028 default, and do not build clang.
1030 Many embedded systems are resource constrained, and will not be able to
1031 build clang in a reasonable time, or in some cases at all. In those
1032 cases, cross building bootable systems on amd64 is a workaround.
1034 This new version of clang introduces a number of new warnings, of which
1035 the following are most likely to appear:
1039 This warns in two cases, for both C and C++:
1040 * When the code is trying to take the absolute value of an unsigned
1041 quantity, which is effectively a no-op, and almost never what was
1042 intended. The code should be fixed, if at all possible. If you are
1043 sure that the unsigned quantity can be safely cast to signed, without
1044 loss of information or undefined behavior, you can add an explicit
1045 cast, or disable the warning.
1047 * When the code is trying to take an absolute value, but the called
1048 abs() variant is for the wrong type, which can lead to truncation.
1049 If you want to disable the warning instead of fixing the code, please
1050 make sure that truncation will not occur, or it might lead to unwanted
1053 -Wtautological-undefined-compare and
1054 -Wundefined-bool-conversion
1056 These warn when C++ code is trying to compare 'this' against NULL, while
1057 'this' should never be NULL in well-defined C++ code. However, there is
1058 some legacy (pre C++11) code out there, which actively abuses this
1059 feature, which was less strictly defined in previous C++ versions.
1061 Squid and openjdk do this, for example. The warning can be turned off
1062 for C++98 and earlier, but compiling the code in C++11 mode might result
1063 in unexpected behavior; for example, the parts of the program that are
1064 unreachable could be optimized away.
1067 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1068 kernel sources have been removed. The .h files remain, since some
1069 utilities include them. This will need to be fixed later.
1070 If "mount -t oldnfs ..." is attempted, it will fail.
1071 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1072 the utilities will report errors.
1075 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1076 directories to top level SUBDIR variable when their parent
1077 directory is included in LOCAL_DIRS. Users with build systems with
1078 such hierarchies and without SUBDIR entries in the parent
1079 directory Makefiles should add them or add the directories to
1083 faith(4) and faithd(8) have been removed from the base system. Faith
1084 has been obsolete for a very long time.
1087 vt(4), the new console driver, is enabled by default. It brings
1088 support for Unicode and double-width characters, as well as
1089 support for UEFI and integration with the KMS kernel video
1092 You may need to update your console settings in /etc/rc.conf,
1093 most probably the keymap. During boot, /etc/rc.d/syscons will
1094 indicate what you need to do.
1096 vt(4) still has issues and lacks some features compared to
1097 syscons(4). See the wiki for up-to-date information:
1098 https://wiki.freebsd.org/Newcons
1100 If you want to keep using syscons(4), you can do so by adding
1101 the following line to /boot/loader.conf:
1105 pjdfstest has been integrated into kyua as an opt-in test suite.
1106 Please see share/doc/pjdfstest/README for more details on how to
1110 gperf has been removed from the base system for architectures
1111 that use clang. Ports that require gperf will obtain it from the
1115 pjdfstest has been moved from tools/regression/pjdfstest to
1119 At svn r271982, The default linux compat kernel ABI has been adjusted
1120 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1121 update. If you wish to continue using the linux-f10 compat ports,
1122 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1123 encouraged to update their linux-compat packages to linux-c6 during
1124 their next update cycle.
1127 The ofwfb driver, used to provide a graphics console on PowerPC when
1128 using vt(4), no longer allows mmap() of all physical memory. This
1129 will prevent Xorg on PowerPC with some ATI graphics cards from
1130 initializing properly unless x11-servers/xorg-server is updated to
1134 The xdev targets have been converted to using TARGET and
1135 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1138 The default unbound configuration has been modified to address
1139 issues with reverse lookups on networks that use private
1140 address ranges. If you use the local_unbound service, run
1141 "service local_unbound setup" as root to regenerate your
1142 configuration, then "service local_unbound reload" to load the
1146 The GNU texinfo and GNU info pages are not built and installed
1147 anymore, WITH_INFO knob has been added to allow to built and install
1149 UPDATE: see 20150102 entry on texinfo's removal
1152 The GNU readline library is now an INTERNALLIB - that is, it is
1153 statically linked into consumers (GDB and variants) in the base
1154 system, and the shared library is no longer installed. The
1155 devel/readline port is available for third party software that
1159 The Itanium architecture (ia64) has been removed from the list of
1160 known architectures. This is the first step in the removal of the
1164 Commit r268115 has added NFSv4.1 server support, merged from
1165 projects/nfsv4.1-server. Since this includes changes to the
1166 internal interfaces between the NFS related modules, a full
1167 build of the kernel and modules will be necessary.
1168 __FreeBSD_version has been bumped.
1171 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1172 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1173 which differs from the behaviour controlled by this knob.)
1176 Maximal length of the serial number in CTL was increased from 16 to
1177 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1178 and ctld, need to be rebuilt to work with a new kernel.
1181 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1182 1 respectively to match the upstream numbers. They were out of
1183 sync because, when they were originally added to FreeBSD, the
1184 upstream versions were not respected. These libraries are private
1185 and not yet built by default, so renumbering them should be a
1186 non-issue. However, unclean source trees will yield broken test
1187 programs once the operator executes "make delete-old-libs" after a
1188 "make installworld".
1190 Additionally, the atf-sh binary was made private by moving it into
1191 /usr/libexec/. Already-built shell test programs will keep the
1192 path to the old binary so they will break after "make delete-old"
1195 If you are using WITH_TESTS=yes (not the default), wipe the object
1196 tree and rebuild from scratch to prevent spurious test failures.
1197 This is only needed once: the misnumbered libraries and misplaced
1198 binaries have been added to OptionalObsoleteFiles.inc so they will
1199 be removed during a clean upgrade.
1202 Clang and llvm have been upgraded to 3.4.1 release.
1205 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1206 be removed to avoid issues in the future (and has been added to
1210 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1211 past, it affected all builds that used the bsd.*.mk files. The old
1212 behavior was a bug, but people may have relied upon it. To get this
1213 behavior back, you can .include /etc/src.conf from /etc/make.conf
1214 (which is still global and isn't changed). This also changes the
1215 behavior of incremental builds inside the tree of individual
1216 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1217 Although this has survived make universe and some upgrade scenarios,
1218 other upgrade scenarios may have broken. At least one form of
1219 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1220 as well... In cases where MAKESYSPATH isn't working with this
1221 setting, you'll need to set it to the full path to your tree.
1223 One side effect of all this cleaning up is that bsd.compiler.mk
1224 is no longer implicitly included by bsd.own.mk. If you wish to
1225 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1229 The lindev device has been removed since /dev/full has been made a
1230 standard device. __FreeBSD_version has been bumped.
1233 The knob WITHOUT_VI was added to the base system, which controls
1234 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1235 in order to reorder files share/termcap and didn't build ex(1) as a
1236 build tool, so building/installing with WITH_VI is highly advised for
1237 build hosts for older releases.
1239 This issue has been fixed in stable/9 and stable/10 in r277022 and
1240 r276991, respectively.
1243 The YES_HESIOD knob has been removed. It has been obsolete for
1244 a decade. Please move to using WITH_HESIOD instead or your builds
1245 will silently lack HESIOD.
1248 The uart(4) driver has been changed with respect to its handling
1249 of the low-level console. Previously the uart(4) driver prevented
1250 any process from changing the baudrate or the CLOCAL and HUPCL
1251 control flags. By removing the restrictions, operators can make
1252 changes to the serial console port without having to reboot.
1253 However, when getty(8) is started on the serial device that is
1254 associated with the low-level console, a misconfigured terminal
1255 line in /etc/ttys will now have a real impact.
1256 Before upgrading the kernel, make sure that /etc/ttys has the
1257 serial console device configured as 3wire without baudrate to
1258 preserve the previous behaviour. E.g:
1259 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1262 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1263 to improve performance. To re-enable it, if needed, run rpcbind
1264 with command line option -W.
1267 Switched back to the GPL dtc compiler due to updates in the upstream
1268 dts files not being supported by the BSDL dtc compiler. You will need
1269 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1270 may result while building dtb files during a kernel build if you fail
1271 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1274 Clang and llvm have been upgraded to 3.4 release.
1277 The nve(4) driver has been removed. Please use the nfe(4) driver
1278 for NVIDIA nForce MCP Ethernet adapters instead.
1281 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1282 This could cause certain C++ applications using shared libraries built
1283 against the previous version of libc++ to crash. The incompatibility
1284 has now been fixed, but any C++ applications or shared libraries built
1285 between r261283 and r261801 should be recompiled.
1288 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1289 capability mode support. Please note that enabling the feature in
1290 kernel is still highly recommended.
1293 OpenSSH is now built with sandbox support, and will use sandbox as
1294 the default privilege separation method. This requires Capsicum
1295 capability mode support in kernel.
1298 The libelf and libdwarf libraries have been updated to newer
1299 versions from upstream. Shared library version numbers for
1300 these two libraries were bumped. Any ports or binaries
1301 requiring these two libraries should be recompiled.
1302 __FreeBSD_version is bumped to 1100006.
1305 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1306 instead of providing an explicit one, this would prevent such
1307 Makefile from providing its own Kyuafile in the future during
1308 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1309 intervention is needed to clean an objdir if you use NO_CLEAN:
1310 # find /usr/obj -name Kyuafile | xargs rm -f
1313 The behavior of gss_pseudo_random() for the krb5 mechanism
1314 has changed, for applications requesting a longer random string
1315 than produced by the underlying enctype's pseudo-random() function.
1316 In particular, the random string produced from a session key of
1317 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1318 be different at the 17th octet and later, after this change.
1319 The counter used in the PRF+ construction is now encoded as a
1320 big-endian integer in accordance with RFC 4402.
1321 __FreeBSD_version is bumped to 1100004.
1324 The WITHOUT_ATF build knob has been removed and its functionality
1325 has been subsumed into the more generic WITHOUT_TESTS. If you were
1326 using the former to disable the build of the ATF libraries, you
1327 should change your settings to use the latter.
1330 The default version of mtree is nmtree which is obtained from
1331 NetBSD. The output is generally the same, but may vary
1332 slightly. If you found you need identical output adding
1333 "-F freebsd9" to the command line should do the trick. For the
1334 time being, the old mtree is available as fmtree.
1337 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1338 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1339 1.1.4_8 and verify bsdyml not linked in, before running "make
1341 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1343 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1346 The stable/10 branch has been created in subversion from head
1350 The rc.d/jail script has been updated to support jail(8)
1351 configuration file. The "jail_<jname>_*" rc.conf(5) variables
1352 for per-jail configuration are automatically converted to
1353 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
1354 This is transparently backward compatible. See below about some
1355 incompatibilities and rc.conf(5) manual page for more details.
1357 These variables are now deprecated in favor of jail(8) configuration
1358 file. One can use "rc.d/jail config <jname>" command to generate
1359 a jail(8) configuration file in /var/run/jail.<jname>.conf without
1360 running the jail(8) utility. The default pathname of the
1361 configuration file is /etc/jail.conf and can be specified by
1362 using $jail_conf or $jail_<jname>_conf variables.
1364 Please note that jail_devfs_ruleset accepts an integer at
1365 this moment. Please consider to rewrite the ruleset name
1369 BIND has been removed from the base system. If all you need
1370 is a local resolver, simply enable and start the local_unbound
1371 service instead. Otherwise, several versions of BIND are
1372 available in the ports tree. The dns/bind99 port is one example.
1374 With this change, nslookup(1) and dig(1) are no longer in the base
1375 system. Users should instead use host(1) and drill(1) which are
1376 in the base system. Alternatively, nslookup and dig can
1377 be obtained by installing the dns/bind-tools port.
1380 With the addition of unbound(8), a new unbound user is now
1381 required during installworld. "mergemaster -p" can be used to
1382 add the user prior to installworld, as documented in the handbook.
1385 OpenSSH is now built with DNSSEC support, and will by default
1386 silently trust signed SSHFP records. This can be controlled with
1387 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1388 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1391 The GNU Compiler Collection and C++ standard library (libstdc++)
1392 are no longer built by default on platforms where clang is the system
1393 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1394 options in src.conf.
1397 The PROCDESC kernel option is now part of the GENERIC kernel
1398 configuration and is required for the rwhod(8) to work.
1399 If you are using custom kernel configuration, you should include
1403 The API and ABI related to the Capsicum framework was modified
1404 in backward incompatible way. The userland libraries and programs
1405 have to be recompiled to work with the new kernel. This includes the
1406 following libraries and programs, but the whole buildworld is
1407 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1408 kdump, procstat, rwho, rwhod, uniq.
1411 AES-NI intrinsic support has been added to gcc. The AES-NI module
1412 has been updated to use this support. A new gcc is required to build
1413 the aesni module on both i386 and amd64.
1416 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1417 Thus "device padlock_rng" and "device rdrand_rng" should be
1418 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1421 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1422 enables just the iconv* functionality and is now on by default.
1423 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1424 compatibility. Set WITHOUT_ICONV to build the old way.
1425 If you have been using WITH_ICONV before, you will very likely
1426 need to turn on WITH_LIBICONV_COMPAT.
1429 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1430 Illumos origin, including ZFS. If you have INVARIANTS in your
1431 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1433 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1434 locks if WITNESS option was set. Because that generated a lot of
1435 witness(9) reports and all of them were believed to be false
1436 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1437 can be used to achieve the previous behavior.
1440 Timer values in IPv6 data structures now use time_uptime instead
1441 of time_second. Although this is not a user-visible functional
1442 change, userland utilities which directly use them---ndp(8),
1443 rtadvd(8), and rtsold(8) in the base system---need to be updated
1444 to r253970 or later.
1447 find -delete can now delete the pathnames given as arguments,
1448 instead of only files found below them or if the pathname did
1449 not contain any slashes. Formerly, the following error message
1452 find: -delete: <path>: relative path potentially not safe
1454 Deleting the pathnames given as arguments can be prevented
1455 without error messages using -mindepth 1 or by changing
1456 directory and passing "." as argument to find. This works in the
1457 old as well as the new version of find.
1460 Behavior of devfs rules path matching has been changed.
1461 Pattern is now always matched against fully qualified devfs
1462 path and slash characters must be explicitly matched by
1463 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1464 subdirectories must be reviewed.
1467 The default ARM ABI has changed to the ARM EABI. The old ABI is
1468 incompatible with the ARM EABI and all programs and modules will
1469 need to be rebuilt to work with a new kernel.
1471 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1473 NOTE: Support for the old ABI will be removed in the future and
1474 users are advised to upgrade.
1477 pkg_install has been disconnected from the build if you really need it
1478 you should add WITH_PKGTOOLS in your src.conf(5).
1481 Most of network statistics structures were changed to be able
1482 keep 64-bits counters. Thus all tools, that work with networking
1483 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1486 Fix a bug that allowed a tracing process (e.g. gdb) to write
1487 to a memory-mapped file in the traced process's address space
1488 even if neither the traced process nor the tracing process had
1489 write access to that file.
1492 CVS has been removed from the base system. An exact copy
1493 of the code is available from the devel/cvs port.
1496 Some people report the following error after the switch to bmake:
1498 make: illegal option -- J
1499 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1501 *** [buildworld] Error code 2
1503 this likely due to an old instance of make in
1504 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1505 which src/Makefile will use that blindly, if it exists, so if
1506 you see the above error:
1508 rm -rf `make -V MAKEPATH`
1513 Use bmake by default.
1514 Whereas before one could choose to build with bmake via
1515 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1516 make. The goal is to remove these knobs for 10-RELEASE.
1518 It is worth noting that bmake (like gmake) treats the command
1519 line as the unit of failure, rather than statements within the
1520 command line. Thus '(cd some/where && dosomething)' is safer
1521 than 'cd some/where; dosomething'. The '()' allows consistent
1522 behavior in parallel build.
1525 Fix a bug that allows NFS clients to issue READDIR on files.
1528 The WITHOUT_IDEA option has been removed because
1529 the IDEA patent expired.
1532 The sysctl which controls TRIM support under ZFS has been renamed
1533 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1537 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1538 rather than creating it's own in the temporary directory in
1539 order allow access to bootstrapped versions of tools such as
1540 install and mtree. When upgrading from version of FreeBSD where
1541 the install command does not support -l, you will need to
1542 install a new mergemaster command if mergemaster -p is required.
1543 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1547 Legacy ATA stack, disabled and replaced by new CAM-based one since
1548 FreeBSD 9.0, completely removed from the sources. Kernel modules
1549 atadisk and atapi*, user-level tools atacontrol and burncd are
1550 removed. Kernel option `options ATA_CAM` is now permanently enabled
1554 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1555 and socketpair(2). Software, in particular Kerberos, may
1556 automatically detect and use these during building. The resulting
1557 binaries will not work on older kernels.
1560 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1561 information, see the respective 20130304 entry).
1564 Recent commits to callout(9) changed the size of struct callout,
1565 so the KBI is probably heavily disturbed. Also, some functions
1566 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1567 by macros. Every kernel module using it won't load, so rebuild
1570 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1571 but does not initialize by default (because of the new CTL_DISABLE
1572 option) to save memory. To re-enable it, remove the CTL_DISABLE
1573 option from the kernel config file or set kern.cam.ctl.disable=0
1574 in /boot/loader.conf.
1577 The ctl device has been disabled in GENERIC for i386 and amd64.
1578 This was done due to the extra memory being allocated at system
1579 initialisation time by the ctl driver which was only used if
1580 a CAM target device was created. This makes a FreeBSD system
1581 unusable on 128MB or less of RAM.
1584 A new compression method (lz4) has been merged to -HEAD. Please
1585 refer to zpool-features(7) for more information.
1587 Please refer to the "ZFS notes" section of this file for information
1588 on upgrading boot ZFS pools.
1591 A BSD-licensed patch(1) variant has been added and is installed
1592 as bsdpatch, being the GNU version the default patch.
1593 To inverse the logic and use the BSD-licensed one as default,
1594 while having the GNU version installed as gnupatch, rebuild
1595 and install world with the WITH_BSD_PATCH knob set.
1598 Due to the use of the new -l option to install(1) during build
1599 and install, you must take care not to directly set the INSTALL
1600 make variable in your /etc/make.conf, /etc/src.conf, or on the
1601 command line. If you wish to use the -C flag for all installs
1602 you may be able to add INSTALL+=-C to /etc/make.conf or
1606 The install(1) option -M has changed meaning and now takes an
1607 argument that is a file or path to append logs to. In the
1608 unlikely event that -M was the last option on the command line
1609 and the command line contained at least two files and a target
1610 directory the first file will have logs appended to it. The -M
1611 option served little practical purpose in the last decade so its
1612 use is expected to be extremely rare.
1615 After switching to Clang as the default compiler some users of ZFS
1616 on i386 systems started to experience stack overflow kernel panics.
1617 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1620 GEOM_LABEL now mangles label names read from file system metadata.
1621 Mangling affect labels containing spaces, non-printable characters,
1622 '%' or '"'. Device names in /etc/fstab and other places may need to
1626 By default, only the 10 most recent kernel dumps will be saved. To
1627 restore the previous behaviour (no limit on the number of kernel dumps
1628 stored in the dump directory) add the following line to /etc/rc.conf:
1633 With the addition of auditdistd(8), a new auditdistd user is now
1634 required during installworld. "mergemaster -p" can be used to
1635 add the user prior to installworld, as documented in the handbook.
1638 The sin6_scope_id member variable in struct sockaddr_in6 is now
1639 filled by the kernel before passing the structure to the userland via
1640 sysctl or routing socket. This means the KAME-specific embedded scope
1641 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1642 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1643 __FreeBSD_version is bumped to 1000025.
1646 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1647 This means that the world and kernel will be compiled with clang
1648 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1649 and /usr/bin/cpp. To disable this behavior and revert to building
1650 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1651 of current may need to bootstrap WITHOUT_CLANG first if the clang
1652 build fails (its compatibility window doesn't extend to the 9 stable
1656 The IPFIREWALL_FORWARD kernel option has been removed. Its
1657 functionality now turned on by default.
1660 The ZERO_COPY_SOCKET kernel option has been removed and
1661 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1662 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1663 mechanism which is not safe and may result in kernel crashes.
1664 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1665 driver supports disposeable external page sized mbuf storage.
1666 Proper replacements for both zero-copy mechanisms are under
1667 consideration and will eventually lead to complete removal
1668 of the two kernel options.
1671 The IPv4 network stack has been converted to network byte
1672 order. The following modules need to be recompiled together
1673 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1674 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1677 Support for non-MPSAFE filesystems was removed from VFS. The
1678 VFS_VERSION was bumped, all filesystem modules shall be
1682 All the non-MPSAFE filesystems have been disconnected from
1683 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1684 portalfs, smbfs, xfs.
1687 The interface cloning API and ABI has changed. The following
1688 modules need to be recompiled together with kernel:
1689 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1690 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1691 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1694 The sdhci driver was split in two parts: sdhci (generic SD Host
1695 Controller logic) and sdhci_pci (actual hardware driver).
1696 No kernel config modifications are required, but if you
1697 load sdhc as a module you must switch to sdhci_pci instead.
1700 Import the FUSE kernel and userland support into base system.
1703 The GNU sort(1) program has been removed since the BSD-licensed
1704 sort(1) has been the default for quite some time and no serious
1705 problems have been reported. The corresponding WITH_GNU_SORT
1709 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1710 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1714 The net80211(4) ABI has been changed to allow for improved driver
1715 PS-POLL and power-save support. All wireless drivers need to be
1716 recompiled to work with the new kernel.
1719 The random(4) support for the VIA hardware random number
1720 generator (`PADLOCK') is no longer enabled unconditionally.
1721 Add the padlock_rng device in the custom kernel config if
1722 needed. The GENERIC kernels on i386 and amd64 do include the
1723 device, so the change only affects the custom kernel
1727 The pf(4) packet filter ABI has been changed. pfctl(8) and
1728 snmp_pf module need to be recompiled to work with new kernel.
1731 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1732 to -HEAD. Pools that have empty_bpobj in active state can not be
1733 imported read-write with ZFS implementations that do not support
1734 this feature. For more information read the zpool-features(5)
1738 The sparc64 ZFS loader has been changed to no longer try to auto-
1739 detect ZFS providers based on diskN aliases but now requires these
1740 to be explicitly listed in the OFW boot-device environment variable.
1743 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1744 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1745 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1748 The following sysctls and tunables have been renamed for consistency
1749 with other variables:
1750 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1751 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1754 The sort utility has been replaced with BSD sort. For now, GNU sort
1755 is also available as "gnusort" or the default can be set back to
1756 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1757 installed as "bsdsort".
1760 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1761 Starting with this version the old system of ZFS pool versioning
1762 is superseded by "feature flags". This concept enables forward
1763 compatibility against certain future changes in functionality of ZFS
1764 pools. The first read-only compatible "feature flag" for ZFS pools
1765 is named "com.delphix:async_destroy". For more information
1766 read the new zpool-features(5) manual page.
1767 Please refer to the "ZFS notes" section of this file for information
1768 on upgrading boot ZFS pools.
1771 The malloc(3) implementation embedded in libc now uses sources imported
1772 as contrib/jemalloc. The most disruptive API change is to
1773 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1774 delete it prior to installworld, and optionally re-create it using the
1775 new format after rebooting. See malloc.conf(5) for details
1776 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1780 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1781 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1782 now spelled mips. This is to aid compatibility with third-party
1783 software that expects this naming scheme in uname(3). Little-endian
1784 settings are unchanged. If you are updating a big-endian mips64 machine
1785 from before this change, you may need to set MACHINE_ARCH=mips64 in
1786 your environment before the new build system will recognize your machine.
1789 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1793 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1794 nullfs(5) did not pass through all behaviours to the underlying layer,
1795 as a result if we bound to a socket on the lower layer we could connect
1796 only to the lower path; if we bound to the upper layer we could connect
1797 only to the upper path. The new behavior is one can connect to both the
1798 lower and the upper paths regardless what layer path one binds to.
1801 The getifaddrs upgrade path broken with 20111215 has been restored.
1802 If you have upgraded in between 20111215 and 20120209 you need to
1803 recompile libc again with your kernel. You still need to recompile
1804 world to be able to configure CARP but this restriction already
1805 comes from 20111215.
1808 The set_rcvar() function has been removed from /etc/rc.subr. All
1809 base and ports rc.d scripts have been updated, so if you have a
1810 port installed with a script in /usr/local/etc/rc.d you can either
1811 hand-edit the rcvar= line, or reinstall the port.
1813 An easy way to handle the mass-update of /etc/rc.d:
1814 rm /etc/rc.d/* && mergemaster -i
1817 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1818 on the current CPU and prevents other threads from running.
1819 This behavior can be reverted using the kern.stop_scheduler_on_panic
1821 The new behavior can be incompatible with kern.sync_on_panic.
1824 The carp(4) facility has been changed significantly. Configuration
1825 of the CARP protocol via ifconfig(8) has changed, as well as format
1826 of CARP events submitted to devd(8) has changed. See manual pages
1827 for more information. The arpbalance feature of carp(4) is currently
1828 not supported anymore.
1830 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1831 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1832 need to be recompiled.
1835 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1839 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1840 explicitely support non-MPSAFE filesystems.
1841 It is on by default for all supported platform at this present
1845 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1846 i386 and pc98 GENERIC kernel configuration files.
1849 sysinstall has been removed
1852 The stable/9 branch created in subversion. This corresponds to the
1853 RELENG_9 branch in CVS.
1859 Avoid using make -j when upgrading. While generally safe, there are
1860 sometimes problems using -j to upgrade. If your upgrade fails with
1861 -j, please try again without -j. From time to time in the past there
1862 have been problems using -j with buildworld and/or installworld. This
1863 is especially true when upgrading between "distant" versions (eg one
1864 that cross a major release boundary or several minor releases, or when
1865 several months have passed on the -current branch).
1867 Sometimes, obscure build problems are the result of environment
1868 poisoning. This can happen because the make utility reads its
1869 environment when searching for values for global variables. To run
1870 your build attempts in an "environmental clean room", prefix all make
1871 commands with 'env -i '. See the env(1) manual page for more details.
1873 When upgrading from one major version to another it is generally best to
1874 upgrade to the latest code in the currently installed branch first, then
1875 do an upgrade to the new branch. This is the best-tested upgrade path,
1876 and has the highest probability of being successful. Please try this
1877 approach if you encounter problems with a major version upgrade. Since
1878 the stable 4.x branch point, one has generally been able to upgrade from
1879 anywhere in the most recent stable branch to head / current (or even the
1880 last couple of stable branches). See the top of this file when there's
1883 When upgrading a live system, having a root shell around before
1884 installing anything can help undo problems. Not having a root shell
1885 around can lead to problems if pam has changed too much from your
1886 starting point to allow continued authentication after the upgrade.
1888 This file should be read as a log of events. When a later event changes
1889 information of a prior event, the prior event should not be deleted.
1890 Instead, a pointer to the entry with the new information should be
1891 placed in the old entry. Readers of this file should also sanity check
1892 older entries before relying on them blindly. Authors of new entries
1893 should write them with this in mind.
1897 When upgrading the boot ZFS pool to a new version, always follow
1900 1.) recompile and reinstall the ZFS boot loader and boot block
1901 (this is part of "make buildworld" and "make installworld")
1903 2.) update the ZFS boot block on your boot drive
1905 The following example updates the ZFS boot block on the first
1906 partition (freebsd-boot) of a GPT partitioned drive ada0:
1907 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1909 Non-boot pools do not need these updates.
1913 If you are updating from a prior version of FreeBSD (even one just
1914 a few days old), you should follow this procedure. It is the most
1915 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1917 make kernel-toolchain
1918 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1919 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1921 To test a kernel once
1922 ---------------------
1923 If you just want to boot a kernel once (because you are not sure
1924 if it works, or if you want to boot a known bad kernel to provide
1925 debugging information) run
1926 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1927 nextboot -k testkernel
1929 To rebuild everything and install it on the current system.
1930 -----------------------------------------------------------
1931 # Note: sometimes if you are running current you gotta do more than
1932 # is listed here if you are upgrading from a really old current.
1934 <make sure you have good level 0 dumps>
1936 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1937 make installkernel KERNCONF=YOUR_KERNEL_HERE
1939 <reboot in single user> [3]
1946 To cross-install current onto a separate partition
1947 --------------------------------------------------
1948 # In this approach we use a separate partition to hold
1949 # current's root, 'usr', and 'var' directories. A partition
1950 # holding "/", "/usr" and "/var" should be about 2GB in
1953 <make sure you have good level 0 dumps>
1956 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1957 <maybe newfs current's root partition>
1958 <mount current's root partition on directory ${CURRENT_ROOT}>
1959 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1960 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1961 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1962 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1963 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1964 <reboot into current>
1965 <do a "native" rebuild/install as described in the previous section>
1966 <maybe install compatibility libraries from ports/misc/compat*>
1970 To upgrade in-place from stable to current
1971 ----------------------------------------------
1972 <make sure you have good level 0 dumps>
1974 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1976 <reboot in single user> [3]
1983 Make sure that you've read the UPDATING file to understand the
1984 tweaks to various things you need. At this point in the life
1985 cycle of current, things change often and you are on your own
1986 to cope. The defaults can also change, so please read ALL of
1987 the UPDATING entries.
1989 Also, if you are tracking -current, you must be subscribed to
1990 freebsd-current@freebsd.org. Make sure that before you update
1991 your sources that you have read and understood all the recent
1992 messages there. If in doubt, please track -stable which has
1993 much fewer pitfalls.
1995 [1] If you have third party modules, such as vmware, you
1996 should disable them at this point so they don't crash your
1999 [3] From the bootblocks, boot -s, and then do
2004 adjkerntz -i # if CMOS is wall time
2005 Also, when doing a major release upgrade, it is required that
2006 you boot into single user mode to do the installworld.
2008 [4] Note: This step is non-optional. Failure to do this step
2009 can result in a significant reduction in the functionality of the
2010 system. Attempting to do it by hand is not recommended and those
2011 that pursue this avenue should read this file carefully, as well
2012 as the archives of freebsd-current and freebsd-hackers mailing lists
2013 for potential gotchas. The -U option is also useful to consider.
2014 See mergemaster(8) for more information.
2016 [5] Usually this step is a no-op. However, from time to time
2017 you may need to do this if you get unknown user in the following
2018 step. It never hurts to do it all the time. You may need to
2019 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2020 install) after the buildworld before this step if you last updated
2021 from current before 20130425 or from -stable before 20130430.
2023 [6] This only deletes old files and directories. Old libraries
2024 can be deleted by "make delete-old-libs", but you have to make
2025 sure that no program is using those libraries anymore.
2027 [8] In order to have a kernel that can run the 4.x binaries needed to
2028 do an installworld, you must include the COMPAT_FREEBSD4 option in
2029 your kernel. Failure to do so may leave you with a system that is
2030 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2031 required to run the 5.x binaries on more recent kernels. And so on
2032 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2034 Make sure that you merge any new devices from GENERIC since the
2035 last time you updated your kernel config file.
2037 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2038 "?=" instead of the "=" assignment operator, so that buildworld can
2039 override the CPUTYPE if it needs to.
2041 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2042 not on the command line, or in /etc/make.conf. buildworld will
2043 warn if it is improperly defined.
2046 This file contains a list, in reverse chronological order, of major
2047 breakages in tracking -current. It is not guaranteed to be a complete
2048 list of such breakages, and only contains entries since September 23, 2011.
2049 If you need to see UPDATING entries from before that date, you will need
2050 to fetch an UPDATING file from an older FreeBSD release.
2052 Copyright information:
2054 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2056 Redistribution, publication, translation and use, with or without
2057 modification, in full or in part, in any form or format of this
2058 document are permitted without further permission from the author.
2060 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2061 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2062 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2063 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2064 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2065 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2066 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2067 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2068 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2069 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2070 POSSIBILITY OF SUCH DAMAGE.
2072 Contact Warner Losh if you have any questions about your use of