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/current-stable.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 PowerPC users must update loader(8) by rebuilding world before
56 installing a new kernel, as the protocol connecting them has
57 changed. Without the update, loader metadata will not be passed
58 successfully to the kernel and users will have to enter their
59 root partition at the kernel mountroot prompt to continue booting.
60 Newer versions of loader can boot old kernels without issue.
63 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
64 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
65 to WITH/OUT_LOADER_GELI.
68 The naive and non-compliant support of posix_fallocate(2) in ZFS
69 has been removed as of r325320. The system call now returns EINVAL
70 when used on a ZFS file. Although the new behavior complies with the
71 standard, some consumers are not prepared to cope with it.
72 One known victim is lld prior to r325420.
75 Building in a FreeBSD src checkout will automatically create object
76 directories now rather than store files in the current directory if
77 'make obj' was not ran. Calling 'make obj' is no longer necessary.
78 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
79 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
83 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
84 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
85 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
86 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
87 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
88 The UNIFIED_OBJDIR option is a transitional feature that will be
89 removed for 12.0 release; please migrate to the new format for any
90 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
91 than hardcoding paths.
94 The native-xtools target no longer installs the files by default to the
95 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
96 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
99 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
100 options are changing from controlling the build if defined / undefined
101 to controlling the build with explicit 'yes' or 'no' values. They will
102 shift to WITH/WITHOUT options to match other options in the system.
105 libstand has turned into a private library for sys/boot use only.
106 It is no longer supported as a public interface outside of sys/boot.
109 The arm port has split armv6 into armv6 and armv7. armv7 is now
110 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
111 and are running a kernel from before r324363, you will need to add
112 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
115 When building multiple kernels using KERNCONF, non-existent KERNCONF
116 files will produce an error and buildkernel will fail. Previously
117 missing KERNCONF files silently failed giving no indication as to
118 why, only to subsequently discover during installkernel that the
119 desired kernel was never built in the first place.
122 The default serial number format for CTL LUNs has changed. This will
123 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
124 or iSCSI clients care about their LUNs' serial numbers. Users who
125 require serial number stability should hardcode serial numbers in
129 For 32-bit arm compiled for hard-float support, soft-floating point
130 binaries now always get their shared libraries from
131 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
132 /usr/libsoft also existed). Only users with a hard-float ld.so, but
133 soft-float everything else should be affected.
136 The geli password typed at boot is now hidden. To restore the previous
137 behavior, see geli(8) for configuration options.
140 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
141 sysctl values. Minor nit, but requires a rebuild of both world/kernel
145 "make check" behavior (made in ^/head@r295380) has been changed to
146 execute from a limited sandbox, as opposed to executing from
150 - The "beforecheck" and "aftercheck" targets are now specified.
151 - ${CHECKDIR} (added in commit noted above) has been removed.
152 - Legacy behavior can be enabled by setting
153 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
155 If the limited sandbox mode is enabled, "make check" will execute
156 "make distribution", then install, execute the tests, and clean up the
157 sandbox if successful.
159 The "make distribution" and "make install" targets are typically run as
160 root to set appropriate permissions and ownership at installation time.
161 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
162 environment if executing "make check" with limited sandbox mode using
163 an unprivileged user.
166 Since the switch to GPT disk labels, fsck for UFS/FFS has been
167 unable to automatically find alternate superblocks. As of r322297,
168 the information needed to find alternate superblocks has been
169 moved to the end of the area reserved for the boot block.
170 Filesystems created with a newfs of this vintage or later
171 will create the recovery information. If you have a filesystem
172 created prior to this change and wish to have a recovery block
173 created for your filesystem, you can do so by running fsck in
174 forground mode (i.e., do not use the -p or -y options). As it
175 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
176 to which you should answer yes.
179 As of r321665, an NFSv4 server configuration that services
180 Kerberos mounts or clients that do not support the uid/gid in
181 owner/owner_group string capability, must explicitly enable
182 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
183 machine's /etc/rc.conf file.
186 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
187 Please see the 20141231 entry below for information about prerequisites
188 and upgrading, if you are not already using clang 3.5.0 or higher.
191 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
192 r-commands (rlogin, rsh, etc.) to be built with the base system.
195 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
196 a very major ABI incompatible change, so users of FreeBSD/powerpc must
197 be careful when performing source upgrades. It is best to run
198 'make installworld' from an alternate root system, either a live
199 CD/memory stick, or a temporary root partition. Additionally, all ports
200 must be recompiled. powerpc64 is largely unaffected, except in the case
201 of 32-bit compatibility. All 32-bit binaries will be affected.
204 Forward compatibility for the "ino64" project have been committed. This
205 will allow most new binaries to run on older kernels in a limited
206 fashion. This prevents many of the common foot-shooting actions in the
207 upgrade as well as the limited ability to roll back the kernel across
208 the ino64 upgrade. Complicated use cases may not work properly, though
209 enough simpler ones work to allow recovery in most situations.
212 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
213 if you require the GPL compiler.
216 The internal ABI used for communication between the NFS kernel modules
217 was changed by r320085, so __FreeBSD_version was bumped to
218 ensure all the NFS related modules are updated together.
221 The ABI of struct event was changed by extending the data
222 member to 64bit and adding ext fields. For upgrade, same
223 precautions as for the entry 20170523 "ino64" must be
227 The GNU roff toolchain has been removed from base. To render manpages
228 which are not supported by mandoc(1), man(1) can fallback on GNU roff
229 from ports (and recommends to install it).
230 To render roff(7) documents, consider using GNU roff from ports or the
231 heirloom doctools roff toolchain from ports via pkg install groff or
232 via pkg install heirloom-doctools.
235 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
236 smaller runtime footprint builds. This is useful for embedded systems
237 which only require one chipset support.
239 If you load it as a module, make sure this is in /boot/loader.conf:
243 This will load the HAL, all chip/RF backends and if_ath_pci.
244 If you have if_ath_pci in /boot/loader.conf, ensure it is after
245 if_ath or it will not load any HAL chipset support.
247 If you want to selectively load things (eg on ye cheape ARM/MIPS
248 platforms where RAM is at a premium) you should:
251 * load the chip modules in question
252 * load ath_rate, ath_dfs
254 * load if_ath_pci and/or if_ath_ahb depending upon your particular
255 bus bind type - this is where probe/attach is done.
257 For further comments/feedback, poke adrian@ .
260 The "ino64" 64-bit inode project has been committed, which extends
261 a number of types to 64 bits. Upgrading in place requires care and
262 adherence to the documented upgrade procedure.
264 If using a custom kernel configuration ensure that the
265 COMPAT_FREEBSD11 option is included (as during the upgrade the
266 system will be running the ino64 kernel with the existing world).
268 For the safest in-place upgrade begin by removing previous build
269 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
270 full procedure documented below under the heading "To rebuild
271 everything and install it on the current system." Specifically,
272 a reboot is required after installing the new kernel before
276 The NATM framework including the en(4), fatm(4), hatm(4), and
277 patm(4) devices has been removed. Consumers should plan a
278 migration before the end-of-life date for FreeBSD 11.
281 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
282 diff has not been implemented, if those are needed a newer version of
283 GNU diff is available via the diffutils package under the gdiff name.
286 As of r316810 for ipfilter, keep frags is no longer assumed when
287 keep state is specified in a rule. r316810 aligns ipfilter with
288 documentation in man pages separating keep frags from keep state.
289 This allows keep state to be specified without forcing keep frags
290 and allows keep frags to be specified independently of keep state.
291 To maintain previous behaviour, also specify keep frags with
292 keep state (as documented in ipf.conf.5).
295 arm64 builds now use the base system LLD 4.0.0 linker by default,
296 instead of requiring that the aarch64-binutils port or package be
297 installed. To continue using aarch64-binutils, set
298 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
301 The UDP optimization in entry 20160818 that added the sysctl
302 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
303 packets will no longer be treated as L3 broadcast packets.
306 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
307 use any explicitly assigned loopback address available in the jail
308 instead of using the first assigned address of the jail.
311 The ctl.ko module no longer implements the iSCSI target frontend:
312 cfiscsi.ko does instead.
314 If building cfiscsi.ko as a kernel module, the module can be loaded
315 via one of the following methods:
316 - `cfiscsi_load="YES"` in loader.conf(5).
317 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
318 - ctladm(8)/ctld(8), when compiled with iSCSI support
319 (`WITH_ISCSI=yes` in src.conf(5))
321 Please see cfiscsi(4) for more details.
324 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
325 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
326 same source (previously, the dependency of mmcsd.ko on mmc.ko was
327 missing, but mmcsd.ko now will refuse to load if it is incompatible
331 The syntax of ipfw(8) named states was changed to avoid ambiguity.
332 If you have used named states in the firewall rules, you need to modify
333 them after installworld and before rebooting. Now named states must
334 be prefixed with colon.
337 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
338 removed as the userland we provide cannot use them. The KMS version
339 (sys/dev/drm2) supports the same hardware.
342 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
343 Please see the 20141231 entry below for information about prerequisites
344 and upgrading, if you are not already using clang 3.5.0 or higher.
347 The code that provides support for ZFS .zfs/ directory functionality
348 has been reimplemented. It's not possible now to create a snapshot
349 by mkdir under .zfs/snapshot/. That should be the only user visible
353 EISA bus support has been removed. The WITH_EISA option is no longer
357 MCA bus support has been removed.
360 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
361 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
364 The EM_MULTIQUEUE kernel configuration option is deprecated now that
365 the em(4) driver conforms to iflib specifications.
368 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
369 IFLIB. If you have a custom kernel configuration that excludes em(4)
370 but you use igb(4), you need to re-add em(4) to your custom configuration.
373 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
374 Please see the 20141231 entry below for information about prerequisites
375 and upgrading, if you are not already using clang 3.5.0 or higher.
378 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
379 Please see the 20141231 entry below for information about prerequisites
380 and upgrading, if you are not already using clang 3.5.0 or higher.
383 The layout of the pmap structure has changed for powerpc to put the pmap
384 statistics at the front for all CPU variations. libkvm(3) and all tools
385 that link against it need to be recompiled.
388 isl(4) and cyapa(4) drivers now require a new driver,
389 chromebook_platform(4), to work properly on Chromebook-class hardware.
390 On other types of hardware the drivers may need to be configured using
391 device hints. Please see the corresponding manual pages for details.
394 The urtwn(4) driver was merged into rtwn(4) and now consists of
395 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
397 Also, firmware for RTL8188CE was renamed due to possible name
398 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
401 GNU rcs has been removed from base. It is available as packages:
402 - rcs: Latest GPLv3 GNU rcs version.
403 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
407 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
408 modules now requires that the kernel configuration contain the
409 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
412 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
413 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
416 Relocatable object files with the extension of .So have been renamed
417 to use an extension of .pico instead. The purpose of this change is
418 to avoid a name clash with shared libraries on case-insensitive file
419 systems. On those file systems, foo.So is the same file as foo.so.
422 GNU rcs has been turned off by default. It can (temporarily) be built
423 again by adding WITH_RCS knob in src.conf.
424 Otherwise, GNU rcs is available from packages:
425 - rcs: Latest GPLv3 GNU rcs version.
426 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
429 The backup_uses_rcs functionality has been removed from rc.subr.
432 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
433 two separate components, QUEUE_MACRO_DEBUG_TRACE and
434 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
435 QUEUE_MACRO_DEBUG behavior.
438 r304787 changed some ioctl interfaces between the iSCSI userspace
439 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
440 rebuilt to work with new kernels. __FreeBSD_version has been bumped
444 The UDP receive code has been updated to only treat incoming UDP
445 packets that were addressed to an L2 broadcast address as L3
446 broadcast packets. It is not expected that this will affect any
447 standards-conforming UDP application. The new behaviour can be
448 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
452 Remove the openbsd_poll system call.
453 __FreeBSD_version has been bumped because of this.
456 The libc stub for the pipe(2) system call has been replaced with
457 a wrapper that calls the pipe2(2) system call and the pipe(2)
458 system call is now only implemented by the kernels that include
459 "options COMPAT_FREEBSD10" in their config file (this is the
460 default). Users should ensure that this option is enabled in
461 their kernel or upgrade userspace to r302092 before upgrading their
465 CAM will now strip leading spaces from SCSI disks' serial numbers.
466 This will affect users who create UFS filesystems on SCSI disks using
467 those disk's diskid device nodes. For example, if /etc/fstab
468 previously contained a line like
469 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
470 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
471 transforms like gmirror may also be affected. ZFS users should
475 The bitstring(3) API has been updated with new functionality and
476 improved performance. But it is binary-incompatible with the old API.
477 Objects built with the new headers may not be linked against objects
478 built with the old headers.
481 The brk and sbrk functions have been removed from libc on arm64.
482 Binutils from ports has been updated to not link to these
483 functions and should be updated to the latest version before
484 installing a new libc.
487 The armv6 port now defaults to hard float ABI. Limited support
488 for running both hardfloat and soft float on the same system
489 is available using the libraries installed with -DWITH_LIBSOFT.
490 This has only been tested as an upgrade path for installworld
491 and packages may fail or need manual intervention to run. New
492 packages will be needed.
494 To update an existing self-hosted armv6hf system, you must add
495 TARGET_ARCH=armv6 on the make command line for both the build
496 and the install steps.
499 Kernel modules compiled outside of a kernel build now default to
500 installing to /boot/modules instead of /boot/kernel. Many kernel
501 modules built this way (such as those in ports) already overrode
502 KMODDIR explicitly to install into /boot/modules. However,
503 manually building and installing a module from /sys/modules will
504 now install to /boot/modules instead of /boot/kernel.
507 The CAM I/O scheduler has been committed to the kernel. There should be
508 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
509 list of known rogues that claim support for this but actually corrupt
510 data is believed to be complete, be on the lookout for data
511 corruption. The known rogue list is believed to be complete:
513 o Crucial MX100, M550 drives with MU01 firmware.
514 o Micron M510 and M550 drives with MU01 firmware.
515 o Micron M500 prior to MU07 firmware
516 o Samsung 830, 840, and 850 all firmwares
517 o FCCT M500 all firmwares
519 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
520 with working NCQ TRIM. For Micron branded drives, see your sales rep for
521 updated firmware. Black listed drives will work correctly because these
522 drives work correctly so long as no NCQ TRIMs are sent to them. Given
523 this list is the same as found in Linux, it's believed there are no
524 other rogues in the market place. All other models from the above
527 To be safe, if you are at all concerned, you can quirk each of your
528 drives to prevent NCQ from being sent by setting:
529 kern.cam.ada.X.quirks="0x2"
530 in loader.conf. If the drive requires the 4k sector quirk, set the
534 The FAST_DEPEND build option has been removed and its functionality is
535 now the one true way. The old mkdep(1) style of 'make depend' has
536 been removed. See 20160311 for further details.
539 Resource range types have grown from unsigned long to uintmax_t. All
540 drivers, and anything using libdevinfo, need to be recompiled.
543 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
544 builds. It no longer runs mkdep(1) during 'make depend', and the
545 'make depend' stage can safely be skipped now as it is auto ran
546 when building 'make all' and will generate all SRCS and DPSRCS before
547 building anything else. Dependencies are gathered at compile time with
548 -MF flags kept in separate .depend files per object file. Users should
549 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
553 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
554 kernel modules. Therefore, if you load any kernel modules at boot time,
555 please install the boot loaders after you install the kernel, but before
559 make kernel KERNCONF=YOUR_KERNEL_HERE
560 make -C sys/boot install
561 <reboot in single user>
563 Then follow the usual steps, described in the General Notes section,
567 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
568 see the 20141231 entry below for information about prerequisites and
569 upgrading, if you are not already using clang 3.5.0 or higher.
572 The AIO subsystem is now a standard part of the kernel. The
573 VFS_AIO kernel option and aio.ko kernel module have been removed.
574 Due to stability concerns, asynchronous I/O requests are only
575 permitted on sockets and raw disks by default. To enable
576 asynchronous I/O requests on all file types, set the
577 vfs.aio.enable_unsafe sysctl to a non-zero value.
580 The ELF object manipulation tool objcopy is now provided by the
581 ELF Tool Chain project rather than by GNU binutils. It should be a
582 drop-in replacement, with the addition of arm64 support. The
583 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
584 to obtain the GNU version if necessary.
587 Building ZFS pools on top of zvols is prohibited by default. That
588 feature has never worked safely; it's always been prone to deadlocks.
589 Using a zvol as the backing store for a VM guest's virtual disk will
590 still work, even if the guest is using ZFS. Legacy behavior can be
591 restored by setting vfs.zfs.vol.recursive=1.
594 The NONE and HPN patches has been removed from OpenSSH. They are
595 still available in the security/openssh-portable port.
598 With the addition of ypldap(8), a new _ypldap user is now required
599 during installworld. "mergemaster -p" can be used to add the user
600 prior to installworld, as documented in the handbook.
603 The tftp loader (pxeboot) now uses the option root-path directive. As a
604 consequence it no longer looks for a pxeboot.4th file on the tftp
605 server. Instead it uses the regular /boot infrastructure as with the
609 The code to start recording plug and play data into the modules has
610 been committed. While the old tools will properly build a new kernel,
611 a number of warnings about "unknown metadata record 4" will be produced
612 for an older kldxref. To avoid such warnings, make sure to rebuild
613 the kernel toolchain (or world). Make sure that you have r292078 or
614 later when trying to build 292077 or later before rebuilding.
617 Debug data files are now built by default with 'make buildworld' and
618 installed with 'make installworld'. This facilitates debugging but
619 requires more disk space both during the build and for the installed
620 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
624 r291527 changed the internal interface between the nfsd.ko and
625 nfscommon.ko modules. As such, they must both be upgraded to-gether.
626 __FreeBSD_version has been bumped because of this.
629 Add support for unicode collation strings leads to a change of
630 order of files listed by ls(1) for example. To get back to the old
631 behaviour, set LC_COLLATE environment variable to "C".
633 Databases administrators will need to reindex their databases given
634 collation results will be different.
636 Due to a bug in install(1) it is recommended to remove the ancient
637 locales before running make installworld.
639 rm -rf /usr/share/locale/*
642 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
643 libcrypto.so.7 or libssl.so.7 must be recompiled.
646 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
647 Kernel modules isp_2400_multi and isp_2500_multi were removed and
648 should be replaced with isp_2400 and isp_2500 modules respectively.
651 The build previously allowed using 'make -n' to not recurse into
652 sub-directories while showing what commands would be executed, and
653 'make -n -n' to recursively show commands. Now 'make -n' will recurse
654 and 'make -N' will not.
657 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
658 and etcupdate will now use this file. A custom sendmail.cf is now
659 updated via this mechanism rather than via installworld. If you had
660 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
661 want to remove the exclusion or change it to "always install".
662 /etc/mail/sendmail.cf is now managed the same way regardless of
663 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
664 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
667 Compatibility shims for legacy ATA device names have been removed.
668 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
669 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
670 environment variables, /dev/ad* and /dev/ar* symbolic links.
673 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
674 Please see the 20141231 entry below for information about prerequisites
675 and upgrading, if you are not already using clang 3.5.0 or higher.
678 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
679 and renamed from .symbols to .debug. This reduces the size requirements
680 on the boot partition or file system and provides consistency with
681 userland debug files.
683 When using the supported kernel installation method the
684 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
685 as is done with /boot/kernel.
687 Developers wishing to maintain the historical behavior of installing
688 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
691 The wireless drivers had undergone changes that remove the 'parent
692 interface' from the ifconfig -l output. The rc.d network scripts
693 used to check presence of a parent interface in the list, so old
694 scripts would fail to start wireless networking. Thus, etcupdate(3)
695 or mergemaster(8) run is required after kernel update, to update your
696 rc.d scripts in /etc.
699 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
700 These configurations are now automatically interpreted as
701 'scrub fragment reassemble'.
704 Kernel-loadable modules for the random(4) device are back. To use
705 them, the kernel must have
708 options RANDOM_LOADABLE
710 kldload(8) can then be used to load random_fortuna.ko
711 or random_yarrow.ko. Please note that due to the indirect
712 function calls that the loadable modules need to provide,
713 the build-in variants will be slightly more efficient.
715 The random(4) kernel option RANDOM_DUMMY has been retired due to
716 unpopularity. It was not all that useful anyway.
719 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
720 Control over building the ELF Tool Chain tools is now provided by
721 the WITHOUT_TOOLCHAIN knob.
724 The polarity of Pulse Per Second (PPS) capture events with the
725 uart(4) driver has been corrected. Prior to this change the PPS
726 "assert" event corresponded to the trailing edge of a positive PPS
727 pulse and the "clear" event was the leading edge of the next pulse.
729 As the width of a PPS pulse in a typical GPS receiver is on the
730 order of 1 millisecond, most users will not notice any significant
731 difference with this change.
733 Anyone who has compensated for the historical polarity reversal by
734 configuring a negative offset equal to the pulse width will need to
735 remove that workaround.
738 The default group assigned to /dev/dri entries has been changed
739 from 'wheel' to 'video' with the id of '44'. If you want to have
740 access to the dri devices please add yourself to the video group
743 # pw groupmod video -m $USER
746 The menu.rc and loader.rc files will now be replaced during
747 upgrades. Please migrate local changes to menu.rc.local and
748 loader.rc.local instead.
751 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
752 strings and strip have been removed. The src.conf(5) knob
753 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
756 As ZFS requires more kernel stack pages than is the default on some
757 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
758 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
760 Please consider using 'options KSTACK_PAGES=X' where X is greater
761 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
764 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
765 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
766 default, i.e., they will not contain "::". For example, instead
767 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
768 to have a more specific match, such as different map entries for
769 IPv6:0:0 vs IPv6:0. This change requires that configuration
770 data (including maps, files, classes, custom ruleset, etc.) must
771 use the same format, so make certain such configuration data is
772 upgrading. As a very simple check search for patterns like
773 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
774 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
775 the cf option UseCompressedIPv6Addresses.
778 The default kernel entropy-processing algorithm is now
779 Fortuna, replacing Yarrow.
781 Assuming you have 'device random' in your kernel config
782 file, the configurations allow a kernel option to override
783 this default. You may choose *ONE* of:
785 options RANDOM_YARROW # Legacy /dev/random algorithm.
786 options RANDOM_DUMMY # Blocking-only driver.
788 If you have neither, you get Fortuna. For most people,
789 read no further, Fortuna will give a /dev/random that works
790 like it always used to, and the difference will be irrelevant.
792 If you remove 'device random', you get *NO* kernel-processed
793 entropy at all. This may be acceptable to folks building
794 embedded systems, but has complications. Carry on reading,
795 and it is assumed you know what you need.
797 *PLEASE* read random(4) and random(9) if you are in the
798 habit of tweaking kernel configs, and/or if you are a member
799 of the embedded community, wanting specific and not-usual
800 behaviour from your security subsystems.
802 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
803 random', you will NOT have a functioning /dev/random, and
804 many cryptographic features will not work, including SSH.
805 You may also find strange behaviour from the random(3) set
806 of library functions, in particular sranddev(3), srandomdev(3)
807 and arc4random(3). The reason for this is that the KERN_ARND
808 sysctl only returns entropy if it thinks it has some to
809 share, and with RANDOM_DUMMY or no 'device random' this
813 An additional fix for the issue described in the 20150614 sendmail
814 entry below has been been committed in revision 284717.
817 FreeBSD's old make (fmake) has been removed from the system. It is
818 available as the devel/fmake port or via pkg install fmake.
821 The fix for the issue described in the 20150614 sendmail entry
822 below has been been committed in revision 284436. The work
823 around described in that entry is no longer needed unless the
824 default setting is overridden by a confDH_PARAMETERS configuration
825 setting of '5' or pointing to a 512 bit DH parameter file.
828 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
829 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
830 and devel/kyua to version 0.20+ and adjust any calling code to work
831 with Kyuafile and kyua.
834 The import of openssl to address the FreeBSD-SA-15:10.openssl
835 security advisory includes a change which rejects handshakes
836 with DH parameters below 768 bits. sendmail releases prior
837 to 8.15.2 (not yet released), defaulted to a 512 bit
838 DH parameter setting for client connections. To work around
839 this interoperability, sendmail can be configured to use a
840 2048 bit DH parameter by:
842 1. Edit /etc/mail/`hostname`.mc
843 2. If a setting for confDH_PARAMETERS does not exist or
844 exists and is set to a string beginning with '5',
846 3. If a setting for confDH_PARAMETERS exists and is set to
847 a file path, create a new file with:
848 openssl dhparam -out /path/to/file 2048
849 4. Rebuild the .cf file:
850 cd /etc/mail/; make; make install
852 cd /etc/mail/; make restart
854 A sendmail patch is coming, at which time this file will be
858 Generation of legacy formatted entries have been disabled by default
859 in pwd_mkdb(8), as all base system consumers of the legacy formatted
860 entries were converted to use the new format by default when the new,
861 machine independent format have been added and supported since FreeBSD
864 Please see the pwd_mkdb(8) manual page for further details.
867 Clang and llvm have been upgraded to 3.6.1 release. Please see the
868 20141231 entry below for information about prerequisites and upgrading,
869 if you are not already using 3.5.0 or higher.
872 TI platform code switched to using vendor DTS files and this update
873 may break existing systems running on Beaglebone, Beaglebone Black,
876 - dtb files should be regenerated/reinstalled. Filenames are the
877 same but content is different now
878 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
879 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
880 addressing scheme is now pin 25 on /dev/gpioc3.
881 - Pandaboard: /etc/ttys should be updated, serial console device is
882 now /dev/ttyu2, not /dev/ttyu0
885 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
886 If you need the GNU extension from groff soelim(1), install groff
887 from package: pkg install groff, or via ports: textproc/groff.
890 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
891 defined in symlink(7); previously symlinks were silently ignored.
894 The const qualifier has been removed from iconv(3) to comply with
895 POSIX. The ports tree is aware of this from r384038 onwards.
898 Libraries specified by LIBADD in Makefiles must have a corresponding
899 DPADD_<lib> variable to ensure correct dependencies. This is now
900 enforced in src.libnames.mk.
903 From legacy ata(4) driver was removed support for SATA controllers
904 supported by more functional drivers ahci(4), siis(4) and mvs(4).
905 Kernel modules ataahci and ataadaptec were removed completely,
906 replaced by ahci and mvs modules respectively.
909 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
910 the 20141231 entry below for information about prerequisites and
911 upgrading, if you are not already using 3.5.0 or higher.
914 The 32-bit PowerPC kernel has been changed to a position-independent
915 executable. This can only be booted with a version of loader(8)
916 newer than January 31, 2015, so make sure to update both world and
917 kernel before rebooting.
920 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
921 but before r278950, the RNG was not seeded properly. Immediately
922 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
923 ssh keys or openssl keys) that were generated w/ a kernel from that
924 range. This does not affect programs that directly used /dev/random
925 or /dev/urandom. All userland uses of arc4random(3) are affected.
928 The autofs(4) ABI was changed in order to restore binary compatibility
929 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
933 The powerpc64 kernel has been changed to a position-independent
934 executable. This can only be booted with a new version of loader(8),
935 so make sure to update both world and kernel before rebooting.
938 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
939 only release, no new features have been added. Please see the 20141231
940 entry below for information about prerequisites and upgrading, if you
941 are not already using 3.5.0.
944 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
945 taken from the ELF Tool Chain project rather than GNU binutils. They
946 should be drop-in replacements, with the addition of arm64 support.
947 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
948 binutils tools, if necessary. See 20150805 for updated information.
951 The default Unbound configuration now enables remote control
952 using a local socket. Users who have already enabled the
953 local_unbound service should regenerate their configuration
954 by running "service local_unbound setup" as root.
957 The GNU texinfo and GNU info pages have been removed.
958 To be able to view GNU info pages please install texinfo from ports.
961 Clang, llvm and lldb have been upgraded to 3.5.0 release.
963 As of this release, a prerequisite for building clang, llvm and lldb is
964 a C++11 capable compiler and C++11 standard library. This means that to
965 be able to successfully build the cross-tools stage of buildworld, with
966 clang as the bootstrap compiler, your system compiler or cross compiler
967 should either be clang 3.3 or later, or gcc 4.8 or later, and your
968 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
971 On any standard FreeBSD 10.x or 11.x installation, where clang and
972 libc++ are on by default (that is, on x86 or arm), this should work out
975 On 9.x installations where clang is enabled by default, e.g. on x86 and
976 powerpc, libc++ will not be enabled by default, so libc++ should be
977 built (with clang) and installed first. If both clang and libc++ are
978 missing, build clang first, then use it to build libc++.
980 On 8.x and earlier installations, upgrade to 9.x first, and then follow
981 the instructions for 9.x above.
983 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
984 default, and do not build clang.
986 Many embedded systems are resource constrained, and will not be able to
987 build clang in a reasonable time, or in some cases at all. In those
988 cases, cross building bootable systems on amd64 is a workaround.
990 This new version of clang introduces a number of new warnings, of which
991 the following are most likely to appear:
995 This warns in two cases, for both C and C++:
996 * When the code is trying to take the absolute value of an unsigned
997 quantity, which is effectively a no-op, and almost never what was
998 intended. The code should be fixed, if at all possible. If you are
999 sure that the unsigned quantity can be safely cast to signed, without
1000 loss of information or undefined behavior, you can add an explicit
1001 cast, or disable the warning.
1003 * When the code is trying to take an absolute value, but the called
1004 abs() variant is for the wrong type, which can lead to truncation.
1005 If you want to disable the warning instead of fixing the code, please
1006 make sure that truncation will not occur, or it might lead to unwanted
1009 -Wtautological-undefined-compare and
1010 -Wundefined-bool-conversion
1012 These warn when C++ code is trying to compare 'this' against NULL, while
1013 'this' should never be NULL in well-defined C++ code. However, there is
1014 some legacy (pre C++11) code out there, which actively abuses this
1015 feature, which was less strictly defined in previous C++ versions.
1017 Squid and openjdk do this, for example. The warning can be turned off
1018 for C++98 and earlier, but compiling the code in C++11 mode might result
1019 in unexpected behavior; for example, the parts of the program that are
1020 unreachable could be optimized away.
1023 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1024 kernel sources have been removed. The .h files remain, since some
1025 utilities include them. This will need to be fixed later.
1026 If "mount -t oldnfs ..." is attempted, it will fail.
1027 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1028 the utilities will report errors.
1031 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1032 directories to top level SUBDIR variable when their parent
1033 directory is included in LOCAL_DIRS. Users with build systems with
1034 such hierarchies and without SUBDIR entries in the parent
1035 directory Makefiles should add them or add the directories to
1039 faith(4) and faithd(8) have been removed from the base system. Faith
1040 has been obsolete for a very long time.
1043 vt(4), the new console driver, is enabled by default. It brings
1044 support for Unicode and double-width characters, as well as
1045 support for UEFI and integration with the KMS kernel video
1048 You may need to update your console settings in /etc/rc.conf,
1049 most probably the keymap. During boot, /etc/rc.d/syscons will
1050 indicate what you need to do.
1052 vt(4) still has issues and lacks some features compared to
1053 syscons(4). See the wiki for up-to-date information:
1054 https://wiki.freebsd.org/Newcons
1056 If you want to keep using syscons(4), you can do so by adding
1057 the following line to /boot/loader.conf:
1061 pjdfstest has been integrated into kyua as an opt-in test suite.
1062 Please see share/doc/pjdfstest/README for more details on how to
1066 gperf has been removed from the base system for architectures
1067 that use clang. Ports that require gperf will obtain it from the
1071 pjdfstest has been moved from tools/regression/pjdfstest to
1075 At svn r271982, The default linux compat kernel ABI has been adjusted
1076 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1077 update. If you wish to continue using the linux-f10 compat ports,
1078 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1079 encouraged to update their linux-compat packages to linux-c6 during
1080 their next update cycle.
1083 The ofwfb driver, used to provide a graphics console on PowerPC when
1084 using vt(4), no longer allows mmap() of all physical memory. This
1085 will prevent Xorg on PowerPC with some ATI graphics cards from
1086 initializing properly unless x11-servers/xorg-server is updated to
1090 The xdev targets have been converted to using TARGET and
1091 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1094 The default unbound configuration has been modified to address
1095 issues with reverse lookups on networks that use private
1096 address ranges. If you use the local_unbound service, run
1097 "service local_unbound setup" as root to regenerate your
1098 configuration, then "service local_unbound reload" to load the
1102 The GNU texinfo and GNU info pages are not built and installed
1103 anymore, WITH_INFO knob has been added to allow to built and install
1105 UPDATE: see 20150102 entry on texinfo's removal
1108 The GNU readline library is now an INTERNALLIB - that is, it is
1109 statically linked into consumers (GDB and variants) in the base
1110 system, and the shared library is no longer installed. The
1111 devel/readline port is available for third party software that
1115 The Itanium architecture (ia64) has been removed from the list of
1116 known architectures. This is the first step in the removal of the
1120 Commit r268115 has added NFSv4.1 server support, merged from
1121 projects/nfsv4.1-server. Since this includes changes to the
1122 internal interfaces between the NFS related modules, a full
1123 build of the kernel and modules will be necessary.
1124 __FreeBSD_version has been bumped.
1127 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1128 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1129 which differs from the behaviour controlled by this knob.)
1132 Maximal length of the serial number in CTL was increased from 16 to
1133 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1134 and ctld, need to be rebuilt to work with a new kernel.
1137 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1138 1 respectively to match the upstream numbers. They were out of
1139 sync because, when they were originally added to FreeBSD, the
1140 upstream versions were not respected. These libraries are private
1141 and not yet built by default, so renumbering them should be a
1142 non-issue. However, unclean source trees will yield broken test
1143 programs once the operator executes "make delete-old-libs" after a
1144 "make installworld".
1146 Additionally, the atf-sh binary was made private by moving it into
1147 /usr/libexec/. Already-built shell test programs will keep the
1148 path to the old binary so they will break after "make delete-old"
1151 If you are using WITH_TESTS=yes (not the default), wipe the object
1152 tree and rebuild from scratch to prevent spurious test failures.
1153 This is only needed once: the misnumbered libraries and misplaced
1154 binaries have been added to OptionalObsoleteFiles.inc so they will
1155 be removed during a clean upgrade.
1158 Clang and llvm have been upgraded to 3.4.1 release.
1161 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1162 be removed to avoid issues in the future (and has been added to
1166 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1167 past, it affected all builds that used the bsd.*.mk files. The old
1168 behavior was a bug, but people may have relied upon it. To get this
1169 behavior back, you can .include /etc/src.conf from /etc/make.conf
1170 (which is still global and isn't changed). This also changes the
1171 behavior of incremental builds inside the tree of individual
1172 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1173 Although this has survived make universe and some upgrade scenarios,
1174 other upgrade scenarios may have broken. At least one form of
1175 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1176 as well... In cases where MAKESYSPATH isn't working with this
1177 setting, you'll need to set it to the full path to your tree.
1179 One side effect of all this cleaning up is that bsd.compiler.mk
1180 is no longer implicitly included by bsd.own.mk. If you wish to
1181 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1185 The lindev device has been removed since /dev/full has been made a
1186 standard device. __FreeBSD_version has been bumped.
1189 The knob WITHOUT_VI was added to the base system, which controls
1190 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1191 in order to reorder files share/termcap and didn't build ex(1) as a
1192 build tool, so building/installing with WITH_VI is highly advised for
1193 build hosts for older releases.
1195 This issue has been fixed in stable/9 and stable/10 in r277022 and
1196 r276991, respectively.
1199 The YES_HESIOD knob has been removed. It has been obsolete for
1200 a decade. Please move to using WITH_HESIOD instead or your builds
1201 will silently lack HESIOD.
1204 The uart(4) driver has been changed with respect to its handling
1205 of the low-level console. Previously the uart(4) driver prevented
1206 any process from changing the baudrate or the CLOCAL and HUPCL
1207 control flags. By removing the restrictions, operators can make
1208 changes to the serial console port without having to reboot.
1209 However, when getty(8) is started on the serial device that is
1210 associated with the low-level console, a misconfigured terminal
1211 line in /etc/ttys will now have a real impact.
1212 Before upgrading the kernel, make sure that /etc/ttys has the
1213 serial console device configured as 3wire without baudrate to
1214 preserve the previous behaviour. E.g:
1215 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1218 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1219 to improve performance. To re-enable it, if needed, run rpcbind
1220 with command line option -W.
1223 Switched back to the GPL dtc compiler due to updates in the upstream
1224 dts files not being supported by the BSDL dtc compiler. You will need
1225 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1226 may result while building dtb files during a kernel build if you fail
1227 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1230 Clang and llvm have been upgraded to 3.4 release.
1233 The nve(4) driver has been removed. Please use the nfe(4) driver
1234 for NVIDIA nForce MCP Ethernet adapters instead.
1237 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1238 This could cause certain C++ applications using shared libraries built
1239 against the previous version of libc++ to crash. The incompatibility
1240 has now been fixed, but any C++ applications or shared libraries built
1241 between r261283 and r261801 should be recompiled.
1244 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1245 capability mode support. Please note that enabling the feature in
1246 kernel is still highly recommended.
1249 OpenSSH is now built with sandbox support, and will use sandbox as
1250 the default privilege separation method. This requires Capsicum
1251 capability mode support in kernel.
1254 The libelf and libdwarf libraries have been updated to newer
1255 versions from upstream. Shared library version numbers for
1256 these two libraries were bumped. Any ports or binaries
1257 requiring these two libraries should be recompiled.
1258 __FreeBSD_version is bumped to 1100006.
1261 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1262 instead of providing an explicit one, this would prevent such
1263 Makefile from providing its own Kyuafile in the future during
1264 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1265 intervention is needed to clean an objdir if you use NO_CLEAN:
1266 # find /usr/obj -name Kyuafile | xargs rm -f
1269 The behavior of gss_pseudo_random() for the krb5 mechanism
1270 has changed, for applications requesting a longer random string
1271 than produced by the underlying enctype's pseudo-random() function.
1272 In particular, the random string produced from a session key of
1273 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1274 be different at the 17th octet and later, after this change.
1275 The counter used in the PRF+ construction is now encoded as a
1276 big-endian integer in accordance with RFC 4402.
1277 __FreeBSD_version is bumped to 1100004.
1280 The WITHOUT_ATF build knob has been removed and its functionality
1281 has been subsumed into the more generic WITHOUT_TESTS. If you were
1282 using the former to disable the build of the ATF libraries, you
1283 should change your settings to use the latter.
1286 The default version of mtree is nmtree which is obtained from
1287 NetBSD. The output is generally the same, but may vary
1288 slightly. If you found you need identical output adding
1289 "-F freebsd9" to the command line should do the trick. For the
1290 time being, the old mtree is available as fmtree.
1293 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1294 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1295 1.1.4_8 and verify bsdyml not linked in, before running "make
1297 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1299 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1302 The stable/10 branch has been created in subversion from head
1306 The rc.d/jail script has been updated to support jail(8)
1307 configuration file. The "jail_<jname>_*" rc.conf(5) variables
1308 for per-jail configuration are automatically converted to
1309 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
1310 This is transparently backward compatible. See below about some
1311 incompatibilities and rc.conf(5) manual page for more details.
1313 These variables are now deprecated in favor of jail(8) configuration
1314 file. One can use "rc.d/jail config <jname>" command to generate
1315 a jail(8) configuration file in /var/run/jail.<jname>.conf without
1316 running the jail(8) utility. The default pathname of the
1317 configuration file is /etc/jail.conf and can be specified by
1318 using $jail_conf or $jail_<jname>_conf variables.
1320 Please note that jail_devfs_ruleset accepts an integer at
1321 this moment. Please consider to rewrite the ruleset name
1325 BIND has been removed from the base system. If all you need
1326 is a local resolver, simply enable and start the local_unbound
1327 service instead. Otherwise, several versions of BIND are
1328 available in the ports tree. The dns/bind99 port is one example.
1330 With this change, nslookup(1) and dig(1) are no longer in the base
1331 system. Users should instead use host(1) and drill(1) which are
1332 in the base system. Alternatively, nslookup and dig can
1333 be obtained by installing the dns/bind-tools port.
1336 With the addition of unbound(8), a new unbound user is now
1337 required during installworld. "mergemaster -p" can be used to
1338 add the user prior to installworld, as documented in the handbook.
1341 OpenSSH is now built with DNSSEC support, and will by default
1342 silently trust signed SSHFP records. This can be controlled with
1343 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1344 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1347 The GNU Compiler Collection and C++ standard library (libstdc++)
1348 are no longer built by default on platforms where clang is the system
1349 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1350 options in src.conf.
1353 The PROCDESC kernel option is now part of the GENERIC kernel
1354 configuration and is required for the rwhod(8) to work.
1355 If you are using custom kernel configuration, you should include
1359 The API and ABI related to the Capsicum framework was modified
1360 in backward incompatible way. The userland libraries and programs
1361 have to be recompiled to work with the new kernel. This includes the
1362 following libraries and programs, but the whole buildworld is
1363 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1364 kdump, procstat, rwho, rwhod, uniq.
1367 AES-NI intrinsic support has been added to gcc. The AES-NI module
1368 has been updated to use this support. A new gcc is required to build
1369 the aesni module on both i386 and amd64.
1372 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1373 Thus "device padlock_rng" and "device rdrand_rng" should be
1374 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1377 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1378 enables just the iconv* functionality and is now on by default.
1379 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1380 compatibility. Set WITHOUT_ICONV to build the old way.
1381 If you have been using WITH_ICONV before, you will very likely
1382 need to turn on WITH_LIBICONV_COMPAT.
1385 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1386 Illumos origin, including ZFS. If you have INVARIANTS in your
1387 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1389 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1390 locks if WITNESS option was set. Because that generated a lot of
1391 witness(9) reports and all of them were believed to be false
1392 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1393 can be used to achieve the previous behavior.
1396 Timer values in IPv6 data structures now use time_uptime instead
1397 of time_second. Although this is not a user-visible functional
1398 change, userland utilities which directly use them---ndp(8),
1399 rtadvd(8), and rtsold(8) in the base system---need to be updated
1400 to r253970 or later.
1403 find -delete can now delete the pathnames given as arguments,
1404 instead of only files found below them or if the pathname did
1405 not contain any slashes. Formerly, the following error message
1408 find: -delete: <path>: relative path potentially not safe
1410 Deleting the pathnames given as arguments can be prevented
1411 without error messages using -mindepth 1 or by changing
1412 directory and passing "." as argument to find. This works in the
1413 old as well as the new version of find.
1416 Behavior of devfs rules path matching has been changed.
1417 Pattern is now always matched against fully qualified devfs
1418 path and slash characters must be explicitly matched by
1419 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1420 subdirectories must be reviewed.
1423 The default ARM ABI has changed to the ARM EABI. The old ABI is
1424 incompatible with the ARM EABI and all programs and modules will
1425 need to be rebuilt to work with a new kernel.
1427 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1429 NOTE: Support for the old ABI will be removed in the future and
1430 users are advised to upgrade.
1433 pkg_install has been disconnected from the build if you really need it
1434 you should add WITH_PKGTOOLS in your src.conf(5).
1437 Most of network statistics structures were changed to be able
1438 keep 64-bits counters. Thus all tools, that work with networking
1439 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1442 Fix a bug that allowed a tracing process (e.g. gdb) to write
1443 to a memory-mapped file in the traced process's address space
1444 even if neither the traced process nor the tracing process had
1445 write access to that file.
1448 CVS has been removed from the base system. An exact copy
1449 of the code is available from the devel/cvs port.
1452 Some people report the following error after the switch to bmake:
1454 make: illegal option -- J
1455 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1457 *** [buildworld] Error code 2
1459 this likely due to an old instance of make in
1460 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1461 which src/Makefile will use that blindly, if it exists, so if
1462 you see the above error:
1464 rm -rf `make -V MAKEPATH`
1469 Use bmake by default.
1470 Whereas before one could choose to build with bmake via
1471 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1472 make. The goal is to remove these knobs for 10-RELEASE.
1474 It is worth noting that bmake (like gmake) treats the command
1475 line as the unit of failure, rather than statements within the
1476 command line. Thus '(cd some/where && dosomething)' is safer
1477 than 'cd some/where; dosomething'. The '()' allows consistent
1478 behavior in parallel build.
1481 Fix a bug that allows NFS clients to issue READDIR on files.
1484 The WITHOUT_IDEA option has been removed because
1485 the IDEA patent expired.
1488 The sysctl which controls TRIM support under ZFS has been renamed
1489 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1493 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1494 rather than creating it's own in the temporary directory in
1495 order allow access to bootstrapped versions of tools such as
1496 install and mtree. When upgrading from version of FreeBSD where
1497 the install command does not support -l, you will need to
1498 install a new mergemaster command if mergemaster -p is required.
1499 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1503 Legacy ATA stack, disabled and replaced by new CAM-based one since
1504 FreeBSD 9.0, completely removed from the sources. Kernel modules
1505 atadisk and atapi*, user-level tools atacontrol and burncd are
1506 removed. Kernel option `options ATA_CAM` is now permanently enabled
1510 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1511 and socketpair(2). Software, in particular Kerberos, may
1512 automatically detect and use these during building. The resulting
1513 binaries will not work on older kernels.
1516 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1517 information, see the respective 20130304 entry).
1520 Recent commits to callout(9) changed the size of struct callout,
1521 so the KBI is probably heavily disturbed. Also, some functions
1522 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1523 by macros. Every kernel module using it won't load, so rebuild
1526 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1527 but does not initialize by default (because of the new CTL_DISABLE
1528 option) to save memory. To re-enable it, remove the CTL_DISABLE
1529 option from the kernel config file or set kern.cam.ctl.disable=0
1530 in /boot/loader.conf.
1533 The ctl device has been disabled in GENERIC for i386 and amd64.
1534 This was done due to the extra memory being allocated at system
1535 initialisation time by the ctl driver which was only used if
1536 a CAM target device was created. This makes a FreeBSD system
1537 unusable on 128MB or less of RAM.
1540 A new compression method (lz4) has been merged to -HEAD. Please
1541 refer to zpool-features(7) for more information.
1543 Please refer to the "ZFS notes" section of this file for information
1544 on upgrading boot ZFS pools.
1547 A BSD-licensed patch(1) variant has been added and is installed
1548 as bsdpatch, being the GNU version the default patch.
1549 To inverse the logic and use the BSD-licensed one as default,
1550 while having the GNU version installed as gnupatch, rebuild
1551 and install world with the WITH_BSD_PATCH knob set.
1554 Due to the use of the new -l option to install(1) during build
1555 and install, you must take care not to directly set the INSTALL
1556 make variable in your /etc/make.conf, /etc/src.conf, or on the
1557 command line. If you wish to use the -C flag for all installs
1558 you may be able to add INSTALL+=-C to /etc/make.conf or
1562 The install(1) option -M has changed meaning and now takes an
1563 argument that is a file or path to append logs to. In the
1564 unlikely event that -M was the last option on the command line
1565 and the command line contained at least two files and a target
1566 directory the first file will have logs appended to it. The -M
1567 option served little practical purpose in the last decade so its
1568 use is expected to be extremely rare.
1571 After switching to Clang as the default compiler some users of ZFS
1572 on i386 systems started to experience stack overflow kernel panics.
1573 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1576 GEOM_LABEL now mangles label names read from file system metadata.
1577 Mangling affect labels containing spaces, non-printable characters,
1578 '%' or '"'. Device names in /etc/fstab and other places may need to
1582 By default, only the 10 most recent kernel dumps will be saved. To
1583 restore the previous behaviour (no limit on the number of kernel dumps
1584 stored in the dump directory) add the following line to /etc/rc.conf:
1589 With the addition of auditdistd(8), a new auditdistd user is now
1590 required during installworld. "mergemaster -p" can be used to
1591 add the user prior to installworld, as documented in the handbook.
1594 The sin6_scope_id member variable in struct sockaddr_in6 is now
1595 filled by the kernel before passing the structure to the userland via
1596 sysctl or routing socket. This means the KAME-specific embedded scope
1597 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1598 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1599 __FreeBSD_version is bumped to 1000025.
1602 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1603 This means that the world and kernel will be compiled with clang
1604 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1605 and /usr/bin/cpp. To disable this behavior and revert to building
1606 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1607 of current may need to bootstrap WITHOUT_CLANG first if the clang
1608 build fails (its compatibility window doesn't extend to the 9 stable
1612 The IPFIREWALL_FORWARD kernel option has been removed. Its
1613 functionality now turned on by default.
1616 The ZERO_COPY_SOCKET kernel option has been removed and
1617 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1618 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1619 mechanism which is not safe and may result in kernel crashes.
1620 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1621 driver supports disposeable external page sized mbuf storage.
1622 Proper replacements for both zero-copy mechanisms are under
1623 consideration and will eventually lead to complete removal
1624 of the two kernel options.
1627 The IPv4 network stack has been converted to network byte
1628 order. The following modules need to be recompiled together
1629 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1630 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1633 Support for non-MPSAFE filesystems was removed from VFS. The
1634 VFS_VERSION was bumped, all filesystem modules shall be
1638 All the non-MPSAFE filesystems have been disconnected from
1639 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1640 portalfs, smbfs, xfs.
1643 The interface cloning API and ABI has changed. The following
1644 modules need to be recompiled together with kernel:
1645 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1646 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1647 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1650 The sdhci driver was split in two parts: sdhci (generic SD Host
1651 Controller logic) and sdhci_pci (actual hardware driver).
1652 No kernel config modifications are required, but if you
1653 load sdhc as a module you must switch to sdhci_pci instead.
1656 Import the FUSE kernel and userland support into base system.
1659 The GNU sort(1) program has been removed since the BSD-licensed
1660 sort(1) has been the default for quite some time and no serious
1661 problems have been reported. The corresponding WITH_GNU_SORT
1665 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1666 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1670 The net80211(4) ABI has been changed to allow for improved driver
1671 PS-POLL and power-save support. All wireless drivers need to be
1672 recompiled to work with the new kernel.
1675 The random(4) support for the VIA hardware random number
1676 generator (`PADLOCK') is no longer enabled unconditionally.
1677 Add the padlock_rng device in the custom kernel config if
1678 needed. The GENERIC kernels on i386 and amd64 do include the
1679 device, so the change only affects the custom kernel
1683 The pf(4) packet filter ABI has been changed. pfctl(8) and
1684 snmp_pf module need to be recompiled to work with new kernel.
1687 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1688 to -HEAD. Pools that have empty_bpobj in active state can not be
1689 imported read-write with ZFS implementations that do not support
1690 this feature. For more information read the zpool-features(5)
1694 The sparc64 ZFS loader has been changed to no longer try to auto-
1695 detect ZFS providers based on diskN aliases but now requires these
1696 to be explicitly listed in the OFW boot-device environment variable.
1699 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1700 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1701 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1704 The following sysctls and tunables have been renamed for consistency
1705 with other variables:
1706 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1707 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1710 The sort utility has been replaced with BSD sort. For now, GNU sort
1711 is also available as "gnusort" or the default can be set back to
1712 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1713 installed as "bsdsort".
1716 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1717 Starting with this version the old system of ZFS pool versioning
1718 is superseded by "feature flags". This concept enables forward
1719 compatibility against certain future changes in functionality of ZFS
1720 pools. The first read-only compatible "feature flag" for ZFS pools
1721 is named "com.delphix:async_destroy". For more information
1722 read the new zpool-features(5) manual page.
1723 Please refer to the "ZFS notes" section of this file for information
1724 on upgrading boot ZFS pools.
1727 The malloc(3) implementation embedded in libc now uses sources imported
1728 as contrib/jemalloc. The most disruptive API change is to
1729 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1730 delete it prior to installworld, and optionally re-create it using the
1731 new format after rebooting. See malloc.conf(5) for details
1732 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1736 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1737 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1738 now spelled mips. This is to aid compatibility with third-party
1739 software that expects this naming scheme in uname(3). Little-endian
1740 settings are unchanged. If you are updating a big-endian mips64 machine
1741 from before this change, you may need to set MACHINE_ARCH=mips64 in
1742 your environment before the new build system will recognize your machine.
1745 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1749 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1750 nullfs(5) did not pass through all behaviours to the underlying layer,
1751 as a result if we bound to a socket on the lower layer we could connect
1752 only to the lower path; if we bound to the upper layer we could connect
1753 only to the upper path. The new behavior is one can connect to both the
1754 lower and the upper paths regardless what layer path one binds to.
1757 The getifaddrs upgrade path broken with 20111215 has been restored.
1758 If you have upgraded in between 20111215 and 20120209 you need to
1759 recompile libc again with your kernel. You still need to recompile
1760 world to be able to configure CARP but this restriction already
1761 comes from 20111215.
1764 The set_rcvar() function has been removed from /etc/rc.subr. All
1765 base and ports rc.d scripts have been updated, so if you have a
1766 port installed with a script in /usr/local/etc/rc.d you can either
1767 hand-edit the rcvar= line, or reinstall the port.
1769 An easy way to handle the mass-update of /etc/rc.d:
1770 rm /etc/rc.d/* && mergemaster -i
1773 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1774 on the current CPU and prevents other threads from running.
1775 This behavior can be reverted using the kern.stop_scheduler_on_panic
1777 The new behavior can be incompatible with kern.sync_on_panic.
1780 The carp(4) facility has been changed significantly. Configuration
1781 of the CARP protocol via ifconfig(8) has changed, as well as format
1782 of CARP events submitted to devd(8) has changed. See manual pages
1783 for more information. The arpbalance feature of carp(4) is currently
1784 not supported anymore.
1786 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1787 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1788 need to be recompiled.
1791 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1795 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1796 explicitely support non-MPSAFE filesystems.
1797 It is on by default for all supported platform at this present
1801 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1802 i386 and pc98 GENERIC kernel configuration files.
1805 sysinstall has been removed
1808 The stable/9 branch created in subversion. This corresponds to the
1809 RELENG_9 branch in CVS.
1815 Avoid using make -j when upgrading. While generally safe, there are
1816 sometimes problems using -j to upgrade. If your upgrade fails with
1817 -j, please try again without -j. From time to time in the past there
1818 have been problems using -j with buildworld and/or installworld. This
1819 is especially true when upgrading between "distant" versions (eg one
1820 that cross a major release boundary or several minor releases, or when
1821 several months have passed on the -current branch).
1823 Sometimes, obscure build problems are the result of environment
1824 poisoning. This can happen because the make utility reads its
1825 environment when searching for values for global variables. To run
1826 your build attempts in an "environmental clean room", prefix all make
1827 commands with 'env -i '. See the env(1) manual page for more details.
1829 When upgrading from one major version to another it is generally best to
1830 upgrade to the latest code in the currently installed branch first, then
1831 do an upgrade to the new branch. This is the best-tested upgrade path,
1832 and has the highest probability of being successful. Please try this
1833 approach if you encounter problems with a major version upgrade. Since
1834 the stable 4.x branch point, one has generally been able to upgade from
1835 anywhere in the most recent stable branch to head / current (or even the
1836 last couple of stable branches). See the top of this file when there's
1839 When upgrading a live system, having a root shell around before
1840 installing anything can help undo problems. Not having a root shell
1841 around can lead to problems if pam has changed too much from your
1842 starting point to allow continued authentication after the upgrade.
1844 This file should be read as a log of events. When a later event changes
1845 information of a prior event, the prior event should not be deleted.
1846 Instead, a pointer to the entry with the new information should be
1847 placed in the old entry. Readers of this file should also sanity check
1848 older entries before relying on them blindly. Authors of new entries
1849 should write them with this in mind.
1853 When upgrading the boot ZFS pool to a new version, always follow
1856 1.) recompile and reinstall the ZFS boot loader and boot block
1857 (this is part of "make buildworld" and "make installworld")
1859 2.) update the ZFS boot block on your boot drive
1861 The following example updates the ZFS boot block on the first
1862 partition (freebsd-boot) of a GPT partitioned drive ada0:
1863 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1865 Non-boot pools do not need these updates.
1869 If you are updating from a prior version of FreeBSD (even one just
1870 a few days old), you should follow this procedure. It is the most
1871 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1873 make kernel-toolchain
1874 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1875 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1877 To test a kernel once
1878 ---------------------
1879 If you just want to boot a kernel once (because you are not sure
1880 if it works, or if you want to boot a known bad kernel to provide
1881 debugging information) run
1882 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1883 nextboot -k testkernel
1885 To rebuild everything and install it on the current system.
1886 -----------------------------------------------------------
1887 # Note: sometimes if you are running current you gotta do more than
1888 # is listed here if you are upgrading from a really old current.
1890 <make sure you have good level 0 dumps>
1892 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1893 make installkernel KERNCONF=YOUR_KERNEL_HERE
1895 <reboot in single user> [3]
1902 To cross-install current onto a separate partition
1903 --------------------------------------------------
1904 # In this approach we use a separate partition to hold
1905 # current's root, 'usr', and 'var' directories. A partition
1906 # holding "/", "/usr" and "/var" should be about 2GB in
1909 <make sure you have good level 0 dumps>
1912 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1913 <maybe newfs current's root partition>
1914 <mount current's root partition on directory ${CURRENT_ROOT}>
1915 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1916 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1917 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1918 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1919 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1920 <reboot into current>
1921 <do a "native" rebuild/install as described in the previous section>
1922 <maybe install compatibility libraries from ports/misc/compat*>
1926 To upgrade in-place from stable to current
1927 ----------------------------------------------
1928 <make sure you have good level 0 dumps>
1930 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1932 <reboot in single user> [3]
1939 Make sure that you've read the UPDATING file to understand the
1940 tweaks to various things you need. At this point in the life
1941 cycle of current, things change often and you are on your own
1942 to cope. The defaults can also change, so please read ALL of
1943 the UPDATING entries.
1945 Also, if you are tracking -current, you must be subscribed to
1946 freebsd-current@freebsd.org. Make sure that before you update
1947 your sources that you have read and understood all the recent
1948 messages there. If in doubt, please track -stable which has
1949 much fewer pitfalls.
1951 [1] If you have third party modules, such as vmware, you
1952 should disable them at this point so they don't crash your
1955 [3] From the bootblocks, boot -s, and then do
1960 adjkerntz -i # if CMOS is wall time
1961 Also, when doing a major release upgrade, it is required that
1962 you boot into single user mode to do the installworld.
1964 [4] Note: This step is non-optional. Failure to do this step
1965 can result in a significant reduction in the functionality of the
1966 system. Attempting to do it by hand is not recommended and those
1967 that pursue this avenue should read this file carefully, as well
1968 as the archives of freebsd-current and freebsd-hackers mailing lists
1969 for potential gotchas. The -U option is also useful to consider.
1970 See mergemaster(8) for more information.
1972 [5] Usually this step is a noop. However, from time to time
1973 you may need to do this if you get unknown user in the following
1974 step. It never hurts to do it all the time. You may need to
1975 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1976 install) after the buildworld before this step if you last updated
1977 from current before 20130425 or from -stable before 20130430.
1979 [6] This only deletes old files and directories. Old libraries
1980 can be deleted by "make delete-old-libs", but you have to make
1981 sure that no program is using those libraries anymore.
1983 [8] In order to have a kernel that can run the 4.x binaries needed to
1984 do an installworld, you must include the COMPAT_FREEBSD4 option in
1985 your kernel. Failure to do so may leave you with a system that is
1986 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1987 required to run the 5.x binaries on more recent kernels. And so on
1988 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1990 Make sure that you merge any new devices from GENERIC since the
1991 last time you updated your kernel config file.
1993 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1994 "?=" instead of the "=" assignment operator, so that buildworld can
1995 override the CPUTYPE if it needs to.
1997 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1998 not on the command line, or in /etc/make.conf. buildworld will
1999 warn if it is improperly defined.
2002 This file contains a list, in reverse chronological order, of major
2003 breakages in tracking -current. It is not guaranteed to be a complete
2004 list of such breakages, and only contains entries since September 23, 2011.
2005 If you need to see UPDATING entries from before that date, you will need
2006 to fetch an UPDATING file from an older FreeBSD release.
2008 Copyright information:
2010 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2012 Redistribution, publication, translation and use, with or without
2013 modification, in full or in part, in any form or format of this
2014 document are permitted without further permission from the author.
2016 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2017 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2018 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2019 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2020 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2021 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2022 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2023 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2024 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2025 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2026 POSSIBILITY OF SUCH DAMAGE.
2028 Contact Warner Losh if you have any questions about your use of