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 Support for Arcnet networks has been removed. If you have device
56 arcnet or device cm in your kernel config file they must be
60 Support for FDDI networks has been removed. If you have device
61 fddi or device fpa in your kernel config file they must be
65 In addition to supporting RFC 3164 formatted messages, the
66 syslogd(8) service is now capable of parsing RFC 5424 formatted
67 log messages. The main benefit of using RFC 5424 is that clients
68 may now send log messages with timestamps containing year numbers,
69 microseconds and time zone offsets.
71 Similarly, the syslog(3) C library function has been altered to
72 send RFC 5424 formatted messages to the local system logging
73 daemon. On systems using syslogd(8), this change should have no
74 negative impact, as long as syslogd(8) and the C library are
75 updated at the same time. On systems using a different system
76 logging daemon, it may be necessary to make configuration
77 adjustments, depending on the software used.
79 When using syslog-ng, add the 'syslog-protocol' flag to local
80 input sources to enable parsing of RFC 5424 formatted messages:
83 unix-dgram("/var/run/log" flags(syslog-protocol));
86 When using rsyslog, disable the 'SysSock.UseSpecialParser' option
87 of the 'imuxsock' module to let messages be processed by the
88 regular RFC 3164/5424 parsing pipeline:
90 module(load="imuxsock" SysSock.UseSpecialParser="off")
92 Do note that these changes only affect communication between local
93 applications and syslogd(8). The format that syslogd(8) uses to
94 store messages on disk or forward messages to other systems
95 remains unchanged. syslogd(8) still uses RFC 3164 for these
96 purposes. Options to customize this behaviour will be added in the
97 future. Utilities that process log files stored in /var/log are
98 thus expected to continue to function as before.
100 __FreeBSD_version has been incremented to 1200061 to denote this
104 Support for token ring networks has been removed. If you
105 have "device token" in your kernel config you should remove
106 it. No device drivers supported token ring.
109 makefs was modified to be able to tag ISO9660 El Torito boot catalog
110 entries as EFI instead of overloading the i386 tag as done previously.
111 The amd64 mkisoimages.sh script used to build amd64 ISO images for
112 release was updated to use this. This may mean that makefs must be
113 updated before "make cdrom" can be run in the release directory. This
114 should be as simple as:
116 $ cd $SRCDIR/usr.sbin/makefs
117 $ make depend all install
120 FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
121 now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
122 Co-existance for the transition period will come shortly. Booting is a
123 complex environment and test coverage for Lua-enabled loaders has been
124 thin, so it would be prudent to assume it might not work and make
125 provisions for backup boot methods.
128 devmatch functionality has been turned on in devd. It will automatically
129 load drivers for unattached devices. This may cause unexpected drivers to
130 be loaded. Please report any problems to current@ and imp@freebsd.org.
133 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
134 6.0.0. Please see the 20141231 entry below for information about
135 prerequisites and upgrading, if you are not already using clang 3.5.0
139 LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
140 This means it is used to link the kernel and userland libraries and
141 executables, but is not yet installed as /usr/bin/ld by default.
143 To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
144 WITHOUT_LLD_BOOTSTRAP=yes
147 On i386, pmtimer has been removed. Its functionality has been folded
148 into apm. It was a no-op on ACPI in current for a while now (but was still
149 needed on i386 in FreeBSD 11 and earlier). Users may need to remove it
150 from kernel config files.
153 The use of RSS hash from the network card aka flowid has been
154 disabled by default for lagg(4) as it's currently incompatible with
155 the lacp and loadbalance protocols.
157 This can be re-enabled by setting the following in loader.conf:
158 net.link.lagg.default_use_flowid="1"
161 The SW_WATCHDOG option is no longer necessary to enable the
162 hardclock-based software watchdog if no hardware watchdog is
163 configured. As before, SW_WATCHDOG will cause the software
164 watchdog to be enabled even if a hardware watchdog is configured.
167 r326887 fixes the issue described in the 20171214 UPDATING entry.
168 r326888 flips the switch back to building GELI support always.
171 r362593 broke ZFS + GELI support for reasons unknown. However,
172 it also broke ZFS support generally, so GELI has been turned off
173 by default as the lesser evil in r326857. If you boot off ZFS and/or
174 GELI, it might not be a good time to update.
177 PowerPC users must update loader(8) by rebuilding world before
178 installing a new kernel, as the protocol connecting them has
179 changed. Without the update, loader metadata will not be passed
180 successfully to the kernel and users will have to enter their
181 root partition at the kernel mountroot prompt to continue booting.
182 Newer versions of loader can boot old kernels without issue.
185 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
186 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
187 to WITH/OUT_LOADER_GELI.
190 The naive and non-compliant support of posix_fallocate(2) in ZFS
191 has been removed as of r325320. The system call now returns EINVAL
192 when used on a ZFS file. Although the new behavior complies with the
193 standard, some consumers are not prepared to cope with it.
194 One known victim is lld prior to r325420.
197 Building in a FreeBSD src checkout will automatically create object
198 directories now rather than store files in the current directory if
199 'make obj' was not ran. Calling 'make obj' is no longer necessary.
200 This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
201 /etc/src-env.conf (not /etc/src.conf), or passing the option in the
205 The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
206 builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
207 /usr/obj/<srcdir>/<arch>. This behavior can be changed to the old
208 format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
209 the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
210 The UNIFIED_OBJDIR option is a transitional feature that will be
211 removed for 12.0 release; please migrate to the new format for any
212 tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
213 than hardcoding paths.
216 The native-xtools target no longer installs the files by default to the
217 OBJDIR. Use the native-xtools-install target with a DESTDIR to install
218 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
221 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
222 options are changing from controlling the build if defined / undefined
223 to controlling the build with explicit 'yes' or 'no' values. They will
224 shift to WITH/WITHOUT options to match other options in the system.
227 libstand has turned into a private library for sys/boot use only.
228 It is no longer supported as a public interface outside of sys/boot.
231 The arm port has split armv6 into armv6 and armv7. armv7 is now
232 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
233 and are running a kernel from before r324363, you will need to add
234 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
237 When building multiple kernels using KERNCONF, non-existent KERNCONF
238 files will produce an error and buildkernel will fail. Previously
239 missing KERNCONF files silently failed giving no indication as to
240 why, only to subsequently discover during installkernel that the
241 desired kernel was never built in the first place.
244 The default serial number format for CTL LUNs has changed. This will
245 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
246 or iSCSI clients care about their LUNs' serial numbers. Users who
247 require serial number stability should hardcode serial numbers in
251 For 32-bit arm compiled for hard-float support, soft-floating point
252 binaries now always get their shared libraries from
253 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
254 /usr/libsoft also existed). Only users with a hard-float ld.so, but
255 soft-float everything else should be affected.
258 The geli password typed at boot is now hidden. To restore the previous
259 behavior, see geli(8) for configuration options.
262 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
263 sysctl values. Minor nit, but requires a rebuild of both world/kernel
267 "make check" behavior (made in ^/head@r295380) has been changed to
268 execute from a limited sandbox, as opposed to executing from
272 - The "beforecheck" and "aftercheck" targets are now specified.
273 - ${CHECKDIR} (added in commit noted above) has been removed.
274 - Legacy behavior can be enabled by setting
275 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
277 If the limited sandbox mode is enabled, "make check" will execute
278 "make distribution", then install, execute the tests, and clean up the
279 sandbox if successful.
281 The "make distribution" and "make install" targets are typically run as
282 root to set appropriate permissions and ownership at installation time.
283 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
284 environment if executing "make check" with limited sandbox mode using
285 an unprivileged user.
288 Since the switch to GPT disk labels, fsck for UFS/FFS has been
289 unable to automatically find alternate superblocks. As of r322297,
290 the information needed to find alternate superblocks has been
291 moved to the end of the area reserved for the boot block.
292 Filesystems created with a newfs of this vintage or later
293 will create the recovery information. If you have a filesystem
294 created prior to this change and wish to have a recovery block
295 created for your filesystem, you can do so by running fsck in
296 foreground mode (i.e., do not use the -p or -y options). As it
297 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
298 to which you should answer yes.
301 As of r321665, an NFSv4 server configuration that services
302 Kerberos mounts or clients that do not support the uid/gid in
303 owner/owner_group string capability, must explicitly enable
304 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
305 machine's /etc/rc.conf file.
308 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
309 Please see the 20141231 entry below for information about prerequisites
310 and upgrading, if you are not already using clang 3.5.0 or higher.
313 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
314 r-commands (rlogin, rsh, etc.) to be built with the base system.
317 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
318 a very major ABI incompatible change, so users of FreeBSD/powerpc must
319 be careful when performing source upgrades. It is best to run
320 'make installworld' from an alternate root system, either a live
321 CD/memory stick, or a temporary root partition. Additionally, all ports
322 must be recompiled. powerpc64 is largely unaffected, except in the case
323 of 32-bit compatibility. All 32-bit binaries will be affected.
326 Forward compatibility for the "ino64" project have been committed. This
327 will allow most new binaries to run on older kernels in a limited
328 fashion. This prevents many of the common foot-shooting actions in the
329 upgrade as well as the limited ability to roll back the kernel across
330 the ino64 upgrade. Complicated use cases may not work properly, though
331 enough simpler ones work to allow recovery in most situations.
334 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
335 if you require the GPL compiler.
338 The internal ABI used for communication between the NFS kernel modules
339 was changed by r320085, so __FreeBSD_version was bumped to
340 ensure all the NFS related modules are updated together.
343 The ABI of struct event was changed by extending the data
344 member to 64bit and adding ext fields. For upgrade, same
345 precautions as for the entry 20170523 "ino64" must be
349 The GNU roff toolchain has been removed from base. To render manpages
350 which are not supported by mandoc(1), man(1) can fallback on GNU roff
351 from ports (and recommends to install it).
352 To render roff(7) documents, consider using GNU roff from ports or the
353 heirloom doctools roff toolchain from ports via pkg install groff or
354 via pkg install heirloom-doctools.
357 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
358 smaller runtime footprint builds. This is useful for embedded systems
359 which only require one chipset support.
361 If you load it as a module, make sure this is in /boot/loader.conf:
365 This will load the HAL, all chip/RF backends and if_ath_pci.
366 If you have if_ath_pci in /boot/loader.conf, ensure it is after
367 if_ath or it will not load any HAL chipset support.
369 If you want to selectively load things (eg on ye cheape ARM/MIPS
370 platforms where RAM is at a premium) you should:
373 * load the chip modules in question
374 * load ath_rate, ath_dfs
376 * load if_ath_pci and/or if_ath_ahb depending upon your particular
377 bus bind type - this is where probe/attach is done.
379 For further comments/feedback, poke adrian@ .
382 The "ino64" 64-bit inode project has been committed, which extends
383 a number of types to 64 bits. Upgrading in place requires care and
384 adherence to the documented upgrade procedure.
386 If using a custom kernel configuration ensure that the
387 COMPAT_FREEBSD11 option is included (as during the upgrade the
388 system will be running the ino64 kernel with the existing world).
390 For the safest in-place upgrade begin by removing previous build
391 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
392 full procedure documented below under the heading "To rebuild
393 everything and install it on the current system." Specifically,
394 a reboot is required after installing the new kernel before
398 The NATM framework including the en(4), fatm(4), hatm(4), and
399 patm(4) devices has been removed. Consumers should plan a
400 migration before the end-of-life date for FreeBSD 11.
403 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
404 diff has not been implemented, if those are needed a newer version of
405 GNU diff is available via the diffutils package under the gdiff name.
408 As of r316810 for ipfilter, keep frags is no longer assumed when
409 keep state is specified in a rule. r316810 aligns ipfilter with
410 documentation in man pages separating keep frags from keep state.
411 This allows keep state to be specified without forcing keep frags
412 and allows keep frags to be specified independently of keep state.
413 To maintain previous behaviour, also specify keep frags with
414 keep state (as documented in ipf.conf.5).
417 arm64 builds now use the base system LLD 4.0.0 linker by default,
418 instead of requiring that the aarch64-binutils port or package be
419 installed. To continue using aarch64-binutils, set
420 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
423 The UDP optimization in entry 20160818 that added the sysctl
424 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
425 packets will no longer be treated as L3 broadcast packets.
428 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
429 use any explicitly assigned loopback address available in the jail
430 instead of using the first assigned address of the jail.
433 The ctl.ko module no longer implements the iSCSI target frontend:
434 cfiscsi.ko does instead.
436 If building cfiscsi.ko as a kernel module, the module can be loaded
437 via one of the following methods:
438 - `cfiscsi_load="YES"` in loader.conf(5).
439 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
440 - ctladm(8)/ctld(8), when compiled with iSCSI support
441 (`WITH_ISCSI=yes` in src.conf(5))
443 Please see cfiscsi(4) for more details.
446 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
447 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
448 same source (previously, the dependency of mmcsd.ko on mmc.ko was
449 missing, but mmcsd.ko now will refuse to load if it is incompatible
453 The syntax of ipfw(8) named states was changed to avoid ambiguity.
454 If you have used named states in the firewall rules, you need to modify
455 them after installworld and before rebooting. Now named states must
456 be prefixed with colon.
459 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
460 removed as the userland we provide cannot use them. The KMS version
461 (sys/dev/drm2) supports the same hardware.
464 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
465 Please see the 20141231 entry below for information about prerequisites
466 and upgrading, if you are not already using clang 3.5.0 or higher.
469 The code that provides support for ZFS .zfs/ directory functionality
470 has been reimplemented. It's not possible now to create a snapshot
471 by mkdir under .zfs/snapshot/. That should be the only user visible
475 EISA bus support has been removed. The WITH_EISA option is no longer
479 MCA bus support has been removed.
482 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
483 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
486 The EM_MULTIQUEUE kernel configuration option is deprecated now that
487 the em(4) driver conforms to iflib specifications.
490 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
491 IFLIB. If you have a custom kernel configuration that excludes em(4)
492 but you use igb(4), you need to re-add em(4) to your custom configuration.
495 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
496 Please see the 20141231 entry below for information about prerequisites
497 and upgrading, if you are not already using clang 3.5.0 or higher.
500 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
501 Please see the 20141231 entry below for information about prerequisites
502 and upgrading, if you are not already using clang 3.5.0 or higher.
505 The layout of the pmap structure has changed for powerpc to put the pmap
506 statistics at the front for all CPU variations. libkvm(3) and all tools
507 that link against it need to be recompiled.
510 isl(4) and cyapa(4) drivers now require a new driver,
511 chromebook_platform(4), to work properly on Chromebook-class hardware.
512 On other types of hardware the drivers may need to be configured using
513 device hints. Please see the corresponding manual pages for details.
516 The urtwn(4) driver was merged into rtwn(4) and now consists of
517 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
519 Also, firmware for RTL8188CE was renamed due to possible name
520 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
523 GNU rcs has been removed from base. It is available as packages:
524 - rcs: Latest GPLv3 GNU rcs version.
525 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
529 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
530 modules now requires that the kernel configuration contain the
531 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
534 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
535 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
538 Relocatable object files with the extension of .So have been renamed
539 to use an extension of .pico instead. The purpose of this change is
540 to avoid a name clash with shared libraries on case-insensitive file
541 systems. On those file systems, foo.So is the same file as foo.so.
544 GNU rcs has been turned off by default. It can (temporarily) be built
545 again by adding WITH_RCS knob in src.conf.
546 Otherwise, GNU rcs is available from packages:
547 - rcs: Latest GPLv3 GNU rcs version.
548 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
551 The backup_uses_rcs functionality has been removed from rc.subr.
554 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
555 two separate components, QUEUE_MACRO_DEBUG_TRACE and
556 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
557 QUEUE_MACRO_DEBUG behavior.
560 r304787 changed some ioctl interfaces between the iSCSI userspace
561 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
562 rebuilt to work with new kernels. __FreeBSD_version has been bumped
566 The UDP receive code has been updated to only treat incoming UDP
567 packets that were addressed to an L2 broadcast address as L3
568 broadcast packets. It is not expected that this will affect any
569 standards-conforming UDP application. The new behaviour can be
570 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
574 Remove the openbsd_poll system call.
575 __FreeBSD_version has been bumped because of this.
578 The libc stub for the pipe(2) system call has been replaced with
579 a wrapper that calls the pipe2(2) system call and the pipe(2)
580 system call is now only implemented by the kernels that include
581 "options COMPAT_FREEBSD10" in their config file (this is the
582 default). Users should ensure that this option is enabled in
583 their kernel or upgrade userspace to r302092 before upgrading their
587 CAM will now strip leading spaces from SCSI disks' serial numbers.
588 This will affect users who create UFS filesystems on SCSI disks using
589 those disk's diskid device nodes. For example, if /etc/fstab
590 previously contained a line like
591 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
592 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
593 transforms like gmirror may also be affected. ZFS users should
597 The bitstring(3) API has been updated with new functionality and
598 improved performance. But it is binary-incompatible with the old API.
599 Objects built with the new headers may not be linked against objects
600 built with the old headers.
603 The brk and sbrk functions have been removed from libc on arm64.
604 Binutils from ports has been updated to not link to these
605 functions and should be updated to the latest version before
606 installing a new libc.
609 The armv6 port now defaults to hard float ABI. Limited support
610 for running both hardfloat and soft float on the same system
611 is available using the libraries installed with -DWITH_LIBSOFT.
612 This has only been tested as an upgrade path for installworld
613 and packages may fail or need manual intervention to run. New
614 packages will be needed.
616 To update an existing self-hosted armv6hf system, you must add
617 TARGET_ARCH=armv6 on the make command line for both the build
618 and the install steps.
621 Kernel modules compiled outside of a kernel build now default to
622 installing to /boot/modules instead of /boot/kernel. Many kernel
623 modules built this way (such as those in ports) already overrode
624 KMODDIR explicitly to install into /boot/modules. However,
625 manually building and installing a module from /sys/modules will
626 now install to /boot/modules instead of /boot/kernel.
629 The CAM I/O scheduler has been committed to the kernel. There should be
630 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
631 list of known rogues that claim support for this but actually corrupt
632 data is believed to be complete, be on the lookout for data
633 corruption. The known rogue list is believed to be complete:
635 o Crucial MX100, M550 drives with MU01 firmware.
636 o Micron M510 and M550 drives with MU01 firmware.
637 o Micron M500 prior to MU07 firmware
638 o Samsung 830, 840, and 850 all firmwares
639 o FCCT M500 all firmwares
641 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
642 with working NCQ TRIM. For Micron branded drives, see your sales rep for
643 updated firmware. Black listed drives will work correctly because these
644 drives work correctly so long as no NCQ TRIMs are sent to them. Given
645 this list is the same as found in Linux, it's believed there are no
646 other rogues in the market place. All other models from the above
649 To be safe, if you are at all concerned, you can quirk each of your
650 drives to prevent NCQ from being sent by setting:
651 kern.cam.ada.X.quirks="0x2"
652 in loader.conf. If the drive requires the 4k sector quirk, set the
656 The FAST_DEPEND build option has been removed and its functionality is
657 now the one true way. The old mkdep(1) style of 'make depend' has
658 been removed. See 20160311 for further details.
661 Resource range types have grown from unsigned long to uintmax_t. All
662 drivers, and anything using libdevinfo, need to be recompiled.
665 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
666 builds. It no longer runs mkdep(1) during 'make depend', and the
667 'make depend' stage can safely be skipped now as it is auto ran
668 when building 'make all' and will generate all SRCS and DPSRCS before
669 building anything else. Dependencies are gathered at compile time with
670 -MF flags kept in separate .depend files per object file. Users should
671 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
675 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
676 kernel modules. Therefore, if you load any kernel modules at boot time,
677 please install the boot loaders after you install the kernel, but before
681 make buildkernel KERNCONF=YOUR_KERNEL_HERE
682 make installkernel KERNCONF=YOUR_KERNEL_HERE
683 make -C sys/boot install
684 <reboot in single user>
686 Then follow the usual steps, described in the General Notes section,
690 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
691 see the 20141231 entry below for information about prerequisites and
692 upgrading, if you are not already using clang 3.5.0 or higher.
695 The AIO subsystem is now a standard part of the kernel. The
696 VFS_AIO kernel option and aio.ko kernel module have been removed.
697 Due to stability concerns, asynchronous I/O requests are only
698 permitted on sockets and raw disks by default. To enable
699 asynchronous I/O requests on all file types, set the
700 vfs.aio.enable_unsafe sysctl to a non-zero value.
703 The ELF object manipulation tool objcopy is now provided by the
704 ELF Tool Chain project rather than by GNU binutils. It should be a
705 drop-in replacement, with the addition of arm64 support. The
706 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
707 to obtain the GNU version if necessary.
710 Building ZFS pools on top of zvols is prohibited by default. That
711 feature has never worked safely; it's always been prone to deadlocks.
712 Using a zvol as the backing store for a VM guest's virtual disk will
713 still work, even if the guest is using ZFS. Legacy behavior can be
714 restored by setting vfs.zfs.vol.recursive=1.
717 The NONE and HPN patches has been removed from OpenSSH. They are
718 still available in the security/openssh-portable port.
721 With the addition of ypldap(8), a new _ypldap user is now required
722 during installworld. "mergemaster -p" can be used to add the user
723 prior to installworld, as documented in the handbook.
726 The tftp loader (pxeboot) now uses the option root-path directive. As a
727 consequence it no longer looks for a pxeboot.4th file on the tftp
728 server. Instead it uses the regular /boot infrastructure as with the
732 The code to start recording plug and play data into the modules has
733 been committed. While the old tools will properly build a new kernel,
734 a number of warnings about "unknown metadata record 4" will be produced
735 for an older kldxref. To avoid such warnings, make sure to rebuild
736 the kernel toolchain (or world). Make sure that you have r292078 or
737 later when trying to build 292077 or later before rebuilding.
740 Debug data files are now built by default with 'make buildworld' and
741 installed with 'make installworld'. This facilitates debugging but
742 requires more disk space both during the build and for the installed
743 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
747 r291527 changed the internal interface between the nfsd.ko and
748 nfscommon.ko modules. As such, they must both be upgraded to-gether.
749 __FreeBSD_version has been bumped because of this.
752 Add support for unicode collation strings leads to a change of
753 order of files listed by ls(1) for example. To get back to the old
754 behaviour, set LC_COLLATE environment variable to "C".
756 Databases administrators will need to reindex their databases given
757 collation results will be different.
759 Due to a bug in install(1) it is recommended to remove the ancient
760 locales before running make installworld.
762 rm -rf /usr/share/locale/*
765 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
766 libcrypto.so.7 or libssl.so.7 must be recompiled.
769 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
770 Kernel modules isp_2400_multi and isp_2500_multi were removed and
771 should be replaced with isp_2400 and isp_2500 modules respectively.
774 The build previously allowed using 'make -n' to not recurse into
775 sub-directories while showing what commands would be executed, and
776 'make -n -n' to recursively show commands. Now 'make -n' will recurse
777 and 'make -N' will not.
780 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
781 and etcupdate will now use this file. A custom sendmail.cf is now
782 updated via this mechanism rather than via installworld. If you had
783 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
784 want to remove the exclusion or change it to "always install".
785 /etc/mail/sendmail.cf is now managed the same way regardless of
786 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
787 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
790 Compatibility shims for legacy ATA device names have been removed.
791 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
792 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
793 environment variables, /dev/ad* and /dev/ar* symbolic links.
796 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
797 Please see the 20141231 entry below for information about prerequisites
798 and upgrading, if you are not already using clang 3.5.0 or higher.
801 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
802 and renamed from .symbols to .debug. This reduces the size requirements
803 on the boot partition or file system and provides consistency with
804 userland debug files.
806 When using the supported kernel installation method the
807 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
808 as is done with /boot/kernel.
810 Developers wishing to maintain the historical behavior of installing
811 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
814 The wireless drivers had undergone changes that remove the 'parent
815 interface' from the ifconfig -l output. The rc.d network scripts
816 used to check presence of a parent interface in the list, so old
817 scripts would fail to start wireless networking. Thus, etcupdate(3)
818 or mergemaster(8) run is required after kernel update, to update your
819 rc.d scripts in /etc.
822 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
823 These configurations are now automatically interpreted as
824 'scrub fragment reassemble'.
827 Kernel-loadable modules for the random(4) device are back. To use
828 them, the kernel must have
831 options RANDOM_LOADABLE
833 kldload(8) can then be used to load random_fortuna.ko
834 or random_yarrow.ko. Please note that due to the indirect
835 function calls that the loadable modules need to provide,
836 the build-in variants will be slightly more efficient.
838 The random(4) kernel option RANDOM_DUMMY has been retired due to
839 unpopularity. It was not all that useful anyway.
842 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
843 Control over building the ELF Tool Chain tools is now provided by
844 the WITHOUT_TOOLCHAIN knob.
847 The polarity of Pulse Per Second (PPS) capture events with the
848 uart(4) driver has been corrected. Prior to this change the PPS
849 "assert" event corresponded to the trailing edge of a positive PPS
850 pulse and the "clear" event was the leading edge of the next pulse.
852 As the width of a PPS pulse in a typical GPS receiver is on the
853 order of 1 millisecond, most users will not notice any significant
854 difference with this change.
856 Anyone who has compensated for the historical polarity reversal by
857 configuring a negative offset equal to the pulse width will need to
858 remove that workaround.
861 The default group assigned to /dev/dri entries has been changed
862 from 'wheel' to 'video' with the id of '44'. If you want to have
863 access to the dri devices please add yourself to the video group
866 # pw groupmod video -m $USER
869 The menu.rc and loader.rc files will now be replaced during
870 upgrades. Please migrate local changes to menu.rc.local and
871 loader.rc.local instead.
874 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
875 strings and strip have been removed. The src.conf(5) knob
876 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
879 As ZFS requires more kernel stack pages than is the default on some
880 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
881 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
883 Please consider using 'options KSTACK_PAGES=X' where X is greater
884 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
887 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
888 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
889 default, i.e., they will not contain "::". For example, instead
890 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
891 to have a more specific match, such as different map entries for
892 IPv6:0:0 vs IPv6:0. This change requires that configuration
893 data (including maps, files, classes, custom ruleset, etc.) must
894 use the same format, so make certain such configuration data is
895 upgrading. As a very simple check search for patterns like
896 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
897 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
898 the cf option UseCompressedIPv6Addresses.
901 The default kernel entropy-processing algorithm is now
902 Fortuna, replacing Yarrow.
904 Assuming you have 'device random' in your kernel config
905 file, the configurations allow a kernel option to override
906 this default. You may choose *ONE* of:
908 options RANDOM_YARROW # Legacy /dev/random algorithm.
909 options RANDOM_DUMMY # Blocking-only driver.
911 If you have neither, you get Fortuna. For most people,
912 read no further, Fortuna will give a /dev/random that works
913 like it always used to, and the difference will be irrelevant.
915 If you remove 'device random', you get *NO* kernel-processed
916 entropy at all. This may be acceptable to folks building
917 embedded systems, but has complications. Carry on reading,
918 and it is assumed you know what you need.
920 *PLEASE* read random(4) and random(9) if you are in the
921 habit of tweaking kernel configs, and/or if you are a member
922 of the embedded community, wanting specific and not-usual
923 behaviour from your security subsystems.
925 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
926 random', you will NOT have a functioning /dev/random, and
927 many cryptographic features will not work, including SSH.
928 You may also find strange behaviour from the random(3) set
929 of library functions, in particular sranddev(3), srandomdev(3)
930 and arc4random(3). The reason for this is that the KERN_ARND
931 sysctl only returns entropy if it thinks it has some to
932 share, and with RANDOM_DUMMY or no 'device random' this
936 An additional fix for the issue described in the 20150614 sendmail
937 entry below has been committed in revision 284717.
940 FreeBSD's old make (fmake) has been removed from the system. It is
941 available as the devel/fmake port or via pkg install fmake.
944 The fix for the issue described in the 20150614 sendmail entry
945 below has been committed in revision 284436. The work
946 around described in that entry is no longer needed unless the
947 default setting is overridden by a confDH_PARAMETERS configuration
948 setting of '5' or pointing to a 512 bit DH parameter file.
951 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
952 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
953 and devel/kyua to version 0.20+ and adjust any calling code to work
954 with Kyuafile and kyua.
957 The import of openssl to address the FreeBSD-SA-15:10.openssl
958 security advisory includes a change which rejects handshakes
959 with DH parameters below 768 bits. sendmail releases prior
960 to 8.15.2 (not yet released), defaulted to a 512 bit
961 DH parameter setting for client connections. To work around
962 this interoperability, sendmail can be configured to use a
963 2048 bit DH parameter by:
965 1. Edit /etc/mail/`hostname`.mc
966 2. If a setting for confDH_PARAMETERS does not exist or
967 exists and is set to a string beginning with '5',
969 3. If a setting for confDH_PARAMETERS exists and is set to
970 a file path, create a new file with:
971 openssl dhparam -out /path/to/file 2048
972 4. Rebuild the .cf file:
973 cd /etc/mail/; make; make install
975 cd /etc/mail/; make restart
977 A sendmail patch is coming, at which time this file will be
981 Generation of legacy formatted entries have been disabled by default
982 in pwd_mkdb(8), as all base system consumers of the legacy formatted
983 entries were converted to use the new format by default when the new,
984 machine independent format have been added and supported since FreeBSD
987 Please see the pwd_mkdb(8) manual page for further details.
990 Clang and llvm have been upgraded to 3.6.1 release. Please see the
991 20141231 entry below for information about prerequisites and upgrading,
992 if you are not already using 3.5.0 or higher.
995 TI platform code switched to using vendor DTS files and this update
996 may break existing systems running on Beaglebone, Beaglebone Black,
999 - dtb files should be regenerated/reinstalled. Filenames are the
1000 same but content is different now
1001 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1002 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1003 addressing scheme is now pin 25 on /dev/gpioc3.
1004 - Pandaboard: /etc/ttys should be updated, serial console device is
1005 now /dev/ttyu2, not /dev/ttyu0
1008 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1009 If you need the GNU extension from groff soelim(1), install groff
1010 from package: pkg install groff, or via ports: textproc/groff.
1013 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1014 defined in symlink(7); previously symlinks were silently ignored.
1017 The const qualifier has been removed from iconv(3) to comply with
1018 POSIX. The ports tree is aware of this from r384038 onwards.
1021 Libraries specified by LIBADD in Makefiles must have a corresponding
1022 DPADD_<lib> variable to ensure correct dependencies. This is now
1023 enforced in src.libnames.mk.
1026 From legacy ata(4) driver was removed support for SATA controllers
1027 supported by more functional drivers ahci(4), siis(4) and mvs(4).
1028 Kernel modules ataahci and ataadaptec were removed completely,
1029 replaced by ahci and mvs modules respectively.
1032 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
1033 the 20141231 entry below for information about prerequisites and
1034 upgrading, if you are not already using 3.5.0 or higher.
1037 The 32-bit PowerPC kernel has been changed to a position-independent
1038 executable. This can only be booted with a version of loader(8)
1039 newer than January 31, 2015, so make sure to update both world and
1040 kernel before rebooting.
1043 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1044 but before r278950, the RNG was not seeded properly. Immediately
1045 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1046 ssh keys or openssl keys) that were generated w/ a kernel from that
1047 range. This does not affect programs that directly used /dev/random
1048 or /dev/urandom. All userland uses of arc4random(3) are affected.
1051 The autofs(4) ABI was changed in order to restore binary compatibility
1052 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
1053 with the new kernel.
1056 The powerpc64 kernel has been changed to a position-independent
1057 executable. This can only be booted with a new version of loader(8),
1058 so make sure to update both world and kernel before rebooting.
1061 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
1062 only release, no new features have been added. Please see the 20141231
1063 entry below for information about prerequisites and upgrading, if you
1064 are not already using 3.5.0.
1067 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1068 taken from the ELF Tool Chain project rather than GNU binutils. They
1069 should be drop-in replacements, with the addition of arm64 support.
1070 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1071 binutils tools, if necessary. See 20150805 for updated information.
1074 The default Unbound configuration now enables remote control
1075 using a local socket. Users who have already enabled the
1076 local_unbound service should regenerate their configuration
1077 by running "service local_unbound setup" as root.
1080 The GNU texinfo and GNU info pages have been removed.
1081 To be able to view GNU info pages please install texinfo from ports.
1084 Clang, llvm and lldb have been upgraded to 3.5.0 release.
1086 As of this release, a prerequisite for building clang, llvm and lldb is
1087 a C++11 capable compiler and C++11 standard library. This means that to
1088 be able to successfully build the cross-tools stage of buildworld, with
1089 clang as the bootstrap compiler, your system compiler or cross compiler
1090 should either be clang 3.3 or later, or gcc 4.8 or later, and your
1091 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1094 On any standard FreeBSD 10.x or 11.x installation, where clang and
1095 libc++ are on by default (that is, on x86 or arm), this should work out
1098 On 9.x installations where clang is enabled by default, e.g. on x86 and
1099 powerpc, libc++ will not be enabled by default, so libc++ should be
1100 built (with clang) and installed first. If both clang and libc++ are
1101 missing, build clang first, then use it to build libc++.
1103 On 8.x and earlier installations, upgrade to 9.x first, and then follow
1104 the instructions for 9.x above.
1106 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1107 default, and do not build clang.
1109 Many embedded systems are resource constrained, and will not be able to
1110 build clang in a reasonable time, or in some cases at all. In those
1111 cases, cross building bootable systems on amd64 is a workaround.
1113 This new version of clang introduces a number of new warnings, of which
1114 the following are most likely to appear:
1118 This warns in two cases, for both C and C++:
1119 * When the code is trying to take the absolute value of an unsigned
1120 quantity, which is effectively a no-op, and almost never what was
1121 intended. The code should be fixed, if at all possible. If you are
1122 sure that the unsigned quantity can be safely cast to signed, without
1123 loss of information or undefined behavior, you can add an explicit
1124 cast, or disable the warning.
1126 * When the code is trying to take an absolute value, but the called
1127 abs() variant is for the wrong type, which can lead to truncation.
1128 If you want to disable the warning instead of fixing the code, please
1129 make sure that truncation will not occur, or it might lead to unwanted
1132 -Wtautological-undefined-compare and
1133 -Wundefined-bool-conversion
1135 These warn when C++ code is trying to compare 'this' against NULL, while
1136 'this' should never be NULL in well-defined C++ code. However, there is
1137 some legacy (pre C++11) code out there, which actively abuses this
1138 feature, which was less strictly defined in previous C++ versions.
1140 Squid and openjdk do this, for example. The warning can be turned off
1141 for C++98 and earlier, but compiling the code in C++11 mode might result
1142 in unexpected behavior; for example, the parts of the program that are
1143 unreachable could be optimized away.
1146 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1147 kernel sources have been removed. The .h files remain, since some
1148 utilities include them. This will need to be fixed later.
1149 If "mount -t oldnfs ..." is attempted, it will fail.
1150 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1151 the utilities will report errors.
1154 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1155 directories to top level SUBDIR variable when their parent
1156 directory is included in LOCAL_DIRS. Users with build systems with
1157 such hierarchies and without SUBDIR entries in the parent
1158 directory Makefiles should add them or add the directories to
1162 faith(4) and faithd(8) have been removed from the base system. Faith
1163 has been obsolete for a very long time.
1166 vt(4), the new console driver, is enabled by default. It brings
1167 support for Unicode and double-width characters, as well as
1168 support for UEFI and integration with the KMS kernel video
1171 You may need to update your console settings in /etc/rc.conf,
1172 most probably the keymap. During boot, /etc/rc.d/syscons will
1173 indicate what you need to do.
1175 vt(4) still has issues and lacks some features compared to
1176 syscons(4). See the wiki for up-to-date information:
1177 https://wiki.freebsd.org/Newcons
1179 If you want to keep using syscons(4), you can do so by adding
1180 the following line to /boot/loader.conf:
1184 pjdfstest has been integrated into kyua as an opt-in test suite.
1185 Please see share/doc/pjdfstest/README for more details on how to
1189 gperf has been removed from the base system for architectures
1190 that use clang. Ports that require gperf will obtain it from the
1194 pjdfstest has been moved from tools/regression/pjdfstest to
1198 At svn r271982, The default linux compat kernel ABI has been adjusted
1199 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1200 update. If you wish to continue using the linux-f10 compat ports,
1201 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1202 encouraged to update their linux-compat packages to linux-c6 during
1203 their next update cycle.
1206 The ofwfb driver, used to provide a graphics console on PowerPC when
1207 using vt(4), no longer allows mmap() of all physical memory. This
1208 will prevent Xorg on PowerPC with some ATI graphics cards from
1209 initializing properly unless x11-servers/xorg-server is updated to
1213 The xdev targets have been converted to using TARGET and
1214 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1217 The default unbound configuration has been modified to address
1218 issues with reverse lookups on networks that use private
1219 address ranges. If you use the local_unbound service, run
1220 "service local_unbound setup" as root to regenerate your
1221 configuration, then "service local_unbound reload" to load the
1225 The GNU texinfo and GNU info pages are not built and installed
1226 anymore, WITH_INFO knob has been added to allow to built and install
1228 UPDATE: see 20150102 entry on texinfo's removal
1231 The GNU readline library is now an INTERNALLIB - that is, it is
1232 statically linked into consumers (GDB and variants) in the base
1233 system, and the shared library is no longer installed. The
1234 devel/readline port is available for third party software that
1238 The Itanium architecture (ia64) has been removed from the list of
1239 known architectures. This is the first step in the removal of the
1243 Commit r268115 has added NFSv4.1 server support, merged from
1244 projects/nfsv4.1-server. Since this includes changes to the
1245 internal interfaces between the NFS related modules, a full
1246 build of the kernel and modules will be necessary.
1247 __FreeBSD_version has been bumped.
1250 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1251 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1252 which differs from the behaviour controlled by this knob.)
1255 Maximal length of the serial number in CTL was increased from 16 to
1256 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1257 and ctld, need to be rebuilt to work with a new kernel.
1260 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1261 1 respectively to match the upstream numbers. They were out of
1262 sync because, when they were originally added to FreeBSD, the
1263 upstream versions were not respected. These libraries are private
1264 and not yet built by default, so renumbering them should be a
1265 non-issue. However, unclean source trees will yield broken test
1266 programs once the operator executes "make delete-old-libs" after a
1267 "make installworld".
1269 Additionally, the atf-sh binary was made private by moving it into
1270 /usr/libexec/. Already-built shell test programs will keep the
1271 path to the old binary so they will break after "make delete-old"
1274 If you are using WITH_TESTS=yes (not the default), wipe the object
1275 tree and rebuild from scratch to prevent spurious test failures.
1276 This is only needed once: the misnumbered libraries and misplaced
1277 binaries have been added to OptionalObsoleteFiles.inc so they will
1278 be removed during a clean upgrade.
1281 Clang and llvm have been upgraded to 3.4.1 release.
1284 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1285 be removed to avoid issues in the future (and has been added to
1289 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1290 past, it affected all builds that used the bsd.*.mk files. The old
1291 behavior was a bug, but people may have relied upon it. To get this
1292 behavior back, you can .include /etc/src.conf from /etc/make.conf
1293 (which is still global and isn't changed). This also changes the
1294 behavior of incremental builds inside the tree of individual
1295 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1296 Although this has survived make universe and some upgrade scenarios,
1297 other upgrade scenarios may have broken. At least one form of
1298 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1299 as well... In cases where MAKESYSPATH isn't working with this
1300 setting, you'll need to set it to the full path to your tree.
1302 One side effect of all this cleaning up is that bsd.compiler.mk
1303 is no longer implicitly included by bsd.own.mk. If you wish to
1304 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1308 The lindev device has been removed since /dev/full has been made a
1309 standard device. __FreeBSD_version has been bumped.
1312 The knob WITHOUT_VI was added to the base system, which controls
1313 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1314 in order to reorder files share/termcap and didn't build ex(1) as a
1315 build tool, so building/installing with WITH_VI is highly advised for
1316 build hosts for older releases.
1318 This issue has been fixed in stable/9 and stable/10 in r277022 and
1319 r276991, respectively.
1322 The YES_HESIOD knob has been removed. It has been obsolete for
1323 a decade. Please move to using WITH_HESIOD instead or your builds
1324 will silently lack HESIOD.
1327 The uart(4) driver has been changed with respect to its handling
1328 of the low-level console. Previously the uart(4) driver prevented
1329 any process from changing the baudrate or the CLOCAL and HUPCL
1330 control flags. By removing the restrictions, operators can make
1331 changes to the serial console port without having to reboot.
1332 However, when getty(8) is started on the serial device that is
1333 associated with the low-level console, a misconfigured terminal
1334 line in /etc/ttys will now have a real impact.
1335 Before upgrading the kernel, make sure that /etc/ttys has the
1336 serial console device configured as 3wire without baudrate to
1337 preserve the previous behaviour. E.g:
1338 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1341 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1342 to improve performance. To re-enable it, if needed, run rpcbind
1343 with command line option -W.
1346 Switched back to the GPL dtc compiler due to updates in the upstream
1347 dts files not being supported by the BSDL dtc compiler. You will need
1348 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1349 may result while building dtb files during a kernel build if you fail
1350 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1353 Clang and llvm have been upgraded to 3.4 release.
1356 The nve(4) driver has been removed. Please use the nfe(4) driver
1357 for NVIDIA nForce MCP Ethernet adapters instead.
1360 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1361 This could cause certain C++ applications using shared libraries built
1362 against the previous version of libc++ to crash. The incompatibility
1363 has now been fixed, but any C++ applications or shared libraries built
1364 between r261283 and r261801 should be recompiled.
1367 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1368 capability mode support. Please note that enabling the feature in
1369 kernel is still highly recommended.
1372 OpenSSH is now built with sandbox support, and will use sandbox as
1373 the default privilege separation method. This requires Capsicum
1374 capability mode support in kernel.
1377 The libelf and libdwarf libraries have been updated to newer
1378 versions from upstream. Shared library version numbers for
1379 these two libraries were bumped. Any ports or binaries
1380 requiring these two libraries should be recompiled.
1381 __FreeBSD_version is bumped to 1100006.
1384 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1385 instead of providing an explicit one, this would prevent such
1386 Makefile from providing its own Kyuafile in the future during
1387 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1388 intervention is needed to clean an objdir if you use NO_CLEAN:
1389 # find /usr/obj -name Kyuafile | xargs rm -f
1392 The behavior of gss_pseudo_random() for the krb5 mechanism
1393 has changed, for applications requesting a longer random string
1394 than produced by the underlying enctype's pseudo-random() function.
1395 In particular, the random string produced from a session key of
1396 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1397 be different at the 17th octet and later, after this change.
1398 The counter used in the PRF+ construction is now encoded as a
1399 big-endian integer in accordance with RFC 4402.
1400 __FreeBSD_version is bumped to 1100004.
1403 The WITHOUT_ATF build knob has been removed and its functionality
1404 has been subsumed into the more generic WITHOUT_TESTS. If you were
1405 using the former to disable the build of the ATF libraries, you
1406 should change your settings to use the latter.
1409 The default version of mtree is nmtree which is obtained from
1410 NetBSD. The output is generally the same, but may vary
1411 slightly. If you found you need identical output adding
1412 "-F freebsd9" to the command line should do the trick. For the
1413 time being, the old mtree is available as fmtree.
1416 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1417 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1418 1.1.4_8 and verify bsdyml not linked in, before running "make
1420 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1422 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1425 The stable/10 branch has been created in subversion from head
1429 The rc.d/jail script has been updated to support jail(8)
1430 configuration file. The "jail_<jname>_*" rc.conf(5) variables
1431 for per-jail configuration are automatically converted to
1432 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
1433 This is transparently backward compatible. See below about some
1434 incompatibilities and rc.conf(5) manual page for more details.
1436 These variables are now deprecated in favor of jail(8) configuration
1437 file. One can use "rc.d/jail config <jname>" command to generate
1438 a jail(8) configuration file in /var/run/jail.<jname>.conf without
1439 running the jail(8) utility. The default pathname of the
1440 configuration file is /etc/jail.conf and can be specified by
1441 using $jail_conf or $jail_<jname>_conf variables.
1443 Please note that jail_devfs_ruleset accepts an integer at
1444 this moment. Please consider to rewrite the ruleset name
1448 BIND has been removed from the base system. If all you need
1449 is a local resolver, simply enable and start the local_unbound
1450 service instead. Otherwise, several versions of BIND are
1451 available in the ports tree. The dns/bind99 port is one example.
1453 With this change, nslookup(1) and dig(1) are no longer in the base
1454 system. Users should instead use host(1) and drill(1) which are
1455 in the base system. Alternatively, nslookup and dig can
1456 be obtained by installing the dns/bind-tools port.
1459 With the addition of unbound(8), a new unbound user is now
1460 required during installworld. "mergemaster -p" can be used to
1461 add the user prior to installworld, as documented in the handbook.
1464 OpenSSH is now built with DNSSEC support, and will by default
1465 silently trust signed SSHFP records. This can be controlled with
1466 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1467 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1470 The GNU Compiler Collection and C++ standard library (libstdc++)
1471 are no longer built by default on platforms where clang is the system
1472 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1473 options in src.conf.
1476 The PROCDESC kernel option is now part of the GENERIC kernel
1477 configuration and is required for the rwhod(8) to work.
1478 If you are using custom kernel configuration, you should include
1482 The API and ABI related to the Capsicum framework was modified
1483 in backward incompatible way. The userland libraries and programs
1484 have to be recompiled to work with the new kernel. This includes the
1485 following libraries and programs, but the whole buildworld is
1486 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1487 kdump, procstat, rwho, rwhod, uniq.
1490 AES-NI intrinsic support has been added to gcc. The AES-NI module
1491 has been updated to use this support. A new gcc is required to build
1492 the aesni module on both i386 and amd64.
1495 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1496 Thus "device padlock_rng" and "device rdrand_rng" should be
1497 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1500 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1501 enables just the iconv* functionality and is now on by default.
1502 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1503 compatibility. Set WITHOUT_ICONV to build the old way.
1504 If you have been using WITH_ICONV before, you will very likely
1505 need to turn on WITH_LIBICONV_COMPAT.
1508 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1509 Illumos origin, including ZFS. If you have INVARIANTS in your
1510 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1512 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1513 locks if WITNESS option was set. Because that generated a lot of
1514 witness(9) reports and all of them were believed to be false
1515 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1516 can be used to achieve the previous behavior.
1519 Timer values in IPv6 data structures now use time_uptime instead
1520 of time_second. Although this is not a user-visible functional
1521 change, userland utilities which directly use them---ndp(8),
1522 rtadvd(8), and rtsold(8) in the base system---need to be updated
1523 to r253970 or later.
1526 find -delete can now delete the pathnames given as arguments,
1527 instead of only files found below them or if the pathname did
1528 not contain any slashes. Formerly, the following error message
1531 find: -delete: <path>: relative path potentially not safe
1533 Deleting the pathnames given as arguments can be prevented
1534 without error messages using -mindepth 1 or by changing
1535 directory and passing "." as argument to find. This works in the
1536 old as well as the new version of find.
1539 Behavior of devfs rules path matching has been changed.
1540 Pattern is now always matched against fully qualified devfs
1541 path and slash characters must be explicitly matched by
1542 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1543 subdirectories must be reviewed.
1546 The default ARM ABI has changed to the ARM EABI. The old ABI is
1547 incompatible with the ARM EABI and all programs and modules will
1548 need to be rebuilt to work with a new kernel.
1550 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1552 NOTE: Support for the old ABI will be removed in the future and
1553 users are advised to upgrade.
1556 pkg_install has been disconnected from the build if you really need it
1557 you should add WITH_PKGTOOLS in your src.conf(5).
1560 Most of network statistics structures were changed to be able
1561 keep 64-bits counters. Thus all tools, that work with networking
1562 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1565 Fix a bug that allowed a tracing process (e.g. gdb) to write
1566 to a memory-mapped file in the traced process's address space
1567 even if neither the traced process nor the tracing process had
1568 write access to that file.
1571 CVS has been removed from the base system. An exact copy
1572 of the code is available from the devel/cvs port.
1575 Some people report the following error after the switch to bmake:
1577 make: illegal option -- J
1578 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1580 *** [buildworld] Error code 2
1582 this likely due to an old instance of make in
1583 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1584 which src/Makefile will use that blindly, if it exists, so if
1585 you see the above error:
1587 rm -rf `make -V MAKEPATH`
1592 Use bmake by default.
1593 Whereas before one could choose to build with bmake via
1594 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1595 make. The goal is to remove these knobs for 10-RELEASE.
1597 It is worth noting that bmake (like gmake) treats the command
1598 line as the unit of failure, rather than statements within the
1599 command line. Thus '(cd some/where && dosomething)' is safer
1600 than 'cd some/where; dosomething'. The '()' allows consistent
1601 behavior in parallel build.
1604 Fix a bug that allows NFS clients to issue READDIR on files.
1607 The WITHOUT_IDEA option has been removed because
1608 the IDEA patent expired.
1611 The sysctl which controls TRIM support under ZFS has been renamed
1612 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1616 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1617 rather than creating it's own in the temporary directory in
1618 order allow access to bootstrapped versions of tools such as
1619 install and mtree. When upgrading from version of FreeBSD where
1620 the install command does not support -l, you will need to
1621 install a new mergemaster command if mergemaster -p is required.
1622 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1626 Legacy ATA stack, disabled and replaced by new CAM-based one since
1627 FreeBSD 9.0, completely removed from the sources. Kernel modules
1628 atadisk and atapi*, user-level tools atacontrol and burncd are
1629 removed. Kernel option `options ATA_CAM` is now permanently enabled
1633 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1634 and socketpair(2). Software, in particular Kerberos, may
1635 automatically detect and use these during building. The resulting
1636 binaries will not work on older kernels.
1639 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1640 information, see the respective 20130304 entry).
1643 Recent commits to callout(9) changed the size of struct callout,
1644 so the KBI is probably heavily disturbed. Also, some functions
1645 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1646 by macros. Every kernel module using it won't load, so rebuild
1649 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1650 but does not initialize by default (because of the new CTL_DISABLE
1651 option) to save memory. To re-enable it, remove the CTL_DISABLE
1652 option from the kernel config file or set kern.cam.ctl.disable=0
1653 in /boot/loader.conf.
1656 The ctl device has been disabled in GENERIC for i386 and amd64.
1657 This was done due to the extra memory being allocated at system
1658 initialisation time by the ctl driver which was only used if
1659 a CAM target device was created. This makes a FreeBSD system
1660 unusable on 128MB or less of RAM.
1663 A new compression method (lz4) has been merged to -HEAD. Please
1664 refer to zpool-features(7) for more information.
1666 Please refer to the "ZFS notes" section of this file for information
1667 on upgrading boot ZFS pools.
1670 A BSD-licensed patch(1) variant has been added and is installed
1671 as bsdpatch, being the GNU version the default patch.
1672 To inverse the logic and use the BSD-licensed one as default,
1673 while having the GNU version installed as gnupatch, rebuild
1674 and install world with the WITH_BSD_PATCH knob set.
1677 Due to the use of the new -l option to install(1) during build
1678 and install, you must take care not to directly set the INSTALL
1679 make variable in your /etc/make.conf, /etc/src.conf, or on the
1680 command line. If you wish to use the -C flag for all installs
1681 you may be able to add INSTALL+=-C to /etc/make.conf or
1685 The install(1) option -M has changed meaning and now takes an
1686 argument that is a file or path to append logs to. In the
1687 unlikely event that -M was the last option on the command line
1688 and the command line contained at least two files and a target
1689 directory the first file will have logs appended to it. The -M
1690 option served little practical purpose in the last decade so its
1691 use is expected to be extremely rare.
1694 After switching to Clang as the default compiler some users of ZFS
1695 on i386 systems started to experience stack overflow kernel panics.
1696 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1699 GEOM_LABEL now mangles label names read from file system metadata.
1700 Mangling affect labels containing spaces, non-printable characters,
1701 '%' or '"'. Device names in /etc/fstab and other places may need to
1705 By default, only the 10 most recent kernel dumps will be saved. To
1706 restore the previous behaviour (no limit on the number of kernel dumps
1707 stored in the dump directory) add the following line to /etc/rc.conf:
1712 With the addition of auditdistd(8), a new auditdistd user is now
1713 required during installworld. "mergemaster -p" can be used to
1714 add the user prior to installworld, as documented in the handbook.
1717 The sin6_scope_id member variable in struct sockaddr_in6 is now
1718 filled by the kernel before passing the structure to the userland via
1719 sysctl or routing socket. This means the KAME-specific embedded scope
1720 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1721 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1722 __FreeBSD_version is bumped to 1000025.
1725 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1726 This means that the world and kernel will be compiled with clang
1727 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1728 and /usr/bin/cpp. To disable this behavior and revert to building
1729 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1730 of current may need to bootstrap WITHOUT_CLANG first if the clang
1731 build fails (its compatibility window doesn't extend to the 9 stable
1735 The IPFIREWALL_FORWARD kernel option has been removed. Its
1736 functionality now turned on by default.
1739 The ZERO_COPY_SOCKET kernel option has been removed and
1740 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1741 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1742 mechanism which is not safe and may result in kernel crashes.
1743 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1744 driver supports disposeable external page sized mbuf storage.
1745 Proper replacements for both zero-copy mechanisms are under
1746 consideration and will eventually lead to complete removal
1747 of the two kernel options.
1750 The IPv4 network stack has been converted to network byte
1751 order. The following modules need to be recompiled together
1752 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1753 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1756 Support for non-MPSAFE filesystems was removed from VFS. The
1757 VFS_VERSION was bumped, all filesystem modules shall be
1761 All the non-MPSAFE filesystems have been disconnected from
1762 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1763 portalfs, smbfs, xfs.
1766 The interface cloning API and ABI has changed. The following
1767 modules need to be recompiled together with kernel:
1768 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1769 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1770 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1773 The sdhci driver was split in two parts: sdhci (generic SD Host
1774 Controller logic) and sdhci_pci (actual hardware driver).
1775 No kernel config modifications are required, but if you
1776 load sdhc as a module you must switch to sdhci_pci instead.
1779 Import the FUSE kernel and userland support into base system.
1782 The GNU sort(1) program has been removed since the BSD-licensed
1783 sort(1) has been the default for quite some time and no serious
1784 problems have been reported. The corresponding WITH_GNU_SORT
1788 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1789 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1793 The net80211(4) ABI has been changed to allow for improved driver
1794 PS-POLL and power-save support. All wireless drivers need to be
1795 recompiled to work with the new kernel.
1798 The random(4) support for the VIA hardware random number
1799 generator (`PADLOCK') is no longer enabled unconditionally.
1800 Add the padlock_rng device in the custom kernel config if
1801 needed. The GENERIC kernels on i386 and amd64 do include the
1802 device, so the change only affects the custom kernel
1806 The pf(4) packet filter ABI has been changed. pfctl(8) and
1807 snmp_pf module need to be recompiled to work with new kernel.
1810 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1811 to -HEAD. Pools that have empty_bpobj in active state can not be
1812 imported read-write with ZFS implementations that do not support
1813 this feature. For more information read the zpool-features(5)
1817 The sparc64 ZFS loader has been changed to no longer try to auto-
1818 detect ZFS providers based on diskN aliases but now requires these
1819 to be explicitly listed in the OFW boot-device environment variable.
1822 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1823 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1824 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1827 The following sysctls and tunables have been renamed for consistency
1828 with other variables:
1829 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1830 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1833 The sort utility has been replaced with BSD sort. For now, GNU sort
1834 is also available as "gnusort" or the default can be set back to
1835 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1836 installed as "bsdsort".
1839 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1840 Starting with this version the old system of ZFS pool versioning
1841 is superseded by "feature flags". This concept enables forward
1842 compatibility against certain future changes in functionality of ZFS
1843 pools. The first read-only compatible "feature flag" for ZFS pools
1844 is named "com.delphix:async_destroy". For more information
1845 read the new zpool-features(5) manual page.
1846 Please refer to the "ZFS notes" section of this file for information
1847 on upgrading boot ZFS pools.
1850 The malloc(3) implementation embedded in libc now uses sources imported
1851 as contrib/jemalloc. The most disruptive API change is to
1852 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1853 delete it prior to installworld, and optionally re-create it using the
1854 new format after rebooting. See malloc.conf(5) for details
1855 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1859 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1860 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1861 now spelled mips. This is to aid compatibility with third-party
1862 software that expects this naming scheme in uname(3). Little-endian
1863 settings are unchanged. If you are updating a big-endian mips64 machine
1864 from before this change, you may need to set MACHINE_ARCH=mips64 in
1865 your environment before the new build system will recognize your machine.
1868 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1872 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1873 nullfs(5) did not pass through all behaviours to the underlying layer,
1874 as a result if we bound to a socket on the lower layer we could connect
1875 only to the lower path; if we bound to the upper layer we could connect
1876 only to the upper path. The new behavior is one can connect to both the
1877 lower and the upper paths regardless what layer path one binds to.
1880 The getifaddrs upgrade path broken with 20111215 has been restored.
1881 If you have upgraded in between 20111215 and 20120209 you need to
1882 recompile libc again with your kernel. You still need to recompile
1883 world to be able to configure CARP but this restriction already
1884 comes from 20111215.
1887 The set_rcvar() function has been removed from /etc/rc.subr. All
1888 base and ports rc.d scripts have been updated, so if you have a
1889 port installed with a script in /usr/local/etc/rc.d you can either
1890 hand-edit the rcvar= line, or reinstall the port.
1892 An easy way to handle the mass-update of /etc/rc.d:
1893 rm /etc/rc.d/* && mergemaster -i
1896 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1897 on the current CPU and prevents other threads from running.
1898 This behavior can be reverted using the kern.stop_scheduler_on_panic
1900 The new behavior can be incompatible with kern.sync_on_panic.
1903 The carp(4) facility has been changed significantly. Configuration
1904 of the CARP protocol via ifconfig(8) has changed, as well as format
1905 of CARP events submitted to devd(8) has changed. See manual pages
1906 for more information. The arpbalance feature of carp(4) is currently
1907 not supported anymore.
1909 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1910 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1911 need to be recompiled.
1914 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1918 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1919 explicitely support non-MPSAFE filesystems.
1920 It is on by default for all supported platform at this present
1924 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1925 i386 and pc98 GENERIC kernel configuration files.
1928 sysinstall has been removed
1931 The stable/9 branch created in subversion. This corresponds to the
1932 RELENG_9 branch in CVS.
1938 Avoid using make -j when upgrading. While generally safe, there are
1939 sometimes problems using -j to upgrade. If your upgrade fails with
1940 -j, please try again without -j. From time to time in the past there
1941 have been problems using -j with buildworld and/or installworld. This
1942 is especially true when upgrading between "distant" versions (eg one
1943 that cross a major release boundary or several minor releases, or when
1944 several months have passed on the -current branch).
1946 Sometimes, obscure build problems are the result of environment
1947 poisoning. This can happen because the make utility reads its
1948 environment when searching for values for global variables. To run
1949 your build attempts in an "environmental clean room", prefix all make
1950 commands with 'env -i '. See the env(1) manual page for more details.
1952 When upgrading from one major version to another it is generally best to
1953 upgrade to the latest code in the currently installed branch first, then
1954 do an upgrade to the new branch. This is the best-tested upgrade path,
1955 and has the highest probability of being successful. Please try this
1956 approach if you encounter problems with a major version upgrade. Since
1957 the stable 4.x branch point, one has generally been able to upgrade from
1958 anywhere in the most recent stable branch to head / current (or even the
1959 last couple of stable branches). See the top of this file when there's
1962 When upgrading a live system, having a root shell around before
1963 installing anything can help undo problems. Not having a root shell
1964 around can lead to problems if pam has changed too much from your
1965 starting point to allow continued authentication after the upgrade.
1967 This file should be read as a log of events. When a later event changes
1968 information of a prior event, the prior event should not be deleted.
1969 Instead, a pointer to the entry with the new information should be
1970 placed in the old entry. Readers of this file should also sanity check
1971 older entries before relying on them blindly. Authors of new entries
1972 should write them with this in mind.
1976 When upgrading the boot ZFS pool to a new version, always follow
1979 1.) recompile and reinstall the ZFS boot loader and boot block
1980 (this is part of "make buildworld" and "make installworld")
1982 2.) update the ZFS boot block on your boot drive
1984 The following example updates the ZFS boot block on the first
1985 partition (freebsd-boot) of a GPT partitioned drive ada0:
1986 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1988 Non-boot pools do not need these updates.
1992 If you are updating from a prior version of FreeBSD (even one just
1993 a few days old), you should follow this procedure. It is the most
1994 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1996 make kernel-toolchain
1997 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1998 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2000 To test a kernel once
2001 ---------------------
2002 If you just want to boot a kernel once (because you are not sure
2003 if it works, or if you want to boot a known bad kernel to provide
2004 debugging information) run
2005 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2006 nextboot -k testkernel
2008 To rebuild everything and install it on the current system.
2009 -----------------------------------------------------------
2010 # Note: sometimes if you are running current you gotta do more than
2011 # is listed here if you are upgrading from a really old current.
2013 <make sure you have good level 0 dumps>
2015 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2016 make installkernel KERNCONF=YOUR_KERNEL_HERE
2018 <reboot in single user> [3]
2025 To cross-install current onto a separate partition
2026 --------------------------------------------------
2027 # In this approach we use a separate partition to hold
2028 # current's root, 'usr', and 'var' directories. A partition
2029 # holding "/", "/usr" and "/var" should be about 2GB in
2032 <make sure you have good level 0 dumps>
2035 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2036 <maybe newfs current's root partition>
2037 <mount current's root partition on directory ${CURRENT_ROOT}>
2038 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
2039 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2040 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2041 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2042 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2043 <reboot into current>
2044 <do a "native" rebuild/install as described in the previous section>
2045 <maybe install compatibility libraries from ports/misc/compat*>
2049 To upgrade in-place from stable to current
2050 ----------------------------------------------
2051 <make sure you have good level 0 dumps>
2053 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
2054 make installkernel KERNCONF=YOUR_KERNEL_HERE
2056 <reboot in single user> [3]
2063 Make sure that you've read the UPDATING file to understand the
2064 tweaks to various things you need. At this point in the life
2065 cycle of current, things change often and you are on your own
2066 to cope. The defaults can also change, so please read ALL of
2067 the UPDATING entries.
2069 Also, if you are tracking -current, you must be subscribed to
2070 freebsd-current@freebsd.org. Make sure that before you update
2071 your sources that you have read and understood all the recent
2072 messages there. If in doubt, please track -stable which has
2073 much fewer pitfalls.
2075 [1] If you have third party modules, such as vmware, you
2076 should disable them at this point so they don't crash your
2079 [3] From the bootblocks, boot -s, and then do
2084 adjkerntz -i # if CMOS is wall time
2085 Also, when doing a major release upgrade, it is required that
2086 you boot into single user mode to do the installworld.
2088 [4] Note: This step is non-optional. Failure to do this step
2089 can result in a significant reduction in the functionality of the
2090 system. Attempting to do it by hand is not recommended and those
2091 that pursue this avenue should read this file carefully, as well
2092 as the archives of freebsd-current and freebsd-hackers mailing lists
2093 for potential gotchas. The -U option is also useful to consider.
2094 See mergemaster(8) for more information.
2096 [5] Usually this step is a no-op. However, from time to time
2097 you may need to do this if you get unknown user in the following
2098 step. It never hurts to do it all the time. You may need to
2099 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2100 install) after the buildworld before this step if you last updated
2101 from current before 20130425 or from -stable before 20130430.
2103 [6] This only deletes old files and directories. Old libraries
2104 can be deleted by "make delete-old-libs", but you have to make
2105 sure that no program is using those libraries anymore.
2107 [8] In order to have a kernel that can run the 4.x binaries needed to
2108 do an installworld, you must include the COMPAT_FREEBSD4 option in
2109 your kernel. Failure to do so may leave you with a system that is
2110 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2111 required to run the 5.x binaries on more recent kernels. And so on
2112 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2114 Make sure that you merge any new devices from GENERIC since the
2115 last time you updated your kernel config file.
2117 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2118 "?=" instead of the "=" assignment operator, so that buildworld can
2119 override the CPUTYPE if it needs to.
2121 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2122 not on the command line, or in /etc/make.conf. buildworld will
2123 warn if it is improperly defined.
2126 This file contains a list, in reverse chronological order, of major
2127 breakages in tracking -current. It is not guaranteed to be a complete
2128 list of such breakages, and only contains entries since September 23, 2011.
2129 If you need to see UPDATING entries from before that date, you will need
2130 to fetch an UPDATING file from an older FreeBSD release.
2132 Copyright information:
2134 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2136 Redistribution, publication, translation and use, with or without
2137 modification, in full or in part, in any form or format of this
2138 document are permitted without further permission from the author.
2140 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2141 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2142 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2143 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2144 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2145 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2146 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2147 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2148 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2149 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2150 POSSIBILITY OF SUCH DAMAGE.
2152 Contact Warner Losh if you have any questions about your use of