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/updating-src.html
11 Items affecting the ports and packages system can be found in
12 /usr/ports/UPDATING. Please read that file before running portupgrade.
14 NOTE: FreeBSD has switched from gcc to clang. If you have trouble bootstrapping
15 from older versions of FreeBSD, try WITHOUT_CLANG and WITH_GCC to bootstrap to
16 the tip of head, and then rebuild without this option. The bootstrap process
17 from older version of current across the gcc/clang cutover is a bit fragile.
19 NOTE TO PEOPLE WHO THINK THAT FreeBSD 12.x IS SLOW:
20 FreeBSD 12.x has many debugging features turned on, in both the kernel
21 and userland. These features attempt to detect incorrect use of
22 system primitives, and encourage loud failure through extra sanity
23 checking and fail stop semantics. They also substantially impact
24 system performance. If you want to do performance measurement,
25 benchmarking, and optimization, you'll want to turn them off. This
26 includes various WITNESS- related kernel options, INVARIANTS, malloc
27 debugging flags in userland, and various verbose features in the
28 kernel. Many developers choose to disable these features on build
29 machines to maximize performance. (To completely disable malloc
30 debugging, define MALLOC_PRODUCTION in /etc/make.conf, or to merely
31 disable the most expensive debugging functionality run
32 "ln -s 'abort:false,junk:false' /etc/malloc.conf".)
35 ****************************** SPECIAL WARNING: ******************************
37 Due to a bug in some versions of clang that's very hard to workaround in
38 the upgrade process, to upgrade to -current you must first upgrade
39 either stable/9 after r286035 or stable/10 after r286033 (including
40 10.3-RELEASE) or current after r286007 (including stable/11 and
41 11.0-RELEASE). These revisions post-date the 10.2 and 9.3 releases, so
42 you'll need to take the unusual step of upgrading to the tip of the
43 stable branch before moving to 11 or -current via a source upgrade.
44 stable/11 and 11.0-RELEASE have working newer compiler. This differs
45 from the historical situation where one could upgrade from anywhere on
46 the last couple of stable branches, so be careful.
48 If you're running a hybrid system on 9.x or 10.x with an updated clang
49 compiler or are using an supported external toolchain, the build system
50 will allow the upgrade. Otherwise it will print a reminder.
52 ****************************** SPECIAL WARNING: ******************************
55 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
56 smaller runtime footprint builds. This is useful for embedded systems
57 which only require one chipset support.
59 If you load it as a module, make sure this is in /boot/loader.conf:
63 This will load the HAL, all chip/RF backends and if_ath_pci.
64 If you have if_ath_pci in /boot/loader.conf, ensure it is after
65 if_ath or it will not load any HAL chipset support.
67 If you want to selectively load things (eg on ye cheape ARM/MIPS
68 platforms where RAM is at a premium) you should:
71 * load the chip modules in question
72 * load ath_rate, ath_dfs
74 * load if_ath_pci and/or if_ath_ahb depending upon your particular
75 bus bind type - this is where probe/attach is done.
77 For further comments/feedback, poke adrian@ .
80 The GNU roff toolchain has been removed from base. To render manpages
81 which are not supported by mandoc(1), man(1) can fallback on GNU roff
82 from ports (and recommends to install it).
83 To render roff(7) documents, consider using GNU roff from ports or the
84 heirloom doctools roff toolchain from ports via pkg install groff or
85 via pkg install heirloom-doctools.
88 The "ino64" 64-bit inode project has been committed, which extends
89 a number of types to 64 bits. Upgrading in place requires care and
90 adherence to the documented upgrade procedure.
92 If using a custom kernel configuration ensure that the
93 COMPAT_FREEBSD11 option is included (as during the upgrade the
94 system will be running the ino64 kernel with the existing world).
96 For the safest in-place upgrade begin by removing previous build
97 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
98 full procedure documented below under the heading "To rebuild
99 everything and install it on the current system." Specifically,
100 a reboot is required after installing the new kernel before
104 The NATM framework including the en(4), fatm(4), hatm(4), and
105 patm(4) devices has been removed. Consumers should plan a
106 migration before the end-of-life date for FreeBSD 11.
109 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
110 diff has not been implemented, if those are needed a newer version of
111 GNU diff is available via the diffutils package under the gdiff name.
114 As of r316810 for ipfilter, keep frags is no longer assumed when
115 keep state is specified in a rule. r316810 aligns ipfilter with
116 documentation in man pages separating keep frags from keep state.
117 This allows keep state to be specified without forcing keep frags
118 and allows keep frags to be specified independently of keep state.
119 To maintain previous behaviour, also specify keep frags with
120 keep state (as documented in ipf.conf.5).
123 arm64 builds now use the base system LLD 4.0.0 linker by default,
124 instead of requiring that the aarch64-binutils port or package be
125 installed. To continue using aarch64-binutils, set
126 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
129 The UDP optimization in entry 20160818 that added the sysctl
130 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
131 packets will no longer be treated as L3 broadcast packets.
134 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
135 use any explicitly assigned loopback address available in the jail
136 instead of using the first assigned address of the jail.
139 The ctl.ko module no longer implements the iSCSI target frontend:
140 cfiscsi.ko does instead.
142 If building cfiscsi.ko as a kernel module, the module can be loaded
143 via one of the following methods:
144 - `cfiscsi_load="YES"` in loader.conf(5).
145 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
146 - ctladm(8)/ctld(8), when compiled with iSCSI support
147 (`WITH_ISCSI=yes` in src.conf(5))
149 Please see cfiscsi(4) for more details.
152 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
153 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
154 same source (previously, the dependency of mmcsd.ko on mmc.ko was
155 missing, but mmcsd.ko now will refuse to load if it is incompatible
159 The syntax of ipfw(8) named states was changed to avoid ambiguity.
160 If you have used named states in the firewall rules, you need to modify
161 them after installworld and before rebooting. Now named states must
162 be prefixed with colon.
165 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
166 removed as the userland we provide cannot use them. The KMS version
167 (sys/dev/drm2) supports the same hardware.
170 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
171 Please see the 20141231 entry below for information about prerequisites
172 and upgrading, if you are not already using clang 3.5.0 or higher.
175 The code that provides support for ZFS .zfs/ directory functionality
176 has been reimplemented. It's not possible now to create a snapshot
177 by mkdir under .zfs/snapshot/. That should be the only user visible
181 EISA bus support has been removed. The WITH_EISA option is no longer
185 MCA bus support has been removed.
188 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
189 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
192 The EM_MULTIQUEUE kernel configuration option is deprecated now that
193 the em(4) driver conforms to iflib specifications.
196 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
197 IFLIB. If you have a custom kernel configuration that excludes em(4)
198 but you use igb(4), you need to re-add em(4) to your custom configuration.
201 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
202 Please see the 20141231 entry below for information about prerequisites
203 and upgrading, if you are not already using clang 3.5.0 or higher.
206 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
207 Please see the 20141231 entry below for information about prerequisites
208 and upgrading, if you are not already using clang 3.5.0 or higher.
211 The layout of the pmap structure has changed for powerpc to put the pmap
212 statistics at the front for all CPU variations. libkvm(3) and all tools
213 that link against it need to be recompiled.
216 isl(4) and cyapa(4) drivers now require a new driver,
217 chromebook_platform(4), to work properly on Chromebook-class hardware.
218 On other types of hardware the drivers may need to be configured using
219 device hints. Please see the corresponding manual pages for details.
222 The urtwn(4) driver was merged into rtwn(4) and now consists of
223 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
225 Also, firmware for RTL8188CE was renamed due to possible name
226 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
229 GNU rcs has been removed from base. It is available as packages:
230 - rcs: Latest GPLv3 GNU rcs version.
231 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
235 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
236 modules now requires that the kernel configuration contain the
237 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
240 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
241 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
244 Relocatable object files with the extension of .So have been renamed
245 to use an extension of .pico instead. The purpose of this change is
246 to avoid a name clash with shared libraries on case-insensitive file
247 systems. On those file systems, foo.So is the same file as foo.so.
250 GNU rcs has been turned off by default. It can (temporarily) be built
251 again by adding WITH_RCS knob in src.conf.
252 Otherwise, GNU rcs is available from packages:
253 - rcs: Latest GPLv3 GNU rcs version.
254 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
257 The backup_uses_rcs functionality has been removed from rc.subr.
260 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
261 two separate components, QUEUE_MACRO_DEBUG_TRACE and
262 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
263 QUEUE_MACRO_DEBUG behavior.
266 r304787 changed some ioctl interfaces between the iSCSI userspace
267 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
268 rebuilt to work with new kernels. __FreeBSD_version has been bumped
272 The UDP receive code has been updated to only treat incoming UDP
273 packets that were addressed to an L2 broadcast address as L3
274 broadcast packets. It is not expected that this will affect any
275 standards-conforming UDP application. The new behaviour can be
276 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
280 Remove the openbsd_poll system call.
281 __FreeBSD_version has been bumped because of this.
284 The libc stub for the pipe(2) system call has been replaced with
285 a wrapper that calls the pipe2(2) system call and the pipe(2)
286 system call is now only implemented by the kernels that include
287 "options COMPAT_FREEBSD10" in their config file (this is the
288 default). Users should ensure that this option is enabled in
289 their kernel or upgrade userspace to r302092 before upgrading their
293 CAM will now strip leading spaces from SCSI disks' serial numbers.
294 This will affect users who create UFS filesystems on SCSI disks using
295 those disk's diskid device nodes. For example, if /etc/fstab
296 previously contained a line like
297 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
298 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
299 transforms like gmirror may also be affected. ZFS users should
303 The bitstring(3) API has been updated with new functionality and
304 improved performance. But it is binary-incompatible with the old API.
305 Objects built with the new headers may not be linked against objects
306 built with the old headers.
309 The brk and sbrk functions have been removed from libc on arm64.
310 Binutils from ports has been updated to not link to these
311 functions and should be updated to the latest version before
312 installing a new libc.
315 The armv6 port now defaults to hard float ABI. Limited support
316 for running both hardfloat and soft float on the same system
317 is available using the libraries installed with -DWITH_LIBSOFT.
318 This has only been tested as an upgrade path for installworld
319 and packages may fail or need manual intervention to run. New
320 packages will be needed.
322 To update an existing self-hosted armv6hf system, you must add
323 TARGET_ARCH=armv6 on the make command line for both the build
324 and the install steps.
327 Kernel modules compiled outside of a kernel build now default to
328 installing to /boot/modules instead of /boot/kernel. Many kernel
329 modules built this way (such as those in ports) already overrode
330 KMODDIR explicitly to install into /boot/modules. However,
331 manually building and installing a module from /sys/modules will
332 now install to /boot/modules instead of /boot/kernel.
335 The CAM I/O scheduler has been committed to the kernel. There should be
336 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
337 list of known rogues that claim support for this but actually corrupt
338 data is believed to be complete, be on the lookout for data
339 corruption. The known rogue list is believed to be complete:
341 o Crucial MX100, M550 drives with MU01 firmware.
342 o Micron M510 and M550 drives with MU01 firmware.
343 o Micron M500 prior to MU07 firmware
344 o Samsung 830, 840, and 850 all firmwares
345 o FCCT M500 all firmwares
347 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
348 with working NCQ TRIM. For Micron branded drives, see your sales rep for
349 updated firmware. Black listed drives will work correctly because these
350 drives work correctly so long as no NCQ TRIMs are sent to them. Given
351 this list is the same as found in Linux, it's believed there are no
352 other rogues in the market place. All other models from the above
355 To be safe, if you are at all concerned, you can quirk each of your
356 drives to prevent NCQ from being sent by setting:
357 kern.cam.ada.X.quirks="0x2"
358 in loader.conf. If the drive requires the 4k sector quirk, set the
362 The FAST_DEPEND build option has been removed and its functionality is
363 now the one true way. The old mkdep(1) style of 'make depend' has
364 been removed. See 20160311 for further details.
367 Resource range types have grown from unsigned long to uintmax_t. All
368 drivers, and anything using libdevinfo, need to be recompiled.
371 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
372 builds. It no longer runs mkdep(1) during 'make depend', and the
373 'make depend' stage can safely be skipped now as it is auto ran
374 when building 'make all' and will generate all SRCS and DPSRCS before
375 building anything else. Dependencies are gathered at compile time with
376 -MF flags kept in separate .depend files per object file. Users should
377 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
381 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
382 kernel modules. Therefore, if you load any kernel modules at boot time,
383 please install the boot loaders after you install the kernel, but before
387 make kernel KERNCONF=YOUR_KERNEL_HERE
388 make -C sys/boot install
389 <reboot in single user>
391 Then follow the usual steps, described in the General Notes section,
395 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
396 see the 20141231 entry below for information about prerequisites and
397 upgrading, if you are not already using clang 3.5.0 or higher.
400 The AIO subsystem is now a standard part of the kernel. The
401 VFS_AIO kernel option and aio.ko kernel module have been removed.
402 Due to stability concerns, asynchronous I/O requests are only
403 permitted on sockets and raw disks by default. To enable
404 asynchronous I/O requests on all file types, set the
405 vfs.aio.enable_unsafe sysctl to a non-zero value.
408 The ELF object manipulation tool objcopy is now provided by the
409 ELF Tool Chain project rather than by GNU binutils. It should be a
410 drop-in replacement, with the addition of arm64 support. The
411 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
412 to obtain the GNU version if necessary.
415 Building ZFS pools on top of zvols is prohibited by default. That
416 feature has never worked safely; it's always been prone to deadlocks.
417 Using a zvol as the backing store for a VM guest's virtual disk will
418 still work, even if the guest is using ZFS. Legacy behavior can be
419 restored by setting vfs.zfs.vol.recursive=1.
422 The NONE and HPN patches has been removed from OpenSSH. They are
423 still available in the security/openssh-portable port.
426 With the addition of ypldap(8), a new _ypldap user is now required
427 during installworld. "mergemaster -p" can be used to add the user
428 prior to installworld, as documented in the handbook.
431 The tftp loader (pxeboot) now uses the option root-path directive. As a
432 consequence it no longer looks for a pxeboot.4th file on the tftp
433 server. Instead it uses the regular /boot infrastructure as with the
437 The code to start recording plug and play data into the modules has
438 been committed. While the old tools will properly build a new kernel,
439 a number of warnings about "unknown metadata record 4" will be produced
440 for an older kldxref. To avoid such warnings, make sure to rebuild
441 the kernel toolchain (or world). Make sure that you have r292078 or
442 later when trying to build 292077 or later before rebuilding.
445 Debug data files are now built by default with 'make buildworld' and
446 installed with 'make installworld'. This facilitates debugging but
447 requires more disk space both during the build and for the installed
448 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
452 r291527 changed the internal interface between the nfsd.ko and
453 nfscommon.ko modules. As such, they must both be upgraded to-gether.
454 __FreeBSD_version has been bumped because of this.
457 Add support for unicode collation strings leads to a change of
458 order of files listed by ls(1) for example. To get back to the old
459 behaviour, set LC_COLLATE environment variable to "C".
461 Databases administrators will need to reindex their databases given
462 collation results will be different.
464 Due to a bug in install(1) it is recommended to remove the ancient
465 locales before running make installworld.
467 rm -rf /usr/share/locale/*
470 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
471 libcrypto.so.7 or libssl.so.7 must be recompiled.
474 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
475 Kernel modules isp_2400_multi and isp_2500_multi were removed and
476 should be replaced with isp_2400 and isp_2500 modules respectively.
479 The build previously allowed using 'make -n' to not recurse into
480 sub-directories while showing what commands would be executed, and
481 'make -n -n' to recursively show commands. Now 'make -n' will recurse
482 and 'make -N' will not.
485 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
486 and etcupdate will now use this file. A custom sendmail.cf is now
487 updated via this mechanism rather than via installworld. If you had
488 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
489 want to remove the exclusion or change it to "always install".
490 /etc/mail/sendmail.cf is now managed the same way regardless of
491 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
492 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
495 Compatibility shims for legacy ATA device names have been removed.
496 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
497 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
498 environment variables, /dev/ad* and /dev/ar* symbolic links.
501 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
502 Please see the 20141231 entry below for information about prerequisites
503 and upgrading, if you are not already using clang 3.5.0 or higher.
506 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
507 and renamed from .symbols to .debug. This reduces the size requirements
508 on the boot partition or file system and provides consistency with
509 userland debug files.
511 When using the supported kernel installation method the
512 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
513 as is done with /boot/kernel.
515 Developers wishing to maintain the historical behavior of installing
516 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
519 The wireless drivers had undergone changes that remove the 'parent
520 interface' from the ifconfig -l output. The rc.d network scripts
521 used to check presence of a parent interface in the list, so old
522 scripts would fail to start wireless networking. Thus, etcupdate(3)
523 or mergemaster(8) run is required after kernel update, to update your
524 rc.d scripts in /etc.
527 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
528 These configurations are now automatically interpreted as
529 'scrub fragment reassemble'.
532 Kernel-loadable modules for the random(4) device are back. To use
533 them, the kernel must have
536 options RANDOM_LOADABLE
538 kldload(8) can then be used to load random_fortuna.ko
539 or random_yarrow.ko. Please note that due to the indirect
540 function calls that the loadable modules need to provide,
541 the build-in variants will be slightly more efficient.
543 The random(4) kernel option RANDOM_DUMMY has been retired due to
544 unpopularity. It was not all that useful anyway.
547 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
548 Control over building the ELF Tool Chain tools is now provided by
549 the WITHOUT_TOOLCHAIN knob.
552 The polarity of Pulse Per Second (PPS) capture events with the
553 uart(4) driver has been corrected. Prior to this change the PPS
554 "assert" event corresponded to the trailing edge of a positive PPS
555 pulse and the "clear" event was the leading edge of the next pulse.
557 As the width of a PPS pulse in a typical GPS receiver is on the
558 order of 1 millisecond, most users will not notice any significant
559 difference with this change.
561 Anyone who has compensated for the historical polarity reversal by
562 configuring a negative offset equal to the pulse width will need to
563 remove that workaround.
566 The default group assigned to /dev/dri entries has been changed
567 from 'wheel' to 'video' with the id of '44'. If you want to have
568 access to the dri devices please add yourself to the video group
571 # pw groupmod video -m $USER
574 The menu.rc and loader.rc files will now be replaced during
575 upgrades. Please migrate local changes to menu.rc.local and
576 loader.rc.local instead.
579 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
580 strings and strip have been removed. The src.conf(5) knob
581 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
584 As ZFS requires more kernel stack pages than is the default on some
585 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
586 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
588 Please consider using 'options KSTACK_PAGES=X' where X is greater
589 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
592 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
593 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
594 default, i.e., they will not contain "::". For example, instead
595 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
596 to have a more specific match, such as different map entries for
597 IPv6:0:0 vs IPv6:0. This change requires that configuration
598 data (including maps, files, classes, custom ruleset, etc.) must
599 use the same format, so make certain such configuration data is
600 upgrading. As a very simple check search for patterns like
601 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
602 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
603 the cf option UseCompressedIPv6Addresses.
606 The default kernel entropy-processing algorithm is now
607 Fortuna, replacing Yarrow.
609 Assuming you have 'device random' in your kernel config
610 file, the configurations allow a kernel option to override
611 this default. You may choose *ONE* of:
613 options RANDOM_YARROW # Legacy /dev/random algorithm.
614 options RANDOM_DUMMY # Blocking-only driver.
616 If you have neither, you get Fortuna. For most people,
617 read no further, Fortuna will give a /dev/random that works
618 like it always used to, and the difference will be irrelevant.
620 If you remove 'device random', you get *NO* kernel-processed
621 entropy at all. This may be acceptable to folks building
622 embedded systems, but has complications. Carry on reading,
623 and it is assumed you know what you need.
625 *PLEASE* read random(4) and random(9) if you are in the
626 habit of tweaking kernel configs, and/or if you are a member
627 of the embedded community, wanting specific and not-usual
628 behaviour from your security subsystems.
630 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
631 random', you will NOT have a functioning /dev/random, and
632 many cryptographic features will not work, including SSH.
633 You may also find strange behaviour from the random(3) set
634 of library functions, in particular sranddev(3), srandomdev(3)
635 and arc4random(3). The reason for this is that the KERN_ARND
636 sysctl only returns entropy if it thinks it has some to
637 share, and with RANDOM_DUMMY or no 'device random' this
641 An additional fix for the issue described in the 20150614 sendmail
642 entry below has been been committed in revision 284717.
645 FreeBSD's old make (fmake) has been removed from the system. It is
646 available as the devel/fmake port or via pkg install fmake.
649 The fix for the issue described in the 20150614 sendmail entry
650 below has been been committed in revision 284436. The work
651 around described in that entry is no longer needed unless the
652 default setting is overridden by a confDH_PARAMETERS configuration
653 setting of '5' or pointing to a 512 bit DH parameter file.
656 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
657 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
658 and devel/kyua to version 0.20+ and adjust any calling code to work
659 with Kyuafile and kyua.
662 The import of openssl to address the FreeBSD-SA-15:10.openssl
663 security advisory includes a change which rejects handshakes
664 with DH parameters below 768 bits. sendmail releases prior
665 to 8.15.2 (not yet released), defaulted to a 512 bit
666 DH parameter setting for client connections. To work around
667 this interoperability, sendmail can be configured to use a
668 2048 bit DH parameter by:
670 1. Edit /etc/mail/`hostname`.mc
671 2. If a setting for confDH_PARAMETERS does not exist or
672 exists and is set to a string beginning with '5',
674 3. If a setting for confDH_PARAMETERS exists and is set to
675 a file path, create a new file with:
676 openssl dhparam -out /path/to/file 2048
677 4. Rebuild the .cf file:
678 cd /etc/mail/; make; make install
680 cd /etc/mail/; make restart
682 A sendmail patch is coming, at which time this file will be
686 Generation of legacy formatted entries have been disabled by default
687 in pwd_mkdb(8), as all base system consumers of the legacy formatted
688 entries were converted to use the new format by default when the new,
689 machine independent format have been added and supported since FreeBSD
692 Please see the pwd_mkdb(8) manual page for further details.
695 Clang and llvm have been upgraded to 3.6.1 release. Please see the
696 20141231 entry below for information about prerequisites and upgrading,
697 if you are not already using 3.5.0 or higher.
700 TI platform code switched to using vendor DTS files and this update
701 may break existing systems running on Beaglebone, Beaglebone Black,
704 - dtb files should be regenerated/reinstalled. Filenames are the
705 same but content is different now
706 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
707 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
708 addressing scheme is now pin 25 on /dev/gpioc3.
709 - Pandaboard: /etc/ttys should be updated, serial console device is
710 now /dev/ttyu2, not /dev/ttyu0
713 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
714 If you need the GNU extension from groff soelim(1), install groff
715 from package: pkg install groff, or via ports: textproc/groff.
718 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
719 defined in symlink(7); previously symlinks were silently ignored.
722 The const qualifier has been removed from iconv(3) to comply with
723 POSIX. The ports tree is aware of this from r384038 onwards.
726 Libraries specified by LIBADD in Makefiles must have a corresponding
727 DPADD_<lib> variable to ensure correct dependencies. This is now
728 enforced in src.libnames.mk.
731 From legacy ata(4) driver was removed support for SATA controllers
732 supported by more functional drivers ahci(4), siis(4) and mvs(4).
733 Kernel modules ataahci and ataadaptec were removed completely,
734 replaced by ahci and mvs modules respectively.
737 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
738 the 20141231 entry below for information about prerequisites and
739 upgrading, if you are not already using 3.5.0 or higher.
742 The 32-bit PowerPC kernel has been changed to a position-independent
743 executable. This can only be booted with a version of loader(8)
744 newer than January 31, 2015, so make sure to update both world and
745 kernel before rebooting.
748 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
749 but before r278950, the RNG was not seeded properly. Immediately
750 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
751 ssh keys or openssl keys) that were generated w/ a kernel from that
752 range. This does not affect programs that directly used /dev/random
753 or /dev/urandom. All userland uses of arc4random(3) are affected.
756 The autofs(4) ABI was changed in order to restore binary compatibility
757 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
761 The powerpc64 kernel has been changed to a position-independent
762 executable. This can only be booted with a new version of loader(8),
763 so make sure to update both world and kernel before rebooting.
766 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
767 only release, no new features have been added. Please see the 20141231
768 entry below for information about prerequisites and upgrading, if you
769 are not already using 3.5.0.
772 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
773 taken from the ELF Tool Chain project rather than GNU binutils. They
774 should be drop-in replacements, with the addition of arm64 support.
775 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
776 binutils tools, if necessary. See 20150805 for updated information.
779 The default Unbound configuration now enables remote control
780 using a local socket. Users who have already enabled the
781 local_unbound service should regenerate their configuration
782 by running "service local_unbound setup" as root.
785 The GNU texinfo and GNU info pages have been removed.
786 To be able to view GNU info pages please install texinfo from ports.
789 Clang, llvm and lldb have been upgraded to 3.5.0 release.
791 As of this release, a prerequisite for building clang, llvm and lldb is
792 a C++11 capable compiler and C++11 standard library. This means that to
793 be able to successfully build the cross-tools stage of buildworld, with
794 clang as the bootstrap compiler, your system compiler or cross compiler
795 should either be clang 3.3 or later, or gcc 4.8 or later, and your
796 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
799 On any standard FreeBSD 10.x or 11.x installation, where clang and
800 libc++ are on by default (that is, on x86 or arm), this should work out
803 On 9.x installations where clang is enabled by default, e.g. on x86 and
804 powerpc, libc++ will not be enabled by default, so libc++ should be
805 built (with clang) and installed first. If both clang and libc++ are
806 missing, build clang first, then use it to build libc++.
808 On 8.x and earlier installations, upgrade to 9.x first, and then follow
809 the instructions for 9.x above.
811 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
812 default, and do not build clang.
814 Many embedded systems are resource constrained, and will not be able to
815 build clang in a reasonable time, or in some cases at all. In those
816 cases, cross building bootable systems on amd64 is a workaround.
818 This new version of clang introduces a number of new warnings, of which
819 the following are most likely to appear:
823 This warns in two cases, for both C and C++:
824 * When the code is trying to take the absolute value of an unsigned
825 quantity, which is effectively a no-op, and almost never what was
826 intended. The code should be fixed, if at all possible. If you are
827 sure that the unsigned quantity can be safely cast to signed, without
828 loss of information or undefined behavior, you can add an explicit
829 cast, or disable the warning.
831 * When the code is trying to take an absolute value, but the called
832 abs() variant is for the wrong type, which can lead to truncation.
833 If you want to disable the warning instead of fixing the code, please
834 make sure that truncation will not occur, or it might lead to unwanted
837 -Wtautological-undefined-compare and
838 -Wundefined-bool-conversion
840 These warn when C++ code is trying to compare 'this' against NULL, while
841 'this' should never be NULL in well-defined C++ code. However, there is
842 some legacy (pre C++11) code out there, which actively abuses this
843 feature, which was less strictly defined in previous C++ versions.
845 Squid and openjdk do this, for example. The warning can be turned off
846 for C++98 and earlier, but compiling the code in C++11 mode might result
847 in unexpected behavior; for example, the parts of the program that are
848 unreachable could be optimized away.
851 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
852 kernel sources have been removed. The .h files remain, since some
853 utilities include them. This will need to be fixed later.
854 If "mount -t oldnfs ..." is attempted, it will fail.
855 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
856 the utilities will report errors.
859 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
860 directories to top level SUBDIR variable when their parent
861 directory is included in LOCAL_DIRS. Users with build systems with
862 such hierarchies and without SUBDIR entries in the parent
863 directory Makefiles should add them or add the directories to
867 faith(4) and faithd(8) have been removed from the base system. Faith
868 has been obsolete for a very long time.
871 vt(4), the new console driver, is enabled by default. It brings
872 support for Unicode and double-width characters, as well as
873 support for UEFI and integration with the KMS kernel video
876 You may need to update your console settings in /etc/rc.conf,
877 most probably the keymap. During boot, /etc/rc.d/syscons will
878 indicate what you need to do.
880 vt(4) still has issues and lacks some features compared to
881 syscons(4). See the wiki for up-to-date information:
882 https://wiki.freebsd.org/Newcons
884 If you want to keep using syscons(4), you can do so by adding
885 the following line to /boot/loader.conf:
889 pjdfstest has been integrated into kyua as an opt-in test suite.
890 Please see share/doc/pjdfstest/README for more details on how to
894 gperf has been removed from the base system for architectures
895 that use clang. Ports that require gperf will obtain it from the
899 pjdfstest has been moved from tools/regression/pjdfstest to
903 At svn r271982, The default linux compat kernel ABI has been adjusted
904 to 2.6.18 in support of the linux-c6 compat ports infrastructure
905 update. If you wish to continue using the linux-f10 compat ports,
906 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
907 encouraged to update their linux-compat packages to linux-c6 during
908 their next update cycle.
911 The ofwfb driver, used to provide a graphics console on PowerPC when
912 using vt(4), no longer allows mmap() of all physical memory. This
913 will prevent Xorg on PowerPC with some ATI graphics cards from
914 initializing properly unless x11-servers/xorg-server is updated to
918 The xdev targets have been converted to using TARGET and
919 TARGET_ARCH instead of XDEV and XDEV_ARCH.
922 The default unbound configuration has been modified to address
923 issues with reverse lookups on networks that use private
924 address ranges. If you use the local_unbound service, run
925 "service local_unbound setup" as root to regenerate your
926 configuration, then "service local_unbound reload" to load the
930 The GNU texinfo and GNU info pages are not built and installed
931 anymore, WITH_INFO knob has been added to allow to built and install
933 UPDATE: see 20150102 entry on texinfo's removal
936 The GNU readline library is now an INTERNALLIB - that is, it is
937 statically linked into consumers (GDB and variants) in the base
938 system, and the shared library is no longer installed. The
939 devel/readline port is available for third party software that
943 The Itanium architecture (ia64) has been removed from the list of
944 known architectures. This is the first step in the removal of the
948 Commit r268115 has added NFSv4.1 server support, merged from
949 projects/nfsv4.1-server. Since this includes changes to the
950 internal interfaces between the NFS related modules, a full
951 build of the kernel and modules will be necessary.
952 __FreeBSD_version has been bumped.
955 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
956 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
957 which differs from the behaviour controlled by this knob.)
960 Maximal length of the serial number in CTL was increased from 16 to
961 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
962 and ctld, need to be rebuilt to work with a new kernel.
965 The libatf-c and libatf-c++ major versions were downgraded to 0 and
966 1 respectively to match the upstream numbers. They were out of
967 sync because, when they were originally added to FreeBSD, the
968 upstream versions were not respected. These libraries are private
969 and not yet built by default, so renumbering them should be a
970 non-issue. However, unclean source trees will yield broken test
971 programs once the operator executes "make delete-old-libs" after a
974 Additionally, the atf-sh binary was made private by moving it into
975 /usr/libexec/. Already-built shell test programs will keep the
976 path to the old binary so they will break after "make delete-old"
979 If you are using WITH_TESTS=yes (not the default), wipe the object
980 tree and rebuild from scratch to prevent spurious test failures.
981 This is only needed once: the misnumbered libraries and misplaced
982 binaries have been added to OptionalObsoleteFiles.inc so they will
983 be removed during a clean upgrade.
986 Clang and llvm have been upgraded to 3.4.1 release.
989 We bogusly installed src.opts.mk in /usr/share/mk. This file should
990 be removed to avoid issues in the future (and has been added to
994 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
995 past, it affected all builds that used the bsd.*.mk files. The old
996 behavior was a bug, but people may have relied upon it. To get this
997 behavior back, you can .include /etc/src.conf from /etc/make.conf
998 (which is still global and isn't changed). This also changes the
999 behavior of incremental builds inside the tree of individual
1000 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1001 Although this has survived make universe and some upgrade scenarios,
1002 other upgrade scenarios may have broken. At least one form of
1003 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1004 as well... In cases where MAKESYSPATH isn't working with this
1005 setting, you'll need to set it to the full path to your tree.
1007 One side effect of all this cleaning up is that bsd.compiler.mk
1008 is no longer implicitly included by bsd.own.mk. If you wish to
1009 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1013 The lindev device has been removed since /dev/full has been made a
1014 standard device. __FreeBSD_version has been bumped.
1017 The knob WITHOUT_VI was added to the base system, which controls
1018 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1019 in order to reorder files share/termcap and didn't build ex(1) as a
1020 build tool, so building/installing with WITH_VI is highly advised for
1021 build hosts for older releases.
1023 This issue has been fixed in stable/9 and stable/10 in r277022 and
1024 r276991, respectively.
1027 The YES_HESIOD knob has been removed. It has been obsolete for
1028 a decade. Please move to using WITH_HESIOD instead or your builds
1029 will silently lack HESIOD.
1032 The uart(4) driver has been changed with respect to its handling
1033 of the low-level console. Previously the uart(4) driver prevented
1034 any process from changing the baudrate or the CLOCAL and HUPCL
1035 control flags. By removing the restrictions, operators can make
1036 changes to the serial console port without having to reboot.
1037 However, when getty(8) is started on the serial device that is
1038 associated with the low-level console, a misconfigured terminal
1039 line in /etc/ttys will now have a real impact.
1040 Before upgrading the kernel, make sure that /etc/ttys has the
1041 serial console device configured as 3wire without baudrate to
1042 preserve the previous behaviour. E.g:
1043 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1046 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1047 to improve performance. To re-enable it, if needed, run rpcbind
1048 with command line option -W.
1051 Switched back to the GPL dtc compiler due to updates in the upstream
1052 dts files not being supported by the BSDL dtc compiler. You will need
1053 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1054 may result while building dtb files during a kernel build if you fail
1055 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1058 Clang and llvm have been upgraded to 3.4 release.
1061 The nve(4) driver has been removed. Please use the nfe(4) driver
1062 for NVIDIA nForce MCP Ethernet adapters instead.
1065 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1066 This could cause certain C++ applications using shared libraries built
1067 against the previous version of libc++ to crash. The incompatibility
1068 has now been fixed, but any C++ applications or shared libraries built
1069 between r261283 and r261801 should be recompiled.
1072 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1073 capability mode support. Please note that enabling the feature in
1074 kernel is still highly recommended.
1077 OpenSSH is now built with sandbox support, and will use sandbox as
1078 the default privilege separation method. This requires Capsicum
1079 capability mode support in kernel.
1082 The libelf and libdwarf libraries have been updated to newer
1083 versions from upstream. Shared library version numbers for
1084 these two libraries were bumped. Any ports or binaries
1085 requiring these two libraries should be recompiled.
1086 __FreeBSD_version is bumped to 1100006.
1089 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1090 instead of providing an explicit one, this would prevent such
1091 Makefile from providing its own Kyuafile in the future during
1092 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1093 intervention is needed to clean an objdir if you use NO_CLEAN:
1094 # find /usr/obj -name Kyuafile | xargs rm -f
1097 The behavior of gss_pseudo_random() for the krb5 mechanism
1098 has changed, for applications requesting a longer random string
1099 than produced by the underlying enctype's pseudo-random() function.
1100 In particular, the random string produced from a session key of
1101 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1102 be different at the 17th octet and later, after this change.
1103 The counter used in the PRF+ construction is now encoded as a
1104 big-endian integer in accordance with RFC 4402.
1105 __FreeBSD_version is bumped to 1100004.
1108 The WITHOUT_ATF build knob has been removed and its functionality
1109 has been subsumed into the more generic WITHOUT_TESTS. If you were
1110 using the former to disable the build of the ATF libraries, you
1111 should change your settings to use the latter.
1114 The default version of mtree is nmtree which is obtained from
1115 NetBSD. The output is generally the same, but may vary
1116 slightly. If you found you need identical output adding
1117 "-F freebsd9" to the command line should do the trick. For the
1118 time being, the old mtree is available as fmtree.
1121 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1122 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1123 1.1.4_8 and verify bsdyml not linked in, before running "make
1125 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1127 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1130 The stable/10 branch has been created in subversion from head
1134 The rc.d/jail script has been updated to support jail(8)
1135 configuration file. The "jail_<jname>_*" rc.conf(5) variables
1136 for per-jail configuration are automatically converted to
1137 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
1138 This is transparently backward compatible. See below about some
1139 incompatibilities and rc.conf(5) manual page for more details.
1141 These variables are now deprecated in favor of jail(8) configuration
1142 file. One can use "rc.d/jail config <jname>" command to generate
1143 a jail(8) configuration file in /var/run/jail.<jname>.conf without
1144 running the jail(8) utility. The default pathname of the
1145 configuration file is /etc/jail.conf and can be specified by
1146 using $jail_conf or $jail_<jname>_conf variables.
1148 Please note that jail_devfs_ruleset accepts an integer at
1149 this moment. Please consider to rewrite the ruleset name
1153 BIND has been removed from the base system. If all you need
1154 is a local resolver, simply enable and start the local_unbound
1155 service instead. Otherwise, several versions of BIND are
1156 available in the ports tree. The dns/bind99 port is one example.
1158 With this change, nslookup(1) and dig(1) are no longer in the base
1159 system. Users should instead use host(1) and drill(1) which are
1160 in the base system. Alternatively, nslookup and dig can
1161 be obtained by installing the dns/bind-tools port.
1164 With the addition of unbound(8), a new unbound user is now
1165 required during installworld. "mergemaster -p" can be used to
1166 add the user prior to installworld, as documented in the handbook.
1169 OpenSSH is now built with DNSSEC support, and will by default
1170 silently trust signed SSHFP records. This can be controlled with
1171 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1172 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1175 The GNU Compiler Collection and C++ standard library (libstdc++)
1176 are no longer built by default on platforms where clang is the system
1177 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1178 options in src.conf.
1181 The PROCDESC kernel option is now part of the GENERIC kernel
1182 configuration and is required for the rwhod(8) to work.
1183 If you are using custom kernel configuration, you should include
1187 The API and ABI related to the Capsicum framework was modified
1188 in backward incompatible way. The userland libraries and programs
1189 have to be recompiled to work with the new kernel. This includes the
1190 following libraries and programs, but the whole buildworld is
1191 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1192 kdump, procstat, rwho, rwhod, uniq.
1195 AES-NI intrinsic support has been added to gcc. The AES-NI module
1196 has been updated to use this support. A new gcc is required to build
1197 the aesni module on both i386 and amd64.
1200 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1201 Thus "device padlock_rng" and "device rdrand_rng" should be
1202 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1205 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1206 enables just the iconv* functionality and is now on by default.
1207 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1208 compatibility. Set WITHOUT_ICONV to build the old way.
1209 If you have been using WITH_ICONV before, you will very likely
1210 need to turn on WITH_LIBICONV_COMPAT.
1213 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1214 Illumos origin, including ZFS. If you have INVARIANTS in your
1215 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1217 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1218 locks if WITNESS option was set. Because that generated a lot of
1219 witness(9) reports and all of them were believed to be false
1220 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1221 can be used to achieve the previous behavior.
1224 Timer values in IPv6 data structures now use time_uptime instead
1225 of time_second. Although this is not a user-visible functional
1226 change, userland utilities which directly use them---ndp(8),
1227 rtadvd(8), and rtsold(8) in the base system---need to be updated
1228 to r253970 or later.
1231 find -delete can now delete the pathnames given as arguments,
1232 instead of only files found below them or if the pathname did
1233 not contain any slashes. Formerly, the following error message
1236 find: -delete: <path>: relative path potentially not safe
1238 Deleting the pathnames given as arguments can be prevented
1239 without error messages using -mindepth 1 or by changing
1240 directory and passing "." as argument to find. This works in the
1241 old as well as the new version of find.
1244 Behavior of devfs rules path matching has been changed.
1245 Pattern is now always matched against fully qualified devfs
1246 path and slash characters must be explicitly matched by
1247 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1248 subdirectories must be reviewed.
1251 The default ARM ABI has changed to the ARM EABI. The old ABI is
1252 incompatible with the ARM EABI and all programs and modules will
1253 need to be rebuilt to work with a new kernel.
1255 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1257 NOTE: Support for the old ABI will be removed in the future and
1258 users are advised to upgrade.
1261 pkg_install has been disconnected from the build if you really need it
1262 you should add WITH_PKGTOOLS in your src.conf(5).
1265 Most of network statistics structures were changed to be able
1266 keep 64-bits counters. Thus all tools, that work with networking
1267 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1270 Fix a bug that allowed a tracing process (e.g. gdb) to write
1271 to a memory-mapped file in the traced process's address space
1272 even if neither the traced process nor the tracing process had
1273 write access to that file.
1276 CVS has been removed from the base system. An exact copy
1277 of the code is available from the devel/cvs port.
1280 Some people report the following error after the switch to bmake:
1282 make: illegal option -- J
1283 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1285 *** [buildworld] Error code 2
1287 this likely due to an old instance of make in
1288 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1289 which src/Makefile will use that blindly, if it exists, so if
1290 you see the above error:
1292 rm -rf `make -V MAKEPATH`
1297 Use bmake by default.
1298 Whereas before one could choose to build with bmake via
1299 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1300 make. The goal is to remove these knobs for 10-RELEASE.
1302 It is worth noting that bmake (like gmake) treats the command
1303 line as the unit of failure, rather than statements within the
1304 command line. Thus '(cd some/where && dosomething)' is safer
1305 than 'cd some/where; dosomething'. The '()' allows consistent
1306 behavior in parallel build.
1309 Fix a bug that allows NFS clients to issue READDIR on files.
1312 The WITHOUT_IDEA option has been removed because
1313 the IDEA patent expired.
1316 The sysctl which controls TRIM support under ZFS has been renamed
1317 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1321 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1322 rather than creating it's own in the temporary directory in
1323 order allow access to bootstrapped versions of tools such as
1324 install and mtree. When upgrading from version of FreeBSD where
1325 the install command does not support -l, you will need to
1326 install a new mergemaster command if mergemaster -p is required.
1327 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1331 Legacy ATA stack, disabled and replaced by new CAM-based one since
1332 FreeBSD 9.0, completely removed from the sources. Kernel modules
1333 atadisk and atapi*, user-level tools atacontrol and burncd are
1334 removed. Kernel option `options ATA_CAM` is now permanently enabled
1338 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1339 and socketpair(2). Software, in particular Kerberos, may
1340 automatically detect and use these during building. The resulting
1341 binaries will not work on older kernels.
1344 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1345 information, see the respective 20130304 entry).
1348 Recent commits to callout(9) changed the size of struct callout,
1349 so the KBI is probably heavily disturbed. Also, some functions
1350 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1351 by macros. Every kernel module using it won't load, so rebuild
1354 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1355 but does not initialize by default (because of the new CTL_DISABLE
1356 option) to save memory. To re-enable it, remove the CTL_DISABLE
1357 option from the kernel config file or set kern.cam.ctl.disable=0
1358 in /boot/loader.conf.
1361 The ctl device has been disabled in GENERIC for i386 and amd64.
1362 This was done due to the extra memory being allocated at system
1363 initialisation time by the ctl driver which was only used if
1364 a CAM target device was created. This makes a FreeBSD system
1365 unusable on 128MB or less of RAM.
1368 A new compression method (lz4) has been merged to -HEAD. Please
1369 refer to zpool-features(7) for more information.
1371 Please refer to the "ZFS notes" section of this file for information
1372 on upgrading boot ZFS pools.
1375 A BSD-licensed patch(1) variant has been added and is installed
1376 as bsdpatch, being the GNU version the default patch.
1377 To inverse the logic and use the BSD-licensed one as default,
1378 while having the GNU version installed as gnupatch, rebuild
1379 and install world with the WITH_BSD_PATCH knob set.
1382 Due to the use of the new -l option to install(1) during build
1383 and install, you must take care not to directly set the INSTALL
1384 make variable in your /etc/make.conf, /etc/src.conf, or on the
1385 command line. If you wish to use the -C flag for all installs
1386 you may be able to add INSTALL+=-C to /etc/make.conf or
1390 The install(1) option -M has changed meaning and now takes an
1391 argument that is a file or path to append logs to. In the
1392 unlikely event that -M was the last option on the command line
1393 and the command line contained at least two files and a target
1394 directory the first file will have logs appended to it. The -M
1395 option served little practical purpose in the last decade so its
1396 use is expected to be extremely rare.
1399 After switching to Clang as the default compiler some users of ZFS
1400 on i386 systems started to experience stack overflow kernel panics.
1401 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1404 GEOM_LABEL now mangles label names read from file system metadata.
1405 Mangling affect labels containing spaces, non-printable characters,
1406 '%' or '"'. Device names in /etc/fstab and other places may need to
1410 By default, only the 10 most recent kernel dumps will be saved. To
1411 restore the previous behaviour (no limit on the number of kernel dumps
1412 stored in the dump directory) add the following line to /etc/rc.conf:
1417 With the addition of auditdistd(8), a new auditdistd user is now
1418 required during installworld. "mergemaster -p" can be used to
1419 add the user prior to installworld, as documented in the handbook.
1422 The sin6_scope_id member variable in struct sockaddr_in6 is now
1423 filled by the kernel before passing the structure to the userland via
1424 sysctl or routing socket. This means the KAME-specific embedded scope
1425 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1426 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1427 __FreeBSD_version is bumped to 1000025.
1430 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1431 This means that the world and kernel will be compiled with clang
1432 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1433 and /usr/bin/cpp. To disable this behavior and revert to building
1434 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1435 of current may need to bootstrap WITHOUT_CLANG first if the clang
1436 build fails (its compatibility window doesn't extend to the 9 stable
1440 The IPFIREWALL_FORWARD kernel option has been removed. Its
1441 functionality now turned on by default.
1444 The ZERO_COPY_SOCKET kernel option has been removed and
1445 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1446 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1447 mechanism which is not safe and may result in kernel crashes.
1448 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1449 driver supports disposeable external page sized mbuf storage.
1450 Proper replacements for both zero-copy mechanisms are under
1451 consideration and will eventually lead to complete removal
1452 of the two kernel options.
1455 The IPv4 network stack has been converted to network byte
1456 order. The following modules need to be recompiled together
1457 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1458 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1461 Support for non-MPSAFE filesystems was removed from VFS. The
1462 VFS_VERSION was bumped, all filesystem modules shall be
1466 All the non-MPSAFE filesystems have been disconnected from
1467 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1468 portalfs, smbfs, xfs.
1471 The interface cloning API and ABI has changed. The following
1472 modules need to be recompiled together with kernel:
1473 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1474 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1475 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1478 The sdhci driver was split in two parts: sdhci (generic SD Host
1479 Controller logic) and sdhci_pci (actual hardware driver).
1480 No kernel config modifications are required, but if you
1481 load sdhc as a module you must switch to sdhci_pci instead.
1484 Import the FUSE kernel and userland support into base system.
1487 The GNU sort(1) program has been removed since the BSD-licensed
1488 sort(1) has been the default for quite some time and no serious
1489 problems have been reported. The corresponding WITH_GNU_SORT
1493 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1494 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1498 The net80211(4) ABI has been changed to allow for improved driver
1499 PS-POLL and power-save support. All wireless drivers need to be
1500 recompiled to work with the new kernel.
1503 The random(4) support for the VIA hardware random number
1504 generator (`PADLOCK') is no longer enabled unconditionally.
1505 Add the padlock_rng device in the custom kernel config if
1506 needed. The GENERIC kernels on i386 and amd64 do include the
1507 device, so the change only affects the custom kernel
1511 The pf(4) packet filter ABI has been changed. pfctl(8) and
1512 snmp_pf module need to be recompiled to work with new kernel.
1515 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1516 to -HEAD. Pools that have empty_bpobj in active state can not be
1517 imported read-write with ZFS implementations that do not support
1518 this feature. For more information read the zpool-features(5)
1522 The sparc64 ZFS loader has been changed to no longer try to auto-
1523 detect ZFS providers based on diskN aliases but now requires these
1524 to be explicitly listed in the OFW boot-device environment variable.
1527 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1528 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1529 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1532 The following sysctls and tunables have been renamed for consistency
1533 with other variables:
1534 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1535 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1538 The sort utility has been replaced with BSD sort. For now, GNU sort
1539 is also available as "gnusort" or the default can be set back to
1540 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1541 installed as "bsdsort".
1544 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1545 Starting with this version the old system of ZFS pool versioning
1546 is superseded by "feature flags". This concept enables forward
1547 compatibility against certain future changes in functionality of ZFS
1548 pools. The first read-only compatible "feature flag" for ZFS pools
1549 is named "com.delphix:async_destroy". For more information
1550 read the new zpool-features(5) manual page.
1551 Please refer to the "ZFS notes" section of this file for information
1552 on upgrading boot ZFS pools.
1555 The malloc(3) implementation embedded in libc now uses sources imported
1556 as contrib/jemalloc. The most disruptive API change is to
1557 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1558 delete it prior to installworld, and optionally re-create it using the
1559 new format after rebooting. See malloc.conf(5) for details
1560 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1564 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1565 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1566 now spelled mips. This is to aid compatibility with third-party
1567 software that expects this naming scheme in uname(3). Little-endian
1568 settings are unchanged. If you are updating a big-endian mips64 machine
1569 from before this change, you may need to set MACHINE_ARCH=mips64 in
1570 your environment before the new build system will recognize your machine.
1573 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1577 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1578 nullfs(5) did not pass through all behaviours to the underlying layer,
1579 as a result if we bound to a socket on the lower layer we could connect
1580 only to the lower path; if we bound to the upper layer we could connect
1581 only to the upper path. The new behavior is one can connect to both the
1582 lower and the upper paths regardless what layer path one binds to.
1585 The getifaddrs upgrade path broken with 20111215 has been restored.
1586 If you have upgraded in between 20111215 and 20120209 you need to
1587 recompile libc again with your kernel. You still need to recompile
1588 world to be able to configure CARP but this restriction already
1589 comes from 20111215.
1592 The set_rcvar() function has been removed from /etc/rc.subr. All
1593 base and ports rc.d scripts have been updated, so if you have a
1594 port installed with a script in /usr/local/etc/rc.d you can either
1595 hand-edit the rcvar= line, or reinstall the port.
1597 An easy way to handle the mass-update of /etc/rc.d:
1598 rm /etc/rc.d/* && mergemaster -i
1601 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1602 on the current CPU and prevents other threads from running.
1603 This behavior can be reverted using the kern.stop_scheduler_on_panic
1605 The new behavior can be incompatible with kern.sync_on_panic.
1608 The carp(4) facility has been changed significantly. Configuration
1609 of the CARP protocol via ifconfig(8) has changed, as well as format
1610 of CARP events submitted to devd(8) has changed. See manual pages
1611 for more information. The arpbalance feature of carp(4) is currently
1612 not supported anymore.
1614 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1615 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1616 need to be recompiled.
1619 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1623 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1624 explicitely support non-MPSAFE filesystems.
1625 It is on by default for all supported platform at this present
1629 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1630 i386 and pc98 GENERIC kernel configuration files.
1633 sysinstall has been removed
1636 The stable/9 branch created in subversion. This corresponds to the
1637 RELENG_9 branch in CVS.
1643 Avoid using make -j when upgrading. While generally safe, there are
1644 sometimes problems using -j to upgrade. If your upgrade fails with
1645 -j, please try again without -j. From time to time in the past there
1646 have been problems using -j with buildworld and/or installworld. This
1647 is especially true when upgrading between "distant" versions (eg one
1648 that cross a major release boundary or several minor releases, or when
1649 several months have passed on the -current branch).
1651 Sometimes, obscure build problems are the result of environment
1652 poisoning. This can happen because the make utility reads its
1653 environment when searching for values for global variables. To run
1654 your build attempts in an "environmental clean room", prefix all make
1655 commands with 'env -i '. See the env(1) manual page for more details.
1657 When upgrading from one major version to another it is generally best to
1658 upgrade to the latest code in the currently installed branch first, then
1659 do an upgrade to the new branch. This is the best-tested upgrade path,
1660 and has the highest probability of being successful. Please try this
1661 approach if you encounter problems with a major version upgrade. Since
1662 the stable 4.x branch point, one has generally been able to upgade from
1663 anywhere in the most recent stable branch to head / current (or even the
1664 last couple of stable branches). See the top of this file when there's
1667 When upgrading a live system, having a root shell around before
1668 installing anything can help undo problems. Not having a root shell
1669 around can lead to problems if pam has changed too much from your
1670 starting point to allow continued authentication after the upgrade.
1672 This file should be read as a log of events. When a later event changes
1673 information of a prior event, the prior event should not be deleted.
1674 Instead, a pointer to the entry with the new information should be
1675 placed in the old entry. Readers of this file should also sanity check
1676 older entries before relying on them blindly. Authors of new entries
1677 should write them with this in mind.
1681 When upgrading the boot ZFS pool to a new version, always follow
1684 1.) recompile and reinstall the ZFS boot loader and boot block
1685 (this is part of "make buildworld" and "make installworld")
1687 2.) update the ZFS boot block on your boot drive
1689 The following example updates the ZFS boot block on the first
1690 partition (freebsd-boot) of a GPT partitioned drive ada0:
1691 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1693 Non-boot pools do not need these updates.
1697 If you are updating from a prior version of FreeBSD (even one just
1698 a few days old), you should follow this procedure. It is the most
1699 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1701 make kernel-toolchain
1702 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1703 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1705 To test a kernel once
1706 ---------------------
1707 If you just want to boot a kernel once (because you are not sure
1708 if it works, or if you want to boot a known bad kernel to provide
1709 debugging information) run
1710 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1711 nextboot -k testkernel
1713 To just build a kernel when you know that it won't mess you up
1714 --------------------------------------------------------------
1715 This assumes you are already running a CURRENT system. Replace
1716 ${arch} with the architecture of your machine (e.g. "i386",
1717 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1719 cd src/sys/${arch}/conf
1720 config KERNEL_NAME_HERE
1721 cd ../compile/KERNEL_NAME_HERE
1726 If this fails, go to the "To build a kernel" section.
1728 To rebuild everything and install it on the current system.
1729 -----------------------------------------------------------
1730 # Note: sometimes if you are running current you gotta do more than
1731 # is listed here if you are upgrading from a really old current.
1733 <make sure you have good level 0 dumps>
1735 make kernel KERNCONF=YOUR_KERNEL_HERE
1737 <reboot in single user> [3]
1744 To cross-install current onto a separate partition
1745 --------------------------------------------------
1746 # In this approach we use a separate partition to hold
1747 # current's root, 'usr', and 'var' directories. A partition
1748 # holding "/", "/usr" and "/var" should be about 2GB in
1751 <make sure you have good level 0 dumps>
1754 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1755 <maybe newfs current's root partition>
1756 <mount current's root partition on directory ${CURRENT_ROOT}>
1757 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1758 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1759 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1760 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1761 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1762 <reboot into current>
1763 <do a "native" rebuild/install as described in the previous section>
1764 <maybe install compatibility libraries from ports/misc/compat*>
1768 To upgrade in-place from stable to current
1769 ----------------------------------------------
1770 <make sure you have good level 0 dumps>
1772 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1774 <reboot in single user> [3]
1781 Make sure that you've read the UPDATING file to understand the
1782 tweaks to various things you need. At this point in the life
1783 cycle of current, things change often and you are on your own
1784 to cope. The defaults can also change, so please read ALL of
1785 the UPDATING entries.
1787 Also, if you are tracking -current, you must be subscribed to
1788 freebsd-current@freebsd.org. Make sure that before you update
1789 your sources that you have read and understood all the recent
1790 messages there. If in doubt, please track -stable which has
1791 much fewer pitfalls.
1793 [1] If you have third party modules, such as vmware, you
1794 should disable them at this point so they don't crash your
1797 [3] From the bootblocks, boot -s, and then do
1802 adjkerntz -i # if CMOS is wall time
1803 Also, when doing a major release upgrade, it is required that
1804 you boot into single user mode to do the installworld.
1806 [4] Note: This step is non-optional. Failure to do this step
1807 can result in a significant reduction in the functionality of the
1808 system. Attempting to do it by hand is not recommended and those
1809 that pursue this avenue should read this file carefully, as well
1810 as the archives of freebsd-current and freebsd-hackers mailing lists
1811 for potential gotchas. The -U option is also useful to consider.
1812 See mergemaster(8) for more information.
1814 [5] Usually this step is a noop. However, from time to time
1815 you may need to do this if you get unknown user in the following
1816 step. It never hurts to do it all the time. You may need to
1817 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1818 install) after the buildworld before this step if you last updated
1819 from current before 20130425 or from -stable before 20130430.
1821 [6] This only deletes old files and directories. Old libraries
1822 can be deleted by "make delete-old-libs", but you have to make
1823 sure that no program is using those libraries anymore.
1825 [8] In order to have a kernel that can run the 4.x binaries needed to
1826 do an installworld, you must include the COMPAT_FREEBSD4 option in
1827 your kernel. Failure to do so may leave you with a system that is
1828 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1829 required to run the 5.x binaries on more recent kernels. And so on
1830 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1832 Make sure that you merge any new devices from GENERIC since the
1833 last time you updated your kernel config file.
1835 [9] When checking out sources, you must include the -P flag to have
1836 cvs prune empty directories.
1838 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1839 "?=" instead of the "=" assignment operator, so that buildworld can
1840 override the CPUTYPE if it needs to.
1842 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1843 not on the command line, or in /etc/make.conf. buildworld will
1844 warn if it is improperly defined.
1847 This file contains a list, in reverse chronological order, of major
1848 breakages in tracking -current. It is not guaranteed to be a complete
1849 list of such breakages, and only contains entries since September 23, 2011.
1850 If you need to see UPDATING entries from before that date, you will need
1851 to fetch an UPDATING file from an older FreeBSD release.
1853 Copyright information:
1855 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1857 Redistribution, publication, translation and use, with or without
1858 modification, in full or in part, in any form or format of this
1859 document are permitted without further permission from the author.
1861 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1862 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1863 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1864 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1865 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1866 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1867 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1868 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1869 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1870 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1871 POSSIBILITY OF SUCH DAMAGE.
1873 Contact Warner Losh if you have any questions about your use of