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 During boot the geli passphrase will be hidden. To restore previous
56 behavior see geli(8) configuration options.
59 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
60 sysctl values. Minor nit, but requires a rebuild of both world/kernel
64 "make check" behavior (made in ^/head@r295380) has been changed to
65 execute from a limited sandbox, as opposed to executing from
69 - The "beforecheck" and "aftercheck" targets are now specified.
70 - ${CHECKDIR} (added in commit noted above) has been removed.
71 - Legacy behavior can be enabled by setting
72 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
74 If the limited sandbox mode is enabled, "make check" will execute
75 "make distribution", then install, execute the tests, and clean up the
76 sandbox if successful.
78 The "make distribution" and "make install" targets are typically run as
79 root to set appropriate permissions and ownership at installation time.
80 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
81 environment if executing "make check" with limited sandbox mode using
85 Since the switch to GPT disk labels, fsck for UFS/FFS has been
86 unable to automatically find alternate superblocks. As of r322297,
87 the information needed to find alternate superblocks has been
88 moved to the end of the area reserved for the boot block.
89 Filesystems created with a newfs of this vintage or later
90 will create the recovery information. If you have a filesystem
91 created prior to this change and wish to have a recovery block
92 created for your filesystem, you can do so by running fsck in
93 forground mode (i.e., do not use the -p or -y options). As it
94 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
95 to which you should answer yes.
98 As of r321665, an NFSv4 server configuration that services
99 Kerberos mounts or clients that do not support the uid/gid in
100 owner/owner_group string capability, must explicitly enable
101 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
102 machine's /etc/rc.conf file.
105 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
106 Please see the 20141231 entry below for information about prerequisites
107 and upgrading, if you are not already using clang 3.5.0 or higher.
110 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
111 r-commands (rlogin, rsh, etc.) to be built with the base system.
114 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
115 a very major ABI incompatible change, so users of FreeBSD/powerpc must
116 be careful when performing source upgrades. It is best to run
117 'make installworld' from an alternate root system, either a live
118 CD/memory stick, or a temporary root partition. Additionally, all ports
119 must be recompiled. powerpc64 is largely unaffected, except in the case
120 of 32-bit compatibility. All 32-bit binaries will be affected.
123 Forward compatibility for the "ino64" project have been committed. This
124 will allow most new binaries to run on older kernels in a limited
125 fashion. This prevents many of the common foot-shooting actions in the
126 upgrade as well as the limited ability to roll back the kernel across
127 the ino64 upgrade. Complicated use cases may not work properly, though
128 enough simpler ones work to allow recovery in most situations.
131 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
132 if you require the GPL compiler.
135 The internal ABI used for communication between the NFS kernel modules
136 was changed by r320085, so __FreeBSD_version was bumped to
137 ensure all the NFS related modules are updated together.
140 The ABI of struct event was changed by extending the data
141 member to 64bit and adding ext fields. For upgrade, same
142 precautions as for the entry 20170523 "ino64" must be
146 The GNU roff toolchain has been removed from base. To render manpages
147 which are not supported by mandoc(1), man(1) can fallback on GNU roff
148 from ports (and recommends to install it).
149 To render roff(7) documents, consider using GNU roff from ports or the
150 heirloom doctools roff toolchain from ports via pkg install groff or
151 via pkg install heirloom-doctools.
154 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
155 smaller runtime footprint builds. This is useful for embedded systems
156 which only require one chipset support.
158 If you load it as a module, make sure this is in /boot/loader.conf:
162 This will load the HAL, all chip/RF backends and if_ath_pci.
163 If you have if_ath_pci in /boot/loader.conf, ensure it is after
164 if_ath or it will not load any HAL chipset support.
166 If you want to selectively load things (eg on ye cheape ARM/MIPS
167 platforms where RAM is at a premium) you should:
170 * load the chip modules in question
171 * load ath_rate, ath_dfs
173 * load if_ath_pci and/or if_ath_ahb depending upon your particular
174 bus bind type - this is where probe/attach is done.
176 For further comments/feedback, poke adrian@ .
179 The "ino64" 64-bit inode project has been committed, which extends
180 a number of types to 64 bits. Upgrading in place requires care and
181 adherence to the documented upgrade procedure.
183 If using a custom kernel configuration ensure that the
184 COMPAT_FREEBSD11 option is included (as during the upgrade the
185 system will be running the ino64 kernel with the existing world).
187 For the safest in-place upgrade begin by removing previous build
188 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
189 full procedure documented below under the heading "To rebuild
190 everything and install it on the current system." Specifically,
191 a reboot is required after installing the new kernel before
195 The NATM framework including the en(4), fatm(4), hatm(4), and
196 patm(4) devices has been removed. Consumers should plan a
197 migration before the end-of-life date for FreeBSD 11.
200 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
201 diff has not been implemented, if those are needed a newer version of
202 GNU diff is available via the diffutils package under the gdiff name.
205 As of r316810 for ipfilter, keep frags is no longer assumed when
206 keep state is specified in a rule. r316810 aligns ipfilter with
207 documentation in man pages separating keep frags from keep state.
208 This allows keep state to be specified without forcing keep frags
209 and allows keep frags to be specified independently of keep state.
210 To maintain previous behaviour, also specify keep frags with
211 keep state (as documented in ipf.conf.5).
214 arm64 builds now use the base system LLD 4.0.0 linker by default,
215 instead of requiring that the aarch64-binutils port or package be
216 installed. To continue using aarch64-binutils, set
217 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
220 The UDP optimization in entry 20160818 that added the sysctl
221 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
222 packets will no longer be treated as L3 broadcast packets.
225 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
226 use any explicitly assigned loopback address available in the jail
227 instead of using the first assigned address of the jail.
230 The ctl.ko module no longer implements the iSCSI target frontend:
231 cfiscsi.ko does instead.
233 If building cfiscsi.ko as a kernel module, the module can be loaded
234 via one of the following methods:
235 - `cfiscsi_load="YES"` in loader.conf(5).
236 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
237 - ctladm(8)/ctld(8), when compiled with iSCSI support
238 (`WITH_ISCSI=yes` in src.conf(5))
240 Please see cfiscsi(4) for more details.
243 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
244 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
245 same source (previously, the dependency of mmcsd.ko on mmc.ko was
246 missing, but mmcsd.ko now will refuse to load if it is incompatible
250 The syntax of ipfw(8) named states was changed to avoid ambiguity.
251 If you have used named states in the firewall rules, you need to modify
252 them after installworld and before rebooting. Now named states must
253 be prefixed with colon.
256 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
257 removed as the userland we provide cannot use them. The KMS version
258 (sys/dev/drm2) supports the same hardware.
261 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
262 Please see the 20141231 entry below for information about prerequisites
263 and upgrading, if you are not already using clang 3.5.0 or higher.
266 The code that provides support for ZFS .zfs/ directory functionality
267 has been reimplemented. It's not possible now to create a snapshot
268 by mkdir under .zfs/snapshot/. That should be the only user visible
272 EISA bus support has been removed. The WITH_EISA option is no longer
276 MCA bus support has been removed.
279 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
280 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
283 The EM_MULTIQUEUE kernel configuration option is deprecated now that
284 the em(4) driver conforms to iflib specifications.
287 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
288 IFLIB. If you have a custom kernel configuration that excludes em(4)
289 but you use igb(4), you need to re-add em(4) to your custom configuration.
292 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
293 Please see the 20141231 entry below for information about prerequisites
294 and upgrading, if you are not already using clang 3.5.0 or higher.
297 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
298 Please see the 20141231 entry below for information about prerequisites
299 and upgrading, if you are not already using clang 3.5.0 or higher.
302 The layout of the pmap structure has changed for powerpc to put the pmap
303 statistics at the front for all CPU variations. libkvm(3) and all tools
304 that link against it need to be recompiled.
307 isl(4) and cyapa(4) drivers now require a new driver,
308 chromebook_platform(4), to work properly on Chromebook-class hardware.
309 On other types of hardware the drivers may need to be configured using
310 device hints. Please see the corresponding manual pages for details.
313 The urtwn(4) driver was merged into rtwn(4) and now consists of
314 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
316 Also, firmware for RTL8188CE was renamed due to possible name
317 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
320 GNU rcs has been removed from base. It is available as packages:
321 - rcs: Latest GPLv3 GNU rcs version.
322 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
326 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
327 modules now requires that the kernel configuration contain the
328 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
331 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
332 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
335 Relocatable object files with the extension of .So have been renamed
336 to use an extension of .pico instead. The purpose of this change is
337 to avoid a name clash with shared libraries on case-insensitive file
338 systems. On those file systems, foo.So is the same file as foo.so.
341 GNU rcs has been turned off by default. It can (temporarily) be built
342 again by adding WITH_RCS knob in src.conf.
343 Otherwise, GNU rcs is available from packages:
344 - rcs: Latest GPLv3 GNU rcs version.
345 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
348 The backup_uses_rcs functionality has been removed from rc.subr.
351 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
352 two separate components, QUEUE_MACRO_DEBUG_TRACE and
353 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
354 QUEUE_MACRO_DEBUG behavior.
357 r304787 changed some ioctl interfaces between the iSCSI userspace
358 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
359 rebuilt to work with new kernels. __FreeBSD_version has been bumped
363 The UDP receive code has been updated to only treat incoming UDP
364 packets that were addressed to an L2 broadcast address as L3
365 broadcast packets. It is not expected that this will affect any
366 standards-conforming UDP application. The new behaviour can be
367 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
371 Remove the openbsd_poll system call.
372 __FreeBSD_version has been bumped because of this.
375 The libc stub for the pipe(2) system call has been replaced with
376 a wrapper that calls the pipe2(2) system call and the pipe(2)
377 system call is now only implemented by the kernels that include
378 "options COMPAT_FREEBSD10" in their config file (this is the
379 default). Users should ensure that this option is enabled in
380 their kernel or upgrade userspace to r302092 before upgrading their
384 CAM will now strip leading spaces from SCSI disks' serial numbers.
385 This will affect users who create UFS filesystems on SCSI disks using
386 those disk's diskid device nodes. For example, if /etc/fstab
387 previously contained a line like
388 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
389 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
390 transforms like gmirror may also be affected. ZFS users should
394 The bitstring(3) API has been updated with new functionality and
395 improved performance. But it is binary-incompatible with the old API.
396 Objects built with the new headers may not be linked against objects
397 built with the old headers.
400 The brk and sbrk functions have been removed from libc on arm64.
401 Binutils from ports has been updated to not link to these
402 functions and should be updated to the latest version before
403 installing a new libc.
406 The armv6 port now defaults to hard float ABI. Limited support
407 for running both hardfloat and soft float on the same system
408 is available using the libraries installed with -DWITH_LIBSOFT.
409 This has only been tested as an upgrade path for installworld
410 and packages may fail or need manual intervention to run. New
411 packages will be needed.
413 To update an existing self-hosted armv6hf system, you must add
414 TARGET_ARCH=armv6 on the make command line for both the build
415 and the install steps.
418 Kernel modules compiled outside of a kernel build now default to
419 installing to /boot/modules instead of /boot/kernel. Many kernel
420 modules built this way (such as those in ports) already overrode
421 KMODDIR explicitly to install into /boot/modules. However,
422 manually building and installing a module from /sys/modules will
423 now install to /boot/modules instead of /boot/kernel.
426 The CAM I/O scheduler has been committed to the kernel. There should be
427 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
428 list of known rogues that claim support for this but actually corrupt
429 data is believed to be complete, be on the lookout for data
430 corruption. The known rogue list is believed to be complete:
432 o Crucial MX100, M550 drives with MU01 firmware.
433 o Micron M510 and M550 drives with MU01 firmware.
434 o Micron M500 prior to MU07 firmware
435 o Samsung 830, 840, and 850 all firmwares
436 o FCCT M500 all firmwares
438 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
439 with working NCQ TRIM. For Micron branded drives, see your sales rep for
440 updated firmware. Black listed drives will work correctly because these
441 drives work correctly so long as no NCQ TRIMs are sent to them. Given
442 this list is the same as found in Linux, it's believed there are no
443 other rogues in the market place. All other models from the above
446 To be safe, if you are at all concerned, you can quirk each of your
447 drives to prevent NCQ from being sent by setting:
448 kern.cam.ada.X.quirks="0x2"
449 in loader.conf. If the drive requires the 4k sector quirk, set the
453 The FAST_DEPEND build option has been removed and its functionality is
454 now the one true way. The old mkdep(1) style of 'make depend' has
455 been removed. See 20160311 for further details.
458 Resource range types have grown from unsigned long to uintmax_t. All
459 drivers, and anything using libdevinfo, need to be recompiled.
462 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
463 builds. It no longer runs mkdep(1) during 'make depend', and the
464 'make depend' stage can safely be skipped now as it is auto ran
465 when building 'make all' and will generate all SRCS and DPSRCS before
466 building anything else. Dependencies are gathered at compile time with
467 -MF flags kept in separate .depend files per object file. Users should
468 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
472 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
473 kernel modules. Therefore, if you load any kernel modules at boot time,
474 please install the boot loaders after you install the kernel, but before
478 make kernel KERNCONF=YOUR_KERNEL_HERE
479 make -C sys/boot install
480 <reboot in single user>
482 Then follow the usual steps, described in the General Notes section,
486 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
487 see the 20141231 entry below for information about prerequisites and
488 upgrading, if you are not already using clang 3.5.0 or higher.
491 The AIO subsystem is now a standard part of the kernel. The
492 VFS_AIO kernel option and aio.ko kernel module have been removed.
493 Due to stability concerns, asynchronous I/O requests are only
494 permitted on sockets and raw disks by default. To enable
495 asynchronous I/O requests on all file types, set the
496 vfs.aio.enable_unsafe sysctl to a non-zero value.
499 The ELF object manipulation tool objcopy is now provided by the
500 ELF Tool Chain project rather than by GNU binutils. It should be a
501 drop-in replacement, with the addition of arm64 support. The
502 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
503 to obtain the GNU version if necessary.
506 Building ZFS pools on top of zvols is prohibited by default. That
507 feature has never worked safely; it's always been prone to deadlocks.
508 Using a zvol as the backing store for a VM guest's virtual disk will
509 still work, even if the guest is using ZFS. Legacy behavior can be
510 restored by setting vfs.zfs.vol.recursive=1.
513 The NONE and HPN patches has been removed from OpenSSH. They are
514 still available in the security/openssh-portable port.
517 With the addition of ypldap(8), a new _ypldap user is now required
518 during installworld. "mergemaster -p" can be used to add the user
519 prior to installworld, as documented in the handbook.
522 The tftp loader (pxeboot) now uses the option root-path directive. As a
523 consequence it no longer looks for a pxeboot.4th file on the tftp
524 server. Instead it uses the regular /boot infrastructure as with the
528 The code to start recording plug and play data into the modules has
529 been committed. While the old tools will properly build a new kernel,
530 a number of warnings about "unknown metadata record 4" will be produced
531 for an older kldxref. To avoid such warnings, make sure to rebuild
532 the kernel toolchain (or world). Make sure that you have r292078 or
533 later when trying to build 292077 or later before rebuilding.
536 Debug data files are now built by default with 'make buildworld' and
537 installed with 'make installworld'. This facilitates debugging but
538 requires more disk space both during the build and for the installed
539 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
543 r291527 changed the internal interface between the nfsd.ko and
544 nfscommon.ko modules. As such, they must both be upgraded to-gether.
545 __FreeBSD_version has been bumped because of this.
548 Add support for unicode collation strings leads to a change of
549 order of files listed by ls(1) for example. To get back to the old
550 behaviour, set LC_COLLATE environment variable to "C".
552 Databases administrators will need to reindex their databases given
553 collation results will be different.
555 Due to a bug in install(1) it is recommended to remove the ancient
556 locales before running make installworld.
558 rm -rf /usr/share/locale/*
561 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
562 libcrypto.so.7 or libssl.so.7 must be recompiled.
565 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
566 Kernel modules isp_2400_multi and isp_2500_multi were removed and
567 should be replaced with isp_2400 and isp_2500 modules respectively.
570 The build previously allowed using 'make -n' to not recurse into
571 sub-directories while showing what commands would be executed, and
572 'make -n -n' to recursively show commands. Now 'make -n' will recurse
573 and 'make -N' will not.
576 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
577 and etcupdate will now use this file. A custom sendmail.cf is now
578 updated via this mechanism rather than via installworld. If you had
579 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
580 want to remove the exclusion or change it to "always install".
581 /etc/mail/sendmail.cf is now managed the same way regardless of
582 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
583 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
586 Compatibility shims for legacy ATA device names have been removed.
587 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
588 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
589 environment variables, /dev/ad* and /dev/ar* symbolic links.
592 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
593 Please see the 20141231 entry below for information about prerequisites
594 and upgrading, if you are not already using clang 3.5.0 or higher.
597 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
598 and renamed from .symbols to .debug. This reduces the size requirements
599 on the boot partition or file system and provides consistency with
600 userland debug files.
602 When using the supported kernel installation method the
603 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
604 as is done with /boot/kernel.
606 Developers wishing to maintain the historical behavior of installing
607 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
610 The wireless drivers had undergone changes that remove the 'parent
611 interface' from the ifconfig -l output. The rc.d network scripts
612 used to check presence of a parent interface in the list, so old
613 scripts would fail to start wireless networking. Thus, etcupdate(3)
614 or mergemaster(8) run is required after kernel update, to update your
615 rc.d scripts in /etc.
618 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
619 These configurations are now automatically interpreted as
620 'scrub fragment reassemble'.
623 Kernel-loadable modules for the random(4) device are back. To use
624 them, the kernel must have
627 options RANDOM_LOADABLE
629 kldload(8) can then be used to load random_fortuna.ko
630 or random_yarrow.ko. Please note that due to the indirect
631 function calls that the loadable modules need to provide,
632 the build-in variants will be slightly more efficient.
634 The random(4) kernel option RANDOM_DUMMY has been retired due to
635 unpopularity. It was not all that useful anyway.
638 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
639 Control over building the ELF Tool Chain tools is now provided by
640 the WITHOUT_TOOLCHAIN knob.
643 The polarity of Pulse Per Second (PPS) capture events with the
644 uart(4) driver has been corrected. Prior to this change the PPS
645 "assert" event corresponded to the trailing edge of a positive PPS
646 pulse and the "clear" event was the leading edge of the next pulse.
648 As the width of a PPS pulse in a typical GPS receiver is on the
649 order of 1 millisecond, most users will not notice any significant
650 difference with this change.
652 Anyone who has compensated for the historical polarity reversal by
653 configuring a negative offset equal to the pulse width will need to
654 remove that workaround.
657 The default group assigned to /dev/dri entries has been changed
658 from 'wheel' to 'video' with the id of '44'. If you want to have
659 access to the dri devices please add yourself to the video group
662 # pw groupmod video -m $USER
665 The menu.rc and loader.rc files will now be replaced during
666 upgrades. Please migrate local changes to menu.rc.local and
667 loader.rc.local instead.
670 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
671 strings and strip have been removed. The src.conf(5) knob
672 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
675 As ZFS requires more kernel stack pages than is the default on some
676 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
677 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
679 Please consider using 'options KSTACK_PAGES=X' where X is greater
680 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
683 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
684 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
685 default, i.e., they will not contain "::". For example, instead
686 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
687 to have a more specific match, such as different map entries for
688 IPv6:0:0 vs IPv6:0. This change requires that configuration
689 data (including maps, files, classes, custom ruleset, etc.) must
690 use the same format, so make certain such configuration data is
691 upgrading. As a very simple check search for patterns like
692 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
693 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
694 the cf option UseCompressedIPv6Addresses.
697 The default kernel entropy-processing algorithm is now
698 Fortuna, replacing Yarrow.
700 Assuming you have 'device random' in your kernel config
701 file, the configurations allow a kernel option to override
702 this default. You may choose *ONE* of:
704 options RANDOM_YARROW # Legacy /dev/random algorithm.
705 options RANDOM_DUMMY # Blocking-only driver.
707 If you have neither, you get Fortuna. For most people,
708 read no further, Fortuna will give a /dev/random that works
709 like it always used to, and the difference will be irrelevant.
711 If you remove 'device random', you get *NO* kernel-processed
712 entropy at all. This may be acceptable to folks building
713 embedded systems, but has complications. Carry on reading,
714 and it is assumed you know what you need.
716 *PLEASE* read random(4) and random(9) if you are in the
717 habit of tweaking kernel configs, and/or if you are a member
718 of the embedded community, wanting specific and not-usual
719 behaviour from your security subsystems.
721 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
722 random', you will NOT have a functioning /dev/random, and
723 many cryptographic features will not work, including SSH.
724 You may also find strange behaviour from the random(3) set
725 of library functions, in particular sranddev(3), srandomdev(3)
726 and arc4random(3). The reason for this is that the KERN_ARND
727 sysctl only returns entropy if it thinks it has some to
728 share, and with RANDOM_DUMMY or no 'device random' this
732 An additional fix for the issue described in the 20150614 sendmail
733 entry below has been been committed in revision 284717.
736 FreeBSD's old make (fmake) has been removed from the system. It is
737 available as the devel/fmake port or via pkg install fmake.
740 The fix for the issue described in the 20150614 sendmail entry
741 below has been been committed in revision 284436. The work
742 around described in that entry is no longer needed unless the
743 default setting is overridden by a confDH_PARAMETERS configuration
744 setting of '5' or pointing to a 512 bit DH parameter file.
747 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
748 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
749 and devel/kyua to version 0.20+ and adjust any calling code to work
750 with Kyuafile and kyua.
753 The import of openssl to address the FreeBSD-SA-15:10.openssl
754 security advisory includes a change which rejects handshakes
755 with DH parameters below 768 bits. sendmail releases prior
756 to 8.15.2 (not yet released), defaulted to a 512 bit
757 DH parameter setting for client connections. To work around
758 this interoperability, sendmail can be configured to use a
759 2048 bit DH parameter by:
761 1. Edit /etc/mail/`hostname`.mc
762 2. If a setting for confDH_PARAMETERS does not exist or
763 exists and is set to a string beginning with '5',
765 3. If a setting for confDH_PARAMETERS exists and is set to
766 a file path, create a new file with:
767 openssl dhparam -out /path/to/file 2048
768 4. Rebuild the .cf file:
769 cd /etc/mail/; make; make install
771 cd /etc/mail/; make restart
773 A sendmail patch is coming, at which time this file will be
777 Generation of legacy formatted entries have been disabled by default
778 in pwd_mkdb(8), as all base system consumers of the legacy formatted
779 entries were converted to use the new format by default when the new,
780 machine independent format have been added and supported since FreeBSD
783 Please see the pwd_mkdb(8) manual page for further details.
786 Clang and llvm have been upgraded to 3.6.1 release. Please see the
787 20141231 entry below for information about prerequisites and upgrading,
788 if you are not already using 3.5.0 or higher.
791 TI platform code switched to using vendor DTS files and this update
792 may break existing systems running on Beaglebone, Beaglebone Black,
795 - dtb files should be regenerated/reinstalled. Filenames are the
796 same but content is different now
797 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
798 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
799 addressing scheme is now pin 25 on /dev/gpioc3.
800 - Pandaboard: /etc/ttys should be updated, serial console device is
801 now /dev/ttyu2, not /dev/ttyu0
804 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
805 If you need the GNU extension from groff soelim(1), install groff
806 from package: pkg install groff, or via ports: textproc/groff.
809 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
810 defined in symlink(7); previously symlinks were silently ignored.
813 The const qualifier has been removed from iconv(3) to comply with
814 POSIX. The ports tree is aware of this from r384038 onwards.
817 Libraries specified by LIBADD in Makefiles must have a corresponding
818 DPADD_<lib> variable to ensure correct dependencies. This is now
819 enforced in src.libnames.mk.
822 From legacy ata(4) driver was removed support for SATA controllers
823 supported by more functional drivers ahci(4), siis(4) and mvs(4).
824 Kernel modules ataahci and ataadaptec were removed completely,
825 replaced by ahci and mvs modules respectively.
828 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
829 the 20141231 entry below for information about prerequisites and
830 upgrading, if you are not already using 3.5.0 or higher.
833 The 32-bit PowerPC kernel has been changed to a position-independent
834 executable. This can only be booted with a version of loader(8)
835 newer than January 31, 2015, so make sure to update both world and
836 kernel before rebooting.
839 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
840 but before r278950, the RNG was not seeded properly. Immediately
841 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
842 ssh keys or openssl keys) that were generated w/ a kernel from that
843 range. This does not affect programs that directly used /dev/random
844 or /dev/urandom. All userland uses of arc4random(3) are affected.
847 The autofs(4) ABI was changed in order to restore binary compatibility
848 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
852 The powerpc64 kernel has been changed to a position-independent
853 executable. This can only be booted with a new version of loader(8),
854 so make sure to update both world and kernel before rebooting.
857 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
858 only release, no new features have been added. Please see the 20141231
859 entry below for information about prerequisites and upgrading, if you
860 are not already using 3.5.0.
863 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
864 taken from the ELF Tool Chain project rather than GNU binutils. They
865 should be drop-in replacements, with the addition of arm64 support.
866 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
867 binutils tools, if necessary. See 20150805 for updated information.
870 The default Unbound configuration now enables remote control
871 using a local socket. Users who have already enabled the
872 local_unbound service should regenerate their configuration
873 by running "service local_unbound setup" as root.
876 The GNU texinfo and GNU info pages have been removed.
877 To be able to view GNU info pages please install texinfo from ports.
880 Clang, llvm and lldb have been upgraded to 3.5.0 release.
882 As of this release, a prerequisite for building clang, llvm and lldb is
883 a C++11 capable compiler and C++11 standard library. This means that to
884 be able to successfully build the cross-tools stage of buildworld, with
885 clang as the bootstrap compiler, your system compiler or cross compiler
886 should either be clang 3.3 or later, or gcc 4.8 or later, and your
887 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
890 On any standard FreeBSD 10.x or 11.x installation, where clang and
891 libc++ are on by default (that is, on x86 or arm), this should work out
894 On 9.x installations where clang is enabled by default, e.g. on x86 and
895 powerpc, libc++ will not be enabled by default, so libc++ should be
896 built (with clang) and installed first. If both clang and libc++ are
897 missing, build clang first, then use it to build libc++.
899 On 8.x and earlier installations, upgrade to 9.x first, and then follow
900 the instructions for 9.x above.
902 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
903 default, and do not build clang.
905 Many embedded systems are resource constrained, and will not be able to
906 build clang in a reasonable time, or in some cases at all. In those
907 cases, cross building bootable systems on amd64 is a workaround.
909 This new version of clang introduces a number of new warnings, of which
910 the following are most likely to appear:
914 This warns in two cases, for both C and C++:
915 * When the code is trying to take the absolute value of an unsigned
916 quantity, which is effectively a no-op, and almost never what was
917 intended. The code should be fixed, if at all possible. If you are
918 sure that the unsigned quantity can be safely cast to signed, without
919 loss of information or undefined behavior, you can add an explicit
920 cast, or disable the warning.
922 * When the code is trying to take an absolute value, but the called
923 abs() variant is for the wrong type, which can lead to truncation.
924 If you want to disable the warning instead of fixing the code, please
925 make sure that truncation will not occur, or it might lead to unwanted
928 -Wtautological-undefined-compare and
929 -Wundefined-bool-conversion
931 These warn when C++ code is trying to compare 'this' against NULL, while
932 'this' should never be NULL in well-defined C++ code. However, there is
933 some legacy (pre C++11) code out there, which actively abuses this
934 feature, which was less strictly defined in previous C++ versions.
936 Squid and openjdk do this, for example. The warning can be turned off
937 for C++98 and earlier, but compiling the code in C++11 mode might result
938 in unexpected behavior; for example, the parts of the program that are
939 unreachable could be optimized away.
942 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
943 kernel sources have been removed. The .h files remain, since some
944 utilities include them. This will need to be fixed later.
945 If "mount -t oldnfs ..." is attempted, it will fail.
946 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
947 the utilities will report errors.
950 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
951 directories to top level SUBDIR variable when their parent
952 directory is included in LOCAL_DIRS. Users with build systems with
953 such hierarchies and without SUBDIR entries in the parent
954 directory Makefiles should add them or add the directories to
958 faith(4) and faithd(8) have been removed from the base system. Faith
959 has been obsolete for a very long time.
962 vt(4), the new console driver, is enabled by default. It brings
963 support for Unicode and double-width characters, as well as
964 support for UEFI and integration with the KMS kernel video
967 You may need to update your console settings in /etc/rc.conf,
968 most probably the keymap. During boot, /etc/rc.d/syscons will
969 indicate what you need to do.
971 vt(4) still has issues and lacks some features compared to
972 syscons(4). See the wiki for up-to-date information:
973 https://wiki.freebsd.org/Newcons
975 If you want to keep using syscons(4), you can do so by adding
976 the following line to /boot/loader.conf:
980 pjdfstest has been integrated into kyua as an opt-in test suite.
981 Please see share/doc/pjdfstest/README for more details on how to
985 gperf has been removed from the base system for architectures
986 that use clang. Ports that require gperf will obtain it from the
990 pjdfstest has been moved from tools/regression/pjdfstest to
994 At svn r271982, The default linux compat kernel ABI has been adjusted
995 to 2.6.18 in support of the linux-c6 compat ports infrastructure
996 update. If you wish to continue using the linux-f10 compat ports,
997 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
998 encouraged to update their linux-compat packages to linux-c6 during
999 their next update cycle.
1002 The ofwfb driver, used to provide a graphics console on PowerPC when
1003 using vt(4), no longer allows mmap() of all physical memory. This
1004 will prevent Xorg on PowerPC with some ATI graphics cards from
1005 initializing properly unless x11-servers/xorg-server is updated to
1009 The xdev targets have been converted to using TARGET and
1010 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1013 The default unbound configuration has been modified to address
1014 issues with reverse lookups on networks that use private
1015 address ranges. If you use the local_unbound service, run
1016 "service local_unbound setup" as root to regenerate your
1017 configuration, then "service local_unbound reload" to load the
1021 The GNU texinfo and GNU info pages are not built and installed
1022 anymore, WITH_INFO knob has been added to allow to built and install
1024 UPDATE: see 20150102 entry on texinfo's removal
1027 The GNU readline library is now an INTERNALLIB - that is, it is
1028 statically linked into consumers (GDB and variants) in the base
1029 system, and the shared library is no longer installed. The
1030 devel/readline port is available for third party software that
1034 The Itanium architecture (ia64) has been removed from the list of
1035 known architectures. This is the first step in the removal of the
1039 Commit r268115 has added NFSv4.1 server support, merged from
1040 projects/nfsv4.1-server. Since this includes changes to the
1041 internal interfaces between the NFS related modules, a full
1042 build of the kernel and modules will be necessary.
1043 __FreeBSD_version has been bumped.
1046 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1047 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1048 which differs from the behaviour controlled by this knob.)
1051 Maximal length of the serial number in CTL was increased from 16 to
1052 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1053 and ctld, need to be rebuilt to work with a new kernel.
1056 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1057 1 respectively to match the upstream numbers. They were out of
1058 sync because, when they were originally added to FreeBSD, the
1059 upstream versions were not respected. These libraries are private
1060 and not yet built by default, so renumbering them should be a
1061 non-issue. However, unclean source trees will yield broken test
1062 programs once the operator executes "make delete-old-libs" after a
1063 "make installworld".
1065 Additionally, the atf-sh binary was made private by moving it into
1066 /usr/libexec/. Already-built shell test programs will keep the
1067 path to the old binary so they will break after "make delete-old"
1070 If you are using WITH_TESTS=yes (not the default), wipe the object
1071 tree and rebuild from scratch to prevent spurious test failures.
1072 This is only needed once: the misnumbered libraries and misplaced
1073 binaries have been added to OptionalObsoleteFiles.inc so they will
1074 be removed during a clean upgrade.
1077 Clang and llvm have been upgraded to 3.4.1 release.
1080 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1081 be removed to avoid issues in the future (and has been added to
1085 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1086 past, it affected all builds that used the bsd.*.mk files. The old
1087 behavior was a bug, but people may have relied upon it. To get this
1088 behavior back, you can .include /etc/src.conf from /etc/make.conf
1089 (which is still global and isn't changed). This also changes the
1090 behavior of incremental builds inside the tree of individual
1091 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1092 Although this has survived make universe and some upgrade scenarios,
1093 other upgrade scenarios may have broken. At least one form of
1094 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1095 as well... In cases where MAKESYSPATH isn't working with this
1096 setting, you'll need to set it to the full path to your tree.
1098 One side effect of all this cleaning up is that bsd.compiler.mk
1099 is no longer implicitly included by bsd.own.mk. If you wish to
1100 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1104 The lindev device has been removed since /dev/full has been made a
1105 standard device. __FreeBSD_version has been bumped.
1108 The knob WITHOUT_VI was added to the base system, which controls
1109 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1110 in order to reorder files share/termcap and didn't build ex(1) as a
1111 build tool, so building/installing with WITH_VI is highly advised for
1112 build hosts for older releases.
1114 This issue has been fixed in stable/9 and stable/10 in r277022 and
1115 r276991, respectively.
1118 The YES_HESIOD knob has been removed. It has been obsolete for
1119 a decade. Please move to using WITH_HESIOD instead or your builds
1120 will silently lack HESIOD.
1123 The uart(4) driver has been changed with respect to its handling
1124 of the low-level console. Previously the uart(4) driver prevented
1125 any process from changing the baudrate or the CLOCAL and HUPCL
1126 control flags. By removing the restrictions, operators can make
1127 changes to the serial console port without having to reboot.
1128 However, when getty(8) is started on the serial device that is
1129 associated with the low-level console, a misconfigured terminal
1130 line in /etc/ttys will now have a real impact.
1131 Before upgrading the kernel, make sure that /etc/ttys has the
1132 serial console device configured as 3wire without baudrate to
1133 preserve the previous behaviour. E.g:
1134 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1137 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1138 to improve performance. To re-enable it, if needed, run rpcbind
1139 with command line option -W.
1142 Switched back to the GPL dtc compiler due to updates in the upstream
1143 dts files not being supported by the BSDL dtc compiler. You will need
1144 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1145 may result while building dtb files during a kernel build if you fail
1146 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1149 Clang and llvm have been upgraded to 3.4 release.
1152 The nve(4) driver has been removed. Please use the nfe(4) driver
1153 for NVIDIA nForce MCP Ethernet adapters instead.
1156 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1157 This could cause certain C++ applications using shared libraries built
1158 against the previous version of libc++ to crash. The incompatibility
1159 has now been fixed, but any C++ applications or shared libraries built
1160 between r261283 and r261801 should be recompiled.
1163 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1164 capability mode support. Please note that enabling the feature in
1165 kernel is still highly recommended.
1168 OpenSSH is now built with sandbox support, and will use sandbox as
1169 the default privilege separation method. This requires Capsicum
1170 capability mode support in kernel.
1173 The libelf and libdwarf libraries have been updated to newer
1174 versions from upstream. Shared library version numbers for
1175 these two libraries were bumped. Any ports or binaries
1176 requiring these two libraries should be recompiled.
1177 __FreeBSD_version is bumped to 1100006.
1180 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1181 instead of providing an explicit one, this would prevent such
1182 Makefile from providing its own Kyuafile in the future during
1183 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1184 intervention is needed to clean an objdir if you use NO_CLEAN:
1185 # find /usr/obj -name Kyuafile | xargs rm -f
1188 The behavior of gss_pseudo_random() for the krb5 mechanism
1189 has changed, for applications requesting a longer random string
1190 than produced by the underlying enctype's pseudo-random() function.
1191 In particular, the random string produced from a session key of
1192 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1193 be different at the 17th octet and later, after this change.
1194 The counter used in the PRF+ construction is now encoded as a
1195 big-endian integer in accordance with RFC 4402.
1196 __FreeBSD_version is bumped to 1100004.
1199 The WITHOUT_ATF build knob has been removed and its functionality
1200 has been subsumed into the more generic WITHOUT_TESTS. If you were
1201 using the former to disable the build of the ATF libraries, you
1202 should change your settings to use the latter.
1205 The default version of mtree is nmtree which is obtained from
1206 NetBSD. The output is generally the same, but may vary
1207 slightly. If you found you need identical output adding
1208 "-F freebsd9" to the command line should do the trick. For the
1209 time being, the old mtree is available as fmtree.
1212 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1213 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1214 1.1.4_8 and verify bsdyml not linked in, before running "make
1216 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1218 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1221 The stable/10 branch has been created in subversion from head
1225 The rc.d/jail script has been updated to support jail(8)
1226 configuration file. The "jail_<jname>_*" rc.conf(5) variables
1227 for per-jail configuration are automatically converted to
1228 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
1229 This is transparently backward compatible. See below about some
1230 incompatibilities and rc.conf(5) manual page for more details.
1232 These variables are now deprecated in favor of jail(8) configuration
1233 file. One can use "rc.d/jail config <jname>" command to generate
1234 a jail(8) configuration file in /var/run/jail.<jname>.conf without
1235 running the jail(8) utility. The default pathname of the
1236 configuration file is /etc/jail.conf and can be specified by
1237 using $jail_conf or $jail_<jname>_conf variables.
1239 Please note that jail_devfs_ruleset accepts an integer at
1240 this moment. Please consider to rewrite the ruleset name
1244 BIND has been removed from the base system. If all you need
1245 is a local resolver, simply enable and start the local_unbound
1246 service instead. Otherwise, several versions of BIND are
1247 available in the ports tree. The dns/bind99 port is one example.
1249 With this change, nslookup(1) and dig(1) are no longer in the base
1250 system. Users should instead use host(1) and drill(1) which are
1251 in the base system. Alternatively, nslookup and dig can
1252 be obtained by installing the dns/bind-tools port.
1255 With the addition of unbound(8), a new unbound user is now
1256 required during installworld. "mergemaster -p" can be used to
1257 add the user prior to installworld, as documented in the handbook.
1260 OpenSSH is now built with DNSSEC support, and will by default
1261 silently trust signed SSHFP records. This can be controlled with
1262 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1263 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1266 The GNU Compiler Collection and C++ standard library (libstdc++)
1267 are no longer built by default on platforms where clang is the system
1268 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1269 options in src.conf.
1272 The PROCDESC kernel option is now part of the GENERIC kernel
1273 configuration and is required for the rwhod(8) to work.
1274 If you are using custom kernel configuration, you should include
1278 The API and ABI related to the Capsicum framework was modified
1279 in backward incompatible way. The userland libraries and programs
1280 have to be recompiled to work with the new kernel. This includes the
1281 following libraries and programs, but the whole buildworld is
1282 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1283 kdump, procstat, rwho, rwhod, uniq.
1286 AES-NI intrinsic support has been added to gcc. The AES-NI module
1287 has been updated to use this support. A new gcc is required to build
1288 the aesni module on both i386 and amd64.
1291 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1292 Thus "device padlock_rng" and "device rdrand_rng" should be
1293 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1296 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1297 enables just the iconv* functionality and is now on by default.
1298 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1299 compatibility. Set WITHOUT_ICONV to build the old way.
1300 If you have been using WITH_ICONV before, you will very likely
1301 need to turn on WITH_LIBICONV_COMPAT.
1304 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1305 Illumos origin, including ZFS. If you have INVARIANTS in your
1306 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1308 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1309 locks if WITNESS option was set. Because that generated a lot of
1310 witness(9) reports and all of them were believed to be false
1311 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1312 can be used to achieve the previous behavior.
1315 Timer values in IPv6 data structures now use time_uptime instead
1316 of time_second. Although this is not a user-visible functional
1317 change, userland utilities which directly use them---ndp(8),
1318 rtadvd(8), and rtsold(8) in the base system---need to be updated
1319 to r253970 or later.
1322 find -delete can now delete the pathnames given as arguments,
1323 instead of only files found below them or if the pathname did
1324 not contain any slashes. Formerly, the following error message
1327 find: -delete: <path>: relative path potentially not safe
1329 Deleting the pathnames given as arguments can be prevented
1330 without error messages using -mindepth 1 or by changing
1331 directory and passing "." as argument to find. This works in the
1332 old as well as the new version of find.
1335 Behavior of devfs rules path matching has been changed.
1336 Pattern is now always matched against fully qualified devfs
1337 path and slash characters must be explicitly matched by
1338 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1339 subdirectories must be reviewed.
1342 The default ARM ABI has changed to the ARM EABI. The old ABI is
1343 incompatible with the ARM EABI and all programs and modules will
1344 need to be rebuilt to work with a new kernel.
1346 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1348 NOTE: Support for the old ABI will be removed in the future and
1349 users are advised to upgrade.
1352 pkg_install has been disconnected from the build if you really need it
1353 you should add WITH_PKGTOOLS in your src.conf(5).
1356 Most of network statistics structures were changed to be able
1357 keep 64-bits counters. Thus all tools, that work with networking
1358 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1361 Fix a bug that allowed a tracing process (e.g. gdb) to write
1362 to a memory-mapped file in the traced process's address space
1363 even if neither the traced process nor the tracing process had
1364 write access to that file.
1367 CVS has been removed from the base system. An exact copy
1368 of the code is available from the devel/cvs port.
1371 Some people report the following error after the switch to bmake:
1373 make: illegal option -- J
1374 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1376 *** [buildworld] Error code 2
1378 this likely due to an old instance of make in
1379 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1380 which src/Makefile will use that blindly, if it exists, so if
1381 you see the above error:
1383 rm -rf `make -V MAKEPATH`
1388 Use bmake by default.
1389 Whereas before one could choose to build with bmake via
1390 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1391 make. The goal is to remove these knobs for 10-RELEASE.
1393 It is worth noting that bmake (like gmake) treats the command
1394 line as the unit of failure, rather than statements within the
1395 command line. Thus '(cd some/where && dosomething)' is safer
1396 than 'cd some/where; dosomething'. The '()' allows consistent
1397 behavior in parallel build.
1400 Fix a bug that allows NFS clients to issue READDIR on files.
1403 The WITHOUT_IDEA option has been removed because
1404 the IDEA patent expired.
1407 The sysctl which controls TRIM support under ZFS has been renamed
1408 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1412 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1413 rather than creating it's own in the temporary directory in
1414 order allow access to bootstrapped versions of tools such as
1415 install and mtree. When upgrading from version of FreeBSD where
1416 the install command does not support -l, you will need to
1417 install a new mergemaster command if mergemaster -p is required.
1418 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1422 Legacy ATA stack, disabled and replaced by new CAM-based one since
1423 FreeBSD 9.0, completely removed from the sources. Kernel modules
1424 atadisk and atapi*, user-level tools atacontrol and burncd are
1425 removed. Kernel option `options ATA_CAM` is now permanently enabled
1429 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1430 and socketpair(2). Software, in particular Kerberos, may
1431 automatically detect and use these during building. The resulting
1432 binaries will not work on older kernels.
1435 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1436 information, see the respective 20130304 entry).
1439 Recent commits to callout(9) changed the size of struct callout,
1440 so the KBI is probably heavily disturbed. Also, some functions
1441 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1442 by macros. Every kernel module using it won't load, so rebuild
1445 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1446 but does not initialize by default (because of the new CTL_DISABLE
1447 option) to save memory. To re-enable it, remove the CTL_DISABLE
1448 option from the kernel config file or set kern.cam.ctl.disable=0
1449 in /boot/loader.conf.
1452 The ctl device has been disabled in GENERIC for i386 and amd64.
1453 This was done due to the extra memory being allocated at system
1454 initialisation time by the ctl driver which was only used if
1455 a CAM target device was created. This makes a FreeBSD system
1456 unusable on 128MB or less of RAM.
1459 A new compression method (lz4) has been merged to -HEAD. Please
1460 refer to zpool-features(7) for more information.
1462 Please refer to the "ZFS notes" section of this file for information
1463 on upgrading boot ZFS pools.
1466 A BSD-licensed patch(1) variant has been added and is installed
1467 as bsdpatch, being the GNU version the default patch.
1468 To inverse the logic and use the BSD-licensed one as default,
1469 while having the GNU version installed as gnupatch, rebuild
1470 and install world with the WITH_BSD_PATCH knob set.
1473 Due to the use of the new -l option to install(1) during build
1474 and install, you must take care not to directly set the INSTALL
1475 make variable in your /etc/make.conf, /etc/src.conf, or on the
1476 command line. If you wish to use the -C flag for all installs
1477 you may be able to add INSTALL+=-C to /etc/make.conf or
1481 The install(1) option -M has changed meaning and now takes an
1482 argument that is a file or path to append logs to. In the
1483 unlikely event that -M was the last option on the command line
1484 and the command line contained at least two files and a target
1485 directory the first file will have logs appended to it. The -M
1486 option served little practical purpose in the last decade so its
1487 use is expected to be extremely rare.
1490 After switching to Clang as the default compiler some users of ZFS
1491 on i386 systems started to experience stack overflow kernel panics.
1492 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1495 GEOM_LABEL now mangles label names read from file system metadata.
1496 Mangling affect labels containing spaces, non-printable characters,
1497 '%' or '"'. Device names in /etc/fstab and other places may need to
1501 By default, only the 10 most recent kernel dumps will be saved. To
1502 restore the previous behaviour (no limit on the number of kernel dumps
1503 stored in the dump directory) add the following line to /etc/rc.conf:
1508 With the addition of auditdistd(8), a new auditdistd user is now
1509 required during installworld. "mergemaster -p" can be used to
1510 add the user prior to installworld, as documented in the handbook.
1513 The sin6_scope_id member variable in struct sockaddr_in6 is now
1514 filled by the kernel before passing the structure to the userland via
1515 sysctl or routing socket. This means the KAME-specific embedded scope
1516 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1517 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1518 __FreeBSD_version is bumped to 1000025.
1521 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1522 This means that the world and kernel will be compiled with clang
1523 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1524 and /usr/bin/cpp. To disable this behavior and revert to building
1525 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1526 of current may need to bootstrap WITHOUT_CLANG first if the clang
1527 build fails (its compatibility window doesn't extend to the 9 stable
1531 The IPFIREWALL_FORWARD kernel option has been removed. Its
1532 functionality now turned on by default.
1535 The ZERO_COPY_SOCKET kernel option has been removed and
1536 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1537 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1538 mechanism which is not safe and may result in kernel crashes.
1539 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1540 driver supports disposeable external page sized mbuf storage.
1541 Proper replacements for both zero-copy mechanisms are under
1542 consideration and will eventually lead to complete removal
1543 of the two kernel options.
1546 The IPv4 network stack has been converted to network byte
1547 order. The following modules need to be recompiled together
1548 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1549 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1552 Support for non-MPSAFE filesystems was removed from VFS. The
1553 VFS_VERSION was bumped, all filesystem modules shall be
1557 All the non-MPSAFE filesystems have been disconnected from
1558 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1559 portalfs, smbfs, xfs.
1562 The interface cloning API and ABI has changed. The following
1563 modules need to be recompiled together with kernel:
1564 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1565 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1566 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1569 The sdhci driver was split in two parts: sdhci (generic SD Host
1570 Controller logic) and sdhci_pci (actual hardware driver).
1571 No kernel config modifications are required, but if you
1572 load sdhc as a module you must switch to sdhci_pci instead.
1575 Import the FUSE kernel and userland support into base system.
1578 The GNU sort(1) program has been removed since the BSD-licensed
1579 sort(1) has been the default for quite some time and no serious
1580 problems have been reported. The corresponding WITH_GNU_SORT
1584 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1585 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1589 The net80211(4) ABI has been changed to allow for improved driver
1590 PS-POLL and power-save support. All wireless drivers need to be
1591 recompiled to work with the new kernel.
1594 The random(4) support for the VIA hardware random number
1595 generator (`PADLOCK') is no longer enabled unconditionally.
1596 Add the padlock_rng device in the custom kernel config if
1597 needed. The GENERIC kernels on i386 and amd64 do include the
1598 device, so the change only affects the custom kernel
1602 The pf(4) packet filter ABI has been changed. pfctl(8) and
1603 snmp_pf module need to be recompiled to work with new kernel.
1606 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1607 to -HEAD. Pools that have empty_bpobj in active state can not be
1608 imported read-write with ZFS implementations that do not support
1609 this feature. For more information read the zpool-features(5)
1613 The sparc64 ZFS loader has been changed to no longer try to auto-
1614 detect ZFS providers based on diskN aliases but now requires these
1615 to be explicitly listed in the OFW boot-device environment variable.
1618 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1619 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1620 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1623 The following sysctls and tunables have been renamed for consistency
1624 with other variables:
1625 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1626 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1629 The sort utility has been replaced with BSD sort. For now, GNU sort
1630 is also available as "gnusort" or the default can be set back to
1631 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1632 installed as "bsdsort".
1635 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1636 Starting with this version the old system of ZFS pool versioning
1637 is superseded by "feature flags". This concept enables forward
1638 compatibility against certain future changes in functionality of ZFS
1639 pools. The first read-only compatible "feature flag" for ZFS pools
1640 is named "com.delphix:async_destroy". For more information
1641 read the new zpool-features(5) manual page.
1642 Please refer to the "ZFS notes" section of this file for information
1643 on upgrading boot ZFS pools.
1646 The malloc(3) implementation embedded in libc now uses sources imported
1647 as contrib/jemalloc. The most disruptive API change is to
1648 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1649 delete it prior to installworld, and optionally re-create it using the
1650 new format after rebooting. See malloc.conf(5) for details
1651 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1655 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1656 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1657 now spelled mips. This is to aid compatibility with third-party
1658 software that expects this naming scheme in uname(3). Little-endian
1659 settings are unchanged. If you are updating a big-endian mips64 machine
1660 from before this change, you may need to set MACHINE_ARCH=mips64 in
1661 your environment before the new build system will recognize your machine.
1664 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1668 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1669 nullfs(5) did not pass through all behaviours to the underlying layer,
1670 as a result if we bound to a socket on the lower layer we could connect
1671 only to the lower path; if we bound to the upper layer we could connect
1672 only to the upper path. The new behavior is one can connect to both the
1673 lower and the upper paths regardless what layer path one binds to.
1676 The getifaddrs upgrade path broken with 20111215 has been restored.
1677 If you have upgraded in between 20111215 and 20120209 you need to
1678 recompile libc again with your kernel. You still need to recompile
1679 world to be able to configure CARP but this restriction already
1680 comes from 20111215.
1683 The set_rcvar() function has been removed from /etc/rc.subr. All
1684 base and ports rc.d scripts have been updated, so if you have a
1685 port installed with a script in /usr/local/etc/rc.d you can either
1686 hand-edit the rcvar= line, or reinstall the port.
1688 An easy way to handle the mass-update of /etc/rc.d:
1689 rm /etc/rc.d/* && mergemaster -i
1692 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1693 on the current CPU and prevents other threads from running.
1694 This behavior can be reverted using the kern.stop_scheduler_on_panic
1696 The new behavior can be incompatible with kern.sync_on_panic.
1699 The carp(4) facility has been changed significantly. Configuration
1700 of the CARP protocol via ifconfig(8) has changed, as well as format
1701 of CARP events submitted to devd(8) has changed. See manual pages
1702 for more information. The arpbalance feature of carp(4) is currently
1703 not supported anymore.
1705 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1706 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1707 need to be recompiled.
1710 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1714 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1715 explicitely support non-MPSAFE filesystems.
1716 It is on by default for all supported platform at this present
1720 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1721 i386 and pc98 GENERIC kernel configuration files.
1724 sysinstall has been removed
1727 The stable/9 branch created in subversion. This corresponds to the
1728 RELENG_9 branch in CVS.
1734 Avoid using make -j when upgrading. While generally safe, there are
1735 sometimes problems using -j to upgrade. If your upgrade fails with
1736 -j, please try again without -j. From time to time in the past there
1737 have been problems using -j with buildworld and/or installworld. This
1738 is especially true when upgrading between "distant" versions (eg one
1739 that cross a major release boundary or several minor releases, or when
1740 several months have passed on the -current branch).
1742 Sometimes, obscure build problems are the result of environment
1743 poisoning. This can happen because the make utility reads its
1744 environment when searching for values for global variables. To run
1745 your build attempts in an "environmental clean room", prefix all make
1746 commands with 'env -i '. See the env(1) manual page for more details.
1748 When upgrading from one major version to another it is generally best to
1749 upgrade to the latest code in the currently installed branch first, then
1750 do an upgrade to the new branch. This is the best-tested upgrade path,
1751 and has the highest probability of being successful. Please try this
1752 approach if you encounter problems with a major version upgrade. Since
1753 the stable 4.x branch point, one has generally been able to upgade from
1754 anywhere in the most recent stable branch to head / current (or even the
1755 last couple of stable branches). See the top of this file when there's
1758 When upgrading a live system, having a root shell around before
1759 installing anything can help undo problems. Not having a root shell
1760 around can lead to problems if pam has changed too much from your
1761 starting point to allow continued authentication after the upgrade.
1763 This file should be read as a log of events. When a later event changes
1764 information of a prior event, the prior event should not be deleted.
1765 Instead, a pointer to the entry with the new information should be
1766 placed in the old entry. Readers of this file should also sanity check
1767 older entries before relying on them blindly. Authors of new entries
1768 should write them with this in mind.
1772 When upgrading the boot ZFS pool to a new version, always follow
1775 1.) recompile and reinstall the ZFS boot loader and boot block
1776 (this is part of "make buildworld" and "make installworld")
1778 2.) update the ZFS boot block on your boot drive
1780 The following example updates the ZFS boot block on the first
1781 partition (freebsd-boot) of a GPT partitioned drive ada0:
1782 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1784 Non-boot pools do not need these updates.
1788 If you are updating from a prior version of FreeBSD (even one just
1789 a few days old), you should follow this procedure. It is the most
1790 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1792 make kernel-toolchain
1793 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1794 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1796 To test a kernel once
1797 ---------------------
1798 If you just want to boot a kernel once (because you are not sure
1799 if it works, or if you want to boot a known bad kernel to provide
1800 debugging information) run
1801 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1802 nextboot -k testkernel
1804 To just build a kernel when you know that it won't mess you up
1805 --------------------------------------------------------------
1806 This assumes you are already running a CURRENT system. Replace
1807 ${arch} with the architecture of your machine (e.g. "i386",
1808 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1810 cd src/sys/${arch}/conf
1811 config KERNEL_NAME_HERE
1812 cd ../compile/KERNEL_NAME_HERE
1817 If this fails, go to the "To build a kernel" section.
1819 To rebuild everything and install it on the current system.
1820 -----------------------------------------------------------
1821 # Note: sometimes if you are running current you gotta do more than
1822 # is listed here if you are upgrading from a really old current.
1824 <make sure you have good level 0 dumps>
1826 make kernel KERNCONF=YOUR_KERNEL_HERE
1828 <reboot in single user> [3]
1835 To cross-install current onto a separate partition
1836 --------------------------------------------------
1837 # In this approach we use a separate partition to hold
1838 # current's root, 'usr', and 'var' directories. A partition
1839 # holding "/", "/usr" and "/var" should be about 2GB in
1842 <make sure you have good level 0 dumps>
1845 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1846 <maybe newfs current's root partition>
1847 <mount current's root partition on directory ${CURRENT_ROOT}>
1848 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1849 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1850 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1851 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1852 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1853 <reboot into current>
1854 <do a "native" rebuild/install as described in the previous section>
1855 <maybe install compatibility libraries from ports/misc/compat*>
1859 To upgrade in-place from stable to current
1860 ----------------------------------------------
1861 <make sure you have good level 0 dumps>
1863 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1865 <reboot in single user> [3]
1872 Make sure that you've read the UPDATING file to understand the
1873 tweaks to various things you need. At this point in the life
1874 cycle of current, things change often and you are on your own
1875 to cope. The defaults can also change, so please read ALL of
1876 the UPDATING entries.
1878 Also, if you are tracking -current, you must be subscribed to
1879 freebsd-current@freebsd.org. Make sure that before you update
1880 your sources that you have read and understood all the recent
1881 messages there. If in doubt, please track -stable which has
1882 much fewer pitfalls.
1884 [1] If you have third party modules, such as vmware, you
1885 should disable them at this point so they don't crash your
1888 [3] From the bootblocks, boot -s, and then do
1893 adjkerntz -i # if CMOS is wall time
1894 Also, when doing a major release upgrade, it is required that
1895 you boot into single user mode to do the installworld.
1897 [4] Note: This step is non-optional. Failure to do this step
1898 can result in a significant reduction in the functionality of the
1899 system. Attempting to do it by hand is not recommended and those
1900 that pursue this avenue should read this file carefully, as well
1901 as the archives of freebsd-current and freebsd-hackers mailing lists
1902 for potential gotchas. The -U option is also useful to consider.
1903 See mergemaster(8) for more information.
1905 [5] Usually this step is a noop. However, from time to time
1906 you may need to do this if you get unknown user in the following
1907 step. It never hurts to do it all the time. You may need to
1908 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1909 install) after the buildworld before this step if you last updated
1910 from current before 20130425 or from -stable before 20130430.
1912 [6] This only deletes old files and directories. Old libraries
1913 can be deleted by "make delete-old-libs", but you have to make
1914 sure that no program is using those libraries anymore.
1916 [8] In order to have a kernel that can run the 4.x binaries needed to
1917 do an installworld, you must include the COMPAT_FREEBSD4 option in
1918 your kernel. Failure to do so may leave you with a system that is
1919 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1920 required to run the 5.x binaries on more recent kernels. And so on
1921 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1923 Make sure that you merge any new devices from GENERIC since the
1924 last time you updated your kernel config file.
1926 [9] When checking out sources, you must include the -P flag to have
1927 cvs prune empty directories.
1929 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1930 "?=" instead of the "=" assignment operator, so that buildworld can
1931 override the CPUTYPE if it needs to.
1933 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1934 not on the command line, or in /etc/make.conf. buildworld will
1935 warn if it is improperly defined.
1938 This file contains a list, in reverse chronological order, of major
1939 breakages in tracking -current. It is not guaranteed to be a complete
1940 list of such breakages, and only contains entries since September 23, 2011.
1941 If you need to see UPDATING entries from before that date, you will need
1942 to fetch an UPDATING file from an older FreeBSD release.
1944 Copyright information:
1946 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1948 Redistribution, publication, translation and use, with or without
1949 modification, in full or in part, in any form or format of this
1950 document are permitted without further permission from the author.
1952 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1953 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1954 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1955 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1956 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1957 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1958 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1959 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1960 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1961 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1962 POSSIBILITY OF SUCH DAMAGE.
1964 Contact Warner Losh if you have any questions about your use of