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