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 u-boot based arm64 UEFI systems: the UEFI loader(8), loader.efi,
56 should be updated in conjunction with installing a new kernel after
57 r330868. The kernel, after this revision, will be more lenient when
58 mapping addresses for UEFI Runtime Services and this may result in a
59 kernel panic without the corresponding loader(8) update. If you have a
60 recent kernel, you can do a installkernel / installworld and then reboot
61 as there's no recent syscall changes. If you have an older kernel and/or
62 a 11.x system, the following sequence is safe:
65 % sudo make installkernel
70 % sudo make installworld
73 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
74 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
75 Co-existance for the transition period will come shortly. Booting is a
76 complex environment and test coverage for Lua-enabled loaders has been
77 thin, so it would be prudent to assume it might not work and make
78 provisions for backup boot methods.
81 devmatch functionality has been turned on in devd. It will automatically
82 load drivers for unattached devices. This may cause unexpected drivers to
83 be loaded. Please report any problems to current@ and imp@freebsd.org.
86 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
87 6.0.0. Please see the 20141231 entry below for information about
88 prerequisites and upgrading, if you are not already using clang 3.5.0
92 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
93 This means it is used to link the kernel and userland libraries and
94 executables, but is not yet installed as /usr/bin/ld by default.
96 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
97 WITHOUT_LLD_BOOTSTRAP=yes
100 On i386, pmtimer has been removed. Its functionality has been folded
101 into apm. It was a no-op on ACPI in current for a while now (but was still
102 needed on i386 in FreeBSD 11 and earlier). Users may need to remove it
103 from kernel config files.
106 The use of RSS hash from the network card aka flowid has been
107 disabled by default for lagg(4) as it's currently incompatible with
108 the lacp and loadbalance protocols.
110 This can be re-enabled by setting the following in loader.conf:
111 net.link.lagg.default_use_flowid="1"
114 The SW_WATCHDOG option is no longer necessary to enable the
115 hardclock-based software watchdog if no hardware watchdog is
116 configured. As before, SW_WATCHDOG will cause the software
117 watchdog to be enabled even if a hardware watchdog is configured.
120 r326887 fixes the issue described in the 20171214 UPDATING entry.
121 r326888 flips the switch back to building GELI support always.
124 r362593 broke ZFS + GELI support for reasons unknown. However,
125 it also broke ZFS support generally, so GELI has been turned off
126 by default as the lesser evil in r326857. If you boot off ZFS and/or
127 GELI, it might not be a good time to update.
130 PowerPC users must update loader(8) by rebuilding world before
131 installing a new kernel, as the protocol connecting them has
132 changed. Without the update, loader metadata will not be passed
133 successfully to the kernel and users will have to enter their
134 root partition at the kernel mountroot prompt to continue booting.
135 Newer versions of loader can boot old kernels without issue.
138 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
139 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
140 to WITH/OUT_LOADER_GELI.
143 The naive and non-compliant support of posix_fallocate(2) in ZFS
144 has been removed as of r325320. The system call now returns EINVAL
145 when used on a ZFS file. Although the new behavior complies with the
146 standard, some consumers are not prepared to cope with it.
147 One known victim is lld prior to r325420.
150 Building in a FreeBSD src checkout will automatically create object
151 directories now rather than store files in the current directory if
152 'make obj' was not ran. Calling 'make obj' is no longer necessary.
153 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
154 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
158 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
159 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
160 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
161 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
162 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
163 The UNIFIED_OBJDIR option is a transitional feature that will be
164 removed for 12.0 release; please migrate to the new format for any
165 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
166 than hardcoding paths.
169 The native-xtools target no longer installs the files by default to the
170 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
171 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
174 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
175 options are changing from controlling the build if defined / undefined
176 to controlling the build with explicit 'yes' or 'no' values. They will
177 shift to WITH/WITHOUT options to match other options in the system.
180 libstand has turned into a private library for sys/boot use only.
181 It is no longer supported as a public interface outside of sys/boot.
184 The arm port has split armv6 into armv6 and armv7. armv7 is now
185 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
186 and are running a kernel from before r324363, you will need to add
187 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
190 When building multiple kernels using KERNCONF, non-existent KERNCONF
191 files will produce an error and buildkernel will fail. Previously
192 missing KERNCONF files silently failed giving no indication as to
193 why, only to subsequently discover during installkernel that the
194 desired kernel was never built in the first place.
197 The default serial number format for CTL LUNs has changed. This will
198 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
199 or iSCSI clients care about their LUNs' serial numbers. Users who
200 require serial number stability should hardcode serial numbers in
204 For 32-bit arm compiled for hard-float support, soft-floating point
205 binaries now always get their shared libraries from
206 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
207 /usr/libsoft also existed). Only users with a hard-float ld.so, but
208 soft-float everything else should be affected.
211 The geli password typed at boot is now hidden. To restore the previous
212 behavior, see geli(8) for configuration options.
215 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
216 sysctl values. Minor nit, but requires a rebuild of both world/kernel
220 "make check" behavior (made in ^/head@r295380) has been changed to
221 execute from a limited sandbox, as opposed to executing from
225 - The "beforecheck" and "aftercheck" targets are now specified.
226 - ${CHECKDIR} (added in commit noted above) has been removed.
227 - Legacy behavior can be enabled by setting
228 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
230 If the limited sandbox mode is enabled, "make check" will execute
231 "make distribution", then install, execute the tests, and clean up the
232 sandbox if successful.
234 The "make distribution" and "make install" targets are typically run as
235 root to set appropriate permissions and ownership at installation time.
236 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
237 environment if executing "make check" with limited sandbox mode using
238 an unprivileged user.
241 Since the switch to GPT disk labels, fsck for UFS/FFS has been
242 unable to automatically find alternate superblocks. As of r322297,
243 the information needed to find alternate superblocks has been
244 moved to the end of the area reserved for the boot block.
245 Filesystems created with a newfs of this vintage or later
246 will create the recovery information. If you have a filesystem
247 created prior to this change and wish to have a recovery block
248 created for your filesystem, you can do so by running fsck in
249 foreground mode (i.e., do not use the -p or -y options). As it
250 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
251 to which you should answer yes.
254 As of r321665, an NFSv4 server configuration that services
255 Kerberos mounts or clients that do not support the uid/gid in
256 owner/owner_group string capability, must explicitly enable
257 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
258 machine's /etc/rc.conf file.
261 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
262 Please see the 20141231 entry below for information about prerequisites
263 and upgrading, if you are not already using clang 3.5.0 or higher.
266 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
267 r-commands (rlogin, rsh, etc.) to be built with the base system.
270 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
271 a very major ABI incompatible change, so users of FreeBSD/powerpc must
272 be careful when performing source upgrades. It is best to run
273 'make installworld' from an alternate root system, either a live
274 CD/memory stick, or a temporary root partition. Additionally, all ports
275 must be recompiled. powerpc64 is largely unaffected, except in the case
276 of 32-bit compatibility. All 32-bit binaries will be affected.
279 Forward compatibility for the "ino64" project have been committed. This
280 will allow most new binaries to run on older kernels in a limited
281 fashion. This prevents many of the common foot-shooting actions in the
282 upgrade as well as the limited ability to roll back the kernel across
283 the ino64 upgrade. Complicated use cases may not work properly, though
284 enough simpler ones work to allow recovery in most situations.
287 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
288 if you require the GPL compiler.
291 The internal ABI used for communication between the NFS kernel modules
292 was changed by r320085, so __FreeBSD_version was bumped to
293 ensure all the NFS related modules are updated together.
296 The ABI of struct event was changed by extending the data
297 member to 64bit and adding ext fields. For upgrade, same
298 precautions as for the entry 20170523 "ino64" must be
302 The GNU roff toolchain has been removed from base. To render manpages
303 which are not supported by mandoc(1), man(1) can fallback on GNU roff
304 from ports (and recommends to install it).
305 To render roff(7) documents, consider using GNU roff from ports or the
306 heirloom doctools roff toolchain from ports via pkg install groff or
307 via pkg install heirloom-doctools.
310 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
311 smaller runtime footprint builds. This is useful for embedded systems
312 which only require one chipset support.
314 If you load it as a module, make sure this is in /boot/loader.conf:
318 This will load the HAL, all chip/RF backends and if_ath_pci.
319 If you have if_ath_pci in /boot/loader.conf, ensure it is after
320 if_ath or it will not load any HAL chipset support.
322 If you want to selectively load things (eg on ye cheape ARM/MIPS
323 platforms where RAM is at a premium) you should:
326 * load the chip modules in question
327 * load ath_rate, ath_dfs
329 * load if_ath_pci and/or if_ath_ahb depending upon your particular
330 bus bind type - this is where probe/attach is done.
332 For further comments/feedback, poke adrian@ .
335 The "ino64" 64-bit inode project has been committed, which extends
336 a number of types to 64 bits. Upgrading in place requires care and
337 adherence to the documented upgrade procedure.
339 If using a custom kernel configuration ensure that the
340 COMPAT_FREEBSD11 option is included (as during the upgrade the
341 system will be running the ino64 kernel with the existing world).
343 For the safest in-place upgrade begin by removing previous build
344 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
345 full procedure documented below under the heading "To rebuild
346 everything and install it on the current system." Specifically,
347 a reboot is required after installing the new kernel before
351 The NATM framework including the en(4), fatm(4), hatm(4), and
352 patm(4) devices has been removed. Consumers should plan a
353 migration before the end-of-life date for FreeBSD 11.
356 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
357 diff has not been implemented, if those are needed a newer version of
358 GNU diff is available via the diffutils package under the gdiff name.
361 As of r316810 for ipfilter, keep frags is no longer assumed when
362 keep state is specified in a rule. r316810 aligns ipfilter with
363 documentation in man pages separating keep frags from keep state.
364 This allows keep state to be specified without forcing keep frags
365 and allows keep frags to be specified independently of keep state.
366 To maintain previous behaviour, also specify keep frags with
367 keep state (as documented in ipf.conf.5).
370 arm64 builds now use the base system LLD 4.0.0 linker by default,
371 instead of requiring that the aarch64-binutils port or package be
372 installed. To continue using aarch64-binutils, set
373 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
376 The UDP optimization in entry 20160818 that added the sysctl
377 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
378 packets will no longer be treated as L3 broadcast packets.
381 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
382 use any explicitly assigned loopback address available in the jail
383 instead of using the first assigned address of the jail.
386 The ctl.ko module no longer implements the iSCSI target frontend:
387 cfiscsi.ko does instead.
389 If building cfiscsi.ko as a kernel module, the module can be loaded
390 via one of the following methods:
391 - `cfiscsi_load="YES"` in loader.conf(5).
392 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
393 - ctladm(8)/ctld(8), when compiled with iSCSI support
394 (`WITH_ISCSI=yes` in src.conf(5))
396 Please see cfiscsi(4) for more details.
399 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
400 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
401 same source (previously, the dependency of mmcsd.ko on mmc.ko was
402 missing, but mmcsd.ko now will refuse to load if it is incompatible
406 The syntax of ipfw(8) named states was changed to avoid ambiguity.
407 If you have used named states in the firewall rules, you need to modify
408 them after installworld and before rebooting. Now named states must
409 be prefixed with colon.
412 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
413 removed as the userland we provide cannot use them. The KMS version
414 (sys/dev/drm2) supports the same hardware.
417 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
418 Please see the 20141231 entry below for information about prerequisites
419 and upgrading, if you are not already using clang 3.5.0 or higher.
422 The code that provides support for ZFS .zfs/ directory functionality
423 has been reimplemented. It's not possible now to create a snapshot
424 by mkdir under .zfs/snapshot/. That should be the only user visible
428 EISA bus support has been removed. The WITH_EISA option is no longer
432 MCA bus support has been removed.
435 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
436 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
439 The EM_MULTIQUEUE kernel configuration option is deprecated now that
440 the em(4) driver conforms to iflib specifications.
443 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
444 IFLIB. If you have a custom kernel configuration that excludes em(4)
445 but you use igb(4), you need to re-add em(4) to your custom configuration.
448 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
449 Please see the 20141231 entry below for information about prerequisites
450 and upgrading, if you are not already using clang 3.5.0 or higher.
453 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
454 Please see the 20141231 entry below for information about prerequisites
455 and upgrading, if you are not already using clang 3.5.0 or higher.
458 The layout of the pmap structure has changed for powerpc to put the pmap
459 statistics at the front for all CPU variations. libkvm(3) and all tools
460 that link against it need to be recompiled.
463 isl(4) and cyapa(4) drivers now require a new driver,
464 chromebook_platform(4), to work properly on Chromebook-class hardware.
465 On other types of hardware the drivers may need to be configured using
466 device hints. Please see the corresponding manual pages for details.
469 The urtwn(4) driver was merged into rtwn(4) and now consists of
470 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
472 Also, firmware for RTL8188CE was renamed due to possible name
473 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
476 GNU rcs has been removed from base. It is available as packages:
477 - rcs: Latest GPLv3 GNU rcs version.
478 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
482 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
483 modules now requires that the kernel configuration contain the
484 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
487 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
488 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
491 Relocatable object files with the extension of .So have been renamed
492 to use an extension of .pico instead. The purpose of this change is
493 to avoid a name clash with shared libraries on case-insensitive file
494 systems. On those file systems, foo.So is the same file as foo.so.
497 GNU rcs has been turned off by default. It can (temporarily) be built
498 again by adding WITH_RCS knob in src.conf.
499 Otherwise, GNU rcs is available from packages:
500 - rcs: Latest GPLv3 GNU rcs version.
501 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
504 The backup_uses_rcs functionality has been removed from rc.subr.
507 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
508 two separate components, QUEUE_MACRO_DEBUG_TRACE and
509 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
510 QUEUE_MACRO_DEBUG behavior.
513 r304787 changed some ioctl interfaces between the iSCSI userspace
514 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
515 rebuilt to work with new kernels. __FreeBSD_version has been bumped
519 The UDP receive code has been updated to only treat incoming UDP
520 packets that were addressed to an L2 broadcast address as L3
521 broadcast packets. It is not expected that this will affect any
522 standards-conforming UDP application. The new behaviour can be
523 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
527 Remove the openbsd_poll system call.
528 __FreeBSD_version has been bumped because of this.
531 The libc stub for the pipe(2) system call has been replaced with
532 a wrapper that calls the pipe2(2) system call and the pipe(2)
533 system call is now only implemented by the kernels that include
534 "options COMPAT_FREEBSD10" in their config file (this is the
535 default). Users should ensure that this option is enabled in
536 their kernel or upgrade userspace to r302092 before upgrading their
540 CAM will now strip leading spaces from SCSI disks' serial numbers.
541 This will affect users who create UFS filesystems on SCSI disks using
542 those disk's diskid device nodes. For example, if /etc/fstab
543 previously contained a line like
544 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
545 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
546 transforms like gmirror may also be affected. ZFS users should
550 The bitstring(3) API has been updated with new functionality and
551 improved performance. But it is binary-incompatible with the old API.
552 Objects built with the new headers may not be linked against objects
553 built with the old headers.
556 The brk and sbrk functions have been removed from libc on arm64.
557 Binutils from ports has been updated to not link to these
558 functions and should be updated to the latest version before
559 installing a new libc.
562 The armv6 port now defaults to hard float ABI. Limited support
563 for running both hardfloat and soft float on the same system
564 is available using the libraries installed with -DWITH_LIBSOFT.
565 This has only been tested as an upgrade path for installworld
566 and packages may fail or need manual intervention to run. New
567 packages will be needed.
569 To update an existing self-hosted armv6hf system, you must add
570 TARGET_ARCH=armv6 on the make command line for both the build
571 and the install steps.
574 Kernel modules compiled outside of a kernel build now default to
575 installing to /boot/modules instead of /boot/kernel. Many kernel
576 modules built this way (such as those in ports) already overrode
577 KMODDIR explicitly to install into /boot/modules. However,
578 manually building and installing a module from /sys/modules will
579 now install to /boot/modules instead of /boot/kernel.
582 The CAM I/O scheduler has been committed to the kernel. There should be
583 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
584 list of known rogues that claim support for this but actually corrupt
585 data is believed to be complete, be on the lookout for data
586 corruption. The known rogue list is believed to be complete:
588 o Crucial MX100, M550 drives with MU01 firmware.
589 o Micron M510 and M550 drives with MU01 firmware.
590 o Micron M500 prior to MU07 firmware
591 o Samsung 830, 840, and 850 all firmwares
592 o FCCT M500 all firmwares
594 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
595 with working NCQ TRIM. For Micron branded drives, see your sales rep for
596 updated firmware. Black listed drives will work correctly because these
597 drives work correctly so long as no NCQ TRIMs are sent to them. Given
598 this list is the same as found in Linux, it's believed there are no
599 other rogues in the market place. All other models from the above
602 To be safe, if you are at all concerned, you can quirk each of your
603 drives to prevent NCQ from being sent by setting:
604 kern.cam.ada.X.quirks="0x2"
605 in loader.conf. If the drive requires the 4k sector quirk, set the
609 The FAST_DEPEND build option has been removed and its functionality is
610 now the one true way. The old mkdep(1) style of 'make depend' has
611 been removed. See 20160311 for further details.
614 Resource range types have grown from unsigned long to uintmax_t. All
615 drivers, and anything using libdevinfo, need to be recompiled.
618 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
619 builds. It no longer runs mkdep(1) during 'make depend', and the
620 'make depend' stage can safely be skipped now as it is auto ran
621 when building 'make all' and will generate all SRCS and DPSRCS before
622 building anything else. Dependencies are gathered at compile time with
623 -MF flags kept in separate .depend files per object file. Users should
624 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
628 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
629 kernel modules. Therefore, if you load any kernel modules at boot time,
630 please install the boot loaders after you install the kernel, but before
634 make kernel KERNCONF=YOUR_KERNEL_HERE
635 make -C sys/boot install
636 <reboot in single user>
638 Then follow the usual steps, described in the General Notes section,
642 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
643 see the 20141231 entry below for information about prerequisites and
644 upgrading, if you are not already using clang 3.5.0 or higher.
647 The AIO subsystem is now a standard part of the kernel. The
648 VFS_AIO kernel option and aio.ko kernel module have been removed.
649 Due to stability concerns, asynchronous I/O requests are only
650 permitted on sockets and raw disks by default. To enable
651 asynchronous I/O requests on all file types, set the
652 vfs.aio.enable_unsafe sysctl to a non-zero value.
655 The ELF object manipulation tool objcopy is now provided by the
656 ELF Tool Chain project rather than by GNU binutils. It should be a
657 drop-in replacement, with the addition of arm64 support. The
658 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
659 to obtain the GNU version if necessary.
662 Building ZFS pools on top of zvols is prohibited by default. That
663 feature has never worked safely; it's always been prone to deadlocks.
664 Using a zvol as the backing store for a VM guest's virtual disk will
665 still work, even if the guest is using ZFS. Legacy behavior can be
666 restored by setting vfs.zfs.vol.recursive=1.
669 The NONE and HPN patches has been removed from OpenSSH. They are
670 still available in the security/openssh-portable port.
673 With the addition of ypldap(8), a new _ypldap user is now required
674 during installworld. "mergemaster -p" can be used to add the user
675 prior to installworld, as documented in the handbook.
678 The tftp loader (pxeboot) now uses the option root-path directive. As a
679 consequence it no longer looks for a pxeboot.4th file on the tftp
680 server. Instead it uses the regular /boot infrastructure as with the
684 The code to start recording plug and play data into the modules has
685 been committed. While the old tools will properly build a new kernel,
686 a number of warnings about "unknown metadata record 4" will be produced
687 for an older kldxref. To avoid such warnings, make sure to rebuild
688 the kernel toolchain (or world). Make sure that you have r292078 or
689 later when trying to build 292077 or later before rebuilding.
692 Debug data files are now built by default with 'make buildworld' and
693 installed with 'make installworld'. This facilitates debugging but
694 requires more disk space both during the build and for the installed
695 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
699 r291527 changed the internal interface between the nfsd.ko and
700 nfscommon.ko modules. As such, they must both be upgraded to-gether.
701 __FreeBSD_version has been bumped because of this.
704 Add support for unicode collation strings leads to a change of
705 order of files listed by ls(1) for example. To get back to the old
706 behaviour, set LC_COLLATE environment variable to "C".
708 Databases administrators will need to reindex their databases given
709 collation results will be different.
711 Due to a bug in install(1) it is recommended to remove the ancient
712 locales before running make installworld.
714 rm -rf /usr/share/locale/*
717 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
718 libcrypto.so.7 or libssl.so.7 must be recompiled.
721 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
722 Kernel modules isp_2400_multi and isp_2500_multi were removed and
723 should be replaced with isp_2400 and isp_2500 modules respectively.
726 The build previously allowed using 'make -n' to not recurse into
727 sub-directories while showing what commands would be executed, and
728 'make -n -n' to recursively show commands. Now 'make -n' will recurse
729 and 'make -N' will not.
732 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
733 and etcupdate will now use this file. A custom sendmail.cf is now
734 updated via this mechanism rather than via installworld. If you had
735 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
736 want to remove the exclusion or change it to "always install".
737 /etc/mail/sendmail.cf is now managed the same way regardless of
738 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
739 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
742 Compatibility shims for legacy ATA device names have been removed.
743 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
744 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
745 environment variables, /dev/ad* and /dev/ar* symbolic links.
748 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
749 Please see the 20141231 entry below for information about prerequisites
750 and upgrading, if you are not already using clang 3.5.0 or higher.
753 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
754 and renamed from .symbols to .debug. This reduces the size requirements
755 on the boot partition or file system and provides consistency with
756 userland debug files.
758 When using the supported kernel installation method the
759 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
760 as is done with /boot/kernel.
762 Developers wishing to maintain the historical behavior of installing
763 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
766 The wireless drivers had undergone changes that remove the 'parent
767 interface' from the ifconfig -l output. The rc.d network scripts
768 used to check presence of a parent interface in the list, so old
769 scripts would fail to start wireless networking. Thus, etcupdate(3)
770 or mergemaster(8) run is required after kernel update, to update your
771 rc.d scripts in /etc.
774 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
775 These configurations are now automatically interpreted as
776 'scrub fragment reassemble'.
779 Kernel-loadable modules for the random(4) device are back. To use
780 them, the kernel must have
783 options RANDOM_LOADABLE
785 kldload(8) can then be used to load random_fortuna.ko
786 or random_yarrow.ko. Please note that due to the indirect
787 function calls that the loadable modules need to provide,
788 the build-in variants will be slightly more efficient.
790 The random(4) kernel option RANDOM_DUMMY has been retired due to
791 unpopularity. It was not all that useful anyway.
794 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
795 Control over building the ELF Tool Chain tools is now provided by
796 the WITHOUT_TOOLCHAIN knob.
799 The polarity of Pulse Per Second (PPS) capture events with the
800 uart(4) driver has been corrected. Prior to this change the PPS
801 "assert" event corresponded to the trailing edge of a positive PPS
802 pulse and the "clear" event was the leading edge of the next pulse.
804 As the width of a PPS pulse in a typical GPS receiver is on the
805 order of 1 millisecond, most users will not notice any significant
806 difference with this change.
808 Anyone who has compensated for the historical polarity reversal by
809 configuring a negative offset equal to the pulse width will need to
810 remove that workaround.
813 The default group assigned to /dev/dri entries has been changed
814 from 'wheel' to 'video' with the id of '44'. If you want to have
815 access to the dri devices please add yourself to the video group
818 # pw groupmod video -m $USER
821 The menu.rc and loader.rc files will now be replaced during
822 upgrades. Please migrate local changes to menu.rc.local and
823 loader.rc.local instead.
826 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
827 strings and strip have been removed. The src.conf(5) knob
828 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
831 As ZFS requires more kernel stack pages than is the default on some
832 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
833 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
835 Please consider using 'options KSTACK_PAGES=X' where X is greater
836 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
839 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
840 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
841 default, i.e., they will not contain "::". For example, instead
842 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
843 to have a more specific match, such as different map entries for
844 IPv6:0:0 vs IPv6:0. This change requires that configuration
845 data (including maps, files, classes, custom ruleset, etc.) must
846 use the same format, so make certain such configuration data is
847 upgrading. As a very simple check search for patterns like
848 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
849 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
850 the cf option UseCompressedIPv6Addresses.
853 The default kernel entropy-processing algorithm is now
854 Fortuna, replacing Yarrow.
856 Assuming you have 'device random' in your kernel config
857 file, the configurations allow a kernel option to override
858 this default. You may choose *ONE* of:
860 options RANDOM_YARROW # Legacy /dev/random algorithm.
861 options RANDOM_DUMMY # Blocking-only driver.
863 If you have neither, you get Fortuna. For most people,
864 read no further, Fortuna will give a /dev/random that works
865 like it always used to, and the difference will be irrelevant.
867 If you remove 'device random', you get *NO* kernel-processed
868 entropy at all. This may be acceptable to folks building
869 embedded systems, but has complications. Carry on reading,
870 and it is assumed you know what you need.
872 *PLEASE* read random(4) and random(9) if you are in the
873 habit of tweaking kernel configs, and/or if you are a member
874 of the embedded community, wanting specific and not-usual
875 behaviour from your security subsystems.
877 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
878 random', you will NOT have a functioning /dev/random, and
879 many cryptographic features will not work, including SSH.
880 You may also find strange behaviour from the random(3) set
881 of library functions, in particular sranddev(3), srandomdev(3)
882 and arc4random(3). The reason for this is that the KERN_ARND
883 sysctl only returns entropy if it thinks it has some to
884 share, and with RANDOM_DUMMY or no 'device random' this
888 An additional fix for the issue described in the 20150614 sendmail
889 entry below has been committed in revision 284717.
892 FreeBSD's old make (fmake) has been removed from the system. It is
893 available as the devel/fmake port or via pkg install fmake.
896 The fix for the issue described in the 20150614 sendmail entry
897 below has been committed in revision 284436. The work
898 around described in that entry is no longer needed unless the
899 default setting is overridden by a confDH_PARAMETERS configuration
900 setting of '5' or pointing to a 512 bit DH parameter file.
903 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
904 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
905 and devel/kyua to version 0.20+ and adjust any calling code to work
906 with Kyuafile and kyua.
909 The import of openssl to address the FreeBSD-SA-15:10.openssl
910 security advisory includes a change which rejects handshakes
911 with DH parameters below 768 bits. sendmail releases prior
912 to 8.15.2 (not yet released), defaulted to a 512 bit
913 DH parameter setting for client connections. To work around
914 this interoperability, sendmail can be configured to use a
915 2048 bit DH parameter by:
917 1. Edit /etc/mail/`hostname`.mc
918 2. If a setting for confDH_PARAMETERS does not exist or
919 exists and is set to a string beginning with '5',
921 3. If a setting for confDH_PARAMETERS exists and is set to
922 a file path, create a new file with:
923 openssl dhparam -out /path/to/file 2048
924 4. Rebuild the .cf file:
925 cd /etc/mail/; make; make install
927 cd /etc/mail/; make restart
929 A sendmail patch is coming, at which time this file will be
933 Generation of legacy formatted entries have been disabled by default
934 in pwd_mkdb(8), as all base system consumers of the legacy formatted
935 entries were converted to use the new format by default when the new,
936 machine independent format have been added and supported since FreeBSD
939 Please see the pwd_mkdb(8) manual page for further details.
942 Clang and llvm have been upgraded to 3.6.1 release. Please see the
943 20141231 entry below for information about prerequisites and upgrading,
944 if you are not already using 3.5.0 or higher.
947 TI platform code switched to using vendor DTS files and this update
948 may break existing systems running on Beaglebone, Beaglebone Black,
951 - dtb files should be regenerated/reinstalled. Filenames are the
952 same but content is different now
953 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
954 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
955 addressing scheme is now pin 25 on /dev/gpioc3.
956 - Pandaboard: /etc/ttys should be updated, serial console device is
957 now /dev/ttyu2, not /dev/ttyu0
960 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
961 If you need the GNU extension from groff soelim(1), install groff
962 from package: pkg install groff, or via ports: textproc/groff.
965 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
966 defined in symlink(7); previously symlinks were silently ignored.
969 The const qualifier has been removed from iconv(3) to comply with
970 POSIX. The ports tree is aware of this from r384038 onwards.
973 Libraries specified by LIBADD in Makefiles must have a corresponding
974 DPADD_<lib> variable to ensure correct dependencies. This is now
975 enforced in src.libnames.mk.
978 From legacy ata(4) driver was removed support for SATA controllers
979 supported by more functional drivers ahci(4), siis(4) and mvs(4).
980 Kernel modules ataahci and ataadaptec were removed completely,
981 replaced by ahci and mvs modules respectively.
984 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
985 the 20141231 entry below for information about prerequisites and
986 upgrading, if you are not already using 3.5.0 or higher.
989 The 32-bit PowerPC kernel has been changed to a position-independent
990 executable. This can only be booted with a version of loader(8)
991 newer than January 31, 2015, so make sure to update both world and
992 kernel before rebooting.
995 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
996 but before r278950, the RNG was not seeded properly. Immediately
997 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
998 ssh keys or openssl keys) that were generated w/ a kernel from that
999 range. This does not affect programs that directly used /dev/random
1000 or /dev/urandom. All userland uses of arc4random(3) are affected.
1003 The autofs(4) ABI was changed in order to restore binary compatibility
1004 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1005 with the new kernel.
1008 The powerpc64 kernel has been changed to a position-independent
1009 executable. This can only be booted with a new version of loader(8),
1010 so make sure to update both world and kernel before rebooting.
1013 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1014 only release, no new features have been added. Please see the 20141231
1015 entry below for information about prerequisites and upgrading, if you
1016 are not already using 3.5.0.
1019 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1020 taken from the ELF Tool Chain project rather than GNU binutils. They
1021 should be drop-in replacements, with the addition of arm64 support.
1022 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1023 binutils tools, if necessary. See 20150805 for updated information.
1026 The default Unbound configuration now enables remote control
1027 using a local socket. Users who have already enabled the
1028 local_unbound service should regenerate their configuration
1029 by running "service local_unbound setup" as root.
1032 The GNU texinfo and GNU info pages have been removed.
1033 To be able to view GNU info pages please install texinfo from ports.
1036 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1038 As of this release, a prerequisite for building clang, llvm and lldb is
1039 a C++11 capable compiler and C++11 standard library. This means that to
1040 be able to successfully build the cross-tools stage of buildworld, with
1041 clang as the bootstrap compiler, your system compiler or cross compiler
1042 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1043 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1046 On any standard FreeBSD 10.x or 11.x installation, where clang and
1047 libc++ are on by default (that is, on x86 or arm), this should work out
1050 On 9.x installations where clang is enabled by default, e.g. on x86 and
1051 powerpc, libc++ will not be enabled by default, so libc++ should be
1052 built (with clang) and installed first. If both clang and libc++ are
1053 missing, build clang first, then use it to build libc++.
1055 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1056 the instructions for 9.x above.
1058 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1059 default, and do not build clang.
1061 Many embedded systems are resource constrained, and will not be able to
1062 build clang in a reasonable time, or in some cases at all. In those
1063 cases, cross building bootable systems on amd64 is a workaround.
1065 This new version of clang introduces a number of new warnings, of which
1066 the following are most likely to appear:
1070 This warns in two cases, for both C and C++:
1071 * When the code is trying to take the absolute value of an unsigned
1072 quantity, which is effectively a no-op, and almost never what was
1073 intended. The code should be fixed, if at all possible. If you are
1074 sure that the unsigned quantity can be safely cast to signed, without
1075 loss of information or undefined behavior, you can add an explicit
1076 cast, or disable the warning.
1078 * When the code is trying to take an absolute value, but the called
1079 abs() variant is for the wrong type, which can lead to truncation.
1080 If you want to disable the warning instead of fixing the code, please
1081 make sure that truncation will not occur, or it might lead to unwanted
1084 -Wtautological-undefined-compare and
1085 -Wundefined-bool-conversion
1087 These warn when C++ code is trying to compare 'this' against NULL, while
1088 'this' should never be NULL in well-defined C++ code. However, there is
1089 some legacy (pre C++11) code out there, which actively abuses this
1090 feature, which was less strictly defined in previous C++ versions.
1092 Squid and openjdk do this, for example. The warning can be turned off
1093 for C++98 and earlier, but compiling the code in C++11 mode might result
1094 in unexpected behavior; for example, the parts of the program that are
1095 unreachable could be optimized away.
1098 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1099 kernel sources have been removed. The .h files remain, since some
1100 utilities include them. This will need to be fixed later.
1101 If "mount -t oldnfs ..." is attempted, it will fail.
1102 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1103 the utilities will report errors.
1106 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1107 directories to top level SUBDIR variable when their parent
1108 directory is included in LOCAL_DIRS. Users with build systems with
1109 such hierarchies and without SUBDIR entries in the parent
1110 directory Makefiles should add them or add the directories to
1114 faith(4) and faithd(8) have been removed from the base system. Faith
1115 has been obsolete for a very long time.
1118 vt(4), the new console driver, is enabled by default. It brings
1119 support for Unicode and double-width characters, as well as
1120 support for UEFI and integration with the KMS kernel video
1123 You may need to update your console settings in /etc/rc.conf,
1124 most probably the keymap. During boot, /etc/rc.d/syscons will
1125 indicate what you need to do.
1127 vt(4) still has issues and lacks some features compared to
1128 syscons(4). See the wiki for up-to-date information:
1129 https://wiki.freebsd.org/Newcons
1131 If you want to keep using syscons(4), you can do so by adding
1132 the following line to /boot/loader.conf:
1136 pjdfstest has been integrated into kyua as an opt-in test suite.
1137 Please see share/doc/pjdfstest/README for more details on how to
1141 gperf has been removed from the base system for architectures
1142 that use clang. Ports that require gperf will obtain it from the
1146 pjdfstest has been moved from tools/regression/pjdfstest to
1150 At svn r271982, The default linux compat kernel ABI has been adjusted
1151 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1152 update. If you wish to continue using the linux-f10 compat ports,
1153 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1154 encouraged to update their linux-compat packages to linux-c6 during
1155 their next update cycle.
1158 The ofwfb driver, used to provide a graphics console on PowerPC when
1159 using vt(4), no longer allows mmap() of all physical memory. This
1160 will prevent Xorg on PowerPC with some ATI graphics cards from
1161 initializing properly unless x11-servers/xorg-server is updated to
1165 The xdev targets have been converted to using TARGET and
1166 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1169 The default unbound configuration has been modified to address
1170 issues with reverse lookups on networks that use private
1171 address ranges. If you use the local_unbound service, run
1172 "service local_unbound setup" as root to regenerate your
1173 configuration, then "service local_unbound reload" to load the
1177 The GNU texinfo and GNU info pages are not built and installed
1178 anymore, WITH_INFO knob has been added to allow to built and install
1180 UPDATE: see 20150102 entry on texinfo's removal
1183 The GNU readline library is now an INTERNALLIB - that is, it is
1184 statically linked into consumers (GDB and variants) in the base
1185 system, and the shared library is no longer installed. The
1186 devel/readline port is available for third party software that
1190 The Itanium architecture (ia64) has been removed from the list of
1191 known architectures. This is the first step in the removal of the
1195 Commit r268115 has added NFSv4.1 server support, merged from
1196 projects/nfsv4.1-server. Since this includes changes to the
1197 internal interfaces between the NFS related modules, a full
1198 build of the kernel and modules will be necessary.
1199 __FreeBSD_version has been bumped.
1202 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1203 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1204 which differs from the behaviour controlled by this knob.)
1207 Maximal length of the serial number in CTL was increased from 16 to
1208 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1209 and ctld, need to be rebuilt to work with a new kernel.
1212 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1213 1 respectively to match the upstream numbers. They were out of
1214 sync because, when they were originally added to FreeBSD, the
1215 upstream versions were not respected. These libraries are private
1216 and not yet built by default, so renumbering them should be a
1217 non-issue. However, unclean source trees will yield broken test
1218 programs once the operator executes "make delete-old-libs" after a
1219 "make installworld".
1221 Additionally, the atf-sh binary was made private by moving it into
1222 /usr/libexec/. Already-built shell test programs will keep the
1223 path to the old binary so they will break after "make delete-old"
1226 If you are using WITH_TESTS=yes (not the default), wipe the object
1227 tree and rebuild from scratch to prevent spurious test failures.
1228 This is only needed once: the misnumbered libraries and misplaced
1229 binaries have been added to OptionalObsoleteFiles.inc so they will
1230 be removed during a clean upgrade.
1233 Clang and llvm have been upgraded to 3.4.1 release.
1236 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1237 be removed to avoid issues in the future (and has been added to
1241 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1242 past, it affected all builds that used the bsd.*.mk files. The old
1243 behavior was a bug, but people may have relied upon it. To get this
1244 behavior back, you can .include /etc/src.conf from /etc/make.conf
1245 (which is still global and isn't changed). This also changes the
1246 behavior of incremental builds inside the tree of individual
1247 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1248 Although this has survived make universe and some upgrade scenarios,
1249 other upgrade scenarios may have broken. At least one form of
1250 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1251 as well... In cases where MAKESYSPATH isn't working with this
1252 setting, you'll need to set it to the full path to your tree.
1254 One side effect of all this cleaning up is that bsd.compiler.mk
1255 is no longer implicitly included by bsd.own.mk. If you wish to
1256 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1260 The lindev device has been removed since /dev/full has been made a
1261 standard device. __FreeBSD_version has been bumped.
1264 The knob WITHOUT_VI was added to the base system, which controls
1265 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1266 in order to reorder files share/termcap and didn't build ex(1) as a
1267 build tool, so building/installing with WITH_VI is highly advised for
1268 build hosts for older releases.
1270 This issue has been fixed in stable/9 and stable/10 in r277022 and
1271 r276991, respectively.
1274 The YES_HESIOD knob has been removed. It has been obsolete for
1275 a decade. Please move to using WITH_HESIOD instead or your builds
1276 will silently lack HESIOD.
1279 The uart(4) driver has been changed with respect to its handling
1280 of the low-level console. Previously the uart(4) driver prevented
1281 any process from changing the baudrate or the CLOCAL and HUPCL
1282 control flags. By removing the restrictions, operators can make
1283 changes to the serial console port without having to reboot.
1284 However, when getty(8) is started on the serial device that is
1285 associated with the low-level console, a misconfigured terminal
1286 line in /etc/ttys will now have a real impact.
1287 Before upgrading the kernel, make sure that /etc/ttys has the
1288 serial console device configured as 3wire without baudrate to
1289 preserve the previous behaviour. E.g:
1290 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1293 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1294 to improve performance. To re-enable it, if needed, run rpcbind
1295 with command line option -W.
1298 Switched back to the GPL dtc compiler due to updates in the upstream
1299 dts files not being supported by the BSDL dtc compiler. You will need
1300 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1301 may result while building dtb files during a kernel build if you fail
1302 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1305 Clang and llvm have been upgraded to 3.4 release.
1308 The nve(4) driver has been removed. Please use the nfe(4) driver
1309 for NVIDIA nForce MCP Ethernet adapters instead.
1312 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1313 This could cause certain C++ applications using shared libraries built
1314 against the previous version of libc++ to crash. The incompatibility
1315 has now been fixed, but any C++ applications or shared libraries built
1316 between r261283 and r261801 should be recompiled.
1319 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1320 capability mode support. Please note that enabling the feature in
1321 kernel is still highly recommended.
1324 OpenSSH is now built with sandbox support, and will use sandbox as
1325 the default privilege separation method. This requires Capsicum
1326 capability mode support in kernel.
1329 The libelf and libdwarf libraries have been updated to newer
1330 versions from upstream. Shared library version numbers for
1331 these two libraries were bumped. Any ports or binaries
1332 requiring these two libraries should be recompiled.
1333 __FreeBSD_version is bumped to 1100006.
1336 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1337 instead of providing an explicit one, this would prevent such
1338 Makefile from providing its own Kyuafile in the future during
1339 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1340 intervention is needed to clean an objdir if you use NO_CLEAN:
1341 # find /usr/obj -name Kyuafile | xargs rm -f
1344 The behavior of gss_pseudo_random() for the krb5 mechanism
1345 has changed, for applications requesting a longer random string
1346 than produced by the underlying enctype's pseudo-random() function.
1347 In particular, the random string produced from a session key of
1348 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1349 be different at the 17th octet and later, after this change.
1350 The counter used in the PRF+ construction is now encoded as a
1351 big-endian integer in accordance with RFC 4402.
1352 __FreeBSD_version is bumped to 1100004.
1355 The WITHOUT_ATF build knob has been removed and its functionality
1356 has been subsumed into the more generic WITHOUT_TESTS. If you were
1357 using the former to disable the build of the ATF libraries, you
1358 should change your settings to use the latter.
1361 The default version of mtree is nmtree which is obtained from
1362 NetBSD. The output is generally the same, but may vary
1363 slightly. If you found you need identical output adding
1364 "-F freebsd9" to the command line should do the trick. For the
1365 time being, the old mtree is available as fmtree.
1368 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1369 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1370 1.1.4_8 and verify bsdyml not linked in, before running "make
1372 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1374 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1377 The stable/10 branch has been created in subversion from head
1381 The rc.d/jail script has been updated to support jail(8)
1382 configuration file. The "jail_<jname>_*" rc.conf(5) variables
1383 for per-jail configuration are automatically converted to
1384 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
1385 This is transparently backward compatible. See below about some
1386 incompatibilities and rc.conf(5) manual page for more details.
1388 These variables are now deprecated in favor of jail(8) configuration
1389 file. One can use "rc.d/jail config <jname>" command to generate
1390 a jail(8) configuration file in /var/run/jail.<jname>.conf without
1391 running the jail(8) utility. The default pathname of the
1392 configuration file is /etc/jail.conf and can be specified by
1393 using $jail_conf or $jail_<jname>_conf variables.
1395 Please note that jail_devfs_ruleset accepts an integer at
1396 this moment. Please consider to rewrite the ruleset name
1400 BIND has been removed from the base system. If all you need
1401 is a local resolver, simply enable and start the local_unbound
1402 service instead. Otherwise, several versions of BIND are
1403 available in the ports tree. The dns/bind99 port is one example.
1405 With this change, nslookup(1) and dig(1) are no longer in the base
1406 system. Users should instead use host(1) and drill(1) which are
1407 in the base system. Alternatively, nslookup and dig can
1408 be obtained by installing the dns/bind-tools port.
1411 With the addition of unbound(8), a new unbound user is now
1412 required during installworld. "mergemaster -p" can be used to
1413 add the user prior to installworld, as documented in the handbook.
1416 OpenSSH is now built with DNSSEC support, and will by default
1417 silently trust signed SSHFP records. This can be controlled with
1418 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1419 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1422 The GNU Compiler Collection and C++ standard library (libstdc++)
1423 are no longer built by default on platforms where clang is the system
1424 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1425 options in src.conf.
1428 The PROCDESC kernel option is now part of the GENERIC kernel
1429 configuration and is required for the rwhod(8) to work.
1430 If you are using custom kernel configuration, you should include
1434 The API and ABI related to the Capsicum framework was modified
1435 in backward incompatible way. The userland libraries and programs
1436 have to be recompiled to work with the new kernel. This includes the
1437 following libraries and programs, but the whole buildworld is
1438 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1439 kdump, procstat, rwho, rwhod, uniq.
1442 AES-NI intrinsic support has been added to gcc. The AES-NI module
1443 has been updated to use this support. A new gcc is required to build
1444 the aesni module on both i386 and amd64.
1447 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1448 Thus "device padlock_rng" and "device rdrand_rng" should be
1449 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1452 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1453 enables just the iconv* functionality and is now on by default.
1454 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1455 compatibility. Set WITHOUT_ICONV to build the old way.
1456 If you have been using WITH_ICONV before, you will very likely
1457 need to turn on WITH_LIBICONV_COMPAT.
1460 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1461 Illumos origin, including ZFS. If you have INVARIANTS in your
1462 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1464 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1465 locks if WITNESS option was set. Because that generated a lot of
1466 witness(9) reports and all of them were believed to be false
1467 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1468 can be used to achieve the previous behavior.
1471 Timer values in IPv6 data structures now use time_uptime instead
1472 of time_second. Although this is not a user-visible functional
1473 change, userland utilities which directly use them---ndp(8),
1474 rtadvd(8), and rtsold(8) in the base system---need to be updated
1475 to r253970 or later.
1478 find -delete can now delete the pathnames given as arguments,
1479 instead of only files found below them or if the pathname did
1480 not contain any slashes. Formerly, the following error message
1483 find: -delete: <path>: relative path potentially not safe
1485 Deleting the pathnames given as arguments can be prevented
1486 without error messages using -mindepth 1 or by changing
1487 directory and passing "." as argument to find. This works in the
1488 old as well as the new version of find.
1491 Behavior of devfs rules path matching has been changed.
1492 Pattern is now always matched against fully qualified devfs
1493 path and slash characters must be explicitly matched by
1494 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1495 subdirectories must be reviewed.
1498 The default ARM ABI has changed to the ARM EABI. The old ABI is
1499 incompatible with the ARM EABI and all programs and modules will
1500 need to be rebuilt to work with a new kernel.
1502 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1504 NOTE: Support for the old ABI will be removed in the future and
1505 users are advised to upgrade.
1508 pkg_install has been disconnected from the build if you really need it
1509 you should add WITH_PKGTOOLS in your src.conf(5).
1512 Most of network statistics structures were changed to be able
1513 keep 64-bits counters. Thus all tools, that work with networking
1514 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1517 Fix a bug that allowed a tracing process (e.g. gdb) to write
1518 to a memory-mapped file in the traced process's address space
1519 even if neither the traced process nor the tracing process had
1520 write access to that file.
1523 CVS has been removed from the base system. An exact copy
1524 of the code is available from the devel/cvs port.
1527 Some people report the following error after the switch to bmake:
1529 make: illegal option -- J
1530 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1532 *** [buildworld] Error code 2
1534 this likely due to an old instance of make in
1535 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1536 which src/Makefile will use that blindly, if it exists, so if
1537 you see the above error:
1539 rm -rf `make -V MAKEPATH`
1544 Use bmake by default.
1545 Whereas before one could choose to build with bmake via
1546 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1547 make. The goal is to remove these knobs for 10-RELEASE.
1549 It is worth noting that bmake (like gmake) treats the command
1550 line as the unit of failure, rather than statements within the
1551 command line. Thus '(cd some/where && dosomething)' is safer
1552 than 'cd some/where; dosomething'. The '()' allows consistent
1553 behavior in parallel build.
1556 Fix a bug that allows NFS clients to issue READDIR on files.
1559 The WITHOUT_IDEA option has been removed because
1560 the IDEA patent expired.
1563 The sysctl which controls TRIM support under ZFS has been renamed
1564 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1568 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1569 rather than creating it's own in the temporary directory in
1570 order allow access to bootstrapped versions of tools such as
1571 install and mtree. When upgrading from version of FreeBSD where
1572 the install command does not support -l, you will need to
1573 install a new mergemaster command if mergemaster -p is required.
1574 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1578 Legacy ATA stack, disabled and replaced by new CAM-based one since
1579 FreeBSD 9.0, completely removed from the sources. Kernel modules
1580 atadisk and atapi*, user-level tools atacontrol and burncd are
1581 removed. Kernel option `options ATA_CAM` is now permanently enabled
1585 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1586 and socketpair(2). Software, in particular Kerberos, may
1587 automatically detect and use these during building. The resulting
1588 binaries will not work on older kernels.
1591 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1592 information, see the respective 20130304 entry).
1595 Recent commits to callout(9) changed the size of struct callout,
1596 so the KBI is probably heavily disturbed. Also, some functions
1597 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1598 by macros. Every kernel module using it won't load, so rebuild
1601 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1602 but does not initialize by default (because of the new CTL_DISABLE
1603 option) to save memory. To re-enable it, remove the CTL_DISABLE
1604 option from the kernel config file or set kern.cam.ctl.disable=0
1605 in /boot/loader.conf.
1608 The ctl device has been disabled in GENERIC for i386 and amd64.
1609 This was done due to the extra memory being allocated at system
1610 initialisation time by the ctl driver which was only used if
1611 a CAM target device was created. This makes a FreeBSD system
1612 unusable on 128MB or less of RAM.
1615 A new compression method (lz4) has been merged to -HEAD. Please
1616 refer to zpool-features(7) for more information.
1618 Please refer to the "ZFS notes" section of this file for information
1619 on upgrading boot ZFS pools.
1622 A BSD-licensed patch(1) variant has been added and is installed
1623 as bsdpatch, being the GNU version the default patch.
1624 To inverse the logic and use the BSD-licensed one as default,
1625 while having the GNU version installed as gnupatch, rebuild
1626 and install world with the WITH_BSD_PATCH knob set.
1629 Due to the use of the new -l option to install(1) during build
1630 and install, you must take care not to directly set the INSTALL
1631 make variable in your /etc/make.conf, /etc/src.conf, or on the
1632 command line. If you wish to use the -C flag for all installs
1633 you may be able to add INSTALL+=-C to /etc/make.conf or
1637 The install(1) option -M has changed meaning and now takes an
1638 argument that is a file or path to append logs to. In the
1639 unlikely event that -M was the last option on the command line
1640 and the command line contained at least two files and a target
1641 directory the first file will have logs appended to it. The -M
1642 option served little practical purpose in the last decade so its
1643 use is expected to be extremely rare.
1646 After switching to Clang as the default compiler some users of ZFS
1647 on i386 systems started to experience stack overflow kernel panics.
1648 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1651 GEOM_LABEL now mangles label names read from file system metadata.
1652 Mangling affect labels containing spaces, non-printable characters,
1653 '%' or '"'. Device names in /etc/fstab and other places may need to
1657 By default, only the 10 most recent kernel dumps will be saved. To
1658 restore the previous behaviour (no limit on the number of kernel dumps
1659 stored in the dump directory) add the following line to /etc/rc.conf:
1664 With the addition of auditdistd(8), a new auditdistd user is now
1665 required during installworld. "mergemaster -p" can be used to
1666 add the user prior to installworld, as documented in the handbook.
1669 The sin6_scope_id member variable in struct sockaddr_in6 is now
1670 filled by the kernel before passing the structure to the userland via
1671 sysctl or routing socket. This means the KAME-specific embedded scope
1672 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1673 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1674 __FreeBSD_version is bumped to 1000025.
1677 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1678 This means that the world and kernel will be compiled with clang
1679 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1680 and /usr/bin/cpp. To disable this behavior and revert to building
1681 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1682 of current may need to bootstrap WITHOUT_CLANG first if the clang
1683 build fails (its compatibility window doesn't extend to the 9 stable
1687 The IPFIREWALL_FORWARD kernel option has been removed. Its
1688 functionality now turned on by default.
1691 The ZERO_COPY_SOCKET kernel option has been removed and
1692 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1693 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1694 mechanism which is not safe and may result in kernel crashes.
1695 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1696 driver supports disposeable external page sized mbuf storage.
1697 Proper replacements for both zero-copy mechanisms are under
1698 consideration and will eventually lead to complete removal
1699 of the two kernel options.
1702 The IPv4 network stack has been converted to network byte
1703 order. The following modules need to be recompiled together
1704 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1705 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1708 Support for non-MPSAFE filesystems was removed from VFS. The
1709 VFS_VERSION was bumped, all filesystem modules shall be
1713 All the non-MPSAFE filesystems have been disconnected from
1714 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1715 portalfs, smbfs, xfs.
1718 The interface cloning API and ABI has changed. The following
1719 modules need to be recompiled together with kernel:
1720 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1721 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1722 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1725 The sdhci driver was split in two parts: sdhci (generic SD Host
1726 Controller logic) and sdhci_pci (actual hardware driver).
1727 No kernel config modifications are required, but if you
1728 load sdhc as a module you must switch to sdhci_pci instead.
1731 Import the FUSE kernel and userland support into base system.
1734 The GNU sort(1) program has been removed since the BSD-licensed
1735 sort(1) has been the default for quite some time and no serious
1736 problems have been reported. The corresponding WITH_GNU_SORT
1740 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1741 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1745 The net80211(4) ABI has been changed to allow for improved driver
1746 PS-POLL and power-save support. All wireless drivers need to be
1747 recompiled to work with the new kernel.
1750 The random(4) support for the VIA hardware random number
1751 generator (`PADLOCK') is no longer enabled unconditionally.
1752 Add the padlock_rng device in the custom kernel config if
1753 needed. The GENERIC kernels on i386 and amd64 do include the
1754 device, so the change only affects the custom kernel
1758 The pf(4) packet filter ABI has been changed. pfctl(8) and
1759 snmp_pf module need to be recompiled to work with new kernel.
1762 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1763 to -HEAD. Pools that have empty_bpobj in active state can not be
1764 imported read-write with ZFS implementations that do not support
1765 this feature. For more information read the zpool-features(5)
1769 The sparc64 ZFS loader has been changed to no longer try to auto-
1770 detect ZFS providers based on diskN aliases but now requires these
1771 to be explicitly listed in the OFW boot-device environment variable.
1774 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1775 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1776 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1779 The following sysctls and tunables have been renamed for consistency
1780 with other variables:
1781 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1782 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1785 The sort utility has been replaced with BSD sort. For now, GNU sort
1786 is also available as "gnusort" or the default can be set back to
1787 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1788 installed as "bsdsort".
1791 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1792 Starting with this version the old system of ZFS pool versioning
1793 is superseded by "feature flags". This concept enables forward
1794 compatibility against certain future changes in functionality of ZFS
1795 pools. The first read-only compatible "feature flag" for ZFS pools
1796 is named "com.delphix:async_destroy". For more information
1797 read the new zpool-features(5) manual page.
1798 Please refer to the "ZFS notes" section of this file for information
1799 on upgrading boot ZFS pools.
1802 The malloc(3) implementation embedded in libc now uses sources imported
1803 as contrib/jemalloc. The most disruptive API change is to
1804 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1805 delete it prior to installworld, and optionally re-create it using the
1806 new format after rebooting. See malloc.conf(5) for details
1807 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1811 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1812 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1813 now spelled mips. This is to aid compatibility with third-party
1814 software that expects this naming scheme in uname(3). Little-endian
1815 settings are unchanged. If you are updating a big-endian mips64 machine
1816 from before this change, you may need to set MACHINE_ARCH=mips64 in
1817 your environment before the new build system will recognize your machine.
1820 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1824 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1825 nullfs(5) did not pass through all behaviours to the underlying layer,
1826 as a result if we bound to a socket on the lower layer we could connect
1827 only to the lower path; if we bound to the upper layer we could connect
1828 only to the upper path. The new behavior is one can connect to both the
1829 lower and the upper paths regardless what layer path one binds to.
1832 The getifaddrs upgrade path broken with 20111215 has been restored.
1833 If you have upgraded in between 20111215 and 20120209 you need to
1834 recompile libc again with your kernel. You still need to recompile
1835 world to be able to configure CARP but this restriction already
1836 comes from 20111215.
1839 The set_rcvar() function has been removed from /etc/rc.subr. All
1840 base and ports rc.d scripts have been updated, so if you have a
1841 port installed with a script in /usr/local/etc/rc.d you can either
1842 hand-edit the rcvar= line, or reinstall the port.
1844 An easy way to handle the mass-update of /etc/rc.d:
1845 rm /etc/rc.d/* && mergemaster -i
1848 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1849 on the current CPU and prevents other threads from running.
1850 This behavior can be reverted using the kern.stop_scheduler_on_panic
1852 The new behavior can be incompatible with kern.sync_on_panic.
1855 The carp(4) facility has been changed significantly. Configuration
1856 of the CARP protocol via ifconfig(8) has changed, as well as format
1857 of CARP events submitted to devd(8) has changed. See manual pages
1858 for more information. The arpbalance feature of carp(4) is currently
1859 not supported anymore.
1861 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1862 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1863 need to be recompiled.
1866 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1870 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1871 explicitely support non-MPSAFE filesystems.
1872 It is on by default for all supported platform at this present
1876 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1877 i386 and pc98 GENERIC kernel configuration files.
1880 sysinstall has been removed
1883 The stable/9 branch created in subversion. This corresponds to the
1884 RELENG_9 branch in CVS.
1890 Avoid using make -j when upgrading. While generally safe, there are
1891 sometimes problems using -j to upgrade. If your upgrade fails with
1892 -j, please try again without -j. From time to time in the past there
1893 have been problems using -j with buildworld and/or installworld. This
1894 is especially true when upgrading between "distant" versions (eg one
1895 that cross a major release boundary or several minor releases, or when
1896 several months have passed on the -current branch).
1898 Sometimes, obscure build problems are the result of environment
1899 poisoning. This can happen because the make utility reads its
1900 environment when searching for values for global variables. To run
1901 your build attempts in an "environmental clean room", prefix all make
1902 commands with 'env -i '. See the env(1) manual page for more details.
1904 When upgrading from one major version to another it is generally best to
1905 upgrade to the latest code in the currently installed branch first, then
1906 do an upgrade to the new branch. This is the best-tested upgrade path,
1907 and has the highest probability of being successful. Please try this
1908 approach if you encounter problems with a major version upgrade. Since
1909 the stable 4.x branch point, one has generally been able to upgrade from
1910 anywhere in the most recent stable branch to head / current (or even the
1911 last couple of stable branches). See the top of this file when there's
1914 When upgrading a live system, having a root shell around before
1915 installing anything can help undo problems. Not having a root shell
1916 around can lead to problems if pam has changed too much from your
1917 starting point to allow continued authentication after the upgrade.
1919 This file should be read as a log of events. When a later event changes
1920 information of a prior event, the prior event should not be deleted.
1921 Instead, a pointer to the entry with the new information should be
1922 placed in the old entry. Readers of this file should also sanity check
1923 older entries before relying on them blindly. Authors of new entries
1924 should write them with this in mind.
1928 When upgrading the boot ZFS pool to a new version, always follow
1931 1.) recompile and reinstall the ZFS boot loader and boot block
1932 (this is part of "make buildworld" and "make installworld")
1934 2.) update the ZFS boot block on your boot drive
1936 The following example updates the ZFS boot block on the first
1937 partition (freebsd-boot) of a GPT partitioned drive ada0:
1938 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1940 Non-boot pools do not need these updates.
1944 If you are updating from a prior version of FreeBSD (even one just
1945 a few days old), you should follow this procedure. It is the most
1946 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1948 make kernel-toolchain
1949 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1950 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1952 To test a kernel once
1953 ---------------------
1954 If you just want to boot a kernel once (because you are not sure
1955 if it works, or if you want to boot a known bad kernel to provide
1956 debugging information) run
1957 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1958 nextboot -k testkernel
1960 To rebuild everything and install it on the current system.
1961 -----------------------------------------------------------
1962 # Note: sometimes if you are running current you gotta do more than
1963 # is listed here if you are upgrading from a really old current.
1965 <make sure you have good level 0 dumps>
1967 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1968 make installkernel KERNCONF=YOUR_KERNEL_HERE
1970 <reboot in single user> [3]
1977 To cross-install current onto a separate partition
1978 --------------------------------------------------
1979 # In this approach we use a separate partition to hold
1980 # current's root, 'usr', and 'var' directories. A partition
1981 # holding "/", "/usr" and "/var" should be about 2GB in
1984 <make sure you have good level 0 dumps>
1987 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1988 <maybe newfs current's root partition>
1989 <mount current's root partition on directory ${CURRENT_ROOT}>
1990 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1991 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1992 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1993 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1994 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1995 <reboot into current>
1996 <do a "native" rebuild/install as described in the previous section>
1997 <maybe install compatibility libraries from ports/misc/compat*>
2001 To upgrade in-place from stable to current
2002 ----------------------------------------------
2003 <make sure you have good level 0 dumps>
2005 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
2007 <reboot in single user> [3]
2014 Make sure that you've read the UPDATING file to understand the
2015 tweaks to various things you need. At this point in the life
2016 cycle of current, things change often and you are on your own
2017 to cope. The defaults can also change, so please read ALL of
2018 the UPDATING entries.
2020 Also, if you are tracking -current, you must be subscribed to
2021 freebsd-current@freebsd.org. Make sure that before you update
2022 your sources that you have read and understood all the recent
2023 messages there. If in doubt, please track -stable which has
2024 much fewer pitfalls.
2026 [1] If you have third party modules, such as vmware, you
2027 should disable them at this point so they don't crash your
2030 [3] From the bootblocks, boot -s, and then do
2035 adjkerntz -i # if CMOS is wall time
2036 Also, when doing a major release upgrade, it is required that
2037 you boot into single user mode to do the installworld.
2039 [4] Note: This step is non-optional. Failure to do this step
2040 can result in a significant reduction in the functionality of the
2041 system. Attempting to do it by hand is not recommended and those
2042 that pursue this avenue should read this file carefully, as well
2043 as the archives of freebsd-current and freebsd-hackers mailing lists
2044 for potential gotchas. The -U option is also useful to consider.
2045 See mergemaster(8) for more information.
2047 [5] Usually this step is a no-op. However, from time to time
2048 you may need to do this if you get unknown user in the following
2049 step. It never hurts to do it all the time. You may need to
2050 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2051 install) after the buildworld before this step if you last updated
2052 from current before 20130425 or from -stable before 20130430.
2054 [6] This only deletes old files and directories. Old libraries
2055 can be deleted by "make delete-old-libs", but you have to make
2056 sure that no program is using those libraries anymore.
2058 [8] In order to have a kernel that can run the 4.x binaries needed to
2059 do an installworld, you must include the COMPAT_FREEBSD4 option in
2060 your kernel. Failure to do so may leave you with a system that is
2061 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2062 required to run the 5.x binaries on more recent kernels. And so on
2063 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2065 Make sure that you merge any new devices from GENERIC since the
2066 last time you updated your kernel config file.
2068 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2069 "?=" instead of the "=" assignment operator, so that buildworld can
2070 override the CPUTYPE if it needs to.
2072 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2073 not on the command line, or in /etc/make.conf. buildworld will
2074 warn if it is improperly defined.
2077 This file contains a list, in reverse chronological order, of major
2078 breakages in tracking -current. It is not guaranteed to be a complete
2079 list of such breakages, and only contains entries since September 23, 2011.
2080 If you need to see UPDATING entries from before that date, you will need
2081 to fetch an UPDATING file from an older FreeBSD release.
2083 Copyright information:
2085 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2087 Redistribution, publication, translation and use, with or without
2088 modification, in full or in part, in any form or format of this
2089 document are permitted without further permission from the author.
2091 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2092 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2093 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2094 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2095 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2096 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2097 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2098 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2099 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2100 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2101 POSSIBILITY OF SUCH DAMAGE.
2103 Contact Warner Losh if you have any questions about your use of