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 r326887 fixes the issue described in the 20171214 UPDATING entry.
56 r326888 flips the switch back to building GELI support always.
59 r362593 broke ZFS + GELI support for reasons unknown. However,
60 it also broke ZFS support generally, so GELI has been turned off
61 by default as the lesser evil in r326857. If you boot off ZFS and/or
62 GELI, it might not be a good time to update.
65 PowerPC users must update loader(8) by rebuilding world before
66 installing a new kernel, as the protocol connecting them has
67 changed. Without the update, loader metadata will not be passed
68 successfully to the kernel and users will have to enter their
69 root partition at the kernel mountroot prompt to continue booting.
70 Newer versions of loader can boot old kernels without issue.
73 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
74 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
75 to WITH/OUT_LOADER_GELI.
78 The naive and non-compliant support of posix_fallocate(2) in ZFS
79 has been removed as of r325320. The system call now returns EINVAL
80 when used on a ZFS file. Although the new behavior complies with the
81 standard, some consumers are not prepared to cope with it.
82 One known victim is lld prior to r325420.
85 Building in a FreeBSD src checkout will automatically create object
86 directories now rather than store files in the current directory if
87 'make obj' was not ran. Calling 'make obj' is no longer necessary.
88 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
89 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
93 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
94 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
95 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
96 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
97 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
98 The UNIFIED_OBJDIR option is a transitional feature that will be
99 removed for 12.0 release; please migrate to the new format for any
100 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
101 than hardcoding paths.
104 The native-xtools target no longer installs the files by default to the
105 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
106 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
109 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
110 options are changing from controlling the build if defined / undefined
111 to controlling the build with explicit 'yes' or 'no' values. They will
112 shift to WITH/WITHOUT options to match other options in the system.
115 libstand has turned into a private library for sys/boot use only.
116 It is no longer supported as a public interface outside of sys/boot.
119 The arm port has split armv6 into armv6 and armv7. armv7 is now
120 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
121 and are running a kernel from before r324363, you will need to add
122 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
125 When building multiple kernels using KERNCONF, non-existent KERNCONF
126 files will produce an error and buildkernel will fail. Previously
127 missing KERNCONF files silently failed giving no indication as to
128 why, only to subsequently discover during installkernel that the
129 desired kernel was never built in the first place.
132 The default serial number format for CTL LUNs has changed. This will
133 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
134 or iSCSI clients care about their LUNs' serial numbers. Users who
135 require serial number stability should hardcode serial numbers in
139 For 32-bit arm compiled for hard-float support, soft-floating point
140 binaries now always get their shared libraries from
141 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
142 /usr/libsoft also existed). Only users with a hard-float ld.so, but
143 soft-float everything else should be affected.
146 The geli password typed at boot is now hidden. To restore the previous
147 behavior, see geli(8) for configuration options.
150 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
151 sysctl values. Minor nit, but requires a rebuild of both world/kernel
155 "make check" behavior (made in ^/head@r295380) has been changed to
156 execute from a limited sandbox, as opposed to executing from
160 - The "beforecheck" and "aftercheck" targets are now specified.
161 - ${CHECKDIR} (added in commit noted above) has been removed.
162 - Legacy behavior can be enabled by setting
163 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
165 If the limited sandbox mode is enabled, "make check" will execute
166 "make distribution", then install, execute the tests, and clean up the
167 sandbox if successful.
169 The "make distribution" and "make install" targets are typically run as
170 root to set appropriate permissions and ownership at installation time.
171 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
172 environment if executing "make check" with limited sandbox mode using
173 an unprivileged user.
176 Since the switch to GPT disk labels, fsck for UFS/FFS has been
177 unable to automatically find alternate superblocks. As of r322297,
178 the information needed to find alternate superblocks has been
179 moved to the end of the area reserved for the boot block.
180 Filesystems created with a newfs of this vintage or later
181 will create the recovery information. If you have a filesystem
182 created prior to this change and wish to have a recovery block
183 created for your filesystem, you can do so by running fsck in
184 forground mode (i.e., do not use the -p or -y options). As it
185 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
186 to which you should answer yes.
189 As of r321665, an NFSv4 server configuration that services
190 Kerberos mounts or clients that do not support the uid/gid in
191 owner/owner_group string capability, must explicitly enable
192 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
193 machine's /etc/rc.conf file.
196 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
197 Please see the 20141231 entry below for information about prerequisites
198 and upgrading, if you are not already using clang 3.5.0 or higher.
201 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
202 r-commands (rlogin, rsh, etc.) to be built with the base system.
205 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
206 a very major ABI incompatible change, so users of FreeBSD/powerpc must
207 be careful when performing source upgrades. It is best to run
208 'make installworld' from an alternate root system, either a live
209 CD/memory stick, or a temporary root partition. Additionally, all ports
210 must be recompiled. powerpc64 is largely unaffected, except in the case
211 of 32-bit compatibility. All 32-bit binaries will be affected.
214 Forward compatibility for the "ino64" project have been committed. This
215 will allow most new binaries to run on older kernels in a limited
216 fashion. This prevents many of the common foot-shooting actions in the
217 upgrade as well as the limited ability to roll back the kernel across
218 the ino64 upgrade. Complicated use cases may not work properly, though
219 enough simpler ones work to allow recovery in most situations.
222 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
223 if you require the GPL compiler.
226 The internal ABI used for communication between the NFS kernel modules
227 was changed by r320085, so __FreeBSD_version was bumped to
228 ensure all the NFS related modules are updated together.
231 The ABI of struct event was changed by extending the data
232 member to 64bit and adding ext fields. For upgrade, same
233 precautions as for the entry 20170523 "ino64" must be
237 The GNU roff toolchain has been removed from base. To render manpages
238 which are not supported by mandoc(1), man(1) can fallback on GNU roff
239 from ports (and recommends to install it).
240 To render roff(7) documents, consider using GNU roff from ports or the
241 heirloom doctools roff toolchain from ports via pkg install groff or
242 via pkg install heirloom-doctools.
245 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
246 smaller runtime footprint builds. This is useful for embedded systems
247 which only require one chipset support.
249 If you load it as a module, make sure this is in /boot/loader.conf:
253 This will load the HAL, all chip/RF backends and if_ath_pci.
254 If you have if_ath_pci in /boot/loader.conf, ensure it is after
255 if_ath or it will not load any HAL chipset support.
257 If you want to selectively load things (eg on ye cheape ARM/MIPS
258 platforms where RAM is at a premium) you should:
261 * load the chip modules in question
262 * load ath_rate, ath_dfs
264 * load if_ath_pci and/or if_ath_ahb depending upon your particular
265 bus bind type - this is where probe/attach is done.
267 For further comments/feedback, poke adrian@ .
270 The "ino64" 64-bit inode project has been committed, which extends
271 a number of types to 64 bits. Upgrading in place requires care and
272 adherence to the documented upgrade procedure.
274 If using a custom kernel configuration ensure that the
275 COMPAT_FREEBSD11 option is included (as during the upgrade the
276 system will be running the ino64 kernel with the existing world).
278 For the safest in-place upgrade begin by removing previous build
279 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
280 full procedure documented below under the heading "To rebuild
281 everything and install it on the current system." Specifically,
282 a reboot is required after installing the new kernel before
286 The NATM framework including the en(4), fatm(4), hatm(4), and
287 patm(4) devices has been removed. Consumers should plan a
288 migration before the end-of-life date for FreeBSD 11.
291 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
292 diff has not been implemented, if those are needed a newer version of
293 GNU diff is available via the diffutils package under the gdiff name.
296 As of r316810 for ipfilter, keep frags is no longer assumed when
297 keep state is specified in a rule. r316810 aligns ipfilter with
298 documentation in man pages separating keep frags from keep state.
299 This allows keep state to be specified without forcing keep frags
300 and allows keep frags to be specified independently of keep state.
301 To maintain previous behaviour, also specify keep frags with
302 keep state (as documented in ipf.conf.5).
305 arm64 builds now use the base system LLD 4.0.0 linker by default,
306 instead of requiring that the aarch64-binutils port or package be
307 installed. To continue using aarch64-binutils, set
308 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
311 The UDP optimization in entry 20160818 that added the sysctl
312 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
313 packets will no longer be treated as L3 broadcast packets.
316 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
317 use any explicitly assigned loopback address available in the jail
318 instead of using the first assigned address of the jail.
321 The ctl.ko module no longer implements the iSCSI target frontend:
322 cfiscsi.ko does instead.
324 If building cfiscsi.ko as a kernel module, the module can be loaded
325 via one of the following methods:
326 - `cfiscsi_load="YES"` in loader.conf(5).
327 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
328 - ctladm(8)/ctld(8), when compiled with iSCSI support
329 (`WITH_ISCSI=yes` in src.conf(5))
331 Please see cfiscsi(4) for more details.
334 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
335 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
336 same source (previously, the dependency of mmcsd.ko on mmc.ko was
337 missing, but mmcsd.ko now will refuse to load if it is incompatible
341 The syntax of ipfw(8) named states was changed to avoid ambiguity.
342 If you have used named states in the firewall rules, you need to modify
343 them after installworld and before rebooting. Now named states must
344 be prefixed with colon.
347 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
348 removed as the userland we provide cannot use them. The KMS version
349 (sys/dev/drm2) supports the same hardware.
352 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
353 Please see the 20141231 entry below for information about prerequisites
354 and upgrading, if you are not already using clang 3.5.0 or higher.
357 The code that provides support for ZFS .zfs/ directory functionality
358 has been reimplemented. It's not possible now to create a snapshot
359 by mkdir under .zfs/snapshot/. That should be the only user visible
363 EISA bus support has been removed. The WITH_EISA option is no longer
367 MCA bus support has been removed.
370 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
371 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
374 The EM_MULTIQUEUE kernel configuration option is deprecated now that
375 the em(4) driver conforms to iflib specifications.
378 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
379 IFLIB. If you have a custom kernel configuration that excludes em(4)
380 but you use igb(4), you need to re-add em(4) to your custom configuration.
383 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
384 Please see the 20141231 entry below for information about prerequisites
385 and upgrading, if you are not already using clang 3.5.0 or higher.
388 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
389 Please see the 20141231 entry below for information about prerequisites
390 and upgrading, if you are not already using clang 3.5.0 or higher.
393 The layout of the pmap structure has changed for powerpc to put the pmap
394 statistics at the front for all CPU variations. libkvm(3) and all tools
395 that link against it need to be recompiled.
398 isl(4) and cyapa(4) drivers now require a new driver,
399 chromebook_platform(4), to work properly on Chromebook-class hardware.
400 On other types of hardware the drivers may need to be configured using
401 device hints. Please see the corresponding manual pages for details.
404 The urtwn(4) driver was merged into rtwn(4) and now consists of
405 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
407 Also, firmware for RTL8188CE was renamed due to possible name
408 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
411 GNU rcs has been removed from base. It is available as packages:
412 - rcs: Latest GPLv3 GNU rcs version.
413 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
417 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
418 modules now requires that the kernel configuration contain the
419 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
422 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
423 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
426 Relocatable object files with the extension of .So have been renamed
427 to use an extension of .pico instead. The purpose of this change is
428 to avoid a name clash with shared libraries on case-insensitive file
429 systems. On those file systems, foo.So is the same file as foo.so.
432 GNU rcs has been turned off by default. It can (temporarily) be built
433 again by adding WITH_RCS knob in src.conf.
434 Otherwise, GNU rcs is available from packages:
435 - rcs: Latest GPLv3 GNU rcs version.
436 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
439 The backup_uses_rcs functionality has been removed from rc.subr.
442 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
443 two separate components, QUEUE_MACRO_DEBUG_TRACE and
444 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
445 QUEUE_MACRO_DEBUG behavior.
448 r304787 changed some ioctl interfaces between the iSCSI userspace
449 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
450 rebuilt to work with new kernels. __FreeBSD_version has been bumped
454 The UDP receive code has been updated to only treat incoming UDP
455 packets that were addressed to an L2 broadcast address as L3
456 broadcast packets. It is not expected that this will affect any
457 standards-conforming UDP application. The new behaviour can be
458 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
462 Remove the openbsd_poll system call.
463 __FreeBSD_version has been bumped because of this.
466 The libc stub for the pipe(2) system call has been replaced with
467 a wrapper that calls the pipe2(2) system call and the pipe(2)
468 system call is now only implemented by the kernels that include
469 "options COMPAT_FREEBSD10" in their config file (this is the
470 default). Users should ensure that this option is enabled in
471 their kernel or upgrade userspace to r302092 before upgrading their
475 CAM will now strip leading spaces from SCSI disks' serial numbers.
476 This will affect users who create UFS filesystems on SCSI disks using
477 those disk's diskid device nodes. For example, if /etc/fstab
478 previously contained a line like
479 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
480 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
481 transforms like gmirror may also be affected. ZFS users should
485 The bitstring(3) API has been updated with new functionality and
486 improved performance. But it is binary-incompatible with the old API.
487 Objects built with the new headers may not be linked against objects
488 built with the old headers.
491 The brk and sbrk functions have been removed from libc on arm64.
492 Binutils from ports has been updated to not link to these
493 functions and should be updated to the latest version before
494 installing a new libc.
497 The armv6 port now defaults to hard float ABI. Limited support
498 for running both hardfloat and soft float on the same system
499 is available using the libraries installed with -DWITH_LIBSOFT.
500 This has only been tested as an upgrade path for installworld
501 and packages may fail or need manual intervention to run. New
502 packages will be needed.
504 To update an existing self-hosted armv6hf system, you must add
505 TARGET_ARCH=armv6 on the make command line for both the build
506 and the install steps.
509 Kernel modules compiled outside of a kernel build now default to
510 installing to /boot/modules instead of /boot/kernel. Many kernel
511 modules built this way (such as those in ports) already overrode
512 KMODDIR explicitly to install into /boot/modules. However,
513 manually building and installing a module from /sys/modules will
514 now install to /boot/modules instead of /boot/kernel.
517 The CAM I/O scheduler has been committed to the kernel. There should be
518 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
519 list of known rogues that claim support for this but actually corrupt
520 data is believed to be complete, be on the lookout for data
521 corruption. The known rogue list is believed to be complete:
523 o Crucial MX100, M550 drives with MU01 firmware.
524 o Micron M510 and M550 drives with MU01 firmware.
525 o Micron M500 prior to MU07 firmware
526 o Samsung 830, 840, and 850 all firmwares
527 o FCCT M500 all firmwares
529 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
530 with working NCQ TRIM. For Micron branded drives, see your sales rep for
531 updated firmware. Black listed drives will work correctly because these
532 drives work correctly so long as no NCQ TRIMs are sent to them. Given
533 this list is the same as found in Linux, it's believed there are no
534 other rogues in the market place. All other models from the above
537 To be safe, if you are at all concerned, you can quirk each of your
538 drives to prevent NCQ from being sent by setting:
539 kern.cam.ada.X.quirks="0x2"
540 in loader.conf. If the drive requires the 4k sector quirk, set the
544 The FAST_DEPEND build option has been removed and its functionality is
545 now the one true way. The old mkdep(1) style of 'make depend' has
546 been removed. See 20160311 for further details.
549 Resource range types have grown from unsigned long to uintmax_t. All
550 drivers, and anything using libdevinfo, need to be recompiled.
553 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
554 builds. It no longer runs mkdep(1) during 'make depend', and the
555 'make depend' stage can safely be skipped now as it is auto ran
556 when building 'make all' and will generate all SRCS and DPSRCS before
557 building anything else. Dependencies are gathered at compile time with
558 -MF flags kept in separate .depend files per object file. Users should
559 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
563 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
564 kernel modules. Therefore, if you load any kernel modules at boot time,
565 please install the boot loaders after you install the kernel, but before
569 make kernel KERNCONF=YOUR_KERNEL_HERE
570 make -C sys/boot install
571 <reboot in single user>
573 Then follow the usual steps, described in the General Notes section,
577 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
578 see the 20141231 entry below for information about prerequisites and
579 upgrading, if you are not already using clang 3.5.0 or higher.
582 The AIO subsystem is now a standard part of the kernel. The
583 VFS_AIO kernel option and aio.ko kernel module have been removed.
584 Due to stability concerns, asynchronous I/O requests are only
585 permitted on sockets and raw disks by default. To enable
586 asynchronous I/O requests on all file types, set the
587 vfs.aio.enable_unsafe sysctl to a non-zero value.
590 The ELF object manipulation tool objcopy is now provided by the
591 ELF Tool Chain project rather than by GNU binutils. It should be a
592 drop-in replacement, with the addition of arm64 support. The
593 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
594 to obtain the GNU version if necessary.
597 Building ZFS pools on top of zvols is prohibited by default. That
598 feature has never worked safely; it's always been prone to deadlocks.
599 Using a zvol as the backing store for a VM guest's virtual disk will
600 still work, even if the guest is using ZFS. Legacy behavior can be
601 restored by setting vfs.zfs.vol.recursive=1.
604 The NONE and HPN patches has been removed from OpenSSH. They are
605 still available in the security/openssh-portable port.
608 With the addition of ypldap(8), a new _ypldap user is now required
609 during installworld. "mergemaster -p" can be used to add the user
610 prior to installworld, as documented in the handbook.
613 The tftp loader (pxeboot) now uses the option root-path directive. As a
614 consequence it no longer looks for a pxeboot.4th file on the tftp
615 server. Instead it uses the regular /boot infrastructure as with the
619 The code to start recording plug and play data into the modules has
620 been committed. While the old tools will properly build a new kernel,
621 a number of warnings about "unknown metadata record 4" will be produced
622 for an older kldxref. To avoid such warnings, make sure to rebuild
623 the kernel toolchain (or world). Make sure that you have r292078 or
624 later when trying to build 292077 or later before rebuilding.
627 Debug data files are now built by default with 'make buildworld' and
628 installed with 'make installworld'. This facilitates debugging but
629 requires more disk space both during the build and for the installed
630 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
634 r291527 changed the internal interface between the nfsd.ko and
635 nfscommon.ko modules. As such, they must both be upgraded to-gether.
636 __FreeBSD_version has been bumped because of this.
639 Add support for unicode collation strings leads to a change of
640 order of files listed by ls(1) for example. To get back to the old
641 behaviour, set LC_COLLATE environment variable to "C".
643 Databases administrators will need to reindex their databases given
644 collation results will be different.
646 Due to a bug in install(1) it is recommended to remove the ancient
647 locales before running make installworld.
649 rm -rf /usr/share/locale/*
652 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
653 libcrypto.so.7 or libssl.so.7 must be recompiled.
656 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
657 Kernel modules isp_2400_multi and isp_2500_multi were removed and
658 should be replaced with isp_2400 and isp_2500 modules respectively.
661 The build previously allowed using 'make -n' to not recurse into
662 sub-directories while showing what commands would be executed, and
663 'make -n -n' to recursively show commands. Now 'make -n' will recurse
664 and 'make -N' will not.
667 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
668 and etcupdate will now use this file. A custom sendmail.cf is now
669 updated via this mechanism rather than via installworld. If you had
670 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
671 want to remove the exclusion or change it to "always install".
672 /etc/mail/sendmail.cf is now managed the same way regardless of
673 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
674 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
677 Compatibility shims for legacy ATA device names have been removed.
678 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
679 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
680 environment variables, /dev/ad* and /dev/ar* symbolic links.
683 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
684 Please see the 20141231 entry below for information about prerequisites
685 and upgrading, if you are not already using clang 3.5.0 or higher.
688 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
689 and renamed from .symbols to .debug. This reduces the size requirements
690 on the boot partition or file system and provides consistency with
691 userland debug files.
693 When using the supported kernel installation method the
694 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
695 as is done with /boot/kernel.
697 Developers wishing to maintain the historical behavior of installing
698 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
701 The wireless drivers had undergone changes that remove the 'parent
702 interface' from the ifconfig -l output. The rc.d network scripts
703 used to check presence of a parent interface in the list, so old
704 scripts would fail to start wireless networking. Thus, etcupdate(3)
705 or mergemaster(8) run is required after kernel update, to update your
706 rc.d scripts in /etc.
709 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
710 These configurations are now automatically interpreted as
711 'scrub fragment reassemble'.
714 Kernel-loadable modules for the random(4) device are back. To use
715 them, the kernel must have
718 options RANDOM_LOADABLE
720 kldload(8) can then be used to load random_fortuna.ko
721 or random_yarrow.ko. Please note that due to the indirect
722 function calls that the loadable modules need to provide,
723 the build-in variants will be slightly more efficient.
725 The random(4) kernel option RANDOM_DUMMY has been retired due to
726 unpopularity. It was not all that useful anyway.
729 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
730 Control over building the ELF Tool Chain tools is now provided by
731 the WITHOUT_TOOLCHAIN knob.
734 The polarity of Pulse Per Second (PPS) capture events with the
735 uart(4) driver has been corrected. Prior to this change the PPS
736 "assert" event corresponded to the trailing edge of a positive PPS
737 pulse and the "clear" event was the leading edge of the next pulse.
739 As the width of a PPS pulse in a typical GPS receiver is on the
740 order of 1 millisecond, most users will not notice any significant
741 difference with this change.
743 Anyone who has compensated for the historical polarity reversal by
744 configuring a negative offset equal to the pulse width will need to
745 remove that workaround.
748 The default group assigned to /dev/dri entries has been changed
749 from 'wheel' to 'video' with the id of '44'. If you want to have
750 access to the dri devices please add yourself to the video group
753 # pw groupmod video -m $USER
756 The menu.rc and loader.rc files will now be replaced during
757 upgrades. Please migrate local changes to menu.rc.local and
758 loader.rc.local instead.
761 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
762 strings and strip have been removed. The src.conf(5) knob
763 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
766 As ZFS requires more kernel stack pages than is the default on some
767 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
768 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
770 Please consider using 'options KSTACK_PAGES=X' where X is greater
771 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
774 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
775 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
776 default, i.e., they will not contain "::". For example, instead
777 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
778 to have a more specific match, such as different map entries for
779 IPv6:0:0 vs IPv6:0. This change requires that configuration
780 data (including maps, files, classes, custom ruleset, etc.) must
781 use the same format, so make certain such configuration data is
782 upgrading. As a very simple check search for patterns like
783 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
784 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
785 the cf option UseCompressedIPv6Addresses.
788 The default kernel entropy-processing algorithm is now
789 Fortuna, replacing Yarrow.
791 Assuming you have 'device random' in your kernel config
792 file, the configurations allow a kernel option to override
793 this default. You may choose *ONE* of:
795 options RANDOM_YARROW # Legacy /dev/random algorithm.
796 options RANDOM_DUMMY # Blocking-only driver.
798 If you have neither, you get Fortuna. For most people,
799 read no further, Fortuna will give a /dev/random that works
800 like it always used to, and the difference will be irrelevant.
802 If you remove 'device random', you get *NO* kernel-processed
803 entropy at all. This may be acceptable to folks building
804 embedded systems, but has complications. Carry on reading,
805 and it is assumed you know what you need.
807 *PLEASE* read random(4) and random(9) if you are in the
808 habit of tweaking kernel configs, and/or if you are a member
809 of the embedded community, wanting specific and not-usual
810 behaviour from your security subsystems.
812 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
813 random', you will NOT have a functioning /dev/random, and
814 many cryptographic features will not work, including SSH.
815 You may also find strange behaviour from the random(3) set
816 of library functions, in particular sranddev(3), srandomdev(3)
817 and arc4random(3). The reason for this is that the KERN_ARND
818 sysctl only returns entropy if it thinks it has some to
819 share, and with RANDOM_DUMMY or no 'device random' this
823 An additional fix for the issue described in the 20150614 sendmail
824 entry below has been committed in revision 284717.
827 FreeBSD's old make (fmake) has been removed from the system. It is
828 available as the devel/fmake port or via pkg install fmake.
831 The fix for the issue described in the 20150614 sendmail entry
832 below has been committed in revision 284436. The work
833 around described in that entry is no longer needed unless the
834 default setting is overridden by a confDH_PARAMETERS configuration
835 setting of '5' or pointing to a 512 bit DH parameter file.
838 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
839 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
840 and devel/kyua to version 0.20+ and adjust any calling code to work
841 with Kyuafile and kyua.
844 The import of openssl to address the FreeBSD-SA-15:10.openssl
845 security advisory includes a change which rejects handshakes
846 with DH parameters below 768 bits. sendmail releases prior
847 to 8.15.2 (not yet released), defaulted to a 512 bit
848 DH parameter setting for client connections. To work around
849 this interoperability, sendmail can be configured to use a
850 2048 bit DH parameter by:
852 1. Edit /etc/mail/`hostname`.mc
853 2. If a setting for confDH_PARAMETERS does not exist or
854 exists and is set to a string beginning with '5',
856 3. If a setting for confDH_PARAMETERS exists and is set to
857 a file path, create a new file with:
858 openssl dhparam -out /path/to/file 2048
859 4. Rebuild the .cf file:
860 cd /etc/mail/; make; make install
862 cd /etc/mail/; make restart
864 A sendmail patch is coming, at which time this file will be
868 Generation of legacy formatted entries have been disabled by default
869 in pwd_mkdb(8), as all base system consumers of the legacy formatted
870 entries were converted to use the new format by default when the new,
871 machine independent format have been added and supported since FreeBSD
874 Please see the pwd_mkdb(8) manual page for further details.
877 Clang and llvm have been upgraded to 3.6.1 release. Please see the
878 20141231 entry below for information about prerequisites and upgrading,
879 if you are not already using 3.5.0 or higher.
882 TI platform code switched to using vendor DTS files and this update
883 may break existing systems running on Beaglebone, Beaglebone Black,
886 - dtb files should be regenerated/reinstalled. Filenames are the
887 same but content is different now
888 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
889 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
890 addressing scheme is now pin 25 on /dev/gpioc3.
891 - Pandaboard: /etc/ttys should be updated, serial console device is
892 now /dev/ttyu2, not /dev/ttyu0
895 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
896 If you need the GNU extension from groff soelim(1), install groff
897 from package: pkg install groff, or via ports: textproc/groff.
900 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
901 defined in symlink(7); previously symlinks were silently ignored.
904 The const qualifier has been removed from iconv(3) to comply with
905 POSIX. The ports tree is aware of this from r384038 onwards.
908 Libraries specified by LIBADD in Makefiles must have a corresponding
909 DPADD_<lib> variable to ensure correct dependencies. This is now
910 enforced in src.libnames.mk.
913 From legacy ata(4) driver was removed support for SATA controllers
914 supported by more functional drivers ahci(4), siis(4) and mvs(4).
915 Kernel modules ataahci and ataadaptec were removed completely,
916 replaced by ahci and mvs modules respectively.
919 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
920 the 20141231 entry below for information about prerequisites and
921 upgrading, if you are not already using 3.5.0 or higher.
924 The 32-bit PowerPC kernel has been changed to a position-independent
925 executable. This can only be booted with a version of loader(8)
926 newer than January 31, 2015, so make sure to update both world and
927 kernel before rebooting.
930 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
931 but before r278950, the RNG was not seeded properly. Immediately
932 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
933 ssh keys or openssl keys) that were generated w/ a kernel from that
934 range. This does not affect programs that directly used /dev/random
935 or /dev/urandom. All userland uses of arc4random(3) are affected.
938 The autofs(4) ABI was changed in order to restore binary compatibility
939 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
943 The powerpc64 kernel has been changed to a position-independent
944 executable. This can only be booted with a new version of loader(8),
945 so make sure to update both world and kernel before rebooting.
948 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
949 only release, no new features have been added. Please see the 20141231
950 entry below for information about prerequisites and upgrading, if you
951 are not already using 3.5.0.
954 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
955 taken from the ELF Tool Chain project rather than GNU binutils. They
956 should be drop-in replacements, with the addition of arm64 support.
957 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
958 binutils tools, if necessary. See 20150805 for updated information.
961 The default Unbound configuration now enables remote control
962 using a local socket. Users who have already enabled the
963 local_unbound service should regenerate their configuration
964 by running "service local_unbound setup" as root.
967 The GNU texinfo and GNU info pages have been removed.
968 To be able to view GNU info pages please install texinfo from ports.
971 Clang, llvm and lldb have been upgraded to 3.5.0 release.
973 As of this release, a prerequisite for building clang, llvm and lldb is
974 a C++11 capable compiler and C++11 standard library. This means that to
975 be able to successfully build the cross-tools stage of buildworld, with
976 clang as the bootstrap compiler, your system compiler or cross compiler
977 should either be clang 3.3 or later, or gcc 4.8 or later, and your
978 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
981 On any standard FreeBSD 10.x or 11.x installation, where clang and
982 libc++ are on by default (that is, on x86 or arm), this should work out
985 On 9.x installations where clang is enabled by default, e.g. on x86 and
986 powerpc, libc++ will not be enabled by default, so libc++ should be
987 built (with clang) and installed first. If both clang and libc++ are
988 missing, build clang first, then use it to build libc++.
990 On 8.x and earlier installations, upgrade to 9.x first, and then follow
991 the instructions for 9.x above.
993 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
994 default, and do not build clang.
996 Many embedded systems are resource constrained, and will not be able to
997 build clang in a reasonable time, or in some cases at all. In those
998 cases, cross building bootable systems on amd64 is a workaround.
1000 This new version of clang introduces a number of new warnings, of which
1001 the following are most likely to appear:
1005 This warns in two cases, for both C and C++:
1006 * When the code is trying to take the absolute value of an unsigned
1007 quantity, which is effectively a no-op, and almost never what was
1008 intended. The code should be fixed, if at all possible. If you are
1009 sure that the unsigned quantity can be safely cast to signed, without
1010 loss of information or undefined behavior, you can add an explicit
1011 cast, or disable the warning.
1013 * When the code is trying to take an absolute value, but the called
1014 abs() variant is for the wrong type, which can lead to truncation.
1015 If you want to disable the warning instead of fixing the code, please
1016 make sure that truncation will not occur, or it might lead to unwanted
1019 -Wtautological-undefined-compare and
1020 -Wundefined-bool-conversion
1022 These warn when C++ code is trying to compare 'this' against NULL, while
1023 'this' should never be NULL in well-defined C++ code. However, there is
1024 some legacy (pre C++11) code out there, which actively abuses this
1025 feature, which was less strictly defined in previous C++ versions.
1027 Squid and openjdk do this, for example. The warning can be turned off
1028 for C++98 and earlier, but compiling the code in C++11 mode might result
1029 in unexpected behavior; for example, the parts of the program that are
1030 unreachable could be optimized away.
1033 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1034 kernel sources have been removed. The .h files remain, since some
1035 utilities include them. This will need to be fixed later.
1036 If "mount -t oldnfs ..." is attempted, it will fail.
1037 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1038 the utilities will report errors.
1041 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1042 directories to top level SUBDIR variable when their parent
1043 directory is included in LOCAL_DIRS. Users with build systems with
1044 such hierarchies and without SUBDIR entries in the parent
1045 directory Makefiles should add them or add the directories to
1049 faith(4) and faithd(8) have been removed from the base system. Faith
1050 has been obsolete for a very long time.
1053 vt(4), the new console driver, is enabled by default. It brings
1054 support for Unicode and double-width characters, as well as
1055 support for UEFI and integration with the KMS kernel video
1058 You may need to update your console settings in /etc/rc.conf,
1059 most probably the keymap. During boot, /etc/rc.d/syscons will
1060 indicate what you need to do.
1062 vt(4) still has issues and lacks some features compared to
1063 syscons(4). See the wiki for up-to-date information:
1064 https://wiki.freebsd.org/Newcons
1066 If you want to keep using syscons(4), you can do so by adding
1067 the following line to /boot/loader.conf:
1071 pjdfstest has been integrated into kyua as an opt-in test suite.
1072 Please see share/doc/pjdfstest/README for more details on how to
1076 gperf has been removed from the base system for architectures
1077 that use clang. Ports that require gperf will obtain it from the
1081 pjdfstest has been moved from tools/regression/pjdfstest to
1085 At svn r271982, The default linux compat kernel ABI has been adjusted
1086 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1087 update. If you wish to continue using the linux-f10 compat ports,
1088 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1089 encouraged to update their linux-compat packages to linux-c6 during
1090 their next update cycle.
1093 The ofwfb driver, used to provide a graphics console on PowerPC when
1094 using vt(4), no longer allows mmap() of all physical memory. This
1095 will prevent Xorg on PowerPC with some ATI graphics cards from
1096 initializing properly unless x11-servers/xorg-server is updated to
1100 The xdev targets have been converted to using TARGET and
1101 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1104 The default unbound configuration has been modified to address
1105 issues with reverse lookups on networks that use private
1106 address ranges. If you use the local_unbound service, run
1107 "service local_unbound setup" as root to regenerate your
1108 configuration, then "service local_unbound reload" to load the
1112 The GNU texinfo and GNU info pages are not built and installed
1113 anymore, WITH_INFO knob has been added to allow to built and install
1115 UPDATE: see 20150102 entry on texinfo's removal
1118 The GNU readline library is now an INTERNALLIB - that is, it is
1119 statically linked into consumers (GDB and variants) in the base
1120 system, and the shared library is no longer installed. The
1121 devel/readline port is available for third party software that
1125 The Itanium architecture (ia64) has been removed from the list of
1126 known architectures. This is the first step in the removal of the
1130 Commit r268115 has added NFSv4.1 server support, merged from
1131 projects/nfsv4.1-server. Since this includes changes to the
1132 internal interfaces between the NFS related modules, a full
1133 build of the kernel and modules will be necessary.
1134 __FreeBSD_version has been bumped.
1137 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1138 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1139 which differs from the behaviour controlled by this knob.)
1142 Maximal length of the serial number in CTL was increased from 16 to
1143 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1144 and ctld, need to be rebuilt to work with a new kernel.
1147 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1148 1 respectively to match the upstream numbers. They were out of
1149 sync because, when they were originally added to FreeBSD, the
1150 upstream versions were not respected. These libraries are private
1151 and not yet built by default, so renumbering them should be a
1152 non-issue. However, unclean source trees will yield broken test
1153 programs once the operator executes "make delete-old-libs" after a
1154 "make installworld".
1156 Additionally, the atf-sh binary was made private by moving it into
1157 /usr/libexec/. Already-built shell test programs will keep the
1158 path to the old binary so they will break after "make delete-old"
1161 If you are using WITH_TESTS=yes (not the default), wipe the object
1162 tree and rebuild from scratch to prevent spurious test failures.
1163 This is only needed once: the misnumbered libraries and misplaced
1164 binaries have been added to OptionalObsoleteFiles.inc so they will
1165 be removed during a clean upgrade.
1168 Clang and llvm have been upgraded to 3.4.1 release.
1171 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1172 be removed to avoid issues in the future (and has been added to
1176 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1177 past, it affected all builds that used the bsd.*.mk files. The old
1178 behavior was a bug, but people may have relied upon it. To get this
1179 behavior back, you can .include /etc/src.conf from /etc/make.conf
1180 (which is still global and isn't changed). This also changes the
1181 behavior of incremental builds inside the tree of individual
1182 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1183 Although this has survived make universe and some upgrade scenarios,
1184 other upgrade scenarios may have broken. At least one form of
1185 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1186 as well... In cases where MAKESYSPATH isn't working with this
1187 setting, you'll need to set it to the full path to your tree.
1189 One side effect of all this cleaning up is that bsd.compiler.mk
1190 is no longer implicitly included by bsd.own.mk. If you wish to
1191 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1195 The lindev device has been removed since /dev/full has been made a
1196 standard device. __FreeBSD_version has been bumped.
1199 The knob WITHOUT_VI was added to the base system, which controls
1200 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1201 in order to reorder files share/termcap and didn't build ex(1) as a
1202 build tool, so building/installing with WITH_VI is highly advised for
1203 build hosts for older releases.
1205 This issue has been fixed in stable/9 and stable/10 in r277022 and
1206 r276991, respectively.
1209 The YES_HESIOD knob has been removed. It has been obsolete for
1210 a decade. Please move to using WITH_HESIOD instead or your builds
1211 will silently lack HESIOD.
1214 The uart(4) driver has been changed with respect to its handling
1215 of the low-level console. Previously the uart(4) driver prevented
1216 any process from changing the baudrate or the CLOCAL and HUPCL
1217 control flags. By removing the restrictions, operators can make
1218 changes to the serial console port without having to reboot.
1219 However, when getty(8) is started on the serial device that is
1220 associated with the low-level console, a misconfigured terminal
1221 line in /etc/ttys will now have a real impact.
1222 Before upgrading the kernel, make sure that /etc/ttys has the
1223 serial console device configured as 3wire without baudrate to
1224 preserve the previous behaviour. E.g:
1225 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1228 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1229 to improve performance. To re-enable it, if needed, run rpcbind
1230 with command line option -W.
1233 Switched back to the GPL dtc compiler due to updates in the upstream
1234 dts files not being supported by the BSDL dtc compiler. You will need
1235 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1236 may result while building dtb files during a kernel build if you fail
1237 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1240 Clang and llvm have been upgraded to 3.4 release.
1243 The nve(4) driver has been removed. Please use the nfe(4) driver
1244 for NVIDIA nForce MCP Ethernet adapters instead.
1247 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1248 This could cause certain C++ applications using shared libraries built
1249 against the previous version of libc++ to crash. The incompatibility
1250 has now been fixed, but any C++ applications or shared libraries built
1251 between r261283 and r261801 should be recompiled.
1254 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1255 capability mode support. Please note that enabling the feature in
1256 kernel is still highly recommended.
1259 OpenSSH is now built with sandbox support, and will use sandbox as
1260 the default privilege separation method. This requires Capsicum
1261 capability mode support in kernel.
1264 The libelf and libdwarf libraries have been updated to newer
1265 versions from upstream. Shared library version numbers for
1266 these two libraries were bumped. Any ports or binaries
1267 requiring these two libraries should be recompiled.
1268 __FreeBSD_version is bumped to 1100006.
1271 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1272 instead of providing an explicit one, this would prevent such
1273 Makefile from providing its own Kyuafile in the future during
1274 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1275 intervention is needed to clean an objdir if you use NO_CLEAN:
1276 # find /usr/obj -name Kyuafile | xargs rm -f
1279 The behavior of gss_pseudo_random() for the krb5 mechanism
1280 has changed, for applications requesting a longer random string
1281 than produced by the underlying enctype's pseudo-random() function.
1282 In particular, the random string produced from a session key of
1283 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1284 be different at the 17th octet and later, after this change.
1285 The counter used in the PRF+ construction is now encoded as a
1286 big-endian integer in accordance with RFC 4402.
1287 __FreeBSD_version is bumped to 1100004.
1290 The WITHOUT_ATF build knob has been removed and its functionality
1291 has been subsumed into the more generic WITHOUT_TESTS. If you were
1292 using the former to disable the build of the ATF libraries, you
1293 should change your settings to use the latter.
1296 The default version of mtree is nmtree which is obtained from
1297 NetBSD. The output is generally the same, but may vary
1298 slightly. If you found you need identical output adding
1299 "-F freebsd9" to the command line should do the trick. For the
1300 time being, the old mtree is available as fmtree.
1303 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1304 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1305 1.1.4_8 and verify bsdyml not linked in, before running "make
1307 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1309 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1312 The stable/10 branch has been created in subversion from head
1316 The rc.d/jail script has been updated to support jail(8)
1317 configuration file. The "jail_<jname>_*" rc.conf(5) variables
1318 for per-jail configuration are automatically converted to
1319 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
1320 This is transparently backward compatible. See below about some
1321 incompatibilities and rc.conf(5) manual page for more details.
1323 These variables are now deprecated in favor of jail(8) configuration
1324 file. One can use "rc.d/jail config <jname>" command to generate
1325 a jail(8) configuration file in /var/run/jail.<jname>.conf without
1326 running the jail(8) utility. The default pathname of the
1327 configuration file is /etc/jail.conf and can be specified by
1328 using $jail_conf or $jail_<jname>_conf variables.
1330 Please note that jail_devfs_ruleset accepts an integer at
1331 this moment. Please consider to rewrite the ruleset name
1335 BIND has been removed from the base system. If all you need
1336 is a local resolver, simply enable and start the local_unbound
1337 service instead. Otherwise, several versions of BIND are
1338 available in the ports tree. The dns/bind99 port is one example.
1340 With this change, nslookup(1) and dig(1) are no longer in the base
1341 system. Users should instead use host(1) and drill(1) which are
1342 in the base system. Alternatively, nslookup and dig can
1343 be obtained by installing the dns/bind-tools port.
1346 With the addition of unbound(8), a new unbound user is now
1347 required during installworld. "mergemaster -p" can be used to
1348 add the user prior to installworld, as documented in the handbook.
1351 OpenSSH is now built with DNSSEC support, and will by default
1352 silently trust signed SSHFP records. This can be controlled with
1353 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1354 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1357 The GNU Compiler Collection and C++ standard library (libstdc++)
1358 are no longer built by default on platforms where clang is the system
1359 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1360 options in src.conf.
1363 The PROCDESC kernel option is now part of the GENERIC kernel
1364 configuration and is required for the rwhod(8) to work.
1365 If you are using custom kernel configuration, you should include
1369 The API and ABI related to the Capsicum framework was modified
1370 in backward incompatible way. The userland libraries and programs
1371 have to be recompiled to work with the new kernel. This includes the
1372 following libraries and programs, but the whole buildworld is
1373 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1374 kdump, procstat, rwho, rwhod, uniq.
1377 AES-NI intrinsic support has been added to gcc. The AES-NI module
1378 has been updated to use this support. A new gcc is required to build
1379 the aesni module on both i386 and amd64.
1382 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1383 Thus "device padlock_rng" and "device rdrand_rng" should be
1384 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1387 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1388 enables just the iconv* functionality and is now on by default.
1389 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1390 compatibility. Set WITHOUT_ICONV to build the old way.
1391 If you have been using WITH_ICONV before, you will very likely
1392 need to turn on WITH_LIBICONV_COMPAT.
1395 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1396 Illumos origin, including ZFS. If you have INVARIANTS in your
1397 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1399 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1400 locks if WITNESS option was set. Because that generated a lot of
1401 witness(9) reports and all of them were believed to be false
1402 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1403 can be used to achieve the previous behavior.
1406 Timer values in IPv6 data structures now use time_uptime instead
1407 of time_second. Although this is not a user-visible functional
1408 change, userland utilities which directly use them---ndp(8),
1409 rtadvd(8), and rtsold(8) in the base system---need to be updated
1410 to r253970 or later.
1413 find -delete can now delete the pathnames given as arguments,
1414 instead of only files found below them or if the pathname did
1415 not contain any slashes. Formerly, the following error message
1418 find: -delete: <path>: relative path potentially not safe
1420 Deleting the pathnames given as arguments can be prevented
1421 without error messages using -mindepth 1 or by changing
1422 directory and passing "." as argument to find. This works in the
1423 old as well as the new version of find.
1426 Behavior of devfs rules path matching has been changed.
1427 Pattern is now always matched against fully qualified devfs
1428 path and slash characters must be explicitly matched by
1429 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1430 subdirectories must be reviewed.
1433 The default ARM ABI has changed to the ARM EABI. The old ABI is
1434 incompatible with the ARM EABI and all programs and modules will
1435 need to be rebuilt to work with a new kernel.
1437 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1439 NOTE: Support for the old ABI will be removed in the future and
1440 users are advised to upgrade.
1443 pkg_install has been disconnected from the build if you really need it
1444 you should add WITH_PKGTOOLS in your src.conf(5).
1447 Most of network statistics structures were changed to be able
1448 keep 64-bits counters. Thus all tools, that work with networking
1449 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1452 Fix a bug that allowed a tracing process (e.g. gdb) to write
1453 to a memory-mapped file in the traced process's address space
1454 even if neither the traced process nor the tracing process had
1455 write access to that file.
1458 CVS has been removed from the base system. An exact copy
1459 of the code is available from the devel/cvs port.
1462 Some people report the following error after the switch to bmake:
1464 make: illegal option -- J
1465 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1467 *** [buildworld] Error code 2
1469 this likely due to an old instance of make in
1470 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1471 which src/Makefile will use that blindly, if it exists, so if
1472 you see the above error:
1474 rm -rf `make -V MAKEPATH`
1479 Use bmake by default.
1480 Whereas before one could choose to build with bmake via
1481 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1482 make. The goal is to remove these knobs for 10-RELEASE.
1484 It is worth noting that bmake (like gmake) treats the command
1485 line as the unit of failure, rather than statements within the
1486 command line. Thus '(cd some/where && dosomething)' is safer
1487 than 'cd some/where; dosomething'. The '()' allows consistent
1488 behavior in parallel build.
1491 Fix a bug that allows NFS clients to issue READDIR on files.
1494 The WITHOUT_IDEA option has been removed because
1495 the IDEA patent expired.
1498 The sysctl which controls TRIM support under ZFS has been renamed
1499 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1503 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1504 rather than creating it's own in the temporary directory in
1505 order allow access to bootstrapped versions of tools such as
1506 install and mtree. When upgrading from version of FreeBSD where
1507 the install command does not support -l, you will need to
1508 install a new mergemaster command if mergemaster -p is required.
1509 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1513 Legacy ATA stack, disabled and replaced by new CAM-based one since
1514 FreeBSD 9.0, completely removed from the sources. Kernel modules
1515 atadisk and atapi*, user-level tools atacontrol and burncd are
1516 removed. Kernel option `options ATA_CAM` is now permanently enabled
1520 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1521 and socketpair(2). Software, in particular Kerberos, may
1522 automatically detect and use these during building. The resulting
1523 binaries will not work on older kernels.
1526 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1527 information, see the respective 20130304 entry).
1530 Recent commits to callout(9) changed the size of struct callout,
1531 so the KBI is probably heavily disturbed. Also, some functions
1532 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1533 by macros. Every kernel module using it won't load, so rebuild
1536 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1537 but does not initialize by default (because of the new CTL_DISABLE
1538 option) to save memory. To re-enable it, remove the CTL_DISABLE
1539 option from the kernel config file or set kern.cam.ctl.disable=0
1540 in /boot/loader.conf.
1543 The ctl device has been disabled in GENERIC for i386 and amd64.
1544 This was done due to the extra memory being allocated at system
1545 initialisation time by the ctl driver which was only used if
1546 a CAM target device was created. This makes a FreeBSD system
1547 unusable on 128MB or less of RAM.
1550 A new compression method (lz4) has been merged to -HEAD. Please
1551 refer to zpool-features(7) for more information.
1553 Please refer to the "ZFS notes" section of this file for information
1554 on upgrading boot ZFS pools.
1557 A BSD-licensed patch(1) variant has been added and is installed
1558 as bsdpatch, being the GNU version the default patch.
1559 To inverse the logic and use the BSD-licensed one as default,
1560 while having the GNU version installed as gnupatch, rebuild
1561 and install world with the WITH_BSD_PATCH knob set.
1564 Due to the use of the new -l option to install(1) during build
1565 and install, you must take care not to directly set the INSTALL
1566 make variable in your /etc/make.conf, /etc/src.conf, or on the
1567 command line. If you wish to use the -C flag for all installs
1568 you may be able to add INSTALL+=-C to /etc/make.conf or
1572 The install(1) option -M has changed meaning and now takes an
1573 argument that is a file or path to append logs to. In the
1574 unlikely event that -M was the last option on the command line
1575 and the command line contained at least two files and a target
1576 directory the first file will have logs appended to it. The -M
1577 option served little practical purpose in the last decade so its
1578 use is expected to be extremely rare.
1581 After switching to Clang as the default compiler some users of ZFS
1582 on i386 systems started to experience stack overflow kernel panics.
1583 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1586 GEOM_LABEL now mangles label names read from file system metadata.
1587 Mangling affect labels containing spaces, non-printable characters,
1588 '%' or '"'. Device names in /etc/fstab and other places may need to
1592 By default, only the 10 most recent kernel dumps will be saved. To
1593 restore the previous behaviour (no limit on the number of kernel dumps
1594 stored in the dump directory) add the following line to /etc/rc.conf:
1599 With the addition of auditdistd(8), a new auditdistd user is now
1600 required during installworld. "mergemaster -p" can be used to
1601 add the user prior to installworld, as documented in the handbook.
1604 The sin6_scope_id member variable in struct sockaddr_in6 is now
1605 filled by the kernel before passing the structure to the userland via
1606 sysctl or routing socket. This means the KAME-specific embedded scope
1607 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1608 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1609 __FreeBSD_version is bumped to 1000025.
1612 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1613 This means that the world and kernel will be compiled with clang
1614 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1615 and /usr/bin/cpp. To disable this behavior and revert to building
1616 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1617 of current may need to bootstrap WITHOUT_CLANG first if the clang
1618 build fails (its compatibility window doesn't extend to the 9 stable
1622 The IPFIREWALL_FORWARD kernel option has been removed. Its
1623 functionality now turned on by default.
1626 The ZERO_COPY_SOCKET kernel option has been removed and
1627 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1628 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1629 mechanism which is not safe and may result in kernel crashes.
1630 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1631 driver supports disposeable external page sized mbuf storage.
1632 Proper replacements for both zero-copy mechanisms are under
1633 consideration and will eventually lead to complete removal
1634 of the two kernel options.
1637 The IPv4 network stack has been converted to network byte
1638 order. The following modules need to be recompiled together
1639 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1640 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1643 Support for non-MPSAFE filesystems was removed from VFS. The
1644 VFS_VERSION was bumped, all filesystem modules shall be
1648 All the non-MPSAFE filesystems have been disconnected from
1649 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1650 portalfs, smbfs, xfs.
1653 The interface cloning API and ABI has changed. The following
1654 modules need to be recompiled together with kernel:
1655 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1656 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1657 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1660 The sdhci driver was split in two parts: sdhci (generic SD Host
1661 Controller logic) and sdhci_pci (actual hardware driver).
1662 No kernel config modifications are required, but if you
1663 load sdhc as a module you must switch to sdhci_pci instead.
1666 Import the FUSE kernel and userland support into base system.
1669 The GNU sort(1) program has been removed since the BSD-licensed
1670 sort(1) has been the default for quite some time and no serious
1671 problems have been reported. The corresponding WITH_GNU_SORT
1675 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1676 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1680 The net80211(4) ABI has been changed to allow for improved driver
1681 PS-POLL and power-save support. All wireless drivers need to be
1682 recompiled to work with the new kernel.
1685 The random(4) support for the VIA hardware random number
1686 generator (`PADLOCK') is no longer enabled unconditionally.
1687 Add the padlock_rng device in the custom kernel config if
1688 needed. The GENERIC kernels on i386 and amd64 do include the
1689 device, so the change only affects the custom kernel
1693 The pf(4) packet filter ABI has been changed. pfctl(8) and
1694 snmp_pf module need to be recompiled to work with new kernel.
1697 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1698 to -HEAD. Pools that have empty_bpobj in active state can not be
1699 imported read-write with ZFS implementations that do not support
1700 this feature. For more information read the zpool-features(5)
1704 The sparc64 ZFS loader has been changed to no longer try to auto-
1705 detect ZFS providers based on diskN aliases but now requires these
1706 to be explicitly listed in the OFW boot-device environment variable.
1709 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1710 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1711 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1714 The following sysctls and tunables have been renamed for consistency
1715 with other variables:
1716 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1717 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1720 The sort utility has been replaced with BSD sort. For now, GNU sort
1721 is also available as "gnusort" or the default can be set back to
1722 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1723 installed as "bsdsort".
1726 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1727 Starting with this version the old system of ZFS pool versioning
1728 is superseded by "feature flags". This concept enables forward
1729 compatibility against certain future changes in functionality of ZFS
1730 pools. The first read-only compatible "feature flag" for ZFS pools
1731 is named "com.delphix:async_destroy". For more information
1732 read the new zpool-features(5) manual page.
1733 Please refer to the "ZFS notes" section of this file for information
1734 on upgrading boot ZFS pools.
1737 The malloc(3) implementation embedded in libc now uses sources imported
1738 as contrib/jemalloc. The most disruptive API change is to
1739 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1740 delete it prior to installworld, and optionally re-create it using the
1741 new format after rebooting. See malloc.conf(5) for details
1742 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1746 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1747 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1748 now spelled mips. This is to aid compatibility with third-party
1749 software that expects this naming scheme in uname(3). Little-endian
1750 settings are unchanged. If you are updating a big-endian mips64 machine
1751 from before this change, you may need to set MACHINE_ARCH=mips64 in
1752 your environment before the new build system will recognize your machine.
1755 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1759 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1760 nullfs(5) did not pass through all behaviours to the underlying layer,
1761 as a result if we bound to a socket on the lower layer we could connect
1762 only to the lower path; if we bound to the upper layer we could connect
1763 only to the upper path. The new behavior is one can connect to both the
1764 lower and the upper paths regardless what layer path one binds to.
1767 The getifaddrs upgrade path broken with 20111215 has been restored.
1768 If you have upgraded in between 20111215 and 20120209 you need to
1769 recompile libc again with your kernel. You still need to recompile
1770 world to be able to configure CARP but this restriction already
1771 comes from 20111215.
1774 The set_rcvar() function has been removed from /etc/rc.subr. All
1775 base and ports rc.d scripts have been updated, so if you have a
1776 port installed with a script in /usr/local/etc/rc.d you can either
1777 hand-edit the rcvar= line, or reinstall the port.
1779 An easy way to handle the mass-update of /etc/rc.d:
1780 rm /etc/rc.d/* && mergemaster -i
1783 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1784 on the current CPU and prevents other threads from running.
1785 This behavior can be reverted using the kern.stop_scheduler_on_panic
1787 The new behavior can be incompatible with kern.sync_on_panic.
1790 The carp(4) facility has been changed significantly. Configuration
1791 of the CARP protocol via ifconfig(8) has changed, as well as format
1792 of CARP events submitted to devd(8) has changed. See manual pages
1793 for more information. The arpbalance feature of carp(4) is currently
1794 not supported anymore.
1796 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1797 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1798 need to be recompiled.
1801 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1805 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1806 explicitely support non-MPSAFE filesystems.
1807 It is on by default for all supported platform at this present
1811 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1812 i386 and pc98 GENERIC kernel configuration files.
1815 sysinstall has been removed
1818 The stable/9 branch created in subversion. This corresponds to the
1819 RELENG_9 branch in CVS.
1825 Avoid using make -j when upgrading. While generally safe, there are
1826 sometimes problems using -j to upgrade. If your upgrade fails with
1827 -j, please try again without -j. From time to time in the past there
1828 have been problems using -j with buildworld and/or installworld. This
1829 is especially true when upgrading between "distant" versions (eg one
1830 that cross a major release boundary or several minor releases, or when
1831 several months have passed on the -current branch).
1833 Sometimes, obscure build problems are the result of environment
1834 poisoning. This can happen because the make utility reads its
1835 environment when searching for values for global variables. To run
1836 your build attempts in an "environmental clean room", prefix all make
1837 commands with 'env -i '. See the env(1) manual page for more details.
1839 When upgrading from one major version to another it is generally best to
1840 upgrade to the latest code in the currently installed branch first, then
1841 do an upgrade to the new branch. This is the best-tested upgrade path,
1842 and has the highest probability of being successful. Please try this
1843 approach if you encounter problems with a major version upgrade. Since
1844 the stable 4.x branch point, one has generally been able to upgade from
1845 anywhere in the most recent stable branch to head / current (or even the
1846 last couple of stable branches). See the top of this file when there's
1849 When upgrading a live system, having a root shell around before
1850 installing anything can help undo problems. Not having a root shell
1851 around can lead to problems if pam has changed too much from your
1852 starting point to allow continued authentication after the upgrade.
1854 This file should be read as a log of events. When a later event changes
1855 information of a prior event, the prior event should not be deleted.
1856 Instead, a pointer to the entry with the new information should be
1857 placed in the old entry. Readers of this file should also sanity check
1858 older entries before relying on them blindly. Authors of new entries
1859 should write them with this in mind.
1863 When upgrading the boot ZFS pool to a new version, always follow
1866 1.) recompile and reinstall the ZFS boot loader and boot block
1867 (this is part of "make buildworld" and "make installworld")
1869 2.) update the ZFS boot block on your boot drive
1871 The following example updates the ZFS boot block on the first
1872 partition (freebsd-boot) of a GPT partitioned drive ada0:
1873 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1875 Non-boot pools do not need these updates.
1879 If you are updating from a prior version of FreeBSD (even one just
1880 a few days old), you should follow this procedure. It is the most
1881 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1883 make kernel-toolchain
1884 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1885 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1887 To test a kernel once
1888 ---------------------
1889 If you just want to boot a kernel once (because you are not sure
1890 if it works, or if you want to boot a known bad kernel to provide
1891 debugging information) run
1892 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1893 nextboot -k testkernel
1895 To rebuild everything and install it on the current system.
1896 -----------------------------------------------------------
1897 # Note: sometimes if you are running current you gotta do more than
1898 # is listed here if you are upgrading from a really old current.
1900 <make sure you have good level 0 dumps>
1902 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1903 make installkernel KERNCONF=YOUR_KERNEL_HERE
1905 <reboot in single user> [3]
1912 To cross-install current onto a separate partition
1913 --------------------------------------------------
1914 # In this approach we use a separate partition to hold
1915 # current's root, 'usr', and 'var' directories. A partition
1916 # holding "/", "/usr" and "/var" should be about 2GB in
1919 <make sure you have good level 0 dumps>
1922 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1923 <maybe newfs current's root partition>
1924 <mount current's root partition on directory ${CURRENT_ROOT}>
1925 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1926 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1927 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1928 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1929 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1930 <reboot into current>
1931 <do a "native" rebuild/install as described in the previous section>
1932 <maybe install compatibility libraries from ports/misc/compat*>
1936 To upgrade in-place from stable to current
1937 ----------------------------------------------
1938 <make sure you have good level 0 dumps>
1940 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1942 <reboot in single user> [3]
1949 Make sure that you've read the UPDATING file to understand the
1950 tweaks to various things you need. At this point in the life
1951 cycle of current, things change often and you are on your own
1952 to cope. The defaults can also change, so please read ALL of
1953 the UPDATING entries.
1955 Also, if you are tracking -current, you must be subscribed to
1956 freebsd-current@freebsd.org. Make sure that before you update
1957 your sources that you have read and understood all the recent
1958 messages there. If in doubt, please track -stable which has
1959 much fewer pitfalls.
1961 [1] If you have third party modules, such as vmware, you
1962 should disable them at this point so they don't crash your
1965 [3] From the bootblocks, boot -s, and then do
1970 adjkerntz -i # if CMOS is wall time
1971 Also, when doing a major release upgrade, it is required that
1972 you boot into single user mode to do the installworld.
1974 [4] Note: This step is non-optional. Failure to do this step
1975 can result in a significant reduction in the functionality of the
1976 system. Attempting to do it by hand is not recommended and those
1977 that pursue this avenue should read this file carefully, as well
1978 as the archives of freebsd-current and freebsd-hackers mailing lists
1979 for potential gotchas. The -U option is also useful to consider.
1980 See mergemaster(8) for more information.
1982 [5] Usually this step is a noop. However, from time to time
1983 you may need to do this if you get unknown user in the following
1984 step. It never hurts to do it all the time. You may need to
1985 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1986 install) after the buildworld before this step if you last updated
1987 from current before 20130425 or from -stable before 20130430.
1989 [6] This only deletes old files and directories. Old libraries
1990 can be deleted by "make delete-old-libs", but you have to make
1991 sure that no program is using those libraries anymore.
1993 [8] In order to have a kernel that can run the 4.x binaries needed to
1994 do an installworld, you must include the COMPAT_FREEBSD4 option in
1995 your kernel. Failure to do so may leave you with a system that is
1996 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1997 required to run the 5.x binaries on more recent kernels. And so on
1998 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2000 Make sure that you merge any new devices from GENERIC since the
2001 last time you updated your kernel config file.
2003 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2004 "?=" instead of the "=" assignment operator, so that buildworld can
2005 override the CPUTYPE if it needs to.
2007 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2008 not on the command line, or in /etc/make.conf. buildworld will
2009 warn if it is improperly defined.
2012 This file contains a list, in reverse chronological order, of major
2013 breakages in tracking -current. It is not guaranteed to be a complete
2014 list of such breakages, and only contains entries since September 23, 2011.
2015 If you need to see UPDATING entries from before that date, you will need
2016 to fetch an UPDATING file from an older FreeBSD release.
2018 Copyright information:
2020 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2022 Redistribution, publication, translation and use, with or without
2023 modification, in full or in part, in any form or format of this
2024 document are permitted without further permission from the author.
2026 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2027 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2028 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2029 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2030 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2031 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2032 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2033 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2034 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2035 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2036 POSSIBILITY OF SUCH DAMAGE.
2038 Contact Warner Losh if you have any questions about your use of