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 The SW_WATCHDOG option is no longer necessary to enable the
56 hardclock-based software watchdog if no hardware watchdog is
57 configured. As before, SW_WATCHDOG will cause the software
58 watchdog to be enabled even if a hardware watchdog is configured.
61 r326887 fixes the issue described in the 20171214 UPDATING entry.
62 r326888 flips the switch back to building GELI support always.
65 r362593 broke ZFS + GELI support for reasons unknown. However,
66 it also broke ZFS support generally, so GELI has been turned off
67 by default as the lesser evil in r326857. If you boot off ZFS and/or
68 GELI, it might not be a good time to update.
71 PowerPC users must update loader(8) by rebuilding world before
72 installing a new kernel, as the protocol connecting them has
73 changed. Without the update, loader metadata will not be passed
74 successfully to the kernel and users will have to enter their
75 root partition at the kernel mountroot prompt to continue booting.
76 Newer versions of loader can boot old kernels without issue.
79 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
80 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
81 to WITH/OUT_LOADER_GELI.
84 The naive and non-compliant support of posix_fallocate(2) in ZFS
85 has been removed as of r325320. The system call now returns EINVAL
86 when used on a ZFS file. Although the new behavior complies with the
87 standard, some consumers are not prepared to cope with it.
88 One known victim is lld prior to r325420.
91 Building in a FreeBSD src checkout will automatically create object
92 directories now rather than store files in the current directory if
93 'make obj' was not ran. Calling 'make obj' is no longer necessary.
94 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
95 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
99 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
100 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
101 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
102 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
103 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
104 The UNIFIED_OBJDIR option is a transitional feature that will be
105 removed for 12.0 release; please migrate to the new format for any
106 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
107 than hardcoding paths.
110 The native-xtools target no longer installs the files by default to the
111 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
112 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
115 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
116 options are changing from controlling the build if defined / undefined
117 to controlling the build with explicit 'yes' or 'no' values. They will
118 shift to WITH/WITHOUT options to match other options in the system.
121 libstand has turned into a private library for sys/boot use only.
122 It is no longer supported as a public interface outside of sys/boot.
125 The arm port has split armv6 into armv6 and armv7. armv7 is now
126 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
127 and are running a kernel from before r324363, you will need to add
128 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
131 When building multiple kernels using KERNCONF, non-existent KERNCONF
132 files will produce an error and buildkernel will fail. Previously
133 missing KERNCONF files silently failed giving no indication as to
134 why, only to subsequently discover during installkernel that the
135 desired kernel was never built in the first place.
138 The default serial number format for CTL LUNs has changed. This will
139 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
140 or iSCSI clients care about their LUNs' serial numbers. Users who
141 require serial number stability should hardcode serial numbers in
145 For 32-bit arm compiled for hard-float support, soft-floating point
146 binaries now always get their shared libraries from
147 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
148 /usr/libsoft also existed). Only users with a hard-float ld.so, but
149 soft-float everything else should be affected.
152 The geli password typed at boot is now hidden. To restore the previous
153 behavior, see geli(8) for configuration options.
156 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
157 sysctl values. Minor nit, but requires a rebuild of both world/kernel
161 "make check" behavior (made in ^/head@r295380) has been changed to
162 execute from a limited sandbox, as opposed to executing from
166 - The "beforecheck" and "aftercheck" targets are now specified.
167 - ${CHECKDIR} (added in commit noted above) has been removed.
168 - Legacy behavior can be enabled by setting
169 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
171 If the limited sandbox mode is enabled, "make check" will execute
172 "make distribution", then install, execute the tests, and clean up the
173 sandbox if successful.
175 The "make distribution" and "make install" targets are typically run as
176 root to set appropriate permissions and ownership at installation time.
177 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
178 environment if executing "make check" with limited sandbox mode using
179 an unprivileged user.
182 Since the switch to GPT disk labels, fsck for UFS/FFS has been
183 unable to automatically find alternate superblocks. As of r322297,
184 the information needed to find alternate superblocks has been
185 moved to the end of the area reserved for the boot block.
186 Filesystems created with a newfs of this vintage or later
187 will create the recovery information. If you have a filesystem
188 created prior to this change and wish to have a recovery block
189 created for your filesystem, you can do so by running fsck in
190 forground mode (i.e., do not use the -p or -y options). As it
191 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
192 to which you should answer yes.
195 As of r321665, an NFSv4 server configuration that services
196 Kerberos mounts or clients that do not support the uid/gid in
197 owner/owner_group string capability, must explicitly enable
198 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
199 machine's /etc/rc.conf file.
202 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
203 Please see the 20141231 entry below for information about prerequisites
204 and upgrading, if you are not already using clang 3.5.0 or higher.
207 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
208 r-commands (rlogin, rsh, etc.) to be built with the base system.
211 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
212 a very major ABI incompatible change, so users of FreeBSD/powerpc must
213 be careful when performing source upgrades. It is best to run
214 'make installworld' from an alternate root system, either a live
215 CD/memory stick, or a temporary root partition. Additionally, all ports
216 must be recompiled. powerpc64 is largely unaffected, except in the case
217 of 32-bit compatibility. All 32-bit binaries will be affected.
220 Forward compatibility for the "ino64" project have been committed. This
221 will allow most new binaries to run on older kernels in a limited
222 fashion. This prevents many of the common foot-shooting actions in the
223 upgrade as well as the limited ability to roll back the kernel across
224 the ino64 upgrade. Complicated use cases may not work properly, though
225 enough simpler ones work to allow recovery in most situations.
228 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
229 if you require the GPL compiler.
232 The internal ABI used for communication between the NFS kernel modules
233 was changed by r320085, so __FreeBSD_version was bumped to
234 ensure all the NFS related modules are updated together.
237 The ABI of struct event was changed by extending the data
238 member to 64bit and adding ext fields. For upgrade, same
239 precautions as for the entry 20170523 "ino64" must be
243 The GNU roff toolchain has been removed from base. To render manpages
244 which are not supported by mandoc(1), man(1) can fallback on GNU roff
245 from ports (and recommends to install it).
246 To render roff(7) documents, consider using GNU roff from ports or the
247 heirloom doctools roff toolchain from ports via pkg install groff or
248 via pkg install heirloom-doctools.
251 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
252 smaller runtime footprint builds. This is useful for embedded systems
253 which only require one chipset support.
255 If you load it as a module, make sure this is in /boot/loader.conf:
259 This will load the HAL, all chip/RF backends and if_ath_pci.
260 If you have if_ath_pci in /boot/loader.conf, ensure it is after
261 if_ath or it will not load any HAL chipset support.
263 If you want to selectively load things (eg on ye cheape ARM/MIPS
264 platforms where RAM is at a premium) you should:
267 * load the chip modules in question
268 * load ath_rate, ath_dfs
270 * load if_ath_pci and/or if_ath_ahb depending upon your particular
271 bus bind type - this is where probe/attach is done.
273 For further comments/feedback, poke adrian@ .
276 The "ino64" 64-bit inode project has been committed, which extends
277 a number of types to 64 bits. Upgrading in place requires care and
278 adherence to the documented upgrade procedure.
280 If using a custom kernel configuration ensure that the
281 COMPAT_FREEBSD11 option is included (as during the upgrade the
282 system will be running the ino64 kernel with the existing world).
284 For the safest in-place upgrade begin by removing previous build
285 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
286 full procedure documented below under the heading "To rebuild
287 everything and install it on the current system." Specifically,
288 a reboot is required after installing the new kernel before
292 The NATM framework including the en(4), fatm(4), hatm(4), and
293 patm(4) devices has been removed. Consumers should plan a
294 migration before the end-of-life date for FreeBSD 11.
297 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
298 diff has not been implemented, if those are needed a newer version of
299 GNU diff is available via the diffutils package under the gdiff name.
302 As of r316810 for ipfilter, keep frags is no longer assumed when
303 keep state is specified in a rule. r316810 aligns ipfilter with
304 documentation in man pages separating keep frags from keep state.
305 This allows keep state to be specified without forcing keep frags
306 and allows keep frags to be specified independently of keep state.
307 To maintain previous behaviour, also specify keep frags with
308 keep state (as documented in ipf.conf.5).
311 arm64 builds now use the base system LLD 4.0.0 linker by default,
312 instead of requiring that the aarch64-binutils port or package be
313 installed. To continue using aarch64-binutils, set
314 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
317 The UDP optimization in entry 20160818 that added the sysctl
318 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
319 packets will no longer be treated as L3 broadcast packets.
322 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
323 use any explicitly assigned loopback address available in the jail
324 instead of using the first assigned address of the jail.
327 The ctl.ko module no longer implements the iSCSI target frontend:
328 cfiscsi.ko does instead.
330 If building cfiscsi.ko as a kernel module, the module can be loaded
331 via one of the following methods:
332 - `cfiscsi_load="YES"` in loader.conf(5).
333 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
334 - ctladm(8)/ctld(8), when compiled with iSCSI support
335 (`WITH_ISCSI=yes` in src.conf(5))
337 Please see cfiscsi(4) for more details.
340 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
341 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
342 same source (previously, the dependency of mmcsd.ko on mmc.ko was
343 missing, but mmcsd.ko now will refuse to load if it is incompatible
347 The syntax of ipfw(8) named states was changed to avoid ambiguity.
348 If you have used named states in the firewall rules, you need to modify
349 them after installworld and before rebooting. Now named states must
350 be prefixed with colon.
353 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
354 removed as the userland we provide cannot use them. The KMS version
355 (sys/dev/drm2) supports the same hardware.
358 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
359 Please see the 20141231 entry below for information about prerequisites
360 and upgrading, if you are not already using clang 3.5.0 or higher.
363 The code that provides support for ZFS .zfs/ directory functionality
364 has been reimplemented. It's not possible now to create a snapshot
365 by mkdir under .zfs/snapshot/. That should be the only user visible
369 EISA bus support has been removed. The WITH_EISA option is no longer
373 MCA bus support has been removed.
376 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
377 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
380 The EM_MULTIQUEUE kernel configuration option is deprecated now that
381 the em(4) driver conforms to iflib specifications.
384 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
385 IFLIB. If you have a custom kernel configuration that excludes em(4)
386 but you use igb(4), you need to re-add em(4) to your custom configuration.
389 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
390 Please see the 20141231 entry below for information about prerequisites
391 and upgrading, if you are not already using clang 3.5.0 or higher.
394 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
395 Please see the 20141231 entry below for information about prerequisites
396 and upgrading, if you are not already using clang 3.5.0 or higher.
399 The layout of the pmap structure has changed for powerpc to put the pmap
400 statistics at the front for all CPU variations. libkvm(3) and all tools
401 that link against it need to be recompiled.
404 isl(4) and cyapa(4) drivers now require a new driver,
405 chromebook_platform(4), to work properly on Chromebook-class hardware.
406 On other types of hardware the drivers may need to be configured using
407 device hints. Please see the corresponding manual pages for details.
410 The urtwn(4) driver was merged into rtwn(4) and now consists of
411 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
413 Also, firmware for RTL8188CE was renamed due to possible name
414 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
417 GNU rcs has been removed from base. It is available as packages:
418 - rcs: Latest GPLv3 GNU rcs version.
419 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
423 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
424 modules now requires that the kernel configuration contain the
425 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
428 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
429 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
432 Relocatable object files with the extension of .So have been renamed
433 to use an extension of .pico instead. The purpose of this change is
434 to avoid a name clash with shared libraries on case-insensitive file
435 systems. On those file systems, foo.So is the same file as foo.so.
438 GNU rcs has been turned off by default. It can (temporarily) be built
439 again by adding WITH_RCS knob in src.conf.
440 Otherwise, GNU rcs is available from packages:
441 - rcs: Latest GPLv3 GNU rcs version.
442 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
445 The backup_uses_rcs functionality has been removed from rc.subr.
448 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
449 two separate components, QUEUE_MACRO_DEBUG_TRACE and
450 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
451 QUEUE_MACRO_DEBUG behavior.
454 r304787 changed some ioctl interfaces between the iSCSI userspace
455 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
456 rebuilt to work with new kernels. __FreeBSD_version has been bumped
460 The UDP receive code has been updated to only treat incoming UDP
461 packets that were addressed to an L2 broadcast address as L3
462 broadcast packets. It is not expected that this will affect any
463 standards-conforming UDP application. The new behaviour can be
464 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
468 Remove the openbsd_poll system call.
469 __FreeBSD_version has been bumped because of this.
472 The libc stub for the pipe(2) system call has been replaced with
473 a wrapper that calls the pipe2(2) system call and the pipe(2)
474 system call is now only implemented by the kernels that include
475 "options COMPAT_FREEBSD10" in their config file (this is the
476 default). Users should ensure that this option is enabled in
477 their kernel or upgrade userspace to r302092 before upgrading their
481 CAM will now strip leading spaces from SCSI disks' serial numbers.
482 This will affect users who create UFS filesystems on SCSI disks using
483 those disk's diskid device nodes. For example, if /etc/fstab
484 previously contained a line like
485 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
486 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
487 transforms like gmirror may also be affected. ZFS users should
491 The bitstring(3) API has been updated with new functionality and
492 improved performance. But it is binary-incompatible with the old API.
493 Objects built with the new headers may not be linked against objects
494 built with the old headers.
497 The brk and sbrk functions have been removed from libc on arm64.
498 Binutils from ports has been updated to not link to these
499 functions and should be updated to the latest version before
500 installing a new libc.
503 The armv6 port now defaults to hard float ABI. Limited support
504 for running both hardfloat and soft float on the same system
505 is available using the libraries installed with -DWITH_LIBSOFT.
506 This has only been tested as an upgrade path for installworld
507 and packages may fail or need manual intervention to run. New
508 packages will be needed.
510 To update an existing self-hosted armv6hf system, you must add
511 TARGET_ARCH=armv6 on the make command line for both the build
512 and the install steps.
515 Kernel modules compiled outside of a kernel build now default to
516 installing to /boot/modules instead of /boot/kernel. Many kernel
517 modules built this way (such as those in ports) already overrode
518 KMODDIR explicitly to install into /boot/modules. However,
519 manually building and installing a module from /sys/modules will
520 now install to /boot/modules instead of /boot/kernel.
523 The CAM I/O scheduler has been committed to the kernel. There should be
524 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
525 list of known rogues that claim support for this but actually corrupt
526 data is believed to be complete, be on the lookout for data
527 corruption. The known rogue list is believed to be complete:
529 o Crucial MX100, M550 drives with MU01 firmware.
530 o Micron M510 and M550 drives with MU01 firmware.
531 o Micron M500 prior to MU07 firmware
532 o Samsung 830, 840, and 850 all firmwares
533 o FCCT M500 all firmwares
535 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
536 with working NCQ TRIM. For Micron branded drives, see your sales rep for
537 updated firmware. Black listed drives will work correctly because these
538 drives work correctly so long as no NCQ TRIMs are sent to them. Given
539 this list is the same as found in Linux, it's believed there are no
540 other rogues in the market place. All other models from the above
543 To be safe, if you are at all concerned, you can quirk each of your
544 drives to prevent NCQ from being sent by setting:
545 kern.cam.ada.X.quirks="0x2"
546 in loader.conf. If the drive requires the 4k sector quirk, set the
550 The FAST_DEPEND build option has been removed and its functionality is
551 now the one true way. The old mkdep(1) style of 'make depend' has
552 been removed. See 20160311 for further details.
555 Resource range types have grown from unsigned long to uintmax_t. All
556 drivers, and anything using libdevinfo, need to be recompiled.
559 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
560 builds. It no longer runs mkdep(1) during 'make depend', and the
561 'make depend' stage can safely be skipped now as it is auto ran
562 when building 'make all' and will generate all SRCS and DPSRCS before
563 building anything else. Dependencies are gathered at compile time with
564 -MF flags kept in separate .depend files per object file. Users should
565 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
569 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
570 kernel modules. Therefore, if you load any kernel modules at boot time,
571 please install the boot loaders after you install the kernel, but before
575 make kernel KERNCONF=YOUR_KERNEL_HERE
576 make -C sys/boot install
577 <reboot in single user>
579 Then follow the usual steps, described in the General Notes section,
583 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
584 see the 20141231 entry below for information about prerequisites and
585 upgrading, if you are not already using clang 3.5.0 or higher.
588 The AIO subsystem is now a standard part of the kernel. The
589 VFS_AIO kernel option and aio.ko kernel module have been removed.
590 Due to stability concerns, asynchronous I/O requests are only
591 permitted on sockets and raw disks by default. To enable
592 asynchronous I/O requests on all file types, set the
593 vfs.aio.enable_unsafe sysctl to a non-zero value.
596 The ELF object manipulation tool objcopy is now provided by the
597 ELF Tool Chain project rather than by GNU binutils. It should be a
598 drop-in replacement, with the addition of arm64 support. The
599 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
600 to obtain the GNU version if necessary.
603 Building ZFS pools on top of zvols is prohibited by default. That
604 feature has never worked safely; it's always been prone to deadlocks.
605 Using a zvol as the backing store for a VM guest's virtual disk will
606 still work, even if the guest is using ZFS. Legacy behavior can be
607 restored by setting vfs.zfs.vol.recursive=1.
610 The NONE and HPN patches has been removed from OpenSSH. They are
611 still available in the security/openssh-portable port.
614 With the addition of ypldap(8), a new _ypldap user is now required
615 during installworld. "mergemaster -p" can be used to add the user
616 prior to installworld, as documented in the handbook.
619 The tftp loader (pxeboot) now uses the option root-path directive. As a
620 consequence it no longer looks for a pxeboot.4th file on the tftp
621 server. Instead it uses the regular /boot infrastructure as with the
625 The code to start recording plug and play data into the modules has
626 been committed. While the old tools will properly build a new kernel,
627 a number of warnings about "unknown metadata record 4" will be produced
628 for an older kldxref. To avoid such warnings, make sure to rebuild
629 the kernel toolchain (or world). Make sure that you have r292078 or
630 later when trying to build 292077 or later before rebuilding.
633 Debug data files are now built by default with 'make buildworld' and
634 installed with 'make installworld'. This facilitates debugging but
635 requires more disk space both during the build and for the installed
636 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
640 r291527 changed the internal interface between the nfsd.ko and
641 nfscommon.ko modules. As such, they must both be upgraded to-gether.
642 __FreeBSD_version has been bumped because of this.
645 Add support for unicode collation strings leads to a change of
646 order of files listed by ls(1) for example. To get back to the old
647 behaviour, set LC_COLLATE environment variable to "C".
649 Databases administrators will need to reindex their databases given
650 collation results will be different.
652 Due to a bug in install(1) it is recommended to remove the ancient
653 locales before running make installworld.
655 rm -rf /usr/share/locale/*
658 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
659 libcrypto.so.7 or libssl.so.7 must be recompiled.
662 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
663 Kernel modules isp_2400_multi and isp_2500_multi were removed and
664 should be replaced with isp_2400 and isp_2500 modules respectively.
667 The build previously allowed using 'make -n' to not recurse into
668 sub-directories while showing what commands would be executed, and
669 'make -n -n' to recursively show commands. Now 'make -n' will recurse
670 and 'make -N' will not.
673 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
674 and etcupdate will now use this file. A custom sendmail.cf is now
675 updated via this mechanism rather than via installworld. If you had
676 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
677 want to remove the exclusion or change it to "always install".
678 /etc/mail/sendmail.cf is now managed the same way regardless of
679 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
680 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
683 Compatibility shims for legacy ATA device names have been removed.
684 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
685 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
686 environment variables, /dev/ad* and /dev/ar* symbolic links.
689 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
690 Please see the 20141231 entry below for information about prerequisites
691 and upgrading, if you are not already using clang 3.5.0 or higher.
694 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
695 and renamed from .symbols to .debug. This reduces the size requirements
696 on the boot partition or file system and provides consistency with
697 userland debug files.
699 When using the supported kernel installation method the
700 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
701 as is done with /boot/kernel.
703 Developers wishing to maintain the historical behavior of installing
704 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
707 The wireless drivers had undergone changes that remove the 'parent
708 interface' from the ifconfig -l output. The rc.d network scripts
709 used to check presence of a parent interface in the list, so old
710 scripts would fail to start wireless networking. Thus, etcupdate(3)
711 or mergemaster(8) run is required after kernel update, to update your
712 rc.d scripts in /etc.
715 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
716 These configurations are now automatically interpreted as
717 'scrub fragment reassemble'.
720 Kernel-loadable modules for the random(4) device are back. To use
721 them, the kernel must have
724 options RANDOM_LOADABLE
726 kldload(8) can then be used to load random_fortuna.ko
727 or random_yarrow.ko. Please note that due to the indirect
728 function calls that the loadable modules need to provide,
729 the build-in variants will be slightly more efficient.
731 The random(4) kernel option RANDOM_DUMMY has been retired due to
732 unpopularity. It was not all that useful anyway.
735 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
736 Control over building the ELF Tool Chain tools is now provided by
737 the WITHOUT_TOOLCHAIN knob.
740 The polarity of Pulse Per Second (PPS) capture events with the
741 uart(4) driver has been corrected. Prior to this change the PPS
742 "assert" event corresponded to the trailing edge of a positive PPS
743 pulse and the "clear" event was the leading edge of the next pulse.
745 As the width of a PPS pulse in a typical GPS receiver is on the
746 order of 1 millisecond, most users will not notice any significant
747 difference with this change.
749 Anyone who has compensated for the historical polarity reversal by
750 configuring a negative offset equal to the pulse width will need to
751 remove that workaround.
754 The default group assigned to /dev/dri entries has been changed
755 from 'wheel' to 'video' with the id of '44'. If you want to have
756 access to the dri devices please add yourself to the video group
759 # pw groupmod video -m $USER
762 The menu.rc and loader.rc files will now be replaced during
763 upgrades. Please migrate local changes to menu.rc.local and
764 loader.rc.local instead.
767 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
768 strings and strip have been removed. The src.conf(5) knob
769 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
772 As ZFS requires more kernel stack pages than is the default on some
773 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
774 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
776 Please consider using 'options KSTACK_PAGES=X' where X is greater
777 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
780 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
781 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
782 default, i.e., they will not contain "::". For example, instead
783 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
784 to have a more specific match, such as different map entries for
785 IPv6:0:0 vs IPv6:0. This change requires that configuration
786 data (including maps, files, classes, custom ruleset, etc.) must
787 use the same format, so make certain such configuration data is
788 upgrading. As a very simple check search for patterns like
789 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
790 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
791 the cf option UseCompressedIPv6Addresses.
794 The default kernel entropy-processing algorithm is now
795 Fortuna, replacing Yarrow.
797 Assuming you have 'device random' in your kernel config
798 file, the configurations allow a kernel option to override
799 this default. You may choose *ONE* of:
801 options RANDOM_YARROW # Legacy /dev/random algorithm.
802 options RANDOM_DUMMY # Blocking-only driver.
804 If you have neither, you get Fortuna. For most people,
805 read no further, Fortuna will give a /dev/random that works
806 like it always used to, and the difference will be irrelevant.
808 If you remove 'device random', you get *NO* kernel-processed
809 entropy at all. This may be acceptable to folks building
810 embedded systems, but has complications. Carry on reading,
811 and it is assumed you know what you need.
813 *PLEASE* read random(4) and random(9) if you are in the
814 habit of tweaking kernel configs, and/or if you are a member
815 of the embedded community, wanting specific and not-usual
816 behaviour from your security subsystems.
818 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
819 random', you will NOT have a functioning /dev/random, and
820 many cryptographic features will not work, including SSH.
821 You may also find strange behaviour from the random(3) set
822 of library functions, in particular sranddev(3), srandomdev(3)
823 and arc4random(3). The reason for this is that the KERN_ARND
824 sysctl only returns entropy if it thinks it has some to
825 share, and with RANDOM_DUMMY or no 'device random' this
829 An additional fix for the issue described in the 20150614 sendmail
830 entry below has been committed in revision 284717.
833 FreeBSD's old make (fmake) has been removed from the system. It is
834 available as the devel/fmake port or via pkg install fmake.
837 The fix for the issue described in the 20150614 sendmail entry
838 below has been committed in revision 284436. The work
839 around described in that entry is no longer needed unless the
840 default setting is overridden by a confDH_PARAMETERS configuration
841 setting of '5' or pointing to a 512 bit DH parameter file.
844 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
845 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
846 and devel/kyua to version 0.20+ and adjust any calling code to work
847 with Kyuafile and kyua.
850 The import of openssl to address the FreeBSD-SA-15:10.openssl
851 security advisory includes a change which rejects handshakes
852 with DH parameters below 768 bits. sendmail releases prior
853 to 8.15.2 (not yet released), defaulted to a 512 bit
854 DH parameter setting for client connections. To work around
855 this interoperability, sendmail can be configured to use a
856 2048 bit DH parameter by:
858 1. Edit /etc/mail/`hostname`.mc
859 2. If a setting for confDH_PARAMETERS does not exist or
860 exists and is set to a string beginning with '5',
862 3. If a setting for confDH_PARAMETERS exists and is set to
863 a file path, create a new file with:
864 openssl dhparam -out /path/to/file 2048
865 4. Rebuild the .cf file:
866 cd /etc/mail/; make; make install
868 cd /etc/mail/; make restart
870 A sendmail patch is coming, at which time this file will be
874 Generation of legacy formatted entries have been disabled by default
875 in pwd_mkdb(8), as all base system consumers of the legacy formatted
876 entries were converted to use the new format by default when the new,
877 machine independent format have been added and supported since FreeBSD
880 Please see the pwd_mkdb(8) manual page for further details.
883 Clang and llvm have been upgraded to 3.6.1 release. Please see the
884 20141231 entry below for information about prerequisites and upgrading,
885 if you are not already using 3.5.0 or higher.
888 TI platform code switched to using vendor DTS files and this update
889 may break existing systems running on Beaglebone, Beaglebone Black,
892 - dtb files should be regenerated/reinstalled. Filenames are the
893 same but content is different now
894 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
895 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
896 addressing scheme is now pin 25 on /dev/gpioc3.
897 - Pandaboard: /etc/ttys should be updated, serial console device is
898 now /dev/ttyu2, not /dev/ttyu0
901 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
902 If you need the GNU extension from groff soelim(1), install groff
903 from package: pkg install groff, or via ports: textproc/groff.
906 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
907 defined in symlink(7); previously symlinks were silently ignored.
910 The const qualifier has been removed from iconv(3) to comply with
911 POSIX. The ports tree is aware of this from r384038 onwards.
914 Libraries specified by LIBADD in Makefiles must have a corresponding
915 DPADD_<lib> variable to ensure correct dependencies. This is now
916 enforced in src.libnames.mk.
919 From legacy ata(4) driver was removed support for SATA controllers
920 supported by more functional drivers ahci(4), siis(4) and mvs(4).
921 Kernel modules ataahci and ataadaptec were removed completely,
922 replaced by ahci and mvs modules respectively.
925 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
926 the 20141231 entry below for information about prerequisites and
927 upgrading, if you are not already using 3.5.0 or higher.
930 The 32-bit PowerPC kernel has been changed to a position-independent
931 executable. This can only be booted with a version of loader(8)
932 newer than January 31, 2015, so make sure to update both world and
933 kernel before rebooting.
936 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
937 but before r278950, the RNG was not seeded properly. Immediately
938 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
939 ssh keys or openssl keys) that were generated w/ a kernel from that
940 range. This does not affect programs that directly used /dev/random
941 or /dev/urandom. All userland uses of arc4random(3) are affected.
944 The autofs(4) ABI was changed in order to restore binary compatibility
945 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
949 The powerpc64 kernel has been changed to a position-independent
950 executable. This can only be booted with a new version of loader(8),
951 so make sure to update both world and kernel before rebooting.
954 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
955 only release, no new features have been added. Please see the 20141231
956 entry below for information about prerequisites and upgrading, if you
957 are not already using 3.5.0.
960 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
961 taken from the ELF Tool Chain project rather than GNU binutils. They
962 should be drop-in replacements, with the addition of arm64 support.
963 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
964 binutils tools, if necessary. See 20150805 for updated information.
967 The default Unbound configuration now enables remote control
968 using a local socket. Users who have already enabled the
969 local_unbound service should regenerate their configuration
970 by running "service local_unbound setup" as root.
973 The GNU texinfo and GNU info pages have been removed.
974 To be able to view GNU info pages please install texinfo from ports.
977 Clang, llvm and lldb have been upgraded to 3.5.0 release.
979 As of this release, a prerequisite for building clang, llvm and lldb is
980 a C++11 capable compiler and C++11 standard library. This means that to
981 be able to successfully build the cross-tools stage of buildworld, with
982 clang as the bootstrap compiler, your system compiler or cross compiler
983 should either be clang 3.3 or later, or gcc 4.8 or later, and your
984 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
987 On any standard FreeBSD 10.x or 11.x installation, where clang and
988 libc++ are on by default (that is, on x86 or arm), this should work out
991 On 9.x installations where clang is enabled by default, e.g. on x86 and
992 powerpc, libc++ will not be enabled by default, so libc++ should be
993 built (with clang) and installed first. If both clang and libc++ are
994 missing, build clang first, then use it to build libc++.
996 On 8.x and earlier installations, upgrade to 9.x first, and then follow
997 the instructions for 9.x above.
999 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1000 default, and do not build clang.
1002 Many embedded systems are resource constrained, and will not be able to
1003 build clang in a reasonable time, or in some cases at all. In those
1004 cases, cross building bootable systems on amd64 is a workaround.
1006 This new version of clang introduces a number of new warnings, of which
1007 the following are most likely to appear:
1011 This warns in two cases, for both C and C++:
1012 * When the code is trying to take the absolute value of an unsigned
1013 quantity, which is effectively a no-op, and almost never what was
1014 intended. The code should be fixed, if at all possible. If you are
1015 sure that the unsigned quantity can be safely cast to signed, without
1016 loss of information or undefined behavior, you can add an explicit
1017 cast, or disable the warning.
1019 * When the code is trying to take an absolute value, but the called
1020 abs() variant is for the wrong type, which can lead to truncation.
1021 If you want to disable the warning instead of fixing the code, please
1022 make sure that truncation will not occur, or it might lead to unwanted
1025 -Wtautological-undefined-compare and
1026 -Wundefined-bool-conversion
1028 These warn when C++ code is trying to compare 'this' against NULL, while
1029 'this' should never be NULL in well-defined C++ code. However, there is
1030 some legacy (pre C++11) code out there, which actively abuses this
1031 feature, which was less strictly defined in previous C++ versions.
1033 Squid and openjdk do this, for example. The warning can be turned off
1034 for C++98 and earlier, but compiling the code in C++11 mode might result
1035 in unexpected behavior; for example, the parts of the program that are
1036 unreachable could be optimized away.
1039 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1040 kernel sources have been removed. The .h files remain, since some
1041 utilities include them. This will need to be fixed later.
1042 If "mount -t oldnfs ..." is attempted, it will fail.
1043 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1044 the utilities will report errors.
1047 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1048 directories to top level SUBDIR variable when their parent
1049 directory is included in LOCAL_DIRS. Users with build systems with
1050 such hierarchies and without SUBDIR entries in the parent
1051 directory Makefiles should add them or add the directories to
1055 faith(4) and faithd(8) have been removed from the base system. Faith
1056 has been obsolete for a very long time.
1059 vt(4), the new console driver, is enabled by default. It brings
1060 support for Unicode and double-width characters, as well as
1061 support for UEFI and integration with the KMS kernel video
1064 You may need to update your console settings in /etc/rc.conf,
1065 most probably the keymap. During boot, /etc/rc.d/syscons will
1066 indicate what you need to do.
1068 vt(4) still has issues and lacks some features compared to
1069 syscons(4). See the wiki for up-to-date information:
1070 https://wiki.freebsd.org/Newcons
1072 If you want to keep using syscons(4), you can do so by adding
1073 the following line to /boot/loader.conf:
1077 pjdfstest has been integrated into kyua as an opt-in test suite.
1078 Please see share/doc/pjdfstest/README for more details on how to
1082 gperf has been removed from the base system for architectures
1083 that use clang. Ports that require gperf will obtain it from the
1087 pjdfstest has been moved from tools/regression/pjdfstest to
1091 At svn r271982, The default linux compat kernel ABI has been adjusted
1092 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1093 update. If you wish to continue using the linux-f10 compat ports,
1094 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1095 encouraged to update their linux-compat packages to linux-c6 during
1096 their next update cycle.
1099 The ofwfb driver, used to provide a graphics console on PowerPC when
1100 using vt(4), no longer allows mmap() of all physical memory. This
1101 will prevent Xorg on PowerPC with some ATI graphics cards from
1102 initializing properly unless x11-servers/xorg-server is updated to
1106 The xdev targets have been converted to using TARGET and
1107 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1110 The default unbound configuration has been modified to address
1111 issues with reverse lookups on networks that use private
1112 address ranges. If you use the local_unbound service, run
1113 "service local_unbound setup" as root to regenerate your
1114 configuration, then "service local_unbound reload" to load the
1118 The GNU texinfo and GNU info pages are not built and installed
1119 anymore, WITH_INFO knob has been added to allow to built and install
1121 UPDATE: see 20150102 entry on texinfo's removal
1124 The GNU readline library is now an INTERNALLIB - that is, it is
1125 statically linked into consumers (GDB and variants) in the base
1126 system, and the shared library is no longer installed. The
1127 devel/readline port is available for third party software that
1131 The Itanium architecture (ia64) has been removed from the list of
1132 known architectures. This is the first step in the removal of the
1136 Commit r268115 has added NFSv4.1 server support, merged from
1137 projects/nfsv4.1-server. Since this includes changes to the
1138 internal interfaces between the NFS related modules, a full
1139 build of the kernel and modules will be necessary.
1140 __FreeBSD_version has been bumped.
1143 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1144 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1145 which differs from the behaviour controlled by this knob.)
1148 Maximal length of the serial number in CTL was increased from 16 to
1149 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1150 and ctld, need to be rebuilt to work with a new kernel.
1153 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1154 1 respectively to match the upstream numbers. They were out of
1155 sync because, when they were originally added to FreeBSD, the
1156 upstream versions were not respected. These libraries are private
1157 and not yet built by default, so renumbering them should be a
1158 non-issue. However, unclean source trees will yield broken test
1159 programs once the operator executes "make delete-old-libs" after a
1160 "make installworld".
1162 Additionally, the atf-sh binary was made private by moving it into
1163 /usr/libexec/. Already-built shell test programs will keep the
1164 path to the old binary so they will break after "make delete-old"
1167 If you are using WITH_TESTS=yes (not the default), wipe the object
1168 tree and rebuild from scratch to prevent spurious test failures.
1169 This is only needed once: the misnumbered libraries and misplaced
1170 binaries have been added to OptionalObsoleteFiles.inc so they will
1171 be removed during a clean upgrade.
1174 Clang and llvm have been upgraded to 3.4.1 release.
1177 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1178 be removed to avoid issues in the future (and has been added to
1182 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1183 past, it affected all builds that used the bsd.*.mk files. The old
1184 behavior was a bug, but people may have relied upon it. To get this
1185 behavior back, you can .include /etc/src.conf from /etc/make.conf
1186 (which is still global and isn't changed). This also changes the
1187 behavior of incremental builds inside the tree of individual
1188 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1189 Although this has survived make universe and some upgrade scenarios,
1190 other upgrade scenarios may have broken. At least one form of
1191 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1192 as well... In cases where MAKESYSPATH isn't working with this
1193 setting, you'll need to set it to the full path to your tree.
1195 One side effect of all this cleaning up is that bsd.compiler.mk
1196 is no longer implicitly included by bsd.own.mk. If you wish to
1197 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1201 The lindev device has been removed since /dev/full has been made a
1202 standard device. __FreeBSD_version has been bumped.
1205 The knob WITHOUT_VI was added to the base system, which controls
1206 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1207 in order to reorder files share/termcap and didn't build ex(1) as a
1208 build tool, so building/installing with WITH_VI is highly advised for
1209 build hosts for older releases.
1211 This issue has been fixed in stable/9 and stable/10 in r277022 and
1212 r276991, respectively.
1215 The YES_HESIOD knob has been removed. It has been obsolete for
1216 a decade. Please move to using WITH_HESIOD instead or your builds
1217 will silently lack HESIOD.
1220 The uart(4) driver has been changed with respect to its handling
1221 of the low-level console. Previously the uart(4) driver prevented
1222 any process from changing the baudrate or the CLOCAL and HUPCL
1223 control flags. By removing the restrictions, operators can make
1224 changes to the serial console port without having to reboot.
1225 However, when getty(8) is started on the serial device that is
1226 associated with the low-level console, a misconfigured terminal
1227 line in /etc/ttys will now have a real impact.
1228 Before upgrading the kernel, make sure that /etc/ttys has the
1229 serial console device configured as 3wire without baudrate to
1230 preserve the previous behaviour. E.g:
1231 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1234 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1235 to improve performance. To re-enable it, if needed, run rpcbind
1236 with command line option -W.
1239 Switched back to the GPL dtc compiler due to updates in the upstream
1240 dts files not being supported by the BSDL dtc compiler. You will need
1241 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1242 may result while building dtb files during a kernel build if you fail
1243 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1246 Clang and llvm have been upgraded to 3.4 release.
1249 The nve(4) driver has been removed. Please use the nfe(4) driver
1250 for NVIDIA nForce MCP Ethernet adapters instead.
1253 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1254 This could cause certain C++ applications using shared libraries built
1255 against the previous version of libc++ to crash. The incompatibility
1256 has now been fixed, but any C++ applications or shared libraries built
1257 between r261283 and r261801 should be recompiled.
1260 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1261 capability mode support. Please note that enabling the feature in
1262 kernel is still highly recommended.
1265 OpenSSH is now built with sandbox support, and will use sandbox as
1266 the default privilege separation method. This requires Capsicum
1267 capability mode support in kernel.
1270 The libelf and libdwarf libraries have been updated to newer
1271 versions from upstream. Shared library version numbers for
1272 these two libraries were bumped. Any ports or binaries
1273 requiring these two libraries should be recompiled.
1274 __FreeBSD_version is bumped to 1100006.
1277 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1278 instead of providing an explicit one, this would prevent such
1279 Makefile from providing its own Kyuafile in the future during
1280 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1281 intervention is needed to clean an objdir if you use NO_CLEAN:
1282 # find /usr/obj -name Kyuafile | xargs rm -f
1285 The behavior of gss_pseudo_random() for the krb5 mechanism
1286 has changed, for applications requesting a longer random string
1287 than produced by the underlying enctype's pseudo-random() function.
1288 In particular, the random string produced from a session key of
1289 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1290 be different at the 17th octet and later, after this change.
1291 The counter used in the PRF+ construction is now encoded as a
1292 big-endian integer in accordance with RFC 4402.
1293 __FreeBSD_version is bumped to 1100004.
1296 The WITHOUT_ATF build knob has been removed and its functionality
1297 has been subsumed into the more generic WITHOUT_TESTS. If you were
1298 using the former to disable the build of the ATF libraries, you
1299 should change your settings to use the latter.
1302 The default version of mtree is nmtree which is obtained from
1303 NetBSD. The output is generally the same, but may vary
1304 slightly. If you found you need identical output adding
1305 "-F freebsd9" to the command line should do the trick. For the
1306 time being, the old mtree is available as fmtree.
1309 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1310 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1311 1.1.4_8 and verify bsdyml not linked in, before running "make
1313 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1315 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1318 The stable/10 branch has been created in subversion from head
1322 The rc.d/jail script has been updated to support jail(8)
1323 configuration file. The "jail_<jname>_*" rc.conf(5) variables
1324 for per-jail configuration are automatically converted to
1325 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
1326 This is transparently backward compatible. See below about some
1327 incompatibilities and rc.conf(5) manual page for more details.
1329 These variables are now deprecated in favor of jail(8) configuration
1330 file. One can use "rc.d/jail config <jname>" command to generate
1331 a jail(8) configuration file in /var/run/jail.<jname>.conf without
1332 running the jail(8) utility. The default pathname of the
1333 configuration file is /etc/jail.conf and can be specified by
1334 using $jail_conf or $jail_<jname>_conf variables.
1336 Please note that jail_devfs_ruleset accepts an integer at
1337 this moment. Please consider to rewrite the ruleset name
1341 BIND has been removed from the base system. If all you need
1342 is a local resolver, simply enable and start the local_unbound
1343 service instead. Otherwise, several versions of BIND are
1344 available in the ports tree. The dns/bind99 port is one example.
1346 With this change, nslookup(1) and dig(1) are no longer in the base
1347 system. Users should instead use host(1) and drill(1) which are
1348 in the base system. Alternatively, nslookup and dig can
1349 be obtained by installing the dns/bind-tools port.
1352 With the addition of unbound(8), a new unbound user is now
1353 required during installworld. "mergemaster -p" can be used to
1354 add the user prior to installworld, as documented in the handbook.
1357 OpenSSH is now built with DNSSEC support, and will by default
1358 silently trust signed SSHFP records. This can be controlled with
1359 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1360 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1363 The GNU Compiler Collection and C++ standard library (libstdc++)
1364 are no longer built by default on platforms where clang is the system
1365 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1366 options in src.conf.
1369 The PROCDESC kernel option is now part of the GENERIC kernel
1370 configuration and is required for the rwhod(8) to work.
1371 If you are using custom kernel configuration, you should include
1375 The API and ABI related to the Capsicum framework was modified
1376 in backward incompatible way. The userland libraries and programs
1377 have to be recompiled to work with the new kernel. This includes the
1378 following libraries and programs, but the whole buildworld is
1379 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1380 kdump, procstat, rwho, rwhod, uniq.
1383 AES-NI intrinsic support has been added to gcc. The AES-NI module
1384 has been updated to use this support. A new gcc is required to build
1385 the aesni module on both i386 and amd64.
1388 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1389 Thus "device padlock_rng" and "device rdrand_rng" should be
1390 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1393 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1394 enables just the iconv* functionality and is now on by default.
1395 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1396 compatibility. Set WITHOUT_ICONV to build the old way.
1397 If you have been using WITH_ICONV before, you will very likely
1398 need to turn on WITH_LIBICONV_COMPAT.
1401 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1402 Illumos origin, including ZFS. If you have INVARIANTS in your
1403 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1405 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1406 locks if WITNESS option was set. Because that generated a lot of
1407 witness(9) reports and all of them were believed to be false
1408 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1409 can be used to achieve the previous behavior.
1412 Timer values in IPv6 data structures now use time_uptime instead
1413 of time_second. Although this is not a user-visible functional
1414 change, userland utilities which directly use them---ndp(8),
1415 rtadvd(8), and rtsold(8) in the base system---need to be updated
1416 to r253970 or later.
1419 find -delete can now delete the pathnames given as arguments,
1420 instead of only files found below them or if the pathname did
1421 not contain any slashes. Formerly, the following error message
1424 find: -delete: <path>: relative path potentially not safe
1426 Deleting the pathnames given as arguments can be prevented
1427 without error messages using -mindepth 1 or by changing
1428 directory and passing "." as argument to find. This works in the
1429 old as well as the new version of find.
1432 Behavior of devfs rules path matching has been changed.
1433 Pattern is now always matched against fully qualified devfs
1434 path and slash characters must be explicitly matched by
1435 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1436 subdirectories must be reviewed.
1439 The default ARM ABI has changed to the ARM EABI. The old ABI is
1440 incompatible with the ARM EABI and all programs and modules will
1441 need to be rebuilt to work with a new kernel.
1443 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1445 NOTE: Support for the old ABI will be removed in the future and
1446 users are advised to upgrade.
1449 pkg_install has been disconnected from the build if you really need it
1450 you should add WITH_PKGTOOLS in your src.conf(5).
1453 Most of network statistics structures were changed to be able
1454 keep 64-bits counters. Thus all tools, that work with networking
1455 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1458 Fix a bug that allowed a tracing process (e.g. gdb) to write
1459 to a memory-mapped file in the traced process's address space
1460 even if neither the traced process nor the tracing process had
1461 write access to that file.
1464 CVS has been removed from the base system. An exact copy
1465 of the code is available from the devel/cvs port.
1468 Some people report the following error after the switch to bmake:
1470 make: illegal option -- J
1471 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1473 *** [buildworld] Error code 2
1475 this likely due to an old instance of make in
1476 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1477 which src/Makefile will use that blindly, if it exists, so if
1478 you see the above error:
1480 rm -rf `make -V MAKEPATH`
1485 Use bmake by default.
1486 Whereas before one could choose to build with bmake via
1487 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1488 make. The goal is to remove these knobs for 10-RELEASE.
1490 It is worth noting that bmake (like gmake) treats the command
1491 line as the unit of failure, rather than statements within the
1492 command line. Thus '(cd some/where && dosomething)' is safer
1493 than 'cd some/where; dosomething'. The '()' allows consistent
1494 behavior in parallel build.
1497 Fix a bug that allows NFS clients to issue READDIR on files.
1500 The WITHOUT_IDEA option has been removed because
1501 the IDEA patent expired.
1504 The sysctl which controls TRIM support under ZFS has been renamed
1505 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1509 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1510 rather than creating it's own in the temporary directory in
1511 order allow access to bootstrapped versions of tools such as
1512 install and mtree. When upgrading from version of FreeBSD where
1513 the install command does not support -l, you will need to
1514 install a new mergemaster command if mergemaster -p is required.
1515 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1519 Legacy ATA stack, disabled and replaced by new CAM-based one since
1520 FreeBSD 9.0, completely removed from the sources. Kernel modules
1521 atadisk and atapi*, user-level tools atacontrol and burncd are
1522 removed. Kernel option `options ATA_CAM` is now permanently enabled
1526 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1527 and socketpair(2). Software, in particular Kerberos, may
1528 automatically detect and use these during building. The resulting
1529 binaries will not work on older kernels.
1532 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1533 information, see the respective 20130304 entry).
1536 Recent commits to callout(9) changed the size of struct callout,
1537 so the KBI is probably heavily disturbed. Also, some functions
1538 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1539 by macros. Every kernel module using it won't load, so rebuild
1542 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1543 but does not initialize by default (because of the new CTL_DISABLE
1544 option) to save memory. To re-enable it, remove the CTL_DISABLE
1545 option from the kernel config file or set kern.cam.ctl.disable=0
1546 in /boot/loader.conf.
1549 The ctl device has been disabled in GENERIC for i386 and amd64.
1550 This was done due to the extra memory being allocated at system
1551 initialisation time by the ctl driver which was only used if
1552 a CAM target device was created. This makes a FreeBSD system
1553 unusable on 128MB or less of RAM.
1556 A new compression method (lz4) has been merged to -HEAD. Please
1557 refer to zpool-features(7) for more information.
1559 Please refer to the "ZFS notes" section of this file for information
1560 on upgrading boot ZFS pools.
1563 A BSD-licensed patch(1) variant has been added and is installed
1564 as bsdpatch, being the GNU version the default patch.
1565 To inverse the logic and use the BSD-licensed one as default,
1566 while having the GNU version installed as gnupatch, rebuild
1567 and install world with the WITH_BSD_PATCH knob set.
1570 Due to the use of the new -l option to install(1) during build
1571 and install, you must take care not to directly set the INSTALL
1572 make variable in your /etc/make.conf, /etc/src.conf, or on the
1573 command line. If you wish to use the -C flag for all installs
1574 you may be able to add INSTALL+=-C to /etc/make.conf or
1578 The install(1) option -M has changed meaning and now takes an
1579 argument that is a file or path to append logs to. In the
1580 unlikely event that -M was the last option on the command line
1581 and the command line contained at least two files and a target
1582 directory the first file will have logs appended to it. The -M
1583 option served little practical purpose in the last decade so its
1584 use is expected to be extremely rare.
1587 After switching to Clang as the default compiler some users of ZFS
1588 on i386 systems started to experience stack overflow kernel panics.
1589 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1592 GEOM_LABEL now mangles label names read from file system metadata.
1593 Mangling affect labels containing spaces, non-printable characters,
1594 '%' or '"'. Device names in /etc/fstab and other places may need to
1598 By default, only the 10 most recent kernel dumps will be saved. To
1599 restore the previous behaviour (no limit on the number of kernel dumps
1600 stored in the dump directory) add the following line to /etc/rc.conf:
1605 With the addition of auditdistd(8), a new auditdistd user is now
1606 required during installworld. "mergemaster -p" can be used to
1607 add the user prior to installworld, as documented in the handbook.
1610 The sin6_scope_id member variable in struct sockaddr_in6 is now
1611 filled by the kernel before passing the structure to the userland via
1612 sysctl or routing socket. This means the KAME-specific embedded scope
1613 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1614 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1615 __FreeBSD_version is bumped to 1000025.
1618 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1619 This means that the world and kernel will be compiled with clang
1620 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1621 and /usr/bin/cpp. To disable this behavior and revert to building
1622 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1623 of current may need to bootstrap WITHOUT_CLANG first if the clang
1624 build fails (its compatibility window doesn't extend to the 9 stable
1628 The IPFIREWALL_FORWARD kernel option has been removed. Its
1629 functionality now turned on by default.
1632 The ZERO_COPY_SOCKET kernel option has been removed and
1633 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1634 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1635 mechanism which is not safe and may result in kernel crashes.
1636 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1637 driver supports disposeable external page sized mbuf storage.
1638 Proper replacements for both zero-copy mechanisms are under
1639 consideration and will eventually lead to complete removal
1640 of the two kernel options.
1643 The IPv4 network stack has been converted to network byte
1644 order. The following modules need to be recompiled together
1645 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1646 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1649 Support for non-MPSAFE filesystems was removed from VFS. The
1650 VFS_VERSION was bumped, all filesystem modules shall be
1654 All the non-MPSAFE filesystems have been disconnected from
1655 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1656 portalfs, smbfs, xfs.
1659 The interface cloning API and ABI has changed. The following
1660 modules need to be recompiled together with kernel:
1661 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1662 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1663 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1666 The sdhci driver was split in two parts: sdhci (generic SD Host
1667 Controller logic) and sdhci_pci (actual hardware driver).
1668 No kernel config modifications are required, but if you
1669 load sdhc as a module you must switch to sdhci_pci instead.
1672 Import the FUSE kernel and userland support into base system.
1675 The GNU sort(1) program has been removed since the BSD-licensed
1676 sort(1) has been the default for quite some time and no serious
1677 problems have been reported. The corresponding WITH_GNU_SORT
1681 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1682 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1686 The net80211(4) ABI has been changed to allow for improved driver
1687 PS-POLL and power-save support. All wireless drivers need to be
1688 recompiled to work with the new kernel.
1691 The random(4) support for the VIA hardware random number
1692 generator (`PADLOCK') is no longer enabled unconditionally.
1693 Add the padlock_rng device in the custom kernel config if
1694 needed. The GENERIC kernels on i386 and amd64 do include the
1695 device, so the change only affects the custom kernel
1699 The pf(4) packet filter ABI has been changed. pfctl(8) and
1700 snmp_pf module need to be recompiled to work with new kernel.
1703 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1704 to -HEAD. Pools that have empty_bpobj in active state can not be
1705 imported read-write with ZFS implementations that do not support
1706 this feature. For more information read the zpool-features(5)
1710 The sparc64 ZFS loader has been changed to no longer try to auto-
1711 detect ZFS providers based on diskN aliases but now requires these
1712 to be explicitly listed in the OFW boot-device environment variable.
1715 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1716 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1717 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1720 The following sysctls and tunables have been renamed for consistency
1721 with other variables:
1722 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1723 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1726 The sort utility has been replaced with BSD sort. For now, GNU sort
1727 is also available as "gnusort" or the default can be set back to
1728 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1729 installed as "bsdsort".
1732 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1733 Starting with this version the old system of ZFS pool versioning
1734 is superseded by "feature flags". This concept enables forward
1735 compatibility against certain future changes in functionality of ZFS
1736 pools. The first read-only compatible "feature flag" for ZFS pools
1737 is named "com.delphix:async_destroy". For more information
1738 read the new zpool-features(5) manual page.
1739 Please refer to the "ZFS notes" section of this file for information
1740 on upgrading boot ZFS pools.
1743 The malloc(3) implementation embedded in libc now uses sources imported
1744 as contrib/jemalloc. The most disruptive API change is to
1745 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1746 delete it prior to installworld, and optionally re-create it using the
1747 new format after rebooting. See malloc.conf(5) for details
1748 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1752 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1753 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1754 now spelled mips. This is to aid compatibility with third-party
1755 software that expects this naming scheme in uname(3). Little-endian
1756 settings are unchanged. If you are updating a big-endian mips64 machine
1757 from before this change, you may need to set MACHINE_ARCH=mips64 in
1758 your environment before the new build system will recognize your machine.
1761 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1765 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1766 nullfs(5) did not pass through all behaviours to the underlying layer,
1767 as a result if we bound to a socket on the lower layer we could connect
1768 only to the lower path; if we bound to the upper layer we could connect
1769 only to the upper path. The new behavior is one can connect to both the
1770 lower and the upper paths regardless what layer path one binds to.
1773 The getifaddrs upgrade path broken with 20111215 has been restored.
1774 If you have upgraded in between 20111215 and 20120209 you need to
1775 recompile libc again with your kernel. You still need to recompile
1776 world to be able to configure CARP but this restriction already
1777 comes from 20111215.
1780 The set_rcvar() function has been removed from /etc/rc.subr. All
1781 base and ports rc.d scripts have been updated, so if you have a
1782 port installed with a script in /usr/local/etc/rc.d you can either
1783 hand-edit the rcvar= line, or reinstall the port.
1785 An easy way to handle the mass-update of /etc/rc.d:
1786 rm /etc/rc.d/* && mergemaster -i
1789 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1790 on the current CPU and prevents other threads from running.
1791 This behavior can be reverted using the kern.stop_scheduler_on_panic
1793 The new behavior can be incompatible with kern.sync_on_panic.
1796 The carp(4) facility has been changed significantly. Configuration
1797 of the CARP protocol via ifconfig(8) has changed, as well as format
1798 of CARP events submitted to devd(8) has changed. See manual pages
1799 for more information. The arpbalance feature of carp(4) is currently
1800 not supported anymore.
1802 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1803 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1804 need to be recompiled.
1807 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1811 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1812 explicitely support non-MPSAFE filesystems.
1813 It is on by default for all supported platform at this present
1817 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1818 i386 and pc98 GENERIC kernel configuration files.
1821 sysinstall has been removed
1824 The stable/9 branch created in subversion. This corresponds to the
1825 RELENG_9 branch in CVS.
1831 Avoid using make -j when upgrading. While generally safe, there are
1832 sometimes problems using -j to upgrade. If your upgrade fails with
1833 -j, please try again without -j. From time to time in the past there
1834 have been problems using -j with buildworld and/or installworld. This
1835 is especially true when upgrading between "distant" versions (eg one
1836 that cross a major release boundary or several minor releases, or when
1837 several months have passed on the -current branch).
1839 Sometimes, obscure build problems are the result of environment
1840 poisoning. This can happen because the make utility reads its
1841 environment when searching for values for global variables. To run
1842 your build attempts in an "environmental clean room", prefix all make
1843 commands with 'env -i '. See the env(1) manual page for more details.
1845 When upgrading from one major version to another it is generally best to
1846 upgrade to the latest code in the currently installed branch first, then
1847 do an upgrade to the new branch. This is the best-tested upgrade path,
1848 and has the highest probability of being successful. Please try this
1849 approach if you encounter problems with a major version upgrade. Since
1850 the stable 4.x branch point, one has generally been able to upgade from
1851 anywhere in the most recent stable branch to head / current (or even the
1852 last couple of stable branches). See the top of this file when there's
1855 When upgrading a live system, having a root shell around before
1856 installing anything can help undo problems. Not having a root shell
1857 around can lead to problems if pam has changed too much from your
1858 starting point to allow continued authentication after the upgrade.
1860 This file should be read as a log of events. When a later event changes
1861 information of a prior event, the prior event should not be deleted.
1862 Instead, a pointer to the entry with the new information should be
1863 placed in the old entry. Readers of this file should also sanity check
1864 older entries before relying on them blindly. Authors of new entries
1865 should write them with this in mind.
1869 When upgrading the boot ZFS pool to a new version, always follow
1872 1.) recompile and reinstall the ZFS boot loader and boot block
1873 (this is part of "make buildworld" and "make installworld")
1875 2.) update the ZFS boot block on your boot drive
1877 The following example updates the ZFS boot block on the first
1878 partition (freebsd-boot) of a GPT partitioned drive ada0:
1879 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1881 Non-boot pools do not need these updates.
1885 If you are updating from a prior version of FreeBSD (even one just
1886 a few days old), you should follow this procedure. It is the most
1887 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1889 make kernel-toolchain
1890 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1891 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1893 To test a kernel once
1894 ---------------------
1895 If you just want to boot a kernel once (because you are not sure
1896 if it works, or if you want to boot a known bad kernel to provide
1897 debugging information) run
1898 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1899 nextboot -k testkernel
1901 To rebuild everything and install it on the current system.
1902 -----------------------------------------------------------
1903 # Note: sometimes if you are running current you gotta do more than
1904 # is listed here if you are upgrading from a really old current.
1906 <make sure you have good level 0 dumps>
1908 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1909 make installkernel KERNCONF=YOUR_KERNEL_HERE
1911 <reboot in single user> [3]
1918 To cross-install current onto a separate partition
1919 --------------------------------------------------
1920 # In this approach we use a separate partition to hold
1921 # current's root, 'usr', and 'var' directories. A partition
1922 # holding "/", "/usr" and "/var" should be about 2GB in
1925 <make sure you have good level 0 dumps>
1928 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1929 <maybe newfs current's root partition>
1930 <mount current's root partition on directory ${CURRENT_ROOT}>
1931 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1932 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1933 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1934 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1935 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1936 <reboot into current>
1937 <do a "native" rebuild/install as described in the previous section>
1938 <maybe install compatibility libraries from ports/misc/compat*>
1942 To upgrade in-place from stable to current
1943 ----------------------------------------------
1944 <make sure you have good level 0 dumps>
1946 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1948 <reboot in single user> [3]
1955 Make sure that you've read the UPDATING file to understand the
1956 tweaks to various things you need. At this point in the life
1957 cycle of current, things change often and you are on your own
1958 to cope. The defaults can also change, so please read ALL of
1959 the UPDATING entries.
1961 Also, if you are tracking -current, you must be subscribed to
1962 freebsd-current@freebsd.org. Make sure that before you update
1963 your sources that you have read and understood all the recent
1964 messages there. If in doubt, please track -stable which has
1965 much fewer pitfalls.
1967 [1] If you have third party modules, such as vmware, you
1968 should disable them at this point so they don't crash your
1971 [3] From the bootblocks, boot -s, and then do
1976 adjkerntz -i # if CMOS is wall time
1977 Also, when doing a major release upgrade, it is required that
1978 you boot into single user mode to do the installworld.
1980 [4] Note: This step is non-optional. Failure to do this step
1981 can result in a significant reduction in the functionality of the
1982 system. Attempting to do it by hand is not recommended and those
1983 that pursue this avenue should read this file carefully, as well
1984 as the archives of freebsd-current and freebsd-hackers mailing lists
1985 for potential gotchas. The -U option is also useful to consider.
1986 See mergemaster(8) for more information.
1988 [5] Usually this step is a noop. However, from time to time
1989 you may need to do this if you get unknown user in the following
1990 step. It never hurts to do it all the time. You may need to
1991 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1992 install) after the buildworld before this step if you last updated
1993 from current before 20130425 or from -stable before 20130430.
1995 [6] This only deletes old files and directories. Old libraries
1996 can be deleted by "make delete-old-libs", but you have to make
1997 sure that no program is using those libraries anymore.
1999 [8] In order to have a kernel that can run the 4.x binaries needed to
2000 do an installworld, you must include the COMPAT_FREEBSD4 option in
2001 your kernel. Failure to do so may leave you with a system that is
2002 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2003 required to run the 5.x binaries on more recent kernels. And so on
2004 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2006 Make sure that you merge any new devices from GENERIC since the
2007 last time you updated your kernel config file.
2009 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2010 "?=" instead of the "=" assignment operator, so that buildworld can
2011 override the CPUTYPE if it needs to.
2013 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2014 not on the command line, or in /etc/make.conf. buildworld will
2015 warn if it is improperly defined.
2018 This file contains a list, in reverse chronological order, of major
2019 breakages in tracking -current. It is not guaranteed to be a complete
2020 list of such breakages, and only contains entries since September 23, 2011.
2021 If you need to see UPDATING entries from before that date, you will need
2022 to fetch an UPDATING file from an older FreeBSD release.
2024 Copyright information:
2026 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2028 Redistribution, publication, translation and use, with or without
2029 modification, in full or in part, in any form or format of this
2030 document are permitted without further permission from the author.
2032 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2033 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2034 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2035 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2036 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2037 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2038 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2039 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2040 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2041 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2042 POSSIBILITY OF SUCH DAMAGE.
2044 Contact Warner Losh if you have any questions about your use of