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 The naive and non-compliant support of posix_fallocate(2) in ZFS
56 has been removed as of r325320. The system call now returns EINVAL
57 when used on a ZFS file. Although the new behavior complies with the
58 standard, some consumers are not prepared to cope with it.
59 One known victim is lld prior to r325420.
62 Building in a FreeBSD src checkout will automatically create object
63 directories now rather than store files in the current directory if
64 'make obj' was not ran. Calling 'make obj' is no longer necesarry.
65 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
66 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
70 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
71 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
72 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
73 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
74 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
75 The UNIFIED_OBJDIR option is a transitional feature that will be
76 removed for 12.0 release; please migrate to the new format for any
77 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
78 than hardcoding paths.
81 The native-xtools target no longer installs the files by default to the
82 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
83 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
86 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
87 options are changing from controlling the build if defined / undefined
88 to controlling the build with explicit 'yes' or 'no' values. They will
89 shift to WITH/WITHOUT options to match other options in the system.
92 libstand has turned into a private library for sys/boot use only.
93 It is no longer supported as a public interface outside of sys/boot.
96 The arm port has split armv6 into armv6 and armv7. armv7 is now
97 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
98 and are running a kernel from before r324363, you will need to add
99 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
102 When building multiple kernels using KERNCONF, non-existent KERNCONF
103 files will produce an error and buildkernel will fail. Previously
104 missing KERNCONF files silently failed giving no indication as to
105 why, only to subsequently discover during installkernel that the
106 desired kernel was never built in the first place.
109 The default serial number format for CTL LUNs has changed. This will
110 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
111 or iSCSI clients care about their LUNs' serial numbers. Users who
112 require serial number stability should hardcode serial numbers in
116 For 32-bit arm compiled for hard-float support, soft-floating point
117 binaries now always get their shared libraries from
118 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
119 /usr/libsoft also existed). Only users with a hard-float ld.so, but
120 soft-float everything else should be affected.
123 The geli password typed at boot is now hidden. To restore the previous
124 behavior, see geli(8) for configuration options.
127 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
128 sysctl values. Minor nit, but requires a rebuild of both world/kernel
132 "make check" behavior (made in ^/head@r295380) has been changed to
133 execute from a limited sandbox, as opposed to executing from
137 - The "beforecheck" and "aftercheck" targets are now specified.
138 - ${CHECKDIR} (added in commit noted above) has been removed.
139 - Legacy behavior can be enabled by setting
140 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
142 If the limited sandbox mode is enabled, "make check" will execute
143 "make distribution", then install, execute the tests, and clean up the
144 sandbox if successful.
146 The "make distribution" and "make install" targets are typically run as
147 root to set appropriate permissions and ownership at installation time.
148 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
149 environment if executing "make check" with limited sandbox mode using
150 an unprivileged user.
153 Since the switch to GPT disk labels, fsck for UFS/FFS has been
154 unable to automatically find alternate superblocks. As of r322297,
155 the information needed to find alternate superblocks has been
156 moved to the end of the area reserved for the boot block.
157 Filesystems created with a newfs of this vintage or later
158 will create the recovery information. If you have a filesystem
159 created prior to this change and wish to have a recovery block
160 created for your filesystem, you can do so by running fsck in
161 forground mode (i.e., do not use the -p or -y options). As it
162 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
163 to which you should answer yes.
166 As of r321665, an NFSv4 server configuration that services
167 Kerberos mounts or clients that do not support the uid/gid in
168 owner/owner_group string capability, must explicitly enable
169 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
170 machine's /etc/rc.conf file.
173 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
174 Please see the 20141231 entry below for information about prerequisites
175 and upgrading, if you are not already using clang 3.5.0 or higher.
178 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
179 r-commands (rlogin, rsh, etc.) to be built with the base system.
182 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
183 a very major ABI incompatible change, so users of FreeBSD/powerpc must
184 be careful when performing source upgrades. It is best to run
185 'make installworld' from an alternate root system, either a live
186 CD/memory stick, or a temporary root partition. Additionally, all ports
187 must be recompiled. powerpc64 is largely unaffected, except in the case
188 of 32-bit compatibility. All 32-bit binaries will be affected.
191 Forward compatibility for the "ino64" project have been committed. This
192 will allow most new binaries to run on older kernels in a limited
193 fashion. This prevents many of the common foot-shooting actions in the
194 upgrade as well as the limited ability to roll back the kernel across
195 the ino64 upgrade. Complicated use cases may not work properly, though
196 enough simpler ones work to allow recovery in most situations.
199 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
200 if you require the GPL compiler.
203 The internal ABI used for communication between the NFS kernel modules
204 was changed by r320085, so __FreeBSD_version was bumped to
205 ensure all the NFS related modules are updated together.
208 The ABI of struct event was changed by extending the data
209 member to 64bit and adding ext fields. For upgrade, same
210 precautions as for the entry 20170523 "ino64" must be
214 The GNU roff toolchain has been removed from base. To render manpages
215 which are not supported by mandoc(1), man(1) can fallback on GNU roff
216 from ports (and recommends to install it).
217 To render roff(7) documents, consider using GNU roff from ports or the
218 heirloom doctools roff toolchain from ports via pkg install groff or
219 via pkg install heirloom-doctools.
222 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
223 smaller runtime footprint builds. This is useful for embedded systems
224 which only require one chipset support.
226 If you load it as a module, make sure this is in /boot/loader.conf:
230 This will load the HAL, all chip/RF backends and if_ath_pci.
231 If you have if_ath_pci in /boot/loader.conf, ensure it is after
232 if_ath or it will not load any HAL chipset support.
234 If you want to selectively load things (eg on ye cheape ARM/MIPS
235 platforms where RAM is at a premium) you should:
238 * load the chip modules in question
239 * load ath_rate, ath_dfs
241 * load if_ath_pci and/or if_ath_ahb depending upon your particular
242 bus bind type - this is where probe/attach is done.
244 For further comments/feedback, poke adrian@ .
247 The "ino64" 64-bit inode project has been committed, which extends
248 a number of types to 64 bits. Upgrading in place requires care and
249 adherence to the documented upgrade procedure.
251 If using a custom kernel configuration ensure that the
252 COMPAT_FREEBSD11 option is included (as during the upgrade the
253 system will be running the ino64 kernel with the existing world).
255 For the safest in-place upgrade begin by removing previous build
256 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
257 full procedure documented below under the heading "To rebuild
258 everything and install it on the current system." Specifically,
259 a reboot is required after installing the new kernel before
263 The NATM framework including the en(4), fatm(4), hatm(4), and
264 patm(4) devices has been removed. Consumers should plan a
265 migration before the end-of-life date for FreeBSD 11.
268 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
269 diff has not been implemented, if those are needed a newer version of
270 GNU diff is available via the diffutils package under the gdiff name.
273 As of r316810 for ipfilter, keep frags is no longer assumed when
274 keep state is specified in a rule. r316810 aligns ipfilter with
275 documentation in man pages separating keep frags from keep state.
276 This allows keep state to be specified without forcing keep frags
277 and allows keep frags to be specified independently of keep state.
278 To maintain previous behaviour, also specify keep frags with
279 keep state (as documented in ipf.conf.5).
282 arm64 builds now use the base system LLD 4.0.0 linker by default,
283 instead of requiring that the aarch64-binutils port or package be
284 installed. To continue using aarch64-binutils, set
285 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
288 The UDP optimization in entry 20160818 that added the sysctl
289 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
290 packets will no longer be treated as L3 broadcast packets.
293 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
294 use any explicitly assigned loopback address available in the jail
295 instead of using the first assigned address of the jail.
298 The ctl.ko module no longer implements the iSCSI target frontend:
299 cfiscsi.ko does instead.
301 If building cfiscsi.ko as a kernel module, the module can be loaded
302 via one of the following methods:
303 - `cfiscsi_load="YES"` in loader.conf(5).
304 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
305 - ctladm(8)/ctld(8), when compiled with iSCSI support
306 (`WITH_ISCSI=yes` in src.conf(5))
308 Please see cfiscsi(4) for more details.
311 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
312 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
313 same source (previously, the dependency of mmcsd.ko on mmc.ko was
314 missing, but mmcsd.ko now will refuse to load if it is incompatible
318 The syntax of ipfw(8) named states was changed to avoid ambiguity.
319 If you have used named states in the firewall rules, you need to modify
320 them after installworld and before rebooting. Now named states must
321 be prefixed with colon.
324 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
325 removed as the userland we provide cannot use them. The KMS version
326 (sys/dev/drm2) supports the same hardware.
329 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
330 Please see the 20141231 entry below for information about prerequisites
331 and upgrading, if you are not already using clang 3.5.0 or higher.
334 The code that provides support for ZFS .zfs/ directory functionality
335 has been reimplemented. It's not possible now to create a snapshot
336 by mkdir under .zfs/snapshot/. That should be the only user visible
340 EISA bus support has been removed. The WITH_EISA option is no longer
344 MCA bus support has been removed.
347 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
348 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
351 The EM_MULTIQUEUE kernel configuration option is deprecated now that
352 the em(4) driver conforms to iflib specifications.
355 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
356 IFLIB. If you have a custom kernel configuration that excludes em(4)
357 but you use igb(4), you need to re-add em(4) to your custom configuration.
360 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
361 Please see the 20141231 entry below for information about prerequisites
362 and upgrading, if you are not already using clang 3.5.0 or higher.
365 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
366 Please see the 20141231 entry below for information about prerequisites
367 and upgrading, if you are not already using clang 3.5.0 or higher.
370 The layout of the pmap structure has changed for powerpc to put the pmap
371 statistics at the front for all CPU variations. libkvm(3) and all tools
372 that link against it need to be recompiled.
375 isl(4) and cyapa(4) drivers now require a new driver,
376 chromebook_platform(4), to work properly on Chromebook-class hardware.
377 On other types of hardware the drivers may need to be configured using
378 device hints. Please see the corresponding manual pages for details.
381 The urtwn(4) driver was merged into rtwn(4) and now consists of
382 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
384 Also, firmware for RTL8188CE was renamed due to possible name
385 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
388 GNU rcs has been removed from base. It is available as packages:
389 - rcs: Latest GPLv3 GNU rcs version.
390 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
394 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
395 modules now requires that the kernel configuration contain the
396 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
399 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
400 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
403 Relocatable object files with the extension of .So have been renamed
404 to use an extension of .pico instead. The purpose of this change is
405 to avoid a name clash with shared libraries on case-insensitive file
406 systems. On those file systems, foo.So is the same file as foo.so.
409 GNU rcs has been turned off by default. It can (temporarily) be built
410 again by adding WITH_RCS knob in src.conf.
411 Otherwise, GNU rcs is available from packages:
412 - rcs: Latest GPLv3 GNU rcs version.
413 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
416 The backup_uses_rcs functionality has been removed from rc.subr.
419 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
420 two separate components, QUEUE_MACRO_DEBUG_TRACE and
421 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
422 QUEUE_MACRO_DEBUG behavior.
425 r304787 changed some ioctl interfaces between the iSCSI userspace
426 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
427 rebuilt to work with new kernels. __FreeBSD_version has been bumped
431 The UDP receive code has been updated to only treat incoming UDP
432 packets that were addressed to an L2 broadcast address as L3
433 broadcast packets. It is not expected that this will affect any
434 standards-conforming UDP application. The new behaviour can be
435 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
439 Remove the openbsd_poll system call.
440 __FreeBSD_version has been bumped because of this.
443 The libc stub for the pipe(2) system call has been replaced with
444 a wrapper that calls the pipe2(2) system call and the pipe(2)
445 system call is now only implemented by the kernels that include
446 "options COMPAT_FREEBSD10" in their config file (this is the
447 default). Users should ensure that this option is enabled in
448 their kernel or upgrade userspace to r302092 before upgrading their
452 CAM will now strip leading spaces from SCSI disks' serial numbers.
453 This will affect users who create UFS filesystems on SCSI disks using
454 those disk's diskid device nodes. For example, if /etc/fstab
455 previously contained a line like
456 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
457 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
458 transforms like gmirror may also be affected. ZFS users should
462 The bitstring(3) API has been updated with new functionality and
463 improved performance. But it is binary-incompatible with the old API.
464 Objects built with the new headers may not be linked against objects
465 built with the old headers.
468 The brk and sbrk functions have been removed from libc on arm64.
469 Binutils from ports has been updated to not link to these
470 functions and should be updated to the latest version before
471 installing a new libc.
474 The armv6 port now defaults to hard float ABI. Limited support
475 for running both hardfloat and soft float on the same system
476 is available using the libraries installed with -DWITH_LIBSOFT.
477 This has only been tested as an upgrade path for installworld
478 and packages may fail or need manual intervention to run. New
479 packages will be needed.
481 To update an existing self-hosted armv6hf system, you must add
482 TARGET_ARCH=armv6 on the make command line for both the build
483 and the install steps.
486 Kernel modules compiled outside of a kernel build now default to
487 installing to /boot/modules instead of /boot/kernel. Many kernel
488 modules built this way (such as those in ports) already overrode
489 KMODDIR explicitly to install into /boot/modules. However,
490 manually building and installing a module from /sys/modules will
491 now install to /boot/modules instead of /boot/kernel.
494 The CAM I/O scheduler has been committed to the kernel. There should be
495 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
496 list of known rogues that claim support for this but actually corrupt
497 data is believed to be complete, be on the lookout for data
498 corruption. The known rogue list is believed to be complete:
500 o Crucial MX100, M550 drives with MU01 firmware.
501 o Micron M510 and M550 drives with MU01 firmware.
502 o Micron M500 prior to MU07 firmware
503 o Samsung 830, 840, and 850 all firmwares
504 o FCCT M500 all firmwares
506 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
507 with working NCQ TRIM. For Micron branded drives, see your sales rep for
508 updated firmware. Black listed drives will work correctly because these
509 drives work correctly so long as no NCQ TRIMs are sent to them. Given
510 this list is the same as found in Linux, it's believed there are no
511 other rogues in the market place. All other models from the above
514 To be safe, if you are at all concerned, you can quirk each of your
515 drives to prevent NCQ from being sent by setting:
516 kern.cam.ada.X.quirks="0x2"
517 in loader.conf. If the drive requires the 4k sector quirk, set the
521 The FAST_DEPEND build option has been removed and its functionality is
522 now the one true way. The old mkdep(1) style of 'make depend' has
523 been removed. See 20160311 for further details.
526 Resource range types have grown from unsigned long to uintmax_t. All
527 drivers, and anything using libdevinfo, need to be recompiled.
530 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
531 builds. It no longer runs mkdep(1) during 'make depend', and the
532 'make depend' stage can safely be skipped now as it is auto ran
533 when building 'make all' and will generate all SRCS and DPSRCS before
534 building anything else. Dependencies are gathered at compile time with
535 -MF flags kept in separate .depend files per object file. Users should
536 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
540 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
541 kernel modules. Therefore, if you load any kernel modules at boot time,
542 please install the boot loaders after you install the kernel, but before
546 make kernel KERNCONF=YOUR_KERNEL_HERE
547 make -C sys/boot install
548 <reboot in single user>
550 Then follow the usual steps, described in the General Notes section,
554 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
555 see the 20141231 entry below for information about prerequisites and
556 upgrading, if you are not already using clang 3.5.0 or higher.
559 The AIO subsystem is now a standard part of the kernel. The
560 VFS_AIO kernel option and aio.ko kernel module have been removed.
561 Due to stability concerns, asynchronous I/O requests are only
562 permitted on sockets and raw disks by default. To enable
563 asynchronous I/O requests on all file types, set the
564 vfs.aio.enable_unsafe sysctl to a non-zero value.
567 The ELF object manipulation tool objcopy is now provided by the
568 ELF Tool Chain project rather than by GNU binutils. It should be a
569 drop-in replacement, with the addition of arm64 support. The
570 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
571 to obtain the GNU version if necessary.
574 Building ZFS pools on top of zvols is prohibited by default. That
575 feature has never worked safely; it's always been prone to deadlocks.
576 Using a zvol as the backing store for a VM guest's virtual disk will
577 still work, even if the guest is using ZFS. Legacy behavior can be
578 restored by setting vfs.zfs.vol.recursive=1.
581 The NONE and HPN patches has been removed from OpenSSH. They are
582 still available in the security/openssh-portable port.
585 With the addition of ypldap(8), a new _ypldap user is now required
586 during installworld. "mergemaster -p" can be used to add the user
587 prior to installworld, as documented in the handbook.
590 The tftp loader (pxeboot) now uses the option root-path directive. As a
591 consequence it no longer looks for a pxeboot.4th file on the tftp
592 server. Instead it uses the regular /boot infrastructure as with the
596 The code to start recording plug and play data into the modules has
597 been committed. While the old tools will properly build a new kernel,
598 a number of warnings about "unknown metadata record 4" will be produced
599 for an older kldxref. To avoid such warnings, make sure to rebuild
600 the kernel toolchain (or world). Make sure that you have r292078 or
601 later when trying to build 292077 or later before rebuilding.
604 Debug data files are now built by default with 'make buildworld' and
605 installed with 'make installworld'. This facilitates debugging but
606 requires more disk space both during the build and for the installed
607 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
611 r291527 changed the internal interface between the nfsd.ko and
612 nfscommon.ko modules. As such, they must both be upgraded to-gether.
613 __FreeBSD_version has been bumped because of this.
616 Add support for unicode collation strings leads to a change of
617 order of files listed by ls(1) for example. To get back to the old
618 behaviour, set LC_COLLATE environment variable to "C".
620 Databases administrators will need to reindex their databases given
621 collation results will be different.
623 Due to a bug in install(1) it is recommended to remove the ancient
624 locales before running make installworld.
626 rm -rf /usr/share/locale/*
629 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
630 libcrypto.so.7 or libssl.so.7 must be recompiled.
633 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
634 Kernel modules isp_2400_multi and isp_2500_multi were removed and
635 should be replaced with isp_2400 and isp_2500 modules respectively.
638 The build previously allowed using 'make -n' to not recurse into
639 sub-directories while showing what commands would be executed, and
640 'make -n -n' to recursively show commands. Now 'make -n' will recurse
641 and 'make -N' will not.
644 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
645 and etcupdate will now use this file. A custom sendmail.cf is now
646 updated via this mechanism rather than via installworld. If you had
647 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
648 want to remove the exclusion or change it to "always install".
649 /etc/mail/sendmail.cf is now managed the same way regardless of
650 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
651 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
654 Compatibility shims for legacy ATA device names have been removed.
655 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
656 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
657 environment variables, /dev/ad* and /dev/ar* symbolic links.
660 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
661 Please see the 20141231 entry below for information about prerequisites
662 and upgrading, if you are not already using clang 3.5.0 or higher.
665 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
666 and renamed from .symbols to .debug. This reduces the size requirements
667 on the boot partition or file system and provides consistency with
668 userland debug files.
670 When using the supported kernel installation method the
671 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
672 as is done with /boot/kernel.
674 Developers wishing to maintain the historical behavior of installing
675 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
678 The wireless drivers had undergone changes that remove the 'parent
679 interface' from the ifconfig -l output. The rc.d network scripts
680 used to check presence of a parent interface in the list, so old
681 scripts would fail to start wireless networking. Thus, etcupdate(3)
682 or mergemaster(8) run is required after kernel update, to update your
683 rc.d scripts in /etc.
686 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
687 These configurations are now automatically interpreted as
688 'scrub fragment reassemble'.
691 Kernel-loadable modules for the random(4) device are back. To use
692 them, the kernel must have
695 options RANDOM_LOADABLE
697 kldload(8) can then be used to load random_fortuna.ko
698 or random_yarrow.ko. Please note that due to the indirect
699 function calls that the loadable modules need to provide,
700 the build-in variants will be slightly more efficient.
702 The random(4) kernel option RANDOM_DUMMY has been retired due to
703 unpopularity. It was not all that useful anyway.
706 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
707 Control over building the ELF Tool Chain tools is now provided by
708 the WITHOUT_TOOLCHAIN knob.
711 The polarity of Pulse Per Second (PPS) capture events with the
712 uart(4) driver has been corrected. Prior to this change the PPS
713 "assert" event corresponded to the trailing edge of a positive PPS
714 pulse and the "clear" event was the leading edge of the next pulse.
716 As the width of a PPS pulse in a typical GPS receiver is on the
717 order of 1 millisecond, most users will not notice any significant
718 difference with this change.
720 Anyone who has compensated for the historical polarity reversal by
721 configuring a negative offset equal to the pulse width will need to
722 remove that workaround.
725 The default group assigned to /dev/dri entries has been changed
726 from 'wheel' to 'video' with the id of '44'. If you want to have
727 access to the dri devices please add yourself to the video group
730 # pw groupmod video -m $USER
733 The menu.rc and loader.rc files will now be replaced during
734 upgrades. Please migrate local changes to menu.rc.local and
735 loader.rc.local instead.
738 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
739 strings and strip have been removed. The src.conf(5) knob
740 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
743 As ZFS requires more kernel stack pages than is the default on some
744 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
745 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
747 Please consider using 'options KSTACK_PAGES=X' where X is greater
748 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
751 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
752 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
753 default, i.e., they will not contain "::". For example, instead
754 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
755 to have a more specific match, such as different map entries for
756 IPv6:0:0 vs IPv6:0. This change requires that configuration
757 data (including maps, files, classes, custom ruleset, etc.) must
758 use the same format, so make certain such configuration data is
759 upgrading. As a very simple check search for patterns like
760 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
761 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
762 the cf option UseCompressedIPv6Addresses.
765 The default kernel entropy-processing algorithm is now
766 Fortuna, replacing Yarrow.
768 Assuming you have 'device random' in your kernel config
769 file, the configurations allow a kernel option to override
770 this default. You may choose *ONE* of:
772 options RANDOM_YARROW # Legacy /dev/random algorithm.
773 options RANDOM_DUMMY # Blocking-only driver.
775 If you have neither, you get Fortuna. For most people,
776 read no further, Fortuna will give a /dev/random that works
777 like it always used to, and the difference will be irrelevant.
779 If you remove 'device random', you get *NO* kernel-processed
780 entropy at all. This may be acceptable to folks building
781 embedded systems, but has complications. Carry on reading,
782 and it is assumed you know what you need.
784 *PLEASE* read random(4) and random(9) if you are in the
785 habit of tweaking kernel configs, and/or if you are a member
786 of the embedded community, wanting specific and not-usual
787 behaviour from your security subsystems.
789 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
790 random', you will NOT have a functioning /dev/random, and
791 many cryptographic features will not work, including SSH.
792 You may also find strange behaviour from the random(3) set
793 of library functions, in particular sranddev(3), srandomdev(3)
794 and arc4random(3). The reason for this is that the KERN_ARND
795 sysctl only returns entropy if it thinks it has some to
796 share, and with RANDOM_DUMMY or no 'device random' this
800 An additional fix for the issue described in the 20150614 sendmail
801 entry below has been been committed in revision 284717.
804 FreeBSD's old make (fmake) has been removed from the system. It is
805 available as the devel/fmake port or via pkg install fmake.
808 The fix for the issue described in the 20150614 sendmail entry
809 below has been been committed in revision 284436. The work
810 around described in that entry is no longer needed unless the
811 default setting is overridden by a confDH_PARAMETERS configuration
812 setting of '5' or pointing to a 512 bit DH parameter file.
815 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
816 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
817 and devel/kyua to version 0.20+ and adjust any calling code to work
818 with Kyuafile and kyua.
821 The import of openssl to address the FreeBSD-SA-15:10.openssl
822 security advisory includes a change which rejects handshakes
823 with DH parameters below 768 bits. sendmail releases prior
824 to 8.15.2 (not yet released), defaulted to a 512 bit
825 DH parameter setting for client connections. To work around
826 this interoperability, sendmail can be configured to use a
827 2048 bit DH parameter by:
829 1. Edit /etc/mail/`hostname`.mc
830 2. If a setting for confDH_PARAMETERS does not exist or
831 exists and is set to a string beginning with '5',
833 3. If a setting for confDH_PARAMETERS exists and is set to
834 a file path, create a new file with:
835 openssl dhparam -out /path/to/file 2048
836 4. Rebuild the .cf file:
837 cd /etc/mail/; make; make install
839 cd /etc/mail/; make restart
841 A sendmail patch is coming, at which time this file will be
845 Generation of legacy formatted entries have been disabled by default
846 in pwd_mkdb(8), as all base system consumers of the legacy formatted
847 entries were converted to use the new format by default when the new,
848 machine independent format have been added and supported since FreeBSD
851 Please see the pwd_mkdb(8) manual page for further details.
854 Clang and llvm have been upgraded to 3.6.1 release. Please see the
855 20141231 entry below for information about prerequisites and upgrading,
856 if you are not already using 3.5.0 or higher.
859 TI platform code switched to using vendor DTS files and this update
860 may break existing systems running on Beaglebone, Beaglebone Black,
863 - dtb files should be regenerated/reinstalled. Filenames are the
864 same but content is different now
865 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
866 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
867 addressing scheme is now pin 25 on /dev/gpioc3.
868 - Pandaboard: /etc/ttys should be updated, serial console device is
869 now /dev/ttyu2, not /dev/ttyu0
872 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
873 If you need the GNU extension from groff soelim(1), install groff
874 from package: pkg install groff, or via ports: textproc/groff.
877 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
878 defined in symlink(7); previously symlinks were silently ignored.
881 The const qualifier has been removed from iconv(3) to comply with
882 POSIX. The ports tree is aware of this from r384038 onwards.
885 Libraries specified by LIBADD in Makefiles must have a corresponding
886 DPADD_<lib> variable to ensure correct dependencies. This is now
887 enforced in src.libnames.mk.
890 From legacy ata(4) driver was removed support for SATA controllers
891 supported by more functional drivers ahci(4), siis(4) and mvs(4).
892 Kernel modules ataahci and ataadaptec were removed completely,
893 replaced by ahci and mvs modules respectively.
896 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
897 the 20141231 entry below for information about prerequisites and
898 upgrading, if you are not already using 3.5.0 or higher.
901 The 32-bit PowerPC kernel has been changed to a position-independent
902 executable. This can only be booted with a version of loader(8)
903 newer than January 31, 2015, so make sure to update both world and
904 kernel before rebooting.
907 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
908 but before r278950, the RNG was not seeded properly. Immediately
909 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
910 ssh keys or openssl keys) that were generated w/ a kernel from that
911 range. This does not affect programs that directly used /dev/random
912 or /dev/urandom. All userland uses of arc4random(3) are affected.
915 The autofs(4) ABI was changed in order to restore binary compatibility
916 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
920 The powerpc64 kernel has been changed to a position-independent
921 executable. This can only be booted with a new version of loader(8),
922 so make sure to update both world and kernel before rebooting.
925 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
926 only release, no new features have been added. Please see the 20141231
927 entry below for information about prerequisites and upgrading, if you
928 are not already using 3.5.0.
931 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
932 taken from the ELF Tool Chain project rather than GNU binutils. They
933 should be drop-in replacements, with the addition of arm64 support.
934 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
935 binutils tools, if necessary. See 20150805 for updated information.
938 The default Unbound configuration now enables remote control
939 using a local socket. Users who have already enabled the
940 local_unbound service should regenerate their configuration
941 by running "service local_unbound setup" as root.
944 The GNU texinfo and GNU info pages have been removed.
945 To be able to view GNU info pages please install texinfo from ports.
948 Clang, llvm and lldb have been upgraded to 3.5.0 release.
950 As of this release, a prerequisite for building clang, llvm and lldb is
951 a C++11 capable compiler and C++11 standard library. This means that to
952 be able to successfully build the cross-tools stage of buildworld, with
953 clang as the bootstrap compiler, your system compiler or cross compiler
954 should either be clang 3.3 or later, or gcc 4.8 or later, and your
955 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
958 On any standard FreeBSD 10.x or 11.x installation, where clang and
959 libc++ are on by default (that is, on x86 or arm), this should work out
962 On 9.x installations where clang is enabled by default, e.g. on x86 and
963 powerpc, libc++ will not be enabled by default, so libc++ should be
964 built (with clang) and installed first. If both clang and libc++ are
965 missing, build clang first, then use it to build libc++.
967 On 8.x and earlier installations, upgrade to 9.x first, and then follow
968 the instructions for 9.x above.
970 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
971 default, and do not build clang.
973 Many embedded systems are resource constrained, and will not be able to
974 build clang in a reasonable time, or in some cases at all. In those
975 cases, cross building bootable systems on amd64 is a workaround.
977 This new version of clang introduces a number of new warnings, of which
978 the following are most likely to appear:
982 This warns in two cases, for both C and C++:
983 * When the code is trying to take the absolute value of an unsigned
984 quantity, which is effectively a no-op, and almost never what was
985 intended. The code should be fixed, if at all possible. If you are
986 sure that the unsigned quantity can be safely cast to signed, without
987 loss of information or undefined behavior, you can add an explicit
988 cast, or disable the warning.
990 * When the code is trying to take an absolute value, but the called
991 abs() variant is for the wrong type, which can lead to truncation.
992 If you want to disable the warning instead of fixing the code, please
993 make sure that truncation will not occur, or it might lead to unwanted
996 -Wtautological-undefined-compare and
997 -Wundefined-bool-conversion
999 These warn when C++ code is trying to compare 'this' against NULL, while
1000 'this' should never be NULL in well-defined C++ code. However, there is
1001 some legacy (pre C++11) code out there, which actively abuses this
1002 feature, which was less strictly defined in previous C++ versions.
1004 Squid and openjdk do this, for example. The warning can be turned off
1005 for C++98 and earlier, but compiling the code in C++11 mode might result
1006 in unexpected behavior; for example, the parts of the program that are
1007 unreachable could be optimized away.
1010 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1011 kernel sources have been removed. The .h files remain, since some
1012 utilities include them. This will need to be fixed later.
1013 If "mount -t oldnfs ..." is attempted, it will fail.
1014 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1015 the utilities will report errors.
1018 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1019 directories to top level SUBDIR variable when their parent
1020 directory is included in LOCAL_DIRS. Users with build systems with
1021 such hierarchies and without SUBDIR entries in the parent
1022 directory Makefiles should add them or add the directories to
1026 faith(4) and faithd(8) have been removed from the base system. Faith
1027 has been obsolete for a very long time.
1030 vt(4), the new console driver, is enabled by default. It brings
1031 support for Unicode and double-width characters, as well as
1032 support for UEFI and integration with the KMS kernel video
1035 You may need to update your console settings in /etc/rc.conf,
1036 most probably the keymap. During boot, /etc/rc.d/syscons will
1037 indicate what you need to do.
1039 vt(4) still has issues and lacks some features compared to
1040 syscons(4). See the wiki for up-to-date information:
1041 https://wiki.freebsd.org/Newcons
1043 If you want to keep using syscons(4), you can do so by adding
1044 the following line to /boot/loader.conf:
1048 pjdfstest has been integrated into kyua as an opt-in test suite.
1049 Please see share/doc/pjdfstest/README for more details on how to
1053 gperf has been removed from the base system for architectures
1054 that use clang. Ports that require gperf will obtain it from the
1058 pjdfstest has been moved from tools/regression/pjdfstest to
1062 At svn r271982, The default linux compat kernel ABI has been adjusted
1063 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1064 update. If you wish to continue using the linux-f10 compat ports,
1065 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1066 encouraged to update their linux-compat packages to linux-c6 during
1067 their next update cycle.
1070 The ofwfb driver, used to provide a graphics console on PowerPC when
1071 using vt(4), no longer allows mmap() of all physical memory. This
1072 will prevent Xorg on PowerPC with some ATI graphics cards from
1073 initializing properly unless x11-servers/xorg-server is updated to
1077 The xdev targets have been converted to using TARGET and
1078 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1081 The default unbound configuration has been modified to address
1082 issues with reverse lookups on networks that use private
1083 address ranges. If you use the local_unbound service, run
1084 "service local_unbound setup" as root to regenerate your
1085 configuration, then "service local_unbound reload" to load the
1089 The GNU texinfo and GNU info pages are not built and installed
1090 anymore, WITH_INFO knob has been added to allow to built and install
1092 UPDATE: see 20150102 entry on texinfo's removal
1095 The GNU readline library is now an INTERNALLIB - that is, it is
1096 statically linked into consumers (GDB and variants) in the base
1097 system, and the shared library is no longer installed. The
1098 devel/readline port is available for third party software that
1102 The Itanium architecture (ia64) has been removed from the list of
1103 known architectures. This is the first step in the removal of the
1107 Commit r268115 has added NFSv4.1 server support, merged from
1108 projects/nfsv4.1-server. Since this includes changes to the
1109 internal interfaces between the NFS related modules, a full
1110 build of the kernel and modules will be necessary.
1111 __FreeBSD_version has been bumped.
1114 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1115 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1116 which differs from the behaviour controlled by this knob.)
1119 Maximal length of the serial number in CTL was increased from 16 to
1120 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1121 and ctld, need to be rebuilt to work with a new kernel.
1124 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1125 1 respectively to match the upstream numbers. They were out of
1126 sync because, when they were originally added to FreeBSD, the
1127 upstream versions were not respected. These libraries are private
1128 and not yet built by default, so renumbering them should be a
1129 non-issue. However, unclean source trees will yield broken test
1130 programs once the operator executes "make delete-old-libs" after a
1131 "make installworld".
1133 Additionally, the atf-sh binary was made private by moving it into
1134 /usr/libexec/. Already-built shell test programs will keep the
1135 path to the old binary so they will break after "make delete-old"
1138 If you are using WITH_TESTS=yes (not the default), wipe the object
1139 tree and rebuild from scratch to prevent spurious test failures.
1140 This is only needed once: the misnumbered libraries and misplaced
1141 binaries have been added to OptionalObsoleteFiles.inc so they will
1142 be removed during a clean upgrade.
1145 Clang and llvm have been upgraded to 3.4.1 release.
1148 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1149 be removed to avoid issues in the future (and has been added to
1153 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1154 past, it affected all builds that used the bsd.*.mk files. The old
1155 behavior was a bug, but people may have relied upon it. To get this
1156 behavior back, you can .include /etc/src.conf from /etc/make.conf
1157 (which is still global and isn't changed). This also changes the
1158 behavior of incremental builds inside the tree of individual
1159 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1160 Although this has survived make universe and some upgrade scenarios,
1161 other upgrade scenarios may have broken. At least one form of
1162 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1163 as well... In cases where MAKESYSPATH isn't working with this
1164 setting, you'll need to set it to the full path to your tree.
1166 One side effect of all this cleaning up is that bsd.compiler.mk
1167 is no longer implicitly included by bsd.own.mk. If you wish to
1168 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1172 The lindev device has been removed since /dev/full has been made a
1173 standard device. __FreeBSD_version has been bumped.
1176 The knob WITHOUT_VI was added to the base system, which controls
1177 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1178 in order to reorder files share/termcap and didn't build ex(1) as a
1179 build tool, so building/installing with WITH_VI is highly advised for
1180 build hosts for older releases.
1182 This issue has been fixed in stable/9 and stable/10 in r277022 and
1183 r276991, respectively.
1186 The YES_HESIOD knob has been removed. It has been obsolete for
1187 a decade. Please move to using WITH_HESIOD instead or your builds
1188 will silently lack HESIOD.
1191 The uart(4) driver has been changed with respect to its handling
1192 of the low-level console. Previously the uart(4) driver prevented
1193 any process from changing the baudrate or the CLOCAL and HUPCL
1194 control flags. By removing the restrictions, operators can make
1195 changes to the serial console port without having to reboot.
1196 However, when getty(8) is started on the serial device that is
1197 associated with the low-level console, a misconfigured terminal
1198 line in /etc/ttys will now have a real impact.
1199 Before upgrading the kernel, make sure that /etc/ttys has the
1200 serial console device configured as 3wire without baudrate to
1201 preserve the previous behaviour. E.g:
1202 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1205 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1206 to improve performance. To re-enable it, if needed, run rpcbind
1207 with command line option -W.
1210 Switched back to the GPL dtc compiler due to updates in the upstream
1211 dts files not being supported by the BSDL dtc compiler. You will need
1212 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1213 may result while building dtb files during a kernel build if you fail
1214 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1217 Clang and llvm have been upgraded to 3.4 release.
1220 The nve(4) driver has been removed. Please use the nfe(4) driver
1221 for NVIDIA nForce MCP Ethernet adapters instead.
1224 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1225 This could cause certain C++ applications using shared libraries built
1226 against the previous version of libc++ to crash. The incompatibility
1227 has now been fixed, but any C++ applications or shared libraries built
1228 between r261283 and r261801 should be recompiled.
1231 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1232 capability mode support. Please note that enabling the feature in
1233 kernel is still highly recommended.
1236 OpenSSH is now built with sandbox support, and will use sandbox as
1237 the default privilege separation method. This requires Capsicum
1238 capability mode support in kernel.
1241 The libelf and libdwarf libraries have been updated to newer
1242 versions from upstream. Shared library version numbers for
1243 these two libraries were bumped. Any ports or binaries
1244 requiring these two libraries should be recompiled.
1245 __FreeBSD_version is bumped to 1100006.
1248 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1249 instead of providing an explicit one, this would prevent such
1250 Makefile from providing its own Kyuafile in the future during
1251 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1252 intervention is needed to clean an objdir if you use NO_CLEAN:
1253 # find /usr/obj -name Kyuafile | xargs rm -f
1256 The behavior of gss_pseudo_random() for the krb5 mechanism
1257 has changed, for applications requesting a longer random string
1258 than produced by the underlying enctype's pseudo-random() function.
1259 In particular, the random string produced from a session key of
1260 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1261 be different at the 17th octet and later, after this change.
1262 The counter used in the PRF+ construction is now encoded as a
1263 big-endian integer in accordance with RFC 4402.
1264 __FreeBSD_version is bumped to 1100004.
1267 The WITHOUT_ATF build knob has been removed and its functionality
1268 has been subsumed into the more generic WITHOUT_TESTS. If you were
1269 using the former to disable the build of the ATF libraries, you
1270 should change your settings to use the latter.
1273 The default version of mtree is nmtree which is obtained from
1274 NetBSD. The output is generally the same, but may vary
1275 slightly. If you found you need identical output adding
1276 "-F freebsd9" to the command line should do the trick. For the
1277 time being, the old mtree is available as fmtree.
1280 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1281 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1282 1.1.4_8 and verify bsdyml not linked in, before running "make
1284 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1286 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1289 The stable/10 branch has been created in subversion from head
1293 The rc.d/jail script has been updated to support jail(8)
1294 configuration file. The "jail_<jname>_*" rc.conf(5) variables
1295 for per-jail configuration are automatically converted to
1296 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
1297 This is transparently backward compatible. See below about some
1298 incompatibilities and rc.conf(5) manual page for more details.
1300 These variables are now deprecated in favor of jail(8) configuration
1301 file. One can use "rc.d/jail config <jname>" command to generate
1302 a jail(8) configuration file in /var/run/jail.<jname>.conf without
1303 running the jail(8) utility. The default pathname of the
1304 configuration file is /etc/jail.conf and can be specified by
1305 using $jail_conf or $jail_<jname>_conf variables.
1307 Please note that jail_devfs_ruleset accepts an integer at
1308 this moment. Please consider to rewrite the ruleset name
1312 BIND has been removed from the base system. If all you need
1313 is a local resolver, simply enable and start the local_unbound
1314 service instead. Otherwise, several versions of BIND are
1315 available in the ports tree. The dns/bind99 port is one example.
1317 With this change, nslookup(1) and dig(1) are no longer in the base
1318 system. Users should instead use host(1) and drill(1) which are
1319 in the base system. Alternatively, nslookup and dig can
1320 be obtained by installing the dns/bind-tools port.
1323 With the addition of unbound(8), a new unbound user is now
1324 required during installworld. "mergemaster -p" can be used to
1325 add the user prior to installworld, as documented in the handbook.
1328 OpenSSH is now built with DNSSEC support, and will by default
1329 silently trust signed SSHFP records. This can be controlled with
1330 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1331 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1334 The GNU Compiler Collection and C++ standard library (libstdc++)
1335 are no longer built by default on platforms where clang is the system
1336 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1337 options in src.conf.
1340 The PROCDESC kernel option is now part of the GENERIC kernel
1341 configuration and is required for the rwhod(8) to work.
1342 If you are using custom kernel configuration, you should include
1346 The API and ABI related to the Capsicum framework was modified
1347 in backward incompatible way. The userland libraries and programs
1348 have to be recompiled to work with the new kernel. This includes the
1349 following libraries and programs, but the whole buildworld is
1350 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1351 kdump, procstat, rwho, rwhod, uniq.
1354 AES-NI intrinsic support has been added to gcc. The AES-NI module
1355 has been updated to use this support. A new gcc is required to build
1356 the aesni module on both i386 and amd64.
1359 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1360 Thus "device padlock_rng" and "device rdrand_rng" should be
1361 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1364 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1365 enables just the iconv* functionality and is now on by default.
1366 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1367 compatibility. Set WITHOUT_ICONV to build the old way.
1368 If you have been using WITH_ICONV before, you will very likely
1369 need to turn on WITH_LIBICONV_COMPAT.
1372 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1373 Illumos origin, including ZFS. If you have INVARIANTS in your
1374 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1376 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1377 locks if WITNESS option was set. Because that generated a lot of
1378 witness(9) reports and all of them were believed to be false
1379 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1380 can be used to achieve the previous behavior.
1383 Timer values in IPv6 data structures now use time_uptime instead
1384 of time_second. Although this is not a user-visible functional
1385 change, userland utilities which directly use them---ndp(8),
1386 rtadvd(8), and rtsold(8) in the base system---need to be updated
1387 to r253970 or later.
1390 find -delete can now delete the pathnames given as arguments,
1391 instead of only files found below them or if the pathname did
1392 not contain any slashes. Formerly, the following error message
1395 find: -delete: <path>: relative path potentially not safe
1397 Deleting the pathnames given as arguments can be prevented
1398 without error messages using -mindepth 1 or by changing
1399 directory and passing "." as argument to find. This works in the
1400 old as well as the new version of find.
1403 Behavior of devfs rules path matching has been changed.
1404 Pattern is now always matched against fully qualified devfs
1405 path and slash characters must be explicitly matched by
1406 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1407 subdirectories must be reviewed.
1410 The default ARM ABI has changed to the ARM EABI. The old ABI is
1411 incompatible with the ARM EABI and all programs and modules will
1412 need to be rebuilt to work with a new kernel.
1414 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1416 NOTE: Support for the old ABI will be removed in the future and
1417 users are advised to upgrade.
1420 pkg_install has been disconnected from the build if you really need it
1421 you should add WITH_PKGTOOLS in your src.conf(5).
1424 Most of network statistics structures were changed to be able
1425 keep 64-bits counters. Thus all tools, that work with networking
1426 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1429 Fix a bug that allowed a tracing process (e.g. gdb) to write
1430 to a memory-mapped file in the traced process's address space
1431 even if neither the traced process nor the tracing process had
1432 write access to that file.
1435 CVS has been removed from the base system. An exact copy
1436 of the code is available from the devel/cvs port.
1439 Some people report the following error after the switch to bmake:
1441 make: illegal option -- J
1442 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1444 *** [buildworld] Error code 2
1446 this likely due to an old instance of make in
1447 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1448 which src/Makefile will use that blindly, if it exists, so if
1449 you see the above error:
1451 rm -rf `make -V MAKEPATH`
1456 Use bmake by default.
1457 Whereas before one could choose to build with bmake via
1458 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1459 make. The goal is to remove these knobs for 10-RELEASE.
1461 It is worth noting that bmake (like gmake) treats the command
1462 line as the unit of failure, rather than statements within the
1463 command line. Thus '(cd some/where && dosomething)' is safer
1464 than 'cd some/where; dosomething'. The '()' allows consistent
1465 behavior in parallel build.
1468 Fix a bug that allows NFS clients to issue READDIR on files.
1471 The WITHOUT_IDEA option has been removed because
1472 the IDEA patent expired.
1475 The sysctl which controls TRIM support under ZFS has been renamed
1476 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1480 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1481 rather than creating it's own in the temporary directory in
1482 order allow access to bootstrapped versions of tools such as
1483 install and mtree. When upgrading from version of FreeBSD where
1484 the install command does not support -l, you will need to
1485 install a new mergemaster command if mergemaster -p is required.
1486 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1490 Legacy ATA stack, disabled and replaced by new CAM-based one since
1491 FreeBSD 9.0, completely removed from the sources. Kernel modules
1492 atadisk and atapi*, user-level tools atacontrol and burncd are
1493 removed. Kernel option `options ATA_CAM` is now permanently enabled
1497 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1498 and socketpair(2). Software, in particular Kerberos, may
1499 automatically detect and use these during building. The resulting
1500 binaries will not work on older kernels.
1503 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1504 information, see the respective 20130304 entry).
1507 Recent commits to callout(9) changed the size of struct callout,
1508 so the KBI is probably heavily disturbed. Also, some functions
1509 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1510 by macros. Every kernel module using it won't load, so rebuild
1513 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1514 but does not initialize by default (because of the new CTL_DISABLE
1515 option) to save memory. To re-enable it, remove the CTL_DISABLE
1516 option from the kernel config file or set kern.cam.ctl.disable=0
1517 in /boot/loader.conf.
1520 The ctl device has been disabled in GENERIC for i386 and amd64.
1521 This was done due to the extra memory being allocated at system
1522 initialisation time by the ctl driver which was only used if
1523 a CAM target device was created. This makes a FreeBSD system
1524 unusable on 128MB or less of RAM.
1527 A new compression method (lz4) has been merged to -HEAD. Please
1528 refer to zpool-features(7) for more information.
1530 Please refer to the "ZFS notes" section of this file for information
1531 on upgrading boot ZFS pools.
1534 A BSD-licensed patch(1) variant has been added and is installed
1535 as bsdpatch, being the GNU version the default patch.
1536 To inverse the logic and use the BSD-licensed one as default,
1537 while having the GNU version installed as gnupatch, rebuild
1538 and install world with the WITH_BSD_PATCH knob set.
1541 Due to the use of the new -l option to install(1) during build
1542 and install, you must take care not to directly set the INSTALL
1543 make variable in your /etc/make.conf, /etc/src.conf, or on the
1544 command line. If you wish to use the -C flag for all installs
1545 you may be able to add INSTALL+=-C to /etc/make.conf or
1549 The install(1) option -M has changed meaning and now takes an
1550 argument that is a file or path to append logs to. In the
1551 unlikely event that -M was the last option on the command line
1552 and the command line contained at least two files and a target
1553 directory the first file will have logs appended to it. The -M
1554 option served little practical purpose in the last decade so its
1555 use is expected to be extremely rare.
1558 After switching to Clang as the default compiler some users of ZFS
1559 on i386 systems started to experience stack overflow kernel panics.
1560 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1563 GEOM_LABEL now mangles label names read from file system metadata.
1564 Mangling affect labels containing spaces, non-printable characters,
1565 '%' or '"'. Device names in /etc/fstab and other places may need to
1569 By default, only the 10 most recent kernel dumps will be saved. To
1570 restore the previous behaviour (no limit on the number of kernel dumps
1571 stored in the dump directory) add the following line to /etc/rc.conf:
1576 With the addition of auditdistd(8), a new auditdistd user is now
1577 required during installworld. "mergemaster -p" can be used to
1578 add the user prior to installworld, as documented in the handbook.
1581 The sin6_scope_id member variable in struct sockaddr_in6 is now
1582 filled by the kernel before passing the structure to the userland via
1583 sysctl or routing socket. This means the KAME-specific embedded scope
1584 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1585 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1586 __FreeBSD_version is bumped to 1000025.
1589 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1590 This means that the world and kernel will be compiled with clang
1591 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1592 and /usr/bin/cpp. To disable this behavior and revert to building
1593 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1594 of current may need to bootstrap WITHOUT_CLANG first if the clang
1595 build fails (its compatibility window doesn't extend to the 9 stable
1599 The IPFIREWALL_FORWARD kernel option has been removed. Its
1600 functionality now turned on by default.
1603 The ZERO_COPY_SOCKET kernel option has been removed and
1604 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1605 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1606 mechanism which is not safe and may result in kernel crashes.
1607 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1608 driver supports disposeable external page sized mbuf storage.
1609 Proper replacements for both zero-copy mechanisms are under
1610 consideration and will eventually lead to complete removal
1611 of the two kernel options.
1614 The IPv4 network stack has been converted to network byte
1615 order. The following modules need to be recompiled together
1616 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1617 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1620 Support for non-MPSAFE filesystems was removed from VFS. The
1621 VFS_VERSION was bumped, all filesystem modules shall be
1625 All the non-MPSAFE filesystems have been disconnected from
1626 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1627 portalfs, smbfs, xfs.
1630 The interface cloning API and ABI has changed. The following
1631 modules need to be recompiled together with kernel:
1632 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1633 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1634 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1637 The sdhci driver was split in two parts: sdhci (generic SD Host
1638 Controller logic) and sdhci_pci (actual hardware driver).
1639 No kernel config modifications are required, but if you
1640 load sdhc as a module you must switch to sdhci_pci instead.
1643 Import the FUSE kernel and userland support into base system.
1646 The GNU sort(1) program has been removed since the BSD-licensed
1647 sort(1) has been the default for quite some time and no serious
1648 problems have been reported. The corresponding WITH_GNU_SORT
1652 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1653 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1657 The net80211(4) ABI has been changed to allow for improved driver
1658 PS-POLL and power-save support. All wireless drivers need to be
1659 recompiled to work with the new kernel.
1662 The random(4) support for the VIA hardware random number
1663 generator (`PADLOCK') is no longer enabled unconditionally.
1664 Add the padlock_rng device in the custom kernel config if
1665 needed. The GENERIC kernels on i386 and amd64 do include the
1666 device, so the change only affects the custom kernel
1670 The pf(4) packet filter ABI has been changed. pfctl(8) and
1671 snmp_pf module need to be recompiled to work with new kernel.
1674 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1675 to -HEAD. Pools that have empty_bpobj in active state can not be
1676 imported read-write with ZFS implementations that do not support
1677 this feature. For more information read the zpool-features(5)
1681 The sparc64 ZFS loader has been changed to no longer try to auto-
1682 detect ZFS providers based on diskN aliases but now requires these
1683 to be explicitly listed in the OFW boot-device environment variable.
1686 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1687 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1688 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1691 The following sysctls and tunables have been renamed for consistency
1692 with other variables:
1693 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1694 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1697 The sort utility has been replaced with BSD sort. For now, GNU sort
1698 is also available as "gnusort" or the default can be set back to
1699 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1700 installed as "bsdsort".
1703 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1704 Starting with this version the old system of ZFS pool versioning
1705 is superseded by "feature flags". This concept enables forward
1706 compatibility against certain future changes in functionality of ZFS
1707 pools. The first read-only compatible "feature flag" for ZFS pools
1708 is named "com.delphix:async_destroy". For more information
1709 read the new zpool-features(5) manual page.
1710 Please refer to the "ZFS notes" section of this file for information
1711 on upgrading boot ZFS pools.
1714 The malloc(3) implementation embedded in libc now uses sources imported
1715 as contrib/jemalloc. The most disruptive API change is to
1716 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1717 delete it prior to installworld, and optionally re-create it using the
1718 new format after rebooting. See malloc.conf(5) for details
1719 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1723 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1724 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1725 now spelled mips. This is to aid compatibility with third-party
1726 software that expects this naming scheme in uname(3). Little-endian
1727 settings are unchanged. If you are updating a big-endian mips64 machine
1728 from before this change, you may need to set MACHINE_ARCH=mips64 in
1729 your environment before the new build system will recognize your machine.
1732 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1736 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1737 nullfs(5) did not pass through all behaviours to the underlying layer,
1738 as a result if we bound to a socket on the lower layer we could connect
1739 only to the lower path; if we bound to the upper layer we could connect
1740 only to the upper path. The new behavior is one can connect to both the
1741 lower and the upper paths regardless what layer path one binds to.
1744 The getifaddrs upgrade path broken with 20111215 has been restored.
1745 If you have upgraded in between 20111215 and 20120209 you need to
1746 recompile libc again with your kernel. You still need to recompile
1747 world to be able to configure CARP but this restriction already
1748 comes from 20111215.
1751 The set_rcvar() function has been removed from /etc/rc.subr. All
1752 base and ports rc.d scripts have been updated, so if you have a
1753 port installed with a script in /usr/local/etc/rc.d you can either
1754 hand-edit the rcvar= line, or reinstall the port.
1756 An easy way to handle the mass-update of /etc/rc.d:
1757 rm /etc/rc.d/* && mergemaster -i
1760 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1761 on the current CPU and prevents other threads from running.
1762 This behavior can be reverted using the kern.stop_scheduler_on_panic
1764 The new behavior can be incompatible with kern.sync_on_panic.
1767 The carp(4) facility has been changed significantly. Configuration
1768 of the CARP protocol via ifconfig(8) has changed, as well as format
1769 of CARP events submitted to devd(8) has changed. See manual pages
1770 for more information. The arpbalance feature of carp(4) is currently
1771 not supported anymore.
1773 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1774 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1775 need to be recompiled.
1778 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1782 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1783 explicitely support non-MPSAFE filesystems.
1784 It is on by default for all supported platform at this present
1788 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1789 i386 and pc98 GENERIC kernel configuration files.
1792 sysinstall has been removed
1795 The stable/9 branch created in subversion. This corresponds to the
1796 RELENG_9 branch in CVS.
1802 Avoid using make -j when upgrading. While generally safe, there are
1803 sometimes problems using -j to upgrade. If your upgrade fails with
1804 -j, please try again without -j. From time to time in the past there
1805 have been problems using -j with buildworld and/or installworld. This
1806 is especially true when upgrading between "distant" versions (eg one
1807 that cross a major release boundary or several minor releases, or when
1808 several months have passed on the -current branch).
1810 Sometimes, obscure build problems are the result of environment
1811 poisoning. This can happen because the make utility reads its
1812 environment when searching for values for global variables. To run
1813 your build attempts in an "environmental clean room", prefix all make
1814 commands with 'env -i '. See the env(1) manual page for more details.
1816 When upgrading from one major version to another it is generally best to
1817 upgrade to the latest code in the currently installed branch first, then
1818 do an upgrade to the new branch. This is the best-tested upgrade path,
1819 and has the highest probability of being successful. Please try this
1820 approach if you encounter problems with a major version upgrade. Since
1821 the stable 4.x branch point, one has generally been able to upgade from
1822 anywhere in the most recent stable branch to head / current (or even the
1823 last couple of stable branches). See the top of this file when there's
1826 When upgrading a live system, having a root shell around before
1827 installing anything can help undo problems. Not having a root shell
1828 around can lead to problems if pam has changed too much from your
1829 starting point to allow continued authentication after the upgrade.
1831 This file should be read as a log of events. When a later event changes
1832 information of a prior event, the prior event should not be deleted.
1833 Instead, a pointer to the entry with the new information should be
1834 placed in the old entry. Readers of this file should also sanity check
1835 older entries before relying on them blindly. Authors of new entries
1836 should write them with this in mind.
1840 When upgrading the boot ZFS pool to a new version, always follow
1843 1.) recompile and reinstall the ZFS boot loader and boot block
1844 (this is part of "make buildworld" and "make installworld")
1846 2.) update the ZFS boot block on your boot drive
1848 The following example updates the ZFS boot block on the first
1849 partition (freebsd-boot) of a GPT partitioned drive ada0:
1850 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1852 Non-boot pools do not need these updates.
1856 If you are updating from a prior version of FreeBSD (even one just
1857 a few days old), you should follow this procedure. It is the most
1858 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1860 make kernel-toolchain
1861 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1862 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1864 To test a kernel once
1865 ---------------------
1866 If you just want to boot a kernel once (because you are not sure
1867 if it works, or if you want to boot a known bad kernel to provide
1868 debugging information) run
1869 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1870 nextboot -k testkernel
1872 To rebuild everything and install it on the current system.
1873 -----------------------------------------------------------
1874 # Note: sometimes if you are running current you gotta do more than
1875 # is listed here if you are upgrading from a really old current.
1877 <make sure you have good level 0 dumps>
1879 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1880 make installkernel KERNCONF=YOUR_KERNEL_HERE
1882 <reboot in single user> [3]
1889 To cross-install current onto a separate partition
1890 --------------------------------------------------
1891 # In this approach we use a separate partition to hold
1892 # current's root, 'usr', and 'var' directories. A partition
1893 # holding "/", "/usr" and "/var" should be about 2GB in
1896 <make sure you have good level 0 dumps>
1899 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1900 <maybe newfs current's root partition>
1901 <mount current's root partition on directory ${CURRENT_ROOT}>
1902 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1903 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1904 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1905 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1906 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1907 <reboot into current>
1908 <do a "native" rebuild/install as described in the previous section>
1909 <maybe install compatibility libraries from ports/misc/compat*>
1913 To upgrade in-place from stable to current
1914 ----------------------------------------------
1915 <make sure you have good level 0 dumps>
1917 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1919 <reboot in single user> [3]
1926 Make sure that you've read the UPDATING file to understand the
1927 tweaks to various things you need. At this point in the life
1928 cycle of current, things change often and you are on your own
1929 to cope. The defaults can also change, so please read ALL of
1930 the UPDATING entries.
1932 Also, if you are tracking -current, you must be subscribed to
1933 freebsd-current@freebsd.org. Make sure that before you update
1934 your sources that you have read and understood all the recent
1935 messages there. If in doubt, please track -stable which has
1936 much fewer pitfalls.
1938 [1] If you have third party modules, such as vmware, you
1939 should disable them at this point so they don't crash your
1942 [3] From the bootblocks, boot -s, and then do
1947 adjkerntz -i # if CMOS is wall time
1948 Also, when doing a major release upgrade, it is required that
1949 you boot into single user mode to do the installworld.
1951 [4] Note: This step is non-optional. Failure to do this step
1952 can result in a significant reduction in the functionality of the
1953 system. Attempting to do it by hand is not recommended and those
1954 that pursue this avenue should read this file carefully, as well
1955 as the archives of freebsd-current and freebsd-hackers mailing lists
1956 for potential gotchas. The -U option is also useful to consider.
1957 See mergemaster(8) for more information.
1959 [5] Usually this step is a noop. However, from time to time
1960 you may need to do this if you get unknown user in the following
1961 step. It never hurts to do it all the time. You may need to
1962 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1963 install) after the buildworld before this step if you last updated
1964 from current before 20130425 or from -stable before 20130430.
1966 [6] This only deletes old files and directories. Old libraries
1967 can be deleted by "make delete-old-libs", but you have to make
1968 sure that no program is using those libraries anymore.
1970 [8] In order to have a kernel that can run the 4.x binaries needed to
1971 do an installworld, you must include the COMPAT_FREEBSD4 option in
1972 your kernel. Failure to do so may leave you with a system that is
1973 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1974 required to run the 5.x binaries on more recent kernels. And so on
1975 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1977 Make sure that you merge any new devices from GENERIC since the
1978 last time you updated your kernel config file.
1980 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1981 "?=" instead of the "=" assignment operator, so that buildworld can
1982 override the CPUTYPE if it needs to.
1984 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1985 not on the command line, or in /etc/make.conf. buildworld will
1986 warn if it is improperly defined.
1989 This file contains a list, in reverse chronological order, of major
1990 breakages in tracking -current. It is not guaranteed to be a complete
1991 list of such breakages, and only contains entries since September 23, 2011.
1992 If you need to see UPDATING entries from before that date, you will need
1993 to fetch an UPDATING file from an older FreeBSD release.
1995 Copyright information:
1997 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1999 Redistribution, publication, translation and use, with or without
2000 modification, in full or in part, in any form or format of this
2001 document are permitted without further permission from the author.
2003 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2004 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2005 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2006 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2007 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2008 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2009 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2010 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2011 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2012 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2013 POSSIBILITY OF SUCH DAMAGE.
2015 Contact Warner Losh if you have any questions about your use of