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 "ino64" 64-bit inode project has been committed, which extends
81 a number of types to 64 bits. Upgrading in place requires care and
82 adherence to the documented upgrade procedure.
84 If using a custom kernel configuration ensure that the
85 COMPAT_FREEBSD11 option is included (as during the upgrade the
86 system will be running the ino64 kernel with the existing world).
88 For the safest in-place upgrade begin by removing previous build
89 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
90 full procedure documented below under the heading "To rebuild
91 everything and install it on the current system." Specifically,
92 a reboot is required after installing the new kernel before
96 The NATM framework including the en(4), fatm(4), hatm(4), and
97 patm(4) devices has been removed. Consumers should plan a
98 migration before the end-of-life date for FreeBSD 11.
101 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
102 diff has not been implemented, if those are needed a newer version of
103 GNU diff is available via the diffutils package under the gdiff name.
106 As of r316810 for ipfilter, keep frags is no longer assumed when
107 keep state is specified in a rule. r316810 aligns ipfilter with
108 documentation in man pages separating keep frags from keep state.
109 This allows keep state to be specified without forcing keep frags
110 and allows keep frags to be specified independently of keep state.
111 To maintain previous behaviour, also specify keep frags with
112 keep state (as documented in ipf.conf.5).
115 arm64 builds now use the base system LLD 4.0.0 linker by default,
116 instead of requiring that the aarch64-binutils port or package be
117 installed. To continue using aarch64-binutils, set
118 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
121 The UDP optimization in entry 20160818 that added the sysctl
122 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
123 packets will no longer be treated as L3 broadcast packets.
126 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
127 use any explicitly assigned loopback address available in the jail
128 instead of using the first assigned address of the jail.
131 The ctl.ko module no longer implements the iSCSI target frontend:
132 cfiscsi.ko does instead.
134 If building cfiscsi.ko as a kernel module, the module can be loaded
135 via one of the following methods:
136 - `cfiscsi_load="YES"` in loader.conf(5).
137 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
138 - ctladm(8)/ctld(8), when compiled with iSCSI support
139 (`WITH_ISCSI=yes` in src.conf(5))
141 Please see cfiscsi(4) for more details.
144 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
145 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
146 same source (previously, the dependency of mmcsd.ko on mmc.ko was
147 missing, but mmcsd.ko now will refuse to load if it is incompatible
151 The syntax of ipfw(8) named states was changed to avoid ambiguity.
152 If you have used named states in the firewall rules, you need to modify
153 them after installworld and before rebooting. Now named states must
154 be prefixed with colon.
157 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
158 removed as the userland we provide cannot use them. The KMS version
159 (sys/dev/drm2) supports the same hardware.
162 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
163 Please see the 20141231 entry below for information about prerequisites
164 and upgrading, if you are not already using clang 3.5.0 or higher.
167 The code that provides support for ZFS .zfs/ directory functionality
168 has been reimplemented. It's not possible now to create a snapshot
169 by mkdir under .zfs/snapshot/. That should be the only user visible
173 EISA bus support has been removed. The WITH_EISA option is no longer
177 MCA bus support has been removed.
180 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
181 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
184 The EM_MULTIQUEUE kernel configuration option is deprecated now that
185 the em(4) driver conforms to iflib specifications.
188 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
189 IFLIB. If you have a custom kernel configuration that excludes em(4)
190 but you use igb(4), you need to re-add em(4) to your custom configuration.
193 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
194 Please see the 20141231 entry below for information about prerequisites
195 and upgrading, if you are not already using clang 3.5.0 or higher.
198 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
199 Please see the 20141231 entry below for information about prerequisites
200 and upgrading, if you are not already using clang 3.5.0 or higher.
203 The layout of the pmap structure has changed for powerpc to put the pmap
204 statistics at the front for all CPU variations. libkvm(3) and all tools
205 that link against it need to be recompiled.
208 isl(4) and cyapa(4) drivers now require a new driver,
209 chromebook_platform(4), to work properly on Chromebook-class hardware.
210 On other types of hardware the drivers may need to be configured using
211 device hints. Please see the corresponding manual pages for details.
214 The urtwn(4) driver was merged into rtwn(4) and now consists of
215 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
217 Also, firmware for RTL8188CE was renamed due to possible name
218 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
221 GNU rcs has been removed from base. It is available as packages:
222 - rcs: Latest GPLv3 GNU rcs version.
223 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
227 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
228 modules now requires that the kernel configuration contain the
229 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
232 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
233 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
236 Relocatable object files with the extension of .So have been renamed
237 to use an extension of .pico instead. The purpose of this change is
238 to avoid a name clash with shared libraries on case-insensitive file
239 systems. On those file systems, foo.So is the same file as foo.so.
242 GNU rcs has been turned off by default. It can (temporarily) be built
243 again by adding WITH_RCS knob in src.conf.
244 Otherwise, GNU rcs is available from packages:
245 - rcs: Latest GPLv3 GNU rcs version.
246 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
249 The backup_uses_rcs functionality has been removed from rc.subr.
252 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
253 two separate components, QUEUE_MACRO_DEBUG_TRACE and
254 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
255 QUEUE_MACRO_DEBUG behavior.
258 r304787 changed some ioctl interfaces between the iSCSI userspace
259 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
260 rebuilt to work with new kernels. __FreeBSD_version has been bumped
264 The UDP receive code has been updated to only treat incoming UDP
265 packets that were addressed to an L2 broadcast address as L3
266 broadcast packets. It is not expected that this will affect any
267 standards-conforming UDP application. The new behaviour can be
268 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
272 Remove the openbsd_poll system call.
273 __FreeBSD_version has been bumped because of this.
276 The libc stub for the pipe(2) system call has been replaced with
277 a wrapper that calls the pipe2(2) system call and the pipe(2)
278 system call is now only implemented by the kernels that include
279 "options COMPAT_FREEBSD10" in their config file (this is the
280 default). Users should ensure that this option is enabled in
281 their kernel or upgrade userspace to r302092 before upgrading their
285 CAM will now strip leading spaces from SCSI disks' serial numbers.
286 This will affect users who create UFS filesystems on SCSI disks using
287 those disk's diskid device nodes. For example, if /etc/fstab
288 previously contained a line like
289 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
290 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
291 transforms like gmirror may also be affected. ZFS users should
295 The bitstring(3) API has been updated with new functionality and
296 improved performance. But it is binary-incompatible with the old API.
297 Objects built with the new headers may not be linked against objects
298 built with the old headers.
301 The brk and sbrk functions have been removed from libc on arm64.
302 Binutils from ports has been updated to not link to these
303 functions and should be updated to the latest version before
304 installing a new libc.
307 The armv6 port now defaults to hard float ABI. Limited support
308 for running both hardfloat and soft float on the same system
309 is available using the libraries installed with -DWITH_LIBSOFT.
310 This has only been tested as an upgrade path for installworld
311 and packages may fail or need manual intervention to run. New
312 packages will be needed.
314 To update an existing self-hosted armv6hf system, you must add
315 TARGET_ARCH=armv6 on the make command line for both the build
316 and the install steps.
319 Kernel modules compiled outside of a kernel build now default to
320 installing to /boot/modules instead of /boot/kernel. Many kernel
321 modules built this way (such as those in ports) already overrode
322 KMODDIR explicitly to install into /boot/modules. However,
323 manually building and installing a module from /sys/modules will
324 now install to /boot/modules instead of /boot/kernel.
327 The CAM I/O scheduler has been committed to the kernel. There should be
328 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
329 list of known rogues that claim support for this but actually corrupt
330 data is believed to be complete, be on the lookout for data
331 corruption. The known rogue list is believed to be complete:
333 o Crucial MX100, M550 drives with MU01 firmware.
334 o Micron M510 and M550 drives with MU01 firmware.
335 o Micron M500 prior to MU07 firmware
336 o Samsung 830, 840, and 850 all firmwares
337 o FCCT M500 all firmwares
339 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
340 with working NCQ TRIM. For Micron branded drives, see your sales rep for
341 updated firmware. Black listed drives will work correctly because these
342 drives work correctly so long as no NCQ TRIMs are sent to them. Given
343 this list is the same as found in Linux, it's believed there are no
344 other rogues in the market place. All other models from the above
347 To be safe, if you are at all concerned, you can quirk each of your
348 drives to prevent NCQ from being sent by setting:
349 kern.cam.ada.X.quirks="0x2"
350 in loader.conf. If the drive requires the 4k sector quirk, set the
354 The FAST_DEPEND build option has been removed and its functionality is
355 now the one true way. The old mkdep(1) style of 'make depend' has
356 been removed. See 20160311 for further details.
359 Resource range types have grown from unsigned long to uintmax_t. All
360 drivers, and anything using libdevinfo, need to be recompiled.
363 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
364 builds. It no longer runs mkdep(1) during 'make depend', and the
365 'make depend' stage can safely be skipped now as it is auto ran
366 when building 'make all' and will generate all SRCS and DPSRCS before
367 building anything else. Dependencies are gathered at compile time with
368 -MF flags kept in separate .depend files per object file. Users should
369 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
373 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
374 kernel modules. Therefore, if you load any kernel modules at boot time,
375 please install the boot loaders after you install the kernel, but before
379 make kernel KERNCONF=YOUR_KERNEL_HERE
380 make -C sys/boot install
381 <reboot in single user>
383 Then follow the usual steps, described in the General Notes section,
387 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
388 see the 20141231 entry below for information about prerequisites and
389 upgrading, if you are not already using clang 3.5.0 or higher.
392 The AIO subsystem is now a standard part of the kernel. The
393 VFS_AIO kernel option and aio.ko kernel module have been removed.
394 Due to stability concerns, asynchronous I/O requests are only
395 permitted on sockets and raw disks by default. To enable
396 asynchronous I/O requests on all file types, set the
397 vfs.aio.enable_unsafe sysctl to a non-zero value.
400 The ELF object manipulation tool objcopy is now provided by the
401 ELF Tool Chain project rather than by GNU binutils. It should be a
402 drop-in replacement, with the addition of arm64 support. The
403 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
404 to obtain the GNU version if necessary.
407 Building ZFS pools on top of zvols is prohibited by default. That
408 feature has never worked safely; it's always been prone to deadlocks.
409 Using a zvol as the backing store for a VM guest's virtual disk will
410 still work, even if the guest is using ZFS. Legacy behavior can be
411 restored by setting vfs.zfs.vol.recursive=1.
414 The NONE and HPN patches has been removed from OpenSSH. They are
415 still available in the security/openssh-portable port.
418 With the addition of ypldap(8), a new _ypldap user is now required
419 during installworld. "mergemaster -p" can be used to add the user
420 prior to installworld, as documented in the handbook.
423 The tftp loader (pxeboot) now uses the option root-path directive. As a
424 consequence it no longer looks for a pxeboot.4th file on the tftp
425 server. Instead it uses the regular /boot infrastructure as with the
429 The code to start recording plug and play data into the modules has
430 been committed. While the old tools will properly build a new kernel,
431 a number of warnings about "unknown metadata record 4" will be produced
432 for an older kldxref. To avoid such warnings, make sure to rebuild
433 the kernel toolchain (or world). Make sure that you have r292078 or
434 later when trying to build 292077 or later before rebuilding.
437 Debug data files are now built by default with 'make buildworld' and
438 installed with 'make installworld'. This facilitates debugging but
439 requires more disk space both during the build and for the installed
440 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
444 r291527 changed the internal interface between the nfsd.ko and
445 nfscommon.ko modules. As such, they must both be upgraded to-gether.
446 __FreeBSD_version has been bumped because of this.
449 Add support for unicode collation strings leads to a change of
450 order of files listed by ls(1) for example. To get back to the old
451 behaviour, set LC_COLLATE environment variable to "C".
453 Databases administrators will need to reindex their databases given
454 collation results will be different.
456 Due to a bug in install(1) it is recommended to remove the ancient
457 locales before running make installworld.
459 rm -rf /usr/share/locale/*
462 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
463 libcrypto.so.7 or libssl.so.7 must be recompiled.
466 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
467 Kernel modules isp_2400_multi and isp_2500_multi were removed and
468 should be replaced with isp_2400 and isp_2500 modules respectively.
471 The build previously allowed using 'make -n' to not recurse into
472 sub-directories while showing what commands would be executed, and
473 'make -n -n' to recursively show commands. Now 'make -n' will recurse
474 and 'make -N' will not.
477 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
478 and etcupdate will now use this file. A custom sendmail.cf is now
479 updated via this mechanism rather than via installworld. If you had
480 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
481 want to remove the exclusion or change it to "always install".
482 /etc/mail/sendmail.cf is now managed the same way regardless of
483 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
484 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
487 Compatibility shims for legacy ATA device names have been removed.
488 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
489 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
490 environment variables, /dev/ad* and /dev/ar* symbolic links.
493 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
494 Please see the 20141231 entry below for information about prerequisites
495 and upgrading, if you are not already using clang 3.5.0 or higher.
498 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
499 and renamed from .symbols to .debug. This reduces the size requirements
500 on the boot partition or file system and provides consistency with
501 userland debug files.
503 When using the supported kernel installation method the
504 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
505 as is done with /boot/kernel.
507 Developers wishing to maintain the historical behavior of installing
508 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
511 The wireless drivers had undergone changes that remove the 'parent
512 interface' from the ifconfig -l output. The rc.d network scripts
513 used to check presence of a parent interface in the list, so old
514 scripts would fail to start wireless networking. Thus, etcupdate(3)
515 or mergemaster(8) run is required after kernel update, to update your
516 rc.d scripts in /etc.
519 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
520 These configurations are now automatically interpreted as
521 'scrub fragment reassemble'.
524 Kernel-loadable modules for the random(4) device are back. To use
525 them, the kernel must have
528 options RANDOM_LOADABLE
530 kldload(8) can then be used to load random_fortuna.ko
531 or random_yarrow.ko. Please note that due to the indirect
532 function calls that the loadable modules need to provide,
533 the build-in variants will be slightly more efficient.
535 The random(4) kernel option RANDOM_DUMMY has been retired due to
536 unpopularity. It was not all that useful anyway.
539 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
540 Control over building the ELF Tool Chain tools is now provided by
541 the WITHOUT_TOOLCHAIN knob.
544 The polarity of Pulse Per Second (PPS) capture events with the
545 uart(4) driver has been corrected. Prior to this change the PPS
546 "assert" event corresponded to the trailing edge of a positive PPS
547 pulse and the "clear" event was the leading edge of the next pulse.
549 As the width of a PPS pulse in a typical GPS receiver is on the
550 order of 1 millisecond, most users will not notice any significant
551 difference with this change.
553 Anyone who has compensated for the historical polarity reversal by
554 configuring a negative offset equal to the pulse width will need to
555 remove that workaround.
558 The default group assigned to /dev/dri entries has been changed
559 from 'wheel' to 'video' with the id of '44'. If you want to have
560 access to the dri devices please add yourself to the video group
563 # pw groupmod video -m $USER
566 The menu.rc and loader.rc files will now be replaced during
567 upgrades. Please migrate local changes to menu.rc.local and
568 loader.rc.local instead.
571 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
572 strings and strip have been removed. The src.conf(5) knob
573 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
576 As ZFS requires more kernel stack pages than is the default on some
577 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
578 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
580 Please consider using 'options KSTACK_PAGES=X' where X is greater
581 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
584 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
585 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
586 default, i.e., they will not contain "::". For example, instead
587 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
588 to have a more specific match, such as different map entries for
589 IPv6:0:0 vs IPv6:0. This change requires that configuration
590 data (including maps, files, classes, custom ruleset, etc.) must
591 use the same format, so make certain such configuration data is
592 upgrading. As a very simple check search for patterns like
593 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
594 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
595 the cf option UseCompressedIPv6Addresses.
598 The default kernel entropy-processing algorithm is now
599 Fortuna, replacing Yarrow.
601 Assuming you have 'device random' in your kernel config
602 file, the configurations allow a kernel option to override
603 this default. You may choose *ONE* of:
605 options RANDOM_YARROW # Legacy /dev/random algorithm.
606 options RANDOM_DUMMY # Blocking-only driver.
608 If you have neither, you get Fortuna. For most people,
609 read no further, Fortuna will give a /dev/random that works
610 like it always used to, and the difference will be irrelevant.
612 If you remove 'device random', you get *NO* kernel-processed
613 entropy at all. This may be acceptable to folks building
614 embedded systems, but has complications. Carry on reading,
615 and it is assumed you know what you need.
617 *PLEASE* read random(4) and random(9) if you are in the
618 habit of tweaking kernel configs, and/or if you are a member
619 of the embedded community, wanting specific and not-usual
620 behaviour from your security subsystems.
622 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
623 random', you will NOT have a functioning /dev/random, and
624 many cryptographic features will not work, including SSH.
625 You may also find strange behaviour from the random(3) set
626 of library functions, in particular sranddev(3), srandomdev(3)
627 and arc4random(3). The reason for this is that the KERN_ARND
628 sysctl only returns entropy if it thinks it has some to
629 share, and with RANDOM_DUMMY or no 'device random' this
633 An additional fix for the issue described in the 20150614 sendmail
634 entry below has been been committed in revision 284717.
637 FreeBSD's old make (fmake) has been removed from the system. It is
638 available as the devel/fmake port or via pkg install fmake.
641 The fix for the issue described in the 20150614 sendmail entry
642 below has been been committed in revision 284436. The work
643 around described in that entry is no longer needed unless the
644 default setting is overridden by a confDH_PARAMETERS configuration
645 setting of '5' or pointing to a 512 bit DH parameter file.
648 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
649 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
650 and devel/kyua to version 0.20+ and adjust any calling code to work
651 with Kyuafile and kyua.
654 The import of openssl to address the FreeBSD-SA-15:10.openssl
655 security advisory includes a change which rejects handshakes
656 with DH parameters below 768 bits. sendmail releases prior
657 to 8.15.2 (not yet released), defaulted to a 512 bit
658 DH parameter setting for client connections. To work around
659 this interoperability, sendmail can be configured to use a
660 2048 bit DH parameter by:
662 1. Edit /etc/mail/`hostname`.mc
663 2. If a setting for confDH_PARAMETERS does not exist or
664 exists and is set to a string beginning with '5',
666 3. If a setting for confDH_PARAMETERS exists and is set to
667 a file path, create a new file with:
668 openssl dhparam -out /path/to/file 2048
669 4. Rebuild the .cf file:
670 cd /etc/mail/; make; make install
672 cd /etc/mail/; make restart
674 A sendmail patch is coming, at which time this file will be
678 Generation of legacy formatted entries have been disabled by default
679 in pwd_mkdb(8), as all base system consumers of the legacy formatted
680 entries were converted to use the new format by default when the new,
681 machine independent format have been added and supported since FreeBSD
684 Please see the pwd_mkdb(8) manual page for further details.
687 Clang and llvm have been upgraded to 3.6.1 release. Please see the
688 20141231 entry below for information about prerequisites and upgrading,
689 if you are not already using 3.5.0 or higher.
692 TI platform code switched to using vendor DTS files and this update
693 may break existing systems running on Beaglebone, Beaglebone Black,
696 - dtb files should be regenerated/reinstalled. Filenames are the
697 same but content is different now
698 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
699 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
700 addressing scheme is now pin 25 on /dev/gpioc3.
701 - Pandaboard: /etc/ttys should be updated, serial console device is
702 now /dev/ttyu2, not /dev/ttyu0
705 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
706 If you need the GNU extension from groff soelim(1), install groff
707 from package: pkg install groff, or via ports: textproc/groff.
710 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
711 defined in symlink(7); previously symlinks were silently ignored.
714 The const qualifier has been removed from iconv(3) to comply with
715 POSIX. The ports tree is aware of this from r384038 onwards.
718 Libraries specified by LIBADD in Makefiles must have a corresponding
719 DPADD_<lib> variable to ensure correct dependencies. This is now
720 enforced in src.libnames.mk.
723 From legacy ata(4) driver was removed support for SATA controllers
724 supported by more functional drivers ahci(4), siis(4) and mvs(4).
725 Kernel modules ataahci and ataadaptec were removed completely,
726 replaced by ahci and mvs modules respectively.
729 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
730 the 20141231 entry below for information about prerequisites and
731 upgrading, if you are not already using 3.5.0 or higher.
734 The 32-bit PowerPC kernel has been changed to a position-independent
735 executable. This can only be booted with a version of loader(8)
736 newer than January 31, 2015, so make sure to update both world and
737 kernel before rebooting.
740 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
741 but before r278950, the RNG was not seeded properly. Immediately
742 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
743 ssh keys or openssl keys) that were generated w/ a kernel from that
744 range. This does not affect programs that directly used /dev/random
745 or /dev/urandom. All userland uses of arc4random(3) are affected.
748 The autofs(4) ABI was changed in order to restore binary compatibility
749 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
753 The powerpc64 kernel has been changed to a position-independent
754 executable. This can only be booted with a new version of loader(8),
755 so make sure to update both world and kernel before rebooting.
758 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
759 only release, no new features have been added. Please see the 20141231
760 entry below for information about prerequisites and upgrading, if you
761 are not already using 3.5.0.
764 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
765 taken from the ELF Tool Chain project rather than GNU binutils. They
766 should be drop-in replacements, with the addition of arm64 support.
767 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
768 binutils tools, if necessary. See 20150805 for updated information.
771 The default Unbound configuration now enables remote control
772 using a local socket. Users who have already enabled the
773 local_unbound service should regenerate their configuration
774 by running "service local_unbound setup" as root.
777 The GNU texinfo and GNU info pages have been removed.
778 To be able to view GNU info pages please install texinfo from ports.
781 Clang, llvm and lldb have been upgraded to 3.5.0 release.
783 As of this release, a prerequisite for building clang, llvm and lldb is
784 a C++11 capable compiler and C++11 standard library. This means that to
785 be able to successfully build the cross-tools stage of buildworld, with
786 clang as the bootstrap compiler, your system compiler or cross compiler
787 should either be clang 3.3 or later, or gcc 4.8 or later, and your
788 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
791 On any standard FreeBSD 10.x or 11.x installation, where clang and
792 libc++ are on by default (that is, on x86 or arm), this should work out
795 On 9.x installations where clang is enabled by default, e.g. on x86 and
796 powerpc, libc++ will not be enabled by default, so libc++ should be
797 built (with clang) and installed first. If both clang and libc++ are
798 missing, build clang first, then use it to build libc++.
800 On 8.x and earlier installations, upgrade to 9.x first, and then follow
801 the instructions for 9.x above.
803 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
804 default, and do not build clang.
806 Many embedded systems are resource constrained, and will not be able to
807 build clang in a reasonable time, or in some cases at all. In those
808 cases, cross building bootable systems on amd64 is a workaround.
810 This new version of clang introduces a number of new warnings, of which
811 the following are most likely to appear:
815 This warns in two cases, for both C and C++:
816 * When the code is trying to take the absolute value of an unsigned
817 quantity, which is effectively a no-op, and almost never what was
818 intended. The code should be fixed, if at all possible. If you are
819 sure that the unsigned quantity can be safely cast to signed, without
820 loss of information or undefined behavior, you can add an explicit
821 cast, or disable the warning.
823 * When the code is trying to take an absolute value, but the called
824 abs() variant is for the wrong type, which can lead to truncation.
825 If you want to disable the warning instead of fixing the code, please
826 make sure that truncation will not occur, or it might lead to unwanted
829 -Wtautological-undefined-compare and
830 -Wundefined-bool-conversion
832 These warn when C++ code is trying to compare 'this' against NULL, while
833 'this' should never be NULL in well-defined C++ code. However, there is
834 some legacy (pre C++11) code out there, which actively abuses this
835 feature, which was less strictly defined in previous C++ versions.
837 Squid and openjdk do this, for example. The warning can be turned off
838 for C++98 and earlier, but compiling the code in C++11 mode might result
839 in unexpected behavior; for example, the parts of the program that are
840 unreachable could be optimized away.
843 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
844 kernel sources have been removed. The .h files remain, since some
845 utilities include them. This will need to be fixed later.
846 If "mount -t oldnfs ..." is attempted, it will fail.
847 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
848 the utilities will report errors.
851 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
852 directories to top level SUBDIR variable when their parent
853 directory is included in LOCAL_DIRS. Users with build systems with
854 such hierarchies and without SUBDIR entries in the parent
855 directory Makefiles should add them or add the directories to
859 faith(4) and faithd(8) have been removed from the base system. Faith
860 has been obsolete for a very long time.
863 vt(4), the new console driver, is enabled by default. It brings
864 support for Unicode and double-width characters, as well as
865 support for UEFI and integration with the KMS kernel video
868 You may need to update your console settings in /etc/rc.conf,
869 most probably the keymap. During boot, /etc/rc.d/syscons will
870 indicate what you need to do.
872 vt(4) still has issues and lacks some features compared to
873 syscons(4). See the wiki for up-to-date information:
874 https://wiki.freebsd.org/Newcons
876 If you want to keep using syscons(4), you can do so by adding
877 the following line to /boot/loader.conf:
881 pjdfstest has been integrated into kyua as an opt-in test suite.
882 Please see share/doc/pjdfstest/README for more details on how to
886 gperf has been removed from the base system for architectures
887 that use clang. Ports that require gperf will obtain it from the
891 pjdfstest has been moved from tools/regression/pjdfstest to
895 At svn r271982, The default linux compat kernel ABI has been adjusted
896 to 2.6.18 in support of the linux-c6 compat ports infrastructure
897 update. If you wish to continue using the linux-f10 compat ports,
898 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
899 encouraged to update their linux-compat packages to linux-c6 during
900 their next update cycle.
903 The ofwfb driver, used to provide a graphics console on PowerPC when
904 using vt(4), no longer allows mmap() of all physical memory. This
905 will prevent Xorg on PowerPC with some ATI graphics cards from
906 initializing properly unless x11-servers/xorg-server is updated to
910 The xdev targets have been converted to using TARGET and
911 TARGET_ARCH instead of XDEV and XDEV_ARCH.
914 The default unbound configuration has been modified to address
915 issues with reverse lookups on networks that use private
916 address ranges. If you use the local_unbound service, run
917 "service local_unbound setup" as root to regenerate your
918 configuration, then "service local_unbound reload" to load the
922 The GNU texinfo and GNU info pages are not built and installed
923 anymore, WITH_INFO knob has been added to allow to built and install
925 UPDATE: see 20150102 entry on texinfo's removal
928 The GNU readline library is now an INTERNALLIB - that is, it is
929 statically linked into consumers (GDB and variants) in the base
930 system, and the shared library is no longer installed. The
931 devel/readline port is available for third party software that
935 The Itanium architecture (ia64) has been removed from the list of
936 known architectures. This is the first step in the removal of the
940 Commit r268115 has added NFSv4.1 server support, merged from
941 projects/nfsv4.1-server. Since this includes changes to the
942 internal interfaces between the NFS related modules, a full
943 build of the kernel and modules will be necessary.
944 __FreeBSD_version has been bumped.
947 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
948 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
949 which differs from the behaviour controlled by this knob.)
952 Maximal length of the serial number in CTL was increased from 16 to
953 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
954 and ctld, need to be rebuilt to work with a new kernel.
957 The libatf-c and libatf-c++ major versions were downgraded to 0 and
958 1 respectively to match the upstream numbers. They were out of
959 sync because, when they were originally added to FreeBSD, the
960 upstream versions were not respected. These libraries are private
961 and not yet built by default, so renumbering them should be a
962 non-issue. However, unclean source trees will yield broken test
963 programs once the operator executes "make delete-old-libs" after a
966 Additionally, the atf-sh binary was made private by moving it into
967 /usr/libexec/. Already-built shell test programs will keep the
968 path to the old binary so they will break after "make delete-old"
971 If you are using WITH_TESTS=yes (not the default), wipe the object
972 tree and rebuild from scratch to prevent spurious test failures.
973 This is only needed once: the misnumbered libraries and misplaced
974 binaries have been added to OptionalObsoleteFiles.inc so they will
975 be removed during a clean upgrade.
978 Clang and llvm have been upgraded to 3.4.1 release.
981 We bogusly installed src.opts.mk in /usr/share/mk. This file should
982 be removed to avoid issues in the future (and has been added to
986 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
987 past, it affected all builds that used the bsd.*.mk files. The old
988 behavior was a bug, but people may have relied upon it. To get this
989 behavior back, you can .include /etc/src.conf from /etc/make.conf
990 (which is still global and isn't changed). This also changes the
991 behavior of incremental builds inside the tree of individual
992 directories. Set MAKESYSPATH to ".../share/mk" to do that.
993 Although this has survived make universe and some upgrade scenarios,
994 other upgrade scenarios may have broken. At least one form of
995 temporary breakage was fixed with MAKESYSPATH settings for buildworld
996 as well... In cases where MAKESYSPATH isn't working with this
997 setting, you'll need to set it to the full path to your tree.
999 One side effect of all this cleaning up is that bsd.compiler.mk
1000 is no longer implicitly included by bsd.own.mk. If you wish to
1001 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1005 The lindev device has been removed since /dev/full has been made a
1006 standard device. __FreeBSD_version has been bumped.
1009 The knob WITHOUT_VI was added to the base system, which controls
1010 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1011 in order to reorder files share/termcap and didn't build ex(1) as a
1012 build tool, so building/installing with WITH_VI is highly advised for
1013 build hosts for older releases.
1015 This issue has been fixed in stable/9 and stable/10 in r277022 and
1016 r276991, respectively.
1019 The YES_HESIOD knob has been removed. It has been obsolete for
1020 a decade. Please move to using WITH_HESIOD instead or your builds
1021 will silently lack HESIOD.
1024 The uart(4) driver has been changed with respect to its handling
1025 of the low-level console. Previously the uart(4) driver prevented
1026 any process from changing the baudrate or the CLOCAL and HUPCL
1027 control flags. By removing the restrictions, operators can make
1028 changes to the serial console port without having to reboot.
1029 However, when getty(8) is started on the serial device that is
1030 associated with the low-level console, a misconfigured terminal
1031 line in /etc/ttys will now have a real impact.
1032 Before upgrading the kernel, make sure that /etc/ttys has the
1033 serial console device configured as 3wire without baudrate to
1034 preserve the previous behaviour. E.g:
1035 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1038 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1039 to improve performance. To re-enable it, if needed, run rpcbind
1040 with command line option -W.
1043 Switched back to the GPL dtc compiler due to updates in the upstream
1044 dts files not being supported by the BSDL dtc compiler. You will need
1045 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1046 may result while building dtb files during a kernel build if you fail
1047 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1050 Clang and llvm have been upgraded to 3.4 release.
1053 The nve(4) driver has been removed. Please use the nfe(4) driver
1054 for NVIDIA nForce MCP Ethernet adapters instead.
1057 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1058 This could cause certain C++ applications using shared libraries built
1059 against the previous version of libc++ to crash. The incompatibility
1060 has now been fixed, but any C++ applications or shared libraries built
1061 between r261283 and r261801 should be recompiled.
1064 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1065 capability mode support. Please note that enabling the feature in
1066 kernel is still highly recommended.
1069 OpenSSH is now built with sandbox support, and will use sandbox as
1070 the default privilege separation method. This requires Capsicum
1071 capability mode support in kernel.
1074 The libelf and libdwarf libraries have been updated to newer
1075 versions from upstream. Shared library version numbers for
1076 these two libraries were bumped. Any ports or binaries
1077 requiring these two libraries should be recompiled.
1078 __FreeBSD_version is bumped to 1100006.
1081 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1082 instead of providing an explicit one, this would prevent such
1083 Makefile from providing its own Kyuafile in the future during
1084 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1085 intervention is needed to clean an objdir if you use NO_CLEAN:
1086 # find /usr/obj -name Kyuafile | xargs rm -f
1089 The behavior of gss_pseudo_random() for the krb5 mechanism
1090 has changed, for applications requesting a longer random string
1091 than produced by the underlying enctype's pseudo-random() function.
1092 In particular, the random string produced from a session key of
1093 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1094 be different at the 17th octet and later, after this change.
1095 The counter used in the PRF+ construction is now encoded as a
1096 big-endian integer in accordance with RFC 4402.
1097 __FreeBSD_version is bumped to 1100004.
1100 The WITHOUT_ATF build knob has been removed and its functionality
1101 has been subsumed into the more generic WITHOUT_TESTS. If you were
1102 using the former to disable the build of the ATF libraries, you
1103 should change your settings to use the latter.
1106 The default version of mtree is nmtree which is obtained from
1107 NetBSD. The output is generally the same, but may vary
1108 slightly. If you found you need identical output adding
1109 "-F freebsd9" to the command line should do the trick. For the
1110 time being, the old mtree is available as fmtree.
1113 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1114 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1115 1.1.4_8 and verify bsdyml not linked in, before running "make
1117 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1119 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1122 The stable/10 branch has been created in subversion from head
1126 The rc.d/jail script has been updated to support jail(8)
1127 configuration file. The "jail_<jname>_*" rc.conf(5) variables
1128 for per-jail configuration are automatically converted to
1129 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
1130 This is transparently backward compatible. See below about some
1131 incompatibilities and rc.conf(5) manual page for more details.
1133 These variables are now deprecated in favor of jail(8) configuration
1134 file. One can use "rc.d/jail config <jname>" command to generate
1135 a jail(8) configuration file in /var/run/jail.<jname>.conf without
1136 running the jail(8) utility. The default pathname of the
1137 configuration file is /etc/jail.conf and can be specified by
1138 using $jail_conf or $jail_<jname>_conf variables.
1140 Please note that jail_devfs_ruleset accepts an integer at
1141 this moment. Please consider to rewrite the ruleset name
1145 BIND has been removed from the base system. If all you need
1146 is a local resolver, simply enable and start the local_unbound
1147 service instead. Otherwise, several versions of BIND are
1148 available in the ports tree. The dns/bind99 port is one example.
1150 With this change, nslookup(1) and dig(1) are no longer in the base
1151 system. Users should instead use host(1) and drill(1) which are
1152 in the base system. Alternatively, nslookup and dig can
1153 be obtained by installing the dns/bind-tools port.
1156 With the addition of unbound(8), a new unbound user is now
1157 required during installworld. "mergemaster -p" can be used to
1158 add the user prior to installworld, as documented in the handbook.
1161 OpenSSH is now built with DNSSEC support, and will by default
1162 silently trust signed SSHFP records. This can be controlled with
1163 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1164 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1167 The GNU Compiler Collection and C++ standard library (libstdc++)
1168 are no longer built by default on platforms where clang is the system
1169 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1170 options in src.conf.
1173 The PROCDESC kernel option is now part of the GENERIC kernel
1174 configuration and is required for the rwhod(8) to work.
1175 If you are using custom kernel configuration, you should include
1179 The API and ABI related to the Capsicum framework was modified
1180 in backward incompatible way. The userland libraries and programs
1181 have to be recompiled to work with the new kernel. This includes the
1182 following libraries and programs, but the whole buildworld is
1183 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1184 kdump, procstat, rwho, rwhod, uniq.
1187 AES-NI intrinsic support has been added to gcc. The AES-NI module
1188 has been updated to use this support. A new gcc is required to build
1189 the aesni module on both i386 and amd64.
1192 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1193 Thus "device padlock_rng" and "device rdrand_rng" should be
1194 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1197 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1198 enables just the iconv* functionality and is now on by default.
1199 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1200 compatibility. Set WITHOUT_ICONV to build the old way.
1201 If you have been using WITH_ICONV before, you will very likely
1202 need to turn on WITH_LIBICONV_COMPAT.
1205 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1206 Illumos origin, including ZFS. If you have INVARIANTS in your
1207 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1209 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1210 locks if WITNESS option was set. Because that generated a lot of
1211 witness(9) reports and all of them were believed to be false
1212 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1213 can be used to achieve the previous behavior.
1216 Timer values in IPv6 data structures now use time_uptime instead
1217 of time_second. Although this is not a user-visible functional
1218 change, userland utilities which directly use them---ndp(8),
1219 rtadvd(8), and rtsold(8) in the base system---need to be updated
1220 to r253970 or later.
1223 find -delete can now delete the pathnames given as arguments,
1224 instead of only files found below them or if the pathname did
1225 not contain any slashes. Formerly, the following error message
1228 find: -delete: <path>: relative path potentially not safe
1230 Deleting the pathnames given as arguments can be prevented
1231 without error messages using -mindepth 1 or by changing
1232 directory and passing "." as argument to find. This works in the
1233 old as well as the new version of find.
1236 Behavior of devfs rules path matching has been changed.
1237 Pattern is now always matched against fully qualified devfs
1238 path and slash characters must be explicitly matched by
1239 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1240 subdirectories must be reviewed.
1243 The default ARM ABI has changed to the ARM EABI. The old ABI is
1244 incompatible with the ARM EABI and all programs and modules will
1245 need to be rebuilt to work with a new kernel.
1247 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1249 NOTE: Support for the old ABI will be removed in the future and
1250 users are advised to upgrade.
1253 pkg_install has been disconnected from the build if you really need it
1254 you should add WITH_PKGTOOLS in your src.conf(5).
1257 Most of network statistics structures were changed to be able
1258 keep 64-bits counters. Thus all tools, that work with networking
1259 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1262 Fix a bug that allowed a tracing process (e.g. gdb) to write
1263 to a memory-mapped file in the traced process's address space
1264 even if neither the traced process nor the tracing process had
1265 write access to that file.
1268 CVS has been removed from the base system. An exact copy
1269 of the code is available from the devel/cvs port.
1272 Some people report the following error after the switch to bmake:
1274 make: illegal option -- J
1275 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1277 *** [buildworld] Error code 2
1279 this likely due to an old instance of make in
1280 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1281 which src/Makefile will use that blindly, if it exists, so if
1282 you see the above error:
1284 rm -rf `make -V MAKEPATH`
1289 Use bmake by default.
1290 Whereas before one could choose to build with bmake via
1291 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1292 make. The goal is to remove these knobs for 10-RELEASE.
1294 It is worth noting that bmake (like gmake) treats the command
1295 line as the unit of failure, rather than statements within the
1296 command line. Thus '(cd some/where && dosomething)' is safer
1297 than 'cd some/where; dosomething'. The '()' allows consistent
1298 behavior in parallel build.
1301 Fix a bug that allows NFS clients to issue READDIR on files.
1304 The WITHOUT_IDEA option has been removed because
1305 the IDEA patent expired.
1308 The sysctl which controls TRIM support under ZFS has been renamed
1309 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1313 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1314 rather than creating it's own in the temporary directory in
1315 order allow access to bootstrapped versions of tools such as
1316 install and mtree. When upgrading from version of FreeBSD where
1317 the install command does not support -l, you will need to
1318 install a new mergemaster command if mergemaster -p is required.
1319 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1323 Legacy ATA stack, disabled and replaced by new CAM-based one since
1324 FreeBSD 9.0, completely removed from the sources. Kernel modules
1325 atadisk and atapi*, user-level tools atacontrol and burncd are
1326 removed. Kernel option `options ATA_CAM` is now permanently enabled
1330 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1331 and socketpair(2). Software, in particular Kerberos, may
1332 automatically detect and use these during building. The resulting
1333 binaries will not work on older kernels.
1336 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1337 information, see the respective 20130304 entry).
1340 Recent commits to callout(9) changed the size of struct callout,
1341 so the KBI is probably heavily disturbed. Also, some functions
1342 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1343 by macros. Every kernel module using it won't load, so rebuild
1346 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1347 but does not initialize by default (because of the new CTL_DISABLE
1348 option) to save memory. To re-enable it, remove the CTL_DISABLE
1349 option from the kernel config file or set kern.cam.ctl.disable=0
1350 in /boot/loader.conf.
1353 The ctl device has been disabled in GENERIC for i386 and amd64.
1354 This was done due to the extra memory being allocated at system
1355 initialisation time by the ctl driver which was only used if
1356 a CAM target device was created. This makes a FreeBSD system
1357 unusable on 128MB or less of RAM.
1360 A new compression method (lz4) has been merged to -HEAD. Please
1361 refer to zpool-features(7) for more information.
1363 Please refer to the "ZFS notes" section of this file for information
1364 on upgrading boot ZFS pools.
1367 A BSD-licensed patch(1) variant has been added and is installed
1368 as bsdpatch, being the GNU version the default patch.
1369 To inverse the logic and use the BSD-licensed one as default,
1370 while having the GNU version installed as gnupatch, rebuild
1371 and install world with the WITH_BSD_PATCH knob set.
1374 Due to the use of the new -l option to install(1) during build
1375 and install, you must take care not to directly set the INSTALL
1376 make variable in your /etc/make.conf, /etc/src.conf, or on the
1377 command line. If you wish to use the -C flag for all installs
1378 you may be able to add INSTALL+=-C to /etc/make.conf or
1382 The install(1) option -M has changed meaning and now takes an
1383 argument that is a file or path to append logs to. In the
1384 unlikely event that -M was the last option on the command line
1385 and the command line contained at least two files and a target
1386 directory the first file will have logs appended to it. The -M
1387 option served little practical purpose in the last decade so its
1388 use is expected to be extremely rare.
1391 After switching to Clang as the default compiler some users of ZFS
1392 on i386 systems started to experience stack overflow kernel panics.
1393 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1396 GEOM_LABEL now mangles label names read from file system metadata.
1397 Mangling affect labels containing spaces, non-printable characters,
1398 '%' or '"'. Device names in /etc/fstab and other places may need to
1402 By default, only the 10 most recent kernel dumps will be saved. To
1403 restore the previous behaviour (no limit on the number of kernel dumps
1404 stored in the dump directory) add the following line to /etc/rc.conf:
1409 With the addition of auditdistd(8), a new auditdistd user is now
1410 required during installworld. "mergemaster -p" can be used to
1411 add the user prior to installworld, as documented in the handbook.
1414 The sin6_scope_id member variable in struct sockaddr_in6 is now
1415 filled by the kernel before passing the structure to the userland via
1416 sysctl or routing socket. This means the KAME-specific embedded scope
1417 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1418 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1419 __FreeBSD_version is bumped to 1000025.
1422 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1423 This means that the world and kernel will be compiled with clang
1424 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1425 and /usr/bin/cpp. To disable this behavior and revert to building
1426 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1427 of current may need to bootstrap WITHOUT_CLANG first if the clang
1428 build fails (its compatibility window doesn't extend to the 9 stable
1432 The IPFIREWALL_FORWARD kernel option has been removed. Its
1433 functionality now turned on by default.
1436 The ZERO_COPY_SOCKET kernel option has been removed and
1437 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1438 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1439 mechanism which is not safe and may result in kernel crashes.
1440 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1441 driver supports disposeable external page sized mbuf storage.
1442 Proper replacements for both zero-copy mechanisms are under
1443 consideration and will eventually lead to complete removal
1444 of the two kernel options.
1447 The IPv4 network stack has been converted to network byte
1448 order. The following modules need to be recompiled together
1449 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1450 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1453 Support for non-MPSAFE filesystems was removed from VFS. The
1454 VFS_VERSION was bumped, all filesystem modules shall be
1458 All the non-MPSAFE filesystems have been disconnected from
1459 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1460 portalfs, smbfs, xfs.
1463 The interface cloning API and ABI has changed. The following
1464 modules need to be recompiled together with kernel:
1465 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1466 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1467 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1470 The sdhci driver was split in two parts: sdhci (generic SD Host
1471 Controller logic) and sdhci_pci (actual hardware driver).
1472 No kernel config modifications are required, but if you
1473 load sdhc as a module you must switch to sdhci_pci instead.
1476 Import the FUSE kernel and userland support into base system.
1479 The GNU sort(1) program has been removed since the BSD-licensed
1480 sort(1) has been the default for quite some time and no serious
1481 problems have been reported. The corresponding WITH_GNU_SORT
1485 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1486 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1490 The net80211(4) ABI has been changed to allow for improved driver
1491 PS-POLL and power-save support. All wireless drivers need to be
1492 recompiled to work with the new kernel.
1495 The random(4) support for the VIA hardware random number
1496 generator (`PADLOCK') is no longer enabled unconditionally.
1497 Add the padlock_rng device in the custom kernel config if
1498 needed. The GENERIC kernels on i386 and amd64 do include the
1499 device, so the change only affects the custom kernel
1503 The pf(4) packet filter ABI has been changed. pfctl(8) and
1504 snmp_pf module need to be recompiled to work with new kernel.
1507 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1508 to -HEAD. Pools that have empty_bpobj in active state can not be
1509 imported read-write with ZFS implementations that do not support
1510 this feature. For more information read the zpool-features(5)
1514 The sparc64 ZFS loader has been changed to no longer try to auto-
1515 detect ZFS providers based on diskN aliases but now requires these
1516 to be explicitly listed in the OFW boot-device environment variable.
1519 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1520 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1521 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1524 The following sysctls and tunables have been renamed for consistency
1525 with other variables:
1526 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1527 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1530 The sort utility has been replaced with BSD sort. For now, GNU sort
1531 is also available as "gnusort" or the default can be set back to
1532 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1533 installed as "bsdsort".
1536 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1537 Starting with this version the old system of ZFS pool versioning
1538 is superseded by "feature flags". This concept enables forward
1539 compatibility against certain future changes in functionality of ZFS
1540 pools. The first read-only compatible "feature flag" for ZFS pools
1541 is named "com.delphix:async_destroy". For more information
1542 read the new zpool-features(5) manual page.
1543 Please refer to the "ZFS notes" section of this file for information
1544 on upgrading boot ZFS pools.
1547 The malloc(3) implementation embedded in libc now uses sources imported
1548 as contrib/jemalloc. The most disruptive API change is to
1549 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1550 delete it prior to installworld, and optionally re-create it using the
1551 new format after rebooting. See malloc.conf(5) for details
1552 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1556 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1557 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1558 now spelled mips. This is to aid compatibility with third-party
1559 software that expects this naming scheme in uname(3). Little-endian
1560 settings are unchanged. If you are updating a big-endian mips64 machine
1561 from before this change, you may need to set MACHINE_ARCH=mips64 in
1562 your environment before the new build system will recognize your machine.
1565 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1569 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1570 nullfs(5) did not pass through all behaviours to the underlying layer,
1571 as a result if we bound to a socket on the lower layer we could connect
1572 only to the lower path; if we bound to the upper layer we could connect
1573 only to the upper path. The new behavior is one can connect to both the
1574 lower and the upper paths regardless what layer path one binds to.
1577 The getifaddrs upgrade path broken with 20111215 has been restored.
1578 If you have upgraded in between 20111215 and 20120209 you need to
1579 recompile libc again with your kernel. You still need to recompile
1580 world to be able to configure CARP but this restriction already
1581 comes from 20111215.
1584 The set_rcvar() function has been removed from /etc/rc.subr. All
1585 base and ports rc.d scripts have been updated, so if you have a
1586 port installed with a script in /usr/local/etc/rc.d you can either
1587 hand-edit the rcvar= line, or reinstall the port.
1589 An easy way to handle the mass-update of /etc/rc.d:
1590 rm /etc/rc.d/* && mergemaster -i
1593 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1594 on the current CPU and prevents other threads from running.
1595 This behavior can be reverted using the kern.stop_scheduler_on_panic
1597 The new behavior can be incompatible with kern.sync_on_panic.
1600 The carp(4) facility has been changed significantly. Configuration
1601 of the CARP protocol via ifconfig(8) has changed, as well as format
1602 of CARP events submitted to devd(8) has changed. See manual pages
1603 for more information. The arpbalance feature of carp(4) is currently
1604 not supported anymore.
1606 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1607 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1608 need to be recompiled.
1611 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1615 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1616 explicitely support non-MPSAFE filesystems.
1617 It is on by default for all supported platform at this present
1621 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1622 i386 and pc98 GENERIC kernel configuration files.
1625 sysinstall has been removed
1628 The stable/9 branch created in subversion. This corresponds to the
1629 RELENG_9 branch in CVS.
1635 Avoid using make -j when upgrading. While generally safe, there are
1636 sometimes problems using -j to upgrade. If your upgrade fails with
1637 -j, please try again without -j. From time to time in the past there
1638 have been problems using -j with buildworld and/or installworld. This
1639 is especially true when upgrading between "distant" versions (eg one
1640 that cross a major release boundary or several minor releases, or when
1641 several months have passed on the -current branch).
1643 Sometimes, obscure build problems are the result of environment
1644 poisoning. This can happen because the make utility reads its
1645 environment when searching for values for global variables. To run
1646 your build attempts in an "environmental clean room", prefix all make
1647 commands with 'env -i '. See the env(1) manual page for more details.
1649 When upgrading from one major version to another it is generally best to
1650 upgrade to the latest code in the currently installed branch first, then
1651 do an upgrade to the new branch. This is the best-tested upgrade path,
1652 and has the highest probability of being successful. Please try this
1653 approach if you encounter problems with a major version upgrade. Since
1654 the stable 4.x branch point, one has generally been able to upgade from
1655 anywhere in the most recent stable branch to head / current (or even the
1656 last couple of stable branches). See the top of this file when there's
1659 When upgrading a live system, having a root shell around before
1660 installing anything can help undo problems. Not having a root shell
1661 around can lead to problems if pam has changed too much from your
1662 starting point to allow continued authentication after the upgrade.
1664 This file should be read as a log of events. When a later event changes
1665 information of a prior event, the prior event should not be deleted.
1666 Instead, a pointer to the entry with the new information should be
1667 placed in the old entry. Readers of this file should also sanity check
1668 older entries before relying on them blindly. Authors of new entries
1669 should write them with this in mind.
1673 When upgrading the boot ZFS pool to a new version, always follow
1676 1.) recompile and reinstall the ZFS boot loader and boot block
1677 (this is part of "make buildworld" and "make installworld")
1679 2.) update the ZFS boot block on your boot drive
1681 The following example updates the ZFS boot block on the first
1682 partition (freebsd-boot) of a GPT partitioned drive ada0:
1683 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1685 Non-boot pools do not need these updates.
1689 If you are updating from a prior version of FreeBSD (even one just
1690 a few days old), you should follow this procedure. It is the most
1691 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1693 make kernel-toolchain
1694 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1695 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1697 To test a kernel once
1698 ---------------------
1699 If you just want to boot a kernel once (because you are not sure
1700 if it works, or if you want to boot a known bad kernel to provide
1701 debugging information) run
1702 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1703 nextboot -k testkernel
1705 To just build a kernel when you know that it won't mess you up
1706 --------------------------------------------------------------
1707 This assumes you are already running a CURRENT system. Replace
1708 ${arch} with the architecture of your machine (e.g. "i386",
1709 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1711 cd src/sys/${arch}/conf
1712 config KERNEL_NAME_HERE
1713 cd ../compile/KERNEL_NAME_HERE
1718 If this fails, go to the "To build a kernel" section.
1720 To rebuild everything and install it on the current system.
1721 -----------------------------------------------------------
1722 # Note: sometimes if you are running current you gotta do more than
1723 # is listed here if you are upgrading from a really old current.
1725 <make sure you have good level 0 dumps>
1727 make kernel KERNCONF=YOUR_KERNEL_HERE
1729 <reboot in single user> [3]
1736 To cross-install current onto a separate partition
1737 --------------------------------------------------
1738 # In this approach we use a separate partition to hold
1739 # current's root, 'usr', and 'var' directories. A partition
1740 # holding "/", "/usr" and "/var" should be about 2GB in
1743 <make sure you have good level 0 dumps>
1746 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1747 <maybe newfs current's root partition>
1748 <mount current's root partition on directory ${CURRENT_ROOT}>
1749 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1750 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1751 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1752 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1753 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1754 <reboot into current>
1755 <do a "native" rebuild/install as described in the previous section>
1756 <maybe install compatibility libraries from ports/misc/compat*>
1760 To upgrade in-place from stable to current
1761 ----------------------------------------------
1762 <make sure you have good level 0 dumps>
1764 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1766 <reboot in single user> [3]
1773 Make sure that you've read the UPDATING file to understand the
1774 tweaks to various things you need. At this point in the life
1775 cycle of current, things change often and you are on your own
1776 to cope. The defaults can also change, so please read ALL of
1777 the UPDATING entries.
1779 Also, if you are tracking -current, you must be subscribed to
1780 freebsd-current@freebsd.org. Make sure that before you update
1781 your sources that you have read and understood all the recent
1782 messages there. If in doubt, please track -stable which has
1783 much fewer pitfalls.
1785 [1] If you have third party modules, such as vmware, you
1786 should disable them at this point so they don't crash your
1789 [3] From the bootblocks, boot -s, and then do
1794 adjkerntz -i # if CMOS is wall time
1795 Also, when doing a major release upgrade, it is required that
1796 you boot into single user mode to do the installworld.
1798 [4] Note: This step is non-optional. Failure to do this step
1799 can result in a significant reduction in the functionality of the
1800 system. Attempting to do it by hand is not recommended and those
1801 that pursue this avenue should read this file carefully, as well
1802 as the archives of freebsd-current and freebsd-hackers mailing lists
1803 for potential gotchas. The -U option is also useful to consider.
1804 See mergemaster(8) for more information.
1806 [5] Usually this step is a noop. However, from time to time
1807 you may need to do this if you get unknown user in the following
1808 step. It never hurts to do it all the time. You may need to
1809 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1810 install) after the buildworld before this step if you last updated
1811 from current before 20130425 or from -stable before 20130430.
1813 [6] This only deletes old files and directories. Old libraries
1814 can be deleted by "make delete-old-libs", but you have to make
1815 sure that no program is using those libraries anymore.
1817 [8] In order to have a kernel that can run the 4.x binaries needed to
1818 do an installworld, you must include the COMPAT_FREEBSD4 option in
1819 your kernel. Failure to do so may leave you with a system that is
1820 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1821 required to run the 5.x binaries on more recent kernels. And so on
1822 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1824 Make sure that you merge any new devices from GENERIC since the
1825 last time you updated your kernel config file.
1827 [9] When checking out sources, you must include the -P flag to have
1828 cvs prune empty directories.
1830 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1831 "?=" instead of the "=" assignment operator, so that buildworld can
1832 override the CPUTYPE if it needs to.
1834 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1835 not on the command line, or in /etc/make.conf. buildworld will
1836 warn if it is improperly defined.
1839 This file contains a list, in reverse chronological order, of major
1840 breakages in tracking -current. It is not guaranteed to be a complete
1841 list of such breakages, and only contains entries since September 23, 2011.
1842 If you need to see UPDATING entries from before that date, you will need
1843 to fetch an UPDATING file from an older FreeBSD release.
1845 Copyright information:
1847 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1849 Redistribution, publication, translation and use, with or without
1850 modification, in full or in part, in any form or format of this
1851 document are permitted without further permission from the author.
1853 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1854 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1855 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1856 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1857 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1858 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1859 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1860 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1861 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1862 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1863 POSSIBILITY OF SUCH DAMAGE.
1865 Contact Warner Losh if you have any questions about your use of