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/updating-src.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 arm port has split armv6 into armv6 and armv7. armv7 is now
56 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
57 and are running a kernel from before r324363, you will need to add
58 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
61 When building multiple kernels using KERNCONF, non-existent KERNCONF
62 files will produce an error and buildkernel will fail. Previously
63 missing KERNCONF files silently failed giving no indication as to
64 why, only to subsequently discover during installkernel that the
65 desired kernel was never built in the first place.
68 The default serial number format for CTL LUNs has changed. This will
69 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
70 or iSCSI clients care about their LUNs' serial numbers. Users who
71 require serial number stability should hardcode serial numbers in
75 For 32-bit arm compiled for hard-float support, soft-floating point
76 binaries now always get their shared libraries from
77 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
78 /usr/libsoft also existed). Only users with a hard-float ld.so, but
79 soft-float everything else should be affected.
82 The geli password typed at boot is now hidden. To restore the previous
83 behavior, see geli(8) for configuration options.
86 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
87 sysctl values. Minor nit, but requires a rebuild of both world/kernel
91 "make check" behavior (made in ^/head@r295380) has been changed to
92 execute from a limited sandbox, as opposed to executing from
96 - The "beforecheck" and "aftercheck" targets are now specified.
97 - ${CHECKDIR} (added in commit noted above) has been removed.
98 - Legacy behavior can be enabled by setting
99 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
101 If the limited sandbox mode is enabled, "make check" will execute
102 "make distribution", then install, execute the tests, and clean up the
103 sandbox if successful.
105 The "make distribution" and "make install" targets are typically run as
106 root to set appropriate permissions and ownership at installation time.
107 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
108 environment if executing "make check" with limited sandbox mode using
109 an unprivileged user.
112 Since the switch to GPT disk labels, fsck for UFS/FFS has been
113 unable to automatically find alternate superblocks. As of r322297,
114 the information needed to find alternate superblocks has been
115 moved to the end of the area reserved for the boot block.
116 Filesystems created with a newfs of this vintage or later
117 will create the recovery information. If you have a filesystem
118 created prior to this change and wish to have a recovery block
119 created for your filesystem, you can do so by running fsck in
120 forground mode (i.e., do not use the -p or -y options). As it
121 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
122 to which you should answer yes.
125 As of r321665, an NFSv4 server configuration that services
126 Kerberos mounts or clients that do not support the uid/gid in
127 owner/owner_group string capability, must explicitly enable
128 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
129 machine's /etc/rc.conf file.
132 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
133 Please see the 20141231 entry below for information about prerequisites
134 and upgrading, if you are not already using clang 3.5.0 or higher.
137 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
138 r-commands (rlogin, rsh, etc.) to be built with the base system.
141 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
142 a very major ABI incompatible change, so users of FreeBSD/powerpc must
143 be careful when performing source upgrades. It is best to run
144 'make installworld' from an alternate root system, either a live
145 CD/memory stick, or a temporary root partition. Additionally, all ports
146 must be recompiled. powerpc64 is largely unaffected, except in the case
147 of 32-bit compatibility. All 32-bit binaries will be affected.
150 Forward compatibility for the "ino64" project have been committed. This
151 will allow most new binaries to run on older kernels in a limited
152 fashion. This prevents many of the common foot-shooting actions in the
153 upgrade as well as the limited ability to roll back the kernel across
154 the ino64 upgrade. Complicated use cases may not work properly, though
155 enough simpler ones work to allow recovery in most situations.
158 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
159 if you require the GPL compiler.
162 The internal ABI used for communication between the NFS kernel modules
163 was changed by r320085, so __FreeBSD_version was bumped to
164 ensure all the NFS related modules are updated together.
167 The ABI of struct event was changed by extending the data
168 member to 64bit and adding ext fields. For upgrade, same
169 precautions as for the entry 20170523 "ino64" must be
173 The GNU roff toolchain has been removed from base. To render manpages
174 which are not supported by mandoc(1), man(1) can fallback on GNU roff
175 from ports (and recommends to install it).
176 To render roff(7) documents, consider using GNU roff from ports or the
177 heirloom doctools roff toolchain from ports via pkg install groff or
178 via pkg install heirloom-doctools.
181 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
182 smaller runtime footprint builds. This is useful for embedded systems
183 which only require one chipset support.
185 If you load it as a module, make sure this is in /boot/loader.conf:
189 This will load the HAL, all chip/RF backends and if_ath_pci.
190 If you have if_ath_pci in /boot/loader.conf, ensure it is after
191 if_ath or it will not load any HAL chipset support.
193 If you want to selectively load things (eg on ye cheape ARM/MIPS
194 platforms where RAM is at a premium) you should:
197 * load the chip modules in question
198 * load ath_rate, ath_dfs
200 * load if_ath_pci and/or if_ath_ahb depending upon your particular
201 bus bind type - this is where probe/attach is done.
203 For further comments/feedback, poke adrian@ .
206 The "ino64" 64-bit inode project has been committed, which extends
207 a number of types to 64 bits. Upgrading in place requires care and
208 adherence to the documented upgrade procedure.
210 If using a custom kernel configuration ensure that the
211 COMPAT_FREEBSD11 option is included (as during the upgrade the
212 system will be running the ino64 kernel with the existing world).
214 For the safest in-place upgrade begin by removing previous build
215 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
216 full procedure documented below under the heading "To rebuild
217 everything and install it on the current system." Specifically,
218 a reboot is required after installing the new kernel before
222 The NATM framework including the en(4), fatm(4), hatm(4), and
223 patm(4) devices has been removed. Consumers should plan a
224 migration before the end-of-life date for FreeBSD 11.
227 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
228 diff has not been implemented, if those are needed a newer version of
229 GNU diff is available via the diffutils package under the gdiff name.
232 As of r316810 for ipfilter, keep frags is no longer assumed when
233 keep state is specified in a rule. r316810 aligns ipfilter with
234 documentation in man pages separating keep frags from keep state.
235 This allows keep state to be specified without forcing keep frags
236 and allows keep frags to be specified independently of keep state.
237 To maintain previous behaviour, also specify keep frags with
238 keep state (as documented in ipf.conf.5).
241 arm64 builds now use the base system LLD 4.0.0 linker by default,
242 instead of requiring that the aarch64-binutils port or package be
243 installed. To continue using aarch64-binutils, set
244 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
247 The UDP optimization in entry 20160818 that added the sysctl
248 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
249 packets will no longer be treated as L3 broadcast packets.
252 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
253 use any explicitly assigned loopback address available in the jail
254 instead of using the first assigned address of the jail.
257 The ctl.ko module no longer implements the iSCSI target frontend:
258 cfiscsi.ko does instead.
260 If building cfiscsi.ko as a kernel module, the module can be loaded
261 via one of the following methods:
262 - `cfiscsi_load="YES"` in loader.conf(5).
263 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
264 - ctladm(8)/ctld(8), when compiled with iSCSI support
265 (`WITH_ISCSI=yes` in src.conf(5))
267 Please see cfiscsi(4) for more details.
270 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
271 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
272 same source (previously, the dependency of mmcsd.ko on mmc.ko was
273 missing, but mmcsd.ko now will refuse to load if it is incompatible
277 The syntax of ipfw(8) named states was changed to avoid ambiguity.
278 If you have used named states in the firewall rules, you need to modify
279 them after installworld and before rebooting. Now named states must
280 be prefixed with colon.
283 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
284 removed as the userland we provide cannot use them. The KMS version
285 (sys/dev/drm2) supports the same hardware.
288 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
289 Please see the 20141231 entry below for information about prerequisites
290 and upgrading, if you are not already using clang 3.5.0 or higher.
293 The code that provides support for ZFS .zfs/ directory functionality
294 has been reimplemented. It's not possible now to create a snapshot
295 by mkdir under .zfs/snapshot/. That should be the only user visible
299 EISA bus support has been removed. The WITH_EISA option is no longer
303 MCA bus support has been removed.
306 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
307 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
310 The EM_MULTIQUEUE kernel configuration option is deprecated now that
311 the em(4) driver conforms to iflib specifications.
314 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
315 IFLIB. If you have a custom kernel configuration that excludes em(4)
316 but you use igb(4), you need to re-add em(4) to your custom configuration.
319 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
320 Please see the 20141231 entry below for information about prerequisites
321 and upgrading, if you are not already using clang 3.5.0 or higher.
324 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
325 Please see the 20141231 entry below for information about prerequisites
326 and upgrading, if you are not already using clang 3.5.0 or higher.
329 The layout of the pmap structure has changed for powerpc to put the pmap
330 statistics at the front for all CPU variations. libkvm(3) and all tools
331 that link against it need to be recompiled.
334 isl(4) and cyapa(4) drivers now require a new driver,
335 chromebook_platform(4), to work properly on Chromebook-class hardware.
336 On other types of hardware the drivers may need to be configured using
337 device hints. Please see the corresponding manual pages for details.
340 The urtwn(4) driver was merged into rtwn(4) and now consists of
341 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
343 Also, firmware for RTL8188CE was renamed due to possible name
344 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
347 GNU rcs has been removed from base. It is available as packages:
348 - rcs: Latest GPLv3 GNU rcs version.
349 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
353 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
354 modules now requires that the kernel configuration contain the
355 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
358 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
359 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
362 Relocatable object files with the extension of .So have been renamed
363 to use an extension of .pico instead. The purpose of this change is
364 to avoid a name clash with shared libraries on case-insensitive file
365 systems. On those file systems, foo.So is the same file as foo.so.
368 GNU rcs has been turned off by default. It can (temporarily) be built
369 again by adding WITH_RCS knob in src.conf.
370 Otherwise, GNU rcs is available from packages:
371 - rcs: Latest GPLv3 GNU rcs version.
372 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
375 The backup_uses_rcs functionality has been removed from rc.subr.
378 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
379 two separate components, QUEUE_MACRO_DEBUG_TRACE and
380 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
381 QUEUE_MACRO_DEBUG behavior.
384 r304787 changed some ioctl interfaces between the iSCSI userspace
385 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
386 rebuilt to work with new kernels. __FreeBSD_version has been bumped
390 The UDP receive code has been updated to only treat incoming UDP
391 packets that were addressed to an L2 broadcast address as L3
392 broadcast packets. It is not expected that this will affect any
393 standards-conforming UDP application. The new behaviour can be
394 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
398 Remove the openbsd_poll system call.
399 __FreeBSD_version has been bumped because of this.
402 The libc stub for the pipe(2) system call has been replaced with
403 a wrapper that calls the pipe2(2) system call and the pipe(2)
404 system call is now only implemented by the kernels that include
405 "options COMPAT_FREEBSD10" in their config file (this is the
406 default). Users should ensure that this option is enabled in
407 their kernel or upgrade userspace to r302092 before upgrading their
411 CAM will now strip leading spaces from SCSI disks' serial numbers.
412 This will affect users who create UFS filesystems on SCSI disks using
413 those disk's diskid device nodes. For example, if /etc/fstab
414 previously contained a line like
415 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
416 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
417 transforms like gmirror may also be affected. ZFS users should
421 The bitstring(3) API has been updated with new functionality and
422 improved performance. But it is binary-incompatible with the old API.
423 Objects built with the new headers may not be linked against objects
424 built with the old headers.
427 The brk and sbrk functions have been removed from libc on arm64.
428 Binutils from ports has been updated to not link to these
429 functions and should be updated to the latest version before
430 installing a new libc.
433 The armv6 port now defaults to hard float ABI. Limited support
434 for running both hardfloat and soft float on the same system
435 is available using the libraries installed with -DWITH_LIBSOFT.
436 This has only been tested as an upgrade path for installworld
437 and packages may fail or need manual intervention to run. New
438 packages will be needed.
440 To update an existing self-hosted armv6hf system, you must add
441 TARGET_ARCH=armv6 on the make command line for both the build
442 and the install steps.
445 Kernel modules compiled outside of a kernel build now default to
446 installing to /boot/modules instead of /boot/kernel. Many kernel
447 modules built this way (such as those in ports) already overrode
448 KMODDIR explicitly to install into /boot/modules. However,
449 manually building and installing a module from /sys/modules will
450 now install to /boot/modules instead of /boot/kernel.
453 The CAM I/O scheduler has been committed to the kernel. There should be
454 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
455 list of known rogues that claim support for this but actually corrupt
456 data is believed to be complete, be on the lookout for data
457 corruption. The known rogue list is believed to be complete:
459 o Crucial MX100, M550 drives with MU01 firmware.
460 o Micron M510 and M550 drives with MU01 firmware.
461 o Micron M500 prior to MU07 firmware
462 o Samsung 830, 840, and 850 all firmwares
463 o FCCT M500 all firmwares
465 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
466 with working NCQ TRIM. For Micron branded drives, see your sales rep for
467 updated firmware. Black listed drives will work correctly because these
468 drives work correctly so long as no NCQ TRIMs are sent to them. Given
469 this list is the same as found in Linux, it's believed there are no
470 other rogues in the market place. All other models from the above
473 To be safe, if you are at all concerned, you can quirk each of your
474 drives to prevent NCQ from being sent by setting:
475 kern.cam.ada.X.quirks="0x2"
476 in loader.conf. If the drive requires the 4k sector quirk, set the
480 The FAST_DEPEND build option has been removed and its functionality is
481 now the one true way. The old mkdep(1) style of 'make depend' has
482 been removed. See 20160311 for further details.
485 Resource range types have grown from unsigned long to uintmax_t. All
486 drivers, and anything using libdevinfo, need to be recompiled.
489 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
490 builds. It no longer runs mkdep(1) during 'make depend', and the
491 'make depend' stage can safely be skipped now as it is auto ran
492 when building 'make all' and will generate all SRCS and DPSRCS before
493 building anything else. Dependencies are gathered at compile time with
494 -MF flags kept in separate .depend files per object file. Users should
495 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
499 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
500 kernel modules. Therefore, if you load any kernel modules at boot time,
501 please install the boot loaders after you install the kernel, but before
505 make kernel KERNCONF=YOUR_KERNEL_HERE
506 make -C sys/boot install
507 <reboot in single user>
509 Then follow the usual steps, described in the General Notes section,
513 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
514 see the 20141231 entry below for information about prerequisites and
515 upgrading, if you are not already using clang 3.5.0 or higher.
518 The AIO subsystem is now a standard part of the kernel. The
519 VFS_AIO kernel option and aio.ko kernel module have been removed.
520 Due to stability concerns, asynchronous I/O requests are only
521 permitted on sockets and raw disks by default. To enable
522 asynchronous I/O requests on all file types, set the
523 vfs.aio.enable_unsafe sysctl to a non-zero value.
526 The ELF object manipulation tool objcopy is now provided by the
527 ELF Tool Chain project rather than by GNU binutils. It should be a
528 drop-in replacement, with the addition of arm64 support. The
529 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
530 to obtain the GNU version if necessary.
533 Building ZFS pools on top of zvols is prohibited by default. That
534 feature has never worked safely; it's always been prone to deadlocks.
535 Using a zvol as the backing store for a VM guest's virtual disk will
536 still work, even if the guest is using ZFS. Legacy behavior can be
537 restored by setting vfs.zfs.vol.recursive=1.
540 The NONE and HPN patches has been removed from OpenSSH. They are
541 still available in the security/openssh-portable port.
544 With the addition of ypldap(8), a new _ypldap user is now required
545 during installworld. "mergemaster -p" can be used to add the user
546 prior to installworld, as documented in the handbook.
549 The tftp loader (pxeboot) now uses the option root-path directive. As a
550 consequence it no longer looks for a pxeboot.4th file on the tftp
551 server. Instead it uses the regular /boot infrastructure as with the
555 The code to start recording plug and play data into the modules has
556 been committed. While the old tools will properly build a new kernel,
557 a number of warnings about "unknown metadata record 4" will be produced
558 for an older kldxref. To avoid such warnings, make sure to rebuild
559 the kernel toolchain (or world). Make sure that you have r292078 or
560 later when trying to build 292077 or later before rebuilding.
563 Debug data files are now built by default with 'make buildworld' and
564 installed with 'make installworld'. This facilitates debugging but
565 requires more disk space both during the build and for the installed
566 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
570 r291527 changed the internal interface between the nfsd.ko and
571 nfscommon.ko modules. As such, they must both be upgraded to-gether.
572 __FreeBSD_version has been bumped because of this.
575 Add support for unicode collation strings leads to a change of
576 order of files listed by ls(1) for example. To get back to the old
577 behaviour, set LC_COLLATE environment variable to "C".
579 Databases administrators will need to reindex their databases given
580 collation results will be different.
582 Due to a bug in install(1) it is recommended to remove the ancient
583 locales before running make installworld.
585 rm -rf /usr/share/locale/*
588 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
589 libcrypto.so.7 or libssl.so.7 must be recompiled.
592 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
593 Kernel modules isp_2400_multi and isp_2500_multi were removed and
594 should be replaced with isp_2400 and isp_2500 modules respectively.
597 The build previously allowed using 'make -n' to not recurse into
598 sub-directories while showing what commands would be executed, and
599 'make -n -n' to recursively show commands. Now 'make -n' will recurse
600 and 'make -N' will not.
603 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
604 and etcupdate will now use this file. A custom sendmail.cf is now
605 updated via this mechanism rather than via installworld. If you had
606 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
607 want to remove the exclusion or change it to "always install".
608 /etc/mail/sendmail.cf is now managed the same way regardless of
609 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
610 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
613 Compatibility shims for legacy ATA device names have been removed.
614 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
615 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
616 environment variables, /dev/ad* and /dev/ar* symbolic links.
619 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
620 Please see the 20141231 entry below for information about prerequisites
621 and upgrading, if you are not already using clang 3.5.0 or higher.
624 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
625 and renamed from .symbols to .debug. This reduces the size requirements
626 on the boot partition or file system and provides consistency with
627 userland debug files.
629 When using the supported kernel installation method the
630 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
631 as is done with /boot/kernel.
633 Developers wishing to maintain the historical behavior of installing
634 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
637 The wireless drivers had undergone changes that remove the 'parent
638 interface' from the ifconfig -l output. The rc.d network scripts
639 used to check presence of a parent interface in the list, so old
640 scripts would fail to start wireless networking. Thus, etcupdate(3)
641 or mergemaster(8) run is required after kernel update, to update your
642 rc.d scripts in /etc.
645 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
646 These configurations are now automatically interpreted as
647 'scrub fragment reassemble'.
650 Kernel-loadable modules for the random(4) device are back. To use
651 them, the kernel must have
654 options RANDOM_LOADABLE
656 kldload(8) can then be used to load random_fortuna.ko
657 or random_yarrow.ko. Please note that due to the indirect
658 function calls that the loadable modules need to provide,
659 the build-in variants will be slightly more efficient.
661 The random(4) kernel option RANDOM_DUMMY has been retired due to
662 unpopularity. It was not all that useful anyway.
665 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
666 Control over building the ELF Tool Chain tools is now provided by
667 the WITHOUT_TOOLCHAIN knob.
670 The polarity of Pulse Per Second (PPS) capture events with the
671 uart(4) driver has been corrected. Prior to this change the PPS
672 "assert" event corresponded to the trailing edge of a positive PPS
673 pulse and the "clear" event was the leading edge of the next pulse.
675 As the width of a PPS pulse in a typical GPS receiver is on the
676 order of 1 millisecond, most users will not notice any significant
677 difference with this change.
679 Anyone who has compensated for the historical polarity reversal by
680 configuring a negative offset equal to the pulse width will need to
681 remove that workaround.
684 The default group assigned to /dev/dri entries has been changed
685 from 'wheel' to 'video' with the id of '44'. If you want to have
686 access to the dri devices please add yourself to the video group
689 # pw groupmod video -m $USER
692 The menu.rc and loader.rc files will now be replaced during
693 upgrades. Please migrate local changes to menu.rc.local and
694 loader.rc.local instead.
697 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
698 strings and strip have been removed. The src.conf(5) knob
699 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
702 As ZFS requires more kernel stack pages than is the default on some
703 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
704 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
706 Please consider using 'options KSTACK_PAGES=X' where X is greater
707 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
710 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
711 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
712 default, i.e., they will not contain "::". For example, instead
713 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
714 to have a more specific match, such as different map entries for
715 IPv6:0:0 vs IPv6:0. This change requires that configuration
716 data (including maps, files, classes, custom ruleset, etc.) must
717 use the same format, so make certain such configuration data is
718 upgrading. As a very simple check search for patterns like
719 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
720 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
721 the cf option UseCompressedIPv6Addresses.
724 The default kernel entropy-processing algorithm is now
725 Fortuna, replacing Yarrow.
727 Assuming you have 'device random' in your kernel config
728 file, the configurations allow a kernel option to override
729 this default. You may choose *ONE* of:
731 options RANDOM_YARROW # Legacy /dev/random algorithm.
732 options RANDOM_DUMMY # Blocking-only driver.
734 If you have neither, you get Fortuna. For most people,
735 read no further, Fortuna will give a /dev/random that works
736 like it always used to, and the difference will be irrelevant.
738 If you remove 'device random', you get *NO* kernel-processed
739 entropy at all. This may be acceptable to folks building
740 embedded systems, but has complications. Carry on reading,
741 and it is assumed you know what you need.
743 *PLEASE* read random(4) and random(9) if you are in the
744 habit of tweaking kernel configs, and/or if you are a member
745 of the embedded community, wanting specific and not-usual
746 behaviour from your security subsystems.
748 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
749 random', you will NOT have a functioning /dev/random, and
750 many cryptographic features will not work, including SSH.
751 You may also find strange behaviour from the random(3) set
752 of library functions, in particular sranddev(3), srandomdev(3)
753 and arc4random(3). The reason for this is that the KERN_ARND
754 sysctl only returns entropy if it thinks it has some to
755 share, and with RANDOM_DUMMY or no 'device random' this
759 An additional fix for the issue described in the 20150614 sendmail
760 entry below has been been committed in revision 284717.
763 FreeBSD's old make (fmake) has been removed from the system. It is
764 available as the devel/fmake port or via pkg install fmake.
767 The fix for the issue described in the 20150614 sendmail entry
768 below has been been committed in revision 284436. The work
769 around described in that entry is no longer needed unless the
770 default setting is overridden by a confDH_PARAMETERS configuration
771 setting of '5' or pointing to a 512 bit DH parameter file.
774 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
775 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
776 and devel/kyua to version 0.20+ and adjust any calling code to work
777 with Kyuafile and kyua.
780 The import of openssl to address the FreeBSD-SA-15:10.openssl
781 security advisory includes a change which rejects handshakes
782 with DH parameters below 768 bits. sendmail releases prior
783 to 8.15.2 (not yet released), defaulted to a 512 bit
784 DH parameter setting for client connections. To work around
785 this interoperability, sendmail can be configured to use a
786 2048 bit DH parameter by:
788 1. Edit /etc/mail/`hostname`.mc
789 2. If a setting for confDH_PARAMETERS does not exist or
790 exists and is set to a string beginning with '5',
792 3. If a setting for confDH_PARAMETERS exists and is set to
793 a file path, create a new file with:
794 openssl dhparam -out /path/to/file 2048
795 4. Rebuild the .cf file:
796 cd /etc/mail/; make; make install
798 cd /etc/mail/; make restart
800 A sendmail patch is coming, at which time this file will be
804 Generation of legacy formatted entries have been disabled by default
805 in pwd_mkdb(8), as all base system consumers of the legacy formatted
806 entries were converted to use the new format by default when the new,
807 machine independent format have been added and supported since FreeBSD
810 Please see the pwd_mkdb(8) manual page for further details.
813 Clang and llvm have been upgraded to 3.6.1 release. Please see the
814 20141231 entry below for information about prerequisites and upgrading,
815 if you are not already using 3.5.0 or higher.
818 TI platform code switched to using vendor DTS files and this update
819 may break existing systems running on Beaglebone, Beaglebone Black,
822 - dtb files should be regenerated/reinstalled. Filenames are the
823 same but content is different now
824 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
825 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
826 addressing scheme is now pin 25 on /dev/gpioc3.
827 - Pandaboard: /etc/ttys should be updated, serial console device is
828 now /dev/ttyu2, not /dev/ttyu0
831 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
832 If you need the GNU extension from groff soelim(1), install groff
833 from package: pkg install groff, or via ports: textproc/groff.
836 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
837 defined in symlink(7); previously symlinks were silently ignored.
840 The const qualifier has been removed from iconv(3) to comply with
841 POSIX. The ports tree is aware of this from r384038 onwards.
844 Libraries specified by LIBADD in Makefiles must have a corresponding
845 DPADD_<lib> variable to ensure correct dependencies. This is now
846 enforced in src.libnames.mk.
849 From legacy ata(4) driver was removed support for SATA controllers
850 supported by more functional drivers ahci(4), siis(4) and mvs(4).
851 Kernel modules ataahci and ataadaptec were removed completely,
852 replaced by ahci and mvs modules respectively.
855 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
856 the 20141231 entry below for information about prerequisites and
857 upgrading, if you are not already using 3.5.0 or higher.
860 The 32-bit PowerPC kernel has been changed to a position-independent
861 executable. This can only be booted with a version of loader(8)
862 newer than January 31, 2015, so make sure to update both world and
863 kernel before rebooting.
866 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
867 but before r278950, the RNG was not seeded properly. Immediately
868 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
869 ssh keys or openssl keys) that were generated w/ a kernel from that
870 range. This does not affect programs that directly used /dev/random
871 or /dev/urandom. All userland uses of arc4random(3) are affected.
874 The autofs(4) ABI was changed in order to restore binary compatibility
875 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
879 The powerpc64 kernel has been changed to a position-independent
880 executable. This can only be booted with a new version of loader(8),
881 so make sure to update both world and kernel before rebooting.
884 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
885 only release, no new features have been added. Please see the 20141231
886 entry below for information about prerequisites and upgrading, if you
887 are not already using 3.5.0.
890 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
891 taken from the ELF Tool Chain project rather than GNU binutils. They
892 should be drop-in replacements, with the addition of arm64 support.
893 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
894 binutils tools, if necessary. See 20150805 for updated information.
897 The default Unbound configuration now enables remote control
898 using a local socket. Users who have already enabled the
899 local_unbound service should regenerate their configuration
900 by running "service local_unbound setup" as root.
903 The GNU texinfo and GNU info pages have been removed.
904 To be able to view GNU info pages please install texinfo from ports.
907 Clang, llvm and lldb have been upgraded to 3.5.0 release.
909 As of this release, a prerequisite for building clang, llvm and lldb is
910 a C++11 capable compiler and C++11 standard library. This means that to
911 be able to successfully build the cross-tools stage of buildworld, with
912 clang as the bootstrap compiler, your system compiler or cross compiler
913 should either be clang 3.3 or later, or gcc 4.8 or later, and your
914 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
917 On any standard FreeBSD 10.x or 11.x installation, where clang and
918 libc++ are on by default (that is, on x86 or arm), this should work out
921 On 9.x installations where clang is enabled by default, e.g. on x86 and
922 powerpc, libc++ will not be enabled by default, so libc++ should be
923 built (with clang) and installed first. If both clang and libc++ are
924 missing, build clang first, then use it to build libc++.
926 On 8.x and earlier installations, upgrade to 9.x first, and then follow
927 the instructions for 9.x above.
929 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
930 default, and do not build clang.
932 Many embedded systems are resource constrained, and will not be able to
933 build clang in a reasonable time, or in some cases at all. In those
934 cases, cross building bootable systems on amd64 is a workaround.
936 This new version of clang introduces a number of new warnings, of which
937 the following are most likely to appear:
941 This warns in two cases, for both C and C++:
942 * When the code is trying to take the absolute value of an unsigned
943 quantity, which is effectively a no-op, and almost never what was
944 intended. The code should be fixed, if at all possible. If you are
945 sure that the unsigned quantity can be safely cast to signed, without
946 loss of information or undefined behavior, you can add an explicit
947 cast, or disable the warning.
949 * When the code is trying to take an absolute value, but the called
950 abs() variant is for the wrong type, which can lead to truncation.
951 If you want to disable the warning instead of fixing the code, please
952 make sure that truncation will not occur, or it might lead to unwanted
955 -Wtautological-undefined-compare and
956 -Wundefined-bool-conversion
958 These warn when C++ code is trying to compare 'this' against NULL, while
959 'this' should never be NULL in well-defined C++ code. However, there is
960 some legacy (pre C++11) code out there, which actively abuses this
961 feature, which was less strictly defined in previous C++ versions.
963 Squid and openjdk do this, for example. The warning can be turned off
964 for C++98 and earlier, but compiling the code in C++11 mode might result
965 in unexpected behavior; for example, the parts of the program that are
966 unreachable could be optimized away.
969 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
970 kernel sources have been removed. The .h files remain, since some
971 utilities include them. This will need to be fixed later.
972 If "mount -t oldnfs ..." is attempted, it will fail.
973 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
974 the utilities will report errors.
977 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
978 directories to top level SUBDIR variable when their parent
979 directory is included in LOCAL_DIRS. Users with build systems with
980 such hierarchies and without SUBDIR entries in the parent
981 directory Makefiles should add them or add the directories to
985 faith(4) and faithd(8) have been removed from the base system. Faith
986 has been obsolete for a very long time.
989 vt(4), the new console driver, is enabled by default. It brings
990 support for Unicode and double-width characters, as well as
991 support for UEFI and integration with the KMS kernel video
994 You may need to update your console settings in /etc/rc.conf,
995 most probably the keymap. During boot, /etc/rc.d/syscons will
996 indicate what you need to do.
998 vt(4) still has issues and lacks some features compared to
999 syscons(4). See the wiki for up-to-date information:
1000 https://wiki.freebsd.org/Newcons
1002 If you want to keep using syscons(4), you can do so by adding
1003 the following line to /boot/loader.conf:
1007 pjdfstest has been integrated into kyua as an opt-in test suite.
1008 Please see share/doc/pjdfstest/README for more details on how to
1012 gperf has been removed from the base system for architectures
1013 that use clang. Ports that require gperf will obtain it from the
1017 pjdfstest has been moved from tools/regression/pjdfstest to
1021 At svn r271982, The default linux compat kernel ABI has been adjusted
1022 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1023 update. If you wish to continue using the linux-f10 compat ports,
1024 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1025 encouraged to update their linux-compat packages to linux-c6 during
1026 their next update cycle.
1029 The ofwfb driver, used to provide a graphics console on PowerPC when
1030 using vt(4), no longer allows mmap() of all physical memory. This
1031 will prevent Xorg on PowerPC with some ATI graphics cards from
1032 initializing properly unless x11-servers/xorg-server is updated to
1036 The xdev targets have been converted to using TARGET and
1037 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1040 The default unbound configuration has been modified to address
1041 issues with reverse lookups on networks that use private
1042 address ranges. If you use the local_unbound service, run
1043 "service local_unbound setup" as root to regenerate your
1044 configuration, then "service local_unbound reload" to load the
1048 The GNU texinfo and GNU info pages are not built and installed
1049 anymore, WITH_INFO knob has been added to allow to built and install
1051 UPDATE: see 20150102 entry on texinfo's removal
1054 The GNU readline library is now an INTERNALLIB - that is, it is
1055 statically linked into consumers (GDB and variants) in the base
1056 system, and the shared library is no longer installed. The
1057 devel/readline port is available for third party software that
1061 The Itanium architecture (ia64) has been removed from the list of
1062 known architectures. This is the first step in the removal of the
1066 Commit r268115 has added NFSv4.1 server support, merged from
1067 projects/nfsv4.1-server. Since this includes changes to the
1068 internal interfaces between the NFS related modules, a full
1069 build of the kernel and modules will be necessary.
1070 __FreeBSD_version has been bumped.
1073 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1074 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1075 which differs from the behaviour controlled by this knob.)
1078 Maximal length of the serial number in CTL was increased from 16 to
1079 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1080 and ctld, need to be rebuilt to work with a new kernel.
1083 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1084 1 respectively to match the upstream numbers. They were out of
1085 sync because, when they were originally added to FreeBSD, the
1086 upstream versions were not respected. These libraries are private
1087 and not yet built by default, so renumbering them should be a
1088 non-issue. However, unclean source trees will yield broken test
1089 programs once the operator executes "make delete-old-libs" after a
1090 "make installworld".
1092 Additionally, the atf-sh binary was made private by moving it into
1093 /usr/libexec/. Already-built shell test programs will keep the
1094 path to the old binary so they will break after "make delete-old"
1097 If you are using WITH_TESTS=yes (not the default), wipe the object
1098 tree and rebuild from scratch to prevent spurious test failures.
1099 This is only needed once: the misnumbered libraries and misplaced
1100 binaries have been added to OptionalObsoleteFiles.inc so they will
1101 be removed during a clean upgrade.
1104 Clang and llvm have been upgraded to 3.4.1 release.
1107 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1108 be removed to avoid issues in the future (and has been added to
1112 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1113 past, it affected all builds that used the bsd.*.mk files. The old
1114 behavior was a bug, but people may have relied upon it. To get this
1115 behavior back, you can .include /etc/src.conf from /etc/make.conf
1116 (which is still global and isn't changed). This also changes the
1117 behavior of incremental builds inside the tree of individual
1118 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1119 Although this has survived make universe and some upgrade scenarios,
1120 other upgrade scenarios may have broken. At least one form of
1121 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1122 as well... In cases where MAKESYSPATH isn't working with this
1123 setting, you'll need to set it to the full path to your tree.
1125 One side effect of all this cleaning up is that bsd.compiler.mk
1126 is no longer implicitly included by bsd.own.mk. If you wish to
1127 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1131 The lindev device has been removed since /dev/full has been made a
1132 standard device. __FreeBSD_version has been bumped.
1135 The knob WITHOUT_VI was added to the base system, which controls
1136 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1137 in order to reorder files share/termcap and didn't build ex(1) as a
1138 build tool, so building/installing with WITH_VI is highly advised for
1139 build hosts for older releases.
1141 This issue has been fixed in stable/9 and stable/10 in r277022 and
1142 r276991, respectively.
1145 The YES_HESIOD knob has been removed. It has been obsolete for
1146 a decade. Please move to using WITH_HESIOD instead or your builds
1147 will silently lack HESIOD.
1150 The uart(4) driver has been changed with respect to its handling
1151 of the low-level console. Previously the uart(4) driver prevented
1152 any process from changing the baudrate or the CLOCAL and HUPCL
1153 control flags. By removing the restrictions, operators can make
1154 changes to the serial console port without having to reboot.
1155 However, when getty(8) is started on the serial device that is
1156 associated with the low-level console, a misconfigured terminal
1157 line in /etc/ttys will now have a real impact.
1158 Before upgrading the kernel, make sure that /etc/ttys has the
1159 serial console device configured as 3wire without baudrate to
1160 preserve the previous behaviour. E.g:
1161 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1164 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1165 to improve performance. To re-enable it, if needed, run rpcbind
1166 with command line option -W.
1169 Switched back to the GPL dtc compiler due to updates in the upstream
1170 dts files not being supported by the BSDL dtc compiler. You will need
1171 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1172 may result while building dtb files during a kernel build if you fail
1173 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1176 Clang and llvm have been upgraded to 3.4 release.
1179 The nve(4) driver has been removed. Please use the nfe(4) driver
1180 for NVIDIA nForce MCP Ethernet adapters instead.
1183 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1184 This could cause certain C++ applications using shared libraries built
1185 against the previous version of libc++ to crash. The incompatibility
1186 has now been fixed, but any C++ applications or shared libraries built
1187 between r261283 and r261801 should be recompiled.
1190 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1191 capability mode support. Please note that enabling the feature in
1192 kernel is still highly recommended.
1195 OpenSSH is now built with sandbox support, and will use sandbox as
1196 the default privilege separation method. This requires Capsicum
1197 capability mode support in kernel.
1200 The libelf and libdwarf libraries have been updated to newer
1201 versions from upstream. Shared library version numbers for
1202 these two libraries were bumped. Any ports or binaries
1203 requiring these two libraries should be recompiled.
1204 __FreeBSD_version is bumped to 1100006.
1207 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1208 instead of providing an explicit one, this would prevent such
1209 Makefile from providing its own Kyuafile in the future during
1210 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1211 intervention is needed to clean an objdir if you use NO_CLEAN:
1212 # find /usr/obj -name Kyuafile | xargs rm -f
1215 The behavior of gss_pseudo_random() for the krb5 mechanism
1216 has changed, for applications requesting a longer random string
1217 than produced by the underlying enctype's pseudo-random() function.
1218 In particular, the random string produced from a session key of
1219 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1220 be different at the 17th octet and later, after this change.
1221 The counter used in the PRF+ construction is now encoded as a
1222 big-endian integer in accordance with RFC 4402.
1223 __FreeBSD_version is bumped to 1100004.
1226 The WITHOUT_ATF build knob has been removed and its functionality
1227 has been subsumed into the more generic WITHOUT_TESTS. If you were
1228 using the former to disable the build of the ATF libraries, you
1229 should change your settings to use the latter.
1232 The default version of mtree is nmtree which is obtained from
1233 NetBSD. The output is generally the same, but may vary
1234 slightly. If you found you need identical output adding
1235 "-F freebsd9" to the command line should do the trick. For the
1236 time being, the old mtree is available as fmtree.
1239 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1240 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1241 1.1.4_8 and verify bsdyml not linked in, before running "make
1243 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1245 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1248 The stable/10 branch has been created in subversion from head
1252 The rc.d/jail script has been updated to support jail(8)
1253 configuration file. The "jail_<jname>_*" rc.conf(5) variables
1254 for per-jail configuration are automatically converted to
1255 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
1256 This is transparently backward compatible. See below about some
1257 incompatibilities and rc.conf(5) manual page for more details.
1259 These variables are now deprecated in favor of jail(8) configuration
1260 file. One can use "rc.d/jail config <jname>" command to generate
1261 a jail(8) configuration file in /var/run/jail.<jname>.conf without
1262 running the jail(8) utility. The default pathname of the
1263 configuration file is /etc/jail.conf and can be specified by
1264 using $jail_conf or $jail_<jname>_conf variables.
1266 Please note that jail_devfs_ruleset accepts an integer at
1267 this moment. Please consider to rewrite the ruleset name
1271 BIND has been removed from the base system. If all you need
1272 is a local resolver, simply enable and start the local_unbound
1273 service instead. Otherwise, several versions of BIND are
1274 available in the ports tree. The dns/bind99 port is one example.
1276 With this change, nslookup(1) and dig(1) are no longer in the base
1277 system. Users should instead use host(1) and drill(1) which are
1278 in the base system. Alternatively, nslookup and dig can
1279 be obtained by installing the dns/bind-tools port.
1282 With the addition of unbound(8), a new unbound user is now
1283 required during installworld. "mergemaster -p" can be used to
1284 add the user prior to installworld, as documented in the handbook.
1287 OpenSSH is now built with DNSSEC support, and will by default
1288 silently trust signed SSHFP records. This can be controlled with
1289 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1290 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1293 The GNU Compiler Collection and C++ standard library (libstdc++)
1294 are no longer built by default on platforms where clang is the system
1295 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1296 options in src.conf.
1299 The PROCDESC kernel option is now part of the GENERIC kernel
1300 configuration and is required for the rwhod(8) to work.
1301 If you are using custom kernel configuration, you should include
1305 The API and ABI related to the Capsicum framework was modified
1306 in backward incompatible way. The userland libraries and programs
1307 have to be recompiled to work with the new kernel. This includes the
1308 following libraries and programs, but the whole buildworld is
1309 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1310 kdump, procstat, rwho, rwhod, uniq.
1313 AES-NI intrinsic support has been added to gcc. The AES-NI module
1314 has been updated to use this support. A new gcc is required to build
1315 the aesni module on both i386 and amd64.
1318 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1319 Thus "device padlock_rng" and "device rdrand_rng" should be
1320 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1323 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1324 enables just the iconv* functionality and is now on by default.
1325 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1326 compatibility. Set WITHOUT_ICONV to build the old way.
1327 If you have been using WITH_ICONV before, you will very likely
1328 need to turn on WITH_LIBICONV_COMPAT.
1331 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1332 Illumos origin, including ZFS. If you have INVARIANTS in your
1333 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1335 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1336 locks if WITNESS option was set. Because that generated a lot of
1337 witness(9) reports and all of them were believed to be false
1338 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1339 can be used to achieve the previous behavior.
1342 Timer values in IPv6 data structures now use time_uptime instead
1343 of time_second. Although this is not a user-visible functional
1344 change, userland utilities which directly use them---ndp(8),
1345 rtadvd(8), and rtsold(8) in the base system---need to be updated
1346 to r253970 or later.
1349 find -delete can now delete the pathnames given as arguments,
1350 instead of only files found below them or if the pathname did
1351 not contain any slashes. Formerly, the following error message
1354 find: -delete: <path>: relative path potentially not safe
1356 Deleting the pathnames given as arguments can be prevented
1357 without error messages using -mindepth 1 or by changing
1358 directory and passing "." as argument to find. This works in the
1359 old as well as the new version of find.
1362 Behavior of devfs rules path matching has been changed.
1363 Pattern is now always matched against fully qualified devfs
1364 path and slash characters must be explicitly matched by
1365 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1366 subdirectories must be reviewed.
1369 The default ARM ABI has changed to the ARM EABI. The old ABI is
1370 incompatible with the ARM EABI and all programs and modules will
1371 need to be rebuilt to work with a new kernel.
1373 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1375 NOTE: Support for the old ABI will be removed in the future and
1376 users are advised to upgrade.
1379 pkg_install has been disconnected from the build if you really need it
1380 you should add WITH_PKGTOOLS in your src.conf(5).
1383 Most of network statistics structures were changed to be able
1384 keep 64-bits counters. Thus all tools, that work with networking
1385 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1388 Fix a bug that allowed a tracing process (e.g. gdb) to write
1389 to a memory-mapped file in the traced process's address space
1390 even if neither the traced process nor the tracing process had
1391 write access to that file.
1394 CVS has been removed from the base system. An exact copy
1395 of the code is available from the devel/cvs port.
1398 Some people report the following error after the switch to bmake:
1400 make: illegal option -- J
1401 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1403 *** [buildworld] Error code 2
1405 this likely due to an old instance of make in
1406 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1407 which src/Makefile will use that blindly, if it exists, so if
1408 you see the above error:
1410 rm -rf `make -V MAKEPATH`
1415 Use bmake by default.
1416 Whereas before one could choose to build with bmake via
1417 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1418 make. The goal is to remove these knobs for 10-RELEASE.
1420 It is worth noting that bmake (like gmake) treats the command
1421 line as the unit of failure, rather than statements within the
1422 command line. Thus '(cd some/where && dosomething)' is safer
1423 than 'cd some/where; dosomething'. The '()' allows consistent
1424 behavior in parallel build.
1427 Fix a bug that allows NFS clients to issue READDIR on files.
1430 The WITHOUT_IDEA option has been removed because
1431 the IDEA patent expired.
1434 The sysctl which controls TRIM support under ZFS has been renamed
1435 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1439 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1440 rather than creating it's own in the temporary directory in
1441 order allow access to bootstrapped versions of tools such as
1442 install and mtree. When upgrading from version of FreeBSD where
1443 the install command does not support -l, you will need to
1444 install a new mergemaster command if mergemaster -p is required.
1445 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1449 Legacy ATA stack, disabled and replaced by new CAM-based one since
1450 FreeBSD 9.0, completely removed from the sources. Kernel modules
1451 atadisk and atapi*, user-level tools atacontrol and burncd are
1452 removed. Kernel option `options ATA_CAM` is now permanently enabled
1456 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1457 and socketpair(2). Software, in particular Kerberos, may
1458 automatically detect and use these during building. The resulting
1459 binaries will not work on older kernels.
1462 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1463 information, see the respective 20130304 entry).
1466 Recent commits to callout(9) changed the size of struct callout,
1467 so the KBI is probably heavily disturbed. Also, some functions
1468 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1469 by macros. Every kernel module using it won't load, so rebuild
1472 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1473 but does not initialize by default (because of the new CTL_DISABLE
1474 option) to save memory. To re-enable it, remove the CTL_DISABLE
1475 option from the kernel config file or set kern.cam.ctl.disable=0
1476 in /boot/loader.conf.
1479 The ctl device has been disabled in GENERIC for i386 and amd64.
1480 This was done due to the extra memory being allocated at system
1481 initialisation time by the ctl driver which was only used if
1482 a CAM target device was created. This makes a FreeBSD system
1483 unusable on 128MB or less of RAM.
1486 A new compression method (lz4) has been merged to -HEAD. Please
1487 refer to zpool-features(7) for more information.
1489 Please refer to the "ZFS notes" section of this file for information
1490 on upgrading boot ZFS pools.
1493 A BSD-licensed patch(1) variant has been added and is installed
1494 as bsdpatch, being the GNU version the default patch.
1495 To inverse the logic and use the BSD-licensed one as default,
1496 while having the GNU version installed as gnupatch, rebuild
1497 and install world with the WITH_BSD_PATCH knob set.
1500 Due to the use of the new -l option to install(1) during build
1501 and install, you must take care not to directly set the INSTALL
1502 make variable in your /etc/make.conf, /etc/src.conf, or on the
1503 command line. If you wish to use the -C flag for all installs
1504 you may be able to add INSTALL+=-C to /etc/make.conf or
1508 The install(1) option -M has changed meaning and now takes an
1509 argument that is a file or path to append logs to. In the
1510 unlikely event that -M was the last option on the command line
1511 and the command line contained at least two files and a target
1512 directory the first file will have logs appended to it. The -M
1513 option served little practical purpose in the last decade so its
1514 use is expected to be extremely rare.
1517 After switching to Clang as the default compiler some users of ZFS
1518 on i386 systems started to experience stack overflow kernel panics.
1519 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1522 GEOM_LABEL now mangles label names read from file system metadata.
1523 Mangling affect labels containing spaces, non-printable characters,
1524 '%' or '"'. Device names in /etc/fstab and other places may need to
1528 By default, only the 10 most recent kernel dumps will be saved. To
1529 restore the previous behaviour (no limit on the number of kernel dumps
1530 stored in the dump directory) add the following line to /etc/rc.conf:
1535 With the addition of auditdistd(8), a new auditdistd user is now
1536 required during installworld. "mergemaster -p" can be used to
1537 add the user prior to installworld, as documented in the handbook.
1540 The sin6_scope_id member variable in struct sockaddr_in6 is now
1541 filled by the kernel before passing the structure to the userland via
1542 sysctl or routing socket. This means the KAME-specific embedded scope
1543 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1544 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1545 __FreeBSD_version is bumped to 1000025.
1548 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1549 This means that the world and kernel will be compiled with clang
1550 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1551 and /usr/bin/cpp. To disable this behavior and revert to building
1552 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1553 of current may need to bootstrap WITHOUT_CLANG first if the clang
1554 build fails (its compatibility window doesn't extend to the 9 stable
1558 The IPFIREWALL_FORWARD kernel option has been removed. Its
1559 functionality now turned on by default.
1562 The ZERO_COPY_SOCKET kernel option has been removed and
1563 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1564 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1565 mechanism which is not safe and may result in kernel crashes.
1566 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1567 driver supports disposeable external page sized mbuf storage.
1568 Proper replacements for both zero-copy mechanisms are under
1569 consideration and will eventually lead to complete removal
1570 of the two kernel options.
1573 The IPv4 network stack has been converted to network byte
1574 order. The following modules need to be recompiled together
1575 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1576 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1579 Support for non-MPSAFE filesystems was removed from VFS. The
1580 VFS_VERSION was bumped, all filesystem modules shall be
1584 All the non-MPSAFE filesystems have been disconnected from
1585 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1586 portalfs, smbfs, xfs.
1589 The interface cloning API and ABI has changed. The following
1590 modules need to be recompiled together with kernel:
1591 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1592 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1593 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1596 The sdhci driver was split in two parts: sdhci (generic SD Host
1597 Controller logic) and sdhci_pci (actual hardware driver).
1598 No kernel config modifications are required, but if you
1599 load sdhc as a module you must switch to sdhci_pci instead.
1602 Import the FUSE kernel and userland support into base system.
1605 The GNU sort(1) program has been removed since the BSD-licensed
1606 sort(1) has been the default for quite some time and no serious
1607 problems have been reported. The corresponding WITH_GNU_SORT
1611 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1612 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1616 The net80211(4) ABI has been changed to allow for improved driver
1617 PS-POLL and power-save support. All wireless drivers need to be
1618 recompiled to work with the new kernel.
1621 The random(4) support for the VIA hardware random number
1622 generator (`PADLOCK') is no longer enabled unconditionally.
1623 Add the padlock_rng device in the custom kernel config if
1624 needed. The GENERIC kernels on i386 and amd64 do include the
1625 device, so the change only affects the custom kernel
1629 The pf(4) packet filter ABI has been changed. pfctl(8) and
1630 snmp_pf module need to be recompiled to work with new kernel.
1633 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1634 to -HEAD. Pools that have empty_bpobj in active state can not be
1635 imported read-write with ZFS implementations that do not support
1636 this feature. For more information read the zpool-features(5)
1640 The sparc64 ZFS loader has been changed to no longer try to auto-
1641 detect ZFS providers based on diskN aliases but now requires these
1642 to be explicitly listed in the OFW boot-device environment variable.
1645 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1646 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1647 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1650 The following sysctls and tunables have been renamed for consistency
1651 with other variables:
1652 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1653 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1656 The sort utility has been replaced with BSD sort. For now, GNU sort
1657 is also available as "gnusort" or the default can be set back to
1658 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1659 installed as "bsdsort".
1662 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1663 Starting with this version the old system of ZFS pool versioning
1664 is superseded by "feature flags". This concept enables forward
1665 compatibility against certain future changes in functionality of ZFS
1666 pools. The first read-only compatible "feature flag" for ZFS pools
1667 is named "com.delphix:async_destroy". For more information
1668 read the new zpool-features(5) manual page.
1669 Please refer to the "ZFS notes" section of this file for information
1670 on upgrading boot ZFS pools.
1673 The malloc(3) implementation embedded in libc now uses sources imported
1674 as contrib/jemalloc. The most disruptive API change is to
1675 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1676 delete it prior to installworld, and optionally re-create it using the
1677 new format after rebooting. See malloc.conf(5) for details
1678 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1682 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1683 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1684 now spelled mips. This is to aid compatibility with third-party
1685 software that expects this naming scheme in uname(3). Little-endian
1686 settings are unchanged. If you are updating a big-endian mips64 machine
1687 from before this change, you may need to set MACHINE_ARCH=mips64 in
1688 your environment before the new build system will recognize your machine.
1691 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1695 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1696 nullfs(5) did not pass through all behaviours to the underlying layer,
1697 as a result if we bound to a socket on the lower layer we could connect
1698 only to the lower path; if we bound to the upper layer we could connect
1699 only to the upper path. The new behavior is one can connect to both the
1700 lower and the upper paths regardless what layer path one binds to.
1703 The getifaddrs upgrade path broken with 20111215 has been restored.
1704 If you have upgraded in between 20111215 and 20120209 you need to
1705 recompile libc again with your kernel. You still need to recompile
1706 world to be able to configure CARP but this restriction already
1707 comes from 20111215.
1710 The set_rcvar() function has been removed from /etc/rc.subr. All
1711 base and ports rc.d scripts have been updated, so if you have a
1712 port installed with a script in /usr/local/etc/rc.d you can either
1713 hand-edit the rcvar= line, or reinstall the port.
1715 An easy way to handle the mass-update of /etc/rc.d:
1716 rm /etc/rc.d/* && mergemaster -i
1719 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1720 on the current CPU and prevents other threads from running.
1721 This behavior can be reverted using the kern.stop_scheduler_on_panic
1723 The new behavior can be incompatible with kern.sync_on_panic.
1726 The carp(4) facility has been changed significantly. Configuration
1727 of the CARP protocol via ifconfig(8) has changed, as well as format
1728 of CARP events submitted to devd(8) has changed. See manual pages
1729 for more information. The arpbalance feature of carp(4) is currently
1730 not supported anymore.
1732 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1733 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1734 need to be recompiled.
1737 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1741 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1742 explicitely support non-MPSAFE filesystems.
1743 It is on by default for all supported platform at this present
1747 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1748 i386 and pc98 GENERIC kernel configuration files.
1751 sysinstall has been removed
1754 The stable/9 branch created in subversion. This corresponds to the
1755 RELENG_9 branch in CVS.
1761 Avoid using make -j when upgrading. While generally safe, there are
1762 sometimes problems using -j to upgrade. If your upgrade fails with
1763 -j, please try again without -j. From time to time in the past there
1764 have been problems using -j with buildworld and/or installworld. This
1765 is especially true when upgrading between "distant" versions (eg one
1766 that cross a major release boundary or several minor releases, or when
1767 several months have passed on the -current branch).
1769 Sometimes, obscure build problems are the result of environment
1770 poisoning. This can happen because the make utility reads its
1771 environment when searching for values for global variables. To run
1772 your build attempts in an "environmental clean room", prefix all make
1773 commands with 'env -i '. See the env(1) manual page for more details.
1775 When upgrading from one major version to another it is generally best to
1776 upgrade to the latest code in the currently installed branch first, then
1777 do an upgrade to the new branch. This is the best-tested upgrade path,
1778 and has the highest probability of being successful. Please try this
1779 approach if you encounter problems with a major version upgrade. Since
1780 the stable 4.x branch point, one has generally been able to upgade from
1781 anywhere in the most recent stable branch to head / current (or even the
1782 last couple of stable branches). See the top of this file when there's
1785 When upgrading a live system, having a root shell around before
1786 installing anything can help undo problems. Not having a root shell
1787 around can lead to problems if pam has changed too much from your
1788 starting point to allow continued authentication after the upgrade.
1790 This file should be read as a log of events. When a later event changes
1791 information of a prior event, the prior event should not be deleted.
1792 Instead, a pointer to the entry with the new information should be
1793 placed in the old entry. Readers of this file should also sanity check
1794 older entries before relying on them blindly. Authors of new entries
1795 should write them with this in mind.
1799 When upgrading the boot ZFS pool to a new version, always follow
1802 1.) recompile and reinstall the ZFS boot loader and boot block
1803 (this is part of "make buildworld" and "make installworld")
1805 2.) update the ZFS boot block on your boot drive
1807 The following example updates the ZFS boot block on the first
1808 partition (freebsd-boot) of a GPT partitioned drive ada0:
1809 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1811 Non-boot pools do not need these updates.
1815 If you are updating from a prior version of FreeBSD (even one just
1816 a few days old), you should follow this procedure. It is the most
1817 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1819 make kernel-toolchain
1820 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1821 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1823 To test a kernel once
1824 ---------------------
1825 If you just want to boot a kernel once (because you are not sure
1826 if it works, or if you want to boot a known bad kernel to provide
1827 debugging information) run
1828 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1829 nextboot -k testkernel
1831 To just build a kernel when you know that it won't mess you up
1832 --------------------------------------------------------------
1833 This assumes you are already running a CURRENT system. Replace
1834 ${arch} with the architecture of your machine (e.g. "i386",
1835 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1837 cd src/sys/${arch}/conf
1838 config KERNEL_NAME_HERE
1839 cd ../compile/KERNEL_NAME_HERE
1844 If this fails, go to the "To build a kernel" section.
1846 To rebuild everything and install it on the current system.
1847 -----------------------------------------------------------
1848 # Note: sometimes if you are running current you gotta do more than
1849 # is listed here if you are upgrading from a really old current.
1851 <make sure you have good level 0 dumps>
1853 make kernel KERNCONF=YOUR_KERNEL_HERE
1855 <reboot in single user> [3]
1862 To cross-install current onto a separate partition
1863 --------------------------------------------------
1864 # In this approach we use a separate partition to hold
1865 # current's root, 'usr', and 'var' directories. A partition
1866 # holding "/", "/usr" and "/var" should be about 2GB in
1869 <make sure you have good level 0 dumps>
1872 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1873 <maybe newfs current's root partition>
1874 <mount current's root partition on directory ${CURRENT_ROOT}>
1875 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1876 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1877 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1878 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1879 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1880 <reboot into current>
1881 <do a "native" rebuild/install as described in the previous section>
1882 <maybe install compatibility libraries from ports/misc/compat*>
1886 To upgrade in-place from stable to current
1887 ----------------------------------------------
1888 <make sure you have good level 0 dumps>
1890 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1892 <reboot in single user> [3]
1899 Make sure that you've read the UPDATING file to understand the
1900 tweaks to various things you need. At this point in the life
1901 cycle of current, things change often and you are on your own
1902 to cope. The defaults can also change, so please read ALL of
1903 the UPDATING entries.
1905 Also, if you are tracking -current, you must be subscribed to
1906 freebsd-current@freebsd.org. Make sure that before you update
1907 your sources that you have read and understood all the recent
1908 messages there. If in doubt, please track -stable which has
1909 much fewer pitfalls.
1911 [1] If you have third party modules, such as vmware, you
1912 should disable them at this point so they don't crash your
1915 [3] From the bootblocks, boot -s, and then do
1920 adjkerntz -i # if CMOS is wall time
1921 Also, when doing a major release upgrade, it is required that
1922 you boot into single user mode to do the installworld.
1924 [4] Note: This step is non-optional. Failure to do this step
1925 can result in a significant reduction in the functionality of the
1926 system. Attempting to do it by hand is not recommended and those
1927 that pursue this avenue should read this file carefully, as well
1928 as the archives of freebsd-current and freebsd-hackers mailing lists
1929 for potential gotchas. The -U option is also useful to consider.
1930 See mergemaster(8) for more information.
1932 [5] Usually this step is a noop. However, from time to time
1933 you may need to do this if you get unknown user in the following
1934 step. It never hurts to do it all the time. You may need to
1935 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1936 install) after the buildworld before this step if you last updated
1937 from current before 20130425 or from -stable before 20130430.
1939 [6] This only deletes old files and directories. Old libraries
1940 can be deleted by "make delete-old-libs", but you have to make
1941 sure that no program is using those libraries anymore.
1943 [8] In order to have a kernel that can run the 4.x binaries needed to
1944 do an installworld, you must include the COMPAT_FREEBSD4 option in
1945 your kernel. Failure to do so may leave you with a system that is
1946 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1947 required to run the 5.x binaries on more recent kernels. And so on
1948 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1950 Make sure that you merge any new devices from GENERIC since the
1951 last time you updated your kernel config file.
1953 [9] When checking out sources, you must include the -P flag to have
1954 cvs prune empty directories.
1956 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1957 "?=" instead of the "=" assignment operator, so that buildworld can
1958 override the CPUTYPE if it needs to.
1960 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1961 not on the command line, or in /etc/make.conf. buildworld will
1962 warn if it is improperly defined.
1965 This file contains a list, in reverse chronological order, of major
1966 breakages in tracking -current. It is not guaranteed to be a complete
1967 list of such breakages, and only contains entries since September 23, 2011.
1968 If you need to see UPDATING entries from before that date, you will need
1969 to fetch an UPDATING file from an older FreeBSD release.
1971 Copyright information:
1973 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1975 Redistribution, publication, translation and use, with or without
1976 modification, in full or in part, in any form or format of this
1977 document are permitted without further permission from the author.
1979 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1980 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1981 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1982 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1983 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1984 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1985 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1986 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1987 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1988 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1989 POSSIBILITY OF SUCH DAMAGE.
1991 Contact Warner Losh if you have any questions about your use of