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