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