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