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