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 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
56 options are changing from controlling the build if defined / undefined
57 to controlling the build with explicit 'yes' or 'no' values. They will
58 shift to WITH/WITHOUT options to match other options in the system.
61 libstand has turned into a private library for sys/boot use only.
62 It is no longer supported as a public interface outside of sys/boot.
65 The arm port has split armv6 into armv6 and armv7. armv7 is now
66 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
67 and are running a kernel from before r324363, you will need to add
68 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
71 When building multiple kernels using KERNCONF, non-existent KERNCONF
72 files will produce an error and buildkernel will fail. Previously
73 missing KERNCONF files silently failed giving no indication as to
74 why, only to subsequently discover during installkernel that the
75 desired kernel was never built in the first place.
78 The default serial number format for CTL LUNs has changed. This will
79 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
80 or iSCSI clients care about their LUNs' serial numbers. Users who
81 require serial number stability should hardcode serial numbers in
85 For 32-bit arm compiled for hard-float support, soft-floating point
86 binaries now always get their shared libraries from
87 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
88 /usr/libsoft also existed). Only users with a hard-float ld.so, but
89 soft-float everything else should be affected.
92 The geli password typed at boot is now hidden. To restore the previous
93 behavior, see geli(8) for configuration options.
96 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
97 sysctl values. Minor nit, but requires a rebuild of both world/kernel
101 "make check" behavior (made in ^/head@r295380) has been changed to
102 execute from a limited sandbox, as opposed to executing from
106 - The "beforecheck" and "aftercheck" targets are now specified.
107 - ${CHECKDIR} (added in commit noted above) has been removed.
108 - Legacy behavior can be enabled by setting
109 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
111 If the limited sandbox mode is enabled, "make check" will execute
112 "make distribution", then install, execute the tests, and clean up the
113 sandbox if successful.
115 The "make distribution" and "make install" targets are typically run as
116 root to set appropriate permissions and ownership at installation time.
117 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
118 environment if executing "make check" with limited sandbox mode using
119 an unprivileged user.
122 Since the switch to GPT disk labels, fsck for UFS/FFS has been
123 unable to automatically find alternate superblocks. As of r322297,
124 the information needed to find alternate superblocks has been
125 moved to the end of the area reserved for the boot block.
126 Filesystems created with a newfs of this vintage or later
127 will create the recovery information. If you have a filesystem
128 created prior to this change and wish to have a recovery block
129 created for your filesystem, you can do so by running fsck in
130 forground mode (i.e., do not use the -p or -y options). As it
131 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
132 to which you should answer yes.
135 As of r321665, an NFSv4 server configuration that services
136 Kerberos mounts or clients that do not support the uid/gid in
137 owner/owner_group string capability, must explicitly enable
138 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
139 machine's /etc/rc.conf file.
142 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
143 Please see the 20141231 entry below for information about prerequisites
144 and upgrading, if you are not already using clang 3.5.0 or higher.
147 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
148 r-commands (rlogin, rsh, etc.) to be built with the base system.
151 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
152 a very major ABI incompatible change, so users of FreeBSD/powerpc must
153 be careful when performing source upgrades. It is best to run
154 'make installworld' from an alternate root system, either a live
155 CD/memory stick, or a temporary root partition. Additionally, all ports
156 must be recompiled. powerpc64 is largely unaffected, except in the case
157 of 32-bit compatibility. All 32-bit binaries will be affected.
160 Forward compatibility for the "ino64" project have been committed. This
161 will allow most new binaries to run on older kernels in a limited
162 fashion. This prevents many of the common foot-shooting actions in the
163 upgrade as well as the limited ability to roll back the kernel across
164 the ino64 upgrade. Complicated use cases may not work properly, though
165 enough simpler ones work to allow recovery in most situations.
168 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
169 if you require the GPL compiler.
172 The internal ABI used for communication between the NFS kernel modules
173 was changed by r320085, so __FreeBSD_version was bumped to
174 ensure all the NFS related modules are updated together.
177 The ABI of struct event was changed by extending the data
178 member to 64bit and adding ext fields. For upgrade, same
179 precautions as for the entry 20170523 "ino64" must be
183 The GNU roff toolchain has been removed from base. To render manpages
184 which are not supported by mandoc(1), man(1) can fallback on GNU roff
185 from ports (and recommends to install it).
186 To render roff(7) documents, consider using GNU roff from ports or the
187 heirloom doctools roff toolchain from ports via pkg install groff or
188 via pkg install heirloom-doctools.
191 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
192 smaller runtime footprint builds. This is useful for embedded systems
193 which only require one chipset support.
195 If you load it as a module, make sure this is in /boot/loader.conf:
199 This will load the HAL, all chip/RF backends and if_ath_pci.
200 If you have if_ath_pci in /boot/loader.conf, ensure it is after
201 if_ath or it will not load any HAL chipset support.
203 If you want to selectively load things (eg on ye cheape ARM/MIPS
204 platforms where RAM is at a premium) you should:
207 * load the chip modules in question
208 * load ath_rate, ath_dfs
210 * load if_ath_pci and/or if_ath_ahb depending upon your particular
211 bus bind type - this is where probe/attach is done.
213 For further comments/feedback, poke adrian@ .
216 The "ino64" 64-bit inode project has been committed, which extends
217 a number of types to 64 bits. Upgrading in place requires care and
218 adherence to the documented upgrade procedure.
220 If using a custom kernel configuration ensure that the
221 COMPAT_FREEBSD11 option is included (as during the upgrade the
222 system will be running the ino64 kernel with the existing world).
224 For the safest in-place upgrade begin by removing previous build
225 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
226 full procedure documented below under the heading "To rebuild
227 everything and install it on the current system." Specifically,
228 a reboot is required after installing the new kernel before
232 The NATM framework including the en(4), fatm(4), hatm(4), and
233 patm(4) devices has been removed. Consumers should plan a
234 migration before the end-of-life date for FreeBSD 11.
237 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
238 diff has not been implemented, if those are needed a newer version of
239 GNU diff is available via the diffutils package under the gdiff name.
242 As of r316810 for ipfilter, keep frags is no longer assumed when
243 keep state is specified in a rule. r316810 aligns ipfilter with
244 documentation in man pages separating keep frags from keep state.
245 This allows keep state to be specified without forcing keep frags
246 and allows keep frags to be specified independently of keep state.
247 To maintain previous behaviour, also specify keep frags with
248 keep state (as documented in ipf.conf.5).
251 arm64 builds now use the base system LLD 4.0.0 linker by default,
252 instead of requiring that the aarch64-binutils port or package be
253 installed. To continue using aarch64-binutils, set
254 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
257 The UDP optimization in entry 20160818 that added the sysctl
258 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
259 packets will no longer be treated as L3 broadcast packets.
262 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
263 use any explicitly assigned loopback address available in the jail
264 instead of using the first assigned address of the jail.
267 The ctl.ko module no longer implements the iSCSI target frontend:
268 cfiscsi.ko does instead.
270 If building cfiscsi.ko as a kernel module, the module can be loaded
271 via one of the following methods:
272 - `cfiscsi_load="YES"` in loader.conf(5).
273 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
274 - ctladm(8)/ctld(8), when compiled with iSCSI support
275 (`WITH_ISCSI=yes` in src.conf(5))
277 Please see cfiscsi(4) for more details.
280 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
281 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
282 same source (previously, the dependency of mmcsd.ko on mmc.ko was
283 missing, but mmcsd.ko now will refuse to load if it is incompatible
287 The syntax of ipfw(8) named states was changed to avoid ambiguity.
288 If you have used named states in the firewall rules, you need to modify
289 them after installworld and before rebooting. Now named states must
290 be prefixed with colon.
293 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
294 removed as the userland we provide cannot use them. The KMS version
295 (sys/dev/drm2) supports the same hardware.
298 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
299 Please see the 20141231 entry below for information about prerequisites
300 and upgrading, if you are not already using clang 3.5.0 or higher.
303 The code that provides support for ZFS .zfs/ directory functionality
304 has been reimplemented. It's not possible now to create a snapshot
305 by mkdir under .zfs/snapshot/. That should be the only user visible
309 EISA bus support has been removed. The WITH_EISA option is no longer
313 MCA bus support has been removed.
316 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
317 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
320 The EM_MULTIQUEUE kernel configuration option is deprecated now that
321 the em(4) driver conforms to iflib specifications.
324 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
325 IFLIB. If you have a custom kernel configuration that excludes em(4)
326 but you use igb(4), you need to re-add em(4) to your custom configuration.
329 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
330 Please see the 20141231 entry below for information about prerequisites
331 and upgrading, if you are not already using clang 3.5.0 or higher.
334 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
335 Please see the 20141231 entry below for information about prerequisites
336 and upgrading, if you are not already using clang 3.5.0 or higher.
339 The layout of the pmap structure has changed for powerpc to put the pmap
340 statistics at the front for all CPU variations. libkvm(3) and all tools
341 that link against it need to be recompiled.
344 isl(4) and cyapa(4) drivers now require a new driver,
345 chromebook_platform(4), to work properly on Chromebook-class hardware.
346 On other types of hardware the drivers may need to be configured using
347 device hints. Please see the corresponding manual pages for details.
350 The urtwn(4) driver was merged into rtwn(4) and now consists of
351 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
353 Also, firmware for RTL8188CE was renamed due to possible name
354 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
357 GNU rcs has been removed from base. It is available as packages:
358 - rcs: Latest GPLv3 GNU rcs version.
359 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
363 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
364 modules now requires that the kernel configuration contain the
365 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
368 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
369 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
372 Relocatable object files with the extension of .So have been renamed
373 to use an extension of .pico instead. The purpose of this change is
374 to avoid a name clash with shared libraries on case-insensitive file
375 systems. On those file systems, foo.So is the same file as foo.so.
378 GNU rcs has been turned off by default. It can (temporarily) be built
379 again by adding WITH_RCS knob in src.conf.
380 Otherwise, GNU rcs is available from packages:
381 - rcs: Latest GPLv3 GNU rcs version.
382 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
385 The backup_uses_rcs functionality has been removed from rc.subr.
388 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
389 two separate components, QUEUE_MACRO_DEBUG_TRACE and
390 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
391 QUEUE_MACRO_DEBUG behavior.
394 r304787 changed some ioctl interfaces between the iSCSI userspace
395 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
396 rebuilt to work with new kernels. __FreeBSD_version has been bumped
400 The UDP receive code has been updated to only treat incoming UDP
401 packets that were addressed to an L2 broadcast address as L3
402 broadcast packets. It is not expected that this will affect any
403 standards-conforming UDP application. The new behaviour can be
404 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
408 Remove the openbsd_poll system call.
409 __FreeBSD_version has been bumped because of this.
412 The libc stub for the pipe(2) system call has been replaced with
413 a wrapper that calls the pipe2(2) system call and the pipe(2)
414 system call is now only implemented by the kernels that include
415 "options COMPAT_FREEBSD10" in their config file (this is the
416 default). Users should ensure that this option is enabled in
417 their kernel or upgrade userspace to r302092 before upgrading their
421 CAM will now strip leading spaces from SCSI disks' serial numbers.
422 This will affect users who create UFS filesystems on SCSI disks using
423 those disk's diskid device nodes. For example, if /etc/fstab
424 previously contained a line like
425 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
426 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
427 transforms like gmirror may also be affected. ZFS users should
431 The bitstring(3) API has been updated with new functionality and
432 improved performance. But it is binary-incompatible with the old API.
433 Objects built with the new headers may not be linked against objects
434 built with the old headers.
437 The brk and sbrk functions have been removed from libc on arm64.
438 Binutils from ports has been updated to not link to these
439 functions and should be updated to the latest version before
440 installing a new libc.
443 The armv6 port now defaults to hard float ABI. Limited support
444 for running both hardfloat and soft float on the same system
445 is available using the libraries installed with -DWITH_LIBSOFT.
446 This has only been tested as an upgrade path for installworld
447 and packages may fail or need manual intervention to run. New
448 packages will be needed.
450 To update an existing self-hosted armv6hf system, you must add
451 TARGET_ARCH=armv6 on the make command line for both the build
452 and the install steps.
455 Kernel modules compiled outside of a kernel build now default to
456 installing to /boot/modules instead of /boot/kernel. Many kernel
457 modules built this way (such as those in ports) already overrode
458 KMODDIR explicitly to install into /boot/modules. However,
459 manually building and installing a module from /sys/modules will
460 now install to /boot/modules instead of /boot/kernel.
463 The CAM I/O scheduler has been committed to the kernel. There should be
464 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
465 list of known rogues that claim support for this but actually corrupt
466 data is believed to be complete, be on the lookout for data
467 corruption. The known rogue list is believed to be complete:
469 o Crucial MX100, M550 drives with MU01 firmware.
470 o Micron M510 and M550 drives with MU01 firmware.
471 o Micron M500 prior to MU07 firmware
472 o Samsung 830, 840, and 850 all firmwares
473 o FCCT M500 all firmwares
475 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
476 with working NCQ TRIM. For Micron branded drives, see your sales rep for
477 updated firmware. Black listed drives will work correctly because these
478 drives work correctly so long as no NCQ TRIMs are sent to them. Given
479 this list is the same as found in Linux, it's believed there are no
480 other rogues in the market place. All other models from the above
483 To be safe, if you are at all concerned, you can quirk each of your
484 drives to prevent NCQ from being sent by setting:
485 kern.cam.ada.X.quirks="0x2"
486 in loader.conf. If the drive requires the 4k sector quirk, set the
490 The FAST_DEPEND build option has been removed and its functionality is
491 now the one true way. The old mkdep(1) style of 'make depend' has
492 been removed. See 20160311 for further details.
495 Resource range types have grown from unsigned long to uintmax_t. All
496 drivers, and anything using libdevinfo, need to be recompiled.
499 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
500 builds. It no longer runs mkdep(1) during 'make depend', and the
501 'make depend' stage can safely be skipped now as it is auto ran
502 when building 'make all' and will generate all SRCS and DPSRCS before
503 building anything else. Dependencies are gathered at compile time with
504 -MF flags kept in separate .depend files per object file. Users should
505 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
509 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
510 kernel modules. Therefore, if you load any kernel modules at boot time,
511 please install the boot loaders after you install the kernel, but before
515 make kernel KERNCONF=YOUR_KERNEL_HERE
516 make -C sys/boot install
517 <reboot in single user>
519 Then follow the usual steps, described in the General Notes section,
523 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
524 see the 20141231 entry below for information about prerequisites and
525 upgrading, if you are not already using clang 3.5.0 or higher.
528 The AIO subsystem is now a standard part of the kernel. The
529 VFS_AIO kernel option and aio.ko kernel module have been removed.
530 Due to stability concerns, asynchronous I/O requests are only
531 permitted on sockets and raw disks by default. To enable
532 asynchronous I/O requests on all file types, set the
533 vfs.aio.enable_unsafe sysctl to a non-zero value.
536 The ELF object manipulation tool objcopy is now provided by the
537 ELF Tool Chain project rather than by GNU binutils. It should be a
538 drop-in replacement, with the addition of arm64 support. The
539 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
540 to obtain the GNU version if necessary.
543 Building ZFS pools on top of zvols is prohibited by default. That
544 feature has never worked safely; it's always been prone to deadlocks.
545 Using a zvol as the backing store for a VM guest's virtual disk will
546 still work, even if the guest is using ZFS. Legacy behavior can be
547 restored by setting vfs.zfs.vol.recursive=1.
550 The NONE and HPN patches has been removed from OpenSSH. They are
551 still available in the security/openssh-portable port.
554 With the addition of ypldap(8), a new _ypldap user is now required
555 during installworld. "mergemaster -p" can be used to add the user
556 prior to installworld, as documented in the handbook.
559 The tftp loader (pxeboot) now uses the option root-path directive. As a
560 consequence it no longer looks for a pxeboot.4th file on the tftp
561 server. Instead it uses the regular /boot infrastructure as with the
565 The code to start recording plug and play data into the modules has
566 been committed. While the old tools will properly build a new kernel,
567 a number of warnings about "unknown metadata record 4" will be produced
568 for an older kldxref. To avoid such warnings, make sure to rebuild
569 the kernel toolchain (or world). Make sure that you have r292078 or
570 later when trying to build 292077 or later before rebuilding.
573 Debug data files are now built by default with 'make buildworld' and
574 installed with 'make installworld'. This facilitates debugging but
575 requires more disk space both during the build and for the installed
576 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
580 r291527 changed the internal interface between the nfsd.ko and
581 nfscommon.ko modules. As such, they must both be upgraded to-gether.
582 __FreeBSD_version has been bumped because of this.
585 Add support for unicode collation strings leads to a change of
586 order of files listed by ls(1) for example. To get back to the old
587 behaviour, set LC_COLLATE environment variable to "C".
589 Databases administrators will need to reindex their databases given
590 collation results will be different.
592 Due to a bug in install(1) it is recommended to remove the ancient
593 locales before running make installworld.
595 rm -rf /usr/share/locale/*
598 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
599 libcrypto.so.7 or libssl.so.7 must be recompiled.
602 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
603 Kernel modules isp_2400_multi and isp_2500_multi were removed and
604 should be replaced with isp_2400 and isp_2500 modules respectively.
607 The build previously allowed using 'make -n' to not recurse into
608 sub-directories while showing what commands would be executed, and
609 'make -n -n' to recursively show commands. Now 'make -n' will recurse
610 and 'make -N' will not.
613 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
614 and etcupdate will now use this file. A custom sendmail.cf is now
615 updated via this mechanism rather than via installworld. If you had
616 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
617 want to remove the exclusion or change it to "always install".
618 /etc/mail/sendmail.cf is now managed the same way regardless of
619 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
620 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
623 Compatibility shims for legacy ATA device names have been removed.
624 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
625 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
626 environment variables, /dev/ad* and /dev/ar* symbolic links.
629 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
630 Please see the 20141231 entry below for information about prerequisites
631 and upgrading, if you are not already using clang 3.5.0 or higher.
634 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
635 and renamed from .symbols to .debug. This reduces the size requirements
636 on the boot partition or file system and provides consistency with
637 userland debug files.
639 When using the supported kernel installation method the
640 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
641 as is done with /boot/kernel.
643 Developers wishing to maintain the historical behavior of installing
644 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
647 The wireless drivers had undergone changes that remove the 'parent
648 interface' from the ifconfig -l output. The rc.d network scripts
649 used to check presence of a parent interface in the list, so old
650 scripts would fail to start wireless networking. Thus, etcupdate(3)
651 or mergemaster(8) run is required after kernel update, to update your
652 rc.d scripts in /etc.
655 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
656 These configurations are now automatically interpreted as
657 'scrub fragment reassemble'.
660 Kernel-loadable modules for the random(4) device are back. To use
661 them, the kernel must have
664 options RANDOM_LOADABLE
666 kldload(8) can then be used to load random_fortuna.ko
667 or random_yarrow.ko. Please note that due to the indirect
668 function calls that the loadable modules need to provide,
669 the build-in variants will be slightly more efficient.
671 The random(4) kernel option RANDOM_DUMMY has been retired due to
672 unpopularity. It was not all that useful anyway.
675 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
676 Control over building the ELF Tool Chain tools is now provided by
677 the WITHOUT_TOOLCHAIN knob.
680 The polarity of Pulse Per Second (PPS) capture events with the
681 uart(4) driver has been corrected. Prior to this change the PPS
682 "assert" event corresponded to the trailing edge of a positive PPS
683 pulse and the "clear" event was the leading edge of the next pulse.
685 As the width of a PPS pulse in a typical GPS receiver is on the
686 order of 1 millisecond, most users will not notice any significant
687 difference with this change.
689 Anyone who has compensated for the historical polarity reversal by
690 configuring a negative offset equal to the pulse width will need to
691 remove that workaround.
694 The default group assigned to /dev/dri entries has been changed
695 from 'wheel' to 'video' with the id of '44'. If you want to have
696 access to the dri devices please add yourself to the video group
699 # pw groupmod video -m $USER
702 The menu.rc and loader.rc files will now be replaced during
703 upgrades. Please migrate local changes to menu.rc.local and
704 loader.rc.local instead.
707 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
708 strings and strip have been removed. The src.conf(5) knob
709 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
712 As ZFS requires more kernel stack pages than is the default on some
713 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
714 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
716 Please consider using 'options KSTACK_PAGES=X' where X is greater
717 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
720 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
721 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
722 default, i.e., they will not contain "::". For example, instead
723 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
724 to have a more specific match, such as different map entries for
725 IPv6:0:0 vs IPv6:0. This change requires that configuration
726 data (including maps, files, classes, custom ruleset, etc.) must
727 use the same format, so make certain such configuration data is
728 upgrading. As a very simple check search for patterns like
729 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
730 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
731 the cf option UseCompressedIPv6Addresses.
734 The default kernel entropy-processing algorithm is now
735 Fortuna, replacing Yarrow.
737 Assuming you have 'device random' in your kernel config
738 file, the configurations allow a kernel option to override
739 this default. You may choose *ONE* of:
741 options RANDOM_YARROW # Legacy /dev/random algorithm.
742 options RANDOM_DUMMY # Blocking-only driver.
744 If you have neither, you get Fortuna. For most people,
745 read no further, Fortuna will give a /dev/random that works
746 like it always used to, and the difference will be irrelevant.
748 If you remove 'device random', you get *NO* kernel-processed
749 entropy at all. This may be acceptable to folks building
750 embedded systems, but has complications. Carry on reading,
751 and it is assumed you know what you need.
753 *PLEASE* read random(4) and random(9) if you are in the
754 habit of tweaking kernel configs, and/or if you are a member
755 of the embedded community, wanting specific and not-usual
756 behaviour from your security subsystems.
758 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
759 random', you will NOT have a functioning /dev/random, and
760 many cryptographic features will not work, including SSH.
761 You may also find strange behaviour from the random(3) set
762 of library functions, in particular sranddev(3), srandomdev(3)
763 and arc4random(3). The reason for this is that the KERN_ARND
764 sysctl only returns entropy if it thinks it has some to
765 share, and with RANDOM_DUMMY or no 'device random' this
769 An additional fix for the issue described in the 20150614 sendmail
770 entry below has been been committed in revision 284717.
773 FreeBSD's old make (fmake) has been removed from the system. It is
774 available as the devel/fmake port or via pkg install fmake.
777 The fix for the issue described in the 20150614 sendmail entry
778 below has been been committed in revision 284436. The work
779 around described in that entry is no longer needed unless the
780 default setting is overridden by a confDH_PARAMETERS configuration
781 setting of '5' or pointing to a 512 bit DH parameter file.
784 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
785 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
786 and devel/kyua to version 0.20+ and adjust any calling code to work
787 with Kyuafile and kyua.
790 The import of openssl to address the FreeBSD-SA-15:10.openssl
791 security advisory includes a change which rejects handshakes
792 with DH parameters below 768 bits. sendmail releases prior
793 to 8.15.2 (not yet released), defaulted to a 512 bit
794 DH parameter setting for client connections. To work around
795 this interoperability, sendmail can be configured to use a
796 2048 bit DH parameter by:
798 1. Edit /etc/mail/`hostname`.mc
799 2. If a setting for confDH_PARAMETERS does not exist or
800 exists and is set to a string beginning with '5',
802 3. If a setting for confDH_PARAMETERS exists and is set to
803 a file path, create a new file with:
804 openssl dhparam -out /path/to/file 2048
805 4. Rebuild the .cf file:
806 cd /etc/mail/; make; make install
808 cd /etc/mail/; make restart
810 A sendmail patch is coming, at which time this file will be
814 Generation of legacy formatted entries have been disabled by default
815 in pwd_mkdb(8), as all base system consumers of the legacy formatted
816 entries were converted to use the new format by default when the new,
817 machine independent format have been added and supported since FreeBSD
820 Please see the pwd_mkdb(8) manual page for further details.
823 Clang and llvm have been upgraded to 3.6.1 release. Please see the
824 20141231 entry below for information about prerequisites and upgrading,
825 if you are not already using 3.5.0 or higher.
828 TI platform code switched to using vendor DTS files and this update
829 may break existing systems running on Beaglebone, Beaglebone Black,
832 - dtb files should be regenerated/reinstalled. Filenames are the
833 same but content is different now
834 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
835 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
836 addressing scheme is now pin 25 on /dev/gpioc3.
837 - Pandaboard: /etc/ttys should be updated, serial console device is
838 now /dev/ttyu2, not /dev/ttyu0
841 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
842 If you need the GNU extension from groff soelim(1), install groff
843 from package: pkg install groff, or via ports: textproc/groff.
846 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
847 defined in symlink(7); previously symlinks were silently ignored.
850 The const qualifier has been removed from iconv(3) to comply with
851 POSIX. The ports tree is aware of this from r384038 onwards.
854 Libraries specified by LIBADD in Makefiles must have a corresponding
855 DPADD_<lib> variable to ensure correct dependencies. This is now
856 enforced in src.libnames.mk.
859 From legacy ata(4) driver was removed support for SATA controllers
860 supported by more functional drivers ahci(4), siis(4) and mvs(4).
861 Kernel modules ataahci and ataadaptec were removed completely,
862 replaced by ahci and mvs modules respectively.
865 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
866 the 20141231 entry below for information about prerequisites and
867 upgrading, if you are not already using 3.5.0 or higher.
870 The 32-bit PowerPC kernel has been changed to a position-independent
871 executable. This can only be booted with a version of loader(8)
872 newer than January 31, 2015, so make sure to update both world and
873 kernel before rebooting.
876 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
877 but before r278950, the RNG was not seeded properly. Immediately
878 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
879 ssh keys or openssl keys) that were generated w/ a kernel from that
880 range. This does not affect programs that directly used /dev/random
881 or /dev/urandom. All userland uses of arc4random(3) are affected.
884 The autofs(4) ABI was changed in order to restore binary compatibility
885 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
889 The powerpc64 kernel has been changed to a position-independent
890 executable. This can only be booted with a new version of loader(8),
891 so make sure to update both world and kernel before rebooting.
894 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
895 only release, no new features have been added. Please see the 20141231
896 entry below for information about prerequisites and upgrading, if you
897 are not already using 3.5.0.
900 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
901 taken from the ELF Tool Chain project rather than GNU binutils. They
902 should be drop-in replacements, with the addition of arm64 support.
903 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
904 binutils tools, if necessary. See 20150805 for updated information.
907 The default Unbound configuration now enables remote control
908 using a local socket. Users who have already enabled the
909 local_unbound service should regenerate their configuration
910 by running "service local_unbound setup" as root.
913 The GNU texinfo and GNU info pages have been removed.
914 To be able to view GNU info pages please install texinfo from ports.
917 Clang, llvm and lldb have been upgraded to 3.5.0 release.
919 As of this release, a prerequisite for building clang, llvm and lldb is
920 a C++11 capable compiler and C++11 standard library. This means that to
921 be able to successfully build the cross-tools stage of buildworld, with
922 clang as the bootstrap compiler, your system compiler or cross compiler
923 should either be clang 3.3 or later, or gcc 4.8 or later, and your
924 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
927 On any standard FreeBSD 10.x or 11.x installation, where clang and
928 libc++ are on by default (that is, on x86 or arm), this should work out
931 On 9.x installations where clang is enabled by default, e.g. on x86 and
932 powerpc, libc++ will not be enabled by default, so libc++ should be
933 built (with clang) and installed first. If both clang and libc++ are
934 missing, build clang first, then use it to build libc++.
936 On 8.x and earlier installations, upgrade to 9.x first, and then follow
937 the instructions for 9.x above.
939 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
940 default, and do not build clang.
942 Many embedded systems are resource constrained, and will not be able to
943 build clang in a reasonable time, or in some cases at all. In those
944 cases, cross building bootable systems on amd64 is a workaround.
946 This new version of clang introduces a number of new warnings, of which
947 the following are most likely to appear:
951 This warns in two cases, for both C and C++:
952 * When the code is trying to take the absolute value of an unsigned
953 quantity, which is effectively a no-op, and almost never what was
954 intended. The code should be fixed, if at all possible. If you are
955 sure that the unsigned quantity can be safely cast to signed, without
956 loss of information or undefined behavior, you can add an explicit
957 cast, or disable the warning.
959 * When the code is trying to take an absolute value, but the called
960 abs() variant is for the wrong type, which can lead to truncation.
961 If you want to disable the warning instead of fixing the code, please
962 make sure that truncation will not occur, or it might lead to unwanted
965 -Wtautological-undefined-compare and
966 -Wundefined-bool-conversion
968 These warn when C++ code is trying to compare 'this' against NULL, while
969 'this' should never be NULL in well-defined C++ code. However, there is
970 some legacy (pre C++11) code out there, which actively abuses this
971 feature, which was less strictly defined in previous C++ versions.
973 Squid and openjdk do this, for example. The warning can be turned off
974 for C++98 and earlier, but compiling the code in C++11 mode might result
975 in unexpected behavior; for example, the parts of the program that are
976 unreachable could be optimized away.
979 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
980 kernel sources have been removed. The .h files remain, since some
981 utilities include them. This will need to be fixed later.
982 If "mount -t oldnfs ..." is attempted, it will fail.
983 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
984 the utilities will report errors.
987 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
988 directories to top level SUBDIR variable when their parent
989 directory is included in LOCAL_DIRS. Users with build systems with
990 such hierarchies and without SUBDIR entries in the parent
991 directory Makefiles should add them or add the directories to
995 faith(4) and faithd(8) have been removed from the base system. Faith
996 has been obsolete for a very long time.
999 vt(4), the new console driver, is enabled by default. It brings
1000 support for Unicode and double-width characters, as well as
1001 support for UEFI and integration with the KMS kernel video
1004 You may need to update your console settings in /etc/rc.conf,
1005 most probably the keymap. During boot, /etc/rc.d/syscons will
1006 indicate what you need to do.
1008 vt(4) still has issues and lacks some features compared to
1009 syscons(4). See the wiki for up-to-date information:
1010 https://wiki.freebsd.org/Newcons
1012 If you want to keep using syscons(4), you can do so by adding
1013 the following line to /boot/loader.conf:
1017 pjdfstest has been integrated into kyua as an opt-in test suite.
1018 Please see share/doc/pjdfstest/README for more details on how to
1022 gperf has been removed from the base system for architectures
1023 that use clang. Ports that require gperf will obtain it from the
1027 pjdfstest has been moved from tools/regression/pjdfstest to
1031 At svn r271982, The default linux compat kernel ABI has been adjusted
1032 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1033 update. If you wish to continue using the linux-f10 compat ports,
1034 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1035 encouraged to update their linux-compat packages to linux-c6 during
1036 their next update cycle.
1039 The ofwfb driver, used to provide a graphics console on PowerPC when
1040 using vt(4), no longer allows mmap() of all physical memory. This
1041 will prevent Xorg on PowerPC with some ATI graphics cards from
1042 initializing properly unless x11-servers/xorg-server is updated to
1046 The xdev targets have been converted to using TARGET and
1047 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1050 The default unbound configuration has been modified to address
1051 issues with reverse lookups on networks that use private
1052 address ranges. If you use the local_unbound service, run
1053 "service local_unbound setup" as root to regenerate your
1054 configuration, then "service local_unbound reload" to load the
1058 The GNU texinfo and GNU info pages are not built and installed
1059 anymore, WITH_INFO knob has been added to allow to built and install
1061 UPDATE: see 20150102 entry on texinfo's removal
1064 The GNU readline library is now an INTERNALLIB - that is, it is
1065 statically linked into consumers (GDB and variants) in the base
1066 system, and the shared library is no longer installed. The
1067 devel/readline port is available for third party software that
1071 The Itanium architecture (ia64) has been removed from the list of
1072 known architectures. This is the first step in the removal of the
1076 Commit r268115 has added NFSv4.1 server support, merged from
1077 projects/nfsv4.1-server. Since this includes changes to the
1078 internal interfaces between the NFS related modules, a full
1079 build of the kernel and modules will be necessary.
1080 __FreeBSD_version has been bumped.
1083 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1084 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1085 which differs from the behaviour controlled by this knob.)
1088 Maximal length of the serial number in CTL was increased from 16 to
1089 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1090 and ctld, need to be rebuilt to work with a new kernel.
1093 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1094 1 respectively to match the upstream numbers. They were out of
1095 sync because, when they were originally added to FreeBSD, the
1096 upstream versions were not respected. These libraries are private
1097 and not yet built by default, so renumbering them should be a
1098 non-issue. However, unclean source trees will yield broken test
1099 programs once the operator executes "make delete-old-libs" after a
1100 "make installworld".
1102 Additionally, the atf-sh binary was made private by moving it into
1103 /usr/libexec/. Already-built shell test programs will keep the
1104 path to the old binary so they will break after "make delete-old"
1107 If you are using WITH_TESTS=yes (not the default), wipe the object
1108 tree and rebuild from scratch to prevent spurious test failures.
1109 This is only needed once: the misnumbered libraries and misplaced
1110 binaries have been added to OptionalObsoleteFiles.inc so they will
1111 be removed during a clean upgrade.
1114 Clang and llvm have been upgraded to 3.4.1 release.
1117 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1118 be removed to avoid issues in the future (and has been added to
1122 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1123 past, it affected all builds that used the bsd.*.mk files. The old
1124 behavior was a bug, but people may have relied upon it. To get this
1125 behavior back, you can .include /etc/src.conf from /etc/make.conf
1126 (which is still global and isn't changed). This also changes the
1127 behavior of incremental builds inside the tree of individual
1128 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1129 Although this has survived make universe and some upgrade scenarios,
1130 other upgrade scenarios may have broken. At least one form of
1131 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1132 as well... In cases where MAKESYSPATH isn't working with this
1133 setting, you'll need to set it to the full path to your tree.
1135 One side effect of all this cleaning up is that bsd.compiler.mk
1136 is no longer implicitly included by bsd.own.mk. If you wish to
1137 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1141 The lindev device has been removed since /dev/full has been made a
1142 standard device. __FreeBSD_version has been bumped.
1145 The knob WITHOUT_VI was added to the base system, which controls
1146 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1147 in order to reorder files share/termcap and didn't build ex(1) as a
1148 build tool, so building/installing with WITH_VI is highly advised for
1149 build hosts for older releases.
1151 This issue has been fixed in stable/9 and stable/10 in r277022 and
1152 r276991, respectively.
1155 The YES_HESIOD knob has been removed. It has been obsolete for
1156 a decade. Please move to using WITH_HESIOD instead or your builds
1157 will silently lack HESIOD.
1160 The uart(4) driver has been changed with respect to its handling
1161 of the low-level console. Previously the uart(4) driver prevented
1162 any process from changing the baudrate or the CLOCAL and HUPCL
1163 control flags. By removing the restrictions, operators can make
1164 changes to the serial console port without having to reboot.
1165 However, when getty(8) is started on the serial device that is
1166 associated with the low-level console, a misconfigured terminal
1167 line in /etc/ttys will now have a real impact.
1168 Before upgrading the kernel, make sure that /etc/ttys has the
1169 serial console device configured as 3wire without baudrate to
1170 preserve the previous behaviour. E.g:
1171 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1174 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1175 to improve performance. To re-enable it, if needed, run rpcbind
1176 with command line option -W.
1179 Switched back to the GPL dtc compiler due to updates in the upstream
1180 dts files not being supported by the BSDL dtc compiler. You will need
1181 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1182 may result while building dtb files during a kernel build if you fail
1183 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1186 Clang and llvm have been upgraded to 3.4 release.
1189 The nve(4) driver has been removed. Please use the nfe(4) driver
1190 for NVIDIA nForce MCP Ethernet adapters instead.
1193 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1194 This could cause certain C++ applications using shared libraries built
1195 against the previous version of libc++ to crash. The incompatibility
1196 has now been fixed, but any C++ applications or shared libraries built
1197 between r261283 and r261801 should be recompiled.
1200 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1201 capability mode support. Please note that enabling the feature in
1202 kernel is still highly recommended.
1205 OpenSSH is now built with sandbox support, and will use sandbox as
1206 the default privilege separation method. This requires Capsicum
1207 capability mode support in kernel.
1210 The libelf and libdwarf libraries have been updated to newer
1211 versions from upstream. Shared library version numbers for
1212 these two libraries were bumped. Any ports or binaries
1213 requiring these two libraries should be recompiled.
1214 __FreeBSD_version is bumped to 1100006.
1217 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1218 instead of providing an explicit one, this would prevent such
1219 Makefile from providing its own Kyuafile in the future during
1220 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1221 intervention is needed to clean an objdir if you use NO_CLEAN:
1222 # find /usr/obj -name Kyuafile | xargs rm -f
1225 The behavior of gss_pseudo_random() for the krb5 mechanism
1226 has changed, for applications requesting a longer random string
1227 than produced by the underlying enctype's pseudo-random() function.
1228 In particular, the random string produced from a session key of
1229 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1230 be different at the 17th octet and later, after this change.
1231 The counter used in the PRF+ construction is now encoded as a
1232 big-endian integer in accordance with RFC 4402.
1233 __FreeBSD_version is bumped to 1100004.
1236 The WITHOUT_ATF build knob has been removed and its functionality
1237 has been subsumed into the more generic WITHOUT_TESTS. If you were
1238 using the former to disable the build of the ATF libraries, you
1239 should change your settings to use the latter.
1242 The default version of mtree is nmtree which is obtained from
1243 NetBSD. The output is generally the same, but may vary
1244 slightly. If you found you need identical output adding
1245 "-F freebsd9" to the command line should do the trick. For the
1246 time being, the old mtree is available as fmtree.
1249 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1250 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1251 1.1.4_8 and verify bsdyml not linked in, before running "make
1253 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1255 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1258 The stable/10 branch has been created in subversion from head
1262 The rc.d/jail script has been updated to support jail(8)
1263 configuration file. The "jail_<jname>_*" rc.conf(5) variables
1264 for per-jail configuration are automatically converted to
1265 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
1266 This is transparently backward compatible. See below about some
1267 incompatibilities and rc.conf(5) manual page for more details.
1269 These variables are now deprecated in favor of jail(8) configuration
1270 file. One can use "rc.d/jail config <jname>" command to generate
1271 a jail(8) configuration file in /var/run/jail.<jname>.conf without
1272 running the jail(8) utility. The default pathname of the
1273 configuration file is /etc/jail.conf and can be specified by
1274 using $jail_conf or $jail_<jname>_conf variables.
1276 Please note that jail_devfs_ruleset accepts an integer at
1277 this moment. Please consider to rewrite the ruleset name
1281 BIND has been removed from the base system. If all you need
1282 is a local resolver, simply enable and start the local_unbound
1283 service instead. Otherwise, several versions of BIND are
1284 available in the ports tree. The dns/bind99 port is one example.
1286 With this change, nslookup(1) and dig(1) are no longer in the base
1287 system. Users should instead use host(1) and drill(1) which are
1288 in the base system. Alternatively, nslookup and dig can
1289 be obtained by installing the dns/bind-tools port.
1292 With the addition of unbound(8), a new unbound user is now
1293 required during installworld. "mergemaster -p" can be used to
1294 add the user prior to installworld, as documented in the handbook.
1297 OpenSSH is now built with DNSSEC support, and will by default
1298 silently trust signed SSHFP records. This can be controlled with
1299 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1300 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1303 The GNU Compiler Collection and C++ standard library (libstdc++)
1304 are no longer built by default on platforms where clang is the system
1305 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1306 options in src.conf.
1309 The PROCDESC kernel option is now part of the GENERIC kernel
1310 configuration and is required for the rwhod(8) to work.
1311 If you are using custom kernel configuration, you should include
1315 The API and ABI related to the Capsicum framework was modified
1316 in backward incompatible way. The userland libraries and programs
1317 have to be recompiled to work with the new kernel. This includes the
1318 following libraries and programs, but the whole buildworld is
1319 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1320 kdump, procstat, rwho, rwhod, uniq.
1323 AES-NI intrinsic support has been added to gcc. The AES-NI module
1324 has been updated to use this support. A new gcc is required to build
1325 the aesni module on both i386 and amd64.
1328 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1329 Thus "device padlock_rng" and "device rdrand_rng" should be
1330 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1333 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1334 enables just the iconv* functionality and is now on by default.
1335 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1336 compatibility. Set WITHOUT_ICONV to build the old way.
1337 If you have been using WITH_ICONV before, you will very likely
1338 need to turn on WITH_LIBICONV_COMPAT.
1341 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1342 Illumos origin, including ZFS. If you have INVARIANTS in your
1343 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1345 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1346 locks if WITNESS option was set. Because that generated a lot of
1347 witness(9) reports and all of them were believed to be false
1348 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1349 can be used to achieve the previous behavior.
1352 Timer values in IPv6 data structures now use time_uptime instead
1353 of time_second. Although this is not a user-visible functional
1354 change, userland utilities which directly use them---ndp(8),
1355 rtadvd(8), and rtsold(8) in the base system---need to be updated
1356 to r253970 or later.
1359 find -delete can now delete the pathnames given as arguments,
1360 instead of only files found below them or if the pathname did
1361 not contain any slashes. Formerly, the following error message
1364 find: -delete: <path>: relative path potentially not safe
1366 Deleting the pathnames given as arguments can be prevented
1367 without error messages using -mindepth 1 or by changing
1368 directory and passing "." as argument to find. This works in the
1369 old as well as the new version of find.
1372 Behavior of devfs rules path matching has been changed.
1373 Pattern is now always matched against fully qualified devfs
1374 path and slash characters must be explicitly matched by
1375 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1376 subdirectories must be reviewed.
1379 The default ARM ABI has changed to the ARM EABI. The old ABI is
1380 incompatible with the ARM EABI and all programs and modules will
1381 need to be rebuilt to work with a new kernel.
1383 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1385 NOTE: Support for the old ABI will be removed in the future and
1386 users are advised to upgrade.
1389 pkg_install has been disconnected from the build if you really need it
1390 you should add WITH_PKGTOOLS in your src.conf(5).
1393 Most of network statistics structures were changed to be able
1394 keep 64-bits counters. Thus all tools, that work with networking
1395 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1398 Fix a bug that allowed a tracing process (e.g. gdb) to write
1399 to a memory-mapped file in the traced process's address space
1400 even if neither the traced process nor the tracing process had
1401 write access to that file.
1404 CVS has been removed from the base system. An exact copy
1405 of the code is available from the devel/cvs port.
1408 Some people report the following error after the switch to bmake:
1410 make: illegal option -- J
1411 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1413 *** [buildworld] Error code 2
1415 this likely due to an old instance of make in
1416 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1417 which src/Makefile will use that blindly, if it exists, so if
1418 you see the above error:
1420 rm -rf `make -V MAKEPATH`
1425 Use bmake by default.
1426 Whereas before one could choose to build with bmake via
1427 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1428 make. The goal is to remove these knobs for 10-RELEASE.
1430 It is worth noting that bmake (like gmake) treats the command
1431 line as the unit of failure, rather than statements within the
1432 command line. Thus '(cd some/where && dosomething)' is safer
1433 than 'cd some/where; dosomething'. The '()' allows consistent
1434 behavior in parallel build.
1437 Fix a bug that allows NFS clients to issue READDIR on files.
1440 The WITHOUT_IDEA option has been removed because
1441 the IDEA patent expired.
1444 The sysctl which controls TRIM support under ZFS has been renamed
1445 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1449 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1450 rather than creating it's own in the temporary directory in
1451 order allow access to bootstrapped versions of tools such as
1452 install and mtree. When upgrading from version of FreeBSD where
1453 the install command does not support -l, you will need to
1454 install a new mergemaster command if mergemaster -p is required.
1455 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1459 Legacy ATA stack, disabled and replaced by new CAM-based one since
1460 FreeBSD 9.0, completely removed from the sources. Kernel modules
1461 atadisk and atapi*, user-level tools atacontrol and burncd are
1462 removed. Kernel option `options ATA_CAM` is now permanently enabled
1466 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1467 and socketpair(2). Software, in particular Kerberos, may
1468 automatically detect and use these during building. The resulting
1469 binaries will not work on older kernels.
1472 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1473 information, see the respective 20130304 entry).
1476 Recent commits to callout(9) changed the size of struct callout,
1477 so the KBI is probably heavily disturbed. Also, some functions
1478 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1479 by macros. Every kernel module using it won't load, so rebuild
1482 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1483 but does not initialize by default (because of the new CTL_DISABLE
1484 option) to save memory. To re-enable it, remove the CTL_DISABLE
1485 option from the kernel config file or set kern.cam.ctl.disable=0
1486 in /boot/loader.conf.
1489 The ctl device has been disabled in GENERIC for i386 and amd64.
1490 This was done due to the extra memory being allocated at system
1491 initialisation time by the ctl driver which was only used if
1492 a CAM target device was created. This makes a FreeBSD system
1493 unusable on 128MB or less of RAM.
1496 A new compression method (lz4) has been merged to -HEAD. Please
1497 refer to zpool-features(7) for more information.
1499 Please refer to the "ZFS notes" section of this file for information
1500 on upgrading boot ZFS pools.
1503 A BSD-licensed patch(1) variant has been added and is installed
1504 as bsdpatch, being the GNU version the default patch.
1505 To inverse the logic and use the BSD-licensed one as default,
1506 while having the GNU version installed as gnupatch, rebuild
1507 and install world with the WITH_BSD_PATCH knob set.
1510 Due to the use of the new -l option to install(1) during build
1511 and install, you must take care not to directly set the INSTALL
1512 make variable in your /etc/make.conf, /etc/src.conf, or on the
1513 command line. If you wish to use the -C flag for all installs
1514 you may be able to add INSTALL+=-C to /etc/make.conf or
1518 The install(1) option -M has changed meaning and now takes an
1519 argument that is a file or path to append logs to. In the
1520 unlikely event that -M was the last option on the command line
1521 and the command line contained at least two files and a target
1522 directory the first file will have logs appended to it. The -M
1523 option served little practical purpose in the last decade so its
1524 use is expected to be extremely rare.
1527 After switching to Clang as the default compiler some users of ZFS
1528 on i386 systems started to experience stack overflow kernel panics.
1529 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1532 GEOM_LABEL now mangles label names read from file system metadata.
1533 Mangling affect labels containing spaces, non-printable characters,
1534 '%' or '"'. Device names in /etc/fstab and other places may need to
1538 By default, only the 10 most recent kernel dumps will be saved. To
1539 restore the previous behaviour (no limit on the number of kernel dumps
1540 stored in the dump directory) add the following line to /etc/rc.conf:
1545 With the addition of auditdistd(8), a new auditdistd user is now
1546 required during installworld. "mergemaster -p" can be used to
1547 add the user prior to installworld, as documented in the handbook.
1550 The sin6_scope_id member variable in struct sockaddr_in6 is now
1551 filled by the kernel before passing the structure to the userland via
1552 sysctl or routing socket. This means the KAME-specific embedded scope
1553 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1554 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1555 __FreeBSD_version is bumped to 1000025.
1558 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1559 This means that the world and kernel will be compiled with clang
1560 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1561 and /usr/bin/cpp. To disable this behavior and revert to building
1562 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1563 of current may need to bootstrap WITHOUT_CLANG first if the clang
1564 build fails (its compatibility window doesn't extend to the 9 stable
1568 The IPFIREWALL_FORWARD kernel option has been removed. Its
1569 functionality now turned on by default.
1572 The ZERO_COPY_SOCKET kernel option has been removed and
1573 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1574 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1575 mechanism which is not safe and may result in kernel crashes.
1576 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1577 driver supports disposeable external page sized mbuf storage.
1578 Proper replacements for both zero-copy mechanisms are under
1579 consideration and will eventually lead to complete removal
1580 of the two kernel options.
1583 The IPv4 network stack has been converted to network byte
1584 order. The following modules need to be recompiled together
1585 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1586 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1589 Support for non-MPSAFE filesystems was removed from VFS. The
1590 VFS_VERSION was bumped, all filesystem modules shall be
1594 All the non-MPSAFE filesystems have been disconnected from
1595 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1596 portalfs, smbfs, xfs.
1599 The interface cloning API and ABI has changed. The following
1600 modules need to be recompiled together with kernel:
1601 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1602 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1603 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1606 The sdhci driver was split in two parts: sdhci (generic SD Host
1607 Controller logic) and sdhci_pci (actual hardware driver).
1608 No kernel config modifications are required, but if you
1609 load sdhc as a module you must switch to sdhci_pci instead.
1612 Import the FUSE kernel and userland support into base system.
1615 The GNU sort(1) program has been removed since the BSD-licensed
1616 sort(1) has been the default for quite some time and no serious
1617 problems have been reported. The corresponding WITH_GNU_SORT
1621 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1622 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1626 The net80211(4) ABI has been changed to allow for improved driver
1627 PS-POLL and power-save support. All wireless drivers need to be
1628 recompiled to work with the new kernel.
1631 The random(4) support for the VIA hardware random number
1632 generator (`PADLOCK') is no longer enabled unconditionally.
1633 Add the padlock_rng device in the custom kernel config if
1634 needed. The GENERIC kernels on i386 and amd64 do include the
1635 device, so the change only affects the custom kernel
1639 The pf(4) packet filter ABI has been changed. pfctl(8) and
1640 snmp_pf module need to be recompiled to work with new kernel.
1643 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1644 to -HEAD. Pools that have empty_bpobj in active state can not be
1645 imported read-write with ZFS implementations that do not support
1646 this feature. For more information read the zpool-features(5)
1650 The sparc64 ZFS loader has been changed to no longer try to auto-
1651 detect ZFS providers based on diskN aliases but now requires these
1652 to be explicitly listed in the OFW boot-device environment variable.
1655 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1656 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1657 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1660 The following sysctls and tunables have been renamed for consistency
1661 with other variables:
1662 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1663 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1666 The sort utility has been replaced with BSD sort. For now, GNU sort
1667 is also available as "gnusort" or the default can be set back to
1668 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1669 installed as "bsdsort".
1672 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1673 Starting with this version the old system of ZFS pool versioning
1674 is superseded by "feature flags". This concept enables forward
1675 compatibility against certain future changes in functionality of ZFS
1676 pools. The first read-only compatible "feature flag" for ZFS pools
1677 is named "com.delphix:async_destroy". For more information
1678 read the new zpool-features(5) manual page.
1679 Please refer to the "ZFS notes" section of this file for information
1680 on upgrading boot ZFS pools.
1683 The malloc(3) implementation embedded in libc now uses sources imported
1684 as contrib/jemalloc. The most disruptive API change is to
1685 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1686 delete it prior to installworld, and optionally re-create it using the
1687 new format after rebooting. See malloc.conf(5) for details
1688 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1692 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1693 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1694 now spelled mips. This is to aid compatibility with third-party
1695 software that expects this naming scheme in uname(3). Little-endian
1696 settings are unchanged. If you are updating a big-endian mips64 machine
1697 from before this change, you may need to set MACHINE_ARCH=mips64 in
1698 your environment before the new build system will recognize your machine.
1701 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1705 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1706 nullfs(5) did not pass through all behaviours to the underlying layer,
1707 as a result if we bound to a socket on the lower layer we could connect
1708 only to the lower path; if we bound to the upper layer we could connect
1709 only to the upper path. The new behavior is one can connect to both the
1710 lower and the upper paths regardless what layer path one binds to.
1713 The getifaddrs upgrade path broken with 20111215 has been restored.
1714 If you have upgraded in between 20111215 and 20120209 you need to
1715 recompile libc again with your kernel. You still need to recompile
1716 world to be able to configure CARP but this restriction already
1717 comes from 20111215.
1720 The set_rcvar() function has been removed from /etc/rc.subr. All
1721 base and ports rc.d scripts have been updated, so if you have a
1722 port installed with a script in /usr/local/etc/rc.d you can either
1723 hand-edit the rcvar= line, or reinstall the port.
1725 An easy way to handle the mass-update of /etc/rc.d:
1726 rm /etc/rc.d/* && mergemaster -i
1729 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1730 on the current CPU and prevents other threads from running.
1731 This behavior can be reverted using the kern.stop_scheduler_on_panic
1733 The new behavior can be incompatible with kern.sync_on_panic.
1736 The carp(4) facility has been changed significantly. Configuration
1737 of the CARP protocol via ifconfig(8) has changed, as well as format
1738 of CARP events submitted to devd(8) has changed. See manual pages
1739 for more information. The arpbalance feature of carp(4) is currently
1740 not supported anymore.
1742 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1743 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1744 need to be recompiled.
1747 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1751 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1752 explicitely support non-MPSAFE filesystems.
1753 It is on by default for all supported platform at this present
1757 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1758 i386 and pc98 GENERIC kernel configuration files.
1761 sysinstall has been removed
1764 The stable/9 branch created in subversion. This corresponds to the
1765 RELENG_9 branch in CVS.
1771 Avoid using make -j when upgrading. While generally safe, there are
1772 sometimes problems using -j to upgrade. If your upgrade fails with
1773 -j, please try again without -j. From time to time in the past there
1774 have been problems using -j with buildworld and/or installworld. This
1775 is especially true when upgrading between "distant" versions (eg one
1776 that cross a major release boundary or several minor releases, or when
1777 several months have passed on the -current branch).
1779 Sometimes, obscure build problems are the result of environment
1780 poisoning. This can happen because the make utility reads its
1781 environment when searching for values for global variables. To run
1782 your build attempts in an "environmental clean room", prefix all make
1783 commands with 'env -i '. See the env(1) manual page for more details.
1785 When upgrading from one major version to another it is generally best to
1786 upgrade to the latest code in the currently installed branch first, then
1787 do an upgrade to the new branch. This is the best-tested upgrade path,
1788 and has the highest probability of being successful. Please try this
1789 approach if you encounter problems with a major version upgrade. Since
1790 the stable 4.x branch point, one has generally been able to upgade from
1791 anywhere in the most recent stable branch to head / current (or even the
1792 last couple of stable branches). See the top of this file when there's
1795 When upgrading a live system, having a root shell around before
1796 installing anything can help undo problems. Not having a root shell
1797 around can lead to problems if pam has changed too much from your
1798 starting point to allow continued authentication after the upgrade.
1800 This file should be read as a log of events. When a later event changes
1801 information of a prior event, the prior event should not be deleted.
1802 Instead, a pointer to the entry with the new information should be
1803 placed in the old entry. Readers of this file should also sanity check
1804 older entries before relying on them blindly. Authors of new entries
1805 should write them with this in mind.
1809 When upgrading the boot ZFS pool to a new version, always follow
1812 1.) recompile and reinstall the ZFS boot loader and boot block
1813 (this is part of "make buildworld" and "make installworld")
1815 2.) update the ZFS boot block on your boot drive
1817 The following example updates the ZFS boot block on the first
1818 partition (freebsd-boot) of a GPT partitioned drive ada0:
1819 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1821 Non-boot pools do not need these updates.
1825 If you are updating from a prior version of FreeBSD (even one just
1826 a few days old), you should follow this procedure. It is the most
1827 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1829 make kernel-toolchain
1830 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1831 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1833 To test a kernel once
1834 ---------------------
1835 If you just want to boot a kernel once (because you are not sure
1836 if it works, or if you want to boot a known bad kernel to provide
1837 debugging information) run
1838 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1839 nextboot -k testkernel
1841 To just build a kernel when you know that it won't mess you up
1842 --------------------------------------------------------------
1843 This assumes you are already running a CURRENT system. Replace
1844 ${arch} with the architecture of your machine (e.g. "i386",
1845 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1847 cd src/sys/${arch}/conf
1848 config KERNEL_NAME_HERE
1849 cd ../compile/KERNEL_NAME_HERE
1854 If this fails, go to the "To build a kernel" section.
1856 To rebuild everything and install it on the current system.
1857 -----------------------------------------------------------
1858 # Note: sometimes if you are running current you gotta do more than
1859 # is listed here if you are upgrading from a really old current.
1861 <make sure you have good level 0 dumps>
1863 make kernel KERNCONF=YOUR_KERNEL_HERE
1865 <reboot in single user> [3]
1872 To cross-install current onto a separate partition
1873 --------------------------------------------------
1874 # In this approach we use a separate partition to hold
1875 # current's root, 'usr', and 'var' directories. A partition
1876 # holding "/", "/usr" and "/var" should be about 2GB in
1879 <make sure you have good level 0 dumps>
1882 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1883 <maybe newfs current's root partition>
1884 <mount current's root partition on directory ${CURRENT_ROOT}>
1885 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1886 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1887 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1888 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1889 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1890 <reboot into current>
1891 <do a "native" rebuild/install as described in the previous section>
1892 <maybe install compatibility libraries from ports/misc/compat*>
1896 To upgrade in-place from stable to current
1897 ----------------------------------------------
1898 <make sure you have good level 0 dumps>
1900 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1902 <reboot in single user> [3]
1909 Make sure that you've read the UPDATING file to understand the
1910 tweaks to various things you need. At this point in the life
1911 cycle of current, things change often and you are on your own
1912 to cope. The defaults can also change, so please read ALL of
1913 the UPDATING entries.
1915 Also, if you are tracking -current, you must be subscribed to
1916 freebsd-current@freebsd.org. Make sure that before you update
1917 your sources that you have read and understood all the recent
1918 messages there. If in doubt, please track -stable which has
1919 much fewer pitfalls.
1921 [1] If you have third party modules, such as vmware, you
1922 should disable them at this point so they don't crash your
1925 [3] From the bootblocks, boot -s, and then do
1930 adjkerntz -i # if CMOS is wall time
1931 Also, when doing a major release upgrade, it is required that
1932 you boot into single user mode to do the installworld.
1934 [4] Note: This step is non-optional. Failure to do this step
1935 can result in a significant reduction in the functionality of the
1936 system. Attempting to do it by hand is not recommended and those
1937 that pursue this avenue should read this file carefully, as well
1938 as the archives of freebsd-current and freebsd-hackers mailing lists
1939 for potential gotchas. The -U option is also useful to consider.
1940 See mergemaster(8) for more information.
1942 [5] Usually this step is a noop. However, from time to time
1943 you may need to do this if you get unknown user in the following
1944 step. It never hurts to do it all the time. You may need to
1945 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1946 install) after the buildworld before this step if you last updated
1947 from current before 20130425 or from -stable before 20130430.
1949 [6] This only deletes old files and directories. Old libraries
1950 can be deleted by "make delete-old-libs", but you have to make
1951 sure that no program is using those libraries anymore.
1953 [8] In order to have a kernel that can run the 4.x binaries needed to
1954 do an installworld, you must include the COMPAT_FREEBSD4 option in
1955 your kernel. Failure to do so may leave you with a system that is
1956 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1957 required to run the 5.x binaries on more recent kernels. And so on
1958 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1960 Make sure that you merge any new devices from GENERIC since the
1961 last time you updated your kernel config file.
1963 [9] When checking out sources, you must include the -P flag to have
1964 cvs prune empty directories.
1966 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1967 "?=" instead of the "=" assignment operator, so that buildworld can
1968 override the CPUTYPE if it needs to.
1970 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1971 not on the command line, or in /etc/make.conf. buildworld will
1972 warn if it is improperly defined.
1975 This file contains a list, in reverse chronological order, of major
1976 breakages in tracking -current. It is not guaranteed to be a complete
1977 list of such breakages, and only contains entries since September 23, 2011.
1978 If you need to see UPDATING entries from before that date, you will need
1979 to fetch an UPDATING file from an older FreeBSD release.
1981 Copyright information:
1983 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1985 Redistribution, publication, translation and use, with or without
1986 modification, in full or in part, in any form or format of this
1987 document are permitted without further permission from the author.
1989 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1990 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1991 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1992 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1993 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1994 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1995 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1996 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1997 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1998 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1999 POSSIBILITY OF SUCH DAMAGE.
2001 Contact Warner Losh if you have any questions about your use of