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