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 On i386, pmtimer has been removed. It's functionality has been folded
56 into apm. It was a nop on ACPI. Users may need to remove it from kernel
60 The use of RSS hash from the network card aka flowid has been
61 disabled by default for lagg(4) as it's currently incompatible with
62 the lacp and loadbalance protocols.
64 This can be re-enabled by setting the following in loader.conf:
65 net.link.lagg.default_use_flowid="1"
68 The SW_WATCHDOG option is no longer necessary to enable the
69 hardclock-based software watchdog if no hardware watchdog is
70 configured. As before, SW_WATCHDOG will cause the software
71 watchdog to be enabled even if a hardware watchdog is configured.
74 r326887 fixes the issue described in the 20171214 UPDATING entry.
75 r326888 flips the switch back to building GELI support always.
78 r362593 broke ZFS + GELI support for reasons unknown. However,
79 it also broke ZFS support generally, so GELI has been turned off
80 by default as the lesser evil in r326857. If you boot off ZFS and/or
81 GELI, it might not be a good time to update.
84 PowerPC users must update loader(8) by rebuilding world before
85 installing a new kernel, as the protocol connecting them has
86 changed. Without the update, loader metadata will not be passed
87 successfully to the kernel and users will have to enter their
88 root partition at the kernel mountroot prompt to continue booting.
89 Newer versions of loader can boot old kernels without issue.
92 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
93 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
94 to WITH/OUT_LOADER_GELI.
97 The naive and non-compliant support of posix_fallocate(2) in ZFS
98 has been removed as of r325320. The system call now returns EINVAL
99 when used on a ZFS file. Although the new behavior complies with the
100 standard, some consumers are not prepared to cope with it.
101 One known victim is lld prior to r325420.
104 Building in a FreeBSD src checkout will automatically create object
105 directories now rather than store files in the current directory if
106 'make obj' was not ran. Calling 'make obj' is no longer necessary.
107 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
108 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
112 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
113 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
114 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
115 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
116 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
117 The UNIFIED_OBJDIR option is a transitional feature that will be
118 removed for 12.0 release; please migrate to the new format for any
119 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
120 than hardcoding paths.
123 The native-xtools target no longer installs the files by default to the
124 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
125 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
128 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
129 options are changing from controlling the build if defined / undefined
130 to controlling the build with explicit 'yes' or 'no' values. They will
131 shift to WITH/WITHOUT options to match other options in the system.
134 libstand has turned into a private library for sys/boot use only.
135 It is no longer supported as a public interface outside of sys/boot.
138 The arm port has split armv6 into armv6 and armv7. armv7 is now
139 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
140 and are running a kernel from before r324363, you will need to add
141 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
144 When building multiple kernels using KERNCONF, non-existent KERNCONF
145 files will produce an error and buildkernel will fail. Previously
146 missing KERNCONF files silently failed giving no indication as to
147 why, only to subsequently discover during installkernel that the
148 desired kernel was never built in the first place.
151 The default serial number format for CTL LUNs has changed. This will
152 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
153 or iSCSI clients care about their LUNs' serial numbers. Users who
154 require serial number stability should hardcode serial numbers in
158 For 32-bit arm compiled for hard-float support, soft-floating point
159 binaries now always get their shared libraries from
160 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
161 /usr/libsoft also existed). Only users with a hard-float ld.so, but
162 soft-float everything else should be affected.
165 The geli password typed at boot is now hidden. To restore the previous
166 behavior, see geli(8) for configuration options.
169 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
170 sysctl values. Minor nit, but requires a rebuild of both world/kernel
174 "make check" behavior (made in ^/head@r295380) has been changed to
175 execute from a limited sandbox, as opposed to executing from
179 - The "beforecheck" and "aftercheck" targets are now specified.
180 - ${CHECKDIR} (added in commit noted above) has been removed.
181 - Legacy behavior can be enabled by setting
182 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
184 If the limited sandbox mode is enabled, "make check" will execute
185 "make distribution", then install, execute the tests, and clean up the
186 sandbox if successful.
188 The "make distribution" and "make install" targets are typically run as
189 root to set appropriate permissions and ownership at installation time.
190 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
191 environment if executing "make check" with limited sandbox mode using
192 an unprivileged user.
195 Since the switch to GPT disk labels, fsck for UFS/FFS has been
196 unable to automatically find alternate superblocks. As of r322297,
197 the information needed to find alternate superblocks has been
198 moved to the end of the area reserved for the boot block.
199 Filesystems created with a newfs of this vintage or later
200 will create the recovery information. If you have a filesystem
201 created prior to this change and wish to have a recovery block
202 created for your filesystem, you can do so by running fsck in
203 forground mode (i.e., do not use the -p or -y options). As it
204 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
205 to which you should answer yes.
208 As of r321665, an NFSv4 server configuration that services
209 Kerberos mounts or clients that do not support the uid/gid in
210 owner/owner_group string capability, must explicitly enable
211 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
212 machine's /etc/rc.conf file.
215 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
216 Please see the 20141231 entry below for information about prerequisites
217 and upgrading, if you are not already using clang 3.5.0 or higher.
220 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
221 r-commands (rlogin, rsh, etc.) to be built with the base system.
224 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
225 a very major ABI incompatible change, so users of FreeBSD/powerpc must
226 be careful when performing source upgrades. It is best to run
227 'make installworld' from an alternate root system, either a live
228 CD/memory stick, or a temporary root partition. Additionally, all ports
229 must be recompiled. powerpc64 is largely unaffected, except in the case
230 of 32-bit compatibility. All 32-bit binaries will be affected.
233 Forward compatibility for the "ino64" project have been committed. This
234 will allow most new binaries to run on older kernels in a limited
235 fashion. This prevents many of the common foot-shooting actions in the
236 upgrade as well as the limited ability to roll back the kernel across
237 the ino64 upgrade. Complicated use cases may not work properly, though
238 enough simpler ones work to allow recovery in most situations.
241 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
242 if you require the GPL compiler.
245 The internal ABI used for communication between the NFS kernel modules
246 was changed by r320085, so __FreeBSD_version was bumped to
247 ensure all the NFS related modules are updated together.
250 The ABI of struct event was changed by extending the data
251 member to 64bit and adding ext fields. For upgrade, same
252 precautions as for the entry 20170523 "ino64" must be
256 The GNU roff toolchain has been removed from base. To render manpages
257 which are not supported by mandoc(1), man(1) can fallback on GNU roff
258 from ports (and recommends to install it).
259 To render roff(7) documents, consider using GNU roff from ports or the
260 heirloom doctools roff toolchain from ports via pkg install groff or
261 via pkg install heirloom-doctools.
264 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
265 smaller runtime footprint builds. This is useful for embedded systems
266 which only require one chipset support.
268 If you load it as a module, make sure this is in /boot/loader.conf:
272 This will load the HAL, all chip/RF backends and if_ath_pci.
273 If you have if_ath_pci in /boot/loader.conf, ensure it is after
274 if_ath or it will not load any HAL chipset support.
276 If you want to selectively load things (eg on ye cheape ARM/MIPS
277 platforms where RAM is at a premium) you should:
280 * load the chip modules in question
281 * load ath_rate, ath_dfs
283 * load if_ath_pci and/or if_ath_ahb depending upon your particular
284 bus bind type - this is where probe/attach is done.
286 For further comments/feedback, poke adrian@ .
289 The "ino64" 64-bit inode project has been committed, which extends
290 a number of types to 64 bits. Upgrading in place requires care and
291 adherence to the documented upgrade procedure.
293 If using a custom kernel configuration ensure that the
294 COMPAT_FREEBSD11 option is included (as during the upgrade the
295 system will be running the ino64 kernel with the existing world).
297 For the safest in-place upgrade begin by removing previous build
298 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
299 full procedure documented below under the heading "To rebuild
300 everything and install it on the current system." Specifically,
301 a reboot is required after installing the new kernel before
305 The NATM framework including the en(4), fatm(4), hatm(4), and
306 patm(4) devices has been removed. Consumers should plan a
307 migration before the end-of-life date for FreeBSD 11.
310 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
311 diff has not been implemented, if those are needed a newer version of
312 GNU diff is available via the diffutils package under the gdiff name.
315 As of r316810 for ipfilter, keep frags is no longer assumed when
316 keep state is specified in a rule. r316810 aligns ipfilter with
317 documentation in man pages separating keep frags from keep state.
318 This allows keep state to be specified without forcing keep frags
319 and allows keep frags to be specified independently of keep state.
320 To maintain previous behaviour, also specify keep frags with
321 keep state (as documented in ipf.conf.5).
324 arm64 builds now use the base system LLD 4.0.0 linker by default,
325 instead of requiring that the aarch64-binutils port or package be
326 installed. To continue using aarch64-binutils, set
327 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
330 The UDP optimization in entry 20160818 that added the sysctl
331 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
332 packets will no longer be treated as L3 broadcast packets.
335 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
336 use any explicitly assigned loopback address available in the jail
337 instead of using the first assigned address of the jail.
340 The ctl.ko module no longer implements the iSCSI target frontend:
341 cfiscsi.ko does instead.
343 If building cfiscsi.ko as a kernel module, the module can be loaded
344 via one of the following methods:
345 - `cfiscsi_load="YES"` in loader.conf(5).
346 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
347 - ctladm(8)/ctld(8), when compiled with iSCSI support
348 (`WITH_ISCSI=yes` in src.conf(5))
350 Please see cfiscsi(4) for more details.
353 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
354 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
355 same source (previously, the dependency of mmcsd.ko on mmc.ko was
356 missing, but mmcsd.ko now will refuse to load if it is incompatible
360 The syntax of ipfw(8) named states was changed to avoid ambiguity.
361 If you have used named states in the firewall rules, you need to modify
362 them after installworld and before rebooting. Now named states must
363 be prefixed with colon.
366 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
367 removed as the userland we provide cannot use them. The KMS version
368 (sys/dev/drm2) supports the same hardware.
371 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
372 Please see the 20141231 entry below for information about prerequisites
373 and upgrading, if you are not already using clang 3.5.0 or higher.
376 The code that provides support for ZFS .zfs/ directory functionality
377 has been reimplemented. It's not possible now to create a snapshot
378 by mkdir under .zfs/snapshot/. That should be the only user visible
382 EISA bus support has been removed. The WITH_EISA option is no longer
386 MCA bus support has been removed.
389 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
390 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
393 The EM_MULTIQUEUE kernel configuration option is deprecated now that
394 the em(4) driver conforms to iflib specifications.
397 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
398 IFLIB. If you have a custom kernel configuration that excludes em(4)
399 but you use igb(4), you need to re-add em(4) to your custom configuration.
402 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
403 Please see the 20141231 entry below for information about prerequisites
404 and upgrading, if you are not already using clang 3.5.0 or higher.
407 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
408 Please see the 20141231 entry below for information about prerequisites
409 and upgrading, if you are not already using clang 3.5.0 or higher.
412 The layout of the pmap structure has changed for powerpc to put the pmap
413 statistics at the front for all CPU variations. libkvm(3) and all tools
414 that link against it need to be recompiled.
417 isl(4) and cyapa(4) drivers now require a new driver,
418 chromebook_platform(4), to work properly on Chromebook-class hardware.
419 On other types of hardware the drivers may need to be configured using
420 device hints. Please see the corresponding manual pages for details.
423 The urtwn(4) driver was merged into rtwn(4) and now consists of
424 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
426 Also, firmware for RTL8188CE was renamed due to possible name
427 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
430 GNU rcs has been removed from base. It is available as packages:
431 - rcs: Latest GPLv3 GNU rcs version.
432 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
436 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
437 modules now requires that the kernel configuration contain the
438 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
441 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
442 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
445 Relocatable object files with the extension of .So have been renamed
446 to use an extension of .pico instead. The purpose of this change is
447 to avoid a name clash with shared libraries on case-insensitive file
448 systems. On those file systems, foo.So is the same file as foo.so.
451 GNU rcs has been turned off by default. It can (temporarily) be built
452 again by adding WITH_RCS knob in src.conf.
453 Otherwise, GNU rcs is available from packages:
454 - rcs: Latest GPLv3 GNU rcs version.
455 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
458 The backup_uses_rcs functionality has been removed from rc.subr.
461 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
462 two separate components, QUEUE_MACRO_DEBUG_TRACE and
463 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
464 QUEUE_MACRO_DEBUG behavior.
467 r304787 changed some ioctl interfaces between the iSCSI userspace
468 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
469 rebuilt to work with new kernels. __FreeBSD_version has been bumped
473 The UDP receive code has been updated to only treat incoming UDP
474 packets that were addressed to an L2 broadcast address as L3
475 broadcast packets. It is not expected that this will affect any
476 standards-conforming UDP application. The new behaviour can be
477 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
481 Remove the openbsd_poll system call.
482 __FreeBSD_version has been bumped because of this.
485 The libc stub for the pipe(2) system call has been replaced with
486 a wrapper that calls the pipe2(2) system call and the pipe(2)
487 system call is now only implemented by the kernels that include
488 "options COMPAT_FREEBSD10" in their config file (this is the
489 default). Users should ensure that this option is enabled in
490 their kernel or upgrade userspace to r302092 before upgrading their
494 CAM will now strip leading spaces from SCSI disks' serial numbers.
495 This will affect users who create UFS filesystems on SCSI disks using
496 those disk's diskid device nodes. For example, if /etc/fstab
497 previously contained a line like
498 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
499 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
500 transforms like gmirror may also be affected. ZFS users should
504 The bitstring(3) API has been updated with new functionality and
505 improved performance. But it is binary-incompatible with the old API.
506 Objects built with the new headers may not be linked against objects
507 built with the old headers.
510 The brk and sbrk functions have been removed from libc on arm64.
511 Binutils from ports has been updated to not link to these
512 functions and should be updated to the latest version before
513 installing a new libc.
516 The armv6 port now defaults to hard float ABI. Limited support
517 for running both hardfloat and soft float on the same system
518 is available using the libraries installed with -DWITH_LIBSOFT.
519 This has only been tested as an upgrade path for installworld
520 and packages may fail or need manual intervention to run. New
521 packages will be needed.
523 To update an existing self-hosted armv6hf system, you must add
524 TARGET_ARCH=armv6 on the make command line for both the build
525 and the install steps.
528 Kernel modules compiled outside of a kernel build now default to
529 installing to /boot/modules instead of /boot/kernel. Many kernel
530 modules built this way (such as those in ports) already overrode
531 KMODDIR explicitly to install into /boot/modules. However,
532 manually building and installing a module from /sys/modules will
533 now install to /boot/modules instead of /boot/kernel.
536 The CAM I/O scheduler has been committed to the kernel. There should be
537 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
538 list of known rogues that claim support for this but actually corrupt
539 data is believed to be complete, be on the lookout for data
540 corruption. The known rogue list is believed to be complete:
542 o Crucial MX100, M550 drives with MU01 firmware.
543 o Micron M510 and M550 drives with MU01 firmware.
544 o Micron M500 prior to MU07 firmware
545 o Samsung 830, 840, and 850 all firmwares
546 o FCCT M500 all firmwares
548 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
549 with working NCQ TRIM. For Micron branded drives, see your sales rep for
550 updated firmware. Black listed drives will work correctly because these
551 drives work correctly so long as no NCQ TRIMs are sent to them. Given
552 this list is the same as found in Linux, it's believed there are no
553 other rogues in the market place. All other models from the above
556 To be safe, if you are at all concerned, you can quirk each of your
557 drives to prevent NCQ from being sent by setting:
558 kern.cam.ada.X.quirks="0x2"
559 in loader.conf. If the drive requires the 4k sector quirk, set the
563 The FAST_DEPEND build option has been removed and its functionality is
564 now the one true way. The old mkdep(1) style of 'make depend' has
565 been removed. See 20160311 for further details.
568 Resource range types have grown from unsigned long to uintmax_t. All
569 drivers, and anything using libdevinfo, need to be recompiled.
572 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
573 builds. It no longer runs mkdep(1) during 'make depend', and the
574 'make depend' stage can safely be skipped now as it is auto ran
575 when building 'make all' and will generate all SRCS and DPSRCS before
576 building anything else. Dependencies are gathered at compile time with
577 -MF flags kept in separate .depend files per object file. Users should
578 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
582 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
583 kernel modules. Therefore, if you load any kernel modules at boot time,
584 please install the boot loaders after you install the kernel, but before
588 make kernel KERNCONF=YOUR_KERNEL_HERE
589 make -C sys/boot install
590 <reboot in single user>
592 Then follow the usual steps, described in the General Notes section,
596 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
597 see the 20141231 entry below for information about prerequisites and
598 upgrading, if you are not already using clang 3.5.0 or higher.
601 The AIO subsystem is now a standard part of the kernel. The
602 VFS_AIO kernel option and aio.ko kernel module have been removed.
603 Due to stability concerns, asynchronous I/O requests are only
604 permitted on sockets and raw disks by default. To enable
605 asynchronous I/O requests on all file types, set the
606 vfs.aio.enable_unsafe sysctl to a non-zero value.
609 The ELF object manipulation tool objcopy is now provided by the
610 ELF Tool Chain project rather than by GNU binutils. It should be a
611 drop-in replacement, with the addition of arm64 support. The
612 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
613 to obtain the GNU version if necessary.
616 Building ZFS pools on top of zvols is prohibited by default. That
617 feature has never worked safely; it's always been prone to deadlocks.
618 Using a zvol as the backing store for a VM guest's virtual disk will
619 still work, even if the guest is using ZFS. Legacy behavior can be
620 restored by setting vfs.zfs.vol.recursive=1.
623 The NONE and HPN patches has been removed from OpenSSH. They are
624 still available in the security/openssh-portable port.
627 With the addition of ypldap(8), a new _ypldap user is now required
628 during installworld. "mergemaster -p" can be used to add the user
629 prior to installworld, as documented in the handbook.
632 The tftp loader (pxeboot) now uses the option root-path directive. As a
633 consequence it no longer looks for a pxeboot.4th file on the tftp
634 server. Instead it uses the regular /boot infrastructure as with the
638 The code to start recording plug and play data into the modules has
639 been committed. While the old tools will properly build a new kernel,
640 a number of warnings about "unknown metadata record 4" will be produced
641 for an older kldxref. To avoid such warnings, make sure to rebuild
642 the kernel toolchain (or world). Make sure that you have r292078 or
643 later when trying to build 292077 or later before rebuilding.
646 Debug data files are now built by default with 'make buildworld' and
647 installed with 'make installworld'. This facilitates debugging but
648 requires more disk space both during the build and for the installed
649 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
653 r291527 changed the internal interface between the nfsd.ko and
654 nfscommon.ko modules. As such, they must both be upgraded to-gether.
655 __FreeBSD_version has been bumped because of this.
658 Add support for unicode collation strings leads to a change of
659 order of files listed by ls(1) for example. To get back to the old
660 behaviour, set LC_COLLATE environment variable to "C".
662 Databases administrators will need to reindex their databases given
663 collation results will be different.
665 Due to a bug in install(1) it is recommended to remove the ancient
666 locales before running make installworld.
668 rm -rf /usr/share/locale/*
671 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
672 libcrypto.so.7 or libssl.so.7 must be recompiled.
675 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
676 Kernel modules isp_2400_multi and isp_2500_multi were removed and
677 should be replaced with isp_2400 and isp_2500 modules respectively.
680 The build previously allowed using 'make -n' to not recurse into
681 sub-directories while showing what commands would be executed, and
682 'make -n -n' to recursively show commands. Now 'make -n' will recurse
683 and 'make -N' will not.
686 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
687 and etcupdate will now use this file. A custom sendmail.cf is now
688 updated via this mechanism rather than via installworld. If you had
689 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
690 want to remove the exclusion or change it to "always install".
691 /etc/mail/sendmail.cf is now managed the same way regardless of
692 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
693 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
696 Compatibility shims for legacy ATA device names have been removed.
697 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
698 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
699 environment variables, /dev/ad* and /dev/ar* symbolic links.
702 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
703 Please see the 20141231 entry below for information about prerequisites
704 and upgrading, if you are not already using clang 3.5.0 or higher.
707 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
708 and renamed from .symbols to .debug. This reduces the size requirements
709 on the boot partition or file system and provides consistency with
710 userland debug files.
712 When using the supported kernel installation method the
713 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
714 as is done with /boot/kernel.
716 Developers wishing to maintain the historical behavior of installing
717 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
720 The wireless drivers had undergone changes that remove the 'parent
721 interface' from the ifconfig -l output. The rc.d network scripts
722 used to check presence of a parent interface in the list, so old
723 scripts would fail to start wireless networking. Thus, etcupdate(3)
724 or mergemaster(8) run is required after kernel update, to update your
725 rc.d scripts in /etc.
728 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
729 These configurations are now automatically interpreted as
730 'scrub fragment reassemble'.
733 Kernel-loadable modules for the random(4) device are back. To use
734 them, the kernel must have
737 options RANDOM_LOADABLE
739 kldload(8) can then be used to load random_fortuna.ko
740 or random_yarrow.ko. Please note that due to the indirect
741 function calls that the loadable modules need to provide,
742 the build-in variants will be slightly more efficient.
744 The random(4) kernel option RANDOM_DUMMY has been retired due to
745 unpopularity. It was not all that useful anyway.
748 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
749 Control over building the ELF Tool Chain tools is now provided by
750 the WITHOUT_TOOLCHAIN knob.
753 The polarity of Pulse Per Second (PPS) capture events with the
754 uart(4) driver has been corrected. Prior to this change the PPS
755 "assert" event corresponded to the trailing edge of a positive PPS
756 pulse and the "clear" event was the leading edge of the next pulse.
758 As the width of a PPS pulse in a typical GPS receiver is on the
759 order of 1 millisecond, most users will not notice any significant
760 difference with this change.
762 Anyone who has compensated for the historical polarity reversal by
763 configuring a negative offset equal to the pulse width will need to
764 remove that workaround.
767 The default group assigned to /dev/dri entries has been changed
768 from 'wheel' to 'video' with the id of '44'. If you want to have
769 access to the dri devices please add yourself to the video group
772 # pw groupmod video -m $USER
775 The menu.rc and loader.rc files will now be replaced during
776 upgrades. Please migrate local changes to menu.rc.local and
777 loader.rc.local instead.
780 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
781 strings and strip have been removed. The src.conf(5) knob
782 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
785 As ZFS requires more kernel stack pages than is the default on some
786 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
787 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
789 Please consider using 'options KSTACK_PAGES=X' where X is greater
790 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
793 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
794 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
795 default, i.e., they will not contain "::". For example, instead
796 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
797 to have a more specific match, such as different map entries for
798 IPv6:0:0 vs IPv6:0. This change requires that configuration
799 data (including maps, files, classes, custom ruleset, etc.) must
800 use the same format, so make certain such configuration data is
801 upgrading. As a very simple check search for patterns like
802 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
803 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
804 the cf option UseCompressedIPv6Addresses.
807 The default kernel entropy-processing algorithm is now
808 Fortuna, replacing Yarrow.
810 Assuming you have 'device random' in your kernel config
811 file, the configurations allow a kernel option to override
812 this default. You may choose *ONE* of:
814 options RANDOM_YARROW # Legacy /dev/random algorithm.
815 options RANDOM_DUMMY # Blocking-only driver.
817 If you have neither, you get Fortuna. For most people,
818 read no further, Fortuna will give a /dev/random that works
819 like it always used to, and the difference will be irrelevant.
821 If you remove 'device random', you get *NO* kernel-processed
822 entropy at all. This may be acceptable to folks building
823 embedded systems, but has complications. Carry on reading,
824 and it is assumed you know what you need.
826 *PLEASE* read random(4) and random(9) if you are in the
827 habit of tweaking kernel configs, and/or if you are a member
828 of the embedded community, wanting specific and not-usual
829 behaviour from your security subsystems.
831 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
832 random', you will NOT have a functioning /dev/random, and
833 many cryptographic features will not work, including SSH.
834 You may also find strange behaviour from the random(3) set
835 of library functions, in particular sranddev(3), srandomdev(3)
836 and arc4random(3). The reason for this is that the KERN_ARND
837 sysctl only returns entropy if it thinks it has some to
838 share, and with RANDOM_DUMMY or no 'device random' this
842 An additional fix for the issue described in the 20150614 sendmail
843 entry below has been committed in revision 284717.
846 FreeBSD's old make (fmake) has been removed from the system. It is
847 available as the devel/fmake port or via pkg install fmake.
850 The fix for the issue described in the 20150614 sendmail entry
851 below has been committed in revision 284436. The work
852 around described in that entry is no longer needed unless the
853 default setting is overridden by a confDH_PARAMETERS configuration
854 setting of '5' or pointing to a 512 bit DH parameter file.
857 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
858 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
859 and devel/kyua to version 0.20+ and adjust any calling code to work
860 with Kyuafile and kyua.
863 The import of openssl to address the FreeBSD-SA-15:10.openssl
864 security advisory includes a change which rejects handshakes
865 with DH parameters below 768 bits. sendmail releases prior
866 to 8.15.2 (not yet released), defaulted to a 512 bit
867 DH parameter setting for client connections. To work around
868 this interoperability, sendmail can be configured to use a
869 2048 bit DH parameter by:
871 1. Edit /etc/mail/`hostname`.mc
872 2. If a setting for confDH_PARAMETERS does not exist or
873 exists and is set to a string beginning with '5',
875 3. If a setting for confDH_PARAMETERS exists and is set to
876 a file path, create a new file with:
877 openssl dhparam -out /path/to/file 2048
878 4. Rebuild the .cf file:
879 cd /etc/mail/; make; make install
881 cd /etc/mail/; make restart
883 A sendmail patch is coming, at which time this file will be
887 Generation of legacy formatted entries have been disabled by default
888 in pwd_mkdb(8), as all base system consumers of the legacy formatted
889 entries were converted to use the new format by default when the new,
890 machine independent format have been added and supported since FreeBSD
893 Please see the pwd_mkdb(8) manual page for further details.
896 Clang and llvm have been upgraded to 3.6.1 release. Please see the
897 20141231 entry below for information about prerequisites and upgrading,
898 if you are not already using 3.5.0 or higher.
901 TI platform code switched to using vendor DTS files and this update
902 may break existing systems running on Beaglebone, Beaglebone Black,
905 - dtb files should be regenerated/reinstalled. Filenames are the
906 same but content is different now
907 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
908 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
909 addressing scheme is now pin 25 on /dev/gpioc3.
910 - Pandaboard: /etc/ttys should be updated, serial console device is
911 now /dev/ttyu2, not /dev/ttyu0
914 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
915 If you need the GNU extension from groff soelim(1), install groff
916 from package: pkg install groff, or via ports: textproc/groff.
919 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
920 defined in symlink(7); previously symlinks were silently ignored.
923 The const qualifier has been removed from iconv(3) to comply with
924 POSIX. The ports tree is aware of this from r384038 onwards.
927 Libraries specified by LIBADD in Makefiles must have a corresponding
928 DPADD_<lib> variable to ensure correct dependencies. This is now
929 enforced in src.libnames.mk.
932 From legacy ata(4) driver was removed support for SATA controllers
933 supported by more functional drivers ahci(4), siis(4) and mvs(4).
934 Kernel modules ataahci and ataadaptec were removed completely,
935 replaced by ahci and mvs modules respectively.
938 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
939 the 20141231 entry below for information about prerequisites and
940 upgrading, if you are not already using 3.5.0 or higher.
943 The 32-bit PowerPC kernel has been changed to a position-independent
944 executable. This can only be booted with a version of loader(8)
945 newer than January 31, 2015, so make sure to update both world and
946 kernel before rebooting.
949 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
950 but before r278950, the RNG was not seeded properly. Immediately
951 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
952 ssh keys or openssl keys) that were generated w/ a kernel from that
953 range. This does not affect programs that directly used /dev/random
954 or /dev/urandom. All userland uses of arc4random(3) are affected.
957 The autofs(4) ABI was changed in order to restore binary compatibility
958 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
962 The powerpc64 kernel has been changed to a position-independent
963 executable. This can only be booted with a new version of loader(8),
964 so make sure to update both world and kernel before rebooting.
967 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
968 only release, no new features have been added. Please see the 20141231
969 entry below for information about prerequisites and upgrading, if you
970 are not already using 3.5.0.
973 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
974 taken from the ELF Tool Chain project rather than GNU binutils. They
975 should be drop-in replacements, with the addition of arm64 support.
976 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
977 binutils tools, if necessary. See 20150805 for updated information.
980 The default Unbound configuration now enables remote control
981 using a local socket. Users who have already enabled the
982 local_unbound service should regenerate their configuration
983 by running "service local_unbound setup" as root.
986 The GNU texinfo and GNU info pages have been removed.
987 To be able to view GNU info pages please install texinfo from ports.
990 Clang, llvm and lldb have been upgraded to 3.5.0 release.
992 As of this release, a prerequisite for building clang, llvm and lldb is
993 a C++11 capable compiler and C++11 standard library. This means that to
994 be able to successfully build the cross-tools stage of buildworld, with
995 clang as the bootstrap compiler, your system compiler or cross compiler
996 should either be clang 3.3 or later, or gcc 4.8 or later, and your
997 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1000 On any standard FreeBSD 10.x or 11.x installation, where clang and
1001 libc++ are on by default (that is, on x86 or arm), this should work out
1004 On 9.x installations where clang is enabled by default, e.g. on x86 and
1005 powerpc, libc++ will not be enabled by default, so libc++ should be
1006 built (with clang) and installed first. If both clang and libc++ are
1007 missing, build clang first, then use it to build libc++.
1009 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1010 the instructions for 9.x above.
1012 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1013 default, and do not build clang.
1015 Many embedded systems are resource constrained, and will not be able to
1016 build clang in a reasonable time, or in some cases at all. In those
1017 cases, cross building bootable systems on amd64 is a workaround.
1019 This new version of clang introduces a number of new warnings, of which
1020 the following are most likely to appear:
1024 This warns in two cases, for both C and C++:
1025 * When the code is trying to take the absolute value of an unsigned
1026 quantity, which is effectively a no-op, and almost never what was
1027 intended. The code should be fixed, if at all possible. If you are
1028 sure that the unsigned quantity can be safely cast to signed, without
1029 loss of information or undefined behavior, you can add an explicit
1030 cast, or disable the warning.
1032 * When the code is trying to take an absolute value, but the called
1033 abs() variant is for the wrong type, which can lead to truncation.
1034 If you want to disable the warning instead of fixing the code, please
1035 make sure that truncation will not occur, or it might lead to unwanted
1038 -Wtautological-undefined-compare and
1039 -Wundefined-bool-conversion
1041 These warn when C++ code is trying to compare 'this' against NULL, while
1042 'this' should never be NULL in well-defined C++ code. However, there is
1043 some legacy (pre C++11) code out there, which actively abuses this
1044 feature, which was less strictly defined in previous C++ versions.
1046 Squid and openjdk do this, for example. The warning can be turned off
1047 for C++98 and earlier, but compiling the code in C++11 mode might result
1048 in unexpected behavior; for example, the parts of the program that are
1049 unreachable could be optimized away.
1052 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1053 kernel sources have been removed. The .h files remain, since some
1054 utilities include them. This will need to be fixed later.
1055 If "mount -t oldnfs ..." is attempted, it will fail.
1056 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1057 the utilities will report errors.
1060 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1061 directories to top level SUBDIR variable when their parent
1062 directory is included in LOCAL_DIRS. Users with build systems with
1063 such hierarchies and without SUBDIR entries in the parent
1064 directory Makefiles should add them or add the directories to
1068 faith(4) and faithd(8) have been removed from the base system. Faith
1069 has been obsolete for a very long time.
1072 vt(4), the new console driver, is enabled by default. It brings
1073 support for Unicode and double-width characters, as well as
1074 support for UEFI and integration with the KMS kernel video
1077 You may need to update your console settings in /etc/rc.conf,
1078 most probably the keymap. During boot, /etc/rc.d/syscons will
1079 indicate what you need to do.
1081 vt(4) still has issues and lacks some features compared to
1082 syscons(4). See the wiki for up-to-date information:
1083 https://wiki.freebsd.org/Newcons
1085 If you want to keep using syscons(4), you can do so by adding
1086 the following line to /boot/loader.conf:
1090 pjdfstest has been integrated into kyua as an opt-in test suite.
1091 Please see share/doc/pjdfstest/README for more details on how to
1095 gperf has been removed from the base system for architectures
1096 that use clang. Ports that require gperf will obtain it from the
1100 pjdfstest has been moved from tools/regression/pjdfstest to
1104 At svn r271982, The default linux compat kernel ABI has been adjusted
1105 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1106 update. If you wish to continue using the linux-f10 compat ports,
1107 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1108 encouraged to update their linux-compat packages to linux-c6 during
1109 their next update cycle.
1112 The ofwfb driver, used to provide a graphics console on PowerPC when
1113 using vt(4), no longer allows mmap() of all physical memory. This
1114 will prevent Xorg on PowerPC with some ATI graphics cards from
1115 initializing properly unless x11-servers/xorg-server is updated to
1119 The xdev targets have been converted to using TARGET and
1120 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1123 The default unbound configuration has been modified to address
1124 issues with reverse lookups on networks that use private
1125 address ranges. If you use the local_unbound service, run
1126 "service local_unbound setup" as root to regenerate your
1127 configuration, then "service local_unbound reload" to load the
1131 The GNU texinfo and GNU info pages are not built and installed
1132 anymore, WITH_INFO knob has been added to allow to built and install
1134 UPDATE: see 20150102 entry on texinfo's removal
1137 The GNU readline library is now an INTERNALLIB - that is, it is
1138 statically linked into consumers (GDB and variants) in the base
1139 system, and the shared library is no longer installed. The
1140 devel/readline port is available for third party software that
1144 The Itanium architecture (ia64) has been removed from the list of
1145 known architectures. This is the first step in the removal of the
1149 Commit r268115 has added NFSv4.1 server support, merged from
1150 projects/nfsv4.1-server. Since this includes changes to the
1151 internal interfaces between the NFS related modules, a full
1152 build of the kernel and modules will be necessary.
1153 __FreeBSD_version has been bumped.
1156 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1157 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1158 which differs from the behaviour controlled by this knob.)
1161 Maximal length of the serial number in CTL was increased from 16 to
1162 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1163 and ctld, need to be rebuilt to work with a new kernel.
1166 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1167 1 respectively to match the upstream numbers. They were out of
1168 sync because, when they were originally added to FreeBSD, the
1169 upstream versions were not respected. These libraries are private
1170 and not yet built by default, so renumbering them should be a
1171 non-issue. However, unclean source trees will yield broken test
1172 programs once the operator executes "make delete-old-libs" after a
1173 "make installworld".
1175 Additionally, the atf-sh binary was made private by moving it into
1176 /usr/libexec/. Already-built shell test programs will keep the
1177 path to the old binary so they will break after "make delete-old"
1180 If you are using WITH_TESTS=yes (not the default), wipe the object
1181 tree and rebuild from scratch to prevent spurious test failures.
1182 This is only needed once: the misnumbered libraries and misplaced
1183 binaries have been added to OptionalObsoleteFiles.inc so they will
1184 be removed during a clean upgrade.
1187 Clang and llvm have been upgraded to 3.4.1 release.
1190 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1191 be removed to avoid issues in the future (and has been added to
1195 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1196 past, it affected all builds that used the bsd.*.mk files. The old
1197 behavior was a bug, but people may have relied upon it. To get this
1198 behavior back, you can .include /etc/src.conf from /etc/make.conf
1199 (which is still global and isn't changed). This also changes the
1200 behavior of incremental builds inside the tree of individual
1201 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1202 Although this has survived make universe and some upgrade scenarios,
1203 other upgrade scenarios may have broken. At least one form of
1204 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1205 as well... In cases where MAKESYSPATH isn't working with this
1206 setting, you'll need to set it to the full path to your tree.
1208 One side effect of all this cleaning up is that bsd.compiler.mk
1209 is no longer implicitly included by bsd.own.mk. If you wish to
1210 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1214 The lindev device has been removed since /dev/full has been made a
1215 standard device. __FreeBSD_version has been bumped.
1218 The knob WITHOUT_VI was added to the base system, which controls
1219 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1220 in order to reorder files share/termcap and didn't build ex(1) as a
1221 build tool, so building/installing with WITH_VI is highly advised for
1222 build hosts for older releases.
1224 This issue has been fixed in stable/9 and stable/10 in r277022 and
1225 r276991, respectively.
1228 The YES_HESIOD knob has been removed. It has been obsolete for
1229 a decade. Please move to using WITH_HESIOD instead or your builds
1230 will silently lack HESIOD.
1233 The uart(4) driver has been changed with respect to its handling
1234 of the low-level console. Previously the uart(4) driver prevented
1235 any process from changing the baudrate or the CLOCAL and HUPCL
1236 control flags. By removing the restrictions, operators can make
1237 changes to the serial console port without having to reboot.
1238 However, when getty(8) is started on the serial device that is
1239 associated with the low-level console, a misconfigured terminal
1240 line in /etc/ttys will now have a real impact.
1241 Before upgrading the kernel, make sure that /etc/ttys has the
1242 serial console device configured as 3wire without baudrate to
1243 preserve the previous behaviour. E.g:
1244 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1247 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1248 to improve performance. To re-enable it, if needed, run rpcbind
1249 with command line option -W.
1252 Switched back to the GPL dtc compiler due to updates in the upstream
1253 dts files not being supported by the BSDL dtc compiler. You will need
1254 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1255 may result while building dtb files during a kernel build if you fail
1256 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1259 Clang and llvm have been upgraded to 3.4 release.
1262 The nve(4) driver has been removed. Please use the nfe(4) driver
1263 for NVIDIA nForce MCP Ethernet adapters instead.
1266 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1267 This could cause certain C++ applications using shared libraries built
1268 against the previous version of libc++ to crash. The incompatibility
1269 has now been fixed, but any C++ applications or shared libraries built
1270 between r261283 and r261801 should be recompiled.
1273 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1274 capability mode support. Please note that enabling the feature in
1275 kernel is still highly recommended.
1278 OpenSSH is now built with sandbox support, and will use sandbox as
1279 the default privilege separation method. This requires Capsicum
1280 capability mode support in kernel.
1283 The libelf and libdwarf libraries have been updated to newer
1284 versions from upstream. Shared library version numbers for
1285 these two libraries were bumped. Any ports or binaries
1286 requiring these two libraries should be recompiled.
1287 __FreeBSD_version is bumped to 1100006.
1290 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1291 instead of providing an explicit one, this would prevent such
1292 Makefile from providing its own Kyuafile in the future during
1293 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1294 intervention is needed to clean an objdir if you use NO_CLEAN:
1295 # find /usr/obj -name Kyuafile | xargs rm -f
1298 The behavior of gss_pseudo_random() for the krb5 mechanism
1299 has changed, for applications requesting a longer random string
1300 than produced by the underlying enctype's pseudo-random() function.
1301 In particular, the random string produced from a session key of
1302 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1303 be different at the 17th octet and later, after this change.
1304 The counter used in the PRF+ construction is now encoded as a
1305 big-endian integer in accordance with RFC 4402.
1306 __FreeBSD_version is bumped to 1100004.
1309 The WITHOUT_ATF build knob has been removed and its functionality
1310 has been subsumed into the more generic WITHOUT_TESTS. If you were
1311 using the former to disable the build of the ATF libraries, you
1312 should change your settings to use the latter.
1315 The default version of mtree is nmtree which is obtained from
1316 NetBSD. The output is generally the same, but may vary
1317 slightly. If you found you need identical output adding
1318 "-F freebsd9" to the command line should do the trick. For the
1319 time being, the old mtree is available as fmtree.
1322 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1323 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1324 1.1.4_8 and verify bsdyml not linked in, before running "make
1326 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1328 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1331 The stable/10 branch has been created in subversion from head
1335 The rc.d/jail script has been updated to support jail(8)
1336 configuration file. The "jail_<jname>_*" rc.conf(5) variables
1337 for per-jail configuration are automatically converted to
1338 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
1339 This is transparently backward compatible. See below about some
1340 incompatibilities and rc.conf(5) manual page for more details.
1342 These variables are now deprecated in favor of jail(8) configuration
1343 file. One can use "rc.d/jail config <jname>" command to generate
1344 a jail(8) configuration file in /var/run/jail.<jname>.conf without
1345 running the jail(8) utility. The default pathname of the
1346 configuration file is /etc/jail.conf and can be specified by
1347 using $jail_conf or $jail_<jname>_conf variables.
1349 Please note that jail_devfs_ruleset accepts an integer at
1350 this moment. Please consider to rewrite the ruleset name
1354 BIND has been removed from the base system. If all you need
1355 is a local resolver, simply enable and start the local_unbound
1356 service instead. Otherwise, several versions of BIND are
1357 available in the ports tree. The dns/bind99 port is one example.
1359 With this change, nslookup(1) and dig(1) are no longer in the base
1360 system. Users should instead use host(1) and drill(1) which are
1361 in the base system. Alternatively, nslookup and dig can
1362 be obtained by installing the dns/bind-tools port.
1365 With the addition of unbound(8), a new unbound user is now
1366 required during installworld. "mergemaster -p" can be used to
1367 add the user prior to installworld, as documented in the handbook.
1370 OpenSSH is now built with DNSSEC support, and will by default
1371 silently trust signed SSHFP records. This can be controlled with
1372 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1373 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1376 The GNU Compiler Collection and C++ standard library (libstdc++)
1377 are no longer built by default on platforms where clang is the system
1378 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1379 options in src.conf.
1382 The PROCDESC kernel option is now part of the GENERIC kernel
1383 configuration and is required for the rwhod(8) to work.
1384 If you are using custom kernel configuration, you should include
1388 The API and ABI related to the Capsicum framework was modified
1389 in backward incompatible way. The userland libraries and programs
1390 have to be recompiled to work with the new kernel. This includes the
1391 following libraries and programs, but the whole buildworld is
1392 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1393 kdump, procstat, rwho, rwhod, uniq.
1396 AES-NI intrinsic support has been added to gcc. The AES-NI module
1397 has been updated to use this support. A new gcc is required to build
1398 the aesni module on both i386 and amd64.
1401 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1402 Thus "device padlock_rng" and "device rdrand_rng" should be
1403 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1406 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1407 enables just the iconv* functionality and is now on by default.
1408 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1409 compatibility. Set WITHOUT_ICONV to build the old way.
1410 If you have been using WITH_ICONV before, you will very likely
1411 need to turn on WITH_LIBICONV_COMPAT.
1414 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1415 Illumos origin, including ZFS. If you have INVARIANTS in your
1416 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1418 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1419 locks if WITNESS option was set. Because that generated a lot of
1420 witness(9) reports and all of them were believed to be false
1421 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1422 can be used to achieve the previous behavior.
1425 Timer values in IPv6 data structures now use time_uptime instead
1426 of time_second. Although this is not a user-visible functional
1427 change, userland utilities which directly use them---ndp(8),
1428 rtadvd(8), and rtsold(8) in the base system---need to be updated
1429 to r253970 or later.
1432 find -delete can now delete the pathnames given as arguments,
1433 instead of only files found below them or if the pathname did
1434 not contain any slashes. Formerly, the following error message
1437 find: -delete: <path>: relative path potentially not safe
1439 Deleting the pathnames given as arguments can be prevented
1440 without error messages using -mindepth 1 or by changing
1441 directory and passing "." as argument to find. This works in the
1442 old as well as the new version of find.
1445 Behavior of devfs rules path matching has been changed.
1446 Pattern is now always matched against fully qualified devfs
1447 path and slash characters must be explicitly matched by
1448 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1449 subdirectories must be reviewed.
1452 The default ARM ABI has changed to the ARM EABI. The old ABI is
1453 incompatible with the ARM EABI and all programs and modules will
1454 need to be rebuilt to work with a new kernel.
1456 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1458 NOTE: Support for the old ABI will be removed in the future and
1459 users are advised to upgrade.
1462 pkg_install has been disconnected from the build if you really need it
1463 you should add WITH_PKGTOOLS in your src.conf(5).
1466 Most of network statistics structures were changed to be able
1467 keep 64-bits counters. Thus all tools, that work with networking
1468 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1471 Fix a bug that allowed a tracing process (e.g. gdb) to write
1472 to a memory-mapped file in the traced process's address space
1473 even if neither the traced process nor the tracing process had
1474 write access to that file.
1477 CVS has been removed from the base system. An exact copy
1478 of the code is available from the devel/cvs port.
1481 Some people report the following error after the switch to bmake:
1483 make: illegal option -- J
1484 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1486 *** [buildworld] Error code 2
1488 this likely due to an old instance of make in
1489 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1490 which src/Makefile will use that blindly, if it exists, so if
1491 you see the above error:
1493 rm -rf `make -V MAKEPATH`
1498 Use bmake by default.
1499 Whereas before one could choose to build with bmake via
1500 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1501 make. The goal is to remove these knobs for 10-RELEASE.
1503 It is worth noting that bmake (like gmake) treats the command
1504 line as the unit of failure, rather than statements within the
1505 command line. Thus '(cd some/where && dosomething)' is safer
1506 than 'cd some/where; dosomething'. The '()' allows consistent
1507 behavior in parallel build.
1510 Fix a bug that allows NFS clients to issue READDIR on files.
1513 The WITHOUT_IDEA option has been removed because
1514 the IDEA patent expired.
1517 The sysctl which controls TRIM support under ZFS has been renamed
1518 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1522 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1523 rather than creating it's own in the temporary directory in
1524 order allow access to bootstrapped versions of tools such as
1525 install and mtree. When upgrading from version of FreeBSD where
1526 the install command does not support -l, you will need to
1527 install a new mergemaster command if mergemaster -p is required.
1528 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1532 Legacy ATA stack, disabled and replaced by new CAM-based one since
1533 FreeBSD 9.0, completely removed from the sources. Kernel modules
1534 atadisk and atapi*, user-level tools atacontrol and burncd are
1535 removed. Kernel option `options ATA_CAM` is now permanently enabled
1539 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1540 and socketpair(2). Software, in particular Kerberos, may
1541 automatically detect and use these during building. The resulting
1542 binaries will not work on older kernels.
1545 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1546 information, see the respective 20130304 entry).
1549 Recent commits to callout(9) changed the size of struct callout,
1550 so the KBI is probably heavily disturbed. Also, some functions
1551 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1552 by macros. Every kernel module using it won't load, so rebuild
1555 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1556 but does not initialize by default (because of the new CTL_DISABLE
1557 option) to save memory. To re-enable it, remove the CTL_DISABLE
1558 option from the kernel config file or set kern.cam.ctl.disable=0
1559 in /boot/loader.conf.
1562 The ctl device has been disabled in GENERIC for i386 and amd64.
1563 This was done due to the extra memory being allocated at system
1564 initialisation time by the ctl driver which was only used if
1565 a CAM target device was created. This makes a FreeBSD system
1566 unusable on 128MB or less of RAM.
1569 A new compression method (lz4) has been merged to -HEAD. Please
1570 refer to zpool-features(7) for more information.
1572 Please refer to the "ZFS notes" section of this file for information
1573 on upgrading boot ZFS pools.
1576 A BSD-licensed patch(1) variant has been added and is installed
1577 as bsdpatch, being the GNU version the default patch.
1578 To inverse the logic and use the BSD-licensed one as default,
1579 while having the GNU version installed as gnupatch, rebuild
1580 and install world with the WITH_BSD_PATCH knob set.
1583 Due to the use of the new -l option to install(1) during build
1584 and install, you must take care not to directly set the INSTALL
1585 make variable in your /etc/make.conf, /etc/src.conf, or on the
1586 command line. If you wish to use the -C flag for all installs
1587 you may be able to add INSTALL+=-C to /etc/make.conf or
1591 The install(1) option -M has changed meaning and now takes an
1592 argument that is a file or path to append logs to. In the
1593 unlikely event that -M was the last option on the command line
1594 and the command line contained at least two files and a target
1595 directory the first file will have logs appended to it. The -M
1596 option served little practical purpose in the last decade so its
1597 use is expected to be extremely rare.
1600 After switching to Clang as the default compiler some users of ZFS
1601 on i386 systems started to experience stack overflow kernel panics.
1602 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1605 GEOM_LABEL now mangles label names read from file system metadata.
1606 Mangling affect labels containing spaces, non-printable characters,
1607 '%' or '"'. Device names in /etc/fstab and other places may need to
1611 By default, only the 10 most recent kernel dumps will be saved. To
1612 restore the previous behaviour (no limit on the number of kernel dumps
1613 stored in the dump directory) add the following line to /etc/rc.conf:
1618 With the addition of auditdistd(8), a new auditdistd user is now
1619 required during installworld. "mergemaster -p" can be used to
1620 add the user prior to installworld, as documented in the handbook.
1623 The sin6_scope_id member variable in struct sockaddr_in6 is now
1624 filled by the kernel before passing the structure to the userland via
1625 sysctl or routing socket. This means the KAME-specific embedded scope
1626 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1627 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1628 __FreeBSD_version is bumped to 1000025.
1631 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1632 This means that the world and kernel will be compiled with clang
1633 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1634 and /usr/bin/cpp. To disable this behavior and revert to building
1635 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1636 of current may need to bootstrap WITHOUT_CLANG first if the clang
1637 build fails (its compatibility window doesn't extend to the 9 stable
1641 The IPFIREWALL_FORWARD kernel option has been removed. Its
1642 functionality now turned on by default.
1645 The ZERO_COPY_SOCKET kernel option has been removed and
1646 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1647 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1648 mechanism which is not safe and may result in kernel crashes.
1649 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1650 driver supports disposeable external page sized mbuf storage.
1651 Proper replacements for both zero-copy mechanisms are under
1652 consideration and will eventually lead to complete removal
1653 of the two kernel options.
1656 The IPv4 network stack has been converted to network byte
1657 order. The following modules need to be recompiled together
1658 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1659 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1662 Support for non-MPSAFE filesystems was removed from VFS. The
1663 VFS_VERSION was bumped, all filesystem modules shall be
1667 All the non-MPSAFE filesystems have been disconnected from
1668 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1669 portalfs, smbfs, xfs.
1672 The interface cloning API and ABI has changed. The following
1673 modules need to be recompiled together with kernel:
1674 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1675 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1676 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1679 The sdhci driver was split in two parts: sdhci (generic SD Host
1680 Controller logic) and sdhci_pci (actual hardware driver).
1681 No kernel config modifications are required, but if you
1682 load sdhc as a module you must switch to sdhci_pci instead.
1685 Import the FUSE kernel and userland support into base system.
1688 The GNU sort(1) program has been removed since the BSD-licensed
1689 sort(1) has been the default for quite some time and no serious
1690 problems have been reported. The corresponding WITH_GNU_SORT
1694 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1695 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1699 The net80211(4) ABI has been changed to allow for improved driver
1700 PS-POLL and power-save support. All wireless drivers need to be
1701 recompiled to work with the new kernel.
1704 The random(4) support for the VIA hardware random number
1705 generator (`PADLOCK') is no longer enabled unconditionally.
1706 Add the padlock_rng device in the custom kernel config if
1707 needed. The GENERIC kernels on i386 and amd64 do include the
1708 device, so the change only affects the custom kernel
1712 The pf(4) packet filter ABI has been changed. pfctl(8) and
1713 snmp_pf module need to be recompiled to work with new kernel.
1716 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1717 to -HEAD. Pools that have empty_bpobj in active state can not be
1718 imported read-write with ZFS implementations that do not support
1719 this feature. For more information read the zpool-features(5)
1723 The sparc64 ZFS loader has been changed to no longer try to auto-
1724 detect ZFS providers based on diskN aliases but now requires these
1725 to be explicitly listed in the OFW boot-device environment variable.
1728 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1729 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1730 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1733 The following sysctls and tunables have been renamed for consistency
1734 with other variables:
1735 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1736 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1739 The sort utility has been replaced with BSD sort. For now, GNU sort
1740 is also available as "gnusort" or the default can be set back to
1741 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1742 installed as "bsdsort".
1745 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1746 Starting with this version the old system of ZFS pool versioning
1747 is superseded by "feature flags". This concept enables forward
1748 compatibility against certain future changes in functionality of ZFS
1749 pools. The first read-only compatible "feature flag" for ZFS pools
1750 is named "com.delphix:async_destroy". For more information
1751 read the new zpool-features(5) manual page.
1752 Please refer to the "ZFS notes" section of this file for information
1753 on upgrading boot ZFS pools.
1756 The malloc(3) implementation embedded in libc now uses sources imported
1757 as contrib/jemalloc. The most disruptive API change is to
1758 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1759 delete it prior to installworld, and optionally re-create it using the
1760 new format after rebooting. See malloc.conf(5) for details
1761 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1765 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1766 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1767 now spelled mips. This is to aid compatibility with third-party
1768 software that expects this naming scheme in uname(3). Little-endian
1769 settings are unchanged. If you are updating a big-endian mips64 machine
1770 from before this change, you may need to set MACHINE_ARCH=mips64 in
1771 your environment before the new build system will recognize your machine.
1774 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1778 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1779 nullfs(5) did not pass through all behaviours to the underlying layer,
1780 as a result if we bound to a socket on the lower layer we could connect
1781 only to the lower path; if we bound to the upper layer we could connect
1782 only to the upper path. The new behavior is one can connect to both the
1783 lower and the upper paths regardless what layer path one binds to.
1786 The getifaddrs upgrade path broken with 20111215 has been restored.
1787 If you have upgraded in between 20111215 and 20120209 you need to
1788 recompile libc again with your kernel. You still need to recompile
1789 world to be able to configure CARP but this restriction already
1790 comes from 20111215.
1793 The set_rcvar() function has been removed from /etc/rc.subr. All
1794 base and ports rc.d scripts have been updated, so if you have a
1795 port installed with a script in /usr/local/etc/rc.d you can either
1796 hand-edit the rcvar= line, or reinstall the port.
1798 An easy way to handle the mass-update of /etc/rc.d:
1799 rm /etc/rc.d/* && mergemaster -i
1802 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1803 on the current CPU and prevents other threads from running.
1804 This behavior can be reverted using the kern.stop_scheduler_on_panic
1806 The new behavior can be incompatible with kern.sync_on_panic.
1809 The carp(4) facility has been changed significantly. Configuration
1810 of the CARP protocol via ifconfig(8) has changed, as well as format
1811 of CARP events submitted to devd(8) has changed. See manual pages
1812 for more information. The arpbalance feature of carp(4) is currently
1813 not supported anymore.
1815 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1816 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1817 need to be recompiled.
1820 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1824 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1825 explicitely support non-MPSAFE filesystems.
1826 It is on by default for all supported platform at this present
1830 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1831 i386 and pc98 GENERIC kernel configuration files.
1834 sysinstall has been removed
1837 The stable/9 branch created in subversion. This corresponds to the
1838 RELENG_9 branch in CVS.
1844 Avoid using make -j when upgrading. While generally safe, there are
1845 sometimes problems using -j to upgrade. If your upgrade fails with
1846 -j, please try again without -j. From time to time in the past there
1847 have been problems using -j with buildworld and/or installworld. This
1848 is especially true when upgrading between "distant" versions (eg one
1849 that cross a major release boundary or several minor releases, or when
1850 several months have passed on the -current branch).
1852 Sometimes, obscure build problems are the result of environment
1853 poisoning. This can happen because the make utility reads its
1854 environment when searching for values for global variables. To run
1855 your build attempts in an "environmental clean room", prefix all make
1856 commands with 'env -i '. See the env(1) manual page for more details.
1858 When upgrading from one major version to another it is generally best to
1859 upgrade to the latest code in the currently installed branch first, then
1860 do an upgrade to the new branch. This is the best-tested upgrade path,
1861 and has the highest probability of being successful. Please try this
1862 approach if you encounter problems with a major version upgrade. Since
1863 the stable 4.x branch point, one has generally been able to upgade from
1864 anywhere in the most recent stable branch to head / current (or even the
1865 last couple of stable branches). See the top of this file when there's
1868 When upgrading a live system, having a root shell around before
1869 installing anything can help undo problems. Not having a root shell
1870 around can lead to problems if pam has changed too much from your
1871 starting point to allow continued authentication after the upgrade.
1873 This file should be read as a log of events. When a later event changes
1874 information of a prior event, the prior event should not be deleted.
1875 Instead, a pointer to the entry with the new information should be
1876 placed in the old entry. Readers of this file should also sanity check
1877 older entries before relying on them blindly. Authors of new entries
1878 should write them with this in mind.
1882 When upgrading the boot ZFS pool to a new version, always follow
1885 1.) recompile and reinstall the ZFS boot loader and boot block
1886 (this is part of "make buildworld" and "make installworld")
1888 2.) update the ZFS boot block on your boot drive
1890 The following example updates the ZFS boot block on the first
1891 partition (freebsd-boot) of a GPT partitioned drive ada0:
1892 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1894 Non-boot pools do not need these updates.
1898 If you are updating from a prior version of FreeBSD (even one just
1899 a few days old), you should follow this procedure. It is the most
1900 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1902 make kernel-toolchain
1903 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1904 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1906 To test a kernel once
1907 ---------------------
1908 If you just want to boot a kernel once (because you are not sure
1909 if it works, or if you want to boot a known bad kernel to provide
1910 debugging information) run
1911 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1912 nextboot -k testkernel
1914 To rebuild everything and install it on the current system.
1915 -----------------------------------------------------------
1916 # Note: sometimes if you are running current you gotta do more than
1917 # is listed here if you are upgrading from a really old current.
1919 <make sure you have good level 0 dumps>
1921 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1922 make installkernel KERNCONF=YOUR_KERNEL_HERE
1924 <reboot in single user> [3]
1931 To cross-install current onto a separate partition
1932 --------------------------------------------------
1933 # In this approach we use a separate partition to hold
1934 # current's root, 'usr', and 'var' directories. A partition
1935 # holding "/", "/usr" and "/var" should be about 2GB in
1938 <make sure you have good level 0 dumps>
1941 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1942 <maybe newfs current's root partition>
1943 <mount current's root partition on directory ${CURRENT_ROOT}>
1944 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1945 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1946 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1947 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1948 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1949 <reboot into current>
1950 <do a "native" rebuild/install as described in the previous section>
1951 <maybe install compatibility libraries from ports/misc/compat*>
1955 To upgrade in-place from stable to current
1956 ----------------------------------------------
1957 <make sure you have good level 0 dumps>
1959 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1961 <reboot in single user> [3]
1968 Make sure that you've read the UPDATING file to understand the
1969 tweaks to various things you need. At this point in the life
1970 cycle of current, things change often and you are on your own
1971 to cope. The defaults can also change, so please read ALL of
1972 the UPDATING entries.
1974 Also, if you are tracking -current, you must be subscribed to
1975 freebsd-current@freebsd.org. Make sure that before you update
1976 your sources that you have read and understood all the recent
1977 messages there. If in doubt, please track -stable which has
1978 much fewer pitfalls.
1980 [1] If you have third party modules, such as vmware, you
1981 should disable them at this point so they don't crash your
1984 [3] From the bootblocks, boot -s, and then do
1989 adjkerntz -i # if CMOS is wall time
1990 Also, when doing a major release upgrade, it is required that
1991 you boot into single user mode to do the installworld.
1993 [4] Note: This step is non-optional. Failure to do this step
1994 can result in a significant reduction in the functionality of the
1995 system. Attempting to do it by hand is not recommended and those
1996 that pursue this avenue should read this file carefully, as well
1997 as the archives of freebsd-current and freebsd-hackers mailing lists
1998 for potential gotchas. The -U option is also useful to consider.
1999 See mergemaster(8) for more information.
2001 [5] Usually this step is a noop. However, from time to time
2002 you may need to do this if you get unknown user in the following
2003 step. It never hurts to do it all the time. You may need to
2004 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2005 install) after the buildworld before this step if you last updated
2006 from current before 20130425 or from -stable before 20130430.
2008 [6] This only deletes old files and directories. Old libraries
2009 can be deleted by "make delete-old-libs", but you have to make
2010 sure that no program is using those libraries anymore.
2012 [8] In order to have a kernel that can run the 4.x binaries needed to
2013 do an installworld, you must include the COMPAT_FREEBSD4 option in
2014 your kernel. Failure to do so may leave you with a system that is
2015 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2016 required to run the 5.x binaries on more recent kernels. And so on
2017 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2019 Make sure that you merge any new devices from GENERIC since the
2020 last time you updated your kernel config file.
2022 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2023 "?=" instead of the "=" assignment operator, so that buildworld can
2024 override the CPUTYPE if it needs to.
2026 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2027 not on the command line, or in /etc/make.conf. buildworld will
2028 warn if it is improperly defined.
2031 This file contains a list, in reverse chronological order, of major
2032 breakages in tracking -current. It is not guaranteed to be a complete
2033 list of such breakages, and only contains entries since September 23, 2011.
2034 If you need to see UPDATING entries from before that date, you will need
2035 to fetch an UPDATING file from an older FreeBSD release.
2037 Copyright information:
2039 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2041 Redistribution, publication, translation and use, with or without
2042 modification, in full or in part, in any form or format of this
2043 document are permitted without further permission from the author.
2045 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2046 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2047 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2048 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2049 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2050 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2051 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2052 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2053 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2054 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2055 POSSIBILITY OF SUCH DAMAGE.
2057 Contact Warner Losh if you have any questions about your use of