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