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 For UEFI systems: the UEFI loader(8), loader.efi, should be updated in
56 conjunction with installing a new kernel after r330868. The kernel,
57 after this revision, will be more lenient when mapping addresses for
58 UEFI Runtime Services and this may result in a kernel panic without the
59 corresponding loader(8) update.
62 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
63 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
64 Co-existance for the transition period will come shortly. Booting is a
65 complex environment and test coverage for Lua-enabled loaders has been
66 thin, so it would be prudent to assume it might not work and make
67 provisions for backup boot methods.
70 devmatch functionality has been turned on in devd. It will automatically
71 load drivers for unattached devices. This may cause unexpected drivers to
72 be loaded. Please report any problems to current@ and imp@freebsd.org.
75 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
76 6.0.0. Please see the 20141231 entry below for information about
77 prerequisites and upgrading, if you are not already using clang 3.5.0
81 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
82 This means it is used to link the kernel and userland libraries and
83 executables, but is not yet installed as /usr/bin/ld by default.
85 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
86 WITHOUT_LLD_BOOTSTRAP=yes
89 On i386, pmtimer has been removed. Its functionality has been folded
90 into apm. It was a no-op on ACPI in current for a while now (but was still
91 needed on i386 in FreeBSD 11 and earlier). Users may need to remove it
92 from kernel config files.
95 The use of RSS hash from the network card aka flowid has been
96 disabled by default for lagg(4) as it's currently incompatible with
97 the lacp and loadbalance protocols.
99 This can be re-enabled by setting the following in loader.conf:
100 net.link.lagg.default_use_flowid="1"
103 The SW_WATCHDOG option is no longer necessary to enable the
104 hardclock-based software watchdog if no hardware watchdog is
105 configured. As before, SW_WATCHDOG will cause the software
106 watchdog to be enabled even if a hardware watchdog is configured.
109 r326887 fixes the issue described in the 20171214 UPDATING entry.
110 r326888 flips the switch back to building GELI support always.
113 r362593 broke ZFS + GELI support for reasons unknown. However,
114 it also broke ZFS support generally, so GELI has been turned off
115 by default as the lesser evil in r326857. If you boot off ZFS and/or
116 GELI, it might not be a good time to update.
119 PowerPC users must update loader(8) by rebuilding world before
120 installing a new kernel, as the protocol connecting them has
121 changed. Without the update, loader metadata will not be passed
122 successfully to the kernel and users will have to enter their
123 root partition at the kernel mountroot prompt to continue booting.
124 Newer versions of loader can boot old kernels without issue.
127 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
128 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
129 to WITH/OUT_LOADER_GELI.
132 The naive and non-compliant support of posix_fallocate(2) in ZFS
133 has been removed as of r325320. The system call now returns EINVAL
134 when used on a ZFS file. Although the new behavior complies with the
135 standard, some consumers are not prepared to cope with it.
136 One known victim is lld prior to r325420.
139 Building in a FreeBSD src checkout will automatically create object
140 directories now rather than store files in the current directory if
141 'make obj' was not ran. Calling 'make obj' is no longer necessary.
142 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
143 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
147 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
148 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
149 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
150 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
151 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
152 The UNIFIED_OBJDIR option is a transitional feature that will be
153 removed for 12.0 release; please migrate to the new format for any
154 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
155 than hardcoding paths.
158 The native-xtools target no longer installs the files by default to the
159 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
160 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
163 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
164 options are changing from controlling the build if defined / undefined
165 to controlling the build with explicit 'yes' or 'no' values. They will
166 shift to WITH/WITHOUT options to match other options in the system.
169 libstand has turned into a private library for sys/boot use only.
170 It is no longer supported as a public interface outside of sys/boot.
173 The arm port has split armv6 into armv6 and armv7. armv7 is now
174 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
175 and are running a kernel from before r324363, you will need to add
176 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
179 When building multiple kernels using KERNCONF, non-existent KERNCONF
180 files will produce an error and buildkernel will fail. Previously
181 missing KERNCONF files silently failed giving no indication as to
182 why, only to subsequently discover during installkernel that the
183 desired kernel was never built in the first place.
186 The default serial number format for CTL LUNs has changed. This will
187 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
188 or iSCSI clients care about their LUNs' serial numbers. Users who
189 require serial number stability should hardcode serial numbers in
193 For 32-bit arm compiled for hard-float support, soft-floating point
194 binaries now always get their shared libraries from
195 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
196 /usr/libsoft also existed). Only users with a hard-float ld.so, but
197 soft-float everything else should be affected.
200 The geli password typed at boot is now hidden. To restore the previous
201 behavior, see geli(8) for configuration options.
204 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
205 sysctl values. Minor nit, but requires a rebuild of both world/kernel
209 "make check" behavior (made in ^/head@r295380) has been changed to
210 execute from a limited sandbox, as opposed to executing from
214 - The "beforecheck" and "aftercheck" targets are now specified.
215 - ${CHECKDIR} (added in commit noted above) has been removed.
216 - Legacy behavior can be enabled by setting
217 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
219 If the limited sandbox mode is enabled, "make check" will execute
220 "make distribution", then install, execute the tests, and clean up the
221 sandbox if successful.
223 The "make distribution" and "make install" targets are typically run as
224 root to set appropriate permissions and ownership at installation time.
225 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
226 environment if executing "make check" with limited sandbox mode using
227 an unprivileged user.
230 Since the switch to GPT disk labels, fsck for UFS/FFS has been
231 unable to automatically find alternate superblocks. As of r322297,
232 the information needed to find alternate superblocks has been
233 moved to the end of the area reserved for the boot block.
234 Filesystems created with a newfs of this vintage or later
235 will create the recovery information. If you have a filesystem
236 created prior to this change and wish to have a recovery block
237 created for your filesystem, you can do so by running fsck in
238 foreground mode (i.e., do not use the -p or -y options). As it
239 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
240 to which you should answer yes.
243 As of r321665, an NFSv4 server configuration that services
244 Kerberos mounts or clients that do not support the uid/gid in
245 owner/owner_group string capability, must explicitly enable
246 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
247 machine's /etc/rc.conf file.
250 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
251 Please see the 20141231 entry below for information about prerequisites
252 and upgrading, if you are not already using clang 3.5.0 or higher.
255 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
256 r-commands (rlogin, rsh, etc.) to be built with the base system.
259 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
260 a very major ABI incompatible change, so users of FreeBSD/powerpc must
261 be careful when performing source upgrades. It is best to run
262 'make installworld' from an alternate root system, either a live
263 CD/memory stick, or a temporary root partition. Additionally, all ports
264 must be recompiled. powerpc64 is largely unaffected, except in the case
265 of 32-bit compatibility. All 32-bit binaries will be affected.
268 Forward compatibility for the "ino64" project have been committed. This
269 will allow most new binaries to run on older kernels in a limited
270 fashion. This prevents many of the common foot-shooting actions in the
271 upgrade as well as the limited ability to roll back the kernel across
272 the ino64 upgrade. Complicated use cases may not work properly, though
273 enough simpler ones work to allow recovery in most situations.
276 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
277 if you require the GPL compiler.
280 The internal ABI used for communication between the NFS kernel modules
281 was changed by r320085, so __FreeBSD_version was bumped to
282 ensure all the NFS related modules are updated together.
285 The ABI of struct event was changed by extending the data
286 member to 64bit and adding ext fields. For upgrade, same
287 precautions as for the entry 20170523 "ino64" must be
291 The GNU roff toolchain has been removed from base. To render manpages
292 which are not supported by mandoc(1), man(1) can fallback on GNU roff
293 from ports (and recommends to install it).
294 To render roff(7) documents, consider using GNU roff from ports or the
295 heirloom doctools roff toolchain from ports via pkg install groff or
296 via pkg install heirloom-doctools.
299 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
300 smaller runtime footprint builds. This is useful for embedded systems
301 which only require one chipset support.
303 If you load it as a module, make sure this is in /boot/loader.conf:
307 This will load the HAL, all chip/RF backends and if_ath_pci.
308 If you have if_ath_pci in /boot/loader.conf, ensure it is after
309 if_ath or it will not load any HAL chipset support.
311 If you want to selectively load things (eg on ye cheape ARM/MIPS
312 platforms where RAM is at a premium) you should:
315 * load the chip modules in question
316 * load ath_rate, ath_dfs
318 * load if_ath_pci and/or if_ath_ahb depending upon your particular
319 bus bind type - this is where probe/attach is done.
321 For further comments/feedback, poke adrian@ .
324 The "ino64" 64-bit inode project has been committed, which extends
325 a number of types to 64 bits. Upgrading in place requires care and
326 adherence to the documented upgrade procedure.
328 If using a custom kernel configuration ensure that the
329 COMPAT_FREEBSD11 option is included (as during the upgrade the
330 system will be running the ino64 kernel with the existing world).
332 For the safest in-place upgrade begin by removing previous build
333 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
334 full procedure documented below under the heading "To rebuild
335 everything and install it on the current system." Specifically,
336 a reboot is required after installing the new kernel before
340 The NATM framework including the en(4), fatm(4), hatm(4), and
341 patm(4) devices has been removed. Consumers should plan a
342 migration before the end-of-life date for FreeBSD 11.
345 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
346 diff has not been implemented, if those are needed a newer version of
347 GNU diff is available via the diffutils package under the gdiff name.
350 As of r316810 for ipfilter, keep frags is no longer assumed when
351 keep state is specified in a rule. r316810 aligns ipfilter with
352 documentation in man pages separating keep frags from keep state.
353 This allows keep state to be specified without forcing keep frags
354 and allows keep frags to be specified independently of keep state.
355 To maintain previous behaviour, also specify keep frags with
356 keep state (as documented in ipf.conf.5).
359 arm64 builds now use the base system LLD 4.0.0 linker by default,
360 instead of requiring that the aarch64-binutils port or package be
361 installed. To continue using aarch64-binutils, set
362 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
365 The UDP optimization in entry 20160818 that added the sysctl
366 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
367 packets will no longer be treated as L3 broadcast packets.
370 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
371 use any explicitly assigned loopback address available in the jail
372 instead of using the first assigned address of the jail.
375 The ctl.ko module no longer implements the iSCSI target frontend:
376 cfiscsi.ko does instead.
378 If building cfiscsi.ko as a kernel module, the module can be loaded
379 via one of the following methods:
380 - `cfiscsi_load="YES"` in loader.conf(5).
381 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
382 - ctladm(8)/ctld(8), when compiled with iSCSI support
383 (`WITH_ISCSI=yes` in src.conf(5))
385 Please see cfiscsi(4) for more details.
388 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
389 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
390 same source (previously, the dependency of mmcsd.ko on mmc.ko was
391 missing, but mmcsd.ko now will refuse to load if it is incompatible
395 The syntax of ipfw(8) named states was changed to avoid ambiguity.
396 If you have used named states in the firewall rules, you need to modify
397 them after installworld and before rebooting. Now named states must
398 be prefixed with colon.
401 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
402 removed as the userland we provide cannot use them. The KMS version
403 (sys/dev/drm2) supports the same hardware.
406 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
407 Please see the 20141231 entry below for information about prerequisites
408 and upgrading, if you are not already using clang 3.5.0 or higher.
411 The code that provides support for ZFS .zfs/ directory functionality
412 has been reimplemented. It's not possible now to create a snapshot
413 by mkdir under .zfs/snapshot/. That should be the only user visible
417 EISA bus support has been removed. The WITH_EISA option is no longer
421 MCA bus support has been removed.
424 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
425 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
428 The EM_MULTIQUEUE kernel configuration option is deprecated now that
429 the em(4) driver conforms to iflib specifications.
432 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
433 IFLIB. If you have a custom kernel configuration that excludes em(4)
434 but you use igb(4), you need to re-add em(4) to your custom configuration.
437 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
438 Please see the 20141231 entry below for information about prerequisites
439 and upgrading, if you are not already using clang 3.5.0 or higher.
442 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
443 Please see the 20141231 entry below for information about prerequisites
444 and upgrading, if you are not already using clang 3.5.0 or higher.
447 The layout of the pmap structure has changed for powerpc to put the pmap
448 statistics at the front for all CPU variations. libkvm(3) and all tools
449 that link against it need to be recompiled.
452 isl(4) and cyapa(4) drivers now require a new driver,
453 chromebook_platform(4), to work properly on Chromebook-class hardware.
454 On other types of hardware the drivers may need to be configured using
455 device hints. Please see the corresponding manual pages for details.
458 The urtwn(4) driver was merged into rtwn(4) and now consists of
459 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
461 Also, firmware for RTL8188CE was renamed due to possible name
462 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
465 GNU rcs has been removed from base. It is available as packages:
466 - rcs: Latest GPLv3 GNU rcs version.
467 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
471 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
472 modules now requires that the kernel configuration contain the
473 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
476 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
477 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
480 Relocatable object files with the extension of .So have been renamed
481 to use an extension of .pico instead. The purpose of this change is
482 to avoid a name clash with shared libraries on case-insensitive file
483 systems. On those file systems, foo.So is the same file as foo.so.
486 GNU rcs has been turned off by default. It can (temporarily) be built
487 again by adding WITH_RCS knob in src.conf.
488 Otherwise, GNU rcs is available from packages:
489 - rcs: Latest GPLv3 GNU rcs version.
490 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
493 The backup_uses_rcs functionality has been removed from rc.subr.
496 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
497 two separate components, QUEUE_MACRO_DEBUG_TRACE and
498 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
499 QUEUE_MACRO_DEBUG behavior.
502 r304787 changed some ioctl interfaces between the iSCSI userspace
503 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
504 rebuilt to work with new kernels. __FreeBSD_version has been bumped
508 The UDP receive code has been updated to only treat incoming UDP
509 packets that were addressed to an L2 broadcast address as L3
510 broadcast packets. It is not expected that this will affect any
511 standards-conforming UDP application. The new behaviour can be
512 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
516 Remove the openbsd_poll system call.
517 __FreeBSD_version has been bumped because of this.
520 The libc stub for the pipe(2) system call has been replaced with
521 a wrapper that calls the pipe2(2) system call and the pipe(2)
522 system call is now only implemented by the kernels that include
523 "options COMPAT_FREEBSD10" in their config file (this is the
524 default). Users should ensure that this option is enabled in
525 their kernel or upgrade userspace to r302092 before upgrading their
529 CAM will now strip leading spaces from SCSI disks' serial numbers.
530 This will affect users who create UFS filesystems on SCSI disks using
531 those disk's diskid device nodes. For example, if /etc/fstab
532 previously contained a line like
533 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
534 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
535 transforms like gmirror may also be affected. ZFS users should
539 The bitstring(3) API has been updated with new functionality and
540 improved performance. But it is binary-incompatible with the old API.
541 Objects built with the new headers may not be linked against objects
542 built with the old headers.
545 The brk and sbrk functions have been removed from libc on arm64.
546 Binutils from ports has been updated to not link to these
547 functions and should be updated to the latest version before
548 installing a new libc.
551 The armv6 port now defaults to hard float ABI. Limited support
552 for running both hardfloat and soft float on the same system
553 is available using the libraries installed with -DWITH_LIBSOFT.
554 This has only been tested as an upgrade path for installworld
555 and packages may fail or need manual intervention to run. New
556 packages will be needed.
558 To update an existing self-hosted armv6hf system, you must add
559 TARGET_ARCH=armv6 on the make command line for both the build
560 and the install steps.
563 Kernel modules compiled outside of a kernel build now default to
564 installing to /boot/modules instead of /boot/kernel. Many kernel
565 modules built this way (such as those in ports) already overrode
566 KMODDIR explicitly to install into /boot/modules. However,
567 manually building and installing a module from /sys/modules will
568 now install to /boot/modules instead of /boot/kernel.
571 The CAM I/O scheduler has been committed to the kernel. There should be
572 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
573 list of known rogues that claim support for this but actually corrupt
574 data is believed to be complete, be on the lookout for data
575 corruption. The known rogue list is believed to be complete:
577 o Crucial MX100, M550 drives with MU01 firmware.
578 o Micron M510 and M550 drives with MU01 firmware.
579 o Micron M500 prior to MU07 firmware
580 o Samsung 830, 840, and 850 all firmwares
581 o FCCT M500 all firmwares
583 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
584 with working NCQ TRIM. For Micron branded drives, see your sales rep for
585 updated firmware. Black listed drives will work correctly because these
586 drives work correctly so long as no NCQ TRIMs are sent to them. Given
587 this list is the same as found in Linux, it's believed there are no
588 other rogues in the market place. All other models from the above
591 To be safe, if you are at all concerned, you can quirk each of your
592 drives to prevent NCQ from being sent by setting:
593 kern.cam.ada.X.quirks="0x2"
594 in loader.conf. If the drive requires the 4k sector quirk, set the
598 The FAST_DEPEND build option has been removed and its functionality is
599 now the one true way. The old mkdep(1) style of 'make depend' has
600 been removed. See 20160311 for further details.
603 Resource range types have grown from unsigned long to uintmax_t. All
604 drivers, and anything using libdevinfo, need to be recompiled.
607 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
608 builds. It no longer runs mkdep(1) during 'make depend', and the
609 'make depend' stage can safely be skipped now as it is auto ran
610 when building 'make all' and will generate all SRCS and DPSRCS before
611 building anything else. Dependencies are gathered at compile time with
612 -MF flags kept in separate .depend files per object file. Users should
613 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
617 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
618 kernel modules. Therefore, if you load any kernel modules at boot time,
619 please install the boot loaders after you install the kernel, but before
623 make kernel KERNCONF=YOUR_KERNEL_HERE
624 make -C sys/boot install
625 <reboot in single user>
627 Then follow the usual steps, described in the General Notes section,
631 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
632 see the 20141231 entry below for information about prerequisites and
633 upgrading, if you are not already using clang 3.5.0 or higher.
636 The AIO subsystem is now a standard part of the kernel. The
637 VFS_AIO kernel option and aio.ko kernel module have been removed.
638 Due to stability concerns, asynchronous I/O requests are only
639 permitted on sockets and raw disks by default. To enable
640 asynchronous I/O requests on all file types, set the
641 vfs.aio.enable_unsafe sysctl to a non-zero value.
644 The ELF object manipulation tool objcopy is now provided by the
645 ELF Tool Chain project rather than by GNU binutils. It should be a
646 drop-in replacement, with the addition of arm64 support. The
647 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
648 to obtain the GNU version if necessary.
651 Building ZFS pools on top of zvols is prohibited by default. That
652 feature has never worked safely; it's always been prone to deadlocks.
653 Using a zvol as the backing store for a VM guest's virtual disk will
654 still work, even if the guest is using ZFS. Legacy behavior can be
655 restored by setting vfs.zfs.vol.recursive=1.
658 The NONE and HPN patches has been removed from OpenSSH. They are
659 still available in the security/openssh-portable port.
662 With the addition of ypldap(8), a new _ypldap user is now required
663 during installworld. "mergemaster -p" can be used to add the user
664 prior to installworld, as documented in the handbook.
667 The tftp loader (pxeboot) now uses the option root-path directive. As a
668 consequence it no longer looks for a pxeboot.4th file on the tftp
669 server. Instead it uses the regular /boot infrastructure as with the
673 The code to start recording plug and play data into the modules has
674 been committed. While the old tools will properly build a new kernel,
675 a number of warnings about "unknown metadata record 4" will be produced
676 for an older kldxref. To avoid such warnings, make sure to rebuild
677 the kernel toolchain (or world). Make sure that you have r292078 or
678 later when trying to build 292077 or later before rebuilding.
681 Debug data files are now built by default with 'make buildworld' and
682 installed with 'make installworld'. This facilitates debugging but
683 requires more disk space both during the build and for the installed
684 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
688 r291527 changed the internal interface between the nfsd.ko and
689 nfscommon.ko modules. As such, they must both be upgraded to-gether.
690 __FreeBSD_version has been bumped because of this.
693 Add support for unicode collation strings leads to a change of
694 order of files listed by ls(1) for example. To get back to the old
695 behaviour, set LC_COLLATE environment variable to "C".
697 Databases administrators will need to reindex their databases given
698 collation results will be different.
700 Due to a bug in install(1) it is recommended to remove the ancient
701 locales before running make installworld.
703 rm -rf /usr/share/locale/*
706 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
707 libcrypto.so.7 or libssl.so.7 must be recompiled.
710 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
711 Kernel modules isp_2400_multi and isp_2500_multi were removed and
712 should be replaced with isp_2400 and isp_2500 modules respectively.
715 The build previously allowed using 'make -n' to not recurse into
716 sub-directories while showing what commands would be executed, and
717 'make -n -n' to recursively show commands. Now 'make -n' will recurse
718 and 'make -N' will not.
721 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
722 and etcupdate will now use this file. A custom sendmail.cf is now
723 updated via this mechanism rather than via installworld. If you had
724 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
725 want to remove the exclusion or change it to "always install".
726 /etc/mail/sendmail.cf is now managed the same way regardless of
727 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
728 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
731 Compatibility shims for legacy ATA device names have been removed.
732 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
733 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
734 environment variables, /dev/ad* and /dev/ar* symbolic links.
737 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
738 Please see the 20141231 entry below for information about prerequisites
739 and upgrading, if you are not already using clang 3.5.0 or higher.
742 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
743 and renamed from .symbols to .debug. This reduces the size requirements
744 on the boot partition or file system and provides consistency with
745 userland debug files.
747 When using the supported kernel installation method the
748 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
749 as is done with /boot/kernel.
751 Developers wishing to maintain the historical behavior of installing
752 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
755 The wireless drivers had undergone changes that remove the 'parent
756 interface' from the ifconfig -l output. The rc.d network scripts
757 used to check presence of a parent interface in the list, so old
758 scripts would fail to start wireless networking. Thus, etcupdate(3)
759 or mergemaster(8) run is required after kernel update, to update your
760 rc.d scripts in /etc.
763 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
764 These configurations are now automatically interpreted as
765 'scrub fragment reassemble'.
768 Kernel-loadable modules for the random(4) device are back. To use
769 them, the kernel must have
772 options RANDOM_LOADABLE
774 kldload(8) can then be used to load random_fortuna.ko
775 or random_yarrow.ko. Please note that due to the indirect
776 function calls that the loadable modules need to provide,
777 the build-in variants will be slightly more efficient.
779 The random(4) kernel option RANDOM_DUMMY has been retired due to
780 unpopularity. It was not all that useful anyway.
783 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
784 Control over building the ELF Tool Chain tools is now provided by
785 the WITHOUT_TOOLCHAIN knob.
788 The polarity of Pulse Per Second (PPS) capture events with the
789 uart(4) driver has been corrected. Prior to this change the PPS
790 "assert" event corresponded to the trailing edge of a positive PPS
791 pulse and the "clear" event was the leading edge of the next pulse.
793 As the width of a PPS pulse in a typical GPS receiver is on the
794 order of 1 millisecond, most users will not notice any significant
795 difference with this change.
797 Anyone who has compensated for the historical polarity reversal by
798 configuring a negative offset equal to the pulse width will need to
799 remove that workaround.
802 The default group assigned to /dev/dri entries has been changed
803 from 'wheel' to 'video' with the id of '44'. If you want to have
804 access to the dri devices please add yourself to the video group
807 # pw groupmod video -m $USER
810 The menu.rc and loader.rc files will now be replaced during
811 upgrades. Please migrate local changes to menu.rc.local and
812 loader.rc.local instead.
815 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
816 strings and strip have been removed. The src.conf(5) knob
817 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
820 As ZFS requires more kernel stack pages than is the default on some
821 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
822 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
824 Please consider using 'options KSTACK_PAGES=X' where X is greater
825 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
828 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
829 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
830 default, i.e., they will not contain "::". For example, instead
831 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
832 to have a more specific match, such as different map entries for
833 IPv6:0:0 vs IPv6:0. This change requires that configuration
834 data (including maps, files, classes, custom ruleset, etc.) must
835 use the same format, so make certain such configuration data is
836 upgrading. As a very simple check search for patterns like
837 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
838 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
839 the cf option UseCompressedIPv6Addresses.
842 The default kernel entropy-processing algorithm is now
843 Fortuna, replacing Yarrow.
845 Assuming you have 'device random' in your kernel config
846 file, the configurations allow a kernel option to override
847 this default. You may choose *ONE* of:
849 options RANDOM_YARROW # Legacy /dev/random algorithm.
850 options RANDOM_DUMMY # Blocking-only driver.
852 If you have neither, you get Fortuna. For most people,
853 read no further, Fortuna will give a /dev/random that works
854 like it always used to, and the difference will be irrelevant.
856 If you remove 'device random', you get *NO* kernel-processed
857 entropy at all. This may be acceptable to folks building
858 embedded systems, but has complications. Carry on reading,
859 and it is assumed you know what you need.
861 *PLEASE* read random(4) and random(9) if you are in the
862 habit of tweaking kernel configs, and/or if you are a member
863 of the embedded community, wanting specific and not-usual
864 behaviour from your security subsystems.
866 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
867 random', you will NOT have a functioning /dev/random, and
868 many cryptographic features will not work, including SSH.
869 You may also find strange behaviour from the random(3) set
870 of library functions, in particular sranddev(3), srandomdev(3)
871 and arc4random(3). The reason for this is that the KERN_ARND
872 sysctl only returns entropy if it thinks it has some to
873 share, and with RANDOM_DUMMY or no 'device random' this
877 An additional fix for the issue described in the 20150614 sendmail
878 entry below has been committed in revision 284717.
881 FreeBSD's old make (fmake) has been removed from the system. It is
882 available as the devel/fmake port or via pkg install fmake.
885 The fix for the issue described in the 20150614 sendmail entry
886 below has been committed in revision 284436. The work
887 around described in that entry is no longer needed unless the
888 default setting is overridden by a confDH_PARAMETERS configuration
889 setting of '5' or pointing to a 512 bit DH parameter file.
892 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
893 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
894 and devel/kyua to version 0.20+ and adjust any calling code to work
895 with Kyuafile and kyua.
898 The import of openssl to address the FreeBSD-SA-15:10.openssl
899 security advisory includes a change which rejects handshakes
900 with DH parameters below 768 bits. sendmail releases prior
901 to 8.15.2 (not yet released), defaulted to a 512 bit
902 DH parameter setting for client connections. To work around
903 this interoperability, sendmail can be configured to use a
904 2048 bit DH parameter by:
906 1. Edit /etc/mail/`hostname`.mc
907 2. If a setting for confDH_PARAMETERS does not exist or
908 exists and is set to a string beginning with '5',
910 3. If a setting for confDH_PARAMETERS exists and is set to
911 a file path, create a new file with:
912 openssl dhparam -out /path/to/file 2048
913 4. Rebuild the .cf file:
914 cd /etc/mail/; make; make install
916 cd /etc/mail/; make restart
918 A sendmail patch is coming, at which time this file will be
922 Generation of legacy formatted entries have been disabled by default
923 in pwd_mkdb(8), as all base system consumers of the legacy formatted
924 entries were converted to use the new format by default when the new,
925 machine independent format have been added and supported since FreeBSD
928 Please see the pwd_mkdb(8) manual page for further details.
931 Clang and llvm have been upgraded to 3.6.1 release. Please see the
932 20141231 entry below for information about prerequisites and upgrading,
933 if you are not already using 3.5.0 or higher.
936 TI platform code switched to using vendor DTS files and this update
937 may break existing systems running on Beaglebone, Beaglebone Black,
940 - dtb files should be regenerated/reinstalled. Filenames are the
941 same but content is different now
942 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
943 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
944 addressing scheme is now pin 25 on /dev/gpioc3.
945 - Pandaboard: /etc/ttys should be updated, serial console device is
946 now /dev/ttyu2, not /dev/ttyu0
949 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
950 If you need the GNU extension from groff soelim(1), install groff
951 from package: pkg install groff, or via ports: textproc/groff.
954 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
955 defined in symlink(7); previously symlinks were silently ignored.
958 The const qualifier has been removed from iconv(3) to comply with
959 POSIX. The ports tree is aware of this from r384038 onwards.
962 Libraries specified by LIBADD in Makefiles must have a corresponding
963 DPADD_<lib> variable to ensure correct dependencies. This is now
964 enforced in src.libnames.mk.
967 From legacy ata(4) driver was removed support for SATA controllers
968 supported by more functional drivers ahci(4), siis(4) and mvs(4).
969 Kernel modules ataahci and ataadaptec were removed completely,
970 replaced by ahci and mvs modules respectively.
973 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
974 the 20141231 entry below for information about prerequisites and
975 upgrading, if you are not already using 3.5.0 or higher.
978 The 32-bit PowerPC kernel has been changed to a position-independent
979 executable. This can only be booted with a version of loader(8)
980 newer than January 31, 2015, so make sure to update both world and
981 kernel before rebooting.
984 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
985 but before r278950, the RNG was not seeded properly. Immediately
986 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
987 ssh keys or openssl keys) that were generated w/ a kernel from that
988 range. This does not affect programs that directly used /dev/random
989 or /dev/urandom. All userland uses of arc4random(3) are affected.
992 The autofs(4) ABI was changed in order to restore binary compatibility
993 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
997 The powerpc64 kernel has been changed to a position-independent
998 executable. This can only be booted with a new version of loader(8),
999 so make sure to update both world and kernel before rebooting.
1002 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1003 only release, no new features have been added. Please see the 20141231
1004 entry below for information about prerequisites and upgrading, if you
1005 are not already using 3.5.0.
1008 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1009 taken from the ELF Tool Chain project rather than GNU binutils. They
1010 should be drop-in replacements, with the addition of arm64 support.
1011 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1012 binutils tools, if necessary. See 20150805 for updated information.
1015 The default Unbound configuration now enables remote control
1016 using a local socket. Users who have already enabled the
1017 local_unbound service should regenerate their configuration
1018 by running "service local_unbound setup" as root.
1021 The GNU texinfo and GNU info pages have been removed.
1022 To be able to view GNU info pages please install texinfo from ports.
1025 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1027 As of this release, a prerequisite for building clang, llvm and lldb is
1028 a C++11 capable compiler and C++11 standard library. This means that to
1029 be able to successfully build the cross-tools stage of buildworld, with
1030 clang as the bootstrap compiler, your system compiler or cross compiler
1031 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1032 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1035 On any standard FreeBSD 10.x or 11.x installation, where clang and
1036 libc++ are on by default (that is, on x86 or arm), this should work out
1039 On 9.x installations where clang is enabled by default, e.g. on x86 and
1040 powerpc, libc++ will not be enabled by default, so libc++ should be
1041 built (with clang) and installed first. If both clang and libc++ are
1042 missing, build clang first, then use it to build libc++.
1044 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1045 the instructions for 9.x above.
1047 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1048 default, and do not build clang.
1050 Many embedded systems are resource constrained, and will not be able to
1051 build clang in a reasonable time, or in some cases at all. In those
1052 cases, cross building bootable systems on amd64 is a workaround.
1054 This new version of clang introduces a number of new warnings, of which
1055 the following are most likely to appear:
1059 This warns in two cases, for both C and C++:
1060 * When the code is trying to take the absolute value of an unsigned
1061 quantity, which is effectively a no-op, and almost never what was
1062 intended. The code should be fixed, if at all possible. If you are
1063 sure that the unsigned quantity can be safely cast to signed, without
1064 loss of information or undefined behavior, you can add an explicit
1065 cast, or disable the warning.
1067 * When the code is trying to take an absolute value, but the called
1068 abs() variant is for the wrong type, which can lead to truncation.
1069 If you want to disable the warning instead of fixing the code, please
1070 make sure that truncation will not occur, or it might lead to unwanted
1073 -Wtautological-undefined-compare and
1074 -Wundefined-bool-conversion
1076 These warn when C++ code is trying to compare 'this' against NULL, while
1077 'this' should never be NULL in well-defined C++ code. However, there is
1078 some legacy (pre C++11) code out there, which actively abuses this
1079 feature, which was less strictly defined in previous C++ versions.
1081 Squid and openjdk do this, for example. The warning can be turned off
1082 for C++98 and earlier, but compiling the code in C++11 mode might result
1083 in unexpected behavior; for example, the parts of the program that are
1084 unreachable could be optimized away.
1087 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1088 kernel sources have been removed. The .h files remain, since some
1089 utilities include them. This will need to be fixed later.
1090 If "mount -t oldnfs ..." is attempted, it will fail.
1091 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1092 the utilities will report errors.
1095 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1096 directories to top level SUBDIR variable when their parent
1097 directory is included in LOCAL_DIRS. Users with build systems with
1098 such hierarchies and without SUBDIR entries in the parent
1099 directory Makefiles should add them or add the directories to
1103 faith(4) and faithd(8) have been removed from the base system. Faith
1104 has been obsolete for a very long time.
1107 vt(4), the new console driver, is enabled by default. It brings
1108 support for Unicode and double-width characters, as well as
1109 support for UEFI and integration with the KMS kernel video
1112 You may need to update your console settings in /etc/rc.conf,
1113 most probably the keymap. During boot, /etc/rc.d/syscons will
1114 indicate what you need to do.
1116 vt(4) still has issues and lacks some features compared to
1117 syscons(4). See the wiki for up-to-date information:
1118 https://wiki.freebsd.org/Newcons
1120 If you want to keep using syscons(4), you can do so by adding
1121 the following line to /boot/loader.conf:
1125 pjdfstest has been integrated into kyua as an opt-in test suite.
1126 Please see share/doc/pjdfstest/README for more details on how to
1130 gperf has been removed from the base system for architectures
1131 that use clang. Ports that require gperf will obtain it from the
1135 pjdfstest has been moved from tools/regression/pjdfstest to
1139 At svn r271982, The default linux compat kernel ABI has been adjusted
1140 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1141 update. If you wish to continue using the linux-f10 compat ports,
1142 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1143 encouraged to update their linux-compat packages to linux-c6 during
1144 their next update cycle.
1147 The ofwfb driver, used to provide a graphics console on PowerPC when
1148 using vt(4), no longer allows mmap() of all physical memory. This
1149 will prevent Xorg on PowerPC with some ATI graphics cards from
1150 initializing properly unless x11-servers/xorg-server is updated to
1154 The xdev targets have been converted to using TARGET and
1155 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1158 The default unbound configuration has been modified to address
1159 issues with reverse lookups on networks that use private
1160 address ranges. If you use the local_unbound service, run
1161 "service local_unbound setup" as root to regenerate your
1162 configuration, then "service local_unbound reload" to load the
1166 The GNU texinfo and GNU info pages are not built and installed
1167 anymore, WITH_INFO knob has been added to allow to built and install
1169 UPDATE: see 20150102 entry on texinfo's removal
1172 The GNU readline library is now an INTERNALLIB - that is, it is
1173 statically linked into consumers (GDB and variants) in the base
1174 system, and the shared library is no longer installed. The
1175 devel/readline port is available for third party software that
1179 The Itanium architecture (ia64) has been removed from the list of
1180 known architectures. This is the first step in the removal of the
1184 Commit r268115 has added NFSv4.1 server support, merged from
1185 projects/nfsv4.1-server. Since this includes changes to the
1186 internal interfaces between the NFS related modules, a full
1187 build of the kernel and modules will be necessary.
1188 __FreeBSD_version has been bumped.
1191 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1192 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1193 which differs from the behaviour controlled by this knob.)
1196 Maximal length of the serial number in CTL was increased from 16 to
1197 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1198 and ctld, need to be rebuilt to work with a new kernel.
1201 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1202 1 respectively to match the upstream numbers. They were out of
1203 sync because, when they were originally added to FreeBSD, the
1204 upstream versions were not respected. These libraries are private
1205 and not yet built by default, so renumbering them should be a
1206 non-issue. However, unclean source trees will yield broken test
1207 programs once the operator executes "make delete-old-libs" after a
1208 "make installworld".
1210 Additionally, the atf-sh binary was made private by moving it into
1211 /usr/libexec/. Already-built shell test programs will keep the
1212 path to the old binary so they will break after "make delete-old"
1215 If you are using WITH_TESTS=yes (not the default), wipe the object
1216 tree and rebuild from scratch to prevent spurious test failures.
1217 This is only needed once: the misnumbered libraries and misplaced
1218 binaries have been added to OptionalObsoleteFiles.inc so they will
1219 be removed during a clean upgrade.
1222 Clang and llvm have been upgraded to 3.4.1 release.
1225 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1226 be removed to avoid issues in the future (and has been added to
1230 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1231 past, it affected all builds that used the bsd.*.mk files. The old
1232 behavior was a bug, but people may have relied upon it. To get this
1233 behavior back, you can .include /etc/src.conf from /etc/make.conf
1234 (which is still global and isn't changed). This also changes the
1235 behavior of incremental builds inside the tree of individual
1236 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1237 Although this has survived make universe and some upgrade scenarios,
1238 other upgrade scenarios may have broken. At least one form of
1239 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1240 as well... In cases where MAKESYSPATH isn't working with this
1241 setting, you'll need to set it to the full path to your tree.
1243 One side effect of all this cleaning up is that bsd.compiler.mk
1244 is no longer implicitly included by bsd.own.mk. If you wish to
1245 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1249 The lindev device has been removed since /dev/full has been made a
1250 standard device. __FreeBSD_version has been bumped.
1253 The knob WITHOUT_VI was added to the base system, which controls
1254 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1255 in order to reorder files share/termcap and didn't build ex(1) as a
1256 build tool, so building/installing with WITH_VI is highly advised for
1257 build hosts for older releases.
1259 This issue has been fixed in stable/9 and stable/10 in r277022 and
1260 r276991, respectively.
1263 The YES_HESIOD knob has been removed. It has been obsolete for
1264 a decade. Please move to using WITH_HESIOD instead or your builds
1265 will silently lack HESIOD.
1268 The uart(4) driver has been changed with respect to its handling
1269 of the low-level console. Previously the uart(4) driver prevented
1270 any process from changing the baudrate or the CLOCAL and HUPCL
1271 control flags. By removing the restrictions, operators can make
1272 changes to the serial console port without having to reboot.
1273 However, when getty(8) is started on the serial device that is
1274 associated with the low-level console, a misconfigured terminal
1275 line in /etc/ttys will now have a real impact.
1276 Before upgrading the kernel, make sure that /etc/ttys has the
1277 serial console device configured as 3wire without baudrate to
1278 preserve the previous behaviour. E.g:
1279 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1282 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1283 to improve performance. To re-enable it, if needed, run rpcbind
1284 with command line option -W.
1287 Switched back to the GPL dtc compiler due to updates in the upstream
1288 dts files not being supported by the BSDL dtc compiler. You will need
1289 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1290 may result while building dtb files during a kernel build if you fail
1291 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1294 Clang and llvm have been upgraded to 3.4 release.
1297 The nve(4) driver has been removed. Please use the nfe(4) driver
1298 for NVIDIA nForce MCP Ethernet adapters instead.
1301 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1302 This could cause certain C++ applications using shared libraries built
1303 against the previous version of libc++ to crash. The incompatibility
1304 has now been fixed, but any C++ applications or shared libraries built
1305 between r261283 and r261801 should be recompiled.
1308 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1309 capability mode support. Please note that enabling the feature in
1310 kernel is still highly recommended.
1313 OpenSSH is now built with sandbox support, and will use sandbox as
1314 the default privilege separation method. This requires Capsicum
1315 capability mode support in kernel.
1318 The libelf and libdwarf libraries have been updated to newer
1319 versions from upstream. Shared library version numbers for
1320 these two libraries were bumped. Any ports or binaries
1321 requiring these two libraries should be recompiled.
1322 __FreeBSD_version is bumped to 1100006.
1325 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1326 instead of providing an explicit one, this would prevent such
1327 Makefile from providing its own Kyuafile in the future during
1328 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1329 intervention is needed to clean an objdir if you use NO_CLEAN:
1330 # find /usr/obj -name Kyuafile | xargs rm -f
1333 The behavior of gss_pseudo_random() for the krb5 mechanism
1334 has changed, for applications requesting a longer random string
1335 than produced by the underlying enctype's pseudo-random() function.
1336 In particular, the random string produced from a session key of
1337 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1338 be different at the 17th octet and later, after this change.
1339 The counter used in the PRF+ construction is now encoded as a
1340 big-endian integer in accordance with RFC 4402.
1341 __FreeBSD_version is bumped to 1100004.
1344 The WITHOUT_ATF build knob has been removed and its functionality
1345 has been subsumed into the more generic WITHOUT_TESTS. If you were
1346 using the former to disable the build of the ATF libraries, you
1347 should change your settings to use the latter.
1350 The default version of mtree is nmtree which is obtained from
1351 NetBSD. The output is generally the same, but may vary
1352 slightly. If you found you need identical output adding
1353 "-F freebsd9" to the command line should do the trick. For the
1354 time being, the old mtree is available as fmtree.
1357 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1358 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1359 1.1.4_8 and verify bsdyml not linked in, before running "make
1361 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1363 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1366 The stable/10 branch has been created in subversion from head
1370 The rc.d/jail script has been updated to support jail(8)
1371 configuration file. The "jail_<jname>_*" rc.conf(5) variables
1372 for per-jail configuration are automatically converted to
1373 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
1374 This is transparently backward compatible. See below about some
1375 incompatibilities and rc.conf(5) manual page for more details.
1377 These variables are now deprecated in favor of jail(8) configuration
1378 file. One can use "rc.d/jail config <jname>" command to generate
1379 a jail(8) configuration file in /var/run/jail.<jname>.conf without
1380 running the jail(8) utility. The default pathname of the
1381 configuration file is /etc/jail.conf and can be specified by
1382 using $jail_conf or $jail_<jname>_conf variables.
1384 Please note that jail_devfs_ruleset accepts an integer at
1385 this moment. Please consider to rewrite the ruleset name
1389 BIND has been removed from the base system. If all you need
1390 is a local resolver, simply enable and start the local_unbound
1391 service instead. Otherwise, several versions of BIND are
1392 available in the ports tree. The dns/bind99 port is one example.
1394 With this change, nslookup(1) and dig(1) are no longer in the base
1395 system. Users should instead use host(1) and drill(1) which are
1396 in the base system. Alternatively, nslookup and dig can
1397 be obtained by installing the dns/bind-tools port.
1400 With the addition of unbound(8), a new unbound user is now
1401 required during installworld. "mergemaster -p" can be used to
1402 add the user prior to installworld, as documented in the handbook.
1405 OpenSSH is now built with DNSSEC support, and will by default
1406 silently trust signed SSHFP records. This can be controlled with
1407 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1408 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1411 The GNU Compiler Collection and C++ standard library (libstdc++)
1412 are no longer built by default on platforms where clang is the system
1413 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1414 options in src.conf.
1417 The PROCDESC kernel option is now part of the GENERIC kernel
1418 configuration and is required for the rwhod(8) to work.
1419 If you are using custom kernel configuration, you should include
1423 The API and ABI related to the Capsicum framework was modified
1424 in backward incompatible way. The userland libraries and programs
1425 have to be recompiled to work with the new kernel. This includes the
1426 following libraries and programs, but the whole buildworld is
1427 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1428 kdump, procstat, rwho, rwhod, uniq.
1431 AES-NI intrinsic support has been added to gcc. The AES-NI module
1432 has been updated to use this support. A new gcc is required to build
1433 the aesni module on both i386 and amd64.
1436 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1437 Thus "device padlock_rng" and "device rdrand_rng" should be
1438 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1441 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1442 enables just the iconv* functionality and is now on by default.
1443 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1444 compatibility. Set WITHOUT_ICONV to build the old way.
1445 If you have been using WITH_ICONV before, you will very likely
1446 need to turn on WITH_LIBICONV_COMPAT.
1449 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1450 Illumos origin, including ZFS. If you have INVARIANTS in your
1451 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1453 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1454 locks if WITNESS option was set. Because that generated a lot of
1455 witness(9) reports and all of them were believed to be false
1456 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1457 can be used to achieve the previous behavior.
1460 Timer values in IPv6 data structures now use time_uptime instead
1461 of time_second. Although this is not a user-visible functional
1462 change, userland utilities which directly use them---ndp(8),
1463 rtadvd(8), and rtsold(8) in the base system---need to be updated
1464 to r253970 or later.
1467 find -delete can now delete the pathnames given as arguments,
1468 instead of only files found below them or if the pathname did
1469 not contain any slashes. Formerly, the following error message
1472 find: -delete: <path>: relative path potentially not safe
1474 Deleting the pathnames given as arguments can be prevented
1475 without error messages using -mindepth 1 or by changing
1476 directory and passing "." as argument to find. This works in the
1477 old as well as the new version of find.
1480 Behavior of devfs rules path matching has been changed.
1481 Pattern is now always matched against fully qualified devfs
1482 path and slash characters must be explicitly matched by
1483 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1484 subdirectories must be reviewed.
1487 The default ARM ABI has changed to the ARM EABI. The old ABI is
1488 incompatible with the ARM EABI and all programs and modules will
1489 need to be rebuilt to work with a new kernel.
1491 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1493 NOTE: Support for the old ABI will be removed in the future and
1494 users are advised to upgrade.
1497 pkg_install has been disconnected from the build if you really need it
1498 you should add WITH_PKGTOOLS in your src.conf(5).
1501 Most of network statistics structures were changed to be able
1502 keep 64-bits counters. Thus all tools, that work with networking
1503 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1506 Fix a bug that allowed a tracing process (e.g. gdb) to write
1507 to a memory-mapped file in the traced process's address space
1508 even if neither the traced process nor the tracing process had
1509 write access to that file.
1512 CVS has been removed from the base system. An exact copy
1513 of the code is available from the devel/cvs port.
1516 Some people report the following error after the switch to bmake:
1518 make: illegal option -- J
1519 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1521 *** [buildworld] Error code 2
1523 this likely due to an old instance of make in
1524 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1525 which src/Makefile will use that blindly, if it exists, so if
1526 you see the above error:
1528 rm -rf `make -V MAKEPATH`
1533 Use bmake by default.
1534 Whereas before one could choose to build with bmake via
1535 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1536 make. The goal is to remove these knobs for 10-RELEASE.
1538 It is worth noting that bmake (like gmake) treats the command
1539 line as the unit of failure, rather than statements within the
1540 command line. Thus '(cd some/where && dosomething)' is safer
1541 than 'cd some/where; dosomething'. The '()' allows consistent
1542 behavior in parallel build.
1545 Fix a bug that allows NFS clients to issue READDIR on files.
1548 The WITHOUT_IDEA option has been removed because
1549 the IDEA patent expired.
1552 The sysctl which controls TRIM support under ZFS has been renamed
1553 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1557 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1558 rather than creating it's own in the temporary directory in
1559 order allow access to bootstrapped versions of tools such as
1560 install and mtree. When upgrading from version of FreeBSD where
1561 the install command does not support -l, you will need to
1562 install a new mergemaster command if mergemaster -p is required.
1563 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1567 Legacy ATA stack, disabled and replaced by new CAM-based one since
1568 FreeBSD 9.0, completely removed from the sources. Kernel modules
1569 atadisk and atapi*, user-level tools atacontrol and burncd are
1570 removed. Kernel option `options ATA_CAM` is now permanently enabled
1574 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1575 and socketpair(2). Software, in particular Kerberos, may
1576 automatically detect and use these during building. The resulting
1577 binaries will not work on older kernels.
1580 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1581 information, see the respective 20130304 entry).
1584 Recent commits to callout(9) changed the size of struct callout,
1585 so the KBI is probably heavily disturbed. Also, some functions
1586 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1587 by macros. Every kernel module using it won't load, so rebuild
1590 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1591 but does not initialize by default (because of the new CTL_DISABLE
1592 option) to save memory. To re-enable it, remove the CTL_DISABLE
1593 option from the kernel config file or set kern.cam.ctl.disable=0
1594 in /boot/loader.conf.
1597 The ctl device has been disabled in GENERIC for i386 and amd64.
1598 This was done due to the extra memory being allocated at system
1599 initialisation time by the ctl driver which was only used if
1600 a CAM target device was created. This makes a FreeBSD system
1601 unusable on 128MB or less of RAM.
1604 A new compression method (lz4) has been merged to -HEAD. Please
1605 refer to zpool-features(7) for more information.
1607 Please refer to the "ZFS notes" section of this file for information
1608 on upgrading boot ZFS pools.
1611 A BSD-licensed patch(1) variant has been added and is installed
1612 as bsdpatch, being the GNU version the default patch.
1613 To inverse the logic and use the BSD-licensed one as default,
1614 while having the GNU version installed as gnupatch, rebuild
1615 and install world with the WITH_BSD_PATCH knob set.
1618 Due to the use of the new -l option to install(1) during build
1619 and install, you must take care not to directly set the INSTALL
1620 make variable in your /etc/make.conf, /etc/src.conf, or on the
1621 command line. If you wish to use the -C flag for all installs
1622 you may be able to add INSTALL+=-C to /etc/make.conf or
1626 The install(1) option -M has changed meaning and now takes an
1627 argument that is a file or path to append logs to. In the
1628 unlikely event that -M was the last option on the command line
1629 and the command line contained at least two files and a target
1630 directory the first file will have logs appended to it. The -M
1631 option served little practical purpose in the last decade so its
1632 use is expected to be extremely rare.
1635 After switching to Clang as the default compiler some users of ZFS
1636 on i386 systems started to experience stack overflow kernel panics.
1637 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1640 GEOM_LABEL now mangles label names read from file system metadata.
1641 Mangling affect labels containing spaces, non-printable characters,
1642 '%' or '"'. Device names in /etc/fstab and other places may need to
1646 By default, only the 10 most recent kernel dumps will be saved. To
1647 restore the previous behaviour (no limit on the number of kernel dumps
1648 stored in the dump directory) add the following line to /etc/rc.conf:
1653 With the addition of auditdistd(8), a new auditdistd user is now
1654 required during installworld. "mergemaster -p" can be used to
1655 add the user prior to installworld, as documented in the handbook.
1658 The sin6_scope_id member variable in struct sockaddr_in6 is now
1659 filled by the kernel before passing the structure to the userland via
1660 sysctl or routing socket. This means the KAME-specific embedded scope
1661 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1662 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1663 __FreeBSD_version is bumped to 1000025.
1666 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1667 This means that the world and kernel will be compiled with clang
1668 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1669 and /usr/bin/cpp. To disable this behavior and revert to building
1670 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1671 of current may need to bootstrap WITHOUT_CLANG first if the clang
1672 build fails (its compatibility window doesn't extend to the 9 stable
1676 The IPFIREWALL_FORWARD kernel option has been removed. Its
1677 functionality now turned on by default.
1680 The ZERO_COPY_SOCKET kernel option has been removed and
1681 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1682 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1683 mechanism which is not safe and may result in kernel crashes.
1684 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1685 driver supports disposeable external page sized mbuf storage.
1686 Proper replacements for both zero-copy mechanisms are under
1687 consideration and will eventually lead to complete removal
1688 of the two kernel options.
1691 The IPv4 network stack has been converted to network byte
1692 order. The following modules need to be recompiled together
1693 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1694 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1697 Support for non-MPSAFE filesystems was removed from VFS. The
1698 VFS_VERSION was bumped, all filesystem modules shall be
1702 All the non-MPSAFE filesystems have been disconnected from
1703 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1704 portalfs, smbfs, xfs.
1707 The interface cloning API and ABI has changed. The following
1708 modules need to be recompiled together with kernel:
1709 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1710 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1711 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1714 The sdhci driver was split in two parts: sdhci (generic SD Host
1715 Controller logic) and sdhci_pci (actual hardware driver).
1716 No kernel config modifications are required, but if you
1717 load sdhc as a module you must switch to sdhci_pci instead.
1720 Import the FUSE kernel and userland support into base system.
1723 The GNU sort(1) program has been removed since the BSD-licensed
1724 sort(1) has been the default for quite some time and no serious
1725 problems have been reported. The corresponding WITH_GNU_SORT
1729 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1730 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1734 The net80211(4) ABI has been changed to allow for improved driver
1735 PS-POLL and power-save support. All wireless drivers need to be
1736 recompiled to work with the new kernel.
1739 The random(4) support for the VIA hardware random number
1740 generator (`PADLOCK') is no longer enabled unconditionally.
1741 Add the padlock_rng device in the custom kernel config if
1742 needed. The GENERIC kernels on i386 and amd64 do include the
1743 device, so the change only affects the custom kernel
1747 The pf(4) packet filter ABI has been changed. pfctl(8) and
1748 snmp_pf module need to be recompiled to work with new kernel.
1751 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1752 to -HEAD. Pools that have empty_bpobj in active state can not be
1753 imported read-write with ZFS implementations that do not support
1754 this feature. For more information read the zpool-features(5)
1758 The sparc64 ZFS loader has been changed to no longer try to auto-
1759 detect ZFS providers based on diskN aliases but now requires these
1760 to be explicitly listed in the OFW boot-device environment variable.
1763 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1764 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1765 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1768 The following sysctls and tunables have been renamed for consistency
1769 with other variables:
1770 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1771 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1774 The sort utility has been replaced with BSD sort. For now, GNU sort
1775 is also available as "gnusort" or the default can be set back to
1776 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1777 installed as "bsdsort".
1780 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1781 Starting with this version the old system of ZFS pool versioning
1782 is superseded by "feature flags". This concept enables forward
1783 compatibility against certain future changes in functionality of ZFS
1784 pools. The first read-only compatible "feature flag" for ZFS pools
1785 is named "com.delphix:async_destroy". For more information
1786 read the new zpool-features(5) manual page.
1787 Please refer to the "ZFS notes" section of this file for information
1788 on upgrading boot ZFS pools.
1791 The malloc(3) implementation embedded in libc now uses sources imported
1792 as contrib/jemalloc. The most disruptive API change is to
1793 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1794 delete it prior to installworld, and optionally re-create it using the
1795 new format after rebooting. See malloc.conf(5) for details
1796 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1800 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1801 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1802 now spelled mips. This is to aid compatibility with third-party
1803 software that expects this naming scheme in uname(3). Little-endian
1804 settings are unchanged. If you are updating a big-endian mips64 machine
1805 from before this change, you may need to set MACHINE_ARCH=mips64 in
1806 your environment before the new build system will recognize your machine.
1809 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1813 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1814 nullfs(5) did not pass through all behaviours to the underlying layer,
1815 as a result if we bound to a socket on the lower layer we could connect
1816 only to the lower path; if we bound to the upper layer we could connect
1817 only to the upper path. The new behavior is one can connect to both the
1818 lower and the upper paths regardless what layer path one binds to.
1821 The getifaddrs upgrade path broken with 20111215 has been restored.
1822 If you have upgraded in between 20111215 and 20120209 you need to
1823 recompile libc again with your kernel. You still need to recompile
1824 world to be able to configure CARP but this restriction already
1825 comes from 20111215.
1828 The set_rcvar() function has been removed from /etc/rc.subr. All
1829 base and ports rc.d scripts have been updated, so if you have a
1830 port installed with a script in /usr/local/etc/rc.d you can either
1831 hand-edit the rcvar= line, or reinstall the port.
1833 An easy way to handle the mass-update of /etc/rc.d:
1834 rm /etc/rc.d/* && mergemaster -i
1837 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1838 on the current CPU and prevents other threads from running.
1839 This behavior can be reverted using the kern.stop_scheduler_on_panic
1841 The new behavior can be incompatible with kern.sync_on_panic.
1844 The carp(4) facility has been changed significantly. Configuration
1845 of the CARP protocol via ifconfig(8) has changed, as well as format
1846 of CARP events submitted to devd(8) has changed. See manual pages
1847 for more information. The arpbalance feature of carp(4) is currently
1848 not supported anymore.
1850 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1851 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1852 need to be recompiled.
1855 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1859 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1860 explicitely support non-MPSAFE filesystems.
1861 It is on by default for all supported platform at this present
1865 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1866 i386 and pc98 GENERIC kernel configuration files.
1869 sysinstall has been removed
1872 The stable/9 branch created in subversion. This corresponds to the
1873 RELENG_9 branch in CVS.
1879 Avoid using make -j when upgrading. While generally safe, there are
1880 sometimes problems using -j to upgrade. If your upgrade fails with
1881 -j, please try again without -j. From time to time in the past there
1882 have been problems using -j with buildworld and/or installworld. This
1883 is especially true when upgrading between "distant" versions (eg one
1884 that cross a major release boundary or several minor releases, or when
1885 several months have passed on the -current branch).
1887 Sometimes, obscure build problems are the result of environment
1888 poisoning. This can happen because the make utility reads its
1889 environment when searching for values for global variables. To run
1890 your build attempts in an "environmental clean room", prefix all make
1891 commands with 'env -i '. See the env(1) manual page for more details.
1893 When upgrading from one major version to another it is generally best to
1894 upgrade to the latest code in the currently installed branch first, then
1895 do an upgrade to the new branch. This is the best-tested upgrade path,
1896 and has the highest probability of being successful. Please try this
1897 approach if you encounter problems with a major version upgrade. Since
1898 the stable 4.x branch point, one has generally been able to upgrade from
1899 anywhere in the most recent stable branch to head / current (or even the
1900 last couple of stable branches). See the top of this file when there's
1903 When upgrading a live system, having a root shell around before
1904 installing anything can help undo problems. Not having a root shell
1905 around can lead to problems if pam has changed too much from your
1906 starting point to allow continued authentication after the upgrade.
1908 This file should be read as a log of events. When a later event changes
1909 information of a prior event, the prior event should not be deleted.
1910 Instead, a pointer to the entry with the new information should be
1911 placed in the old entry. Readers of this file should also sanity check
1912 older entries before relying on them blindly. Authors of new entries
1913 should write them with this in mind.
1917 When upgrading the boot ZFS pool to a new version, always follow
1920 1.) recompile and reinstall the ZFS boot loader and boot block
1921 (this is part of "make buildworld" and "make installworld")
1923 2.) update the ZFS boot block on your boot drive
1925 The following example updates the ZFS boot block on the first
1926 partition (freebsd-boot) of a GPT partitioned drive ada0:
1927 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1929 Non-boot pools do not need these updates.
1933 If you are updating from a prior version of FreeBSD (even one just
1934 a few days old), you should follow this procedure. It is the most
1935 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1937 make kernel-toolchain
1938 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1939 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1941 To test a kernel once
1942 ---------------------
1943 If you just want to boot a kernel once (because you are not sure
1944 if it works, or if you want to boot a known bad kernel to provide
1945 debugging information) run
1946 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1947 nextboot -k testkernel
1949 To rebuild everything and install it on the current system.
1950 -----------------------------------------------------------
1951 # Note: sometimes if you are running current you gotta do more than
1952 # is listed here if you are upgrading from a really old current.
1954 <make sure you have good level 0 dumps>
1956 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1957 make installkernel KERNCONF=YOUR_KERNEL_HERE
1959 <reboot in single user> [3]
1966 To cross-install current onto a separate partition
1967 --------------------------------------------------
1968 # In this approach we use a separate partition to hold
1969 # current's root, 'usr', and 'var' directories. A partition
1970 # holding "/", "/usr" and "/var" should be about 2GB in
1973 <make sure you have good level 0 dumps>
1976 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1977 <maybe newfs current's root partition>
1978 <mount current's root partition on directory ${CURRENT_ROOT}>
1979 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1980 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1981 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1982 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1983 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1984 <reboot into current>
1985 <do a "native" rebuild/install as described in the previous section>
1986 <maybe install compatibility libraries from ports/misc/compat*>
1990 To upgrade in-place from stable to current
1991 ----------------------------------------------
1992 <make sure you have good level 0 dumps>
1994 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1996 <reboot in single user> [3]
2003 Make sure that you've read the UPDATING file to understand the
2004 tweaks to various things you need. At this point in the life
2005 cycle of current, things change often and you are on your own
2006 to cope. The defaults can also change, so please read ALL of
2007 the UPDATING entries.
2009 Also, if you are tracking -current, you must be subscribed to
2010 freebsd-current@freebsd.org. Make sure that before you update
2011 your sources that you have read and understood all the recent
2012 messages there. If in doubt, please track -stable which has
2013 much fewer pitfalls.
2015 [1] If you have third party modules, such as vmware, you
2016 should disable them at this point so they don't crash your
2019 [3] From the bootblocks, boot -s, and then do
2024 adjkerntz -i # if CMOS is wall time
2025 Also, when doing a major release upgrade, it is required that
2026 you boot into single user mode to do the installworld.
2028 [4] Note: This step is non-optional. Failure to do this step
2029 can result in a significant reduction in the functionality of the
2030 system. Attempting to do it by hand is not recommended and those
2031 that pursue this avenue should read this file carefully, as well
2032 as the archives of freebsd-current and freebsd-hackers mailing lists
2033 for potential gotchas. The -U option is also useful to consider.
2034 See mergemaster(8) for more information.
2036 [5] Usually this step is a no-op. However, from time to time
2037 you may need to do this if you get unknown user in the following
2038 step. It never hurts to do it all the time. You may need to
2039 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2040 install) after the buildworld before this step if you last updated
2041 from current before 20130425 or from -stable before 20130430.
2043 [6] This only deletes old files and directories. Old libraries
2044 can be deleted by "make delete-old-libs", but you have to make
2045 sure that no program is using those libraries anymore.
2047 [8] In order to have a kernel that can run the 4.x binaries needed to
2048 do an installworld, you must include the COMPAT_FREEBSD4 option in
2049 your kernel. Failure to do so may leave you with a system that is
2050 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2051 required to run the 5.x binaries on more recent kernels. And so on
2052 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2054 Make sure that you merge any new devices from GENERIC since the
2055 last time you updated your kernel config file.
2057 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2058 "?=" instead of the "=" assignment operator, so that buildworld can
2059 override the CPUTYPE if it needs to.
2061 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2062 not on the command line, or in /etc/make.conf. buildworld will
2063 warn if it is improperly defined.
2066 This file contains a list, in reverse chronological order, of major
2067 breakages in tracking -current. It is not guaranteed to be a complete
2068 list of such breakages, and only contains entries since September 23, 2011.
2069 If you need to see UPDATING entries from before that date, you will need
2070 to fetch an UPDATING file from an older FreeBSD release.
2072 Copyright information:
2074 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2076 Redistribution, publication, translation and use, with or without
2077 modification, in full or in part, in any form or format of this
2078 document are permitted without further permission from the author.
2080 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2081 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2082 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2083 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2084 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2085 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2086 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2087 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2088 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2089 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2090 POSSIBILITY OF SUCH DAMAGE.
2092 Contact Warner Losh if you have any questions about your use of