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 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
56 sysctl values. Minor nit, but requires a rebuild of both world/kernel
60 "make check" behavior (made in ^/head@r295380) has been changed to
61 execute from a limited sandbox, as opposed to executing from
65 - The "beforecheck" and "aftercheck" targets are now specified.
66 - ${CHECKDIR} (added in commit noted above) has been removed.
67 - Legacy behavior can be enabled by setting
68 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
70 If the limited sandbox mode is enabled, "make check" will execute
71 "make distribution", then install, execute the tests, and clean up the
72 sandbox if successful.
74 The "make distribution" and "make install" targets are typically run as
75 root to set appropriate permissions and ownership at installation time.
76 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
77 environment if executing "make check" with limited sandbox mode using
81 Since the switch to GPT disk labels, fsck for UFS/FFS has been
82 unable to automatically find alternate superblocks. As of r322297,
83 the information needed to find alternate superblocks has been
84 moved to the end of the area reserved for the boot block.
85 Filesystems created with a newfs of this vintage or later
86 will create the recovery information. If you have a filesystem
87 created prior to this change and wish to have a recovery block
88 created for your filesystem, you can do so by running fsck in
89 forground mode (i.e., do not use the -p or -y options). As it
90 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
91 to which you should answer yes.
94 As of r321665, an NFSv4 server configuration that services
95 Kerberos mounts or clients that do not support the uid/gid in
96 owner/owner_group string capability, must explicitly enable
97 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
98 machine's /etc/rc.conf file.
101 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
102 Please see the 20141231 entry below for information about prerequisites
103 and upgrading, if you are not already using clang 3.5.0 or higher.
106 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
107 r-commands (rlogin, rsh, etc.) to be built with the base system.
110 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
111 a very major ABI incompatible change, so users of FreeBSD/powerpc must
112 be careful when performing source upgrades. It is best to run
113 'make installworld' from an alternate root system, either a live
114 CD/memory stick, or a temporary root partition. Additionally, all ports
115 must be recompiled. powerpc64 is largely unaffected, except in the case
116 of 32-bit compatibility. All 32-bit binaries will be affected.
119 Forward compatibility for the "ino64" project have been committed. This
120 will allow most new binaries to run on older kernels in a limited
121 fashion. This prevents many of the common foot-shooting actions in the
122 upgrade as well as the limited ability to roll back the kernel across
123 the ino64 upgrade. Complicated use cases may not work properly, though
124 enough simpler ones work to allow recovery in most situations.
127 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
128 if you require the GPL compiler.
131 The internal ABI used for communication between the NFS kernel modules
132 was changed by r320085, so __FreeBSD_version was bumped to
133 ensure all the NFS related modules are updated together.
136 The ABI of struct event was changed by extending the data
137 member to 64bit and adding ext fields. For upgrade, same
138 precautions as for the entry 20170523 "ino64" must be
142 The GNU roff toolchain has been removed from base. To render manpages
143 which are not supported by mandoc(1), man(1) can fallback on GNU roff
144 from ports (and recommends to install it).
145 To render roff(7) documents, consider using GNU roff from ports or the
146 heirloom doctools roff toolchain from ports via pkg install groff or
147 via pkg install heirloom-doctools.
150 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
151 smaller runtime footprint builds. This is useful for embedded systems
152 which only require one chipset support.
154 If you load it as a module, make sure this is in /boot/loader.conf:
158 This will load the HAL, all chip/RF backends and if_ath_pci.
159 If you have if_ath_pci in /boot/loader.conf, ensure it is after
160 if_ath or it will not load any HAL chipset support.
162 If you want to selectively load things (eg on ye cheape ARM/MIPS
163 platforms where RAM is at a premium) you should:
166 * load the chip modules in question
167 * load ath_rate, ath_dfs
169 * load if_ath_pci and/or if_ath_ahb depending upon your particular
170 bus bind type - this is where probe/attach is done.
172 For further comments/feedback, poke adrian@ .
175 The "ino64" 64-bit inode project has been committed, which extends
176 a number of types to 64 bits. Upgrading in place requires care and
177 adherence to the documented upgrade procedure.
179 If using a custom kernel configuration ensure that the
180 COMPAT_FREEBSD11 option is included (as during the upgrade the
181 system will be running the ino64 kernel with the existing world).
183 For the safest in-place upgrade begin by removing previous build
184 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
185 full procedure documented below under the heading "To rebuild
186 everything and install it on the current system." Specifically,
187 a reboot is required after installing the new kernel before
191 The NATM framework including the en(4), fatm(4), hatm(4), and
192 patm(4) devices has been removed. Consumers should plan a
193 migration before the end-of-life date for FreeBSD 11.
196 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
197 diff has not been implemented, if those are needed a newer version of
198 GNU diff is available via the diffutils package under the gdiff name.
201 As of r316810 for ipfilter, keep frags is no longer assumed when
202 keep state is specified in a rule. r316810 aligns ipfilter with
203 documentation in man pages separating keep frags from keep state.
204 This allows keep state to be specified without forcing keep frags
205 and allows keep frags to be specified independently of keep state.
206 To maintain previous behaviour, also specify keep frags with
207 keep state (as documented in ipf.conf.5).
210 arm64 builds now use the base system LLD 4.0.0 linker by default,
211 instead of requiring that the aarch64-binutils port or package be
212 installed. To continue using aarch64-binutils, set
213 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
216 The UDP optimization in entry 20160818 that added the sysctl
217 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
218 packets will no longer be treated as L3 broadcast packets.
221 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
222 use any explicitly assigned loopback address available in the jail
223 instead of using the first assigned address of the jail.
226 The ctl.ko module no longer implements the iSCSI target frontend:
227 cfiscsi.ko does instead.
229 If building cfiscsi.ko as a kernel module, the module can be loaded
230 via one of the following methods:
231 - `cfiscsi_load="YES"` in loader.conf(5).
232 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
233 - ctladm(8)/ctld(8), when compiled with iSCSI support
234 (`WITH_ISCSI=yes` in src.conf(5))
236 Please see cfiscsi(4) for more details.
239 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
240 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
241 same source (previously, the dependency of mmcsd.ko on mmc.ko was
242 missing, but mmcsd.ko now will refuse to load if it is incompatible
246 The syntax of ipfw(8) named states was changed to avoid ambiguity.
247 If you have used named states in the firewall rules, you need to modify
248 them after installworld and before rebooting. Now named states must
249 be prefixed with colon.
252 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
253 removed as the userland we provide cannot use them. The KMS version
254 (sys/dev/drm2) supports the same hardware.
257 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
258 Please see the 20141231 entry below for information about prerequisites
259 and upgrading, if you are not already using clang 3.5.0 or higher.
262 The code that provides support for ZFS .zfs/ directory functionality
263 has been reimplemented. It's not possible now to create a snapshot
264 by mkdir under .zfs/snapshot/. That should be the only user visible
268 EISA bus support has been removed. The WITH_EISA option is no longer
272 MCA bus support has been removed.
275 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
276 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
279 The EM_MULTIQUEUE kernel configuration option is deprecated now that
280 the em(4) driver conforms to iflib specifications.
283 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
284 IFLIB. If you have a custom kernel configuration that excludes em(4)
285 but you use igb(4), you need to re-add em(4) to your custom configuration.
288 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
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 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
294 Please see the 20141231 entry below for information about prerequisites
295 and upgrading, if you are not already using clang 3.5.0 or higher.
298 The layout of the pmap structure has changed for powerpc to put the pmap
299 statistics at the front for all CPU variations. libkvm(3) and all tools
300 that link against it need to be recompiled.
303 isl(4) and cyapa(4) drivers now require a new driver,
304 chromebook_platform(4), to work properly on Chromebook-class hardware.
305 On other types of hardware the drivers may need to be configured using
306 device hints. Please see the corresponding manual pages for details.
309 The urtwn(4) driver was merged into rtwn(4) and now consists of
310 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
312 Also, firmware for RTL8188CE was renamed due to possible name
313 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
316 GNU rcs has been removed from base. It is available as packages:
317 - rcs: Latest GPLv3 GNU rcs version.
318 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
322 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
323 modules now requires that the kernel configuration contain the
324 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
327 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
328 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
331 Relocatable object files with the extension of .So have been renamed
332 to use an extension of .pico instead. The purpose of this change is
333 to avoid a name clash with shared libraries on case-insensitive file
334 systems. On those file systems, foo.So is the same file as foo.so.
337 GNU rcs has been turned off by default. It can (temporarily) be built
338 again by adding WITH_RCS knob in src.conf.
339 Otherwise, GNU rcs is available from packages:
340 - rcs: Latest GPLv3 GNU rcs version.
341 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
344 The backup_uses_rcs functionality has been removed from rc.subr.
347 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
348 two separate components, QUEUE_MACRO_DEBUG_TRACE and
349 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
350 QUEUE_MACRO_DEBUG behavior.
353 r304787 changed some ioctl interfaces between the iSCSI userspace
354 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
355 rebuilt to work with new kernels. __FreeBSD_version has been bumped
359 The UDP receive code has been updated to only treat incoming UDP
360 packets that were addressed to an L2 broadcast address as L3
361 broadcast packets. It is not expected that this will affect any
362 standards-conforming UDP application. The new behaviour can be
363 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
367 Remove the openbsd_poll system call.
368 __FreeBSD_version has been bumped because of this.
371 The libc stub for the pipe(2) system call has been replaced with
372 a wrapper that calls the pipe2(2) system call and the pipe(2)
373 system call is now only implemented by the kernels that include
374 "options COMPAT_FREEBSD10" in their config file (this is the
375 default). Users should ensure that this option is enabled in
376 their kernel or upgrade userspace to r302092 before upgrading their
380 CAM will now strip leading spaces from SCSI disks' serial numbers.
381 This will affect users who create UFS filesystems on SCSI disks using
382 those disk's diskid device nodes. For example, if /etc/fstab
383 previously contained a line like
384 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
385 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
386 transforms like gmirror may also be affected. ZFS users should
390 The bitstring(3) API has been updated with new functionality and
391 improved performance. But it is binary-incompatible with the old API.
392 Objects built with the new headers may not be linked against objects
393 built with the old headers.
396 The brk and sbrk functions have been removed from libc on arm64.
397 Binutils from ports has been updated to not link to these
398 functions and should be updated to the latest version before
399 installing a new libc.
402 The armv6 port now defaults to hard float ABI. Limited support
403 for running both hardfloat and soft float on the same system
404 is available using the libraries installed with -DWITH_LIBSOFT.
405 This has only been tested as an upgrade path for installworld
406 and packages may fail or need manual intervention to run. New
407 packages will be needed.
409 To update an existing self-hosted armv6hf system, you must add
410 TARGET_ARCH=armv6 on the make command line for both the build
411 and the install steps.
414 Kernel modules compiled outside of a kernel build now default to
415 installing to /boot/modules instead of /boot/kernel. Many kernel
416 modules built this way (such as those in ports) already overrode
417 KMODDIR explicitly to install into /boot/modules. However,
418 manually building and installing a module from /sys/modules will
419 now install to /boot/modules instead of /boot/kernel.
422 The CAM I/O scheduler has been committed to the kernel. There should be
423 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
424 list of known rogues that claim support for this but actually corrupt
425 data is believed to be complete, be on the lookout for data
426 corruption. The known rogue list is believed to be complete:
428 o Crucial MX100, M550 drives with MU01 firmware.
429 o Micron M510 and M550 drives with MU01 firmware.
430 o Micron M500 prior to MU07 firmware
431 o Samsung 830, 840, and 850 all firmwares
432 o FCCT M500 all firmwares
434 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
435 with working NCQ TRIM. For Micron branded drives, see your sales rep for
436 updated firmware. Black listed drives will work correctly because these
437 drives work correctly so long as no NCQ TRIMs are sent to them. Given
438 this list is the same as found in Linux, it's believed there are no
439 other rogues in the market place. All other models from the above
442 To be safe, if you are at all concerned, you can quirk each of your
443 drives to prevent NCQ from being sent by setting:
444 kern.cam.ada.X.quirks="0x2"
445 in loader.conf. If the drive requires the 4k sector quirk, set the
449 The FAST_DEPEND build option has been removed and its functionality is
450 now the one true way. The old mkdep(1) style of 'make depend' has
451 been removed. See 20160311 for further details.
454 Resource range types have grown from unsigned long to uintmax_t. All
455 drivers, and anything using libdevinfo, need to be recompiled.
458 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
459 builds. It no longer runs mkdep(1) during 'make depend', and the
460 'make depend' stage can safely be skipped now as it is auto ran
461 when building 'make all' and will generate all SRCS and DPSRCS before
462 building anything else. Dependencies are gathered at compile time with
463 -MF flags kept in separate .depend files per object file. Users should
464 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
468 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
469 kernel modules. Therefore, if you load any kernel modules at boot time,
470 please install the boot loaders after you install the kernel, but before
474 make kernel KERNCONF=YOUR_KERNEL_HERE
475 make -C sys/boot install
476 <reboot in single user>
478 Then follow the usual steps, described in the General Notes section,
482 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
483 see the 20141231 entry below for information about prerequisites and
484 upgrading, if you are not already using clang 3.5.0 or higher.
487 The AIO subsystem is now a standard part of the kernel. The
488 VFS_AIO kernel option and aio.ko kernel module have been removed.
489 Due to stability concerns, asynchronous I/O requests are only
490 permitted on sockets and raw disks by default. To enable
491 asynchronous I/O requests on all file types, set the
492 vfs.aio.enable_unsafe sysctl to a non-zero value.
495 The ELF object manipulation tool objcopy is now provided by the
496 ELF Tool Chain project rather than by GNU binutils. It should be a
497 drop-in replacement, with the addition of arm64 support. The
498 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
499 to obtain the GNU version if necessary.
502 Building ZFS pools on top of zvols is prohibited by default. That
503 feature has never worked safely; it's always been prone to deadlocks.
504 Using a zvol as the backing store for a VM guest's virtual disk will
505 still work, even if the guest is using ZFS. Legacy behavior can be
506 restored by setting vfs.zfs.vol.recursive=1.
509 The NONE and HPN patches has been removed from OpenSSH. They are
510 still available in the security/openssh-portable port.
513 With the addition of ypldap(8), a new _ypldap user is now required
514 during installworld. "mergemaster -p" can be used to add the user
515 prior to installworld, as documented in the handbook.
518 The tftp loader (pxeboot) now uses the option root-path directive. As a
519 consequence it no longer looks for a pxeboot.4th file on the tftp
520 server. Instead it uses the regular /boot infrastructure as with the
524 The code to start recording plug and play data into the modules has
525 been committed. While the old tools will properly build a new kernel,
526 a number of warnings about "unknown metadata record 4" will be produced
527 for an older kldxref. To avoid such warnings, make sure to rebuild
528 the kernel toolchain (or world). Make sure that you have r292078 or
529 later when trying to build 292077 or later before rebuilding.
532 Debug data files are now built by default with 'make buildworld' and
533 installed with 'make installworld'. This facilitates debugging but
534 requires more disk space both during the build and for the installed
535 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
539 r291527 changed the internal interface between the nfsd.ko and
540 nfscommon.ko modules. As such, they must both be upgraded to-gether.
541 __FreeBSD_version has been bumped because of this.
544 Add support for unicode collation strings leads to a change of
545 order of files listed by ls(1) for example. To get back to the old
546 behaviour, set LC_COLLATE environment variable to "C".
548 Databases administrators will need to reindex their databases given
549 collation results will be different.
551 Due to a bug in install(1) it is recommended to remove the ancient
552 locales before running make installworld.
554 rm -rf /usr/share/locale/*
557 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
558 libcrypto.so.7 or libssl.so.7 must be recompiled.
561 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
562 Kernel modules isp_2400_multi and isp_2500_multi were removed and
563 should be replaced with isp_2400 and isp_2500 modules respectively.
566 The build previously allowed using 'make -n' to not recurse into
567 sub-directories while showing what commands would be executed, and
568 'make -n -n' to recursively show commands. Now 'make -n' will recurse
569 and 'make -N' will not.
572 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
573 and etcupdate will now use this file. A custom sendmail.cf is now
574 updated via this mechanism rather than via installworld. If you had
575 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
576 want to remove the exclusion or change it to "always install".
577 /etc/mail/sendmail.cf is now managed the same way regardless of
578 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
579 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
582 Compatibility shims for legacy ATA device names have been removed.
583 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
584 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
585 environment variables, /dev/ad* and /dev/ar* symbolic links.
588 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
589 Please see the 20141231 entry below for information about prerequisites
590 and upgrading, if you are not already using clang 3.5.0 or higher.
593 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
594 and renamed from .symbols to .debug. This reduces the size requirements
595 on the boot partition or file system and provides consistency with
596 userland debug files.
598 When using the supported kernel installation method the
599 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
600 as is done with /boot/kernel.
602 Developers wishing to maintain the historical behavior of installing
603 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
606 The wireless drivers had undergone changes that remove the 'parent
607 interface' from the ifconfig -l output. The rc.d network scripts
608 used to check presence of a parent interface in the list, so old
609 scripts would fail to start wireless networking. Thus, etcupdate(3)
610 or mergemaster(8) run is required after kernel update, to update your
611 rc.d scripts in /etc.
614 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
615 These configurations are now automatically interpreted as
616 'scrub fragment reassemble'.
619 Kernel-loadable modules for the random(4) device are back. To use
620 them, the kernel must have
623 options RANDOM_LOADABLE
625 kldload(8) can then be used to load random_fortuna.ko
626 or random_yarrow.ko. Please note that due to the indirect
627 function calls that the loadable modules need to provide,
628 the build-in variants will be slightly more efficient.
630 The random(4) kernel option RANDOM_DUMMY has been retired due to
631 unpopularity. It was not all that useful anyway.
634 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
635 Control over building the ELF Tool Chain tools is now provided by
636 the WITHOUT_TOOLCHAIN knob.
639 The polarity of Pulse Per Second (PPS) capture events with the
640 uart(4) driver has been corrected. Prior to this change the PPS
641 "assert" event corresponded to the trailing edge of a positive PPS
642 pulse and the "clear" event was the leading edge of the next pulse.
644 As the width of a PPS pulse in a typical GPS receiver is on the
645 order of 1 millisecond, most users will not notice any significant
646 difference with this change.
648 Anyone who has compensated for the historical polarity reversal by
649 configuring a negative offset equal to the pulse width will need to
650 remove that workaround.
653 The default group assigned to /dev/dri entries has been changed
654 from 'wheel' to 'video' with the id of '44'. If you want to have
655 access to the dri devices please add yourself to the video group
658 # pw groupmod video -m $USER
661 The menu.rc and loader.rc files will now be replaced during
662 upgrades. Please migrate local changes to menu.rc.local and
663 loader.rc.local instead.
666 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
667 strings and strip have been removed. The src.conf(5) knob
668 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
671 As ZFS requires more kernel stack pages than is the default on some
672 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
673 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
675 Please consider using 'options KSTACK_PAGES=X' where X is greater
676 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
679 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
680 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
681 default, i.e., they will not contain "::". For example, instead
682 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
683 to have a more specific match, such as different map entries for
684 IPv6:0:0 vs IPv6:0. This change requires that configuration
685 data (including maps, files, classes, custom ruleset, etc.) must
686 use the same format, so make certain such configuration data is
687 upgrading. As a very simple check search for patterns like
688 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
689 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
690 the cf option UseCompressedIPv6Addresses.
693 The default kernel entropy-processing algorithm is now
694 Fortuna, replacing Yarrow.
696 Assuming you have 'device random' in your kernel config
697 file, the configurations allow a kernel option to override
698 this default. You may choose *ONE* of:
700 options RANDOM_YARROW # Legacy /dev/random algorithm.
701 options RANDOM_DUMMY # Blocking-only driver.
703 If you have neither, you get Fortuna. For most people,
704 read no further, Fortuna will give a /dev/random that works
705 like it always used to, and the difference will be irrelevant.
707 If you remove 'device random', you get *NO* kernel-processed
708 entropy at all. This may be acceptable to folks building
709 embedded systems, but has complications. Carry on reading,
710 and it is assumed you know what you need.
712 *PLEASE* read random(4) and random(9) if you are in the
713 habit of tweaking kernel configs, and/or if you are a member
714 of the embedded community, wanting specific and not-usual
715 behaviour from your security subsystems.
717 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
718 random', you will NOT have a functioning /dev/random, and
719 many cryptographic features will not work, including SSH.
720 You may also find strange behaviour from the random(3) set
721 of library functions, in particular sranddev(3), srandomdev(3)
722 and arc4random(3). The reason for this is that the KERN_ARND
723 sysctl only returns entropy if it thinks it has some to
724 share, and with RANDOM_DUMMY or no 'device random' this
728 An additional fix for the issue described in the 20150614 sendmail
729 entry below has been been committed in revision 284717.
732 FreeBSD's old make (fmake) has been removed from the system. It is
733 available as the devel/fmake port or via pkg install fmake.
736 The fix for the issue described in the 20150614 sendmail entry
737 below has been been committed in revision 284436. The work
738 around described in that entry is no longer needed unless the
739 default setting is overridden by a confDH_PARAMETERS configuration
740 setting of '5' or pointing to a 512 bit DH parameter file.
743 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
744 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
745 and devel/kyua to version 0.20+ and adjust any calling code to work
746 with Kyuafile and kyua.
749 The import of openssl to address the FreeBSD-SA-15:10.openssl
750 security advisory includes a change which rejects handshakes
751 with DH parameters below 768 bits. sendmail releases prior
752 to 8.15.2 (not yet released), defaulted to a 512 bit
753 DH parameter setting for client connections. To work around
754 this interoperability, sendmail can be configured to use a
755 2048 bit DH parameter by:
757 1. Edit /etc/mail/`hostname`.mc
758 2. If a setting for confDH_PARAMETERS does not exist or
759 exists and is set to a string beginning with '5',
761 3. If a setting for confDH_PARAMETERS exists and is set to
762 a file path, create a new file with:
763 openssl dhparam -out /path/to/file 2048
764 4. Rebuild the .cf file:
765 cd /etc/mail/; make; make install
767 cd /etc/mail/; make restart
769 A sendmail patch is coming, at which time this file will be
773 Generation of legacy formatted entries have been disabled by default
774 in pwd_mkdb(8), as all base system consumers of the legacy formatted
775 entries were converted to use the new format by default when the new,
776 machine independent format have been added and supported since FreeBSD
779 Please see the pwd_mkdb(8) manual page for further details.
782 Clang and llvm have been upgraded to 3.6.1 release. Please see the
783 20141231 entry below for information about prerequisites and upgrading,
784 if you are not already using 3.5.0 or higher.
787 TI platform code switched to using vendor DTS files and this update
788 may break existing systems running on Beaglebone, Beaglebone Black,
791 - dtb files should be regenerated/reinstalled. Filenames are the
792 same but content is different now
793 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
794 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
795 addressing scheme is now pin 25 on /dev/gpioc3.
796 - Pandaboard: /etc/ttys should be updated, serial console device is
797 now /dev/ttyu2, not /dev/ttyu0
800 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
801 If you need the GNU extension from groff soelim(1), install groff
802 from package: pkg install groff, or via ports: textproc/groff.
805 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
806 defined in symlink(7); previously symlinks were silently ignored.
809 The const qualifier has been removed from iconv(3) to comply with
810 POSIX. The ports tree is aware of this from r384038 onwards.
813 Libraries specified by LIBADD in Makefiles must have a corresponding
814 DPADD_<lib> variable to ensure correct dependencies. This is now
815 enforced in src.libnames.mk.
818 From legacy ata(4) driver was removed support for SATA controllers
819 supported by more functional drivers ahci(4), siis(4) and mvs(4).
820 Kernel modules ataahci and ataadaptec were removed completely,
821 replaced by ahci and mvs modules respectively.
824 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
825 the 20141231 entry below for information about prerequisites and
826 upgrading, if you are not already using 3.5.0 or higher.
829 The 32-bit PowerPC kernel has been changed to a position-independent
830 executable. This can only be booted with a version of loader(8)
831 newer than January 31, 2015, so make sure to update both world and
832 kernel before rebooting.
835 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
836 but before r278950, the RNG was not seeded properly. Immediately
837 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
838 ssh keys or openssl keys) that were generated w/ a kernel from that
839 range. This does not affect programs that directly used /dev/random
840 or /dev/urandom. All userland uses of arc4random(3) are affected.
843 The autofs(4) ABI was changed in order to restore binary compatibility
844 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
848 The powerpc64 kernel has been changed to a position-independent
849 executable. This can only be booted with a new version of loader(8),
850 so make sure to update both world and kernel before rebooting.
853 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
854 only release, no new features have been added. Please see the 20141231
855 entry below for information about prerequisites and upgrading, if you
856 are not already using 3.5.0.
859 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
860 taken from the ELF Tool Chain project rather than GNU binutils. They
861 should be drop-in replacements, with the addition of arm64 support.
862 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
863 binutils tools, if necessary. See 20150805 for updated information.
866 The default Unbound configuration now enables remote control
867 using a local socket. Users who have already enabled the
868 local_unbound service should regenerate their configuration
869 by running "service local_unbound setup" as root.
872 The GNU texinfo and GNU info pages have been removed.
873 To be able to view GNU info pages please install texinfo from ports.
876 Clang, llvm and lldb have been upgraded to 3.5.0 release.
878 As of this release, a prerequisite for building clang, llvm and lldb is
879 a C++11 capable compiler and C++11 standard library. This means that to
880 be able to successfully build the cross-tools stage of buildworld, with
881 clang as the bootstrap compiler, your system compiler or cross compiler
882 should either be clang 3.3 or later, or gcc 4.8 or later, and your
883 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
886 On any standard FreeBSD 10.x or 11.x installation, where clang and
887 libc++ are on by default (that is, on x86 or arm), this should work out
890 On 9.x installations where clang is enabled by default, e.g. on x86 and
891 powerpc, libc++ will not be enabled by default, so libc++ should be
892 built (with clang) and installed first. If both clang and libc++ are
893 missing, build clang first, then use it to build libc++.
895 On 8.x and earlier installations, upgrade to 9.x first, and then follow
896 the instructions for 9.x above.
898 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
899 default, and do not build clang.
901 Many embedded systems are resource constrained, and will not be able to
902 build clang in a reasonable time, or in some cases at all. In those
903 cases, cross building bootable systems on amd64 is a workaround.
905 This new version of clang introduces a number of new warnings, of which
906 the following are most likely to appear:
910 This warns in two cases, for both C and C++:
911 * When the code is trying to take the absolute value of an unsigned
912 quantity, which is effectively a no-op, and almost never what was
913 intended. The code should be fixed, if at all possible. If you are
914 sure that the unsigned quantity can be safely cast to signed, without
915 loss of information or undefined behavior, you can add an explicit
916 cast, or disable the warning.
918 * When the code is trying to take an absolute value, but the called
919 abs() variant is for the wrong type, which can lead to truncation.
920 If you want to disable the warning instead of fixing the code, please
921 make sure that truncation will not occur, or it might lead to unwanted
924 -Wtautological-undefined-compare and
925 -Wundefined-bool-conversion
927 These warn when C++ code is trying to compare 'this' against NULL, while
928 'this' should never be NULL in well-defined C++ code. However, there is
929 some legacy (pre C++11) code out there, which actively abuses this
930 feature, which was less strictly defined in previous C++ versions.
932 Squid and openjdk do this, for example. The warning can be turned off
933 for C++98 and earlier, but compiling the code in C++11 mode might result
934 in unexpected behavior; for example, the parts of the program that are
935 unreachable could be optimized away.
938 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
939 kernel sources have been removed. The .h files remain, since some
940 utilities include them. This will need to be fixed later.
941 If "mount -t oldnfs ..." is attempted, it will fail.
942 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
943 the utilities will report errors.
946 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
947 directories to top level SUBDIR variable when their parent
948 directory is included in LOCAL_DIRS. Users with build systems with
949 such hierarchies and without SUBDIR entries in the parent
950 directory Makefiles should add them or add the directories to
954 faith(4) and faithd(8) have been removed from the base system. Faith
955 has been obsolete for a very long time.
958 vt(4), the new console driver, is enabled by default. It brings
959 support for Unicode and double-width characters, as well as
960 support for UEFI and integration with the KMS kernel video
963 You may need to update your console settings in /etc/rc.conf,
964 most probably the keymap. During boot, /etc/rc.d/syscons will
965 indicate what you need to do.
967 vt(4) still has issues and lacks some features compared to
968 syscons(4). See the wiki for up-to-date information:
969 https://wiki.freebsd.org/Newcons
971 If you want to keep using syscons(4), you can do so by adding
972 the following line to /boot/loader.conf:
976 pjdfstest has been integrated into kyua as an opt-in test suite.
977 Please see share/doc/pjdfstest/README for more details on how to
981 gperf has been removed from the base system for architectures
982 that use clang. Ports that require gperf will obtain it from the
986 pjdfstest has been moved from tools/regression/pjdfstest to
990 At svn r271982, The default linux compat kernel ABI has been adjusted
991 to 2.6.18 in support of the linux-c6 compat ports infrastructure
992 update. If you wish to continue using the linux-f10 compat ports,
993 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
994 encouraged to update their linux-compat packages to linux-c6 during
995 their next update cycle.
998 The ofwfb driver, used to provide a graphics console on PowerPC when
999 using vt(4), no longer allows mmap() of all physical memory. This
1000 will prevent Xorg on PowerPC with some ATI graphics cards from
1001 initializing properly unless x11-servers/xorg-server is updated to
1005 The xdev targets have been converted to using TARGET and
1006 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1009 The default unbound configuration has been modified to address
1010 issues with reverse lookups on networks that use private
1011 address ranges. If you use the local_unbound service, run
1012 "service local_unbound setup" as root to regenerate your
1013 configuration, then "service local_unbound reload" to load the
1017 The GNU texinfo and GNU info pages are not built and installed
1018 anymore, WITH_INFO knob has been added to allow to built and install
1020 UPDATE: see 20150102 entry on texinfo's removal
1023 The GNU readline library is now an INTERNALLIB - that is, it is
1024 statically linked into consumers (GDB and variants) in the base
1025 system, and the shared library is no longer installed. The
1026 devel/readline port is available for third party software that
1030 The Itanium architecture (ia64) has been removed from the list of
1031 known architectures. This is the first step in the removal of the
1035 Commit r268115 has added NFSv4.1 server support, merged from
1036 projects/nfsv4.1-server. Since this includes changes to the
1037 internal interfaces between the NFS related modules, a full
1038 build of the kernel and modules will be necessary.
1039 __FreeBSD_version has been bumped.
1042 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1043 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1044 which differs from the behaviour controlled by this knob.)
1047 Maximal length of the serial number in CTL was increased from 16 to
1048 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1049 and ctld, need to be rebuilt to work with a new kernel.
1052 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1053 1 respectively to match the upstream numbers. They were out of
1054 sync because, when they were originally added to FreeBSD, the
1055 upstream versions were not respected. These libraries are private
1056 and not yet built by default, so renumbering them should be a
1057 non-issue. However, unclean source trees will yield broken test
1058 programs once the operator executes "make delete-old-libs" after a
1059 "make installworld".
1061 Additionally, the atf-sh binary was made private by moving it into
1062 /usr/libexec/. Already-built shell test programs will keep the
1063 path to the old binary so they will break after "make delete-old"
1066 If you are using WITH_TESTS=yes (not the default), wipe the object
1067 tree and rebuild from scratch to prevent spurious test failures.
1068 This is only needed once: the misnumbered libraries and misplaced
1069 binaries have been added to OptionalObsoleteFiles.inc so they will
1070 be removed during a clean upgrade.
1073 Clang and llvm have been upgraded to 3.4.1 release.
1076 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1077 be removed to avoid issues in the future (and has been added to
1081 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1082 past, it affected all builds that used the bsd.*.mk files. The old
1083 behavior was a bug, but people may have relied upon it. To get this
1084 behavior back, you can .include /etc/src.conf from /etc/make.conf
1085 (which is still global and isn't changed). This also changes the
1086 behavior of incremental builds inside the tree of individual
1087 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1088 Although this has survived make universe and some upgrade scenarios,
1089 other upgrade scenarios may have broken. At least one form of
1090 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1091 as well... In cases where MAKESYSPATH isn't working with this
1092 setting, you'll need to set it to the full path to your tree.
1094 One side effect of all this cleaning up is that bsd.compiler.mk
1095 is no longer implicitly included by bsd.own.mk. If you wish to
1096 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1100 The lindev device has been removed since /dev/full has been made a
1101 standard device. __FreeBSD_version has been bumped.
1104 The knob WITHOUT_VI was added to the base system, which controls
1105 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1106 in order to reorder files share/termcap and didn't build ex(1) as a
1107 build tool, so building/installing with WITH_VI is highly advised for
1108 build hosts for older releases.
1110 This issue has been fixed in stable/9 and stable/10 in r277022 and
1111 r276991, respectively.
1114 The YES_HESIOD knob has been removed. It has been obsolete for
1115 a decade. Please move to using WITH_HESIOD instead or your builds
1116 will silently lack HESIOD.
1119 The uart(4) driver has been changed with respect to its handling
1120 of the low-level console. Previously the uart(4) driver prevented
1121 any process from changing the baudrate or the CLOCAL and HUPCL
1122 control flags. By removing the restrictions, operators can make
1123 changes to the serial console port without having to reboot.
1124 However, when getty(8) is started on the serial device that is
1125 associated with the low-level console, a misconfigured terminal
1126 line in /etc/ttys will now have a real impact.
1127 Before upgrading the kernel, make sure that /etc/ttys has the
1128 serial console device configured as 3wire without baudrate to
1129 preserve the previous behaviour. E.g:
1130 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1133 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1134 to improve performance. To re-enable it, if needed, run rpcbind
1135 with command line option -W.
1138 Switched back to the GPL dtc compiler due to updates in the upstream
1139 dts files not being supported by the BSDL dtc compiler. You will need
1140 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1141 may result while building dtb files during a kernel build if you fail
1142 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1145 Clang and llvm have been upgraded to 3.4 release.
1148 The nve(4) driver has been removed. Please use the nfe(4) driver
1149 for NVIDIA nForce MCP Ethernet adapters instead.
1152 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1153 This could cause certain C++ applications using shared libraries built
1154 against the previous version of libc++ to crash. The incompatibility
1155 has now been fixed, but any C++ applications or shared libraries built
1156 between r261283 and r261801 should be recompiled.
1159 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1160 capability mode support. Please note that enabling the feature in
1161 kernel is still highly recommended.
1164 OpenSSH is now built with sandbox support, and will use sandbox as
1165 the default privilege separation method. This requires Capsicum
1166 capability mode support in kernel.
1169 The libelf and libdwarf libraries have been updated to newer
1170 versions from upstream. Shared library version numbers for
1171 these two libraries were bumped. Any ports or binaries
1172 requiring these two libraries should be recompiled.
1173 __FreeBSD_version is bumped to 1100006.
1176 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1177 instead of providing an explicit one, this would prevent such
1178 Makefile from providing its own Kyuafile in the future during
1179 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1180 intervention is needed to clean an objdir if you use NO_CLEAN:
1181 # find /usr/obj -name Kyuafile | xargs rm -f
1184 The behavior of gss_pseudo_random() for the krb5 mechanism
1185 has changed, for applications requesting a longer random string
1186 than produced by the underlying enctype's pseudo-random() function.
1187 In particular, the random string produced from a session key of
1188 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1189 be different at the 17th octet and later, after this change.
1190 The counter used in the PRF+ construction is now encoded as a
1191 big-endian integer in accordance with RFC 4402.
1192 __FreeBSD_version is bumped to 1100004.
1195 The WITHOUT_ATF build knob has been removed and its functionality
1196 has been subsumed into the more generic WITHOUT_TESTS. If you were
1197 using the former to disable the build of the ATF libraries, you
1198 should change your settings to use the latter.
1201 The default version of mtree is nmtree which is obtained from
1202 NetBSD. The output is generally the same, but may vary
1203 slightly. If you found you need identical output adding
1204 "-F freebsd9" to the command line should do the trick. For the
1205 time being, the old mtree is available as fmtree.
1208 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1209 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1210 1.1.4_8 and verify bsdyml not linked in, before running "make
1212 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1214 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1217 The stable/10 branch has been created in subversion from head
1221 The rc.d/jail script has been updated to support jail(8)
1222 configuration file. The "jail_<jname>_*" rc.conf(5) variables
1223 for per-jail configuration are automatically converted to
1224 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
1225 This is transparently backward compatible. See below about some
1226 incompatibilities and rc.conf(5) manual page for more details.
1228 These variables are now deprecated in favor of jail(8) configuration
1229 file. One can use "rc.d/jail config <jname>" command to generate
1230 a jail(8) configuration file in /var/run/jail.<jname>.conf without
1231 running the jail(8) utility. The default pathname of the
1232 configuration file is /etc/jail.conf and can be specified by
1233 using $jail_conf or $jail_<jname>_conf variables.
1235 Please note that jail_devfs_ruleset accepts an integer at
1236 this moment. Please consider to rewrite the ruleset name
1240 BIND has been removed from the base system. If all you need
1241 is a local resolver, simply enable and start the local_unbound
1242 service instead. Otherwise, several versions of BIND are
1243 available in the ports tree. The dns/bind99 port is one example.
1245 With this change, nslookup(1) and dig(1) are no longer in the base
1246 system. Users should instead use host(1) and drill(1) which are
1247 in the base system. Alternatively, nslookup and dig can
1248 be obtained by installing the dns/bind-tools port.
1251 With the addition of unbound(8), a new unbound user is now
1252 required during installworld. "mergemaster -p" can be used to
1253 add the user prior to installworld, as documented in the handbook.
1256 OpenSSH is now built with DNSSEC support, and will by default
1257 silently trust signed SSHFP records. This can be controlled with
1258 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1259 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1262 The GNU Compiler Collection and C++ standard library (libstdc++)
1263 are no longer built by default on platforms where clang is the system
1264 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1265 options in src.conf.
1268 The PROCDESC kernel option is now part of the GENERIC kernel
1269 configuration and is required for the rwhod(8) to work.
1270 If you are using custom kernel configuration, you should include
1274 The API and ABI related to the Capsicum framework was modified
1275 in backward incompatible way. The userland libraries and programs
1276 have to be recompiled to work with the new kernel. This includes the
1277 following libraries and programs, but the whole buildworld is
1278 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1279 kdump, procstat, rwho, rwhod, uniq.
1282 AES-NI intrinsic support has been added to gcc. The AES-NI module
1283 has been updated to use this support. A new gcc is required to build
1284 the aesni module on both i386 and amd64.
1287 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1288 Thus "device padlock_rng" and "device rdrand_rng" should be
1289 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1292 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1293 enables just the iconv* functionality and is now on by default.
1294 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1295 compatibility. Set WITHOUT_ICONV to build the old way.
1296 If you have been using WITH_ICONV before, you will very likely
1297 need to turn on WITH_LIBICONV_COMPAT.
1300 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1301 Illumos origin, including ZFS. If you have INVARIANTS in your
1302 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1304 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1305 locks if WITNESS option was set. Because that generated a lot of
1306 witness(9) reports and all of them were believed to be false
1307 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1308 can be used to achieve the previous behavior.
1311 Timer values in IPv6 data structures now use time_uptime instead
1312 of time_second. Although this is not a user-visible functional
1313 change, userland utilities which directly use them---ndp(8),
1314 rtadvd(8), and rtsold(8) in the base system---need to be updated
1315 to r253970 or later.
1318 find -delete can now delete the pathnames given as arguments,
1319 instead of only files found below them or if the pathname did
1320 not contain any slashes. Formerly, the following error message
1323 find: -delete: <path>: relative path potentially not safe
1325 Deleting the pathnames given as arguments can be prevented
1326 without error messages using -mindepth 1 or by changing
1327 directory and passing "." as argument to find. This works in the
1328 old as well as the new version of find.
1331 Behavior of devfs rules path matching has been changed.
1332 Pattern is now always matched against fully qualified devfs
1333 path and slash characters must be explicitly matched by
1334 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1335 subdirectories must be reviewed.
1338 The default ARM ABI has changed to the ARM EABI. The old ABI is
1339 incompatible with the ARM EABI and all programs and modules will
1340 need to be rebuilt to work with a new kernel.
1342 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1344 NOTE: Support for the old ABI will be removed in the future and
1345 users are advised to upgrade.
1348 pkg_install has been disconnected from the build if you really need it
1349 you should add WITH_PKGTOOLS in your src.conf(5).
1352 Most of network statistics structures were changed to be able
1353 keep 64-bits counters. Thus all tools, that work with networking
1354 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1357 Fix a bug that allowed a tracing process (e.g. gdb) to write
1358 to a memory-mapped file in the traced process's address space
1359 even if neither the traced process nor the tracing process had
1360 write access to that file.
1363 CVS has been removed from the base system. An exact copy
1364 of the code is available from the devel/cvs port.
1367 Some people report the following error after the switch to bmake:
1369 make: illegal option -- J
1370 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1372 *** [buildworld] Error code 2
1374 this likely due to an old instance of make in
1375 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1376 which src/Makefile will use that blindly, if it exists, so if
1377 you see the above error:
1379 rm -rf `make -V MAKEPATH`
1384 Use bmake by default.
1385 Whereas before one could choose to build with bmake via
1386 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1387 make. The goal is to remove these knobs for 10-RELEASE.
1389 It is worth noting that bmake (like gmake) treats the command
1390 line as the unit of failure, rather than statements within the
1391 command line. Thus '(cd some/where && dosomething)' is safer
1392 than 'cd some/where; dosomething'. The '()' allows consistent
1393 behavior in parallel build.
1396 Fix a bug that allows NFS clients to issue READDIR on files.
1399 The WITHOUT_IDEA option has been removed because
1400 the IDEA patent expired.
1403 The sysctl which controls TRIM support under ZFS has been renamed
1404 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1408 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1409 rather than creating it's own in the temporary directory in
1410 order allow access to bootstrapped versions of tools such as
1411 install and mtree. When upgrading from version of FreeBSD where
1412 the install command does not support -l, you will need to
1413 install a new mergemaster command if mergemaster -p is required.
1414 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1418 Legacy ATA stack, disabled and replaced by new CAM-based one since
1419 FreeBSD 9.0, completely removed from the sources. Kernel modules
1420 atadisk and atapi*, user-level tools atacontrol and burncd are
1421 removed. Kernel option `options ATA_CAM` is now permanently enabled
1425 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1426 and socketpair(2). Software, in particular Kerberos, may
1427 automatically detect and use these during building. The resulting
1428 binaries will not work on older kernels.
1431 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1432 information, see the respective 20130304 entry).
1435 Recent commits to callout(9) changed the size of struct callout,
1436 so the KBI is probably heavily disturbed. Also, some functions
1437 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1438 by macros. Every kernel module using it won't load, so rebuild
1441 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1442 but does not initialize by default (because of the new CTL_DISABLE
1443 option) to save memory. To re-enable it, remove the CTL_DISABLE
1444 option from the kernel config file or set kern.cam.ctl.disable=0
1445 in /boot/loader.conf.
1448 The ctl device has been disabled in GENERIC for i386 and amd64.
1449 This was done due to the extra memory being allocated at system
1450 initialisation time by the ctl driver which was only used if
1451 a CAM target device was created. This makes a FreeBSD system
1452 unusable on 128MB or less of RAM.
1455 A new compression method (lz4) has been merged to -HEAD. Please
1456 refer to zpool-features(7) for more information.
1458 Please refer to the "ZFS notes" section of this file for information
1459 on upgrading boot ZFS pools.
1462 A BSD-licensed patch(1) variant has been added and is installed
1463 as bsdpatch, being the GNU version the default patch.
1464 To inverse the logic and use the BSD-licensed one as default,
1465 while having the GNU version installed as gnupatch, rebuild
1466 and install world with the WITH_BSD_PATCH knob set.
1469 Due to the use of the new -l option to install(1) during build
1470 and install, you must take care not to directly set the INSTALL
1471 make variable in your /etc/make.conf, /etc/src.conf, or on the
1472 command line. If you wish to use the -C flag for all installs
1473 you may be able to add INSTALL+=-C to /etc/make.conf or
1477 The install(1) option -M has changed meaning and now takes an
1478 argument that is a file or path to append logs to. In the
1479 unlikely event that -M was the last option on the command line
1480 and the command line contained at least two files and a target
1481 directory the first file will have logs appended to it. The -M
1482 option served little practical purpose in the last decade so its
1483 use is expected to be extremely rare.
1486 After switching to Clang as the default compiler some users of ZFS
1487 on i386 systems started to experience stack overflow kernel panics.
1488 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1491 GEOM_LABEL now mangles label names read from file system metadata.
1492 Mangling affect labels containing spaces, non-printable characters,
1493 '%' or '"'. Device names in /etc/fstab and other places may need to
1497 By default, only the 10 most recent kernel dumps will be saved. To
1498 restore the previous behaviour (no limit on the number of kernel dumps
1499 stored in the dump directory) add the following line to /etc/rc.conf:
1504 With the addition of auditdistd(8), a new auditdistd user is now
1505 required during installworld. "mergemaster -p" can be used to
1506 add the user prior to installworld, as documented in the handbook.
1509 The sin6_scope_id member variable in struct sockaddr_in6 is now
1510 filled by the kernel before passing the structure to the userland via
1511 sysctl or routing socket. This means the KAME-specific embedded scope
1512 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1513 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1514 __FreeBSD_version is bumped to 1000025.
1517 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1518 This means that the world and kernel will be compiled with clang
1519 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1520 and /usr/bin/cpp. To disable this behavior and revert to building
1521 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1522 of current may need to bootstrap WITHOUT_CLANG first if the clang
1523 build fails (its compatibility window doesn't extend to the 9 stable
1527 The IPFIREWALL_FORWARD kernel option has been removed. Its
1528 functionality now turned on by default.
1531 The ZERO_COPY_SOCKET kernel option has been removed and
1532 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1533 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1534 mechanism which is not safe and may result in kernel crashes.
1535 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1536 driver supports disposeable external page sized mbuf storage.
1537 Proper replacements for both zero-copy mechanisms are under
1538 consideration and will eventually lead to complete removal
1539 of the two kernel options.
1542 The IPv4 network stack has been converted to network byte
1543 order. The following modules need to be recompiled together
1544 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1545 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1548 Support for non-MPSAFE filesystems was removed from VFS. The
1549 VFS_VERSION was bumped, all filesystem modules shall be
1553 All the non-MPSAFE filesystems have been disconnected from
1554 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1555 portalfs, smbfs, xfs.
1558 The interface cloning API and ABI has changed. The following
1559 modules need to be recompiled together with kernel:
1560 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1561 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1562 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1565 The sdhci driver was split in two parts: sdhci (generic SD Host
1566 Controller logic) and sdhci_pci (actual hardware driver).
1567 No kernel config modifications are required, but if you
1568 load sdhc as a module you must switch to sdhci_pci instead.
1571 Import the FUSE kernel and userland support into base system.
1574 The GNU sort(1) program has been removed since the BSD-licensed
1575 sort(1) has been the default for quite some time and no serious
1576 problems have been reported. The corresponding WITH_GNU_SORT
1580 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1581 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1585 The net80211(4) ABI has been changed to allow for improved driver
1586 PS-POLL and power-save support. All wireless drivers need to be
1587 recompiled to work with the new kernel.
1590 The random(4) support for the VIA hardware random number
1591 generator (`PADLOCK') is no longer enabled unconditionally.
1592 Add the padlock_rng device in the custom kernel config if
1593 needed. The GENERIC kernels on i386 and amd64 do include the
1594 device, so the change only affects the custom kernel
1598 The pf(4) packet filter ABI has been changed. pfctl(8) and
1599 snmp_pf module need to be recompiled to work with new kernel.
1602 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1603 to -HEAD. Pools that have empty_bpobj in active state can not be
1604 imported read-write with ZFS implementations that do not support
1605 this feature. For more information read the zpool-features(5)
1609 The sparc64 ZFS loader has been changed to no longer try to auto-
1610 detect ZFS providers based on diskN aliases but now requires these
1611 to be explicitly listed in the OFW boot-device environment variable.
1614 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1615 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1616 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1619 The following sysctls and tunables have been renamed for consistency
1620 with other variables:
1621 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1622 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1625 The sort utility has been replaced with BSD sort. For now, GNU sort
1626 is also available as "gnusort" or the default can be set back to
1627 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1628 installed as "bsdsort".
1631 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1632 Starting with this version the old system of ZFS pool versioning
1633 is superseded by "feature flags". This concept enables forward
1634 compatibility against certain future changes in functionality of ZFS
1635 pools. The first read-only compatible "feature flag" for ZFS pools
1636 is named "com.delphix:async_destroy". For more information
1637 read the new zpool-features(5) manual page.
1638 Please refer to the "ZFS notes" section of this file for information
1639 on upgrading boot ZFS pools.
1642 The malloc(3) implementation embedded in libc now uses sources imported
1643 as contrib/jemalloc. The most disruptive API change is to
1644 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1645 delete it prior to installworld, and optionally re-create it using the
1646 new format after rebooting. See malloc.conf(5) for details
1647 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1651 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1652 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1653 now spelled mips. This is to aid compatibility with third-party
1654 software that expects this naming scheme in uname(3). Little-endian
1655 settings are unchanged. If you are updating a big-endian mips64 machine
1656 from before this change, you may need to set MACHINE_ARCH=mips64 in
1657 your environment before the new build system will recognize your machine.
1660 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1664 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1665 nullfs(5) did not pass through all behaviours to the underlying layer,
1666 as a result if we bound to a socket on the lower layer we could connect
1667 only to the lower path; if we bound to the upper layer we could connect
1668 only to the upper path. The new behavior is one can connect to both the
1669 lower and the upper paths regardless what layer path one binds to.
1672 The getifaddrs upgrade path broken with 20111215 has been restored.
1673 If you have upgraded in between 20111215 and 20120209 you need to
1674 recompile libc again with your kernel. You still need to recompile
1675 world to be able to configure CARP but this restriction already
1676 comes from 20111215.
1679 The set_rcvar() function has been removed from /etc/rc.subr. All
1680 base and ports rc.d scripts have been updated, so if you have a
1681 port installed with a script in /usr/local/etc/rc.d you can either
1682 hand-edit the rcvar= line, or reinstall the port.
1684 An easy way to handle the mass-update of /etc/rc.d:
1685 rm /etc/rc.d/* && mergemaster -i
1688 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1689 on the current CPU and prevents other threads from running.
1690 This behavior can be reverted using the kern.stop_scheduler_on_panic
1692 The new behavior can be incompatible with kern.sync_on_panic.
1695 The carp(4) facility has been changed significantly. Configuration
1696 of the CARP protocol via ifconfig(8) has changed, as well as format
1697 of CARP events submitted to devd(8) has changed. See manual pages
1698 for more information. The arpbalance feature of carp(4) is currently
1699 not supported anymore.
1701 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1702 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1703 need to be recompiled.
1706 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1710 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1711 explicitely support non-MPSAFE filesystems.
1712 It is on by default for all supported platform at this present
1716 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1717 i386 and pc98 GENERIC kernel configuration files.
1720 sysinstall has been removed
1723 The stable/9 branch created in subversion. This corresponds to the
1724 RELENG_9 branch in CVS.
1730 Avoid using make -j when upgrading. While generally safe, there are
1731 sometimes problems using -j to upgrade. If your upgrade fails with
1732 -j, please try again without -j. From time to time in the past there
1733 have been problems using -j with buildworld and/or installworld. This
1734 is especially true when upgrading between "distant" versions (eg one
1735 that cross a major release boundary or several minor releases, or when
1736 several months have passed on the -current branch).
1738 Sometimes, obscure build problems are the result of environment
1739 poisoning. This can happen because the make utility reads its
1740 environment when searching for values for global variables. To run
1741 your build attempts in an "environmental clean room", prefix all make
1742 commands with 'env -i '. See the env(1) manual page for more details.
1744 When upgrading from one major version to another it is generally best to
1745 upgrade to the latest code in the currently installed branch first, then
1746 do an upgrade to the new branch. This is the best-tested upgrade path,
1747 and has the highest probability of being successful. Please try this
1748 approach if you encounter problems with a major version upgrade. Since
1749 the stable 4.x branch point, one has generally been able to upgade from
1750 anywhere in the most recent stable branch to head / current (or even the
1751 last couple of stable branches). See the top of this file when there's
1754 When upgrading a live system, having a root shell around before
1755 installing anything can help undo problems. Not having a root shell
1756 around can lead to problems if pam has changed too much from your
1757 starting point to allow continued authentication after the upgrade.
1759 This file should be read as a log of events. When a later event changes
1760 information of a prior event, the prior event should not be deleted.
1761 Instead, a pointer to the entry with the new information should be
1762 placed in the old entry. Readers of this file should also sanity check
1763 older entries before relying on them blindly. Authors of new entries
1764 should write them with this in mind.
1768 When upgrading the boot ZFS pool to a new version, always follow
1771 1.) recompile and reinstall the ZFS boot loader and boot block
1772 (this is part of "make buildworld" and "make installworld")
1774 2.) update the ZFS boot block on your boot drive
1776 The following example updates the ZFS boot block on the first
1777 partition (freebsd-boot) of a GPT partitioned drive ada0:
1778 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1780 Non-boot pools do not need these updates.
1784 If you are updating from a prior version of FreeBSD (even one just
1785 a few days old), you should follow this procedure. It is the most
1786 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1788 make kernel-toolchain
1789 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1790 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1792 To test a kernel once
1793 ---------------------
1794 If you just want to boot a kernel once (because you are not sure
1795 if it works, or if you want to boot a known bad kernel to provide
1796 debugging information) run
1797 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1798 nextboot -k testkernel
1800 To just build a kernel when you know that it won't mess you up
1801 --------------------------------------------------------------
1802 This assumes you are already running a CURRENT system. Replace
1803 ${arch} with the architecture of your machine (e.g. "i386",
1804 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1806 cd src/sys/${arch}/conf
1807 config KERNEL_NAME_HERE
1808 cd ../compile/KERNEL_NAME_HERE
1813 If this fails, go to the "To build a kernel" section.
1815 To rebuild everything and install it on the current system.
1816 -----------------------------------------------------------
1817 # Note: sometimes if you are running current you gotta do more than
1818 # is listed here if you are upgrading from a really old current.
1820 <make sure you have good level 0 dumps>
1822 make kernel KERNCONF=YOUR_KERNEL_HERE
1824 <reboot in single user> [3]
1831 To cross-install current onto a separate partition
1832 --------------------------------------------------
1833 # In this approach we use a separate partition to hold
1834 # current's root, 'usr', and 'var' directories. A partition
1835 # holding "/", "/usr" and "/var" should be about 2GB in
1838 <make sure you have good level 0 dumps>
1841 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1842 <maybe newfs current's root partition>
1843 <mount current's root partition on directory ${CURRENT_ROOT}>
1844 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1845 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1846 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1847 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1848 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1849 <reboot into current>
1850 <do a "native" rebuild/install as described in the previous section>
1851 <maybe install compatibility libraries from ports/misc/compat*>
1855 To upgrade in-place from stable to current
1856 ----------------------------------------------
1857 <make sure you have good level 0 dumps>
1859 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1861 <reboot in single user> [3]
1868 Make sure that you've read the UPDATING file to understand the
1869 tweaks to various things you need. At this point in the life
1870 cycle of current, things change often and you are on your own
1871 to cope. The defaults can also change, so please read ALL of
1872 the UPDATING entries.
1874 Also, if you are tracking -current, you must be subscribed to
1875 freebsd-current@freebsd.org. Make sure that before you update
1876 your sources that you have read and understood all the recent
1877 messages there. If in doubt, please track -stable which has
1878 much fewer pitfalls.
1880 [1] If you have third party modules, such as vmware, you
1881 should disable them at this point so they don't crash your
1884 [3] From the bootblocks, boot -s, and then do
1889 adjkerntz -i # if CMOS is wall time
1890 Also, when doing a major release upgrade, it is required that
1891 you boot into single user mode to do the installworld.
1893 [4] Note: This step is non-optional. Failure to do this step
1894 can result in a significant reduction in the functionality of the
1895 system. Attempting to do it by hand is not recommended and those
1896 that pursue this avenue should read this file carefully, as well
1897 as the archives of freebsd-current and freebsd-hackers mailing lists
1898 for potential gotchas. The -U option is also useful to consider.
1899 See mergemaster(8) for more information.
1901 [5] Usually this step is a noop. However, from time to time
1902 you may need to do this if you get unknown user in the following
1903 step. It never hurts to do it all the time. You may need to
1904 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1905 install) after the buildworld before this step if you last updated
1906 from current before 20130425 or from -stable before 20130430.
1908 [6] This only deletes old files and directories. Old libraries
1909 can be deleted by "make delete-old-libs", but you have to make
1910 sure that no program is using those libraries anymore.
1912 [8] In order to have a kernel that can run the 4.x binaries needed to
1913 do an installworld, you must include the COMPAT_FREEBSD4 option in
1914 your kernel. Failure to do so may leave you with a system that is
1915 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1916 required to run the 5.x binaries on more recent kernels. And so on
1917 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1919 Make sure that you merge any new devices from GENERIC since the
1920 last time you updated your kernel config file.
1922 [9] When checking out sources, you must include the -P flag to have
1923 cvs prune empty directories.
1925 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1926 "?=" instead of the "=" assignment operator, so that buildworld can
1927 override the CPUTYPE if it needs to.
1929 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1930 not on the command line, or in /etc/make.conf. buildworld will
1931 warn if it is improperly defined.
1934 This file contains a list, in reverse chronological order, of major
1935 breakages in tracking -current. It is not guaranteed to be a complete
1936 list of such breakages, and only contains entries since September 23, 2011.
1937 If you need to see UPDATING entries from before that date, you will need
1938 to fetch an UPDATING file from an older FreeBSD release.
1940 Copyright information:
1942 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1944 Redistribution, publication, translation and use, with or without
1945 modification, in full or in part, in any form or format of this
1946 document are permitted without further permission from the author.
1948 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1949 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1950 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1951 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1952 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1953 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1954 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1955 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1956 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1957 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1958 POSSIBILITY OF SUCH DAMAGE.
1960 Contact Warner Losh if you have any questions about your use of