1 Updating Information for FreeBSD current users.
3 This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>.
4 See end of file for further details. For commonly done items, please see the
5 COMMON ITEMS: section later in the file. These instructions assume that you
6 basically know what you are doing. If not, then please consult the FreeBSD
9 https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-src.html
11 Items affecting the ports and packages system can be found in
12 /usr/ports/UPDATING. Please read that file before running portupgrade.
14 NOTE: FreeBSD has switched from gcc to clang. If you have trouble bootstrapping
15 from older versions of FreeBSD, try WITHOUT_CLANG and WITH_GCC to bootstrap to
16 the tip of head, and then rebuild without this option. The bootstrap process
17 from older version of current across the gcc/clang cutover is a bit fragile.
19 NOTE TO PEOPLE WHO THINK THAT FreeBSD 12.x IS SLOW:
20 FreeBSD 12.x has many debugging features turned on, in both the kernel
21 and userland. These features attempt to detect incorrect use of
22 system primitives, and encourage loud failure through extra sanity
23 checking and fail stop semantics. They also substantially impact
24 system performance. If you want to do performance measurement,
25 benchmarking, and optimization, you'll want to turn them off. This
26 includes various WITNESS- related kernel options, INVARIANTS, malloc
27 debugging flags in userland, and various verbose features in the
28 kernel. Many developers choose to disable these features on build
29 machines to maximize performance. (To completely disable malloc
30 debugging, define MALLOC_PRODUCTION in /etc/make.conf, or to merely
31 disable the most expensive debugging functionality run
32 "ln -s 'abort:false,junk:false' /etc/malloc.conf".)
35 ****************************** SPECIAL WARNING: ******************************
37 Due to a bug in some versions of clang that's very hard to workaround in
38 the upgrade process, to upgrade to -current you must first upgrade
39 either stable/9 after r286035 or stable/10 after r286033 (including
40 10.3-RELEASE) or current after r286007 (including stable/11 and
41 11.0-RELEASE). These revisions post-date the 10.2 and 9.3 releases, so
42 you'll need to take the unusual step of upgrading to the tip of the
43 stable branch before moving to 11 or -current via a source upgrade.
44 stable/11 and 11.0-RELEASE have working newer compiler. This differs
45 from the historical situation where one could upgrade from anywhere on
46 the last couple of stable branches, so be careful.
48 If you're running a hybrid system on 9.x or 10.x with an updated clang
49 compiler or are using an supported external toolchain, the build system
50 will allow the upgrade. Otherwise it will print a reminder.
52 ****************************** SPECIAL WARNING: ******************************
55 The arm port has split armv6 into armv6 and armv7. armv7 is now
56 a valid TARGET_ARCH/MACHINE_ARCH setting.
59 When building multiple kernels using KERNCONF, non-existent KERNCONF
60 files will produce an error and buildkernel will fail. Previously
61 missing KERNCONF files silently failed giving no indication as to
62 why, only to subsequently discover during installkernel that the
63 desired kernel was never built in the first place.
66 The default serial number format for CTL LUNs has changed. This will
67 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
68 or iSCSI clients care about their LUNs' serial numbers. Users who
69 require serial number stability should hardcode serial numbers in
73 For 32-bit arm compiled for hard-float support, soft-floating point
74 binaries now always get their shared libraries from
75 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
76 /usr/libsoft also existed). Only users with a hard-float ld.so, but
77 soft-float everything else should be affected.
80 The geli password typed at boot is now hidden. To restore the previous
81 behavior, see geli(8) for configuration options.
84 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
85 sysctl values. Minor nit, but requires a rebuild of both world/kernel
89 "make check" behavior (made in ^/head@r295380) has been changed to
90 execute from a limited sandbox, as opposed to executing from
94 - The "beforecheck" and "aftercheck" targets are now specified.
95 - ${CHECKDIR} (added in commit noted above) has been removed.
96 - Legacy behavior can be enabled by setting
97 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
99 If the limited sandbox mode is enabled, "make check" will execute
100 "make distribution", then install, execute the tests, and clean up the
101 sandbox if successful.
103 The "make distribution" and "make install" targets are typically run as
104 root to set appropriate permissions and ownership at installation time.
105 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
106 environment if executing "make check" with limited sandbox mode using
107 an unprivileged user.
110 Since the switch to GPT disk labels, fsck for UFS/FFS has been
111 unable to automatically find alternate superblocks. As of r322297,
112 the information needed to find alternate superblocks has been
113 moved to the end of the area reserved for the boot block.
114 Filesystems created with a newfs of this vintage or later
115 will create the recovery information. If you have a filesystem
116 created prior to this change and wish to have a recovery block
117 created for your filesystem, you can do so by running fsck in
118 forground mode (i.e., do not use the -p or -y options). As it
119 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
120 to which you should answer yes.
123 As of r321665, an NFSv4 server configuration that services
124 Kerberos mounts or clients that do not support the uid/gid in
125 owner/owner_group string capability, must explicitly enable
126 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
127 machine's /etc/rc.conf file.
130 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
131 Please see the 20141231 entry below for information about prerequisites
132 and upgrading, if you are not already using clang 3.5.0 or higher.
135 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
136 r-commands (rlogin, rsh, etc.) to be built with the base system.
139 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
140 a very major ABI incompatible change, so users of FreeBSD/powerpc must
141 be careful when performing source upgrades. It is best to run
142 'make installworld' from an alternate root system, either a live
143 CD/memory stick, or a temporary root partition. Additionally, all ports
144 must be recompiled. powerpc64 is largely unaffected, except in the case
145 of 32-bit compatibility. All 32-bit binaries will be affected.
148 Forward compatibility for the "ino64" project have been committed. This
149 will allow most new binaries to run on older kernels in a limited
150 fashion. This prevents many of the common foot-shooting actions in the
151 upgrade as well as the limited ability to roll back the kernel across
152 the ino64 upgrade. Complicated use cases may not work properly, though
153 enough simpler ones work to allow recovery in most situations.
156 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
157 if you require the GPL compiler.
160 The internal ABI used for communication between the NFS kernel modules
161 was changed by r320085, so __FreeBSD_version was bumped to
162 ensure all the NFS related modules are updated together.
165 The ABI of struct event was changed by extending the data
166 member to 64bit and adding ext fields. For upgrade, same
167 precautions as for the entry 20170523 "ino64" must be
171 The GNU roff toolchain has been removed from base. To render manpages
172 which are not supported by mandoc(1), man(1) can fallback on GNU roff
173 from ports (and recommends to install it).
174 To render roff(7) documents, consider using GNU roff from ports or the
175 heirloom doctools roff toolchain from ports via pkg install groff or
176 via pkg install heirloom-doctools.
179 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
180 smaller runtime footprint builds. This is useful for embedded systems
181 which only require one chipset support.
183 If you load it as a module, make sure this is in /boot/loader.conf:
187 This will load the HAL, all chip/RF backends and if_ath_pci.
188 If you have if_ath_pci in /boot/loader.conf, ensure it is after
189 if_ath or it will not load any HAL chipset support.
191 If you want to selectively load things (eg on ye cheape ARM/MIPS
192 platforms where RAM is at a premium) you should:
195 * load the chip modules in question
196 * load ath_rate, ath_dfs
198 * load if_ath_pci and/or if_ath_ahb depending upon your particular
199 bus bind type - this is where probe/attach is done.
201 For further comments/feedback, poke adrian@ .
204 The "ino64" 64-bit inode project has been committed, which extends
205 a number of types to 64 bits. Upgrading in place requires care and
206 adherence to the documented upgrade procedure.
208 If using a custom kernel configuration ensure that the
209 COMPAT_FREEBSD11 option is included (as during the upgrade the
210 system will be running the ino64 kernel with the existing world).
212 For the safest in-place upgrade begin by removing previous build
213 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
214 full procedure documented below under the heading "To rebuild
215 everything and install it on the current system." Specifically,
216 a reboot is required after installing the new kernel before
220 The NATM framework including the en(4), fatm(4), hatm(4), and
221 patm(4) devices has been removed. Consumers should plan a
222 migration before the end-of-life date for FreeBSD 11.
225 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
226 diff has not been implemented, if those are needed a newer version of
227 GNU diff is available via the diffutils package under the gdiff name.
230 As of r316810 for ipfilter, keep frags is no longer assumed when
231 keep state is specified in a rule. r316810 aligns ipfilter with
232 documentation in man pages separating keep frags from keep state.
233 This allows keep state to be specified without forcing keep frags
234 and allows keep frags to be specified independently of keep state.
235 To maintain previous behaviour, also specify keep frags with
236 keep state (as documented in ipf.conf.5).
239 arm64 builds now use the base system LLD 4.0.0 linker by default,
240 instead of requiring that the aarch64-binutils port or package be
241 installed. To continue using aarch64-binutils, set
242 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
245 The UDP optimization in entry 20160818 that added the sysctl
246 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
247 packets will no longer be treated as L3 broadcast packets.
250 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
251 use any explicitly assigned loopback address available in the jail
252 instead of using the first assigned address of the jail.
255 The ctl.ko module no longer implements the iSCSI target frontend:
256 cfiscsi.ko does instead.
258 If building cfiscsi.ko as a kernel module, the module can be loaded
259 via one of the following methods:
260 - `cfiscsi_load="YES"` in loader.conf(5).
261 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
262 - ctladm(8)/ctld(8), when compiled with iSCSI support
263 (`WITH_ISCSI=yes` in src.conf(5))
265 Please see cfiscsi(4) for more details.
268 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
269 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
270 same source (previously, the dependency of mmcsd.ko on mmc.ko was
271 missing, but mmcsd.ko now will refuse to load if it is incompatible
275 The syntax of ipfw(8) named states was changed to avoid ambiguity.
276 If you have used named states in the firewall rules, you need to modify
277 them after installworld and before rebooting. Now named states must
278 be prefixed with colon.
281 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
282 removed as the userland we provide cannot use them. The KMS version
283 (sys/dev/drm2) supports the same hardware.
286 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
287 Please see the 20141231 entry below for information about prerequisites
288 and upgrading, if you are not already using clang 3.5.0 or higher.
291 The code that provides support for ZFS .zfs/ directory functionality
292 has been reimplemented. It's not possible now to create a snapshot
293 by mkdir under .zfs/snapshot/. That should be the only user visible
297 EISA bus support has been removed. The WITH_EISA option is no longer
301 MCA bus support has been removed.
304 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
305 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
308 The EM_MULTIQUEUE kernel configuration option is deprecated now that
309 the em(4) driver conforms to iflib specifications.
312 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
313 IFLIB. If you have a custom kernel configuration that excludes em(4)
314 but you use igb(4), you need to re-add em(4) to your custom configuration.
317 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
318 Please see the 20141231 entry below for information about prerequisites
319 and upgrading, if you are not already using clang 3.5.0 or higher.
322 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
323 Please see the 20141231 entry below for information about prerequisites
324 and upgrading, if you are not already using clang 3.5.0 or higher.
327 The layout of the pmap structure has changed for powerpc to put the pmap
328 statistics at the front for all CPU variations. libkvm(3) and all tools
329 that link against it need to be recompiled.
332 isl(4) and cyapa(4) drivers now require a new driver,
333 chromebook_platform(4), to work properly on Chromebook-class hardware.
334 On other types of hardware the drivers may need to be configured using
335 device hints. Please see the corresponding manual pages for details.
338 The urtwn(4) driver was merged into rtwn(4) and now consists of
339 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
341 Also, firmware for RTL8188CE was renamed due to possible name
342 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
345 GNU rcs has been removed from base. It is available as packages:
346 - rcs: Latest GPLv3 GNU rcs version.
347 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
351 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
352 modules now requires that the kernel configuration contain the
353 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
356 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
357 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
360 Relocatable object files with the extension of .So have been renamed
361 to use an extension of .pico instead. The purpose of this change is
362 to avoid a name clash with shared libraries on case-insensitive file
363 systems. On those file systems, foo.So is the same file as foo.so.
366 GNU rcs has been turned off by default. It can (temporarily) be built
367 again by adding WITH_RCS knob in src.conf.
368 Otherwise, GNU rcs is available from packages:
369 - rcs: Latest GPLv3 GNU rcs version.
370 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
373 The backup_uses_rcs functionality has been removed from rc.subr.
376 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
377 two separate components, QUEUE_MACRO_DEBUG_TRACE and
378 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
379 QUEUE_MACRO_DEBUG behavior.
382 r304787 changed some ioctl interfaces between the iSCSI userspace
383 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
384 rebuilt to work with new kernels. __FreeBSD_version has been bumped
388 The UDP receive code has been updated to only treat incoming UDP
389 packets that were addressed to an L2 broadcast address as L3
390 broadcast packets. It is not expected that this will affect any
391 standards-conforming UDP application. The new behaviour can be
392 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
396 Remove the openbsd_poll system call.
397 __FreeBSD_version has been bumped because of this.
400 The libc stub for the pipe(2) system call has been replaced with
401 a wrapper that calls the pipe2(2) system call and the pipe(2)
402 system call is now only implemented by the kernels that include
403 "options COMPAT_FREEBSD10" in their config file (this is the
404 default). Users should ensure that this option is enabled in
405 their kernel or upgrade userspace to r302092 before upgrading their
409 CAM will now strip leading spaces from SCSI disks' serial numbers.
410 This will affect users who create UFS filesystems on SCSI disks using
411 those disk's diskid device nodes. For example, if /etc/fstab
412 previously contained a line like
413 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
414 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
415 transforms like gmirror may also be affected. ZFS users should
419 The bitstring(3) API has been updated with new functionality and
420 improved performance. But it is binary-incompatible with the old API.
421 Objects built with the new headers may not be linked against objects
422 built with the old headers.
425 The brk and sbrk functions have been removed from libc on arm64.
426 Binutils from ports has been updated to not link to these
427 functions and should be updated to the latest version before
428 installing a new libc.
431 The armv6 port now defaults to hard float ABI. Limited support
432 for running both hardfloat and soft float on the same system
433 is available using the libraries installed with -DWITH_LIBSOFT.
434 This has only been tested as an upgrade path for installworld
435 and packages may fail or need manual intervention to run. New
436 packages will be needed.
438 To update an existing self-hosted armv6hf system, you must add
439 TARGET_ARCH=armv6 on the make command line for both the build
440 and the install steps.
443 Kernel modules compiled outside of a kernel build now default to
444 installing to /boot/modules instead of /boot/kernel. Many kernel
445 modules built this way (such as those in ports) already overrode
446 KMODDIR explicitly to install into /boot/modules. However,
447 manually building and installing a module from /sys/modules will
448 now install to /boot/modules instead of /boot/kernel.
451 The CAM I/O scheduler has been committed to the kernel. There should be
452 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
453 list of known rogues that claim support for this but actually corrupt
454 data is believed to be complete, be on the lookout for data
455 corruption. The known rogue list is believed to be complete:
457 o Crucial MX100, M550 drives with MU01 firmware.
458 o Micron M510 and M550 drives with MU01 firmware.
459 o Micron M500 prior to MU07 firmware
460 o Samsung 830, 840, and 850 all firmwares
461 o FCCT M500 all firmwares
463 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
464 with working NCQ TRIM. For Micron branded drives, see your sales rep for
465 updated firmware. Black listed drives will work correctly because these
466 drives work correctly so long as no NCQ TRIMs are sent to them. Given
467 this list is the same as found in Linux, it's believed there are no
468 other rogues in the market place. All other models from the above
471 To be safe, if you are at all concerned, you can quirk each of your
472 drives to prevent NCQ from being sent by setting:
473 kern.cam.ada.X.quirks="0x2"
474 in loader.conf. If the drive requires the 4k sector quirk, set the
478 The FAST_DEPEND build option has been removed and its functionality is
479 now the one true way. The old mkdep(1) style of 'make depend' has
480 been removed. See 20160311 for further details.
483 Resource range types have grown from unsigned long to uintmax_t. All
484 drivers, and anything using libdevinfo, need to be recompiled.
487 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
488 builds. It no longer runs mkdep(1) during 'make depend', and the
489 'make depend' stage can safely be skipped now as it is auto ran
490 when building 'make all' and will generate all SRCS and DPSRCS before
491 building anything else. Dependencies are gathered at compile time with
492 -MF flags kept in separate .depend files per object file. Users should
493 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
497 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
498 kernel modules. Therefore, if you load any kernel modules at boot time,
499 please install the boot loaders after you install the kernel, but before
503 make kernel KERNCONF=YOUR_KERNEL_HERE
504 make -C sys/boot install
505 <reboot in single user>
507 Then follow the usual steps, described in the General Notes section,
511 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
512 see the 20141231 entry below for information about prerequisites and
513 upgrading, if you are not already using clang 3.5.0 or higher.
516 The AIO subsystem is now a standard part of the kernel. The
517 VFS_AIO kernel option and aio.ko kernel module have been removed.
518 Due to stability concerns, asynchronous I/O requests are only
519 permitted on sockets and raw disks by default. To enable
520 asynchronous I/O requests on all file types, set the
521 vfs.aio.enable_unsafe sysctl to a non-zero value.
524 The ELF object manipulation tool objcopy is now provided by the
525 ELF Tool Chain project rather than by GNU binutils. It should be a
526 drop-in replacement, with the addition of arm64 support. The
527 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
528 to obtain the GNU version if necessary.
531 Building ZFS pools on top of zvols is prohibited by default. That
532 feature has never worked safely; it's always been prone to deadlocks.
533 Using a zvol as the backing store for a VM guest's virtual disk will
534 still work, even if the guest is using ZFS. Legacy behavior can be
535 restored by setting vfs.zfs.vol.recursive=1.
538 The NONE and HPN patches has been removed from OpenSSH. They are
539 still available in the security/openssh-portable port.
542 With the addition of ypldap(8), a new _ypldap user is now required
543 during installworld. "mergemaster -p" can be used to add the user
544 prior to installworld, as documented in the handbook.
547 The tftp loader (pxeboot) now uses the option root-path directive. As a
548 consequence it no longer looks for a pxeboot.4th file on the tftp
549 server. Instead it uses the regular /boot infrastructure as with the
553 The code to start recording plug and play data into the modules has
554 been committed. While the old tools will properly build a new kernel,
555 a number of warnings about "unknown metadata record 4" will be produced
556 for an older kldxref. To avoid such warnings, make sure to rebuild
557 the kernel toolchain (or world). Make sure that you have r292078 or
558 later when trying to build 292077 or later before rebuilding.
561 Debug data files are now built by default with 'make buildworld' and
562 installed with 'make installworld'. This facilitates debugging but
563 requires more disk space both during the build and for the installed
564 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
568 r291527 changed the internal interface between the nfsd.ko and
569 nfscommon.ko modules. As such, they must both be upgraded to-gether.
570 __FreeBSD_version has been bumped because of this.
573 Add support for unicode collation strings leads to a change of
574 order of files listed by ls(1) for example. To get back to the old
575 behaviour, set LC_COLLATE environment variable to "C".
577 Databases administrators will need to reindex their databases given
578 collation results will be different.
580 Due to a bug in install(1) it is recommended to remove the ancient
581 locales before running make installworld.
583 rm -rf /usr/share/locale/*
586 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
587 libcrypto.so.7 or libssl.so.7 must be recompiled.
590 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
591 Kernel modules isp_2400_multi and isp_2500_multi were removed and
592 should be replaced with isp_2400 and isp_2500 modules respectively.
595 The build previously allowed using 'make -n' to not recurse into
596 sub-directories while showing what commands would be executed, and
597 'make -n -n' to recursively show commands. Now 'make -n' will recurse
598 and 'make -N' will not.
601 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
602 and etcupdate will now use this file. A custom sendmail.cf is now
603 updated via this mechanism rather than via installworld. If you had
604 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
605 want to remove the exclusion or change it to "always install".
606 /etc/mail/sendmail.cf is now managed the same way regardless of
607 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
608 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
611 Compatibility shims for legacy ATA device names have been removed.
612 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
613 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
614 environment variables, /dev/ad* and /dev/ar* symbolic links.
617 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
618 Please see the 20141231 entry below for information about prerequisites
619 and upgrading, if you are not already using clang 3.5.0 or higher.
622 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
623 and renamed from .symbols to .debug. This reduces the size requirements
624 on the boot partition or file system and provides consistency with
625 userland debug files.
627 When using the supported kernel installation method the
628 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
629 as is done with /boot/kernel.
631 Developers wishing to maintain the historical behavior of installing
632 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
635 The wireless drivers had undergone changes that remove the 'parent
636 interface' from the ifconfig -l output. The rc.d network scripts
637 used to check presence of a parent interface in the list, so old
638 scripts would fail to start wireless networking. Thus, etcupdate(3)
639 or mergemaster(8) run is required after kernel update, to update your
640 rc.d scripts in /etc.
643 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
644 These configurations are now automatically interpreted as
645 'scrub fragment reassemble'.
648 Kernel-loadable modules for the random(4) device are back. To use
649 them, the kernel must have
652 options RANDOM_LOADABLE
654 kldload(8) can then be used to load random_fortuna.ko
655 or random_yarrow.ko. Please note that due to the indirect
656 function calls that the loadable modules need to provide,
657 the build-in variants will be slightly more efficient.
659 The random(4) kernel option RANDOM_DUMMY has been retired due to
660 unpopularity. It was not all that useful anyway.
663 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
664 Control over building the ELF Tool Chain tools is now provided by
665 the WITHOUT_TOOLCHAIN knob.
668 The polarity of Pulse Per Second (PPS) capture events with the
669 uart(4) driver has been corrected. Prior to this change the PPS
670 "assert" event corresponded to the trailing edge of a positive PPS
671 pulse and the "clear" event was the leading edge of the next pulse.
673 As the width of a PPS pulse in a typical GPS receiver is on the
674 order of 1 millisecond, most users will not notice any significant
675 difference with this change.
677 Anyone who has compensated for the historical polarity reversal by
678 configuring a negative offset equal to the pulse width will need to
679 remove that workaround.
682 The default group assigned to /dev/dri entries has been changed
683 from 'wheel' to 'video' with the id of '44'. If you want to have
684 access to the dri devices please add yourself to the video group
687 # pw groupmod video -m $USER
690 The menu.rc and loader.rc files will now be replaced during
691 upgrades. Please migrate local changes to menu.rc.local and
692 loader.rc.local instead.
695 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
696 strings and strip have been removed. The src.conf(5) knob
697 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
700 As ZFS requires more kernel stack pages than is the default on some
701 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
702 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
704 Please consider using 'options KSTACK_PAGES=X' where X is greater
705 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
708 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
709 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
710 default, i.e., they will not contain "::". For example, instead
711 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
712 to have a more specific match, such as different map entries for
713 IPv6:0:0 vs IPv6:0. This change requires that configuration
714 data (including maps, files, classes, custom ruleset, etc.) must
715 use the same format, so make certain such configuration data is
716 upgrading. As a very simple check search for patterns like
717 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
718 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
719 the cf option UseCompressedIPv6Addresses.
722 The default kernel entropy-processing algorithm is now
723 Fortuna, replacing Yarrow.
725 Assuming you have 'device random' in your kernel config
726 file, the configurations allow a kernel option to override
727 this default. You may choose *ONE* of:
729 options RANDOM_YARROW # Legacy /dev/random algorithm.
730 options RANDOM_DUMMY # Blocking-only driver.
732 If you have neither, you get Fortuna. For most people,
733 read no further, Fortuna will give a /dev/random that works
734 like it always used to, and the difference will be irrelevant.
736 If you remove 'device random', you get *NO* kernel-processed
737 entropy at all. This may be acceptable to folks building
738 embedded systems, but has complications. Carry on reading,
739 and it is assumed you know what you need.
741 *PLEASE* read random(4) and random(9) if you are in the
742 habit of tweaking kernel configs, and/or if you are a member
743 of the embedded community, wanting specific and not-usual
744 behaviour from your security subsystems.
746 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
747 random', you will NOT have a functioning /dev/random, and
748 many cryptographic features will not work, including SSH.
749 You may also find strange behaviour from the random(3) set
750 of library functions, in particular sranddev(3), srandomdev(3)
751 and arc4random(3). The reason for this is that the KERN_ARND
752 sysctl only returns entropy if it thinks it has some to
753 share, and with RANDOM_DUMMY or no 'device random' this
757 An additional fix for the issue described in the 20150614 sendmail
758 entry below has been been committed in revision 284717.
761 FreeBSD's old make (fmake) has been removed from the system. It is
762 available as the devel/fmake port or via pkg install fmake.
765 The fix for the issue described in the 20150614 sendmail entry
766 below has been been committed in revision 284436. The work
767 around described in that entry is no longer needed unless the
768 default setting is overridden by a confDH_PARAMETERS configuration
769 setting of '5' or pointing to a 512 bit DH parameter file.
772 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
773 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
774 and devel/kyua to version 0.20+ and adjust any calling code to work
775 with Kyuafile and kyua.
778 The import of openssl to address the FreeBSD-SA-15:10.openssl
779 security advisory includes a change which rejects handshakes
780 with DH parameters below 768 bits. sendmail releases prior
781 to 8.15.2 (not yet released), defaulted to a 512 bit
782 DH parameter setting for client connections. To work around
783 this interoperability, sendmail can be configured to use a
784 2048 bit DH parameter by:
786 1. Edit /etc/mail/`hostname`.mc
787 2. If a setting for confDH_PARAMETERS does not exist or
788 exists and is set to a string beginning with '5',
790 3. If a setting for confDH_PARAMETERS exists and is set to
791 a file path, create a new file with:
792 openssl dhparam -out /path/to/file 2048
793 4. Rebuild the .cf file:
794 cd /etc/mail/; make; make install
796 cd /etc/mail/; make restart
798 A sendmail patch is coming, at which time this file will be
802 Generation of legacy formatted entries have been disabled by default
803 in pwd_mkdb(8), as all base system consumers of the legacy formatted
804 entries were converted to use the new format by default when the new,
805 machine independent format have been added and supported since FreeBSD
808 Please see the pwd_mkdb(8) manual page for further details.
811 Clang and llvm have been upgraded to 3.6.1 release. Please see the
812 20141231 entry below for information about prerequisites and upgrading,
813 if you are not already using 3.5.0 or higher.
816 TI platform code switched to using vendor DTS files and this update
817 may break existing systems running on Beaglebone, Beaglebone Black,
820 - dtb files should be regenerated/reinstalled. Filenames are the
821 same but content is different now
822 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
823 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
824 addressing scheme is now pin 25 on /dev/gpioc3.
825 - Pandaboard: /etc/ttys should be updated, serial console device is
826 now /dev/ttyu2, not /dev/ttyu0
829 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
830 If you need the GNU extension from groff soelim(1), install groff
831 from package: pkg install groff, or via ports: textproc/groff.
834 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
835 defined in symlink(7); previously symlinks were silently ignored.
838 The const qualifier has been removed from iconv(3) to comply with
839 POSIX. The ports tree is aware of this from r384038 onwards.
842 Libraries specified by LIBADD in Makefiles must have a corresponding
843 DPADD_<lib> variable to ensure correct dependencies. This is now
844 enforced in src.libnames.mk.
847 From legacy ata(4) driver was removed support for SATA controllers
848 supported by more functional drivers ahci(4), siis(4) and mvs(4).
849 Kernel modules ataahci and ataadaptec were removed completely,
850 replaced by ahci and mvs modules respectively.
853 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
854 the 20141231 entry below for information about prerequisites and
855 upgrading, if you are not already using 3.5.0 or higher.
858 The 32-bit PowerPC kernel has been changed to a position-independent
859 executable. This can only be booted with a version of loader(8)
860 newer than January 31, 2015, so make sure to update both world and
861 kernel before rebooting.
864 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
865 but before r278950, the RNG was not seeded properly. Immediately
866 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
867 ssh keys or openssl keys) that were generated w/ a kernel from that
868 range. This does not affect programs that directly used /dev/random
869 or /dev/urandom. All userland uses of arc4random(3) are affected.
872 The autofs(4) ABI was changed in order to restore binary compatibility
873 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
877 The powerpc64 kernel has been changed to a position-independent
878 executable. This can only be booted with a new version of loader(8),
879 so make sure to update both world and kernel before rebooting.
882 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
883 only release, no new features have been added. Please see the 20141231
884 entry below for information about prerequisites and upgrading, if you
885 are not already using 3.5.0.
888 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
889 taken from the ELF Tool Chain project rather than GNU binutils. They
890 should be drop-in replacements, with the addition of arm64 support.
891 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
892 binutils tools, if necessary. See 20150805 for updated information.
895 The default Unbound configuration now enables remote control
896 using a local socket. Users who have already enabled the
897 local_unbound service should regenerate their configuration
898 by running "service local_unbound setup" as root.
901 The GNU texinfo and GNU info pages have been removed.
902 To be able to view GNU info pages please install texinfo from ports.
905 Clang, llvm and lldb have been upgraded to 3.5.0 release.
907 As of this release, a prerequisite for building clang, llvm and lldb is
908 a C++11 capable compiler and C++11 standard library. This means that to
909 be able to successfully build the cross-tools stage of buildworld, with
910 clang as the bootstrap compiler, your system compiler or cross compiler
911 should either be clang 3.3 or later, or gcc 4.8 or later, and your
912 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
915 On any standard FreeBSD 10.x or 11.x installation, where clang and
916 libc++ are on by default (that is, on x86 or arm), this should work out
919 On 9.x installations where clang is enabled by default, e.g. on x86 and
920 powerpc, libc++ will not be enabled by default, so libc++ should be
921 built (with clang) and installed first. If both clang and libc++ are
922 missing, build clang first, then use it to build libc++.
924 On 8.x and earlier installations, upgrade to 9.x first, and then follow
925 the instructions for 9.x above.
927 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
928 default, and do not build clang.
930 Many embedded systems are resource constrained, and will not be able to
931 build clang in a reasonable time, or in some cases at all. In those
932 cases, cross building bootable systems on amd64 is a workaround.
934 This new version of clang introduces a number of new warnings, of which
935 the following are most likely to appear:
939 This warns in two cases, for both C and C++:
940 * When the code is trying to take the absolute value of an unsigned
941 quantity, which is effectively a no-op, and almost never what was
942 intended. The code should be fixed, if at all possible. If you are
943 sure that the unsigned quantity can be safely cast to signed, without
944 loss of information or undefined behavior, you can add an explicit
945 cast, or disable the warning.
947 * When the code is trying to take an absolute value, but the called
948 abs() variant is for the wrong type, which can lead to truncation.
949 If you want to disable the warning instead of fixing the code, please
950 make sure that truncation will not occur, or it might lead to unwanted
953 -Wtautological-undefined-compare and
954 -Wundefined-bool-conversion
956 These warn when C++ code is trying to compare 'this' against NULL, while
957 'this' should never be NULL in well-defined C++ code. However, there is
958 some legacy (pre C++11) code out there, which actively abuses this
959 feature, which was less strictly defined in previous C++ versions.
961 Squid and openjdk do this, for example. The warning can be turned off
962 for C++98 and earlier, but compiling the code in C++11 mode might result
963 in unexpected behavior; for example, the parts of the program that are
964 unreachable could be optimized away.
967 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
968 kernel sources have been removed. The .h files remain, since some
969 utilities include them. This will need to be fixed later.
970 If "mount -t oldnfs ..." is attempted, it will fail.
971 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
972 the utilities will report errors.
975 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
976 directories to top level SUBDIR variable when their parent
977 directory is included in LOCAL_DIRS. Users with build systems with
978 such hierarchies and without SUBDIR entries in the parent
979 directory Makefiles should add them or add the directories to
983 faith(4) and faithd(8) have been removed from the base system. Faith
984 has been obsolete for a very long time.
987 vt(4), the new console driver, is enabled by default. It brings
988 support for Unicode and double-width characters, as well as
989 support for UEFI and integration with the KMS kernel video
992 You may need to update your console settings in /etc/rc.conf,
993 most probably the keymap. During boot, /etc/rc.d/syscons will
994 indicate what you need to do.
996 vt(4) still has issues and lacks some features compared to
997 syscons(4). See the wiki for up-to-date information:
998 https://wiki.freebsd.org/Newcons
1000 If you want to keep using syscons(4), you can do so by adding
1001 the following line to /boot/loader.conf:
1005 pjdfstest has been integrated into kyua as an opt-in test suite.
1006 Please see share/doc/pjdfstest/README for more details on how to
1010 gperf has been removed from the base system for architectures
1011 that use clang. Ports that require gperf will obtain it from the
1015 pjdfstest has been moved from tools/regression/pjdfstest to
1019 At svn r271982, The default linux compat kernel ABI has been adjusted
1020 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1021 update. If you wish to continue using the linux-f10 compat ports,
1022 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1023 encouraged to update their linux-compat packages to linux-c6 during
1024 their next update cycle.
1027 The ofwfb driver, used to provide a graphics console on PowerPC when
1028 using vt(4), no longer allows mmap() of all physical memory. This
1029 will prevent Xorg on PowerPC with some ATI graphics cards from
1030 initializing properly unless x11-servers/xorg-server is updated to
1034 The xdev targets have been converted to using TARGET and
1035 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1038 The default unbound configuration has been modified to address
1039 issues with reverse lookups on networks that use private
1040 address ranges. If you use the local_unbound service, run
1041 "service local_unbound setup" as root to regenerate your
1042 configuration, then "service local_unbound reload" to load the
1046 The GNU texinfo and GNU info pages are not built and installed
1047 anymore, WITH_INFO knob has been added to allow to built and install
1049 UPDATE: see 20150102 entry on texinfo's removal
1052 The GNU readline library is now an INTERNALLIB - that is, it is
1053 statically linked into consumers (GDB and variants) in the base
1054 system, and the shared library is no longer installed. The
1055 devel/readline port is available for third party software that
1059 The Itanium architecture (ia64) has been removed from the list of
1060 known architectures. This is the first step in the removal of the
1064 Commit r268115 has added NFSv4.1 server support, merged from
1065 projects/nfsv4.1-server. Since this includes changes to the
1066 internal interfaces between the NFS related modules, a full
1067 build of the kernel and modules will be necessary.
1068 __FreeBSD_version has been bumped.
1071 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1072 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1073 which differs from the behaviour controlled by this knob.)
1076 Maximal length of the serial number in CTL was increased from 16 to
1077 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1078 and ctld, need to be rebuilt to work with a new kernel.
1081 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1082 1 respectively to match the upstream numbers. They were out of
1083 sync because, when they were originally added to FreeBSD, the
1084 upstream versions were not respected. These libraries are private
1085 and not yet built by default, so renumbering them should be a
1086 non-issue. However, unclean source trees will yield broken test
1087 programs once the operator executes "make delete-old-libs" after a
1088 "make installworld".
1090 Additionally, the atf-sh binary was made private by moving it into
1091 /usr/libexec/. Already-built shell test programs will keep the
1092 path to the old binary so they will break after "make delete-old"
1095 If you are using WITH_TESTS=yes (not the default), wipe the object
1096 tree and rebuild from scratch to prevent spurious test failures.
1097 This is only needed once: the misnumbered libraries and misplaced
1098 binaries have been added to OptionalObsoleteFiles.inc so they will
1099 be removed during a clean upgrade.
1102 Clang and llvm have been upgraded to 3.4.1 release.
1105 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1106 be removed to avoid issues in the future (and has been added to
1110 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1111 past, it affected all builds that used the bsd.*.mk files. The old
1112 behavior was a bug, but people may have relied upon it. To get this
1113 behavior back, you can .include /etc/src.conf from /etc/make.conf
1114 (which is still global and isn't changed). This also changes the
1115 behavior of incremental builds inside the tree of individual
1116 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1117 Although this has survived make universe and some upgrade scenarios,
1118 other upgrade scenarios may have broken. At least one form of
1119 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1120 as well... In cases where MAKESYSPATH isn't working with this
1121 setting, you'll need to set it to the full path to your tree.
1123 One side effect of all this cleaning up is that bsd.compiler.mk
1124 is no longer implicitly included by bsd.own.mk. If you wish to
1125 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1129 The lindev device has been removed since /dev/full has been made a
1130 standard device. __FreeBSD_version has been bumped.
1133 The knob WITHOUT_VI was added to the base system, which controls
1134 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1135 in order to reorder files share/termcap and didn't build ex(1) as a
1136 build tool, so building/installing with WITH_VI is highly advised for
1137 build hosts for older releases.
1139 This issue has been fixed in stable/9 and stable/10 in r277022 and
1140 r276991, respectively.
1143 The YES_HESIOD knob has been removed. It has been obsolete for
1144 a decade. Please move to using WITH_HESIOD instead or your builds
1145 will silently lack HESIOD.
1148 The uart(4) driver has been changed with respect to its handling
1149 of the low-level console. Previously the uart(4) driver prevented
1150 any process from changing the baudrate or the CLOCAL and HUPCL
1151 control flags. By removing the restrictions, operators can make
1152 changes to the serial console port without having to reboot.
1153 However, when getty(8) is started on the serial device that is
1154 associated with the low-level console, a misconfigured terminal
1155 line in /etc/ttys will now have a real impact.
1156 Before upgrading the kernel, make sure that /etc/ttys has the
1157 serial console device configured as 3wire without baudrate to
1158 preserve the previous behaviour. E.g:
1159 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1162 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1163 to improve performance. To re-enable it, if needed, run rpcbind
1164 with command line option -W.
1167 Switched back to the GPL dtc compiler due to updates in the upstream
1168 dts files not being supported by the BSDL dtc compiler. You will need
1169 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1170 may result while building dtb files during a kernel build if you fail
1171 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1174 Clang and llvm have been upgraded to 3.4 release.
1177 The nve(4) driver has been removed. Please use the nfe(4) driver
1178 for NVIDIA nForce MCP Ethernet adapters instead.
1181 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1182 This could cause certain C++ applications using shared libraries built
1183 against the previous version of libc++ to crash. The incompatibility
1184 has now been fixed, but any C++ applications or shared libraries built
1185 between r261283 and r261801 should be recompiled.
1188 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1189 capability mode support. Please note that enabling the feature in
1190 kernel is still highly recommended.
1193 OpenSSH is now built with sandbox support, and will use sandbox as
1194 the default privilege separation method. This requires Capsicum
1195 capability mode support in kernel.
1198 The libelf and libdwarf libraries have been updated to newer
1199 versions from upstream. Shared library version numbers for
1200 these two libraries were bumped. Any ports or binaries
1201 requiring these two libraries should be recompiled.
1202 __FreeBSD_version is bumped to 1100006.
1205 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1206 instead of providing an explicit one, this would prevent such
1207 Makefile from providing its own Kyuafile in the future during
1208 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1209 intervention is needed to clean an objdir if you use NO_CLEAN:
1210 # find /usr/obj -name Kyuafile | xargs rm -f
1213 The behavior of gss_pseudo_random() for the krb5 mechanism
1214 has changed, for applications requesting a longer random string
1215 than produced by the underlying enctype's pseudo-random() function.
1216 In particular, the random string produced from a session key of
1217 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1218 be different at the 17th octet and later, after this change.
1219 The counter used in the PRF+ construction is now encoded as a
1220 big-endian integer in accordance with RFC 4402.
1221 __FreeBSD_version is bumped to 1100004.
1224 The WITHOUT_ATF build knob has been removed and its functionality
1225 has been subsumed into the more generic WITHOUT_TESTS. If you were
1226 using the former to disable the build of the ATF libraries, you
1227 should change your settings to use the latter.
1230 The default version of mtree is nmtree which is obtained from
1231 NetBSD. The output is generally the same, but may vary
1232 slightly. If you found you need identical output adding
1233 "-F freebsd9" to the command line should do the trick. For the
1234 time being, the old mtree is available as fmtree.
1237 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1238 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1239 1.1.4_8 and verify bsdyml not linked in, before running "make
1241 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1243 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1246 The stable/10 branch has been created in subversion from head
1250 The rc.d/jail script has been updated to support jail(8)
1251 configuration file. The "jail_<jname>_*" rc.conf(5) variables
1252 for per-jail configuration are automatically converted to
1253 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
1254 This is transparently backward compatible. See below about some
1255 incompatibilities and rc.conf(5) manual page for more details.
1257 These variables are now deprecated in favor of jail(8) configuration
1258 file. One can use "rc.d/jail config <jname>" command to generate
1259 a jail(8) configuration file in /var/run/jail.<jname>.conf without
1260 running the jail(8) utility. The default pathname of the
1261 configuration file is /etc/jail.conf and can be specified by
1262 using $jail_conf or $jail_<jname>_conf variables.
1264 Please note that jail_devfs_ruleset accepts an integer at
1265 this moment. Please consider to rewrite the ruleset name
1269 BIND has been removed from the base system. If all you need
1270 is a local resolver, simply enable and start the local_unbound
1271 service instead. Otherwise, several versions of BIND are
1272 available in the ports tree. The dns/bind99 port is one example.
1274 With this change, nslookup(1) and dig(1) are no longer in the base
1275 system. Users should instead use host(1) and drill(1) which are
1276 in the base system. Alternatively, nslookup and dig can
1277 be obtained by installing the dns/bind-tools port.
1280 With the addition of unbound(8), a new unbound user is now
1281 required during installworld. "mergemaster -p" can be used to
1282 add the user prior to installworld, as documented in the handbook.
1285 OpenSSH is now built with DNSSEC support, and will by default
1286 silently trust signed SSHFP records. This can be controlled with
1287 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1288 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1291 The GNU Compiler Collection and C++ standard library (libstdc++)
1292 are no longer built by default on platforms where clang is the system
1293 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1294 options in src.conf.
1297 The PROCDESC kernel option is now part of the GENERIC kernel
1298 configuration and is required for the rwhod(8) to work.
1299 If you are using custom kernel configuration, you should include
1303 The API and ABI related to the Capsicum framework was modified
1304 in backward incompatible way. The userland libraries and programs
1305 have to be recompiled to work with the new kernel. This includes the
1306 following libraries and programs, but the whole buildworld is
1307 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1308 kdump, procstat, rwho, rwhod, uniq.
1311 AES-NI intrinsic support has been added to gcc. The AES-NI module
1312 has been updated to use this support. A new gcc is required to build
1313 the aesni module on both i386 and amd64.
1316 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1317 Thus "device padlock_rng" and "device rdrand_rng" should be
1318 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1321 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1322 enables just the iconv* functionality and is now on by default.
1323 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1324 compatibility. Set WITHOUT_ICONV to build the old way.
1325 If you have been using WITH_ICONV before, you will very likely
1326 need to turn on WITH_LIBICONV_COMPAT.
1329 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1330 Illumos origin, including ZFS. If you have INVARIANTS in your
1331 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1333 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1334 locks if WITNESS option was set. Because that generated a lot of
1335 witness(9) reports and all of them were believed to be false
1336 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1337 can be used to achieve the previous behavior.
1340 Timer values in IPv6 data structures now use time_uptime instead
1341 of time_second. Although this is not a user-visible functional
1342 change, userland utilities which directly use them---ndp(8),
1343 rtadvd(8), and rtsold(8) in the base system---need to be updated
1344 to r253970 or later.
1347 find -delete can now delete the pathnames given as arguments,
1348 instead of only files found below them or if the pathname did
1349 not contain any slashes. Formerly, the following error message
1352 find: -delete: <path>: relative path potentially not safe
1354 Deleting the pathnames given as arguments can be prevented
1355 without error messages using -mindepth 1 or by changing
1356 directory and passing "." as argument to find. This works in the
1357 old as well as the new version of find.
1360 Behavior of devfs rules path matching has been changed.
1361 Pattern is now always matched against fully qualified devfs
1362 path and slash characters must be explicitly matched by
1363 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1364 subdirectories must be reviewed.
1367 The default ARM ABI has changed to the ARM EABI. The old ABI is
1368 incompatible with the ARM EABI and all programs and modules will
1369 need to be rebuilt to work with a new kernel.
1371 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1373 NOTE: Support for the old ABI will be removed in the future and
1374 users are advised to upgrade.
1377 pkg_install has been disconnected from the build if you really need it
1378 you should add WITH_PKGTOOLS in your src.conf(5).
1381 Most of network statistics structures were changed to be able
1382 keep 64-bits counters. Thus all tools, that work with networking
1383 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1386 Fix a bug that allowed a tracing process (e.g. gdb) to write
1387 to a memory-mapped file in the traced process's address space
1388 even if neither the traced process nor the tracing process had
1389 write access to that file.
1392 CVS has been removed from the base system. An exact copy
1393 of the code is available from the devel/cvs port.
1396 Some people report the following error after the switch to bmake:
1398 make: illegal option -- J
1399 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1401 *** [buildworld] Error code 2
1403 this likely due to an old instance of make in
1404 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1405 which src/Makefile will use that blindly, if it exists, so if
1406 you see the above error:
1408 rm -rf `make -V MAKEPATH`
1413 Use bmake by default.
1414 Whereas before one could choose to build with bmake via
1415 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1416 make. The goal is to remove these knobs for 10-RELEASE.
1418 It is worth noting that bmake (like gmake) treats the command
1419 line as the unit of failure, rather than statements within the
1420 command line. Thus '(cd some/where && dosomething)' is safer
1421 than 'cd some/where; dosomething'. The '()' allows consistent
1422 behavior in parallel build.
1425 Fix a bug that allows NFS clients to issue READDIR on files.
1428 The WITHOUT_IDEA option has been removed because
1429 the IDEA patent expired.
1432 The sysctl which controls TRIM support under ZFS has been renamed
1433 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1437 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1438 rather than creating it's own in the temporary directory in
1439 order allow access to bootstrapped versions of tools such as
1440 install and mtree. When upgrading from version of FreeBSD where
1441 the install command does not support -l, you will need to
1442 install a new mergemaster command if mergemaster -p is required.
1443 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1447 Legacy ATA stack, disabled and replaced by new CAM-based one since
1448 FreeBSD 9.0, completely removed from the sources. Kernel modules
1449 atadisk and atapi*, user-level tools atacontrol and burncd are
1450 removed. Kernel option `options ATA_CAM` is now permanently enabled
1454 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1455 and socketpair(2). Software, in particular Kerberos, may
1456 automatically detect and use these during building. The resulting
1457 binaries will not work on older kernels.
1460 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1461 information, see the respective 20130304 entry).
1464 Recent commits to callout(9) changed the size of struct callout,
1465 so the KBI is probably heavily disturbed. Also, some functions
1466 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1467 by macros. Every kernel module using it won't load, so rebuild
1470 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1471 but does not initialize by default (because of the new CTL_DISABLE
1472 option) to save memory. To re-enable it, remove the CTL_DISABLE
1473 option from the kernel config file or set kern.cam.ctl.disable=0
1474 in /boot/loader.conf.
1477 The ctl device has been disabled in GENERIC for i386 and amd64.
1478 This was done due to the extra memory being allocated at system
1479 initialisation time by the ctl driver which was only used if
1480 a CAM target device was created. This makes a FreeBSD system
1481 unusable on 128MB or less of RAM.
1484 A new compression method (lz4) has been merged to -HEAD. Please
1485 refer to zpool-features(7) for more information.
1487 Please refer to the "ZFS notes" section of this file for information
1488 on upgrading boot ZFS pools.
1491 A BSD-licensed patch(1) variant has been added and is installed
1492 as bsdpatch, being the GNU version the default patch.
1493 To inverse the logic and use the BSD-licensed one as default,
1494 while having the GNU version installed as gnupatch, rebuild
1495 and install world with the WITH_BSD_PATCH knob set.
1498 Due to the use of the new -l option to install(1) during build
1499 and install, you must take care not to directly set the INSTALL
1500 make variable in your /etc/make.conf, /etc/src.conf, or on the
1501 command line. If you wish to use the -C flag for all installs
1502 you may be able to add INSTALL+=-C to /etc/make.conf or
1506 The install(1) option -M has changed meaning and now takes an
1507 argument that is a file or path to append logs to. In the
1508 unlikely event that -M was the last option on the command line
1509 and the command line contained at least two files and a target
1510 directory the first file will have logs appended to it. The -M
1511 option served little practical purpose in the last decade so its
1512 use is expected to be extremely rare.
1515 After switching to Clang as the default compiler some users of ZFS
1516 on i386 systems started to experience stack overflow kernel panics.
1517 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1520 GEOM_LABEL now mangles label names read from file system metadata.
1521 Mangling affect labels containing spaces, non-printable characters,
1522 '%' or '"'. Device names in /etc/fstab and other places may need to
1526 By default, only the 10 most recent kernel dumps will be saved. To
1527 restore the previous behaviour (no limit on the number of kernel dumps
1528 stored in the dump directory) add the following line to /etc/rc.conf:
1533 With the addition of auditdistd(8), a new auditdistd user is now
1534 required during installworld. "mergemaster -p" can be used to
1535 add the user prior to installworld, as documented in the handbook.
1538 The sin6_scope_id member variable in struct sockaddr_in6 is now
1539 filled by the kernel before passing the structure to the userland via
1540 sysctl or routing socket. This means the KAME-specific embedded scope
1541 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1542 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1543 __FreeBSD_version is bumped to 1000025.
1546 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1547 This means that the world and kernel will be compiled with clang
1548 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1549 and /usr/bin/cpp. To disable this behavior and revert to building
1550 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1551 of current may need to bootstrap WITHOUT_CLANG first if the clang
1552 build fails (its compatibility window doesn't extend to the 9 stable
1556 The IPFIREWALL_FORWARD kernel option has been removed. Its
1557 functionality now turned on by default.
1560 The ZERO_COPY_SOCKET kernel option has been removed and
1561 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1562 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1563 mechanism which is not safe and may result in kernel crashes.
1564 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1565 driver supports disposeable external page sized mbuf storage.
1566 Proper replacements for both zero-copy mechanisms are under
1567 consideration and will eventually lead to complete removal
1568 of the two kernel options.
1571 The IPv4 network stack has been converted to network byte
1572 order. The following modules need to be recompiled together
1573 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1574 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1577 Support for non-MPSAFE filesystems was removed from VFS. The
1578 VFS_VERSION was bumped, all filesystem modules shall be
1582 All the non-MPSAFE filesystems have been disconnected from
1583 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1584 portalfs, smbfs, xfs.
1587 The interface cloning API and ABI has changed. The following
1588 modules need to be recompiled together with kernel:
1589 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1590 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1591 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1594 The sdhci driver was split in two parts: sdhci (generic SD Host
1595 Controller logic) and sdhci_pci (actual hardware driver).
1596 No kernel config modifications are required, but if you
1597 load sdhc as a module you must switch to sdhci_pci instead.
1600 Import the FUSE kernel and userland support into base system.
1603 The GNU sort(1) program has been removed since the BSD-licensed
1604 sort(1) has been the default for quite some time and no serious
1605 problems have been reported. The corresponding WITH_GNU_SORT
1609 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1610 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1614 The net80211(4) ABI has been changed to allow for improved driver
1615 PS-POLL and power-save support. All wireless drivers need to be
1616 recompiled to work with the new kernel.
1619 The random(4) support for the VIA hardware random number
1620 generator (`PADLOCK') is no longer enabled unconditionally.
1621 Add the padlock_rng device in the custom kernel config if
1622 needed. The GENERIC kernels on i386 and amd64 do include the
1623 device, so the change only affects the custom kernel
1627 The pf(4) packet filter ABI has been changed. pfctl(8) and
1628 snmp_pf module need to be recompiled to work with new kernel.
1631 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1632 to -HEAD. Pools that have empty_bpobj in active state can not be
1633 imported read-write with ZFS implementations that do not support
1634 this feature. For more information read the zpool-features(5)
1638 The sparc64 ZFS loader has been changed to no longer try to auto-
1639 detect ZFS providers based on diskN aliases but now requires these
1640 to be explicitly listed in the OFW boot-device environment variable.
1643 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1644 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1645 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1648 The following sysctls and tunables have been renamed for consistency
1649 with other variables:
1650 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1651 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1654 The sort utility has been replaced with BSD sort. For now, GNU sort
1655 is also available as "gnusort" or the default can be set back to
1656 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1657 installed as "bsdsort".
1660 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1661 Starting with this version the old system of ZFS pool versioning
1662 is superseded by "feature flags". This concept enables forward
1663 compatibility against certain future changes in functionality of ZFS
1664 pools. The first read-only compatible "feature flag" for ZFS pools
1665 is named "com.delphix:async_destroy". For more information
1666 read the new zpool-features(5) manual page.
1667 Please refer to the "ZFS notes" section of this file for information
1668 on upgrading boot ZFS pools.
1671 The malloc(3) implementation embedded in libc now uses sources imported
1672 as contrib/jemalloc. The most disruptive API change is to
1673 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1674 delete it prior to installworld, and optionally re-create it using the
1675 new format after rebooting. See malloc.conf(5) for details
1676 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1680 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1681 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1682 now spelled mips. This is to aid compatibility with third-party
1683 software that expects this naming scheme in uname(3). Little-endian
1684 settings are unchanged. If you are updating a big-endian mips64 machine
1685 from before this change, you may need to set MACHINE_ARCH=mips64 in
1686 your environment before the new build system will recognize your machine.
1689 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1693 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1694 nullfs(5) did not pass through all behaviours to the underlying layer,
1695 as a result if we bound to a socket on the lower layer we could connect
1696 only to the lower path; if we bound to the upper layer we could connect
1697 only to the upper path. The new behavior is one can connect to both the
1698 lower and the upper paths regardless what layer path one binds to.
1701 The getifaddrs upgrade path broken with 20111215 has been restored.
1702 If you have upgraded in between 20111215 and 20120209 you need to
1703 recompile libc again with your kernel. You still need to recompile
1704 world to be able to configure CARP but this restriction already
1705 comes from 20111215.
1708 The set_rcvar() function has been removed from /etc/rc.subr. All
1709 base and ports rc.d scripts have been updated, so if you have a
1710 port installed with a script in /usr/local/etc/rc.d you can either
1711 hand-edit the rcvar= line, or reinstall the port.
1713 An easy way to handle the mass-update of /etc/rc.d:
1714 rm /etc/rc.d/* && mergemaster -i
1717 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1718 on the current CPU and prevents other threads from running.
1719 This behavior can be reverted using the kern.stop_scheduler_on_panic
1721 The new behavior can be incompatible with kern.sync_on_panic.
1724 The carp(4) facility has been changed significantly. Configuration
1725 of the CARP protocol via ifconfig(8) has changed, as well as format
1726 of CARP events submitted to devd(8) has changed. See manual pages
1727 for more information. The arpbalance feature of carp(4) is currently
1728 not supported anymore.
1730 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1731 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1732 need to be recompiled.
1735 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1739 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1740 explicitely support non-MPSAFE filesystems.
1741 It is on by default for all supported platform at this present
1745 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1746 i386 and pc98 GENERIC kernel configuration files.
1749 sysinstall has been removed
1752 The stable/9 branch created in subversion. This corresponds to the
1753 RELENG_9 branch in CVS.
1759 Avoid using make -j when upgrading. While generally safe, there are
1760 sometimes problems using -j to upgrade. If your upgrade fails with
1761 -j, please try again without -j. From time to time in the past there
1762 have been problems using -j with buildworld and/or installworld. This
1763 is especially true when upgrading between "distant" versions (eg one
1764 that cross a major release boundary or several minor releases, or when
1765 several months have passed on the -current branch).
1767 Sometimes, obscure build problems are the result of environment
1768 poisoning. This can happen because the make utility reads its
1769 environment when searching for values for global variables. To run
1770 your build attempts in an "environmental clean room", prefix all make
1771 commands with 'env -i '. See the env(1) manual page for more details.
1773 When upgrading from one major version to another it is generally best to
1774 upgrade to the latest code in the currently installed branch first, then
1775 do an upgrade to the new branch. This is the best-tested upgrade path,
1776 and has the highest probability of being successful. Please try this
1777 approach if you encounter problems with a major version upgrade. Since
1778 the stable 4.x branch point, one has generally been able to upgade from
1779 anywhere in the most recent stable branch to head / current (or even the
1780 last couple of stable branches). See the top of this file when there's
1783 When upgrading a live system, having a root shell around before
1784 installing anything can help undo problems. Not having a root shell
1785 around can lead to problems if pam has changed too much from your
1786 starting point to allow continued authentication after the upgrade.
1788 This file should be read as a log of events. When a later event changes
1789 information of a prior event, the prior event should not be deleted.
1790 Instead, a pointer to the entry with the new information should be
1791 placed in the old entry. Readers of this file should also sanity check
1792 older entries before relying on them blindly. Authors of new entries
1793 should write them with this in mind.
1797 When upgrading the boot ZFS pool to a new version, always follow
1800 1.) recompile and reinstall the ZFS boot loader and boot block
1801 (this is part of "make buildworld" and "make installworld")
1803 2.) update the ZFS boot block on your boot drive
1805 The following example updates the ZFS boot block on the first
1806 partition (freebsd-boot) of a GPT partitioned drive ada0:
1807 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1809 Non-boot pools do not need these updates.
1813 If you are updating from a prior version of FreeBSD (even one just
1814 a few days old), you should follow this procedure. It is the most
1815 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1817 make kernel-toolchain
1818 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1819 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1821 To test a kernel once
1822 ---------------------
1823 If you just want to boot a kernel once (because you are not sure
1824 if it works, or if you want to boot a known bad kernel to provide
1825 debugging information) run
1826 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1827 nextboot -k testkernel
1829 To just build a kernel when you know that it won't mess you up
1830 --------------------------------------------------------------
1831 This assumes you are already running a CURRENT system. Replace
1832 ${arch} with the architecture of your machine (e.g. "i386",
1833 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1835 cd src/sys/${arch}/conf
1836 config KERNEL_NAME_HERE
1837 cd ../compile/KERNEL_NAME_HERE
1842 If this fails, go to the "To build a kernel" section.
1844 To rebuild everything and install it on the current system.
1845 -----------------------------------------------------------
1846 # Note: sometimes if you are running current you gotta do more than
1847 # is listed here if you are upgrading from a really old current.
1849 <make sure you have good level 0 dumps>
1851 make kernel KERNCONF=YOUR_KERNEL_HERE
1853 <reboot in single user> [3]
1860 To cross-install current onto a separate partition
1861 --------------------------------------------------
1862 # In this approach we use a separate partition to hold
1863 # current's root, 'usr', and 'var' directories. A partition
1864 # holding "/", "/usr" and "/var" should be about 2GB in
1867 <make sure you have good level 0 dumps>
1870 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1871 <maybe newfs current's root partition>
1872 <mount current's root partition on directory ${CURRENT_ROOT}>
1873 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1874 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1875 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1876 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1877 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1878 <reboot into current>
1879 <do a "native" rebuild/install as described in the previous section>
1880 <maybe install compatibility libraries from ports/misc/compat*>
1884 To upgrade in-place from stable to current
1885 ----------------------------------------------
1886 <make sure you have good level 0 dumps>
1888 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1890 <reboot in single user> [3]
1897 Make sure that you've read the UPDATING file to understand the
1898 tweaks to various things you need. At this point in the life
1899 cycle of current, things change often and you are on your own
1900 to cope. The defaults can also change, so please read ALL of
1901 the UPDATING entries.
1903 Also, if you are tracking -current, you must be subscribed to
1904 freebsd-current@freebsd.org. Make sure that before you update
1905 your sources that you have read and understood all the recent
1906 messages there. If in doubt, please track -stable which has
1907 much fewer pitfalls.
1909 [1] If you have third party modules, such as vmware, you
1910 should disable them at this point so they don't crash your
1913 [3] From the bootblocks, boot -s, and then do
1918 adjkerntz -i # if CMOS is wall time
1919 Also, when doing a major release upgrade, it is required that
1920 you boot into single user mode to do the installworld.
1922 [4] Note: This step is non-optional. Failure to do this step
1923 can result in a significant reduction in the functionality of the
1924 system. Attempting to do it by hand is not recommended and those
1925 that pursue this avenue should read this file carefully, as well
1926 as the archives of freebsd-current and freebsd-hackers mailing lists
1927 for potential gotchas. The -U option is also useful to consider.
1928 See mergemaster(8) for more information.
1930 [5] Usually this step is a noop. However, from time to time
1931 you may need to do this if you get unknown user in the following
1932 step. It never hurts to do it all the time. You may need to
1933 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1934 install) after the buildworld before this step if you last updated
1935 from current before 20130425 or from -stable before 20130430.
1937 [6] This only deletes old files and directories. Old libraries
1938 can be deleted by "make delete-old-libs", but you have to make
1939 sure that no program is using those libraries anymore.
1941 [8] In order to have a kernel that can run the 4.x binaries needed to
1942 do an installworld, you must include the COMPAT_FREEBSD4 option in
1943 your kernel. Failure to do so may leave you with a system that is
1944 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1945 required to run the 5.x binaries on more recent kernels. And so on
1946 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1948 Make sure that you merge any new devices from GENERIC since the
1949 last time you updated your kernel config file.
1951 [9] When checking out sources, you must include the -P flag to have
1952 cvs prune empty directories.
1954 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1955 "?=" instead of the "=" assignment operator, so that buildworld can
1956 override the CPUTYPE if it needs to.
1958 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1959 not on the command line, or in /etc/make.conf. buildworld will
1960 warn if it is improperly defined.
1963 This file contains a list, in reverse chronological order, of major
1964 breakages in tracking -current. It is not guaranteed to be a complete
1965 list of such breakages, and only contains entries since September 23, 2011.
1966 If you need to see UPDATING entries from before that date, you will need
1967 to fetch an UPDATING file from an older FreeBSD release.
1969 Copyright information:
1971 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1973 Redistribution, publication, translation and use, with or without
1974 modification, in full or in part, in any form or format of this
1975 document are permitted without further permission from the author.
1977 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1978 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1979 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1980 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1981 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1982 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1983 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1984 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1985 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1986 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1987 POSSIBILITY OF SUCH DAMAGE.
1989 Contact Warner Losh if you have any questions about your use of